date:20210212

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

2021-02-12 Thread Donat Zenichev

Good day Rick,

please try to carefully read the manual in order to understand the meaning
of options, which are given to the binary at the start time.
It's pretty clear, furthermore an example of the systemd service file is
given as an example, I underline this - an example.

This means you use that as a template, but you adjust it to your setup
using the provided user manual. I hope I'm clear enough.

Log level option has the following syntax: -d log_level[:log_facility]
So you need to pick out one of the following log levels: DBUG, INFO, WARN,
ERR and CRIT
and an existing log facility at your system, so in other words this should
be pre-defined, for e.g. (file /etc/rsyslog.d/50-default.conf):
...
local5.*/var/log/rtpproxy.log

What relates to the "-u rtpproxy rtpproxy" option, this means that you
should have created a user and an appropriate group with a given name.
The option which is pointed out in the template, is only as an example, one
can freely pick out any other user/group he or she wants to run.
One might as well skip this and run using default user/group which will be
picked out in its turn by a supervisor of the OS.

Best regards.

On Fri, Feb 12, 2021 at 9:27 PM Rick McGill - ₪  wrote:

> Dear Donat,
>
> I went through your links and setup RTPproxy to autostart at boot time.
> Also changed the log from LOG-LOCAL5  =  rtpproxy.log
>
> Note that it was hell getting it to work.  It kept failing to load a boot
> time.
> Seems like it would not work with this option on the command line  "-u
> rtpproxy rtproxy"   I had to remove it then all would autostart at boot
> time ok.
>
> FROIM:
> ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -s
> unix:/var/run/rtpproxy/rtpproxy.sock \
>  -u rtpproxy rtpproxy -n unix:/var/run/rtpproxy/rtpproxy_timeout.sock
> $OPTIONS
>
> TO:
> ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -s
> unix:/var/run/rtpproxy/rtpproxy.sock \
>  -n unix:/var/run/rtpproxy/rtpproxy_timeout.sock $OPTIONS
>
> Just FYI.
>
>
> 
> Rick McGill – CEO
> r...@netrovoip.com | r...@netropolitanworks.com
> Thailand: +66-2105-4262  x1001  |   USA: +1-737-237-2030   |Mobile:
> +66-85557-3000
> Support:: +66-97047-2000  |  SKYPE & LINE ID:  NetroVOIP  |
> supp...@netrovoip.com
>   ₪  www.NetroVOIP.com  Telecommunications / Video Consulting & Solutions
> Provider
>
> --
>
> From: Donat Zenichev 
> Sent: Friday, February 12, 2021 8:03 PM
> To: Rick McGill - ₪ 
> Cc: OpenSIPS users mailling list 
> Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs
> rtpproxy
>
> Good day Rick,
> you are right, RTPproxy does not start after a reboot of a machine,
> because there is essentially no entity responsible for that (to start
> RTPproxy).
> As I have already mentioned, you need to configure systemd (if that is a
> supervisor on your Debian system, which should actually be).
>
> Please read two following sections of the user manual:
> - getting started with RTPproxy -
> https://www.rtpproxy.org/doc/master/user_manual.html#idm221
> - configuration of systemd service for RTPproxy -
> https://www.rtpproxy.org/doc/master/user_manual.html#idm650
>
> After you are done with steps mentioned in those sections, your RTPproxy
> will start independently after the following reboot.
>
> What relates to listening sockets please read the mentioned chapters to
> find an answer.
> Just a brief overview of the most commonly used options:
> "-L" - sets the maximum number of open file descriptors per process
> "-l" - binding a socket to a particular IP interface of the machine. You
> can essentially set just "0.0.0.0" if you desire to listen to all available
> IP interfaces
> "-m" - the lowest port to be used for RTP/RTCP sessions allocation
> "-M" - an opposite to the above
> "-d" - debug level (which will be used to log events to either syslog or a
> separate log file, if you choose so)
> "-p" - a link to the PID file, which will be created as soon as binary
> starts its work
> "-u" - user and group to be used for handling the process(es)
> "-n" - specifies permitted notification socket, this socket must be
> created by another application, preferably before starting rtpproxy itself
> (for e.g. OpenSIPS crates a timeout socket by usage of this modparam:
> https://opensips.org/html/docs/modules/3.1.x/rtpproxy.html#param_rtpp_notify_socket
> )
>
> Other than that, please read the user manual to find a ready template for
> running with the systemd supervisor.
>
> I hope this answers your questions.
>
>
>
> On Fri, Feb 12, 2021 at 12:40 PM Rick McGill - ₪  r...@netrovoip.com> wrote:
> Dear Donat,
>
> I REALLY REALLY appreciate your comments and help!!   It got the ball
> rolling for me.
> I was stuck a bit because I’m

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

