THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#229 - ACK not in transaction when t_relay or t_check_trans User who did this - Daniel-Constantin Mierla (miconda) ---------- The ACK seems ok, can you get any debug info from the device not accepting the ACK? ACK comes to kamailio and it is routed to callee, based on source IP and port of 200ok, because the callee is behind nat. The code you are referring to I guess is the one related to matching ACK to an existing INVITE transaction, used for accounting purposes. But the ACK itself for a 200OK is a separate transaction, being a request within dialog and has to be routed base on Route header. In the initial description of this item you say that Record-Route is added to ACK, I could not spot that in the trace you attached. Even it would be, that is a matter of config, transaction management/matching has nothing to do with Record-Route headers. If you want to get ACK matched to INVITE transaction, set acc module to record the ACK events and try again to see if there is any difference. Can you post the trace taken when using 1.5.x? I would like to see if there is any difference. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=229#comment6… You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.