You delete that registration, and re-add it using the hostname instead of using the default local registration.
Right-click on the (local) entry and click "Delete SQL Server Registration". Then right-click on the SQL Server Group and click "New SQL Server Registration". Enter your CallManager's hostname if you need to, but it should be present already in a list you can pick from. Use Windows authentication, and choose to add it to your existing group.
Does recreating the registration in any way effect a production Callmanager? I have a subscriber CM that has been offline for some time ... in re-establishing the subscription I realized the "(local)" registration and need to fix. I need to confirm that the active Callmanager will not be effected. Thanks.
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...