2021-02-12 Thread Rick McGill - ₪

Dear Donat,

I went through your links and setup RTPproxy to autostart at boot time.
Also changed the log from LOG-LOCAL5  =  rtpproxy.log

Note that it was hell getting it to work.  It kept failing to load a boot time. 
 
Seems like it would not work with this option on the command line  "-u rtpproxy 
rtproxy"   I had to remove it then all would autostart at boot time ok.

FROIM:
ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -s 
unix:/var/run/rtpproxy/rtpproxy.sock \
 -u rtpproxy rtpproxy -n unix:/var/run/rtpproxy/rtpproxy_timeout.sock $OPTIONS

TO:
ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -s 
unix:/var/run/rtpproxy/rtpproxy.sock \
 -n unix:/var/run/rtpproxy/rtpproxy_timeout.sock $OPTIONS

Just FYI.


Rick McGill – CEO
r...@netrovoip.com | r...@netropolitanworks.com 
Thailand: +66-2105-4262  x1001  |   USA: +1-737-237-2030   |Mobile: 
+66-85557-3000
Support:: +66-97047-2000  |  SKYPE & LINE ID:  NetroVOIP  | 
supp...@netrovoip.com
  ₪  www.NetroVOIP.com  Telecommunications / Video Consulting & Solutions 
Provider
--

From: Donat Zenichev  
Sent: Friday, February 12, 2021 8:03 PM
To: Rick McGill - ₪ 
Cc: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

Good day Rick,
you are right, RTPproxy does not start after a reboot of a machine, because 
there is essentially no entity responsible for that (to start RTPproxy).
As I have already mentioned, you need to configure systemd (if that is a 
supervisor on your Debian system, which should actually be).

Please read two following sections of the user manual:
- getting started with RTPproxy - 
https://www.rtpproxy.org/doc/master/user_manual.html#idm221
- configuration of systemd service for RTPproxy - 
https://www.rtpproxy.org/doc/master/user_manual.html#idm650

After you are done with steps mentioned in those sections, your RTPproxy will 
start independently after the following reboot.

