- sr-users - kamailio.org

Setting up Kamailio as SIP Proxy
by Saul Ibarra 04 Dec '23

04 Dec '23

Hi, I am needing some help setting up kamailio as a sip proxy between a provider(trunk) and a test pbx The trunk requires username&password and i would like to add that information to the request within the Kamailio proxy, so that the PBX can authenticate directly by IP (without username&password) through the Kamailio proxy. As a programmer with a limited background in SIP (currently learning), I am keen on understanding the intricacies of this setup at the SIP level. Could you please direct me to resources or documentation that covers scenarios similar to mine? Any help or guidance you could provide would be greatly appreciated. Thanks

4 8

tsilo dependency on usrloc
by Alex Balashov 03 Dec '23

03 Dec '23

Hi, I wanted to revisit the topic of tsilo dependence on the location service. All three ts_append*() functions have the following quality: - ts_append(): "performing a contact lookup on the table specified by the domain parameter." - ts_append_by_contact(): "the contact lookup is performed" - ts_append_to(): "performing a contacts lookup on the table specified by the domain parameter" Why is this extensive coupling to usrloc necessary? This makes it impossible to use `tsilo` in case of providing a push-notification add-on that front-ends an upstream registrar, requiring a kind of local shadow registrar or mid-registrar. What would make more sense is a generic mechanism that allows one to "drip" new contacts into an existing transaction, whether suspended or active. Kamailio has a mechanism to add more branches to an existing transaction, but the scope of that mechanism is only from *inside* the vantage point of the transaction in question. The key parlour trick of `tsilo` is that it permits dripping new branches into a *different* transaction. ts_append_to() almost does the trick, providing a target index and label, but it just insists on doing a registrar lookup to source the contacts. What is really wanted and needed for the downstream PN gateway use-case is a means of extracting contacts from incoming registrations (or other sources, potentially) without storing them in any fashion locally, without using or even loading usrloc, and just throwing them over the fence into a different transaction. Is this somehow possible by means other than tsilo? Am I overlooking something? Cheers, -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 3

Unable to use db_alias_lookup to call multiple extensions
by Merul Patel, PhD 01 Dec '23

01 Dec '23

Hi, Kamailio newby here. Having some trouble with using alias_db to forward an incoming call to two extensions. Thanks in advance for any help. I've tried using the Ubuntu Jammy ARM64 packages, as well as compiling the source for version 5.7.3. In both cases, I've added three extensions, and calls directly between them work fine with the vanilla kamailio.cfg. However, I then wanted to add an alias so that when called it would dial two extensions, but only the first extension is ever called. My kamailio.cfg only differs in a few places: $ diff kamailio.cfg kamailio.cfg.original 3,6d2 < #!define WITH_AUTH 1 < #!define WITH_DEBUG 1 < #!define WITH_ALIASDB 1 < # 268,270d263 < loadmodule "db_sqlite.so" < #!define DBURL "sqlite:///usr/local/kamailio-devel/etc/kamailio/kamailio.sqlite" < 367c360 < modparam("tm", "failure_reply_mode", 0) --- > modparam("tm", "failure_reply_mode", 3) 450d442 < modparam("alias_db", "append_branches", 1) I can see from the log that when dialling the desired alias (5000) an alias_db query is performed: Dec 01 20:00:23 merrivale /usr/local/kamailio-devel/sbin/kamailio[3264]: DEBUG: {1 2 INVITE 651794328853009-230332414159388(a)192.168.17.145} alias_db [alookup.c:169]: alias_db_query(): new URI [0] is [sip:6002@merrivale.localdomain] Dec 01 20:00:23 merrivale /usr/local/kamailio-devel/sbin/kamailio[3264]: DEBUG: {1 2 INVITE 651794328853009-230332414159388(a)192.168.17.145} alias_db [alookup.c:169]: alias_db_query(): new URI [1] is [sip:6001@merrivale.localdomain] But only the first result is called. I've changed the order of the aliases in the sqlite db and just the first result is called. What am I missing? Merul

