VoIP technology and cloud telephony

What is Cloud Telephony and Why is it Replacing Traditional Lines?

If you're still using analog lines or legacy PBX systems for your organization's communications, you're likely facing limitations such as high long-distance call costs, poor scalability, and dependence on physical hardware. Cloud Telephony, which works based on VoIP (Voice over IP) technology, completely changes this equation. In this model, voice calls are transmitted over the internet as data packets instead of the traditional PSTN network. The result? Lower costs, greater flexibility, and features you couldn't even imagine with conventional lines.

In this article, instead of clichéd definitions, we'll dive into practical matters: exactly how much bandwidth do you need? How do you ensure call quality? What are the most common mistakes made when migrating to cloud telephony? And finally, we'll provide a practical roadmap for a smooth transition.

The Real Advantages of Cloud Telephony Over Traditional Lines

Let's be honest: the benefits of cloud telephony aren't just about being "cheaper." If you're only looking for cost savings, maybe a used PBX system could do the job. But the main difference lies in the architecture and capabilities that traditional lines simply cannot offer.

Cost Reduction by Eliminating Physical Infrastructure

With traditional lines, you need one analog line for every 4 to 8 employees, and for expansion, you need new cabling. With cloud telephony, all you need is a stable internet connection and an IP phone (or even software on a laptop). Hardware maintenance, repair, and upgrade costs are also eliminated. For example, a 50-person organization making about 200 long-distance calls daily typically saves between 30% and 50% on their phone bill by eliminating call and maintenance costs.

Scalability Without Geographical Boundaries

In a traditional system, adding a new branch means purchasing hardware, installing lines, and spending weeks of time. With cloud telephony, a new employee in another city only needs internet and an IP phone device. You can create a new extension in minutes, connect it to an internal number, and manage call routing rules from a web dashboard. This means organizational growth without being tied to physical infrastructure.

Advanced Features That Traditional Lines Lack

• Automatic call recording: For call centers and sales teams, recording all calls with advanced search within conversation text.
• Smart IVR: A multi-level phone menu that guides callers to the appropriate department based on their needs.
• Real-time reporting: Number of missed calls, average wait time, performance of each operator.
• CRM integration: Pop-up display of customer information on incoming calls.
• Presence and status: See if colleagues are online and transfer calls with a single click.

Call Quality in Cloud Telephony: Why Do Some Calls "Cut In and Out"?

The biggest concern for IT managers about cloud telephony is voice quality. The truth is that VoIP call quality is directly dependent on your network quality. If calls suffer from latency, jitter, or packet loss, the audio will sound robotic or choppy. But the good news is that by following a few simple principles, you can achieve quality even better than traditional lines.

Bandwidth Requirements: The Exact Calculation Formula

To calculate required bandwidth, you need to know the codec being used. The most common codecs in cloud telephony are:

• G.711: Excellent quality, consuming about 87 kilobits per second (Kbps) per call.
• G.729: Good quality, consuming about 31 kilobits per second per call.
• Opus: Adaptive quality, consuming between 6 and 51 kilobits per second.

The simple formula is: Required bandwidth = (Number of concurrent calls) × (Codec consumption) × 1.3 (the 1.3 factor accounts for IP and Ethernet protocol overhead). For example, if you have 20 employees and expect a maximum of 10 concurrent calls, with the G.711 codec you need:

10 × 87 Kbps × 1.3 = 1131 Kbps ≈ 1.1 Mbps

So a dedicated 2 Mbps internet connection is sufficient for calls. But note: this number is only for VoIP. If you're simultaneously using the internet for web browsing, email, and video conferencing, you should at least triple the total bandwidth.

Solutions for Ensuring Call Quality (QoS)

The most important step is enabling QoS on your organizational router or firewall. With QoS, VoIP packets receive higher priority than web traffic. On MikroTik routers (which are very common in Iran), you can prioritize SIP and RTP traffic with the following commands:

/ip firewall mangle
add chain=prerouting protocol=udp dst-port=5060 action=change-mss new-mss=clamp-to-pmtu
add chain=forward protocol=udp dst-port=5060 action=mark-packet new-packet-mark=voip
add chain=forward protocol=udp dst-port=10000-20000 action=mark-packet new-packet-mark=voip

