I got several Polycom HDX endpoints which are correctly registered to TMS. On the systems located at the same LAN (but diffrent IP Subnets) I mapped a manual phonebook. Everything is fine so far. It is not possible to map this manual phonebook to systems at remote sites, there it is only possible to map a phonebook with all the registered endpoints in it. The remote sites are connected over a VPN and there is nothing blocked between the endsystem and TMS. Is there a limitation in mapping manaual phonebooks or does anyone have an idea, why I suddenly can't map this manual phonebook anymore?
Are you not able to set the phonebook for the system in TMS? Or are the endpoints not receiving the phonebook data? WHat are the details of the phone book contacts? SIP? H323? IP? Have you tested with disabling the "route phonebook entries" in the TMS under the general settings page?
I'm able to set the phonebook in TMS, but on the Polycom I never get the green check mark. The phonebook consists only manual SIP entries. I tried to disable "route phonebook entries" in TMS, this is resulting in a green check mark on the system, but the phonebook entry on the endpoint is empty (no SIP address, no IP address), it's just empty exept of the name.
Leave the setting for route phonebook entries to on. On the Polycom endpoint, does it still show a green check mark in the GDS listing? Uncheck register and click update. Uncheck the "Save Global Directory to System" option. With this enabled, there coulc be an issues with the Polycom caching onld phonebook data. Check register and click update. It would be normal for the icon displayed to be the diasabled symbol as the Polycom is not fully aware of the registration yet to the PLCM service on TMS. Navigate awat from the page, and then go back. By then you should see it is a green check mark. Now go to the Place a Call page, and select the directory option. What do you have listed?
During this procedure, you could run a packet capture on TMS to verify was is being reguested. The listening port on the TMS is TCP 3601. The traffic is in clear text, so you should be able to read it.
An other quick question: Is the Polyom registered to a gatekeeper or is it stand alone? If registered, is it SIP or H323?
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...