sr-users

sr-users@lists.kamailio.org

49 participants
37556 discussions

Setting $conid per branch
by Marrold 14 May '21

14 May '21

Hi all, I'm currently adding a feature to our Kamailio configuration to fork calls based on user agent. To do so I'm getting the registered endpoints with reg_fetch_contacts() iterating through and matching on them, then using seturi() / append_branch() and setting the dst-uri and flags as required. However, calls are intermittently going to the wrong TCP connection, despite the logs showing the correct destination IP and port in the ONSEND route. Looking in the location table I can see each registration has a connection_id, and the debug log indicates it's finding the connection by ID: DEBUG: <core> [core/tcp_main.c:1651]: _tcpconn_find(): found connection by id: 3 Is there a way to set the conid per branch? Is it necessary? We're using kamailio 5.3.3 on Debian 10. Thanks Matthew

2 8

Possible to get the value of $DLG_lifetime before the BYE hits loose_route()
by ryan embgrets 13 May '21

13 May '21

Greetings, I would like to know if it is possible to get the value of $DLG_lifetime before the BYE hits loose_route(). opensips provides a similar function which lets you get dialog life. https://opensips.org/html/docs/modules/3.1.x/dialog.html#func_load_dialog_c… But i could not get the same from kamailio or maybe kamailio has a better way for this? Thanks for any pointer. Ryan

1 0

Bad config - you can not call 'handle_publish' function (db_url not set)
by Marrold 13 May '21

13 May '21

