[SR-Users] topos with mask_callid

Hi all, I am using Kamailio 5.8.1 on a Debian 12 machine with topos and topoh hiding the topology. I have observed with modparam("topos", "mask_callid", 1), in-dialog requests are relayed with the incorrect caller-id. In the scenario, A calls B. The call is set up and the call-id for the B-Leg

[SR-Users] Missing newline in dbtext tables causes crash and core dump

Hi all, I am using Kamailio 5.7.4 on a Debian 12 machine. I used ansible to template some files, and a newline was omitted at the end of the uacreg table due to a templating issue. This caused kamailio to crash on start up, with the error: 20(27) CRITICAL: [core/pass_fd.c:281]: receive_fd():

[SR-Users] Re: Using uac_replace_to when forwarding call to another endpoint

After digging through old mailing posts I've been able to resolve this by applying the changes in the BRANCH route. This fixes the corruption, although the logs still show a warning for applying it twice. Cheers On Thu, 7 Mar 2024 at 09:23, Benoit Panizzon wrote: > Hi Matthew > > > However in

[SR-Users] Using uac_replace_to when forwarding call to another endpoint

Hi all, I am using uac_replace_to to replace the TO header on requests. I understand it can only be called once per message and the recommendation is to store the updated value in a pvar and apply it in the branch route. However in my scenario I wish to first try one endpoint and then if it gets

[SR-Users] Re: rtimer intermittent failures

Hi Richard, Thanks for the tip, I had indeed overlooked the return value. Cheers Matthew On Tue, 5 Mar 2024 at 05:34, Richard Chan wrote: > In the method can you put > > return 1 > > at the end. KEMI python is very strict on an int return value. > > On Tue, 5 Mar 2024,

[SR-Users] rtimer intermittent failures

Hi all, I am using Kamailio 5.7.4 on a Debian 12 machine, with a Python Kemi based config. I am seeing some intermittent failures when accessing an instance variable within a function called by rtimer. I'm using the rtimer module with the following parameters: modparam("rtimer", "timer",

[SR-Users] Re: sips to sip

> I have this setup where one side is TLS and the other UDP. Normally this works fine, but we have this provider sending sips In theory SIPS should be TLS end-to-end. Some UAs will reject the call or misbehave if it's not. I'm not sure this is the issue you're experiencing but it's worth keeping

[SR-Users] Re: TOPOS + Forcing the send socket

t; > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* Marrold > *Sent:* Donnerstag, 19. Oktober 2023 02:05 > *To:* Henning Westerholt > *Cc:* Kamailio (SER) - Users Mailing List > *Subject:* Re

[SR-Users] Re: TOPOS + Forcing the send socket

; memory pool (e.g. by changing /etc/default/kamailio or similar). You can > verify with “ps aux”. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > &

[SR-Users] Re: TOPOS + Forcing the send socket

sers] Re: TOPOS + Forcing the send socket > > > > In the header of the topic you talking about topos, but inside the > messages you talking about topoh. > > They are 2 different modules. If you usr them together - they can > conflictin case how they affect message. Try use or just to

[SR-Users] Re: TOPOS + Forcing the send socket

alloc.c:501]: qm_free(): BUG: bad pointer 0x2 (out of memory block!) called from core: core/data_lump.c: free_lump(470) - ignoring 3(9) INFO: [core/parser/parse_fline.c:80]: parse_first_line(): message too short: 0 [] Does anyone have any ideas what's going on here? Thanks Matthew On Tue,

[SR-Users] TOPOS + Forcing the send socket

Hi all, I am using Kamailio (5.7.2, Debian 11, Python KEMI) in a mutli-homed environment with the topos module to hide the topology. I have noticed that when I use `set_send_socket` or `$fsn` to force the socket it's sent from, it breaks topos and the ACK is not proxied to the other leg of the

[SR-Users] uac_auth() in KEMI Python - Drop 401 sent to caller

Hi all, I'm attempting to use the uac module in KEMI (Python) to authenticate outbound requests. When the downstream replies with a 401 the proxy correctly re-sends the request with a Authorization header, but the 401 is also relayed to the caller. As far as I can tell I've converted the example

[SR-Users] Re: Creating CDRs for Missed and failed calls

