The problem you describe is quite general, do you have any details of what might have changed? Upgrade of TMS? Change on the network? Firewall? Are all endpoint affected or only few? If all are affected then the issue is most likely tms (web server). There are lots of other threads in this forum discussing pb issues. Have you tried searching the existing threads?
To cover the basics if all the connectivity factors and management settings are OK. The only thing you need to do in TMS is to set the phonebooks on the systems. If the systems have the phonebooks set and they still do not get anything then it might be a connectivity issue as all pb requests are live. Here there is a number of things that can be the issue, the most common being the Public folder in the IIS server hosting the TMS web interface having an authentication issue. To troubleshoot this you can do a wireshark on the TMS server it self and see what is being received and sent when the ep does a pb request.
If this is all greek to you, you might be better off opening a TAC case. But you said it was working before right? Then something must have changed...
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...
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 discusses the bas...