Re: [reSIProcate] Subscription Refresh get 401Unauthorized
Hi,
I too am agree with you.
While calling requestRefresh() of ClientSubscription it is sending
mLastRequest with the updated expire values. If 401 Response comes then dum
uses baseCreator for sending request with the updated nuance, the value
stored in mLastRequest of ClientSubscription and of BaseCreator is different
hence handledByAuthOrRedirect() function in DialogUsageManager fails and
goes to default handling where it calls onTerminated() call back.
Thanks,
Niraj
-----Original Message-----
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Monday, February 05, 2007 9:30 PM
To: Niraj Roy; resiprocate-devel
Subject: RE: [reSIProcate] Subscription Refresh get 401Unauthorized
Can you provide a DEBUG level trace of this scenario? What version of
the stack?
The code looks correct, as long as you are sending the refresh using the
ClientSubscription API's.
Scott
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
> Niraj Roy
> Sent: Saturday, February 03, 2007 3:49 AM
> To: 'resiprocate-devel'
> Subject: [reSIProcate] Subscription Refresh get 401Unauthorized
>
> Hi,
> My application has subscribed for Message Waiting Indication
with
> Call Manager. Initially when Call Manager challenges this message with
> 401
> unauthorized stack successfully sends authentication detail and got
> success
> response.
> At the time of refreshing when resiprocate sends subscribe to
> Call
> Manager it gives 401 Unauthorized with the new nuance.
> Instead of sending subscribe with newer authentication detail
> stack
> gives onTerminated call back.
>
> Can any body shade some light on that..?
>
> Thanks,
> Niraj
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
__________ NOD32 2037 (20070205) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com