AudioCodes MediaPack 114 Instrukcja Użytkownika Strona 344

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 390
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 343
SIP User's Manual 344 Document #: LTRT-65411
MediaPack Series
CK sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacZYpJWxZ
From: <sip:[email protected]>;tag=1c5354
To: <sip:[email protected]>;tag=1c7345
User-Agent: Audiocodes-Sip-Gateway/MediaPack/v.5.40.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:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud
From: <sip:[email protected]>;tag=1c5354
To: <sip:[email protected]>;tag=1c7345
User-Agent: Audiocodes-Sip-Gateway/MediaPack/v.5.40.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 O
K
Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud
From: <sip:[email protected]>;tag=1c5354
To: <sip:[email protected]>;tag=1c7345
Server: Audiocodes-Sip-Gateway/MediaPack/v.5.40.010.006
CSeq: 18154 BYE
Supported: 100rel,em
Content-Length: 0
7.13.2 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.
The following example describes the Digest Authentication procedure, including
computation of user agent credentials:
1. The REGISTER request is sent to Registrar/Proxy server for registration, as follows:
Przeglądanie stron 343
1 2 ... 339 340 341 342 343 344 345 346 347 348 349 ... 389 390

Komentarze do niniejszej Instrukcji

Brak uwag