Jabber Registration Rejected

[refram]

I have now had a handful of instances where when I configure a Jabber phone in CUCM and hit Save, the phone comes back listed as "rejected".  I haven't even gotten to the part where I've entered a directory number for the phone yet, much less tried to get a user logged in.  Our standard naming convention for Jabber phones is "CSF" followed by a 5-digit alphanumeric username.  This issue continues to be a problem even if I change the name so that the letters are in lower-case as opposed to all caps.  If I change any of the letters in the name to a different letter, or leave some of the letters off, the phone has no problems.

In the past this has only happened very occasionally, and only when we did a "super copy" of an existing Jabber phone, so the workaround was to create the phone from scratch.  However, the last couple of times creating the phone from scratch has not worked either.

We want to keep our naming configuration.  Does anyone have a solution to this?

[Flo.Matalis]

Hi, what CUCM version are you using? If 12.5, your naming should be supported. In fact,

Cisco Unified Client Services Framework

Valid characters: a–z, A–Z, 0–9. 15-character limit.

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_5/DIG_OnPrem/cjab_b_on-premises-deployment-cisco-jabber_125/cjab_b_on-premises-deployment-cisco-jabber_125_chapter_01010.html

As for the "Rejected" status, I encountered this as well and Directory Number is mandatory for a SIP device.

[Nithin Eluvathingal]

I haven't even gotten to the part where I've entered a directory number for the phone yet:- Configure the directory for the CSF device. Make sure you complete all required configurations for jabber device. 

[refram · Accepted solution]

It turned out the issue was that we had replication problems on the cluster.  When we resynchronized the tables we were able to create the phones with our standard names.