I would consider the use of the Multiservice IP-IP Gateway (aka. Session Border Controller). This is an IOS feature which runs operates with a "via-zone" Gatekeeper (co-resident on the IPIPGW box).
I used this, and mapped my 7985 and VTA DNs (registered the CallManager) onto valid E.164 addresses with the necessary zone prefixes configured on the gatekeeper, which in turn, was registered with a Directory Gatekeeper.
The IPIPGW effectively re-originates call legs, effectively hiding the internal structure of the network (helping to solve the NAT issues with video conferencing), and the IPIPGW controls call admission control and can optionally support RSVP.
CallManager provides the interoperability between Skinny (SCCP) endpoints and more traditional H.323 VC endpoints. The IPIPGW can also provide interoperability between H.323 and SIP (usually used in this context to connect to service provider trunks).
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...