[kamailio/kamailio] Topos not working Properly for ACK (Issue #4208)
Pandi1981 created an issue (kamailio/kamailio#4208) We are facing an issue while using TOPOS in Kamailio P-CSCF (running under Docker). Kamailio version: 6.0.0 operating system: "10 (buster)" **Call Flow & Issue Description:** Note: Public IP and Private IP mapping using the below configuration. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ listen=udp:LOCAL_IP:5060 name "internal" listen=udp:LOCAL_IP:6080 advertise PUBLIC_IP:6080 name "external" ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ **Call Flow (INVITE):** A-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP) B-Party <-- Kamailio P-CSCF (Public IP) <-- Kamailio P-CSCF (Private IP) <-- Kamailio S-CSCF (Private IP) Everything works correctly up to the point where the 200 OK is received by the A-Party. However, when the A-Party sends the ACK, it is received by the Kamailio P-CSCF but is not forwarded to the B-Party. Upon investigation, we found that when Kamailio receives the ACK from the A-Party, the rr (Record-Route) module fails to recognize its own Route header and thus falls back to strict routing instead of performing loose routing. This results in an incorrect rewrite of the Request-URI of the ACK, causing it to fail to reach the B-Party. Essentially, the Route header is not popped as expected and the ACK routing breaks. TOPOS module is configured as follows: loadmodule "topos_redis.so" loadmodule "ndb_redis.so" loadmodule "topos.so" modparam("ndb_redis", "server", "name=tps;addr=127.0.0.1;port=6379;db=0") modparam("topos", "storage", "redis") modparam("topos_redis", "serverid", "tps") modparam("topos", "rr_update", 1) modparam("topos", "contact_mode", 1) modparam("topos", "xavu_field_a_contact", "a_contact") modparam("topos", "xavu_field_b_contact", "b_contact") modparam("topos", "xavu_cfg", "tps") Please guide us how to achieve and what we are doing wrong. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208@github.com>
linuxmaniac left a comment (kamailio/kamailio#4208)
Upon investigation, we found that when Kamailio receives the ACK from the A-Party, the rr (Record-Route) module fails to recognize its own Route header and thus falls back to strict routing instead of performing loose routing.
could you maybe attach a kamailio log with topos in debug mode for that scenario? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-2785674104 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/2785674104@github.com>
Pandi1981 left a comment (kamailio/kamailio#4208) [topos_github.log](https://github.com/user-attachments/files/19795756/topos_github.log) Please find the below details as per the node and IP. PCSCF_IP : 192.168.208.2 ICSCF_IP : 192.168.208.3 SCSCF_IP : 192.168.208.4 AS_IP : 192.168.208.8 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-2813024717 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/2813024717@github.com>
Pandi1981 left a comment (kamailio/kamailio#4208) Any update Please? Please let me know if you need any other information. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-2817718901 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/2817718901@github.com>
Pandi1981 left a comment (kamailio/kamailio#4208) Please guide us...it's a blocking issue as of now!! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-2842147302 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/2842147302@github.com>
Pandi1981 left a comment (kamailio/kamailio#4208) @linuxmaniac To understand TOPOS behaviour better, we simulated interconnection between two different providers and its working fine. In Kamailio,We suspected that both the originating and terminating INVITE requests were staying within the same network, which could impact proper ACK/BYE routing to the B-party. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-2880228754 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/2880228754@github.com>
github-actions[bot] left a comment (kamailio/kamailio#4208) This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-3006925438 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/3006925438@github.com>
Closed #4208 as not planned. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#event-18557108349 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issue/4208/issue_event/18557108349@github.com>
zusrut left a comment (kamailio/kamailio#4208) Same issue **topos** breakes **ACK** from A-Party - set **R-URI** from RR header according strict routing on the SBC. So it not pass to the B-Party. @Pandi1981 did find a way to make it works? @linuxmaniac can we reopen the issue I can provide any debug data if needed -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-3707201532 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/3707201532@github.com>
miconda left a comment (kamailio/kamailio#4208) Try to use `loose_route_mode("1")` and if not working, create a new issue attaching the pcap with the sip messages for the call. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-3707291455 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/3707291455@github.com>
zusrut left a comment (kamailio/kamailio#4208) With `loose_route_mode("1")` works - ACK traveling as expected. @miconda Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4208#issuecomment-3707414574 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4208/3707414574@github.com>
participants (5)
-
Daniel-Constantin Mierla -
github-actions[bot] -
Pandi1981 -
Victor Seva -
zusrut