Thank you, Castillo.

At 3.2 in RFC3665, F2 407 is below:

   F2 407 Proxy Authorization Required Proxy 1 -> Alice

   SIP/2.0 407 Proxy Authorization Required
   Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b43
    ;received=192.0.2.101
   From: Alice <sip:[email protected]>;tag=9fxced76sl
   To: Bob <sip:[email protected]>;tag=3flal12sf
   Call-ID: [email protected]
   CSeq: 1 INVITE
   Proxy-Authenticate: Digest realm="atlanta.example.com", qop="auth",
    nonce="f84f1cec41e6cbe5aea9c8e88d359",
    opaque="", stale=FALSE, algorithm=MD5
   Content-Length: 0

In the above, there is no "Contact" header .
So I think Alice can NOT know even the full host name of Proxy1
(ss1.atlanta.example.com).
But Alice(UAC) can resend INVITE to the originator(Proxy1)
at F4 INVITE.
Why  can Alice(UAC) do so?


2010/2/10 Iñaki Baz Castillo <[email protected]>:
> El Miércoles, 10 de Febrero de 2010, Couret Tabt escribió:
>> Dear folks,
>>
>> At F2 in the following flow,
>> why alice recognize who sent 407?
>> In F2 407, there is NOT the address of Proxy1.
>> (The following flow is from 3.2. in RFC3665.)
>
>
> It's not possible to know which is the originator of 401/407. That is just
> possible for replies including "Contact" header (200 for INVITE and 1XX with
> 100rel).
>
> But theorically the UAC should matter it. It just must inspect the "realm"
> field and build a credentials based on such realm.
>
>
> --
> Iñaki Baz Castillo <[email protected]>
>

FYI:

3.2.  Session Establishment Through Two Proxies
(in RFC3665)

   Alice           Proxy 1          Proxy 2            Bob
     |                |                |                |
     |   INVITE F1    |                |                |
     |--------------->|                |                |
     |     407 F2     |                |                |
     |<---------------|                |                |
     |     ACK F3     |                |                |
     |--------------->|                |                |
     |   INVITE F4    |                |                |
     |--------------->|   INVITE F5    |                |
     |     100  F6    |--------------->|   INVITE F7    |
     |<---------------|     100  F8    |--------------->|
     |                |<---------------|                |
     |                |                |     180 F9     |
     |                |    180 F10     |<---------------|
     |     180 F11    |<---------------|                |
     |<---------------|                |     200 F12    |
     |                |    200 F13     |<---------------|
     |     200 F14    |<---------------|                |
     |<---------------|                |                |
     |     ACK F15    |                |                |
     |--------------->|    ACK F16     |                |
     |                |--------------->|     ACK F17    |
     |                |                |--------------->|
     |                Both Way RTP Media                |
     |<================================================>|
     |                |                |     BYE F18    |
     |                |    BYE F19     |<---------------|
     |     BYE F20    |<---------------|                |
     |<---------------|                |                |
     |     200 F21    |                |                |
     |--------------->|     200 F22    |                |
     |                |--------------->|     200 F23    |
     |                |                |--------------->|
     |                |                |                |

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to