sr-users December 2019

sr-users@lists.kamailio.org

63 participants
78 discussions

by Andrew Chen

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.*

4 years, 11 months

OPTION pings with dispatcher to asterisk box

by Karsten Horsmann

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*

4 years, 11 months

Reject tls invites without a=crypto sdp

by Karsten Horsmann

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

4 years, 11 months

Removing extra Connection information in SDP

by Kjeld Flarup

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>

4 years, 11 months

using tls targets in dispatcher

by Narasimhaiah, Vinod Maralenahalli

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

4 years, 11 months

Kamailio dispatcher to use tls targets.

by vinod mn

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

4 years, 11 months

using a pseudo-variable as a parameter to a module function

by Michael Iedema

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

4 years, 11 months

lookup(aliases) issues with 5.2

by igor.potjevlesch＠gmail.com

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 years, 11 months

t_newtrans() README issue

by Juha Heinanen

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

4 years, 11 months

S-CSCF tear down call while deleting contact

by Liu, Charles

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.

4 years, 11 months

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 December 2019