3300 can't dial 0 over the PRI

[tt1tom]

I have a 3300 with a PRI, I have been over The ARS with a fine tooth comb and can't figure out what I am missing, I can make all of my calls, local, long distance everything works fine. I can not dial 0 to get an operator out on the PRI. I dial 8+1+ anything it works fine, I dial 8+ any 7 digits and it works fine, if I dial 8+0 I hang and then go to an invalid on the display and a fast busy. The PRI carrier sees my request for operator assited call on the D-Channel but no digit 0 comes out of the switch. What am I missing

 

[IrwinMFletcher]

I'm far from the best at this, but it sounds like you might have something like:

8XXXXXXX

which would as you say, allow any 7 digit call, so when you dial 80 the system is waiting for those last 6 digits.

Try to add a specific entry for 80.

 

[kwbMitel]

Assuming from your post that you are in North America you should have ARS entries like the following

Digits Qty Follow Route
80 0 X (For operator)
80X 9 X (For Calling Cards)
801X unknown X (For Overseas)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[tt1tom]

I have digits Qty Follow route
80 0 x

I have gone through all of the ARS and all other calls go out fine and the calls are all useing the same routes and modify digit table and stripping only the lead access digit of 8, the only thing that won't go out is 0. I am hitting the trunk but the actual 0 is not outpulsing

 

[kwbMitel]

Is there anything other than Blank in the digits before outpulsing field?

What type of trunks are you using (Analog or PRI)

If PRI, what digits, if any, do you have in your Digit Modification - Digits to be inserted?

Something to try:
Use the Direct Trunk Access feature access code to remove ARS and test dialing directly.

e.g.
AAA TTTT MMM 0 #

AAA = FAC for Direct Trunk Access
TTTT = 4 digit trunk number. (Trunk 1 = 0001)
MMM = Digits to insert (If any) as programmed in Mod digit form.
0 = digit zero
# = digit # (end of dial)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[tt1tom]

It is a PRI and in my digit mod table I am stripping 1 which is the 8 and inserting none, which should send the 0 out. i am useing all of the same route and mod digit table as local calls use which are 7 digit calls, the caller dials 8 xxx-xxxx and it strips the 8 and sends the 7 digits and works fine. I can see the 7 outpulsed digits on the PRI by my Central office but they never see the 0 come out.

 

[kwbMitel]

Try direct trunk access to remove ARS issues.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[tt1tom]

I dialed direct trunk access code plus 4 digit trunk number plus a 7 digit local number and all works fine that way. I do the same thing with direct trunk access and dial 0 and it goes nowhere. Sits and then comes back with a fast busy and invalid on the superset. Now what???

 

[phoneman429]

What kind of PRI interface? NSU, Dual Framer, Combo module?
What kind of C.O. For chuckles & grins, write a digit mod that strips 8 and add 0 (zero). Basically make ARS dial 00, if it works, the protocol set up is issue. Usually this is issue when PRI Card is set for NI2 5ESS and C.O. is DMS or needs NI2 Bellcore.

 

[phoneman429]

I bet you can't call international (011+)either, if not this is issue.

 

[kwbMitel]

It sounds as if Zero+ is blocked by the CO.

Try a 0+10 digit or international call.

Try dialing more than 1 zero as well.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[tt1tom]

Thanks for all of the sugestions, the problem was solved by going under protocol assignment and going to Enable Unknown TON/NP and checking it to true, this taggs the dial 0 call as unknown instead of the way it was as national, and then the PRI knows how to route it. Be careful, when checking it to true it will crash the PRI, but it comes right back

 

[kwbMitel]

I never thought toask if you were NI-1 or NI-2. I now assume you are connected to a 5ess with NI-2 protocol.

Yes, unknown call type will make it work but in reality it's like 2 wrongs making a right.

I take it my suggestion of dialing more than 1 zero led you to this?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.