- sr-users - kamailio.org

How to setup Kamailio to dispatch SIP client requests to WebRTC enabled Asterisk
by Adesh Pandey 20 Feb '19

20 Feb '19

Hi Guys, I have recently setup a Kamailio server which can accept SIP or WebSocket connections but voice is not coming in the case of SIP client. I have no idea to change avp in the incoming request, please advise how to proceed.

3 3

Topos and subst_hf
by Igor Olhovskiy 19 Feb '19

19 Feb '19

Hi! I'm using subst_hf to add some extra info to contact subst_hf("Contact", "/^(.*)sip:(.*)@(.*)$/\1sip:encei$var(extra_info)-\2@\3/i", "f"); With combination of topos it's giving me strange results like 2(26) WARNING: sanity [sanity.c:282]: check_ruri_scheme(): failed to parse request uri [sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74><sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74] Seems, it's doubling R-URI on in-dialog requests. If I'm disabling topos - all is ok. What is interesting - this can't be reproduced with remove_hf/append_hf mechanisms.

1 1

Problem with requests routing when topoh is enabled
by Leonid Fainshtein 19 Feb '19

19 Feb '19

Hi, I have Kamailio 5.1 and I'm using the topology hiding module (topoh) that is configured as the following: modparam("topoh", "mask_key", "...") modparam("topoh", "uparam_name", "....") modparam("topoh", "uri_prefix_checks", 0) Unfortunately Fanvil SIP phone modifies the remote party Contact's URI before it puts it as R-URI in the re-INVITE request. For example, The remote party Contact header: Contact: <sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd> The re-INVITE request line: INVITE sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd;user=phone SIP/2.0 As you can see, ";user=phone" was added. As result of that Kamailio tries to send the request to 127.0.0.8. If I disable sending 'user=phone' in Fanvil configuration then everything works well. I assumed that if uri_prefix_checks=0 then the topoh module should take rid of such URI modifications. Am I wrong? Is there any way to solve the problem except to modify the endpoint configuration? Best regards, Leonid Fainshtein

1 0

How can i send presence status from Asterisk 13 to kamailio presence module
by PICCORO McKAY Lenz 19 Feb '19

19 Feb '19

i have followed the guie in https://kb.asipto.com/kamailio:presence:k43-blf and asterisk are working (due we connnect the phones directly to asterisk and works) but when connect the phones to the kamailio the led in phones does not work! ther's some info missing or what? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

1 0

Re: [SR-Users] TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 19 Feb '19

19 Feb '19

Hi, Looks that space comes from copy/paste or page formatting - in the log file there is no space within this variable. Thank's

2 3

Detecting end of DNS failover in tm:branch-failure
by Ivan Ribakov 19 Feb '19

19 Feb '19

Hi all, I have a custom routing logic implemented in my module. This routing logic may return a list of 2 or more endpoints where INVITE should be attempted to be routed. Since endpoint URI can contain domain names, I’m also trying to take care of DNS resolution. Based on the documentation found in https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt <https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt> current DNS resolver/failover logic takes good care of RFC3263. To support switching between various endpoints returned by custom routing logic I have been using “tm:branch-failure” routing blocks. Problem I’m facing right now is that I am unable to distinguish between a DNS failover branch failure that has more SRV records to try and the “final” DNS failover branch failure (at which point I should be switching to another endpoint). I’ve tried monitoring $T_reply_code values, but it is “408” in both cases. Any ideas on how “final” and “non-final” DNS failover branch failures can be distinguished? Regards, Ivan

1 0

Re: [SR-Users] Issue with UAC restore_mode when restore_dlg is enabled
by Daniel-Constantin Mierla 19 Feb '19

19 Feb '19

Can you check via rpc and looking at database tables if dialog record is there? Cheers, Daniel On Tue, 19 Feb 2019, 08:44 <jenus(a)cyberchaos.nl wrote: > Daniel, > > Yes the uac_replace_from is called from a branch route. > > Jan > > Daniel-Constantin Mierla schreef op 2019-02-19 08:26: > > I do not recall any relevant changes recently in this part of the code, > > so likely to be same result for 5.2. > > > > With restore_dlg set to 1, dialog variables are used for storing the > > headers. When do you call uac_replace_from()/_to()? Is it in a > > branch_route? > > > > Cheers, > > Daniel > > > > On 19.02.19 08:07, jenus(a)cyberchaos.nl wrote: > >> Forgot to mention, i'm running kamailio 5.1.7, did not test yet with > >> the latest 5.2 release. > >> > >> Jan > >> > >> > >> jenus(a)cyberchaos.nl schreef op 2019-02-18 15:22: > >>> Hello, > >>> > >>> I'm running into a issue with restore_mode auto when i enable > >>> restore_dlg in the uac module. I have a feature where i reroute calls > >>> for a subscriber when it is offline. When routing calls to the > >>> subscriber i check the exit status of "lookup("location")" and > >>> re-route the call. This works fine. It seems to fail when i hit the > >>> failure route (subscriber has a usrloc entry but does not respond). > >>> In > >>> the failure route i append_branch and reroute the call. > >>> > >>> The rerouting works fine, but when i receive the ACK on the 200OK on > >>> the re-routed call the "restore" feature seems to fail and i end up > >>> with a header like: > >>> > >>> To: > >>> <sip:+<null>@voip-dev.domain.nl > >;tag=5B8ABC8A-5C6ABE83000EBF35-AB202700 > >>> in the ACK. > >>> > >>> If i disable restore_dlg feature from the UAC module it adds the > >>> vsf/vst to the Record-Route header and all works fine. > >>> > >>> Do i need to do something special when i create a new branch and use > >>> the restore_dlg feature? > >>> > >>> > >>> Thanks, > >>> > >>> Jan Hazenberg > >>> > >>> _______________________________________________ > >>> Kamailio (SER) - Users Mailing List > >>> sr-users(a)lists.kamailio.org > >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >

2 2

Issue with UAC restore_mode when restore_dlg is enabled
by jenus＠cyberchaos.nl 19 Feb '19

19 Feb '19

Hello, I'm running into a issue with restore_mode auto when i enable restore_dlg in the uac module. I have a feature where i reroute calls for a subscriber when it is offline. When routing calls to the subscriber i check the exit status of "lookup("location")" and re-route the call. This works fine. It seems to fail when i hit the failure route (subscriber has a usrloc entry but does not respond). In the failure route i append_branch and reroute the call. The rerouting works fine, but when i receive the ACK on the 200OK on the re-routed call the "restore" feature seems to fail and i end up with a header like: To: <sip:+<null>@voip-dev.domain.nl>;tag=5B8ABC8A-5C6ABE83000EBF35-AB202700 in the ACK. If i disable restore_dlg feature from the UAC module it adds the vsf/vst to the Record-Route header and all works fine. Do i need to do something special when i create a new branch and use the restore_dlg feature? Thanks, Jan Hazenberg

2 3

Presence module with external MWI
by Trevor Peirce 19 Feb '19

19 Feb '19

Hello, Looking for pointers as to what I'm missing here. I'm using the presence module to allow UAs to subscribe to message-summary events. I can see the entries appearing in the active_watchers table and I see subscription renewals increment the cseq columns so I'm satisfied this part is working well. I'm having trouble finding out how to tell Kamailio about a change to the message-summary so that it can notify the watchers. The pua module seems to provide a way but it doesn't seem to work with the subscriptions set up by the presence module. The presence module itself does not seem to offer any RPCs capable of doing this. Appreciate any pointers! Thanks, -- Trevor Peirce AcroVoice Solutions Inc

4 5

Integration with mobile oprators
by sina yazdanian 18 Feb '19

18 Feb '19

Dear Kamailio Technical team I’m Sina from a small software development company in Middle-East. We are interested in your product. For R&D research we need some documents about your product. Your support would be appreciated in case of sharing document. We need document about* SIP server integration with Mobile operator*. I would be grateful if you support me and the team to complete research. Best Regards Sina Yazdanian

2 1

how to see banned address after rule it
by PICCORO McKAY Lenz 18 Feb '19

18 Feb '19

i configure rules for routing banned ip and i want to see where i can autdit this issues.. i mean where i can automatically define a cron setup that grep those logs definitios.. where are loggin those all? my rules are: define at begining of kamailio.cfg "#!WITH_ANTIFLOOD", later add: #!ifdef WITH_ANTIFLOOD loadmodule "htable.so" loadmodule "pike.so" modparam("pike", "sampling_time_unit", 2) modparam("pike", "reqs_density_per_unit", 16) modparam("pike", "remove_latency", 4) modparam("htable", "htable", "ipban=>size=8;autoexpire=300;") #!endif later routing definitions: route[REQINIT] { if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); exit; } if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); $sht(ipban=>$si) = 1; exit; } } if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { xlog("L_ALERT","ALERT: friendly canings from $fu (IP:$si:$sp)\n"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 3

Dispatcher No destinations available
by Cristian Livadaru 18 Feb '19

18 Feb '19

Hi, I have a Kamailio running as Load Balancer and it works great but since a couple of weeks I kept noticing 404s in Homer and when looked into it they came from Kamailio. ``` route[LOADBALANCE] { #ds_select_dst(destination_set, algorithm) function chooses the destination for the call. For this it can use a lot of algorithms. #Alg. 0 is the default one that does the the choosing over the call ID hash #Alg. 4 is a Round-Robin #Alg. 10 is the one that chooses the destination based on the minimum load of all destinations if(!ds_select_dst("1", "4")) { #if we are here that means no destination is available. We notify the user by 404 and exit the script. xlog("L_NOTICE", "No destination available!"); send_reply("404", "No destination"); exit; } xlog("L_NOTICE", "Routing call to <$ru> via <$du>\n"); #set the no_reply_recieved timeout to 2 second ... adjust the value to your need #note: The first value "0" is invite timeout .. we do not need to change it #This means that is the selected media server fails to respond within 2 seconds the failure_route "MANAGE_FAILURE" is called #note: this implies that ale the signaling from media servers on the way back to the user goes through the proxy as well t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); return; } ``` The two asterisks behind it seem fine and I can’t really see why this started happening. Also I thing that returning 404 might be misleading, wouldn’t it be better if I would return 503 instead? I enabled debugging in Kamailio but can’t really seem to notice anything wrong here: ``` Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/udp_server.c:491]: udp_rcv_loop(): received on udp socket: (106/100/1104) [[INVITE sip:431230123@213.137.140.230:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 196.27.235.76:5060;branch=z9h]] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:604]: parse_msg(): SIP Request: Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:606]: parse_msg(): method: <INVITE> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:608]: parse_msg(): uri: <sip:431230123@213.137.140.230:5060> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): version: <SIP/2.0> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK0080827005DD9C0D8E963B2EA293>; state=16 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:492]: parse_headers(): Via found, flags=2 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:494]: parse_headers(): this is the first via Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=10 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [52]; uri=[sip:431230123@213.137.140.230] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): to body ["431230123" <sip:431230123@213.137.140.230> Feb 15 09:50:28 wlb kamailio[6659]: ] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <36825> <INVITE> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/receive.c:200]: receive_msg(): --- received sip message - request - call-id: [2610e00004f5-5c66843f-6400386f-2c1b8100-6c4782(a)127.0.0.1] - cseq: [36825 INVITE] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/receive.c:248]: receive_msg(): preparing to run routing scripts... Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=0080827005DD9C0D8E96C55CF6CD Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace.c:507]: sip_trace_store_db(): database connection not initialized Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:498]: pipport2su(): the port string is 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:498]: pipport2su(): the port string is 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/proxy.c:264]: mk_proxy(): doing DNS lookup... Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:302]: trace_send_hep2_duplicate(): setting up the socket_info Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: Tracing 6(6668) DEBUG: maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:183]: get_hdr_field(): content_length=355 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: sanity [sanity_mod.c:256]: w_sanity_check(): sanity checks result: 1 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==9 && [213.137.140.230] == [127.0.0.1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==14 && [213.137.140.230] == [213.137.140.230] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: OPTIONS from 196.27.235.76:5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siputils [checks.c:120]: has_totag(): no totag Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:1018]: t_check_msg(): msg (0x7f7e7edd3be8) id=6845 global id=6844 T start=(nil) Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:476]: t_lookup_request(): start searching: hash=29308, isACK=0 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:435]: matching_3261(): RFC3261 transaction matching failed Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:659]: t_lookup_request(): no transaction found Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:1087]: t_check_msg(): msg (0x7f7e7edd3be8) id=6845 global id=6845 T end=(nil) Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: rr [loose.c:1209]: is_direction(): param ftag not found Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: dispatcher [dispatch.c:1832]: ds_select_dst_limit(): set [1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: dispatcher [dispatch.c:1935]: ds_select_dst_limit(): alg hash [1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: No destination available! 6(6668) DEBUG: sl [sl.c:282]: send_reply(): reply in stateless mode (sl) ``` My kamailio.cfg ``` #!KAMAILIO # # sample config file for dispatcher module # - load balancing of VoIP calls with round robin # - no TPC listening # - don't dispatch REGISTER and presence requests # # Kamailio (OpenSER) SIP Server v3.2 # - web: http://www.kamailio.org # - git: http://sip-router.org # # Direct your questions about this file to: sr-users(a)lists.sip-router.org # # Refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php # for an explanation of possible statements, functions and parameters. # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # ####### Global Parameters ######### #!define WITH_HOMER #!define WITH_DEBUG #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4 /* comment the next line to enable TCP */ disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases based on revers DNS on IPs (default on) */ auto_aliases=yes /* add local domain aliases */ port=5060 /* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ # listen=udp:127.0.0.1:5060 sip_warning=no ####### Modules Section ######## #set module path mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" # loadmodule "db_mysql.so" # loadmodule "mi_fifo.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "counters.so" loadmodule "dispatcher.so" #!ifdef WITH_HOMER loadmodule "siptrace.so" #!endif #loadmodule "kex.so" #loadmodule "tm.so" #loadmodule "tmx.so" #loadmodule "sl.so" #loadmodule "rr.so" #loadmodule "pv.so" #loadmodule "maxfwd.so" #loadmodule "textops.so" #loadmodule "siputils.so" #loadmodule "xlog.so" #loadmodule "sanity.so" ## loadmodule "ctl.so" #loadmodule "mi_rpc.so" #loadmodule "acc.so" # ----- acc params ----- modparam("acc", "log_flag", 1) modparam("acc", "failed_transaction_flag", 3) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") #!ifdef WITH_HOMER # check IP and port of your capture node modparam("siptrace", "duplicate_uri", "sip:213.136.47.31:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) #!endif # ----------------- setting module-specific parameters --------------- # modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(dssocket)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") #set next two parameters if you want to enable balance alg. no. 10 #modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") #modparam("dispatcher", "ds_hash_size", 8) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_from", "sip:kamailio@example.com") #modparam("dispatcher", "ds_ping_method", "INFO") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 1) #configure codes or classes of SIP replies to list only allowed replies (i.e. when temporarily unavailable=480) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=480;code=404") ####### Routing Logic ######## # main request routing logic route { #!ifdef WITH_HOMER #start duplicate the SIP message now sip_trace(); setflag(22); xlog("L_NOTICE","Tracing"); #!endif # per request initial checks route(REQINIT); # handle requests within SIP dialogs route(WITHINDLG); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) record_route(); #if (is_method("INVITE")) #{ # ds_select_domain("1","4"); # #sl_send_reply("300","Redirect"); # #t_relay(); # exit; #} # account only INVITEs if (is_method("INVITE")) { setflag(1); # do accounting } # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } route(LOADBALANCE); route(RELAY); } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } # Reply to options if (uri==myself) { xlog("L_NOTICE","OPTIONS from $si:$sp\n"); if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { xlog("L_NOTICE","answering options $si:$sp\n"); options_reply(); } } } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails } route(RELAY); } else { if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # non loose-route, but stateful ACK; # must be ACK after a 487 or e.g. 404 from upstream server t_relay(); exit; } else { # ACK without matching transaction ... ignore and discard. exit; } } sl_send_reply("404","Not here"); } exit; } } # Handle SIP registrations route[REGISTRAR] { if(!is_method("REGISTER")) return; #sl_send_reply("404", "No registrar"); #t_relay(); if(!ds_select_dst("1", "4")) { sl_send_reply("404", "No registrar"); exit; } forward(); exit; } # Presence server route route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; sl_send_reply("404", "Not here"); exit; } route[LOADBALANCE] { #ds_select_dst(destination_set, algorithm) function chooses the destination for the call. For this it can use a lot of algorithms. #Alg. 0 is the default one that does the the choosing over the call ID hash #Alg. 4 is a Round-Robin #Alg. 10 is the one that chooses the destination based on the minimum load of all destinations if(!ds_select_dst("1", "4")) { #if we are here that means no destination is available. We notify the user by 404 and exit the script. xlog("L_NOTICE", "No destination available!"); send_reply("404", "No destination"); exit; } xlog("L_NOTICE", "Routing call to <$ru> via <$du>\n"); #set the no_reply_recieved timeout to 2 second ... adjust the value to your need #note: The first value "0" is invite timeout .. we do not need to change it #This means that is the selected media server fails to respond within 2 seconds the failure_route "MANAGE_FAILURE" is called #note: this implies that ale the signaling from media servers on the way back to the user goes through the proxy as well t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); return; } # manage failure routing cases failure_route[MANAGE_FAILURE] { # route(NATMANAGE); if (t_is_canceled()) { exit; } xlog("L_NOTICE", "Media server $du failed to answer, selecting other one!"); # next DST - only for 500 reply or local timeout (set by t_set_fr()) if (t_check_status("500") || t_branch_timeout() || !t_branch_replied()) { #we mark the destination Inactive and Probing ds_mark_dst("ip"); #select the new destination if(ds_next_dst()) { #again set local timeout for reply t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); route(RELAY); exit; } else { #last available node failed to reply, no other destinations available send_reply("404", "No destination"); exit; } } } route[RELAY] { xlog("L_NOTICE", "going to <$ru> via <$du>"); if (!t_relay()) { sl_reply_error(); } exit; } ``` and my dispatcher.list ``` # line format # id(int,auto) setid(int) destination(string) flags(int) priority(int) attrs(string) description(string) 1 sip:196.27.235.76:5060 1 sip:213.137.140.230:5060 ``` any help to understand these issues would be greatly appreciated. Cris --- Cristian Livadaru LcX IT Solutions Web: http://lcx.at/ Tel: +43 1 37 37 37 Fax: +43 1 37 37 37 - 25 **24/7 Support: 0900 474 455** (1,81€/Min)

2 3

Info: Kamailio World 2019 - First group of speakers
by Daniel-Constantin Mierla 18 Feb '19

18 Feb '19

Hello, a short note to let everybody know that we have published the details for the first group of speakers at Kamailio World 2019 (May 6-8, in Berlin) - you can read more about at: * https://www.kamailioworld.com/k07/2019/02/kamailio-world-2019-first-group-o… * https://www.kamailioworld.com/k07/speakers/ The target is to finish the review of the speaking proposals by end of the month, then start working on the schedule. We received a lot more than it can be accommodated, but we will try to select all that are very interesting by having several short sessions/lightning talks. There will be few new concepts, trying to engage more the participants as well as use better the evening time for social networking with a boat trip at the end of first day, in addition to the cocktail party on the second day. Hoping to meet many of you in Berlin at Kamailio World 2019! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Branches Routes
by Nicolas Breuer 18 Feb '19

18 Feb '19

Hello, We have a main route where we try multiple destinations (SIP Providers) one by one in case of failure. We modify the $ru in branch routes. I have to manipulate the $rU in the main route (adding 000 and strip 000) to create the second branch. Otherwise I have an error in Kamailio , is it expected ?? Feb 16 10:29:13 proxy2 /usr/sbin/kamailio[3837]: NOTICE: RU => 0003280033800 (Branch 0) * Adding 000 in main route Feb 16 10:29:13 proxy2 /usr/sbin/kamailio[3837]: NOTICE: RU => 3280033800 (Branch 0) * Strip "000" in main route * Timeout of first provider (going to main route again with an other branch) Feb 16 10:29:15 proxy2 /usr/sbin/kamailio[3840]: NOTICE: RU => 0003280033800 (Branch 1) Feb 16 10:29:15 proxy2 /usr/sbin/kamailio[3840]: NOTICE: RU => 3280033800 (Branch 1) * Call OK I will now remove the prefix & strip command in main route Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: RU => 3280033800 (Branch 0) Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: RU => 3280033800 (Branch 0) Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: Branch to sip:3280033800@XXXXXXXXXXX * Timeout Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: NOTICE: RU => 3280033800 (Branch 1) Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: NOTICE: RU => 3280033800 (Branch 1) Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: tm [tm.c:1548]: _w_t_relay_to(): t_forward_noack failed Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (6/SL) Any suggestions ?

3 4

kamailio with oracle database
by eyas barhouk 17 Feb '19

17 Feb '19

hello dears i'm trying to run kamailio 5.1.7 with Oracle database and after building it from source with the needed module and installing Oracle Instant Client when i'm trying to run kamailio i get the following Error : ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/local/lib64/kamailio/modules/db_oracle.so>: libclntsh.so.12.1: cannot open shared object file: No such file or directory so is there any way to make the libclntsh.so.12.1 open shared object ?? best regards Eyas

2 2

Re. SRTP configuration Rtpengine
by vinod mn 16 Feb '19

16 Feb '19

Hi I am not able to do SRTP configuration properly this the kamailio configuration *route[NATMANAGE] {* *rtpengine_manage("replace-origin replace-session-connection RTP/SAVP");}* I can see in SDP RTP/SAVP but still the packets are RTP. clients used linphone-android (media-encryption is SRTP ) and 3cx-windows-client

2 1

Log/Alerts Volume
by Daniel Greenwald 15 Feb '19

15 Feb '19

Curious how other folks are dealing with the volume of logs that Kamailio generates. We are currently sending them to syslog and alerting on WARN and above but the amount of alert noise is unbearable. For example (there are many variations): ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection reset by peer INVITE:WARNING: sanity [sanity.c:776]: check_parse_uris(): failed to parse >From header INVITE:ERROR: <core> [core/parser/parse_from.c:75]: parse_from_header(): b ad From header The fact that these are WARN/ERROR level and from core makes me wonder how we can possibly make alerts relevant. Any input would be appreciated. Thanks, Daniel G

3 3

Memory allocator was called from cdp: diameter_avp.c:365
by Denys Pozniak 15 Feb '19

15 Feb '19

