cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6068
Views
0
Helpful
19
Replies

CUCM - Soft Phone IP Communicator 8.6.6

vipclubber
Level 1
Level 1

VOICE SYSTEM: Cisco Systems Small Business Pro UC560-FXO-K9 V01
PHONES: Cisco CP-7975G IP Phone Gig Ethernet, Color and 8 Lines

FIREWALL: Juniper SRX650-BASE-SRE6-645AP
SWITCH: JUNIPER 650 VLAN POE of 24 Ports
SIP PROVIDER: VOIP Innovations.

 

My Cisco phones are functioning well with UC560.

The issue is soft phone IP Communicator version 8.6.6.0

It seems to be able to contact TFTP server from my PC Win 10 and obtain IP address but no dial tone.

 

Do I need to install Call Manager and if so what version will be compatible with my UC560 box? Is there another way?

 

If needed, I am planning to deploy Call Manager on vmware 6.5.

Any advice is appreciated.

2018-04-05_19-16-42.jpg

19 Replies 19

Lost and confused. Are you refering to the link within the link?

 

Cisco Unified IP Phone 6921, 6945, 7906, 7911, 7921, 7931, 7941, 7961, 7970, 7971, 8941, 8945, and Cisco IP Communicator—You must download locale files to support the system-defined locales and store the files in flash memory, slot 0, or on an external TFTP server. See Install System-Defined Locales for Cisco Unified IP Phone 6921, 6945, 7906, 7911, 7921, 7931, 7941, 7961, 7970, 7971, and Cisco IP Communicator.

 

If so there is too much info, what specifically are you pointing to and what should be done next?

Please spell it out if possible.

If you have access to CCO and can download software, you should be able to download the locale files (g3-tones.jar etc), add to the flash on the UC and configure TFTP bindings so that the CME can provide these files to the phones.

Now, from an early screenshot the CIPC was reporting that it cannot reach the TFTP server which in case of CME would be the UC. Are they both reachable to start with ?

Do a "debug tftp events" and see if the CIPC request for CNF file even reaches the CME.

Nipun,

 

The OP did say that the host PC can reach the TFTP IP address, and he posted a CIPC log file that shows the phone successfully downloading its cnf.xml file but later failing when downloading the localization files.

 

vipclubber,

 

Here is a link to the localization files on Cisco's website. Locate your version of CCME on the left and select the Locale file on the right. You will need to log in with your CCO account to access this link, and will need an active service contract to download the locale file.

https://software.cisco.com/download/home/277641082/type/282897001/

 

The links are the detailed instructions, but the short answer for installing them is:

Download the locale file from cisco.com

Unzip and locate the English Localization files

Copy the files into the flash on your router

Add the TFTP commands to your router that make the files available.

 

Hopefully this gives you enough information to follow Cisco's more detailed instructions.

It's very rare that the localisation update would cause the CIPC to not register. I have seen it happen only a couple of times. If the CIPC is getting a config file and is able to establish port 2000 TCP, phone should register. It should just bypass the locale request with a "Error Updating Locale" message and continue with registration. Locale download should not be a mandate.

We still don't know what is happening on the CME side of things. A quick TCP and TFTP debugs on the CME side will should isolate the issue further. Adding locale files to the CME is not a bad option either.

I agree it's rare, but is what is indicated in the log file. Yes, a debug tftp events would be helpful to double-check that.