<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Hi, Adrian!<br>
<br>
Unfortunately RTPProxy can send timeout notifications only to one
timeout_socket - the one specified in the -n parameter. We did
discuss with Maxim a while back the ability to support different
timeout_sockets to different opensips instances, but that
discussion didn't materialize yet.<br>
<br>
However, for your setup, I guess you are already using a
VIP(Virtual IP) that you share between the active and backup
instance. An idea is to use the same VIP as the -n parameter -
that way you will always send the timeout notification to the
active OpenSIPS instance.<br>
<br>
Let me know if that works for you.<br>
<br>
Best regards,<br>
</tt>
<pre class="moz-signature" cols="72">Răzvan Crainea
OpenSIPS Developer
<a class="moz-txt-link-abbreviated" href="http://www.opensips-solutions.com">www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 01/13/2018 03:26 PM, Adrian Fretwell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4d5615d3-a8fb-c468-36a0-5044dba50f8a@topgreen.co.uk">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<font size="-1">Hello & Happy New Year,<br>
<br>
</font><font size="-1">Just trying to work out what to do with the
timeout notifications from RTPProxy when the RTPProxy is used by
more than one Opensips proxy.</font><br>
<font size="-1"><br>
RTPProxy manual says: <br>
</font>
<blockquote><i><font size="-1">-n timeout_socket </font></i><br>
<br>
<font size="-1"><i>This parameter configures the optional
timeout notification socket. The socket should be created by
another application, preferably before starting rtpproxy.
For those sessions where the timeout mechanism is enabled,
notifications are sent on this socket if the session times
out.</i></font><br>
<br>
<font size="-1"><i>There is no default value, notifications are
not sent and not permitted unless a value is specified
explicitly. </i></font><br>
</blockquote>
<font size="-1">So if I have a primary and a backup SIP proxy, how
do I get timeout notifications to both?</font><br>
<font size="-1"><br>
I have tried specifying one of the SIP proxies in the -n
parameter and it works ok, but if I then put a call through the
other SIP proxy , the RTPProxy logs:</font><br>
<font size="-1">Jan 13 13:00:13 rtpproxy1 rtpproxy[474]: <a
class="moz-txt-link-abbreviated"
href="mailto:ERR:1_395279493@192.168.6.48:rtpp_command_ul_handle"
moz-do-not-send="true">ERR:1_395279493@192.168.6.48:rtpp_command_ul_handle</a>:
invalid socket name 81.xx.xxx.250:19991<br>
<br>
I ask the question here because I know some of you do
development work on both Opensips and RTPProxy.</font><br>
<br>
<div class="moz-signature"><font size="-1"><font face="Verdana">Kind
regards,<br>
<br>
Adrian Fretwell<br>
Nottinghamshire<br>
UK.<br>
<br>
</font></font><font size="-1"><font face="Verdana"> </font></font>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>