A hardware solution might also work out since this would not be for the majority of our users, just the few who are mobile.
Thanks for the input. Mike On Mon, 5 Oct 2009 16:17:25 -0400, Tony Graziano wrote: > We've always had good luck with Ingate and remote users. It's a tad more > expensive, but seems to work flawlessly for our needs. > > On Mon, Oct 5, 2009 at 3:50 PM, [email protected] <[email protected]> > wrote: >>> We haven't done any load or capacity testing. Regardless, your milage >>> will >>> vary depending on CPU and bandwidth. So far, no issues that I'm aware >>> of. >>> >> >> Days of testing show that remote users are going to be a support >> nightmare. >> I'm very interested in trying OpenVPN and wondering about one thing that >> I can't seem to find anything on. >> I would run this on it's own server, at minimum, dual XEON 2.8Ghz/4GB of >> memory. >> >> Are there any latency issues I should be aware of before trying this out? >> I'm thinking I would probably end up having to put such servers in >> between the router and SBC or would I instead be allowing users to >> connect directly to sipx at this point? >> >> Trying to get a clear picture of what I need to accomplish. >> >> 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/ _______________________________________________ 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/
