2nd Whitepaper in the OTT Telephony Application Series
In our previous whitepaper – OTT telephony application testing: Designing a generic OTT telephony
application for accurate quality assessment and troubleshooting of encrypted OTT voice services – we examined the generic OTT telephony application concept, its codec/client adaptation and settings, and recommended KPIs to be used for testing.
In this accompanying whitepaper, we now examine data-driven validation of the Infovista TEMS™ generic OTT telephony application vs. a native OTT app.
This validation of a generic OTT voice app vs. a native OTT voice app (WhatsApp in this case) needs to adhere to the following main requirements:
- Simultaneously run the generic and native OTT telephony apps
- Closely synchronize the call start of the two applications
- Use digital, instead of analog, audio to ensure increased accuracy when measuring the native OTT telephony application
- Run the two applications in a broad range of network conditions, uniformly covering the whole quality range, from very good to very bad. The very bad conditions likely need to be created with dampers in a radio-shielded room or with network emulators, since driving for a long time in poor live network conditions is not easily achievable.
The technical paper presents the requirements for a generic OTT application to be a representative benchmark and set the expectations on differences when compared with a native application. In addition, using WhatsApp, and an extensive live test, the paper validates Infovista’s generic OTT telephony application for the main KPIs: voice quality (MOS scoring), call setup time, call completion and failure, and speech path delay. The results show no statistically significant differences and close performance trends.
Submit the form to download the whitepaper to understand how Infovista’s generic OTT telephony application testing approach using a generic voice client was validated to be a representative benchmark for native OTT telephony application testing.