sr-users September 2020

sr-users@lists.kamailio.org

84 participants
106 discussions

by Peter Baines

Hi, Can someone send me an invite to the Kamailio Slack channel please. I am sure I used to be a member but I may have used a different email address. -- *Web:* http://pbaines.com *Email:* peter(a)pbaines.com

3 years, 7 months

Info: recordings of Kamailio World 2020 sessions

by Daniel-Constantin Mierla

Hello, for those that couldn't attend the Kamailio World 2020 online event that happened a few weeks ago, or someone wants to view again a session, the recordings of the two days were split per session -- they are available on KamailioWorld youtube channel: * https://www.youtube.com/c/KamailioWorld/ For convenience, they were also grouped in a playlist for KW2020, see: * https://www.youtube.com/c/KamailioWorld/playlists No other editing than just cutting at start/stop of each session. Slides should be available at: * http://kamailio.org/events/2020-KamailioWorldOnline/ Enjoy! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 years, 7 months

Error on ACK/BYE After 200

by Neimar

Hello, I am trying to set up a Webrtc by using Kamailio, Asterisk and Rtpengine. So far, everything is working fine , I'm able to register an extension and make a call, but for some reason, when i'm trying to call a WebRTC extension from any SIP Extension from Asterisk, Kamailio is sending INVITE, WebRTC extension is sending back 200 OK, and then Kamailio is trying to send an ACK through UDP protocol, and not through wss, as it's supposed to do. In console, I see: Sep 21 20:39:06 vsphone3-sbc /usr/sbin/kamailio[9756]: WARNING: {1 102 ACK 332ee81b4eb178ac156e8d3e53a98900@172.16.11.6:5060} <core> [core/forward.c:231]: get_send_socket2(): protocol/port mismatch (forced tls:172.16.11.57:8443, to udp:187.20.56.83:27730) My scenario is: Internet -> Firewall -> Kamailio -> Asterisk Working: Softphone -> Kamailio -> Asterisk (TCP/UDP/TLS(SRTP) Asterisk -> Kamailio -> Softphone (TCP/UDP/TLS(SRTP)) Webrtc -> Kamailio -> Asterisk (WSS) Not Working: Asterisk -> Kamailio -> Webrtc After a answer from Webrtc, I can listen sound, so, RTP in theory is fine. Webrtc send 200 OK to Kamailio Kamailio Send 200 OK to Asterisk. Asterisk Send ACK to Kamailio ACK not forwarded to Webrtc. In attachment, my kamailio.cfg Every Help is welcome. Thanks Neimar.

3 years, 7 months

Kamailio uses Python

by Pavithra Mohanraja

Hi, I am building kamailio as an docker image by installing kamailio using "apt-get install kamailio" in ubuntu 18.04, which installs python by default which makes my image size bigger. Does kamailio uses Python?. else what could be the alternative? Does anybody came across this situation. Kindly advise. Thanks, Pavithra

3 years, 7 months

Kamailio IF Routes

by conradcordeiro＠gmail.com

Hello, Is it possible to set up Kamailio 5.4.1 to use IF to determine how calls are proxied depending on the source of the request? For example, *_if_* calls originate from /pstn.us1.twilio.com/ then _/$du = "sip01.example.com:5060"/_, wheres _*if*_ calls originate from /pstn.us2.twilio.com/ then _/$du = "sip01.example.com:5060"/_. Additionally, would this also be possible based on numbers? For example, _*if*_ calls are to number +1-800-777-8888 then /$du = "sip01.example.com:5060"/, or if calls are to number +1-800-777-9999 then /$du = "sip02.example.com:5060"/. To be clear, I don't expect both examples above to work in the same Kamailio instance but IF and AND clauses are possible, such as _*if*_ calls are to number +1-800-777-8888 AND from /pstn.us1.twilio.com/ then _/$du = "sip01.example.com:5060"/_, it'd be great to test this too. I'm not sure if I'm allowed to ask such specific questions on this mailing list and I hope I'm not asking too much. Many thanks, Conrad

3 years, 7 months

SRTP/TLS BYE Problem with One of the Legs of the Call

by conradcordeiro＠gmail.com

Hello, Thank you for your reading this and for your help. I'm a Kamailio newbie and managed to set up an edge proxy, which works perfectly on UDP traffic. I'm now attempting to deploy TLS/SRTP and everything almost works perfectly. The single issue I'm having is that when either of the parties to an SRTP/TLS call disconnect, the other party's call remains active. With UDP, when one of the parties disconnects the call, the other leg of the call receives the BYE command and the call automatically disconnects. This is how I have our infrastructure set up: 1. Twilio SIP Trunk with Secure Media enabled. 2. Kamailio 5.4.1 set up with TLS module, set to listen on TLS port 5061, SSL certificates from Let's Encrypt, route set to our phone system. 3. Phone system is Asterisk. As per above, everything works almost perfectly with TLS/SRTP. The only issue is that calls will not disconnect when one of the sides hang up. If I disable TLS/SRTP and use UDP only, everything works. Audio is just fine with TLS/SRTP. Does anyone know why calls with SRTP/TLS will not disconnect automatically when one of the parties ends the call? Thank you, Conrad

3 years, 7 months

Kamailio support for 5g

by Pavithra Mohanraja

Hi, Does kamailio IMS support for 5g Network functions since in 5g everything is handled via http requests. Could anyone please respond Thanks, Pavithra

3 years, 7 months

IMS Diameter server module

by Pavithra Mohanraja

Hi, Can anybody reply what is the exact use of diameter server module. I am unable to understand from the kamailio doc provided. It is mentioned that it converts diameter messages to json messages. But without diameter.xml file, it is not working. Whats the exact use of it. Can i not be able to send the http request alone via Rx interface instead of using diameter.xml file. Kindly reply as i am blocked in this for few days. Thanks, Pavithra

3 years, 7 months

Connection-oriented socket closure event hooks

by Alex Balashov

Hi, The `tcpops` module exposes, * event_route[tcp:closed] * event_route[tcp:timeout] * event_route[tcp:reset] These fire on closure of TCP connections and TLS connections. TLS is considered a separate transport in Kamailio, having distinct identifiers in all cases where transport protocol is relevant, configured by separate and specific parameters, and provided by a separate module (tls). But TLS runs on top of TCP, of course, so treating a TLS disconnection as a superset of TCP disconnection makes sense. WebSocket is considered a separate transport in Kamailio, having distinct identifiers in all cases where transport protocol is relevant, configured by separate and specific parameters, and provided by a separate module (websocket). But WebSocket runs on top of TCP, of course... ... yet it doesn't trigger these TCP connection events. Instead, one must use a separate `event_route[websocket_closed]` event route for this. Is there a reason for this inconsistency? I would think that the common denominator of TCP would lead to the same hierarchy of abstraction when it comes to events. It becomes important because if one wishes for Kamailio to log or notify disconnections for vanilla SIP or browser-based clients, one must essentially implement the same code twice. Thank you, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 years, 7 months

webrtc sound problem in version 85.0 google chrome version

by Hamed Rastegar

Hello I am using kamailio 5.1 for WebRTC (websocket) But in the latest version of Google Chrome (85.0) I have a problem, No sound is transmitted between the source and the destination. This problem does not exist in Firefox browser If you have experience in this field, please comment

3 years, 7 months

← Newer
1
2
3
4
5
6
7
8
9
10
11
Older →

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 September 2020