So just firewall the port as we do with RTPProxy and rtp_sock. Got it :).
Thanks Vlad.
N.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Sorry, please ignore. Replied to the wrong post.
On Wed, Aug 7, 2013 at 9:54 AM, mayamatakeshi mayamatake...@gmail.comwrote:
Hello Vlad,
I tested and confirmed it is OK now.
Thanks.
Regards,
Takeshi
On Wed, Aug 7, 2013 at 4:52 AM, Vlad Paiu vladp...@opensips.org wrote:
Hello,
What
Hello,
What are you thinking about more exactly here in terms of security ?
The OpenSIPS worker processes that listen for BIN replicated packages do
not perform any IP authentication by themselves, so if you leave those
UDP ports open from the outside, you are leaving yourself exposed to
Hello Vlad,
I tested and confirmed it is OK now.
Thanks.
Regards,
Takeshi
On Wed, Aug 7, 2013 at 4:52 AM, Vlad Paiu vladp...@opensips.org wrote:
Hello,
What are you thinking about more exactly here in terms of security ?
The OpenSIPS worker processes that listen for BIN replicated
Hi Ryan,
This has nothing to do with dialog pining or accounting - the new
interface allows OpenSIPS to replicate the dialog state to another
OpenSIPS instance. If I misunderstood you, please rephrase :)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
This is pretty exciting!
What are the plans for how this will work with features such as dialog
pinging and accounting?
Regards,
Ryan
On Mon, Jul 29, 2013 at 9:46 AM, Bogdan-Andrei Iancu bog...@opensips.orgwrote:
**
In long term we plan to use the BIN interface to replicate even more
