sr-users May 2021

sr-users@lists.kamailio.org

57 participants
66 discussions

Getting MOS feedback from rtpengine
by Barry Flanagan 17 May '21

17 May '21

Hi Using Kamailio 5.4.4 on Debian Buster. I am trying to get feedback of the MOS scores at call end. However the variables are always <null>. I have the modparams set as follows: # ----- rtpengine params ----- modparam("rtpengine", "rtpengine_sock", "udp:localhost:2223") modparam("rtpengine", "rtpengine_disable_tout", -1) modparam("rtpengine", "rtpengine_tout_ms", 2000) modparam("rtpengine", "rtpengine_allow_op", 1) modparam("rtpengine", "mos_min_pv", "$avp(s:mos_min)") modparam("rtpengine", "mos_max_pv", "$avp(s:mos_max)") modparam("rtpengine", "mos_average_pv", "$avp(s:mos_avg)") modparam("rtpengine", "mos_average_packetloss_pv", "$avp(s:mos_avg_packetloss)") modparam("rtpengine", "mos_average_jitter_pv", "$avp(s:mos_avg_jitter)") modparam("rtpengine", "mos_average_roundtrip_pv", "$avp(s:mos_avg_roundtrip)") I am trying to log the values from within the dialog:end event_route: event_route[dialog:end] { rtpengine_delete(); xlog("L_INFO","mos_avg=$avp(mos_avg), packetloss_avg=$avp(mos_avg_packetloss), jitter_avg=$avp(mos_avg_jitter), latency_avg=$avp(mos_avg_roundtrip), sip_last_reply=$rs - $ci\n"); return; } Am I missing something? I have tried rtpengine_query and rtpengine_manage in place of the _delete and also tried placing this in the BYE handling section of WITHIN_DIALOG but no joy. Any assistance much appreciated! -Barry -- -Barry

5 10

Hunting Kamailio.cfg for Voice termination System
by Edo 16 May '21

16 May '21

Hi, I am looking to get a complete kamailio.cfg file that I can use to set up a voice termination system. This system will only connect with peers making multiple simultaneous calls, registering strictly via ip, accounting calls to sql db, capable of multiple rate tables for the different peers, call control, CDR tool and billing capable and call routing to multiple media servers. I am willing to try to build this myself but at this time I do not even understand why I need to use "record_route" or "t_precheck_trans" -- :)). I am a lover of information and cannot find a simple enough text to help in my kamailio journey -- unlike asterisk. If you are interested please respond to me directly at edo.ekunwe(a)gmail.com and I am willing to pay for this information or guidance(if you have the patience and time to mentor me). Thanks -- ----- Nogie Ekunwe

3 4

Help to overwrite the $od, or another solution
by Victor Velo 15 May '21

15 May '21

Hello, I'm facing to some challenge in my learning process and using Kamalio as MS Teams SBC, the request I receive from MS Teams seems to be correct but I need to overwrite the Original Domain, which is the FQDN of Kamailio itself, to another domain name: INVITE sip:+15142144069@dev-sbc.openfabrik.com:5061;user=phone;transport=tls SIP/2.0Record-Route: <sip:155.138.140.233;r2=on;lr=on;ftag=3e2ca0c5d0da4335b121f205a6f20541>Record-Route: <sip:155.138.140.233:5061;transport=tls;r2=on;lr=on;ftag=3e2ca0c5d0da4335b121f205a6f20541>FROM: Victor Velo<sip:+14507001777@sip.pstnhub.microsoft.com:5061;user=phone>;tag=3e2ca0c5d0da4335b121f205a6f20541TO: <sip:+15142144069@dev-sbc.openfabrik.com:5061;user=phone> rewrite to: INVITE sip:+15142144069@dev-sbc.openfabrik.com:5061;user=phone;transport=tls SIP/2.0Record-Route: <sip:155.138.140.233;r2=on;lr=on;ftag=3e2ca0c5d0da4335b121f205a6f20541>Record-Route: <sip:155.138.140.233:5061;transport=tls;r2=on;lr=on;ftag=3e2ca0c5d0da4335b121f205a6f20541>FROM: Victor Velo<sip:+14507001777@sip.pstnhub.microsoft.com:5061;user=phone>;tag=3e2ca0c5d0da4335b121f205a6f20541TO: <sip:+15142144069@dev.myinternaldomain.openfabrik.com:5061;user=phone> What would the best why to achieve this rewriting? Thanks, Victor

