Emerging Network Technology: VoIP Virtualization

As enterprises move towards server virtualization, does the VoIP/ipserver adapt to the server consolidation plan? The answer is yes.

PBX (Programmable switch) was previously an independent proprietary system. With the emergence of Internet protocol Voice Technology (VoIP) and network telephone technology (IPTS), PBX has become a system-based server. Why Should organizations and their ability to virtualize VoIP and other communication services.

Why virtualization VoIP

Whether the VoIP system can be virtualized depends on the manufacturer's VoIP/ipserver software you are using. Some VoIP software can only run on a VPC, not a candidate for virtualization. Other vendors that can run their software on standard Linux or Windows systems may be virtualized.

The good thing is that ip pbx vendors gradually do not provide proprietary products. They now produce software that can run on multiple server platforms. Private servers are being replaced by common servers, making it easier for enterprises to consider virtualized VoIP.

Call manager)

To understand when VoIP can become a good candidate for virtualization, Let's first look at call processing components or VoIP/ipserver.

Data centers can benefit from virtualized Call Management Servers because their resources are not fully used. Since no server is used for conversations/presentations, basically, VoIP/ipserver is idle for most VoIP calls. It is only busy at the beginning of the call setting several seconds and at the end of the call.

Let me explain it. The VoIP/ipserver is not a telephone switch like the old PBX. This server is just a call controller. This server is connected to the endpoint, network phone number, softphones, and gateway to establish a telephone call. The endpoint is connected to the server and requests a telephone call connection using a protocol like H.323 signal protocol and SIP standard protocol or Cisco SCCP proprietary protocol. The endpoint sends a call request packet to the server. The server then contacts other endpoints to create a call. Servers associated with endpoints are unique for most IT applications. Once the server allows two endpoints to accept the call, the server will return to one side, and the call will be established point-to-point without passing through the server.

Even during call peak hours, call processing component resources are not fully used. Depending on the vendor, a server creates 25,000 to 30,000 calls per hour, which is called BHCC (number of calls completed during busy hours ). The server processes 6-10 transient packets for each call. The traffic is not too large. Assume that the server will set 1000 calls within one hour, with an average of 2-4 packets per second. When the terminal fails, the server can receive 2-4 packets. Therefore, a call must process 8-14 transient data packets.

Now, if you operate a large call center, you may consider that your server usage should be higher. Yes, BHCC can be higher. In an enterprise, a call center can be improved by about 5-20 times compared with a common call. However, even in a call center, this is not an important load. Why? BHCC reduces the number of calls due to a long call period. This means that the server must support fewer calls to complete the operation.

Unified messaging and communication Virtualization

Unified Messaging (UM) refers to the combination of e-mail, voice, and fax in the same mailbox. Unified Communication (UC) integrates UM with conference, cooperation, and attendance management, they present more possibilities of virtualization. For IP technology, UM and UC functions are similar. UM and UC servers are not constantly busy, so they are not fully utilized during the operation cycle. Virtualization can be applied to UM and UC support.

VoIP virtualization platform

As I mentioned earlier, the increasingly common use of VoIP servers is the second reason for virtualization.

Linux is one of the most popular VoIP/IPSS operating systems. Companies like 3Com, Intecom, and Siemens all run on IBM servers running Linux. 3Com and Siemens can also run on IBM System I computers. Other vendors can also run their software on Linux, but you need to check their software to ensure that the software runs on your Linux version. If a small ip pbx vendor uses their own Linux version, you must use the ip pbx software to download it. In this case, ip pbx software may not work in a virtualized environment.

Of course, VoIP virtualization is not restricted by open-source platforms. The Cisco 4.x software runs on Windows. Avaya IP offices serving hundreds of workstations and most small ip pbx vendors also run on Windows. Therefore, if you have a virtualized Windows environment, VoIP virtualization is possible.

In general, for the underutilized VoIP/IPT servers and new software from ip pbx vendors running on third-party platforms (such as IBM servers running Linux operating systems ), virtualization is an attractive choice. Virtualization can also reduce the number of VoIP servers you use, reducing energy consumption and cooling requirements. With the transition from a hardware model to a virtualized software model, we hope to see this change in the data center.

1. Basic concepts, principles, and application of VoIP technology
2. Application of server-bound Softswitch VoIP in Small and Medium-sized Enterprises
3. Three Popular manufacturers of integrated communication work hard to achieve unified VoIP Communication