[SR-Users] Question regarding Dispatcher + ds_default_socket() modparam + Call-ID generation

Joel Serrano joel at textplus.com
Wed Aug 14 17:12:21 CEST 2019


Simple doubt regarding dispatcher module when you have
the ds_default_socket() modparam set:

Say you have 2 kamailio boxes, active + passive, one shared IP via
keepalived.... On the actrive node, you have dispatcher.send_ping to 1, and
the passive has it set to 0.

So far OK, only the active box is sending out probing OPTIONS requests, and
it's using as outbound socket the virtual IP out of all the available ones
(as defined with ds_default_socket() modparam)

I have seen in a capture that the outbound OPTIONS look like:

OPTIONS sip: SIP/2.0
Via: SIP/2.0/UDP A.B.C.180
To: <sip:>
From: <sip:dspinger at my.domain>;tag=e2bdd495733c59fd91487a137fccad4e-8a73
Call-ID: 2019f8491329c382-31419 at A.B.C.181
Max-Forwards: 70
Content-Length: 0

A.B.C.180 -> VRRP
A.B.C.181 -> Physical IP of the box

My doubt is, shouldn't ds_default_socket also update the IP used to
generate the Call-ID used in the OPTIONS request? Currently, I believe it's
using the first defined listen= IP from config script as I switched the
order the listen= are defined and I get the desired result:

OPTIONS sip: SIP/2.0
Via: SIP/2.0/UDP A.B.C.180
To: <sip:>
From: <sip:dspinger at my.domain>;tag=5e2e1773f812f6a7e4085c5d036e29d8-d323
Call-ID: 7d9a92c218fc1ba0-32111 at A.B.C.180
Max-Forwards: 70
Content-Length: 0

Is this expected?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190814/7903ce87/attachment.html>

More information about the sr-users mailing list