2 2

loose_route() and FQDN
by Igor Olhovskiy 14 May '21

14 May '21

Hello, I saw there are some topics on this already and carefully walked through all of them, but can't solve following issue. For a reason I do need that in Record-Route header sent to endpoint would present FQDN. If it matters, it's UDP/WSS conversion done on Kamailio. So, scheme is quite simple Enpoint A ->UDP-> Kamailio ->WSS-> Endpoint B (NAT) Main issue here, that if in Record-Route headers it's FQDN, but not IP addresses, on a new transactions with a dialog (ACK on 200, PRACK, BYE), Kamailio*loose_route()* function resolves address of destination not current dialog, but actual R-URI (or itself, if R-URI is something from WebRTC world) that is not correct due to NAT. If in RR headers IP addresses are present - all is working as expected. As an example (RR with FQDN) B answers 200 SIP/2.0 200 OK Record-Route: <sip:KAMAILIO_FQDN:8089;transport=ws;r2=on;lr=on;ftag=0a3e31a6-96ad-42d0-9310-81b35cedbd3d;nat=wss> Record-Route: <sip:KAMAILIO_FQDN;r2=on;lr=on;ftag=0a3e31a6-96ad-42d0-9310-81b35cedbd3d;nat=wss> Via: SIP/2.0/UDP <A_IP_ADDRESS>:5060;received=A IP ADDRESS;rport=5060;branch=z9hG4bKPj67fb6d86-97d7-4231-995b-e54b0f62881e To: <sip:88290@<KAMAILIO_FQDN>>;tag=hvra7mj3q0 From: <sip:+XXXX7688881@<KAMAILIO_FQDN>>;tag=0a3e31a6-96ad-42d0-9310-81b35cedbd3d Call-ID: 46f44741-d155-4dd5-8fd8-78e540fc1acb CSeq: 18326 INVITE Contact: <sip:88290@toleivu2gdbh.invalid;transport=wss> Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER Supported: outbound Content-Type: application/sdp Content-Length: 817 ACK looks like ACK sip:88290@toleivu2gdbh.invalid;transport=wss SIP/2.0 Via: SIP/2.0/UDP A_IP_ADDRESS:5060;rport;branch=z9hG4bKPj8d05548a-91ef-4332-8617-32f8eeebf8f2 From: <sip:88881@A_IP_ADDRESS>;tag=0a3e31a6-96ad-42d0-9310-81b35cedbd3d To: <sip:88290@KAMAILIO_FQDN>;tag=hvra7mj3q0 Call-ID: 46f44741-d155-4dd5-8fd8-78e540fc1acb CSeq: 18326 ACK Route: <sip:FQDN;lr;r2=on;ftag=0a3e31a6-96ad-42d0-9310-81b35cedbd3d;nat=wss> Route: <sip:FQDN:8089;transport=ws;lr;r2=on;ftag=0a3e31a6-96ad-42d0-9310-81b35cedbd3d;nat=wss> Max-Forwards: 70 User-Agent: Asterisk PBX 13.33.0 Content-Length: 0 And Kamailio on *loose_route()* loops ACK to itself. (with result of function == 1) In a case if in Record-Route/Route headers just IP address of Kamailio present, all works as expected, but it's not really behavior I want to achieve. I've tried to play with *record_route_preset("...")* specifying only WSS part (as suggested in https://skalatan.de/de/blog/kamailio-sbc-teams) with FQDN, but no luck. Also wanted to try approach using record_route_preset() function in branch route, but it was working only with first branch, not affecting others (but I assume having different RR headers across branches is not a good idea) -- Regards, Igor

4 18

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

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 May 2021