[OpenSIPS-Users] opensips crash

2018-07-26 Thread volga629 

Hello Everyone,
Opensips crashing randomly how possible find what the issue


Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6297]: 
CRITICAL:core:handle_tcp_worker: dead tcp worker 4 (EOF received), pid 
6292
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
child process 6292 exited by a signal 11
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
core was generated
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: INFO:core:handle_sigs: 
terminating due to SIGCHLD
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6265]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6266]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6267]: INFO:core:sig_usr: 
signal 15 received
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 15(6279) [SIP receiver 
udp:private_ip_interface:5060 ] terminated, still waiting for 31 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 18(6282) [SIP receiver 
udp:public_ip_interface:5082 ] terminated, still waiting for 30 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 20(6284) [SIP receiver 
udp:public_ip_interface:5060 ] terminated, still waiting for 29 more
Jul 26 12:11:43 sbc01 /usr/sbin/opensips[6264]: 
INFO:core:shutdown_opensips: process 22(6286) [SIP receiver 
udp:public_ip_interface:5060 ] terminated, still waiting for 28 more


volga629


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] FreeSWITCH and OpenSIPS for a Pure SIP Video, Chat and Conference Service, ClueCon Presentation Slides

2018-07-26 Thread Bogdan-Andrei Iancu 

Hey, that's a good presentation Giovanni, thanks for sharing it with us !!

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
  http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 07/25/2018 07:29 PM, Giovanni Maruzzelli wrote:

Hello fellow RTCers,

just finished presenting about scaling videoconferencing, chat and 
moderation/direction controls in SIP, with web clients, deskphones, 
smartphone apps, server push (google fcm) via cordova and SIP.js at 
www.cluecon.com .


Here's the slides of my presentation:

http://178.79.181.125/Maruzzelli_FreeSWITCH_OpenSIPS_WebRTC_Pure_SIP_Video_Call_Conferencing_and_Chat_ClueCon_2018_Chicago.pdf

or, shorter,

http://178.79.181.125/Maruzzelli_ClueCon_2018.pdf


From ClueCon blurb:


FreeSWITCH and OpenSIPS for a Pure SIP Video, Chat and
Conference Service

On top of traditional SIP deskphones and softphones, WebRTC let us 
extend the reach of SIP to all browsers, and to smartphone apps that 
wake up with a server push. OpenSIPS has superb SIP and WebRTC support 
and can protect, balance and scale FreeSWITCH insuperable 
conferencing, video MCU, media switching/mixing, SIP SIMPLE message 
processing capabilities. We will see how to build and implement such a 
complete platform, touching both on servers and on clients. Hint: 
SIMPLE, the SIP Instant Messaging Protocol, can be leveraged to 
transport statuses, commands and chats between participants and 
administrators of SIP audio/video calls/conferences.



  Giovanni Maruzzelli


Principal at OpenTelecom.IT



Giovanni is a consultant for the Telco sector, developing software and 
training courses for FreeSWITCH, SIP, WebRTC and Kamailio. He is 
heavily engaged with FreeSWITCH, of which he wrote the interface with 
Skype and with cellular phones. An Internet tech pioneer, in 1996 
Giovanni was cofounder of Italia Online, the most popular Italian 
portal and consumer ISP, and architect of its Internet technologies – 
www.italiaonline.it  Then supervisor of 
Internet operations and architect of the first engine for paid access 
to www.ilsole24ore.com  , the most read 
financial newspaper in Italy and to its databases (migrated from 
mainframe). After that, he was CEO of venture capital funded Matrice, 
developing Telemail unified messaging and multi language phone access 
to email (Text To Speech), and CTO of incubator funded Open4, an open 
source managed applications provider. Then he was for two years in 
Serbia as Internet and Telecommunication Investment Expert for World 
Bank – IFC. Since 2005 he’s based in Italy, and serves ICT and Telco 
companies worldwide.



-giovanni

--

Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Using LetsEncrypt certs with v2.4

2018-07-26 Thread Bogdan-Andrei Iancu 

Hi John,

When the cert is configured via modparam, the cert is loaded on startup 
by OpenSIPS, so any renewal of the cert will have 0 impact on OpenSIPS - 
so you will have to restart after each renewal.


I suggest you to provision the certs via DB (and not script), so you can 
do a reload after renewal, with any need to restart opensips.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
  http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 07/25/2018 06:09 PM, John Quick wrote:

Does anyone have experience using LetsEncrypt certificates for tls or wss in
OpenSIPS v2.4.x over a long enough period of time for the certificate to be
renewed?

