[OpenSIPS-Users] STUN

[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
>
>
> 2014-02-19 16:14 GMT+04:00 Ali Pey <alipey at gmail.com 
> <mailto:alipey at gmail.com>>:
>
>     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
>     replies from more knowledgeable people.
>
>     Please post updates when you find a solution.
>
>
>     Regards,
>     Ali Pey
>
>
>     On Wed, Feb 19, 2014 at 5:47 AM, Nick Altmann
>     <nick.altmann at gmail.com <mailto:nick.altmann at gmail.com>> wrote:
>
>         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 at lists.opensips.org <mailto:Users at lists.opensips.org>
>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140219/5e1b71a1/attachment-0001.htm>