AudioCodes Mediant 4000 SBC User Manual page 332

Parameter
SBC Operation Mode
sbc-operation-mode
[IPGroup_SBCOperationMo
de]
SBC Client Forking Mode
enable-sbc-client-forking
[IPGroup_EnableSBCClient
Forking]
Advanced
Local Host Name
local-host-name
[IPGroup_ContactName]
User's Manual
Defines the device's operational mode for the IP Group.

[-1] Not Configured = (Default)

[0] B2BUA = Device operates as a back-to-back user agent
(B2BUA), changing the call identifiers and headers between the
inbound and outbound legs.

[1] Call Stateful Proxy = Device operates as a Stateful Proxy,
passing the SIP message transparently between inbound and
outbound legs. In other words, the same SIP dialog identifiers
(tags, Call-Id and CSeq) occur on both legs (as long as no other
configuration disrupts the CSeq compatibleness).

[2] Microsoft Server = Operating mode for the One-Voice
Resiliency 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 416.
Note: If configured, the parameter overrides the 'SBC Operation
Mode' parameter in the SRDs table.
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.
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.
332
Mediant 4000 SBC
Description
Document #: LTRT-41729