Hello! I have faced with Kamailio (5.1.7) crashes, probably it is connected to cdp module, please check the source of issue: 14(5649) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [diameter1.dev] Receiver process doing init on new process... 14(5649) INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [diameter1.dev] 14(5649) INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [diameter1.dev] Receiver process starting up... 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: cdp [cdp_timer] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: cdp_avp [cdp_timer] 16(5651) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [1001] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: acc [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: uac [cdp_acceptor] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: ims_charging [cdp_timer] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: ims_dialog [cdp_timer] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: htable [cdp_acceptor] 15(5650) DEBUG: htable [htable.c:236]: child_init(): rank is (1000) 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: carrierroute [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: dispatcher [cdp_acceptor] 16(5651) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: cdp [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: cdp_avp [cdp_acceptor] 15(5650) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [1000] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: ims_charging [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: ims_dialog [cdp_acceptor] 15(5650) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 15(5650) DEBUG: cdp [tcp_accept.c:114]: create_socket(): create_sockets: create socket and bind for IPv4... 15(5650) WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 10.10.10.10 port 38680 15(5650) WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.10.10.10 port 38680 15(5650) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... [root@10-10-10-10 kamailio]# 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: kex [tcp main process] 17(5652) DEBUG: kex [kex_mod.c:157]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [srid-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: corex [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: tm [tcp main process] 17(5652) DEBUG: tm [callid.c:137]: child_init_callid(): callid: ' 46ac84cd57961b27-5652(a)10.10.10.10' 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: tmx [tcp main process] 17(5652) DEBUG: tmx [tmx_mod.c:261]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: sl [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: usrloc [tcp main process] 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [ulcx-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: registrar [tcp main process] 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [uloc-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ctl [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: acc [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: uac [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: htable [tcp main process] 17(5652) DEBUG: htable [htable.c:236]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: carrierroute [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: dispatcher [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: cdp [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: cdp_avp [tcp main process] 17(5652) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [-4] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ims_charging [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ims_dialog [tcp main process] 17(5652) DEBUG: <core> [core/local_timer.c:61]: init_local_timer(): timer_list between 0xa6e0a8 and 0xab20a8 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 7, 4, 0x7fbdd97d7bec), fd_no=0 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 8, 4, 0x7fbdd97d7c78), fd_no=1 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 9, 4, 0x7fbdd97d7d04), fd_no=2 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 10, 4, 0x7fbdd97d7d90), fd_no=3 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 11, 4, 0x7fbdd97d7e1c), fd_no=4 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 12, 4, 0x7fbdd97d7ea8), fd_no=5 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 13, 4, 0x7fbdd97d7f34), fd_no=6 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 15, 4, 0x7fbdd97d7fc0), fd_no=7 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 4, 4, 0x7fbdd97d804c), fd_no=8 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 16, 4, 0x7fbdd97d80d8), fd_no=9 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 17, 4, 0x7fbdd97d8164), fd_no=10 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 18, 4, 0x7fbdd97d81f0), fd_no=11 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 23, 4, 0x7fbdd97d827c), fd_no=12 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 24, 4, 0x7fbdd97d8308), fd_no=13 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 25, 4, 0x7fbdd97d8394), fd_no=14 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 26, 4, 0x7fbdd97d8420), fd_no=15 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829471] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: cdp [peermanager.c:263]: peer_timer(): peer_timer(): taking care of peers... 16(5651) DEBUG: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer diameter1.dev State 0 16(5651) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Closed Event Start 16(5651) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer diameter1.dev 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) INFO: cdp [receiver.c:875]: peer_connect(): peer_connect(): Trying to connect to 10.10.10.20 port 3868 16(5651) INFO: cdp [receiver.c:954]: peer_connect(): peer_connect(): Peer diameter1.dev:3868 connected 14(5649) DEBUG: cdp [receiver.c:702]: receive_loop(): select_recv(): There is something on the fd exchange pipe 14(5649) DEBUG: cdp [receiver.c:711]: receive_loop(): select_recv(): fd exchange pipe says fd [8] for peer 0x7fbdd979e368:[diameter1.dev] 14(5649) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Wait_Conn_Ack Event I_Rcv_Conn_Ack 14(5649) DEBUG: cdp [diameter_msg.c:184]: AAANewMessage(): AAANewMessage: param session received null and it's a request!! 14(5649) ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 14(5649) DEBUG: cdp [diameter_msg.c:81]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=184 14(5649) DEBUG: cdp [receiver.c:1013]: peer_send_msg(): peer_send_msg(): Pipe push [0x7fbdd97e0788] 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:756]: receive_loop(): select_recv(): There is something on the send pipe 14(5649) DEBUG: cdp [receiver.c:769]: receive_loop(): select_recv(): Send pipe says [0x7fbdd97e0788] 8 14(5649) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7fbdd97e0788) 257 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: cdp [peermanager.c:143]: log_peer_list(): --- Peer List: --- 16(5651) DEBUG: cdp [peermanager.c:145]: log_peer_list(): State of peer: Wait_I_CEA FQDN: diameter1.dev Port: 3868 Is dynamic 16(5651) DEBUG: cdp [peermanager.c:149]: log_peer_list(): ------------------ 16(5651) DEBUG: cdp [session.c:396]: cdp_sessions_log(): ------- CDP Sessions ---------------- 16(5651) DEBUG: cdp [session.c:431]: cdp_sessions_log(): ------------------------------------- 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 1 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:579]: do_receive(): receive_loop(): [diameter1.dev] Recv Version 1 Length 172 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 2 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:1107]: receive_message(): receive_message(): [diameter1.dev] Recv msg 257 14(5649) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Wait_I_CEA Event I_Rcv_CEA 14(5649) DEBUG: cdp [peerstatemachine.c:698]: count_Supported_Vendor_Id_AVPS(): Found 1 Supported_Vendor AVPS14(5649) DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 0 of maximum 1 14(5649) DEBUG: cdp [peerstatemachine.c:750]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 14(5649) DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 1 of maximum 1 14(5649) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7fbdd97e0788) 257 14(5649) CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(28af, abcdefed)[0x7fbdd97e0c98:0x7fbdd97e0cd0]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec from core/mem/q_malloc.c:504. 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829472] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 15(5650) DEBUG: cdp [tcp_accept.c:221]: accept_loop(): accept_loop(): No connection attempts 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829473] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 17(5652) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 24 17(5652) DEBUG: <core> [core/tcp_main.c:3513]: handle_ser_child(): dead child 14, pid 5649 (shutting down?) 17(5652) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6dee0, 24, -1, 0x0) fd_no=16 called 0(5635) ALERT: <core> [main.c:739]: handle_sigs(): child process 5649 exited by a signal 6 0(5635) ALERT: <core> [main.c:742]: handle_sigs(): core was generated 0(5635) INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD 0(5635) DEBUG: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD 16(5651) INFO: <core> [main.c:819]: sig_usr(): signal 15 received GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New LWP 5649] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `kamailio -f kamailio.cfg -E'. Program terminated with signal 6, Aborted. #0 0x00007fbde6015207 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7_6.3.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_6.x86_64 libcom_err-1.42.9-13.el7.x86_64 libgcc-4.8.5-36.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 mariadb-libs-5.5.60-1.el7_5.x86_64 openssl-libs-1.0.2k-16.el7.x86_64 pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb) bt full #0 0x00007fbde6015207 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007fbde60168f8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x0000000000673469 in qm_debug_check_frag (qm=0x7fbdd94fd000, f=0x7fbdd97e0c98, file=0x7fbdde6bb992 "cdp: diameter_avp.c", line=365, efile=0x7dc6b7 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 __FUNCTION__ = "qm_debug_check_frag" #3 0x00000000006765ec in qm_free (qmp=0x7fbdd94fd000, p=0x7fbdd97e0cd0, file=0x7fbdde6bb992 "cdp: diameter_avp.c", func=0x7fbdde6bd478 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7fbdde6bb7c0 "cdp") at core/mem/q_malloc.c:504 qm = 0x7fbdd94fd000 f = 0x7fbdd97e0c98 size = 140730526467984 next = 0x7a8db8 prev = 0x7a8db8 __FUNCTION__ = "qm_free" #4 0x0000000000680148 in qm_shm_free (qmp=0x7fbdd94fd000, p=0x7fbdd97e0cd0, file=0x7fbdde6bb992 "cdp: diameter_avp.c", func=0x7fbdde6bd478 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7fbdde6bb7c0 "cdp") at core/mem/q_malloc.c:1268 No locals. #5 0x00007fbdde696e61 in AAAFreeAVP (avp=0x7ffe610a0860) at diameter_avp.c:365 __FUNCTION__ = "AAAFreeAVP" #6 0x00007fbdde65c88f in AAAFreeAVPList (avpList=0x7fbdd97e07d8) at diameter_msg.c:396 avp_t = 0x7fbdd97e0cd0 avp = 0x7fbdd97e0bb8 #7 0x00007fbdde65cc4c in AAAFreeMessage (msg=0x7ffe610a0910) at diameter_msg.c:416 __FUNCTION__ = "AAAFreeMessage" #8 0x00007fbdde63f05e in Process_CEA (p=0x7fbdd979e368, cea=0x7fbdd97e0788) at peerstatemachine.c:804 avp = 0x7fbdd97e10b0 #9 0x00007fbdde638223 in sm_process (p=0x7fbdd979e368, event=I_Rcv_CEA, msg=0x7fbdd97e0788, peer_locked=0, sock=8) at peerstatemachine.c:166 result_code = -563425872 next_event = 32701 msg_received = 0 __FUNCTION__ = "sm_process" #10 0x00007fbdde6874be in receive_message (msg=0x7fbdd97e0788, sp=0x7fbde59538b0) at receiver.c:1147 avp1 = 0xde6b2c50 avp2 = 0x7fbdd97e0990 __FUNCTION__ = "receive_message" #11 0x00007fbdde67c5bb in do_receive (sp=0x7fbde59538b0) at receiver.c:598 cnt = 152 n = 152 version = 1 dst = 0x7fbdd97e1164 "" dmsg = 0x7fbdd97e0788 __FUNCTION__ = "do_receive" #12 0x00007fbdde68038e in receive_loop (original_peer=0x7fbdd979e368) at receiver.c:805 rfds = {__fds_bits = {256, 0 <repeats 15 times>}} efds = {__fds_bits = {0 <repeats 16 times>}} tv = {tv_sec = 0, tv_usec = 999998} n = 1 max = 21 cnt = 1 msg = 0x0 sp = 0x7fbde59538b0 sp2 = 0x7fbde59538b0 p = 0x7fbdd979e368 fd = 8 fd_exchange_pipe_local = 21 __FUNCTION__ = "receive_loop" #13 0x00007fbdde679aec in receiver_process (p=0x7fbdd979e368) at receiver.c:464 ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "receiver_process" #14 0x00007fbdde62a7d5 in diameter_peer_start (blocking=0) at diameter_peer.c:289 pid = 0 k = -1 p = 0x7fbdd979e368 __FUNCTION__ = "diameter_peer_start" #15 0x00007fbdde61c9a8 in cdp_child_init (rank=0) at cdp_mod.c:243 __FUNCTION__ = "cdp_child_init" #16 0x000000000053b6b1 in init_mod_child (m=0x7fbde5885150, rank=0) at core/sr_module.c:943 __FUNCTION__ = "init_mod_child" #17 0x000000000053b353 in init_mod_child (m=0x7fbde5885dc8, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #18 0x000000000053b353 in init_mod_child (m=0x7fbde5886190, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #19 0x000000000053b353 in init_mod_child (m=0x7fbde58865d0, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #20 0x000000000053ba85 in init_child (rank=0) at core/sr_module.c:970 No locals. #21 0x0000000000424fe5 in main_loop () at main.c:1701 i = 4 pid = 5641 si = 0x0 si_desc = "udp receiver child=3 sock=10.10.10.10:5060\000\275\177\000\000\300\023\na\376\177\000\000\022\000\000\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000\200\000\000\000\000\000\263\215z", '\000' <repeats 13 times>, "\220\026\na\376\177\000\000\207\"\003\346\275\177\000\000\260yw\000\000\000\000\000\060;\223\345\275\177\000" nrprocs = 4 woneinit = 1 __FUNCTION__ = "main_loop" #22 0x000000000042b994 in main (argc=4, argv=0x7ffe610a1778) at main.c:2642 cfg_stream = 0x103a020 c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 0 proto = 0 options = 0x758c10 ":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 = 1364069336 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x0 st = {st_dev = 19, st_ino = 68292, st_nlink = 2, st_mode = 16832, st_uid = 995, st_gid = 994, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1550156643, tv_nsec = 630000000}, st_mtim = {tv_sec = 1550158563, tv_nsec = 502470819}, st_ctim = {tv_sec = 1550158563, tv_nsec = 502470819}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) version: kamailio 5.1.7 (x86_64/linux) 567df3 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: 567df3 compiled on 02:06:09 Feb 2 2019 with gcc 4.8.5 -- BR, Denys Pozniak

2 2

Assemble struct sip_uri back to string?
by Ivan Ribakov 15 Feb '19

15 Feb '19

Hi all, does anyone know if there is a C function available in some module/header that assembles parsed sip_uri struct back into a single buffer? I’ve been looking at msg_parser.h (where sip_uri struct is defined) and parse_uri.h, but I can’t see anything of that kind. Thanks in advance, Ivan

3 3

Fwd: pv_buffer_size config value actually ignored?
by Enrico Bandiera 14 Feb '19

14 Feb '19

---------- Forwarded message --------- From: Enrico Bandiera <enrico.bandiera(a)cloud.timenet.it> Date: mer 13 feb 2019 alle ore 09:18 Subject: Re: [SR-Users] pv_buffer_size config value actually ignored? To: Daniel-Constantin Mierla <miconda(a)gmail.com> Hello Daniel, yes we do use that $avp for a log line which is actually a big json, the $avp is composed by multiple jansson_append calls and at the end an xlog() calls prints it Could it also be that I'm miscalculating because of the encoding? 4K utf8 characters could be more than 4K (but I don't think there are so many multibytes characters to let it reach the 8K limit) Il giorno mer 13 feb 2019 alle ore 09:15 Daniel-Constantin Mierla < miconda(a)gmail.com> ha scritto: > Hello, > > where do you use that avp, because for the avp value itself, that buffer > is not used -- avp values are stored in shared memory. > > Do you use that avp in xlog() or other functions parameters? > > Cheers, > Daniel > On 13.02.19 09:10, Enrico Bandiera wrote: > > Hi, I'm having some strange issues with a somewhat big $avp value, when it > reaches a size of about 4K I get this error: > > 29(47) ERROR: <core> [core/pvapi.c:1452]: pv_printf(): no more space for > spec value > 29(47) ERROR: <core> [core/pvapi.c:1461]: pv_printf(): buffer overflow – > increase the buffer size... > > In the docs I read that the default pv_buffer_size is 8K, I still tried to > enforce it to something bigger and checked the logs to be sure it was set: > > 0(384) DEBUG: <core> [core/pvapi.c:2062]: pv_init_buffer(): PV print > buffer initialized to [40][16384] > > But still when reaching the 4K size inside the $avp that error comes out, > is there any limit I'm not aware of? > > Thanks, > Enrico. > > _______________________________________________ > Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com > Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com > >

2 6

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 14 Feb '19

14 Feb '19

Hi List, Can someone give a hint related to this issue, please? On other messages, I found that this problem may happen why variable $du is empty, but in my case looks that it's present: Config File: if (!t_relay()) { switch ($retcode) { case -1: xlogl("L_ERR", "[$cfg(route)] Generic Internal Error\n"); xlogl("L_ERR", "[$cfg(route)] | $du/$ru |\n"); break; Log File: [RELAY] Generic Internal Error [RELAY] | sip:192.168.180.23:15109/sip:1003@ 192.168.180.23:15109 | sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) Also, as I understand this may happen when there is a problem on the physical network, i'm not sure that is my case - because kamailio and asterisk are 2 VM's running on the same Physical Server, and both their interfaces are connected to the same Virtual Switch. There is no firewalls/selinux on those servers. Can someone help please?

2 1

Kamailio/Dispatcher failure routing to SRV record
by Jesse Strahn 13 Feb '19

13 Feb '19

Hi all, I'm hoping someone can help me with this as I am baffled. I have a server running Kamailio with dispatcher. I am trying to direct calls from kamailio to an SRV record but am receiving a 404 error on the calls. If I instead place one of the hostnames from the SRV record in my dispatcher.list, the call completes fine. Contents of dispatcher.list look like: 1 sip:bvr.production.instance:5060 Nslookup from the Kamailio server for SRV record: nslookup -type=SRV _sip._udp.bvr.production.instance Server: 10.0.0.2 Address: 10.0.0.2#53 Non-authoritative answer: _sip._udp.bvr.production.instance service = 1 10 5060 ip-10-100-79-143.production.instance. _sip._udp.bvr.production.instance service = 1 10 5060 ip-10-100-96-92.production.instance. Again, if I put 1 sip: ip-10-100-96-92.production.instance:5060 into the dispatcher.list, the call routes fine. Is there some configuration within Kamailio required to route to an SRV record in this way? I haven't found anything indicating that is the case. Any help is greatly appreciated. Thanks, Jesse

2 2

Mysql to hastable conversion
by Duarte Rocha 13 Feb '19

13 Feb '19

Greetings, I have Kamailio has an SBC and i'm using a MySQL database to store all the relevant configurations and settings regarding the NAP's, Users, Numbers, etc. That being said, i'm having lots of of performance issues originated by the queries. In order to solve that i think the best way to proceed would be to implement hashtables. However, i would like to keep Sql DB's for easier configuration and having them automatically transformed into hashtables. Is there a simple way to do this? As i see, the htable module is able to load from a DB, but i understand it, the table should be already in "hashtable form". Does kamailio has any way to solve this or should i use external tools? Best Regards, Duarte Rocha

2 1

kamailio with oracle data base
by eyas barhouk 13 Feb '19

13 Feb '19

Hello Community i'm trying to build kamailio on top of oracle D.B so is there any way to configure kamailio to deal with Oracle D.B and call functions from it ? Thanks in advance. Regards Eyas

4 9

Cannot get message routing for websockets "invalid" URI
by Sergey Safarov 13 Feb '19

13 Feb '19

I have configured websocket usage using this module description https://kamailio.org/docs/modules/devel/modules/websocket.html Added registrar and usrloc modules Registration saved using this block route[REGISTRAR] { if(!is_method("REGISTER")) return; if (!save("location")) { xlog("L_INFO", "Location save error\n"); sl_reply_error(); } } Now in database i can see WebRTC client registration { "jsonrpc": "2.0", "result": { "Domains": [{ "Domain": { "Domain": "location", "Size": 1024, "AoRs": [{ "Info": { "AoR": "1000", "HashID": 924766747, "Contacts": [{ "Contact": { "Address": "sips:1000@df7jal23ls0d.invalid ;rtcweb-breaker=no;transport=wss", "Expires": 155, "Q": -1, "Call-ID": "0c818ac1-5e77-bd4c-b7fe-a135d6c6a4bf", "CSeq": 61442, "User-Agent": "IM-client/OMA1.0 sipML5-v1.2016.03.04", "Received": "[not set]", "Path": "[not set]", "State": "CS_SYNC", "Flags": 0, "CFlags": 0, "Socket": "tls:192.168.2.10:7443", "Methods": -1, "Ruid": "uloc-5c643a67-4b56-1", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": 2, "Keepalive": 0, "Last-Keepalive": 1550074434, "Last-Modified": 1550074434 } }] } } ], "Stats": { "Records": 1, "Max-Slots": 1 } } }] }, "id": 19493 } Now I try deliver call to WebRTC client. Kamailio receives message INVITE sip:1001@192.168.30.2 SIP/2.0 Via: SIP/2.0/UDP 192.168.30.2:45060;rport;branch=z9hG4bK5gaK3B38egZQH Route: <sip:192.168.2.10> Max-Forwards: 70 From: "" <sip:0000000000@192.168.30.2>;tag=8e7Za8pD6pcKg To: <sip:1001@192.168.30.2> Call-ID: 989274f0-aa4d-1237-08a1-94b86deaeed5 CSeq: 483510 INVITE Contact: <sip:mod_sofia@192.168.30.2:45060> User-Agent: FreeSWITCH-mod_sofia/1.8.4+git-20181228T070140Z~a0377e9677~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 621 X-FS-Support: update_display,send_info Remote-Party-ID: <sip:0000000000@192.168.30.2 >;party=calling;screen=yes;privacy=off Expected that Kamailio using follow config block route message to WEbRTC client via websocket. route[FROM_FS] { record_route(); if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } route(RELAY); exit; } But really Kamailio try resolve "sips:1000@df7jal23ls0d.invalid" URI via DNS and deliver for non locally connected device 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=238 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=231 a=41 n=isflagset 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=232 a=5 n=route 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=266 a=24 n=record_route 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=281 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=267 a=25 n=lookup 3(19341) DEBUG: registrar [lookup.c:255]: lookup_helper(): contact for [1000] found by address 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=281 a=5 n=route 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=289 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=286 a=24 n=t_relay 3(19341) DEBUG: tm [t_lookup.c:1326]: t_newtran(): msg id=2 , global msg id=2 , T on entrance=0 3(19341) DEBUG: tm [t_lookup.c:483]: t_lookup_request(): start searching: hash=7468, isACK=0 3(19341) DEBUG: tm [t_lookup.c:441]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK72v4614F91BXr] 3(19341) DEBUG: tm [t_lookup.c:666]: t_lookup_request(): no transaction found 3(19341) DEBUG: tm [t_hooks.c:348]: run_reqin_callbacks_internal(): trans=0x7fbb0b1d0d40, callback type 1, id 0 entered 3(19341) DEBUG: <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 07ad473ba02a6d3a4f8753a378c102e8 3(19341) DEBUG: tm [t_funcs.c:324]: t_relay_to(): new INVITE 3(19341) DEBUG: tm [t_reply.c:596]: _reply_light(): reply sent out. buf=0x7fbb0f256750: SIP/2.0 100 trying -..., shmem=0x7fbb0b1e75d8: SIP/2.0 100 trying - 3(19341) DEBUG: tm [t_reply.c:607]: _reply_light(): finished 3(19341) DEBUG: <core> [core/dns_cache.c:527]: _dns_hash_find(): (_sips._tcp.df7jal23ls0d.invalid(31), 33), h=232 3(19341) DEBUG: <core> [core/resolve.c:967]: get_record(): skipping 1 NS (p=0x561007b83e71, end=0x561007b83ebc) 3(19341) DEBUG: <core> [core/resolve.c:980]: get_record(): parsing 0 ARs (p=0x561007b83ebc, end=0x561007b83ebc) 3(19341) DEBUG: <core> [core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (_sips._tcp.df7jal23ls0d.invalid, 33, 60, 1) 3(19341) DEBUG: <core> [core/dns_cache.c:701]: dns_cache_add(): adding _sips._tcp.df7jal23ls0d.invalid(31) 33 (flags=1) at 232 3(19341) DEBUG: <core> [core/dns_cache.c:527]: _dns_hash_find(): (df7jal23ls0d.invalid(20), 1), h=139 3(19341) DEBUG: <core> [core/resolve.c:967]: get_record(): skipping 1 NS (p=0x561007b83e66, end=0x561007b83eb1) 3(19341) DEBUG: <core> [core/resolve.c:980]: get_record(): parsing 0 ARs (p=0x561007b83eb1, end=0x561007b83eb1) 3(19341) DEBUG: <core> [core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (df7jal23ls0d.invalid, 1, 60, 1) 3(19341) DEBUG: <core> [core/dns_cache.c:701]: dns_cache_add(): adding df7jal23ls0d.invalid(20) 1 (flags=1) at 139 3(19341) ERROR: <core> [core/resolve.c:1698]: sip_hostport2su(): could not resolve hostname: "df7jal23ls0d.invalid" 3(19341) ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve "df7jal23ls0d.invalid" 3(19341) ERROR: tm [t_fwd.c:1735]: t_forward_nonack(): failure to add branches 3(19341) DEBUG: tm [t_funcs.c:334]: t_relay_to(): t_forward_nonack returned error -478 (-478) 3(19341) DEBUG: tm [t_funcs.c:352]: t_relay_to(): -478 error reply generation delayed 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=287 a=24 n=sl_reply_error 3(19341) ERROR: sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: Unresolvable destination (478/SL) 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=289 a=2 n=exit 3(19341) DEBUG: <core> [core/receive.c:353]: receive_msg(): request-route executed in: 12632 usec 3(19341) DEBUG: tm [t_lookup.c:1490]: t_unref(): delayed error reply generation(-478) 3(19341) DEBUG: tm [t_reply.c:1650]: cleanup_uac_timers(): RETR/FR timers reset 3(19341) DEBUG: tm [t_reply.c:596]: _reply_light(): reply sent out. buf=0x7fbb0f2571f0: SIP/2.0 478 Unresolv..., shmem=0x7fbb0b1e7860: SIP/2.0 478 Unresolv 3(19341) DEBUG: tm [t_reply.c:607]: _reply_light(): finished Looks I missed some thing in message routing, But cannot find what. Please point me how to properly route call for this case.

1 0

$HN(d) null when DNS cache is enabled
by Julien Klingenmeyer 13 Feb '19

13 Feb '19

Hello, I have a small question regarding the internal DNS resolver. Here is my current Kamailio DNS configuration: dns_try_naptr=on use_dns_failover=yes use_dns_cache=yes I need the $HN variable inside my script and it appeared while testing that $HN(d) was null (and consequently $HN(f) was only containing the hostname part of the FQDN). I know /etc/hosts file is bypassed when the DNS cache is activated, so I thought Kamailio was using the domain parameter set in the /etc/resolv.conf file in such cases in order to get the domain. But it was not. I figured out Kamailio correctly retrieves the domain name as long as it is explicitly part of the /etc/hostname file. Is my understanding correct or am I wrong somewhere? What if /etc/hostname does not contain the domain name but hostname only? Thanks! Cheers Julien

1 0

pv_buffer_size config value actually ignored?
by Enrico Bandiera 13 Feb '19

13 Feb '19

Hi, I'm having some strange issues with a somewhat big $avp value, when it reaches a size of about 4K I get this error: 29(47) ERROR: <core> [core/pvapi.c:1452]: pv_printf(): no more space for spec value 29(47) ERROR: <core> [core/pvapi.c:1461]: pv_printf(): buffer overflow – increase the buffer size... In the docs I read that the default pv_buffer_size is 8K, I still tried to enforce it to something bigger and checked the logs to be sure it was set: 0(384) DEBUG: <core> [core/pvapi.c:2062]: pv_init_buffer(): PV print buffer initialized to [40][16384] But still when reaching the 4K size inside the $avp that error comes out, is there any limit I'm not aware of? Thanks, Enrico.

2 1

memory issue with jsonrpc
by Benjamin Roy 12 Feb '19

12 Feb '19

Hi, I'm hoping someone can guide me in the right direction. In kamailio 5.2.1 I'm getting the following memory errors after a while (hours or days) of sending messages with jsonrpc. Restarting kamailio clears them for a while. Any suggestions on what I should change, or how to better identify the issue? 24(6177) ERROR: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7f1cbe6fd000, 5712); Free fragment not found! 24(6177) ERROR: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7f1cbe6fd000, 5712) called from tm: h_table.c: build_cell(339), module: tm; Free fragment not found! 24(6177) ERROR: tm [uac.c:422]: t_uac_prepare(): short of cell shmem 24(6177) ERROR: pua [send_publish.c:700]: send_publish(): in t_request tm module function 24(6177) ERROR: pua_rpc [pua_rpc.c:280]: pua_rpc_publish_mode(): pua send_publish failed I have these buffer values in the config file tcp_rd_buf_size=65536 pv_buffer_size=32768 and I'm running kamailio with these memory options "-m 1024 -M 16" The jsonrpc message I'm sending look like this { "jsonrpc": "2.0", "method": "pua.publish", "params": [ "sip:172.1.1.3:5060;transport=tcp", "300", "reg", "application/reginfo+xml", ".", ".", ".", ".", "<?xml version='1.0' ?> <reginfo state='partial' version='0' xmlns='urn:ietf:params:xml:ns:reginfo' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> <registration aor='sip:55555@uw.edu' id='a19685' state='active'> <contact duration-registered='906' event='registered' id='c19685--1732979172--1829864152-2' q='1.0' state='active'> <uri>sips:55555@172.1.2.4:62270;transport=tls;avaya-sc-enabled</uri> <elin></elin> </contact> </registration> </reginfo> " ], "id": 1 } Thanks, -Ben

2 3

Programmatically modify SIP Requests/Responses in Kamailio
by Filippos Vasilakis 12 Feb '19

12 Feb '19

Hi, First of all I would like to congratulate and thank everyone who has worked in Kamailio. It looks like an awesome tool. I am starting a side project and I am not very familiar with Kamailio although I know SIP and VoIP in general, so I am more looking for answers that tell me if it's possible or not what I am asking along with some hints on how/where to look. Is there a way to filter/forward/modify(through the headers) incoming SIP requests and Kamailio SIP responses programmatically in Kamailio ? I have seen that you can run embedded code like Ruby, but I wonder if this is for simple things or more complex stuff which probably is in my case since there will be plenty of business logic to figure out what action to take with a SIP request. I have also found the EVAPI that is supposed to be handle events through TCP but not much more info available. So to sum up, is there a way to filter/forward/modify incoming SIP requests and create responses programmatically in Kamailio ? If yes, what's the proper way of doing that ? If no, any idea where I should look for that? Thanks, Filippos

2 1

Kamailio modules that can be used in Lua
by Leonid Fainshtein 12 Feb '19

12 Feb '19

Hello, I am checking a possibility to replace the traditional cfg script with a Lua script. In the app_lua module documentation there is a relatively short list of modules that can be registered to Lua. The modules nathelper, rtpproxy, topoh and many others don't appear in the list. Does it mean that it is not possible to use that modules in Lua? Best regards, Leonid Fainshtein Xorcom Ltd

2 1

Repository for automatic deployment of Kamailio
by Gholamreza Sabery 11 Feb '19

11 Feb '19

Hi, A few years ago, I developed an Ansible repository for automatic deployment of Kamailio. Recently, I added some new features, and now you can deploy the playbooks on Docker containers. I think it is a good starting point for anyone who wants to deploy and use Kamailio for the first time. Link of the repository: https://github.com/ghrst/Kamailio-HA Regards Gholamreza Sabery Tabrizy

2 1

Kamailio TOPOS fail
by Marcos Pytel 11 Feb '19

11 Feb '19

Hi, When I activate the TOPOS function, the Kamailio lb fail. This is the traceback Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) backtrace #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f66d5aab42a in __GI_abort () at abort.c:89 #2 0x00007f66d5ae7c00 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f66d5bdb305 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x00007f66d5b701f7 in __GI___fortify_fail (msg=msg@entry=0x7f66d5bdb29c "buffer overflow detected") at fortify_fail.c:30 #4 0x00007f66d5b6e330 in __GI___chk_fail () at chk_fail.c:28 #5 0x00007f66b867e097 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=0x7f66b8892524 <_tps_redis_cbuf+4>) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #6 tps_redis_load_branch (msg=<optimized out>, md=<optimized out>, sd=0x7ffed3993d30, mode=<optimized out>) at topos_redis_storage.c:744 #7 0x00007f66b88b35c0 in tps_request_received (msg=msg@entry=0x7ffed3995f80, dialog=dialog@entry=1) at tps_msg.c:786 #8 0x00007f66b88b9255 in tps_msg_received (evp=<optimized out>) at topos_mod.c:332 #9 0x000055e1dc07da88 in sr_event_exec (type=<optimized out>, evp=<optimized out>) at core/events.c:211 #10 0x000055e1dc0415f5 in receive_msg ( buf=buf@entry=0x55e1dc511d40 <buf> "BYE sip:atpsh-5c4b0f6e-25b2-9@10.10.10.2 SIP/2.0\r\nVia: SIP/2.0/UDP 10.10.10.1:5060;branch=z9hG4bK898122669\r\nFrom: <sip:2972426338@10.10.10.1>;tag=3296734298\r\nTo: <sip:414533@10.10.10.2>;tag=03D2CCF0-5"..., len=381, rcv_info=rcv_info@entry=0x7ffed3996980) at core/receive.c:157 #11 0x000055e1dbf5e6e3 in udp_rcv_loop () at core/udp_server.c:554 #12 0x000055e1dbef3a9f in main_loop () at main.c:1619 #13 0x000055e1dbeea8cb in main (argc=<optimized out>, argv=0x7ffed3996f38) at main.c:2638 This is a Kamailio error? I can fix it? Thanks. Marcos.

