[reSIProcate] ACK to non-2xx response not read by reSIProcate
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.
Mehul.