[reSIProcate] ACK to non-2xx response not read by reSIProcate

[Jason Fischl]

On 9/13/05, Mehul Jain <Mehul at ingenio.com> wrote:
>  
> In a INVITE, non-2xx response, ACK transaction -  the UAC receives a 403
> Messgae and generates the ACK as a part of the same transaction using the
> Helper::makeFailureAck function. The ACK message is built fine and at the
> other end, I see the ACK being received in the Ethereal trace. But the
> running instance of reSIProcate stack does not recognize this message; I
> dont see any logs (Logging is enabled DEBUG mode) that show the ACK message
> was received. 
>   
> I verified the message using ethereal at both ends. 
> Anybody faced such a problem before, or having an idea as to where the
> problem may be. 

It sounds like everything is working fine. Do you see any
retransmissions? If you aren't seeing retransmissions than I would
guess everything is working fine. It doesn't log the ACK at DEBUG
level. Try running at STACK log level if you want it to be more
verbose.

Jason