> 2010/3/19 Brett Tate <br...@broadsoft.com>: > >> But in any case, no specification states that, upon an in-dialog > >> OPTIONS timeout, the UA should terminate the RTP without sending > >> a BYE. Am I right? > > > > Correct. However if I recall correctly, rfc3261 often only indicates > SHOULD send BYE instead of MUST send BYE when the UAC notices a > potential issue with dialog; your rfc5057 snippet using "should > terminate" re-enforces my recollection. > > Which is the different in this case? This is, is the client detects > some problem within the dialog (in-dialog OPTIONS ignored => timeout) > and decides to close its RTP without sending a BYE, what does it > expect? of course the server would remain counting the call as active > (so CDR is increased). > Shouldn't the client send the BYE "yes or yes"? :)
Yes; devices should play nice with proxies/B2BUAs and send BYE. And I assume that since issue noticed with media instead of SIP dialog, rfc3261 likely indicates MUST send BYE. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
