On Wed, 2008-08-20 at 19:29 +0530, Vivek Batra wrote:
> Thanks to all for your suggestions!
>
> Few ITSP disconnects the call when INVITE is challenged by called party viz
> (B). E.g., VoIPtalk
>
> When (B) sends 407 Auth. to VoIPtalk server, VoIPtalk then sends 486 Busy to
> caller viz (A). Hen
Authentication in multihoming application
Hi,
I have query regarding challenge response mechanism (digest authentication,
MD5) in SIP as follows:
A and B are SIP clients registered with B2BUA.
A calls B and sends INVITE to B2BUA. B2BUA challenges INVITE with response
407 Auth.
A again sends the
From: "Vivek Batra" <[EMAIL PROTECTED]>
I have query regarding challenge response mechanism (digest authentication,
MD5) in SIP as follows:
A and B are SIP clients registered with B2BUA.
A calls B and sends INVITE to B2BUA. B2BUA challenges INVITE with response
407 Auth.
A
PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Digest Authentication in multihoming application
Hi,
I have query regarding challenge response mechanism (digest authentication,
MD5) in SIP as follows:
A and B are SIP clients registered with B2BUA.
A calls B and se
El Tuesday 19 August 2008 14:26:31 Iñaki Baz Castillo escribió:
> How does B2BUA it has already authentiacted A before?
I mean:
"How does B2BUA it has already authentiacted A before?"
> The behaviour is what you describe but:
> - When 403 from B arrives to B2BUA, B2BUA could resend the request
>
2008/8/19, Vivek Batra <[EMAIL PROTECTED]>:
> Hi,
>
> I have query regarding challenge response mechanism (digest authentication,
> MD5) in SIP as follows:
>
>
>
> A and B are SIP clients registered with B2BUA.
>
> A calls B and sends INVITE to B2BUA. B2BUA challenges INVITE with response
> 40
Hi,
I have query regarding challenge response mechanism (digest authentication,
MD5) in SIP as follows:
A and B are SIP clients registered with B2BUA.
A calls B and sends INVITE to B2BUA. B2BUA challenges INVITE with response
407 Auth.
A again sends the INVITE with authentication header (say
