ThousandEyes and Meraki for voice network assessment

See also

Sources

1. 1
   Control Hub Webex Calling troubleshooting shows calls from the past 21 days and requires the full admin, read-only admin or support admin role.

   Troubleshoot Webex Calling calls in Control Hub · Overview; roles paragraph · Checked 2026-10-14
2. 2
   Because ThousandEyes Webex Calling Cloud Agents exist only in a listed subset of data centers, an organization whose calls are hosted elsewhere likely cannot run agent-to-agent tests against a same-data-center Webex target.inferred

   ThousandEyes integration with Webex services in Control Hub · Webex Calling section: data center table (read with ThousandEyes guide 'Recommended tests') · Checked 2026-10-14
3. 3
   Meraki data in Control Hub Troubleshooting is shown in five-minute intervals, with AP channel utilization in ten-minute intervals.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Overview; Troubleshooting charts and data · Checked 2026-10-14
4. 4
   For a Webex Calling call, the Meraki wireless SNR, RSSI and latency appear by hovering the Wireless connection quality line on the Hop Detail page, which offers a Check Meraki Dashboard cross-launch.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Example: Webex Calling · Checked 2026-10-14
5. 5
   For Webex App calls and meetings, Meraki data appears only if the Collect Client Metrics setting in Control Hub Organization Settings is on, allowing Cisco to collect client IP and MAC addresses.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Limitations: client metrics · Checked 2026-10-14
6. 6
   Meraki data in Control Hub for calls on Desk Phone devices requires client version 3.4 or later.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Prerequisites; Limitations · Checked 2026-10-14
7. 7
   Setting up the Meraki integration requires a Control Hub full administrator (external full administrators cannot) and a Meraki full administrator account to authorize access.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Prerequisites · Checked 2026-10-14
8. 8
   The Meraki Control Hub integration supports the Webex App desktop client but not the Webex mobile app, and the Meraki data line does not show for offline devices.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Limitations · Checked 2026-10-14
9. 9
   Control Hub shows Meraki troubleshooting data only for meetings and calls hosted in the customer's own organization, not for external meetings users join.

   Integrate Cisco Meraki with Troubleshooting in Control Hub · Overview · Checked 2026-10-14
10. 10
    Control Hub Troubleshooting keeps Meraki data for at most seven days; older meetings show the Meraki data line greyed out.

    Integrate Cisco Meraki with Troubleshooting in Control Hub · Overview; Limitations · Checked 2026-10-14
11. 11
    The Meraki Control Hub integration article lists the Webex App desktop client and Cisco Room series devices as supported.disputed

    Integrate Cisco Meraki with Troubleshooting in Control Hub · Limitations: Webex App and devices bullet · Checked 2026-10-14
12. 12
    The Meraki Control Hub integration article lists RoomOS as not yet supported.disputed

    Integrate Cisco Meraki with Troubleshooting in Control Hub · Limitations: RoomOS bullet · Checked 2026-10-14
13. 13
    Meraki is integrated by turning on Allow Meraki API access in Control Hub Organization Settings, signing in to the Meraki dashboard as a Meraki full administrator, selecting the Meraki organization, and selecting Allow.

    Integrate Cisco Meraki with Troubleshooting in Control Hub · Set up the integration, steps 1-6 · Checked 2026-10-14
14. 14
    The Meraki Network line is not available for wired devices in Participant Details, and devices behind a Meraki MX show their connections as wired.

    Integrate Cisco Meraki with Troubleshooting in Control Hub · Limitations: wired devices; Meraki MX · Checked 2026-10-14
15. 15
    Control Hub rates Meraki wireless quality good when SNR is at least 20 dB, RSSI is at least -80 dBm, or average wireless latency is at most 200 ms, and poor below those values.

    Integrate Cisco Meraki with Troubleshooting in Control Hub · Overview: thresholds · Checked 2026-10-14
16. 16
    An MX acting as an Auto VPN hub cannot analyze Meraki Insight traffic arriving over VPN from spokes, so Insight must be enabled on spoke MXs to see that traffic.

    Meraki Insight Introduction · Auto VPN considerations · Checked 2026-10-14
