v/1.10.0 (2026-03-16)
Dynamic platform data model
-
Added the ability for dynamic data model collections bound to a postgresql storage to use an intermediate message broker and batch data insertion.
-
Corrected behavior of the dynamic data model service when working with ClickHouse storage and optional fields like 'datetime'.
-
Added operations of the SETUP method on historical type collections: read_partitions, drop_partition.
-
Added periodic checking and restoration of the consumer state in ClickHouse from KAFKA in dynamic collections of the transactionlog type.
-
Added opts.readonly property for dynamic model classes, applied entirely to the collection.
-
Added opts.unique_properties property for dynamic model classes with types ram, runtime, category, history.
-
Added the ability to sort entities in the REST API using functional wrappers, for example `[ ["asc",["isnull",["property","name"]]],
["asc",["upper",["property","name"]]] ]` for case-insensitive sorting by name with wrapping NULL values at the end. - Implemented automatic removal of attachments when deleting dynamic class entities by timer (for ram and runtime types).
-
Implemented automatic removal of attachments when deleting partitions of dynamic classes using the SETUP method (for history and transactionlog types).
-
Implemented automatic removal of attachments from S3 storages when clearing dynamic classes.
-
Added the opts.log_read_details_ms property for dynamic model classes, which sets a time limit for executing a request to read a collection, exceeding which places the request parameters in the log.
-
Support for the REST API 'countonly' parameter has been implemented in aggregating selections from collections of the dynamic data model.
Telephony
-
Implemented the function of collecting and managing ad-hoc conferences using the conference factory feature code, including commands from the CTI panel.
-
A model for group setting of telephony service restrictions and available call directions through the CoS/CoR/Feature (Class Of Service, Class Of Restrictions) access matrix has been implemented.
-
Added a master domain option (settings.mgc_options.trunk_no_voice_stop_after_sec) for global control of dialogue termination when the set time of absence of expected traffic from at least one of the legs (excluding holds and CN) is exceeded.
Other
-
Added the ability to download entire node log archives. Including through the administrator bot in Telegram.
-
Added MAX messenger IM channel adapter.
-
An issue was discovered and fixed in the email microservice for working with IMAP, which could lead to a loop in the attempt to parse an invalid MIME message. The invalidity of the message may be due to the presence in the MIME content of a text representation of the final line of the response to the IMAP request.
-
Added the ability to install a client certificate for a specific integration channel and thereby further restrict access to the third-party Websocket / HTTP API.
-
The 'add_headers' option has been added to the configuration parameters of the ws role for adding static headers to each response to an HTTPS request.
-
The ability to not interrupt execution if an error occurs in any individual operation from a list of multiple operations has been added to the Parser scripting component.
-
A backup copy of the license is stored in the master domain database, used when changing the configuration by moving MDC nodes.
-
Added the ability to generate SNMP trap via API.
Product layer
-
History of changes to the product layer: 2026_03_10_PL_history.txt (1.10.2 Release)
v/1.10.2 (2026-04-12)
-
Fixed the behavior of the system when the connected NFS server is unavailable in terms of working with call recordings.
-
DSCP markers are set to prioritize outgoing IPv4 traffic packets: 'af31' for signaling and 'ef' for RTP.
v/1.10.3 (2026-04-24)
-
Added the ability for dynamic data model classes with storage in PostgreSQL (category and history types) to specify in lookup_properties not only individual fields, but also sets of fields - to create indexes consisting of several fields.
-
Added the ability to configure address modifiers for Telegram accounts.
-
Added the ability to configure a timeout for requests to read a selection from dynamic collections, primarily the history and category types. Set for the entire DMS instance, and also sent in a REST request to the websocket API.
-
Optimized the operation of reading the number of rows in collections of history types.
-
The properties 'r/ip', 'l/ip', 'route' have been added to the rtp statistics - they contain information about the addresses involved in the transmission of rtp traffic and signaling, respectively.
-
Linking an incoming INVITE request to a provider account has been supplemented with the step of checking the username from Request-URI with the domain from From-URI.
-
Fixed the ThirdParty websocket API problem with subscriptions when the domain center or subscription management service is unavailable.
v/1.10.4 (2026-05-14)
-
Added a heuristic mechanism for adjusting the timestamp in the sent rtp stream based on real time. Under normal conditions, the timestamp is generated based on the carrier of the incoming rtp stream. But in some cases, for example in a webrtc stream from a browser, when put on hold, the stream is temporarily suspended, but further packets contain a timestamp that does not take into account the actual time the stream was suspended.
-
The format for setting up the system telegram bot has been changed, it is now possible to set a proxyUrl to modify the target Url of the service. The new parameter 'system_telegram_bot' automatically takes the value of the previous parameter 'telegram_bot_token'.
-
Fixed an issue where websocket connections to a SIP port might not occur if selective network interfaces for the port listener are configured in the configuration for SG.
-
Resending SIP responses to repeated requests now takes into account the sender’s address and port and adjusts, if necessary, the outermost Via header in terms of the received and rport options and the sending address.
-
Fixed an issue where loading a REST HTTP attachment using the GET method was interrupted under heavy load conditions.
-
Added configuration setting for the range of ports used to create different TFTP sessions.
-
A problem with the keep-alive request to the MDC microservice database has been detected and fixed.
v/1.10.5 (2026-05-19)
-
A vulnerability has been discovered and fixed that allows unauthorized access to files through path manipulation.
-
An issue with the operation of saving script context (for the conversation recovery service) in multi-server configurations has been discovered and fixed.
-
An emerging problem in restoring a conversation on the webrtc shoulder when migrating to another media context/media gateway has been detected and fixed.
-
A HUNT group management tool has been added to the domain administrator settings application.
-
A header indicating the reason has been added to the BYE request sent when a DTLS connection is timed out on the webrtc arm.
-
The internal_representative option has been added to the sipuser settings to control the substitution of the initiator number during internal calls in the domain between users.
-
The algorithmic rigor of checking the uniqueness of values (class.opts.unique_properties) in the dynamic data model management service has been increased under high loads.
v/1.10.6 (2026-05-20)
-
Optimized the operation of page-by-page data retrieval from collections of runtime and ram types with a large number of records and pages using the 'snapshot' parameter.
v/1.10.7 (2026-06-03)
-
Fixed a bug when working with placing files in an NFS folder (including if NFS is not actually connected). It manifests itself in the fact that call recordings accumulate in the recmover queue and do not reach the target location if default settings or NFS are used, and not S3 storage.
v/1.10.8 (2026-06-04)
-
Implemented a work-around for checking LetsEncrypt Generation Y certificates in outgoing client requests. Symptom: failed connection/handshake by the web request scripting component (failed_connect) while a CURL request is successfully executed at the same time.
-
A user’s connection to a MAX channel is treated as the first message containing the payload, rather than simply a system action to create a RemoteParty.
-
Fixed an ESG error that caused a failure in call processing when a repeated INVITE request was received before the final response was sent.
-
Double sending of ACK from ESG to a re-arrived 200 OK response was detected and eliminated.
v/1.10.9 (2026-06-09)
-
In IM, when working with messenger services, a work-around has been added for checking certificates (similar to that implemented in v/1.10.8).
v/1.10.10 (2026-06-15)
-
Testing of redirection rules has been supplemented with the ability to set the number and domain of the redirected subscriber.
-
Fixed shortcomings in the search algorithm for presentation rules: the action=abort parameter was taken into account, a search for inner rules was added in the domain of the forwarding subscriber.
-
Fixed a recent problem in version 1.10.6 in issuing snapshots, leading to an increase in the number of open file descriptors.
v/1.10.11
-
In the 'Receive email' script component, some emails caused an error when parsed. Detected, fixed.
-
Added 'openid' dialect for authorization providers, and 'oauth' dialect now queries 'uri_info' anyway.
-
Fixed token_type in the Authorization header when requesting uri_info as part of OAuth authorization.
-
Fixed the problem of long waiting times for a response (more than 30 seconds) when dialing outgoing campaign numbers. Incorrect response codes were included in the statistics.
-
For the MAX messenger, the default URL has been changed, and the ability to modify the URL using Account.options.proxyUrl has been added.
-
A new root certificate has been added to the list of CA certificates.
-
Fixed the output of some domain center entity classes when reading a selection using the mask parameter.
-
Fixed format of l/ip and r/ip values in rtp statistics astat and bstat.
-
The parameters passed to the external numbers normalization script have been supplemented and adjusted.
-
Implemented binding to an existing session instead of creating an additional session in a new domain when consulting transfer of a cross-domain call.
-
A situation with a webrtc call being dropped when placed on hold through the border media gateway has been identified and resolved.