What relates to listening sockets please read the mentioned chapters to find an 
answer.
Just a brief overview of the most commonly used options:
"-L" - sets the maximum number of open file descriptors per process
"-l" - binding a socket to a particular IP interface of the machine. You can 
essentially set just "0.0.0.0" if you desire to listen to all available IP 
interfaces
"-m" - the lowest port to be used for RTP/RTCP sessions allocation
"-M" - an opposite to the above
"-d" - debug level (which will be used to log events to either syslog or a 
separate log file, if you choose so)
"-p" - a link to the PID file, which will be created as soon as binary starts 
its work
"-u" - user and group to be used for handling the process(es)
"-n" - specifies permitted notification socket, this socket must be created by 
another application, preferably before starting rtpproxy itself
(for e.g. OpenSIPS crates a timeout socket by usage of this modparam: 
https://opensips.org/html/docs/modules/3.1.x/rtpproxy.html#param_rtpp_notify_socket)

Other than that, please read the user manual to find a ready template for 
running with the systemd supervisor.

I hope this answers your questions.



On Fri, Feb 12, 2021 at 12:40 PM Rick McGill - ₪  
wrote:
Dear Donat,
 
I REALLY REALLY appreciate your comments and help!!   It got the ball rolling 
for me.  
I was stuck a bit because I’m so unfamiliar with OpenSIPs and RTPproxy and the 
info out there is sparce or a little openended.  Not sure what to focus on or 
ignore.
 
I finally got it working!
Only a little bit left I need to do so that it all works automatically when I 
reboot.   Right now after a reboot it does not listen still on port 12221
For now I just did the startup command via the command line to see if it would 
work.
 
root@sip:/usr/src/rtpproxy# rtpproxy -l 10.1.1.57 -s udp:localhost:12221 -F
 
I probably need to add the Public IP and 127.0.0.1 or localhost also for -l  
command line option.
 
root@sip:/usr/src/rtpproxy# rtpproxy -V
2.2.alpha.3a82dd9d
 
 
 
Feb 12 17:22:27 sip /usr/sbin/opensips[16714]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled 
Feb 12 17:22:27 sip /usr/sbin/opensips[16715]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled   
Feb 12 17:22:27 sip /usr/sbin/opensips[16720]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled  
Feb 12 17:22:27 sip /usr/sbin/opensips[16718]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled  
Feb 12 17:22:27 sip /usr/sbin/opensips[16719]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled 
Feb 12 17:22:27 sip /usr/sbin/opensips[16721]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found,

Re: [OpenSIPS-Users] [BLOG] Exploring SSL/TLS libraries for OpenSIPS 3.2

2021-02-12 Thread volga629 via Users


  
  
Hello Vlad,
Interesting thoughts about wolfssl.
How it will play with Linux system where are default openssl.
If it will require additional packaging. 
What benefits compare to current state.

Just some questions list so I will not forget later on to ask.


volga629
 
  
On 2/11/21 12:45 PM, Callum Guy wrote:


  Thanks for that Vlad, I always learn something from these article
releases and this was no exception 

On Thu, 11 Feb 2021 at 12:35, Vlad Patrascu  wrote:

  

Hello everyone,

Check out this new blog post [1] that recounts our process of searching
for and choosing a SSL/TLS library to use in OpenSIPS 3.2, as an
alternative to the problematic OpenSSL.

[1]
https://blog.opensips.org/2021/02/11/exploring-ssl-tls-libraries-for-opensips-3-2/

Cheers,

--
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com


___
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] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

2021-02-12 Thread Donat Zenichev

Good day Rick,
you are right, RTPproxy does not start after a reboot of a machine, because
there is essentially no entity responsible for that (to start RTPproxy).
As I have already mentioned, you need to configure systemd (if that is a
supervisor on your Debian system, which should actually be).

Please read two following sections of the user manual:
- getting started with RTPproxy -
https://www.rtpproxy.org/doc/master/user_manual.html#idm221
- configuration of systemd service for RTPproxy -
https://www.rtpproxy.org/doc/master/user_manual.html#idm650

After you are done with steps mentioned in those sections, your RTPproxy
will start independently after the following reboot.

What relates to listening sockets please read the mentioned chapters to
find an answer.
Just a brief overview of the most commonly used options:
"-L" - sets the maximum number of open file descriptors per process
"-l" - binding a socket to a particular IP interface of the machine. You
can essentially set just "0.0.0.0" if you desire to listen to all available
IP interfaces
"-m" - the lowest port to be used for RTP/RTCP sessions allocation
"-M" - an opposite to the above
"-d" - debug level (which will be used to log events to either syslog or a
separate log file, if you choose so)
"-p" - a link to the PID file, which will be created as soon as binary
starts its work
"-u" - user and group to be used for handling the process(es)
"-n" - specifies permitted notification socket, this socket must be created
by another application, preferably before starting rtpproxy itself
(for e.g. OpenSIPS crates a timeout socket by usage of this modparam:
https://opensips.org/html/docs/modules/3.1.x/rtpproxy.html#param_rtpp_notify_socket
)

Other than that, please read the user manual to find a ready template for
running with the systemd supervisor.

