can you guys point me in the right direction - i have a branch office that cant dial information. the route patterns dial peers are not a strong point for me. i have read some cisco white papers concerning dial plan but it is so complicated - i need to begin at the very basic level - recommendations?
It would help if you post the dial-peer config, but I'll make a guess and try to help out. Also, you mention route patterns, typically it's one or the other.
First, I agree, it takes a while to get dial-peers straight, especially after you've worked with CallManager for so long.
I've just gone through a crash course of learning how to program dial-peers because we're implementing SRST on the branch router.
The one thing that slipped by me is how a POTS dial-peer behaves over a voip dial-peer. With a POTS dial-peer, only the non-explicity matched digits are forwarded by default. So, if you have a dial-peer that is 9411 then it is explicitly matching all digits and none are forwarded. You would need to add a "prefix 411" or "forward digits 3" to the dial-peer to make it work.
A sample is below:
dial-peer voice 411 pots
If you are using CoR lists, then I would suggest removing the CoR lists and getting things working simply.
Once you get dial-peers working, then you can revisit CoR lists.
If you are having problems getting 9.411 to work with CallManager route patterns, i.e. CCM controlled gateways, then you'll have to look at your transformations on your route pattern, route list and route groups.
Again, make it simple, point the route pattern to the gateway directly if you can to simplify things. Otherwise, remember that the settings of a route list overwrite those of the route pattern. Depending on your trunk, you'll likely need to do a 'drop pre-dot' on the pattern.
Let us know how that helps or doesn't and we'll follow up.
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...