a look to the default configuration, there is a stateful 404 send > in a similar scenario for (also) this reason in location lookup phase. > > Cheers, > > Henning > > -- > Henning Westerholt - https://skalatan.de/blog/ > Kamailio services - https://gilawa.com > > &g

[SR-Users] Creating CDRs for Missed and failed calls

Hi all, I'm using the acc module along with postgres to generate CDRs. For connected calls the CDRs are created as expected, but in the scenario where a lookup() fails and Kamailio sends a stateless 404 there's no CDR logged. I'm setting the FLT_ACCMISSED and FLT_ACCFAILED flags in the initial

Re: [SR-Users] TOPOH is generating new Call-ID for BYE

> Hello, > > check if the call-id value is not somehow changed by the endpoints, then > also direction has to be detected properly (check from/to/rr tags). > > Cheers, > Daniel > On 23.03.22 16:05, Marrold wrote: > > Hi, > > I have enabled the TOPOH module wi

[SR-Users] TOPOH is generating new Call-ID for BYE

Hi, I have enabled the TOPOH module with mask_callid enabled, but it's generating a new Call-ID for a BYE which gets rejected with a 481 downstream. If I disable the TOPOH module it works as expected. Does anyone know where I should start looking? SIP-wise the initial BYE seems compliant. This

[SR-Users] Can Kamailio send an ACK to a final response?

Hello, I'm exploring using Kamailio as a dumb edge proxy, and as such I want to keep things as lean as possible. In some scenarios I would like the "core" proxies to signal to the edge that a request should be dropped without a response. This could be with a custom header in the reply or perhaps

Re: [SR-Users] help to configure topos module configuration

Hi, I recently looked into this and I don't believe it's possible. As a work around I used split DNS and an FQDN in the contact. Thanks Matthew On Fri, Mar 18, 2022 at 8:44 AM Patrick Karton wrote: > > Caller <--> (internal_IP) Kamailio (external_IP) <---> Callee > > > I have this set up of

Re: [SR-Users] Kamailio + RADCLI

old email, but if it was not sorted out, then looks like some > issues with setting the radius dictionaries for the library. Here is an > aged tutorial, but there could still be useful details: > > * https://www.kamailio.org/docs/openser-radius-1.0.x.html > > Cheers, > Daniel > &

Re: [SR-Users] Kamailio + KEMI + topos + change_reply_status

the change is overwritten. Thanks Matthew On Wed, Mar 9, 2022 at 12:11 AM Karsten Horsmann wrote: > Hi Marrold, > > not tested but could it be that you check an string with an int? > > Kind regards > Karsten Horsmann > > Marrold schrieb am Di., 8. März 2022, 23:46: >

[SR-Users] Kamailio + KEMI + topos + change_reply_status

Hi, I'm using Kamailio 5.5.3 with a KEMI / Python based configuration on Debian 11. In my reply route I am trying to convert a 183 to a 180 with: KSR.textopsx.change_reply_status(180, "Ringing") I've noticed with TOPOS enabled, it doesn't work and I still see a 183 go out. But with it disabled,

Re: [SR-Users] topos xavu_field_contact_host kamailio 5.5

Hi Jonathan, Were you able to solve this problem? I'm running Kamailio in docker and need to write a different contact in each direction based on the flow - i.e the contact in the leg to the end device should be the external address, but the leg to another back end running in docker should be the

[SR-Users] Kamailio + RADCLI

Hi, We're currently testing Kamailio 5.5.3 on Debian 11 compiled with RADCLI and we're experiencing an issue with radius authentication: Feb 23 08:54:22 redacted /sbin/kamailio[817172]: WARNING:

[SR-Users] allow_source_address_group in failure route

Hello, I'm using Kamailio as a proxy between several voice gateways and if the call fails for whatever reason (far end is busy etc) I am forwarding to an Asterisk box to play an announcement. Within the failure route I am using allow_source_address_group() to ascertain if the failure response

Re: [SR-Users] Comunication between devices RTP/SRTP and viceversa

Hi, Unfortunately in my experience "Opportunistic SRTP" support is broken in many UAs. There are (at least) two ways of doing it covered indirectly in RFC3264 and the second explicitly in RFC8643 and devices seem

Re: [SR-Users] wireshark decode kamailio / rtpengine ng messages

