[reSIProcate] ACK Challange issue

[Byron Campen]

	As far as I know, neither DUM nor repro challenges ACK. What  
revision are you working with? If you are working with release 0.9.0,  
be advised that 1.0.1 is out.

Best regards,
Byron Campen

>
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061113/77aa8fc0/attachment.bin>