<!-- Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment). -->
### 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.
<!-- Explain what you did, what you expected to happen, and what actually happened. -->
### Troubleshooting
#### Reproduction
<!-- If the issue can be reproduced, describe how it can be done. -->
#### Debugging Data
<!-- If you got a core dump, use gdb to extract troubleshooting data - full backtrace, local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile bt full info locals list
If you are familiar with gdb, feel free to attach more of what you consider to be relevant. -->
``` (paste your debugging data here) ```
#### Log Messages
<!-- Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->
``` (paste your log messages here) ```
#### SIP Traffic
<!-- If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->
``` (paste your sip traffic here) ```
### Possible Solutions
<!-- If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix. -->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
``` (paste your output here) ```
* **Operating System**:
<!-- Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...; Kernel details (output of `uname -a`) -->
``` (paste your output here) ```
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 .
yeah right now we are using dialog module for tracking those things but there should be an option to use same tcp connection across the call if connection is alive.
that's already the case if you use IP addresses in 200 OK => ACK. The parameter you are speaking can not be implemented in core modules like tm, because that would mean implementing a tracking between transactions which is totally out of scope for those modules. Again, mechanisms external external to transactions need to be used.
Like mentioned by comments here, the behavior is as expected by specs, the proxy has to resolve the R-URI address for forwarding. The ACK following 200ok is independent of INVITE transaction (can have also different path than the INVITE, a matter of Record-Route headers).
Use other variants if you want to keep the ip/port of the callee, like a dialog variable, or htable value based on call id and to-tag, or even use set_contact_alias()/handle_ruri_alias() for a solution that doesn't require storage inside kamailio.
I am closing this one, if you want to discuss further about possible solutions, write to sr-users mailing list.
Closed #1998.