Hi, I'm new in CUCM and i'm working on my lab with the CUCM 7.x Business Edition on VMWare and the Cisco IP Communicator by now. I have configure a ISR2821 as a MGCP Gateway (which also has a VIC2-4FXO card).
Right now I'm defining the route patter to do calls from my PC to outside the PSTN.
My IP Communicator has configured two lines 1000 and 1001. When I try to call the 1001 from the 1000 the soft-phone starts to ring immediately. This happens without configure the route patterns.
Once I configure a route pattern (i.e: !) all the calls, internal and out the PSTN has the T302 timer delay (for my case is set at 5000ms). So if I want to call the 1001 from the 1000 I have to wait 5 seconds to receive the Ring-in at the 1001 line. The same for the calls made out the PSTN.
Later I add the # symbol in the route patter (i.e: !#) to get the call routed immediately I press the # symbol without the need to wait the T302 timer to finish, but the result was the same.
So, I have tow questions:
1. Why does the internal calls have a delay (T302) when I configure a Route Pattern? It does not suppose to work the same with or without the route pattern, at last, are internal calls.
2. I have understood that the '#' symbol works marking the end of the number dialed, and this was usefull in the case I don´t want to wait for the T302 timer to finish. How does this wildcard actually work??
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...