Configuring Proxy And Registration Parameters; Sip Message Authentication Example - AudioCodes Mediant 4000 SBC User Manual

Session border controller
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

18.2

Configuring Proxy and Registration Parameters

The Proxy & Registration page allows you to configure the Proxy server and registration
parameters. For a description of the parameters appearing on this page, see
''Configuration Parameters Reference'' on page 803. To configure Proxy servers (Proxy
Sets), see ''Configuring Proxy Sets'' on page 363.
Note:
To view the registration status of endpoints with a SIP Registrar/Proxy server,
see ''Viewing Registration Status'' on page 722.
To configure the Proxy and registration parameters:
1.
Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP
Definitions folder > Proxy & Registration).
2.
Configure the parameters as required.
3.
Click Apply.
To register or un-register the device to a Proxy/Registrar:
Click the Register button to register.
Click Un-Register button to un-register.
Instead of registering the entire device, you can register specific entities as listed below by
using the Register button located on the page in which these entities are configured:
Accounts - Accounts table (see ''Configuring Registration Accounts'' on page 377)

18.2.1 SIP Message Authentication Example

The device supports basic and digest (MD5) authentication types, according to SIP RFC
3261. A proxy server might require authentication before forwarding an INVITE message. A
Registrar/Proxy server may also require authentication for client registration. A proxy
replies to an unauthenticated INVITE with a 407 Proxy Authorization Required response,
containing a Proxy-Authenticate header with the form of the challenge. After sending an
ACK for the 407, the user agent can then re-send the INVITE with a Proxy-Authorization
header containing the credentials.
User agents, Redirect or Registrar servers typically use the SIP 401 Unauthorized
response to challenge authentication containing a WWW-Authenticate header, and expect
the re-INVITE to contain an Authorization header.
The following example shows the Digest Authentication procedure, including computation
of user agent credentials:
1.
The REGISTER request is sent to a Registrar/Proxy server for registration:
REGISTER sip:10.2.2.222 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.200
From: <sip: 122@10.1.1.200>;tag=1c17940
To: <sip: 122@10.1.1.200>
Call-ID: 634293194@10.1.1.200
User-Agent: Sip-Gateway/Mediant 4000 SBC/v.7.20A.000.038
CSeq: 1 REGISTER
Contact: sip:122@10.1.1.200:
Expires:3600
2.
Upon receipt of this request, the Registrar/Proxy returns a 401 Unauthorized
response:
User's Manual
384
Mediant 4000 SBC
Document #: LTRT-40203

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mediant 4000b sbc

Table of Contents