On 2/16/16 11:19 AM, Jing Jiang wrote:
Recently, we saw a case that a server (Asterisk) sent our client an authentication-info header in
its "bye" message, but our SIP device is just a client and never challenges the server.
Our client doesn't expect this header so the "bye" request was declined.
What is the right behavior for the client? The client should ignore the
unexpected header and process others?
Yes, ignore it. That header field has not been registered with IANA as a
valid header field. But we don't expect implementations to distinguish
between undefined headers and headers that are defined in extensions
that the server doesn't support. Unknown header fields are to be ignored.
Thanks,
Paul
Thanks,
Jing
-----------------------------------------------------------------------------------
BIAMP SYSTEMS EMAIL NOTICE
The information contained in this email and any attachments is confidential and
may be subject to copyright or other intellectual property protection. If you
are not the intended recipient, you are not authorized to use or disclose this
information, and we request that you notify us by reply mail or telephone and
delete the original message from your mail system.
-----------------------------------------------------------------------------------
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
