sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

topoh problem with bye from trunk
by mohsen khashei 04 Aug '20

04 Aug '20

Hi all. I use topoh module for topology hiding and this is my config for topoh: modparam("topoh", "mask_key", "my key") modparam("topoh", "mask_callid", 1) modparam("topoh", "callid_prefix", "!!:") modparam("topoh", "sanity_checks", 1) modparam("topoh", "mask_ip", "x.x.x.x") modparam("topoh", "uri_prefix_checks", 1) modparam("topoh", "uparam_name", "line") modparam("topoh", "uparam_prefix", "sr-") modparam("topoh", "vparam_name", "branch") modparam("topoh", "vparam_prefix", "z9hG4bKsr-") and also i use: modparam("dialog", "lreq_callee_headers", "TH: dlh\r\n") for dialog module. my calls come from asterisk and routed to the carrier(sip trunk) and vice versa, when i make a call from asterisk every thing works fine until the call hanged up from the carrier. at that modemt the kamailio send an 481 call/leg transaction does not exist. if call dropped bye the asterisk user everything works fine. how can i solve this?

3 3

Kamailio-IMS - Public Network Issue
by Pavithra Mohanraja 04 Aug '20

04 Aug '20

Hi, I have deployed kamailio-ims-5.3.5 as docker containers. I had private IP for containers. So when i try to establish a call from the public network , The via header is taken as container Private IP even if i use advertise address as public IP. So ACK is not reaching the pcscf from ue. Any idea can be provided for this issue. Kindly help. Thanks, Pavithra

2 1

Setting up MSFT Teams SBC <> SIP trunk but forwarding ACK and CANCEL messages
by Daniel van der Tang 02 Aug '20

02 Aug '20