4 6

reg_fetch_contacts and t_relay usage
by Володимир Іванець 11 Feb '19

11 Feb '19

Hello! I'm using *reg_fetch_contacts* function to get information about all contacts. This allows to define which contacts should receive the call. My question is if it's possible to choose only one contact before *t_relay* is called? Or *reg_fetch_contacts* call and verification should be done after *t_relay* in all branches and those which are not needed should be stopped? Thanks a lot!

2 2

rtpengine not listening on specified port range
by Narayan P 11 Feb '19

11 Feb '19

Hello, I am starting the rtpengine through this command,but rtpengine is not listening on the specified port range.It is listening on some other port outside of this.Here first IP is private IP and the second IP is public one.So issue is with audio.Can you please let me know what exactly I am missing. rtpengine --interface=172.20.xx.xxx\!34.209.1.xx -f -m 16384 -M 16884 -E --listen-ng=127.0.0.1:22222 & Any suggestion will be highly appreciated. Thanks, Narayan NP

2 2

trace sip msg topos
by Giuseppe Pandolfi 11 Feb '19

11 Feb '19

Hi All, is it possible print sip msg after stripping by topos module? I have need to print sip msg stripped by topos in syslog. Thanks

4 3

rtpengine not listening on specified port range
by Narayan P 11 Feb '19

11 Feb '19

Hello, I am starting the rtpengine through this command,but rtpengine is not listening on the specified port range.It is listening on some other port outside of this.Here first IP is private IP and the second IP is public one.So issue is with audio.Can you please let me know what exactly I am missing. rtpengine --interface=172.20.xx.xxx\!34.209.1.xx -f -m 16384 -M 16884 -E --listen-ng=127.0.0.1:22222 & Any suggestion will be highly appreciated. Thanks, Narayan

1 0

rat-proxy issue
by aroosa satti 10 Feb '19

10 Feb '19

Hi! I have issue regarding my rtpproxy.I have start it but it does't work and give error like Feb 9 02:46:50 ns1 ./kamailio[3682]: NOTICE: <core> [main.c:692]: handle_sigs(): Thank you for flying kamailio!!! Feb 9 02:46:53 ns1 ./kamailio[4318]: ERROR: <core> [main.c:1165]: parse_phostport(): bad protocol in unix:/var/run/rtpproxy.sock these are the issue I will be grateful for you if you solve this problem. kind regards Aroosa Satti

2 1

how to differentiate branches in parallel call forking
by Koray Vatansever 09 Feb '19

09 Feb '19

Hi, I'm trying to implement parallel call forking scenario. Since target clients have different media profiles, I need to set different rtpengine options for those forked calls. So according to the rtpengine module documentation, I set via-branch option on request and response, '1' and '2' respectively ('auto' option is not working. There is no code implementing this parameter). However all forked branches have the same via branch id which is the incoming INVITE's via branch id. As a result, rtpengine thinks that all the offers belong to the same session I guess. It seems I have only 'extra' option with extra_pv_id variable. In order to use it, I need an elegant way to differentiate forked branches in request and response processing. I would appreciate any suggestion.

1 1

rtpproxy issues
by aroosa satti 08 Feb '19

08 Feb '19

Hi! I have issue regarding my rtpproxy.I have start it but it does't work and give error like Feb 9 02:46:50 ns1 ./kamailio[3682]: NOTICE: <core> [main.c:692]: handle_sigs(): Thank you for flying kamailio!!! Feb 9 02:46:53 ns1 ./kamailio[4318]: ERROR: <core> [main.c:1165]: parse_phostport(): bad protocol in unix:/var/run/rtpproxy.sock these are the issue I will be grateful for you if you solve this problem. kind regards Aroosa Satti

1 0

Kamailio modules that can be used in Lua
by Leonid Fainshtein 08 Feb '19

08 Feb '19

Hello, I am checking a possibility to replace the traditional cfg script with a Lua script. In the app_lua module documentation there is a relatively short list of modules that can be registered to Lua. The modules nathelper, rtpproxy, topoh and many others don't appear in the list. Does it mean that it is not possible to use that modules in Lua? Best regards, Leonid Fainshtein

3 2

Waiting for calls
by Mark Hall 08 Feb '19

08 Feb '19

Hi, I am using Kamailio as a gateway for inbound calls to a group of Asterisk servers. One particular call scenario involves matching pairs of calls. Originally I was just sending the calls through to Asterisk for processing (including the 'matching up'), but there is a further requirement that the first received call must not be answered until its matching call arrives - and this is a little awkward in Asterisk, especially if there will be many calls. I thought of t_suspend/t_continue functionality in Kamailio. I have implemented this: CallA arrives. Send 180-ringing Use ds_select_dst() to choose an Asterisk to handle the paired calls Store destination and other data in an htable so that I can match the call later. Invoke t_suspend() for CallA. What I have implemented when the matching call arrives is this: CallB arrives (and some logic matches it to the suspended CallA). Invoke t_continue('id','label','CONTINUE_CALL'); so that CallA is now released and the route ends in t_relay() to send it on to Asterisk. Set $du on CallB to match the destination, then t_relay() this call to send it on to the same Asterisk. The solution almost works, but there is a problem. The t_relay() for CallA is fine, and the call is forwarded. When the script runs the t_relay() for CallB, I get this logged: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (6/SL) AND after each call I notice an extra transaction stuck in Kamailio (when I use kamctl rpc tm.list). Can anyone point out where my Kamailio/SIP understanding has let me down? Many Thanks, Mark Hall

2 2

Re: [SR-Users] TLS challenge
by Gertjan Wolzak 07 Feb '19

07 Feb '19

Hello Kamailions, Julien, thank you for the help, I have added the letsencrypt ca certificate to the ca list, still no dice. So, still got lots of questions, but after my last booboo going to do some more research and testing. When I have no more hair left will get back to the list. Thanks for now. Rgds, Gertjan Wolzak

2 1

ERROR : EAGAIN and write queue full or failed for tcp Connection
by YASIN CANER 07 Feb '19

07 Feb '19

Hello, Kamailio gave this error that couldnt bind tcp connection other side. Thanks Yasin CANER Kamailio IPv6:TCP: -----> IPv6:TCP Kamailio -----> X ERROR XXXX IPv6:TCP Kamailio IPv6::C IPv6::8 IPv6::5 LOGS: 7(15781) DEBUG: <core> [core/msg_translator.c:2937]: create_via_hf(): id added: <;i=1>, rcv proto=2 7(15781) DEBUG: <core> [core/msg_translator.c:162]: check_via_address(): (FD61:C23C:B3B6:0:0:0:0:C, [FD61:C23C:B3B6:0:0:0:0:C], 0) 7(15781) DEBUG: <core> [core/tcp_main.c:1977]: tcp_send(): no open tcp connection found, opening new one 7(15781) DEBUG: <core> [core/ip_addr.c:242]: print_ip(): tcpconn_new: new tcp connection: fd61:c23c:b3b6:0:0:0:0:5 7(15781) DEBUG: <core> [core/tcp_main.c:1229]: tcpconn_new(): on port 5060, type 2 7(15781) DEBUG: <core> [core/tcp_main.c:1539]: tcpconn_add(): hashes: 507:2382:0, 2 7(15781) DEBUG: <core> [core/tcp_main.c:2873]: tcpconn_1st_send(): pending write on new connection 0x7fd15b5e7c98 (-1/1483 bytes written) (err: 11 - Resource temporarily unavailable) 7(15781) ERROR: <core> [core/tcp_main.c:2891]: tcpconn_1st_send(): [FD61:C23C:B3B6:0:0:0:0:5]:5060: EAGAIN and write queue full or failed for 0x7fd15b5e7c98 7(15781) DEBUG: <core> [core/tcp_main.c:3153]: tcpconn_chld_put(): destroying connection 0x7fd15b5e7c98 (2, -1) flags 0060 7(15781) ERROR: tm [../../core/forward.h:251]: msg_send_buffer(): tcp_send failed 7(15781) DEBUG: tm [t_fwd.c:1549]: t_send_branch(): send to FD61:C23C:B3B6:0:0:0:0:5:5060 (2) failed 7(15781) WARNING: tm [t_fwd.c:1567]: t_send_branch(): sending request on branch 0 failed CONF: dns_try_ipv6=yes dns_retr_time=1 dns_retr_no=1 dns_cache_flags=4 tcp_source_ipv6 = [fd61:c23c:b3b6::8] tcp_async=yes tcp_rd_buf_size=65536 tcp_wq_blk_size=3000 listen=tcp:[fd61:c23c:b3b6::8]:5060 tcp_connection_lifetime=3605 listen=tcp:[fd61:c23c:b3b6::8]:5060 ..... route[]{ remove_hf("Route"); #loose_route(); if (!is_method("INVITE")) return; $du="sip: mykamailio1.test:5060;transport=tcp"; if(!t_newtran()){ xlog("L_WARN"," Couldnt create new transaction \r\n"); sl_send_reply("503", "Service not available"); exit; } if(!t_relay()){ send_reply("503", "Service not available"); exit; } exit; }

4 7

Keep requests order
by Duarte Rocha 07 Feb '19

07 Feb '19

Greetings, I'm having some problems with keeping the order of the messages in Kamailio. In some cases i'm receiving an ACK for the first INVITE and immediately after that a RE-INVITE is sent by the client. What is happening is that the the ACK took double the time of the RE-INVITE to process and as a consequence, the RE-INVITE was relayed before the ACK. I have two questions : 1 - Is there a way to keep the order of the messages in a dialog, and if so, what are the downsides to it? 2 - The machine wasn't in a load state (only one concurrent call) and the ACK and the RE-INVITE should go roughly through the same processing methods and should take took the same time to be be relayed. What can be the reason for this? Best Regards, Duarte Rocha

4 7

Kamailio with RTPengine, allow source port of RTP to change during a call
by Laurent Schweizer 06 Feb '19

06 Feb '19

Hello, I'm using the RTPengine with Kamailio and I have a question for a specific case. I have some customer that are changing the source port of the RTP stream during the call ( no re-invite) I think it's more a NAT issue that a user agent issue... I see in the doc that I can handle this case with the "media handover" but in that case the rtpengine will allow a change of the source port but also of the source IP. Any possibility to allow only a change of the source port so source IP must still be the same ? Thanks BR Laurent

2 1

Kamailio failure routing to SRV Record
by Jesse Strahn 05 Feb '19

05 Feb '19

Hi all, I am trying to route requests from Kamailio to a private SRV record in AWS Route 53. If I setup the record as an A record and put the 3 destination sip server IPs in the record, Kamailio routes perfectly round-robinning between the 3 servers. However, If I switch my dispatcher.list over to the SRV record, the calls do not route and I get a 404 No Destination in my pcap. When I perform a `dig _sip._udp.pool.sip.servers` from the Kamailio server, it properly returns the hostnames of the 3 sip servers that the SRV record points to. I'm not sure if something in the Kamailio routing has to be changed to accommodate SRV record routing rather than A record? I have scoured the internet and can't really find much of anything. Would greatly appreciate any guidance. Thanks, Jesse

3 3

Error UAS
by Nicolas Breuer 05 Feb '19

05 Feb '19

Hello, How can we avoid these errors ? Feb 5 11:21:39 proxy1 /usr/sbin/kamailio[29563]: ERROR: tm [t_reply.c:1301]: t_should_relay_response(): status rewrite by UAS: stored: 408, received: 200 Thanks

2 1

TLS challenge
by Gertjan Wolzak 05 Feb '19

05 Feb '19

Hello Kamailions, Ive beent trying to configure a tls connection between kamailio servers, but looks like Im missing some knowledge. The situation: phone1 <> internet <> kamailio1 <internet> kamailio2<> internet <> phone2 The phones are yealink phones, they are connected using TLS v1.2, phone 1 registers at kamailio1 and phone2 registers at kamailio2. Both kamailio servers have an letsencrypt certificate. When the connection between the two kamailio servers is set as sip, a call from a phone1 to phone2 the singnaling is forwarded and rtp flows. When I set the connection between the two kamailio servers to tls, things go wrong.. or better said I go wrong. The kamailio log on the receiving kamailio(kamailio2) shows that things go wrong and where, but I just cant figure out how to solve it. The log shows that the tls connection will be handled by the TLS Default configuration, the CA certificate is missing, well unknown. 15(7209) DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 116.203.53.212 15(7209) DEBUG: <core> [core/tcp_main.c:999]: tcpconn_new(): on port 44153, type 3 15(7209) DEBUG: <core> [core/tcp_main.c:1309]: tcpconn_add(): hashes: 1805:3331:3809, 3 15(7209) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa77de0, 32, 2, 0x7ff9596d4b10), fd_no=23 15(7209) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa77de0, 32, -1, 0x0) fd_no=24 called 15(7209) DEBUG: <core> [core/tcp_main.c:4196]: handle_tcpconn_ev(): sending to child, events 1 15(7209) DEBUG: <core> [core/tcp_main.c:3878]: send2child(): selected tcp worker 1 8(7202) for activity on [tls:kamailio2:5061], 0x7ff9596d4b10 8(7202) DEBUG: <core> [core/tcp_read.c:1759]: handle_io(): received n=8 con=0x7ff9596d4b10, fd=9 8(7202) DEBUG: tls [tls_server.c:199]: tls_complete_init(): completing tls connection initialization 8(7202) DEBUG: tls [tls_server.c:228]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7ff959498600 ctx 0x7ff9594b6430 sn []) 8(7202) DEBUG: tls [tls_domain.c:724]: sr_ssl_ctx_info_callback(): SSL handshake started 8(7202) DEBUG: <core> [core/tcp_main.c:2460]: tcpconn_do_send(): sending... 8(7202) DEBUG: <core> [core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7ff9596d4b10 n=2637 fd=9 8(7202) DEBUG: <core> [core/tcp_main.c:2495]: tcpconn_do_send(): buf= 8(7202) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xac78a0, 9, 2, 0x7ff9596d4b10), fd_no=1 8(7202) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca 8(7202) ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7ff9596d4b10 r: 0x7ff9596d4b90 (-1) 8(7202) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xac78a0, 9, -1, 0x10) fd_no=2 called 8(7202) DEBUG: <core> [core/tcp_read.c:1683]: release_tcpconn(): releasing con 0x7ff9596d4b10, state -2, fd=9, id=3 (kamailio1]:44153 -> [kamailio1]:5061) 8(7202) DEBUG: <core> [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7ff9596d2ab0 15(7209) DEBUG: <core> [core/tcp_main.c:3308]: handle_tcp_child(): reader response= 7ff9596d4b10, -2 from 1 15(7209) DEBUG: tls [tls_server.c:667]: tls_h_close(): Closing SSL connection 0x7ff9596d2ab0 I assume I have configured tls.cfg partially correct, as the phones register and can make tls calls. What I find strange is this line: 8(7202) DEBUG: <core> [core/tcp_read.c:1683]: release_tcpconn(): releasing con 0x7ff9596d4b10, state -2, fd=9, id=3 (kamailio1]:44153 -> [kamailio1]:5061) Would the "[kamailio1]:5061" be the client configuration? So, what do I need to configure within the tls.cfg file so when a tls connection is initiated from the other server it will work. I have tried adding the other server as server within the tls.cfg, which does not work as kamailio is not listening on the ip address configured. When I add the server as a client in the tls.cfg as follows, the connection is handled by the default TLS configuration. [server:default] method = TLSv1.2 verify_certificate = no require_certificate = no private_key = /etc/letsencrypt/live/kamailio.kazlow.nl/privkey.pem certificate = /etc/letsencrypt/live/kamailio.kazlow.nl/fullchain.pem #ca_list = /etc/kamailio/tls/cacert.pem #crl = /etc/kamailio/tls/crl.pem [client:kamailio1:5061] method = TLSv1.2 verify_certificate = no require_certificate = yes certificate = /etc/kamailio/tls/fullchain.pem ca_list = /etc/kamailio/tls/cacert.pem # This is the default client domain, settings # in this domain will be used for all outgoing # TLS connections that do not match any other # client domain in this configuration file. # We require that servers present valid certificate. # [client:default] method = TLSv1.2 verify_certificate = no require_certificate = no ca_list = /etc/kamailio/tls/cacert.pem I have tried forcing the socket on the sending kamailio, but that does not work. Any feedback on what I am doing wrong or where I can find information to extend my knowledge would be appreciated. Rgds, Gertjan Wolzak

2 1

How to chain proxies with Route header and loose_route()
by Ivan Ribakov 05 Feb '19

05 Feb '19

