07-05-2021 05:34 PM
Hi All
facing jabber registration issue with call manager version 12.5 when Jabber Version(12.9.3) uses the device security profile with security mode is 'Non Secure' and Transport Type 'UDP'. But registers successfully when transport type changes to 'TCP+UDP' in Phone security profile. All firewall ports are allowed since trying to register the Jabber from Windows machine which has same subnet as Call manager.
Jabber error notification says 'Connection to Phone Service failed' and Error code is CJ:2100:2
07-05-2021 06:40 PM - edited 07-05-2021 06:41 PM
You need to keep the Transport Type for Non secure TCP/UDP. Go through the below guide and see the session Ports and Protocols.
07-05-2021 07:22 PM
Hi Nithin
Thanks for your reply.
customer having call manager version 10.5(2) with Jabber version 12.0 which configured and running with transport type 'UDP' and security mode 'Non-Secure'. Now we are planning to upgrade the CCM 10.5 to 12.5, so hereafter Jabber should configured with transport type 'TCP+UDP' for successful registration with Call manager?
Best Regards
07-05-2021 09:08 PM
Default Non Secure profile comes with TCP +UDP. Use it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide