5 Questions for a VoIP Expert

Posted on
Causes Analysis Screenshot

A few months ago, I received a direct message on LinkedIn from a member organization. They were interested in knowing if I was still in the VoIP troubleshooting business? If so, they wanted to know if I could help and provide any best practice recommendations.

Ooredoo Chooses Empirix to Assure Optimal Service Quality to Wholesale Carrier Customers

Posted on
Global Network

OGS selected the Empirix service assurance monitoring solution to gain visibility into the international connections providing carriers with access to its voice (both legacy circuit-switched and VoIP) and 2G/3G roaming services. With Empirix, OGS has uninterrupted visibility of network performance and service quality, as well as the ability proactively identify potential issues before they negatively impact customers. This flexible solution is capable of adapting to new technologies and innovative new services; OGS plans to extend the Empirix solution’s coverage to a recently announced LTE roaming service.

Fraud Within a VoIP Environment

Posted on
Hacker

Since the introduction of VoIP, the service or underlying technology (based on the SIP protocol) has been susceptible to multiple fraud scenarios. In particular, by exploiting some of the features of VoIP, such as three way call and call transfer, hackers can inject call signals into the network and effectively hijack calls. The result is significant non-billable revenue for the Service Provider. Since commands associated with VoIP technology are often sent un-encrypted and without authorization for each command, this is an easy technique to carry out.

If at First You Don’t Succeed, Test, Test Again

Posted on
Test Failure

In one recent test Empirix was involved with, callers were complaining about long connection times and poor voice quality during a storm. The company involved conducted a test of its SBC to better understand the origin of the issue. During the test process, the organization discovered that, while having a registration flood of 10,000 concurrent SIP registrations, SIP call setup time doubled. Moreover, jitter increased on the SBC.