IPKll Dialing problems

[idahomitel]

New install with 1.5 software. I have two digital sets with two trunk keys assigned to them only. When you dial local numbers on the trunk key, the audio doen't cut through to the called party until after you dial two digits (like it's waiting for account codes). Account codes are disabled system-wide. Long distance cuts right through. Ars is on for the system, but these are direct appearing trunks that appear nowhere else. Any ideas?

 

[smoom]

Other than programming did you check the polarity of the trunk....The IPK2 is very polarity sensitive.

 

[idahomitel]

Loop start trunks- how do I check polarity?

 

[smoom]

you would check polarity using a volt meter, or a newer test set will show if polarity is reversed. Have you checked 21-01-03. Are the buttons programmed as trunks or trunk group buttons? Are you running 1.5 or have you upgraded to the latest? Did you check 20-31-05, 14-02-08???

 

[idahomitel]

I will check polarity today, and the programs you listed. I thought 1.5 was the latest. Do you recommend grounding the system? Most tell me they never ground these IPK systems. I have always grounded PBX installs. What about this KS?

 

[smoom]

On systems with a power cord we never ground the KSU unless there is no earth ground on the electrical plug in. Larger system i.e. 2400 we always install a ground. When you install a seperate ground on the KSU you stand the chance of have a ground potential between the AC ground and your KSU ground...not a good thing...

 

[pave35]

The IPKII has 911 without trunk access enabled by default. So as a result it will always pause after dialing 9 to see if the nex t 2 digits are 11. You can disable this option in 21-01-12.

 

[idahomitel]

Somehow the system is wanting to see 9 digits . I direct trunk access line 7 from what is programmed as a co key, trunk 7. It's not centrex on trunk 7. Audio won't cut through until I dial 2 more digits. Long distance is not a problem. I fixed the centrex trunks by using ars to add a nine, redial what I dialed, add a 1 and end (again for local calls). Long distance is fine. Somewhere, system-wide, it's looking for 9 digits, and I can't figure out why. Tried a new processor tonight. Same thing. No account codes are in play here, but that's what it acts like.

 

[smoom]

Have you upgraded the site to 1.51? I just tested it here in the office using 1.51 and find that the delay is only 1-2 seconds. Pressing extra digits did not help/cause the delay to go away.

 

[idahomitel]

1.50 is the latest we have received.

 

[pave35]

Are you pointing the digits dialed in ARS to an F-Route or directly to a trunk route?

 

[idahomitel]

Directly to a trunk route--I found it!! Not where you'd think- 21-01-10 was set as 9. I can't figure how this defaulted as 9, or why it applied when toll control isn't being used, but talk about a mindf*ck!!! Set to 0 cuts right through. Thanks for all your help, everyone.

 

[pave35]

It applies because it is not a toll restriction feature but a system outgoing call feature. It CAN also be set with toll restriction classes if required.
21-01-10 is the minimum number of digits that MUST be dialed before a talk path is established. You should not ever really use this option as it will stop 911 calls if an entry of 4 or higher is assigned.
I checked the default setting on 1.10, 1.13, 1.15, 1.50, 1.51 and all CPU versions were set ot a 0.