How to Carve a PBX

How to Carve a PBX

By Marty Parker June 24, 2014 12 Comments
Marty_Parker
How to Carve a PBX by Marty Parker

The vertically-integrated silo of the PBX is obsolete. A like-for-like replacement of any PBX – TDM or IP – should be challenged before making any investments. We saw this happen with mainframe computers several decades ago (See “Only the Paranoid Survive” by Andy Grove, Chairman Emeritus, Intel). Now it has happened with PBXs, the mainframes of voice communications. So, what would you buy instead?

A recent chat on this topic brought up the Thanksgiving image of carving up a turkey (e.g. this great Whole Foods YouTube). So, how about a post on "how to carve a PBX?"

Just like the turkey video, there will be some preparation. In our case, let’s assume that the enterprise already has an Instant Messaging (or an internal business social networking) system with access to the corporate directory, including the names and phone numbers of all the employees. This includes the mobile device clients for the IM systems, such as for Microsoft Lync, Salesforce.com Chatter, IBM Sametime or Connections, etc. We will assume that your enterprise has some experience with Session Border Controllers (SBCs), which will certainly be the case if you have SIP trunks, and/or smart gateways to support Voice over IP (VoIP) connections to the public networks. Also, just as the video recommends using a sharp knife, PBX carving needs a sharp mind for IT architecture and economics.

OK, let’s begin carving.

Step 1: Take off anything that doesn’t need telephony features. This will include almost all of those things that are now on analog lines or on IP-based Analog Telephone Adapters (ATA); examples include fax machines, door alarms, refrigeration alarms, ATM machines, parking lot phones, etc. There is no reason to be paying for PBX ports, licenses and maintenance on these devices, most of which don’t even have a dial pad and many of which never receive a call or use any of the PBX features (ever seen a Fax machine on hold or in a conference call or a pickup group?). You can remove these from your PBX and connect them directly to analog ports on a gateway or session border controller for a much lower cost. Or, move them to a very low cost open source switch such as Asterisk software. (Note: Cisco’s UCL Essential license, with a license list price of only $40, may provide an exception to this, but most customers are still licensing these analog device ports at the same price as a user phone line.)

Step 2: Remove the mobile, field and remote workers from the PBX. For most companies in most industries roughly 30% of the workers are field workers or workers who do not need a PBX phone number. The enterprise is usually either buying or reimbursing for the user’s mobile device, which is increasingly the case with the overwhelming BYOD trend. What’s more, all of the leading US cellular carriers are now offering unlimited voice minute plans, so there are no savings and likely some added costs from routing the mobile calls through the PBX.

If you still want the remote employees to have an enterprise direct inward dial (DID) number on their business cards, those DID numbers can land on the directory-enabled SBCs or gateways and be routed back out to the cellular user’s phone. Or, the DID provider may allow a permanent redirect of individual DID numbers while the call is still in the network. The cellular user can set their phone to route unanswered calls to the enterprise’s voice mail or unified messaging system (a PBX phone line is not required for each mailbox). The mobile users will be able to make calls from their smartphones using their e-mail contact lists and their IM contact lists, with no need to dial manually and no need to install a PBX-based mobile client on the device. If the remote users want a nice speakerphone or handset when they are in the office, they can use the attractive and economical Bluetooth docking stations, rather than an expensive PBX phone line.

We’re halfway done and your PBX is probably about 50% smaller.

Step 3: Move the in-house collaborative roles to a communications-enabled collaboration system. This includes roles such as R&D, business planning, product management and marketing, legal department, and often most of the enterprise leadership. These people communicate almost entirely in the context of documents and information, so move their communications to their document environment. Microsoft Lync with Office, IBM Sametime or Connections with IBM Docs, and Google Apps are all examples of this. Since these employees are working on a PC (Windows or Mac) or tablet (Windows, Mac, Android), they will likely feel comfortable using a wired or wireless headset and the built-in cameras for their voice and video communications. Note that this approach to collaboration starts from the documents and workflows, not from the voice or video calls that most IP PBX providers position as the basis for collaboration, though most IP PBX providers do have plug-ins to connect their communications to Microsoft Office and/or Google Apps.

Step 4: Audit and remove phone lines/numbers that are only there for voice mail routing to employee mailboxes. Many roles in retail, transportation, manufacturing and distribution operations, financial services, local government, and education do not need a dedicated PBX line. These roles do need to receive voice mail while at work and need to return calls and make other calls when on their breaks (if they are not using their own cell phones for these purposes), so provide plenty of telephones in the break rooms and provide each employee with a voice mailbox; but a DID number will not be needed if the voice mail system prompts the caller for a spoken name or a mailbox number.

We’re almost done. At this point the PBX should be supporting primarily call center agents, desk-based workers (who are likely using application software for most of their work), operator or receptionist positions, and some number of open space phones (lobbies, cafeterias, safety phones, etc.). So the final actions are:

Step 5: Cut out the phones for desk-based or device-based business application users that weren’t removed in Steps 2 and 3. The new model is to embed communications directly into the business applications whether on PCs/Macs, tablets or smartphones (often called CEBP or Communications Enabled Business Processes). Increasingly, the business applications suppliers are already including communications features in their software and their user interfaces and are providing APIs or standards-based modules for connection to gateways, to the telephone network/PBXs, to directories, and to IM systems. Users will often prefer wired or wireless headsets and USB or Bluetooth appliances rather than desk phones, since that’s what they already use in this BYOD world.

Step 6: Clean up the maintenance contracts. You can now save money year after year by downsizing the maintenance contract to cover only those user licenses that are still needed. The PBX vendor will sternly warn you that if you remove the licenses from maintenance you can’t get them back without buying new user licenses; but you know you won’t need the licenses that have been carved off so go ahead – cancel them and reduce your maintenance costs.

Step 7: Garnish this platter-full of cost savings with some treats and goodies. The turkey-carving video showed garnishes of fresh herbs. But in our case, maybe the garnish is to add some enhanced video or BYOD options, to refresh the mobile device reimbursement policies, or to provide a menu of PC and device appliances such as headsets and speakerphones.

If or when you ever decide to replace this much smaller PBX, you will save significantly by buying only what you need for the future, not what you had in the past.

If you serve this action plan up to your CIO and CFO, they will most likely savor the experience much more than a Thanksgiving dinner.

Of course, you may have your own way to do this. Some may even prefer Turducken, i.e. stuffing the turkey with lots of other things, analogous to stuffing the PBX licenses with UC components such as video conferencing bridges. But the disaggregation of the PBX is a pretty certain future, so best to get the sharp minds together now and start carving. Enjoy!

 

12 Responses to "How to Carve a PBX" - Add Yours

Gravatar
Art Rosenberg 6/24/2014 5:52:29 PM

Wow!

Great thoughts for moving forward without the "tyranny of telephony!"
Gravatar
Barb Grothe 6/25/2014 5:05:23 AM

Excellent Marty! One of your best articles, and there have been many that I have enjoyed reading over the years. Thank you.
Gravatar
Jon Arnold 6/25/2014 5:27:54 AM

Nicely done, Marty! I'll bet you have a reprise post planned for Thanksgiving, maybe for carving up the physical network itself.
Gravatar
Alan Percy 6/25/2014 10:42:37 AM

This article does reflect what we've seen at a number of customers - not always in that order, but the same basic "uncoupling" from their legacy infrastructure. The key is that each step is done on their timeframe and comfort level with the new technology.

One interesting addition is the mobile redirect - for those employees that primarily are OOO (out of the office), giving them a DID that forward to their mobile is a nice tool. However, the return call usually exposes the recipient's mobile number, which some would prefer to avoid. That's where the power of the various UC platforms surfaces.

Nice work!
Gravatar
Marty Parker 6/25/2014 5:48:08 PM

Thanks, Alan, for the confirmation that this can and is being done.

Also, if the OOO user (or their employer) does not want to expose their mobile number, it is easy for them to self-administer this via the cellular carrier's web site or help desk. So, that's still not a reason to have PBX lines or UC voice accounts for the mobile users.
Gravatar
Peter Huboi 6/26/2014 4:09:49 PM

I'd suggest doing step 3 before step 2. If, for example you decide to "voice enable Lync" as many are now doing, this could impact the number of employees that you remove DID phone numbers for and expect them to use their mobile devices (and we assume the company is paying the monthly cellphone bill in these cases, correct?). Also, in step 2, while it makes a lot of sense for sales to just use their mobile phone all the time, not every "field worker" would like to have their phone number exposed to be reachable 24 hours per day, so retaining DID lines is probably a good idea for many employees.

Also, in step 3, many will still like the choice of using a handset or speakerphone rather than always wearing a headset. A USB phone like the Polycom CX300 (Lync Qualified, plug and play) gives users the choice of using handset, speakerphone, or headset (through headset jack on the USB phone, headset not included). An actual phone registered to Lync also can add some benefit for executives, managers and admins. So it's good to look through the features list. Feature like shared line appearance (Boss/Admin), call park, intercom, and more may be better served with a phone registered to Lync that using a Lync client alone. What we are seeing a lot of (at Polycom) is customers doing a small Lync voice trial while they still have the PBX or IP PBX to get a better idea how it will all work before they make the larger jump to voice enabling Lync throughout the company.

Overall, I think your article has the IT/Communications team asking the right questions. An excellent starting point for any company who's lease agreement is a year away from renewal or who's PBX/IP PBX investment is already fully depreciated.
Gravatar
Fabrizio Capone 6/27/2014 2:57:15 AM