1 0

How to use: kamcmd ul.db_users?
by Benoit Panizzon 01 Dec '23

01 Dec '23

Hi List I want to find a way to check how many users are regsitered. https://www.kamailio.org/docs/modules/devel/modules/usrloc.html#usrloc.r.db… But no matter how I try, I get a 500 error... # kamcmd ul.db_users location And yes, the table is called 'location'. I did try to find out how kamctl ul show --brief pulls that information, but did not succeed. Also that command takes way too long how that we have several thousand registered users. Or would I need to query this directly from the database? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

Info: RTC Devroom at FOSDEM 2024
by Daniel-Constantin Mierla 01 Dec '23

01 Dec '23

Hello, another edition of FOSDEM is approaching and it will include again a Real Time Communications devroom. If anyone wants to share their interesting applications or experiences in the field, consider to submit a presentation proposal. The CfP is available at: - https://lists.fosdem.org/pipermail/fosdem/2023q4/003518.html It does not have to be about Kamailio, all RTC topics are welcome, just think to be something useful for developers, as the event is targeting them. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

No access to variables within timer route
by dries＠degendt.com 30 Nov '23

30 Nov '23

Hi, I have a timer which is called each 5 seconds: modparam("timer", "declare_timer", "REFRESH_CALLSTATE_TIMER=REFRESH_CALLSTATE_TIMER,5000,slow"); I'm enabling setting the variable "testvar" and enabling the timer when an INVITE is received: if (is_method("INVITE|ACK|UPDATE|CANCEL|BYE")) { $var(testvar) = "blablabla"; timer_enable("REFRESH_CALLSTATE_TIMER", "1"); ... route[REFRESH_CALLSTATE_TIMER] { xlog("L_INFO", "Testvariable: $var(test)\n"); } However, the variable is always 0: INFO: <script>: Testvariable: 0 I've also tried printing pseudovariables like $ci, $du but nothinh seems accessible. Is there a workaround for this? Best regards, Dries

3 6

kamailio t_on_failure tcp timeout
by Julien Chavanton 29 Nov '23

29 Nov '23

Hi, I would like to catch TCP timeouts when I use a socket that was not closed. In this example I am sending SIP MESSAGE ... t_on_reply("ON_REPLY_MESSAGE"); t_on_failure("FAILURE_MESSAGE"); if (!t_relay()) sl_reply_error();

1 2

Evapi Async - suspend transaction for a limited time
by Ilie Soltanici 29 Nov '23

29 Nov '23

Hello, I'm trying to use the evapi_async_relay function from the evapi module, however,I don't want the transaction to be suspended for more than 1 second. For instance, if there's no response from the external application within this time frame, I want the script to continue and remove that transaction from memory. One potential approach I am considering is to add suspended transactions to a hash table with a timestamp value. Then, using rtimer module, I could periodically parse this table every second and process the results, but I'm not sure how efficient is that. Maybe you know other alternative, more efficient solutions (from a performance point of view) that could achieve the same goal? Any insights or recommendations would be greatly appreciated. Thank you.

3 6

5.6.4 debian htable dbmode=1 not writing at shutdown
by Bernd Krueger-Knauber 29 Nov '23

29 Nov '23

Hi, I have still the problem that my htables are not written into a sqlite db when I shutdown kamailio. Manual writing via: kamcmd htable.store ... is working. As I can see in the logs with highest loglevel, the function destroy() is never called. ht_db_url.len is > 0 ht_db_init_con() should work, else nothing would work with the db. But I can not see the debug messages from ht_db_open_con() Any ideas? Best regards, Bernd

5 5

Incompatibility of the DMQ htable protocol with older Kamailio versions
by Denys Pozniak 29 Nov '23

29 Nov '23

