Dear Brett & Members, What about the following highlighted behavior with regards to UAC.
15.1.1 *UAC Behavior* A BYE request is constructed as would any other request within a dialog, as described in Section 12. Once the BYE is constructed, the UAC core creates a new non-INVITE client transaction, and passes it the BYE request. The UAC MUST consider the session terminated (and therefore stop sending or listening for media) as soon as the BYE request is passed to the client transaction. If the response for the BYE is a 481 (Call/Transaction Does Not Exist) or a 408 (Request Timeout) or *no response at all is received for the BYE (that is, a timeout is returned by the client transaction), the UAC MUST consider the session and the dialog terminated.* On Wed, Apr 15, 2015 at 3:13 PM, Brett Tate <br...@broadsoft.com> wrote: > > Is it mandatory or optional to send back 481 for a scenario > > in which UAS doesn't know how to handle the transaction. > > If you are still asking about CANCEL, the following snippet is applicable. > > RFC 3261 section 9.2: > > "If the UAS did not find a matching transaction for the CANCEL > according to the procedure above, it SHOULD respond to the CANCEL > with a 481 (Call Leg/Transaction Does Not Exist)." > > > RFC 2119 section 3: > > "SHOULD This word, or the adjective "RECOMMENDED", mean that there > may exist valid reasons in particular circumstances to ignore a > particular item, but the full implications must be understood and > carefully weighed before choosing a different course." > -- Br, Imran Saleem +966-533-414475 _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