Hi Karsten, The term they use is a "dissector" if that helps with your search. If you're just parsing info from one packet statelessly (I.E no relation to any other packet) it's fairly straightforward to throw something together. Thanks __

Re: [SR-Users] Catching websocket / TCP errors

in > case of network failure. > > On Wed, 20 Oct 2021 at 4:39 PM, Marrold wrote: > >> Hi all, >> >> Is there any way of catching these errors before sending a 500 No error >> (2/SL) ? >> >> Thanks >> >> On Tue, Oct 5, 2021 at 5:01 PM Mar

Re: [SR-Users] Catching websocket / TCP errors

Hi all, Is there any way of catching these errors before sending a 500 No error (2/SL) ? Thanks On Tue, Oct 5, 2021 at 5:01 PM Marrold wrote: > Hi Arsen > > That looks perfect, except we're still using 4.3.X on some of our proxies > ( I should have mentioned, sorry) . We plan

Re: [SR-Users] Catching websocket / TCP errors

odules/devel/modules/usrloc.html#usrloc.p.db_clean_tcp > > On Tue, Oct 5, 2021 at 8:49 PM Marrold wrote: > >> Hi, >> >> We're currently implementing WebRTC (SIP over a websocket) on our >> Kamailio proxies and we're experiencing a minor issue after a restart.

[SR-Users] Catching websocket / TCP errors

Hi, We're currently implementing WebRTC (SIP over a websocket) on our Kamailio proxies and we're experiencing a minor issue after a restart. We write all USRLOC entries to a shared database to implement HA. These are then loaded on a restart, which leaves us with entries with TCP connections

[SR-Users] Fwd: Catching an overall timeout after dropping replies

Hi, This is partially related to a previous thread - https://lists.kamailio.org/pipermail/sr-users/2021-August/113128.html We are using the TSILO module to suspend transactions whilst we wait for mobile app users to register after receiving a push notification. In the time we are waiting for

Re: [SR-Users] How to drop negative final response and send ACK

Hi Koray, I'm glad you mentioned this, I'm currently working on a similar configuration and tested your scenario and found the same thing. I'm assuming you're using TSILO? I just quickly tried this in the failure_route and it appears to be working but I'm sure there's still some optimisations to

Re: [SR-Users] Issues with TOPOS when not relaying an in-dialog request

the message. Everything else gets relayed. If I relay the SUBSCRIBE like other messages, the subsequent BYE is sent to the correct IP and everything works as expected. Thanks > > чт, 5 авг. 2021 г. в 14:27, Marrold : > >> Hi Henning, >> >> I realised as soon as I sent t

Re: [SR-Users] Issues with TOPOS when not relaying an in-dialog request

. Once I get to the bottom of this issue I'll try to share something. Thanks On Thu, Aug 5, 2021 at 2:45 PM mohsen khashei wrote: > Hi marrold can you share your config . I an trying to use kamailio as > b2bua with no success may be seeing some config help me. > Thanks > > On Thu,

Re: [SR-Users] Issues with TOPOS when not relaying an in-dialog request

e REGISTER and PUBLISH requests are skipped from > processing > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-users *On Behalf Of * >

[SR-Users] Converting Cisco SIP NOTIFY DTMF to SIP INFO (Binary operations)

Hi, I am using an old Cisco 2811 with an FXS card and trying to get it to convert between POTS and SIP. Mostly for "fun". For the most part it works, however there are some problems with DTMF in the call. Because the end device uses pulse dialling it seems that only the Cisco Proprietary SIP

Re: [SR-Users] Setting $conid per branch

etch_contact(). > > Cheers, > Daniel > On 19.03.21 11:13, Marrold wrote: > > We don't see the issue when using the standard lookup() function, only > when we start manually appending branches with the results > from reg_fetch_contact() > > Thanks > Matthew > >

Re: [SR-Users] Bad config - you can not call 'handle_publish' function (db_url not set)

Hi Daniel, That fixed the issue, thanks as always. On Wed, May 12, 2021 at 5:18 PM Daniel-Constantin Mierla wrote: > Hello, > On 12.05.21 18:01, Marrold wrote: > > Hi All, > > I've performed some crude troubleshooting and managed to replicate the > issue with the Debian

