Yes, Reason-Header can appear in BYE as per RFC3326 " The Reason header field MAY appear in any request within a dialog, in any CANCEL request and in any response whose status code explicitly allows the presence of this header field. "
Somesh * Please do not take print out of this e-mail unless its absolutely necessary * -----Original Message----- From: [email protected] on behalf of krishna kalluri Sent: Thu 1/29/2009 10:55 PM To: [email protected] Subject: [Sip-implementors] RFC 4028 & Reason header Hi, Keep alive mechanisms are described in RFC 4028. If a session refresh is not received before the interval passes then the UA not acting as a refresher sends BYE request to termination the session. Is it allowed and possible to use the Reason header (RFC 3326) in BYE to tell the reason for the termination of the session? If yes what is the best Reason Code? I can think of 487. Regards Krishna _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors EMAIL DISCLAIMER : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised distribution or copying is strictly prohibited. If you receive this transmission in error, please notify the sender by reply email and then destroy the message. Opinions, conclusions and other information in this message that do not relate to official business of Mascon shall be understood to be neither given nor endorsed by Mascon. Any information contained in this email, when addressed to Mascon clients is subject to the terms and conditions in governing client contract. Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we can not guarantee that any email or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. Mascon grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
