I had to implement the OPTIONS option :) thanx for the response :)
one more thing.. I came across a scenario where UAC sends BYE with a sequence number less than/equal to the sequence number sent in last request. and UAS has to respond with a 500. my questions are 1- what should be the behaviour of UAS.. should it close its media streams even when sequence number is not correct. coz as per RFC section 15.1.1 " 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." 2- For a proxy which is also doing some sort of billing..what is the usual practice.. Do proxies write the CDR information on receiving or they wait for the 200 response for BYE.. ----- Original Message ---- From: Paul Kyzivat <[EMAIL PROTECTED]> To: Arif <[EMAIL PROTECTED]> Cc: [email protected] Sent: Wednesday, July 9, 2008 6:23:09 PM Subject: Re: [Sip-implementors] call stateull proxy and session termination Arif wrote: > Hi! > > in the implementation of a call stateful proxy.. > I want to cleanup dead sessions..i.e sessions whose peers have died suddenly > due to any reason.. > > i think rfc 4028 addresses this by introducing Session Timers.. but wat if > the End Points do not support rfc 4028. > wat others means can i employ to cleanup hanged sessions..? You are really pretty much out of luck. You could send periodic OPTIONS messages to the two ends to see if they are still functional, but that won't tell you if the call is still active. Or you can just drop your state after some period of inactivity regardless of whether the endpoints are still in session or not. Why would you want to have a call stateful proxy? Paul _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
