Analog Trunks on 3300 CX

[JAGO]

Hi,

I have a 3300 Cx with release 8.0.9.18 and I have 6 analog trunks connected on it. The problem is sometimes the LS get blocked. To unblocked them I have to disconnect them manually from back or write the command busy and rts.

Does anybody know how to fix it?

Thank you

[ralph]

What do you mean by blocked?  Are they busy?   In Lockout?  Suspect?
When it happens, do a Stat on the PLID.  It should show you the state.
If it shows BUSY do a reso on the PLID.  This will show you what it is connected to.  If it's connected to another trunk then we need to have a more indepth discussion.

Ralph

[Chakara]

  I've seen them get hung up when the tip and ring are reversed as well - just a thought....

[JAGO]

Ralph,

I did what you suggested me an these were the results.

  Location    | Device               | State          |  Owner  | ID  |Status   
----------------------------------------------------------------------------   
 2 1  1   5   | LS on Embedded ASU   | Idle           |         |     |         
 2 1  1   6   | LS on Embedded ASU   | Idle           |         |     |         
 2 1  1   7   | LS on Embedded ASU   | Busy           |Call Proc|1 254|Wait     
 2 1  1   8   | LS on Embedded ASU   | Busy           |Call Proc|8 253|Wait     
 2 1  1   9   | LS on Embedded ASU   | Idle           |         |     |         
 2 1  1  10   | LS on Embedded ASU   | Idle           |         |     |         
----------------------------------------------------------------------------


RESOURCE 2 1 1 8

Circuit: MC282AA Hybrid 4 ONS 6 LS at location  2  1  1  7                     
Call Process: 1 254                     Device Type: LS on Embedded ASU         
Call State: Talking                     Party Type: Terminator                 
Receive Link:  19   Channel: 20         Transmit Link:  19   Channel: 20       
                                                                               
>>>>> Other Party for Call Process 1 254                                       
Circuit: MC282AA Hybrid 4 ONS 6 LS at location  2  1  1  8                     
Call Process: 8 253                     Device Type: LS on Embedded ASU         
Call State: Talking                     Party Type: Terminator                 
Receive Link:  20   Channel: 21         Transmit Link:  20   Channel: 21   


RESOURCE 2 1 1 9

Circuit: MC282AA Hybrid 4 ONS 6 LS at location  2  1  1  8                     
Call Process: 8 253                     Device Type: LS on Embedded ASU         
Call State: Talking                     Party Type: Terminator                 
Receive Link:  20   Channel: 21         Transmit Link:  20   Channel: 21       
                                                                               
>>>>> Other Party for Call Process 8 253                                       
Circuit: MC282AA Hybrid 4 ONS 6 LS at location  2  1  1  7                     
Call Process: 1 254                     Device Type: LS on Embedded ASU         
Call State: Talking                     Party Type: Terminator                 
Receive Link:  19   Channel: 20         Transmit Link:  19   Channel: 20       

[ralph]

Ok,  you have two trunks locked together.
The next step is to find out what is transferring one trunk to another.   Is it supposed to?
There are several ways to fix this, all depending on what device is transferring trunk to trunk and if that is supposed to happen.
Go into your SMDR form and be sure you have smdr turned on.
Then go into the COS of the trunk and be sure it is turned on in there also.
Then when it happens next busy the PLID and RTS the PLID. 
Command "busy <PLID>" , then "force";
This will disconnect the call.   
Then restore the trunk "rts <PLID>"
If SMDR was active BEFORE the call, you can do a search for the call to see if you can find what device transferred the trunk to the other trunk.

My next question is this: are you a dealer or end user?  The reason I ask is if you are an end user, I could probably knock this out in just a few minutes once I had remote access to your sytem.  You'd have to go through the company I work for but that shouldn't be a big deal.

Ralph

[v2win]

This should be easy to fix, the easiest way is to interconnect restrict the trunks.

If you are not using interconnect restriction this should work


Go to the interconnect restriction form and go to line 2 and restrict 2 then go to trunk service assignment or analog trunk assignment I cant remember which and change the interconnect of the trunks to 2.

The downside of this is you wont be able to transfer calls offsite

Are the analog trunks your only trunks in the system?

[ralph]

JANGO hooked me up with remote access and that's exaclty what I did to resolve it.
I found one user that was making a call and then transferring that call back out.
Per JANGO the user should not be allowed to do that.
I'm still a bit concerned the the system wasn't reacting to trunk disconnect (if we were getting any at all) so I lowered the diconnect timers down some.
But like you said, the interconnect restriction was the fastest fix.

Ralph

[JAGO]

Thank you guys for your help.

Analog trunks are the only trunks that I use.

On the other hand as Ralph said, Te interconnection was already configured however I am checking the trunks and they are still getiing blocked (busy).

regards,

JAGO

[JAGO]

Hi,

The problem has been solved. The interconnection was done over analog trunks besides this on Co Circuit descriptor was changed to no.
Also Disconnect Timer to 250 from 500.

Thank you,