System requirements
1. Asterisk requirements
The requirements can be checked automatically using our script itgrix_checker\
Download the check script
curl -OJLk "https://itgrix.ru/download/itgrix_checker"
Run the script
bash itgrix_checker
Setup is performed from a user account with the following permissions:
Viewing and editing configuration files Asterisk;
Installing additional software on the server, configuring its operation as a service.
1. Asterisk 13.0 and higher
asterisk -V
Answer: Asterisk 13, FreePBX 14 and similar Will do Asterisk, and FreePBX, Elastix, Issabel...
2. AMI is enabled and configured in Asterisk
asterisk -rx 'manager show settings'
Answer:
Manager (AMI): Yes
3. Important: Asterisk has enabled logging of calls to the CEL table, which is located in MySQL. List of required events:
CHAN_START CHAN_END ANSWER LINKEDID_END
BLINDTRANSFER ATTENDEDTRANSFER
PICKUP
1. Checking the work status CEL:
asterisk -rx 'cel show status'
Ответ:
CEL Logging: Enabled
CEL Tracking Event: CHAN_START
CEL Tracking Event: CHAN_END
CEL Tracking Event: ANSWER
CEL Tracking Event: BLINDTRANSFER
CEL Tracking Event: ATTENDEDTRANSFER
CEL Tracking Event: LINKEDID_END
CEL Tracking Event: PICKUP
...
CEL Event Subscriber: ODBC CEL backend
2. Checking information about recent events:
mysql
use asteriskcdrdb;
select id, eventtype, eventtime, cid_num, exten, uniqueid, linkedid, channame from cel order by id desc limit 10;
The table should not be empty, it should display the call events.
Login/Password to connect to mysql can usually be found in the /etc/asterisk/res_odbc_additional.conf
4. Conversation recording is enabled and the CDR has information about the recording file name
select recordingfile from cdr order by calldate desc limit 10;
If there were calls through the PBX, the last 10 record file names should be in the response.
5. For the customizer to work,
PHP 5.3 or higher is required
php -v
Example output:
PHP 5.6.40 (cli) (built: Jan 22 2019 23:51:52)
5.1. The php-json package is required ( necessary, customizations will work without it)
php -r 'var_dump(function_exists("json_decode"));'
Expected output:
bool(true)
5.2. To run requests in CRM from the customizer php-curl package is required (optional, without it the customizer will execute everything except HTTP requests)
php -r 'echo curl_version()["version"];'
Example output:
7.47.0
6. Converting records to mp3 with path update requires UPDATE permission on the CDR table
Check rights:
SHOW GRANTS FOR '<user>'@'<host>';
Add permission UPDATE:
GRANT UPDATE ON asteriskcdrdb.cdr TO '<user>'@'<host>';
Bitrix24 requirements
Portal configuration should be done by user with administrative rights.
For the self-hosted Bitrix24:
Main module version 16.5.11 and higher
REST API (rest)
"Telephony" module
"CRM"
“Push&Pull”
Application supports any Bitrix24 cloud version with any limitations.
Network requirements
You should allow outgoing connections on the server where connector installed (it’s Asterisk server usually) to:
Your Bitrix24 (cloud or on-premise) with http or https protocols.
Bitrix24 authorization server: https://oauth.bitrix.info.
Connector license server: https://lk.bx24asterisk.ru.
To the application server: https://iw.bx24asterisk.ru.
Outer network access (8077 and 8078 port forwarding) is required for full functionality: click-to-call functionality and call records listening by link.
Kommo requirements
In the Itgrix widget settings, in the 'External module address for Click-to-Call requests' field, the address should be specified with https protocol.
Network:
You should allow outgoing connections on the server where connector installed (it’s Asterisk server usually) to:
Your Kommo with http or https protocols.
Kommo authorization server: https://kommo.com
Connector license server: https://lk.bx24asterisk.ru
Our click-to-call sever (if used) https://apix.itgrix.ru
Outer network access (8077 and 8078 port forwarding) is required for full functionality: click-to-call (if not using our c2c server) functionality and call records listening by link.
Starting from version 3.0.0, the call card function requires to set up and ensure the ability for users to connect to the integration module via the WSS protocol. The new Kommo REST API does not provide the ability to display/hide a call card anymore, so it is done through a Web Socket.
The connection address is in the format wss://<Asterisk IP>:8078/crm/cardws. It can be configured in the application widget in the Kommo interface. The necessary conditions for a proper operation are as follows.
The address is accessible from user's computer. It can be a local network address, a VPN-accessible address, or (not recommended) an external address.
Settings of all nodes in the route between a user and the card socket address allow connections via the WSS protocol. This may require additional configuration of an existing Nginx server or another proxy server.
The server where the integration module is installed has a valid SSL certificate that is successfully verified by the user's browser, and this certificate is specified in the module's configuration interface
http://<Asterisk IP>:8077/config/module.The server where the integration module is installed and all intermediate network nodes in the route are configured to support the required number of connections, one for each browser tab with the Kommo CRM interface open for each user.
If this is not configured, the base functionality of the integration module will work, but the call card will not be displayed.
Operating system requirements
Connector installation is made without problems for:
CentOS 6 and higher.
Debian 7 and higher.
Integration failed on this operating systems:
CentOS 5
Debian 6
Gentoo
If you have another OS, then there should be such packages in OS repositories: unixODBC, mysql-connector-odbc, mysql-server. If that packages already installed, it will simplify connector installation.
Last updated
Was this helpful?