Call: Waiting for Line - Issue with Circuit or IP Office?

[anon0101]

We just moved our office, same IP Office with no config changes. We went from 3 PRIs to 1. The T1 was due to be turned up on Monday July 31 at noon. When dialing out we were getting 5 quick beeps and an error on our phones "Call: Waiting on line". The call would hit the phone you were dialing (my cell phone) but when you try to answer you get nothing. This went on until Tuesday at 4pm when the circuit was finally turned up. Wednesday morning when I came in I was getting the same error on the phones. I called into our provider and the circuit has yet to be repaired. Has anyone seen this error and if so was it anything on the IP Office side of the equation that could be causing it? We have a third party company we can lean on for IP Office issues when they're over my head and we've had them look at everything but they couldn't find anything on our end. Just thought I'd post this while I wait on a call back.

 

[DaIPOTek]

Waiting for line means just what it says, no line is currently available to seize. Did you simply turn down 2 of the PRIs or change to a new vendor? If its a new vendor, my bet is they are giving you SIP trunks being handed off as a PRI. There are a lot of fly by night companies out there selling super cheap PRI service this way, but too often they don't know enough about what they are doing on the AdTran side of things.

If you had your vendor look at the config, then I am assuming they verified that your line group only contains the active PRI channels. If you want to post a config I could take a look for you.

 

[anon0101]

We just turned down 2 PRIs, still using the same vendor. When I get a moment I'll get a config posted, thanks DaIPOTek!

 

[Telecomboy]

If you went from 3 to 1 PRI and you didn't make any config changes then you will get "waiting for line" as the phone system will still be trying to use those 2 unused PRI's. You need to remove those PRI's from your outgoing line group.

 

[Telecomboy]

And if the 3rd party you use for IP Office doesn't realize that you should probably look into a new vendor as this is the basics.

 

[anon0101]

I put the other PRIs in out of service, shouldn't that eliminate them from being used?

 

[DaIPOTek]

It should eliminate them from being used. Best practice is to remove them entirely. Also a monitor trace of an attempted call would reveal more info.

 

[Telecomboy]

That should be fine. You don't mention if inbound calls work at all or not. Do you have access to using System Status? You can check the errors to see where they point (system or provider)?

 

[anon0101]

Incoming calls roll to our HQ office automagically. I need to reinstall System Status so I can see those errors. Here is a monitor trace of a call I tried from my desk to my cell.

 

[DaIPOTek]

14:42:49 651578mS CMARS: FOUND A SHORT CODE - short_code: XXXXXXXXXX - Tel: N - Called_Party: ********** - Line Group Id: 0

14:42:58 659586mS CMARS: Target: Short_Code: XXXXXXXXXX - Line_Group_ID: 0 has been set to: CMARS_OUTOFSERVICE

The call is trying to use line group 0. Is that the correct line group for your PRI? Post a sanitized config if you can.

 

[anon0101]

Yes it is. We had all 3 set to 0 with a 4th for expansion that we never needed.

 

[anon0101]

Finally, I got System Status running. I'm showing the line I'm supposed to be using as Trunk out of Service. Repair tech told me everything looked good on his end and it had to be something with my system. They have a tech out right now testing.

 

[anon0101]

Issue was upstream

 

[Westi]

Provider that can't get properly, never heard that before.
I never had an IP office with a bad PRI card since I install them (2003)

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Telecomboy]

Well that's a jix Westi...Hahaha. I actually have never had a IP500V2 PRI be bad either. I did have (1) IP500V1 PRI card go bad.

 

[critchey]

I saw a PRI card with a scorch mark on it not work clearly Avaya's fault! /endsarcasm

The truth is just an excuse for lack of imagination.