[EMAIL PROTECTED] wrote:
> Hi,
>
> In Sec 15.1.1:
> The UAC MUST consider the session terminated as soon as
> the BYE request is passed to the client transaction.
> If the response for the BYE is a 481 or a 408 or no response at all
> is received for the BYE ,
> the UAC MUST consider the session and the dialog terminated.
>
> So when will a UAC terminate a session and/or a dialog?
> Shall it wait for the 200 from the UAS?
At the risk of taking a guess, I would say that you are confusing the
protocol state with the user expectation. The BYE is generated by
the UAC core as soon as the user using the UAC "hangs" up (i.e. by
actually hanging up an IP phone, or pressing the "Stop" button on
a GUI, or something to that effect). As far as the user is concerned,
the session is terminated.
It is now upto the protocol to make sure that the BYE reaches the
intended destination and elicits a final response (200 or non-200),
or times out.
- vijay
--
Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and eServices
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566 Voice: +1 630 224 0216
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
