Hi John,

John Quick wrote:
> Hi Bogdan
>
> Thanks for the info about running OpenSIPS behind NAT. I have to do some more 
> work on the server that
> is behind NAT (such as upgrade it to a later release) so I will try using the 
> advertised_address and
> see if it helps. Tell me please, will the advertised_address make any 
> difference when using mediaproxy
> for far-end NAT traversal? Is there an equivalent parameter in the 
> mediaproxy? Or is it just best to
> not use mediaproxy behind NAT?
>   
the advertise_port|address params affects only the signalling part (as 
opensips does only signalling). No media.....
> I still say that I wouldn't choose to run OpenSIPS behind NAT if at all 
> possible and especially if it
> is required to do far-end NAT traversal, and from Brett's "world of pain" 
> comment it seems I am not
> alone in this opinion. It would also be much easier for a beginner to learn 
> about OpenSIPS if they
> didn't have to deal with the additional complication of near-end NAT.
>   
For media purposes, you need an RTPproxy / mediaproxy on the public 
interface or in bridging mode - I cannot say 100%, but AFAIK, RTPP does 
not have something like "advertise_address" option - it simply uses the 
ip it is listening on.
> As far as the original questions from [email protected], perhaps the problem 
> is just that there are
> too many of them in one post!
>   
too many or too ambiguous....if pin point to a specific matter, you have 
higher chances to get the right answer ;)

Regards,
Bogdan


> Regards
> John
>
>
>   
>> -----Original Message-----
>> From: Bogdan-Andrei Iancu [mailto:[email protected]]
>> Sent: 07 July 2009 09:23
>> To: [email protected]
>> Cc: [email protected]
>> Subject: Re: [OpenSIPS-Users] Is opensips a front end to asterisk?
>>
>> Hi John,
>>
>> Actually you can run OpenSIPS from behind a NAT. You can instruct it
>> what IP and port to advertise to the outer world via advertised_address
>> and advertised_port core parameters:
>>        http://www.opensips.org/Resources/DocsCoreFcn15#toc24
>>        http://www.opensips.org/Resources/DocsCoreFcn15#toc25
>>
>> Regards,
>> Bogdan
>>
>> John Quick wrote:
>>     
>>>> Date: Fri, 3 Jul 2009 10:02:42 -0500
>>>> From: "[email protected]" <[email protected]>
>>>> Subject: Re: [OpenSIPS-Users] Is opensips a front end to asterisk?
>>>> To: users <[email protected]>
>>>> Message-ID: <20097310242.197...@leena>
>>>> Content-Type: text/plain; charset="us-ascii"
>>>>
>>>>
>>>>         
>>>>> I recommend that you don't try to run OpenSIPS on a NAT'd server. I tried
>>>>> recently and have been
>>>>> regretting it ever since. It is not designed to be behind NAT, although it
>>>>> is great for handling UA's that are.
>>>>>
>>>>>           
>>>> Bit confused about this. Our asterisk machines have always been behind a 
>>>> firewall and on NAT
>>>>         
>> IPs.
>>     
>>>> My thought was to use opensips at it's own location, sending the traffic 
>>>> to at least two
>>>>         
>> separate
>>     
>>>> locations for load balancing and redundancy. I'm not sure how I could 
>>>> avoid using NAT?
>>>>
>>>>         
>>> Asterisk works fine behind NAT, but OpenSIPS does not. Asterisk has a 
>>> parameter, externip, you
>>>       
>> can set
>>     
>>> that tells it what its external IP address. I am not aware of an equivalent 
>>> in OpenSIPS. You
>>>       
>> would
>>     
>>> avoid NAT by having multiple static IP addresses assigned to a DMZ or even 
>>> directly connecting
>>>       
>> the
>>     
>>> OpenSIPS server to the Internet and using iptables to block unwanted 
>>> connections.
>>>
>>> I'd be interested to hear from other users/developers of OpenSIPS on this 
>>> subject.
>>>
>>> John
>>>
>>>
>>>
>>> _______________________________________________
>>> 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