<div dir="ltr">Hi,<div><br></div><div style>I came across an interesting scenario yesterday related to early media:</div><div style><br></div><div style>A calls B and an early media session is setup. If A decides to "cancel" the request with a BYE (instead of CANCEL), TM ignores this as a tear down of the transaction. After a timeout, TM sends a "408 request canceled" upstream and a CANCEL request downstream (to B). This happens even though the BYE was correctly routed (loose routing) to B and the 200OK routed back. Both UAs (A and B) behave as if the session has been correctly terminated. Kamailio (TM) however seems to think otherwise???</div>
<div style><br></div><div style>According to the SIP RFC, a UE MAY send either a BYE OR CANCEL with Early Media. (See section 15 of RFC3261 on page 88) - "<span style="color:rgb(0,0,0);white-space:pre-wrap">The caller's UA MAY send a BYE for either </span><span style="color:rgb(0,0,0);white-space:pre-wrap">confirmed or early dialogs, and the callee's UA MAY send a BYE on </span><span style="color:rgb(0,0,0);white-space:pre-wrap">confirmed dialogs, but MUST NOT send a BYE on early dialogs."</span></div>
<div style><br></div><div style>Is this a known issue or should I look into it?</div><div style><br></div><div style>Cheers</div><div style>Jason</div></div>