17. 17
    Meraki Insight requires MX firmware 14.20 or later (14.21 or later recommended) and runs on MX appliances and Z3/Z4 teleworker gateways, not on MR or MS devices.

    Meraki Insight Introduction · Requirements; Supported platforms · Checked 2026-10-14
18. 18
    From July 26, 2024, standalone Meraki Insight licensing and functionality is available only within the Meraki SD-WAN Plus licensing tier.

    Meraki Insight Introduction · Licensing notice (top of page) · Checked 2026-10-14
19. 19
    Meraki Insight VoIP Health actively probes admin-configured VoIP server IPs from each MX WAN uplink with ICMP every second and reports loss, latency, jitter and MOS.

    MI VoIP Health Overview · Overview; How it works · Checked 2026-10-14
20. 20
    Meraki Insight VoIP Health classifies MOS above 4 as good, 3.5 to 4 as moderate and below 3.5 as bad.

    MI VoIP Health Overview · MOS thresholds table · Checked 2026-10-14
21. 21
    Meraki Insight VoIP Health does proactive path monitoring only; it does not measure the quality of actual calls and has no metrics between the MX and individual phones.

    MI VoIP Health Overview · Limitations · Checked 2026-10-14
22. 22
    Meraki Insight VoIP Health does not support H.323 or subnet targets, and for servers that do not answer ICMP it can fall back to Best Effort Monitoring of the nearest responding hop.

    MI VoIP Health Overview · Configuration; Best Effort Monitoring; Limitations · Checked 2026-10-14
23. 23
    The ThousandEyes account group whose connection string is used on RoomOS devices must match the account group used for the Control Hub integration.

    ThousandEyes Agent integration for Board, Desk, and Room Series devices · Prerequisites · Checked 2026-10-14
24. 24
    ThousandEyes is activated in Control Hub under Organization Settings in the ThousandEyes section by turning on API access, pasting the OAuth bearer token and selecting Activate.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Install and activate ThousandEyes · Checked 2026-10-14
25. 25
    ThousandEyes recommends deploying an Enterprise Agent on the same network as the Webex devices or applications and using it as the source agent for Webex Calling tests.

    Monitoring Webex Calling · Agent placement · Checked 2026-10-14
26. 26
    The ThousandEyes token used for the Control Hub integration is created in ThousandEyes under Account Settings > Users and Roles > Profile, in the User API Tokens section.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Before you begin: create a token · Checked 2026-10-14
27. 27
    Control Hub Troubleshooting integration with ThousandEyes endpoint automated session testing requires Webex App desktop version 42.7 or later.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Overview · Checked 2026-10-14
28. 28
    Cisco recommends a ThousandEyes automated session test for Webex with target Webex, protocol auto-detect, a one-minute interval and all agents selected.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Before you begin: create an automated session test · Checked 2026-10-14
29. 29
    ThousandEyes documents that Call on Webex 1:1 calls use Webex Meetings infrastructure and are routed to a meeting data center by client geolocation, so the monitoring target can change with the user's network.

    Monitoring Webex Calling · Identifying monitoring targets: Call on Webex · Checked 2026-10-14
30. 30
    The Webex Calling ThousandEyes Cloud Agents are available to all customers who have ThousandEyes agents on their enterprise network.

    ThousandEyes integration with Webex services in Control Hub · Webex Calling section · Checked 2026-10-14
31. 31
    For Webex Calling, the ThousandEyes Troubleshooting integration supports only the desktop Webex App, PhoneOS 3.2.1 and later, and Board, Desk and Room Series devices.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Limitations: Webex Calling · Checked 2026-10-14
32. 32
    ThousandEyes Cloud Agents deployed at Webex Calling data centers capture RTP traffic bidirectionally to locate issues on the path between the Webex Calling data center and the enterprise network.

    ThousandEyes integration with Webex services in Control Hub · Webex Calling section · Checked 2026-10-14
