Sip Authentication Example - 3Com V7111 - VCX 4 Channels Analog FXO Media Gateway User Manual

Supported: 100rel,em
Content-Length: 0
F6 10.8.201.158 ==> 10.8.201.161
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.8.201.161;branch=z9hG4bKacLBzZgmA
From: <sip:6000@10.8.201.161>;tag=1c29715
To: <sip:2000@10.8.201.158>;tag=1c3535
Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158
CSeq: 34541 BYE
Supported: 100rel,em
Content-Length: 0

SIP Authentication Example

The 8FXS Gateway supports basic and digest (MD5) authentication types, according to the
SIP standard. A proxy server might require authentication before forwarding an INVITE
message. A registrar 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 resend the INVITE with a Proxy-Authorization header
containing the credentials.
User Agent, redirect or registrar servers typically use 401 Unauthorized response to
challenge authentication containing a WWW-Authenticate header, and expect the re-INVITE
to contain an Authorization header.
The following example describes the Digest Authentication procedure including computation
of User Agent credentials.
The REGISTER request is send to registrar server for registration, as follows:
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
CSeq: 1 REGISTER
Contact: sip:122@10.1.1.200:
Expires:3600
On receiving this request the registrar returns 401 Unauthorized response.
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.2.1.200
From: <sip:122@10.2.2.222 >;tag=1c17940
To: <sip:122@10.2.2.222 >
Call-ID: 634293194@10.1.1.200
Cseq: 1 REGISTER
Date: Mon, 30 Jul 2001 15:33:54 GMT
Server: Columbia-SIP-Server/1.17
Content-Length: 0
WWW-Authenticate: Digest realm="3com.com",
nonce="11432d6bce58ddf02e3b5e1c77c010d2",
stale=FALSE,
algorithm=MD5
According to the sub-header present in the WWW-Authenticate header the correct
REGISTER request is formed.
3Com VCX V7111 VoIP SIP Gateways User Manual
200 OK
59