Re: [OpenSIPS-Users] STUN Server Question

2015-10-02 Thread Bogdan-Andrei Iancu
Hi, If you do not set any values for ports, the defaults are: port1 is 5060 port2 is 3478 Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02.10.2015 18:39, sevpal wrote: Hi, the documentation states “The sockets come from existing SIP sockets

[OpenSIPS-Users] STUN Server Question

2015-10-02 Thread sevpal
Hi, the documentation states “The sockets come from existing SIP sockets or are created”. Based the example in the documentation, “two sockets are defined and two are created”. The stun server will use 4 sockets: a.. socket1 = ip1 : port1 (assuming 5060 inbound/outbound) b.. socket2 = ip1

Re: [OpenSIPS-Users] STUN

2014-03-04 Thread Liviu Chircu
Hello Nick, Thank you for the feedback! Now I have to start updating the documentation... :( Best regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 03/04/2014 07:08 AM, Nick Altmann wrote: Hello, Liviu. It seems it works well. Thank you. Let's add it to source t

Re: [OpenSIPS-Users] STUN

2014-03-03 Thread Nick Altmann
Hello, Liviu. It seems it works well. Thank you. Let's add it to source tree. :-) -- Nick 2014-02-20 20:47 GMT+04:00 Liviu Chircu : > Hello Nick, > > Could you test out the attached patch for the advertised interfaces? > Example of module configuration: > > modparam("stun", "primary_ip", "192.

Re: [OpenSIPS-Users] STUN

2014-02-20 Thread Nick Altmann
Oh, so quick. :-) Thank you. I'll test it and let you know some later. -- Nick 2014-02-20 20:47 GMT+04:00 Liviu Chircu : > Hello Nick, > > Could you test out the attached patch for the advertised interfaces? > Example of module configuration: > > modparam("stun", "primary_ip", "192.168.2.133

Re: [OpenSIPS-Users] STUN

2014-02-20 Thread Liviu Chircu
Hello Nick, Could you test out the attached patch for the advertised interfaces? Example of module configuration: modparam("stun", "primary_ip", "192.168.2.133 / 46.78.50.64") modparam("stun", "primary_port", "5060/ 5061") modparam("stun", "alternate_ip", "192.168.2.134 / 50.64.46.78")

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Bogdan-Andrei Iancu
Yes, that is very true - it is a very good catch ! Thanks and regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 19.02.2014 19:35, Nick Altmann wrote: Thank you. This code needed to run STUN on always NATed servers like Amazon cloud. -- Nick 20

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Nick Altmann
Thank you. This code needed to run STUN on always NATed servers like Amazon cloud. -- Nick 2014-02-19 21:32 GMT+04:00 Bogdan-Andrei Iancu : > Hi, > > I identify the code that need to be changed - it should be a lot of work > to add an "advertised" value for the configured IPs and ports. It sho

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Bogdan-Andrei Iancu
Hi, I identify the code that need to be changed - it should be a lot of work to add an "advertised" value for the configured IPs and ports. It should make it in the new release. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 19.02.2014 17:45

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Nick Altmann
Yes, it is! -- Nick 2014-02-19 17:19 GMT+04:00 Bogdan-Andrei Iancu : > Hi, > > Nick, you want something like an "advertised" but for the STUN stuff ? > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 19.02.2014 14:25, Nick Altmann wro

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Bogdan-Andrei Iancu
Hi, Nick, you want something like an "advertised" but for the STUN stuff ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 19.02.2014 14:25, Nick Altmann wrote: I'm about STUN only. Its required two external IPs. I'm not about routing. -- Nick

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Nick Altmann
I'm about STUN only. Its required two external IPs. I'm not about routing. -- Nick 2014-02-19 16:14 GMT+04:00 Ali Pey : > Hi Nick, > > I don't think such a thing is possible in opensips. There can only be one > advertised_address as far as I know. I think you need to do your own > message manip

Re: [OpenSIPS-Users] STUN

2014-02-19 Thread Ali Pey
Hi Nick, I don't think such a thing is possible in opensips. There can only be one advertised_address as far as I know. I think you need to do your own message manipulation in your route script based on the route it's going to. I'm interested in this scenario as well and look forward to more repl

[OpenSIPS-Users] STUN

2014-02-19 Thread Nick Altmann
Hi! How to correctly configure STUN module if we have two interfaces with internal addresses where NATed two external IPs? (ports are the same) I mean something like advertised_address option. -- Nick ___ Users mailing list Users@lists.opensips.org http

Re: [OpenSIPS-Users] Stun Module - OpenSIPS won't start

2010-05-07 Thread osiris123d
Thanks. Just looked at RFC 3489 and didn't know STUN had to have a second IP. Makes sense why it needs one now. On May 7, 2010 2:56am, "Bogdan-Andrei Iancu [via OpenSIPS (Open SIP Server)]" wrote: > Hi, > you need to define the secondary IP and port params too. > Regards, > Bogda

Re: [OpenSIPS-Users] Stun Module - OpenSIPS won't start

2010-05-07 Thread Bogdan-Andrei Iancu
Hi, you need to define the secondary IP and port params too. Regards, Bogdan osiris123d wrote: > I just compiled the STUN module on Debian 5.0.4 x64 and added the following > stun parameters to my config > > > port=5060 > > /* uncomment and configure the following line if you w

[OpenSIPS-Users] Stun Module - OpenSIPS won't start

2010-05-06 Thread osiris123d
I just compiled the STUN module on Debian 5.0.4 x64 and added the following stun parameters to my config port=5060 /* uncomment and configure the following line if you want opensips to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:173