[SR-Users] record_route_advertised_address causes null send socket error

[Henning Westerholt]

Hello,

so it is more about transparently replacing one header in both directions. You could probably implement something like this with the help of the dialog module, or more lightweight with the htable module and normal header texops operations. Maybe the topo* modules are also worth a look for you, but they might be doing too much in this scenario.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>

From: Daniel Greenwald <dgreenwald at gmail.com>
Sent: Tuesday, February 25, 2020 11:39 PM
To: Henning Westerholt <hw at skalatan.de>
Cc: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>; Daniel-Constantin Mierla <miconda at gmail.com>
Subject: Re: [SR-Users] record_route_advertised_address causes null send socket error

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 at skalatan.de<mailto:hw at 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<https://gilawa.com/>

From: sr-users <sr-users-bounces at lists.kamailio.org<mailto:sr-users-bounces at lists.kamailio.org>> On Behalf Of Daniel Greenwald
Sent: Tuesday, February 25, 2020 10:48 PM
To: Daniel-Constantin Mierla <miconda at gmail.com<mailto:miconda at gmail.com>>
Cc: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org<mailto:sr-users at 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 at gmail.com<mailto:miconda at 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 at lists.kamailio.org<mailto:sr-users at lists.kamailio.org>

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--

Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>

www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com<http://www.asipto.com>

Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com<http://www.kamailioworld.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20200226/624acaba/attachment.html>