Unified Communications
Unified communication traffic regenerates voice and video traffic that goes through networks.
| |
Citrix |
| Description |
Citrix Traffic - From Probe Is Client And To Probe Is Server |
| Purpose |
|
| Available Options |
|
| Metrics |
- Throughput (Mbps) from->to
- Response Time (ms)
- Transaction Rate (per sec)
|
| Advanced Information |
|
| Results interpretation |
|
|
Potential
Errors
|
|
| |
Skype4B traffic from -> to |
| Description |
Microsoft Skype4B traffic.
Default parameters for audio and video based on Microsoft recommended settings. User configurable parameters.
This test is for bidirectional configuration.
|
| Purpose |
Reproduce Skype4B traffic to assess the network capability to transport this traffic either in volumes or for singe calls.
|
| Available Options |
For each direction, options include the following:
- Generated bitrate audio
- Generated bitrate video
- QOS for each traffic
- Packet size audio
- Packet size video
- Total number of users (number of streams)
|
| Metrics |
For each direction and each stream (audio/video), options include the following:
- Upstream and downstream loss
- Jitter
- Max jitter
- One way delay
- Throughput audio
- Throughput video
- Max loss bursts (max consecutive packet loss)
|
| Advanced Information |
Skype4B traffic unidirectional emulates Skype4B users talking to each other in one way. This test is designed according to Microsoft recommended network validation of network use for Skype4B.
You can use and fine tune the test for any Unified Communication solution that combines Voice and Video traffic.
We recommend you to use the test in meshes so that both directions are tested at the same time.
The number of users is typically not used to generate volume traffic. We recommend you to leave this setting to 1 and compute the total volume of traffic according to traffic profiles.
|
| Results interpretation |
This test generates Skype4B Audio and Video streams on the selected paths.
You can optimize the test by setting up Send Low Jitter in Preferences to be 1, if the endpoints support it.
|
|
Potential
Errors
|
If test result pair cannot be collected, check the following:
- Your E2 endpoint can open the 10115 port toward E1 for management (this is needed for stream pairs).
- Synchronization port between the pairs is opened (management UDP 10115).
- Port in use is in range. See Preferences > Traffic Port Management > Destination Port Conf Option and Preferences > Test Controller > First Destination Port so that you can use the correct destination port for test traffic.
Skype4B has its own port management control. Go to Preferences > Traffic Port Management > Destination Port Conf Option. If Use Skype4B Special Range option is set to 1 this will take precedence over the default port management for Skype4B tests (only for Skype4B tests).
|
| |
Skype4B traffic |
| Description |
Microsoft Skype4B traffic.
Default parameters for audio and video based on microsoft recommended settings. User configurable parameters.
This test is for unidirectional configuration. |
| Purpose |
Reproduce Skype4B traffic to assess the network capability to transport this traffic either in volumes or for singe calls.
This test is for bidirectional communication - reproducing the traffic of realistic conversations.
|
| Available Options |
Per direction:
- Generated bitrate audio
- Generated bitrate video
- QOS for each traffic
- Packet size audio
- Packetsize video
- Total number of users (number of streams)
Typically traffic are symmetrical per transaction.
|
| Metrics |
For each direction and each stream (audio/video)
- Upstream/Downstream loss
- jitter
- max jitter
- one way delay
- throughput audio
- throughput video
- max loss bursts (max consecutive packet loss)
|
| Advanced Information |
Skype4B traffic unidirectional emulates Skype4B users talking to each other in one way. This test is designed according to Microsoft recommended network validation of network use for Skype4B.
You can use and fine tune the test for any Unified Communication solution that combines Voice and Video traffic.
We recommend you to use the test in meshes so that both directions are tested at the same time.
The number of users is typically not used to generate volume traffic. We recommend you to leave this setting to 1 and compute the total volume of traffic according to traffic profiles.
|
| Results interpretation |
This test generates Skype4B traffic streams on the selected paths.
You can optimize the test by setting up Send Low Jitter in Preferences to be 1, if the endpoints support it.
|
|
Potential
Errors
|
If test result pair cannot be collected, check the following:
- Your E2 endpoint can open the 10115 port toward E1 for management (this is needed for stream pairs).
- Synchronization port between the pairs is opened (management UDP 10115).
- Port in use is in range. See Preferences > Traffic Port Management > Destination Port Conf Option and Preferences > Test Controller > First Destination Port so that you can use the correct destination port for test traffic.
Skype4B has its own port management control. Go to Preferences > Traffic Port Management > Destination Port Conf Option. If Use Skype4B Special Range option is set to 1 this will take precedence over the default port management for Skype4B tests (only for Skype4B tests).
|
| |
Teams Cloud Call |
| Description |
Microsoft Teams Cloud Call is generating Cloud calls emulating Microsoft Teams media protocols. Node from should be on prem while node to should be in the cloud. The same ports and traffic patterns than realistic cloud calls are going to be emulated.
Ideally endpoint to (destination of the call) should be in Azure Cloud to emulate a Teams handler. Alternatively having any location on internet using other public clouds can be sufficient to validate the WAN/last mile portion.
|
| Purpose |
Reproduce Teams Cloud traffic to assess the network capability to transport this traffic either in volumes or for singe calls.
This test is handling bidirectional communication - reproducing the traffic of realistic conversations.
|
| Available Options |
Per direction:
- Number of calls supporting Audio
- Number of calls supporting Video (typically same or less than Audio only)
- QOS for each traffic
- Packet size audio (only option is 100 bytes)
- Packet size video (only option is 1000 bytes)
- Port to use for contacting server – defaults to Microsoft Teams cloud range.
Typically, traffic is symmetrical per transaction.
|
| Metrics |
For each direction and each stream (audio/video), following are the matrics:
- Upstream/Downstream loss
- jitter
- max jitter
- one-way delay
- throughput audio
- throughput video
- max loss bursts (max consecutive packet loss)
|
| Advanced Information |
The number of calls is typically not used to generate volume traffic. We recommend you to leave this setting to 1 and compute the total volume of traffic according to traffic profiles.
|
| Results interpretation |
This test generates Teams Audio and Video streams on the selected paths. Default thresholds are set according to Microsoft minimum recommendations. |
| Potential Errors
|
If test result pair cannot be collected, check the following:
- Your E2 endpoint can open the 10115 port toward E1 for management (this is needed for stream pairs).
- Synchronization port between the pairs is opened (management UDP 10115).
- Port in use is in range. See Preferences > Traffic Port Management > Destination Port Conf Option and Preferences > Test Controller > First Destination Port so that you can use the correct destination port for test traffic.
Ports used are part of the test parameters and not from ones set in preferences
|
| |
Teams WAN Call |
| Description |
Microsoft Teams WAN Call is generating WAN calls emulating Microsoft Teams media protocols. Node from and to should be on same WAN emulating calls between computers or from computers to a gateway. The same ports and traffic patterns than realistic cloud calls are going to be emulated.
|
| Purpose |
Reproduce Teams WAN traffic to assess the network capability to transport this traffic either in volumes or for singe calls.
This test is handling bidirectional communication – reproducing the traffic of realistic conversations.
|
| Available Options |
Per direction:
- Number of calls supporting Audio
- Number of calls supporting Video (typically same or less than Audio only)
- QOS for each traffic
- Packet size audio (only option is 100 bytes)
- Packet size video (only option is 1000 bytes)
- Port to use for contacting server – defaults to Microsoft Teams WAN range.
Typically, traffic is symmetrical per transaction.
|
| Metrics |
For each direction and each stream (audio/video), following are the matrics:
- Upstream/Downstream loss
- jitter
- max jitter
- one-way delay
- throughput audio
- throughput video
- max loss bursts (max consecutive packet loss)
|
| Advanced Information |
The number of calls is typically not used to generate volume traffic. We recommend you to leave this setting to 1 and compute the total volume of traffic according to traffic profiles.
|
| Results interpretation |
This test generates Teams Audio and Video streams on the selected paths. Default thresholds are set according to Microsoft minimum recommendations. |
| Potential Errors
|
If test result pair cannot be collected, check the folowing:
- Your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs).
- Synchronization port between the pairs is opened (management UDP 10115).
- Port in use is in range. See Preferences > Traffic Port Management > Destination Port Conf Option and Preferences > Test Controller > First Destination Port so that correct destination port for test traffic is used.
Ports used are part of the test parameters and not from ones set in preferences
|
| |
Traffic Mix – HTTP – Video - Voice |
| Description |
Traffic Mix. Emulates three different traffic types. Measures voice, video and HTTP metrics. |
| Purpose |
This can simulate three traffic types through network with one test. |
| Available Options |
Test duration, Total bitrate voice from->to, and Total bitrate HTTP from->to.
|
| Metrics |
- HTTP throughput (Kbpa)
- HTTP Transactions per sec
- Delay video (ms)
- Jitter video (ms)
- Loss video
- Max loss burst video
- Throughput Video (Mbps)
- Total Bytes Lost Video
- Delay voice (ms)
- Jitter voice (ms)
- Loss voice (ms)
- Max Loss Burst voice (ms)
- MOS
|
| Advanced Information |
This test uses pre-defined configurations for Video and Voice codec traffic.
|
| Results interpretation |
This test generates test metrics for HTTP/Video/Voice. |
| Potential Errors
|
If test result pair cannot be collected:
- Ensure that your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs).
- Ensure that synchronization port between pairs is opened (management UDP 10115).
- Ensure that ports for video and voice are open.
|
| |
Zoom meeting |
| Description |
Zoom meeting is generating traffic emulating Zoom meeting media protocols. Node from should be on prem while node to should be in the cloud. The same ports and traffic patterns than realistic cloud calls are going to be emulated.
Ideally endpoint to (destination of the call) should be in any location on internet using public clouds to validate the WAN/last mile portion.
|
| Purpose |
Reproduce Zoom traffic to assess the network capability to transport this traffic either in volumes or for singe calls.
This test is handling bidirectional communication - reproducing the traffic of realistic conversations.
|
| Available Options |
Per direction:
- Number of calls supporting Audio
- Number of calls supporting Video (typically same or less than Audio only)
- QOS for each traffic
- Packet size audio (only option is 100 bytes)
- Packet size video (only option is 1000 bytes)
- Port to use for contacting server – defaults to Zoom Meeting cloud range.
Typically, traffic is symmetrical per transaction.
|
| Metrics |
For each direction and each stream (audio/video), following are the matrics:
- Upstream/Downstream loss
- jitter
- max jitter
- one-way delay
- throughput audio
- throughput video
- max loss bursts (max consecutive packet loss)
|
| Advanced Information |
The number of calls is typically not used to generate volume traffic. We recommend you to leave this setting to 1 and compute the total volume of traffic according to traffic profiles.
|
| Results interpretation |
This test generates Zoom Audio and Video streams on the selected paths. Default thresholds are set according to Zoom minimum recommendations. |
| Potential Errors
|
If test result pair cannot be collected, check the folowing:
- Your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs).
- Synchronization port between the pairs is opened (management UDP 10115).
- Port in use is in range. See Preferences > Traffic Port Management > Destination Port Conf Option and Preferences > Test Controller > First Destination Port so that correct destination port for test traffic is used.
Ports used are part of the test parameters and not from ones set in preferences.
|