ARS / COR Problem? Can't dial toll-free numbers 1

[Colpritt]

I’m sure I’m overlooking something simple, but I just can’t figure this out. I installed 2 phones in our training lobby to replace pay phones. Created a new COR for these phones, with Calling Party Restriction at All-Toll. Dialed an 800 number, worked fine, tried a long distance call and got waved off. I thought all was good. Until yesterday, someone from one of the classes tried to call an 877 number and could not. Sure enough, only 800 and local calls will go through. 888, 877 and 866 do not work. All of them use the same route pattern. The FRL of the COR is the same as the FRL of the route pattern.

Thanks!

 

[98Converter]

do a "list trace station XXXX" on the phone and compare the the results with 800# and 877#'s...

Post results and we'll get it working.

Thanks,
Chris

 

[Colpritt]

Here are the list traces. Looks like it's related to ARS, but they're all defined the same in the ARS table. ?? Thanks!



list trace station 3450 Page 1

LIST TRACE

time data

15:26:55 tone-receiver 01A0205 cid 0x3e
15:26:55 active station 3450 cid 0x3e
15:26:59 dial 91866932
15:26:59 denial event 1751: No AAR/ARS route pat/pref D1=0xa0 D2=0x1c0019
15:26:59 dial 91866932
15:26:59 denial station 3450 cid 0x3e
15:27:01 idle station 3450 cid 0x3e

LIST TRACE

time data

15:32:40 tone-receiver 01A0208 cid 0x68
15:32:40 active station 3450 cid 0x68
15:32:44 dial 91888500
15:32:44 denial event 1751: No AAR/ARS route pat/pref D1=0xa0 D2=0x1c0019
15:32:44 dial 91888500
15:32:44 denial station 3450 cid 0x68
15:32:46 idle station 3450 cid 0x68
15:33:42 tone-receiver 01A0202 cid 0x6e
15:33:42 active station 3450 cid 0x6e
15:33:53 dial 91877740
15:33:53 denial event 1751: No AAR/ARS route pat/pref D1=0xa0 D2=0x1c0019
15:33:53 dial 91877740
15:33:53 denial station 3450 cid 0x6e
15:33:55 idle station 3450 cid 0x6e

LIST TRACE

time data

15:35:39 tone-receiver 01A0205 cid 0x84
15:35:39 active station 3450 cid 0x84
15:35:43 dial 91800838
15:35:43 term trunk-group 6 cid 0x84
15:35:43 dial 91800838
15:35:43 route-pattern 3 preference 1 cid 0x84
15:35:43 seize trunk-group 6 member 4 cid 0x84
15:35:47 dial 918008389426
15:35:47 outpulse done 18008389426
15:35:47 tone-receiver 01A0202 cid 0x84
15:35:51 idle station 3450 cid 0x84

 

[98Converter]

cha ars an 1800, confirm the

display ars analysis 180 Page 1 of 2 SPE B
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 11

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
180 11 11 p4 fnpa n
1800 11 11 p1 fnpa n
1877 11 11 p1 fnpa n
1888 11 11 p1 fnpa n

Just make sure they're all listed going over your same trunk that the 800 is.

Should work... as you know to change it, you need to enter it on the next page.

Thanks,
Chris

 

[Colpritt]

Yes, they are all the same. ??? I just change the call pattern to trunk group 3 from p3 to see if it would make any difference - they were all p3. What do you think? Thanks!!!

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1800 11 11 p3 fnpa n
1800555 11 11 p3 fnpa n
1866 11 11 3 fnpa n
1877 11 11 3 fnpa n
1888 11 11 p3 fnpa n

 

[98Converter]

well generally P3 will point to 3 but not always... P3 is your partition route table. 3 is your route table.

If you do a "list ars rou chosen 1877#. and a "list ars route-chose 1800#. The results should be the same.

Also you may want to check your ARS DIGIT CONVERSION table.. maybe something's happening in there.

"Chang ars dig 1"

Hope this helps,
Chris

 

[Colpritt]

Yes, the results were all the same - either route pattern 3 or p3. Partition route index 3 does point to route pattern 3. My ARS Digit Conversion table is empty. Any more ideas? I really appreciate your help! Thanks!

 

[TelcoTech]

The way we set things up is to not use the all toll restriction in the COR. For the COR you created but both restrictions at none, and use the FRL level to administer. Make the COR a level 1 FRL, and make sure the FRL for the route pattern for 800/888/877 dialed strings are 1 as well.

 

[NX01]

Have you tried doing a "cha ars ana 1800" That is working correct? Once you are on the line item for 1800, replace the 00 with XX. See if that helps for the interim.

In the future everything will work...

 

[orypecos]

Does 888, 877 and 866 not work for all users or just this group. If it is all users then maybe a problem with your trunk provider.

 

[Colpritt]

NX01 - Nope, that didn't work. Could still dial 800, but not the others.

Orypecos - Just these 2 phones in this particular COR.

TelcoTech - I will likely try your solution.... it's just so frustrating, because it SHOULD work as is... I think.

 

[TelcoTech]

The Dialed String field must be marked as being associated
with the system’s Toll List. If you change toll 1888 does that dialed string have an x in the toll list field? If not put an x in there. That defines what strings are toll.

 

[NX01]

Is there a "cha ars ana 91888" or any of the others giving you problems?

In the future everything will work...

 

[Colpritt]

Thanks, TelcoTech - that did the trick. However... I don't quite understand why it worked. I'm confused, as it seems that the toll analysis table does the opposite of what I would have thought. Do you know of any documentation that would explain how the table is used? I didn't find anything useful in the regular Admin manual. Thanks again!

 

[Colpritt]

Actually, that wasn't completely true, that it worked. I set up 1888 exactly like 1800 in the toll table, without paying attention to what I was doing. Upon looking closer, and trying to add 1877 and 1866, the only way it worked was putting an x in the unrestricted call list field. Now I'm even more confused. Is that what I should have had to do, TelcoTech? Thanks!