SIP User's Manual 436 Document #: LTRT-65412
MP-11x & MP-124
îš„ F5 (10.8.201.108 >> 10.8.201.10 ACK):
ACK sip:1000@10.8.201.10;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacZYpJWxZ
From: <sip:8000@10.8.201.108>;tag=1c5354
To: <sip:1000@10.8.201.10>;tag=1c7345
Call-ID: 534366556655skKw-8000--1000@10.8.201.108
User-Agent: Audiocodes-Sip-Gateway/MediaPack/v.5.80.010.006
CSeq: 18153 ACK
Supported: 100rel,em
Content-Length: 0
Note: Phone ‘8000’ goes on-hook and device 10.8.201.108 sends a BYE to device
10.8.201.10. Voice path is established.
îš„ F6 (10.8.201.108 >> 10.8.201.10 BYE):
BYE sip:1000@10.8.201.10;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud
From: <sip:8000@10.8.201.108>;tag=1c5354
To: <sip:1000@10.8.201.10>;tag=1c7345
Call-ID: 534366556655skKw-8000--1000@10.8.201.108
User-Agent: Audiocodes-Sip-Gateway/MediaPack/v.5.80.010.006
CSeq: 18154 BYE
Supported: 100rel,em
Content-Length: 0
îš„ F7 (10.8.201.10 >> 10.8.201.108 200 OK):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud
From: <sip:8000@10.8.201.108>;tag=1c5354
To: <sip:1000@10.8.201.10>;tag=1c7345
Call-ID: 534366556655skKw-8000--1000@10.8.201.108
Server: Audiocodes-Sip-Gateway/MediaPack/v.5.80.010.006
CSeq: 18154 BYE
Supported: 100rel,em
Content-Length: 0
9.18 SIP Authentication Example
The device supports basic and digest (MD5) authentication types, according to SIP RFC
3261 standard. 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 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.
To Next Page
Loading...
Need help?
General
