Nevermind, I just realized I haven't tried putting the phones on 10.1.10.0/24 yet.
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, July 02, 2012 10:14 PM To: [email protected] Subject: [sipx-users] recommendations for multiple phones behind nat When requesting a static IP from Comcast they force you use their CPE, a SMC modem/router combo, and then they provision the static with RIPv2. This leaves you with two usuable IPs when you request one IP; one static that is bridged through, the other is the gateway IP in which clients behind the SMC NAT would go out. I've set up sipxecs on the static IP only (multihome attempt was a failure) and phones are behind the NAT like so : WAN (gateway IP) -> SMC -> 10.1.10.0/24 -> Firewall -> 192.168.1.0/24 clients and phones WAN (public static IP) -> SMC -> sipxecs w/public static ip I initially tried using the SMC's 10.1.10.0/24 NAT address space/firewall for clients but discovered quickly that I need to be able to set clients to 192.168.1.0/24 because of hard coded IPs inside their software/databases. For some reason the SMC just wouldn't let me set that address space and I can't change the hard coded IPs without major surgery. Anyway, I'm seeing the two phones (Polycom 321's with 3.2.7 firmware and 4.2.1 bootrom) successfully register and then "freeze" right after loading sip.ld. They become completely unresponsive and the only thing I can do at that point is hard power cycle them. Do I need to set up another sipxecs behind the NAT as a branch, or should both phones be able to stay registered with this setup using TCPPreferred transport? The firewall is just a linux box with iptables masquerading like so : iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth0 -j MASQUERADE I've also tried using netfilter/conntrack and setting it to watch TCP, UDP, and RDP. Thanks, Matt
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
