Can't redial from call log/voicemail

[argent3993]

Need some help with ARS. Just switched to a different provider for our PRI - and now we need to dial a 1 for LD calls instead of using simple 10-digit dialing (ala cell phone).

If we manually dial a LD number, it works, but if we use the system speed dial or the redial/callback feature on the phone to make a LD call, the "1" is not being inserted. The caller id number will show 9 plus the 10 digit number that called. The 9 is being inserted via the system prefix feature.

Here is the ARS table:

11 911 Dial Emergency
911 911 Dial Emergency
0N; 0Nsi<tele #> Dial3K1
1N; 1Nsi<tele #> Dial3K1
XN; Nsi<tele #> Dial3K1
XXXXXXXXXXN 1Nsi<tele #> Dial 3K1 //LD
817XXXXXXX 817Nsi<tele#> Dial 3K1 //local 10-digit diaiing
972XXXXXXX 972Nsi<tele#> Dial 3K1 //local 10-digit diaiing
214XXXXXXX 214Nsi<tele#> Dial 3K1 //local 10-digit diaiing
682XXXXXXX 682Nsi<tele#> Dial 3K1 //local 10-digit diaiing
469XXXXXXX 469Nsi<tele#> Dial 3K1 //local 10-digit diaiing

Watching the status monitor, when I manually dial a LD number, the system matches on "XXXXXXXXXXN". If I use the system speed dial or callback feature in voice mail, the system matches on "XN;".

I'm sure this is a timing issue with the entire number being received at once vs manually entering it, but how do I resolve this?

Thanks!
Mark

 

[Westi]

OK now a question
How would the phone system know which is a LD call and which is a local one?

YOU have to tell the system that or the line provider has to send caller ID to you with the 1 inserted.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[argent3993]

I guess my initial post wasn't clear enough.

Of course the phone system doesn't know. Instead - the ARS table is set to automatically add a "1" to any 10-digit dialed number unless the first 3 digits match our local calling area.

And it works just fine - when manually dialing the number. However, when using the system speed dial or hitting "Call" when viewing the call history, the system isn't matching the rules that are setup - instead it's matching on "XN" - which doesn't insert the "1".

So - for example - I can pick up the handset and dial - 9 281 890 5500 - and watch in system monitor as the ARS table matches "XXXXXXXXXX" and it inserts the "1" and successfully makes the outbound call.

However, if I hang up and then hit "Redial", select the number I just dialed (which is displayed as 92818905000 on the phone display), and select "Call", I get a message from my Telco that you have to dial "1" first. Looking at system monitor, the ARS match it used was "XN" instead of "XXXXXXXXX".

Same number - two different results. I'm trying to find out why - when using system speed dial/redial/etc - it's not matching on my more specific dialing rule and instead falling back to the very generic "XN" code.

 

[TouchToneTommy]

Have a look at this:

http://www.ipofficehelp.com/HOWTO_BypassDial9.aspx

It seems complicated at first. But it allows calls to be dialed as 10 digit strings, beginning with the area code, even if local. It will insert the 1 before the area code if long distance, and strip the area code and send 7 digits if local.

If you program it for one system, you can cut and paste the ARS and the User Rights into every system you set up, and only need to change the local area code portion if necessary.