Route patterns in CallManager and dial-peers in the gateway work hand in hand. They are not necessarily mutually exclusive, and the use of one does not mean the other is not needed.
If IP phones are registered on the CallManager and they are expected to be able to be able to place calls out, then the CallManager must have route patterns which determine how CallManager will handle the numbers dialed, and where the call will be sent.
If a call must be routed through a H.323 VoIP gateway, then the gateway must have dial-peers configured, because dial-peers is the method by which the gateway determines what to do with the call.
For outgoing calls where you have CallManager controlled phones, you must have both route patterns and dial-peers configured.
For incoming calls, the gateway will always use dial-peers. The CallManager does not require route patterns to accept incoming calls.
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...
[toc:faq]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 discusse...