The following are a few best practices you should consider when introducing quprobeRTC into your workflow. These can help to improve your efficiency.
Office Location Network Monitoring
Monitoring network conditions over time is crucial for locations that regularly communicate with your data centers, such as call centers, schools, or hospitals. By setting up a probeRTC monitor at the location, the system continuously probes the connection between the office network and the communication data centers, storing and analyzing data in real-time. This helps identify issues that occur at different times of the day or changes in network conditions over time.
Remote Agent Troubleshooting
When call center agents experience network issues that can’t be easily diagnosed with a single ad-hoc test, probeRTC can continuously monitor the local home network for hours or days, providing deeper insights into persistent network problems.
Locations Comparison
Deploy multiple probeRTC probes to compare their results over time. This allows you to identify if a network issue is localized—such as on the office floor or near a network switch—or if it’s a broader problem affecting multiple sites. Comparing performance across various offices, or between offices and a stable high-speed network, can help determine if the issue lies within office network configurations or the communication data center itself.
Browser or PC Daemon Application?
probeRTC is available in two variations: browser-based and daemon.
-
Browser Application: Requires no installation. A probe is created in probeRTC, and its URL is sent and opened on a machine within the monitored network. This zero-footprint solution is ideal when a quick deployment is needed without security or IT approvals.
-
Daemon Application: Installed on a machine within the monitored network, this persistent probe continues to run even if applications are closed or the machine is rebooted, as long as the machine remains on.