Could not register Cisco IP Communicator.

[raso]

I am unable to register Cisco IP Communicator. The device shows registering all the time. I know we need to look at EventView logs from CUCM. But when I download the logs it shows nothing. I am using TranslatorX to read the logs. Any other troubleshooting can help to resolve this issue? Its a CUCM 11.5 cluster. Please advice

[raso]

Can someone help on this topic

[Roger Kallberg]

Have you configured a TFTP server in your CIPC application?

[raso]

Yes I configured TFTP 1 and 2 in CIPC application. I given the correct device name as well. I can register to another cluster but not the cucm cluster I want to register 

[Roger Kallberg]

Then I have no idea, other than resorting to doing a packet capture with Wireshark on the computer and checking if it can reach the CM.

[Maren Mahoney]

What does the Status Messages on the CIPC read? Also, can you ping the IP address of the host PC from the cluster you are trying to register to?

Maren

[Nithin Eluvathingal]

As @Maren Mahoney mentioned, what does status message on CIPC says.

Does this device  has been added on the cluster if you are not using auto registration.

[raso]

There was a firewall block reaching to TFTP server. It was resolved. Even after that, the Cisco IP communicator is not registering.

It says keep registering and there is a red color X symbol on the top of DN. Attached screenshot . I do not find any logs on the Eventviewer and syslog. Please help me to resolve the issue 

[Maren Mahoney]

The Status Messages would be on the phone itself. Press the Settings button, then scroll down to Status and view the Status Messages. What does the phone tell you?

Maren

[raso]

@Maren Mahoney  Thanks for the reply. The status message shows the below

<devicename>.cnf.xml

No Trust List Installed.

The above two messages are there in the status messages. The CIPC able to get the cnf file from TFTP server. The only problem is the CIPC display keep says registering and the DN shows red X on the phone icon.

[Leo Laohoo]

Factory-reset the phone and delete the CTL.

[raso]

@Leo Laohoo  I did the reset and deleted the CTL. But still the CIPC shows registering and red X symbol on the DN.

Status messages shows 

<Device Name>.cnf.xml

CTL Update failed

Please let me know when other logs can help to resolve the issue

[Maren Mahoney]

So the phone indicates that it is able to download its CNF file? (No mention of XMLDefault.cnf.xml?) 

And if it is able to receive its CNF file, then it has the right information. As CIPCs don't get ITL files, that shouldn't be an impediment.

Suggestion 1: If the Web Client is enabled on the CIPC, go to http://<ip.of.cipc> and then go look at the log file (or share it if you like) to see if the problem is shown.

Suggestion 2: Exit the CIPC software, go into %appdata%/Roaming/Cisco and delete the IP Communicator folder. Then go into %appdata%/Local and do the same. Then re-launch CIPC which will cause it to need to be reconfigured with its information, but will clean out anything that might make the client be 'stuck'.

Suggestion 3: Delete the CIPC phone from CUCM, restart the TFTP service just to be safe, then rebuild the CIPC in CUCM. 

Maren

[raso]

@Maren Mahoney 

Yes, the CIPC is able to download the CNF file from TFTP server

Suggestion 1 -> I could not do because I do not see the IP address for the CIPC in CUCM.

Suggestion 2 -> I followed this. After delete both Communicator folder I re-launched CIPC. First time the application is crashed. I re-launched again. It shows updating locale. Then the display shows the same as registering and Red X sybmol on the DN.

Suggestion 3 : Rebuilt the CIPC in CUCM but I do not want to restart the TFTP service just for this one device.

[Maren Mahoney]

If it showed "Updating Locale" then the phone is absolutely talking to CUCM. How interesting! 

Are you running the phone as SIP or SCCP? And does that agree in Model (CIPC) and protocol in CUCM?

There is a log file for CIPC in that IP Communicator folder in either Roaming or Local, I don't remember which. You'll have to dig around for it but it might show what's going on.

It might also be worth looking at the CallManager trace file to see what is going on with the registration messages from the phone.

Maren