On Tue, 17 Nov 2009 12:47:46 -0500, Tony Graziano wrote: > When I did this from outside of your network to the public IP it worked, as > in, port 80 redirected me to 8443 and loaded the login screen.
No one else has been able to get that screen. Going to the IP did it uh? >As long as both ports are forwarded from your public IP to sipx, it will work. >Remember you have to have the NAT rule as well as the matching firewall rule >in order for the traffic to pass. Yes, things should be fine on the firewall. I've not changed anything that I can think of other than disabling the port 80/8443 and now enabling to test. On the NAT, port forward settings, I do have; WAN TCP 80 (HTTP) 192.168.10.70 (ext.: xxx.xxx.xxx.35) 80 (HTTP) http to sipx WAN TCP 8443 192.168.10.70 (ext.: xxx.xxx.xxx.35) 8443 And in the Rules; TCP * * 192.168.10.70 80 (HTTP) * NAT http to sipx TCP * * 192.168.10.70 8443 * NAT https redirect to sipx I did have these disabled for a while and just re enabled them. > Internally sipx sees the request on port 80 and changes it to 8443 and the > url forwards to https://sipx:8443/sipxconfig/app. Right, and this is what is not happening. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
