I encounter an outbound dial problem with the EADS PBX. The topology is the Cisco 2611XM router using an E1 interface to connect the EADS PBX(the topology can not be changed). The EADS PBX has 60 copper lines to CO. The trunk link is using ISDN PRI and working fine. However, when my IP Phone needs to dial out. The IP Phone needs to dial 448(connect to the PBX internal specific number and get PBX dial tone) > 666 (PBX guys say this is their outbound access code, then get PBX dial tone) > 1234 (they say this is access code password, then get PBX dial tone) > 0 (CO dial tone). The PBX guys said it is the only way to connect outside(i think it is a lie). However, this is the situation what I meet and I cannot do any thing in PBX.
I know we can setup a prefix number in router or in CallManager. The result is I add a "prefix 448" in router dial-peer and user can ignore first digit without dial 448 now. I am thinking how to add all the prefix digits to make the user just push 0 to get CO dial tone for outbound dialing. That means I need to make router or callmanger to provide prefix digits 448 > 666 > 1234. Each digit needs a small time gap to wait the PBX gives the dial tone. I check document which said CallManager does not have pause function in prefix field. The router dial-peer command accept "," to have a second pause. However, when i added "," in prefix it does not work and the Phone hear nothing(no signal) until terminated.
Does anyone have the idea to solve the depressed question?
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...