Webex Cloud Agents
ThousandEyes has Webex-specific Cloud Agents deployed at the front door of several Webex data centers responsible for serving customer traffic. These agents are available for general use by all ThousandEyes customers and are a tool to better monitor and troubleshoot your Webex performance. For more information about the key value of these agents, see the Webex Monitoring solution page.
Cloud Agents that are Webex-specific display the Webex icon, and are identified as such in parentheses after the location name, as shown below:

Key Differences

There are a few key differences between these Webex Cloud Agents and our general Cloud Agents you see on the ThousandEyes platform:
  • Most importantly, these agents can only be used as test targets and cannot be the source of any tests. This means that these agents can only be used in agent-to-agent and RTP stream tests, and only as the target of that test.
  • These agents can perform bidirectional testing, but only after they are selected as a target for the test.
  • You can use the Webex Cloud Agents only with other IPv4 agents. IPv6 testing is not supported with the Webex Cloud Agents.

Best Practices

We recommend that you set up the following tests with Webex Cloud Agents to better understand your Webex performance. For full visibility into Webex, these tests should supplement any HTTP server, web transaction, or DNS tests that you have targeting your Webex environment
  • An RTP stream test between any applicable Enterprise Agents and the Webex Cloud Agent hosted within the VPC of your closest multimedia platform server. You should use (UDP) 9000 and 5004, with DSCP 46. This will help you understand inbound performance of voice traffic into the Webex Cloud environment.
  • An agent-to-agent bidirectional test between any applicable Enterprise Agents and the Webex Cloud Agent hosted within the VPC of your closest multimedia platform server. You should use (UDP) 9000 and 5004, with DSCP 34. This will help you understand simulated, bidirectional performance of video-marked traffic into the Webex Cloud environment.
    Keep in mind that for agent-to-agent tests, in many cases you must configure the firewall to allow the test to succeed. For detailed information, see Firewall Configuration.
If the Enterprise Agent in the test is behind a NAT, you must also select the Behind a NAT option. For detailed information, see NAT Traversal Requirements.
  • Another agent-to-agent bidirectional test, this one between any applicable Enterprise Agents and the Webex Cloud Agent hosted within the VPC of the second-closest multimedia platform server. You should use (UDP) 9000 and 5004, with DSCP 34. This will help you understand the bidirectional reachability of your multimedia platform and the network performance of your backup Webex traffic.
If you attempt to run a TCP-based test, we recommend that you enable in-session path trace mode for consistent path visualization results. If you don’t enable this setting, you may notice TCP packets getting dropped at the ingress of the Webex infrastructure.

Webex Cloud Agent Locations

Webex Cloud Agents are currently available in the following locations:
  • San Jose
  • Singapore
  • London
  • Dallas
  • Frankfurt
  • Amsterdam
  • Chicago
  • Montreal
  • New York
  • Sydney
  • Tokyo
  • Toronto
Copy link
Outline
Key Differences
Best Practices
Webex Cloud Agent Locations