Hi, Denis!
Try to use the same socket for both rtpproxy module and application:
modparam("nathelper", "rtpp_notify_socket", "tcp:127.0.0.1:9999")
rtpproxy -n tcp:127.0.0.1:9999

Regards,
--
Răzvan Crainea
OpenSIPS Developer
http://www.opensips-solutions.com

On 05/23/2012 05:13 PM, dpa wrote:

Hello Răzvan

 

Thank you for replay.

But one more question

In man for rtpproxy I read “-n timeout_socket…. The socket should be created by another  application, preferably before starting rtpproxy….”

So as I understand “rtpp_notify_socket” should be like  modparam("nathelper", "rtpp_notify_socket", "tcp:localhost:9999")

and after this rtpproxy should be started with “–n tcp:1.1.1.1:9999” where 1.1.1.1 – ip of opensips serever.

Am I right?

 

From: [email protected] [mailto:[email protected]] On Behalf Of Razvan Crainea
Sent: Wednesday, May 23, 2012 5:47 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] opensips and rtpproxy

 

Hi, Denis!

The socket can be UNIX or TCP according to the documentation[1].

[1] http://www.opensips.org/html/docs/modules/devel/rtpproxy.html#id250454


Regards,

--
Răzvan Crainea
OpenSIPS Developer
http://www.opensips-solutions.com


On 05/23/2012 04:11 PM, dpa wrote:

Hello!

Opensips 1.6.4-2

 

There is one question.

rtpp_notify_socket  may be only unix socket? Or I can use UPD or TCP too?

 

Thank you for any help

 

 

 




_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to