- sr-users - kamailio.org

kamailio 5.2.5 wrong send socket on a mhomed proxy.
by Vitalii Aleksandrov 19 Dec '19

19 Dec '19

Hi, kamailio 5.2 branch has a commit 09ac3e47ef79dbd599b7dec5b84ae3b792f025ed cherry picked from master branch. It makes sense for master because get_send_socket2() behavior has changed and function became started and also there were some patches to propagate connection it to uac structure. 5.2 kamailio takes the first interface for TCP/TLS/WS connections and then finds existing tcp connection matched by ip:port, but when the patch is applied connection lookup fails and kamailio can't forward in-dialog messages.

2 1

How to reduce re-INVITE time in Kamailio
by Anuran Barman 18 Dec '19

18 Dec '19

Hi, I am using Kamailio for my SIP Phone app. My main SIP client is the iOS app. Till now everything is working fine regarding the calling. But the problem is when the app is killed I am not able to pick up incoming call. The thing is, when app is killed I am sending PushKit VOIP message to my ios app to wake it up. App is waking up. But by the time app is waking up, the original INVITE message got missed up. So according to SIP protocol it will re-INVITE after some time. Currently if I keep my app open for 10-15 secs after it wakes up, I am able to get the re-INVITE and everything works fine just as it was supposed to. But waiting 10-15 sec on the app is not practical in any sense. So my question is there any way I can reduce the re-INVITE time to like 5/6 seconds so that as soon as the app open it will wait for 5/6 seconds (practical upto some extent) and it will get the call ? Or what kamailio is using as the interval time is a SIP standard and can not be changed? If possible to do so, how can I do that? Please help.

6 11

kamcmd stuck
by Andrew Chen 17 Dec '19

17 Dec '19

Hi everyone, Have anyone experienced kamcmd getting stuck and the only way to fix it was to restart the process? Running 5.2.5 Thanks -- Andy Chen Sr. Telephony Lead Engineer 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

OPTION pings with dispatcher to asterisk box
by Karsten Horsmann 16 Dec '19

16 Dec '19

Hello all! i am using kamailio 5.3.1-4 on CentOS and i am using dispatcher to ping his targets. Now i have someone with asterisk that answers with 401 or 404 (depends on asterisk version). So i tried code=401;code=404 as aditional attrs. Seems not to work. Also i tired to change the modparam from class=2 to this: modparam("dispatcher", "ds_ping_reply_codes", "class=2,code=401,code=404") Is that a "bug" or a hidden feature, or i missed something? Btw - Have a nice weekend! SELECT * FROM dispatcher WHERE id=1 \G *************************** 1. row *************************** id: 1 setid: 1100 destination: sip:SOMEWHERE;transport=tls flags: 0 priority: 0 attrs: socket=tls:MY.IP.AD.RR:5061;ping_from=sip:MY.SIP.DOMAIN;code=401;code=404 description: UNTRUSTED "SET": { "ID": 1100, "TARGETS": [{ "DEST": { "URI": "sip:SOMEWHERE;transport=tls", "FLAGS": "IP", "PRIORITY": 0, "ATTRS": { "BODY": "socket=tls:MY.IP.AD.RR:5061;ping_from=sip:MY.SIP.DOMAIN;code=401;code=404", "DUID": "", "MAXLOAD": 0, "WEIGHT": 0, "RWEIGHT": 0, "SOCKET": "tls:MY.SIP.DOMAIN:5061" }, "LATENCY": { "AVG": 48768.816406, "STD": 139490.953125, "EST": 43359.566406, "MAX": 568876, "TIMEOUT": 8 } } }] } }] #!ifdef WITH_MYSQL modparam("dispatcher", "db_url", "DBURL") modparam("dispatcher", "table_name", "dispatcher") #!endif #!ifndef WITH_MYSQL modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") #!endif modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_from", "<sip:ping@FANCY-COMPANY-WEBNAME>") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 2) modparam("dispatcher", "setid_pvname", "$var(setid)") modparam("dispatcher", "attrs_pvname", "$var(attrs)") modparam("dispatcher", "ds_ping_reply_codes", "class=2,code=401,code=404") modparam("dispatcher", "ds_ping_latency_stats", 1) https://community.asterisk.org/t/asterisk-responds-with-404-to-options-even… Dec 13 17:25:46 siptrunk3 /usr/sbin/kamailio[25115]: INFO: <script>: Sending message 'OPTIONS sip:SOMEWHERE;transport=tls SIP/2.0 Via: SIP/2.0/TLS MY.IP.AD.RR:5061;branch=z9hG4bK2527.825671c0000000000000000000000000.0 To: <sip:SOMEWHERE;transport=tls> From: <sip:MY.SIP.DOMAIN>;tag=f9bf2579cb456ea8d260d4aabc8248ef-9ca844ad CSeq: 10 OPTIONS Call-ID: 01cb6e272da7b0dd-25115(a)MY.IP.AD.RR Max-Forwards: 70 Content-Length: 0 User-Agent: SBC-OS ' Dec 13 17:25:46 siptrunk3 /usr/sbin/kamailio[25127]: INFO: <script>: Received message 'SIP/2.0 404 Not Found Via: SIP/2.0/TLS MY.IP.AD.RR:5061;branch=z9hG4bK2527.825671c0000000000000000000000000.0;received=MY.IP.AD.RR From: <sip:MY.SIP.DOMAIN>;tag=f9bf2579cb456ea8d260d4aabc8248ef-9ca844ad To: <sip:SOMEWHERE;transport=tls>;tag=as54adca41 Call-ID: 01cb6e272da7b0dd-25115(a)MY.IP.AD.RR CSeq: 10 OPTIONS Server: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Accept: application/sdp Content-Length: 0 ' -- Cheers *Karsten Horsmann*