Assuming there are several proxies that have to be hopped sequentially to deliver the request and the order is determined dynamically (!), how can one achieve that behaviour in Kamailio? My understanding was that Route header is used for that - it allows to keep R-URI intact but still route the egress message elsewhere. Documentation of the loose_route() from RR module seems to confirm that. But the catch is that loose_route() will not pick up any Route header that I might add in the config via append_hf() due to the delayed lump processing (as explained in https://sourceforge.net/p/openser/bugs/277/#5f42). Thanks in advance for any help or ideas. Regards, Ivan

2 1

TLS traffic visualization HOWTO
by Giovanni Maruzzelli 04 Feb '19

04 Feb '19

# How to TRACE and visualize TLS and non-TLS SIP traffic in real time (thanks to Homer's Lorenzo Mangani for pointing me toward Frida) apt-get install python-pip pip install frida pip install hexdump wget https://raw.githubusercontent.com/google/ssl_logger/master/ssl_logger.py #first ssh terminal # create fifo pipe, then will send the content from fifo pipe to an sngrep without gui, which will be reading pcap from stdin, and sending eep packets to the other sngrep (third terminal) mkfifo /tmp/pipe cat /tmp/pipe | sngrep -N -q -H udp:127.0.0.1:5077 -I - #second ssh terminal # writes as pcap to fifo pipe what freeswitch writes and reads from ssl lib python ssl_logger_giova.py -pcap /tmp/pipe freeswitch #third ssh terminal # sngrep that receives packets from both the Ethernet device, and the eep packets sent by the other sngrep (eg, the tls packets ssl_logger grabs from freeswitch's ssl lib) sngrep -L udp:127.0.0.1:5077 (you may want to edit ssl_logger.py and change 228 to be 101 - LINKTYPE_IPV4 to be LINKTYPE_RAW ) -- Sincerely, Giovanni Maruzzelli OpenTelecom.IT cell: +39 347 266 56 18

2 2

Planning Fosdem 2019
by Daniel-Constantin Mierla 02 Feb '19

02 Feb '19

Hello, Fosdem 2019 is approaching, so I am writing to see if any of you plans to go to the event. If there is interest, we can try to organize again a dinner on Saturday evening, a tradition for our project at the past 10 editions or even more. Henning Westerholt will give a presentation about Kamailio in the RTC Devroom, I will be around as well. I know few more developers that plan to go to the event, so let's see who else from the community wants to join us. As usual, at Fosdem will be developers from other VoIP projects, like Asterisk, Janus, CGRates, Homer, Jitsi, ... At the past editions we typically had two "kamailio" events: 1) an "ad-hoc" developers meeting in the cantina (or other available room around) to discuss about short term plans for Kamailio -- time and place being decided as we meet there between us (expected in the afternoon of Saturday or during Sunday). 2) a dinner at a place nearby, with other VoIP folks joining us Reply if you plan to go to Fosdem and say if you want to join for a dinner. Just be aware that you have to pay for your food and drinks at the dinner, unless we are going to be surprised again by a generous sponsor that covers partially or completely to dinner. If you need more details about Fosdem, the website is: - https://fosdem.org Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

3 5

kamailio + asterisk + webrtc
by arish haque 01 Feb '19

01 Feb '19

Hi Daniel, Within a network above tech stack is working fine for VOIP calls. But when i am trying from outside there is no sign of RTP. Cmd for rtp - /sbin/rtpengine -p /var/run/rtpengine.pid --interface=192.168.1.249\!106.51.78.78 --listen-ng 127.0.0.1:60000 -m 50000 -M 55000 --log-level 6 --log-facility local1 106.51.78.78 - public ip 192.168.1.249 - priv ip (kamailio + RTPEngine) Kamailio config when call is b/w WebRTC --> WebRTC rtpengine_manage("trust-address replace-origin replace-session-connection direction=internal direction=external"); Here is SDP, captured on the client sitting outside. v=0 o=root 1133801452 1133801452 IN IP4 106.51.78.78 s=Asterisk PBX 16.0.0 c=IN IP4 106.51.78.78 t=0 0 m=audio 50196 UDP/TLS/RTP/SAVPF 0 8 111 9 126 a=maxptime:60 a=ice-ufrag:5e13a1292fc0b7163d49328b7516f763 a=ice-pwd:4fa5e003195492fa165020c81eff9346 a=candidate:Hc0a801ac 1 UDP 2130706431 192.168.1.172 46810 typ host a=candidate:Hc0a801ac 2 UDP 2130706430 192.168.1.172 46811 typ host a=connection:new a=setup:active a=fingerprint:SHA-256 AA:5A:51:BD:4C:53:65:E4:2B:EC:EB:BF:A9:07:DD:60:E3:46:D8:26:6D:04:C8:21:8B:B9:81:37:3A:EB:55:C0 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:111 opus/48000/2 a=rtpmap:9 G722/8000 a=rtpmap:126 telephone-event/8000 a=fmtp:126 0-16 a=sendrecv a=rtcp:50196 a=rtcp-mux a=ptime:20 a=candidate:T7Tqd3oKM4NvATH3 1 UDP 2097152255 106.51.78.78 50196 typ host Looking forward for help from you guys. Thanks & Regards, Arish Haque

1 0

dispatcher alg - 8
by Andrew Chen 31 Jan '19

31 Jan '19

Hey all, I need some more clarification on dispatcher alg 8: “8” - use first destination (good for failover). What is meant by "first destination"? How is that defined if I have more than one carrier. More specifically in our case for some PSTN locations we have this setup: primary carrier - 1 sip trunk backup carrier - 4 sip trunks or primary carrier - 4 sip trunks backup carrier - 1 sip trunk the one that have 4 sip trunks is it going to round-robin through it? this is setup on our old 4.1.5 release. 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.*

2 2

IMS early media
by Tsvetan Filev 31 Jan '19

31 Jan '19

Hi all. I want to use SIP early media to play music to the caller in kamailio IMS installation like this: http://www.sharetechnote.com/html/IMS_SIP_EarlyMedia.html I looked a little bit but didn't find ready solution. The information is vague on this topic. Should this be done through a module or application server ? May I need to handle ringing in onreply_route and send OK with SDP to the caller in SCSCF ? Regards.

2 8

Kamailio/dispatcher routing with SRV record
by Jesse Strahn 31 Jan '19

31 Jan '19

Is it possible to route to the back-end SIP servers via DNS SRV record rather than specifying multiple IP addresses in the dispatcher list on the Kamailio server? Running in AWS and looking to be able to dynamically update my list of available sip servers if a server goes offline or if a server comes online. Have Cloudwatch/Lambda setup to manipulate the SRV record with the IP address additions or subtractions but when I try to put the SRV record as the destination in dispatcher, it fails.

2 2

Kamailio v5.1.7 Released
by Daniel-Constantin Mierla 31 Jan '19

31 Jan '19

Hello, Kamailio SIP Server v5.1.7 stable release is out. This is a maintenance release of the previous stable branch, 5.1, that includes fixes since the release of v5.1.6. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.7 or to v5.2.x series. For more details about version 5.1.7 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/01/kamailio-v5-1-7-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.1 is the previous stable branch. The latest stable branch is 5.2, at this time with v5.2.1 being released out of it. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Planing the release of Kamailio v5.1.7
by Daniel-Constantin Mierla 31 Jan '19

31 Jan '19

Hello, I am considering to release Kamailio v5.1.7 later this week, likely on Thursday, January 31, 2019. As usual, here come the notice to report any issue that you are aware of and not yet registered on the bug tracker in order to give them a chance to be analyzed and eventually fixed before the release. Also, take a look at the branch 5.1 in git and check if there are any missing commits from those you expected to be backported. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 1

Altering received parameter in Contact
by David Cunningham 30 Jan '19

30 Jan '19

Hello, I'm hoping someone can give advice on altering the received parameter in the Contact header on a reply. The situation is that a customer is REGISTERing using TLS, and our Kamailio replies with a 200 OK that includes a Contact header like this: Contact: <sip:123456789@xx.xx.102.10 :5061;transport=tls>;expires=3600;received="sip:xx.xx.102.10:36051;transport=TLS" The customer's device apparently had an issue with this, and the device manufacturer advises that they need the ";transport=TLS" on the received parameter removed. This sounds like a strange requirement, but it's what we've been told. Does anyone know how to alter this in a Kamailio configuration? Our system uses www_authorize to authenticate and is running Kamailio 4.2.1. Thanks in advance for any help! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

5 9

Kamailio TCP/TLS Connection getting failed
by arish haque 30 Jan '19

30 Jan '19

Hi All, I am running kamailio 5.2.x on CentOS 7. Call is happening but i am getting the below error continuously in kamailio logs. WARNING: websocket [ws_frame.c:228]: encode_and_send_ws_frame(): TCP/TLS connection get failed Jan 30 17:57:01 localhost /usr/local/sbin/kamailio[22097]: ERROR: websocket [ws_frame.c:765]: ping_pong(): sending keepalive Any clue of why this is happening? Thanks, Arish Haque

1 0

TSILO on Kamailio 5.2.0
by Володимир Іванець 29 Jan '19

29 Jan '19

Hello! I am trying to repeat awesome configuration provided by Federico Cabiddu https://www.youtube.com/watch?v=4XIrR9bwUkM but only got it to work partially. So I'm wondering if someone else has same problem as me on latest Kamailio? I have two clients configured on 100-test account. Only one is registered. When *ts_store()* is executed on INVITE I get: *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_store.c:80]: ts_store(): storing transaction 29157:1612520187 for r-uri: 100-test* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_hash.c:264]: insert_ts_urecord(): urecord entry 0x7f2bfcf7dd78* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_handlers.c:56]: ts_set_tm_callbacks(): registered TMCB for transaction 29157:1612520187* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_store.c:103]: ts_store(): transaction 29157:1612520187 (ruri: 100-test) inserted* *# kamcmd ts.dump*: *{* * Size: 2048* * R-URIs: {* * R-URI: 100-thirdlane* * Hash: 451001090* * Transactions: {* * Transaction: {* * Tindex: 29157* * Tlabel: 1612520187* * }* * }* * }* * Stats: {* * RURIs: 1* * Max-Slots: 1* * Transactions: 1* * }* *}* When second UAC registers, *ts_append("location", "$tU")* in route *PUSHJOIN* is executed. It throws following error: *Jan 28 19:18:10 test /usr/sbin/kamailio[11210]: ERROR: tsilo [tsilo.c:199]: ts_check_uri(): bad uri [100-test]* At same time running *kamcmd ts.lookup 100-test* command returns expected result: *{* * Transaction: {* * Tindex: 29157* * Tlabel: 1612520187* * }* *}* Thanks a lot!

2 2

Kamailio IMS Deployment
by Yağız AYDIN 29 Jan '19

29 Jan '19

Hello everyone, I'm new to Kamailio environment, and trying to implement Kamailio IMS services with FHoSS HSS on a single Ubuntu 18.04 . I have followed instructions on the Kamailio website, but faced some issues. I have managed to install FHoSS, but when I try to start HSS, i got following errors: [Thread-24] ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - StateMachine: Peer icscf.mnc001.mcc001.3gppnetwork.org:3869 not responding to connection attempt [Thread-24] ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - StateMachine: Peer scscf.mnc001.mcc001.3gppnetwork.org:3870 not responding to connection attempt I have started CSCFs by following commands: root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/pcscf/kamailio-pcscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:5060 Aliases: *: pcscf.mnc001.mcc001.3gppnetwork.org:* ************************************************ root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/scscf/kamailio-scscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:6060 Aliases: *: scscf.mnc001.mcc001.3gppnetwork.org:* *********************************************** root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/icscf/kamailio-icscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:4060 tcp: 10.3.0.188 [10.3.0.188]:4060 Aliases: *: icscf.mnc001.mcc001.3gppnetwork.org:* How do I ensure that CSCFs work? And also how can I troubleshoot error that I've faced on FHoSS. I have attached my config files. Any helps will be appreciated. Best regards, Yağız --

2 1

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 28 Jan '19

28 Jan '19

Hello, Can someone help me to understand this error given by TM Module? I have a Kamailio SIP Proxy running in front of a few Asterisk boxes. On average, he is processing 70-80 requests per second. The problem is that sometimes (90-100 times/day) - I see such errors in the logs: 500 I'm terribly sorry, server error occurred (1/SL) 477 Unfortunately error on sending to next hop occurred (477/TM) Trying to investigate this error - I found that this is happening randomly and for INVITES coming from the Asterisk Box. For ex, the INVITE below: 192.168.180.10 - Kamailio Server 192.168.180.36 - Asterisk Server INVITE sip:1001@192.168.180.10:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.180.36:5060;branch=z9hG4bK4624ab4e;rport Max-Forwards: 70 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Contact: <sip:anonymous@192.168.180.36:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE User-Agent: MYCOMPANY Date: Mon, 28 Jan 2019 16:01:56 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Type: application/sdp Content-Length: 251 v=0 o=SIP 2139556641 2139556641 IN IP4 192.168.180.36 s=MYCOMPANY PBX c=IN IP4 192.168.180.36 t=0 0 m=audio 14674 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv Kamailio is replying back with 100 Trying and then with 500/477 errors: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 And I cannot actually get what is wrong with this INVITE - and why Kamailio cannot process it? Other calls for the same extension are working fine, this is happening randomly and with different extensions. Load on the server is very low: [root@kamailio root]# nproc 8 [root@kamailio root]# uptime 17:49:15 up 8 days, 21:17, 6 users, load average: 0.66, 0.56, 0.52 [root@kamailio root]# free -m total used free shared buff/cache available Mem: 7981 4283 142 818 3556 2581 Swap: 6141 137 6004 [root@kamailio root]# ss -4 -n -l | grep 5060 udp UNCONN 0 0 192.168.180.10 :5060 *:* udp UNCONN 0 0 127.0.0.1:5060 *:* tcp LISTEN 0 128 192.168.180.10 :5060 *:* tcp LISTEN 0 128 127.0.0.1:5060 *:* In the kamailio logs I found that kamailio was able to get the contact address: kamailio[18168]: INFO: {INVITE (1) Contacts loaded for 1001} kamailio[18168]: INFO: {INVITE (1) t_next_contacts - Only one contact found for 1001, calling} kamailio[18168]: INFO: {INVITE (1) Next Hop: <192.168.180.211:3126>} I don't know how to reproduce this - I tried to disconnect the phone from the power source - and made a call to that extension, and it is giving timeouts - like it is supposed to be. What could be the problem and how I can fix it? Thank You.

1 0

Playing with Diameter - Error opening connection to :3868
by Steve Bucklin 28 Jan '19

28 Jan '19

Hello all, I am brand new to this list and I am also on a steep learning curve with Kamailio and Diameter.... so please be gentle as I am just starting! I am trying to look at the Diameter signaling and have a glimpse into the information passed. I have set up a compiled 5.2 on CentOS 7. I suspect that I am missing something obvious, but not sure what. I am seeing this error: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known It looks like the FQDN in the diameter.xml under 'peer' is not being resolved, as it is seeing port 3868? Any pointers would be greatly taken :-) Here is my diameter: <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="mra1.testservers.xxx" Realm="testservers.xxx" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="16" QueueLength="32" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <peer FGDN="mra2.testservers.xxx" Realm="testservers.xxx" proto="sctp" port="3868"/> <Acceptor port="3868" bind="192.168.1.20"/> <Auth id="16777251" vendor="10415"/>  <SupportedVendor vendor="10415" /> </DiameterPeer> And here is what I am getting on the startup: Jan 28 14:19:35 telco-lon1-02 kamailio: INFO: <core> [core/tcp_main.c:4722]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: <core> [main.c:2649]: main(): processes (at least): 29 - shm size: 67108864 - pkg size: 8388608 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:240]: cdp_child_init(): CDiameterPeer child starting ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22783]: INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:242]: cdp_child_init(): ... CDiameterPeer child started Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22790]: INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22784]: INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22786]: INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22793]: INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22794]: INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22796]: INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22788]: INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [] Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22791]: INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22792]: INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22785]: INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22787]: INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22795]: INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22782]: INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22789]: INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22797]: INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22802]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: WARNING: cdp [receiver.c:866]: peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known Thanks, Steve

2 2

database reconnection db_unixodbc
by Karthik Srinivasan 27 Jan '19

27 Jan '19

