mbia.edu
Subject: Re: [Sip-implementors] authentication-info header
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 ser
n...@lists.cs.columbia.edu [mailto:sip-
> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
> Sent: Tuesday, February 16, 2016 12:39 PM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] authentication-info header
>
> On 2/16/16 11:19 AM, J
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 decline
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 cl
Hi all,
I have a question regarding Authentication-Info header field. If we send
INVITE message and receive 401 or 407 with, for example, three different
challenges ( three Authentication header fields ). So, we re-send INVITE
with three credentials ( three Authorization header fields ). When we
