anynode Release 4.8
Version Highlights
-
Search Function: The new search function in the anynode frontend is a serious help to find parameters in your configuration. By applying various filters you can narrow down the search to your specific wishes.
-
Conditional Events: You can now define your own conditional events and write those into the event log or let them be signalled via the various event transport mechanisms.
-
Redundant Media Recording: Multiple parallel recordings can now be specified. This allows redundancy of your recordings and it allows to have a unique set of configuration for each recording session.
-
Mute / Unmute Media Recording: An ongoing recording can now be muted and unmuted during the recording session via a REST API from your own application. This can prevent the recording privacy specific moments during a call center chat with an agent for example.
-
New REST Functions: The REST APIs available in the anynode frontend have been broadly extended to allow for you us
anynode Setup 4.8.17 (August 23, 2023)
Technical Setup
-
Core: anynode 4.8.17
-
Frontend: anynode frontend 4.8.17
-
UCMA: anynode UCMA 4.8.17
-
Java: JRE 8u382 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.17
-
Trace: anynode trace 4.8.17
-
Administration: anynode ad 4.8.17
Bug Fixes
-
A potential crash in the anynode monitor when trying to retrieve node information
-
An issue where the configuration pages for tag rewriting for call forking were not displayed in the anynode frontend
-
An issue where a newly configured SMTP client was not shown in the event transport assistant
anynode Setup 4.8.16 (August 15, 2023)
Technical Setup
-
Core: anynode 4.8.16
-
Frontend: anynode frontend 4.8.16
-
UCMA: anynode UCMA 4.8.16
-
Java: JRE 8u382 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.16
-
Trace: anynode trace 4.8.16
-
Administration: anynode ad 4.8.16
Improvements
-
The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u372 to 8u382
Bug Fixes
-
An issue when copying certain signalling objects in the anynode core
-
A potential crash in the anynode trace analyzer
-
A potential issue in the anynode monitor with detecting the state of a SIP node when used from multiple nodes
-
An issue when importing and cloning database connected directory, directory route supervision, media recording multiplexer and ELIN binding database objects
-
A potential issue during finalization of a SQLite database statement in anynode (both core and monitor)
anynode Setup 4.8.15 (July 03, 2023)
Technical Setup
-
Core: anynode 4.8.15
-
Frontend: anynode frontend 4.8.15
-
UCMA: anynode UCMA 4.8.15
-
Java: JRE 8u372 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.15
-
Trace: anynode trace 4.8.15
-
Administration: anynode ad 4.8.15
Improvements
-
Route supervision now also works if the response from the external REST server does not transmit a reason behind the status-code
-
The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.9
Bug Fixes
-
When going into maintenance mode, the anynode frontend internal write access right was not relinquished
anynode Setup 4.8.14 (June 20, 2023)
Technical Setup
-
Core: anynode 4.8.14
-
Frontend: anynode frontend 4.8.14
-
UCMA: anynode UCMA 4.8.14
-
Java: JRE 8u372 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.14
-
Trace: anynode trace 4.8.14
-
Administration: anynode ad 4.8.14
Bug Fixes
-
A potential crash during registration operation due to a reference counting issue
-
A potential issue with the count of transport connections in the anynode monitor and the anynode trace analyzer
-
An issue where the option set display name to could not be selected in the Rewrite Rule Assistant
-
An issue where no all objects were shown in the Condition Wizard
anynode Setup 4.8.13 (June 09, 2023)
Technical Setup
-
Core: anynode 4.8.13
-
Frontend: anynode frontend 4.8.13
-
UCMA: anynode UCMA 4.8.13
-
Java: JRE 8u372 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.13
-
Trace: anynode trace 4.8.13
-
Administration: anynode ad 4.8.13
New Features
-
New VoIP provider profile: Zoom Contact Center
Improvements
-
VoIP provider profile optimized: Zoom Phone Premise Peering
-
VoIP provider profile optimized: Zoom Phone Provider Exchange
Bug Fixes
-
An issue with automatic removal for recorded audio after a specific number of days
-
An issue with the IPC connection between the anynode frontend and the anynode monitor
-
An issue where certain calls were not shown in the call history (or in the anynode trace analyzer)
-
An issue with evaluation of the SIP end status code in the anynode monitor
-
A possibly crash of the anynode monitor during a route supervision operation
-
An issue when displaying the remote peer address for a received RTP packets in the anynode trace analyzer
-
An issue where a trace could not be loaded by the anynode trace analyzer under specific circumstances
-
An rights issue for the REST API call /api/maintenanceMode/set
anynode Setup 4.8.12 (May 11, 2023)
Technical Setup
-
Core: anynode 4.8.12
-
Frontend: anynode frontend 4.8.12
-
UCMA: anynode UCMA 4.8.12
-
Java: JRE 8u372 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.12
-
Trace: anynode trace 4.8.12
-
Administration: anynode ad 4.8.12
New Features
-
New VoIP provider profile: LWLcom
Improvements
-
The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u362 to 8u372
Bug Fixes
-
A potential crash during Route Supervision
-
A potential status display issue for Route Supervision
-
A potential issue with configuration in connection with replication
-
The anynode trace analyzer showing an invalid LOD for demo licenses
anynode Setup 4.8.11 (April 21, 2023)
Technical Setup
-
Core: anynode 4.8.11
-
Frontend: anynode frontend 4.8.11
-
UCMA: anynode UCMA 4.8.11
-
Java: JRE 8u362 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.11
-
Trace: anynode trace 4.8.11
-
Administration: anynode ad 4.8.11
New Features
-
New VoIP provider profile: New Voice
-
New VoIP provider profile: New Voice Mobicall (secure)
-
New VoIP provider profile: Zoom Phone Provider Exchange
Improvements
-
The duration of a timer for standby operation
-
The duration of a timer for refresh of the Azure Active directory
-
Improved recovery handling when CDRs are written into an external database when the lost connection to that database has been restored
-
Some small revisions in the web configuration
Bug Fixes
-
A potential issue with media negotiation in connection with secure RTP and RTCP
-
An issue with UTF8 when writing into external databases from the anynode monitor
-
An issue when validating external database tables
anynode Setup 4.8.10 (March 28, 2023)
Technical Setup
-
Core: anynode 4.8.10
-
Frontend: anynode frontend 4.8.10
-
UCMA: anynode UCMA 4.8.10
-
Java: JRE 8u362 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.10
-
Trace: anynode trace 4.8.10
-
Administration: anynode ad 4.8.10
Improvements
-
Unified fonts on the web user interface of the anynode frontend
Bug Fixes
-
A potential crash in the anynode UCMA module during release of endpoints
anynode Setup 4.8.9 (March 22, 2023)
Technical Setup
-
Core: anynode 4.8.9
-
Frontend: anynode frontend 4.8.9
-
UCMA: anynode UCMA 4.8.9
-
Java: JRE 8u362 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.9
-
Trace: anynode trace 4.8.9
-
Administration: anynode ad 4.8.9
Improvements
-
Outgoing REFERs can now be delayed until completion of other REFER or INVITE transactions, or even be totally inhibited
-
VoIP provider profile optimized: Deutsche Telekom (IP-basiert) (1TR114)
-
An outdated certificate for Azure Active Directory has been replaced in the wizard
Bug Fixes
-
A potential issue updating a token for OAUTH operation, inhibiting further updates of Azure Dial string Directories
-
A potential issue when showing the display name in the Dial string Rewriting Wizard
-
Some issues in the REST API
-
Some potential issues during monitoring and tracing of Route Supervision and Dial string Directories
anynode Setup 4.8.8 (March 6, 2023)
Technical Setup
-
Core: anynode 4.8.8
-
Frontend: anynode frontend 4.8.8
-
UCMA: anynode UCMA 4.8.8
-
Java: JRE 8u362 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.8
-
Trace: anynode trace 4.8.8
-
Administration: anynode ad 4.8.8
Improvements
-
It is now possible to only use RTP/SAVP when both RTP/AVP and RTP/SAVP are offered
-
Interoperability with non-conforming SDP from remote peers
-
The Java Runtime that is used by the web anynode frontend on Windows has been updated from 8u352 to 8u362
-
The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.8
-
VoIP provider optimized: gnTel SIP-Trunk
Bug Fixes
-
An error during certification expiry checking in the anynode trace analyzer
anynode Setup 4.8.7 (February 17, 2023)
Technical Setup
-
Core: anynode 4.8.7
-
Frontend: anynode frontend 4.8.7
-
UCMA: anynode UCMA 4.8.7
-
Java: JRE 8u362 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.7
-
Trace: anynode trace 4.8.7
-
Administration: anynode ad 4.8.7
Improvements
-
Optimized the evaluation of number information from SIP dialogs for monitoring
Bug Fixes
-
Some potential issues with Microsoft Teams SBA
-
A potential crash during Route Supervision
-
A potential issue during monitoring of SIP transactions with authentication
-
A potential problem during system-updates on Linux
anynode Setup 4.8.5 (December 21, 2022)
Technical Setup
-
Core: anynode 4.8.5
-
Frontend: anynode frontend 4.8.5
-
UCMA: anynode UCMA 4.8.5
-
Java: JRE 8u352 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.5
-
Trace: anynode trace 4.8.5
-
Administration: anynode ad 4.8.5
Improvements
-
When relaying REFER messages, optionally also user-to-user and referred-by headers can be forwarded
-
VoIP system profile optimized: New regions for the Zoom Phone Premise Peering
-
VoIP system profile optimized: Speedcom AG - Speedvoice
Bug Fixes
-
A potential crash during sending of MWI in core anynode
-
A potential crash in the anynode trace analyzer
anynode Setup 4.8.5 (January 16, 2023)
Technical Setup
-
Core: anynode 4.8.5
-
Frontend: anynode frontend 4.8.5
-
UCMA: anynode UCMA 4.8.5
-
Java: JRE 8u352 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.5
-
Trace: anynode trace 4.8.5
-
Administration: anynode ad 4.8.5
Improvements
-
Added the ability to forward DTMFs towards the recording session
Bug Fixes
-
A potential issue with TCP connections on mapped ports
-
A potential issue when showing recording sessions in the anynode trace analyzer
anynode Setup 4.8.4 (December 12, 2022)
Technical Setup
-
Core: anynode 4.8.4
-
Frontend: anynode frontend 4.8.4
-
UCMA: anynode UCMA 4.8.4
-
Java: JRE 8u352 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.4
-
Trace: anynode trace 4.8.4
-
Administration: anynode ad 4.8.4
Improvements
-
All Diffie-Hellman key lengths used in the anynode frontend now require at least 2048 bits
Bug Fixes
-
A race condition which caused the wrong termination reason to be sent to the remote party
-
A potential issue with session not showing up in the call history
-
An issue when executing system updates on Linux platforms
-
Some minor issues in the RESTful-API of the anynode frontend
-
Some minor issues with text-display and dialogs in the anynode frontend
anynode Setup 4.8.3 (November 24, 2022)
Technical Setup
-
Core: anynode 4.8.3
-
Frontend: anynode frontend 4.8.3
-
UCMA: anynode UCMA 4.8.3
-
Java: JRE 8u352 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.3
-
Trace: anynode trace 4.8.3
-
Administration: anynode ad 4.8.3
Improvements
-
The Jetty components used by the anynode frontend have been updated to 9.4.49.v20220914
Bug Fixes
-
An error with media reception with activated Negotiated Peers Only
-
An error with the timezone difference to UTC for the event log
-
An issue with update of session end reasons in the anynode monitor
-
An issue when displaying conditions for transport connections on the anynode frontend
-
An issue where not every condition could be selected for Operational State Condition
-
An issue with the REST API for setting certificates
anynode Setup 4.8.2 (November 16, 2022)
Technical Setup
-
Core: anynode 4.8.2
-
Frontend: anynode frontend 4.8.2
-
UCMA: anynode UCMA 4.8.2
-
Java: JRE 8u352 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)
-
Monitor: anynode monitor 4.8.2
-
Trace: anynode trace 4.8.2
-
Administration: anynode ad 4.8.2
Improvements
-
The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u342 to 8u352
-
A new option Assign a transport connection to incoming sessions has been added to the configuration for Microsoft Teams Nodes
Bug Fixes
-
A potential crash during mapping of unusual status codes (especially in connection with new Microsoft Teams functionality)
-
A potential crash when using encrypted sessions
-
Some potential issues in the RESTful API
-
A potential reference-counting issue with LDAP-authentication
-
Some cryptic error-message when using the PowerShell object
anynode Setup 4.8.1 (November 08, 2022)
Technical Setup
-
Core: anynode 4.8.1
-
Frontend: anynode frontend 4.8.1
-
UCMA: anynode UCMA 4.8.1
-
Java: JRE 8u342 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)
-
Monitor: anynode monitor 4.8.1
-
Trace: anynode trace 4.8.1
-
Administration: anynode ad 4.8.1
Improvements
-
The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.7
-
The SQLite library integrated into the Windows version of anynode has been updated to 3.39.4
Bug Fixes
-
A potential crash in the route supervision
-
Some corrections for the new RESTful APIs
anynode Setup 4.8.0 (November 01, 2022)
Technical Setup
-
Core: anynode 4.8.0
-
Frontend: anynode frontend 4.8.0
-
UCMA: anynode UCMA 4.8.0
-
Java: JRE 8u342 (private install with anynodefe, now based on openJDK)
-
Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)
-
Monitor: anynode monitor 4.8.0
-
Trace: anynode trace 4.8.0
-
Administration: anynode ad 4.8.0
New Features
-
The anynode frontend now supports free text searching
-
Recordings can now be muted via IPC
-
Multiple recordings can now be configured
-
The anynode monitor now includes customer-specific events for condition changes.
-
Those can be written into the event-log and signalled via SNMP, REST, WMI and SNMP
-
New VoIP system: Microsoft Azure Communication Services
Improvements
-
The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.5
-
Various adaptations to use the new features of OpenSSL 3
-
Recordings can now be enumerated based on the SIP Call Id An anynode specific SIP header P-Xz-Sipua-Dialog-Identifier can now be used to identify SIP-dialogs
-
Route Supervision can now transmit local identifiers like SipCallId, SipLocalTag, SipRemoteTag and SipUserAgentDialog
-
Route Supervision can now use all results of a DNS resolve for establishment of the connection to the remote server
-
Route Supervision now supports information delivery like destination address and end reason for parallel calls
-
Route Supervision now supports the ability of the remote server to override the accept-node and the routing forward profile
-
Ability to selectively set the trace-focus to specific objects RPI headers can now be used in responses just like PAI and PPI-headers
-
Optionally the via header will always contain the local IP address instead of host name and maddr parameter
-
Mapping of asserted address tweaked to improve interoperability with some specific remote peers
-
The LDAP dial string directory now has an additional option to ignore special characters (like space or hyphen) during lookup
-
The call history can be retrieved using the end-time instead of the start time of a call
-
The call history now also contains an entry how many calls are active on the node Improved details when logging registration and LDAP connection failures
-
Table layout of external databases will now be validated prior to usage The RESTful API of the anynode frontend has been extended by lots of new functionality
-
The rewrite rules for dial strings can now be exported and imported in JSON format TLS protocol order optimized for anynode frontend connector negotiation
-
The wizard for the provisioning server one can now reuse the Network Controller of the SIP phones node
-
It is now possible to optionally migrate existing Microsoft Teams nodes to support a new trusted Root CA which will be mandatory with the start of 2023
-
VoIP provider renamed: Voxbone Trunk in Bandwidth Global SIP Trunk (Voxbone)
-
The anynode trace analyzer can now show the Route Supervision messages within the signalling view
-
The anynode trace analyzer now implements a search functionality within a specific trace stream
-
The anynode trace analyzer has improved the display of SIP information in case of transmission errors
Bug Fixes
-
The certificate retrieval during configuration of SMTP connectors