SER can be put inside the private network, but you will have to configure your NAT to forward all the SIP traffic (port 5060) to the machine running SER.
In addition to that you would have to forward some port numbers for media to phones behind the NAT, for example 8000 -> IP of phone1, 8002 -> IP of phone 2, and so on.
Configuring ser for such operation is not easy, you would have to rewrite the contents of SIP messages.
In conclusion, it can be done, but it is not trivial. Run SER in the public internet if you can.
Jan.
On 29-01 00:36, Edson Gellert Schubert wrote:
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.
#============================= f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers