Interesting. Can you explain a little more or perhaps give us an example? This (like many other things) wasn't discussed in CVOICE (or CIPT) classes. Of course there's only a week's time to cover 4 weeks of material
you will need an access code since XXXX can be anything within a NPA-NXX area, or almost anything.
In this example 9 is for outside calls and let's say internal DN's are in the 5XXXX and 6XXXX range. So 8 can do or anything for that matter. * or # would work but let's go with 8.
User will dial 8XXXX where the XXXX is the last 4 digits of the LD number you are trying to dial.
That will hit a translation pattern the will strip the 8 and add the 9.1xxx-xxx in front of the XXXX making a LD call.
That will match a route pattern and send the call out the appropriate gateway.
Yes they will need to dial 5 digits, but if they don't want to dial 12, 5 is much better.
Versions prior to 9, not so much. Props to whykap for a creative pre9 workaround. I also have used a TCL script on the gateway to add digits to the end of a dial string successfully, for long distance codes or pager return digits. It wasn't easily scalable but it works great. Upgrade to 9 if you can.
Just set up your existing speed dial to send out the first 6 digits, then manually type in the last 4.
ie set up 91212555 then add in 1212 manually. You may have to test the timing on it to know when to enter the digits.
You may also need to set up translation pattern in your partition to open a line after the abbreviated dial so the system does not time out/error on the fact that you have dialed too few digits.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.