Microsoft Teams Call Test

Purpose:

In this test scenario, real devices connected to the Access Point participate in a Teams call session. The test validates:

• Audio and video call stability
• Real-time communication performance under load
• Multi-device conferencing behavior
• AP handling of uplink/downlink traffic during video calls The LANforge system initiates Teams call sessions on selected devices using configured credentials and parameters. This helps simulate real-world collaboration workloads.

Chambers and attenuators are not required for this test; however, running it inside isolation chambers typically provides more stable and reliable results. This feature is supported in LANforge version 5.4.9 and later.

Test Case:

Step 1:

Open Chrome and enter the LANforge Manager's IP address followed by port 5454 in the address bar. This will open the WebGUI Login Page as shown below:

Step 2:

Select Interop and enter login credentials to sign in:

• Username: test@lanforge.com
• Password: lanforge

Step 3:

After logging into the WebGUI, the user should enter the LANforge Manager's IP address and select Connect. The Device Manager page will then be displayed, showing all real devices connected to the Candela Box. This view includes devices across multiple operating systems, such as Android, iOS, Windows, Linux, and MacOS.

• NOTE: Real Devices must be clustered using Interop Cookbooks and have a unique hostname to appear in Device Manager.

Step 4:

After reviewing the connected devices, the user should navigate to the Testing page. In the Testing page, select the required device from the Available Devices panel, choosing Teams call Test from the Tests panel. Enter the necessary test parameters and then click Run Test to begin the interoperability test.

Teams Call Test Parameters

1. Instance Name^* - Specifies the custom name for the test. The instance name must begin with an alphabet. Special characters and numbers cannot be used at the beginning of the instance name. Each test must have a unique instance name.
   • Example: Teams_Test1
2. Resources^# - Specifies the Resource IDs of selected devices participating in the Teams call.
   • Example: 15,11,10
3. Select Host^* - Defines the primary host device initiating or coordinating the Teams session.
   • Example: 15
4. Test Type^* - Specifies the type of Teams session workload.
   • Example: AUDIO & VIDEO
5. Duration^* - Defines the total duration of the Teams Call Test, in minutes.
   • Example: 5
6. Upstream Port^* - Indicates the AP's wired connection to the LANforge Ethernet interface used to generate and run traffic.
   • Example: eth2-192.168.50.41

^* - Mandatory
^# - Automatically filled

Step 5:

After clicking Run Test, an instance will be created using the specified test name. During the test execution, the user can monitor the real-time graph, review logs in the Log Viewer, and observe the configured test parameters. Once the test has completed, the user should generate the PDF report from the Testing page and save it to the desired directory.

Note: When the test is initiated, the cross connection is created in the generic tab in the LANforge manager. After the test completes, a detailed PDF report is saved in the webgui_reports folder located under the home/lanforge directory on the LANforge manager.

Sample PDF report: teams_call_report.pdf