You could build some redundancy into your network via a second connection to your main location. How about low cost DSL circuits, with VPN between the different routers. When you have a T-1 failure, you would have some re-route scenarios to limp by.
I suspect having one email platform is probably critical to your integration efforts. By having one Core network, and some diversity planning between that location and the rest of your network, you will achieve one large PBX network, with one integrated VM platform, one Auto Attendant, etc. From: [email protected] [mailto:[email protected]] On Behalf Of Michael Picher Sent: Sunday, October 23, 2011 4:43 AM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] HA or a 2nd server at remote location? Audiocodes has Stand Alone Survivability in their gateways. SAS works for 25 users in the MP series gateways and is a licensed feature in the Mediant gateways. Hint, you can put two MP series gateways at 1 remote if you have more than 25 users. This allows users to still call each other, dial out and inbound calls can be routed to particular extensions. Mike On Sat, Oct 22, 2011 at 11:10 PM, Nathaniel Watkins <[email protected]> wrote: Until now, I've only ever had a single sipXecs server that handles all the phones at various locations (all routable directly on our network). I have a remote site that has a point to point T1 circuit to our main location. We've been having issues for the past week with the T1 going down. The phone company has been giving me the run around, so I'm looking at some 'easy/smart/cheap' fixes. I have 2 pots lines at the remote site (1 is a fax line - and 1 is a line we left out there in the event of an outage). Currently, when the T1 is down, I have the calls forwarded to those 'backup' lines - and they are answering calls on different phones. What is the recommended way to provide them with a reliable backup solution (a totally separate sipXecs install with dial rules to route between locations and shared gateways | or | setting up an HA server at that location). I've not played with an HA solution - but it would be nice if I wouldn't have to manage several different servers if possible. I'd also want the 'main server' to handle registrations unless it was unreachable - then it would fall back to the other server. Moving forward, I'd like to implement a similar solution at another of our locations with a p2p T1. Remote 'A' has 10 phones, Remote 'B' has 50 phones. Recommendations/Suggestions? Nathaniel Watkins IT Director Garrett County Government 203 South 4th Street, Room 210 Oakland, MD 21550 Telephone: 301-334-5001 Fax: 301-334-5021 E-mail: [email protected] _____ This message and any files transmitted with it are intended only for the individual(s) or entity named. If you are not the intended individual(s) or entity named you are hereby notified that any disclosure, copying, distribution or reliance upon its contents is strictly prohibited. If you have received this in error, please notify the sender, delete the original, and destroy all copies. Email transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Garrett County Government therefore does not accept any liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Garrett County Government, 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 www.garrettcounty.org _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square Suite 201 Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
