Int'l call setup digits

[FortKnox]

I am having trouble making 13-digit int'l calls.

My route pattern is set to 12 through 23 digits, but I have to sneak the 13th digit in super, super fast for it to setup the 13th digit...how do I correct this?

Thanks,

-CaN

 

[phoneguy55]

Run a list trace then copy and paste your results. It sounds like it may be keying of something else in your ars table.

 

[FortKnox]

OK,

this is just a fake number, but this is what I tried to dial:
011 73 8311 610 732 (as soon as I enter 011 73 8311 610 73...it tries to send the number)

list trace sta 444 -
07:56:51 dial 9011738311610
07:56:51 term trunk-group 17 cid 0xf8
07:56:53 dial 901173831161073
07:56:53 route-pattern 2 preference 1 cid 0xf8
07:56:53 seize trunk-group 17 member 2 cid 0xf8
07:56:53 Setup digits 01173831161073
07:56:53 Calling Number & Name NO-CPNumber NO-CPName
07:56:53 Proceed trunk-group 17 member 2 cid 0xf8
07:56:59 idle station 444 cid 0xf8

disp ars ana 011 -
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
011 12 23 p5 intl n

disp part 5 -
Index PGN 1 PGN 2 PGN 3 PGN 4 PGN 5 PGN 6 PGN 7
----- ----- ----- ----- ----- ----- -----
5 2 5


My station, 444, has a COR of 1 which is time of day chart 1, so I'll paste route pattern 2

disp route 2 -

1: 17 1 615 1 n user


The way it is now, it would be impossible to ever get 23 digits in before the digits get sent out the t1.


Thanks for your help.

 

[1a22ip]

Are you sending this out on a PRI? Just for whips and grins change the call type in the ars analysis table to FNPA and try the call again. I have had that same problem and this worked for me.

Hope this helps
ED

1a2 to ip I seen it all

 

[phoneguy55]

Do any international calls work. Try my test number.

011 44 8705 111 999 (Sony UK)

Do you get a recording from your LD carrier when the call is sent out? What is it?

I have seen that some some LD (AT&T) require you to stip off the 011, in that case you need to put a 'delete 3' in your route pattern.

 

[FortKnox]

Mmmm...found the problem. I cant believe it hasnt caused havoc here in the past b/c we do a lot of int'l calling, but I believe Paul Beddows in here actually helped me set it up my first ISD/PRI long ago as enbloc/overlap.

In case you dont know what overlap is, it means that as soon as your dialed digits "overlap" with anything in the ars table, it sets up the digits. So since my int'l was set to min-12 max-23, as soon as it met the min=12 criteria it shot off the number to the carrier.

I changed it to enbloc/enbloc, now all is well.

Thanks for the help.