Mtalk integrates on call view a connection quality indicator in order to monitoring, in real time, the performance of the underlying network connection as it is measured by app
Generally there is no immediate relationship between the level of network signal (WiFi or 3G as shown by device) and the performance of the network itself (as measured by the indicator), so may have poor network performance also in case of full signal. This can occur for several reasons, among which:
- Reduced capacity of the network: some network-intensive applications, for example, may saturate the network; on the other hand a mobile data connection (3G) offers fluctuating performances often with no traffic periods and this is very limiting for VoIP traffic: the result is that in these cases the quality is compromised especially about the uplink (in output from the terminal point of view)
- Radio interference: it is important to check that your WiFi Access Point uses a radio channel as "clean" as possible: it should not overlap with that of other neighboring Wi-Fi networks. Where Access Point model does not operate in automatic channel selection mode, users may use free smartphone apps that analyze the environment to suggest the most appropriate radio channel to configure the access point in order to minimize interference.
Connection quality indicator shows critical network conditions using either low levels or a triangle icon.
For those users who wish more advanced technical information about network performance, there is an advanced panel viewable by clicking on the quality indicator. The panel shows the following information:
- [Codec]: the audio codec used by current call
- [RTT]: the statistic of a parameter related to the network delay; single values greater than 100 ms mean that network delay is too high and it may affect the call quality
- [Obfuscation]: the information concerning the obfuscation algorithms applied to the current call at network layer; the obfuscation has no effect on the call quality
- [Connection]: the frequency of the events "no traffic received from the network"; each time that first number increases (dead) means that the network connection has been idle for too long without receiving packets; this phenomenon is often linked to interference issues among overlapped WiFi networks (if app uses WiFi connection)
- [Packets recv/sent Δ]: the percentage of alignment among the two streams uplink / downlink; the optimal value is zero. Negative values are the most critical as indicate that the number of received packets is less than the expected one
- [PLC]: the percentage of audio packets artificially synthesized since they do not arrive in time to play; the higher the value the worse the quality of the call as the app is not receiving packets from the network so it is forced to synthesize locally with a significant deterioration in quality [ either metallic effect or fragmented audio ]