Re: Dispatcher sets IP flag on servers even though SIP OPTIONS receive 200 OK
Pablo Oliver via sr-users <[email protected]>
| Newsgroups | gmane.comp.voip.ser |
|---|---|
| Message-ID | <CA+GoCoVoa63bg+ffY-NL+C0L3cB2tDY5PuLx3WXYynv1LKaE+g@mail.gmail.com> |
Thanks for that. I didn't know about that setting On Thu, 26 Jun 2025, 09:31 James Browne, <[email protected]> wrote: > It's strange that your screenshot didn't show that, but thanks for the > feedback. By the way, you can also use ds_default_socket module parameter > instead of relying on the order of the listen directives. > > James > > On Thu 26 Jun 2025, 08:18 Pablo Oliver via sr-users, < > [email protected]> wrote: > >> I found the issue, I have two IPs one public and one private. For some >> reason Kamailio was using the public to send the SIP request to the private >> network. I've swapped the order and use advertise, and it's working fine. >> >> Thanks for quick reply >> >> On Wed, 25 Jun 2025, 09:35 Daniel-Constantin Mierla, <[email protected]> >> wrote: >> >>> Hello, >>> >>> you have to send the pcap with the keepalive OPTIONS? The screen shots >>> are not that useful for troubleshooting, it is some indication of >>> retransmissions, but it cannot be asserted properly on the screenshot. >>> Furthermore, the dispatcher.list output shows 183 timeouts, meaning that >>> the gateways haven't responded to 183 keepalives till that moment. >>> >>> Cheers, >>> Daniel >>> On 24.06.25 20:51, Pablo Oliver via sr-users wrote: >>> >>> Hi there, >>> >>> I'm new to Kamailio, and maybe this is a silly question. >>> >>> I’ve set up Kamailio as a SIP proxy with two Asterisk servers acting as >>> media services. >>> >>> This is my configuration for the dispatcher module: >>> >>> loadmodule "dispatcher.so" >>> >>> modparam("dispatcher", "db_url", DBURL) >>> modparam("dispatcher", "table_name", "dispatcher") >>> modparam("dispatcher", "flags", 2) >>> modparam("dispatcher", "ds_ping_interval", 20) >>> modparam("dispatcher", "ds_ping_method", "OPTIONS") >>> modparam("dispatcher", "ds_probing_threshold", 5) >>> modparam("dispatcher", "ds_inactive_threshold", 5) >>> modparam("dispatcher", "ds_ping_latency_stats", 1) >>> modparam("dispatcher", "ds_probing_mode", 1) >>> modparam("dispatcher", "ds_ping_reply_codes", >>> "class=2;code=403;code=488;class=3") >>> modparam("dispatcher", "ds_ping_from", SIPCALL) >>> >>> I can see the SIP OPTIONS requests going from Kamailio to Asterisk and >>> receiving 200 OK responses. >>> >>> >>> >>> However, the dispatcher is still setting the IP (Inactive Probing) flag >>> on the servers: >>> >>> kamcmd dispatcher.list >>> { >>> NRSETS: 1 >>> RECORDS: { >>> SET: { >>> ID: 1 >>> TARGETS: { >>> DEST: { >>> URI: sip:172.16.254.21:5060 >>> FLAGS: IP >>> PRIORITY: 0 >>> LATENCY: { >>> AVG: 0 >>> STD: 0 >>> EST: 0 >>> MAX: 0 >>> TIMEOUT: 183 >>> } >>> } >>> DEST: { >>> URI: sip:172.16.254.20:5060 >>> FLAGS: IP >>> PRIORITY: 0 >>> LATENCY: { >>> AVG: 0 >>> STD: 0 >>> EST: 0 >>> MAX: 0 >>> TIMEOUT: 183 >>> } >>> } >>> } >>> } >>> } >>> } >>> >>> >>> So when I try to use ds_select_dst("1", "4"), it always fails. >>> >>> Did I miss something in my configuration? >>> >>> Thanks! >>> >>> Regards, >>> Pablo. >>> >>> >>> __________________________________________________________ >>> Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] >>> To unsubscribe send an email to [email protected] >>> Important: keep the mailing list in the recipients, do not reply only to the sender! >>> >>> -- >>> Daniel-Constantin Mierla (@ asipto.com)twitter.com/miconda -- linkedin.com/in/miconda >>> Kamailio Consultancy, Training and Development Services -- asipto.com >>> >>> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions -- >> [email protected] >> To unsubscribe send an email to [email protected] >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> > __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!