33. 33
    ThousandEyes Cloud Agents can monitor Webex Calling calls hosted only in a limited set of data centers: Chicago, Dallas, Montreal, Toronto, Frankfurt, London, Melbourne, Sydney, Osaka and Tokyo.

    ThousandEyes integration with Webex services in Control Hub · Webex Calling section: data center table · Checked 2026-10-14
34. 34
    Webex Calling admins can troubleshoot media quality in Control Hub, and with the ThousandEyes integration they can cross-launch from Control Hub into the ThousandEyes application for further network analysis.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Overview (opening section) · Checked 2026-10-14
35. 35
    ThousandEyes data can take up to five minutes to appear in Control Hub Troubleshooting.

    Integrate ThousandEyes with Troubleshooting in Control Hub · View ThousandEyes data in Troubleshooting · Checked 2026-10-14
36. 36
    Although ThousandEyes automated session tests support both the Webex Meetings desktop app and Webex App, Control Hub Troubleshooting shows the network path only for users who join through the desktop Webex App.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Overview · Checked 2026-10-14
37. 37
    Enabling the ThousandEyes agent on Cisco phones and collaboration devices requires a ThousandEyes Endpoint Agent license (Essential or Advantage), one per device.

    ThousandEyes Agent integration for Board, Desk, and Room Series devices · Prerequisites · Checked 2026-10-14
38. 38
    ICE-optimized Webex Calling calls between users on the same network may not traverse the Webex Calling cloud, so Control Hub shows no ThousandEyes network path for them.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Limitations · Checked 2026-10-14
39. 39
    ThousandEyes round-trip loss is measured before error recovery, so it will not match the Audio Quality packet loss in Control Hub, which Cisco calls the better indicator of user experience.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Network path details: loss note · Checked 2026-10-14
40. 40
    For users with a ThousandEyes endpoint agent, a Network Path line appears under Audio Quality on the participant details page in Control Hub Troubleshooting.

    Integrate ThousandEyes with Troubleshooting in Control Hub · View ThousandEyes data in Troubleshooting · Checked 2026-10-14
41. 41
    In Control Hub, ThousandEyes cross-launch links for Webex Calling appear only when metrics exist for a media call; calls without media have no ThousandEyes link.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Webex Calling section · Checked 2026-10-14
42. 42
    Control Hub colours the ThousandEyes network path green (good) when latency is below 300 ms or round-trip loss is below 3%, and yellow (fair) otherwise when not poor.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Network path details: thresholds · Checked 2026-10-14
43. 43
    Control Hub colours the ThousandEyes network path red (poor) when latency is above 400 ms or round-trip loss is above 5%.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Network path details: thresholds · Checked 2026-10-14
44. 44
    Phones running the ThousandEyes agent under Unified CM support scheduled tests and dynamic tests for SIP calls, and phone tests should use the Webex template.

    Enable ThousandEyes integration for 9800 Series and 8875 phones (Unified CM) · Supported features (ThousandEyes portal) · Checked 2026-10-14
45. 45
    For phones running the ThousandEyes agent, phone Wi-Fi statistics are not available in the ThousandEyes portal, Run Once instant tests are not supported, and real user tests are not supported.

    Enable ThousandEyes integration for 9800 Series and 8875 phones (Unified CM) · Limitations · Checked 2026-10-14
46. 46
    The ThousandEyes Endpoint Agent built into phone firmware is supported on the Cisco Video Phone 8875 at firmware 5.0.1 or later and the Cisco Desk Phone 9861 and 9871 at firmware 3.2.1 or later.

    Enable ThousandEyes integration for 9800 Series and 8875 phones (Unified CM) · Supported phone models and firmware · Checked 2026-10-14
47. 47
    ThousandEyes supports its PhoneOS endpoint agent on 9800 series and 8875 phones registered to Webex Calling multi-tenant, Webex Calling Dedicated Instance, or Unified CM.

    Endpoint Agent Installation on Cisco Phone Devices (PhoneOS) · Prerequisites · Checked 2026-10-14
