Re: [reSIProcate] ACK to non-2xx response not read by reSIProcate
On 9/13/05, Mehul Jain <Mehul@xxxxxxxxxxx> wrote:
> Hi Jason,
> I ran the stack at "Stack" Log level and see the ACK in the Logs
> (TransactionState::processServerInvite: SipReq: ACK) but it is not
> being passed to the upper layer, where I have called
> "sipStack->receive()" .
>
> Regarding retransmissions, yes I do see many retransmissions. the INV
> and 403 were retransmitted once while the ACK was retransmitted twice.
The ACK is not passed up to the application. There is no reason for an
ACK to a failure response to be passed to the TU.