Changelog Itgrix_kommo


Version (new features)TypeLatest release (patch)



3.0.7 - 03.07.2024


2.13.14 - 04.07.2024

Versions are denoted with three numbers X.Y.Z:

  • X - major version, big changes that may break compatibility

  • Y - minor version, new features and improvements

  • Z - patch, bug fixes

Last 3 minor versions are being updated with patches. Latest minor version contains newest features and all applicable bug fixes. Supported versions are only getting compatible bug fixes.

To update to version X.Y.Z: /opt/itgrix_bx/ --version=X.Y.Z


Versions are sorted by release date.




  • Fixed crash when retrieving a conversation record without one of the numbers (observed since version 2.13.0)

  • Updated default AMI permissions

  • Added logging of the moment when the Originate request is sent

  • Fixed rare crash when reading AMI data

  • Fixed rare freeze during prolonged network communication issues with AMI




  • Fixed rare crash on calls with empty numbers in transfers (observed since version 3.0.0)

  • Fixed rare crash when determining responsible user for calls that are unanswered on IVR (observed since version 3.0.0)

  • Fixed rare freeze during prolonged network communication issues with AMI

  • More detailed logging of call registration result

  • Made entity search correspond closer to call registration algorithm

  • Added API method /crm/format_crm_numbers for formatting numbers of all entities in CRM with configured autoreplacements and customizations




  • Fixed rare crash when working with a user without an internal number (observed since version 2.13.0)

  • Fixed error in alternative conversation ID search method during attended transfer (observed since version 3.0.0)




  • Fixed not hiding the call card after long calls

  • Fixed incorrect filtering when searching for unsorted (observed since version 3.0.0)

  • Fixed repeated restarts when updating the CRM token while the admin panel is open (observed since version 3.0.0)

  • Phone number search for entities is made consistent with CRM search (observed since version 3.0.0)

  • Improved error handling for CRM requests

  • Updated default AMI permissions

  • Default logrotate settings now include use of dates in extensions

  • Fixed rare settings validation errors

  • Fixed license check schedule errors (observed since version 3.0.0)

  • Fixed rare crash when reading AMI data

  • Added logging of the moment when the Originate request is sent


  • Fixed cancellation of entity, deal, and call creation requests through customizations




  • Fixed crash when on call end where the direction of the last conversation is unknown (observed since version 2.12.0)

  • Fixed skip of call card close event (observed since version 3.0.0)

  • Retry requests to CRM on authorization errors

  • Fixed error in transferring authorization code to CRM when changing portals

  • Added support for JSON input data in the API request /pbx/read_cel




  • Added cancellation of task creation from task customization

  • Fixed incorrect unsorted cache update when unsorted is manually deleted immediately after creation (was observed since version 2.2.3)

  • Fixed incorrect path to the fmc_patterns file for non-standard installations

  • Fixed unsorted cache update when unsorted is not created (was observed since version 2.12.3)

  • Fixed incorrect output of the authorization server address in case of network access errors

  • Fixed potential freezes on license check errors (observed since version 2.11.0)

  • Fixed error when closing call card on prolonged conversations



Admin Panel

  • Fixed rare errors in live status updates on the main page (observed since version 3.0.0)

  • Added links to the most recent documentation in tips in the admin panel


  • Fixed errors when reading non-string custom fields of entities (observed since version 3.0.0)

  • Fixed errors in handling of attended transfers where the transfer event is in the second call (observed since version 3.0.0)

  • Fixed potential freezes on license check errors (observed since version 2.11.0)




  • Fixed a number of rare admin panel bugs when encountering unexpected states of settings file

  • Fixed incorrect CRM name display in the admin panel

  • Fixed inability to save changes when deleting certain settings in the admin panel

  • Fixed admin panel crash when opening trunks page




  • Fixed deals not being linked to contacts/companies (observed since version 3.0.0)

  • Fixed unexpected acceptance of unsorted when updating responsible (observed since version 3.0.0)

  • Removed delay when processing attended transfers involving local channels (observed since version 2.13.0)

  • Fixed error when assigning call result (observed since version 2.8.0)

  • Fixed incorrect license check before launching optional customizations (observed since version 2.13.0)

  • Fixed execution of repeated CRM request attempts when the authorization token is revoked

  • Fixed incorrect log output when generating a CRM authorization link

  • Fixed incorrect output of the authorization server address in case of network access errors



