- sr-users - kamailio.org

Re: [SR-Users] Error in db_mysql while using presence
by Henning Westerholt 10 Jan '19

10 Jan '19

Am Mittwoch, 9. Januar 2019, 09:47:07 CET schrieb Ravindrakumar Bhatt: > I tried on command line with LOCK TABLES watchers write; and it works > fine. also i am usinf root@localhost with all permissions still same errors > show continuously. please tell if any more details are required for same. > Errors: Hello Ravindrakumar, I would suggest then to enable mysql query logging and have a look to the actual query that is executed from the module and match to the errors below. Please keep the sr-users list in CC. Best regards, Henning > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} presence > [subscribe.c:2827]: get_db_subs_auth(): while querying watchers table > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} presence > [subscribe.c:1217]: handle_subscribe(): getting subscription status from > watchers table > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'active_watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [notify.c:1370]: publ_notify_notifier(): Can't query db > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [publish.c:178]: msg_presentity_clean(): Updating watcher records > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'active_watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [notify.c:1370]: publ_notify_notifier(): Can't query db > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [publish.c:178]: msg_presentity_clean(): Updating watcher records > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'active_watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [notify.c:1370]: publ_notify_notifier(): Can't query db > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [publish.c:178]: msg_presentity_clean(): Updating watcher records > > On Wed, Jan 9, 2019 at 1:55 AM Henning Westerholt <hw(a)kamailio.org> wrote: > > Am Dienstag, 8. Januar 2019, 14:57:21 CET schrieb Ravindrakumar Bhatt: > > > I am using latest kamailio stable version. i have used it for presenece > > > > and > > > > > BLF. i am facing issue in presence related method when i am setting > > > sub_db_mode to any db related mode like 3. > > > > Hello Ravindrakumar, > > > > the presence module uses a database LOCK TABLE command and this fails. Can > > you > > check if the database user that is used from Kamailio has the appropriate > > permissions to issue this command on the database? You can try e.g. with > > mysql > > command line client. > > > > > Version : > > > version: kamailio 5.2.0 (x86_64/linux) 535e13 > > > flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, > > > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, > > > Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, > > > FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, > > > USE_DST_BLACKLIST, HAVE_RESOLV_RES > > > ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, > > > BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB > > > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > > > id: 535e13 > > > compiled on 06:32:22 Jan 8 2019 with gcc 4.8.5 > > > > > > Kamailio.cfg setup: > > > modparam("presence|presence_xml", "db_url", DBURL) > > > modparam("presence", "server_address", "sip:XX.XX.XX.XX:5050") > > > modparam("presence", "send_fast_notify", 0) > > > modparam("presence", "db_update_period", 20) > > > modparam("presence", "clean_period", 40) > > > modparam("presence", "subs_db_mode", 0) > > > modparam("presence", "fetch_rows", 1000) > > > > > > # ----- presence_xml params ----- > > > #modparam("presence_xml", "db_url", DBURL) > > > modparam("presence_xml", "force_active", 1) > > > > > > # ----- pua params ----- > > > modparam("pua", "db_url", DBURL) > > > modparam("pua", "db_mode", 2) > > > modparam("pua", "update_period", 60) > > > modparam("pua", "dlginfo_increase_version", 0) > > > modparam("pua", "reginfo_increase_version", 0) > > > modparam("pua", "check_remote_contact", 1) > > > modparam("pua", "fetch_rows", 1000) > > > > > > # ----- pua_dialoginfo params ----- > > > modparam("pua_dialoginfo", "include_callid", 1) > > > modparam("pua_dialoginfo", "send_publish_flag", FLT_DLGINFO) > > > modparam("pua_dialoginfo", "caller_confirmed", 0) > > > modparam("pua_dialoginfo", "include_tags", 1) > > > modparam("pua_dialoginfo", "override_lifetime", 124) > > > > > > # ----- dialog params ----- > > > modparam("dialog", "db_url", DBURL) > > > modparam("dialog", "enable_stats", 1) > > > modparam("dialog", "db_mode", 1) > > > modparam("dialog", "dlg_flag", FLT_DLG) > > > modparam("presence_dialoginfo", "force_single_dialog", 0) > > > Error: > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: db_mysql > > > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > > > 'active_watchers' was not locked with LOCK TABLES (1100) > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: <core> > > > [db_query.c:132]: db_do_query_internal(): error while submitting query > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence > > > [notify.c:1369]: publ_notify_notifier(): Can't query db > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence > > > [presentity.c:1152]: update_presentity(): updating watcher records > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: db_mysql > > > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > > > 'watchers' was not locked with LOCK TABLES (1100) > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: <core> > > > [db_query.c:132]: db_do_query_internal(): error while submitting query > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: presence > > > [subscribe.c:2827]: get_db_subs_auth(): while querying watchers table > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: presence > > > [subscribe.c:1217]: handle_subscribe(): getting subscription status from > > > watchers table > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence > > > [publish.c:499]: ki_handle_publish_uri(): when updating presentity > > > > > > I am currently using presence with memory only db_mode but for > > > > persistence > > > > > i would like to use db_only mode which is not possible due to this > > > issue. > > > Any idea or suggetions for this issue. > > > > Best regards, > > > > Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment

