- sr-users - kamailio.org

Re: RTPENGINE - RTP Proxy
by Duarte Rocha 27 Jul '23

27 Jul '23

Hello Alex, Thank you for your answer, I still don't have sound but the behaviour is now different. Is it possible to configure this behaviour on a call by call basis with flags on the rtpengine_manage() function? Or in alternative having it consume the "direction=" attribute on the SDP? Cheers

1 0

RTPENGINE - RTP Proxy
by Duarte Rocha 26 Jul '23

26 Jul '23

Hello all, I'm currently doing some experiments with RTPENGINE and I need some help configuring it. First scenario i'm under NAT and Kamailio receives an INVITE with a private address, rewrites (c) line on SDP with it's own IP address and relays the message to the destination endpoint. After that the originator receives the 183 Session Progress with kamailio's IP as (c) parameter. After receiving the first RTP packet from the originator the media streams flow normally and I have sound on both sides including ringing. Second scenario I use different equipment that is not under NAT, but the remaining scenario is the same, except the originator doesn't send an RTP packet after the 183 Session Progress. However, in this case, no RTP stream is relayed to the originator and as a consequence it doesn't hear a ring or voice when the call is answered. As i see it, it looks like Kamailio is on passive mode to the A-Leg of the call and waits for a RTP packet to establish its stream. Is this correct? If so, how do i change this behaviour? Cheers

2 1

Re: Kamailio as SIP proxy for an Asterisk with Private IP Address
by Lewis Hutchinson 25 Jul '23

25 Jul '23

This is always a good place to start https://www.fredposner.com/1457/kamailio-behind-nat/ Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

5 6

tcpops: Variable conid on tcp-closed event
by Michal Hajek 24 Jul '23

24 Jul '23

Hi, I have problem with the conid variable, when I use in an event when closing a tcp connection. Simple kamailio.cfg: debug=3 log_stderror=no loadpath "/usr/lib64/kamailio/modules" memdbg=5 memlog=5 log_facility=LOG_LOCAL3 listen=udp:10.10.8.94:5060 listen=tcp:10.10.8.94:5060 loadmodule "sl.so" loadmodule "xlog.so" loadmodule "pv.so" loadmodule "tcpops.so" request_route { xlog("L_INFO", "Welcome TCP conn $conid\n"); exit; } event_route[tcp:closed] { xlog("L_INFO", "Close TCP conn $conid\n"); } Log: kamailio DEBUG: <core> [core/ip_addr.c:577]: print_ip(): tcpconn_new: new tcp connection: 10.10.9.64 kamailio DEBUG: <core> [core/tcp_main.c:1216]: tcpconn_new(): on port 38124, type 2, socket 34 kamailio DEBUG: <core> [core/tcp_main.c:1549]: tcpconn_add(): hashes: 3487:2267:2872, 19 kamailio DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0xb39c40, 34, 2, 0x14c2479867f0) - fd_no=28 kamailio DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xb39c40, 34, -1, 0x0) fd_no=29 called kamailio DEBUG: <core> [core/tcp_main.c:4557]: handle_tcpconn_ev(): sending to child, events 2001 kamailio DEBUG: <core> [core/tcp_main.c:4227]: send2child(): selected tcp worker idx:2 proc:14 pid:1203550 for activity on [tcp:10.10.8.94:5060], 0x14c2479867f0 kamailio DEBUG: <core> [core/tcp_read.c:1735]: handle_io(): received n=8 con=0x14c2479867f0, fd=6 kamailio DEBUG: <core> [core/tcp_read.c:284]: tcp_read_data(): EOF on connection 0x14c2479867f0 (state: 3, flags: 4118) - FD 6, bytes 218, rd-flags 10000 ([10.10.9.64]:38124 -> [10.10.9.64]:5060) kamailio DEBUG: <core> [core/tcp_read.c:1533]: tcp_read_req(): content-length=0 kamailio DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 kamailio DEBUG: <core> [core/parser/msg_parser.c:678]: parse_msg(): SIP Request: kamailio DEBUG: <core> [core/parser/msg_parser.c:680]: parse_msg(): method: <OPTIONS> kamailio DEBUG: <core> [core/parser/msg_parser.c:682]: parse_msg(): uri: <sip:100@localhost> kamailio DEBUG: <core> [core/parser/msg_parser.c:684]: parse_msg(): version: <SIP/2.0> kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Via] type 1 kamailio DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKhjhs8ass877>; state=15 kamailio DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 kamailio DEBUG: <core> [core/parser/msg_parser.c:554]: parse_headers(): Via found, flags=2 kamailio DEBUG: <core> [core/parser/msg_parser.c:556]: parse_headers(): this is the first via kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Call-ID] type 6 kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [From] type 4 kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [To] type 3 kamailio DEBUG: <core> [core/parser/parse_addr_spec.c:884]: parse_addr_spec(): end of header reached, state=10 kamailio DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): <To> [20]; uri=[sip:100@localhost] kamailio DEBUG: <core> [core/parser/msg_parser.c:175]: get_hdr_field(): to body (20)[<sip:100@localhost> ], to tag (0)[] kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Content-Length] type 12 kamailio DEBUG: <core> [core/parser/msg_parser.c:186]: get_hdr_field(): content_length=0 kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [CSeq] type 5 kamailio DEBUG: <core> [core/parser/msg_parser.c:153]: get_hdr_field(): cseq <CSeq>: <63104> <OPTIONS> kamailio DEBUG: <core> [core/receive.c:389]: receive_msg(): --- received sip message - request - call-id: [ahoj423432432] - cseq: [63104 OPTIONS] kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:261]: ksr_evrt_pre_routing(): event route core:pre-routing not defined kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:471]: receive_msg(): preparing to run routing scripts... kamailio DEBUG: {1 ahoj423432432} <core> [core/tcp_main.c:1645]: _tcpconn_find(): found connection by id: 19 kamailio INFO: {1 ahoj423432432} <script>: Welcome TCP conn 19 kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:529]: receive_msg(): request-route executed in: 47 usec kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/xavp.c:640]: xavp_destroy_list(): destroying xavp list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/xavp.c:640]: xavp_destroy_list(): destroying xavp list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/xavp.c:640]: xavp_destroy_list(): destroying xavp list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:628]: receive_msg(): cleaning up kamailio DEBUG: <core> [core/tcp_read.c:1634]: tcp_read_req(): EOF after reading complete request ([10.10.9.64]:38124 -> [10.10.9.64]:5060) kamailio DEBUG: <core> [core/tcp_read.c:1653]: release_tcpconn(): releasing con 0x14c2479867f0, state -1, fd=6, id=19 ([10.10.9.64]:38124 -> [10.10.9.64]:5060) kamailio DEBUG: <core> [core/tcp_read.c:1657]: release_tcpconn(): extra_data (nil) kamailio DEBUG: <core> [core/tcp_main.c:3653]: handle_tcp_child(): reader response= 14c2479867f0, -1 from 2 kamailio DEBUG: <core> [core/tcp_main.c:3578]: tcp_emit_closed_event(): TCP closed event creation triggered (reason: 0) kamailio DEBUG: tcpops [tcpops.c:295]: tcpops_handle_tcp_closed(): received TCP closed event kamailio DEBUG: tcpops [tcpops.c:249]: tcpops_tcp_closed_run_route(): event reason id: 0 rt: 1 kamailio INFO: <script>: Close TCP conn <null> Can you help me, where is issue?

1 0

Kamailio as SIP proxy for an Asterisk with Private IP Address
by John shuku 24 Jul '23

24 Jul '23

Dear Kamailio users, Im new to kamailio so excuse me if the question doesnt make sense. I have an asterisk server with private IP address behind the NAT . Is it possible to have a Kamailio Server with Public IP Address as a proxy server for my asterisk ? What I want to achieve is that remote users should be able to call internal users who are registered in the Asterisk . The problem here is that Asterisk does not have public IP address and I want the remote users to be registered in my asterisk . Best WishesJ. sh

