I am trying to give access to users on an Avaya PBX linked over a PRI trunk to my system speed dials on CallManager. The system speed dials in CCM are #XXXX. I am providing dialtone to the Avaya, so they go off hook, get dialtone and can call my users fine at their 4 digit extension.
But when they try to access my #.... destination pattern they get fast busy as soon as they press the #.
I have never led off a pattern with a # before in a router, so I wanted to know if anyone else had any ideas.
The # does not signify a matched digit in call manager. This signifies as follows: The octothorpe (#) character generally identifies the end of the dialing sequence. Ensure the # character is the last character in the pattern.
You may need to use an actual digit to signify the beginning of your wild-card pattern. Just be sure you dont overlap your dial-plan.
**Just reread, and you are specifying your dial-peer. Can you post your dial-peer? Immediately after pressing # your users get a fast busy? Do you have your avaya system recognizing the # and sending the digits to the gateway?
then I have VOIP dial peers with destination-patterns of .... that match my 4 digit extensions. That is working OK
So if I do a VOIP dial peer of #...., it gives up right after you hit #
In the CCM, the numbers are all configured as directory numbers, not phones. They have no partition so they can be called from anywhere and a CSS of International.
My gateway is configured with internal calling CSS only, but if the DN's are no partition I would assume I could forward to that. I actually tried matching the gateway CSS with the DN CSS, but the behavior was the same.
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...