<div dir="ltr"><div>Good day Rick,</div><div><br></div><div>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.</div><div>It's pretty clear, furthermore an example of the systemd service file is given as an example, I underline this - an example.</div><div><br></div><div>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.</div><div><br></div><div>Log level option has the following syntax: -d log_level[:log_facility]</div><div>So you need to pick out one of the following log levels: DBUG, INFO, WARN, ERR and CRIT</div><div>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):</div><div>...</div><div>local5.* /var/log/rtpproxy.log</div><div><br></div><div>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.</div><div>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.</div><div>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.</div><div><br></div><div>Best regards.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 12, 2021 at 9:27 PM Rick McGill - ₪ <<a href="mailto:rick@netrovoip.com">rick@netrovoip.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Donat,<br>
<br>
I went through your links and setup RTPproxy to autostart at boot time.<br>
Also changed the log from LOG-LOCAL5 = rtpproxy.log<br>
<br>
Note that it was hell getting it to work. It kept failing to load a boot time. <br>
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.<br>
<br>
FROIM:<br>
ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -s unix:/var/run/rtpproxy/rtpproxy.sock \<br>
-u rtpproxy rtpproxy -n unix:/var/run/rtpproxy/rtpproxy_timeout.sock $OPTIONS<br>
<br>
TO:<br>
ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -s unix:/var/run/rtpproxy/rtpproxy.sock \<br>
-n unix:/var/run/rtpproxy/rtpproxy_timeout.sock $OPTIONS<br>
<br>
Just FYI.<br>
<br>
------------------------------------------------------------------------------------------------------------------------<br>
Rick McGill – CEO<br>
Rick@NetroVOIP.com | Rick@NetropolitanWorks.com <br>
Thailand: +66-2105-4262 x1001 | USA: +1-737-237-2030 | Mobile: +66-85557-3000<br>
Support:: +66-97047-2000 | SKYPE & LINE ID: NetroVOIP | Support@NetroVOIP.com<br>
₪ <a href="http://www.NetroVOIP.com" rel="noreferrer" target="_blank">www.NetroVOIP.com</a> Telecommunications / Video Consulting & Solutions Provider<br>
--------------------------------------------------------------------------------------------------------------------------<br>
<br>
From: Donat Zenichev <<a href="mailto:donat.zenichev@gmail.com" target="_blank">donat.zenichev@gmail.com</a>> <br>
Sent: Friday, February 12, 2021 8:03 PM<br>
To: Rick McGill - ₪ <<a href="mailto:rick@netrovoip.com" target="_blank">rick@netrovoip.com</a>><br>
Cc: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy<br>
<br>
Good day Rick,<br>
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).<br>
As I have already mentioned, you need to configure systemd (if that is a supervisor on your Debian system, which should actually be).<br>
<br>
Please read two following sections of the user manual:<br>
- getting started with RTPproxy - <a href="https://www.rtpproxy.org/doc/master/user_manual.html#idm221" rel="noreferrer" target="_blank">https://www.rtpproxy.org/doc/master/user_manual.html#idm221</a><br>
- configuration of systemd service for RTPproxy - <a href="https://www.rtpproxy.org/doc/master/user_manual.html#idm650" rel="noreferrer" target="_blank">https://www.rtpproxy.org/doc/master/user_manual.html#idm650</a><br>
<br>
After you are done with steps mentioned in those sections, your RTPproxy will start independently after the following reboot.<br>
<br>
What relates to listening sockets please read the mentioned chapters to find an answer.<br>
Just a brief overview of the most commonly used options:<br>
"-L" - sets the maximum number of open file descriptors per process<br>
"-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<br>
"-m" - the lowest port to be used for RTP/RTCP sessions allocation<br>
"-M" - an opposite to the above<br>
"-d" - debug level (which will be used to log events to either syslog or a separate log file, if you choose so)<br>
"-p" - a link to the PID file, which will be created as soon as binary starts its work<br>
"-u" - user and group to be used for handling the process(es)<br>
"-n" - specifies permitted notification socket, this socket must be created by another application, preferably before starting rtpproxy itself<br>
(for e.g. OpenSIPS crates a timeout socket by usage of this modparam: <a href="https://opensips.org/html/docs/modules/3.1.x/rtpproxy.html#param_rtpp_notify_socket" rel="noreferrer" target="_blank">https://opensips.org/html/docs/modules/3.1.x/rtpproxy.html#param_rtpp_notify_socket</a>)<br>
<br>
Other than that, please read the user manual to find a ready template for running with the systemd supervisor.<br>
<br>
I hope this answers your questions.<br>
<br>
<br>
<br>
On Fri, Feb 12, 2021 at 12:40 PM Rick McGill - ₪ <mailto:<a href="mailto:rick@netrovoip.com" target="_blank">rick@netrovoip.com</a>> wrote:<br>
Dear Donat,<br>
<br>
I REALLY REALLY appreciate your comments and help!! It got the ball rolling for me. <br>
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.<br>
<br>
I finally got it working!<br>
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<br>
For now I just did the startup command via the command line to see if it would work.<br>
<br>
root@sip:/usr/src/rtpproxy# rtpproxy -l 10.1.1.57 -s udp:localhost:12221 -F<br>
<br>
I probably need to add the Public IP and 127.0.0.1 or localhost also for -l command line option.<br>
<br>
root@sip:/usr/src/rtpproxy# rtpproxy -V<br>
2.2.alpha.3a82dd9d<br>
<br>
<br>
<br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16714]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16715]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16720]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16718]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16719]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16721]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16722]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16724]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16723]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16726]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16725]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16728]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
Feb 12 17:22:27 sip systemd[1]: Started OpenSIPS is a very fast and flexible SIP (RFC3261) server. <br>
Feb 12 17:22:27 sip /usr/sbin/opensips[16730]: INFO:rtpproxy:rtpp_test: rtp proxy <udp:localhost:12221> found, support for it enabled <br>
<br>
<br>
------------------------------------------------------------------------------------------------------------------------<br>
Rick McGill – CEO<br>
mailto:<a href="mailto:Rick@NetroVOIP.com" target="_blank">Rick@NetroVOIP.com</a> | mailto:<a href="mailto:Rick@NetropolitanWorks.com" target="_blank">Rick@NetropolitanWorks.com</a> <br>
Thailand: +66-2105-4262 x1001 | USA: +1-737-237-2030 | Mobile: +66-85557-3000<br>
Support:: +66-97047-2000 | SKYPE & LINE ID: NetroVOIP | mailto:<a href="mailto:Support@NetroVOIP.com" target="_blank">Support@NetroVOIP.com</a><br>
₪ <a href="http://www.NetroVOIP.com" rel="noreferrer" target="_blank">http://www.NetroVOIP.com</a> Telecommunications / Video Consulting & Solutions Provider<br>
-------------------------------------------------------------------------------------------------------------------------- <br>
<br>
From: Donat Zenichev <mailto:<a href="mailto:donat.zenichev@gmail.com" target="_blank">donat.zenichev@gmail.com</a>> <br>
Sent: Friday, February 12, 2021 3:22 PM<br>
To: Rick McGill - ₪ <mailto:<a href="mailto:rick@netrovoip.com" target="_blank">rick@netrovoip.com</a>><br>
Cc: OpenSIPS users mailling list <mailto:<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy<br>
<br>
Good day Rick,<br>
sure I'm always glad to help.<br>
<br>
OpenSIPS is first of all a SIP proxy.<br>
That's why you get OpenSIPS binary, accompanying shared libraries (.so libraries) and configuration files for it (opensips script, it's C-like).<br>
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.:<br>
media proxying (RTPproxy in your case), B2B logic, fraud detection/protection, load-balancing etc. etc. (this list is dramatically huge).<br>
<br>
Here you can find a list of useful guidelines provided by OpenSIPS dev team:<br>
<a href="https://www.opensips.org/Documentation/Manual-3-1" rel="noreferrer" target="_blank">https://www.opensips.org/Documentation/Manual-3-1</a><br>
<br>
If you wonder how to start with RTPproxy, I would advise to compile 2.0 firstly.<br>
It's here: <a href="https://github.com/sippy/rtpproxy/tree/rtpp_2_0" rel="noreferrer" target="_blank">https://github.com/sippy/rtpproxy/tree/rtpp_2_0</a><br>
Looking in the experience back, this version showed itself as the best one.<br>
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.<br>
<br>
As a guideline to RTPproxy, please try to look into that: <a href="https://www.rtpproxy.org/doc/master/user_manual.html" rel="noreferrer" target="_blank">https://www.rtpproxy.org/doc/master/user_manual.html</a><br>
<br>
Then depending on which supervisor you use (if you have debian 10.7, that should be systemd),<br>
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.<br>
Options and syntax of their usage can be obtained at the user manual I mentioned above.<br>
<br>
Best regards.<br>
<br>
<br>
<br>
<br>
On Fri, Feb 12, 2021 at 9:22 AM Rick McGill - ₪ <mailto:<a href="mailto:rick@netrovoip.com" target="_blank">rick@netrovoip.com</a>> wrote:<br>
Dear Donat,<br>
<br>
No I did not install or compile RTPproxy yet.<br>
I'm very new to OpenSIPs but have knowledge in other areas of Telco.<br>
<br>
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.<br>
<br>
Anyway thanks for your reply. Just your questions got me pointed in the right direction.<br>
<br>
<br>
------------------------------------------------------------------------------------------------------------------------<br>
Rick McGill – CEO<br>
mailto:<a href="mailto:Rick@NetroVOIP.com" target="_blank">Rick@NetroVOIP.com</a> | mailto:<a href="mailto:Rick@NetropolitanWorks.com" target="_blank">Rick@NetropolitanWorks.com</a> <br>
Thailand: +66-2105-4262 x1001 | USA: +1-737-237-2030 | Mobile: +66-85557-3000<br>
Support:: +66-97047-2000 | SKYPE & LINE ID: NetroVOIP | mailto:<a href="mailto:Support@NetroVOIP.com" target="_blank">Support@NetroVOIP.com</a><br>
₪ <a href="http://www.NetroVOIP.com" rel="noreferrer" target="_blank">http://www.NetroVOIP.com</a> Telecommunications / Video Consulting & Solutions Provider<br>
-------------------------------------------------------------------------------------------------------------------------- <br>
<br>
From: Donat Zenichev <mailto:<a href="mailto:donat.zenichev@gmail.com" target="_blank">donat.zenichev@gmail.com</a>> <br>
Sent: Thursday, February 11, 2021 2:37 PM<br>
To: OpenSIPS users mailling list <mailto:<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] OpenSIPs 3.1 New install ERROR in Logs rtpproxy<br>
<br>
Good day Rick.<br>
<br>
It looks like your OpenSIPS instance is complaining due to the absence of RTPproxy daemon.<br>
Or at least a socket, which OpenSIPS tries to use, is not reachable for some reason (udp:localhost:12221).<br>
<br>
Have you compiled the RTPproxy already?<br>
And also could you share your configuration of rtpproxy.so ?<br>
<br>
Best regards<br>
<br>
On Thu, Feb 11, 2021 at 9:28 AM Rick McGill - ₪ <mailto:<a href="mailto:mailto" target="_blank">mailto</a>:<a href="mailto:rick@netrovoip.com" target="_blank">rick@netrovoip.com</a>> wrote:<br>
Dear OpenSIPs Community,<br>
<br>
I have a fresh install of OpenSIPs 3.1 on Debian 10.7<br>
I have done the basic install but it is yet to be configured with any<br>
gateways and only has a few test users setup on it.<br>
I'm new to OpenSIPs.<br>
<br>
The ERROR issue I'm seeing in the log files seems related to rtpproxy.<br>
I’m not familiar yet with OpenSIPs so if someone could at least point in the<br>
right direction to start to solve this error it might save me a lot of time<br>
Googling.<br>
<br>
-----------------------------<br>
Feb 11 13:32:03 sip /usr/sbin/opensips[1704]: WARNING:rtpproxy:rtpp_test:<br>
support for RTP proxy <udp:localhost:12221> has been disabled temporarily<br>
Feb 11 13:32:03 sip /usr/sbin/opensips[1703]:<br>
ERROR:rtpproxy:send_rtpp_command: can't send (#2 iovec buffers) command to a<br>
RTP proxy (111:Connection refused)<br>
Feb 11 13:32:03 sip /usr/sbin/opensips[1703]:<br>
ERROR:rtpproxy:send_rtpp_command: proxy <udp:localhost:12221> does not<br>
respond, disable it<br>
Feb 11 13:32:03 sip /usr/sbin/opensips[1703]: WARNING:rtpproxy:rtpp_test:<br>
can't get version of the RTP proxy<br>
-----------------------------<br>
<br>
<br>
----------------------------------------------------------------------------<br>
--------------------------------------------<br>
Rick McGill – CEO<br>
mailto:<a href="mailto:mailto" target="_blank">mailto</a>:Rick@NetroVOIP.com | mailto:<a href="mailto:mailto" target="_blank">mailto</a>:Rick@NetropolitanWorks.com <br>
Thailand: +66-2105-4262 x1001 | USA: +1-737-237-2030 | Mobile:<br>
+66-85557-3000<br>
Support:: +66-97047-2000 | SKYPE & LINE ID: NetroVOIP |<br>
mailto:<a href="mailto:mailto" target="_blank">mailto</a>:Support@NetroVOIP.com <br>
₪ <a href="http://www.NetroVOIP.com" rel="noreferrer" target="_blank">http://www.NetroVOIP.com</a> Telecommunications / Video Consulting & Solutions<br>
Provider<br>
----------------------------------------------------------------------------<br>
---------------------------------------------- <br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
mailto:<a href="mailto:mailto" target="_blank">mailto</a>:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
-- <br>
<br>
Best regards,<br>
Donat Zenichev<br>
<br>
<br>
-- <br>
<br>
Best regards,<br>
Donat Zenichev<br>
<br>
<br>
-- <br>
<br>
Best regards,<br>
Donat Zenichev<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr"><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">Best regards,<br></font></div><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">Donat Zenichev<br><br></font></div></div></div></div></div></div></div></div>