err136 on all my T1s

[coniglio]

I keep getting the following alarms on all three of my in/outbound T1s:
TRK0136 (followed by loop & channel)
Release failure on incoming DID trunk. Disconnect supervision timer
(DSI) was exceeded.
Action: "Trunk state is changed to lockout. Refer to ""Trunk
Failures"" section."
Severity: Minor

AT&T says the channel is NOT in lockout. But doesn't the above alarm indicate it is? It isn't in lockout in my PBX. I know it says Minor but it keeps happening. what should I do to correct this? is it the carrier or my equipment? thank you.

 

[phnechic]

Sounds to me like the circuit may be misoptioned. You might ask AT&T to perform round robin testing on the circuit to make sure it is optioned the same throughout.

 

[coniglio]

We actually have three circuits in one route. I called AT&T and, naturally, they said they saw nothing on their end and that I should call my PBX vendor. But if the alarm is referring to release failure I would think that's them, right?

 

[Reusser]

I have see this a lot where your T1 Vendor (at&t in this case) is not providing disconnect suvervision on the trunks. Once a call disconnects the diconnected party should send a momentary change in the a/b bit string to indicate call termination. This is either not sent or recognized.
As long as channels are not staying in lockout doesn't sound like a problem. However, assuming trunks are built EAM or EM4 - supervision should be set to yes, If GRD or LOP supervision should be set to no.
Print the trunk members to see.