Thank you, Castillo. I mean below:
A UAC can NOT know an originator of 407. But UAC can send back INVITE to the originator of 407. Why? 2010/2/10 Iñaki Baz Castillo <[email protected]>: > El Miércoles, 10 de Febrero de 2010, Couret Tabt escribió: >> 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 . > > Of course, 4XX responses have no Contact as it's useless. > > >> So I think Alice can NOT know even the full host name of Proxy1 >> (ss1.atlanta.example.com). > > Alice doesn't know if the 407 comes from P1, P2 or whatever as Alice where P1 > relayed the requests. > > > >> But Alice(UAC) can resend INVITE to the originator(Proxy1) >> at F4 INVITE. >> Why can Alice(UAC) do so? > > This is basically as Digest authentication works in SIP. Not sure if I > understand what you mean in this last question. > > > > -- > Iñaki Baz Castillo <[email protected]> > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