3 4

Re: Add a digest authorization with password and username (INVITE)
by Max Kemel 20 Jul '23

20 Jul '23

Thank you very much Barry, that was it 🙂 Max Kemel

1 0

Add a digest authorization with password and username (INVITE)
by Max Kemel 20 Jul '23

20 Jul '23

Hello, I would appreciate any help you can provide on this matter, I would like to make an outgoing INVITE request which will have a digest authorization with password and username. I was wandering around the Auth module to find the most fit method to build this header but hadn't found anything. Maybe I am missing something really obvious here, thanks for the help in advance Best regards, Max.

2 1

Kamailio v5.5.7 Released
by Daniel-Constantin Mierla 19 Jul '23

19 Jul '23

Hello, Kamailio SIP Server v5.5.7 stable release is out. This is a maintenance release of the stable branch 5.5 that includes fixes since the release of v5.5.6. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.7. Note that 5.5 is now the third last stable branch, v5.5.7 being the last planned released in 5.5.x series. The latest two stable branch are 5.6 and 5.7, with v5.7.1 being released a while ago. For more details about version 5.5.7 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/07/kamailio-v5-5-7-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 0

Releasing Kamailio v5.5.7
by Daniel-Constantin Mierla 19 Jul '23

19 Jul '23

Hello, I am planning to release v5.5.7 our of branch 5.5 this week, most likely on Wednesday, July 19, 2023. It will mark the end of official packaging for release series 5.5.x, currently the latest two stable branches are 5.6 and 5.7. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 1

Re: WebRTC proxy with rtpengine - How to change from RTP to SRTP on 488 response
by Alex Balashov 18 Jul '23

18 Jul '23

I wouldn't do a delete in that situation; it might be simpler to just do another rtpengine_offer() on a <Call-ID, From-tag> tuple that RTPEngine already knows about, just as one would in a reinvite. I believe rtpengine_manage() would cover this situation as well. And yes, then just t_relay() anew! > On Jul 18, 2023, at 11:41 AM, Barry Flanagan <barry(a)flantel.com> wrote: > > On 18/07/2023 16:33, Alex Balashov wrote: >> Barry, >> >> Might it not be simpler to follow Richard's first suggestion in that thread, and simply catch the 488 response in a failure_route and re-issue a non-SRTP offer on another branch? > > hi Alex, > > Might be. I am just unsure about how to instruct rtpengine to re-send the plain RTP invite. Do I do a rtpengine_delete and then restart with rtpengine_manage() then relay again? > > Thanks. > > -Barry > > >> >> -- Alex >> >>> On Jul 18, 2023, at 11:05 AM, Barry Flanagan <barry(a)flantel.com> wrote: >>> >>> Hi, >>> >>> I have implemented a WebRTC proxy using Kamailio and rtpengine, in front >>> of Asterisk servers. I have an issue where I do not know in advance >>> whether the Asterisk client is set to use RTP or SRTP. >>> >>> My implementation expects the web side to be SRTP and the Asterisk side >>> plain RTP. However, if the asterisk side requires SRTP I receive a 488 >>> Not Acceptable here. The same is true when an SRTP client from the >>> Asterisk side dials out to the webrtc client, I need to catch whether >>> the request is SRTP or RTP and generate rtpengine offer accordingly. >>> >>> This was discussed in github, with a description of a solution here: >>> https://github.com/sipwise/rtpengine/issues/435#issuecomment-391937398 - >>> however I am unsure how to implement this. >>> >>> Does anyone have an example of how I can change the rtpengine SDP in >>> such a case? >>> >>> Thanks >>> -- >>> -Barry >>> __________________________________________________________ >>> Kamailio - Users Mailing List - Non Commercial Discussions >>> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org >>> Important: keep the mailing list in the recipients, do not reply only to the sender! >>> Edit mailing list options or unsubscribe: > > -- > -Barry > -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

1 0

WebRTC proxy with rtpengine - How to change from RTP to SRTP on 488 response
by Barry Flanagan 18 Jul '23

18 Jul '23

Hi, I have implemented a WebRTC proxy using Kamailio and rtpengine, in front of Asterisk servers. I have an issue where I do not know in advance whether the Asterisk client is set to use RTP or SRTP. My implementation expects the web side to be SRTP and the Asterisk side plain RTP. However, if the asterisk side requires SRTP I receive a 488 Not Acceptable here. The same is true when an SRTP client from the Asterisk side dials out to the webrtc client, I need to catch whether the request is SRTP or RTP and generate rtpengine offer accordingly. This was discussed in github, with a description of a solution here: https://github.com/sipwise/rtpengine/issues/435#issuecomment-391937398 <https://github.com/sipwise/rtpengine/issues/435#issuecomment-391937398>- however I am unsure how to implement this. Does anyone have an example of how I can change the rtpengine SDP in such a case? Thanks -- -Barry

2 1

Kamailio 5.6.4 and htable dbmode=1
by Bernd Krueger-Knauber 18 Jul '23

18 Jul '23

