[Serusers] SER + Proxy + NAT

[Edson Gellert Schubert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I thing that I didn't put myself very clear... Let me try an ASCII-Diagram... ;)

    UA1 ---- public IP ---- Internet ------ ADSL/GW ------ UA2
 (Win Mes)   (dialup)        |   |         (IPTables)  (Win Mes)
                             |   |
                       /-----/   \-----------\
                       |                     |
                    Router(NAT)           ADSL/Win (Windows)
                       |                     |
       UA3 ------------+                     |
    (Win Mes)          |                    UA4 (Win Mes)
                      SER


What I'm looking for is a Proxy to put in the ROUTER-Machine (could be a Linux/IPTables, FreeBSD, etc):

I undestand what Jan explain, about the complications, and that's why I was asking about an "inteligent" Proxy to handle SIP traffic.

Suppose that UA3 wants to talk with UA2 (were the ADSL/GW should have SIProxd installed). The communications flow would be UA3-SER-Router-Internet-ADSL/GW-UA2. Ok, in the Router appears the first challenge (how to transverse the NAT, keeping track from the flow?). Here comes the SIP-Proxy in action. It recieves the packet from SER, make desired changes and forward it through "Internet" to ADSL/GW. There, the SIProxyd recieves the packet, apply the related changes and forward it to UA2. Great. Is what we want. 

The reverse, that is, when UA2 (or UA1, or UA4) wants to talk with UA3 becomes the great challenge. How should the Proxy, in Router, knows where to send the packets that arrive from Internet? To SER? Directly to UA3? It's hard to make the decision.

The Proxy had to have many from a SIP-Server functionalities. It has to maintain flows tables with users-ID, ports and servers IP used in each communication flow (other infos could help in other tasks, but I thing that these one are the minimum), so that it could decide to whom send each packet from each flow.

So, do I make my doubts/points clear to You? If my understand is wrong, sorry and please correct me where necessary.

Edson.

P.S.: In my scenario there is no SER-2-SER communications, but another problem would be having two (or more) sites like the "Router" one. How to make than communicate each other through NAT GW/FW?



- ----- Original Message ----- 
From: "Adrian Georgescu" <ag at ag-projects.com>
To: <serusers at lists.iptel.org>
Sent: Thursday, January 29, 2004 8:00 AM
Subject: [Serusers] SER + Proxy + NAT


> Edson,
> 
> Putting a NAT traversal solution behing NAT is a chicken and eg 
> problem, isn't it?
> 
> --
> Adrian
> 
> 
> 
> Hi all...
> 
> I look through the list's archives, but an not finding info to help me.
> 
> The goal is use SER but not instaled in the GW/FW (it's not an 
> acceptable
> option, well it's acceptable, but not for now). So I'm trying to put 
> the SER
> in the Internal LAN (it could be installed in a DMZ also). So the 
> question
> is if there is any proxy that could be putted on the GW/FW to handle
> incomming calls (INVITEs) and forward it correctly to the SER machine 
> taken
> over the NAT issues?
> 
> I already look at SIProxd and RTProxy, but the first didn't forward
> incomming calls, and the second demands that it be instaled, with SER 
> on the
> GW/FW. I also am looking at SERMediaProxy (RTProxy alternative) but the
> documentations aren't sufficient detailed to answer my question. Any 
> help
> would be appreciated.
> 
> Edson.
> 
> 


- --------------------------------------------------------------------------------


> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQA/AwUBQBkkYDdMQB7Du1dpEQLGiQCfcjklZxwiAtG+rj+rKqCpKIORLA0AoOZF
oBf1QhqGvX67oZ14W127mCxl
=oB8Y
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040129/89171ec5/attachment.htm>