3 3

Dispatcher attributes
by Jason.Park 10 Jan '19

10 Jan '19

Hi. When using the attributes feature of the dispatcher module, is it possible to directly access/address an individual attribute directly? For example, if I use the following dispatcher text file: -- # line format # setid(int) destination(sip uri) flags(int,opt) priority(int,opt) attributes(str,opt) 1234 sip:10.10.10.10:5060;transport=tcp 0 0 attr1=red;attr2=blue -- And this config snippet, I was hoping to be able to access the attribute with a variable. -- modparam("dispatcher", "attrs_pvname", "$vxavp(ds_attrs)") if(ds_is_from_list(1234,1)) { x_log(“L_NOTICE”,”attr1: $xavp(ds_attrs=>attr1)\n”); } -- Jason Park | Lead Engineer | Voice Services | • Target<http://www.target.com/> | TNC | 816-273-8336

2 5

No Media in SIP Incoming calls
by Prashant Gupta 10 Jan '19

10 Jan '19

Hi, I have the following architecture - SIP provider <-> Kamailio <-> Asterisk servers Currently I have everything setup and incoming calls from Sip are routed to my asterisk server. The issue is however that when I answer the call, there is no media in the call. I have tried connecting with a normal local extension(not SIP,eg 1001) and there is a normal flow of media. When i try to sniff my connection via Wireshark on the asterisk server, there is an outflow of RTP packets but the same RTP traffic does not appear on the Wireshark of my Kamailio server connection. I am not sure if this is an RTP engine issue and how to resolve this. I have - modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:45038") this in my kamailio cfg but I don;t know which port to use here. Any suggestions?

5 5

kamailio rabbitmq segfault
by Sylvain Boily 10 Jan '19

10 Jan '19

Hello, I tried to test the rabbitmq module in kamailio with the debian 9 repo from kamailio.org but there is a segfault when the service is launched. Is there is people also have this issue? /etc/init.d/kamailio restart [....] Restarting kamailio (via systemctl): kamailio.serviceJun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/cfg.y:1659]: yyparse(): loading module rabbitmq.so Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/sr_module.c:575]: load_module(): trying to load </usr/lib/x86_64-linux-gnu/kamailio/modules/rabbitmq.so> Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/kemi.c:1295]: sr_kemi_modules_add(): adding module: rabbitmq Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/cfg.lex:1737]: pp_define(): defining id: MOD_rabbitmq Jun 9 13:02:03 siprouter kernel: [159315.610811] kamailio[13226]: segfault at 7f03b2296287 ip 00007f03b2080ca3 sp 00007fff133285c0 error 7 in librabbitmq.so.4.2.0[7f03b2074000+13000] Jun 9 13:02:03 siprouter /usr/sbin/kamailio[13226]: DEBUG: <core> [core/sr_module.c:988]: init_mod(): rabbitmq Sylvain

4 6

User connection history
by José Antonio Gutiérrez Delgado 10 Jan '19

10 Jan '19

Hi, I would like to know if there is a possibility to see a user's connection history, or at least their last connection. Thank you -- José Antonio Gutiérrez Delgado Responsable técnico Oficina: (+34) 923040031 <http://www.arsoft-company.com/> *Este mensaje se dirige exclusivamente a su destinatario/s y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.* *Antes de imprimir, piensa si es necesario. Cuidar el medioambiente es tarea de todos.*

