After sending a 1xx response, why couldn't the UAS send some request?
then, both sides know the Via path, and a virtual ciruit can be set up.
As the path is in the message, the proxy won't suffer too much payload.
The virtual ciruit can fast the exchanging, i think, and all messages, including
the CANCEL, should be using the virtual ciruit.
Dose it do any harm?
thanks,
Louis
Hisham wrote:
>If the client is an endpoint, it will construct any SIP request with
>only the one Via header pointing to itself, regardless what the request
>is. If the client is an intermediary, like a proxy, then it constructs
>the CANCEL with one Via header because CANCEL requests are hop by hop.
>The intermediary consumes the response and does not forward it up
>stream.
>
>Regards,
>Hisham
>
>On Mar 31, 2005, at 3:02 PM, Kaixuan Liu wrote:
>
>> hi,
>>
>> Section 9.1 of RFC3261 says that
>>> A CANCEL constructed by a client MUST have only
>>> a single Via header field value matching the
>>> top Via value in the request being cancelled.
>>
>> why couldn't it contain all the Via?
>>
>> thanks,
>> Louis
>>
>>
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>>
>
>
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
