we have a customer with 4 TX 9000 systems and registered with TMS server for the OBTP scheduling features. When I added CUCM (8.6.2)registered endpoints to the TMS Server (13.2.2), I noticed the TX 9000 system have a SIP URI in the TMS server same as a DN in the CUCM.
DN for the TX 9000: 123456
SIP URI in the TMS: 123456
We have a TMS upgrade (14.3.2)recently to fix the TMSXE issue. After the upgrade we have noticed the SIP URI for the TX 9000 in the TMS Server have been changed from 123456 to email@example.com.
Now, when they schedule the Conference with a OBTP, the Conference connection settings for the TX 9000 is firstname.lastname@example.org, where email@example.com is the Telepresence server SIP URI for the scheduled conference. TX 9000 can't dialled SIP URI and couldn't connect to the scheduled conference. This SIP URI in the TMS Server may be changed randomely in the TMS Server, not sure yet.
Have anyone experienced these issues with the TMS Server version 14.3.2 and CUCM 8.6.2?. or is there any fix for this issue?
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...