Hello, I am testing how kamailio reacts to various database conditions. One such condition is if the database engine is simply shut down (that is, database server process no longer running, tcp listening socket closed, etc...) I am utilizing the db_unixodbc module to connect to an Informix database engine. I am currently running on Kamailio version 5.0. I have a test query that executes against the database engine every 10 seconds. Here is what i have noticed if i shut down the database engine at some point after i run Kamailio. the first test query that attempts to run against the db engine fails; it tries to reconnect and fails. The second test query (10 seconds after the 1st) results in a SIG_CHILD and shuts down the entire Kamailio process. Has anyone experienced this? Is there a solution to this? Ideally the second query should also fail and return gracefully; and ideally queries continue to fail until the database engine is back up. See logs below: Jan 17 20:07:25 [29297]: INFO: (s) SQL query: FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:135]: db_unixodbc_submit_query(): rv=-1. Query= FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=08S01:1:-11020:[Informix][Informix ODBC Driver]Communication link failure. Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:59]: reconnect(): Attempting DB reconnect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:74]: reconnect(): failed to connect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=08002:1:0:[unixODBC][Driver Manager]Connection name in use Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=HY010:2:-11067:[Informix][Informix ODBC Driver]Function sequence error. Jan 17 20:07:25 [29297]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jan 17 20:07:25 [29297]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query FIRST TEST QUERY Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL ret: fail (-1) Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL res: no rows Jan 17 20:07:35 [29297]: INFO: (s) [123] SQL query: 10 seconds later the SECOND TEST QUERY (it's the same query as the first one) Jan 17 20:07:35 [29301]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 28 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:744]: handle_sigs(): child process 29297 exited by a signal 11 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:747]: handle_sigs(): core was not generated Jan 17 20:07:35 [29283]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jan 17 20:07:35 [29301]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29295]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29291]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29288]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29300]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29284]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29286]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29293]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29289]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29287]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29292]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29296]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29298]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29299]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29285]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29294]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29290]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29283]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Thank you, Karthik

2 5

Why kamailio can not be a consumer of RabbitMQ?
by CuiGang 26 Jan '19

26 Jan '19

Hello every one. I noticed that module RABBITMQ just implements the publish functions. It means kamailio can only as a producer of RabbitMQ. My question is Why RABBITMQ module not implement consumer functions? As NSQ, let kamailio can be a consumer receive messages from RabbitMQ. Regards. CuiGang cuigang0120(a)aliyun.com

2 1

DMQ errors
by Aleksandar Sosic 25 Jan '19

25 Jan '19

Hi, when I have only one node and dmq enabled I've got this errors: ``` 17(45) ERROR: dmq [notification_peer.c:337]: add_server_and_notify(): error adding notification node 17(45) ERROR: dmq [dmq_funcs.c:516]: ping_servers(): cannot retrieve initial nodelist from sip:dmq-router-service.alex.svc.cluster.local:5062 ``` On the second node booting after this one I don't get any of these errors. Is there any flag/option to turn off this error on the `cannot retrieve initial nodelist` in case I have only one node for a period of time? Thanks, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 2

Re: [SR-Users] kamailio-lb fails after topos enabled.
by Daniel Tryba 25 Jan '19

25 Jan '19

On Fri, Jan 25, 2019 at 10:19:45AM -0300, Marcos Pytel wrote: > Could you help me to catch the coredump file? Please keep the mailinglist in the loop. > When I execute bt full the systems shows "no symbols". What package i need to perform it? I don't know what the sipwise config is, but it if is (anything like) debian the normal kamailio package is strippped of debugging symbols. You'll need to install the debug package (kamailio-dbg in debian).

1 0

kamailio-lb fails after topos enabled.
by Marcos Pytel 25 Jan '19

25 Jan '19

Hi team! I'm using Kamailio version: kamailio 5.1.6 (x86_64/linux). When I enabled topos, after a few minutes i get this erros in the log file and the LB Service goes down.: Jan 24 13:20:21 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:21:36 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:29:06 sipwise lb[30135]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:31:36 sipwise lb[30133]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:34:41 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:43:06 sipwise lb[30134]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:45:21 sipwise lb[30136]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:06 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:21 sipwise lb[30136]: ERROR: topos [tps_storage.c:340]: tps_storage_link_msg(): bad sip message or missing Contact hdr Jan 24 13:47:35 sipwise lb[30163]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:738]: handle_sigs(): child process 30120 exited by a signal 6 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:741]: handle_sigs(): core was generated I attached the coredump file. I tried to get bt full but i think that i need something else to catch it. Thank you! Marcos.

2 2

ERROR while using KEMI - Python
by Prabhat Kumar 25 Jan '19

25 Jan '19

Hi, I am getting this error message while starting kamailio. Enviroment: OS- Ubuntu 16.04.5 LTS (Xenial Xerus) python 2.7 ERROR: app_python [app_python_mod.c:164]: mod_init(): failed to load python script ERROR: <core> [core/sr_module.c:990]: init_mod(): Error while initializing module app_python (/usr/local/lib64/kamailio/modules/app_python.so)

2 2

Error while installing kamailio
by Prabhat Kumar 25 Jan '19

25 Jan '19

I am getting this error while installing kamailio LD (gcc) [U kamcmd] kamcmd /usr/bin/ld: cannot find -lncurses collect2: error: ld returned 1 exit status ../../src//Makefile.rules:191: recipe for target 'kamcmd' failed make[3]: *** [kamcmd] Error 1 ERROR: make --no-print-directory -C ../../../utils/kamcmd install-if-newer failed ../../Makefile.modules:145: recipe for target 'install-utils' failed make[2]: *** [install-utils] Error 1 Makefile:511: recipe for target 'install-modules' failed make[1]: *** [install-modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.1/kamailio/src' Makefile:36: recipe for target 'install' failed make: *** [install] Error 2

2 1

Kamailio Ignore Re-INVITE
by Alvaro Araos 25 Jan '19

25 Jan '19

Hi, When receive a Re-INVITE with new Media IP and PORT, kamailio keeps sending RTP to the old IP PORT. Seems kamailio not update info to the rtpproxy. Saludos, ALVARO ARAOS MÉNDEZ Director de Tecnología en FONOIP +56 2 2947 9000 alvaro(a)fonoip.com | www.fonoip.com [1] Moisés Chacón 46, El Monte, RM Links: ------ [1] http://www.fonoip.com

2 1

presence_mwi body check problem
by Володимир Іванець 24 Jan '19

24 Jan '19

Hello! I'm trying to process PUBLISH on Kamailio (v. 5.2.1) but constantly getting "500 Server Internal Error" responce. For packet body: *Messages-Waiting: yes* *Message-Account: sip:100-test@172.16.30.151 <sip%3A100-test(a)172.16.30.151>* *Voice-Message: 1/2* ... debug output is: *kamailio: 2(27127) DEBUG: presence [event_list.c:348]: search_event(): start event= [message-summary/6]* *kamailio: 2(27127) DEBUG: presence [publish.c:351]: ki_handle_publish_uri(): SIP-If-Match header not found* *kamailio: 2(27127) DEBUG: presence [presentity.c:88]: generate_ETag(): etag= a.1548164100.27127.7.0 / 22* *kamailio: 2(27127) DEBUG: presence [publish.c:360]: ki_handle_publish_uri(): new etag = a.1548164100.27127.7.0* *kamailio: 2(27127) DEBUG: presence [publish.c:385]: ki_handle_publish_uri(): Expires header found, value= 16* *kamailio: 2(27127) ERROR: presence_mwi [add_events.c:110]: mwi_publ_handl(): check of body <Messages-Waiting: yes* *kamailio: Message-Account: sip:100-test@172.16.30.151 <sip%3A100-test(a)172.16.30.151>* *kamailio: Voice-Message: 1/2* *kamailio: > failed at character number 22* *kamailio: 2(27127) ERROR: presence [publish.c:480]: ki_handle_publish_uri(): in event specific publish handling* I'm not sure, but it appears to me that check in line 95 from https://github.com/kamailio/kamailio/blob/5.2/src/modules/presence_mwi/add_… is not passing. I was trying to add "\n" and "\r" to the end of each string but I always had failure on character number 22. Does anyone know how exactly PUBLISH packet body should look like? Thanks a lot!

2 4

Problem at Rx Interface - kamailio P-CSCF 5.1.6
by Valentin Christoph 23 Jan '19

23 Jan '19

Hi all, We are using kamailio 5.1.6, configured as P-CSCF, facing following problem. Please refer to the attached tshark trace, too. If during call setup (by simulated UAs) at the terminating P-CSCF the simulated PCRF rejects the Diameter AAR message (frame 46/47 at the attached trace), then the kamailio P-CSCF runs into a questionable behaviour. By calling the Rx_AAR() function in configuration, the processing of the 200 OK (frame 45) is suspended (by the ims_qos module) and then resumed with the receipt of the AAA message (frame 47). Now the ims_dialog module is called with the dlg_terminate("all", "reason") function, but the 200 OK has not yet been sent. The ims_dialog sends CANCEL downstream and 488 upstream. However, the 200 OK is sent additionally. We would rather have expected the ims_dialog module should send BYE in both directions. When we respond the CANCEL with 481 Call/Transaction does not exist (which we MUST according to RFC 3261), then we would expect the ims_dialog module at least now to react with BYE in both directions. Could you help? What's our misunderstanding? How could we proceed to get this issue fixed? Kind regards Christoph ____ Christoph VALENTIN Software Developer | R&D Core / SIP Core P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 1

MWI notification through pua.publish
by willy 23 Jan '19

23 Jan '19

Hello. Have anyone tried to use pua.publish to send MWI notification? Can it work at all? I'm sending request through jsonrpc server, but it is not dispatched by handle_publish. Thank you, Kirill

6 9

Maximum Number of Probed Gateways
by Duarte Rocha 23 Jan '19

23 Jan '19

Greetings, Is there a limitation to the number of Gateways probed by Dispatcher? I have several gateways configured to be probed, but the OPTIONS is only sent to the first 16? Is there a configuration regarding this? Thanks in advance, Duarte Rocha

2 2

Kamailio v5.1.6 crashes with rtpengine restarts
by Yufei Tao 23 Jan '19

23 Jan '19

Hi, I have been testing one Kamailio v5.1.6 instance with one rtpengine instance, using sipp playing media files at 40 cps (-r 40) with up to 1600 concurrent calls. During the load tests if rtpengine is pkill'ed/restarted a few times Kamailio would crash. It is quite repeatable and every time the backtrace from gdb points to the same place as shown below. However the same tests on Kamailio v5.0.7 with the same cfg files and the same rtpengine instance did not cause any crash. Here’s what I got from gdb backtrace for v5.1.6 using a dbg build: 2 core dump files: 1. UDP receiver processes 14483 {{{ [New LWP 14483] 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 0x00007fadfa824d8e in t_should_relay_response (Trans=0x7fadf4207730, new_code=200, branch=0, should_store=0x7ffd5038fce4, should_relay=0x7ffd5038fce0, cancel_data=0x7ffd5038fed0, reply=0x7fadfb545210) at t_reply.c:1282 1282 t_reply.c: No such file or directory. (gdb) bt #0 0x00007fadfa824d8e in t_should_relay_response (Trans=0x7fadf4207730, new_code=200, branch=0, should_store=0x7ffd5038fce4, should_relay=0x7ffd5038fce0, cancel_data=0x7ffd5038fed0, reply=0x7fadfb545210) at t_reply.c:1282 #1 0x00007fadfa829577 in relay_reply (t=0x7fadf4207730, p_msg=0x7fadfb545210, branch=0, msg_status=200, cancel_data=0x7ffd5038fed0, do_put_on_wait=1) at t_reply.c:1786 #2 0x00007fadfa82f54c in reply_received (p_msg=0x7fadfb545210) at t_reply.c:2537 #3 0x000000000054624b in do_forward_reply (msg=0x7fadfb545210, mode=0) at core/forward.c:747 #4 0x0000000000547e4c in forward_reply (msg=0x7fadfb545210) at core/forward.c:852 #5 0x000000000058e186 in receive_msg ( buf=0xa595a0 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 192.168.70.102;branch=z9hG4bKa042.afac8eb973f1dfad7a549af0ab1a8ccc.0, SIP/2.0/UDP 192.168.60.80:5060;branch=z9hG4bK-3750-978-0\r\nFrom: sipp < sip:Customer68@192.168.60.8"..., len=888, rcv_info=0x7ffd50390480) at core/receive.c:364 #6 0x00000000004af6b1 in udp_rcv_loop () at core/udp_server.c:554 #7 0x00000000004246ac in main_loop () at main.c:1619 #8 0x000000000042bd5c in main (argc=13, argv=0x7ffd50390b38) at main.c:2638 }}} 2. Main process 14468 {{{ [New LWP 14468] Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fadfbc77428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007fadfbc77428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007fadfbc7902a in __GI_abort () at abort.c:89 #2 0x000000000041a029 in sig_alarm_abort (signo=14) at main.c:646 #3 <signal handler called> #4 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:37 #5 0x00007fadf354e67d in futex_get (lock=0x7fadf3e94e50) at ../../core/parser/../mem/../futexlock.h:121 #6 0x00007fadf3561113 in mod_destroy () at rtpengine.c:1810 #7 0x000000000055132b in destroy_modules () at core/sr_module.c:832 #8 0x0000000000418c9f in cleanup (show_status=1) at main.c:521 #9 0x000000000041a313 in shutdown_children (sig=15, show_status=1) at main.c:663 #10 0x000000000041cfa5 in handle_sigs () at main.c:768 #11 0x0000000000425fb5 in main_loop () at main.c:1752 #12 0x000000000042bd5c in main (argc=13, argv=0x7ffd50390b38) at main.c:2638 }}} The parameters for rtpengine: {{{ loadmodule "rtpengine.so" modparam("rtpengine", "db_url", "text:///usr/share/kamailio/dbtext/kamailio") modparam("rtpengine", "hash_table_size", 4) modparam("rtpengine", "setid_default", 1) modparam("rtpengine", "rtpengine_disable_tout", 20) modparam("rtpengine", "rtpengine_retr", 1) modparam("rtpengine", "setid_avp", "$avp(setid)") modparam("rtpengine", "rtp_inst_pvar", "$avp(rtpInstance)") modparam("rtpengine", "rtpengine_tout_ms", 1000) modparam("rtpengine", "read_sdp_pv", "$var(sdpToRtpengine)") modparam("rtpengine", "write_sdp_pv", "$var(sdpFromRtpengine)") }}} I'm using a simplified kamailio.cfg from installation, and here are calls to rtpengine: {{{ ... route[INVITE] { $var(sdpToRtpengine) = $rb; $var(ret) = rtpengine_manage("direction=dirty direction=clean ICE=remove"); xlog("L_INFO", "$ci INVITE: rtpengine chosen: $avp(rtpInstance)"); remove_body(); replace_body(".*", $var(sdpFromRtpengine)); t_on_reply("RESPONSE"); route(RELAY); } onreply_route[RESPONSE] { $var(sdpToRtpengine) = $rb; $var(ret) = rtpengine_manage("direction=clean direction=dirty ICE=remove"); remove_body(); replace_body(".*", $var(sdpFromRtpengine)); xlog("L_INFO", "$ci RESPONSE: $rm - $rs $rr, cseq=$cs, by [$hdr(Server)], from $si:$sp"); } ... }}} When rtpengine is down for a couple of seconds, there were a lot of SIP retransmissions and timeouts. Doing a netstat and I can see Kamailio’s receive buffer is quite filled up. Please let me know if more information is needed. Thank you! Cheers, Yufei

2 3

Additional Param Check in ConsumeCredential Auth
by Prabhat Kumar 22 Jan '19

22 Jan '19

Hi, I want to check additional param in Auth module. For. ex., other than username and secret , i want to validate user by its email address. How can i do that? Regards, Prabhat Kumar

4 8

How to send NOTIFY to UA
by CuiGang 22 Jan '19

22 Jan '19

Hello, Does any one know, how to send a NOTIFY message to a special UA? Why I need to do this? I’m using kamailio integration with Yealink IP Phone. Yealink IP Phone can perform some specified action immediately by accepting a SIP NOTIFY message with the “Event: ACTION-URI” header. I want to use RPC or HTTP or NSQ or some other interface trigger kamailio ROUTE make a NOTIFY message and send it to a special Yealink IP Phone. Thanks! Regards, CuiGang cuigang0120(a)aliyun.com

2 2

Empty presence event NOTIFY
by EDUARDO PASCUAL GALLEGO 22 Jan '19

22 Jan '19

Hello: I am testing the Kamailio Presence Server. I can see when the presence of an user agent expires then the server sends an empty NOTIFY without XML document. Also, when the server receives a SUBSCRIBE it sends a NOTIFY with XML if the UA is present but it sends an empty NOTIFY when the UA is not present. However, if the presence server receive a PUBLISH with Expires header equals cero then it sends a NOTIFY with XML document. I do not understant why it sends empty NOTIFY messages. Especially if the user agent is not present. I tested 4.4.7 version and I can see that it is the best version, because I tested 5.1.6 and 5.2.0 versions and I could see that they sends empty NOTIFY messages even the user agent is present. Then I am using 4.4.7 version, an I am considering as no present when a NOTIFY message is empty. But I think it is not RFC3856 compliant. Kamailio presence server es configured like that: #!ifdef WITH_PRESENCE # ----- presence params ----- modparam("presence", "db_url", DBURL) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) #!endif Can anyone help me? Thank you very much in advance. *Eduardo Pascual Gallego* *Ingeniero de Desarrollo / Development Engineer.* T. +34 91 807 39 99 · eduardo.pascual(a)nucleocc.com <https://www.nucleocc.com/> *Núcleo HQ* C/Vía de los Poblados, 7 28033 Madrid (Spain) <https://www.google.es/maps/place/DF+N%C3%BAcleo/@40.4747861,-3.6352894,17z/…> *Núcleo USA* 100 Crescent Dr, STE.700 75201 Dallas, Texas (USA) <https://www.google.es/maps/place/100+Crescent+Ct,+Dallas,+TX+75201,+EE.+UU.…> *www.nucleocc.com* <https://www.nucleocc.com/> Este correo electrónico y cualquier fichero adjunto al mismo contienen información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. En el caso de haber recibido este correo electrónico por error, le indicamos que no le está permitido por ley la lectura, copia y uso del mismo . En tal caso, le rogamos notifique lo antes posible esta circunstancia mediante reenvío a la dirección electrónica del remitente y destruya el mensaje. Antes de imprimir este correo, piense en su responsabilidad y compromiso con el medio ambiente. -- Advertencia | Este mensaje está destinado únicamente a su destinatario y puede contener información CONFIDENCIAL y/o protegida por secreto profesional cuya revelación está prohibida por la ley. Si usted no es el destinatario a quien va dirigido le informamos que la lectura, la distribución, el copiado o la revelación de este mensaje están prohibidos por la ley. Si ha recibido este mensaje por error le solicitamos que nos notifique por e-mail su recepción equivocada y que borre este mensaje sin conservar copia, al tiempo que le pedimos disculpas por las molestias que le haya ocasionado. El servicio de e-mail por internet no garantiza ni la confidencialidad ni la integridad o la recepción de los mensajes por lo que nuestra Firma no asume ninguna responsabilidad portales circunstancias. De conformidad con lo previsto en el REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO de 27 de abril de 2016, a continuación facilitamos la información básica en relación con la protección de los datos personales que nos sean suministrados: Responsable: NUCLEO DE COMUNICACIONES Y CONTROL, SLU Finalidad: Cumplimiento de las relaciones jurídicas y obligaciones legales asociadas. Legitimación: Ejecución contractual y cumplimiento de nuestras obligaciones. No se cederán o transferirán los datos personales a terceros, salvo siguiendo sus instrucciones o por obligación legal. Ejercicio de derechos de acceso, rectificación y supresión de los datos, así como el ejercicio de otros derechos, tal y como se explica en la información adicional. Puede consultar la información adicional y detallada en el siguiente enlace a nuestra política de privacidad y *Tratamiento de Datos Personales* <http://www.nucleocc.com/paginas_informativas/proteccin_de_datos_de_carcter_…>*.*

1 1

uri_param function
by Andrew Chen 21 Jan '19

21 Jan '19

Hi all, Question. I'm executing uri_param() function to look for our customized Request-URI parameters generated by our client. However, it keeps saying the param is not there even though my client logs shows the param was generated. Below is an example Request-URI from a test call I made: sips:<some long string>@sjomainkamavip50.fuzemeeting.com:443;FN= sjomainfn92.a.fuzemeeting.com;BR=sjomainfn91.a.fuzemeeting.com;AK=<some key>;transport=wss" And here is my line of code to check it: if(uri_param("AK") ||uri_param("ak")) { xlog("L_INFO", "[CSeq $cs] AK value detected"); } else { xlog("L_INFO", "[CSeq $cs] AK value not detected. Aborting call"); drop(); } Am I misusing this function somehow? I'm running 5.1.2. Thanks Regards, -- Andy Chen -- *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.*

2 4

Radius Accounting with Kamailio 5.1 (On-line Charging)
by Yazar Lwin 21 Jan '19

21 Jan '19

Hi All, I've Kamailio 5.1 running with Mysql as local DB. I've configured Siremis as well. I completed accounting configuration as per the instruction. Now I can see the accounting list, CDR list and as well as missed calls in Siremis But I can't integrate with free radius server to trigger the accounting, just like Diameter transaction in IMS. Kindly advise which doc I should check. I would like to enable Radius server as an online charging. Best regards Yazar

2 3

Dynamic UAC Registration
by Mack Hendricks 20 Jan '19

20 Jan '19

Hey All, So, I want to use the UAC module to handle Digest Auth to upstream carriers. But, I don’t know which carrier will be selected until another module (dRouting in this case) tells the logic which carrier to use. I can see in the logs that the uac_auth function can capture the Auth Realm. But, I need to access it from the Kamailio script so that I can lookup the credentials for that realm and then call uac_auth. I’ve tried getting the info from $ar, but that gives me the realm of the inbound request versus the realm of the upstream carrier. Also, I’ve tried using $T_rpl($ar), but that returns 0. Here’s my logic from the Kamailio file: if(t_check_status("401|407")) { $var(reply_realm) = $T_rpl($ar); $var(query)="select auth_username,auth_password from uacreg where realm='" + $var(reply_realm) + "'"; sql_xquery("cb","$var(query)","rb"); xlog("L_DEBUG","[MANAGE_FAILURE: Proxy Auth]: The query is $var(query) auth realm is $var(reply_realm) and the user name is $xavp(rb=>auth_username)"); $avp(auser) = $xavp(rb=>auth_username); $avp(apass) = $xavp(rb=>auth_password); uac_auth(); t_relay(); exit;` } A snippet of the log file is below: Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1616 a=63 n=assign Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1617 a=63 n=assign Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1618 a=24 n=uac_auth Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:409]: uac_auth(): picked reply is 0x7f900cb7eaf0, code 407 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:225]: get_autenticate_hdr(): looking for header "Proxy-Authenticate" Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:429]: uac_auth(): header found; body=<Digest realm="sip.flowroute.com", nonce="XERJMlxESAbDNCK3INmBfoET1GGxpcyr", qop="auth"> Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <realm>="sip.flowroute.com" state=2 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <nonce>="XERJMlxESAbDNCK3INmBfoET1GGxpcyr" state=3 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <qop>="auth" state=1 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:449]: uac_auth(): no credential for realm "sip.flowroute.com" Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1619 a=24 n=t_relay Thanks in advance for any help Mack Hendricks dSIPRouter

4 4

Kamailio Docker 5.2.1
by Grant Bagdasarian 20 Jan '19

20 Jan '19

Hello, I was wondering when the Kamailio Docker image will be updated to use 5.2.1 and be available through the Docker public repository ( https://hub.docker.com/r/kamailio/kamailio)? Thanks and regards, Grant

4 10

Mysql
by Nicolas Breuer 20 Jan '19

20 Jan '19

Hello, Working on sip_trace table produce this error WARNING: db_mysql [km_res.c:142]: db_mysql_get_columns(): unhandled data type column (Msg_text) type id (250), use DB1_STRING as default

5 16

segfault error - process stopped
by AL RSM 20 Jan '19

20 Jan '19

Hi We are running Kamailio 3.7 on our production servers. The Kamailio process stopped running on one of the 4 servers. Log shows "segfault error". No core file generated. Any suggestion on how to verify the issue would be appreciated. kernel: [63574875.776269] kamailio[1558]: segfault at 0 ip 000000000055933a sp 00007fffd4ca6700 error 4 in kamailio[400000+211000] /usr/sbin/kamailio[1545]: ALERT: <core> [main.c:785]: child process 1558 exited by a signal 11 /usr/sbin/kamailio[1545]: ALERT: <core> [main.c:788]: core was not generated CRON[21436]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Thanks, AL

3 2

Mid-Registrar
by Mark Thomas 20 Jan '19

20 Jan '19

I’m currently and OpenSIPS user and I really want to be able to use their software on OpenWRT, but I have found it really hard to cross-compile. Is there a possibility to run Kamailio as a mid-registrar? For my application this is required, and I haven’t been able to find any information on this.

3 3

handling BYEs generated by dialog-timeout
by * Paolo Visintin - evosip.cloud 19 Jan '19

19 Jan '19

Hello! I'm wondering if someone have experience in changing $du on local kamailio generated packets (like BYE generated at the dialog-timeout) I'm trying to manipulate in `event_route[tm:local-request]` with no success. In the end I have it working using the `forward()` function and then using `exit;` but in this case instead of having 2 BYEs , kamailio sends 4 BYEs (2 with original $du, 2 with new $du) this an example : event_route[tm:local-request] { if ($rm == "BYE") { route(SELECT_OUTBOUND_PROXY); forward(); exit; } } I'm using a kamailio proxy on top with no record-route (we want to have multiple instances of proxy that can change ip address). Thanks in advance! Paolo

2 6

Dev documentation on implementing event_route events in custom module
by Ivan Ribakov 19 Jan '19

19 Jan '19

Is there any documentation for module developers that lays out API for registering and triggering events from a custom Kamailio module (similar to https://kamailio.org/docs/modules/5.0.x/modules/tm.html#tm.event_routes)? I have been referring to https://www.kamailio.org/docs/kamailio-devel-guide/ <https://www.kamailio.org/docs/kamailio-devel-guide/> up until now but it doesn’t seem to cover event_routes. Thanks in advance, Ivan

3 5

Diameter (CDP) crashes on startup. ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket
by Denys Pozniak 18 Jan '19

18 Jan '19

Hello! Please help me to find the issue with CDP module as it blocks Kamailio to start. [root@10-10-10-10 kamailio]# cat diameter.xml <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="10-10-10-10.ams.proxy.dev" Realm="proxy.dev" Product_Name="Diameter Credit Control" Vendor_Id="10415" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="4" QueueLength="32"> <Peer FQDN="dev-diameter-1.ams.proxy.dev" Realm="proxy.dev" port="3868"/> <Acceptor port="3868" bind="10.10.10.10"/> <Auth id="16777216" vendor="10415"/> <Acct id="16777216" vendor="0" /> <Auth id="16777216" vendor="10415"/> <Auth id="16777216" vendor="0" /> <SupportedVendor vendor="10415"/> <Realm name="proxy.dev"> <Route FQDN="dev-diameter-1.ams.proxy.dev" metric="1"/> </Realm> <DefaultRoute FQDN="dev-diameter-1.ams.proxy.dev" metric="10"/> </DiameterPeer> 38(7825) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 37(7824) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 39(7826) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 40(7827) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 41(7828) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 41(7828) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process starting up... 42(7829) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [dev-diameter-1.ams.proxy.dev] Receiver process doing init on new process... 42(7829) INFO: cdp [receiver.c:184]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [dev-diameter-1.ams.proxy.dev] 42(7829) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [dev-diameter-1.ams.proxy.dev] Receiver process starting up... 43(7830) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 0(7787) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 43(7830) WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 10.10.10.10 port 3868 43(7830) WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.10.10.10 port 3868 43(7830) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 44(7831) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... [root@10-10-10-10 kamailio]# 44(7831) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer dev-diameter-1.ams.proxy.dev 44(7831) INFO: cdp [receiver.c:869]: peer_connect(): peer_connect(): Trying to connect to 10.10.10.20 port 3868 44(7831) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer dev-diameter-1.ams.proxy.dev:3868 connected 42(7829) ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 42(7829) CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(0, abcdefed)[0x7f3ecb7ef018:0x7f3ecb7ef050]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec from core/mem/q_malloc.c:504. 45(7832) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 52 0(7787) ALERT: <core> [main.c:739]: handle_sigs(): child process 7829 exited by a signal 6 0(7787) ALERT: <core> [main.c:742]: handle_sigs(): core was generated 0(7787) INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD DNS record dev-diameter-1.ams.proxy.dev is pointed to 10.10.10.20 NU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New LWP 7829] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `kamailio -f kamailio.cfg -DDDD -E'. Program terminated with signal 6, Aborted. #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-34.el7.x86_64 libcom_err-1.42.9-13.el7.x86_64 libgcc-4.8.5-36.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 mariadb-libs-5.5.60-1.el7_5.x86_64 openssl-libs-1.0.2k-16.el7.x86_64 pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb) bt #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 #1 0x00007f3ed7dc18f8 in abort () from /lib64/libc.so.6 #2 0x000000000067d5f7 in qm_debug_check_frag (qm=0x7f3ecb4d0000, f=0x7f3ecb7ef018, file=0x7f3ed068d932 "cdp: diameter_avp.c", line=365, efile=0x7df137 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 #3 0x000000000068077a in qm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:504 #4 0x000000000068a2d6 in qm_shm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:1268 #5 0x00007f3ed06691c8 in AAAFreeAVP (avp=0x7ffd86bdd300) at diameter_avp.c:365 #6 0x00007f3ed0636d66 in AAAFreeAVPList (avpList=0x7f3ecb7eea40) at diameter_msg.c:396 #7 0x00007f3ed0637123 in AAAFreeMessage (msg=0x7ffd86bdd3b0) at diameter_msg.c:416 #8 0x00007f3ed06088ec in Process_CEA (p=0x7f3ecb7a00d8, cea=0x7f3ecb7ee9f0) at peerstatemachine.c:804 #9 0x00007f3ed0601ab1 in sm_process (p=0x7f3ecb7a00d8, event=I_Rcv_CEA, msg=0x7f3ecb7ee9f0, peer_locked=0, sock=8) at peerstatemachine.c:166 #10 0x00007f3ed0659825 in receive_message (msg=0x7f3ecb7ee9f0, sp=0x7f3ed76feec8) at receiver.c:1128 #11 0x00007f3ed064f295 in do_receive (sp=0x7f3ed76feec8) at receiver.c:593 #12 0x00007f3ed0653068 in receive_loop (original_peer=0x7f3ecb7a00d8) at receiver.c:800 #13 0x00007f3ed064c7c6 in receiver_process (p=0x7f3ecb7a00d8) at receiver.c:459 #14 0x00007f3ed05fd7de in diameter_peer_start (blocking=0) at diameter_peer.c:289 #15 0x00007f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243 #16 0x0000000000544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at core/sr_module.c:943 #17 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at core/sr_module.c:939 #18 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at core/sr_module.c:939 #19 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at core/sr_module.c:939 #20 0x0000000000545205 in init_child (rank=0) at core/sr_module.c:970 #21 0x0000000000424f85 in main_loop () at main.c:1701 #22 0x000000000042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638 (gdb) bt full #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f3ed7dc18f8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x000000000067d5f7 in qm_debug_check_frag (qm=0x7f3ecb4d0000, f=0x7f3ecb7ef018, file=0x7f3ed068d932 "cdp: diameter_avp.c", line=365, efile=0x7df137 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 __FUNCTION__ = "qm_debug_check_frag" #3 0x000000000068077a in qm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:504 qm = 0x7f3ecb4d0000 f = 0x7f3ecb7ef018 size = 140726864040496 next = 0x7df14b prev = 0x7f3ed067f329 __FUNCTION__ = "qm_free" #4 0x000000000068a2d6 in qm_shm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:1268 No locals. #5 0x00007f3ed06691c8 in AAAFreeAVP (avp=0x7ffd86bdd300) at diameter_avp.c:365 __FUNCTION__ = "AAAFreeAVP" #6 0x00007f3ed0636d66 in AAAFreeAVPList (avpList=0x7f3ecb7eea40) at diameter_msg.c:396 avp_t = 0x7f3ecb7ef050 avp = 0x7f3ecb7eef40 #7 0x00007f3ed0637123 in AAAFreeMessage (msg=0x7ffd86bdd3b0) at diameter_msg.c:416 __FUNCTION__ = "AAAFreeMessage" #8 0x00007f3ed06088ec in Process_CEA (p=0x7f3ecb7a00d8, cea=0x7f3ecb7ee9f0) at peerstatemachine.c:804 avp = 0x7f3ecb7ef440 #9 0x00007f3ed0601ab1 in sm_process (p=0x7f3ecb7a00d8, event=I_Rcv_CEA, msg=0x7f3ecb7ee9f0, peer_locked=0, sock=8) at peerstatemachine.c:166 result_code = -798486160 next_event = 32574 msg_received = 0 __FUNCTION__ = "sm_process" #10 0x00007f3ed0659825 in receive_message (msg=0x7f3ecb7ee9f0, sp=0x7f3ed76feec8) at receiver.c:1128 avp1 = 0xd0684fc0 avp2 = 0x7f3ecb7eed10 __FUNCTION__ = "receive_message" #11 0x00007f3ed064f295 in do_receive (sp=0x7f3ed76feec8) at receiver.c:593 cnt = 184 n = 184 version = 1 dst = 0x7f3ecb7ef4f4 "" dmsg = 0x7f3ecb7ee9f0 __FUNCTION__ = "do_receive" #12 0x00007f3ed0653068 in receive_loop (original_peer=0x7f3ecb7a00d8) at receiver.c:800 rfds = {__fds_bits = {256, 0 <repeats 15 times>}} efds = {__fds_bits = {0 <repeats 16 times>}} tv = {tv_sec = 0, tv_usec = 999998} n = 1 max = 49 cnt = 1 msg = 0x0 sp = 0x7f3ed76feec8 sp2 = 0x7f3ed76feec8 p = 0x7f3ecb7a00d8 fd = 8 fd_exchange_pipe_local = 49 __FUNCTION__ = "receive_loop" #13 0x00007f3ed064c7c6 in receiver_process (p=0x7f3ecb7a00d8) at receiver.c:459 ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "receiver_process" #14 0x00007f3ed05fd7de in diameter_peer_start (blocking=0) at diameter_peer.c:289 pid = 0 k = -1 p = 0x7f3ecb7a00d8 __FUNCTION__ = "diameter_peer_start" #15 0x00007f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243 __FUNCTION__ = "cdp_child_init" #16 0x0000000000544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at core/sr_module.c:943 __FUNCTION__ = "init_mod_child" #17 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #18 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #19 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #20 0x0000000000545205 in init_child (rank=0) at core/sr_module.c:970 No locals. #21 0x0000000000424f85 in main_loop () at main.c:1701 i = 32 pid = 7821 si = 0x0 si_desc = "udp receiver child=31 sock=10.10.10.10:5060\000\177\000\000`\336\275\206\375\177\000\000A\307g\000\000\000\000\000`\202A\000\000\000\000\000ȖP\313>\177", '\000' <repeats 14 times>, "\001\000\000\000\260\336\275\206\375\177\000\000\234\240h\000\000\000\000\000 \243w\000\000\000\000\000H\361m\327>\177\000" nrprocs = 32 woneinit = 1 __FUNCTION__ = "main_loop" #22 0x000000000042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638 cfg_stream = 0x2b13020 c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 0 proto = 0 options = 0x758490 ":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 = 4201223303 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 4 n_lst = 0x0 p = 0x0 st = {st_dev = 19, st_ino = 82198, st_nlink = 2, st_mode = 16832, st_uid = 995, st_gid = 2, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1547739314, tv_nsec = 582000000}, st_mtim = {tv_sec = 1547743303, tv_nsec = 194148453}, st_ctim = {tv_sec = 1547743303, tv_nsec = 194148453}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) -- BR, Denys Pozniak

1 1

event_route[usrloc:contact-expired]
by Javier Valencia 18 Jan '19

18 Jan '19

Hi there! I'm using Kamailio 4.4.3, and I add this code to my Kamailio: event_route[usrloc:contact-expired] { xlog("L_INFO", "EXPIRED CONTACT START\n"); xlog("L_INFO", "EXPIRED CONTACT for $ulc(exp=>aor)\n"); xlog("L_INFO", "EXPIRED CONTACT END\n"); } I can't see this entries in the log. I read many times the docs and code, but I don't understand why it's not working. I have two phone with 60 and 300 expiry seconds, if then expire, when it's event_route[usrloc:contact-expired] triggered? Why this event route it's named as usrloc but it's documented in registrar module? I need to provide more info about? Thank you very much.

3 11

segfault at 0 - process stopped
by AL RSM 18 Jan '19

18 Jan '19

3 2

rtpengine_manage() in async tasks
by Alex Balashov 18 Jan '19

18 Jan '19

Hi, I've run into an issue with handling reinvites in async task workers--which I need to do in order to introduce a small delay to avoid a UA race condition--in which some state that is necessary for rtpengine_manage() to do the right thing seems to be lost. Specifically, if I do this: -- loadmodule "mqueue" loadmodule "rtimer" ... modparam("rtimer", "timer", "name=reinvite_q1;interval=10000u;mode=1;") modparam("rtimer", "exec", "timer=reinvite_q1;route=REINVITE_DEQUEUE") modparam("mqueue", "mqueue", "name=reinvite_q"); ... route { ... if(has_totag()) { if(loose_route()) { ... if(is_method("INVITE")) { if(!t_suspend()) { sl_send_reply("500", "Server Internal Error"); exit; } mq_add("reinvite_q", "$T(id_index):$T(id_label)", ""); } else route(IN_DLG_REQ); exit; } ... } route[REINVITE_DEQUEUE] { while(mq_fetch("reinvite_q")) { $var(id) = $(mqk(reinvite_q){s.select,0,:}{s.int}); $var(label) = $(mqk(reinvite_q){s.select,1,:}{s.int}); t_continue("$var(id)", "$var(label)", "IN_DLG_REQ"); } } route[IN_DLG_REQ] { handle_ruri_alias(); if(is_method("BYE")) rtpengine_manage(); else if(is_method("INVITE") && sdp_content()) rtpengine_manage("replace-origin replace-session-connection ICE=remove") t_on_reply("MAIN_REPLY"); if(!t_relay()) sl_reply_error(); } onreply_route[MAIN_REPLY] { if(is_method("INVITE") && sdp_content()) rtpengine_manage("replace-origin replace-session-connection ICE=remove"); } -- What I find is that if I generate a reinvite from either side, rtpengine_manage() passes through the SDP offer in the reinvite unadulterated, although the answer returns properly adulterated by RTPEngine. The same thing occurs if I use 'async', which as I gather is just a wrapper of convenience around t_suspend/t_continue() anyway. That module won't do for my purposes because I need a millisecond-level delay resolution rather than second-level, anyhow. Anyway, surely enough, this is because the execution context is one that insinuates a stream deletion. When the reinvite offer comes across and I call rtpengine_manage(), the command sent is 'delete': -- Jan 14 20:24:23 staccato.evaristesys.com rtpengine[33830]: INFO: [c94347dcf92e7ccc10dee84c4e0d1c8a]: Received command 'delete' from 209.51.167.66:39788 -- The RTPEngine module documentation actually warns about this: https://kamailio.org/docs/modules/5.2.x/modules/rtpengine.html#rtpengine.f.… But this insight is buried in the fourth bullet point: "If BYE or CANCEL, or called within a FAILURE_ROUTE[], then call rtpengine_delete(). Be careful with calling this function after resuming a suspended transaction (e.g., after t_continue()), because the context of executed route is FAILURE ROUTE (in other words, rtpengine_manage() in the route block of t_continue() does the same as in failure_route)." This would lead one to believe that it applies only in the context of handling a BYE or CANCEL in a resumed transaction, when in fact it seems to hold true of non-BYE/CANCEL and non-failure contexts as well, as can be clearly seen with the reinvite. The behaviour is exactly as expected if I don't use rtpengine_manage() and instead manually call rtpengine_offer()/rtpengine_answer(). And expected behaviour comes from rtpengine_manage() if I don't handle the request in a resumed transaction context. This yields the fundamental question: Is there any way to have my cake and eat it too? I really want to use rtpengine_manage() because I need to handle a potential SDP offer-in-ACK scenario and don't want to do a bunch of state-keeping in order to use the correct choice of rtpengine_{offer|answer}() in the right context, which is a problem rtpengine_manage() solves beautifully. At the same time, I absolutely need the slight reinvite delay that can be accomplished via async processing; a UA on this side has a nasty habit of sending a reinvite almost simultaneously to the 2xx answer for the INVITE transaction, leading to indeterminate egress velocity for those respective messages out of Kamailio worker threads. Many thanks in advance! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

authentification issue when nb user increase
by Laurent Schweizer 18 Jan '19

18 Jan '19

Hello, I have a proxy with Kamailio 5.0.6 working since few month without any issue. Around 4500 locations and 5300 contacts This weekend we move a very old proxy (Kamailio 3.3.2 with an old server )to this new one, adding around 14’000 users and 15’000 contacts. Yesterday when calls was starting we get an big issue with this new proxy, lot of phones was disconnected and some calls was rejected. I see that the issue was the authentication (done via a mysql DB with the cluster db module) many phone get a failure and was disconnected, mostly phone connected via TCP or TLS we see less issue with UDP even we have much more . The issue was not the number of TCP/TLS connection as we see the REGISTER and the 401 going back, so connection was correctly done Currently it’s working but I don’t know exactly why ☹, I mean I have done a change but it has really no relation … , during the same time I get another issue, some calls have no voice… We are using rtpengine (on the old proxy we was using rtpproxy) and with the rtproxy we already face a long time ago such case and to solve it we setup multiple rtpproxy (on the same host) So I try to do the same, I setup a second rtpengine on the same host and when I reload the config with : kamcmd rtpengine.reload all registration was working perfectly ... As they is no relation with the registration end the rtpengine I don't know why now it's working. Any idea ? BR Laurent

2 1

Limitation in Dispatcher Probing
by Duarte Rocha 17 Jan '19

17 Jan '19

Greetings, I have a question about Dispatcher's probing. I have it configured with ds_probing_mode = 3 and ds_ping_interval = 60. Currently i have 35 Gateways with state = 8, meaning they will be probed. However, when i do a SIP capture i get a different scenario. Altough Kamailio sends OPTIONS at every 60 seconds it only sends to 16 destinations. Is there a configuration that limits this? What can i do to have every gateway probed? Best Regards, Duarte Rocha

1 0

Dispatcher Probing
by Duarte Rocha 17 Jan '19

17 Jan '19

Greetings, I have a question about Dispatcher's probing. I have it configured with ds_probing_mode = 3 and ds_ping_interval = 60. Currently i have 35 Gateways with state = 8, meaning they will be probed. However, when i do a SIP capture i get a different scenario. Altough Kamailio sends OPTIONS at every 60 seconds it only sends to 16 destinations. Is there a configuration that limits this? What can i do to have every gateway probed? Best Regards, Duarte Rocha

1 0

AWS binat external -> internal routing and record_route
by Dmitry Sytchev 17 Jan '19

17 Jan '19

Hi all! I have a question that arises in mailing list sometimes, but it is still not clear for me how to work with this. We have AWS instance with standard Amazon bi-nat, so basically communication with external hosts works with listen udp:ip:port advertise ip:port But in case when we need to send external call to internal network by internal ip addresses, we want to have internal host in record-route. As far as I understand, basic recommendation is to use separate port or internal address and select it with appropriate function. Maybe it is more theoretical question, but can we do something to generate correct record-routes and VIA for calls coming from external network to make their softswitches happy, and still maintain internal address in messages going to internal hosts, using single host and port on Kamailio behind nat? Thanks! -- Best regards, Dmitry Sytchev, IT Engineer

3 6

Invalid sqlops parameter
by Yağız AYDIN 17 Jan '19

17 Jan '19

Hello, I'm trying to install Kamailio IMS for my Ubuntu 18.04 device. I have followed the configuration files which are provided by installation, but I have a problem about sqlops module. While I'm trying to execute pcscf module, following errors appear: root@yagiz-HP-ZBook-15:/usr/local/src/kamailio# kamailio -f /etc/kamailio/pcscf/kamailio.cfg -c loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(12536) ERROR: sqlops [sql_api.c:669]: sql_parse_param(): invalid sqlops parameter [mysql://Mysql@localhost/pcscf] at [29] 0(12536) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 278, column 60: Can't set module parameter 0(12536) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks array size 16 0(12536) CRITICAL: <core> [core/cfg.lex:1599]: sr_push_yy_state(): cannot open included file: route/register.cfg (/etc/kamailio/pcscf/route/register.cfg) 0(12536) : <core> [core/cfg.lex:1308]: yylex(): error at /etc/kamailio/pcscf/kamailio.cfg line 907 I have set my sqlops parameter as : #!define SQLOPS_DBURL "mysql://Mysql@localhost/pcscf" PS: I have created necessary databases and tables which are mentioned on usrloc files ( which are ims_usrloc_pcscf-create.sql and ims_usrloc_scscf-create.sql) Here is my pcscf.cfg file # IP-Adress for incoming SIP-Traffic, in the following format: # SIP / UDP listen=udp:10.3.0.188:5060 # SIP / TCP #listen=tcp:11.22.33.44:5060 # SIP / TCP/TLS #listen=tls:11.22.33.44:5061 alias=pcscf.mnc001.mcc001.3gppnetwork.org #!define MY_WS_PORT 80 #!define MY_WSS_PORT 443 #!define PCSCF_URL "sip:pcscf.mnc001.mcc001.3gppnetwork.org" #!define TCP_PROCESSES 8 #!subst "/NETWORKNAME/mnc001.mcc001.3gppnetwork.org/" #!subst "/HOSTNAME/pcscf.mnc001.mcc001.3gppnetwork.org/" # SIP-Address of capturing node, if not set, capturing is disabled. ##!define CAPTURE_NODE "sip:127.0.0.1:9060" # Allowed IPs for XML-RPC-Queries ##!define XMLRPC_WHITELIST_1 "127.0.0.1" ##!define XMLRPC_WHITELIST_2 "127.0.0.1" ##!define XMLRPC_WHITELIST_3 "127.0.0.1" #!define RTPPROXY_ADDRESS "udp:10.1.2.186:22222" # Databases: #!define DB_URL "mysql://Mysql@localhost/pcscf" ##!define DB_URL "mysql://kamailio:kamailiorw@localhost/kamailio/pcscf" ##!define DB_URL2 "con2=>mysql://pcscf:heslo@127.0.0.1/pcscf" #!define SQLOPS_DBURL "mysql://Mysql@localhost/pcscf" ##!define SQLOPS_DBURL "mysql://root@localhost/pcscf" #! Optional: Server-URL for Websocket-Requests ##!define WEBSOCKET_WEBSERVER "phone.ng-voice.com" ##!define TRF_FUNCTION "trf.mnc001.mcc001.3gppnetwork.org" # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # # *** To enable nat traversal execute: # - define WITH_NAT # - define the connection to the RTP-Proxy: RTPPROXY_ADDRESS # # *** To force alls calls through the RTP-Proxy # - this will automagically enable NAT-Traversal # - define FORCE_RTPRELAY # # *** To enable IPv4/IPv6 Translation (RTPProxy) # - this will automagically enable NAT-Traversal # - define WITH_RTPIPV4 # # *** To enable TCP support execute: # - define WITH_TCP # # *** To enable TLS support execute: # - adjust CFGDIR/tls.cfg as needed # - define WITH_TLS # - this will automagically enable TCP # # *** To enable XMLRPC support execute: # - define WITH_XMLRPC # - this will automagically enable TCP # # *** To enable anti-flood detection execute: # - adjust pike and htable=>ipban settings as needed (default is # block if more than 16 requests in 2 seconds and ban for 300 seconds) # - define WITH_ANTIFLOOD # # *** To enable the Rx-Interface: # - Configure Rx-Diameter-Interface in pcscf.xml # - define WITH_RX # # *** To enable a Homer SIP-Capter-Node: # - define CAPTURE_NODE with a proper address # # *** To enable support for the SEMS-SBC # - define WITH_SBC # - configure dispatcher-list with a set of SBC's # # Enabled Features for this host: ##!define WITH_DEBUG #!define WITH_NAT #!define WITH_NATPING #!define FORCE_RTPRELAY ##!define WITH_TLS ##!define WITH_XMLRPC ##!define WITH_IPBLOCK ##!define WITH_ANTIFLOOD ##!define WITH_RX ##!define WITH_RX_REG ##!define WITH_RX_CALL ##!define WITH_TCP ##!define WITH_RTPIPV4 ##!define WITH_SBC ##!define WITH_SBC_CALL ##!define WITH_REGINFO ##!define WITH_RTPPING ##!define WITH_WEBSOCKET Any helps would be appreciated, Regards, Yağız --

2 1

Setting up Kamailio IMS in a Box difficulties.
by Jason Tsay 17 Jan '19

17 Jan '19

Hi miconda, I am new to the Kamailio and RCS world. I'm trying to set up an IMS core so I can get two devices communication through RCS. I am trying to set up the Kamailio IMS in a box vmware image, and when I boot it up, it asks for the server login information. ??All parameters and passwords used are documented in the log-file.? I couldn't find documentation for the username and password. I was wondering if there is a new link available or login information where I could see the set up. These are the things that I have found (to be working) getting started - https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/ configs - https://www.dropbox.com/s/nm51v4orxrox4ac/Kamailio-IMS%20config-files.zip?d… pdf - https://www.kamailio.org/docs/tutorials/ims/Kamailio-IMS-in-a-Box.pdf I did find the config files in a dropbox but I wanted to get the vmware sandbox working so I have a working environment (as I have failed many times to get my own instance set up.) In addition, I was looking for some Android clients or if you could recommend some. I've tried rcsjta but I keep getting an API not compatible error (Doesn't work on Android Pie (Pixel 3 device) or Android M (6.0.1) Nexus device.) I also tried IMSdroid, and it looks like it works with Android M (6.0.1) Nexus device but not compatible with Android Pie. Thanks, Jason

2 1

Updating default kamailio.cfg to use rtpengine
by Daniel-Constantin Mierla 16 Jan '19

16 Jan '19

Hello, being discussed at events offline or during irc meetings couple of times, I want to open the discussion about updating the default configuration file to use rtpengine. So far I let rtpproxy because was packaged in many Linux distros, however, given the benefits of rtpengine in terms of performance as well as webrtc support, doubled by the fact that nowadays in the community it seems to be the primary choice of rtp relay, we should decide what to do. I see two options: 1) add a define to allow selection between rtpproxy and rtpengine 2) replace rtpproxy completely with rtpengine I would prefer 2) for simplicity of the configuration file, but the main question for the users community is how easy they find the deploying of rtpengine. Using Debian/Ubuntu should be trivial, there are packages for it, but I do not know about CentOS, Fedora, openSUSE or other Linux/BSD OSes people here are using it. Reply to sr-users if you have an opinion on this matter (I cc-ed sr-dev mainly to make aware the devs, but it is a matter of using kamailio). Of course, other suggestions are welcome as well. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