3 4

"Discarded invalid SRTP packet: authentication failed" warning
by David Cunningham 10 Jan '19

10 Jan '19

Hello, We're having an issue with rtpengine (used by Kamailio) where audio works initially, but then after an apparently random amount of time stop working. We see that when audio stops working rtpengine logs this: Dec 10 09:58:57 hostname rtpengine[376]: WARNING: [Pl1SeGDssOsDNWQdvey4lg.. port 48766]: Discarded invalid SRTP packet: authentication failed It then logs similar messages until the call hangs up. No such messages were logged while audio was working. Searching for this error message suggests that a change in the SSRC can cause the problem, but we don't see any such change in the PCAP. The source IP, port, codec, and SSRC all stay the same, and the Sequence increments as normal. Does anyone have suggestions on where to look next? We can share the PCAP privately if that would help anyone. Thanks for any advice! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

2 3

Re: [SR-Users] [EXT] Re: P-CSCF returns SIP error: 483 Too may hops
by Woscek, Martin W. 09 Jan '19

09 Jan '19

Yes, The DNS NAPTR records are correct. I have all running on single laptop, P:4060, I:5060, S:6060 and all DNS tests verified. I don’t have any traffic other than the P talking to itself until the number hops is exceeded. From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Iman Mohammadi Sent: Wednesday, January 9, 2019 9:49 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [EXT] Re: [SR-Users] P-CSCF returns SIP error: 483 Too may hops Hi Check the Ports in DNS and in configuration files.for example if you set 5060 in configuration of pcscf,set 5060 in dns for pcscf too For Registration REGISTER goes from pcscf to icscf first then icscf gets address of scscf in UAA from HSS,then icscf forwards REGISTER to scscf and ... On Wed, Jan 9, 2019, 18:04 Woscek, Martin W. <mwoscek(a)mitre.org<mailto:mwoscek@mitre.org> wrote: Hi all, I’ve stood up IMS 4.3.4. When I try to register with a boghe IMS client the P-CSCF gets in a loop and a SIP error: 483 Too may hops is returned. I would think the path would b to S-CSCF:6060 which would then check the HSS for user bob. The P-CSCF log attached. I believe Im missing some basic configuration setting here. If there is configuration (test scenario) documentation that I can be pointed to, it’d be appreciated. R, martin _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

P-CSCF returns SIP error: 483 Too may hops
by Woscek, Martin W. 09 Jan '19

09 Jan '19

Hi all, I've stood up IMS 4.3.4. When I try to register with a boghe IMS client the P-CSCF gets in a loop and a SIP error: 483 Too may hops is returned. I would think the path would b to S-CSCF:6060 which would then check the HSS for user bob. The P-CSCF log attached. I believe Im missing some basic configuration setting here. If there is configuration (test scenario) documentation that I can be pointed to, it'd be appreciated. R, martin

2 1

Issue in ACK in WS <-> sip scenario
by Ravindrakumar Bhatt 09 Jan '19

09 Jan '19

Hello, I am using latest stable kamailio version 5.2 . I am getting following error while calling from webrtc client to sip client. Error: Jan 9 07:25:05 client1 /usr/local/sbin/kamailio[15318]: INFO: <script>: ACK rsponse: WebRTC --> WebRTC Jan 9 07:25:05 client1 /usr/local/sbin/kamailio[15318]: WARNING: <core> [core/msg_translator.c:2812]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Jan 9 07:25:05 client1 /usr/local/sbin/kamailio[15318]: ERROR: <core> [core/msg_translator.c:2003]: build_req_buf_from_sip_req(): could not create Via header Jan 9 07:25:05 client1 /usr/local/sbin/kamailio[15318]: ERROR: <core> [core/forward.c:549]: forward_request(): building failed Jan 9 07:25:05 client1 /usr/local/sbin/kamailio[15318]: ERROR: sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) Here it is saying that websocket connection is not found but when i check using netstat connection is in established state. netstat -anp | grep kamailio result : tcp 0 0 XX.XX.XX.XX:3080 0.0.0.0:* LISTEN 15324/kamailio tcp 0 0 XX.XX.XX.XX:3080 0 XX.XX.XX.XX:53632 ESTABLISHED 15298/kamailio 53632 is same port as port mentioned in received field of location table. So what can be the issue ? please provide your feedback on same. -- *Thanks and Regards,* *Ravindrakumar Bhatt* Jr. Software Developer Ecosmob Technologies Ltd Ahmedabad Mo:*+918460692402*