Does the OpenSIPS service need to be restarted after each certbot renewal?
This happens about every 2 months.
I have configured opensips so the path in modparam("tls_mgm", "certificate"
is "/etc/letsencrypt/live//cert.pem"
This is actually a sym-link to the actual cert. It seems to work okay, but
I'm wondering what will happen in two months' time when the cert is renewed.

Thanks.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mediaproxy and Debian 8.11

2018-07-26 Thread Tijmen de Mes 
Hi Simone,

Thanks for your suggestion and we updated the download and install guide.

Best regards,

Tijmen de Mes
—
AG Projects

> On 24 jul. 2018, at 15:17, Simone Sestini  wrote:
> 
> Dear Dan,
> 
> this is very clear to me.. this way fix the issue .. but i can suggest you 
> and the stuff to update the Doc pages..
> 
> --> http://mediaproxy.ag-projects.com/download/
> 
> 
> The right way for configure is to add on the source list of apt the follow 
> lines.. where you need to substitude "jessie" with the debian release..
> 
> 
> deb http://ftp.debian.org/debian/ jessie-backports main
> deb-src http://ftp.debian.org/debian/ jessie-backports main
> 
> deb http://ag-projects.com/debian jessie main
> deb-src http://ag-projects.com/debian jessie main
> 
> 
> Thanks a lot for your support.
> 
> Regards
> 
> 
> 
> Il 24/07/18 13:27, Dan Pascu ha scritto:
>> Your problem is that you mix debian 8.11 (jessie) with ag-projects' debian 
>> unstable repositories.
>> 
>> Change your ag-projects repositories to read 'jessie main' instead of 
>> 'unstable main', rerun apt-get update and it should work.
>> 
>> You might also consider adding the jessie-backports repository:
>> 
>> deb http://ftp.it.debian.org/debian/ jessie-bakcports main
>> deb-src http://ftp.it.debian.org/debian/ jessie-bakcports main
>> 
>> Some of our software needs newer versions of some packages that are only 
>> available in the jessie-backports repository (not sure if mediaproxy is one 
>> of them, but others like blink or sipsimple are).
>> 
>> On 24 Jul 2018, at 13:48, Simone Sestini wrote:
>> 
>>> Hi,
>>> 
>>> only the standard and official repository here..
>>> 
>>> ---
>>> deb http://ftp.it.debian.org/debian/ jessie main
>>> deb-src http://ftp.it.debian.org/debian/ jessie main
>>> 
>>> deb http://security.debian.org/ jessie/updates main
>>> deb-src http://security.debian.org/ jessie/updates main
>>> 
>>> # jessie-updates, previously known as 'volatile'
>>> deb http://ftp.it.debian.org/debian/ jessie-updates main
>>> deb-src http://ftp.it.debian.org/debian/ jessie-updates main
>>> 
>>> # AG Projects software
>>> deb http://ag-projects.com/debian unstable main
>>> deb-src http://ag-projects.com/debian unstable main
>>> 
>>> ---
>>> 
>>> and here the output for the  policy you requested.
>>> 
>>> test-rtp:~# apt-cache policy iptables mediaproxy-common
>>> iptables:
>>>   Installato: 1.4.21-2+b1
>>>   Candidato:  1.4.21-2+b1
>>>   Tabella versione:
>>>  *** 1.4.21-2+b1 0
>>> 500 http://ftp.it.debian.org/debian/ jessie/main amd64 Packages
>>> 100 /var/lib/dpkg/status
>>> mediaproxy-common:
>>>   Installato: (nessuno)
>>>   Candidato:  2.6.6
>>>   Tabella versione:
>>>  2.6.6 0
>>> 500 http://ag-projects.com/debian/ unstable/main amd64 Packages
>>> 
>>> 
>>> Thanks
>>> 
>>> 
>>> Il 24/07/18 12:32, Dan Pascu ha scritto:
 Please paste apt's sources list (you can delete private repositories if 
 you have any, I only want to see debian's and ag-projects' repositories). 
 Alternatively you can paste the output from
 
 apt-cache policy iptables mediaproxy-common
 
 On 24 Jul 2018, at 12:20, Simone Sestini wrote:
 
> Dear list..
> 
> I'm trying to install mediaproxy software on Debian 8.11.
> 
> I'm looking around for a solution.. because i'm receiving
> test-rtp:/# apt-get install mediaproxy-common  mediaproxy-relay 
> mediaproxy-web-sessions
> Lettura elenco dei pacchetti... Fatto
> Generazione albero delle dipendenze
> Lettura informazioni sullo stato... Fatto
> Alcuni pacchetti non possono essere installati. Questo può voler dire
> che è stata richiesta una situazione impossibile oppure, se si sta
> usando una distribuzione in sviluppo, che alcuni pacchetti richiesti
> non sono ancora stati creati o sono stati rimossi da Incoming.
> Le seguenti informazioni possono aiutare a risolvere la situazione:
> 
> I seguenti pacchetti hanno dipendenze non soddisfatte:
>  mediaproxy-common : Dipende: libiptc0 ma non è installabile
> E: Impossibile correggere i problemi, ci sono pacchetti danneggiati 
> bloccati.
> test-rtp:/#
> 
> Praticaly mediaproxy-common depend of libiptc0 but it's not found on 
> debian.
> 
> The only lib exist are
> lrwxrwxrwx 1 root root   16 nov  8  2014 /lib/libiptc.so -> 
> libiptc.so.0.0.0
> lrwxrwxrwx 1 root root   16 nov  8  2014 /lib/libiptc.so.0 -> 
> libiptc.so.0.0.0
> -rw-r--r-- 1 root root 5816 nov  8  2014 /lib/libiptc.so.0.0.0
> 
> and i tried to add libiptc0 links too but it dosn't fix..
> 
> lrwxrwxrwx 1 root root   16 lug 23 12:49 /lib/libiptc0.so -> 
> libiptc.so.0.0.0
> lrwxrwxrwx 1 root root   16 lug 23 12:50 /lib/libiptc0.so.0 -> 
> libiptc.so.0.0.0
> 
> Any idea ?
> 
> Regards
> ___
> Users mailing list
>