1. Make sure CUCM is reachable from the jabber client PC. If the server is configured as hostname or FDQN under System – Server of CUCM administration, verify on the reachability towards the same. Verify on the DNS configuration if there is reachability issue while using hostnames / FQDN.
2. Verify on the TFTP configured for the jabber. TFTP should be configured in IM&P server administration
Navigate to IM&P admin page --- Application --- Legacy Clients --- Settings. This should point to the CUCM server, which has the TFTP service running.
3. Verify on the CCMCIP configuration:
Navigate to IM&P admin page --- Application --- Legacy Clients --- CCMCIP. This should be pointing to the CUCM server, which has the Cisco Call Manager IP phone service running.
Make sure the jabber user is associated with the CCMCIP profile.
4. Check the SIP Profile for the “Timer Register Delta” Configured. From the CSF device, find out the SIP profile configured.
Navigate to CUCM admin page --- Device --- Device Settings --- SIP Profile --- Find the SIP Profile applied on the CSF device --- look for “Timer Register Delta”
The default value for this is 5 and having a large value here would affect the jabber windows registration. Value between 5 to 10 is normal for a proper registration on a stable network.
5. The CSF line should have the end user associated with it. Find the CSF device configured for the user, navigate to DN configured à Verify that the end user is associated to it.