I hope this answers your questions.

On Fri, Feb 12, 2021 at 12:40 PM Rick McGill - ₪  wrote:

> Dear Donat,
>
>
>
> I REALLY REALLY appreciate your comments and help!!   It got the ball
> rolling for me.
> I was stuck a bit because I’m so unfamiliar with OpenSIPs and RTPproxy and
> the info out there is sparce or a little openended.  Not sure what to focus
> on or ignore.
>
>
>
> I finally got it working!
>
> Only a little bit left I need to do so that it all works automatically
> when I reboot.   Right now after a reboot it does not listen still on port
> 12221
>
> For now I just did the startup command via the command line to see if it
> would work.
>
>
>
> root@sip:/usr/src/rtpproxy# rtpproxy -l 10.1.1.57 -s udp:localhost:12221
> -F
>
>
>
> I probably need to add the Public IP and 127.0.0.1 or localhost also for
> -l  command line option.
>
>
>
> root@sip:/usr/src/rtpproxy# rtpproxy -V
>
> 2.2.alpha.3a82dd9d
>
>
>
>
>
>
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16714]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it
> enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16715]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16720]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16718]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16719]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16721]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16722]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16724]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it
> enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16723]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16726]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it
> enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16725]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16728]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
> Feb 12 17:22:27 sip systemd[1]: Started OpenSIPS is a very fast and
> flexible SIP (RFC3261) server.
>
> Feb 12 17:22:27 sip /usr/sbin/opensips[16730]: INFO:rtpproxy:rtpp_test:
> rtp proxy  found, support for it enabled
>
>
>
>
>
>
> 
>
> Rick McGill – CEO
>
> r...@netrovoip.com | r...@netropolitanworks.com
>
> Thailand: +66-2105-4262  x1001  |   USA: +1-737-237-2030   |Mobile:
> +66-85557-3000
>
> Support:: +66-97047-2000  |  SKYPE & LINE ID:  NetroVOIP  |
> supp...@netrovoip.com
>
>   ₪  www.NetroVOIP.com  Telecommunications / Video Consulting & Solutions
> Provider
>
>

Re: [OpenSIPS-Users] where to catch CANCELs in script for branches canceled by tm module

2021-02-12 Thread Jeff Pyle

A week ago I asked the question where the CANCELs appear in the script when
tm sends then to cancel losing branches after a winning one presents
itself.  No takers so far.  Any thoughts?


- Jeff


On Fri, Feb 5, 2021 at 1:01 PM Jeff Pyle  wrote:

> Hello,
>
> This is on OpenSIPS 3.1.1 (abe7ab7c7).  I use t_relay() after lookup() to
> relay INVITEs to all registered contacts for an AOR.  I use
> rtpengine_offer() per-branch, and I keep track of the branches with
> rtpengine's extra_id_pv modparam and via-branches=extra.  To do this right
> I should use rtpengine_delete() on the losing/canceled branches.  I can't
> find where tm's CANCELs hits the script.  I expected them in local_route
> but I don't see them there.  I don't see the corresponding 487s in the
> failure_route, either.  What am I missing?
>
>
> - Jeff
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

2021-02-12 Thread Rick McGill - ₪

Dear Donat,

 

I REALLY REALLY appreciate your comments and help!!   It got the ball rolling 
for me.  
I was stuck a bit because I’m so unfamiliar with OpenSIPs and RTPproxy and the 
info out there is sparce or a little openended.  Not sure what to focus on or 
ignore.

 

I finally got it working!

Only a little bit left I need to do so that it all works automatically when I 
reboot.   Right now after a reboot it does not listen still on port 12221

For now I just did the startup command via the command line to see if it would 
work.

 

root@sip:/usr/src/rtpproxy# rtpproxy -l 10.1.1.57 -s udp:localhost:12221 -F

 

I probably need to add the Public IP and 127.0.0.1 or localhost also for -l  
command line option.

 

root@sip:/usr/src/rtpproxy# rtpproxy -V

