Hi, John!
Those errors are reported by the RTPProxy server, and depending on the
error, they can be handled by opensips.
In your case, the errors 71 and 72 are reported by RTPProxy when it can
not create UDP listeners for media. Usually these errors are triggered
when rtpproxy runs out of available sockets/file descriptors. You can
increase the number of sockets/file descriptors the RTPProxy server can
use using the -L parameter.
Hope this helps.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 01/16/2018 07:18 PM, John Quick wrote:
Hello,
Can anyone help me understand what might be causing the following error
messages to be reported by OpenSIPS?
2018-01-16 16:42:47 ERROR:rtpproxy:engage_rtp_proxy4_f: error forcing rtp
proxy
2018-01-16 16:42:48 ERROR:rtpproxy:force_rtp_proxy_body: unhandled rtpproxy
error: 71
2018-01-16 16:42:48 ERROR:rtpproxy:force_rtp_proxy_body: unhandled rtpproxy
error: 71
2018-01-16 16:42:49 ERROR:rtpproxy:force_rtp_proxy_body: unhandled rtpproxy
error: 72
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