3 2

DMQ tries to resolve dns AAA even when it is disabled in kamailio core config
by José Seabra 16 Jan '19

16 Jan '19

Hi all, I'm using DMQ with multi_notify set to 1, the dns_try_ipv6 is disabled and dns_cache_flags is set to 1, but even this way DMQ is making dns AAA queries. Once that AAA queries are disabled in core dns config it seems that DMQ is not respecting those configurations, is that supposed? Thank you for your support Best Regards -- Cumprimentos José Seabra

2 3

Kamailio on Kubernetes
by Amar Tinawi 16 Jan '19

16 Jan '19

Hello all i'm wondering if Kamailio docker file is ready to be built over kubernetes i haven't try it yet, but don't know if it is available with all kamailio modules? does the database included or should be on different containers? Thanks in advance Regads

2 1

Kamailio v5.2.1 Released
by Daniel-Constantin Mierla 16 Jan '19

16 Jan '19

Hello, Kamailio SIP Server v5.2.1 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2.x. Deployments running previous v5.2.x versions are strongly recommended to be upgraded to v5.2.1. For more details about version 5.2.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/01/kamailio-v5-2-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Overhead of health check with dispatcher
by Jesse Strahn 16 Jan '19

16 Jan '19

Hi all, I'm new to Kamailio. I am using Kamailio/dispatcher to distribute calls to several SIP IVRs. I'm trying to determine the best solution to autoscale in AWS when call capacity of the IVRs is reached. The most straight forward solution is to spin up a new IVR on a dedicated subnet when required. I would configure dispatcher such that the whole IP range of this subnet is in the dispatcher.list so that once a new instance becomes available, Kamailio starts sending calls there. My question is, how much overhead would this add as Kamailio/dispatcher would be polling the IPs in the subnet that were not yet active. The plan would be to have a /28 subnet with 16 IPs. To start, there would be 2 active IVRs up and responding and 14 IPs in dispatcher.list that would not be responding. Appreciate any insight. Thanks, Jesse

2 1

Releasing Kamailio v5.2.1
by Daniel-Constantin Mierla 16 Jan '19

16 Jan '19

Hello, I am considering to release Kamailio v5.2.1 sometime next week, likely on Tuesday (Jan 15) or Wednesday (Jan 16). Should any of you be aware of issues not reported to the bug tracker, open a bug report as soon as possible to give it a chance for analysis and an eventual fix: - https://github.com/kamailio/kamailio/issues Days after it, I am planning to make new releases from branch 5.1 and 5.0 (it should be the last one from there to mark the end of official packaging). Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 2

Re: [SR-Users] Kamailio OPTIONS Round-Trip
by Soltanici Ilie 15 Jan '19

15 Jan '19

OK, that looks interesting - and I think I would able to generate such options from kamailio - but how do I measure the time for a response for this request? Is there any variables which can provide response time for some requests?

3 3

test
by AL RSM 14 Jan '19

14 Jan '19

1 0

N-Way call
by José Antonio Gutiérrez Delgado 14 Jan '19

14 Jan '19

Hi, I am trying unsuccessfully to create three calls from an already created call or, if possible, calls to n users. I do not know if I need an additional module or if I need to do it at the plot level. I have searched unsuccessfully for guides and manuals, so I would appreciate any kind of guidance. I use for MjSIP communication. 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.*

2 1

siptarce module and SIP-Replying Messages
by Mojtaba 14 Jan '19

14 Jan '19

Hello, I am using siptrace module in Kamailio. As you know, it sends a copy of signalling message for specific destination. Like HOMER project. Because of i won't run main route block in destination, i just have changed this block like below: request_route { //do some works. drop(); exit; } I know it would make a question in your mind why i do this? No problem, Let's come back to question. All things works correct except Replying SIP message. The destination is trying to relay Replying SIP message that it get from siptrace module in other server. How can i disable replying SIP mesages? With Best Regards --Mojtaba Esfandiari.S

2 1

Response VIA Header
by Soltanici Ilie 14 Jan '19

14 Jan '19

Hi, version: kamailio 5.1.6 (x86_64/linux) 7d1964 Also, i'm using force_rport(); in routing configuration file, but 'received' parameter anyway is missing :( Thank You.

2 5

RADIUS auth func diff
by morfair＠gmail.com 14 Jan '19

14 Jan '19

Hello! In auth_radius manual present two functions: radius_www_authorize() and radius_proxy_authorize(). What is the difference?

2 2

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

rtpengine in stateless kamailio
by Yuriy Gorlichenko 03 Jan '19

03 Jan '19

Hi! Happy new year to all!!! Look like I am first in this year wit hthe questions in this list :-). I'm using stateless kamailio and RTPengnine to build some kind of the stateless cluster I found that kamailio keeps some data in the SHMEM in case of using RTPengine module even if it is not a rtpengine_manage function but offer/answer/delete In this case if INVITE (offer) handled by 1-st kamailio in my cluster, and BYE/CANCEL handled by second kamailio in the cluster - 1-st kamailio (which has been used for offer) will hase kinda internal "memory leak" (in SHMEM it never decrased) At the rtpengine module source I found some transation dependencies for the rtpengine_manage function but did not find for the offer/answer/delete I supposed these 3 functions just sending requests to the rtpnegine with keys and not storing anything So my question - is it possible to use RTPengine module in stateless way to avoid internal "memory leak" because in my scenario I have big chance never receive BYE/CANCEL on the machine that started handle particular call

4 7

Re: [SR-Users] sr-users Digest, Vol 163, Issue 31
by Geovanny de Jesús García Rojas 03 Jan '19

03 Jan '19

estoy haciendo un trabajo con websockts y kamailio. Me gustaría saber como puedo vincular mi sevidor Kamailio instalado en una maquina virtual en el sistema operativo Ubuntu, como podria vincularlo con los websockets creados , me gustaria saber como es ese proceso. no tengo mucho conocimiento de ello.. espero su respuesta gracias El lun., 31 de dic. de 2018 a la(s) 06:00, < sr-users-request(a)lists.kamailio.org> escribió: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Phonenum Module (Soltanici Ilie) > 2. Re: Phonenum Module (Joel Serrano) > 3. Re: Phonenum Module (Joel Serrano) > 4. Re: Phonenum Module (Soltanici Ilie) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 30 Dec 2018 21:21:36 +0300 > From: Soltanici Ilie <iliesh(a)mail.ru> > To: sr-users <sr-users(a)lists.kamailio.org> > Subject: [SR-Users] Phonenum Module > Message-ID: <1546194096.91991005(a)f406.i.mail.ru> > Content-Type: text/plain; charset="utf-8" > > Hi All, > > How can i get Local Number by using phonenum module? > What is the variable for that? > > Thank You >

2 1

Phonenum Module
by Soltanici Ilie 30 Dec '18

30 Dec '18

Hi All, How can i get Local Number by using phonenum module? What is the variable for that? Thank You

2 3

Logging from cfg file
by Muhammad Allaudin 29 Dec '18

29 Dec '18

Hi everyone, I have recently started working on Kamailio, I am trying to learn the basics. For "Register" route, I am trying to print the log but log is not appearing in log file. Other logs are there, only this one is missing. *if(is_method("REGISTER")){* * log(2, "Register request");* *}* I will be really helpful if you can help me with this. Thanks & Kind Regards *Regards,* *M.Allaudin* *Software EngineerNowtel GroupPhone # +92-333-8291874Blogger @ allaudin.github.io <http://allaudin.github.io>*

5 5

A bit trick in msg_translator.c source file
by Mojtaba 29 Dec '18

29 Dec '18

Hello , Does anybody know why the lenght of both ip-address (s and name) in check_via_address function in msg_translator.c source file dose not check first? Actually i think it's better do. For example if via:192.168.122.1 and src:192.168.122.100, the result returned true, as they are not the same! With.Regards. Mojtaba Happy new year --Mojtaba Esfandiari.S

2 1

Re: [SR-Users] kamailio does not responde if an rtpengine is unreachable
by David Escartin 29 Dec '18

29 Dec '18

hello Daniel Thanks a lot for the update. We will also test it. It has not 100% relation with this issue, but i only wanted to share the setup we have for cases where a rtpengine fails having high traffic load, to minimize the impact on the kamailio processes. modparam("rtpengine", "queried_nodes_limit", 2) modparam("rtpengine", "rtpengine_retr", 2) modparam("rtpengine", "rtpengine_tout_ms", 350) considering we don't use sets with more than 2 rtpengine instances, at least for retry attempts. And your rtpengine instances are in the same network too. this works quite fine for us, there are some few secs of impact while the rtpengine is marked as disabled, but the system recovers quite ok. best regards david -----Original Message----- From: "Daniel-Constantin Mierla" <miconda(a)gmail.com> Sent: Friday, December 28, 2018 9:15am To: "Juha Heinanen" <jh(a)tutpro.com> Cc: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] kamailio does not responde if an rtpengine is unreachable I just pushed a series of commits trying to rework how loading (and reloading) of rtpegines list is done, to avoid that sync'ed probing, which can take long if any of the rtpengines is down. Now, building the local (per process) structures/sockets for rtpengines during kamailio start up is done without locking. This is guarded by the fact a reload command can be executed only after all children were initialized (added also with these commits). Moreover, the probing of rtpeningesis done only by child process 1, because the status is stored in shared memory list, so it is visible in all children. Based on my understanding there, doing probing from all processes is useless now, that was probably kept from the time when the list was not stored in shared memory, from the early rtpproxy times. There is also a restriction on how often the rtpengine list can be reloaded, now having a 10 seconds interval guard. I added this because the reload is done over the old list, not building a new list to swap with the old one. So it requires some time to walk through the existing list and update based on the new records. I went this way for now, even building a new list may be better/safer in long term, but it would require more work. I also wanted to avoid being very intrusive right now, given that those patches would need to be backported. The last relevant change was to use a version number to discover when a reload was done. So far, as I understood, it was relying on the number of rtpengines, but one may trigger a reload with same rtpengines, but different attributes (e.g., disabled or not). Having a version number is better in detecting when each worker needs to rebuild its local list of sockets, as well as for troubleshooting, because a value is increased with each reload, so easier to track if it was done or now. I didn't have time for any tests, so it would be good if you can test and report if works as expected. All related commits are in master, if they prove to work fine, we can backport all those patches. Cheers, Daniel On 26.12.18 12:46, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> I pushed a quick fix for the case when db support is not enabled, >> because these locks are useless in that case, so all children will do >> the rtpengine init at the same time, without waiting for the others: > Still took in rtpengine db mode about 2 minutes before kamailio became > responsive after start. > > -- Juha -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

kamailio does not responde if an rtpengine is unreachable
by Juha Heinanen 28 Dec '18

28 Dec '18

I noticed that if one rtpengine in a set is unreachable, kamailio 5.2 does start, but does not process any SIP requests. Is this intentional? -- Juha

5 26

Re: [SR-Users] Kamailio 5.2 0IMS configuration documentation
by Woscek, Martin W. 27 Dec '18

27 Dec '18

