[reSIProcate] 503 Response from stack for BYE when UPDATE times out.

[Byron Campen]

	Since 1.2, resip doesn't blacklist on timeout (it instead  
"greylists", which causes the DNS tuple to be lowered in priority, but  
does not prevent it from being used if there are no other DNS tuples).  
I _strongly_ encourage you to update to the latest release, 1.3.4,  
since it incorporates a _very_ large number of vulnerability fixes.

Best regards,
Byron Campen

> Hi,
>
> I am using resiprocate1.1.
> I start an INVITE session with the server.
> The client refreshes the INVITE by sending UPDATE.
> If this UPDATE times out because the server dies out due to some  
> reason, I get 408 from the stack.
> Then I try to send BYE, but I get "503 Service Unavailable" from the  
> stack.
> From the resiprocate code "TransactionState.cxx" , it appears that  
> the stack blacklists the dns entry after getting 408.
>
> So is this an issue which needs to be resolved or is it resolved? If  
> resolved which version of resiprocate has it?
>
> Thanks,
> Sonika
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

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