I don't think restarting RTPProxy is acceptable, because you will loose
the ongoing RTP sessions.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 01/15/2018 01:03 PM, Adrian Fretwell wrote:
Razvan,
Thankyou for clarifying this, I can work around it either with VIP or
by restarting RTP Proxy with a different -n value.
Kind regards,
Adrian.
On 15/01/18 09:02, Răzvan Crainea wrote:
Hi, Adrian!
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.
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.
Let me know if that works for you.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 01/13/2018 03:26 PM, Adrian Fretwell wrote:
Hello & Happy New Year,
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.
RTPProxy manual says:
/-n timeout_socket /
/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./
/There is no default value, notifications are not sent and not
permitted unless a value is specified explicitly. /
So if I have a primary and a backup SIP proxy, how do I get timeout
notifications to both?
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:
Jan 13 13:00:13 rtpproxy1 rtpproxy[474]:
ERR:1_395279493@192.168.6.48:rtpp_command_ul_handle: invalid socket
name 81.xx.xxx.250:19991
I ask the question here because I know some of you do development
work on both Opensips and RTPProxy.
Kind regards,
Adrian Fretwell
Nottinghamshire
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
_______________________________________________
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
