sr-users October 2018

sr-users@lists.kamailio.org

81 participants
121 discussions

Double Session Description Protocol Version (v) 0 data when using rtpengine
by Wilkins, Steve 24 Oct '18

24 Oct '18

Hello all, I noticed double Session Description Protocol Version (v) 0 data in the SDP section when using rtpengine with Kamailio. Has any else noticed this? Is there a way for Kamailio to remove one of them? Thank you, -Steve

3 12

Double Session Description Protocol Version (v) 0 data when using rtpengine
by Wilkins, Steve 24 Oct '18

24 Oct '18

I was looking at the sdpops_mod.c code hoping that there was an easy way to remove a sess_version (Session Description Protocol Version (v): 0) structure, but there does not appear to be that functionality in that module. It might be a bit of work to remove a duplicate sess_version line. I am using Kamailio 5.1, does anyone know if this is an issue in later versions? Thank you, -Steve

2 4

Re: [SR-Users] htable 1 Millon registers
by Henning Westerholt 24 Oct '18

24 Oct '18

Am Dienstag, 23. Oktober 2018, 23:45:49 CEST schrieb Mauricio Tejeda: > Hello Henning. > Thanks for answered. > Yes, the failure is during the kamailio load. > > I'm increased the shared memory but there is no change, the failure > persists. > > I will try with redis Hello Mauricico, ok - if you want to look people on this list into the error you need to give more details, like some actual error messages from the Kamailio log. But as already pointed out, going with redis is indeed a valid option. Best regards, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio security assessment - https://skalatan.de/de/assessment

1 0

Info: Pre-announcement about Kamailio World 2019
by Daniel-Constantin Mierla 24 Oct '18

24 Oct '18

Hello, being asked couple of times recently, for now I am sending a short note to say that the next edition of Kamailio World Conference is likely to take place at the same location in the city center of Berlin, Germany, during May 6-8, 2019. There are still some bits to sort out before making the dates final, so just have the dates in mind at this moment. Once all is set from organising point of view, we will make the official announcement. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

kamailio+asterisk+webrtc
by arish haque 23 Oct '18

23 Oct '18

Hi, Thank you for the reply! I tried advertising udp port like this listen=udp:192.168.1.x:5060 advertise 182.70.xx.yy:5060. How to advertise RTP ports? Kamailio+RTPengine on a Centos s/m with a priv ip - 192.168.1.x Asterisk is on another CentOs s/m with a priv ip - 192.168.1.y pfsense on pub ip - 182.75.xx.yy PORT FORWARDING on pfsense- sip and rtp ports to kamailio+rtpengine server 192.168.1.x. How to make RTPengine listen on public interface-- 182.75.181.70? sip.conf ======== [general] context=external realm=192.168.1.y bindaddr=0.0.0.0:5080 tcpenable=no allowoverlap=no transport=udp,wss,ws srvlookup=yes qualify=yes directmedia=no canreinvite=no ;---------NAT SUPPORT--------- externip=182.75.xx.yy localnet=192.168.1.0/255.255.255.0 nat=yes ;nat=no //tried but no RTP ;nat=force_rport,comedia //tried but no RTP ;-----------RTP SUPPORT---------------- rtpkeepalive=30 disallow=all allow=gsm allow=ulaw allow=opus allow=alaw allow=g723 ================== and i am using asterisk realtime support for mysql to store peer details. With Regards, Arish Haque

1 0

kamailio + asterisk + webrtc
by arish haque 23 Oct '18

23 Oct '18

Hi, Thank you for the reply! I tried advertising udp port like this listen=udp:192.168.1.x:5060 advertise 182.70.xx.yy:5060. How to advertise RTP ports? Kamailio+RTPengine on a Centos s/m with a priv ip - 192.168.1.x Asterisk is on another CentOs s/m with a priv ip - 192.168.1.y pfsense on pub ip - 182.75.xx.yy PORT FORWARDING on pfsense- sip and rtp ports to kamailio+rtpengine server 192.168.1.x. sip.conf ======== [general] context=external realm=192.168.1.y bindaddr=0.0.0.0:5080 tcpenable=no allowoverlap=no transport=udp,wss,ws srvlookup=yes qualify=yes directmedia=no canreinvite=no ;---------NAT SUPPORT--------- externip=182.75.xx.yy localnet=192.168.1.0/255.255.255.0 nat=yes ;nat=no //tried but no RTP ;nat=force_rport,comedia //tried but no RTP ;-----------RTP SUPPORT---------------- rtpkeepalive=30 disallow=all allow=gsm allow=ulaw allow=opus allow=alaw allow=g723 ================== How to make RTPengine listen to public interface-- 182.75.181.70? With Regards, Arish Haque

1 0

kamailio + asterisk + webrtc
by arish haque 23 Oct '18

23 Oct '18

Hi, I tried advertising udp port like this listen=udp:192.168.1.x:5060 advertise 182.70.xx.yy:5060. How to advertise RTP ports? Kamailio+RTPengine on a Centos s/m with a priv ip - 192.168.1.x Asterisk is on another CentOs s/m with a priv ip - 192.168.1.y pfsense on pub ip - 182.75.xx.yy PORT FORWARDING on pfsense- sip and rtp ports to kamailio+rtpengine server 192.168.1.x. Config and logs are attached. Thank you for the reply! With Regards, Arish Haque

1 0

Re: [SR-Users] kamailio + asterisk + webrtc
by arish haque 23 Oct '18

23 Oct '18

Hi Fred, I have advertised the udp port in kamailio.cfg like below - listen=udp:192.168.1.x:5060 advertise 182.70.xx.yy:5060 But how to advertise rtp Ports?? I have attached sip.conf *Asterisk 1----\ * * \ ------ **Kamailio+RTPPROXY ----** FW (pfsense **182.75.xx.yy public-IP)**--- INTERNET** \ **(private ip - 192.168.1.x)* *Asterisk n------\ * *Th**anks & Regards,* *Arish Haque*

3 2

htable 1 Millon registers
by Mauricio Tejeda 23 Oct '18

23 Oct '18

Good afternoon. Trying to use the htables module to load an extensive table in memory, I can not start kamailio. If the table contains few records (5 and 10 in my examples), this works without problems, for everything else I lose the connection to the database "Lost connection to MySQL server during query" I modified the timeout of mariadb but I can not work. Someone with a similar problem or ideas on how to solve it? Thank you

3 3

RTPEngine set IDs
by Alex Balashov 22 Oct '18

22 Oct '18

Hi, I have a question about RTPEngine set IDs: As of Kamailio 5.x, it appears the RTPEngine module has got quite smart. Even if I don't set `setid_avp`, it still knows which RTPEngine instance and set ID was engaged by an initial rtpengine_offer() / rtpengine_manage() command. This knowledge persists even to delete calls in CANCEL / BYE handling, or in subsequent offer/answer calls in reinvites or UPDATEs. That's great, and very convenient. It saves me the trouble of having to store the set ID in an RR param or as a dialog variable, because everything Just Works. The problem, of course, is that if I restart Kamailio, all this state is forgotten. So, for example, if I set up a call, answer it, restart Kamailio, then hang it up, the delete command will go to the default set and not necessarily the non-zero set chosen. If I want proper RTPEngine call teardown to persist across restarts, as far as I can tell I will need to store the set ID in an RR param or some other reasonably stateless way. Am I missing anything here? Does the `rtpengine` module offer some means of persisting this data across restarts? As far as I can tell, its database backing is for the set definitions only and not for call state. Cheers, -- 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/

1 0

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

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 October 2018