I would like to ask if we can have a 2 TMS server in an environment having same devices that was registered to it. The 1 server is just only for testing/POC. Will there be any effect on the management?
Most definitely...meaning you can't have two management systems 'fighting' over the same devices, as well as a whole lot of other services and functions TMS provides to those devices. Therefore, this is not supported nor recommended.
You can have two TMS in your network, however only 1 will be active at a time and in case of failure of 1st one, second TMS will take over. The database replication will remain same for both of them i.e SQL database would remain the same.
For more information, you can refer the below guide. :-
@Saurabh: If he is looking at this from a TMS Redundancy point of view...meaning one TMS sql db (aka tmsng)...then I totally agree However, and as he said 1 x TMS would be for testing, I read this has being he wanted two totally seperate TMSs...meaning two seperate sql dbs.
And with that said, and the fact the TMS is all about the sql db, I don't think he would want to be "testing" by setting up a second TMS pointing at a "production" TMS deployment.
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...