SIP-USERS: Denial event 1732 when trying a consultative transfer

Doc ID		SOLN329298
Version:		1.0
Status:		Published
Published date:		13 Sep 2018

Author:

Ronaldo Vallino

Details

Unable to complete consultative transfer when COR are restricted
Users - COR 1
Secretary - COR 2
Director - COR 3

All statios are SIP-CM users

Users cannot call Director directly restricted by COR, so they must call secretary and request a transfer.

Call flow:

users (cor 1) call secretary (cor 2) that transfers to director (cor 3):

- blind transfers works fine
- transfers using hold, seconde line and then transfer works fine
- conference works fine

Problem Clarification

Denial event 1732 after consultative transfer

Problem: when secretary tries to make a consultative transfer (Transfer button, call and talk to director and then transfer again), it failes with denial event 1732.

Cause

Running traces we can see REFER command is sent to endpoint (user) so this endpoint must send a new invite according to refer-to information. This new invite is direct to director and this call is restricted by COR. (COR 1 to COR 3)

Solution

In system-parameter feature form - page 19 - parameter "SIP Endpoint Managed Transfer?" was set to YES (default=n). In this case, CM send the REFER to endpoint causing the behavior explained above.
Setting it to NO, CM will handle the REFER and will not consider it as a new call not applying COR restrictions.

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy