Re: [reSIProcate] Subscription Refresh get 401Unauthorized

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

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