RFC3261, sec 15 : "Typically, when the user hangs up, it indicates a desire
to
terminate the attempt to establish a session, and to terminate any
sessions already created. For the caller's UA, this would imply a
CANCEL request if the initial INVITE has not generated a final
response, and a BYE to all confirmed dialogs after a final
response.".
So in this text, it is implying CANCEL is to be sent to terminate a session
& dialog before call answered.
But an earlier paragraph in same section sec 15:: "The caller's UA MAY send
a BYE for either confirmed or early dialogs".
Why has the RFC left open the option to send BYE before call has answered?
If CANCEL is meant to be the METHOD to send before INVITE in accepted to
terminate the session & dialog, why also allow BYE? Or to ask the other way,
why create & define the CANCEL method if BYE can be used to terminate the
session & dialog before call answered?
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