Hi Daniel, thank you for your response. As you can see in the provided debug output: kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable [callpush] - dbmode [1] kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable [callpush] - dbtable [userpush] kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable [callpush] - expire [86400] kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable [callpush] - size [10] dbmode is set to 1 in the config: modparam("htable", "db_url", "sqlite:////etc/kamailio/htable.sqlite") ... modparam("htable", "htable", "userpush=>size=3;autoexpire=600;dbtable=userpush;dbmode=1") If I execute kamcmd htable.store userpush I get Ok. Htable successfully stored to DB. But the table is still empty!!! In the log I found: ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database ERROR: db_sqlite [dbase.c:177]: db_sqlite_cleanup_query(): finalize failed: attempt to write a readonly database ERROR: htable [ht_db.c:668]: ht_db_delete_records(): failed to delete db records in [userpush] ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database Ok. But I can not see this entries if I shutdown kamailio. And: -rw-rw-rw- 1 kamailio root 16384 Jul 13 16:14 htable.sqlite I never used: modparam("db_sqlite","db_set_readonly" ... I also restarted kamailio. no difference. Now more errors then before: It is not written at shutdown. (no messages) It is not written (live) (with error messages, but why it is readonly?) The message of kamcmd is wrong (says Ok but it failed) Best regards, Bernd Am 17.07.2023 um 08:48 schrieb Daniel-Constantin Mierla: > Hello, > > is dbmode=1 in htable definition? > > If you run rpc command htable.store for the htable, are the records > saved to database? > > Cheers, > Daniel > > On 13.07.23 17:45, Bernd Krueger-Knauber wrote: >> Hi, >> >> I just tried to use sqlite and htable to load and save the values. >> At start I can see in the log, that all parameters are correct and >> that htable want to load the values from the table. >> No errors. >> >> But if I stop kamailio, nothing is written to the tables. >> >> At start I can see: >> >> kamailio[]: DEBUG: <core> [core/modparam.c:112]: >> set_mod_param_regex(): 'htable' matches module 'htable' >> kamailio[]: DEBUG: <core> [core/sr_module.c:814]: find_param_export(): >> found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: <core> [core/modparam.c:128]: >> set_mod_param_regex(): found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable >> [callpush] - dbmode [1] >> kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable >> [callpush] - dbtable [userpush] >> kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable >> [callpush] - expire [86400] >> kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable >> [callpush] - size [10] >> >> >> >> kamailio[]: DEBUG: htable [ht_api.c:1084]: ht_db_load_tables(): >> loading db table [userpush] in ht [userpush] >> kamailio[]: DEBUG: htable [ht_db.c:232]: ht_db_load_table(): >> =============== loading hash table [userpush] from database [userpush] >> kamailio[]: DEBUG: db_sqlite [dbase.c:223]: db_sqlite_submit_query(): >> submit_query: select key_name,key_type,value_type,key_value from >> userpush order by key_name >> kamailio[]: DEBUG: <core> [db_query.c:72]: db_do_submit_query(): >> submitted query: select key_name,key_type,value_type,key_value from >> userpush order by key_name, result 0 >> kamailio[]: DEBUG: <core> [db_res.c:119]: db_new_result(): allocate 56 >> bytes for result set at 0x7f4882107938 >> kamailio[]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 >> columns >> kamailio[]: DEBUG: <core> [db_res.c:138]: db_free_result(): freeing >> result set at 0x7f4882107938 >> >> Ok, the file is empty, but it tries to load the data from the table. >> >> The table looks like: >> >> sqlite> .schema userpush >> CREATE TABLE userpush ( >> key_name TEXT, >> "key_type" INTEGER, >> value_type INTEGER, >> key_value TEXT >> ); >> >> >> I checked the source code and I saw that destroy() should be called. >> Inside is ht_db_open_con() called before ht_db_sync_tables(), were it >> happens. >> But I can even not see the debug message from ht_db_open_con() : >> >> LM_DBG("database connection opened successfully\n") >> and also not >> LM_ERR("failed to connect to the database\n"); >> >> For me it looks like, that the destroy() function is not called. >> >> Even with debug=3, I can only see: >> >> >> systemd[]: Stopping kamailio.service - Kamailio - the Open Source SIP >> Server... >> kamailio[]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received >> systemd[]: kamailio.service: Deactivated successfully. >> systemd[]: Stopped kamailio.service - Kamailio - the Open Source SIP >> Server. >> >> I stopped kamailio with >> >> systemctl stop kamailio >> >> I'm sure that something was inside the htable before I stoped kamailio: >> >> { >> entry: 0 >> size: 1 >> slot: { >> { >> name: >> 07db580a6c13e798a5acc0d123d6e957897c8650b43f99d6d5cb9c2cb5ba4fa4 >> value: >> 3a28dcb73eb65722df5a261983b7692cecdca482bf8725032e46a0c6b89fb355 >> type: str >> } >> } >> } >> >> Any further ideas? >> >> Best regards, >> >> Bernd >> >> >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email tosr-users-leave(a)lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only >> to the sender! >> Edit mailing list options or unsubscribe: -- EDNT GmbH Werner-von-Siemens-Strasse 7 64625 Bensheim www.ednt.de Registergericht: Darmstadt Registernummer: 24972 Geschäftsführer: Karlheinz Knapp

6 8

Fwd: Kamailio 5.6.4 and htable dbmode=1
by Bernd Krueger-Knauber 17 Jul '23

17 Jul '23

-------- Weitergeleitete Nachricht -------- Betreff: Re: [SR-Users] Kamailio 5.6.4 and htable dbmode=1 Datum: Mon, 17 Jul 2023 09:50:37 +0200 Von: Bernd Krueger-Knauber <bkk(a)ednt.de> An: miconda(a)gmail.com Hi Daniel, thank you for your response. As you can see in the provided debug output: kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable [callpush] - dbmode [1] kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable [callpush] - dbtable [userpush] kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable [callpush] - expire [86400] kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable [callpush] - size [10] dbmode is set to 1 in the config: modparam("htable", "db_url", "sqlite:////etc/kamailio/htable.sqlite") ... modparam("htable", "htable", "userpush=>size=3;autoexpire=600;dbtable=userpush;dbmode=1") If I execute kamcmd htable.store userpush I get Ok. Htable successfully stored to DB. But the table is still empty!!! In the log I found: ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database ERROR: db_sqlite [dbase.c:177]: db_sqlite_cleanup_query(): finalize failed: attempt to write a readonly database ERROR: htable [ht_db.c:668]: ht_db_delete_records(): failed to delete db records in [userpush] ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database Ok. But I can not see this entries if I shutdown kamailio. And: -rw-rw-rw- 1 kamailio root 16384 Jul 13 16:14 htable.sqlite I never used: modparam("db_sqlite","db_set_readonly" ... I also restarted kamailio. no difference. No more errors then before: It is not written at shutdown. (no messages) It is not written (live) (with error messages, but why it is readonly?) The message of kamcmd is wrong (says Ok but it failed) Best regards, Bernd Am 17.07.2023 um 08:48 schrieb Daniel-Constantin Mierla: > Hello, > > is dbmode=1 in htable definition? > > If you run rpc command htable.store for the htable, are the records > saved to database? > > Cheers, > Daniel > > On 13.07.23 17:45, Bernd Krueger-Knauber wrote: >> Hi, >> >> I just tried to use sqlite and htable to load and save the values. >> At start I can see in the log, that all parameters are correct and >> that htable want to load the values from the table. >> No errors. >> >> But if I stop kamailio, nothing is written to the tables. >> >> At start I can see: >> >> kamailio[]: DEBUG: <core> [core/modparam.c:112]: >> set_mod_param_regex(): 'htable' matches module 'htable' >> kamailio[]: DEBUG: <core> [core/sr_module.c:814]: find_param_export(): >> found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: <core> [core/modparam.c:128]: >> set_mod_param_regex(): found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable >> [callpush] - dbmode [1] >> kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable >> [callpush] - dbtable [userpush] >> kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable >> [callpush] - expire [86400] >> kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable >> [callpush] - size [10] >> >> >> >> kamailio[]: DEBUG: htable [ht_api.c:1084]: ht_db_load_tables(): >> loading db table [userpush] in ht [userpush] >> kamailio[]: DEBUG: htable [ht_db.c:232]: ht_db_load_table(): >> =============== loading hash table [userpush] from database [userpush] >> kamailio[]: DEBUG: db_sqlite [dbase.c:223]: db_sqlite_submit_query(): >> submit_query: select key_name,key_type,value_type,key_value from >> userpush order by key_name >> kamailio[]: DEBUG: <core> [db_query.c:72]: db_do_submit_query(): >> submitted query: select key_name,key_type,value_type,key_value from >> userpush order by key_name, result 0 >> kamailio[]: DEBUG: <core> [db_res.c:119]: db_new_result(): allocate 56 >> bytes for result set at 0x7f4882107938 >> kamailio[]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 >> columns >> kamailio[]: DEBUG: <core> [db_res.c:138]: db_free_result(): freeing >> result set at 0x7f4882107938 >> >> Ok, the file is empty, but it tries to load the data from the table. >> >> The table looks like: >> >> sqlite> .schema userpush >> CREATE TABLE userpush ( >> key_name TEXT, >> "key_type" INTEGER, >> value_type INTEGER, >> key_value TEXT >> ); >> >> >> I checked the source code and I saw that destroy() should be called. >> Inside is ht_db_open_con() called before ht_db_sync_tables(), were it >> happens. >> But I can even not see the debug message from ht_db_open_con() : >> >> LM_DBG("database connection opened successfully\n") >> and also not >> LM_ERR("failed to connect to the database\n"); >> >> For me it looks like, that the destroy() function is not called. >> >> Even with debug=3, I can only see: >> >> >> systemd[]: Stopping kamailio.service - Kamailio - the Open Source SIP >> Server... >> kamailio[]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received >> systemd[]: kamailio.service: Deactivated successfully. >> systemd[]: Stopped kamailio.service - Kamailio - the Open Source SIP >> Server. >> >> I stopped kamailio with >> >> systemctl stop kamailio >> >> I'm sure that something was inside the htable before I stoped kamailio: >> >> { >> entry: 0 >> size: 1 >> slot: { >> { >> name: >> 07db580a6c13e798a5acc0d123d6e957897c8650b43f99d6d5cb9c2cb5ba4fa4 >> value: >> 3a28dcb73eb65722df5a261983b7692cecdca482bf8725032e46a0c6b89fb355 >> type: str >> } >> } >> } >> >> Any further ideas? >> >> Best regards, >> >> Bernd >> >> >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email tosr-users-leave(a)lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only >> to the sender! >> Edit mailing list options or unsubscribe: -- EDNT GmbH Werner-von-Siemens-Strasse 7 64625 Bensheim www.ednt.de Registergericht: Darmstadt Registernummer: 24972 Geschäftsführer: Karlheinz Knapp

1 0

Kamailio 5.6.4 and htable dbmode=1
by Bernd Krueger-Knauber 17 Jul '23

17 Jul '23

Hi, I just tried to use sqlite and htable to load and save the values. At start I can see in the log, that all parameters are correct and that htable want to load the values from the table. No errors. But if I stop kamailio, nothing is written to the tables. At start I can see: kamailio[]: DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'htable' matches module 'htable' kamailio[]: DEBUG: <core> [core/sr_module.c:814]: find_param_export(): found <htable> in module htable [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] kamailio[]: DEBUG: <core> [core/modparam.c:128]: set_mod_param_regex(): found <htable> in module htable [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable [callpush] - dbmode [1] kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable [callpush] - dbtable [userpush] kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable [callpush] - expire [86400] kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable [callpush] - size [10] kamailio[]: DEBUG: htable [ht_api.c:1084]: ht_db_load_tables(): loading db table [userpush] in ht [userpush] kamailio[]: DEBUG: htable [ht_db.c:232]: ht_db_load_table(): =============== loading hash table [userpush] from database [userpush] kamailio[]: DEBUG: db_sqlite [dbase.c:223]: db_sqlite_submit_query(): submit_query: select key_name,key_type,value_type,key_value from userpush order by key_name kamailio[]: DEBUG: <core> [db_query.c:72]: db_do_submit_query(): submitted query: select key_name,key_type,value_type,key_value from userpush order by key_name, result 0 kamailio[]: DEBUG: <core> [db_res.c:119]: db_new_result(): allocate 56 bytes for result set at 0x7f4882107938 kamailio[]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns kamailio[]: DEBUG: <core> [db_res.c:138]: db_free_result(): freeing result set at 0x7f4882107938 Ok, the file is empty, but it tries to load the data from the table. The table looks like: sqlite> .schema userpush CREATE TABLE userpush ( key_name TEXT, "key_type" INTEGER, value_type INTEGER, key_value TEXT ); I checked the source code and I saw that destroy() should be called. Inside is ht_db_open_con() called before ht_db_sync_tables(), were it happens. But I can even not see the debug message from ht_db_open_con() : LM_DBG("database connection opened successfully\n") and also not LM_ERR("failed to connect to the database\n"); For me it looks like, that the destroy() function is not called. Even with debug=3, I can only see: systemd[]: Stopping kamailio.service - Kamailio - the Open Source SIP Server... kamailio[]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received systemd[]: kamailio.service: Deactivated successfully. systemd[]: Stopped kamailio.service - Kamailio - the Open Source SIP Server. I stopped kamailio with systemctl stop kamailio I'm sure that something was inside the htable before I stoped kamailio: { entry: 0 size: 1 slot: { { name: 07db580a6c13e798a5acc0d123d6e957897c8650b43f99d6d5cb9c2cb5ba4fa4 value: 3a28dcb73eb65722df5a261983b7692cecdca482bf8725032e46a0c6b89fb355 type: str } } } Any further ideas? Best regards, Bernd

2 1

Using Kamailio in front of Freeswitch for load balancing REG and Calls
by Shah Hussain Khattak 12 Jul '23

12 Jul '23

Hello Awesome people, I have configured Kamailio in front of two Freeswitch servers. I am using the dispatcher module to load and balance the traffic between the two FS boxes. My dispatcher is configured in a round-robin fashion. If I send a register to my FS servers, the re-register post-challenge (401) message is routed to the second FS server and the registration fails. I want to check with you guys how are you handling this in your setups. I am sure a lot of companies are using Kamailio to load balance traffic toward the FS and Asterisk servers. UAC --- > Kamailio --- > FS1 REG ---- > REG ---- > REG 401 <---- 401 < ---- 401 re-register with authorization data: UAC --- > Kamailio --- > FS2 REG --- > REG ---- > REG 401 <---- 401 < ---- 401 it just create this loop and register fails. Ideally, I want Kamailio to send the re-register (with auth data) to the same FS server that challenged it. Any ideas or pointers to fix this issue would be highly appreciated, maybe I am missing some very basic configuration. Or maybe there is another simpler way instead of using a dispatcher module. Thank you! Regards, Shah Hussain

2 4

Re: sr-users Digest, Vol 218, Issue 16
by satyaprakash ch 11 Jul '23

11 Jul '23

Hi Please find some more before and after, Ip address and number is masked FYI. INFO: <script>: TIME : TEST - Rewriting To header with Request line so that vendor prefix is present INFO: <script>: TIME : TEST2 - tu is sip:+123456789@10.0.77.88 and ru is sip:10.0.1.47:5060 INFO: <script>: TIME : TEST3 - tu is sip:+123456789@10.0.77.88 and ru is sip:10.0.1.47:5060 ERROR: tm [tm.c:1752]: _w_t_relay_to(): t_forward_noack failed ERROR: tm [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for failure handler INFO: <script>: TIME : [Mon Jul 10 12:24:14 2023] CALL ID : [31bca077-99fa-123c-eb84-00219b9e3ef4] [WITHINDIALOG] The request is [ACK] INFO: <script>: TIME : [Mon Jul 10 12:24:14 2023] CALL ID : [31bca077-99fa-123c-eb84-00219b9e3ef4] [PROXY_OUTBOUND_HANDLE] [ACK] INFO: <script>: TIME : [Mon Jul 10 12:24:14 2023] CALL ID : [ 205526695_49743609(a)206.147.84.20] [WITHINDIALOG] The request is [ACK] Here is the code i suspect, Let me know if you can find some thing why the error usually gets, *failure_route["serial"] { if (!t_next_contacts()) { exit; } t_on_failure("serial"); xlog("L_INFO","TIME : [$Tf] CALL ID : [$ci] [serial]The altered ruri is [$ru] \n"); xlog("L_INFO", "TIME : TEST - Rewriting To header with Request line so that vendor prefix is present"); xlog("L_INFO","TIME : TEST2 - tu is $tu and ru is $ru \n"); $tu = $ru; xlog("L_INFO","TIME : TEST3 - tu is $tu and ru is $ru \n"); t_relay();}event_route[tm:branch-failure:REMOVE_OLD_REGISTER] { if (t_check_status("(404)|(410)")) { xlog("L_INFO","TIME : Received code [$T(reply_code)] from SBC, need to remove registration \n"); xlog("L_INFO","TIME : [$Tf] CALL ID : [$ci] [REMOVE_OLD_REGISTER] contact is [$ct]Unregister section is entered [$ru] \n"); unregister("location", "$tu", "$T_reply_ruid"); }}* Thank you. On Tue, Jul 11, 2023 at 3:46 PM <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > Today's Topics: > > 1. Need an error description (satyaprakash ch) > 2. Re: Need an error description (Alex Balashov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Jul 2023 22:25:31 +0530 > From: satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com> > Subject: [SR-Users] Need an error description > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.kamailio.org> > Message-ID: > < > CAO-xAtGhcDMiPtoGdBeb6qvhOg8u7hxKt-w-5oU4KuOkdRHuqg(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000005a4339060024dadd" > > Hi, > > Can anyone help me with the error why can we get this? > > ERROR: tm [tm.c:1752]: _w_t_relay_to(): t_forward_noack failed ERROR: tm > [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for > failure handler > > Thank you. >

2 1

Need an error description
by satyaprakash ch 10 Jul '23

10 Jul '23

Hi, Can anyone help me with the error why can we get this? ERROR: tm [tm.c:1752]: _w_t_relay_to(): t_forward_noack failed ERROR: tm [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for failure handler Thank you.

2 1

event_route[tm:local-response] only executes a few times
by Kaufman 10 Jul '23

10 Jul '23

Hello, I'm writing a 302 redirect server and wanting to capture some events on all replies, so I'm trying to do this in event_route[tm:local-response], but I noticed that the event route is only called a few times for the first few requests, and then never gets executed again. This is the simplest case in which I can reproduce the issue: #!KAMAILIO loadmodule "pv" loadmodule "tm" loadmodule "xlog" route { xinfo("[$rm $ci-$cs] Src:[$si:$sp] RURI:[$ru] To:[$tu] From:[$fu]\n"); t_send_reply("404", "Not Found"); exit; } event_route[tm:local-response] { xcrit("[$rm $ci-$cs] tm:local-response replied locally\n"); } If I start Kamailio with kamailio -ddDDeE it has 8 children. If I use sipp to send 10 requests, this is what I see in the kamailio logs. The critical line in the event route is only printed four times. This is tested on 5.7.0 and 5.6.4 9(66) INFO: <script>: [INVITE 1-14(a)172.26.0.3-1<mailto:1-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 9(66) CRITICAL: <script>: [INVITE 1-14(a)172.26.0.3-1<mailto:1-14@172.26.0.3-1>] tm:local-response replied locally 10(67) INFO: <script>: [ACK 1-14(a)172.26.0.3-1<mailto:1-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) INFO: <script>: [INVITE 2-14(a)172.26.0.3-1<mailto:2-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) CRITICAL: <script>: [INVITE 2-14(a)172.26.0.3-1<mailto:2-14@172.26.0.3-1>] tm:local-response replied locally 12(69) INFO: <script>: [ACK 2-14(a)172.26.0.3-1<mailto:2-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 13(70) INFO: <script>: [INVITE 3-14(a)172.26.0.3-1<mailto:3-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 13(70) CRITICAL: <script>: [INVITE 3-14(a)172.26.0.3-1<mailto:3-14@172.26.0.3-1>] tm:local-response replied locally 14(71) INFO: <script>: [ACK 3-14(a)172.26.0.3-1<mailto:3-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 15(72) INFO: <script>: [INVITE 4-14(a)172.26.0.3-1<mailto:4-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 15(72) CRITICAL: <script>: [INVITE 4-14(a)172.26.0.3-1<mailto:4-14@172.26.0.3-1>] tm:local-response replied locally 16(73) INFO: <script>: [ACK 4-14(a)172.26.0.3-1<mailto:4-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 9(66) INFO: <script>: [INVITE 5-14(a)172.26.0.3-1<mailto:5-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 10(67) INFO: <script>: [ACK 5-14(a)172.26.0.3-1<mailto:5-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) INFO: <script>: [INVITE 6-14(a)172.26.0.3-1<mailto:6-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 12(69) INFO: <script>: [ACK 6-14(a)172.26.0.3-1<mailto:6-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 13(70) INFO: <script>: [INVITE 7-14(a)172.26.0.3-1<mailto:7-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 14(71) INFO: <script>: [ACK 7-14(a)172.26.0.3-1<mailto:7-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 15(72) INFO: <script>: [INVITE 8-14(a)172.26.0.3-1<mailto:8-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 16(73) INFO: <script>: [ACK 8-14(a)172.26.0.3-1<mailto:8-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 9(66) INFO: <script>: [INVITE 9-14(a)172.26.0.3-1<mailto:9-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 10(67) INFO: <script>: [ACK 9-14(a)172.26.0.3-1<mailto:9-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) INFO: <script>: [INVITE 10-14(a)172.26.0.3-1<mailto:10-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 12(69) INFO: <script>: [ACK 10-14(a)172.26.0.3-1<mailto:10-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] Kaufman

2 2

Random number
by Ali Taher 07 Jul '23

07 Jul '23

Hello, As per Kamailio documentation, $RANDOM returns a random value from the [0 - 2^31) range. But when testing it it's always returning a random number of 9 or 10 digits. I'm not sure if it's always the case or if it can also returns numbers with 1 or 2 digits as well. Another question, how can I force it to return a number of specific digits starting with certain prefix. Regards,

2 1

Finding a way to gracefully restart kamailio with dialog module enabled and DMQ sync
by Benoît Panizzon 07 Jul '23

07 Jul '23

Hi Gang We are still having massive issues on how to safely reload kamailio after config changes when using the dialog module and DMQ. If there are active dialogues, kamailio corrupts them on a restart even when using MySQL as dialog backend. As we use two core nodes for redundancy, I am looking for a way to gracefully restart kamailio. I am considering adding some key in a hash table or anything else I can reload on runtime to indicate to kamailio not to accept any new calls (effectively rejecting Invites without To-Tag with 503 causing the registrar or IC peer to hopefully resend the invite to the other node). Then wait, until no more dialogues are active, so kamailio can safely be restarted. My Issue now: How can I find out, one specific node does not have any active dialogues? 'kamcmd dlg.stats_active' returns the count of all DMQ synced nodes, not of the local one. And suggestions or any other ideas how I can 'reload' the kamailio config without disrupting active dialogues? My last resort would be to look into the database: modparam("dialog", "h_id_start", -1) # Use server_id modparam("dialog", "h_id_step", 2) So odd/even H_ID should tell me the number per node. But I see a lot of orphan dialogues hanging around in the database not being cleaned so I guess that will not be reliable at all. Yes, I know I will get the question: 'Why do you need to restart kamailio that often'. We have started production on our kamailio based TSP platform. And of course, despite a LOT of testing beforehand, there is always some issue that pops up. At the moment, I have to implement a config change about once or twice a week to fix some new minor issues. I hope, somewhen in the future we will hopefully have a stable config which will last for several months, but at the moment this is the situation. -- 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 ______________________________________________________

3 4

Randomize calling number
by Ali Taher 06 Jul '23

06 Jul '23

Hello, What is the best way to change the calling number to a random number (based on specific pattern, like number of digits for example) in an invite packet without using a database. So the scenario is : * receive an invite packet from certain source * change the calling number * send back the invite packet including the new calling number to the original source. Regards, Ali Taher

3 7

302 Handling issue in failure route
by Devang Dhandhalya 05 Jul '23

05 Jul '23

Hello All I am handling 302 response in the failure route and when receiving 302 response in kamailio, it's not going into the failure route , kamailio just executing the onreply route when 302 response are received. A few days ago the same code with failure route worked but now it does not. i dont know why kamailio is not executing a failure route from where we can redirect calls to another server. code snippet route[RELAY]{ t_on_reply("MANAGE_REPLY"); t_on_failure("MANAGE_FAILURE"); t_on_branch("MANAGE_BRANCH"); if (!t_relay()) { sl_reply_error(); } exit; } failure_route[MANAGE_FAILURE] { if (t_is_canceled()) { exit; } if (t_check_status("302")){ get_redirects("*"); $ru= $T_rpl($sel(contact.uri)); route(RELAY); } } kamailio version : 5.6.4 Please suggest if I am doing anything wrong. -- Regards, *Devang Dhandhalya* -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

3 3

SL absorbed ACK is counted as dropped by core.drop_requests
by Kaufman 03 Jul '23

03 Jul '23

Just checking to see if this is the designed behavior. The SL module will attempt to match ACKs for stateless replies and handle them (absorb them?). The question I have is that it looks as though this ACK gets counted as dropped by the core.drop_requests from the KEX module. Tested using this config: #!KAMAILIO loadmodule "pv" loadmodule "sl" loadmodule "xlog" loadmodule "kex" loadmodule "corex" loadmodule "ctl" modparam("sl", "bind_tm", 0) route { xinfo("[$ci] $rm Request. Src:[$si:$sp] RURI:[$ru] To:[$tu] From:[$fu]\n"); sl_send_reply("404", "Not Found"); } event_route[sl:filtered-ack] { xnotice("sl:filtered-ack ACK [$ci] to local reply absorbed\n"); } Then validate by kamcmd stats.fetch core:drop_requests Is this the designed and "correct" behavior? Kaufman

3 4

Kamailio v5.7.1 Released
by Daniel-Constantin Mierla 28 Jun '23

28 Jun '23

Hello, Kamailio SIP Server v5.7.1 stable release is out. This is a maintenance release of the latest stable branch, 5.7, that includes fixes since the release of v5.7.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.7.x. Deployments running previous v5.7.x versions are strongly recommended to be upgraded to v5.7.1. For more details about version 5.7.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/06/kamailio-v5-7-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 0

Forward Registration
by nutxase 28 Jun '23

28 Jun '23

Hi All I have setup kamailio using websockets(wss) i am trying to forward any registration that comes to kamailio to go to asterisk, so in theory kamailio is a registration proxy i have set rewritehostport("xxx.xxx.xxx[:5080](http://node3.sipalto.com:5080)"); the registration forwards fine but the contact on asterisk side shows as sip:xxx:kamailioip.xxxx.invalid so therefore asterisk sees the sip peer as offline what am i missing :( Sent with [Proton Mail](https://proton.me/) secure email.

1 0

Releasing v5.7.1
by Daniel-Constantin Mierla 28 Jun '23

28 Jun '23

Hello, I am considering to release Kamailio v5.7.1 (out of branch 5.7) this week (likely on Wednesday or Thursday, Jun 28/29, 2023). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 1

Matching the From Username in LCR rule table
by harneet singh 27 Jun '23

27 Jun '23

Hi Experts, We wished to used the LCR Module to be able to select the Gateway(s) to send the calls to based on the From(Caller) Username. Based on the LCR Documentation, the usage of other fields like request URI or prefix etc is pretty clear. But for the From Usename I am having certain trouble understanding the same. It refers to some mtree. Excerpt below: "A gateway matches a request if user part of Request-URI matches "prefix", caller URI matches "from_uri" pattern,* caller URI userpart matches mtree with "mt_value"*, and callee URI matches "request_uri" pattern in a tuple that is associated with the gateway." Can someone explain/ share a sample lcr_rule table entries for the From Username that can be matched against the incoming sip message for gw selection? Do we need to manually create an mtree by the name "*lcr*". Asking based on the below section in LCR documentation? Any pointers are highly appreciated. 3.35. mtree (string) Name of mtree to which load_gws() matches caller URI userpart. *Default value is "lcr".* Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

uac_replace() and uac_restore debug help
by Duarte Rocha 24 Jun '23

24 Jun '23

Hello, I'm currently experiencing some odd behaviours when using these functions and I need some help debugging to find the root of the issue. I receive a call from a client and do some changes to the To and From header using auto mode with password. Encrypted info goes on the Record-Route header parameters (vsf\vst) normally. 1 - On subsequent requests sent by the originating client, domains on To and From header are different from the ones sent in the first INVITE. In this scenario, somehow the automatic modifying has errors on the end result. Can the different domains affect the end result of the automatic modifying or only the vsf\vst parameters and password are needed to the auto replace\restore? 2 - How can I decrypt the info on vsf and vst parameters in order to verify the info sent and the encryption? Cheers, Duarte Rocha

2 1

uac_restore behaviour question
by Duarte Rocha 22 Jun '23

22 Jun '23

Hello, I have some questions regarding uac_replace methods. When I receive the first INVITE from someone I change To and From using uac_replace_to() and uac_replace_from(). I do this only on first INVITES. In order to restore them I use the "auto" so the changes are restored automatically in replies or requests sent to the call originator.. In the case of subsequent requests from the originator kamailio still changes To and From without me using uac_replace functions. Is this caused by the auto restore? Does it work for both sides and is this is the intended behaviour? Cheers

1 1

How to handle 302 redirects
by Trey Ormsbee 22 Jun '23

22 Jun '23

Hello, Im having a hard time figuring out how to handle a 302 reidrect, the uac_redirect modules shows a simple configuration. However for me, what it is not doing is changing the 302 back to invite. It is sending the 302 as is on. if(!t_check_status("3[0-9][0-9]")) { exit; } get_redirects("3:1"); t_relay(); This code just relays the 302 for me. I should add I am using this with the DISPATCHER module so perhaps that has something to do with my issue. Setup is this, kamailio is sitting between to sip servers, so the flow goes like this, sip_server_a -> kamailio -> sip_server_b. sip_server_b only responds with 302 redirects, sip_server_a does not handle 302’s at all. Kamailio will only get invites from sip_server_a, and the redirects from sip_server_b will only have one contact. How can I get kamailio to reply to sip_server_a’s invite with the updated INVITE? My config is a mesh of the dispatcher example and uac_redirect example with this specific section handling the redirect: # Sample failure route failure_route[RTF_DISPATCH] { xlog("L_NOTICE", "RTF_DISPATCH: "); if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { if(ds_next_dst()) { t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } if (t_check_status("302")) { xlog("L_NOTICE", "RTF_DISPATCH: 302 "); if (!get_redirects("1:1")) { xlog("L_NOTICE", "RTF_DISPATCH: failed to get_redirects "); t_reply("480", "Temporarily Unavailable"); exit; } xlog("L_NOTICE", "RTF_DISPATCH: got redirects "); t_relay(“sip_server_a”,”5060”); } } Any ideas what I am doing wrong is this supported? Im expecting once I relay this message that it should be an INVITE not a 302 redirect. I cant find any examples of anyone else really doing this.

3 3

Missing posops module from 5.7 debian repo
by Patrick Karton 20 Jun '23

20 Jun '23

hello , i have installed kamailio 5.7 from debian repo http://deb.kamailio.org/kamailio57 bullseye main but i dont find the posops module in the directory modules. what is the exactly package where i can find it. Thanks.

2 5

KEMI
by iliusha.md＠gmail.com 19 Jun '23

19 Jun '23

Hello, I have the following statement: if KSR.is_method("INVITE") then KSR.log("info", "method not allowed " .. KSR.kx.get_method() .."\n"); KSR.x.exit(); end For some reason, it falls into this condition no matter which method I use, I tried OPTIONS, NOTIFY etc. log file: <core> [core/kemi.c:152]: sr_kemi_core_log(): method not allowed OPTIONS the same with this check: if KSR.is_method_in("I") then KSR.log("info", "method not allowed " .. KSR.kx.get_method() .."\n"); KSR.x.exit(); end this is the lua modparam settings: # ---- lua params ---- modparam("app_lua", "load", "/usr/local/etc/kamailio/main.lua") modparam("app_lua", "reload", 1) modparam("app_lua", "log_mode", 1) cfgengine "lua" version: kamailio 5.7.0 (x86_64/linux) 1c23c2 Any idea what I'm doing wrong?

2 1

Kamailio failover in aws/azure environment
by M Arqum CH 17 Jun '23

17 Jun '23

Hi members, I am setting up kamailio as loadbalcer for asterisk server farm with active-backup conf in Azure cloud using azure loadbalcer, for incoming it works fine external incoming traffic with nated external IP, can any one guide how to do active-backup configuration for internal traffic, as asterisk servers are running on local network. Thanks and regards Arqum

2 1

TLS errors
by nutxase 16 Jun '23

16 Jun '23

Hey All I have been setting up TLS and websocket for kamailio but i keep getting these errors in the log please can someone help me Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: tls [tls_util.h:51]: tls_err_ret(): TLS accept:error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher (sni: [sip.domain.com](http://sip.sipalto.com)) Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: tls [tls_server.c:1333]: tls_h_read_f(): src addr: 1.2.3.4.5:57265 Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: tls [tls_server.c:1336]: tls_h_read_f(): dst addr: 5.4.3.2.1:8089Jun 14 20:51:57 so-sbc-02 /usr/sbin/kamailio[25490]: ERROR: <core> [core/tcp_read.c:1478]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f3c8fc16720 r: 0x7f3c8fc16848 (-1) my config is pretty standard so i am not sure what i am missing using letsencrypt certs #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "tls_method", "TLSv1.2+") modparam("tls", "certificate", "/etc/kamailio/tls/cert.pem") modparam("tls", "private_key", "/etc/kamailio/tls/ckey.pem") modparam("tls", "ca_list", "/etc/kamailio/tls/fullchain.pem")#!endif Sent with [Proton Mail](https://proton.me/) secure email.

3 5

impossible to modify $tU twice
by David VILLAUME 15 Jun '23

15 Jun '23

Hello, I’m in a scenario where i would apply different modification to $tU to User with KEMI, but I can’t achieve it. I managed to reproduce it with legacy config : Scenario 1 (both values concatenates): route[dbg] { $tU ="aaa"; $tU ="bbb"; } To: sip:aaabbb@5.5.5.5 Scenario 1 (both values concatenates and @ disapears): route[dbg] { $tU ="aaa"; $tU=$null; $tU ="bbb"; } To: sip:aaabbb5.5.5.5 --->without @ I tried different combination with [*] as for avps without success, does anyone have an idea about how to perform it ? Regards, David

3 2

Cannot achieve rtpengine HA
by Arsenijs Kabihno 13 Jun '23

13 Jun '23

Hello, We are trying to achieve rtpengine HA solely with kamailio and rtpengine module. In the following example call goes to rtpengine node 10.5.0.183:22222 and then we stop rtpengine service on this node to simulate failure. Client is triggering re-INVITE, but, apparently, kamailio sticks to initially selected rtpengine, producing the following errors: Jun 12 06:59:48 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) INFO: {2 2 INVITE jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: <null>, method:INVITE, status:200, extra_id: z9hG4bK55018600, rtpengine_answer: replace-origin replace-session-connection SIP-source-address direction=priv1 direction=pub1 SIP-source-address via-branch=extra rtcp-mux-offer generate-mid DTLS=passive SDES-off ICE=force RTP/SAVPF Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) NOTICE: {2 2 INVITE jdl9kq6fv51jcv1agk2e} acc [acc.c:287]: acc_log_request(): ACC: transaction answered: timestamp=1686553189;method=INVITE;from_tag=fcn109nfe9;to_tag=01284cc8-bc58-4104-9629-8e6bb827d97f;call_id=jdl9kq6fv51jcv1agk2e;code=200;reason=OK;src_user=90362;src_domain=10.181.0.1;src_ip=10.5.0.145;dst_ouser=123;dst_user=123;dst_domain=10.181.0.1 Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 31(37) INFO: {2 2 INVITE jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: <null>, method:INVITE, status:200, extra_id: z9hG4bK55018600, rtpengine_answer: replace-origin replace-session-connection SIP-source-address direction=priv1 direction=pub1 SIP-source-address via-branch=extra rtcp-mux-offer generate-mid DTLS=passive SDES-off ICE=force RTP/SAVPF Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 51(57) INFO: {1 2 ACK jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: sip:10.5.2.192:5060, method:ACK, status:<null>, extra_id: <null>, rtpengine_offer: replace-origin replace-session-connection SIP-source-address direction=pub1 direction=priv1 SIP-source-address rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP Jun 12 06:59:49 ap07stvp.xxxxxxx.xxx docker[9373]: 51(57) INFO: {1 2 ACK jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: sip:10.5.2.192:5060, method:ACK, status:<null>, extra_id: <null>, rtpengine_offer: replace-origin replace-session-connection SIP-source-address direction=pub1 direction=priv1 SIP-source-address rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) INFO: {2 3 INVITE jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: <null>, method:INVITE, status:200, extra_id: z9hG4bK20888040, rtpengine_answer: replace-origin replace-session-connection SIP-source-address direction=priv1 direction=pub1 SIP-source-address via-branch=extra rtcp-mux-offer generate-mid DTLS=passive SDES-off ICE=force RTP/SAVPF Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) ERROR: {2 3 INVITE jdl9kq6fv51jcv1agk2e} rtpengine [rtpengine.c:3070]: send_rtpp_command(): can't send command "offer" to RTPEngine <udp:10.5.0.183:22222> Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 54(60) INFO: {1 3 ACK jdl9kq6fv51jcv1agk2e} <script>: RTPENGINE branch_id:0 ruri: sip:10.5.2.192:5060, method:ACK, status:<null>, extra_id: <null>, rtpengine_offer: replace-origin replace-session-connection SIP-source-address direction=pub1 direction=priv1 SIP-source-address rtcp-mux-demux DTLS=off SDES-off ICE=remove RTP/AVP Jun 12 07:01:26 ap07stvp.xxxxxxx.xxx docker[9373]: 54(60) ERROR: {1 3 ACK jdl9kq6fv51jcv1agk2e} rtpengine [rtpengine.c:2706]: rtpp_function_call(): no available proxies We also found Daniel answer on similar issue here: https://github.com/kamailio/kamailio/issues/2713#issuecomment-823138302 Please advise how it can be solved. Kind regards, Arsenijs

4 5

Carrierroute Test API?
by sr.maillists＠gmail.com 13 Jun '23

13 Jun '23

Hi List Does someone know a function to test a number against the carrierroute module, to see which route it picked? My Idea: We have multiple Kamailio-Proxies and I would like to test a number against all hosts to see where it will be routed, without performing testcalls. Regards Stefan

2 1

Kamailio/MySQL Module compatibility with MySQL 8.0+
by Pedro Ulhoa 13 Jun '23

13 Jun '23

Hello friends. I didn't find about it in the documentation, but I will need to update my database version to MySQL 8.0.32 and I'm using Kamailio version 5.4. I did some quick tests, and I only needed to adjust the user due to the authentication mode, and with that, apparently I had no problems. I would like to know if you are using Kamailio with the latest version of MySQL, if you have had any problems in production, and if it really is safe to upgrade. -- Aviso Legal: Este documento pode conter informações confidenciais e/ou privilegiadas. Se você não for o destinatário ou a pessoa autorizada a receber este documento, não deve usar, copiar ou divulgar as informações nele contidas ou tomar qualquer ação baseada nessas informações. Disclaimer: The information contained in this document may be privileged and confidential and protected from disclosure. If the reader of this document is not the intended recipient, or an employee agent responsible for delivering this document to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

3 2

What is the best way to return a lot of data via JSONRPC and jansson?
by Benoit Panizzon 12 Jun '23

12 Jun '23

Hi Team To offer some diagnose functionality I created an API that returns the location list via JSONRPC But this creates huge variables. Jun 12 09:43:32 prod-cpereg02 kamailio[2174548]: ERROR: <core> [core/pvapi.c:1491]: pv_printf_mode(): no more space for spec value - printed:0 token:8599 buffer:8192 Jun 12 09:43:32 prod-cpereg02 kamailio[2174548]: ERROR: <core> [core/pvapi.c:1503]: pv_printf_mode(): buffer overflow -- increase the buffer size... Already hitting the default limit and not sure this is the right way to go as we will end up with thousands of registrations. What is the best way to return larger ammounts of data out of kamailio? Avoid using the JSONRPC and access the database externally? 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 1

Dialog DMQ state after restart
by Calvin E. 10 Jun '23

10 Jun '23

Does the dialog module do anything similar to the htable dmq_init_sync behavior? The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover? -Calvin E.

5 7

Kamailio - could not allocate private memory from pkg pool
by Muhammad Danish Moosa 09 Jun '23

09 Jun '23

Hi, I have been kamailio services working for few months and suddenly I got this error. ERROR: <core> [core/kemi.c:2923]: sr_kemi_pv_sets(): unable to set pv [$rp] ERROR: <core> [core/pvapi.c:352]: pv_cache_add(): could not allocate private memory from pkg pool ERROR: <core> [core/kemi.c:2914]: sr_kemi_pv_sets(): cannot get pv spec for [$dlg_var(BW0930526150606231188928742(a)10.10.16.100)] ERROR: <core> [core/data_lump.c:544]: dup_lump_list_r(): could not allocate private memory from pkg pool ERROR: <core> [core/data_lump.c:582]: dup_lump_list_r(): out of mem ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches ERROR: <core> [core/msg_translator.c:2501]: build_res_buf_from_sip_req(): could not allocate private memory from pkg pool ERROR: sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) ERROR: <core> [core/msg_translator.c:2501]: build_res_buf_from_sip_req(): could not allocate private memory from pkg pool ERROR: tm [t_reply.c:475]: _reply_light(): response building failed WARNING: tm [t_lookup.c:1499]: t_unref(): generation of a delayed stateful reply failed Issue was fixed after the restart of kamailio. -- Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

4 10

Kamailio World
by Fred Posner 05 Jun '23

05 Jun '23

1 0

Invalid Links
by Brandon Armstead 04 Jun '23

04 Jun '23

https://www.kamailio.org/w/kamailio-v5-7-0-release-notes/ article references math module and tls_wolfssl, 2 of the 4 modules mentioned link back to 5.6 (these two) instead of 5.7 resulting in a 404. Respective links should be as follows: math - https://www.kamailio.org/docs/modules/5.7.x/modules/math.html tls_wolfssl - https://www.kamailio.org/docs/modules/5.7.x/modules/tls_wolfssl.html Can we get a correction in the article on WP? Thanks - Brandon

1 0

header from failure_route
by David Villasmil 04 Jun '23

04 Jun '23

Hello guys, so i'm doing on a failure_route: $var(xgws_in_reply) = $T_rpl($hdr(X-GWs)); which when it’s present on the reply is cool… but when there is NO REPLY, then kamailio sets it to “0”… anyway over this? i only want to know whether it is present on the reply Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Missing transformations for {val.*}?
by Kaufman 03 Jun '23

03 Jun '23

Beginning in 5.6 new {val.*} transformations are documented as being exported by the pv module, however if I try using it Kamailio fails to start. Wondering if maybe it's actually imported by another module and the documentation is wrong or something like that? This configuration in 5.6.3 on Alpine Linux installed from packages: #!KAMAILIO loadmodule "pv" loadmodule "xlog" request_route { xlog("Null val: $(avp(nothing){val.ne})\n"); exit; } Fails to start with the following: 0(114) INFO: <core> [main.c:3055]: main(): processes (at least): 29 - shm size: 67108864 - pkg size: 8388608 0(114) ERROR: <core> [core/pvapi.c:1774]: tr_lookup(): unknown transformation: [val] in [{val.ne}] 0(114) ERROR: <core> [core/pvapi.c:1799]: tr_lookup(): error parsing [{val.ne}] 0(114) ERROR: <core> [core/pvapi.c:1106]: pv_parse_spec2(): bad tr in pvar name "avp" 0(114) ERROR: <core> [core/pvapi.c:1131]: pv_parse_spec2(): invalid parsing in [$(avp(nothing){val.ne})] at (4) 0(114) ERROR: xlog [xlog.c:551]: xdbg_fixup_helper(): wrong format[Null val: $(avp(nothing){val.ne})] 0(114) ERROR: <core> [core/route.c:1169]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:7 Kaufman Sr. VoIP Engineer - BCM One +1.612.735.9309 bkaufman(a)bcmone.com<mailto:bkaufman@bcmone.com> 24 hour client support: +1.855.639.6300 [https://www.bcmone.com/files/bcmone-logo.png]<https://www.bcmone.com/> [https://www.bcmone.com/files/twitter-icon-circle.png] <https://www.facebook.com/bcmonenyc/> [https://www.bcmone.com/files/twitter-icon-circle.png] <https://twitter.com/bcm_one/> [https://www.bcmone.com/files/linkedin-icon-circle.png] <https://www.linkedin.com/company/business-communications-management/> NOTE: This e-mail and any attachments are from BCM One, Inc. and are intended solely for the use and review of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail (and any attachments) from your computer and do not copy or disclose it to anyone else.

2 1

custom mid registrar using kamailio.
by Yuriy Nasida 01 Jun '23

01 Jun '23

Hello, https://lists.kamailio.org/pipermail/sr-users/2020-October/110792.html I read this thread very carefully and I think I managed to implement all the steps described by Daniel. Thank you so much for the detailed description. But it looks like I'm stuck on the last step. I can't delete records from htable when an incoming call cannot reach the registered device (e.g., no more internet access, power off at the device). I try to do this from failure route but looks like i kamailio has not access to htable from it. failure_route[INTERNAL_TO_EXTERNAL_FAILURE] { if (t_check_status("408")) { xlog("L_WARN", "$ci|log| hello \n"); xlog("L_WARN", "$ci|log| mid reg token - $sht(mid_reg_token=>$fU::$si::$sp) \n"); } } I do not see xlog message with mid reg token but i see 'hello'. Yes, htable record exists in case i check using: kamcmd htable.dump mid_reg_token Also I need a way to remove registration at the registrar (Freeswitch in my case). This means I need to send api request from kamailio or just run some script that will do this. What is the best way ? module exec ? Please advice, Thanks

2 3

Kamailio and MS Teams side by side present staus und chat function
by Hans-Jürgen Brand 31 May '23

31 May '23

2 1

Is Min-SE check broken?
by harneet singh 31 May '23

31 May '23

Hi All, I am facing an issue in understanding how the min_se should be working in kamailio. As per the SST documentation, it seems like if the min_se is configured as 500, then any value of Session-Expires OR MIN-SE if lower than 500, can be responded to by a 422. However, I strangely see the reverse happening. To investigate further, I looked in to the ki_sst_check_min() code in the master, and these seems like a potential issue. Ref Code: Inside ki_sst_check_min(), there is an if condition like below: if (sst_min_se < MIN(minse, se.interval)) { However, shouldn't it be the other way around? ie if (sst_min_se > MIN(minse, se.interval)) { because we need to send 422 if the received value(in INVITE etc) is smaller than the sst configure min_se value? I also found a different documentation, at https://git.sgu.ru/oldssu/ex-opensips/blob/cb9df8d59dbb254a9d862569fd5d11f6… where the check is as below? if (sst_min_se > MIN(minse, se.interval)) { Can someone confirm if this is broken, or my understanding is incorrect? Regards, Harneet -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

http_client using JWT?
by Benoît Panizzon 31 May '23

31 May '23

Hi The http_client module support the somehow old fashioned way to submit credentials as part of the URL. Our 'held' server developer would love to use either JWT or a Bearer Token in the Auth-Header or a 'cookie-jar' to authenticate the requests. Is this somehow possible? -- 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 ______________________________________________________

3 2

Knowing about the uac module with primary and secondary proxy setting
by MUSLIH K 31 May '23

31 May '23

Hi, *sip_provider_proxy1[* uac module-register] ---> *kamailio* [dispatcher Module] ----> *Asterisk1* ----> *Asterisk 2* in my configuration kamailio register to the sip provider using *uac module*, sip information are stored in database (uacreg). when a incoming call(INVITE) come to kamailio it will dispatch call to Asterisk using* "dispatcher module".* Here i have couple of questions 1. If my SIP provider has a secondary proxy as a failover server (sip_provider_proxy2), can I configure Kamailio with the uac module to use the secondary proxy if the primary proxy fails? 2. Since my application is inbound-only, registration failure is only identified when the registration expires (3600 seconds = 1 hour). Can I use the dispatcher module to select the SIP proxy and switch the registration to the secondary proxy if the primary proxy is not reachable (using OPTIONS)?

2 2

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