Great article!!! I totally agree and I think this can be a good advice for the Customers to start thinking about their path toward the Cloud Communications.
Gravatar
Marty Parker 6/27/2014 12:15:07 PM

Thanks, Peter, for your thoughtful comments.

As suggested to Alan (you may not have seen that post when you wrote), it is easy for a mobile worker to block their cell number visibility. No need for a PBX or Lync client for that purpose.

Also, for personal preferences of speakerphones and handsets, there are many choices, such as the Polycom VoiceStation 500 (since you're at Polycom), which pairs with my mobile phone when I'm in the office. But, sure, some people and enterprises may want to keep the PBX or UC phone lines for this reason.

The call coverage features are also important, depending on the workflows. For example, our Law Firm clients probably would not get much benefit from Step 2 (all-mobile workers), while our Manufacturing, Distribution and Transportation clients would have a lot of users in all-mobile usage profiles.

Glad you agree that these are important questions and planning steps, and sure it's fine to flip Steps 2 and 3, just so long as the all-mobile case is anticipated so as to avoid over-investment in step 3.

Thanks again, Peter.
Gravatar
Dave Michels 7/5/2014 4:10:19 PM

Very interesting. I do have a few concerns though.

Starting with Step 2. I do think it makes sense to use a corporate telno for inbound calls. Employees change jobs very frequently and it's problematic have kids, customers, partner,s and bosses all calling the same number - esp at a new job. Your solution is a gateway forwarding service. This masquerade works fine for incoming calls, but not outbound calls. Once the cat gets out of the bag, people start calling personal numbers again - did you have a suggestion to mitigate this?

Regarding Step 4: Voice mail is a reasonably effective and inexpensive solution for on the go mobile workers. I find that desktop workers prefer Unified Messaging, but on the go workers prefer voice messaging. Do you think voice mail - sans PBX - makes sense? Have you seen customers implement a T1 or SIP trunks directly into a stand alone messaging server?

Regarding Step 5: This seems more theoretical than practical because there are so many different types of knowledge workers at a given firm. Some use CRM, some are in accounting apps, some are in manufacturing, others in logistics apps, etc. Not to mention many knowledge workers work with other knowledge workers in other organizations and countries. The phone is universal - connects to everyone, without training. Thoughts on this?
Gravatar
Roland Rivera 7/9/2014 10:22:19 AM

Nice article Marty. For your step 1, we’ve found that there are operational issues to address such as how to effectively manage ATAs for a large enterprise of 30,000 lines that includes 3000-4000 analog lines. There is also the potential added complexity of the dial plan as you split numbers between the PBX and the local gateways. If the dial plan is not split, we would expect to see an increase in trunking license costs to connect the gateways to the SIP core. Additionally, there are added security issues to address for the increased number of gateways. Finally, while there is a decrease in PBX license costs, we have encountered increased expenses for the acquisition and maintenance of the additional ATAs and gateways. Ultimately, the recommendation is definitely doable once we address the operational issues for a large enterprise.

Thanks again

-Roland
Gravatar
Marty Parker 7/16/2014 3:51:13 PM

Thanks, Dave and Roland, for your review and suggestions on the Steps. Great points.

Here are quick responses to each of them:

Step 1: For this step it may not be necessary to use ATAs. Rather just use the existing twisted pair cable plant and use cards in the gateway to do the conversion between analog and IP. The dial plan can be managed in a master directory (AD, LDAP, or a even a Session Manager) and synched to the directory-enabled gateway, so the administration workload need not increase and may even decrease. If the gateway is installed on the SBCs (which is possible with Sonus, AudioCodes and similar gateways), then there would be no change to the 'SIP core.'

Step 2: Yes, use a corporate tel. no. for the incoming calls, routed to the mobile device; users can self-administer to block their outgoing mobile number, if they wish, so the customers will not call them back at that number. Family and friends will still know the number, from their contacts, and may start with SMS anyway.

Step 4: Yes, voice mail is an important part of the solution. All of the leading, standalone voice mail (and UM) systems, such as AVST or ESNA, can do this without requiring a PBX line. Can prompt the caller via spoken name or can take the DID info passed by the gateway to route caller to user's greeting, mailbox and other features.

Step 5: Yes, this is not one clean motion. Would proceed on an application by application basis. But since large blocks of users (Usage Profiles, employee roles) are using a specific application, it is very feasible to move entire groups based on their primary business app. Since the directory-enabled gateway/SBC can route calls to/from other employees and to/from PSTN, shouldn't impair any functionality for the user.

Thanks for the commentary, Dave and Roland. Helps make this more clear and usable.
Gravatar
Bhuvanesh US 10/3/2014 2:26:55 AM

Great Article

To Leave a Comment, Please Login or Register

CLP Central: Where Consultants, Vendors, and the Channel Connect
BC Summit 2016 UC Alerts
UC Blogs
UC ROI Tool RSS Feeds

Related UC Vendors

See all UC Vendors»