/queue simple
add name="voip-priority" packet-marks=voip priority=1/1 limit-at=2M/2M max-limit=10M/10M

Also, don't use wireless (Wi-Fi) connections for fixed IP phones. Always connect the phone to the switch with a network cable. If you must use Wi-Fi, make sure to use the 5GHz band and 802.11ac standard or higher.

Technical and Infrastructure Prerequisites for Setting Up Cloud Telephony

Before taking any action, you need to prepare your network infrastructure. In this section, we'll review a practical checklist.

Required Equipment

1. IP Phone: Popular models like Yealink T4x series or Grandstream GXP16xx. The cost per device ranges from 2 to 5 million Tomans.
2. VoIP Server or Cloud Service: You can use open-source software like Asterisk or FreePBX on a virtual server, or use managed cloud telephony services. Companies like ServerNet also offer suitable cloud infrastructure for hosting these services.
3. Router and Switch with QoS Support: MikroTik or Cisco routers are ideal for this purpose.
4. FXO/FXS Adapter (if needed for analog lines): If you're still connected to city lines, you'll need these devices to convert analog to VoIP.

Basic Asterisk Server Configuration

If you decide to set up a dedicated server, first install the software:

sudo apt update
sudo apt install asterisk

Then edit the /etc/asterisk/sip.conf file and define a simple extension:

[6001]
type=friend
host=dynamic
secret=YourStrongPassword
context=from-internal
qualify=yes

And in /etc/asterisk/extensions.conf, specify the call routing:

[from-internal]
exten => _6XXX,1,Dial(SIP/${EXTEN},30)
exten => _6XXX,n,Hangup()

This simple configuration creates an internal line with number 6001 that you can set up on your IP phone.

Step-by-Step Migration from Traditional Lines to Cloud Telephony

Migration shouldn't be sudden and risky. The best approach is gradual transition.

Step 1: Network Assessment and Preparation

First, perform a network speed and quality test. Use tools like ping and mtr to check latency to the VoIP server. Latency (RTT) should be less than 150 milliseconds, and packet loss should be zero percent.

ping -c 100 your-voip-server.com | grep "loss\|avg"

If the average latency is above 100 milliseconds, look for a more optimal route or a better internet service.

Step 2: Parallel Setup

Set up the cloud telephony system in parallel with the traditional line. Activate one or two internal numbers on the cloud phone and ask employees to use them. This allows you to assess call quality in real conditions and identify issues before full migration.

Step 3: Gradual Transition and Employee Training

Once you're confident in quality, gradually migrate more lines. Take employee training seriously: many dissatisfactions with cloud telephony stem from unfamiliarity with the new software or phone. Prepare a one-page guide for using the IP phone and Softphone software.

Step 4: Complete Disconnection of Traditional Lines

After a parallel period (usually 2 to 4 weeks), disconnect the analog lines. But don't abandon your old numbers: use number porting services so that existing customers can still reach you through the previous number.

Security Tips You Shouldn't Overlook

Cloud telephony is an internet service and, like any other service, is exposed to attacks. The most common attacks include Toll Fraud and call eavesdropping.

• Always use strong passwords for extensions. Change the default password 1234 immediately.
• Configure the firewall so that only authorized IPs can access port 5060 (SIP).
• Use secure protocols SIP over TLS and SRTP for call encryption.
• Restrict international calls or set cost limits for them.

In /etc/asterisk/sip.conf, you can increase security by adding the following lines:

[general]
context=public
allowguest=no
alwaysauthreject=yes
rtpbindaddr=0.0.0.0
rtpencryption=yes

Final Thoughts: Is Cloud Telephony Right for Your Organization?

If your organization has more than 5 employees, plans to expand across multiple branches, or uses CRM systems, the answer is almost certainly "yes." Cloud telephony not only reduces costs but also provides capabilities that are essential in today's competitive world. However, the success of this migration depends on two factors: proper network infrastructure and careful planning. By following the tips in this article, you can confidently and with minimal risk transition your organizational communications to the new generation.

If you don't have suitable cloud infrastructure to host your VoIP server, exploring domestic cloud services like those offered by ServerNet can be a good starting point. But remember: your most important assets are proper planning and training your team.