You can't really 'move' or 'merge' a system from one TMS to the other, i.e. two completely different databases. Therefore, you can add the system to the other TMS (either manually or automatic discovery methods) and then do an enforce management settings on those systems to reflect your other TMS. You'd then want to remove all the systems from the former TMS and/or take the other TMS down since if not, you'll effectively have two TMSs fighting over the same system.
Can you use the AdminTool>Configuration>Netwroks>Advanced Network Settings for Systems on Public Internet/Behind Firewall setting on the old server to tell the system behind firewall that they need to now use a different address? ( new TMS server address) If you have auto discovery of SOHO system enabled on the new server then they should appear in the new TMS?
I suspect you may need to reboot the endpoint first but I have not tested this
That's a good thought Garvan since Martin now mentions most of these systems are Behind the Firewall. And are your External Services also 'On' and configured on these systems to reflect the new TMS server?
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...