1 1

SIP Express Media Server (aka SEMS)
by Abhijit Dutta 09 Jan '19

09 Jan '19

Hi All, Is the development work for SEMS server still on or stopped? Does it support video? Thanks Abhijit

3 5

Re: [SR-Users] Planning Fosdem 2019
by Dan Christian Bogos 09 Jan '19

09 Jan '19

Hi Daniel, Please count us also for the dinner event (4 people from CGRateS project). Thanks and looking forward to meet you all in Brussels! DanB

1 0

json.parse transformation documentation
by YAS0 CANER 09 Jan '19

09 Jan '19

Hello, i saw a transformation on PUA_JSON module about json.parse transformation. i think it is missing on cookbook transformation. Kind regards ... event_route[xhttp:request] { $var(call-id) = $(rb{json.parse,Call-ID}); if ($(rb{json.parse,Event-Package}) == "dialog") { xlog("L_INFO", "$var(call-id)|log|received $(rb{json.parse,Event -Package}) update for $(rb{json.parse,From})"); pua_json_publish($rb); } } ... https://www.kamailio.org/wiki/cookbooks/devel/transformations cookbooks:devel:transformations [Kamailio SIP Server Wiki]<https://www.kamailio.org/wiki/cookbooks/devel/transformations> Main author: Daniel-Constantin Mierla <miconda (at) gmail.com> Transformation is basically a function that is applied to a pseudo-variable (PV) to get a property of it. The value of PV is not affected at all. Transformations are implemented by various modules, most of them being in pv module.. The transformations are intended to facilitate access to different attributes of PV (like strlen of ... www.kamailio.org

2 2

Kamailio IMS Implementation DNS Problem
by Yağız AYDIN 09 Jan '19

09 Jan '19

Hello, I am trying to implement Kamailio as IMS system. I have followed tutorial linked below: https://www.kamailio.org/wiki/tutorials/ims/installation-howto When I try to configure my DNS, I cannot ping cscf modules on my local network, however when I'm on wireless, I can ping them. Config: kamailio-ims.org.dnszone $ORIGIN kamailio-ims.org. $TTL 1W @ 1D IN SOA localhost. root.localhost. ( 2006101001 ; serial 3H ; refresh 15M ; retry 1W ; expiry 1D ) ; minimum 1D IN NS ns ns 1D IN A 127.0.0.1 pcscf 1D IN A 127.0.0.1 _sip.pcscf 1D SRV 0 0 5060 pcscf _sip._udp.pcscf 1D SRV 0 0 5060 pcscf _sip._tcp.pcscf 1D SRV 0 0 5060 pcscf icscf 1D IN A 127.0.0.1 _sip 1D SRV 0 0 5060 icscf _sip._udp 1D SRV 0 0 5060 icscf _sip._tcp 1D SRV 0 0 5060 icscf kamailio-ims.org. 1D IN A 127.0.0.1 kamailio-ims.org. 1D IN NAPTR 10 50 "s" "SIP+D2U" "" _sip._udp kamailio-ims.org. 1D IN NAPTR 20 50 "s" "SIP+D2T" "" _sip._tcp scscf 1D IN A 127.0.0.1 _sip.scscf 1D SRV 0 0 5060 scscf _sip._udp.scscf 1D SRV 0 0 5060 scscf _sip._tcp.scscf 1D SRV 0 0 5060 scscf hss 1D IN A 127.0.0.1 named.conf.options options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you may need to fix the firewall to allow multiple // ports to talk. See http://www.kb.cert.org/vuls/id/800113 // If your ISP provided one or more IP addresses for stable // nameservers, you probably want to use them as forwarders. // Uncomment the following block, and insert the addresses replacing // the all-0's placeholder. // forwarders { // 127.0.0.1; // }; //======================================================================== // If BIND logs error messages about the root key being expired, // you will need to update your keys. See https://www.isc.org/bind-keys //======================================================================== dnssec-validation auto; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { any; }; }; named.conf.local // // Do any local configuration here // // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; zone "kamailio-ims.org" { type master; file "/etc/bind/kamailio-ims.org.dnszone"; }; dhclient.conf # Configuration file for /sbin/dhclient. # # This is a sample configuration file for dhclient. See dhclient.conf's # man page for more information about the syntax of this file # and a more comprehensive list of the parameters understood by # dhclient. # # Normally, if the DHCP server provides reasonable information and does # not leave anything out (like the domain name, for example), then # few changes must be made to this file, if any. # option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; send host-name = gethostname(); request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers; #send dhcp-client-identifier 1:0:a0:24:ab:fb:9c; #send dhcp-lease-time 3600; #supersede domain-name "fugue.com home.vix.com"; prepend domain-name-servers 127.0.0.1; #require subnet-mask, domain-name-servers; timeout 300; #retry 60; #reboot 10; #select-timeout 5; #initial-interval 2; #script "/sbin/dhclient-script"; #media "-link0 -link1 -link2", "link0 link1"; #reject 192.33.137.209; #alias { # interface "eth0"; # fixed-address 192.5.5.213; # option subnet-mask 255.255.255.255; #} #lease { # interface "eth0"; # fixed-address 192.33.137.200; # medium "link0 link1"; # option host-name "andare.swiftmedia.com"; # option subnet-mask 255.255.255.0; # option broadcast-address 192.33.137.255; # option routers 192.33.137.250; # option domain-name-servers 127.0.0.1; # renew 2 2000/1/12 00:00:01; # rebind 2 2000/1/12 00:00:01; # expire 2 2000/1/12 00:00:01; #} Thanks for helps, Yağız --

