| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
I’ve got a fix for this which I’ll
check in; it is fixed in the teltel branch. --Derek CONFIDENTIALITY NOTICE This email and any files transmitted with it contains
proprietary information and, unless expressly stated otherwise, all contents
and attachments are confidential. This email is intended for the addressee(s)
only and access by anyone else is unauthorized. If you are not an addressee,
any disclosure, distribution, printing or copying of the contents of this email
or its attachments, or any action taken in reliance on it, is unauthorized and
may be unlawful. If you are not an addressee, please inform the sender
immediately and then delete this email and any copies of it. Thank you for your
co-operation. From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Elizabeth Clark I noticed a subscription is terminated if sending a NOTIFY
results in a 401 Unauthorized. Is there is reason the NOTIFY is not resent using digest
credentials if it has it? The code related to this is in Dialog::dispatch where the
msg is a response and the C_Seq is NOTIFY. The following if fails because
the lastRequest is null. if ( lastRequest && mDum.mClientAuthManager.get()
&& mDum.mClientAuthManager->handle( *lastRequest, msg ) ) In RFC 3265, section 3.2.2 it says "A the NOTIFY is
considered failed if ... a non-200 class response is received ... and no
implied further action which can be taken...". I believe, however if
the agent has the credentials, it should be able to resend the NOTIFY. Is this a bug? Regards, Liz |