Re: [Siproxd-users] Remote NAT Traversal

[Thomas R. <tr...@gm...>]

Hi Alejandro,

You did not hear from me because currently I'm quite busy at work
and lacking spare time (well... beside having fun, we all need to
earn some money for living, don't we?).

Ok, thanks for your short description about the remote NAT issue.
I've got a slight idea of the concept, however I still need to take a
deeper look into the draft of the TURN protocol to understant what
it is all about.

With my current knowledge, I have to answer 'no' to your initial
question (siproxd solution for remote NAT traversal). Siproxd must
be running on the firewall host itself as an application proxy.

I hope I could help with this answer.

Best regards,

/Thomas


On 18 Mar, Alejandro Olchik wrote:
> Thomas,
> As I haven't heard from you I'm forwarding this
> email directly to your email address.
> 
> Let me know your thoughts,
> Best regards,
> Alejandro
> 
> -------- Original Message --------
> Subject: Re: [Siproxd-users] Remote NAT Traversal
> From: "Alejandro Olchik" <ao...@te...>
> Date: Fri, March 14, 2003 10:59 am
> To: <sip...@li...>
> 
> 
> Some companies, like Jasomi, implement
> NAT Relay Agents. They work like SIP Proxies but
> make sure all signaling and RTP goes through then
> allowing enpoints behing NAT router to initiate
> or terminate calls withouth using any other NAT
> traversal mechanism (STUN, uPNP or an ALG).
> 
> J.Rosenberg wrote a draft for a protocol called
> TURN (Traversal Using Relay NAT -
> draft-rosenberg-midcon-turn). The NAT Relay
> agent is very similiar to that but is transparent
> to end enpoint (endpoints don't need to explicitly
> allocate ports at the TURN server).
> 
> The advantage of such a solution is that you don't
> need a siproxd running on each of the network edges.
> 
> Alejandro
> 
>> Hello Alejandro
>>
>> I'm not aware of a technique called 'remote NAT traversal'. Could you
>> describe more in detail what exactly you do mean by that?
>> What is the situation you have and what would you like to do?
>>
>> The main purpose of Siproxd is to enable SIP user agents that are
>> 'hidden' behind a masquerading firewall (e.g. in a private IP range)
>> to call and be called to/from the internet.
>>
>> /Thomas
>> Maintainer of Siproxd
>>
>>
>> On 13 Mar, Alejandro Olchik wrote:
>>>
>>> I was trying to figure out if the siproxd can be
>>> used as a solution for remote NAT traversal.
>>>
>>> Thanks,
>>> Alejandro Olchik
>>>


-- 
GnuPG Public Key:
pub  1024D/87BCDC94 2000-03-19 Thomas Ries <tr...@gm...>
uid                            Thomas Ries <tho...@gm...>
Key fingerprint = 13D1 19F5 77D0 4CEC 8D3F  A24E 09FC C18A 87BC DC94