Troubleshooting "User Busy" on PRI

[edoo]

I am setting up a MICS rev6.0 on a standard PRI. I am having issues with one of the DIDs sometimes coming up user busy.

When I call this DIDs, the correct set rings, it is answered and a long conversation takes place. If another call is immediately made to the same DID (while the long conversation is still going), I get a slow busy signal with a release reason of 17. It's as if this DID can only handle one call at a time.

Any ideas on how to troubleshoot this? Thanks!


*** Configuration Notes ***
The DID is setup on line 157. It is a public line, rec'd #800, busy to prime with a prime set of 221. Set 221 has line 157 to Appear & Ring. It also has 5 intercoms and Fwd No Answer/Busy is set to none. Other DIDs are configured in the same way and do not have this problem. Other notes... Telco set to Ascending. ICS set to descending. PRI is factional. B-Channels are 1 to 9. Other B-Channels are disabled and de-provisioned.

 

[bwtc]

Go into **CONFIG

Terminal & Sets
(Type in the extension that is giving you problems)
Line Access
Line Assignment

SCAN

When the line comes up, make sure it is set to "Ring Only", with Appearances: 2 (or the number of intercom keys that you have). You set the appearances with the upper right "triangle".

In the line configuration, you may want to set the line to "If Busy" -> To Prime (which can be an operator's phone, voice mail, etc).

Hope this helps!

 

[edoo]

Thank you for your suggestions. I made the changes to the line, number 157. It is now set to rings only with 5 appearances. (This setting slipped my mind. Thanks!)

I was very hopeful when making my first test call. However, I still got the slow busy with release reason 17. Any other ideas?

 

[bwtc]

Does line 157 appear on any other phone? Does any other phone have set 221 as an Answer DN? Does it *always* give a slow busy whenever the user answers the DID & another calls comes in on the DID, or is it intermittant?

If I think of anything else, I'll let you know...

 

[serviceboy]

6.0 had pri issues...6.1 mr cleared them
4.0,4.1,6.0 and first ver of 6.1 had isssues

******6 months till ski season******

"There are those who would make you believe there are no choices left.That they have the last word and its final.To those who try the world is wide open choices many.To those who dont only death awaits you.

 

[edoo]

bwtc,

I don't believe it appears or rings on any other ext. I checked a couple of likely extensions but not all. Line 157 is answered and routed by the receptionist. Therefore it should not show up on any other extension. When the receptionist is not around, ext 221 is forwarded (feature 4) to an alternate set.

No other set has ext 221 as an Answer DN.

The DID always gives a slow busy whenever the DID is currently in use. Here's the testing method. Call the DID. Call rings, is answered and then put on hold. Another call is placed to the DID which results in slow busy.

I hope this helps. And again, thank you for your suggestions.

 

[edoo]

serviceboy,

What type of issues have you seen with 6.0? (related to pri)

Something else that is interesting.... I am actually switching my pri provider. I did not have this same issue with my last provider. Do you think it could be something on the telco side that is making the slow busy?

Also, why would there be a problem only with this one DID and not the other 20+ DIDs that we have? (iow, did I miss something while configuring this DID?)

very perplexing....

 

[acewarlock]

Do you have 5 INT KEYs on that phone? You need 1 for each RING ONLY

 

[edoo]

Yes, ext 221 (which has 5 appearances for line 157) has 5 intercom keys.

 

[silver987]

How about appear & ring, app 5 they will show up as lines in regular line positions, only difference you can't call out on them (incoming only)
Just a thought..........

http://www.silverlakecom.com

 

[serviceboy]

first to verify one occurence of said line ...make private to prime set...this will remove from all other sets...
2. are u making these call from same pri..if yes
then try from another site...as far as pri issues/6.0 nortel info is available on their website

******6 months till ski season******

"There are those who would make you believe there are no choices left.That they have the last word and its final.To those who try the world is wide open choices many.To those who dont only death awaits you.

 

[edoo]

Serviceboy,

I made line 157 private to prime. Prime set is 221. Still not any better.

I am making the call from the same pri. Looking at the link status I can see my first call is going out the last B channel (#9) and coming in on the first B channel (#1). Once the first call is put on hold, I made the second call. The second call went out on channel #8 and then gets the busy tone. I don't see channel #2 ever getting to the busy state.

It's as if the number is stuck to channel #1 and will not roll over to channel #2. Could this be a programing issue on the telco side?

Thanks for your help.