System requirements
Asterisk requirements
Requirements
How to test
Asterisk version 1.8+, FreePBX, Esabel, Elastrix
$ asterisk -V
Asterisk 13 or FreePBX 14
CEL table enabled and configured to collect
data to MySQL
$ 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: BRIDGE_START CEL Tracking Event: BRIDGE_END CEL Tracking Event: LINKEDID_END
CEL Tracking Event: PICKUP
...
CEL Event Subscriber: ODBC CEL backend
$ asterisk -rx 'odbc show'
ODBC DSN Settings
-----------------
Name: asteriskcdrdb
DSN: MySQL-asteriskcdrdb
Number of active connections: 2 (out of 5)
$ mysql -u root -D asteriskcdrdb -p
> use asteriskcdrdb;
> select eventtime from cel order by id desc limit 10;
You should see 10 lines from CEL with current date.
AMI enabled and configured
$ asterisk -rx 'manager show settings'
Manager (AMI): Yes
TCP Bind address: 0.0.0.0:5038
Call recording have to be enabled and to CDR. You have access to recording files.
$ mysql -u root -D asteriskcdrdb -p
> SELECT recordingfile FROM cdr ORDER BY calldate desc limit 10;
You will see 10 lines from CDR with the path to file
CURL have to be enabled in Asterisk
$ asterisk -rx 'core show function CURL'
-= Info about function 'CURL' =-
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.
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
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