Hi, >From an implementor perspective, I would say that people normally don't care what the BYE response is. If I want to hang up my call, and release the resources associated with it, I should not be "forbidden" to do so just because something has happened in the network and I get a strange error response...
I don't think that functions related to charging should care about the response either. Regards, Christer > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Sonja Belic > Sent: 12. huhtikuuta 2007 14:16 > To: [EMAIL PROTECTED] > Subject: [Sip-implementors] non 2xx final response to BYE > > Hi, > > RFC 3261 implies : "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. " > > What is the appropriate behaviour in case some other non-2xx > final response is received ? > > Thanks in advance. > > Best Regards, > Sonja > > -- > Sonja Belic > Software Development & Testing > --- > "ZESIUM mobile" d.o.o. > Valentina Vodnika 8/9 > 21000 Novi Sad > Serbia > > Tel: +381 (0)21 472 15 48 > Fax: +381 (0)21 472 15 49 > Mob: +381 (0)64 150 80 90 > > E-mail: [EMAIL PROTECTED] > Web: www.zesium.com > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