48. 48
    The ThousandEyes PhoneOS agent does not support ICE-optimized calls, proxy configurations, VPNs, WebRTC, BroadWorks or third-party call control.

    Endpoint Agent Installation on Cisco Phone Devices (PhoneOS) · Limitations · Checked 2026-10-14
49. 49
    The ThousandEyes PhoneOS setup sequence is: create a ThousandEyes API token, activate the Control Hub integration, register the phone, enable ThousandEyes with the account-group connection string and apply config, then create a Webex-template test.

    Endpoint Agent Installation on Cisco Phone Devices (PhoneOS) · Setup steps 1-7 · Checked 2026-10-14
50. 50
    The ThousandEyes PhoneOS agent does not support Cisco Desk Phone 9811, 9841 or 9851 models.

    Endpoint Agent Installation on Cisco Phone Devices (PhoneOS) · Limitations · Checked 2026-10-14
51. 51
    ThousandEyes documents that Webex Calling premium (PSTN-capable) call routing depends on the user's configured location country rather than the network the user is on.

    Monitoring Webex Calling · Identifying monitoring targets: Premium Calling · Checked 2026-10-14
52. 52
    Before activating the Control Hub integration, users must be assigned to a ThousandEyes account group and the ThousandEyes admin role must include view permissions for endpoint agent data.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Before you begin (prerequisites list) · Checked 2026-10-14
53. 53
    The ThousandEyes agent is already part of RoomOS on Board, Desk and Room Series devices and is turned on in Control Hub under Devices > Settings, per device or for all devices in the organization.

    ThousandEyes Agent integration for Board, Desk, and Room Series devices · How to enable · Checked 2026-10-14
54. 54
    The RoomOS ThousandEyes agent integration is not supported in IPv6-only networks and is unavailable when Security FIPS mode is on.

    ThousandEyes Agent integration for Board, Desk, and Room Series devices · Limitations · Checked 2026-10-14
55. 55
    The RoomOS ThousandEyes agent supports 1-to-1 Webex Calling calls and on-premises Unified CM calls among its supported scenarios, alongside Webex Meetings and several interop meeting types.

    ThousandEyes Agent integration for Board, Desk, and Room Series devices · Supported scenarios · Checked 2026-10-14
56. 56
    ThousandEyes suggests Webex Calling RTP test alerts on MOS below 2-3, errors present, packet delay variation above two standard deviations, DSCP not EF, and discards above 10-20%.

    Monitoring Webex Calling · Alert recommendations: RTP tests · Checked 2026-10-14
57. 57
    For Webex Calling media, ThousandEyes recommends an RTP Stream test from an Enterprise Agent to the Webex Cloud Agent in the same regional data center on port 5004 or 19560-65535 with DSCP EF (46) for audio.

    Monitoring Webex Calling · Recommended tests: RTP Stream · Checked 2026-10-14
58. 58
    For Webex Calling signaling, ThousandEyes recommends an Agent-to-Agent TCP test from an Enterprise Agent to the Webex Cloud Agent in the same regional data center on port 5062 or 8934 with DSCP CS3 (24) and path trace enabled.

    Monitoring Webex Calling · Recommended tests: Agent-to-Agent TCP · Checked 2026-10-14
59. 59
    On Unified CM, ThousandEyes is enabled on phones by setting ThousandEyes Enable to True and pasting the ThousandEyes connection string, at enterprise, common phone profile or individual phone scope, then Save and Apply Config.

    Enable ThousandEyes integration for 9800 Series and 8875 phones (Unified CM) · Setup steps · Checked 2026-10-14
60. 60
    Cisco documents a known issue where ThousandEyes tests showed 100% packet loss when a VPN was used even though calls were not affected.

    Integrate ThousandEyes with Troubleshooting in Control Hub · Limitations: VPN · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). ThousandEyes and Meraki for voice network assessment. WarmTransfer. https://warmtransfer.net/knowledge/network-assessment-tooling

@misc{warmtransfer-network-assessment-tooling,
  title  = {ThousandEyes and Meraki for voice network assessment},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/network-assessment-tooling},
  note   = {Verified 2026-10-14}
}