Call detail fields description
The following table describes the fields of call details.
|
Field |
Description |
|---|---|
|
|
UUID of the call. |
|
|
ID of calling entity. |
|
|
Type of calling entity:
|
|
|
Name of calling entity. |
|
|
Phone number of calling entity (can be after number manipulation, for example, to E.164). Note: Applicable only to AudioCodes service-number. |
|
|
ID of called entity. |
|
|
Type of called entity:
|
|
|
Name of called entity. |
|
|
For AC service-number, should have the phone number (from SDR: dest.serviceNumber). Otherwise, should be undefined. |
|
|
Service number. Note: Applicable only to SIP Connections with a configured Service Number or customized Service Number (otherwise, undefined). |
|
|
Entity for calls triggered by a transfer:
|
|
|
Number in the SIP From header in the INVITE message. |
|
|
Call setup time (SIP INVITE) in RFC 3339 UTC time format (with "Z" suffix). |
|
|
Call connect time (200 OK) in RFC 3339 UTC time format (with "Z" suffix). |
|
|
Time call ended (SIP BYE or failure) in RFC 3339 UTC time format (with "Z" suffix). |
|
|
Indicates if call ended successfully:
|
|
|
Duration of call (in seconds). |
|
|
Reason for call termination. |
|
|
Boolean
|
|
|
Indicates ( |
|
|
Conversation ID if the call is with a bot (otherwise, undefined). |
|
|
Time of the expected deletion of the call detail. Note: Applicable only if the call detail was marked for deletion (otherwise, undefined). |
|
|
Global Session ID (GID). |
|
|
Provides delay‑related performance metrics for the bot interaction, including Speech‑to‑Text (STT), Text‑to‑Speech (TTS), and bot‑processing delays. The statistics include average, maximum, and median delay values (in milliseconds) to help monitor and evaluate system responsiveness. |