sr-users

sr-users@lists.kamailio.org

28 participants
37537 discussions

Should I ignore Route header in ACK?
by Yuriy Gorlichenko 02 Jul '18

02 Jul '18

Hi I know that this is not question too much close to the kamialio users but mostly losed to the RFC specifiacations but this community looks like pretty much close to it that is why I want to ask this question here, that's why sorry and thanks for help in this question: I have a situation when provider sends me 200 response with Request-Route header and changed contact header: Means response comes from 1.1.1.1:5060 Request-Route contains: 1.1.1.1:5060 But Contact contains: 1.1.1.1:5061 My … [View More]

2 24

Is it possible to play earlmedia with kamailio
by vinod mn 02 Jul '18

02 Jul '18

Hi, I am trying to configure kamailio to play early media and i am using rtpproxy_stream2uac(), but the audio file plays only after the call is connected. How to use rtpproxy_stream2uac() to play only the early media. Thank you vinod.M.N

1 1

Kamailio installation problem
by Dipayan Sanyal 01 Jul '18

01 Jul '18

Hi, I have installed kamailio in my system but while starting I am geeting following errors- Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Access denied for user 'kamailio'@'localhost' (using password: YES) Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool Jul 1 00:32:42 … [View More]coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: usrloc [dlist.c:644]: register_udomain(): failed to open database connection Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: registrar [registrar.c:651]: domain_fixup(): failed to register domain Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: <core> [core/route.c:1153]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/kamailio-5.1/etc/kamailio/kamailio.cfg:643 Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: <core> [core/rvalue.c:3859]: fix_rval_expr(): failure in cfg at line: 643 col: 22 Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: <core> [core/rvalue.c:3859]: fix_rval_expr(): failure in cfg at line: 643 col: 22 Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: ERROR: <core> [core/route.c:1153]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/kamailio-5.1/etc/kamailio/kamailio.cfg:646 Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: tm [t_funcs.c:85]: tm_shutdown(): start Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: tm [t_funcs.c:88]: tm_shutdown(): emptying hash table Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: tm [t_funcs.c:90]: tm_shutdown(): removing semaphores Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: tm [t_funcs.c:92]: tm_shutdown(): destroying tmcb lists Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: tm [t_funcs.c:95]: tm_shutdown(): done Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: <core> [core/mem/shm.c:260]: shm_destroy_manager(): destroying memory manager: q_malloc Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: <core> [core/mem/q_malloc.c:1169]: qm_shm_lock_destroy(): destroying the shared memory lock Jul 1 00:32:42 coditas-Vostro-3558 /usr/local/kamailio-5.1/sbin/kamailio[4354]: DEBUG: <core> [core/mem/pkg.c:90]: pkg_destroy_manager(): destroying memory manager: q_malloc Please look into the problem. Thanking You, Dip [View Less]

2 1

Fwd: Video call recording and mobile push notifications
by Jeremy Renner 01 Jul '18

01 Jul '18

