A hotel chain needs call failures investigated with the Webex experience and the network path in the same effort. Which approach fits?
Select an answer to reveal the explanation.
Short Explanation
You want the guest's story and a view of the hallway in the same conversation. You use Webex Control Hub with ThousandEyes so the call experience and the path are investigated together. A complaint spreadsheet, turning Webex monitoring off, or a collector that does not share the path keeps those views apart.
Full Explanation
Call failures of this kind need the experience Webex recorded and the network path for the same call, because either side can be the fault and each side explains the other. Webex Control Hub together with ThousandEyes for the call experience and the path fits, because the collaboration view and the path view are used as one investigation instead of two unrelated notes. A spreadsheet of call complaints that includes neither the Webex experience nor the network path stores the fact that someone complained and omits both datasets the investigation requires. Turning Webex monitoring off and keeping only a separate collector aimed at the path throws away the call experience and leaves a path with nothing to correlate to a failed call. A second collector that records the calls and does not share them with the path view may capture audio symptoms and still cannot place them on the path, which is the gap the hotel is trying to close. Exam caveat: collecting calls in one product and paths in another is not a joint investigation unless the two views are actually used together. Operational check: for one failed call, open the Webex experience and the ThousandEyes path for that same call and the same time.