Hi,
>From RFC 3261
A UAC SHOULD include a Contact header field in any target refresh
requests within a dialog, and unless there is a need to change it,the URI
SHOULD be the same as used in previous requests within the dialog.
>From RFC 3261
Refer pager 162 Contact is optional in Register and Option Request.
>From RFC 3265
Refer page 33 Contact is mandatory in Subscribe and Notify request.
Regards,
Thangarajan.
IMPORTANT: HUGHES SOFTWARE SYSTEMS LTD. (HSS) IS NOW FLEXTRONICS SOFTWARE
SYSTEMS LTD. (FSS)
SiM
<face2faceonlinux
@yahoo.co.in> To
Sent by: [email protected]
sip-implementors- cc
[EMAIL PROTECTED]
ia.edu Subject
Re: [Sip-implementors] contact
header field
07/04/2005 10:05
PM
Kishoresowdi <[EMAIL PROTECTED]> wrote:
Hi there ,
RFC 3261 says concact header field is added by UAS while responding the
request .The contact header feild contains an address where UAS would like
to be contacted for subsequent requests in the dialog . How about contact
header feild in requests ? . Does INVITE request only do contain contact
header feild or other requests may contain ? .
[Simith]
Other requests as well,the Dialog creating ones ,For Eg: a SUBSCRIBE will
also need a Contact header !
A REGISTER request, a non-dialog creating method, also requires a Contact
header field.
Cheers.
Simith
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
---------------------------------
Too much spam in your inbox? Yahoo! Mail gives you the best spam
protection for FREE!
http://in.mail.yahoo.com
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
*********************** FSS-Private ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) 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. HSS 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]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