2.2.alpha.3a82dd9d

 

 

 

Feb 12 17:22:27 sip /usr/sbin/opensips[16714]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled 

Feb 12 17:22:27 sip /usr/sbin/opensips[16715]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled   

Feb 12 17:22:27 sip /usr/sbin/opensips[16720]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled  

Feb 12 17:22:27 sip /usr/sbin/opensips[16718]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled  

Feb 12 17:22:27 sip /usr/sbin/opensips[16719]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled 

Feb 12 17:22:27 sip /usr/sbin/opensips[16721]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled   

Feb 12 17:22:27 sip /usr/sbin/opensips[16722]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled

Feb 12 17:22:27 sip /usr/sbin/opensips[16724]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled

Feb 12 17:22:27 sip /usr/sbin/opensips[16723]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled   

Feb 12 17:22:27 sip /usr/sbin/opensips[16726]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled

Feb 12 17:22:27 sip /usr/sbin/opensips[16725]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled

Feb 12 17:22:27 sip /usr/sbin/opensips[16728]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled 

Feb 12 17:22:27 sip systemd[1]: Started OpenSIPS is a very fast and flexible 
SIP (RFC3261) server. 

Feb 12 17:22:27 sip /usr/sbin/opensips[16730]: INFO:rtpproxy:rtpp_test: rtp 
proxy  found, support for it enabled   

 

 



Rick McGill – CEO

r...@netrovoip.com | r...@netropolitanworks.com 

Thailand: +66-2105-4262  x1001  |   USA: +1-737-237-2030   |Mobile: 
+66-85557-3000

Support:: +66-97047-2000  |  SKYPE & LINE ID:  NetroVOIP  | 
supp...@netrovoip.com

  ₪  www.NetroVOIP.com  Telecommunications / Video Consulting & Solutions 
Provider

--
   

 

From: Donat Zenichev  
Sent: Friday, February 12, 2021 3:22 PM
To: Rick McGill - ₪ 
Cc: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

 

Good day Rick,

sure I'm always glad to help.

 

OpenSIPS is first of all a SIP proxy.

