I have a CS 1000 running over a PRI. One of the external services we use to process calls requires that we embed a pause in the dial string. As an example:
Certain calls to certain area codes and exchanges will be routed through this external service. When the CS 1000 see's someone has dialed particular combination of digits, it picks an outbound trunk, dials an access number NPA-NXX-XXXX to the service, and waits for dial tone (the remote switch provides the dialtone once the connection is made) once the remote switch dialtone is received (it's jsut simpler to use a pause on the diling end rather than try to build a detection scheme), the dialing end sends a series of authorization digit, followed immediately by the original digits dialed. Sort of like the old LD cards used to work.
Here the logic:
User dials NPA1NXX-XXXX, CS-1000 recognizes NPA-NXX (in an ars table or least cost routing), and determines the call should be routed over an external service providers network, CS-1000 captures dialed digits, selects the appropriate trunk, dials (digit insertion) the remote access number NPA-NXX-0000, and waits for dialtone. After the pause, CS-1000 sends the authorization digits XXXXXXX (again, digit insertion), followed by the NPA-NXX-XXXX originally dialed by the user. The problem I have, and that is seemingly unique to Nortel, is that I can't get a pause to work over a PRI interface. Similar system from other brands have accomodated this capability, or allowed me to manipulate the 'end of dial string' function. I can't even find either a pause, or end of dial string reference in the Nortel documentation.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.
Your password has been sent to:email@example.com
To follow this tag...
Thanks! We'll email you when relevant content is added and updated.
Share this item with your network: