LogoLogo
  • What is Itgrix
  • Contacts
  • Our story
  • Connector installation
    • System requirements
    • Itgrix for Bitrix24 and Asterisk
      • How to perform offline authorization
      • How to obtain a license offline
      • Configuring the connector to work in a closed network
      • Call tests
    • Itgrix for Kommo and Asterisk
      • Restricted mode setting features
      • Call card
      • Call tests
  • Additional functions
    • Automatic call transfer to responsible manager
    • Setting up click-to-call features
      • Features of customization after Bitrix24 23.300.0 update
    • Autoreplacement for phone numbers
    • How to view employee call statistics in Bx24
    • FMC number recognition
    • Configuring WebRTC in Asterisk (FreePBX)
    • Itgrix AsterPhone for Bitrix24
    • Itgrix AsterPhone for Kommo
  • For admins
    • Running an additional copy of the module
    • Deploying a module backup
    • Call processing for the period
    • Examples of the structure of registered calls from CEL
    • Wrong time in created cases in Bitrix24
    • SSH access
    • Useful commands
    • Script to test the module service
    • Changing login and password to enter the admin panel
    • Module files
    • Status monitoring
    • Application update
    • In the CEL table, there is no internal employee number in the cid_num column
    • How to fix click-to-call
    • Custom SSL certificates for https requests
    • Examples of configuring WSS connections
    • Converting recordings to MP3 before sending to Bitrix24
    • How to fix call recording problems
    • Install and configure CEL
    • B24 authorization bugfix
  • Useful customizations (any CRM)
    • Audio file name customization
    • Call data (call_full) in customizations
    • Change the number / context for calling to asterisk
    • Change phone number before sending data to CRM
    • Black and white lists
  • Useful customizations itgrix_bx (Bitrix24)
  • Useful customizations itgrix_kmo (Kommo)
  • FAQ
    • How to pay
    • How to check licence status
    • Differences in connection to B24 via SIP-connector and Itgrix
    • How to turn off the display of calls in the calendar
    • How to view statistics on employee calls
    • Updating the app
    • Offline install (only for Bitrix24)
    • Offline update
    • Reliable softphones for Asterisk
    • Detail-call-statuses
  • Changelog Itgrix_bx
  • Changelog Itgrix_kommo
  • Policy of interaction with Asterisk
Powered by GitBook
On this page
  • Call processing for the period
  • Itgrix module API request
  • Using the call ID

Was this helpful?

  1. For admins

Call processing for the period

Call processing for the period

Itgrix module API request

If for some reason the Itgrix module has been disabled, or if during the first installation there is a desire to process already passed calls, you can use a special request /pbx/read_call in the API of the Itgrix module. It can be used to trigger the processing of certain calls.

For example, you can make a query using curl (here <Asterisk> is the address of the server where the Itgrix module is installed, login:password is the login:password for the integration module's admin panel):

curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?<parameters>"

The method has two options for using parameters:

  • specify one or more call identifiers id;

  • specify the start_date and (optionally) end_date (in this case the module finds all CEL records in the specified dates and processes calls by ID) (in this case the module finds all CEL records in the specified dates, takes linkedid from them and processes calls by ID).

Using the call ID

If you need to process a single call, the easiest thing to do is to make GET-query with parameter id:

curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?id=1234567890.1"

If you need to process several calls, you can pass a JSON-object with an id array via POST request :

curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call" \
-H "Content-Type: application/json" \
-d '{"id":["1111111111.1", "2222222222.2"]}'

Использование границ периода

Границы периода определяются параметрами start_date и end_date . При этом параметр end_date опциональный, т.е. его можно не указывать, и в таком случае модуль обработает все звонки, начиная с start_date.

Параметры могут быть указаны в трёх видах:

  • Дата-время в формате ГГГГ-ММ-ДД чч:мм:сс. При отправке GET-запроса с таким параметром нужно заменить пробел на специальную последовательность %20, при отправке POST-запроса с параметрами в формате JSON это не требуется. Например, обработаем звонки за 25 мая 2021 с 10:30 до 22:00:

    curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?\
    start_date=2021-05-25%2010:30:00&\
    end_date=2021-05-25%2022:00:00"
  • curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?start_date=1622138519"
  • Количество дней назад (отрицательное целое число). Например, обработать звонки за позавчера:

    curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?start_date=-2&end_date=-1"

    Пример обработки звонков за неделю:

    curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?start_date=-7"

    Также есть специальный вариант start_date=-0 - обработка звонков за сегодня (с полуночи по местному времени):

    curl --digest -u login:password "<Asterisk IP>:8077/pbx/read_call?start_date=-0"
PreviousDeploying a module backupNextExamples of the structure of registered calls from CEL

Last updated 1 year ago

Was this helpful?

Метка времени в формате UNIX-time (можно получить ; например, в звонке 1267568856.11 число 1267568856 является меткой времени). Например, обработаем звонки с 27 мая 2021 06:01:59 GMT, т.е. UNIX-time 1622138519:

из ID звонка, - это число до точки