Re: MGCP issue with incoming calls (CUCM 6.1) after change from
You have 2 working solutions:
1/ If possible (but I don't think it's available with 6.1), uncheck the "Urgent Priority" in the Translation Pattern 03928171. The call will not be routed immedialty when the Translation Pattern is matched, if an another Translation Pattern or Directory Number can be called by adding a digit.
2/ If the 1st solution is not possible, then delete your existing translation pattern, and replace it by a Directory Number 03928171. Then you can configure a Call Forward All to act like a Translation Pattern. As soon as there are other matches by adding digit, the call will not be routed immediatly.
In both case, when you will dial the main number, you will wait the T302 timeout, so don't let the default 15sec.
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...