Has anyone had any success getting this phone to register to Call Manager? I have been jumping through hoops all day - I am not able to get the phone to register to CM. It gets an IP Address from the DHCP server and I have hard coded the Call Manager's IP address with port 5060 and udp trans etc. I also created a end user for the digest credentials.
I have been tasked with making this work in a 8.5.1 cluster. The best I can do so far is see in RTMT traces that the phone is trying to pull it's MAC.cfg file. I do see it attempt to also pull a 000000000000.cfg file for it's base configs but I would hate to have to hand code each phone's config file in to the TFTP server to make this SIP phone work. Has any one mde one of these work in UCM as either SIP basic or SIP advance? If they have made one work was with another firmware load and if so what. Thanks we just aquired over 100 of these when we aquired another small company and they would like to keep this handset if possible for a bit before we completely over-haul them.
Polycom ip450 phone has the 22.214.171.124 firmware on it.
Communications Manager won't build configuration files for 3rd party phones. There is no standard configuration file format so each vendor has their own unique format. You will need to build the configuration file for the phone and either upload it to the CUCM TFTP server or another 3rd party server.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...