[reSIProcate] ACK Challange issue

[Jason Fischl]

I'm pretty sure this was a known issue with 0.9.

I think we need to put something big and in bold on the resiprocate
homepage to indicate that it is highly recommended to move from 0.9 to
1.0.x.

Thanks
Jason


On 11/13/06, Scott Godin <slgodin at icescape.com> wrote:
> There is code at the top of ServerAuthManager::handle - that excludes
> ACKs and CANCELs from being challenged.  Are you using the latest SVN
> code or 1.0?
>
> > -----Original Message-----
> > From: resiprocate-devel-bounces at list.sipfoundry.org
> > [mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
> > Roger Peter
> > Sent: Monday, November 13, 2006 12:04 AM
> > To: resiprocate-devel at list.sipfoundry.org
> > Subject: [reSIProcate] ACK Challange issue
> >
> >
> > Why reSIProcate challanges ACK...?
> > And when then challanged is dispached by DUM it is cancelled by TU.
> > This
> > leads to inconsisten state. Server and client give and take lots of
> > 200OK
> > and ACK. But as the Challanged ACK din't reached the client it does
> not
> > respond with credentials. And thus it is not precessed by DUM.
> >
> > Can anyone tell me Solution to this....?
> >
> >
> >
> > Regards,
> > Roger.
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel at list.sipfoundry.org
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>