That's why you get OpenSIPS binary, accompanying shared libraries (.so 
libraries) and configuration files for it (opensips script, it's C-like).

And as another side of OpenSIPS, which is perfect and powerful, you can always 
add needed modules to it for any desires you have, e.g.:

media proxying (RTPproxy in your case), B2B logic, fraud detection/protection, 
load-balancing etc. etc. (this list is dramatically huge).

 

Here you can find a list of useful guidelines provided by OpenSIPS dev team:

https://www.opensips.org/Documentation/Manual-3-1

 

If you wonder how to start with RTPproxy, I would advise to compile 2.0 firstly.

It's here: https://github.com/sippy/rtpproxy/tree/rtpp_2_0

Looking in the experience back, this version showed itself as the best one.

Still, I want to underline that I might be mistaken about what relates to the 
most stable version, as things could have changed during the course of time.

 

As a guideline to RTPproxy, please try to look into that: 
https://www.rtpproxy.org/doc/master/user_manual.html

 

Then depending on which supervisor you use (if you have debian 10.7, that 
should be systemd),
you can form a configuration file for RTPproxy service and you can pick out 
which parameters to hand to the rtpproxy binary at the start time.

Options and syntax of their usage can be obtained at the user manual I 
mentioned above.

 

Best regards.

 

 

 

 

On Fri, Feb 12, 2021 at 9:22 AM Rick McGill - ₪ mailto:r...@netrovoip.com> > wrote:

Dear Donat,

No I did not install or compile RTPproxy yet.
I'm very new to OpenSIPs but

Re: [OpenSIPS-Users] SIP to WebRTC via OpenSIPS mid-registrar fails: forced proto 6 not matching sips uri

2021-02-12 Thread juancarlosg6

Hi Mark,  is working for us more or less, because is strange situtation, if
the extension WSS received a incoming call working good but if a put the
call in on-hold inmediatly hangout, but if the same extension do the call to
a external number or a SIP extension or another Webrtc extension work very
good hold and unhold very good the call, i dont know how to identify what is
the problem, we are trying to do this in Opensips because actually our
Asterisk PBX receiving directly WSS conections some times have Flooding
Error (From Traffic Valid).



--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

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

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

2021-02-12 Thread johan

Hi Rick,

I would suggest to go for rtpengine.

Below how to install the thing on buster.

|install below packets:|
|gperf libavcodec-dev libavfilter-dev libavformat-dev libavutil-dev
libbencode-perl libcrypt-openssl-rsa-perl libcrypt-rijndael-perl
libdigest-crc-perl libdigest-hmac-perl libevent-dev libglib2.0-dev
libhiredis-dev libio-multiplex-perl libio-socket-inet6-perl libiptc-dev
libjson-glib-dev libnet-interface-perl libpcap0.8-dev libsocket6-perl
libspandsp-dev libswresample-dev libsystemd-dev libxmlrpc-core-c3-dev
iptables-dev dkms libconfig-tiny-perl netcat-openbsd linux-headers-amd64
libopencv-dev default-libmysqlclient-dev libwebsockets-dev libwebsockets8|





|build and install: |
|/usr/src/git clone https://github.com/sipwise/rtpengine.git rtpengine|
|/usr/src/rtpegine/dpkg-buildpackage -d |
|cd ..|
|||pkg-config xtables --variable=xtlibdir |
|// install all packages|
|dpkg -i ngcp-rtpengine-kernel-dkms_9.0.0.0+0~mr9.0.0.0_all.deb |
|dpkg -i ngcp-rtpengine-utils_9.0.0.0+0~mr9.0.0.0_all.deb |
|dpkg -i ngcp-rtpengine-iptables_9.3.0.0+0~mr9.3.0.0_amd64.deb |
|dpkg -i ngcp-rtpengine-daemon_9.0.0.0+0~mr9.0.0.0_amd64.deb|

|add [rtpengine] in /etc/rtpengine/rtpengine.conf|
|specify an interface in rtpengine.conf|
|copy defaults to /etc/defaults/rtpengine |

On 12/02/2021 09:22, Donat Zenichev wrote:
>
> OpenSIPS is first of all a SIP proxy.
> That's why you get OpenSIPS binary, accompanying shared libraries (.so
> libraries) and configuration files for it (opensips script, it's C-like).
> And as another side of OpenSIPS, which is perfect and powerful, you
> can always add needed modules to it for any desires you have, e.g.:
> media proxying (RTPproxy in your case), B


0xD7D896F7DDA70EC3.asc
Description: application/pgp-keys
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

2021-02-12 Thread Donat Zenichev

Good day Rick,
sure I'm always glad to help.

OpenSIPS is first of all a SIP proxy.
That's why you get OpenSIPS binary, accompanying shared libraries (.so
libraries) and configuration files for it (opensips script, it's C-like).
And as another side of OpenSIPS, which is perfect and powerful, you can
always add needed modules to it for any desires you have, e.g.:
media proxying (RTPproxy in your case), B2B logic, fraud
detection/protection, load-balancing etc. etc. (this list is dramatically
huge).

Here you can find a list of useful guidelines provided by OpenSIPS dev team:
https://www.opensips.org/Documentation/Manual-3-1

If you wonder how to start with RTPproxy, I would advise to compile 2.0
firstly.
It's here: https://github.com/sippy/rtpproxy/tree/rtpp_2_0
Looking in the experience back, this version showed itself as the best one.
Still, I want to underline that I might be mistaken about what relates to
the most stable version, as things could have changed during the course of
time.

As a guideline to RTPproxy, please try to look into that:
https://www.rtpproxy.org/doc/master/user_manual.html

Then depending on which supervisor you use (if you have debian 10.7, that
should be systemd),
you can form a configuration file for RTPproxy service and you can pick out
which parameters to hand to the rtpproxy binary at the start time.
Options and syntax of their usage can be obtained at the user manual I
mentioned above.

Best regards.




On Fri, Feb 12, 2021 at 9:22 AM Rick McGill - ₪  wrote:

> Dear Donat,
>
> No I did not install or compile RTPproxy yet.
> I'm very new to OpenSIPs but have knowledge in other areas of Telco.
>
> I'm using the OpenSIPS quick start guides.   Surprised that RTPproxy is
> not even mentioned in them considering the need for it to get OpenSIPs to
> work.
>
> Anyway thanks for your reply.  Just your questions got me pointed in the
> right direction.
>
>
>
> 
> Rick McGill – CEO
> r...@netrovoip.com | r...@netropolitanworks.com
> Thailand: +66-2105-4262  x1001  |   USA: +1-737-237-2030   |Mobile:
> +66-85557-3000
> Support:: +66-97047-2000  |  SKYPE & LINE ID:  NetroVOIP  |
> supp...@netrovoip.com
>   ₪  www.NetroVOIP.com  Telecommunications / Video Consulting & Solutions
> Provider
> --
>
>
> From: Donat Zenichev 
> Sent: Thursday, February 11, 2021 2:37 PM
> To: OpenSIPS users mailling list 
> Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs
> rtpproxy
>
> Good day Rick.
>
> It looks like your OpenSIPS instance is complaining due to the absence of
> RTPproxy daemon.
> Or at least a socket, which OpenSIPS tries to use, is not reachable for
> some reason (udp:localhost:12221).
>
> Have you compiled the RTPproxy already?
> And also could you share your configuration of rtpproxy.so ?
>
> Best regards
>
> On Thu, Feb 11, 2021 at 9:28 AM Rick McGill - ₪ 
> wrote:
> Dear OpenSIPs Community,
>
> I have a fresh install of OpenSIPs 3.1 on Debian 10.7
> I have done the basic install but it is yet to be configured with any
> gateways and only has a few test users setup on it.
> I'm new to OpenSIPs.
>
> The ERROR issue I'm seeing in the log files seems related to rtpproxy.
> I’m not familiar yet with OpenSIPs so if someone could at least point in
> the
> right direction to start to solve this error it might save me a lot of time
> Googling.
>
> -
> Feb 11 13:32:03 sip /usr/sbin/opensips[1704]: WARNING:rtpproxy:rtpp_test:
> support for RTP proxy  has been disabled temporarily
> Feb 11 13:32:03 sip /usr/sbin/opensips[1703]:
> ERROR:rtpproxy:send_rtpp_command: can't send (#2 iovec buffers) command to
> a
> RTP proxy (111:Connection refused)
> Feb 11 13:32:03 sip /usr/sbin/opensips[1703]:
> ERROR:rtpproxy:send_rtpp_command: proxy  does not
> respond, disable it
> Feb 11 13:32:03 sip /usr/sbin/opensips[1703]: WARNING:rtpproxy:rtpp_test:
> can't get version of the RTP proxy
> -
>
>
>
> 
> 
> Rick McGill – CEO
> mailto:r...@netrovoip.com | mailto:r...@netropolitanworks.com
> Thailand: +66-2105-4262  x1001  |   USA: +1-737-237-2030   |Mobile:
> +66-85557-3000
> Support:: +66-97047-2000  |  SKYPE & LINE ID:  NetroVOIP  |
> mailto:supp...@netrovoip.com
>   ₪  http://www.NetroVOIP.com  Telecommunications / Video Consulting &
> Solutions
> Provider
>
> 
> --
>
>
>
>
> ___
> Users mailing list
> mailto:Users@lists.opensips.org
>

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

Re: [OpenSIPS-Users] [BLOG] Exploring SSL/TLS libraries for OpenSIPS 3.2

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

Re: [OpenSIPS-Users] where to catch CANCELs in script for branches canceled by tm module

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

Re: [OpenSIPS-Users] SIP to WebRTC via OpenSIPS mid-registrar fails: forced proto 6 not matching sips uri

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy

9 matches

Site Navigation

Mail list logo

Footer information