Hello! I noticed that there are differences in the DMQ htable replication protocol for the old version of Kamailio 5.2 and the new 5.7. For example, the new version uses action 2 when updating values and action 4 to remove. The old Kamailio version uses the values 1 and 3 respectively. Well, as a result, the htable data is not shared between such nodes, plus there are errors in the syslog of the old version: ERROR: htable [ht_dmq.c:328]: ht_dmq_handle_msg(): failed to replay action It would probably be worth introducing some kind of DMQ htable protocol versioning to maintain compatibility? And is there any option to make them work together (I wouldn’t really want to change the action number in sip/sdp/json on the fly)? Kamialio 5.2 {"action":1,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1} {"action":3,"htname":"shared","cname":"user","mode":0} Kamailio 5.7 {"action":2,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1} {"action":4,"htname":"shared","cname":"user","mode":0} -- BR, Denys Pozniak

2 2

tps_storage_fill_contact(): no r-uri user
by Denys Pozniak 28 Nov '23

28 Nov '23

Hello! My topology is like this: PBX -> Kamailio Topos -> User When calling the user, PBX does not add the user part in the Contact URI, something like: Contact: <sip:10.10.10.10:5080;transport=udp> When the customer sends a reinvite, the topos turns off for this transaction and the sip partially breaks down with error: topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user topos [tps_storage.c:615]: tps_storage_record(): failed to store As far as I understand, the RFC allows the absence of the user part in the URI and this occurs quite often. I can provide the pcap file and debug log in a private message if this helps identify the essence of the problem. # kamailio -v version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty -- BR, Denys Pozniak

3 5

Kamailio ver 5.7.3 - source installation warnings
by Muhammad Danish Moosa 28 Nov '23

28 Nov '23

Hi, I am planning to upgrade Kamailio to version 5.7.3 to manage some memory leaks issues. I am installing from source and came across these warnings, just wanted to be sure if they are safe to be ignored. cr_func.c: In function ‘set_next_domain_on_rule’: cr_func.c:160:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ cr_func.c:160:2: warning: (near initialization for ‘val.rs’) [-Wmissing-braces] cr_func.c: In function ‘actually_rewrite’: cr_func.c:348:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ cr_func.c:348:2: warning: (near initialization for ‘val.rs’) [-Wmissing-braces] cr_func.c: In function ‘ki_cr_load_user_carrier_helper’: cr_func.c:782:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ -- LD (gcc) [M p_usrloc.so] p_usrloc.so CC (gcc) [M evrexec.so] evrexec_mod.o evrexec_mod.c:64:1: warning: missing braces around initializer [-Wmissing-braces] static evrexec_info_t _evrexec_info = {0}; ^ evrexec_mod.c:64:1: warning: (near initialization for ‘_evrexec_info.data’) [-Wmissing-braces] LD (gcc) [M evrexec.so] evrexec.so CC (gcc) [M avp.so] avp.o LD (gcc) [M avp.so] avp.so CC (gcc) [M acc_diameter.so] diam_message.o CC (gcc) [M acc_diameter.so] acc_diameter_mod.o CC (gcc) [M acc_diameter.so] diam_avp.o CC (gcc) [M acc_diameter.so] diam_tcp.o LD (gcc) [M acc_diameter.so] acc_diameter.so CC (gcc) [M dmq.so] bind_dmq.o CC (gcc) [M dmq.so] message.o CC (gcc) [M dmq.so] dmq_funcs.o dmq_funcs.c: In function ‘ki_dmq_send_message’: dmq_funcs.c:304:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:304:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] dmq_funcs.c: In function ‘ki_dmq_bcast_message’: dmq_funcs.c:374:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:374:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] CC (gcc) [M dmq.so] notification_peer.o CC (gcc) [M dmq.so] dmq.o dmq.c:61:1: warning: missing braces around initializer [-Wmissing-braces] sip_uri_t dmq_server_uri = {0}; ^ dmq.c:61:1: warning: (near initialization for ‘dmq_server_uri.user’) [-Wmissing-braces] dmq.c:67:1: warning: missing braces around initializer [-Wmissing-braces] static sip_uri_t dmq_notification_uri = {0}; ^ dmq.c:67:1: warning: (near initialization for ‘dmq_notification_uri.user’) [-Wmissing-braces] Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