Hello, I'm setting up a Kamailio MSFT Teams SBC that is connected to our SIP trunk provider. This server is directly connected to the Internet and not behind a NAT routing. It is successfully processing invites from both sides (MSFT Teams and SIP trunk). Unfortunately the ACKs and CANCEL messages are not relaying to Teams. In the sipdump i can't find these messages. Does anyone see what I am doing wrong? Below you can find my config #!KAMAILIO ####### Defined Values ######### #!define MULTIDOMAIN 0 # - flags # FLT_ - per transaction (message) flags # FLB_ - per branch flags #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_NATS 5 #!define FLB_NATB 6 #!define FLB_NATSIPPING 7 #!define FROM_TEAMS 11 #!define FROM_PBX 12 ######## Define Modules ########### #!define WITH_RTPENGINE #!define WITH_TLS #!define WITH_SIPDUMP #!define WITH_DISPATCH ####### Global Parameters ######### ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR debug=2 log_stderror=no memdbg=5 memlog=5 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " /* number of SIP routing processes */ children=2 /* uncomment the next line to disable TCP (default on) */ # disable_tcp=yes alias=SBC_FQDN /* listen addresses */ listen=udp:PUBLIC_IP:5060 advertise SBC_FQDN:5060 #!ifdef WITH_TLS listen=tls:PUBLIC_IP:5061 advertise SBC_FQDN:5061 #!endif server_header= "Server: ABC SBC" user_agent_header= "User-Agent: ABC SBC" ###### TLS Enable ###### #!ifdef WITH_TLS enable_tls=yes #tcp_connect_timeout=1000 tcp_accept_no_cl=yes tcp_async = yes tcp_connection_lifetime=600 /* upper limit for TLS connections */ tls_max_connections=2048 #!endif ####### Custom Parameters ######### /* These parameters can be modified runtime via RPC interface * - see the documentation of 'cfg_rpc' module. * * Format: group.id = value 'desc' description * Access: $sel(cfg_get.group.id) or @cfg_get.group.id */ ####### Modules Section ######## /* set paths to location of modules */ 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 "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "counters.so" #!ifdef WITH_RTPENGINE loadmodule "rtpengine.so" #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_SIPDUMP loadmodule "sipdump.so" #!endif #!ifdef WITH_DISPATCH loadmodule "dispatcher.so" #!endif # ----------------- setting module-specific parameters --------------- #!ifdef WITH_RTPENGINE # ----- rtpengine params -----+ modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:12222") #!endif #!ifdef WITH_TLS # ----- tls params -----+ modparam("tls", "xavp_cfg", "tls") modparam("tls", "config", "/etc/kamailio/tls.cfg") modparam("tls", "connection_timeout", 10) modparam("tls", "ssl_release_buffers", 1) modparam("tls", "send_close_notify", 1) modparam("tls", "session_cache", 0) #!endif #!ifdef WITH_SIPDUMP modparam("sipdump", "enable", 1) #!endif #!ifdef WITH_DISPATCH #---------- dispatch modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_ping_interval", 300) #!endif # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ # modparam("jsonrpcs", "fifo_name", "/run/kamailio/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ # modparam("jsonrpcs", "dgram_socket", "/run/kamailio/kamailio_rpc.sock") # ----- ctl params ----- /* set the path to RPC unix socket control file */ # modparam("ctl", "binrpc", "unix:/run/kamailio/kamailio_ctl") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) /* by default ww do not adjust the direct of the sequential requests. * if you enable this parameter, be sure the enable "append_fromtag" * in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) ####### Routing Logic ######## /* Main SIP request routing logic * - processing of any incoming SIP request starts with this route * - note: this is the same as route { ... } */ request_route { # per request initial checks route(REQINIT); #check who is the sender route(INITCHECK); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle retransmissions if (!is_method("ACK")) { if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); } # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # 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(); } # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # update $du to set the destination address for proxying #$du = "sip:" + $rd + ":9"; route(RELAY); exit; } route[INITCHECK] { if(from_uri =~ ".*microsoft.com") { setflag(FROM_TEAMS); $du = "sip:" + "PBX_IP"; route(HANDLE_RTP_FROM_TEAMS); } else if(from_uri =~ ".*" + "PBX_IP") { setflag(FROM_PBX); $du="sip:sip.pstnhub.microsoft.com;transport=tls"; route(HANDLE_RTP_FROM_PBX); } else { exit; } } #Manage RTP & transcoding comming from Teams to PBX route[HANDLE_RTP_FROM_TEAMS] { if (has_body("application/sdp")) { t_on_reply("PBX_REPLY_TO_TEAMS"); rtpengine_manage("RTP codec-mask=all codec-transcode=PCMA replace-origin replace-session-connection ICE=remove"); record_route(); t_relay_to_udp("PBX_IP","5060"); } } #Manage RTP & transcoding comming from PBX to Teams route[HANDLE_RTP_FROM_PBX] { if (has_body("application/sdp")) { t_on_reply("TEAMS_REPLY_TO_PBX"); rtpengine_manage("SRTP codec-mask=all ICE=force codec-transcode=PCMA replace-origin replace-session-connection"); record_route_preset("SBC_FQDN:5061;transport=tls"); add_rr_param(";r2=on"); $rd = "sip.pstnhub.microsoft.com"; $td = "SBC_FQDN"; $fd = "SBC_FQDN"; #Set TLS SNI (server name & server id) $xavp(tls=>server_name) = "SBC_FQDN"; $xavp(tls=>server_id) = "SBC_FQDN"; t_relay(); } } # Wrapper for relaying requests route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { # silent drop for scanners - uncomment next line if want to reply # sl_send_reply("200", "OK"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS")) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) return; #Teams reINVITEs if(isflagset(FROM_TEAMS)) { t_relay_to_udp("PBX_IP","5060"); exit; } # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails #set coresponding cert on transactions if($fd == "SBC_FQDN") { $xavp(tls=>server_name) = "SBC_FQDN"; $xavp(tls=>server_id) = "SBC_FQDN"; } } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not here"); exit; } # Manage outgoing branches branch_route[MANAGE_BRANCH] { xdbg("new branch [$T_branch_idx] to $ru\n"); } # Manage incoming replies onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); } #PBX On Reply onreply_route[PBX_REPLY_TO_TEAMS] { if (has_body("application/sdp")) { rtpengine_manage("SRTP codec-mask=all codec-transcode=PCMA replace-origin replace-session-connection media-address=PUBLIC_IP"); } } #From Teams On Reply onreply_route[TEAMS_REPLY_TO_PBX] { if (has_body("application/sdp")) { rtpengine_manage("RTP codec-mask=all codec-transcode=PCMA replace-origin replace-session-connection media-address=PUBLIC_IP"); } } # Manage failure routing cases failure_route[MANAGE_FAILURE] { if (t_is_canceled()) exit; } event_route[tm:local-request] { if(is_method("OPTIONS") && $ru =~ "pstnhub.microsoft.com") { append_hf("Contact: <sip:SBC_FQDN:5061;transport=tls>\r\n"); } xlog("L_INFO", "Sent out tm request: $mb\n"); }

6 5

Manipulating SDP IP for Inbound Calls
by Edward Romanenco 02 Aug '20

02 Aug '20

Hey guys, I am working on a project involving Kamailio dockerezation, which is meant to run alongside Freeswitch and RTPEngine containers, on the basis of a Docker-Compose file which is launched on top of a CentOS 7.7 host system. Anyway, I would love to know if there is any way to manipulate / mask the IP addresses that are being appended to a status 183 response for an incoming invite. For some reason which I am trying to figure out in parallel, Freeswitch uses the local network bridge subnet instead of the defined external RTP IPs, and I was wondering - Can I manipulate them using Kamailio? I know that Mangler module can do it for outbound calls, but can I do the same for inbound? v=0. o=FreeSWITCH 1595974788 1595974789 IN IP4 172.18.0.40. s=FreeSWITCH. c=IN IP4 172.18.0.40. t=0 0. m=audio 45878 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16 Edward

