When Nortel went bankrupt in 2009, we were faced with a phone system that was at its end of life, expensive to maintain, impossible to upgrade and lacking in advanced features like unified messaging, find me-follow me, voicemail to email and built in multi-party conference rooms.
We contacted our long-time, trusted consultant Rick Pommet of Nelson Communications who introduced us to the Abacus virtual PBX. We went live with the Abacus system on December 7, 2010 and have been overwhelmingly satisfied with the service. As I said to Rick at the time, “if half of what you say is true, I want it”.
All call control, voice mail, conferencing and call center functionality reside on servers in a secure SunGard data center with full redundancy and geographic backup. We have no phone system equipment onsite except a secure gateway device installed between our site and the data center. All of the intelligence lives in the network and features are always on and accessible from any device – desk phone, smart phone, virtual extension, etc.
We selected Polycom high definition (wideband audio) phones because of their superior quality and the built-in speakerphone. Listening to a voice on a “high definition” phone is quite an experience. The Abacus service is compatible with all SIP compatible phones including Cisco and smart phones – iPad2, iPhone, Android, Blackberry. We can mix and match devices so we will never be locked in to a single proprietary vendor.
Our Blue Bell, PA and Richardson, TX offices are treated as one virtual PBX, so calls between offices are free “on net” calls. We share resources: call paths (sometimes called SIP trunks) and local, long distance minutes between the sites. Since our offices operate in two different time zones, we never max out on call paths because our respective busy hours are always 1hour apart. If we did exceed the number of call paths we subscribe to, we have a feature called “cloud bursting”, which automatically provisions more virtual circuits, but only when we need them.
A business continuity (disaster recovery) plan is “baked in” so if we lose internet connectivity or power, our auto attendant and voice mail is replicated in the proverbial cloud. Callers are automatically re-routed to cell phones, home numbers, remote offices, and the caller will never know that it’s not business as usual. If no one answers, the caller goes to voice mail and the recipient gets an email with a .wav file attachment to play back the message. We got a lot of snow last year in Blue Bell, PA so we purchased an extra Polycom phone with a sidecar so our receptionist can work from home on snow days. That keeps everyone happy.
Several of our sales representatives and implementation people work from home throughout the United States. This gives us the flexibility to hire local talent and recruit based on knowledge and skills rather than commuting distance from our corporate office. The virtual PBX platform makes the home workers an integrated part of the overall look and feel of our organization.
Was the transition problem free? No. We had a major cutover problem that resulted in seriously degraded voice quality calls in our satellite office. In our Blue Bell headquarters, we had diverse internet providers and were able to separate voice traffic from data traffic. Blue Bell went “live” without issue. We installed a 3.0 bonded T1 VPN between Blue Bell and Richardson. The plan was to share the bandwidth in Richardson between voice and data. In theory, there was plenty of bandwidth to go around. Our carrier improperly configured the circuit so 100% of the bandwidth was allocated to VPN traffic between our sites. This killed the VoIP calls. The problem took an inordinate amount of time to resolve because the carrier could not “see” any errors in their router. Abacus worked with our consultant and the carrier and the reports provided by our session border controller gateway, and convinced the carrier to “nail down” the bandwidth, i.e. allocate 1.5 Mbps to voice and 1.5 Mbps to data. This solved the problem temporarily but was not a permanent solution because we would never benefit from the full 3.0 Mbps we were promised on the data side. Long story short, we implemented “Plan B” and added a diverse internet carrier in our Richardson office and split off the voice from the data. Our consultant negotiated three months credit with our carrier for the mishap. And I learned more than I cared to know about bandwidth allocation.
We do a lot of conference calling, and now, every employee can have their own conference bridge and set up ad hoc conference calls on the fly. This service is integrated into our virtual PBX and we were able to transition from a 3rd party conference service that was more expensive. Everyone is happy with the call quality built into the network and the Polycom phones.
We’ve been told that IP Fax will be integrated into our virtual PBX this month. We’ll be comparing those costs to our 3rd party fax service down the road. One of the advantages to a hosted PBX is that as new features are added, they become available automatically to everyone on the network. There are no hardware upgrades, software updates, bug fixes, licenses, maintenance contracts, etc. to worry about.
Our new service meets our needs and our total monthly costs are less -not a bad deal in this economy.