Attention! The release includes important changes that may affect the functionality of the application. Details can be found in the documentation.

Due to an update of the Kommo REST API from version v2 to v4, the following aspects of the application have changed:

  1. To have the call card function enabled, it is now necessary 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 will be 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:

    • 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.

    (8077 and 8078 specified here are default ports; your actual ports may differ)

  2. Customizations that use the Kommo REST API may require an update. The data in requests and a set of capabilities in the new API version have changed.

    Among other changes, the set of parameters related to attaching a call (which is a type of note) to additional entities was reduced. Adding call information is still possible, but the call will appear differently, and the customization code using this feature has to be updated.

    If you have previously ordered customizations from us, please contact our support team so we can assist you with the update.


  • Moved from deprecated REST API v2 to the latest v4 version

  • Displaying/hiding call card is now done through WebSocket instead of REST API

  • Call card is displayed regardless of whether an entity was created

  • Call transfers are handled separately from conversations, allowing for more detailed control over conversation durations

  • When encountering a "connection reset by peer" AMI error, fast reconnection without a full restart is attempted if possible

  • Added updating responsible user for repeated deals/leads

  • Added synchronization of from numbers between initial outgoing PJSIP conversations

  • Default settings (on initial installation) include autoreplacement of client number on C2C: removal of non-digit characters

  • Default settings (on initial installation) have autoreplacement of FMC numbers disabled

  • Added --report flag for generating a report for technical support

  • Added a stats section to the /status API response, including the number of errors and calls per day and per hour

Admin Panel

  • License information is updated in real time

  • When there is no connection to CRM, elements requiring such connection are replaced with placeholders

  • Statuses are pinned at the top of non-main pages

  • Tooltips are updated

  • Minor layout improvements


  • Fixed incorrect number update on conversation end (was observed since version 2.13.2)

  • Fixed incorrect display of authorization status in CRM

  • Fixed crash when handling calls with unrecognized FMC numbers

  • Fixed unsorted cache update when unsorted is not created (was observed since version 2.12.3)

  • Fixed incorrect unsorted cache update when unsorted is manually deleted immediately after creation (was observed since version 2.2.3)

  • Fixed error with transferring responsible to contact and entity after creating unsorted (was observed since version 2.12.4)

  • Fixed extraneous license requests when updating CRM token (was observed since version 2.13.0)

  • Fixed incorrect path to the fmc_patterns file for non-standard installations

  • Fixed incorrect formatting of uniqueid in channel creation error message (was observed since version 2.12.4)

  • Fixed open file limit leak when updating config (was observed since version 2.13.0)

  • Added a clear error message when using a non-existent funnel


  • Implemented requests to CRM via REST API v4

  • CRM requests are executed through the module, to maintain rate limits

  • Added customizations for contact and deal updates

  • Added cancellation of task creation from task customization

  • Updated customizer documentation




  • Fixed duplicate calls when unsorted is enabled

  • Fixed extraneous entity update requests after creating an unsorted (was observed since version 2.13.0)



Admin Panel

  • Fixed error when saving settings on first launch

  • Updated status text when there are no recent call records in the CDR table


  • Fixed a rare freeze when disconnecting from AMI (was observed since version 2.13.0)

  • Improved error handling for AMI connection errors

  • Added support for reading from CEL "extra" column with NULL values

  • Fixed a crash when receiving non-standard custom fields structure for entities

  • Fixed a rare case of C2C client restarting in a loop (was observed since version 2.13.0)




Admin Panel

  • Entity name templates settings now show default values when empty

  • Added ability to resize query field on MySQL page

  • Fixed errors when saving autoreplacements and task creation settings

  • Fixed minor layout issues on admin panel pages


  • Fixed duplicate reading of call events that are in the processing queue at the time of restart




  • Fixed error with reading responsible users from state.json (was observed since version 2.13.9)




  • Fixed admin panel crashing (was observed since version 2.13.7)

  • Fixed value of is_new field in call data for contact and deal when creating unsorted (was observed since version 2.13.0)

  • Fixed a rare issue with conversation prioritization in a call (was observed since version 2.13.0)

  • Fixed output of NULL values in on MySQL page in admin panel

  • Fixed choosing incorrect responsible for entities during call transfers (was observed since version 2.13.0)