Hi Yasin, That VM was built with 4.3.4. It did help in fixing the scripts to build the pcsf, scscf and icscf databases. The config files are different and being that I need to understand the configuration and getting it up and running, isn’t helping much more. Being I need an IMS for lab testing, perhaps 4.3.4 does what I need, then maybe 5.2.0 is not required. Thanks, MArtin From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of YAS0 CANER Sent: Thursday, December 27, 2018 12:56 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [EXT] Re: [SR-Users] Kamailio 5.2 0IMS configuration documentation Hello i found it. https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/ Good luck Yasin caner YAS0 CANER <caner_yaso(a)hotmail.com<mailto:caner_yaso@hotmail.com>> şunları yazdı (27 Ara 2018 20:50): Hello, ims vmware snapshot was shared by Franz Edler in mailling list. it helps you to build it. Good luck iPhone’umdan gönderildi Woscek, Martin W. <mwoscek(a)mitre.org<mailto:mwoscek@mitre.org>> şunları yazdı (27 Ara 2018 19:53): Hi all, Ive been in the process of standing up an instance of Kamailio 5.20, in particular the IMS. The P-CSCF, I-CSCF and P-CSCF as well as the mysql are on this single VM. I’ve been slowly working thru the errors as I bring up the P-SCSF first. Can someone point me to detailed documentation for setting this up? What is the base minimum for basic IMS functionality (eg: do I need the mysql database)? Thanks, 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 _______________________________________________ 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

Kamailio 5.2 0IMS configuration documentation
by Woscek, Martin W. 27 Dec '18

27 Dec '18

Hi all, Ive been in the process of standing up an instance of Kamailio 5.20, in particular the IMS. The P-CSCF, I-CSCF and P-CSCF as well as the mysql are on this single VM. I've been slowly working thru the errors as I bring up the P-SCSF first. Can someone point me to detailed documentation for setting this up? What is the base minimum for basic IMS functionality (eg: do I need the mysql database)? Thanks, Martin

2 2

Dispatcher Probing
by Duarte Rocha 27 Dec '18

27 Dec '18

Greetings, I have Kamailio with the Dispatcher module and it's probing mechanics set up. I want to be able to access the OPTIONS request generated by Kamailio in the request_route or somewhere else in the configuration file in order to modify it. Is that possible? Best Regards, Duarte Rocha

3 4

xlog $mb produces ERROR
by Andrew Chen 27 Dec '18

27 Dec '18

Hey community, I'm currently trying to config our new 5.1.2 kamailio server and I want to xlog $mb. Whenever I do this, I get an ERROR logged to my syslog Dec 26 21:15:58 sjomainkama55 /usr/sbin/kamailio[5954]: {1 1 INVITE <padding>@<padding>} ERROR: <script>: INVITE sip:<padding>@ sjomainkama55.a.fuzemeeting.com:443 Does anyone know why this is? Also, I noticed I can't get rid of #012#015 at all. I modified the rsyslogd.conf file as instructed here: "i need to add the next line to /etc/rsyslog.conf "$EscapeControlCharactersOnReceive off" and when I did this, the control characters disappear but all it printed out was the first line of the SIP message. I also try to assign $mb to a $var() and do a {re.replace} on that string and that didn't work either. I ended up having to create a side script to parse the whole /var/log/syslog and do regex replace the #012#015 with real newline which is not what I really want for me or anyone else who needs to analyze the Kamailio logs. Please advise. 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.*

3 4

Re: [SR-Users] [EXT] Re: Using a network STUN Server
by Wilkins, Steve 27 Dec '18

27 Dec '18

Thank you, I just was not sure what else would cause the relayed packets to not be sent out to my fios router. As mentioned, I can pick any other server in my network and I can see, in the pcap file, that the relay is attempted to the selected server. I verified our ACL and it is it open for TCP output to any IP and Port so that is not the issue. -----Original Message----- From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Alex Balashov Sent: Wednesday, December 26, 2018 12:55 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [EXT] Re: [SR-Users] Using a network STUN Server As STUN is a client-side construct, I am not aware of any functionality Kamailio might have to make *use* of a STUN server for its own representations about its reachability. But I could be wrong. -- Sent from mobile. Apologies for brevity and errors. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

2 1

Fwd: Dialog getting disconnected as soon as call is ended
by Subham Singhal 27 Dec '18

27 Dec '18

---------- Forwarded message --------- From: Subham Singhal <subham.singhal(a)zemosolabs.com> Date: Sat, Dec 8, 2018 at 10:19 AM Subject: Re: [SR-Users] Dialog getting disconnected as soon as call is ended To: <miconda(a)gmail.com> Hello, I am getting this error in kamailio console. I thought websocket connection is getting disconnected before receiving bye message so I tried to keep tcp connection open. But that also didn't work. On Fri 7 Dec, 2018, 6:48 PM Daniel-Constantin Mierla <miconda(a)gmail.com wrote: > Hello, > > which application is printing that log message? > > Cheers, > Daniel > On 03.12.18 08:21, Subham Singhal wrote: > > Hello, > > I am new to kamailio. I have been trying to integrate kamailio with > asterisk. I am able to send INVITE and get RTP packets as well, but I am > unable to receive BYE from asterisk. Call is getting terminated through > following websocket error. > "WebSocket connection to 'wss://172.16.16.169:5061/' failed: One or more > reserved bits are on: reserved1 = 1, reserved2 = 0, reserved3 = 0." > > -- > Thanks and Regards > Subham Singhal > > _______________________________________________ > Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com > Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com > > -- Thanks and Regards Subham Singhal

1 0

Using a network STUN Server
by Wilkins, Steve 26 Dec '18

26 Dec '18

Hello All, Can I point Kamilio to use a STUN server located on my network? Kamilio will not relay to my fios router but will relay to other Servers on my network. Thank you,

2 1

stateless error reply used: transaction canceled
by Евгений Голей 26 Dec '18

26 Dec '18

Hello! I would be grateful if you could tell me what the causes of the error in Kamailio version 5.1.5. 2018-12-26T20: 28: 18.3875 "ERROR: tm [tm.c: 1545]: _w_t_relay_to (): t_forward_noack failed" 2018-12-26T20: 28: 18.3879 "ERROR: sl [sl_funcs.c: 362]: sl_reply_error (): stateless error reply used: transaction canceled (487 / SL)" B.R. Evgeniy

1 0

Merry Christmas and Happy Holidays!
by Daniel-Constantin Mierla 24 Dec '18

24 Dec '18

With the season holiday just starting, it's again a good time to express my thanks and greetings to all the friends, developers and community members that made 2018 another great year for Kamailio project. Enjoy the holidays! Merry Christmas! Daniel * Santa is flying Kamailio! * -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 - www.kamailioworld.com

2 1

app_python3 and kamailio 5.2.0 docker
by Grant Bagdasarian 24 Dec '18

24 Dec '18

Hello, I've pulled the Kamailio 5.2.0 Debian Stretch Docker image, and tried to load app_python3, but without success. It's also not in the Debian repository, at least not part of the kamailio-python-modules package. What is the current, recommended, way of installing the app_python3 module? Source files only? Regards, Grant

2 2

failure route is not executed when suspended invite is cancelled
by Koray Vatansever 24 Dec '18

24 Dec '18

Hi all, I'm trying to upgrade kamailio from 4.2.7 to 5.1.5 and I realized that when CANCEL is received for a suspended INVITE, failure route is not executed in release 5.1.5. In 4.2.7 failure route is executed for this scenario. Is this the expected behaviour or am I missing something?

2 7

Manipulate sip header on an in-dialog negative reply
by Olli Attila 24 Dec '18

24 Dec '18

Hello, We have a call case where our softswitch replies to in-dialog re-invite with "SIP 491 Request pending". This happens when a customer sip device is trying to re-invite the session too fast even though the softswitch is still processing the earlier request. Kamailio operates between this customer device and the softswitch. The softswitch is adding a P-Charging-Vector header to this SIP 491 reply which we want to drop (remove_hf...) from the reply when we route the SIP 491 message back to the customers device. I tried to drop this inside in-dialog failure route but it seems that Kamailio forwards the orginal 491 message statelessly to customer and the header still extists there eventhough failure route has deleted it. I guess this modification should be done in a sateful manner for Kamailio to actually write the changes to the outgoing reply towards the customer device. Any suggestions how the 491 reply could be edited and then forwarded onwards to the customer device? Cheers, --Olli

4 5

Large PDD
by Zhan Bazarov 22 Dec '18

22 Dec '18

Hello, I have kamailio+asterisk platform. Everything works fine. But, sometimes, for unclear reasons, the PDD(8000 and more) rises to an incoming call(at the stage when the call goes to an asterisk). I can not figure it out myself (SIP is clean, hardware metrics are ok) and it happens in random order (under load and without it). Anybody have ideas, what in can the reason?

2 1

Build Kamialio Docker Image Failed.
by Zhong, Alec (NSB - CN/Qingdao) 21 Dec '18

21 Dec '18

Hello, When we build kamailio image, the below error happened. At the same time, we can not access http://security.debian.org/debian-security/dists/jessie/updates/main/binary… Look like the Packages had been moved. Could you please help check below issue? Step 1/21 : FROM debian:jessie ---> 4eb8376dc2a3 Step 2/21 : MAINTAINER L. Mangani <lorenzo.mangani(a)gmail.com> ---> Running in ebf133dd0924 ---> 0abb8a3fcf82 Removing intermediate container ebf133dd0924 Step 3/21 : ENV HOME /root ---> Running in a92f7359fefd ---> e9872a1d4892 Removing intermediate container a92f7359fefd Step 4/21 : ENV DEBIAN_FRONTEND noninteractive ---> Running in eab86e90f492 ---> 25b976249d19 Removing intermediate container eab86e90f492 Step 5/21 : RUN apt-get update -qq ---> Running in e1132468ff42 W: Failed to fetch http://security.debian.org/debian-security/dists/jessie/updates/main/binary… 503 Service Unavailable E: Some index files failed to download. They have been ignored, or old ones used instead. The command '/bin/sh -c apt-get update -qq' returned a non-zero code: 100 make: *** [build] Error 100 Best Regards, Alec Zhong

3 3

Kamailio as an SBC - five years on
by Alex Balashov 20 Dec '18

20 Dec '18

Hi John, Sorry, I accidentally deleted your original e-mail and thus am breaking threading; my apologies for that. As a matter of fact, I wrote an article recently to address the very questions you ask: http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/ As always, it is a matter of professional opinion, and I do not speak for the project nor the intentions of the core developers. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 2

Rather noob question about functionality of Kamailio as an SBC
by John Millican 20 Dec '18

20 Dec '18

Hello, I have read the article at: https://likewise.am/2013/03/10/kamailio-as-an-sbc-session-border-controller/ Since this was written back in 2013, I was wondering if there has been any changes/additions/improvements in Kamailio since then that would have an impact on the conclusions made in the above article? Where I work we are in the process of 1) determining what functionality we need now and in the not too distant future 2) based on the choices made in #1, do we need a fully functional "professional" SBC or can we get away with a "pedestrian" SBC and use an application like Kamailio. Generalizations are ok of course but pointers to specifics would be awesome if possible. I know this list is not here to do my homework for me. I will be doing more research myself but I am sure there are many folks here that have gone down this road already and am hoping to benefit form their experience while I build my own knowledge. Thanks, John

1 0

Stateless non200 ACK processing
by Serge S. Yuriev 20 Dec '18

20 Dec '18

Hello, I'm trying to build pretty simple stateless proxy to stay between gw and softswitch. Most working properly but not for non200 ACKs. For some reason softswitch not accepting my ACK. Trace (note different branch in top Via for INVITE and ACK towards switch) https://pastebin.freeswitch.org/view/8f1433b0 Simplified script https://pastebin.com/u9DTSqcS I'm pretty new to this so believe doing something wrong. -- Serge S. Yuriev Senior VoIP engineer

2 4

TOPOS with Redis Issues
by Aleksandar Sosic 20 Dec '18

20 Dec '18

Hi Guys, We're having issues trying to use redis as the db for topos. The conf is the following: ``` ... loadmodule "ndb_redis.so" loadmodule "topos.so" loadmodule "topos_redis.so" ... modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379;db=1") modparam("topos", "storage", "redis") modparam("topos", "dialog_expire", 12600) modparam("topos_redis", "serverid", "srv1") ... ``` We've tried also with a redis server running on another machine with no success. The errors I've got in the kamailio logs are the following: ``` 2(22) ERROR: dialog [dlg_handlers.c:212]: populate_leg_info(): empty CSeq number 2(22) ERROR: dialog [dlg_handlers.c:506]: dlg_onreply(): could not add further info to the dialog ``` and ``` 17(37) ERROR: dialog [dlg_req_within.c:117]: build_dlg_t(): invalid cseq 17(37) ERROR: dialog [dlg_req_within.c:383]: send_bye(): failed to create dlg_t 17(37) ERROR: dialog [dlg_req_within.c:87]: build_dlg_t(): no contact available 17(37) ERROR: dialog [dlg_req_within.c:383]: send_bye(): failed to create dlg_t ``` Kamailio version used is this: 5.2.0+0~20181218003543.18+xenial Thanks in advance for your time, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 3

Default memory
by Duarte Rocha 20 Dec '18

20 Dec '18

Greetings, How can i ibcrease permanently the Kamailio default private and shared memory size? Thanks in advance, Duarte Rocha

4 3

Memory allocation
by Duarte Rocha 19 Dec '18

19 Dec '18

Greetings, I have some things that i want to udnerstand about Kamailio's memory allocation. My settings are 1024Mb for shared memory and 12Mb for private memory. I'm running Kamailio on a machine with CentOS7 and 2Gb of RAM. As i understand, at startup Kamailio will allocate 1024+12*number_of_processes megabytes of memory. Is this correct? When i set up Kamailio to run with 150 processes, after starting, i still have 500Mb of free RAM and therefore not allocated to any process. That goes against what i wrote earlier. What is the best way to plan for memory specs in my machines according to the desired number of processes and shared\private memory defined? Best Regards, Duarte Rocha

2 1

reg_fetch_contacts always returns -1
by Denys Pozniak 19 Dec '18

19 Dec '18

Hello! I want to get some parameters from user location database via function reg_fetch_contacts(). But it returns -1 and $(ulc(caller=>aor)) is <null> respectively. Please help me to understand where issue is. Script: ... $var(c_uri)="sip:+1234567890@10.10.10.10:5065"; reg_fetch_contacts("location","$var(c_uri)","caller"); $var(rc) = $rc; xlog("L_WARNING","[LOCATION] caller=>aor: rc=$var(rc) aor=$(ulc(caller=>aor)) \n"); ... [root@kamailio]# kamcmd ul.lookup location customer1 { AoR: customer1 Contacts: { Contact: { Address: sip:+1234567890@10.10.10.10:5065 Expires: 861 Q: -1.000000 Call-ID: 00DB5F27-0B02-E966-92C3-A231C378F993(a)10.10.10.10 CSeq: 1787 User-Agent: SIPPER for PhonerLite Received: sip:2.2.2.2:15043 Path: [not set] State: CS_SYNC Flags: 0 CFlags: 64 Socket: udp:3.3.3.3:5060 Methods: 8095 Ruid: uloc-1-5c1a3512-66a6-1 Instance: <urn:uuid:00FB3C49-24E8-E811-ACAA-D72FCD766436> Reg-Id: 0 Server-Id: 1 Tcpconn-Id: -1 Keepalive: 1 Last-Keepalive: 1545232794 Last-Modified: 1545232794 } } } [root@kamailio]# kamailio -v version: kamailio 5.1.6 (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_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: unknown compiled on 13:53:57 Nov 12 2018 with gcc 4.8.5 -- BR, Denys Pozniak

1 2

RFC: updates to some core functions
by Daniel-Constantin Mierla 19 Dec '18

19 Dec '18

Hello, it was brought into discussions several times in the past about core functions not accepting variables in the parameters. I think it is time to update them during the 5.3 release development. For few of them, I added in the past some alternative function in the corex module (e.g., force_send_socket() in core and set_send_socket() in corex module). So, I see two options: 1) add a function with similar name in corex module and same behaviour like the one from core 2) remove the function export from the core and export one with the same name from the corex module First one will ensure that configs using the functions right now keep working without any update. The second one will be better in long term from the point of documentation (no duplicated docs), but there might be few cases that would require updates in the config -- iirc, there are some functions that can get special tokens in the parameters (like forward(uri:host, uri:port)), they will get an equivalent with variables, but old config will not be compatible. Obviously the reason for this email is to ask the developers and users what would be the preferred way from own point of view. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

7 11

passing $avp to t_relay functions.
by YAS0 CANER 19 Dec '18

19 Dec '18