2 2

kamailio 5.0 questions
by Lv, Victor (NSB - CN/Qingdao) 09 Jan '19

09 Jan '19

Hi All, I am using kamailio 5.0, one question is: is there any one make it works to send rx_aar for origin calls? That's when we receive the INVITE message and send out rx_aar? Below link not work when receive INVITE message, I need to send AAR when we receive INVITE for origin and send AAR when we receive 200 OK for term? Rx_AAR("MT_aar_reply", "origin","",2); >From code, we got below comments. //we dont apply QoS if its not a reply to an INVITE! or UPDATE or PRACK! Thanks, Victor

4 10

Error in db_mysql while using presence
by Ravindrakumar Bhatt 08 Jan '19

08 Jan '19

Hello, I am using latest kamailio stable version. i have used it for presenece and BLF. i am facing issue in presence related method when i am setting sub_db_mode to any db related mode like 3. Version : version: kamailio 5.2.0 (x86_64/linux) 535e13 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 535e13 compiled on 06:32:22 Jan 8 2019 with gcc 4.8.5 Kamailio.cfg setup: modparam("presence|presence_xml", "db_url", DBURL) modparam("presence", "server_address", "sip:XX.XX.XX.XX:5050") modparam("presence", "send_fast_notify", 0) modparam("presence", "db_update_period", 20) modparam("presence", "clean_period", 40) modparam("presence", "subs_db_mode", 0) modparam("presence", "fetch_rows", 1000) # ----- presence_xml params ----- #modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 2) modparam("pua", "update_period", 60) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 1) modparam("pua", "fetch_rows", 1000) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_DLGINFO) modparam("pua_dialoginfo", "caller_confirmed", 0) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "override_lifetime", 124) # ----- dialog params ----- modparam("dialog", "db_url", DBURL) modparam("dialog", "enable_stats", 1) modparam("dialog", "db_mode", 1) modparam("dialog", "dlg_flag", FLT_DLG) modparam("presence_dialoginfo", "force_single_dialog", 0) Error: Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table 'active_watchers' was not locked with LOCK TABLES (1100) Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence [notify.c:1369]: publ_notify_notifier(): Can't query db Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence [presentity.c:1152]: update_presentity(): updating watcher records Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table 'watchers' was not locked with LOCK TABLES (1100) Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: presence [subscribe.c:2827]: get_db_subs_auth(): while querying watchers table Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: presence [subscribe.c:1217]: handle_subscribe(): getting subscription status from watchers table Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence [publish.c:499]: ki_handle_publish_uri(): when updating presentity I am currently using presence with memory only db_mode but for persistence i would like to use db_only mode which is not possible due to this issue. Any idea or suggetions for this issue. -- *Thanks and Regards,* *Ravindrakumar Bhatt* Jr. Software Developer Ecosmob Technologies Ltd Ahmedabad Mo:*+918460692402*

