Telepresence Testing Approach by Shenick
•Download as PPT, PDF•
0 likes•706 views
The document discusses using traffic emulation to test the interoperability and performance of telepresence systems. It describes emulating real end users and devices to conduct tests that evaluate factors like video and audio quality, call connectivity, and system functionality under different conditions. Traffic emulation allows for testing scenarios that incorporate real user behavior and diverse network environments.
![Overview ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
More Related Content
What's hot
Similar to Telepresence Testing Approach by Shenick
Similar to Telepresence Testing Approach by Shenick (20)
More from IMTC
More from IMTC (20)
Recently uploaded
Recently uploaded (20)
Telepresence Testing Approach by Shenick
- 1. Mark Lambe Product Marketing Manager Shenick Network Systems Use of Traffic Emulation in Interoperability Testing
- 13. Thank You! Questions & Answers email : mark.lambe@shenick.com
Editor's Notes
- Shenick is an award winning provider of IP test solutions for Next Generation Networks and Applications. Shenick’s unique selling point is the ‘Per flow’ architecture enabling users emulate unique end-points running various applications like Telepresence, with as close to real activity. This provides users with the unique ability to build test scenarios with varying load conditions and traffic types.
- Telepresence success is based on an almost flawless presentation of HD video and Audio. Clearly the video and audio quality are clearly the most relevant metrics. But in relation to understanding the full picture of quality of experience more test parameters need to be included in the test strategy. Evidently Telepresence is not the only service ro run on a network, therefore its important to test with varying applications and load conditions.
- Its clear that different people will require different test processes and procedures along the production path. It’s important to select a test partner/solution that will work efficiently and effectively at each stage, including the full implemented live solution.
- Closed testing, enabling users pre-empt the likely outcome of the test, these type tests are useful in examining performance of the basic system in isolation.
- At a network wide level performance can still be pre-empted, this enables fine tuning of components and various QoS settings, these type tests should still be seen as closed.
- A key component of Telepresence is the management of video and audio flows from unique end-points. Its clear to test Telepresence requires a per flow approach in which each end-point has its own unique parameters. As part of the overall Telepresence experience its important to include tests such as DHCP server timing performance and test end-point management databases access times, all of which contribute to a successful call attempt .
- Adding dynamic user behaviour is a step towards an open test environment. This means tests conditions can be altered during live runs, making it a little harder to predict the actual outcome e.g. what happens when all end-points mute calls and un-mute at the same time, with high decibel noise?
- Order is critical
- By adding additional user traffic flows to the test such as web, email, P2P the test strategy becomes Open. Open means its less likely the outcome of the test can be predicted.
- `Shenick has two distinct product lines diversifEye and servicEye. diversifEye is a lab based tool.
- servicEye Spider enables users test from remote end-points on the network against real services.
- If you require more details, or alternatively would like to organise a demo please do not hesitate in getting in touch. Thank you.