10-17-2006 09:28 AM - edited 03-15-2019 04:38 AM
I'm trying to get an IP Communicator 2.0.1.1 to register with CM 4.1(3). There is no problem with the device name and the phone is properly provisioned in CM. However, I get the error "Error Updating Locale" on the IP Communicator.
When I look at the TFTP error log on the CallManager, I see the following:
File not found inside tftp() English_United_States/ipc-sccp.jar]
File not found inside tftp() [United_States/g3-tones.xml]
Which I believe to be the source of the error. Why are these files not present in the TFTPDIR? Where do I get them from?
Solved! Go to Solution.
10-17-2006 09:50 AM
This message means that IP communicator tries to look for Locale files
which are not present on Callmanager. This is a known issue, this
message is seen when communicator is launched for first time. You can
safely ignore this error message, as it is harmless message. It does not
have any impact on functionality of communicator.
IP communicator currently supports 2 locales - English and French only.
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/i
pc/relns/ipcrn115.htm
Error message indicates that it is defaulting to the built-in locale -
i.e. English.
To avoid this error message - you can try forcing the Network Locale to
"United States" and "User Locale" to English United States from
Callmanager configuration pages for IP Communicator device.
10-17-2006 09:50 AM
This message means that IP communicator tries to look for Locale files
which are not present on Callmanager. This is a known issue, this
message is seen when communicator is launched for first time. You can
safely ignore this error message, as it is harmless message. It does not
have any impact on functionality of communicator.
IP communicator currently supports 2 locales - English and French only.
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/i
pc/relns/ipcrn115.htm
Error message indicates that it is defaulting to the built-in locale -
i.e. English.
To avoid this error message - you can try forcing the Network Locale to
"United States" and "User Locale" to English United States from
Callmanager configuration pages for IP Communicator device.
10-17-2006 10:26 AM
Your response got me looking elsewhere, and it looks like you are right. My problem turned out to be a DNS one. The "locale" errors were not the problem at all.
Thanks.
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