2 1

lua_dostring sr vs KSR
by Julien Chavanton 31 Jul '20

31 Jul '20

lua_dostring("sr.pv.seti(\"$$var(var1)\", $avp(var1) < $avp(var3) and 1 or 0)"); results in error : kamailio app lual_dostring(): error from Lua: attempt to index global 'sr' (a nil value) replacing sr with KSR is working : lua_dostring("KSR.pv.seti(\"$$var(var1)\", $avp(var1) < $avp(var3) and 1 or 0)"); Shall we update the docs for https://kamailio.org/docs/modules/devel/modules/app_lua.html#app_lua.f.lua_… ?

2 4

Issue with kamctl after upgrading to 5.3.4
by Igor Potjevlesh 31 Jul '20

31 Jul '20

Hello there! I'm having trouble with kamctl since I upgraded to 5.3.4. The command is working fine with root user but not with another user. The problem seems to be that the command try to access to /var/run/kamailio/kamailio_rpc.fifo even if the file exists. I guess it's a permission problem. But I was thinking that FIFO is no more used. Only jsonrpcs. How can I fix that? Regards, Igor. -- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

3 11

publishing hash values for download files of releases
by Daniel-Constantin Mierla 30 Jul '20

30 Jul '20

Hello, being discussed during the last devel meetings, I published the md5, sha1 and sha256 hash values for the tarballs with sources and i386 binaries we make available for download on kamailio.org on each release -- e.g., for 5.4.0: * https://www.kamailio.org/pub/kamailio/5.4.0/src/ * https://www.kamailio.org/pub/kamailio/5.4.0/bin/ Before making a more official announcement about it and adding to the download/install docs, I want to discuss a little bit here and get to the right solution to publish these hash values. For the moment I put them in a single file, adding -checksums.txt to the tarball name, listing inside all 3 hashes as computed by md5sum, sha1sum and sha256sum. That because I couldn't decide alone if there is sort of a standard on how to do it. Couple of projects I checked they just list the hash values on the html page with the link to download file. Others have dedicated files per hashing type, named like MD5SUMS, SHA1SUMS and SHA256SUMS, containing hash values for all downloadable files in the folder. Then, asterisk projects publishes 3 files, asterisk-VERSION.{md5,sha1,sha256}, corresponding to the tar.gz file they made available. Freeswitch publishes more than one archive file type, so it makes available files like freeswitch-VERSION.EXT.{md5,sha1,sha256}, where EXT can be tar.gz, tar.xz, zip ... My questions now. What kind of files with hash values people here are used with? Any variants that tends to be (or become the standard)? Any tools you are aware of for automatically checking the integrity with one of these specific hash files (like, if I have the tarball and the hashes file in the same folder and run it, it gives the ok/not-ok, without me having to do md5/sha1/sha256 manually and check "by eye" the values)? Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

2 2

Kamailio v5.4.0 Released - new major version is out
by Daniel-Constantin Mierla 29 Jul '20

29 Jul '20

Kamailio v5.4.0 is out – it comes with 5 new modules and a considerable set of improvements touching again more than 100 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-4-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.4.0 brings more flexibility and optimizations across many components, enhancements to load balancer, stateless active calls tracking, STIR/SHAKEN support, Kafka connector, plenty of new variables and transformations, ability do print JSON-structured log messages ... just to list only a few here. Enjoy Kamailio v5.4.0! Thank you for flying Kamailio! Stay safe and healthy! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

The plan for releasing Kamailio v5.4.0
by Daniel-Constantin Mierla 29 Jul '20

29 Jul '20

Hello, we are considering to release the next major stable release, respectively 5.4.0, on Wednesday, July 29, 2020. The branch 5.4 was already created, several doc resources were already added (wiki pages with what is new, core/variables/transformations/rpcs/stats cookbooks, alphabetic indexes, ...), at least debian/ubuntu packages should be built nightly, ... If anyone is testing an upgrade from branch 5.3 to 5.4 and encounters changes that should be done in Kamailio config, add notes about at: * https://www.kamailio.org/wiki/install/upgrade/5.3.x-to-5.4.0 Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

1 2

PHONENUM Module on Centos7
by Duarte Rocha 28 Jul '20

28 Jul '20

Greetings, I've trying to use the module PHONENUM on my Kamailio on CentOS 7. However, getting the required libphonenumber library hasn't been possible. Is there any CentOs7 repository for this ? What's the best way to work with this module on CentOS ? Best Regards,

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users