Hello,
iirc, ACKs for negative replies should be hop-by-hop, without any route set. Maybe you can paste a ngrep with invite/407/ack to see exactly what is there.
On the other hand, t_check_trans() for ack returns true if there is an active invite transaction associated with it, because ack itself does not create transaction, being a request that doesn't take a reply.
Cheers, Daniel
On 7/12/13 5:11 PM, Hugh Waite wrote:
Hello, I have a question on the use of t_check_trans for in-dialog requests.
If an in-dialog INVITE is challenged by kamailio (sending a 407 response), the ACK should be absorbed. However, the t_check_trans function does not terminate the script. In our config, this means the ACK gets sent to the client due to the route-set.
Should t_check_trans recognise that this transaction was rejected locally, even though there is an onward route-set?
Hugh