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

[Joel Serrano]

Hello,

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:190.14.203.219:5060 SIP/2.0
Via: SIP/2.0/UDP A.B.C.180
;branch=z9hG4bK7abb.6fbaccc1000000000000000000000000.0
To: <sip:190.14.203.219:5060>
From: <sip:dspinger at my.domain>;tag=e2bdd495733c59fd91487a137fccad4e-8a73
CSeq: 10 OPTIONS
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:186.188.220.174:5060 SIP/2.0
Via: SIP/2.0/UDP A.B.C.180
;branch=z9hG4bKc97e.a8d9e1c2000000000000000000000000.0
To: <sip:186.188.220.174:5060>
From: <sip:dspinger at my.domain>;tag=5e2e1773f812f6a7e4085c5d036e29d8-d323
CSeq: 10 OPTIONS
Call-ID: 7d9a92c218fc1ba0-32111 at A.B.C.180
Max-Forwards: 70
Content-Length: 0


Is this expected?

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