Re: [SR-Users] Bad config - you can not call 'handle_publish' function (db_url not set)

amailio starts up without error: modparam("presence", "local_log_facility", "3") Thanks On Tue, May 11, 2021 at 8:12 PM Marrold wrote: > Hi Both, > > Juha - Thanks for sharing your config , I tweaked the values in my config > but still experience the same issue

Re: [SR-Users] Bad config - you can not call 'handle_publish' function (db_url not set)

ou use utils module? If yes, what is your operating system and the > compiler version (if you compiled from sources, not installing from > packages)? > > Cheers, > Daniel > On 10.05.21 15:01, Marrold wrote: > > Hi, > > We're trying to upgrade from 5.3.X to 5.4

[SR-Users] Bad config - you can not call 'handle_publish' function (db_url not set)

Hi, We're trying to upgrade from 5.3.X to 5.4.5 however kamailio will not start and produces the following error, despite the db_url being set in the config and printed in the logs: Bad config - you can not call 'handle_publish' function (db_url not set) Looking at the code this error only

Re: [SR-Users] geting $conid on outbound INVITE

Hi David, I've previously looked at $conid and I was under the impression it was only available as the *source* connection ID for received messages, not the destination connection ID. Some experiments confirmed this, although I didn't dig too deeply into the code. It's inferred in the docs

Re: [SR-Users] Setting $conid per branch

We don't see the issue when using the standard lookup() function, only when we start manually appending branches with the results from reg_fetch_contact() Thanks Matthew On Wed, Mar 17, 2021 at 7:18 AM Daniel-Constantin Mierla wrote: > Hello, > > > On 11.03.21 10:55, Marrold w

Re: [SR-Users] Setting $conid per branch

ad of setting the r-uri > and append_branch(). > > Cheers, > Daniel > On 10.03.21 06:00, Marrold wrote: > > Hi, > > I've done a bit more digging and realised that $conid is read-only, and > only available for an inbound connection - so I dont think it will achieve > what I ne

Re: [SR-Users] Setting $conid per branch

Hi, I've done a bit more digging and realised that $conid is read-only, and only available for an inbound connection - so I dont think it will achieve what I need. I did a bit more troubleshooting and observed the differences in the debug log between two identical calls: This example failed -

[SR-Users] Setting $conid per branch

Hi all, I'm currently adding a feature to our Kamailio configuration to fork calls based on user agent. To do so I'm getting the registered endpoints with reg_fetch_contacts() iterating through and matching on them, then using seturi() / append_branch() and setting the dst-uri and flags as

Re: [SR-Users] Dispatcher - Force one end point active

nd others in "AP" > (flag 8) > > > On 21 August 2018 at 14:23, Marrold wrote: > >> Hi, >> >> We are currently using the dispatcher module and probing end points with >> OPTIONS, and making them active / inactive depending on the response: >> >>

[SR-Users] Dispatcher - Force one end point active

Hi, We are currently using the dispatcher module and probing end points with OPTIONS, and making them active / inactive depending on the response: modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3;code=404") modparam("dispatcher",

Re: [SR-Users] Re-write From URI Domain ($fd) with source IP or relayed message

Thanks Daniel, if that's the case we will re-write the from domain earlier in the logic On Wed, Jul 4, 2018 at 11:07 AM, Daniel Tryba wrote: > On Tue, Jul 03, 2018 at 11:21:50PM +0100, Marrold wrote: > > For interoperability reasons I need to re-write the From URI Domain ($fd) > &

[SR-Users] Re-write From URI Domain ($fd) with source IP or relayed message

Hi All, For interoperability reasons I need to re-write the From URI Domain ($fd) in requests proxied by Kamailio to the source IP (socket) that Kamailio will send them via. I have experimented with onsend_route and can successfully discover the snd_ip, however it seems I am unable to rewrite

Re: [SR-Users] Inserting local path into shared USRLOC table.

msg_apply_changes() worked nicely, thanks guys On Wed, Oct 11, 2017 at 10:45 AM, Charles Chance < charles.cha...@sipcentric.com> wrote: > Hello, > > > On 11 Oct 2017 10:16 a.m., "Daniel Tryba" <d.tr...@pocos.nl> wrote: > > On Tue, Oct 10, 2017 at 1