800 calls getting fast busy intermitent

[skip555]

I have a customer with a two cabinet panasonic kx-td1232 rel5 no vm or auto attendent

reports are customers calling in on the 800 line are getting a fast busy on occasion (not consistent ) most all calls are on the 800 line so we cant really say if its only 800

they recently went from sprint to a Clec problem followed from sprint to CLEC . (we where hoping that would clear it )

Clec says they have replaced everything on their end so it must be my switch

I dont see how the pansonic switch could be causing this seems to me it has to be outside but I thought I would post in case anyone could shed some light on it

its a lot of money for me to start replacing when I cant see it making a diffrence.

 

[orypecos]

I have been told by very experienced telephony engineers that a 'fast busy' on a 800 line only comes from a network problem. Most times a trunk between two central offices that is busy or has gone down and another route has not been set up.

 

[hbiss]

..a 'fast busy' on a 800 line only comes from a network problem.

Right. A fast busy on any LD or toll free call would indicate network problems. That's what a fast busy is for. If the trunk or CO line on your end were busy it would result in a regular busy.

Sounds like somebodies passing the buck here!

-Hal

 

[edmhtel]

Check how many lines are in the inbound hunt group that your 800 number points to. Too many simultaneous calls could be your problem, and if so, correct by adding more lines in the hunt. Test by placing as many simultaneous calls to the 800 # as you possibly can.

 

[Dexman]

Do the toll-free calls terminate on a T1 circuit or POTs lines? As edmhtel stated, this could be a congestion situation where available trunks are being maxed out by other calls.

Assuming a T1 is being used, an IXC or CLEC can route calls to stand alone POTs lines if the allocated channels on the T1 are maxed out. If POTs lines are being used all available lines might be in use concurrently and require additional lines be ordered and added to the existing hunt sequence.

Either of these 2 situations would result in the calling party hearing either a reorder (fast busy) or an "All Circuits Are Busy" recording.

 

[ISDNman]

ISDN gives you a way to "snoop" the network that can be valuable.

One way to troubleshoot this would be to set up and ISDN terminal and ISDN protocol analyzer somewhere to place calls to the 800 number until the problem occurs.

Once the problem occurs the look at the first Octet of the disconnect cause and this will identify who issued the disconnect as follows:

80 = User
81 = private network serving the local user (e.g. local PBX)
82 = public network serving the local user (e.g. local CO)
83 = transit network
84 = public network serving the remote user (e.g. far end CO)
85 = private network serving the remote user (e.g. far end PBX)
87 = international network
8A = network beyond interworking point (e.g. far end non-ISDN network such as POTS or Switched 56)

Unless this octet is 85 or *A then it is not your PBX!

The cause code itself (the second Octet) may offer a clue as to what is going on as well, but the first Octet will be more usefull in this case.

Good luck.