We just finished a 14 site VoIP implementation, and I would love to give you some advise after learning from our experience.
send me an email:
tbritten *at* yahoo *dot* com
We Just Installed a enterprise VOIP Solution
on
Will VoIP Kill the PBX?
·
· Score: 2, Interesting
We used Avaya, and the main advantage, is while it is VoIP, the backplane of the PBX is good 'ol TDM. SO our sites can have a mix of digital, VoIP, and analog phones. Also if you currently have an avaya PBX, you can doa quick swap, and keep your TDM phones but do site-to-site with H.323 IP Trunks, and add VoIP phones as you go.
The management aspect of VoIP is often overlooked. While the new features, dial routing ability (route outside calls out the PRI of the closest office) are nice, there is alot of troubleshooting and M/A/C work that has to be done. Its more like managing network gear (switches, etc) then PCs/Servers. The system has meant more work, not less, because there is ZERO integration with our AD infrastructure. We have to add users and maintain users in like 4 different places now. Atleast Cisco's Call Manager is ActiveDirectory Integrated.
A system of automated switches with real-time network links could be used to disconnect parts of the grid instantly before the problem could spread.
That's exactly whats in place - but much simpler. Inbetween each power terriory is a couple interconnects that couple the grids together. They have switching relays similiar to the ones on the generators that monitor the power moving in or out of the territorry (in the case of ConEd NY, in) The nanosecond the power falls out of the acceptable tolorance for phase, voltage, or amperage, BOOM it drops the connection. Thats what SHOULD have happened today - when we lost power from the 5,000 MW lines from canada, it should have started to brown out the NY power pool, and the other pools should have broken off and kept their section of the grid up.
the problem is, really, our reliance on outside power sources in canda, and the huge power consumption by NYC - ConEd can't make even close to enough power to cover their load - imagine if the hippies got their way and closed indian point?
Slashdot Mirror
We just finished a 14 site VoIP implementation, and I would love to give you some advise after learning from our experience. send me an email: tbritten *at* yahoo *dot* com
We used Avaya, and the main advantage, is while it is VoIP, the backplane of the PBX is good 'ol TDM. SO our sites can have a mix of digital, VoIP, and analog phones. Also if you currently have an avaya PBX, you can doa quick swap, and keep your TDM phones but do site-to-site with H.323 IP Trunks, and add VoIP phones as you go. The management aspect of VoIP is often overlooked. While the new features, dial routing ability (route outside calls out the PRI of the closest office) are nice, there is alot of troubleshooting and M/A/C work that has to be done. Its more like managing network gear (switches, etc) then PCs/Servers. The system has meant more work, not less, because there is ZERO integration with our AD infrastructure. We have to add users and maintain users in like 4 different places now. Atleast Cisco's Call Manager is ActiveDirectory Integrated.
Get a 256MB CF card from them. They'll hit you for 800 Bucks, and its not even cisco-branded, its just a SMART.
PENN STATE! see ya at the skeller!