Hi, We're trying to upgrade from 5.3.X to 5.4.5 however kamailio will not start and produces the following error, despite the db_url being set in the config and printed in the logs: Bad config - you can not call 'handle_publish' function (db_url not set) Looking at the code this error only seems plausible if the *pres_library_mode* is set to 1 here <https://github.com/kamailio/kamailio/blob/cc2a9518207e36b7b18aef5c8714f0c21…> but we don't see the corresponding "switch to library mode" message in the debug logs which leaves me a bit stuck - I've included the grepped logs at the bottom of the message. Does anyone have any ideas what is causing this issue? I've seen a previous issue relating to interactions between presence and presence_xml which we're also using, but it looks like this was fixed in an older version. Any suggestions appreciated. # ----- presence params ----- modparam("presence", "db_url", DBURL) modparam("presence", "db_update_period", 20) modparam("presence", "clean_period", 60) modparam("presence", "local_log_facility", "LOG_LOCAL3") modparam("presence", "max_expires", 14430) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) root@kamailio:/etc/kamailio# grep -i "presence" /var/log/kamailio/kamailio.log May 10 12:44:14 kamailio /sbin/kamailio[23729]: ERROR: presence [presence.c:656]: fixup_presence(): Bad config - you can not call 'handle_publish' function (db_url not set) May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.y:1810]: yyparse(): loading module presence.so May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:525]: load_module(): trying to load </lib64/kamailio/modules/presence.so> May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/kemi.c:2927]: sr_kemi_modules_add(): adding module: presence May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:287]: register_module(): register PV from: presence May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.lex:1796]: pp_define(): defining id: MOD_presence May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.y:1810]: yyparse(): loading module presence_xml.so May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:525]: load_module(): trying to load </lib64/kamailio/modules/presence_xml.so> May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/kemi.c:2927]: sr_kemi_modules_add(): adding module: presence_xml May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.lex:1796]: pp_define(): defining id: MOD_presence_xml May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.y:1810]: yyparse(): loading module presence_mwi.so May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:525]: load_module(): trying to load </lib64/kamailio/modules/presence_mwi.so> May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.lex:1796]: pp_define(): defining id: MOD_presence_mwi May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.y:1810]: yyparse(): loading module presence_dialoginfo.so May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:525]: load_module(): trying to load </lib64/kamailio/modules/presence_dialoginfo.so> May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/cfg.lex:1796]: pp_define(): defining id: MOD_presence_dialoginfo May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence' matches module 'presence' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <db_url> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <db_url> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence' matches module 'presence' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <db_update_period> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <db_update_period> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence' matches module 'presence' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <clean_period> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <clean_period> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence' matches module 'presence' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <local_log_facility> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <local_log_facility> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence' matches module 'presence' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <max_expires> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <max_expires> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence_xml' matches module 'presence_xml' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <db_url> in module presence_xml [/lib64/kamailio/modules/presence_xml.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <db_url> in module presence_xml [/lib64/kamailio/modules/presence_xml.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:107]: set_mod_param_regex(): 'presence_xml' matches module 'presence_xml' May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/sr_module.c:744]: find_param_export(): found <force_active> in module presence_xml [/lib64/kamailio/modules/presence_xml.so] May 10 12:44:41 kamailio kamailio: DEBUG: <core> [core/modparam.c:123]: set_mod_param_regex(): found <force_active> in module presence_xml [/lib64/kamailio/modules/presence_xml.so] May 10 12:44:43 kamailio kamailio: DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <handle_publish> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:43 kamailio kamailio: DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <handle_subscribe> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:43 kamailio kamailio: DEBUG: <core> [core/route.c:129]: route_add(): mapping routing block (0x560e73f9a440)[PRESENCE] to 11 May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:873]: init_mod(): presence May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [presence.c:293]: mod_init(): db_url=mysql://kamailio:PASSWORD@localhost/kamailio (len=50 addr=0x7f3a33d4e288) May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [presence.c:337]: mod_init(): server_address parameter not set in configuration file May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [subscribe.c:2529]: restore_db_subs(): loading information from database 0 records May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:873]: init_mod(): presence_xml May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence_xml [presence_xml.c:170]: mod_init(): db_url=mysql://kamailio:PASSWORD@localhost/kamailio (len=50 addr=0x7f3a33d4ef00) May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <bind_presence> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [presence/1] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [presence.winfo/2] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:239]: add_event(): successfully added event: presence - len= 8 May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence_xml [add_events.c:75]: xml_add_events(): added 'presence' event to presence module May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [presence.winfo/2] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [presence/1] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:188]: add_event(): Found wipeer event [presence] for event [presence.winfo] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:239]: add_event(): successfully added event: presence.winfo - len= 14 May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence_xml [add_events.c:94]: xml_add_events(): added 'presence.winfo' event to presence module May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [xcap-diff/0] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [xcap-diff.winfo/0] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:239]: add_event(): successfully added event: xcap-diff - len= 9 May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence_xml [add_events.c:132]: xml_add_events(): added 'xcap-diff' event to presence module May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:873]: init_mod(): presence_mwi May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <bind_presence> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [message-summary/6] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [message-summary.winfo/0] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:239]: add_event(): successfully added event: message-summary - len= 15 May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:873]: init_mod(): presence_dialoginfo May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: <core> [core/sr_module.c:652]: find_mod_export_record(): found export of <bind_presence> in module presence [/lib64/kamailio/modules/presence.so] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [dialog/5] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:324]: search_event(): start event= [dialog.winfo/0] May 10 12:44:45 kamailio /sbin/kamailio[23830]: DEBUG: presence [event_list.c:239]: add_event(): successfully added event: dialog - len= 6 May 10 12:44:47 kamailio /sbin/kamailio[23830]: ERROR: presence [presence.c:656]: fixup_presence(): Bad config - you can not call 'handle_publish' function (db_url not set) May 10 12:44:47 kamailio /sbin/kamailio[23830]: DEBUG: presence_xml [presence_xml.c:295]: destroy(): start May 10 12:44:47 kamailio /sbin/kamailio[23830]: DEBUG: presence [subscribe.c:2433]: timer_db_update(): db_update timer May 10 12:44:47 kamailio /sbin/kamailio[23830]: DEBUG: presence [subscribe.c:2137]: update_db_subs_timer(): update_db_subs_timer: start

3 6

secsipid
by David Villasmil 12 May '21

12 May '21

