I am having a problem with incoming calls on one of my remote gateways. Calls from area code that begin with 9 are not being completed - outside users are getting fast busy when they dial from these area code (ex 908, 970, 973)
I ran a debug voice dialpeer on the gateway and noticed that when users from these area code dial in, the call is matching dial-peer 1, however, when users call from other area code the call matches dial-peer 999011 which is correct. For the time being I have shut down dial-peer 1,2,3,4 to force calls to use the MGCP dial-peers. However, for SRST purpose i would need to use these dial-peers for outbound calls. Any suggestions?
Oct 24 18:55:12 EDT: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7326611000, Called Number=, Voice-Interface=0x452F6E1C,
Just put service mgcpapp under the rest of the dial-peers, and make sure you have MGCP fallback setup properly and then when the MGCPAPP service isn't available all those dialpeers will fall back to H323 mode including the dial peers starting with 999. You could put destination-pattern commands on those peers also.
The reason why the 1 is being used, the calls wil hit the first dial peer with the port on it which is configured for H323 mode and not MGCP.
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...