HOW TO CORRECTLY DEPLOY A VoIP PHONE SYSTEM
A white paper by Pierre Kerbage
VP of Sales & Marketing for Zultys, Inc.
VoIP phone systems today vary greatly in features, size, type of phone lines they can operate with, wiring they use, and phones (stations) that they use. Voice Over Internet Protocol (VoIP) has evolved greatly in the past decade. One thing that has not changed however are the fundamentals of VoIP Systems, how they operate, and what they need in order for them to work reliably.
For starters, many VoIP Phone systems (PBX) do not rely solely on VoIP phone lines. What re VoIP Phone Lines ? While there are proprietary VoIP lines, in general, what is used today is called SIP (Session Initiated Protocol). VoIP/SIP is simply the ability to carry your voice conversations over a data trunk (such as a data T1, Cable Modem, DSL, etc…). It is very unusual today to see VoIP phone systems only accepting SIP/VoIP Trunks (a trunk is a phone line). In fact, the vast majority of VoIP Phone systems today continue to operate on standard Analog Trunks (the same type of lines that you have in your house) and/or PRI (Primary Rate Interface) which is carrier grade 23 phone lines. Why would a VoIP Phone system connect to Analog Trunks or PRI ? There could be many reasons for that. For one, clients may already have existing contracts on those trunks and they cannot change. The other reason is that they are comfortable in that technology and it has served them well. So why and when do SIP / VoIP trunks come to play ?
SIP trunks are now sold for as low as $5 per month per Trunk (+utilization) to $40 per trunk ("all you can eat") which includes an unlimited Long Distance Plan (in the US typically) and Overseas rates extremely compelling (i.e. 1.1 cents per minute to some Western European countries). Some phone systems (i.e. ZULTYS) allow you to have a variety of trunks and use them in the most appropriate way. For example, a company might still like to connect using Analog Trunks for most of their inbound or outbound calls (or a PRI or two), except when placing Long Distance calls. LD calls in this case, would exit/use the SIP trunk, therefore saving the consumer long distance fees, and arriving to a more predictable monthly fee. This is called LEAST COST ROUTING. This can vastly decrease cost of operations (often to the point where the phone system can pay for itself in a very short amount of time, depending on the long distance the company normally uses.
So what about SIP/ VoIP ? Is it dependable ? How does it sound?
There is a right way and a wrong way to deploy SIP and unfortunately, most of the time, consumers are unclear about the choices they have or what to do and are unfamiliar with technologies that are available to them. Here is what to keep in mind. Each SIP conversation requires about 84Kb (Kilobit) in data to function correctly (without compression). Compression can sometimes be used or turned on to reduce the voice/data utilization and optimize networks, but the more you compress the sound, the worse it sounds. Different vendors have developed different compression techniques to get the most out of your bandwidth. One thing for sure, IN VoIP, YOU GET WHAT YOU PAY FOR !!!! Different providers might give you different SLAs (Service Level Agreements). Be sure to read them and understand your terms and conditions.
Here is how to roll out VoIP in your Enterprise CORRECTLY:
10. Insist on DEDICATED BANDWIDTH FOR YOUR SIP TRUNKS - shared bandwidth (BYOB - bring your own bandwidth) IS A RECIPE FOR FAILURE NO MATTER WHAT THE PROVIDER TELLS YOU.
11. Insist on QoS Routers end to end - meaning the provider has a QoS router(s) on their end.
12. It is NOT enough to put a QoS Router on your end, because if that is only what you do, you would have NO control over that packet when it leaves your Network (how do you QoS the Internet ????)
You would think that all of the above would cost a fortune. But in reality , they do not. These are BASIC items that ANY good network infrastructure today SHOULD have. Whether you use VoIP or not.
The Top 2 mistakes that we see CONSISTENTLY with consumers that have problems with their VoIP trunks are: BYOB (Bring your own Bandwidth) - where the provider promises great service over your existing DSL, T1 or Cable. What happens if someone on your Network starts to Email a large file ? Or is infected by a virus/Trojan ? Again, insist on dedicating the proper bandwidth to your SIP trunks and if you can separate them from your data, QoS the Network and QoS the Router end to end (to your Provider)
Now - let's talk about the Tele-worker (Remote workers that need to connect to the VoIP System at the office). By distributing its work force nationwide, companies are far less seriously impacted by regional weather conditions, and can secure better ongoing coverage and support for their customer base
While bandwidth in the US has seriously improved in the past few years, internet in homes (or businesses) using Cable and DSL are UNPREDICTABLE at best. Some services SHARE your bandwidth with the rest of the consumers/businesses on the block. Some have good download speeds but horrible upload speeds. Remember that you need 84KB per conversation no matter what. So what happens when you are talking on the phone and sending out Emails ? The sound packet might get distorted. How do you improve on it? There is a reason why a T1 costs around $400 per month and Cable or DSL costs typically under $100 per month. T1 speeds give you a consistent 1.5 Megabits upload and download speeds (Symmetrical). Whereas Cable and DSL can be as low as 384Kb in some markets in upload speeds. And sometimes, upload speed is not just the only problem. Sometimes there is a LAG on the line (as it is the case with some Satellite providers). Wireless (802.11x) can also present a challenge for VoIP Consumers. So, for the Tele-worker, the best way to minimize (not eliminate) problems are:
IP Telephony has improved significantly in the past few years and R&D continues to develop new methods of minimizing problems. But consider also a failover mechanism. If your Internet fails at your house and that is your only phone, how will you place calls ? Be sure your mobile phone is available to you. Also, insure that your IP Phone is registering 911 calls to your HOUSE not to the office. (If you are connected to the office PBX and you dial 911 - you are essentially using one of the TRUNKS from your office - so the 911 truck will come to the office NOT to your house - unless there is a way for that PBX to indicate differently ). Be prepared for VoIP, and prepare your Network. At the end of the day, you will find that these steps outlined above will provide not only a more pleasurable VoIP experience, but also a better and more reliable and predictable DATA experience. Reliable networks, are no longer a luxury items. Businesses DEPEND on the Network. Spend the time and the money to improve your infrastructure, use a Managed IT Service provider that uses monitoring (such as Kaseya, or Level Platform or others similar to that) to look at your Network 24x7 and provide proactive steps to improve it.
Video conferencing is quickly becoming one of the most important communication channels for both small and big businesses. As more businesses turn to this technology, expectations about the experience are also rising. It’s not enough to just offer video conferencing as a communication method. You also need to meet minimum audio and visual standards, and there’s even proper etiquette to consider. more
Choosing the perfect phone system for your business is no small task …. Depending on the size of your company, the industry in which you work, and the specific needs your phone system will be required to meet, any number of solutions could get the job done. more
Reducing expenses is one of the main reasons that businesses switch from traditional office phone systems to VoIP technology. But many people rush this decision and end up spending more than they need to. The costs of implementing a new VoIP system can increase quickly, especially if you don’t strategically plan for it ahead of time. more