Hi, I would like to setup up my SIP server / PBX for my business, now we have some candidates: 1. Open source solution: - Asterisk PBX, - Freeswitch PBX - Kamailio - OpenSIPS 2. Business solution: - Brekeke PBX(https://www.brekeke.com - Vodia PBX(https://www.vodia.com) - 3CX PBX(https://www.3cx.com) - PortSIP PBX(https://www.portsip.com/portsip-pbx) *Below features are mandatory for our project:* - Video call recording (For the finance … [View More]

1 0

linphone & presence_xml ERROR
by Pali Rohár 01 Jul '18

01 Jul '18

Hi! I'm using linphone 3.6.1 as SIP client and Kamailio 4.4.4 as proxy server and registrar. And every time I try to change online status (presence) in linphone client, I see following error messages in kamailio server log: ERROR: presence_xml [add_events.c:167]: xml_publ_handl(): bad body format ERROR: presence [publish.c:443]: handle_publish(): in event specific publish handling ERROR: tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't generate 500 reply when a final 415 was … [View More]sent out ERROR: sl [sl.c:269]: send_reply(): failed to reply stateful (tm) ERROR: presence [utils_func.c:146]: send_error_reply(): sending 500 Server Internal Error reply ERROR: presence [publish.c:492]: handle_publish(): failed to send error reply So it looks like kamailio is not able to parse presence change which is linphone doing. I captured traffic via tcpdump what linphone sends: 21:58:58.704792 IP (tos 0x68, ttl 64, id 64109, offset 0, flags [DF], proto UDP (17), length 32) LINPHONE_IP_ADDRESS.5060 > KAMAILIO_IP_ADDRESS.5060: SIP 21:58:58.704919 IP (tos 0x68, ttl 64, id 64110, offset 0, flags [DF], proto UDP (17), length 752) LINPHONE_IP_ADDRESS.5060 > KAMAILIO_IP_ADDRESS.5060: SIP, length: 724 PUBLISH sip:USER@HOST SIP/2.0 Via: SIP/2.0/UDP LINPHONE_IP_ADDRESS:5060;rport;branch=z9hG4bK2049418743 From: User <sip:USER@HOST>;tag=184282924 To: User <sip:USER@HOST> Call-ID: 1435474953 CSeq: 26 PUBLISH Content-Type: application/pidf+xml Max-Forwards: 70 User-Agent: Linphone/3.6.1 (eXosip2/4.1.0) Expires: 600 Event: presence Content-Length: 353 <?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="User <sip:USER@HOST>"> <tuple id="sg89ae"> <status><basic>closed</basic></status> <contact priority="0.8">User <sip:USER@HOST></contact> </tuple> </presence> 21:58:58.710097 IP (tos 0x10, ttl 53, id 10255, offset 0, flags [none], proto UDP (17), length 473) KAMAILIO_IP_ADDRESS.5060 > LINPHONE_IP_ADDRESS.5060: SIP, length: 445 SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP LINPHONE_IP_ADDRESS:5060;rport=5060;branch=z9hG4bK2049418743;received=EXTERNAL_IP_ADDRESS From: User <sip:USER@HOST>;tag=184282924 To: User <sip:USER@HOST>;tag=515cb47c4c34ffa85b598d6b25676122.744d Call-ID: 1435474953 CSeq: 26 PUBLISH Proxy-Authenticate: Digest realm="HOST", nonce="NONCE" Server: kamailio (4.4.4 (x86_64/linux)) Content-Length: 0 21:58:58.718147 IP (tos 0x68, ttl 64, id 64111, offset 0, flags [DF], proto UDP (17), length 940) LINPHONE_IP_ADDRESS.5060 > KAMAILIO_IP_ADDRESS.5060: SIP, length: 912 PUBLISH sip:USER@HOST SIP/2.0 Via: SIP/2.0/UDP LINPHONE_IP_ADDRESS:5060;rport;branch=z9hG4bK1165141043 From: User <sip:USER@HOST>;tag=184282924 To: User <sip:USER@HOST> Call-ID: 1435474953 CSeq: 27 PUBLISH Proxy-Authorization: Digest username="USER", realm="HOST", nonce="NONCE", uri="sip:USER@HOST", response="RESP", algorithm=MD5 Content-Type: application/pidf+xml Max-Forwards: 70 User-Agent: Linphone/3.6.1 (eXosip2/4.1.0) Expires: 600 Event: presence Content-Length: 353 <?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="User <sip:USER@HOST>"> <tuple id="sg89ae"> <status><basic>closed</basic></status> <contact priority="0.8">User <sip:USER@HOST></contact> </tuple> </presence> 21:58:58.781668 IP (tos 0x10, ttl 53, id 10259, offset 0, flags [none], proto UDP (17), length 380) KAMAILIO_IP_ADDRESS.5060 > LINPHONE_IP_ADDRESS.5060: SIP, length: 352 SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP LINPHONE_IP_ADDRESS:5060;rport=5060;branch=z9hG4bK1165141043;received=EXTERNAL_IP_ADDRESS From: User <sip:USER@HOST>;tag=184282924 To: User <sip:USER@HOST>;tag=97d8e785fdf42bf9622a64c13c504961-3901 Call-ID: 1435474953 CSeq: 27 PUBLISH Server: kamailio (4.4.4 (x86_64/linux)) Content-Length: 0 I replaced ip addresses in packets by KAMAILIO_IP_ADDRESS, LINPHONE_IP_ADDRESS and EXTERNAL_IP_ADDRESS strings and also SIP account by USER@HOST. Maybe it helps you. Any idea why kamailio refuse presence update and reports those error into error log? Or is there any special setting which is needed for linphone or other SIP clients for online status / presence support? -- Pali Rohár pali.rohar(a)gmail.com [View Less]

2 6

dovecot authentication
by Pali Rohár 30 Jun '18

30 Jun '18

Hi! Is there any module or configuration how to use dovecot SASL authentication in Kamailio? Dovecot exports unix socket (or tcp on localhost) for authentication service and lot of server applications can be configured to use it (e.g. postfix, prosody, ...) to have one central place of user and authentication database. It supports also strong authentication schemas like SCRAM-SHA, but also plain text password or DIGEST-MD5. In SIP is used DIGEST-MD5 therefore it could be suitable also for SIP … [View More]

2 1

Understanding 5XX stats in Kamailio
by Joel Serrano 29 Jun '18

29 Jun '18

Hi, Does anyone know the difference between these metrics?? core:rcv_replies_5xx sl:5xx_replies tmx:5xx_transactions Specially between core and tmx? Thanks, Joel.

2 1

Relevant development links
by Amauri Oliveira 28 Jun '18

28 Jun '18

Hello. I'm new to Kamailio perhaps I've seen it in actions at AirBNB. I'm starting the journey as a new developer who wants to grab Kamailio and build something. I would like to check if you could provide the most relevant links for a beginner also with some samples. I noticed the abundance of modules perhaps I would like to see what people are doing with it. Best Regards, Amauri.

2 1

Fwd: Understanding is_first_hop() and how it handles in-dialog replies
by Joel Serrano 28 Jun '18

28 Jun '18

Hi guys, I'm having an issue which I have narrowed down to is_first_hop(), I can apply a workaround, but I don't know if I'm doing it correctly or if my problem is caused by misconfiguration of anything. Let's say we have the following flow: Client (NAT) TLS -> Kamailio1 (only Public IP) UDP -> Kamailio2 (only Public IP) UDP -> FreeSWITCH (only Public IP). Regarding this setup, let's focus only on Kamailio1. And for the sake of a clear example, I have done a little draw.io … [View More]diagram: >From the above flow, let's stick to the *200 OK* that Kam1 is going to receive from Kam2. (marked in *blue* in the screenshot). First 200 OK (replying to initial INVITE): SIP/2.0 200 OK Via: SIP/2.0/UDP KAM1_PUB_IP;rport=5060;branch=z9hG4bK1e2b. e1307b519c9b5f0015343e13f35aeace.0;i=3 Via: SIP/2.0/TLS [2607:fb90:489b:6e13:85f8:596b:b86b:c831]:54744; received=172.58.17.149;branch=z9hG4bK.jmXSnh-7x;rpo =43842 Record-Route: <sip:KAM2_PUB_IP;lr=on;ftag=7vidaJ3Hw;did=36e.d441> Record-Route: <sip:KAM1_PUB_IP;r2=on;lr=on;ftag=7vidaJ3Hw;did=36e.a792; nat=yes> Record-Route: <sip:KAM1_PUB_FQDN:443;transport=tls;r2=on;lr=on; ftag=7vidaJ3Hw;did=36e.a792;nat=yes> From: "Joel Test 1" <sip:8bd2a0aba14541789bb7269800646458@MY_DOMAIN >;tag=7vidaJ3Hw To: "Joel Test 2" <sip:e78f2617b0d345d3bdb7b6780ece903c@MY_DOMAIN>;tag= vceg6N0m5ypHa Call-ID: 3ezoQGF1kp CSeq: 21 INVITE Contact: <sip:e78f2617b0d345d3bdb7b6780ece903c@FS_PUB_IP:6061;transport=udp> User-Agent: TP MEDIA 2.0 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 358 Remote-Party-ID: "e78f2617b0d345d3bdb7b6780ece903c" <sip: e78f2617b0d345d3bdb7b6780ece903c@MY_DOMAIN>;party=calling; privacy=off;screen=no v=0 o=TP 1529576021 1529576022 IN IP4 FS_PUB_IP s=TP c=IN IP4 FS_PUB_IP t=0 0 m=audio 25484 RTP/AVP 96 101 a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1; maxplaybackrate=8000; sprop-maxcapturerate=8000 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=rtcp:25485 IN IP4 FS_PUB_IP Second 200 OK (replying to in-dialog INVITE with updated SDP): SIP/2.0 200 OK Via: SIP/2.0/UDP KAM1_PUB_IP;rport=5060;branch=z9hG4bKed2b. 0006a6a159e800129a62b4415fdd64e6.0;i=7 Via: SIP/2.0/TLS 192.168.30.63:54752;received=A.B.C.D;branch=z9hG4bK. iKO2iYIgK;rport=27819 From: "Joel Test 1" <sip:8bd2a0aba14541789bb7269800646458@MY_DOMAIN >;tag=7vidaJ3Hw To: "Joel Test 2" <sip:e78f2617b0d345d3bdb7b6780ece903c@MY_DOMAIN>;tag= vceg6N0m5ypHa Call-ID: 3ezoQGF1kp CSeq: 22 INVITE Contact: <sip:e78f2617b0d345d3bdb7b6780ece903c@FS_PUB_IP:6061;transport=udp> User-Agent: TP MEDIA 2.0 Accept: application/sdp Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Content-Type: application/sdp Content-Disposition: session Content-Length: 358 v=0 o=TP 1529576021 1529576022 IN IP4 FS_PUB_IP s=TP c=IN IP4 FS_PUB_IP t=0 0 m=audio 25484 RTP/AVP 96 101 a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1; maxplaybackrate=8000; sprop-maxcapturerate=8000 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=rtcp:25485 IN IP4 FS_PUB_IP Now here comes the problem, I have the following in my kam1 config: route[NATMANAGE] { ... if (is_reply()) { if (isbflagset(FLB_NATB)) { if (is_first_hop()) { fix_nated_contact(); } } } ... } So, on the first 200 OK, when it reaches that part of the config: 1- is_reply() -> OK 2- isbflagset(FLB_NATB) -> OK (because on the initial request NAT was detected blablabla....) 3- is_first_hop() -> FAIL fix_nated_contact() is NOT applied. (This is the correct and the expected behavior). Now, on the second 200 OK, again in that part of the config: 1- is_reply() -> OK 2- isbflagset(FLB_NATB) -> OK 3-is_first_hop() -> OK fix_nated_contact() is applied, thus the contact will be changed, and the client will send the ACK with incorrect information leading to another set of issues... >From the docs: https://www.kamailio.org/docs/modules/5.1.x/ modules/siputils.html#siputils.f.is_first_hop *4.30. is_first_hop()* *The function returns true if the proxy is first hop after the original sender. For incoming SIP requests, it means there is only one Via header. For incoming SIP replies, it means that top Record-Route URI is 'myself' and source address is not matching it (to avoid detecting in case of local loops). Note that it does not detect spirals, which can have the condition for replies true also in the case of additional SIP reply receival.* So going back to the examples: first 200 OK: 1- "top Record-Route URI is 'myself' -> FAIL So we we are NOT the first hop, we do nothing and forward the reply to the client. second 200 OK: 1- "top Record-Route URI is 'myself' -> No record-route headers are present, so we enter the is_first_hop() condition and modify the contact with fix_nated_contact(). Now to the real topic, I have a workaround as: ... if (is_reply()) { if (isbflagset(FLB_NATB)) { if (is_first_hop()) { if (!ds_is_from_list()) { # <-- Check to see if the reply is coming from our internal servers fix_nated_contact(); } } } } ... And that is working correctly, but I would like to understand the reasons. I hope I have explained myself correctly, otherwise it's impossible to get to the point of my questions: 1- Is it correct for is_first_hop() to detect the second 200 OK as a first hop when it isn't? the behavior matches the documentation, so I don't know. If we stick to the check of the headers etc etc, it's working as described, if we stick to the concept of kam1 being actually being the first hop of that 200OK, then the check would need another condition to exclude the 200 OK (or better, the replies) of an in-dialog INVITE. 2- Do you guys consider the workaround something reasonable? Under my opinion I would like to not have to add that, but I also don't know. 3- Am I missing something super standard that avoids all of this? I'm starting to go crazy trying and comparing different things to get to understand this and I want to make sure it's not just a is_first_hop() bug? Sorry for such a long email, but I think that describing the scenario and flow was required. Any input is more than welcome! Thanks! Joel. [View Less]

1 0

Question on the new Kamailio v5.x Releases
by Ginhoux, Patrick 27 Jun '18

27 Jun '18

Hi, I always read your email regarding new stable releases. I am currently working on a project upgrade of multiples servers to the most recent OS (Windows, RedHat) and middleware. In this project, I have upgraded SIP Proxies server running on old version of Kamailio, to the 5.0.1 release (over RedHat 7.4). Effort to make that upgrade and tests have been done with success in the last months. So considering to upgrade to the 5.0.7 or 5.1.4 would be a subsequent work I need to … [View More]

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