this is what we said from the beginning... ipsec (pfsense) and add that ip subnet to intranet with sipx so the media flows over the vpn.
vpn and host use the other end. we do that all the time. it doesnt matter if you are trying to use the gateway, or sipx. it's the same "network" as private, but routed. with an ipsec connection your two networks can't overlap. you'll also want to create a route at each end to the network it already has, so dns lookups from the remote phones can resolve through the sipx host. it also means tftp will work for phone provisioning if you configure the tftp server in the remote firewall dhcp settings. it's all very slick and works well. On Wed, Sep 14, 2011 at 2:26 PM, [email protected] <[email protected]> wrote: > On Wed, 14 Sep 2011 11:16:44 -0700, Todd Hodgen wrote: >> Setup an IPSEC tunnel between the two locations - you should have all of the >> sipXecs features. Except 911 calls dispatching to the right location. Put >> in a local FXO gateway for that. > > Cool, local VPN after all! Yet another possible solution. > > Thanks very much. > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet faxservices! _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
