CUCM connection options
Trace calls and door bells
Define the CTI account and devices for trace calls and read the live call list of those devices.
In EasyUC: Administration → CUCM & Provisioning → CUCM Connections → Actions → Call tracing; Devices → Trace Calls
What it is for
Trace calls watches the calls of selected phones over CTI and shows them live in a list: who calls whom, when the call was connected, when it was hung up. Unlike Live Calls, it applies only to the devices you enter explicitly.
The same setting controls the door bells. When a phone entered as a door bell places a call, the called phone receives an image from a stored address and an additional button.
You first set up the CTI account and the set of devices at the CUCM connection. After that you read the calls in progress under Devices → Trace Calls and manage door bells under Devices → Door Bells.
Prerequisites
- A licence with provisioning. The Trace Calls entry appears in the action menu of the connection only then.
- Access to the CUCM connections in the administration to change the setting.
- For the list: role
ROLE_APP_LIST_TRACE_CALLS. For door bells:ROLE_APP_LIST_DOOR_BELLS. Creating, editing and deleting door bells requiresROLE_APP_ADMIN. - The phones to be watched exist in the CUCM and allow control over CTI.
- For door bells: an image address that delivers the camera picture.
Step by step: set up trace calls at the connection
Step by step: read traced calls
Step by step: create a door bell and view its call history
Fields and options
| Field / action | Meaning and use |
|---|---|
| Enable | Switches trace calls for the connection on or off. |
| User Id | CTI user for the monitoring. Always starts with euc_. |
| Password / Retype Password | Password of this user, entered twice as a check. |
| Devices | Devices of the connection whose calls are traced. Multiple selection. |
| Door Bells | Devices treated as door bells. Multiple selection. |
| Image Url | Address from which the image for the called phone is fetched. |
| Code | Code assigned to the door bell. The additional button on the called phone triggers the stored action. |
| Button Name | Label of the additional button on the called phone. |
| Period to re-send image (seconds) | Interval in seconds after which the image is sent again. |
How to read the call list
| Field / action | Meaning and use |
|---|---|
| Status | As text: Calling (call is being set up), Ringing, Answered, Hang Up, Declined, Failed. |
| Row colour grey | Call is being set up. |
| Row colour blue | Ringing. |
| Row colour green | Call in progress, or ended after a conversation. |
| Row colour yellow | Hung up without being connected, or declined. |
| Row colour red | Failed. |
| Caller / Called | Number, with display name and device below it. |
| Created At / Connected At / Disconnected At | Times of start, answer and end. A dash means the event did not occur. |
| In Call | Talk time in seconds. |
Check the result and narrow down errors
- You recognise success when a test call on one of the phones entered appears as a row immediately and turns green once answered.
- An empty list is no proof that all lines are free. It shows only calls of the devices entered. Check the set of devices and the CTI account.
- The notice that the device was already configured and no changes will be made means: the phone is already part of trace calls.
- If the dialog reports devices that no longer exist in the CUCM, it offers the option Should EasyUC remove these devices from trace calls?. Tick it and save.
- If no call appears at all, check on the CUCM whether the CTI user exists, the password is correct and the devices allow CTI control.
- If the called phone receives no image, check whether the image address can be reached from the network of EasyUC and of the phone.
- For all calls in the cluster without selecting devices, use Live Calls.