3 6

Reject tls invites without a=crypto sdp
by Karsten Horsmann 16 Dec '19

16 Dec '19

Hi, I use Kamailio 5.3.1 with rtpengine to offer an siptrunk endpoint for my customers. I observe that someone of them use tls to encrypt signaling but forgotten to encrypt rtp. I want to reject this invites. Are there any hints how to do this? Thought about reading the sdp and search for a=crypto line and if not send reply with (what code ever will be good for that). Cheers Karsten

2 4

Removing extra Connection information in SDP
by Kjeld Flarup 16 Dec '19

16 Dec '19

Hello I have a problem with some phone numbers at Telenor. Our door telephone does not reply with an ACK on the 200 OK. All I found was a weird SDP response with two "connection information" lines Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): BroadWorks 307119541 1 IN IP4 194.247.61.31 Session Name (s): - Connection Information (c): IN IP4 194.247.61.31 Time Description, active time (t): 0 0 Session Attribute (a): sendrecv Media Description, name and address (m): audio 23116 RTP/AVP 8 101 Connection Information (c): IN IP4 194.247.61.31 Media Attribute (a): rtpmap:8 PCMA/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-15 Media Attribute (a): maxptime:40 Media Attribute (a): bsoft:1 image udptl t38 Media Attribute (a): sendrecv Media Attribute (a): silenceSupp:off - - - - Media Attribute (a): setup:actpass To debug, I would like to remove one of the "Connection Information (c): IN IP4 194.247.61.31", to see if this is what confuses the door telephone. But how do I do that? I tried with this but nothing happeded onreply_route[DOOR_MANAGE_REPLY] { if (is_method("INVITE|SUBSCRIBE")) { sdp_remove_line_by_prefix("c=IN IP4 194"); } return 1; } -- --------------------- 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 <http://www.liberalismen.dk>

2 1

using tls targets in dispatcher
by Narasimhaiah, Vinod Maralenahalli 15 Dec '19

15 Dec '19

Hi I am using kamailio server to forward the request to a new kamailio-server which listens only on TLS. *problem: Not able to specify the dispatcher with tls protocol* I am using the below configuration in dispatcher.list kamailio version:4.4.2 *# setid(integer) destination(sip uri) flags (integer, optional), priority(int,opt), attrs (str,optional)1 sip:mynetwork.com <http://mynetwork.com>;transport=tls 8 1 socket=tls:mynetwork.com:5328 <http://mynetwork.com:5328>* and if I specify the destination as just sip:mynetwork.com:5328 with out attrs and transport=tls if is falling back to UDP. Thank you vinod.M.N

2 1

Kamailio dispatcher to use tls targets.
by vinod mn 15 Dec '19

15 Dec '19

Hi I am using kamailio server to forward the request to a new kamailio-server which listens only on TLS. *problem: Not able to specify the dispatcher with tls protocol* I am using the below configuration in dispatcher.list kamailio version:4.4.2 *# setid(integer) destination(sip uri) flags (integer, optional), priority(int,opt), attrs (str,optional)1 sip:mynetwork.com <http://mynetwork.com/>;transport=tls 8 1 socket=tls:mynetwork.com:5328 <http://mynetwork.com:5328/>* and if I specify the destination as just sip:mynetwork.com:5328 with out attrs and transport=tls if is falling back to UDP. Thank you vinod.M.N

