Denial event 1749: No Disconnect Supervision

[Cethlenn]

Hi,
We have a Definity G3R switch tied to another switch.

Avaya Definity G3csiV11

Calls from the H323 TG to extensions local to the Definity work fine... its only when we try and go out another TG that it chokes (ie.. outbound call)

We get the following message:

LIST TRACE

time data

16:25:15 Calling party trunk-group 2 member 1 cid 0x168
16:25:15 Calling Number & Name NO-CPNumber Michel Vailla
16:25:15 active trunk-group 2 member 1 cid 0x168
16:25:15 denial event 1749: No Disconnect Supervision D1=0x830002 D2=0x168
16:25:15 dial 92
16:25:15 term trunk-group 1 cid 0x168
16:25:15 idle trunk-group 2 cid 0x168

Now I'm the Jr. Admin and even the Sr. Admin is stumped. Any help would be greatly appreciated



Cethlenn

 

[telecomravi]

What other trunk group are you ging over? is it analog trunk group like Loop-start trunk ?

 

[Cethlenn]

It's a tie trunk group, linking our Asterisk server to our Avaya PBX.

 

[randyb19]

Check page one for your trunk group 2 and toward the bottom check to see how Disconnect Supervision is set. Here's the info on it:


Disconnect Supervision-In
This field indicates whether Avaya Communication Manager receives disconnect supervision for
incoming calls over this trunk group. It appears when the Direction field is incoming or two-way. (If the
Direction field is outgoing, Communication Manager internally sets this field to n.)

The entry in this field is crucial if you allow trunk-to-trunk transfers. (To allow trunk-to-trunk transfers
involving trunks in this group, this field must be y and the Trunk-to-Trunk Transfer field on the
Feature-Related System Parameters screen must be y).

If a user connects 2 trunks through conference or transfer, and neither far-end media server or switch on
the resulting connection provides disconnect supervision, the trunks involved will not be released
because Avaya Communication Manager cannot detect the end of the call. Communication Manager will
not allow trunk-to-trunk transfers unless it believes that at least one party on the call can provide
disconnect supervision. Therefore, setting this field incorrectly may cause trunks to become unusable
until the problem is detected and the trunks are reset.

Disconnect Supervision-Out
This field indicates whether Communication Manager receives disconnect supervision for outgoing calls
over this trunk group. It appears when the Direction field is either outgoing or two-way. (If the Direction
field is incoming, Communication Manager internally sets this field to n.)

The entry in this field is crucial if you allow trunk-to-trunk transfers. (To allow trunk-to-trunk transfers
involving trunks in this group, this field must be y and the Trunk-to-Trunk Transfer field on the
Feature-Related System Parameters screen must be y). If a user connects 2 trunks through conference or
transfer, and neither far-end server/switch on the resulting connection provides disconnect supervision,
the trunks involved won’t be released because Communication Manager can’t detect the end of the call.
Communication Manager will not allow trunk-to-trunk transfers unless it believes that at least one party
on the call can provide disconnect supervision. Therefore, setting this field incorrectly may cause trunks
to become unusable until the problem is detected and the trunks are reset.

Also, remember that Avaya Communication Manager must receive answer supervision on outgoing
analog CO, FX, WATS, Tie, Tandem, and Access trunks before it will recognize a disconnect signal. If
this trunk group does not receive answer supervision from the far-end server/switch, and you enter y in
this field, Avaya Communication Manager will internally set the field to n.

 

[Cethlenn]

Thank you very much! That was exactly the problem and changing those two settings (Disconnect Supervision In and Out) to Y, completely resolved the problem we were having!

Cethlenn