What is Disconnect Supervision? 1

[AvayaHelp]

I have two inbound/outbound trunks 1 & 5.

If I look at my trunk-groups 1&5 at the bottom of the first page is

Disconnect Supervision - In? y Out? n

The Vendor tells me that because this is set for Out? n on both this is the reason my Agents cannot Transfer/Conference received calls to an off switch location/number. But the weird part is that the ability only stops when the desk is really busy with a high abnormal call volume, if things are slow they can use the feature no problem.

So far I have VDNs that route-to external numbers fine, and almost everytime I <list trace> the station when I test it it works but then I used my Avaya phone and tried to call my cell (fine) then transfer my cell to my Nortel extension it failed. The trace did show a "denile 1740: No Supervision.

Does this mean I should change the Disconnect Supervision - Out? n to Out? y for btoh trunk groups?

Anyone can help me or better yet get me a job somewhere else ?

Avaya, Octel, AUDIX, CMS and other fun stuff.

&quot;There is always a way, it may not be pretty but there is always a way.&quot;

&quot;I don't have a technical solution to your management problem.&quot; <PeaveyPhones>

P:-D

 

[randyb19]

This is from the Admin manual. Hopefully, it will help explain:

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.