Please enable JavaScript to view this site.

IP Office Basic Edition - Web Manager R11.1

> Configuration Menus > System > SIP Trunks > SIP Trunk Details

Refer Support

Scroll Prev Up Next More

Refer Support: Default = On.
REFER is the method used by many SIP devices, including SIP trunks, to transfer calls. These settings can be used to control whether REFER is used as the method to transfer calls on this SIP trunk to another call on the same trunk. If supported, once the transfer has been completed, the IP Office system is no longer involved in the call. If not supported, the transfer may still be completed but the call will continue to be routed via the IP Office.

Incoming: Default = Auto
Select whether REFER can or should be used when an attempt to transfer an incoming call on the trunk results in an outgoing call on another channel on the same trunk. The options are:

Always
Always use REFER for call transfers that use this trunk for both legs of the transfer. If REFER is not supported, the call transfer attempt is stopped.

Auto
Request to use REFER if possible for call transfers that use this trunk for both legs of the transfer. If REFER is not supported, transfer the call via the system as for the Never setting below.

Never
Do not use REFER for call transfers that use this trunk for both legs of the transfer. The transfer can be completed but will use 2 channels on the trunk.

Outgoing: Default = Auto
Select whether REFER can or should be used when attempt to transfer an outgoing call on the trunk results in an incoming call on another channel on the same trunk. This uses system resources and may incur costs for the duration of the transferred call. The options available are the same as for the Incoming setting.

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

© 2020 AVAYA
Issue 05.a.–
Thursday, July 23, 2020