I'd say QoS drops even more abruptly if you hit the bandwidth or performance limits. tshark, a text terminal version of Wireshark, can analyze the quality of RTP streams and print a report that you can parse. Keep in mind that the analysis itself is quite CPU-intensive, so what I usually do is collect the RTP streams with tcpdump, and then run tshark in low-priority mode. Here in scripts/ you can find a simple script that launches tshark and analyses the output: https://github.com/voxserv/voip_qos_probe There is also a library for comparing WAV streams -- this would be the best for QoS measurements, and you would also be able to get the PSTN path into the test. But I didn't yet try it, as the customer was satisfied with RTP analysis: http://openpreservation.org/knowledge/blogs/2012/07/09/xcorrsound-waveform-c... https://github.com/openpreserve/scape-xcorrsound I hope this helps :) On Wed, Feb 25, 2015 at 1:35 AM, Andrew V <avstarventures@gmail.com> wrote:
How do you measure quality of service across all calls? What are ways to avoid bad quality of service? Say the call volume is in your control. Is it as easy as not letting the call volume get out of control? The attached is a hypothesis of the relationship between QOS and the number of concurrent calls. Does it work that way? What other factors need to be taken into account?
[image: Inline image 1]
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
