sr-users

sr-users@lists.kamailio.org

8 participants
37391 discussions

Kamailio as MS-Teams SBC
by Davide Zanichelli 09 Feb '21

09 Feb '21

Hello everybody! i am trying a setup of kamailio like sbc for ms teams, I currently have the following scenario: TLS Connection OK Out Call ok (except BYE 481 on reply) my problem is in incoming calls microsoft only supports srtp and my pbx (freeswitch based) only works with rtp, now i was reading that you need to use rtpengine to manage srtp to rtp, unfortunately it seems that rtpengine has become very difficult to build especially with recent os, I was wondering if it is possible to have an alternative to rtpengine for managing the srtp (rtpproxy does not seem to work) has anyone managed to get a working setup? in case it is possible to send a configuration template? Thanks You !!! Davide

8 26

run_trans_callbacks_internal crash
by Juha Heinanen 09 Feb '21

09 Feb '21

We got the crash below with 5.4.2. Before the crash there was db_mysql_async_exec_task(): failed to execute query related error messages in syslog. -- Juha Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f601d4b2f32 in run_trans_callbacks_internal (cb_lst=0x7f5ffb53e318, type=512, trans=0x7f5ffb53e2a0, params=0x7ffd1c349720) at t_hooks.c:254 254 t_hooks.c: No such file or directory. (gdb) bt full #0 0x00007f601d4b2f32 in run_trans_callbacks_internal (cb_lst=0x7f5ffb53e318, type=512, trans=0x7f5ffb53e2a0, params=0x7ffd1c349720) at t_hooks.c:254 cbp = 0x72743b6d6f632e61 backup_from = 0x560e8abbe2f0 <def_list+16> backup_to = 0x560e8abbe2f8 <def_list+24> backup_dom_from = 0x560e8abbe300 <def_list+32> backup_dom_to = 0x560e8abbe308 <def_list+40> backup_uri_from = 0x560e8abbe2e0 <def_list> backup_uri_to = 0x560e8abbe2e8 <def_list+8> backup_xavps = 0x560e8abbeae0 <_xavp_list_head> backup_xavus = 0x560e8abbeae8 <_xavu_list_head> backup_xavis = 0x560e8abbeaf0 <_xavi_list_head> __func__ = "run_trans_callbacks_internal" #1 0x00007f601d4b35bb in run_trans_callbacks_with_buf (type=512, rbuf=0x7f5ffb53e370, req=0x7f5ffafe3b70, repl=0xffffffffffffffff, flags=0) at t_hooks.c:303 params = {req = 0x7f5ffafe3b70, rpl = 0xffffffffffffffff, param = 0x7f5ffa61e640, code = 487, flags = 0, branch = 0, t_rbuf = 0x7f5ffb53e370, dst = 0x7f5ffb53e3c0, send_buf = {s = 0x7f5ffa6d4d40 "F", len = 621}} trans = 0x7f5ffb53e2a0 #2 0x00007f601d458025 in relay_reply (t=0x7f5ffb53e2a0, p_msg=0xffffffffffffffff, branch=0, msg_status=408, cancel_data=0x7ffd1c349910, do_put_on_wait=0) at t_reply.c:2124 relay = 0 save_clone = 0 buf = 0x7f601e46a4e0 "SIP/2.0 487 Request Terminated\r\nVia: SIP/2.0/TCP 46.182.160.40;branch=z9hG4bK9ef2.1bbf20df35272cd85c43814302770601.2\r\nVia: SIP/2.0/UDP 95.216.75.211;rport=5060;branch=z9hG4bK9ef2.d6265991eb8da9b735273"... res_len = 621 relayed_code = 487 relayed_msg = 0xffffffffffffffff reply_bak = 0x20000000 bm = {to_tag_val = { s = 0x7f601e46a692 "f148edd50b878efc51a72f445b390303-e1110000\r\nCall-ID: c2e2b55c-e574-1239-3cbd-6cb3112351ce\r\nCSeq: 31882977 INVITE\r\nServer: OpenSIPg SIP Proxy (5.4.2-8 (x86_64/linux))\r\nContent-Length: 0\r\n\r\n", len = 41}} totag_retr = 0 reply_status = RPS_COMPLETED uas_rb = 0x7f5ffb53e370 to_tag = 0x7f601d525770 <tm_tag> reason = {s = 0x560e8aad2dbb "Request Terminated", len = 18} onsend_params = {req = 0x7ffd1c349940, rpl = 0x7f5ffaeeb7c0, param = 0x7ffd1c349880, code = 491640932, flags = 32608, branch = 0, t_rbuf = 0x59d, dst = 0x7f5ffb0ea590, send_buf = {s = 0x7ffd1c349940 "p\231\064\034\375\177", len = 491699179}} ip = {af = 1, len = 0, u = {addrl = {140050215200048, 140050209586032}, addr32 = {4216579376, 32607, 4210965360, 32607}, addr16 = {58672, 64339, 32607, 0, 15216, 64254, 32607, 0}, addr = "0\345S\373_\177\000\000p;\376\372_\177\000"}} __func__ = "relay_reply" #3 0x00007f601d49c7b3 in fake_reply (t=0x7f5ffb53e2a0, branch=0, code=408) at timer.c:295 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 517217456}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 517217456}}}} do_cancel_branch = 0 reply_status = 3845367323 #4 0x00007f601d49cc35 in final_response_handler (r_buf=0x7f5ffb53e540, t=0x7f5ffb53e2a0) at timer.c:462 silent = 0 branch_ret = -1 prev_branch = -1 now = 2146494577 #5 0x00007f601d49cd29 in retr_buf_handler (ticks=2146494577, tl=0x7f5ffb53e560, p=0xfa0) at timer.c:518 rbuf = 0x7f5ffb53e540 fr_remainder = 32608 retr_remainder = 473209280 retr_interval = 32765 new_retr_interval_ms = 547787427795 crt_retr_interval_ms = 140725076662752 t = 0x7f5ffb53e2a0 __func__ = "retr_buf_handler" #6 0x0000560e8a7375fa in slow_timer_main () at core/timer.c:1105 n = 12 ret = 0 tl = 0x7f5ffb53e560 i = 610 __func__ = "slow_timer_main"

