Set up the CTI on CM and CallHandler, that works fine.
Within the AA I have set up the user input such to go to another Callhandler.
e.g press 1 to go to XYZ location.
Once in the new call handler they are then prompted to enter the number they wish to call. So far so good.
But when I enter the number to call its says it cannot be connected.
I have added the number 6123* in the Call routing and restrictions to support this, this then should route to CM and onto the gateway. I can see the DTMF information being placed in the traces on Unity but the call will not transfer and does not go back to CM.
What am I doing wrong or what do I need to set up to allow a call to an external number
Is 6123 a number on CCM or something used to route externally? Is there another entry higher up in the restriction table that 6123* might be matching that is not set to "Allow this String" - Yes
You can modify the predefined restriction tables, and you can create up to 100 new ones. You can also add up to 100 dial strings to a table. New dial strings are automatically inserted into the restriction table as Dial String 0. Note that the order of the dial strings is very important because Cisco Unity sequentially compares a phone number to the call patterns in the restriction table, starting with Dial String 0. If a number matches more than one call pattern, the number is handled according to the first call pattern it matches.
I though by using the the * wildcard then I would not need to specify the amount of digits, according to the Unity docs the ? is any single digit, the * is any one or more digits.
Would the ability to dial back out through callManager have naything to do with the restriction of the Ports as when installed using the wizard and Cisco Guides they instruct then Ports with the expcetion of the pilot to be in their own Partition and CSS to eliminate Toll Fraud etc.
That could definately be the problem. Can you try putting a phone in using the same CSS and see if you can dial the applicable number. I have seen similar problems before.You could also change one the ports to a known CSS (that has the proper dial-out access)
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...