Identifying Inconsistencies Between the Target Caller and Original Target Number

Prev Next
This content is currently unavailable in Portugese. You are viewing the default (English) version.

Introduction

The WXP Collaboration Platform provides visibility into call routing through the Target Caller and Original Target Number fields. This article explains how to interpret these values using the specific data from your monitored call control system.

Question

Why are the target caller and original target number not consistent in WXP Collaboration?

Answer

The data in the Target Caller and Original Target Number are displayed differently, according to what data is available to the WXP Collaboration system for the system monitored.

The intent is always to use the 'friendly' (display name) wherever possible - this can be achieved with call control systems that provide this mapping, as, for instance, Pexip systems do.

Some control systems - notably CUCM- do not provide the display name; WXP Collaboration will therefore use the alias in these fields when available.

In this case, the timestamps for the last seen files should be used to determine if there has been a problem - if it is known that calls were processed since the last timestamp, then this should be investigated.

WXP Collaboration has no way to identify if there is an issue with the data being sent from the call control system, so it is important to check the system logs to ensure that the data is being sent correctly.

Contact Us

For any assistance, create a support case or email support@wxp.hp.com.