Hello guys, I'm trying to use secsipid as per https://kamailio.org/docs/modules/5.5.x/modules/secsipid.html I just installed go on a new vm: the env is as follows: # env GOPATH=/root/go then: ~# go get github.com/asipto/secsipidx ~# Then: ~# cd $GOPATH/src/github.com/asipto/secsipidx/csecsipid/ bash: cd: /root/go/src/github.com/asipto/secsipidx/csecsipid/: No such file or directory it looks like it's not downloaded where the documentation says. It is however in: go |-- bin `-- pkg |-- mod | |-- cache | | `-- download | | |-- github.com | | | |-- asipto | | | | `-- secsipidx | | | | `-- @v | | | `-- google | | | `-- uuid | | | `-- @v | | `-- sumdb | | `-- sum.golang.org | | |-- lookup | | | `-- github.com | | | |-- asipto | | | `-- google | | `-- tile | | `-- 8 | | |-- 0 | | | |-- x010 | | | |-- x011 | | | `-- x016 | | | `-- 560.p | | |-- 1 | | | `-- 064.p | | `-- 2 | | `-- 000.p | `-- github.com | |-- asipto | | `-- secsipidx(a)v1.0.0 | | |-- csecsipid | | `-- secsipid | `-- google | `-- uuid(a)v1.2.0 `-- sumdb `-- sum.golang.org 38 directories But going into ~/go/pkg/mod/github.com/asipto/secsipidx(a)v1.0.0/csecsipid we have: ~/go/pkg/mod/github.com/asipto/secsipidx(a)v1.0.0/csecsipid# ls -l total 16 -r--r--r-- 1 root root 231 May 11 13:14 Makefile -r--r--r-- 1 root root 1778 May 11 13:14 csecsipid.go -r--r--r-- 1 root root 1988 May 11 13:14 libsecsipid.h -r--r--r-- 1 root root 120 May 11 13:14 secsipid.h The Makefile contains the proper liba: # Makefile to build libraries # all: libso libso: go build -o libsecsipid.so -buildmode=c-shared csecsipid.go liba: go build -o libsecsipid.a -buildmode=c-archive csecsipid.go clean: rm -f libsecsipid.so rm -f linsecsipid.a But "make liba" returns: # make liba go build -o libsecsipid.a -buildmode=c-archive csecsipid.go csecsipid.go:6:2: no required module provides package github.com/asipto/secsipidx/secsipid: go.mod file not found in current directory or any parent directory; see 'go help modules' make: *** [Makefile:10: liba] Error 1 Obviously not a "go" guy here. What am I doing wrong? Thanks for your help! David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 9

bogus event with terminated dialogs with late 200ok responses
by David Escartín 12 May '21

12 May '21

Hello all using kamailio version 5.4.4, we are seeing some errors like CRITICAL: dialog [dlg_hash.c:1205]: next_state_dlg(): bogus event 3 in state 5 (with BYE) for dlg 0x7f6ca2304b48 [15135:39671] with clid '00463385_20210512_002_HPRA_1.1.4.40.sp3_7532_0_54533900281' and tags 'Out-55089-0000000CB27947F9' '170cB11c48vmj' which seem to be generated when we receive a BYE from the remote UA but we were expecting an ACK also, For example INVITE ----------> <---------------183 <---------------200 BYE -------------> (no ACK) <--------------200 <--------------200 .... so the b2bua (freeswitch) keeps retransmitting the 200ok, and on each 200ok retransmission we are getting this type of message. These seem to be like race conditions since 200/BYE flow almost at the same time, and as I understand, the UA should send the ACK. But my doubt is if these errors can be harmful for the kamailio or they can be ignored and address the issue to the remote UA on each case thanks a lot and regards david -- <http://www.sonoc.io/> David Escartín NOC engineer *www.sonoc.io* <http://www.sonoc.io/> [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Facebook] <https://www.facebook.com/SONOCio/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: *dataprotection(a)sonoc.io* <dataprotection(a)sonoc.io>*.* <dataprotection(a)sonoc.io>

2 1

Kamailio as front proxy for multiple sip servers
by Eliphas Levy Theodoro 10 May '21

10 May '21

Hello! I am trying to config one kamailio as reverse proxy for a bunch of internal (no internet address) separate asterisk sip instances (per domain). The kamailio server would be the only with the valid IP address, so would use rtpengine to force to be in the media path. Like this scenario: https://opensips.org/pipermail/users/2020-August/043610.html I have used as starting point this very basic config: https://blog.voipxswitch.com/2015/03/27/kamailio-basic-sip-proxy-all-reques… Basically just added rtpproxy support, and voilà, inter-SIP is working, media always passing into the proxy. The problem: I would have WebRTC phones connecting too. I tried setting WSS up in kamailio, and asterisk (pjsip) wouldn't know how to send the message to the proxy: on register it has trasnport=wss in the contact: header, looks like it is confusing the asterisk. So, I resort for the wisdom of the list :) What would be the good-best-path to take here, hack the header, or put the webphones registering directly on the asterisks (with a nginx reverse proxy maybe)? Someone must have already made a blog with such setup, but I could not google-unearth it at least until now. Regards, -- Eliphas

5 7

MS Teams SBC
by Victor Velo 09 May '21

09 May '21

Hello, I'm trying to test a Henning's tutorial for Teams SBC described here: https://skalatan.de/en/blog/kamailio-sbc-teams. A minor change at the MS Teams setup is just about the login. Now it requires MFA.The license I used is : Microsoft 365 developer subscriptions (E5).The domanin dv-sbc.openabrik.com is added + 1 user PS> Connect-MicrosoftTeams (MFA)PS> New-CsOnlinePSTNGateway -Fqdn dev-sbc.openfabrik.com -SipSignalingPort 5061 -MaxConcurrentSessions 10 -ForwardCallHistory $true -Enabled $true Everything seems to be OK at MS Teams side. I'm using the Kamailio coming with Kazoo. Version 5.2.5[root@dev-sbc kamailio]# kamailio -versionversion: kamailio 5.2.5 (x86_64/linux) 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_RESADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MBpoll method support: poll, epoll_lt, epoll_et, sigio_rt, select.id: unknown compiled on 01:14:59 Nov 19 2019 with gcc 7.3.1 When Kamailio is probing MS Teams, the log shows the following errors (for the 3 GW): hG4bKc188.6a606040000000000000000000000000.0#015#012To: <sip:sip2.pstnhub.microsoft.com;transport=tls>#015#012From: <sip:dev-sbc.openfabrik.com>;tag=d9a52ca041d9e6253dd2a7d5399056e3-2f56#015#012CSeq: 10 OPTIONS#015#012Call-ID: 4ed99b8a73a96dcd-10234(a)155.138.140.233#015#012Max-Forwards: 70#015#012Content-Length: 0May 9 01:26:17 dev-sbc kamailio[10234]: ERROR: <core> [core/tcp_main.c:618]: _wbufq_add(): (517 bytes): write queue full or timeout (0, total 1100374016, last write 41683154 s ago)May 9 01:26:17 dev-sbc kamailio[10234]: ERROR: <core> [core/tcp_main.c:2673]: tcpconn_1st_send(): 52.114.76.76:5061: EAGAIN and write queue full or failed for 0x7fce434db860May 9 01:26:17 dev-sbc kamailio[10234]: ERROR: tm [../../core/forward.h:293]: msg_send_buffer(): tcp_send failedMay 9 01:26:17 dev-sbc kamailio[10234]: ERROR: tm [uac.c:648]: send_prepared_request_impl(): Attempt to send to precreated request failedMay 9 01:26:17 dev-sbc kamailio[10234]: INFO: <script>: Sent out tm request to Teams: OPTIONS sip:sip.pstnhub.microsoft.com;transport=tls SIP/2.0#015#012Via: SIP/2.0/TLS 155.138.140.233:5061;branc config: tls.cfg [server:default]method = TLSv1.2+verify_certificate = yesrequire_certificate = yesprivate_key = /etc/letsencrypt/live/openfabrik.com/privkey.pemcertificate = /etc/letsencrypt/live/openfabrik.com/fullchain.pemca_list = /etc/letsencrypt/live/openfabrik.com/bc2025.pemserver_name = dev-sbc.openfabrik.com [client:default]method = TLSv1.2+verify_certificate = yesrequire_certificate = yesprivate_key = /etc/letsencrypt/live/openfabrik.com/privkey.pemcertificate = /etc/letsencrypt/live/openfabrik.com/fullchain.pemca_list = /etc/letsencrypt/live/openfabrik.com/bc2025.pem ==== event_route[tm:local-request]{ setflag(FLAG_LOCAL_REQUEST); if(is_method("OPTIONS") && $ru =~ "pstnhub.microsoft.com") { append_hf("Contact: <sip:dev-sbc.openfabrik.com:5061;transport=tls>\r\n"); xlog("L_INFO", "Sent out tm request to Teams: $mb\n"); } xlog("L_DEBUG", "$ci|local|start $pr request $rm $ou\n"); xlog("L_DEBUG", "$ci|local|source $si:$sp -> $dd:$dp\n"); xlog("L_DEBUG", "$ci|local|from $fu\n"); xlog("L_DEBUG", "$ci|local|to $tu\n"); #!ifdef SIP_TRACE_ROLE route(SIP_TRACE); #!endif #!ifdef PRESENCE_ROLE route(PRESENCE_LOCAL_REQUEST); #!endif } ====# setid(integer) destination(sip uri) flags (integer, optional), priority(int,opt), attrs (str,optional)kamctl dispatcher add 2 'sip:sip.pstnhub.microsoft.com;transport=tls' 0 3 'socket=tls:155.138.140.233:5061;ping_from=sip:dev-sbc.openfabrik.com'kamctl dispatcher add 3 'sip:sip2.pstnhub.microsoft.com;transport=tls' 0 2 'socket=tls:155.138.140.233:5061;ping_from=sip:dev-sbc.openfabrik.com'kamctl dispatcher add 4 'sip:sip3.pstnhub.microsoft.com;transport=tls' 0 1 'socket=tls:155.138.140.233:5061;ping_from=sip:dev-sbc.openfabrik.com' [root@dev-sbc kamailio]# kamctl dispatcher showdispatcher gatewayssqlite_query: /usr/bin/sqlite3 /etc/kazoo/kamailio/db/kazoo.db select * FROM dispatcher ORDER BY setid; 1|1|sip:155.138.140.233:11000|9|0|zone=local;profile=sipinterface_1;duid=243;node=freeswitch@dev-sbc.openfabrik.com|added by nodes role2|2|sip:sip.pstnhub.microsoft.com;transport=tls|0|3|socket=tls:155.138.140.233:5061;ping_from=sip:dev-sbc.openfabrik.com|3|3|sip:sip2.pstnhub.microsoft.com;transport=tls|0|2|socket=tls:155.138.140.233:5061;ping_from=sip:dev-sbc.openfabrik.com|4|4|sip:sip3.pstnhub.microsoft.com;transport=tls|0|1|socket=tls:155.138.140.233:5061;ping_from=sip:dev-sbc.openfabrik.com| Is it a bug on the Kamailio 5.2.5 release or Do I miss something? Thanks, Victor

2 3

Unable to parse the Cancel request
by Ilie Soltanici 05 May '21

05 May '21

Hello, We are having an issue here where Kamailio is complaining about duplicate To header, while in the SIP Packet there is just one. See below the log message: DEBUG: tm [t_msgbuilder.c:391]: build_local_reparse(): duplicate To header ERROR: tm [t_msgbuilder.c:531]: build_local_reparse(): cannot build CANCEL request ERROR: tm [t_cancel.c:297]: cancel_branch(): attempt to build a CANCEL failed ERROR: tm [t_fwd.c:1434]: e2e_cancel(): cancel error And this is the sip message: CANCEL sip:123456789@1.2.3.4:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.1:19373 ;branch=z9hG4bK-524287-1---7774073fad1a3264;rport Max-Forwards: 70 To: <sip:123456789@1.2.3.4:5060> From: "101"<sip:101@1.2.3.4:5060>;tag=6f373b66 Call-ID: hC2O6zx8ZaUJ1di046 CSeq: 2 CANCEL Proxy-Authorization: Digest username="101",realm="1.2.3.4",nonce="YJKbfWCSmlFTHxdJfKmySydF9L7FzfaqcgyOo4A=",uri=" sip:123456789@1.2.3.4:5060 ",response="2bf2ba8ef2374d6aa8c39d650613077d",algorithm=MD5 User-Agent: TEST Content-Length: 0 version: kamailio 5.5.0 (x86_64/linux) d4c1a1 The route itself, is like in the standard documentation: # CANCEL processing if KSR.is_CANCEL() : KSR.info(RANDOM_LOG + 'KSR.is_CANCEL') if KSR.tm.t_check_trans()>0 : self.ksr_route_relay(msg) return 1 def ksr_route_relay(self, msg): if KSR.is_method_in("IBSU") : if KSR.tm.t_is_set("branch_route")<0 : KSR.tm.t_on_branch("ksr_branch_manage") if KSR.is_method_in("ISU") : if KSR.tm.t_is_set("onreply_route")<0 : KSR.tm.t_on_reply("ksr_onreply_manage") if KSR.is_INVITE() : if KSR.tm.t_is_set("failure_route")<0 : KSR.tm.t_on_failure("ksr_failure_manage") if KSR.tm.t_relay()<0 : KSR.sl.sl_reply_error() return -255 Thanks

2 7

start_recording and stop_recording inside event_route[xhttp:request]
by Володимир Іванець 05 May '21

05 May '21

Hello! I'm testing call recording with Rtpengine. It works fine when the "record-call=on" flag is added to the *rtpengine_offer* or *start_recording* is used in the *request_route*. But I was wondering if the call recording can be managed by a separate application. So I add the following lines to the *event_route[xhttp:request]* and triggered it with an HTTP request after the call was established. The call-id value was taken from the Rtpengine log and sent with the request. * if ($hu =~ "^/CALL_RECORD_START/") {* * $var(call_id) = *"call-id=" + *$(hu{s.select,2,/});* xlog("L_DBG", "$var(call_id)"); * start_recording($var(call_id));* exit; * }* In this case, Kamailio will log errors and will not send the Rtpengine command to start call recording. *Apr 27 18:25:00 test /usr/sbin/kamailio[5347]: DEBUG: <script>: call-id=3de74068278ede4417086eb82bdf5a06@127.0.0.1:5080.0* *Apr 27 18:25:00 test /usr/sbin/kamailio[5347]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header* *Apr 27 18:25:00 test /usr/sbin/kamailio[5347]: ERROR: rtpengine [rtpengine_funcs.c:294]: get_callid(): call-id not found* *Apr 27 18:25:00 test /usr/sbin/kamailio[5347]: ERROR: rtpengine [rtpengine.c:2383]: rtpp_function_call(): can't get Call-Id field* Have anyone tried to call functions *start_recording* and *stop_recording* inside *event_route[xhttp:request]*? Thanks a lot!

3 12

Kamailio v5.5.0 Released - new major version is out
by Daniel-Constantin Mierla 05 May '21

05 May '21

Kamailio v5.5.0 is out – it comes with 6 new modules and a considerable set of improvements touching again more than 80 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-5-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.5.0 brings more flexibility and optimizations across many components, enhancements to distributed message queue (dmq module), load balancer, http client, STIR/SHAKEN support, IMS/VoLTE, rtpengine and tls as well as to make available more functions to KEMI interface ... just to list only a few here. Enjoy Kamailio v5.5.0! Thank you for flying Kamailio! Stay safe and healthy! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

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