2 1

TLS Problem OpenSSL 1.1
by Ulrich Landermann 08 Jan '19

08 Jan '19

2 1

Dispatcher with a view
by Duarte Rocha 08 Jan '19

08 Jan '19

Greetings, Is it possible for Dispatcher to use a view for "table_name" instead of a regular table? Best Regards, Duarte Rocha

2 2

Re: [SR-Users] Kamailio 5.1.6 Debian Package -> SEGFAULT
by Floimair Florian 08 Jan '19

08 Jan '19

This is the backtrace of 2 core-dumps i got just recently (both with the same timestamp). Nothing obvious that hits my eyes (at least no NULL pointer). Maybe you can see more in it. Backtrace #1: =========== [New LWP 99122] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fca0d45e996 in t_should_relay_response (Trans=0x7fca067b2a60, new_code=401, branch=0, should_store=0x7ffff47edd44, should_relay=0x7ffff47edd40, cancel_data=0x7ffff47edf30, reply=0x7fca0d8fd020) at t_reply.c:1282 1282 t_reply.c: No such file or directory. (gdb) bt #0 0x00007fca0d45e996 in t_should_relay_response (Trans=0x7fca067b2a60, new_code=401, branch=0, should_store=0x7ffff47edd44, should_relay=0x7ffff47edd40, cancel_data=0x7ffff47edf30, reply=0x7fca0d8fd020) at t_reply.c:1282 #1 0x00007fca0d46317f in relay_reply (t=0x7fca067b2a60, p_msg=0x7fca0d8fd020, branch=0, msg_status=401, cancel_data=0x7ffff47edf30, do_put_on_wait=1) at t_reply.c:1786 #2 0x00007fca0d469154 in reply_received (p_msg=0x7fca0d8fd020) at t_reply.c:2537 #3 0x000055e77686fbe3 in do_forward_reply (msg=0x7fca0d8fd020, mode=0) at core/forward.c:747 #4 0x000055e776871a00 in forward_reply (msg=0x7fca0d8fd020) at core/forward.c:852 #5 0x000055e7768bd4e7 in receive_msg ( buf=0x55e776da0520 <buf> "SIP/2.0 401 Unauthorized\r\nVia: SIP/2.0/UDP 172.17.217.10;rport=5060;received=172.17.217.10;branch=z9hG4bKe4bf.c46a843afa3ff97f5b20df53926515a2.0;i=62\r\nVia: SIP/2.0/TCP 195.225.36.194:1797;rport=40047;"..., len=736, rcv_info=0x7ffff47ee4e0) at core/receive.c:364 #6 0x000055e7767ce4fe in udp_rcv_loop () at core/udp_server.c:554 #7 0x000055e77673a15d in main_loop () at main.c:1619 #8 0x000055e7767421fe in main (argc=13, argv=0x7ffff47eeb98) at main.c:2638 Backtrace #2: =========== [New LWP 99120] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fca0d45e996 in t_should_relay_response (Trans=0x7fca067da3c0, new_code=200, branch=0, should_store=0x7ffff47edd44, should_relay=0x7ffff47edd40, cancel_data=0x7ffff47edf30, reply=0x7fca0d8fd020) at t_reply.c:1282 1282 t_reply.c: No such file or directory. (gdb) bt #0 0x00007fca0d45e996 in t_should_relay_response (Trans=0x7fca067da3c0, new_code=200, branch=0, should_store=0x7ffff47edd44, should_relay=0x7ffff47edd40, cancel_data=0x7ffff47edf30, reply=0x7fca0d8fd020) at t_reply.c:1282 #1 0x00007fca0d46317f in relay_reply (t=0x7fca067da3c0, p_msg=0x7fca0d8fd020, branch=0, msg_status=200, cancel_data=0x7ffff47edf30, do_put_on_wait=1) at t_reply.c:1786 #2 0x00007fca0d469154 in reply_received (p_msg=0x7fca0d8fd020) at t_reply.c:2537 #3 0x000055e77686fbe3 in do_forward_reply (msg=0x7fca0d8fd020, mode=0) at core/forward.c:747 #4 0x000055e776871a00 in forward_reply (msg=0x7fca0d8fd020) at core/forward.c:852 #5 0x000055e7768bd4e7 in receive_msg ( buf=0x55e776da0520 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 172.17.217.10;rport=5060;received=172.17.217.10;branch=z9hG4bK3494.0e37cca5019fe3c95285a3464d0eaa5e.0;i=b3\r\nVia: SIP/2.0/TCP 192.168.0.102:53360;rport=53360;received=9"..., len=638, rcv_info=0x7ffff47ee4e0) at core/receive.c:364 #6 0x000055e7767ce4fe in udp_rcv_loop () at core/udp_server.c:554 #7 0x000055e77673a15d in main_loop () at main.c:1619 #8 0x000055e7767421fe in main (argc=13, argv=0x7ffff47eeb98) at main.c:2638

