User's Manual
Avaya Branch Gateway Manager 10.0 Page 240
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
· By Source IP Address
This option uses the source IP address and port of the incoming request for association. The match is against the
configured remote end of the SIP line, using either an IP address/port or the resolution of a fully qualified domain
name.
· "From" header hostpart against ITSP domain
This option uses the host part of the From header in the incoming SIP request for association. The match is
against the ITSP Domain Name above.
· R-URI hostpart against ITSP domain
This option uses the host part of the Request-URI header in the incoming SIP request for association. The match is
against the ITSP Domain Name above.
· "To" header hostpart against ITSP domain
This option uses the host part of the To header in the incoming SIP request for association. The match is against
the ITSP Domain Name above.
· "From" header hostpart against DNS-resolved ITSP domain
This option uses the host part of the FROM header in the incoming SIP request for association. The match is found
by comparing the FROM header against a list of IP addresses resulting from resolution of the ITSP Domain Name
above or, if set, the ITSP Proxy Address on the Transport tab.
· "Via" header hostpart against DNS-resolved ITSP domain
This option uses the host part of the VIA header in the incoming SIP request for association. The match is found
by comparing the VIA header against a list of IP addresses resulting from resolution of the ITSP Domain Name
above or, if set, the ITSP Proxy Address on the Transport tab.
· "From" header hostpart against ITSP proxy
This option uses the host part of the “From” header in the incoming SIP request for association. The match is
against the ITSP Proxy Address on the Transport tab.
· "To" header hostpart against ITSP proxy
This option uses the host part of the From header in the incoming SIP request for association. The match is
against the ITSP Proxy Address on the Transport tab.
· R-URI hostpart against ITSP proxy
This option uses the host part of the Request-URI in the incoming SIP request for association. The match is against
the ITSP Proxy Address on the Transport tab.
· REFER Support: Default = On.
REFER is the method used by many SIP device, 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 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 system.
· 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.
· UPDATE Supported: Default = Never.
The SIP UPDATE method (RFC 3311) allows a client to update parameters of a session (such as the set of media
streams and their codecs) but has no impact on the state of a dialog. It is similar to RE-INVITE, but can be sent before
the initial INVITE has completed. This allows it to update session parameters within early dialogs. The settings are
Never, Allow or Auto. If set to Allow or Auto and the other party supports UPDATE, the IP Office will send UPDATE
messages for session refresh.
· In Service: Default = On.
When this field is not selected, the SIP trunk is unregistered and not available to incoming and outgoing calls.
243
243
243
243
243