[SR-Users] Critical log when $mbu pseudovariable is accessed

[Daniel-Constantin Mierla]

The place to get the final message is in onsend_route, being available
in the $snd(buf).

That's when Kamailio figures out everything required for sending out
(e.g., resolving NAPTR/SRV/CNAME/ANAME/... dns, doing mhomed processing
to select local socket.a.s.o) and builds the appropriate headers like
Via, Record-Route, ...

Cheers,
Daniel

On 08.10.21 09:09, Alberto Izquierdo wrote:
> I see, would it be possible to obtain the final message (with the
> generated Record-Route headers) somehow?
>
> Thank you.
>
> On Fri, Oct 8, 2021 at 8:51 AM Daniel-Constantin Mierla
> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>
>     You have to use $mbu before record_route() because the outgoing
>     socket is not known and corresponding Record-Route header is added
>     with empty address. Same apply for use of msg_apply_changes().
>
>     Cheers,
>     Daniel
>
>     On 08.10.21 08:28, Alberto Izquierdo wrote:
>>     It is also worth mentioning that there are two Record-Route
>>     headers, the first one is the correct one and contains a valid
>>     value, and this extra one which does not appear in the egress
>>     INVITE in the pcap.
>>
>>     On Thu, Oct 7, 2021 at 9:18 AM Alberto Izquierdo
>>     <a.izquierdo at zaleos.net <mailto:a.izquierdo at zaleos.net>> wrote:
>>
>>         Hello Daniel,
>>
>>         I have just realized about an error in the 'Record-Route"
>>         header: "Record-Route: <sip:;r2=on;lr=on;ftag=478.0eb>".
>>
>>         Thanks for the response.
>>
>>         On Thu, Oct 7, 2021 at 9:05 AM Daniel-Constantin Mierla
>>         <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>>
>>             Hello,
>>
>>             in onsend_route the changes are already applied, use of
>>             $mbu makes no sense there -- you can see the updated
>>             buffer content with $snd(buf).
>>
>>             Cheers,
>>             Daniel
>>
>>             On 06.10.21 11:43, Alberto Izquierdo wrote:
>>>             Hi,
>>>
>>>             I'm getting some CRITICAL logs when accessing the
>>>             content of the $mbu pseudovariable in a "onsend_route"
>>>             function. The log lines look like this:
>>>
>>>             ```
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:893 FIXME:
>>>             null send_sock
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:1479 FIXME:
>>>             null bind_address
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             CRITICAL core    35847:core/msg_translator.c:493 null
>>>             send socket
>>>             ```
>>>
>>>             I've checked the msg_translator.c source file and there
>>>             are many of `LM_CRIT("FIXME: {message}\n");` calls, and
>>>             I wonder if the "FIXME" tag relates to the location of
>>>             the error: a Kamailio error or there is an issue in the
>>>             user code.
>>>
>>>             Could I have more information about the "FIXME" tag?
>>>
>>>             Thanks in advance!
>>>
>>>             __________________________________________________________
>>>             Kamailio - Users Mailing List - Non Commercial Discussions
>>>               * sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
>>>             Important: keep the mailing list in the recipients, do not reply only to the sender!
>>>             Edit mailing list options or unsubscribe:
>>>               * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <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 - Online
>>             Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone)
>>               * https://www.asipto.com/sw/kamailio-advanced-training-online/ <https://www.asipto.com/sw/kamailio-advanced-training-online/>
>>
>     -- 
>     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 - Online
>     Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone)
>       * https://www.asipto.com/sw/kamailio-advanced-training-online/ <https://www.asipto.com/sw/kamailio-advanced-training-online/>
>
-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone)
  * https://www.asipto.com/sw/kamailio-advanced-training-online/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20211008/8306c5b0/attachment.htm>