4 13

nat_uac_test not recognized command in onreply_route
by Andrew Chen 07 Jan '19

07 Jan '19

Hey it's me again. So I'm following the instructions in the Kamailio 5.1.x wiki module page for websocket configuration and it specifically mention to set this block: onreply_route[WS_REPLY] { xlog("L_INFO", "[CSeq $cs] Is in WS_REPLY."); xlog("L_INFO", "[CSeq $cs] Sending $rs $rr to $sel(via[2].host) via $sel(via[2].transport) len: $ml"); xlog("L_INFO", "[CSeq $cs] \n$mb \n"); if(nat_uac_test("64")) { # Do NAT traversal stuff for replies to a WebSocket connection # - even if it is not behind a NAT! # This won't be needed in the future if Kamailio and the # WebSocket client support Outbound and Path. add_contact_alias(); } } When I did this and started up Kamailio, it gave me an error: Jan 3 22:19:43 sjomainkama55 kamailio: ERROR: <core> [core/cfg.y:3309]: yyparse(): cfg. parser: failed to find command nat_uac_test (params 1) I moved that if statement to a route block and I was able to start it up. The wiki page for nathelper module specify this function can be run in onreply_route as well: 5.5. nat_uac_test(flags) Tries to guess if client's request originated behind a nat. The parameter determines what heuristics is used. Meaning of the flags is as follows: - *1* - The “Contact” header field is searched for occurrence of RFC1918 or RFC6598 addresses. - *2* - the "received" test is used: address in the “Via” header is compared against source IP address of signaling - *4* - The Top Most “Via” is searched for occurrence of RFC1918 or RFC6598 addresses - *8* - The SDP is searched for occurrence of RFC1918 or RFC6598 addresses - *16* - Test if the source port is different from the port in the “Via” header - *32* - Test if the source IP address of signaling is a RFC1918 or RFC6598 address - *64* - Test if the source connection of signaling is a WebSocket - *128* - Test if the “Contact” header URI port differs from the source port of the request (Warning: this is might be legal or even intended combination in non NATted scenarios) All flags can be bitwise combined, the test returns true if any of the tests identified a NAT. This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE. is this some known bug in 5.1.x? Thanks -- Andy Chen achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

4 9

Unable to start Kamailio with acc_json
by Joonas Kamailio 07 Jan '19

07 Jan '19

Dear List, I have a problem with initializing acc_json. As soon as I try to load acc_json module, Kamailio fails to start. I get the following messages to log with debug 4 (non-related messages omitted): Jan 7 16:17:42 labkam2 kamailio[51089]: INFO: acc_json [acc_json_mod.c:99]: mod_init(): janson version : 2.9 Jan 7 16:17:43 labkam2 kamailio: ERROR: <core> [core/daemonize.c:303]: daemonize(): Main process exited before writing to pipe Running 'bt full' on coredump tells following: (gdb) bt full #0 strlen () at ../sysdeps/x86_64/strlen.S:106 No locals. #1 0x00007f086d0a69fd in mod_init () at acc_json_mod.c:120 __func__ = "mod_init" #2 0x000055f1699cc6a2 in init_mod (m=0x7f087c0983d0) at core/sr_module.c:897 __func__ = "init_mod" #3 0x000055f1699cca16 in init_modules () at core/sr_module.c:926 t = 0x29ceb62d i = -1 __func__ = "init_modules" #4 0x000055f16989445a in main (argc=3, argv=0x7ffc56d94378) at main.c:2617 cfg_stream = 0x55f16beb0010 c = -1 r = 0 tmp = 0x7f087c9512e7 "__vdso_getcpu" tmp_len = 32764 port = 1457078704 proto = 32520 options = 0x55f169c019f0 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2201341167 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0xf0b0ff <error: Cannot access memory at address 0xf0b0ff> st = {st_dev = 19, st_ino = 306346, st_nlink = 2, st_mode = 16832, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 80, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1543318847, tv_nsec = 544329773}, st_mtim = {tv_sec = 1546870639, tv_nsec = 902332400}, st_ctim = {tv_sec = 1546870639, tv_nsec = 902332400}, __glibc_reserved = {0, 0, 0}} __func__ = "main" I have loaded "acc" module before loading "acc_json", are there any other mandatory prerequisites? I am trying to use acc_json to output accounting data to syslog. I just recompiled latest 5.2 kamailio but problem still occurs. Kamailio version below: root@labkam2:/opt/git/kamailio# kamailio -v version: kamailio 5.2.0 (x86_64/linux) c5216b flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: c5216b compiled on 16:13:00 Jan 7 2019 with gcc 6.3.0 Best Regards, Joonas Keskitalo

2 2

Dispatcher probing
by Duarte Rocha 07 Jan '19

07 Jan '19

Hey. I have another question regarding the Dispatcher Probing. In my SBC, a Gateway is defined by it's IP, Port and SAP (Kamailio's IP used for signaling). Those 3 parameters are defined in the Gateway table. In this case ( using Options for probing), i only have access to the destination IP ($dd) and Port ($dp). I need to know the SAP associated to the gateway that is currently being probed, in order to force the correct socket in the OPTIONS request. Is there any way to get more info about the db line that is being read by dispatcher for the probing? If that's not possible i was thinking about querying my db for the Ip:Port pair and if i got more than one result, do forking using the the SAPs in the results, sending multiple OPTIONS through the multiple sockets. In this case, if only one of the OPTIONS is answered, will the gateway still appear as "Active" ? Best Regards, Duarte Rocha

3 2

Kami, rtpproxy, T38 fax - anyone?
by yu＠yu-boot.ru 07 Jan '19

07 Jan '19

Yet again, fighting against strange fax behavior on Kamailio. When call is routed from device behind Kami and uplink is plain old Mediant2000 gateway to E1, T.38 always correctly established via reinvite and fax works perfectly. When call is routed to anything else including local Asterisk or Freeswitch, seems called don't hear fax noises and quickly throw BYE to me. Asterisk just don't see anything about UDPTL. Even more confusing, "near" device drops a call when detects fax tones from Asterisk or Yate. What can it be? SDP seem to be all transformed as they should be, I cant see anything wrong or different on SIP dumps. Rtpproxy is on bridge mode. Local device is Audiocodes MP118 and on private addressing, another end of Kami is on static IP. Voice calls work perfectly on this configuration. I can provide anything configs dumps etc, if it will help to solve this issue. Anyone using rtpproxy bridge and working T.38? Help me please. -- sent from myMail for Android

2 1

Sipt redirection number
by Duarte Rocha 04 Jan '19

04 Jan '19

Greetings, Regarding the module sipt and $sipt(redirection_number). Does this PV can show non digits correctly? I have a redirection number that has one char in the middle, like this "12C34567899". However, when i print the PV, i get "12<34567899". How can i fix this? Thanks, Best Regards, Duarte Rocha

2 1

Best place to change mem settings
by Duarte Rocha 03 Jan '19

03 Jan '19

Greetings, As far as i can tell, i have 3 ways to permanently change the memory settings in Kamailio : /etc/init.d/kamailio , /etc/default/kamailio and src/core/config.h. What's the priority between them? If i have different values in all 3 of them, which one will be used? Which is one is the best to use reliably? I recently upgraded my Kamailio from 5.0 to 5.2 and i need 12Mb of PKG. Before starting the new version for the first time i changed the values in /etc/default and the memory error didn't go away. It only worked after i changed it in core/config.h and recompilled. After that, i started Kamailio and i could do the changes in /etc/default without any problem. Does this happen for a reason? Best Regards, Duarte Rocha

3 2

logging destination IP and proto on reponse
by Andrew Chen 03 Jan '19

03 Jan '19

Hey all, Any way to log destination IP and proto of SIP responses? I'd tried to use majority of the pseudovars, but they all just return <null>. Thanks. -- Andy Chen achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

5 8

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