If memory serves me correct it might be your routing. My config was that sipx would use the pfsense box as its default gateway.
I also tried from the outside when you originally did this and port 80 was redirected to 8443. So I think it is either an internal route or a proxy config that you might be using inside. On Tue, Nov 17, 2009 at 12:29 PM, [email protected] <[email protected]>wrote: > Bit stumped here. > Using Tony's pfsense config file, sip/rtp traffic gets in just fine but > 80/8443 does not. > > I think it's a sipx setting and not pfsense because I also tried giving > remote access to > sipx over my main firewall and sipx never wants to reply to anything > outside of the lan. > > I've been looking for ideas on what might be causing this since yesterday > and can't find > anything that makes sense. I'm sure it's something tiny I'm overlooking but > I'm befuddled > at this point. > > Any input would be most appreciated. > > Mike > > > _______________________________________________ > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/
_______________________________________________ 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/