2 2

Timeout for provisional response other that 100
by David Villasmil 09 Feb '21

09 Feb '21

Hello all, I’m trying to figure out if I can set. Timeout for specific provisional responses. I know I can set timeouts for INV, and restart the timer every time a provisional response is received. But this not what I actually need. What I need is to set a timeout from the 100 Trying to the next 180/183 (or a final response) and set back a 480 if not received. I’m not sure TM would allow me to do that, so maybe using a hash table to store transactions and calculate the time since the INV to the received 180/183. But there’s gotta be a simpler way. Many thanks! David -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Best SIP reply for service activation
by Duarte Rocha 09 Feb '21

09 Feb '21

Hello, I'm currently developing a service on Kamailio where it's possible to configure redirections for a subscriber using a code. In order to implement that client should send an INVITE with a specific code on the Request URI and the redirection is configured. What should be the best way to answer this INVITE? A 200 OK will make the call answered and doesn't seem the best way. A negative reply (4/5/6xx) would work, but it seems strange to have the operation concluded with success and answering with a negative reply. I found "199 - Early Dialog Terminated" to be suitable, but the documentation suggests it should be used upstream. Thanks in advance for any suggestion. Cheers

2 1

Kamailio inbound proxy -> Asterisk
by Mihai 09 Feb '21

09 Feb '21