Admin Panel

  • Interface language is preserved between sessions


  • Fixed CRM status output in /status request

  • Fixed showing call card to users uninvolved in current call (was observed since version 2.13.0)

  • Fixed repeated processing of "conversation ended" stage during blind transfer

  • Fixed saving entity data in state.json (was observed since version 2.13.0)

  • Changed logging levels of some events



Admin Panel

  • Fixed not displaying the deal name template field in the admin panel when repeated deals are disabled (was observed since version 2.13.4)


  • Fixed call card not showing (was observed since version 2.13.0)



Admin panel

  • Added configuration option for entity title templates (was present in config file since version 2.13.0)


  • Fixed resetting last_id when restarting without state.json

  • Added information about CRM authentication token in /status request output

  • Fixed incorrect variable name in default lead title pattern (was observed since version 2.13.0)




  • Fixed bug in reading requests from C2C server (was observed since version 2.13.0)




  • Fixed multiple deal creation in calls with multiple conversations (was observed since version 2.13.0)


  • Fixed the value of is_new field in deals in customization data (was observed since version 2.13.0)



Admin panel

  • Fixed the display of portal switching in the interface


  • Fixed crash when reading transactions from state.json (was observed since version 2.13.0)




  • Enhanced standardization of application logic

  • Added customization of the CORS whitelist (to manage the rights for making requests to the application from external resources, such as your website)

  • Added API /crm/request to send requests to CRM through the connector's common queue, which reduces the slowdown of additional requests from customizations

  • New customizations added: customization of creating unassembled, customization after call registration

  • Real-time monitoring of config and token files was implemented

  • Optimized application launch procedure

  • Changed log format

  • Added templates for the names of contacts, companies and deals

  • Added separate auto substitutions for trunk names, FMC numbers and C2C

  • Path parameter added to the /status request

  • Improved support for missed calls registration to FMC numbers

  • Added Originate success check by AMI event

  • Added launch flags for more detailed data cleansing

  • Added data compression of customizations when processing large calls

  • Implemented support for managed unanswered transfers between employees

Admin panel

  • Added automatic sorting of the b/w list

  • Added display of unsaved changes presence

  • Added autoformatting of the portal address

  • Added error displaying license price loading

  • Markup of log tables was updated

  • Added error output on pressing inactive buttons

  • Fixed an error of incorrect positioning of the chat button

  • Help on customizations was updated


  • Smooth application stopping procedure implemented

  • Centralized synchronous storage of call data was implemented

  • Fixed problem with re-reading calls/hanging state.json

  • Fixed incorrect attachment of record links in some cases (separated logic for trimming phone numbers)

  • Fixed hanging on AMI reconnection after connection break

  • Fixed a rare bug that sometimes caused the wrong end time

  • During C2C the number to is updated by customization results

  • Added verification of remote Asterisk version via AMI

  • Fixed saving CEL with special characters through the admin panel

  • Fixed issue with number list generation when searching for a record file

  • Fixed rare memory leak when event processing time limit was exceeded

  • Fixed rare hiccups during multiple processing of a single call event

  • Fixed MySQL connection leaks

  • Fixed missing CallStarted call processing step on some C2C calls

  • Fixed problem reconnecting to AMI when authorization data is changed

  • Fixed issue with reconnecting to Apix when changing a portal

  • The way to send tags to CRM has been changed to a more universal way

  • Fixed rare issues with prefixes

  • Added time zone accounting in CEL time stamps

  • Application status text is always displayed in /status in Title Case

  • Fixed delay in clearing user cache when changing the portal


  • Full call_full data along with legacy data is transferred to the customizer for backward compatibility

  • Requests to CRM through the module are added and activated in the customizer

  • In the auto assignment, a trunk is processed and all request data and full entity data are sent to the customizer

  • The /status of the customizer shows false in all methods if the customizer is disabled

  • In the need_registration and number customization we added the step and the call data

  • Removed duplicate number customizations, now they are executed when a number appears on CallStarted or ConversationRequested

  • Added customization after call registration

  • Added unassembled customization

  • Added possibility to cancel requests in CRM customizations

  • Combined output is used when performing customizations

  • Updated the format of customizer logs

  • Customizer prioritizes new call data

  • Standard customizations were updated

  • New options added to call recording path customization to eliminate path duplication


  • When an update error occurs, the absolute path to update.log is displayed

  • Fixed supervisor version output in API

Last updated