1 0

using a pseudo-variable as a parameter to a module function
by Michael Iedema 14 Dec '19

14 Dec '19

Hi all, I’m trying to write a basic Kamailio module from scratch and have run into an area where I’m in need of a couple pointers (pun not intended). :-) I have the module loading correctly and can call a function in my routing script like this: mymod_getinfo(“5551234”); This, for now, just triggers a print of the submitted parameter. What I’d like to do next is have it accept and print the From URI in configuration script like so: mymod_getinfo(“$fU”); For now, this prints the string literal of “$fU” and I’m trying to extract the value of the referenced variable and print that. The example module “print” does not involve this concept of pseudo-variables. The skeleton module example in the wiki also does not mention variables. I’ve looked into other modules to see how it works but they all seem to have a slightly different handling of this task. Can someone point me to an example in the modules which accomplishes this? What I’ve been searching for is a replace_all function which accepts a string containing pseudo-variables and returns a new string with them all replaced with their corresponding values. Thanks in advance and apologies if I’ve overlooked a relevant piece of developer documentation or if I’m looking at this incorrectly. Regards, -Michael

3 3

lookup(aliases) issues with 5.2
by igor.potjevlesch＠gmail.com 13 Dec '19

13 Dec '19

Hello! I have notice some issues with lookup(aliases) since I upgraded to 5.2 from 5.1: First with kamctl: If this default command is executed: ctl_cmd_run ul.add "$USRLOC_TABLE" "$OSERUSER@$OSERDOMAIN" "$2" \ "$UL_EXPIRES" "$DEFAULT_Q" "$UL_PATH" "$UL_FLAGS" "$BR_FLAGS" "$ALL_METHODS" as $ALL_METHODS is not defined, there is a huge value in methods and then lookup(aliases) fails with -2. I have to update kamctl script and put -1 ("-1") instead of the variable. So, now, methods is a NULL value in DB and my alias is not ignored. But I use to make my alias like this: sip:number@blabla_1.local Which is no longer works: ERROR: registrar [common.c:62]: extract_aor(): failed to parse AoR [sip:number@blabla_1.local] Any idea of the difference since 5.2 with this behaviour? Without the underscore, the AoR seems to be valid but I need to support underscore as before. Regards, Igor.

4 16

t_newtrans() README issue
by Juha Heinanen 12 Dec '19

12 Dec '19

I noticed this in t_newtrans() README: Note that any flag operations (e.g. for accounting) after this function has been called will be ignored. You can use the the tmx module function t_flush_flags() to flush the altered flags to the already created transaction. The text is wrong. I have for ages set bflags after calliing t_newtrans() and the sets are NOT ignored. Here is an example: In route blocks: Dec 12 08:41:53 /usr/bin/sip-proxy[231131]: INFO: ********* called t_newtrans() Dec 12 08:41:53 /usr/bin/sip-proxy[231131]: INFO: ************ set bflag 9 In failure route block: Dec 12 08:41:58 /usr/bin/sip-proxy[231195]: INFO: ************ bflag 9 is set -- Juha

3 2

S-CSCF tear down call while deleting contact
by Liu, Charles 12 Dec '19

12 Dec '19

