[cisco-voip] CSF Device name and format - Discrepancy between older docs, online help and reality - CUCM 10.5.2

[Anthony Holloway]

Here is the database rule which governs the name format for a CSF device:

admin:run sql select name, tkmodel, devicenameformat from typeproduct where
name like '%Client Services Framework%'
name                                    tkmodel devicenameformat
======================================= ======= =================
Cisco Unified Client Services Framework 503     [a-zA-Z0-9]{1,15}

So, the documentation is obviously incorrect, because we can see that in
two places the validation regex does not contain "dot" nor can it be longer
than 15 characters.

As an added bonus, the BOT, TCT, and TAB devices require all upper case
letters, and *do* support dot, as well as dash and underscore.

admin:run sql select name, tkmodel, devicenameformat from typeproduct where
name like '%Dual Mode%' or name like '%Tablet%'
name                        tkmodel devicenameformat
=========================== ======= ====================
Cisco Dual Mode for iPhone  562     TCT[0-9A-Z._-]{1,12}
Cisco Jabber for Tablet     652     TAB[0-9A-Z._-]{1,12}
Cisco Dual Mode for Android 575     BOT[0-9A-Z._-]{1,12}


On Tue, Jun 2, 2015 at 6:02 PM Brian V <bvanbens at gmail.com> wrote:

> I have a customer where the username has a dot "." in it.  First.Last
> Cisco's docs recommend to make the CSF device name be CSF + Username.
> I know this is not required anymore but many customers like the
> consistency of that naming standard.
> On my current customers CUCM 10.5.2.10000-5 when i try to add a CSF device
> with a dot I get the error message that the device name should contain the
> valid characters [a-zA-Z0-9]{1,15}  which seems to imply it can only be 15
> characters long and contain letters and numbers only
> [image: Inline image 1]
>
> On my current customers CUCM 10.5.2.10000-5 server the online help says
> that CSF devices can contain the following:   "Enter a text name for the
> Client Services Framework. This name can comprise up to 50 characters.
> Valid characters include letters, numbers, dashes, dots (periods), spaces,
> and underscores."
> [image: Inline image 2]
>
> CSF doc for 9.x says the same thing that dot, dash, underscore and
> length=50 is ok
>
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmcfg/CUCM_BK_CDF59AFB_00_admin-guide-90_chapter_01101001.pdf
>
> CSF doc for jabber 10.6 doesn't mention any requirements for the name but
> does recommend using CSF+Username as the format.
>
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and_chapter_0101.html#CJAB_TK_C7F0CAD6_00
>
> There is a support community posting about this referencing a bug that
> states it wont be fixed.
>
> https://supportforums.cisco.com/discussion/12387151/does-jabber-csf-device-support-username-contain-dot
> https://tools.cisco.com/bugsearch/bug/CSCus90842/?reffering_site=dumpcr
>
> So is there a documentation bug or did Cisco change the rules somewhere
> along the way ?
>
> Is there any definitive documentation that states the proper naming
> standard for the CSF device and the other Jabber device types (BOT, TCT,
> TAB)
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150602/1c18dacb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 23731 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150602/1c18dacb/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 3700 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150602/1c18dacb/attachment-0001.png>