AudioCodes E-SBC User Manual

CHAPTER30 SBC Overview
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Value Comment
'Transport Type' HTTPS Secured HTTP.
3. Configure OAuth-based authentication for the source IP Group (client that the device needs to
authenticate):
Parameter Value Comment
'Authentication Mode' SBC as Server The device authenticates as a server.
'Authentication Method List' "register/setup-
invite"
The SIP methods that the device
needs to authenticate.
'SBC Server Authentication
Type'
Authenticate with
OAuth Server
The device authenticates the SIP
requests with an OAuth Authentication
server.
'OAuth HTTP Service' OAuth-Server Assigns the Remote Web Service that
you configured (in Step 1) for the
OAuth Authentication server.
Interworking SIP Signaling
The device supports interworking of SIP signaling messages to ensure interoperability between
communicating SIP UAs or entities. This is critical in network environments where the UAs on
opposing SBC legs have different SIP signaling support. For example, some UAs may support
different versions of a SIP method while others may not event support a specific SIP method. The
configuration method for assigning specific SIP message handling modes to UAs, includes
configuring an IP Profile with the required interworking mode, and then assigning the IP Profile to
the relevant IP Group.
This section describes some of the device's support for handling SIP methods to ensure
interoperability.
Interworking SIP 3xx Redirect Responses
The device supports interworking of SIP 3xx redirect responses. By default, the device's handling
of SIP 3xx responses is to send the Contact header unchanged. However, some SIP UAs may
support different versions of the SIP 3xx standard while others may not even support SIP 3xx.
The handling of SIP 3xx can be configured for all calls, using the global parameter
SBC3xxBehavior. To configure different SIP 3xx handling options for different UAs (i.e., per IP
Group), use the IP Profiles table parameter, 'SBC Remote 3xx Mode'.
Resultant INVITE Traversing Device
The device can handle SIP 3xx responses so that the new INVITE message sent as a result of the
3xx traverses the device. The reasons for enforcing resultant INVITEs to traverse the device may
vary:
■ The user that receives the 3xx is unable to route to the 3xx contact (i.e., the user is on the LAN
and the new contact is on the WAN). In such a scenario, the device enables the user to reach
the WAN contact and overcome NAT problems.
■ Enforce certain SBC policies (e.g., call admission control, header manipulation, and
transcoding) on the resultant INVITE.
The device enforces this by modifying each Contact in the 3xx response as follows:
- 744 -

AudioCodes E-SBC Specifications

General

Brand	AudioCodes
Model	E-SBC
Category	Gateway
Language	English