Hi All, I need some expert help to trouble shoot a problem I have seen, S-CSCF send BYE to tear down a call. I have make some progress to trace the problem to impurecord.c in ims_usrloc_scscf module, _c->first_dialog_data !=0 while try to delete an expired contact. I need some help to find out why _c->first_dialog_data is not 0 for an expired contact. To reproduce the problem, I began with the following for user1. Contact id 4098, 4114, and 4115 would expire and a call was using id 4116. When the time to delete contact, somehow scscf mistakenly think id 4098 still has a dialog, but the dialog was with id 4116 which was NOT expired. Therefore, S-CSCF send BYE to tear down the call, so end user see call drop. Please note, if id 4098 never make calls before, first call was working fine. But once a call was make, you will see this problem for next call. it seem S-CSCF did not clean up the dialog_data from last call properly and some data still hanging with the contact caused this problem. any insight how to fix or avoid this would be appreciated. id contact params path received user_agent expires callid 2192 sip:user2@192.168.164.136:62837;rinstance=bca96a7c77f53916;transport=UDP NULL <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-12 15:50:10 UPIM_gl22a13wlo47aeHRQ.. 4098 sip:user1@192.168.164.9:61946;rinstance=7ab86c5e85643767;transport=UDP NULL <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-12 15:49:21 ocl7UYxJLo8TnMw2p2-6NQ.. 4114 sip:user1@192.168.164.9:61946;rinstance=65afabdb886de0a7;transport=UDP NULL <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-12 15:50:11 GZrZHDyL3ojhDlLDPpJnvQ.. 4115 sip:user1@192.168.164.9:61946;rinstance=074e2e926212237b;transport=UDP NULL <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-12 15:50:13 DCKsqvUjZ1dAfJLfJ3nOhA.. 4116 sip:user1@192.168.164.9:61946;rinstance=38cc0c6188509aea;transport=UDP NULL <sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-12 15:50:15 gF3fphqyrSbQwaN0eW4JLw.. 13(18) DEBUG: ims_usrloc_scscf [udomain.c:384]: mem_timer_udomain(): *** mem_timer_udomain - checking IMPUs - FINISHED *** 13(18) DEBUG: ims_usrloc_scscf [udomain.c:406]: mem_timer_udomain(): deleting contact [sip:user1@ims.mnc001.mcc001.3gppnetwork.org] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:598]: delete_scontact(): Deleting contact: [sip:user1@192.168.164.9:61946;rinstance=074e2e926212237b;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [usrloc_db.c:370]: db_delete_ucontact(): Deleting ucontact [sip:user1@192.168.164.9:61946;rinstance=074e2e926212237b;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:310]: mem_delete_ucontact(): Checking if dialog_data is there and needs to be torn down 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:312]: mem_delete_ucontact(): first dialog is 0! 13(18) DEBUG: ims_usrloc_scscf [udomain.c:406]: mem_timer_udomain(): deleting contact [sip:user1@ims.mnc001.mcc001.3gppnetwork.org] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:598]: delete_scontact(): Deleting contact: [sip:user1@192.168.164.9:61946;rinstance=7ab86c5e85643767;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [usrloc_db.c:370]: db_delete_ucontact(): Deleting ucontact [sip:user1@192.168.164.9:61946;rinstance=7ab86c5e85643767;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:310]: mem_delete_ucontact(): Checking if dialog_data is there and needs to be torn down 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:314]: mem_delete_ucontact(): first dialog is not 0 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:317]: mem_delete_ucontact(): Going to tear down dialog with info h_entry [1081] h_id [2579] 13(18) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f803f803108 with 1 -> 3 13(18) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=2579 found on entry 1081 13(18) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f803f803108 with 1 -> 2 13(18) DEBUG: ims_dialog [dlg_req_within.c:379]: dlg_terminate(): terminating confirmed dialog Thanks, --Charles CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

1 0

Kamailio delayed reponse in case of database load
by Ali Taher 12 Dec '19

12 Dec '19

Hello, I have Kamailio installed as SIP redirect for an SBC to make routing decisions. I'm using SQLOps module with postgresql 11.5 where I have multiple tables containing each around 6M record of routing codes: Code options 392342 sup1|sup2|sup3 Where code field is of prefix_range data type and has a gist index. I'm sending traffic of 300 CPS to SBC which is forwarding it to Kamailio, and Kamailio respond with 300 multiple choice with the routing decision. In normal cases, everything is going smoothly where Kamailio repsonds up to 50 ms. But during the process of loading data to the routing tables, Kamailio response to SBC is dramatically delayed , where for some calls it takes up to 7 seconds to respond. Noting that during this process the data are loaded to staging tables and not to live tables used by Kamailio. Kamailio is installed on a VM with 32GB RAM and 16 vcores. Following configuration is used in Kamailio: fork=yes children=10 following are the customized parameters in postgresql.conf max_connections = 100 shared_buffers = 8GB effective_cache_size = 24GB maintenance_work_mem = 2GB checkpoint_completion_target = 0.7 wal_buffers = 16MB default_statistics_target = 100 random_page_cost = 1.1 effective_io_concurrency = 200 work_mem = 5242kB min_wal_size = 1GB max_wal_size = 2GB max_worker_processes = 16 max_parallel_workers_per_gather = 8 max_parallel_workers = 16 Following is the routing logic I'm using: route{ if (is_method("INVITE")) { $var(inc) = $(ct{param.value,tgrp}); xlog("L_INFO","CONTACT : $var(inc)" ); xlog("L_INFO","from number : $rU" ); if($var(inc)!=0) route(customer); route(block); } } route[customer] { sql_query("cb", "select caid from customeridentification where trunk='$var(inc)'", "ra"); $var(cid)=$dbr(ra=>[0,0]); sql_result_free("ra"); xlog("L_INFO","cid: $var(cid) \n"); sql_query("cb", "select routetablename from carrieraccount where caid=$var(cid)", "ra"); $var(tid)=$dbr(ra=>[0,0]); sql_result_free("ra"); if($var(cid)!=0) route(query); else route(block); } route[query] { #sql_query("cb", "select supplierid from route_$var(cid) where prefix @>'$rU' order by prefix limit 1", "ra"); sql_query("cb", "select get_routing('$var(tid)','$rU')", "ra"); $var(sup)=$dbr(ra=>[0,0]); sql_result_free("ra"); xlog("L_INFO","supplieris: $var(sup) \n"); #$var(x)=$(var(sup){s.replace,|,}{s.len})/4; $var(a)=$(var(sup){s.len}); $var(z)=$(var(sup){s.replace,|,}); $var(b)=$(var(z){s.len}); $var(suplen)=$var(a) - $var(b); if($var(sup)!=0) route(send); else route(block); } route[send] { xlog("L_INFO","Inside Send \n"); $var(i)=0; append_to_reply("Contact:"); while($var(i)<$var(suplen) + 1) { $var(s)=$(var(sup){s.select,$var(i),|}); $var(s)=$(var(s){s.select,0,;}); append_to_reply("<sip:$rU;tgrp=$(var(s){s.ltrim})@ xxx.xxx.xxx.xxx:5060;user=phone>"); if($var(i)<$var(suplen)) append_to_reply(","); $var(i)=$var(i)+1; } append_to_reply("\r\n"); sl_send_reply("300","Multiple Choices"); exit; } route[block] { xlog("L_INFO","INSIDE BLOCK" ); append_to_reply("Contact:<sip:$rU;tgrp=999999@xxx.xxx.xxx.xxx:5060;user=phone>\r\n"); sl_send_reply("300","Multiple Choices"); exit; } How can we enhance the Kamailio response in case of load on the postgresql server. Regards, Ali Taher