Hi! Don't know if this is a Kamailio Question, maybe someone had deal with it in the past. I use Kamailio with dispatcher to send the request (registration, invites, all) to my asterisk (inbound) and then the asterisk has the outbound trunks, everything works, but this is little thing in asterisk when entering the "sip show peers" it shows me that all the peers are registered with the kamailio IP, if I set the nat option to no, it will show me the correct IP but breaks other clients. Any idea what to do ?

1 0

How to drop 200 OK in onreply_route ?
by Denys Pozniak 09 Feb '21

09 Feb '21

Hello! In the configuration below Kamailio Proxy creates a transaction for the SIP PUBLISH to get info from the HTTP server in async mode. But before creating a transaction, a synthetic 200 OK is sent, so that I need somehow to drop the real 200 OK from the upstream Presence Server. If drop 200 OK in *reply_route*, tm module starts to retransmit. Those it is necessary that the 200 OK be consumed by the tm module, but does not go further. *if ( !is_method("PUBLISH") ) {* * sl_send_reply("200", "Ok"); t_newtran();* * $http_req(suspend) = 1; http_async_query("$var(url)", "CALLBACK");* *}* *route[CALLBACK] {* * <some header manipulation>* * t_on_reply("PUBLISH_REPLY"); route(RELAY); exit;* *}* *onreply_route[PUBLISH_REPLY] { if ( t_check_status("200") ) { drop; # Does not work!!! }}* Any advice is appreciated -- BR, Denys Pozniak

3 8

Kamailio config file for making Kamailio a Sip Proxy
by Derick Greenlee 08 Feb '21

08 Feb '21

Hello, I had some questions regarding the Kamailio config file. I am trying to make Kamailio just behave as a sip proxy between two sip trunks. Could you send me an example for this possibly?

2 1

authenticated INVITE badly managed when topos is activated
by frédéric Gaisnon 08 Feb '21

08 Feb '21

Hi, If topos is activated and kamailio responds with a 407 "proxy authentication required" to an initial INVITE, INVITE received after with credentials (MD5 response in Proxy-Authorization header) is badly managed. Credentials are never validated and Kamailio responds 407 again. If topoh is used instead topos all works fine and credentials are validated. call flow is: Phone sends INVITE to kamailio SBC kamailio respond 407 "proxy authentication required" because SBC wants to authenticate caller Phone resends INVITE with Proxy-Authorization header with all valid information kamailio responds 407 again instead forwarding INVITE. My code: if (!pv_auth_check("$fd", "$sht(auth_cache=>$var(key))", "0", "1")) { auth_challenge("$fd", “1”); exit; } # user authenticated - remove auth header consume_credentials(); So if topos is used, pv_auth_check always returns false even if the phone sets valid information. If topoh is activated, pv_auth_check always returns true (same phone and same kamailio SBC versioning) I made my tests with kamailio 5.4.3 on centos 7. Regards, Frédéric Gaisnon

1 0

Registered with sip user using user pass
by Gaurav Bmotra 08 Feb '21

08 Feb '21

Hi I m using kamailio 5.3 OS Ubuntu 18 I wan to Register on sip server and then send traffic to to it form kamailio. Like : Client ---(sip peer)-->kamailio------(sip peer)---->gateway Please help me Thank you Regards Gaurav Kumar

1 0

filter_body("application/sdp") on multipart/mixed; boundary with double Content-Length
by Karsten Horsmann 08 Feb '21

08 Feb '21

Hi List, I have some weird multipart/mixed;boundary issues. I use kamailio 5.3.6 with rtpengine 7.x.x (same with 8.x.x). If i try to remove a multipart/mixed and leave only the sdp with filter_body() that works except one thing. The sender used IMHO an non RFC compliant version of rfc5621 and wrote the Content-Length Header twice (one in the header, one in the sdp). After manipulating the SDP filter_body() lets Content-Length in the sdp (i guess). And rtpengine is not happy with the sdp after that. rtpengine [rtpengine.c:2588]: rtpp_function_call(): proxy replied with error: Failed to parse SDP Any ideas how to solve this? Kind regards Karsten Horsmann https://tools.ietf.org/html/rfc5621#section-3.1 route[REMOVE_MULTIPART] { if (has_body("multipart/mixed")) { if ($sel(cfg_get.remove.multipart) == 1) { if (filter_body("application/sdp")) { remove_hf("Content-Type"); append_hf("Content-Type: application/sdp\r\n"); msg_apply_changes(); xlog("L_WARN", "[$cfg(route)] Body part multipart/mixed with application/sdp found\n"); } else { xlog("L_ERROR", "[$cfg(route)] Body part multipart/mixed without application/sdp found\n"); } } else { xlog("L_INFO", "[$cfg(route)] Body part multipart/mixed found - manipulation disabled\n"); } } } ------------------- INVITE sip:+49XXXXXXXX@172.20.120.57:5060 SIP/2.0 Via: SIP/2.0/UDP 172.20.120.51:5061;branch=z9hG4bK-6589-1-0 From: sipp <sip:sipp@172.20.120.51:5061>;tag=6589SIPpTag001 To: sut <sip:+49XXXXXXXXX@172.20.120.57:5060> Call-ID: 1-6589(a)172.20.120.51 CSeq: 1 INVITE Contact: sip:sipp@172.20.120.51:5061 Max-Forwards: 70 Subject: Performance Test Content-Type: multipart/mixed;boundary=sonus-content-delim Content-Length: 1185 --sonus-content-delim Content-Type: application/sdp Content-Length: 305 v=0 o=Sonus_UAC 895311 862130 IN IP4 8.8.8.8 s=SIP Media Capabilities c=IN IP4 8.8.8.8 t=0 0 m=audio 26088 RTP/AVP 8 0 18 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:18 annexb=no a=fmtp:101 0-15 a=sendrecv a=rtcp:26089 a=ptime:20 --sonus-content-delim Content-Type: application/pidf+xml <?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicLoc" mlns:btd="http://btd.orange-business.com" entity=" pres:geotarget@btip.orange-business.com"><tuple id="XXXX"><status><gp:geopriv><gp:location-info><cl:civicAddress><cl:country>DE</cl:countr <cl:A1>Some State</cl:A1><cl:A3>Somewhere</cl:A3><cl:A4>Somewhere</cl:A4><cl:A6>Somestreet</cl:A6><cl:YYY>1</cl:YYY><cl:PC>9999</cl:PC><cl:EMERGENCYZONE>XXXXXXX</cl:EMERG CYZONE></cl:civicAddress></gp:location-info><gp:usage-rules></gp:usage-rules></gp:geopriv></status></tuple></presence> --sonus-content-delim-- --------------------- INVITE sip:+49XXXXXXXX@foo SIP/2.0 Via: SIP/2.0/TCP 212.XX.XX.XX;branch=z9hG4bKc228.6b8fdf20d79998d1d355feb2dcf5ba63.0 From: sipp <sip:sipp@foo>;tag=6589SIPpTag001 To: sut <sip:+49XXXXXXXX@foo> Call-ID: 1-6589(a)172.20.120.51 CSeq: 1 INVITE Max-Forwards: 69 Content-Length: 347 Content-Type: application/sdp P-Asserted-Identity: <sip:+49XXXXXXXX@212.XX.XX.XX> Contact: <sip:btpsh-60211bbe-674b-1@212.XX.XX.XX;transport=tcp> Content-Length: 305 v=0 o=Sonus_UAC 895311 862130 IN IP4 8.8.8.8 s=SIP Media Capabilities c=IN IP4 8.8.8.8 t=0 0 m=audio 26088 RTP/AVP 8 0 18 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:18 annexb=no a=fmtp:101 0-15 a=sendrecv a=rtcp:26089 a=ptime:20 -- Mit freundlichen Grüßen *Karsten Horsmann*

1 0

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