We have a Cisco SIP phone which seems to go through the full blown re-registration process every 15 minutes and this is displayed on the screen of the phone. The phone uses TCP for the SIP connection as this is the only way it would work with the CME.
The first packet which initiates the process seems to be a TCP FIN from the CME to the Phone itself. The TCP connection is then torn down and the next packet seems to be the phone requesting the config files from the CME and the registration process occurs.
This exact same sequence of packets happen every 15 minutes and there is nothing within the CFG file for the phone or the CME config itself which show any timers.
I don't understand why the CME is tearing down the TCP connection which is then causing the phone to do a full blown re-registration?
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...