> For the complete documentation index, see [llms.txt](https://docs.itgrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itgrix.com/custom_common/call-data-call_full-in-customizations.md).

# Call data (call\_full) in customizations

{% hint style="info" %}
For Bitrix24, the call\_full object is available starting with Itgrix\_bx 3.10.0.

For Kommo, the call\_full object will appear in the Itgrix\_amo 2.13.0 version.
{% endhint %}

## Main object (call\_full)

```php
{
  "call_full": {
    "active_conversation_id": "<uniqueid of the current call (or an empty line)>",
    "channel": {<Call channel data from Asterisk (main channel - linkedid)>},
    "conversations": {
      "1111111111.11111": {
        "channel": {<Conversation channel data from Asterisk>},
        "is_parked": <Whether the conversation is on hold (true/false)>,
        "user": {<User data found by phone number (or null)>}
      },
      ...
    },
    "deal": {<Transaction data (or null)>},
    "entity": {<Entity data (or null)>},
    "is_ivr": <Is a missed call on a IVR (true/false)>,
    "record": "<Link to call recording (or empty string)>",
    "registration": {<Call registration data (or null) - only for Bitrix24>},
    "result": <Call result (SIP-status, int)>
  }
}
```

## Channel data (channel)

```php
"channel": {
  "answer_time": "<Answer time (or 0001-01-01 00:00:00)>",
  "end_time": "<End time (or 0001-01-01 00:00:00)>",
  "extra": {<Extra fields from the CEL table>},
  "from": {<Details of the number from which the call was made>},
  "id": "<channel uniqueid>",
  "is_primary": <Whether the channel is “main”, i.e. uniqueid = linkedid (true/false)>,
  "name": "<Channel name from the CEL table>",
  "start_time": "<Start time (or 0001-01-01 00:00:00)>",
  "state": "The status (line) is one of:
    ringing - in the process of dialing (the subscriber's phone is ringing, there is no answer yet);
    talking - in the process of talking (already had an answer, not yet hung up);
    ended - finished;
    processed - processed by the connector",
  "to": {<Data of the number called>},
  "trunk": {<Trunk number data>},
  "type": "Type (string) - one of:
    local - local (from internal number to internal number);
    incoming - incoming (from external number to internal number);
    outgoing - outgoing (from internal number to external number);
    unknown - unknown (unable to determine type)",
  "was_answered": <Was the answer (true/false)>
}
```

## Date-time format

The date-time is output in the format `YYYYY-MM-DD HH:MM:SS`.

If no value is set (no event occurred), the value is displayed `0001-01-01 00:00:00`.

{% hint style="info" %}
The time values correspond to the time zone on the Asterisk server.
{% endhint %}

## Number data (from, to, trunk)

```php
"from/to/trunk": {
  "base": "<Number without prefixes>",
  "custom": "<Customized number>",
  "is_local": <Is the number internal (true/false)>,
  "original": "<The number as it was received from Asterisk>",
  "variants": [
    <Number options corresponding to the list of prefixes from the connector settings,
    i.e. base, as well as “prefix+base” numbers for each prefix
    (list of strings)>
  ]
}
```

Example of prefix configuration:

<figure><img src="/files/VXnVaQTn7oi8qVouDnb1" alt=""><figcaption></figcaption></figure>

Example of a number to:

```php
"to": {
  "base": "9001234567",
  "custom": "89001234567",
  "is_local": false,
  "original": "+79001234567",
  "variants": [
    "9001234567",
    "+74959001234567",
    "84959001234567",
    "+79001234567",
    "79001234567",
    "89001234567"
  ]
}
```

{% hint style="info" %}
The connector first tries to use the number in the field `custom` (i.e., the result of autosubstitution and/or customization); if it is not present, the original number in the field `original`.
{% endhint %}

## User data (user)

```
"user": {
  "email": "<Email>",
  "id": "<User ID in CRM>",
  "name": "<User name>",
  "phones": [
    <List of user phone numbers - strings>
  ],
  "position": "<Position>",
  "raw": {<User data as in CRM>}
}
```

{% hint style="warning" %}
Only non-empty/non-zero fields are present in the `raw` object.
{% endhint %}

{% hint style="info" %}
Bitrix24 user fields are described in the [REST API documentation](https://apidocs.bitrix24.com/api-reference/user/user-fields.html).

The Connector considers the following field values in Bitrix24 as user phone numbers:

* Internal telephone (field `UF_PHONE_INNER`)
* Cell phone (field `PERSONAL_MOBILE` )
* Work phone (field `WORK_PHONE`)
* Phone (field `PERSONAL_PHONE` )

User phone numbers in the `phones` object are represented as strings (as in Bitrix24).
{% endhint %}

## Deal data (deal)

{% hint style="warning" %}
Only itgrix\_kmo connector for amoCRM works with deals.

In Bitrix24, the itgrix\_bx connector does NOT work with deals, so the value of the `deal` field will always be `null`.
{% endhint %}

## Entity data (entity)

```php
"entity": {
  "id": "<Entity ID>",
  "is_new": <Whether an entity was created when registering this call - true/false>,
  "name": "<Entity name>",
  "phones": [
    <List of phone numbers of the entity - objects>
  ],
  "raw": {<Entity data as in CRM>},
  "responsible": {<Responsible user data>},
  "responsible_id": "<Responsible user ID>",
  "type": "<Entity type by string>"
}
```

{% hint style="info" %}
Telephone numbers in the phones array are represented as an object similar in structure to the number in the `channel`: [Number Data](https://docs.itgrix.com/custom_common/call-data-call_full-in-customizations#number-data-from-to-trunk).
{% endhint %}

{% hint style="info" %}
In the type field for Bitrix24 there are possible values: `company`,`contact`,`lead`.
{% endhint %}

{% hint style="warning" %}
Only non-empty/non-zero fields are present in the `raw` object.
{% endhint %}

## Call registration data in CRM (registration)

The `registration` object is present only for Bitrix24 (for Kommo it will always be `null`).

```php
"registration": {
  "activity_id": "<Activity ID (or empty string)>",
  "created_company_id": "<ID of the company created during registration (or empty string)>",
  "created_contact_id": "<ID of the contact created during registration (or empty string)>",
  "created_deal_id": "<ID of the deal created during registration (or empty string)>",
  "created_lead_id": "<ID of the lead created during registration (or empty string)>",
  "entity_id": "<ID of the entity used>",
  "entity_type": "<Type of used entity by string (in Bitrix24 - company/contact/lead)>",
  "id": "<Call ID in Bitrix24>",
  "responsible_id": "<ID of the user responsible for the call>"
}
```

## Call result (result)

The result of the call in the form of SIP status (integer).

Detailed description in the article [Detail-call-statuses](https://docs.itgrix.com/faq/detail-call-statuses).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.itgrix.com/custom_common/call-data-call_full-in-customizations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.