Yes but 2 problems with this: 1) listen parameter does not seem to accept an SRV or hostname listen=udp:MYPRIVATEIP:EXTERNALPORT advertise EXTERNALHOSTNAME causes the listen line to be ignored
2) My goal is not to do any state replication so I only want the SRV in record-route not VIA. VIA will still have IP. These are very light configs (no Dialog or backends etc) If a kamailio goes away, an in-dialog request should still hit another kamailio and the call will progress as if nothing happened. (Yes, in-progress Transactions will still fail but that's acceptable vs cost of TM replication)
On Wed, Feb 26, 2020 at 3:31 AM Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
if you control the freeswitches or change where they send traffic/receive traffic, then I recommend to use two listen parameters with advertise address, like:
listen=udp:my.ip.ad.dr:5060 advertise publicsrv:5060
listen=udp:my.ip.ad.dr:5080
and carriers will be linked to my.ip.ad.dr:5060, while for freeswitch you use udp:my.ip.ad.dr:5080. You can use force_send_socket()/set_send_socket() or $fs to enforce a specific socket for sending traffic (e.g., towards freeswitch or carriers).
There will be two record-route headers, but, besides enforcing sockets, everything else will be done automatically.
Cheers, Daniel On 25.02.20 23:38, Daniel Greenwald wrote:
carrier<---->kamailioes<----->freeswitches I am sending a record route header with a private SRV in the direction of freeswitch boxes and removing it when sending packets to carrier. I am using a different (pubic) SRV in contact header being sent to the carrier.
On Tue, Feb 25, 2020 at 4:59 PM Henning Westerholt hw@skalatan.de wrote:
Hi,
why are you calling record_route_advertised_address(..) on these replies or in-dialog requests? The record_route functions are usually used on initial dialog forming requests (INVITE, SUBSCRIBE etc..).
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*From:* sr-users sr-users-bounces@lists.kamailio.org *On Behalf Of *Daniel Greenwald *Sent:* Tuesday, February 25, 2020 10:48 PM *To:* Daniel-Constantin Mierla miconda@gmail.com *Cc:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* Re: [SR-Users] record_route_advertised_address causes null send socket error
They occur when calling it on responses to the initial INVITE, for example 183 and 200 OK.
On Tue, Feb 25, 2020 at 4:33 PM Daniel-Constantin Mierla < miconda@gmail.com> wrote:
Hello,
are those messages printed during the processing of the initial INVITE or when handling requests within dialog (re-INVITE, BYE, ...).
Cheers, Daniel
On 25.02.20 21:20, Daniel Greenwald wrote:
I am using record_route_advertised_address to insert a record route header with an SRV record. The header is added correctly and everything appears to be working fine however I get a CRITICAL log error when calling
record_route_advertised_address('INTERNAL_SRV');
2020-02-25T20:14:57.078235+00:00,ip-10-0-16-53: CRITICAL: cbbcfe06-d181-467c-bbf4-78772aa0562f 2 16777053 INVITE:<core> [core/msg_translator.c:514]: lump_check_opt(): null send socket 2020-02-25T20:14:57.078352+00:00,ip-10-0-16-53: CRITICAL: cbbcfe06-d181-467c-bbf4-78772aa0562f 2 16777053 INVITE:<core> [core/msg_translator.c:514]: lump_check_opt(): null send socket
Any ideas? I'm considering using insert_hf() to manually add it and bypass whatever check is failing. Thoughts?
Thanks
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com