2 2

Info: Issue and PR automatic management
by Daniel-Constantin Mierla 27 Nov '23

27 Nov '23

Hello, during the Kamailio Development Meeting that took place in Dusseldorf earlier this month, one topic was related to administrative tasks related to project development and management, how to simplify/automatize such tasks. To reduce the work load on volunteering contributors, GitHub Actions were already used for various tasks related to project development and management (e.g., automatic builds on commits and pull requests to detect compile errors or code formatting mistakes). In Dusseldorf another task was configured to be managed with GitHub Actions, respectively the check of open issues and pull requests to evaluate the interest of submitters, developers and community users to pursue them. If there is no activity on an issue (potential bug or feature request) or a pull request, after 6 weeks it is marked with the label `stale`. After two more weeks of no activity, the issue or the pull request is marked with the label `expired` and closed. Note that any comment postpones the expire timeline, being considered that there is interest in pursuing the issue or the pull request. Requests for features were already treated in this way: if nobody commits to implement it, it can be closed after one month, but it needed manual work and many were still kept open. Potential bug reports that become very old are hard to tackle if the source code changes or new major releases are out, they might even not be valid anymore. Anyhow, this automatic operations can be reverted if there is still interest in pursuing the specific issues or pull requests. A registered developer can remove labels and reopen a closed issue or pull request. The non-registered-developer contributors have to make a comment that includes the token `/notstale` to remove the label `stale` or includes the token `/notexpired` to reopen a closed item. This new kind of automatic task management might add a little inconvenience because one has to restate the interest from time to time for those items that could not be addressed. However, considering that Kamailio is an open source collaborative project, in order to be fair for those that volunteer to spend time and resources for development of Kamailio, also the users/submitters have to stay engaged, not just report and forget about. The process to automatize tasks related to Kamailio development and administration is work in progress. Everything can be adjusted based on feedback (e.g., time lines), feel free to suggest improvements or new solutions to make things easier for everyone within the project ecosystem. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

How to remove record-route and via from a forwarded call?
by Benoit Panizzon 27 Nov '23

27 Nov '23

Hi List Two Kamailio Nodes situation. Node A: Routing Instance. Node B: Registrar Instance. An invite is sent from Node A to B. Customer registered on B is 'busy' as example. B initiates Call Forwarding by adding a Diversion Header and sending the Invite back to A with a new R-URI towards the CFB destination. The Invite sent from B to A still has Node B in it's Record-Route. So all subsequent SIP messages pass via B, which is not needed and cause issue with rtpengine running on B. I attempted to remove_record_route(); when sending the call back to A, but this causes: parse_headers(): bad header field [;lr;ftag=3910078620-883101371> It looks like only the beginning of the RR header is removed leaving back a competely broken line. What is the propper was to remove a node from RR and Via routing? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

WEBRTC-to-SIP & Vice Versa
by Vishal Pai 26 Nov '23

26 Nov '23

Hello All Good Day Here I am trying to achieve something like this WSS to UDP Ext registartion which works well using https://github.com/havfo/WEBRTC-to-SIP/tree/master/etc Note here i am forwarding the registartion to asterisk pbx server and define WSS of kamailio Now for calls - Webrtc - SIP calls works - SIP - Webrtc calls not working Here I am getting the request of the call on kamailio but kamailio send 404 not found to Asterisk PBX Webrtc - Webrtc calls not working Can anyone guide me on what I am doing wrong? Thanks Vishal P

3 3

refer-to to new INVITE
by Social Boh 26 Nov '23

26 Nov '23

Hello, I'd like to know if there is a way, from Kamailio side, take the refer-to header Kamailio receive in a REFER request and create a new INVITE whit this data; then bridge the call between the originating user and the new destination user. Thank you Regards -- --- I'm SoCIaL, MayBe

3 4

Re: RADIUS - Can't use extra attributes
by Duarte Rocha 24 Nov '23

24 Nov '23

