Tweet
If you were going to build a rock solid 5 site system, what would you include. Average of 20 extensions per site, all connected through MPLS.
Let's hear some ideas!!
Charles
Let's hear some ideas!!
Charles
-
-
Originally posted by Charles
Any analog at the remote sites? Voicemail important at the remotes? -
Hypothetical...what would you do? Double -take on the server? DVM's at all sites. What would be the 'perfect build'?Comment
-
We've done Doubletake, it's not quite as nice as you'd like it. I'd do the following:Originally posted by Charles
HQ -
2 Shoregear 50 Switches (little extra capacity and, more importantly, so you have two master configuration switches in the system)
Main HQ server (backed up via doubletake or an equivlant product)
PRIs for voice connectivity
Remote sites --
1 SG 50 switch (new switches for the memory expansion slot on the side that can be later used for vm, eliminating the DVM)
DVM (not the bundle since we are doing the perfect world... Would be a real server)
I would centralize trunking and do backup POTS at the remote sites with the exception of one of the sites would have a PRI that the other sites could fail over to in the event HQ PRI's are unavailable. You can also do diaster routing at the carrier level to fail over numbers if needed. If money really was no object, you could do partial PRIs at the remote locations.
Network --
I would run Foundry on the LAN and VLAN the voice traffic. I'd run Juniper J-Series routers on the WAN with a fully meshed IP VPN solution from Time Warner Telecom.
Now that being said, the DVMs don't quite work as well as they should
- Once the new release comes up that opens up the memory slot on the new switches, i'd elminate the DVM servers.
Comment
-
Which release is suppose to free up a memory slot on the switches... 7.0?
Never mind... 7.0 is correct because the SG 50 switches are associated with 7.0 Duhhh!!!Last edited by luckycharms; 05-22-2007, 02:16 PM.-LCComment
-
Originally posted by luckycharms
No clue...Comment
Comment