I'm afraid that this is perfectly legitimate proxy behavior as per RFC.
If your 200 OK contact contains a FQDN as domain part, the ACK will have it
in the R-URI and Kamailio will forcefully have to resolve it before
relaying and there is no guarantee that the result will be the same.
Also don't forget that ACK is a transaction on its own, if you want to
track down things between INVITE transaction and ACL transaction you have
to use an "external" mechanism, like can using dialog module or htable
module.


On Tue, Jul 2, 2019 at 10:55 AM Surendra Tiwari <notifications@github.com>
wrote:

> Description
>
> We are converting udp call to tcp call in kamailio. kamailio sending out
> an invite to a destination. Before sending, kamailio resolving that
> destination domain to IP. After receiving invite request, Destination send
> 180 and 200 OK . 200 Ok contact contains the domain name of destination.
> After this kamailio forward those request to next route. kamailio recieved
> the ack from upstream. After reciving the ack from upstream it resolves
> again the domain name to different IP, as domain name have 2 IP's behind.
> Troubleshooting Reproduction Debugging Data
>
> (paste your debugging data here)
>
> Log Messages
>
> (paste your log messages here)
>
> SIP Traffic
>
> (paste your sip traffic here)
>
> Possible Solutions Additional Information
>
> - *Kamailio Version* - output of kamailio -v
>
> (paste your output here)
>
>
> - *Operating System*:
>
> (paste your output here)
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/kamailio/kamailio/issues/1998?email_source=notifications&email_token=AA4KTY26Y3WSPZK2HKAFA63P5MJXPA5CNFSM4H4ZREHKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G42NI6Q>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA4KTYZCXGKHDSDETQJ253LP5MJXPANCNFSM4H4ZREHA>
> .
>


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.