AudioCodes Mediant 500 MSBR, User Manual

Page: 340 / 1248

User's Manual 340 Document #: LTRT-10375
Mediant 500 MSBR
feature, whereby the device is deployed together with Skype for
Business-compatible IP Phones at small remote branch offices in a
Microsoft® Skype for Business™ environment.
For more information on B2BUA and Stateful Proxy modes, see B2BUA
and Stateful Proxy Operating Modes on page 628.
Note: If configured, the parameter overrides the 'SBC Operation Mode'
parameter in the SRDs table.
SBC Client Forking Mode
sbc-client-forking-mode
[IPGroup_EnableSBCClie
ntForking]
Defines call forking of INVITE messages to up to five separate SIP
outgoing legs for User-type IP Groups. This occurs if multiple contacts
are registered under the same AOR in the device's registration database.

[0] Sequential = (Default) Sequentially sends the INVITE to each
contact. If there is no answer from the first contact, it sends the
INVITE to the second contact, and so on until a contact answers. If no
contact answers, the call fails or is routed to an alternative
destination, if configured.

[1] Parallel = Sends the INVITE simultaneously to all contacts. The
call is established with the first contact that answers.

[2] Sequential Available Only = Sequentially sends the INVITE only to
available contacts (i.e., not busy). If there is no answer from the first
available contact, it sends the INVITE to the second contact, and so
on until a contact answers. If no contact answers, the call fails or is
routed to an alternative destination, if configured.
Note: The device can also fork INVITE messages received for a
Request-URI of a specific contact (user) registered in the database to all
other users located under the same AOR as the specific contact. This is
configured using the SBCSendInviteToAllContacts parameter.
Advanced
Local Host Name
local-host-name
[IPGroup_ContactName]
Defines the host name (string) that the device uses in the SIP message's
Via and Contact headers. This is typically used to define an FQDN as
the host name. The device uses this string for Via and Contact headers
in outgoing INVITE messages sent to a specific IP Group, and the
Contact header in SIP 18x and 200 OK responses for incoming INVITE
messages received from a specific IP Group. The IP-to-Tel Routing table
can be used to identify the source IP Group from where the INVITE
message was received.
If the parameter is not configured, these headers are populated with the
device's dotted-decimal IP address of the network interface on which the
message is sent.
By default, no value is defined.
Note: To ensure proper device handling, the parameter should be a valid
FQDN.
UUI Format
uui-format
[IPGroup_UUIFormat]
Enables the generation of the Avaya UCID value, adding it to the
outgoing INVITE sent to this IP Group.

[0] Disabled (default)

[1] Enabled
This provides support for interworking with Avaya equipment by
generating Avaya's UCID value in outgoing INVITE messages sent to
Avaya's network. The device adds the UCID in the User-to-User SIP
header.
Avaya's UCID value has the following format (in hexadecimal): 00 + FA +
08 + node ID (2 bytes) + sequence number (2 bytes) + timestamp (4
bytes)