2 4

xhttp_prom Metric Naming Issue
by ENGIN ESIN 12 Dec '19

12 Dec '19

Hi everyone, I am trying to use xhttp_prom and there are some issues that i want to share with you. Metric Naming: I get warning at prometheus side like as follows, WARN[0659] append failed err="no token found" source="scrape.go:648" target="{__address__="192.168.42.1:9080", __metrics_path__="/metrics", __scheme__="http", instance="192.168.42.1:9080", job="vmm"}" With respect to prometheus documentation, metric names need to fullfill following naming requirement -> "It must match the regex [a-zA-Z_:][a-zA-Z0-9_:]*" (source: https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels) However, kamailio gives unmatch outputs as follows because they have '-' char, (related discussion: https://github.com/prometheus/prometheus/issues/3154 ) * kamailio_usrloc_location-contacts 0 1576046310669 * kamailio_usrloc_location-expires 0 1576046310669 * kamailio_usrloc_location-users 0 1576046310669 whit that naming, prometheus can not parse values of any metrics. Documentation: Example 1.1. Set xhttp_prom_buf_size parameter ... modparam("xhttp", "xhttp_prom_buf_size", 1024) ... For that example, it should be as follows, ... modparam("xhttp_prom", "xhttp_prom_buf_size", 1024) ... [http://www.turkcell.com.tr/downloads/bireysel/img/Tcelldis.gif] <http://turkcell.li/iyaani> Bu elektronik posta ve onunla iletilen butun dosyalar sadece gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir. TURKCELL bu mesajin icerdigi bilgilerin do?rulu?u veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir. ________________________________ This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted. TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL. This e-mail has been scanned for all known computer viruses.

2 1

Please Help
by Sharath 12 Dec '19

12 Dec '19

Dear Team, If we want add a free-pbx as a trunk then what are configuration we need to do in admin panel of siremis. * SHARATH. O.M.** *

2 1

Kamailio delayed reponse in case of database load
by Ali Taher 10 Dec '19

10 Dec '19

Hello, I have Kamailio installed as SIP redirect for an SBC to make routing decisions. I'm using SQLOps module with postgresql 11.5 where I have multiple tables containing each around 6M record of routing codes: Code options ----------------------- 392342 sup1|sup2|sup3 Where code field is of prefix_range data type and has a gist index. I'm sending traffic of 300 CPS to SBC which is forwarding it to Kamailio, and Kamailio respond with 300 multiple choice with the routing decision. In normal cases, everything is going smoothly where Kamailio repsonds up to 50 ms. But during the process of loading data to the routing tables, Kamailio response to SBC is dramatically delayed , where for some calls it takes up to 7 seconds to respond. Noting that during this process the data are loaded to staging tables and not to live tables used by Kamailio. Kamailio is installed on a VM with 32GB RAM and 16 vcores. Following configuration is used in Kamailio: fork=yes children=10 following are the customized parameters in postgresql.conf max_connections = 100 shared_buffers = 8GB effective_cache_size = 24GB maintenance_work_mem = 2GB checkpoint_completion_target = 0.7 wal_buffers = 16MB default_statistics_target = 100 random_page_cost = 1.1 effective_io_concurrency = 200 work_mem = 5242kB min_wal_size = 1GB max_wal_size = 2GB max_worker_processes = 16 max_parallel_workers_per_gather = 8 max_parallel_workers = 16

4 6

authcheck and fd variable
by Robert Lieback 10 Dec '19

10 Dec '19

Hello, i'm looking into kamalio (btw: thanks to asipto for the great book) and i hope someone can push me in the right direction. I have a question/problem with some lines in the default config (kamailio.cfg) around line 754: ... if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } ... auth_check() and auth_challenge doesn't work, but i've provided the correct credentials. When i replace "$fd" with domain "voip.XXXXXX.de" it works. This domain is also defined as alias in the config and all sip messages i send to the server have a correct from header with this domain. First step for me would be to look whats stored in $fd, but how can i output the content of $fd? Cause log(2, "$fd") or xlog("$fd") doesn't work and throws errors about unknown variables. Thanks, Robert Lieback

2 2

Kamailio management group updates
by Daniel-Constantin Mierla 09 Dec '19

09 Dec '19

Hello, Jesus Rodrigues and Inaki Baz Castillo changed their work roles a while ago, so they no longer deal with Kamailio and they do not expect to do it in the near future. To keep the Management group with members connected as much as possible with the project, Fred Posner and Victor Seva were proposed to replace them. For the new members in the public lists: the management group of Kamailio is not involved in the daily development or administration of the project -- all those are done on public mailing lists or kadmin group (internal infrastructure administration) -- management team is supposed to take the decisions on sensitive situations for the evolution of the project. Should anyone have opinions about these changes, let's discuss on sr-users mailing list. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

1 0

duplicated registrations
by Liu, Charles 08 Dec '19

08 Dec '19

Hi All, Does this look correct? I am using Zoiper client and did multiple registration/re-registration, but I saw duplicated contacts in the database for the same user/device(alice). I was expecting to see only one. Is this a bug? How do I prevent this happening? "select * from scscf.contact" id contact params path received user_agent expires callid 49 sip:bob@192.168.10.201:60944;rinstance=44b4024df17bd284;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-08 10:31:51 r7jCYp7JuVbA8QjocnouLw.. 64 sip:alice@192.168.10.241:60383;rinstance=e850d3ed0605bcd3;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-08 10:31:11 EHLOADkLUEe8d0CMpdLL9A.. 142 sip:alice@192.168.10.241:60383;rinstance=bc755d87cc438890;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-08 10:31:51 P1rBkHGUVdv7oqW3_UWQPg.. 143 sip:alice@192.168.10.241:60383;rinstance=146303cf7501a125;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-08 10:32:15 etUEoAGSM4q4e_39wFKa7w.. 144 sip:alice@192.168.10.241:60383;rinstance=e0a260b7b78ecf6b;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-08 10:32:17 WUtIYeGlBZmHD3TGklmKCQ.. 145 sip:alice@192.168.10.241:60383;rinstance=2681245431c4e4e4;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.3gppnetwork.org;lr> Zoiper rv2.10.3.2 2019-12-08 10:32:19 HNZPyeO173jfscKYNOT0bw.. Thanks, --Charles CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

2 2

ul.dump empty
by Liu, Charles 07 Dec '19

07 Dec '19

Hi All, I am running Kamailio v5.2.4 with P/S/I-cscf instances on 3 different machines with default IMS example configurations. Kamcmd ul.dump show empty, but I can make calls... any idea what is the problem? root@pcscf:/# kamcmd ulpcscf.status { Domain: location Size: 512 AoRs: { Stats: { Records: 7 Max-Slots: 6 } } } root@pcscf:/# kamcmd ul.dump { Domains: { } } CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

1 1

Pike module never release IP
by Andrew Chen 06 Dec '19

06 Dec '19

Hi all, Have anyone ever experienced pike module not releasing the IP after "remove_latency" period? We ran a load test and this is what happened to one of the two paired nodes and I had to restart kamailio process to release it. I'm running Kam 5.2.5 Thanks. -- Andy Chen Sr. Telephony Lead Engineer 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 6

How can I make calls between the two domains?
by Yanko 06 Dec '19

06 Dec '19

Hello: I have two virtual machines with two kamailo domains VM1: Domain: 172.16.16.1 Users:2000, 2001, 2002... VM2: Domain: 172.16.16.2 Users:3000, 3001, 3002... In each domain I can make calls. For example, user 2000 can call 2001. User 3000 can call 3001. How can I make calls between the two domains? What modules do I need to load? How to configure the kamailio.cfg file? Thanks, YANKO.

2 1

Scripts still valid?
by David Villasmil 05 Dec '19

05 Dec '19

Hello guys, Is this still valid? https://github.com/kamailio/kamailio/blob/master/misc/examples/scripts/ctd.… Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 4

call disconnected between 15 to 45 minutes
by Liu, Charles 05 Dec '19

05 Dec '19

Hi all, I am still looking for some help to debug why S-CSCF send BYE to caller and callee after a call was connected. from wireshark, I just saw S-CSCF send BYE to both caller and callee. That matched the S-CSCF debug output. But the question is why S-CSCF delete contact and send BYE to a active call? There was no timer expire or something like that in the log... Anyone can help? Thanks, --Charles 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09413e6d0 alloc'ed from cdp: diameter_msg.c: AAATranslateMessage(484) 19(24) DEBUG: tm [t_lookup.c:1618]: t_lookup_ident(): transaction found 19(24) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb093db6000, 6872) called from core: core/sip_msg_clone.c: sip_msg_shm_clone(496) 19(24) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb093db6000, 6872) returns address 0x7fb09414d450 frag. 0x7fb09414d418 (size=6872) on 1 -th hit 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=767 a=26 n=xlog 19(24) DEBUG: <script>: saa_return code is 1 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=769 a=26 n=xlog 19(24) DEBUG: <script>: saa_return code (for scscf_save on register) is 1 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=783 a=21 n=switch 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=772 a=26 n=xlog 19(24) DEBUG: <script>: SAR success - 200 response sent from module 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=773 a=2 n=exit 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09414d450), called from tm: t_reply.c: free_faked_req(948) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09414d418 alloc'ed from core: core/sip_msg_clone.c: sip_msg_shm_clone(496) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09413e978), called from ims_registrar_scscf: cxdx_sar.c: free_saved_transaction_data(94) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09413e940 alloc'ed from ims_registrar_scscf: save.c: save(1414) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09413e0b0), called from ims_registrar_scscf: reply.c: free_contact_buf(830) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09413e078 alloc'ed from ims_registrar_scscf: reply.c: build_contact(443) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb094145218), called from ims_registrar_scscf: reply.c: free_contact_buf(835) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb0941451e0 alloc'ed from ims_registrar_scscf: reply.c: build_contact(435) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb094147dc0), called from ims_registrar_scscf: cxdx_sar.c: free_saved_transaction_data(98) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb094147d88 alloc'ed from ims_registrar_scscf: save.c: save(1396) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09415b4c8), called from cdp: transaction.c: cdp_free_trans(182) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09415b490 alloc'ed from cdp: transaction.c: cdp_add_trans(110) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb0941442a0), called from cdp: transaction.c: cdp_free_trans(183) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb094144268 alloc'ed from cdp: transaction.c: cdp_add_trans(105) 13(18) DEBUG: ims_usrloc_scscf [ims_usrloc_scscf_mod.c:481]: timer(): Syncing cache 13(18) DEBUG: ims_usrloc_scscf [udomain.c:291]: mem_timer_udomain(): *** mem_timer_udomain - checking contacts - START *** 13(18) DEBUG: ims_usrloc_scscf [udomain.c:301]: mem_timer_udomain(): We have a [3gpp=0] contact in the new contact list in slot 95 = [sip:bob@ims.mnc001.mnc001.3gppnetwork.org] (sip:bob@192.168.164.248:50448;rinstance=989f943bd5098a11;transport=UDP) which expires in -60.000000 seconds and has a ref count of 0 (state: Contact with delayed delete) 13(18) DEBUG: ims_usrloc_scscf [udomain.c:309]: mem_timer_udomain(): contact in state CONTACT_DELATED_DELETE is about to be deleted13(18) DEBUG: ims_usrloc_scscf [udomain.c:301]: mem_timer_udomain(): We have a [3gpp=0] contact in the new contact list in slot 464 = [sip:alice@ims.mnc001.mnc001.3gppnetwork.org] (sip:alice@192.168.164.203:44640;rinstance=e35e9704884c3208;transport=UDP) which expires in 50.000000 seconds and has a ref count of 1 (state: Contact valid) 13(18) DEBUG: ims_usrloc_scscf [udomain.c:301]: mem_timer_udomain(): We have a [3gpp=0] contact in the new contact list in slot 478 = [sip:bob@ims.mnc001.mnc001.3gppnetwork.org] (sip:bob@192.168.164.248:50448;rinstance=9e742618a5f6bcae;transport=UDP) which expires in 56.000000 seconds and has a ref count of 1 (state: Contact valid) 13(18) DEBUG: ims_usrloc_scscf [udomain.c:353]: mem_timer_udomain(): *** mem_timer_udomain - checking contacts - FINISHED *** 13(18) DEBUG: ims_usrloc_scscf [udomain.c:359]: mem_timer_udomain(): *** mem_timer_udomain - checking IMPUs - START *** 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:372]: process_impurecord(): Checking validity of IMPU: <sip:alice@ims.mnc001.mnc001.3gppnetwork.org> registration subscriptions 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:404]: process_impurecord(): Public Identity sip:alice@ims.mnc001.mnc001.3gppnetwork.org, Barred: [0], State: [registered], contacts [1], 3gppcontacts [0] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:441]: process_impurecord(): Contact #0 - sip:alice@192.168.164.203:44640;rinstance=e35e9704884c3208;transport=UDP, Ref [1] (expires in 50 seconds) (State: 0) 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:372]: process_impurecord(): Checking validity of IMPU: <sip:bob@ims.mnc001.mnc001.3gppnetwork.org> registration subscriptions 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:404]: process_impurecord(): Public Identity sip:bob@ims.mnc001.mnc001.3gppnetwork.org, Barred: [0], State: [registered], contacts [1], 3gppcontacts [0] 3(18) DEBUG: ims_usrloc_scscf [impurecord.c:441]: process_impurecord(): Contact #0 - sip:bob@192.168.164.248:50448;rinstance=9e742618a5f6bcae;transport=UDP, Ref [1] (expires in 56 seconds) (State: 0) 3(18) DEBUG: ims_usrloc_scscf [udomain.c:384]: mem_timer_udomain(): *** mem_timer_udomain - checking IMPUs - FINISHED *** 3(18) DEBUG: ims_usrloc_scscf [udomain.c:406]: mem_timer_udomain(): deleting contact [sip:bob@ims.mnc001.mnc001.3gppnetwork.org] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:598]: delete_scontact(): Deleting contact: [sip:bob@192.168.164.248:50448;rinstance=989f943bd5098a11;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [usrloc_db.c:370]: db_delete_ucontact(): Deleting ucontact [sip:bob@192.168.164.248:50448;rinstance=989f943bd5098a11;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:310]: mem_delete_ucontact(): Checking if dialog_data is there and needs to be torn down 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:314]: mem_delete_ucontact(): first dialog is not 0 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:317]: mem_delete_ucontact(): Going to tear down dialog with info h_entry [1694] h_id [3889] 13(18) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fb09414ce40 with 1 -> 3 13(18) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=3889 found on entry 1694 13(18) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fb09414ce40 with 1 -> 2 13(18) DEBUG: ims_dialog [dlg_req_within.c:379]: dlg_terminate(): terminating confirmed dialog 13(18) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 18) called from ims_dialog: dlg_req_within.c: build_extra_hdr(229) 13(18) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 24) returns address 0x7fb09b640c30 frag. 0x7fb09b640bf8 (size=64) on 1 -th hit 13(18) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 248) called from ims_dialog: dlg_req_within.c: build_dlg_t(81) 13(18) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 248) returns address 0x7fb09b74b100 frag. 0x7fb09b74b0c8 (size=248) on 1 -th hit 13(18) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 72) called from core: core/parser/parse_rr.c: do_parse_rr_body(68) 13(18) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 72) returns address 0x7fb09b74b048 frag. 0x7fb09b74b010 (size=80) on 1 -th hit 13(18) DEBUG: ims_dialog [dlg_req_within.c:272]: send_bye(): sending BYE to caller 13(18) DEBUG: ims_dialog [dlg_hash.c:1047]: ref_dlg(): ref dlg 0x7fb09414ce40 with 1 -> 3 CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

2 2

Question regarding priority in dispatcher module
by Floimair Florian 05 Dec '19

05 Dec '19

Dear all! After reading the documentation on dispatcher module I still have a question that isn't really documented. Regarding the priority value of an entry in a dispatcher list: Is a lower numerical priority value regarded as higher priority or is it the other way around? Hopefully someone can help me to clarify this. With best regards FLORIAN FLOIMAIR Software Development Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria commend.com LG Salzburg / FN 178618z

2 2

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