VoIP QoS Analysis over Asterisk and Axon Servers in LAN Environment

Abstract

Voice over IP (VoIP) is a developing technology and a key factor in both the emerging cyberspace engineering and also an accomplishment to set up its position in the telecom industry. VoIP technology is based on internet technology; where data packets switching system is used rather than circuit switching. Whereas, an analog signal is changed over into the digital signals in the full-duplex transmission. VoIP technology is replaced with the conventional public switched telephone network (PSTN) system due to the high flexibility and low-cost. The purpose of this research work is to deliberate experimental and computational performance in the view of quality of service (QoS) parameters of VoIP over local area network (LAN) network. The VoIP systems implementation is based on two different operating system framework (Linux and Windows), whereas, Linux-based and Windows-based private branch exchanges (PBXs), such as Asterisk (Linux-open source) and Axon (window-close source) are configured, installed and verified. QoS factors (such as packet loss, delay, jitter, etc.) are observed over the Asterisk and Axon PBXs in a LAN domain with the assistance of Paessler switch activity grapher (PRTG) monitoring tool. The validations of results are looked at for QoS parameters crosswise over both PBXs with data load (i.e., file transfer and HTTP traffic) during VoIP calls. The productivity and execution of Axon and Asterisk have been equated and analyzed over experimental based outcomes.

The Development of a Secure Internet Protocol (IP) Network Based on Asterisk Private Branch Exchange (PBX)

“…To ensure the security of the network built on the basis of Asterisk PBX, there is a wide range of security features, such as encryption, authentication, and authorization, which help protect against unauthorized access to the system and data [11][12][13]. For such setups, the Asterisk PBX software is highly available, which means that it can automatically fail over to a standby server in the event of a hardware failure or other problem, ensuring that services are always available [14][15][16][17].…”