Hello Daniel, Thanks for the reply. The extra dictionary is already included otherwise an error is thrown and Kamailio doesn't start. However, i realized my mistake now and you were right. I was checking for the extra attributes in a tcpdump and on radius server and i didn't had the dictionary configured on both of them. The extra attributes are in the packet but weren't being listed. One more question. Kamailio doesn't have a way to do a totally custom RADIUS access-request packet right? (Sorry if this opens another thread. I usually just hit reply on the mailing list and let Outlook create the e-mail, but it usually creates another thread and i'm not sure why). Thanks again. Cheers, Duarte

1 0

Re: RADIUS - Can't use extra attributes
by Duarte Rocha 24 Nov '23

24 Nov '23

Hello Daniel, Thanks for the reply. The extra dictionary is already included otherwise an error is thrown and Kamailio doesn't start. However, i realized my mistake now and you were right. I was checking for the extra attributes in a tcpdump and on radius server and i didn't had the dictionary configured on both of them. The extra attributes are in the packet but weren't being listed. One more question. Kamailio doesn't have a way to do a totally custom RADIUS access-request packet right? (Sorry if this opens another thread. I usually just hit reply on the mailing list and let Outlook create the e-mail, but it usually creates another thread and i'm not sure why). Thanks again. Cheers, Duarte

1 0

Max-Forwards header missing in OPTIONS keep-alive messages
by Christian Schnell 24 Nov '23

24 Nov '23

Hello, in RFC 3261 (sec. 8.1.1.6) it states about the Max-Forwards header field: > A UAC MUST insert a Max-Forwards header field into each request it originates with a value that SHOULD be 70. > > Source: https://datatracker.ietf.org/doc/html/rfc3261#section-8.1.1.6 When Kamailio sends its OPTIONS keep-alive requests (from the nathelper module I believe), Max-Forwards is missing: > OPTIONS sip:alice@example.com:61266 SIP/2.0 > Via: SIP/2.0/UDP aa.bb.cc.dd:5060;branch=z9hG4bK5124450 > From: sip:pinger@sip.example.com;tag=uloc-6550aa14-7456-2461-6390f173-5fdb4667 > To: sip:alice@example.com:61266 > Call-ID: aba25282-2ca72be1-9d1fd53(a)aa.bb.cc.dd > CSeq: 1 OPTIONS > Content-Length: 0 The user agent library I'm using (libre from baresip) rejects these requests with a "400 Bad Request" response, I looked at the sources and it denies these requests because of the missing Max-Forwards header. Of course this suffices for the keep-alive logic because all that's needed is any traffic in both directions to keep both (potential) NATs open. However you might agree that it does look a bit confusing at first, and the RFC is clear about that. So it's not a bug, but is this behavior intended? Thanks, also thanks for all the great work that has been put into Kamailio. Christian

3 3

error sending message to heplify server.
by masoud96＠mail.ru 24 Nov '23

24 Nov '23

Hello, I have an error when sending a message to the heplify server: Nov 23 15:09:59 sip1-life3 kamailio[1045006]: CRITICAL: {2 1395 INVITE ad25bc92-16a8-4be6-a29f-a4e4ee3a2c0c} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045006]: ERROR: {2 1395 INVITE ad25bc92-16a8-4be6-a29f-a4e4ee3a2c0c} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc5f0, len: 445, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044995]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948b18, len: 1511, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154979898, len: 485, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044995]: CRITICAL: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c50, len: 532, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c80, len: 560, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c40, len: 529, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f215494b6a8, len: 823, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044996]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045015]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc5a0, len: 507, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045015]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045015]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc158, len: 1037, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044996]: CRITICAL: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154978c18, len: 506, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045195]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948e00, len: 567, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045195]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045195]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948fe8, len: 488, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc158, len: 542, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message version: kamailio 5.7.2 (x86_64/linux) 95629c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 95629c compiled on 14:30:56 Nov 20 2023 with gcc 10.2.1

2 1

Hump presence mwi htable
by David VILLAUME 24 Nov '23

