Hi,

 If you include it in 1XX and 2XX it should not be a problem.
RFC does not say anywhere that it MUST not be included. It depends on the
usage.

Thanks,
Shyam

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Abhishek Dhammawat
Sent: Friday, August 14, 2009 9:55 AM
To: Kapil Saxena; [email protected]
Subject: Re: [Sip-implementors] Can Reason header be inluded in 18x and 200
OKresponses to INVITE ?

Hi

In my opinion the CANCEL, BYE, 4xx response has usage of the "Reason"
header.

The "Reason" header is mainly used in error conditions and the 200 OK
response is notifying that the request has been succeeded so the status code
and the reason phrase gives sufficient information therefore usage of
"Reason" header is not required in 200 OK.

Few more use cases can be found in RFC 4411.

regards
Abhishek Dhammawat
Aricent


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Kapil
Saxena
Sent: Thursday, August 13, 2009 3:00 PM
To: [email protected]
Subject: [Sip-implementors] Can Reason header be inluded in 18x and 200
OKresponses to INVITE ?

RFC 3326 states following:


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.  The syntax of the header

   field follows the standard SIP parameter syntax.

Does it imply that 18x and 200 OK can also contain Reason header ? I have
come across examples where "Reason" header is included in
INVITE, CANCEL, BYE, 4xx responses but have not found any 1xx or 200 OK (for
INVITE) containing "Reason" header ?

Pl. clarify ?

Thanks
Kapil Saxena
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

"DISCLAIMER: This message is proprietary to Aricent and is intended solely
for the use of the individual to whom it is addressed. It may contain
privileged or confidential information and should not be circulated or used
for any purpose other than for what it is intended. If you have received
this message in error,please notify the originator immediately. If you are
not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this
message. Aricent accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including damage from
virus."

_______________________________________________
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

Reply via email to