sr-users

sr-users@lists.kamailio.org

4 participants
37456 discussions

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

Jump to page:

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