24 Nov '23

Hello, I'm running presence_mwi without database. I'm looking for a way to dump the presence htable content, is there any way to perform that ? Regards [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_bf…] David VILLAUME Ingénieur Voix Tel : +33 156377321 david.villaume(a)sewan.fr 2 cité Paradis - 75010 PARIS www.sewan.fr<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_78…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_13…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_24…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…>

2 1

RADIUS - Can't use extra attributes
by duarterocha91＠gmail.com 24 Nov '23

24 Nov '23

Hello all, I'm currently implementing a Kamailio with RADIUS. I want to send an Access-Request to my RADIUS server and in order to do that i'm using misc_radius module and radius_does_uri_exist() function without any arguments : "if (radius_does_uri_exist()) {" For my module configuration I have the following configurations : "modparam("misc_radius", "radius_config", "/etc/radcli/radiusclient.conf") modparam("misc_radius", "uri_extra", "Sip-Method=$rm")" From what i understand, with this config my access-request should contain the default attributes and Sip-Method Attribute but that is not happening. Only defaults attributes are included. I've tried to run Kamailio with "-ddd" flag for better debug and i only get this error : "1(176) DEBUG: misc_radius [functions.c:615]: radius_does_uri_user_host_exist(): failure". Is there any other configuration that i must do? Thanks for the help. Cheers, Duarte

2 1

Online devel meeting on matrix - 14:30 UTC, Dec 5, 2023
by Daniel-Constantin Mierla 24 Nov '23

24 Nov '23

Hello, we should consider an online devel meeting sometime soon to summarize what was done at (and still needs to be done after) devel meeting in Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)? If considered useful, I propose Dec 5 at 14:30UTC (15:30 Berlin/Paris/Madrid/Rome), but we can also look for other dates as well. Topics to be discussed can be added at: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings… Pull requests can be made by users without git access. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 1

sips to sip
by David Villasmil 24 Nov '23

24 Nov '23

Hello guys, I have this setup where one side is TLS and the other UDP. Normally this works fine, but we have this provider sending sips as the schema everywhere (from, to, rr, contacts), kamailio sends the same sips to the upstream usp freeswitch. My problem is when FS sends back a 200OK and kamailio forwards it back to the provider, the provider sends an ACK and kamailio can't match it with the dialog and doesn't know where to forward it. i think this is happening because FS when is sees SIPS is setting the contact port as 5081 instead of the usual 5080... Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 8

Dialog + DMQ: dlg_ontimeout() triggered on wrong node!
by Benoît Panizzon 23 Nov '23

23 Nov '23

Hello World! Kamailio 5.5 in use. I wonder, how I could prevent this issue. modparam("dialog", "send_bye", 1) modparam("dialog", "default_timeout", 21600) in the corresponding route: $dlg_ctx(timeout_route) = "DIALOG_TIMEOUT"; dlg_manage(); Dialog starts on Node01 and it's variables, status and timer are DMQ synced to Node02 As both nodes have the same information, I guess both arm the timeout trigger and sometimes the wrong node is more trigger friendly. If dlg_ontimeout() is triggered on Node02 then: * No Bye is send, as Node02 is not handling that Dialog. * Dialog is removed from Memory on Node02 and state synced back to Node01 * Dialog is removed from Memory on Node01 too, but NOT from database [*1] * Dialog CDR is never commited on Node01 * Call is never sent to timeout_route And subsequent in dialog messages on Node01 result in: dlg_onroute(): unable to find dialog Did I misconfigure something? Is there a way to make sure the timer is NOT triggered on the node not handling the dialogue? Shall I try by setting the default_timeout and then use a timeout_avp to set that timeout slightly lower AFTER the dialog has started? Or would this be synced to the other node too? I found out, session timer changes are not synced after an initial timer was synced, so you can not extend the session timer after setting a initial timeout. So maybe this is also true for dialog timeout? [*1] this also explains why upon restarting kamailio, the dialog suddenly is back and after timing out again, a CDR is then written with a way too long duration. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users