Hello , is there a way to pass $avp values to t_relay function. i tried ; t_relay t_relay_udp/tcp t_relay_to t_relay_avp functions log 0(75155) ERROR: tm [tm.c:2456]: fixup_t_relay_to(): fixing ($avp(dd), 1) 0(75155) ERROR: tm [tm.c:2459]: fixup_t_relay_to(): param type 8 0(75155) ERROR: tm [tm.c:2456]: fixup_t_relay_to(): fixing ($avp(flags), 2) 0(75155) ERROR: tm [tm.c:2459]: fixup_t_relay_to(): param type 11 0(75155) CRITICAL: tm [tm.c:2549]: fixup_t_relay_to(): invalid flags <$avp(flags)> 0(75155) ERROR: <core> [core/route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio/kamailio.cfg:489 0(75155) ERROR: <core> [core/rvalue.c:3860]: fix_rval_expr(): failure in cfg at line: 489 col: 42 0(75155) ERROR: <core> [core/route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio/kamailio.cfg:494 0(75155) ERROR: <core> [core/route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/etc/kamailio/kamailio.cfg:495 in addition i have a look code , in fixup functions try to resolve host values so parameteres cannot find $avp . in conclusion , does kamailio need new function to pass $avp value? Can i try to code? Thanks.

2 6

Kazoo module problem.
by Володимир Іванець 18 Dec '18

18 Dec '18

Hello! I'm trying to test kazoo module but unfortunately it is not loading: *0(25107) ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/lib64/kamailio/modules/kazoo.so>: /usr/lib64/kamailio/modules/kazoo.so: undefined symbol: event_set* It was built today together with other modules and Kamailio itself today from branch 5.2 on CentOS 6. librabbitmq version is 0.5.2-1. Does anyone has it running and if so what version is it? Thanks a lot!

3 4

Access to tables like location, imc_rooms and imc_members when kamailio is running
by hamidreza ramezani 18 Dec '18

18 Dec '18

Hello everyone I have a question regarding kamailio database, I see when kamailio is stopped, usrloc -> location and imc -> imc_rooms module tables shows some information. but when kamailio is running it's not. is it possible to manually insert to these tables, I don't want to use IMC commands like #join #accept ... is it possible to access location table and see which users are registered when kamailio is running? Best regards Hamid

2 1

Routing of Audio and Video Stream.
by Abhijit Dutta 18 Dec '18

18 Dec '18

Hi All, Is it possible to redirect only the audio stream towards Asterisk from Kamailio (Proxy) via RTPEngine and not to send the video stream to Asterisk. I am yet to get the complete reason why my client wants this to happen though. Thanks Abhijit

5 12

Re: [SR-Users] Setup dmq_usrloc
by Gertjan Wolzak 17 Dec '18

17 Dec '18

Hello Kamailions, Reading and understanding is a skill in it self.. Learned a bit more of that this morning. To be able to use the dmq_ursloc, just use: if(is_method("KDMQ")) { dmq_handle_message(); } So, I have registrar replication working, on with reading to get the rest working. With regards, Gertjan

2 1

Setup dmq_usrloc
by Gertjan Wolzak 17 Dec '18

17 Dec '18

Hello Kamailions, Im trying to setup registration replication with the use of the dmq and dmq_usrlog modules. I have configured two servers, configured kamailio on both. When I register a sip client on the one I get a nice KDMQ message on the second server, but the second server reacts with a 404 not found: U 2018/12/17 05:08:38.974495 10.10.0.1:6000 -> 10.10.0.2:6000 #3 KDMQ sip:usrloc@10.10.0.2:6000 SIP/2.0. Via: SIP/2.0/UDP 10.10.0.1:6000;branch=z9hG4bK00ed.e1666b85000000000000000000000000.0. To: <sip:usrloc@10.10.0.2:6000>. From: <sip:usrloc@10.10.0.1:6000>;tag=a2652bb825a097f3b7285d4c70edd51a-0513. CSeq: 10 KDMQ. Call-ID: 35571d0247178282-3780(a)10.88.77.172. Content-Length: 360. User-Agent: kamailio (5.1.6 (x86_64/linux)). Max-Forwards: 1. Content-Type: application/json. . {"action":2,"aor":"test01(a)10.88.77.172","ruid":"uloc-5c177363-ec4-1","c":"sip:test01@10.88.77.140:59293;ob","received":"","path":"","callid":"zjucvmzUT2hNJCIfqeUXEsOaEzyHCs-4","user_agent":"CSipSimple_G3121-26/r2457","instance":"","expires":1545041786,"cseq":24435,"flags":0,"cflags":0,"q":-1,"last_modified":1545040886,"methods":8159,"reg_id":0,"server_id":0} U 2018/12/17 05:08:38.979062 10.10.0.2:6000 -> 10.10.0.1:6000 #4 SIP/2.0 404 Not Found. Via: SIP/2.0/UDP 10.10.0.1:6000;branch=z9hG4bK00ed.e1666b85000000000000000000000000.0;rport=6000. To: <sip:usrloc@10.10.0.2:6000>;tag=02f7a7b91eadf5e07797231cb2f64326-b794. From: <sip:usrloc@10.10.0.1:6000>;tag=a2652bb825a097f3b7285d4c70edd51a-0513. CSeq: 10 KDMQ. Call-ID: 35571d0247178282-3780(a)10.88.77.172. Server: kamailio (5.1.6 (x86_64/linux)). Content-Length: 0. . I think I have to configure a bit more than just the parameters of the dmq and dqm_usrloc modules. Ive googled, looked in the Sip routing with kamailio book, but no luck. Did not see any examples in the kamailio source, with regards to the dmq_usrloc module. I am not looking for direct answers, have not provided you with enough information for that, but I would appreciate information on how to correctly configure registration replication using the dmq/dmq_usrloc module... Thank you. With regards, Gertjan

1 0

Reminding again about private/direct emails from mailing lists discussions
by Daniel-Constantin Mierla 17 Dec '18

17 Dec '18

I see that still a lot of emails are sent directly to me after a discussion started on public mailing lists (subject with mailing lists prefix, but the sender header is not the mailing list daemon), I would like to remind that, at least in my case, writing emails directly without cc-ing the mailing list is highly not recommended and there is practically 0 chance to get an answer from myself. The rule is also suggested in the mailing lists presentation page: - https://www.kamailio.org/w/mailing-lists/ Unless I asked explicitly for a private email with some specific details, the message will not be noticed in decent time and therefore not replied. I use this email address for many public mailing lists and it is intended only for that usage, I am reacting based on the filters I created, unmatched messages getting the lowest priority. Therefore if you wrote me and expect a response, re-send the message to the appropriate public mailing list. Checking and answering the messages on Kamailio mailing lists are among the top of priorities on my daily activity, so it is high chance you get the response faster when you write there. Note that you can always mask sensitive data (e.g., replace passwords, IP addresses) before sending logs or config file. There are several common sense as well as technical reasons for keeping the discussion on public mailing lists. Here are some along with other suggestions to improve the likeliness of getting an answer: - we are not answering questions on mailing lists to help only one person, but also other people that may have similar issues in the future -- they can find the answers in the archive with a search engine. Also, other people subscribed to the list can learn from conversation or contribute to the discussion, resulting in better outcome - the amount of unexpected messages is very high -- it is practically a zero chance to get to the folder with messages that didn't match any filter (thus your message is not going to be replied) - whenever I find time, the first emails I answer are those coming on mailing lists. They are many there as well, people are traveling or having other personal or business projects, so sometime is good to send a reminder if a question does not get an answer - starting with negative approach or no technical content, like you are going to use something else if you don't get a reply instantly, or this application is missing what so ever tutorial giving exactly the solution you need, or simply asking for full config of complex requirements, is not helping at all, but actually making people to ignore your messages. Start with what you tried and where you got stuck. Everything you get is for free, have appropriate expectation and behavior. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

P-CSCF without Rx interface
by Tsvetan Filev 17 Dec '18

17 Dec '18

Hi All. May be this has been asked before but I was not able to find an answer. I setup IMS with 3 instances of kamailio: P-CSCF, I-CSCF and S-CSCF (I got the config files from here https://github.com/kamailio/kamailio/tree/master/misc/examples/ims). I would like to register two clients to the IMS and make a VoLTE like call. So I want to setup my P-CSCF to send SIP messages to my I-CSCF without Rx interface (without using PCRF). I'm not able to find how to tell P-CSCF where to direct the sip traffic. It obviously should happen in route[REGISTER]. Right now P-CSCF sends all REGISTER requests to itself and goes to a loop. Regards.

3 3

Sending to an announcement server from a failure_route
by Boden Garman 17 Dec '18

17 Dec '18

Hi list, I'm trying to play an announcement for my users when my PSTN gateway responds with a 404 Not Found (Reason: Q.850;cause=3), indicating a wrong number. I'm a bit lost and would appreciate any advice. What I am seeing is two parallel SIP invites, one to my announcement server (hooray!) and one to the PSTN gateway again (which I don't want). How do I stop the original branch from starting again? I've tried changing the order of rewritehostport and append_branch without any difference. I've also tried to use t_relay() instead of the RELAY route. I'm using Kamailio 5.1 and have modified the deafult kamailio.cfg Thanks! Boden I think this is the relevant parts of the config: # PSTN GW routing route[PSTN] { [PSTN regex logic omitted] # classify as an outbound call set_dlg_profile("outbound_calls"); # select a PSTN gateway from the dispatcher if (!ds_select_dst("66", "8")) { send_reply("404", "No destination"); exit; } # failover if the selected PSTN gateway is down t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } # Try next destinations in failure route failure_route[RTF_DISPATCH] { xlog("inside RTF_DISPATCH"); if (t_is_canceled()) { exit; } # wrong number from PSTN if (t_check_status("404")) { append_branch(); append_hf("X-Application: announcement\r\n"); append_hf("X-Announcement-Playback: wrong-number\r\n"); route(TO_ANNOUNCEMENT); exit; } # next DST - only for 500 or local timeout if (t_check_status("500") or (t_branch_timeout() and !t_branch_replied())) { xlog("selecting next destination"); if (ds_next_dst()) { t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } # Routing to announcement server route[TO_ANNOUNCEMENT] { if (!is_method("INVITE")) { return; } rewritehostport('ANNOUNCEMENT_SERVER:5060'); route(RELAY); exit; }

2 3

Problem with selection Transport Protocol - MultiHomed Problem
by YAS0 CANER 17 Dec '18

17 Dec '18

Hello , i have trouble about selection transport protocol. i have tried so many thing but couldnt find TM selected which IPv? and protocol type (TCP or UDP) For example; i have 2 interface ipv6 and ipv4. i will route my message (INVITE-Register etc.) another node that use TCP and IPV6 , domain name is test1.test. TM module or some module resolve this domain to IPV6:UDP but i want to sent it over IPV6:TCP socket. so i cannot know which protocol is resolved and cannot route the right socket. $du variable show only sip:ali@test1.test Conclusion : There isn't any pseudo value about which destination of IP version will use. Thanks Flow: UAC (IPv4:UDP) ----------> Kamailio (MultiHomed) ----> (TCP:IPv6)Kamailio ---- Kamailo (multiHomed ) cfg ------ auto_bind_ipv6=1 dns_try_ipv6=yes dns_retr_time=1 dns_retr_no=1 dns_cache_flags=4 mhomed=1 fork=yes tcp_source_ipv6 = [fd61:c23c:b3b6::5] listen=tcp:[fd61:c23c:b3b2::5]:5060 listen=udp:[fd61:c23c:b3b2::5]:5060 listen=udp:192.168.1.107:5060 listen=tcp:192.168.1.107:5060 route []{ if($dP=="TCP"){ xlog("L_INFO","[route] [TCP] 1\n"); if (!t_relay_to_tcp()) { xlog("L_ERR", "Error t_relay [route] \n"); t_reply("500","Server - ERROR "); exit; } } else if($dP=="TCP"){ xlog("L_INFO","[route] [TCP] 2\n"); if (!t_relay_to_tcp()) { xlog("L_ERR", "Error t_relay [route] \n"); t_reply("500","Server - ERROR "); exit; } }else if($dP=="UDP"){ xlog("L_INFO","[route] [UDP] 1\n"); if (!t_relay_to_udp()) { xlog("L_ERR", "Error t_relay [route] \n"); t_reply("500","Server - ERROR "); exit; } }else{ xlog("L_INFO","[route] [??] 1\n"); if (!t_relay()) { xlog("L_ERR", "Error t_relay [route] \n"); t_reply("500","Server - ERROR "); exit; } } }

2 5

Re: [SR-Users] sr-users Digest, Vol 163, Issue 15
by Toufic Mobarak 17 Dec '18

17 Dec '18

Tnhxtx Regards, Toufic Mobarak > On Dec 15, 2018, at 6:00 AM, sr-users-request(a)lists.kamailio.org wrote: > > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Re: Routing of Audio and Video Stream. (Daniel-Constantin Mierla) > 2. Problem with selection Transport Protocol - MultiHomed > Problem (YAS0 CANER) > 3. Re: Problem with selection Transport Protocol - MultiHomed > Problem (YAS0 CANER) > 4. Re: Routing of Audio and Video Stream. (Sergiu Pojoga) > 5. Re: Problem with selection Transport Protocol - MultiHomed > Problem (Daniel-Constantin Mierla) > 6. Issue on kamailio 4.1.9 of database reconnection (Emmanuel BUU) > 7. Re: Routing of Audio and Video Stream. (Abhijit Dutta) > 8. Re: Routing of Audio and Video Stream. (Abhijit Dutta) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 14 Dec 2018 12:54:44 +0100 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.kamailio.org>, Abhijit Dutta <duttaa(a)hotmail.com> > Subject: Re: [SR-Users] Routing of Audio and Video Stream. > Message-ID: <26c51f12-5242-4794-5124-f37bc523c7ae(a)gmail.com> > Content-Type: text/plain; charset="windows-1252" > > Hello, > > > I guess you still need to send the INVITE to Asterisk, right? > > > Cheers, > Daniel > > >> On 14.12.18 11:15, Abhijit Dutta wrote: >> Hi All, >> >> Is it possible to redirect only the audio stream towards Asterisk from >> Kamailio (Proxy) via RTPEngine and not to send the video stream to >> Asterisk. I am yet to get the complete reason why my client wants this >> to happen though. >> >> Thanks >> Abhijit >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com > Kamailio Advanced Training -- www.asipto.com > >

2 1

Automating installation
by John Tuxies 14 Dec '18

14 Dec '18

Hi all. I am new to this and i would like some help please. I am looking to deploy Kamailio and Asterisk in my systems and i would like to automate the process. I have found a bash script but it it outdated from here: https://github.com/gurumelo/asteriskkamailio i did some changes and modifications to adapt it to newer version of software, but it fails to start Kamailio and continue to Asterisk. I would appreciate if someone could help me with this script and make it work. The systems i am planning to execute it is in Debian 9 and Ubuntu 18.04 server, both 64bit. Sincerely yous, John

8 21

FreeBSD Kamailio pkg
by Sergiu Pojoga 14 Dec '18

14 Dec '18

Did anyone notice that when installing Kamailio from FreeBSD package, by default, it accepts registration with whatever account credentials? Not sure if it's like that with other OS packages (usually I install it from source), but this behavior kind of doesn't go with the popular saying that Kamailio by default "does nothing", lol. Regards, --Sergiu

3 4

Kamailio ERROR: _reply_light(): can't generate xxx reply when a final yyy was sent out
by Olli Attila 13 Dec '18

13 Dec '18

Hello, I'm getting these error messages on kamailio log from time to time: Dec 11 19:18:30 /usr/sbin/kamailio[23913]: ERROR: tm [t_reply.c:482]: _reply_light(): can't generate 487 reply when a final 200 was sent out Dec 8 04:44:56 /usr/sbin/kamailio[14960]: ERROR: tm [t_reply.c:482]: _reply_light(): can't generate 487 reply when a final 486 was sent out Dec 5 07:46:04 /usr/sbin/kamailio[14961]: ERROR: tm [t_reply.c:482]: _reply_light(): can't generate 487 reply when a final 480 was sent out Kamailio is configured to act as a proxy between SBC and a softswitch. According to the signaling we can see that these errors occure when the SBC sends CANCEL message towards Kamailio when at the same time final reply is received from the Softswitch side. The call seems to be teared down nicely and finally Kamailio replies to SBC by sending "200 ok, no more pending brances". I guess Kamailio treats this situation as an error because the sip processing engine has sent the final reply out and at the same time SBC sends the CANCEL to Kamailio. Is there any way we could handle this situation better on Kamailio end? The three example ERROR messages are from cases where B subscriber has answered the call, the B has been busy and the last one is from a case where B subscriber has been temporarily unavailable. Cheers, Olli

2 4

is_e164 logic to detect valid number
by Patrick Wakano 11 Dec '18

11 Dec '18

Hello list, Hope you are all doing fine! I am using the is_e164() function to validate the number we receive, and I come to see that the number +555 was accepted.... After some googling it looks like(it is not very clear though) that 7 digits are the minimum we could have for e164 numbers but after checking the source code, I saw it accepts anything starting with + and having between 2 and 16 numbers. So is it really valid to have a number with just 2 digits? What is the case? Thank you, Kind regards, Patrick Wakano

5 7

Performance tests of native vs. kemi scripting for SIP routing
by Daniel-Constantin Mierla 11 Dec '18

11 Dec '18

Hello, during the preparations of Kamailio v5.2.0 and the days after, I got the time to run some tests in order to see the differences of running similar SIP routing logic when using native configuration file scripting versus KEMI languages. So far I did it for Lua and Python (v2), hopefully I will find time to run also for the rest of supported scripting languages: Python (v3), JavaScript, Ruby, Squrrel and Lua with LuaJIT. The pleasant surprise was to see that this time, the results of using Python were similar to native scripting and Lua. When I did some basic tests during development of KEMI, using Python seemed slower. More details about how tests were performed, the config files/scripts, used tools and results were published in a wiki page: - https://www.kamailio.org/wiki/kemi/performance-tests/5.2.x A news article with further details is on kamailio website: - https://www.kamailio.org/w/2018/12/performance-tests-for-kemi-scripting-lan… Should anyhow of you have some time to run the tests in own environment and share the results (on sr-users mailing list), it would be appreciated and would help to validate the tests and discover if I forgot something in any of the configs. Note that the goal of the tests is not measuring the capacity of Kamailio in your environment, but see the differences between using different scripting languages in the same environment (so you can do the tests on raspberry pi, if you like). I would also be interested in knowing if you are using Kamailio with KEMI or you are planning to, if yes, which scripting language. If already doing it, is already in production? These are useful to plan where to allocate developer resources in the future... And to start, I am running Kamailio with Lua (4 instances) and Python (1) scripting in production deployments, with very good results so far. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training -- www.asipto.com

2 2

core at kamailio 5.1.6
by David Escartín 11 Dec '18

11 Dec '18

hello all we are seeing in a new kamailio instance some crashes. We are not sure the root cause, here you have the last core generated https://pastebin.com/xMRrug2X COuld you please take a look to see if there might be any issue with the last message that caused the core (to me seems normal) or there might be some issues related to other system libraries, etc? thanks a lot and regards david

3 7

DTLS HA redis-pacemaker-corosync
by Жан Базаров 10 Dec '18

10 Dec '18

Hello! Are there any ways to implement using DTLS in redis HA scenario? When I reboot the active RTPEngine server the system correctly fails over to the other server and, after only a small pause (~1s), incoming audio continues to arrive. However, approximately 15 seconds after this I hear nothing but silence. Thanks.

2 1

Kamailio World 2019 - Call for Presentations
by Daniel-Constantin Mierla 10 Dec '18

10 Dec '18

Hello, I would like to announce that Call for Presentations at Kamailio World 2019 is now open. You can submit your proposal or see more details at: - https://www.kamailioworld.com/k07/call-for-speakers/ The 7th edition of the event takes place again in Berlin, Germany, during May 6-8, 2019. Expect over 150 participants, developers and community members as well as representatives from other popular open source VoIP projects such as Asterisk or FreeSwitch. Looking forward to meeting many of you there! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training -- www.asipto.com

1 0

SIP SIMPLE TO XMPP AND VICE VERSA
by sagar malam 08 Dec '18

08 Dec '18

Hello, We have a system which using FreeSWITCH for calls and Ejabberd( XMPP) for chat.Now we want to support SIP SIMPLE as well.But we are not going to move old users to SIP SIMPLE but only new users will use SIP SIMPLE.This leads to requirement of having SIP-XMPP gateway for which are are considering Kamailio server. I have gone through documentation about Kamailio XMPP module, it is clear that Kamailio can convert SIP MESSAGE to XMPP so SIP to XMPP will work but what about XMPP to SIP MESSAGE ? Does that work as well ? Thanks in advance. -- Thanks, Sagar

2 2

Dialplan Module limits
by Enrico Bandiera 07 Dec '18

07 Dec '18

Hi guys, does anyone know which are the limits of the diaplan module? After how many entries I will encounter serious performance issues? Thanks, Enrico.

2 1

question about replace_body_all
by Wilkins, Steve 07 Dec '18

07 Dec '18

Hello, I am attempting to change the Message Body of an SIP message using replace_body_all; I want to replace all attributes that start with rtcp. Here is my code => replace_body_all("rtcp:{1}[0-9]{5,}", newstring), and I call msg_apply_changes() after this call. Note that I verified that the regex is working using search. The problem is that nothing gets changed. However, what I do get is a new string at the bottom of the Message Body with my newstring concatenated three times, which happens to be the number of times that rtcp occurs in the Message Body. Note, I am doing this so that I can add the IP address to the rtcp attribute because this is required by a Provider. Any ideas? Thank you, -Steve

3 2

Dialog getting disconnected as soon as call is ended
by Subham Singhal 07 Dec '18

07 Dec '18

Hello, I am new to kamailio. I have been trying to integrate kamailio with asterisk. I am able to send INVITE and get RTP packets as well, but I am unable to receive BYE from asterisk. Call is getting terminated through following websocket error. "WebSocket connection to 'wss://172.16.16.169:5061/' failed: One or more reserved bits are on: reserved1 = 1, reserved2 = 0, reserved3 = 0." -- Thanks and Regards Subham Singhal

2 1

Auth_xkeys module - freeing already freed pointer
by José Seabra 06 Dec '18

06 Dec '18

Hello there, I'm constantly getting the following message when i'm using module auth_xkeys. CRITICAL: <core> [core/mem/q_malloc.c:514]: qm_free(): BUG: freeing already freed pointer (0x7f6310987400), called from core: core/data_lump.c: free_lump(466), first free core: core/data_lump.c: free_lump(466) - ignoring Apparently kamailio only throw this message but i would like to know if its a normal protection from kamailio or it should be fixed? Thank you for the support Regards -- José Seabra

3 5

Assistance with re.subst & newline
by Mark Hall 06 Dec '18

06 Dec '18

Hi, I am using rtpengine to proxy audio to/from media servers. The outbound calls are being rejected by a couple of my carriers (although accepted by others), and the closest that I have been able to find for the reason is the inclusion of "a=rtcp:xxxxx" in the SDP generated by rtpengine. To test further, I am trying to remove this line. Rtpengine itself doesn't have any options to remove it, so I am left with manipulating the generated SDP in Kamailio. A sample of generated SDP is: a=maxptime:150 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:18 annexb=no a=fmtp:101 0-16 a=sendrecv a=rtcp:30939 s=My Media Server I am using rtpengine_manage("RTP/AVP ICE=remove"); to generate the SDP to a variable ($avp(sdp)) Now, I am trying to just remove the whole a=rtcp line with re.subst $avp(sdp)=$(avp(sdp){re.subst,|a=rtcp:[0-9]*\R||s}); *** Tried / as delimiter also, but | looks cleaner *** This should match the line and any CR/LF characters - BUT in results, nothing is changed (various online Regex testers show this match to be correct - I tried \r\n also). If I do the same but without the \R, then the line is removed but not the CR/LF, leaving a gap in the SDP - which is invalid. $avp(sdp)=$(avp(sdp){re.subst,|a=rtcp:[0-9]*||s}); Gives: a=maxptime:150 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:18 annexb=no a=fmtp:101 0-16 a=sendrecv s=My Media Server Can anyone see where I am going wrong, or suggest an alternative? Kind Regards, Mark Hall

3 3

New features: dialog - list dialogs via rpc using matching expressions
by Daniel-Constantin Mierla 06 Dec '18

06 Dec '18

Hello, being discussed and requested couple of times via lists, irc channel and discussions at events world wide, I just want to send a short note to announce that yesterday I pushed a new rpc command to dialog module that returns dialog records that match on conditions applied to request uri, from uri, to uri or callid fields. The filtering can be done with string comparison, regular expression or starts-with (prefix) matching. See more details at: - https://www.kamailio.org/docs/modules/devel/modules/dialog.html#dlg.r.list_… It should enable listing dialogs only for specific users, caller or callee, without dumping all dialogs. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 0

set_advertised_address
by Kjeld Flarup 06 Dec '18

06 Dec '18

Hello I have a PBX behind NAT. Thus I advertise the public IP, and forwards the port to my PBX. listen=LOCALIP:5070 advertise EXTERNALIP:5070 Now clients can connect to the PBX from the Internet. And also inside the LAN, because I have enabled NAT loopback. However some customers sysadmins complains that NAT loopback is a security risk. I have not been able to find any exploits of this, but the sales and support people asks if it is possible to remove this NAT loopback requirement. I could look at $rd and if it is local, then I could advertise LOCALIP. I found set_advertised_address("LOCALIP"); set_advertised_address however only seems to modify the latest Via header, not the Record-route, and audio neither works. Could I do something to make this work, or is it a dead end? -- -------------------- Med Liberalistiske Hilsner ---------------------- Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49 Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

4 11

Dispatcher clear dst_avp
by Grant Bagdasarian 05 Dec '18

05 Dec '18

Hello, I'm trying to use multiple destination sets which may include the same destination. For instance: SET ID: 1 sip:10.0.0.1:5060 sip:10.0.0.2:5060 SET ID: 2 sip:10.0.0.1:5060 Whenever a new SIP INVITE is sent to the Kamailio instance it will use SET ID 1. If then for some reason this call attempt fails, failure_route will trigger and SET ID 2 will be used. At first glance this might not make any sense, but there is some business logic behind this, but it's not relevant for this case. For some reason, the dst_avp variable still contains the destinations of SET ID 1 in failure_route. Is there a built-in way to reset this variable for every call to ds_select_domain(), such that only the destinations of passed SET ID will be loaded into the avp? I tried setting the avp to $null before calling ds_select_domain, but that had some undesirable effects. The reason I'm asking this is the destinations the call is being sent to are Freeswitch instances, which will return a 482 Request Merged when the same INVITE is sent to the same Freeswitch within 4 seconds (default T4 timer). I'm trying to match the previously selected destination in failure_route with the next destination and skip if they're the same, or stop processing when they are the same and no more destinations are available. I know I can mess with the T4 timer in Freeswitch and perhaps even sleep in failure route to deal with the 482 failure, but I rather fix this in a normal way. Regards, Grant Bagdasarian Senior Developer

2 2

xlog issue
by Soltanici Ilie 04 Dec '18

04 Dec '18

Hello, I have a strange situation by using xlog module. I don't know for what reason I'm not receiving all logs generated by kamailio. This is the configuration which I'm using in kamailio.cfg: log_facility=LOG_LOCAL0 log_name="kamailio" log_prefix="{$rm ($mt) | Seq=$cs | Source IP=$si ($proto) | Call ID=$ci} " # ----- xlog ----- modparam("xlog", "buf_size", 8192) modparam("xlog", "long_format", 0) modparam("xlog", "force_color", 1) modparam("xlog", "log_colors", "L_ERR=cr;L_WARN=px,L_INFO=px") This is rsyslog configuration file: local0.* /var/log/kamailio/kamailio.log Kamailio is running under kamailio user, permission for the log file are as shown below: -rwxrwxr-x 1 kamailio kamailio 252885132 Dec 2 14:51 /var/log/kamailio/kamailio.log In request_route block this is the first line: xlog("L_INFO","[START ROUTING]-(Source IP=$si:$sp/Destination IP=$Ri:$Rp)\n"); The problem is that not every request is logged in the log-file. For example, some "INVITES" requests I can find in the log file, but some of them - I cannot, even that in sngrep I see the request and the call is successfully processed by kamailio. Also, for some requests i can see only partial data, not full call-flow as it supposed to be (for ex. i see only BYE requests, or ACK response instead of full call flow). Does someone have the same issue? If you don't - how are you dealing with kamailio log files? I'm thinking to send them to the central ELK stack, but if I have such problems by saving them locally - I don't see any reason to send them elsewhere. I may think that the problem could be in rsyslog itself, but how can I troubleshoot that? The traffic on the server is not very high - 30-50 concurrent calls. As a storage i'm using an SSD disk and xfs filesystem. Load on the disk - according to iostat/iotop - is minimum. OS: CentOS Linux 7 (Core), Kamailio: 5.2.0 (x86_64/linux) 535e13 Thank You.

3 9

presence/mwi issue
by Andreas Granig 04 Dec '18

04 Dec '18

Hi, Currently playing with presence_mwi in kamailio 5.1, and it appears the issue reported by Juha two years ago at https://lists.kamailio.org//pipermail/sr-dev/2016-September/036609.html seems to have appeared again somewhere along the way. I’m sending a PUBLISH with message-summary event type, however I’m getting this error: ERROR: presence [presentity.c:283]: check_if_dialog(): failed to parse xml document As said in the old thread, it’s not an XML document, so it shouldn’t try to treat it as such. Any ideas? Best, Andreas

2 8

Dispatcher with a naptr address as destination
by José Seabra 04 Dec '18

04 Dec '18

Hello all, I'm trying to use a naptr address as a dispatcher destination and i'm facing some issues here. When i configure a naptr address in dispatcher table, like: *1:1:sip\:proxy-registrar-ci1.fuze.domain:0:0:'':''* I see kamailio making a dns query of type A, but since that this name doesn't have any A record configured in dns, kamailio didn't get any positive reply from it. Should't kamailio make dns query by this order? 1. NAPTR 2. SRV 3. A I noticed also that if the name configured in dispatcher table is resolved successfully with A record from dns, then kamailio tries to make a query to NAPTR and then SRV services for the exactly same name used for query previously done(type A), but only if it gets a positive answer from dns to the A type query. I'm using kamailio version 5.1.0 with the following dns parameters configured: ####### DNS Parameters ######### dns = no rev_dns = no dns_try_ipv6 = no dns_retr_time = 1 dns_retr_no = 1 dns_cache_del_nonexp = no dns_cache_flags = 1 dns_cache_gc_interval = 120 dns_cache_init = 1 dns_cache_mem = 1000 dns_cache_negative_ttl = 60 dns_try_naptr = yes use_dns_cache = on use_dns_failover = on dns_srv_lb = yes Is there something wrongly configured here that can make kamailio behaves like that? Thank you. Regards -- Cumprimentos José Seabra

4 8

Issue with ACK's
by Dan Quinney 30 Nov '18

30 Nov '18

Hi all, I’m having some issues with ACK’s. Specifically, when an ACK reaches Kamailio from either Asterisk or an endpoint, Kamailio is adding a second Via header - which isn’t valid as per RFC 3261 (17.1.1.3); “The ACK MUST contain a single Via header field, and this MUST be equal to the top Via header field of the original request." Endpoints are registered with Kamailio but INVITES are routed via Asterisk for dial plan and media reasons. I’m running fairly bog-standard Kamailio and Asterisk installs. I’ve attached a sample PCAP for if anyone has any suggestions. Thanks. Dan

2 2

Issue with ACK's
by Dan Quinney 30 Nov '18

30 Nov '18

Hi all, I’m having some issues with ACK’s. Specifically, when an ACK reaches Kamailio from either Asterisk or an endpoint, Kamailio is adding a second Via header - which isn’t valid as per RFC 3261 (17.1.1.3); “The ACK MUST contain a single Via header field, and this MUST be equal to the top Via header field of the original request." Endpoints are registered with Kamailio but INVITES are routed via Asterisk for dial plan and media reasons. I’m running fairly bog-standard Kamailio and Asterisk installs. I’ve attached a sample PCAP for if anyone has any suggestions. Thanks. Dan

1 0

Kamailio v5.2.0 Released - new major version is out
by Daniel-Constantin Mierla 30 Nov '18

30 Nov '18

Kamailio v5.2.0 is out – it comes with 6 new modules and a consistent group of improvements touching more than 100 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-2-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.2.0 brings more flexibility and optimizations for KEMI interpreters (including two new interpreters for Python3 and Ruby), major enhancements to load balancer and tls implementations, new variables and lots of other new features. Enjoy Kamailio v5.2.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference 2019 - http://www.kamailioworld.com

2 2

Response VIA Header
by Soltanici Ilie 29 Nov '18

29 Nov '18

Hi, We have a Kamailio Instance running on Public IP Address, one of our ISP cannot send ACK back to us because we are sending 100 Trying - without "received" parameter. Is there any way in Kamailio to force a "received" parameter in the via header for 100 Trying Message? SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP X.X.X.X:5060;branch=z9hG4bK8tgchsfjaKJdf.1;rport=5060 Thank you.

2 1

Forward() not handles Route headers
by Yuriy Gorlichenko 29 Nov '18

29 Nov '18

We are building some stateless solution and found that in case of using forward() kamailio sends traffic only via URI or $du variable. It never removes itself from route headers. Is this is the truth? Or I need to add some other module to handle it? (rr already added)

1 1

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