Re: [reSIProcate] 100rel and digest authentication
Hi Jeremy,
On 9/26/05, Jeremy Geras <jgeras@xxxxxxxxxxxxxx> wrote:
> Hi there,
>
> I've encountered the following scenario, using the resiprocate stack alone
> (without DUM):
>
> I send an INVITE (WITHOUT an Authorization header, but WITH a Supported:
> 100rel) and get back a 401 response. OK. The 401 response also includes
> "Supported: 100rel".
>
> When resiprocate receives this 401 response, it decides to send an ACK and
> terminate the transaction. I believe the responsible code is in
snip
> TransactionState.cxx, method processClientInvite():
> My question is: where's the bug here? I think I'm using 100rel correctly,
> but maybe not. Any advice would be appreciated.
>
There is no bug here. When resip receives a 401 that is the end of the
transaction and so the stack should send an ACK. You application (the
TU) needs to send a new INVITE with credentials in it. The 100rel is
only applicable to provisional responses (101 - 199).
Jason