anynode Release notes 4.12 - 2.0

anynode Setup 4.12.8 (November 8, 2024)

Technical Setup

• Core: anynode 4.12.8

• Frontend: anynode frontend 4.12.8

• UCMA: anynode UCMA 4.12.8

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2024.8.15.1

• Monitor: anynode monitor 4.12.8

• Trace: anynode trace 4.12.8

• Administration: anynode ad 4.12.8

Improvements

• Export from event log is now also possible if the webserver connector only has "Graphical user interface" configured

Bug Fixes

• A possible crash of the anynode monitor when retrieving information about the Request Router

• A possible crash of the anynode monitor when during processing of specific intial messages of a transaction

• During parallel calls the final end-reason of the last failover-call is now being properly handed back to the initial incoming call

• A problem when updating rewrites in routes when using a configuration prior to 4.12.x

• A potential issue when adding routes with active filter

• The transport protocol for the SRV loadbalancer can now be set to default

anynode Setup 4.12.7 (November 4, 2024)

Technical Setup

• Core: anynode 4.12.7

• Frontend: anynode frontend 4.12.7

• UCMA: anynode UCMA 4.12.7

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2024.8.15.1

• Monitor: anynode monitor 4.12.7

• Trace: anynode trace 4.12.7

• Administration: anynode ad 4.12.7

New Features

• New VoIP-Provider added: Genesis Cloud

Improvements

• Transfer for WebRTC sessions can now be displayed in the anynode trace analyzer

• Shared IP addresses are now only deactivated towards the operating-system if the anynode is currently using it

• New option integrated to optimized header-creation for SIP response messages

• Export from Call-History is now also possible if the webserver connector only has "Graphical user interface" configured

Bug Fixes

• A potential crash when processing single ELINs in anynode

• A potential issue with reference-counting

• A potential deadlock in TLS channels

• Some issues with WMI and SNMP fixed in the anynode monitor

• An issue providing system information in the call history

• An issue with removing SIP messages from the database

• An issue with specific SIP messages not being recorded into the database

• An issue with timestamps when exporting PCAP from anynode trace analyzer

• An issue with the test-function for LDAP directories without Digital Identity and Trust configuration

anynode Setup 4.12.6 (October 9, 2024)

Technical Setup

• Core: anynode 4.12.6

• Frontend: anynode frontend 4.12.6

• UCMA: anynode UCMA 4.12.6

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2024.8.15.1

• Monitor: anynode monitor 4.12.6

• Trace: anynode trace 4.12.6

• Administration: anynode ad 4.12.6

Improvements

• Memory consumption in the core anynode daemon has been reduced

• Some minor improvements in various anynode frontend wizards

Bug Fixes

• A minor issue when storing and restoring crypto-information within the configuration

• A potential crash when an invalid SIP transport was signalled from the remote peer

• A potential crash during WebRTC media negotiation

• When committing a large configuration, certain operations in anynode could be blocked for some time

• A potential issue where the shutdown of the anynode frontend was stalling

• Some issues during call evaluation in the anynode monitor

• A potential problem in the trace analyzer has been corrected where the remote address for RTP-packets were not correctly displayed

anynode Setup 4.12.5 (September 13, 2024)

Technical Setup

• Core: anynode 4.12.5

• Frontend: anynode frontend 4.12.5

• UCMA: anynode UCMA 4.12.5

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2024.8.15.1

• Monitor: anynode monitor 4.12.5

• Trace: anynode trace 4.12.5

• Administration: anynode ad 4.12.5

New Features

• The Failover Routing feature in anynode makes it possible to define several target nodes with specific routing and rewriting rules within a route. Failover routing ensures that calls reach their destination even if the primary route fails.

Improvements

• The load of Transport-Connections of a Request Router can now be evaluated and displayed on the Dashboard (see our new TechNote Request Router)

• It is now possible to use hostnames in PostgreSQL connections

• Directory Route Supervision can now also react on an existing user

• The anynode powershell module has been updated

• Unnecessary SNI check in anynode frontend has been disabled

• The Microsoft Teams SBA Installer integrated into the Windows version of anynode has been upgraded to 2024.8.15.1

Bug Fixes

• A potential crash during use of the new configuration file format

• A potential crash during anynode shutdown

• A potential issue with the encoding of LDAP queries on Debian systems

• A potential issue with connections to encrypted external PostgreSQL servers

• A potential crash in the anynode monitor on newly installed systems

• A potential crash in the anynode monitor in regard to registered SIP clients

• An issue with usage of session in parallel call scenarios

• An issue with playback of inband disconnect tones

• An issue with showing transferred calls

• An issue with showing wrong ip-addresses in SIP messages

• A problem in the trace analyzer when showing Teams SBA and Cloud connections

• A problem in the monitor and the trace analyzer during detection of SIP registrations

• A potential issue where a TLS-connection with the anynode frontend could result in high system-load

• A potential problem when installing the anynode frontend on Debian 12

anynode Setup 4.12.4 (August 27, 2024)

Technical Setup

• Core: anynode 4.12.4

• Frontend: anynode frontend 4.12.4

• UCMA: anynode UCMA 4.12.4

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.12.4

• Trace: anynode trace 4.12.4

• Administration: anynode ad 4.12.4

Improvements

• The anynode powershell module has been updated

Bug Fixes

• A potential crash in database connected directories

• A potential crash in the anynode monitor

• A potential issue creating licensing errors in the log

anynode Setup 4.12.3 (August 23, 2024)

Technical Setup

• Core: anynode 4.12.3

• Frontend: anynode frontend 4.12.3

• UCMA: anynode UCMA 4.12.3

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.12.3

• Trace: anynode trace 4.12.3

• Administration: anynode ad 4.12.3

New Features

• New VoIP Provider: IP Austria SIP-Trunk

Improvements

• Improved media-renegotiation during transfer of sessions on the WebRTC node

Bug Fixes

• A possible issue when filtering statistics

• An issue with completing a wizard using a shared network peer whitelist

• An issue where UTC was always used in a statistic-filter

anynode Setup 4.12.2 (August 20, 2024)

Technical Setup

• Core: anynode 4.12.2

• Frontend: anynode frontend 4.12.2

• UCMA: anynode UCMA 4.12.2

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.12.2

• Trace: anynode trace 4.12.2

• Administration: anynode ad 4.12.2

Improvements

• To improve interoperability, optionally SIP-authentication can be re-initiated instead of aborted during a failed authentication attempt

• Secondary ELIN addresses are now supported

Bug Fixes

• A potential crash when parsing headers during SIP authentication

• A potential crash when setting configuration

• Issues when handling T.38 packets in the trace analyzer

• An issue when configuring maximum file size for tracing

anynode Setup 4.12.1 (August 19, 2024)

Technical Setup

• Core: anynode 4.12.1

• Frontend: anynode frontend 4.12.1

• UCMA: anynode UCMA 4.12.1

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.12.1

• Trace: anynode trace 4.12.1

• Administration: anynode ad 4.12.1

Improvements

• Naming-change to "Request Router"

Bug Fixes

• An issue during install on Debian based platforms

anynode Setup 4.12.00 (August 12, 2024)

Technical Setup

• Core: anynode 4.12.00

• Frontend: anynode frontend 4.12.00

• UCMA: anynode UCMA 4.12.00

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.12.00

• Trace: anynode trace 4.12.00

• Administration: anynode ad 4.12.00

New Features

• The SIP messages for sessions can be stored in the call-history for later retrieval and analysis.

• Support for using the Operating-System specific trusted certificate store as additional source for anynode trusted certificates

• Support for replicating ACME handled certificates across multiple systems

• A SIP request router has been integrated to allow for load balancing etc. in various scenarios

• Multiple SIP nodes can now share a single SIP transport and thus one signalling port

• Specific trusted certificates can now automatically be checked and updated from TE-SYSTEMS' community

• Support for Ubuntu 24.04 "Noble Numbat" has been added

• Support for Debian 10 "Buster" has been removed

Improvements

• Transport-connections can now be configured to be used conditionally via a matching condition

• An active session filter can now limit the visible session in the monitoring simplifying the search for and administration of specific calls.

• Various REST API enhancements for configuration and administration of anynode improving integration into third party IT systems

• Sampling rate conversion has been fully replaced by libsamplerate, achieving higher quality, greater flexibility and almost equal performance

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.14

• The SQLite library integrated into the Windows version of anynode has been updated to 3.46.0

• An ICE-negotiation-option for the transport timeout included

• Additional matching rules for comparison of phone-number in the Azure Active Directory

• The media transcoding options now have a profile with the selection of "compatible" or "performance"

• Rewriting now allows to attach ";ext=" on dialstrings

• The maximum duration of sessions can now be configured

• It is now possible to limit the maximum size of a single trace-file

• Incoming WebRTC connections can now be limited to originate from certain URLs

• It is now possible to configure local and remote matching conditions for transport-connections

• ICE negotiation interoperability with Zoom has been improved

• Code-refactorization in the anynode monitor

• Performance of the trace analyzer in session view has been improved

• Loading of traces with a high count of configuration objects has been optimized

• The trace-analyzer now also shows version-information about used components (e.g. SQLite...)

• The trace-analyzer can now suppress the display of "successful" sessions

• The trace-analyzer can now show decoded certificates The trace-analyzer can now load multiple (rolling) traces at the same time

Bug Fixes

• Several issues when decoding and displaying options-packets in the trace-analyzer

• An issue when showing timestamp units of DTMFs in the trace-analyzer

anynode Setup 4.10.30 (October 9, 2024)

Technical Setup

• Core: anynode 4.10.30

• Frontend: anynode frontend 4.10.30

• UCMA: anynode UCMA 4.10.30

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2024.8.15.1

• Monitor: anynode monitor 4.10.30

• Trace: anynode trace 4.10.30

• Administration: anynode ad 4.10.30

Bug Fixes

• A potential crash when an invalid SIP transport was signalled from the remote peer

• A potential crash during WebRTC media negotiation

• A potential problem in the trace analyzer has been corrected where the remote address for RTP-packets were not correctly displayed

• A potential issue where the shutdown of the anynode frontend was stalling

anynode Setup 4.10.29 (September 24, 2024)

Technical Setup

• Core: anynode 4.10.29

• Frontend: anynode frontend 4.10.29

• UCMA: anynode UCMA 4.10.29

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2024.8.15.1

• Monitor: anynode monitor 4.10.29

• Trace: anynode trace 4.10.29

• Administration: anynode ad 4.10.29

Improvements

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.14

• The Microsoft Teams SBA Installer integrated into the Windows version of anynode has been upgraded to 2024.8.15.1

• It is now possible to use hostnames in PostgreSQL connections

Bug Fixes

• When committing a large configuration, certain operations in anynode could be blocked for some time

• A potential crash during shutdown of anynode

• A potential issue with connections to encrypted external PostgreSQL servers

• A potential issue with the encoding of LDAP queries on Debian systems

anynode Setup 4.10.28 (August 19, 2024)

Technical Setup

• Core: anynode 4.10.28

• Frontend: anynode frontend 4.10.28

• UCMA: anynode UCMA 4.10.28

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.28

• Trace: anynode trace 4.10.28

• Administration: anynode ad 4.10.28

Improvements

• To improve interoperability, optionally SIP-authentication can be re-initialized instead of aborted during a failed authentication attempt

Bug Fixes

• A potential crash when parsing headers during SIP authentication

• A potential crash when setting configuration

• Issue when handling T.38 packets in the trace analyzer

anynode Setup 4.10.27 (August 7, 2024)

Technical Setup

• Core: anynode 4.10.27

• Frontend: anynode frontend 4.10.27

• UCMA: anynode UCMA 4.10.27

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.27

• Trace: anynode trace 4.10.27

• Administration: anynode ad 4.10.27

Improvements

• Interoperability during ICE negotiation with certain peers has been improved

Bug Fixes

• A potential performance-issue when inserting call-progress-tones in very specific circumstances

anynode Setup 4.10.26 (July 31, 2024)

Technical Setup

• Core: anynode 4.10.26

• Frontend: anynode frontend 4.10.26

• UCMA: anynode UCMA 4.10.26

• Java: JRE 11u24 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.26

• Trace: anynode trace 4.10.26

• Administration: anynode ad 4.10.26

Improvements

• Interoperability during ICE negotiation with certain peers has been improved

• The Java Runtime that is used by the Web-Frontend on Windows has been updated from 11u22 to 11u24

Bug Fixes

• A potential issue which caused the omission of the "a=label" in SDP during a SIPREC session

anynode Setup 4.10.25 (July 24, 2024)

Technical Setup

• Core: anynode 4.10.25

• Frontend: anynode frontend 4.10.25

• UCMA: anynode UCMA 4.10.25

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.25

• Trace: anynode trace 4.10.25

• Administration: anynode ad 4.10.25

Improvements

• VoIP-Provider-profile changed: Deutsche Telekom Company Flex profile optimized:

• The algorithm selecting the appropriate HTTP(S) connector for starting the frontend on Windows has been optimized

• A new version of the Intel Performance Primitives (2021.11) has been integrated

Bug Fixes

• A potential issue which caused the omission of the "a=label" in SDP during a SIPREC session

• A potential issue with the test-functionality for Directory Route Supervision

anynode Setup 4.10.24 (June 21, 2024)

Technical Setup

• Core: anynode 4.10.24

• Frontend: anynode frontend 4.10.24

• UCMA: anynode UCMA 4.10.24

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.24

• Trace: anynode trace 4.10.24

• Administration: anynode ad 4.10.24

New Features

• New VoIP provider profile: EasyFone SIP Trunk

Improvements

• Support for SQL-server of Dynamics365.

• A specific case of high memory consumption in very special high-availability scenarios has been reduced

• An adaptation in the communication with the Microsoft Teams SBA has been applied

Bug Fixes

• An issue with WebRTC Nodes when interoperating via WebSocket with Firefox

• An issue decoding RTP send streams in the trace analyzer: If the remote address or port changed only the last used address and port were shown

• A potential crash of the anynode monitor when opening of an external database failed

• An issue with finding certificates with the search function in the anynode frontend

• A display issue in the configuration of the Route Supervision

anynode Setup 4.10.23 (May 30, 2024)

Technical Setup

• Core: anynode 4.10.23

• Frontend: anynode frontend 4.10.23

• UCMA: anynode UCMA 4.10.23

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.23

• Trace: anynode trace 4.10.23

• Administration: anynode ad 4.10.23

Improvements

• Support for SDP attribute "silenceSupp" from RFC 3108

Bug Fixes

• A potential deadlock when decoding erroneous OPUS codec packets

• An issue, where newly created ACME orders were not displayed in the certificate issuance status window under unfavorable circumstances

anynode Setup 4.10.22 (May 13, 2024)

Technical Setup

• Core: anynode 4.10.22

• Frontend: anynode frontend 4.10.22

• UCMA: anynode UCMA 4.10.22

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.22

• Trace: anynode trace 4.10.22

• Administration: anynode ad 4.10.22

Improvements

• The internal process system has been enhanced to be able to retrieve performance meta-data for analysis purposes

Bug Fixes

• The object section for the SIP registrations in the frontend now shows the correct updated data

anynode Setup 4.10.21 (April 24, 2024)

Technical Setup

• Core: anynode 4.10.21

• Frontend: anynode frontend 4.10.21

• UCMA: anynode UCMA 4.10.21

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.21

• Trace: anynode trace 4.10.21

• Administration: anynode ad 4.10.21

Improvements

• Depth of notifications sent for REFERs is now configurable to improve Interoperability with AudioCodes devices

• Interoperability with certain peers during ELIN operation has been improved

• The anynode frontend LDAP access (for frontend authentication and authorization) has been revamped to improved handling of connection-loss and timeouts

• The anynode monitor and trace analyzer now evaluate certificates used by LDAP connections

Bug Fixes

• A potential issue with displaying certificates being used as digital identity

• A potential issue with loosing trusted certificates for the event transport

• A potential issue when downloading very large configuration backup files on a slow network connection

• A response to a REST request to "/api/licenses/importLod" taking too long

anynode Setup 4.10.20 (April 15, 2024)

Technical Setup

• Core: anynode 4.10.20

• Frontend: anynode frontend 4.10.20

• UCMA: anynode UCMA 4.10.20

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.20

• Trace: anynode trace 4.10.20

• Administration: anynode ad 4.10.20

Improvements

• When retrieving attributes from Azure Active Directory, rewriting now also takes place for attributes configured as phone number

• For tests of the LDAP/database connections for the SIP registrar now also a phone-number can be specified

Bug Fixes

• A potential crash when using the Azure Active Directory user directory in context with WebRTC

• A potential crash when testing database connections for both the base anynode and the anynode monitor.

• An incorrect error messages displayed on the test page for the REST client route supervision

• Potential vulnerabilities (CVE-2024-29187 & CVE-2024-29188) of the anynode installer caused by the WiX Toolset have been corrected by creating the installer using a fixed version of the toolset

anynode Setup 4.10.19 (March 18, 2024)

Technical Setup

• Core: anynode 4.10.19

• Frontend: anynode frontend 4.10.19

• UCMA: anynode UCMA 4.10.19

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2023.5.9.2

• Monitor: anynode monitor 4.10.19

• Trace: anynode trace 4.10.19

• Administration: anynode ad 4.10.19

New Features

• New VoIP provider profile: Firstcom Europe Universe SIP Trunk

Improvements

• Some new configuration-options are available for ICE-negotiation

• The Microsoft Teams SBA Installer integrated into the Windows version of anynode has been upgraded to 2023.5.9.2

Bug Fixes

• A potential memory-leak during media-recording

• A potential vulnerability (CVE-2024-24810) of the anynode installer caused by the WiX Toolset has been corrected by creating the installer using a fixed version of the toolset

• A potential crash in route supervision with LDAP connections

• An issue when displaying network controller information during configuration restore

anynode Setup 4.10.18 (February 29, 2024)

Technical Setup

• Core: anynode 4.10.18

• Frontend: anynode frontend 4.10.18

• UCMA: anynode UCMA 4.10.18

• Java: JRE 11u22 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.10.18

• Trace: anynode trace 4.10.18

• Administration: anynode ad 4.10.18

New Features

• New VoIP provider profile: foncloud

Improvements

• The Azure Dialstring Directory is now able to cache entries for offline use (in case no connection to Azure can be established). This offline cache is even persisted across anynode restarts.

• The display name of authenticated users when registering is now being displayed

• The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u392 to 11u22

• Trace analyzer now has a row in the media view which shows the payload value

• REST API: "nodes/addProvider" for Telstra EP (SIP connect) extended

• The REST documentation is now automatically created and integrated during the build

• VoIP provider profile changed: Telstra EP (SIP Connect)

Bug Fixes

• A potential crash in anynode

• An issue in the monitor when changing condition events

• An issue in the trace analyzer with the description of the channels in the audio view

• An issue in the trace analyzer and monitor when evaluating transport addresses

• An issue in the node wizard in context with ACME certificates

• An issue during export of the rewrite type in static user directories

• Some issues during configuration backup

anynode Setup 4.10.17 (January 23, 2024)

Technical Setup

• Core: anynode 4.10.17

• Frontend: anynode frontend 4.10.17

• UCMA: anynode UCMA 4.10.17

• Java: JRE 8u392 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.10.17

• Trace: anynode trace 4.10.17

• Administration: anynode ad 4.10.17

Bug Fixes

• An issue with the initialization of the SIP session timer default

• Issues with the WebRTC node have been corrected

anynode Setup 4.10.16 (January 16, 2024)

Technical Setup

• Core: anynode 4.10.16

• Frontend: anynode frontend 4.10.16

• UCMA: anynode UCMA 4.10.16

• Java: JRE 8u392 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.10.16

• Trace: anynode trace 4.10.16

• Administration: anynode ad 4.10.16

New Features

• New VoIP provider profile:Telstra EP (SIP Connect)

• The PowerShell module has been enhanced by the Create-anynodeConfigBackup function

Improvements

• Now returning an error when trying to delete dial string rewrite rules with any index below zero using the REST API

• The documentation of the PowerShell module can now be shown on the Info menu

• The defaults for SIPREC nodes have been improved for operability with remote peers

Bug Fixes

• An issue with the test-section for LDAP based directories

• An issue with access rights when downloading media-recordings

• An issue unintentionally displaying an error when installing a new license

• An issue with not showing certificates in the event transport assistant

• An issue with restoring call-history and event-log when trying to load a backup configuration on Linux systems

• An issue where the wrong time units for the Maximum duration of DTMF tones sent was shown

• An issue with the /api/backup REST-API when no connection to anynode monitor was established

• An issue when testing HTTP based event transports

anynode Setup 4.10.15 (December 15, 2023)

Technical Setup

• Core: anynode 4.10.15

• Frontend: anynode frontend 4.10.15

• UCMA: anynode UCMA 4.10.15

• Java: JRE 8u392 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.10.15

• Trace: anynode trace 4.10.15

• Administration: anynode ad 4.10.15

Improvements

• The G.722 and Opus codecs won't allocate licenses from now on

• VoIP provider profile optimized: sipcall

• Added new Trusted Certificate for Zoom nodes (DigiCert TLS RSA4096 Root G5)

Bug Fixes

• An issue with encrypted LDAP connections on Linux

• An issue with session-licenses not being released in rare conditions

• An issue when using the test-section of LDAP directories

anynode Setup 4.10.14 (December 04, 2023)

Technical Setup

• Core: anynode 4.10.14

• Frontend: anynode frontend 4.10.14

• UCMA: anynode UCMA 4.10.14

• Java: JRE 8u392 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.10.14

• Trace: anynode trace 4.10.14

• Administration: anynode ad 4.10.14

Improvements

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.12

Bug Fixes

• A potential crash when disabling an LDAP connection in the configuration

• A potential crash in connection with Windows system timers

• A potential error encoding the content-length multiple times

• A high memory usage condition when using a very large amount of TLS channels in a very short timeframe

• A potential crash in the trace analyzer for sessions which were not fully established

• The REST API "/api/anynodeConfig/get" always returned "404 Not Found"

anynode Setup 4.10.13 (November 14, 2023)

Technical Setup

• Core: anynode 4.10.13

• Frontend: anynode frontend 4.10.13

• UCMA: anynode UCMA 4.10.13

• Java: JRE 8u392 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.10.13

• Trace: anynode trace 4.10.13

• Administration: anynode ad 4.10.13

Improvements

• The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u382 to 8u392

• Implemented a potential attempt to re-establish an outgoing communication flow when trying to send a SIP message

Bug Fixes

• When sending data on a TCP connection on Linux that was about to be shut down, a SIGPIPE could be raised and terminate the anynode daemon.

• A memory leak in the anynode frontend that could occur when reading certificates, private keys and signing requests.

anynode Setup 4.10.12 (November 7, 2023)

Technical Setup

• Core: anynode 4.10.12

• Frontend: anynode frontend 4.10.12

• UCMA: anynode UCMA 4.10.12

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

• Trace: anynode trace 4.10.12

• Administration: anynode ad 4.10.12

New Features

• New number verification provider profile: Bulk CNAM

Improvements

• Additional parameters for the connect strings to external databases MSSQL and PostgreSQL

Bug Fixes

• A potential crash during LDAP usage on Linux

• A potential crash in the trace analyzer when decoding audio

• An issue during configuration of sending events using SMTP

• An issue when activating live trace

anynode Setup 4.10.11 (October 12, 2023)

Technical Setup

• Core: anynode 4.10.11

• Frontend: anynode frontend 4.10.11

• UCMA: anynode UCMA 4.10.11

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

• Trace: anynode trace 4.10.11

• Administration: anynode ad 4.10.11

Bug Fixes

• A memory-leak in the Linux SNMP sub-daemon

• A potential crash during access to MSSQL databases

• In the node assistant, the X-Google-Pbx-Trunk-Secret-Key is now being saved correctly

anynode Setup 4.10.10 (October 5, 2023)

Technical Setup

• Core: anynode 4.10.10

• Frontend: anynode frontend 4.10.10

• UCMA: anynode UCMA 4.10.10

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

• Trace: anynode trace 4.10.10

• Administration: anynode ad 4.10.10

Bug Fixes

• A potential crash when using consecutive RTP/RTCP ports in a NAT environment

• Some corrections in anynode frontend concerning route supervision test functions

anynode Setup 4.10.9 (September 29, 2023)

Technical Setup

• Core: anynode 4.10.9

• Frontend: anynode frontend 4.10.9

• UCMA: anynode UCMA 4.10.9

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

• Trace: anynode trace 4.10.9

• Administration: anynode ad 4.10.9

Improvements

• The content type for PUT and POST requests in the Powershell script is now explicitly set to application/json

Bug Fixes

• A potential issue when using NAT mapping

• A potential issue during replication

• A display issue with the HTTP challenge in the node assistant

• A potential issue with Azure Active Directory authentication

anynode Setup 4.10.8 (September 22, 2023)

Technical Setup

• Core: anynode 4.10.8

• Frontend: anynode frontend 4.10.8

• UCMA: anynode UCMA 4.10.8

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

• Trace: anynode trace 4.10.8

• Administration: anynode ad 4.10.8

Bug Fixes

• A potential issue of notifications being send late by the anynode monitor when the system time was changed

• A potential issue with the start time of calls in the call history

• A potential memory leak in the anynode monitor specifically in refer situations

• A potential issue with audio volume on wideband and multi-channel configurations

anynode Setup 4.10.7 (September 13, 2023)

Technical Setup

• Core: anynode 4.10.7

• Frontend: anynode frontend 4.10.7

• UCMA: anynode UCMA 4.10.7

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

• Trace: anynode trace 4.10.7

• Administration: anynode ad 4.10.7

New Features

• New VoIP provider profile: Netcom Kassel

Improvements

• Performance metrics of LDAP connections have been added to the dashboard

• TCP-based connections now utilize the system's TCP keep-alive mechanism to monitor the status of these connections, enhancing recovery capabilities during outages.

• Optimized incoming call handling when anynode plays media

• The display of errors during call history retrieval has been improved

• VoIP provider profile optimized: sipcall

• New functions have been added to the REST API

• Webserver connectors now try to rebind to a port that did not bind successfully before

• The client side of the web application is now not able to read the session cookie anymore

• Entries into the event log have been optimized

• The display of the serial number in certificates has been optimized

Bug Fixes

• A potential crash in the anynode monitor during a path replacement

• A potential issue during primary/replica operations which resulted in recovery not being possible

• A potential issue where a registration would use a wrong binding IRI.

• A display issue in the configuration of SIP authentication in plain transport connections

• A potential issue causing higher system load during ACME order processing

• A potential deadlock in the webserver during certificate retrieval

• The REST API /api/nodes/incomingManipulations/set now works correctly even if no manipulation type is provided

• All REST APIs which are handed an invalid node ID will now respond with an error

• An issue where maintenance reboot and shutdown were not executed

anynode Setup 4.10.6 (August 25, 2023)

Technical Setup

• Core: anynode 4.10.6

• Frontend: anynode frontend 4.10.6

• UCMA: anynode UCMA 4.10.6

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

• Trace: anynode trace 4.10.6

• Administration: anynode ad 4.10.6

Improvements

• The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u372 to 8u382

• Interoperability for RFC4733 events with multiple clock rates being offered has been improved

• Timeout handling when accessing remote databases during directory route supervision has been improved

Bug Fixes

• During an update from 4.8.x and earlier, configured SANs for a network security profile could go missing

• A potential crash during path replacement

• An issue when copying certain signalling objects in the anynode core

• An issue when shutting down and restarting network interfaces

• A potential crash when using the SQLite database backend

• A potential issue in the anynode monitor with detecting the state of a SIP node when used from multiple nodes

• A potential crash of the anynode monitor when accessing system status information

• A potential crash of the anynode monitor when trying to access node information

• An issue when decoding custom headers in the anynode monitor

anynode Setup 4.10.5 (August 1, 2023)

Technical Setup

• Core: anynode 4.10.5

• Frontend: anynode frontend 4.10.5

• UCMA: anynode UCMA 4.10.5

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

• Trace: anynode trace 4.10.5

• Administration: anynode ad 4.10.5

Improvements

• Public IP addresses are not slightly preferred during auto selection on an interface in contrast to private addresses anymore

anynode Setup 4.10.4 (July 28, 2023)

Technical Setup

• Core: anynode 4.10.4

• Frontend: anynode frontend 4.10.4

• UCMA: anynode UCMA 4.10.4

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

• Trace: anynode trace 4.10.4

• Administration: anynode ad 4.10.4

Improvements

• VoIP system profile optimized: Google Voice

• Manual hand over and recover operations for hot standby are now written to the event log

• New functions have been added to the REST API

• Various improvements in ICE and DTLS handling

• Optimizations in the SRV-based Load Balancer

• Public IP addresses are now slightly preferred during auto selection on an interface in contrast to private addresses

Bug Fixes

• An issue when importing and cloning media recording multiplexer objects

• A potential crash in the anynode trace analyzer

• A reference counting issue in the anynode monitor

• An issue with the information forwarder in context of fail over handling

• An issue with XOR operator during route selection

anynode Setup 4.10.3 (July 06, 2023)

Technical Setup

• Core: anynode 4.10.3

• Frontend: anynode frontend 4.10.3

• UCMA: anynode UCMA 4.10.3

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

• Trace: anynode trace 4.10.3

• Administration: anynode ad 4.10.3

Bug Fixes

• An issue with storing Hot Standby Conditions during commit

anynode Setup 4.10.2 (July 05, 2023)

Technical Setup

• Core: anynode 4.10.2

• Frontend: anynode frontend 4.10.2

• UCMA: anynode UCMA 4.10.2

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

• Trace: anynode trace 4.10.2

• Administration: anynode ad 4.10.2

Bug Fixes

• A race condition potentially causing a crash in the anynode core

• A problem with timer handling with the SRV-based load balancing

• A problem during a copy operation of a SIP route in the config

• Some potential issues in the REST API of the anynode frontend

• An issue in the configuration of the SRV-based load balancing

anynode Setup 4.10.1 (July 04, 2023)

Technical Setup

• Core: anynode 4.10.1

• Frontend: anynode frontend 4.10.1

• UCMA: anynode UCMA 4.10.1

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

• Trace: anynode trace 4.10.1

• Administration: anynode ad 4.10.1

Improvements

• Improved handling of SRV-based load balancing (used with Cisco Webex)

• Improved handling of monitoring and logging of HA fail over

• Added web token signing mode RS256 and RS512 for WebRTC connections

• SIP OPTIONS can now optionally be answered with 200 OK. Even if no license is installed

• Improved PowerShell functions

Bug Fixes

• An issue when probing IPC connections

• An issue with redirection from HTTP to HTTPS for the anynode frontend web server

anynode Setup 4.10.0 (June 26, 2023)

Technical Setup

• Core: anynode 4.10.1

• Frontend: anynode frontend 4.10.0

• UCMA: anynode UCMA 4.10.0

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

• Trace: anynode trace 4.10.0

• Administration: anynode ad 4.10.0

New Features

• Added a WebRTC node as a new node type in anynode

• Support for Debian 12 Bookworm

• Various changes to certificate and private key handling objects to support advanced functionality

• SIPREC support for recording calls

• Support for automatic certificate renewal on certificate authorities that implement the ACME protocol (for example Let‘s Encrypt, ZeroSSL, GoDaddy)

• The anynode frontend authentication and authorization can now also use Azure Active Directory

• New VoIP system profile: Google Voice

• New VoIP system profile: Cisco Webex

Improvements

• The TLS server can now totally disable mutual authentication

• The HTTP server integrated into anynode now sets the content type for responses for JavaScript and JSON for the respective file types

• Outage of RTP/RTCP for a certain time may now optionally shut down the corresponding SIP session

• Configurable strings can be removed from phone numbers of the Azure Dial String Directory

• Registrations can now be terminated from the anynode frontend

• Some changes for support of SIP-R added

• Improved certificate check for secure LDAP on Windows

• Blocking DNS queries which could have blocked other anynode functionality have been removed from most places

• Added basic support of extended RTCP (RFC4585)

• Compatibility enhancements for Mime multi part boundaries with specific peers

• Added ability to log bad response times when accessing remote LDAP server

• Support for receiving DTMFs via SIP-INFO

• Route Supervision enhanced to add SIP headers, setting the route action and the directory to use for call forking

• Support for opportunistic SAVP negotiation with multiple m-lines

• Optimization of Opus Codec defaults

• Added ability to send keep alive packets on TCP connections

• The SIP load balancer now has support to evaluate SRV records

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 3.0.9

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

anynode Setup 4.6.29 (November 23, 2022)

Technical Setup

• Core: anynode 4.6.29

• Frontend: anynode frontend 4.6.29

• UCMA: anynode UCMA 4.6.29

• Java: JRE 8u342 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.6.29

• Trace: anynode trace 4.6.29

• Administration: anynode ad 4.6.29

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

• 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

anynode Setup 4.6.28 (November 15, 2022)

Technical Setup

• Core: anynode 4.6.28

• Frontend: anynode frontend 4.6.28

• UCMA: anynode UCMA 4.6.28

• Java: JRE 8u342 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.6.28

• Trace: anynode trace 4.6.28

• Administration: anynode ad 4.6.28

Bug Fixes

• A potential crash during mapping of unusual status codes (especially in connection with new Microsoft Teams functionality)

anynode Setup 4.6.27 (November 11, 2022)

Technical Setup

• Core: anynode 4.6.27

• Frontend: anynode frontend 4.6.27

• UCMA: anynode UCMA 4.6.27

• Java: JRE 8u342 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.6.27

• Trace: anynode trace 4.6.27

• Administration: anynode ad 4.6.27

Improvements

• Due to a possible performance issue on virtual file systems, improved polling of file-size for anynode trace files

Bug Fixes

• A potential crash in the route supervision

• A potential crash in the anynode monitor with corrupted external databases

• An issue with the CSV-import of the dial-string rewrite rules

• An issue when editing network-interfaces

• An issue when showing unbound settings in media-negotiation config

anynode Setup 4.6.26 (September 9, 2022)

Technical Setup

• Core: anynode 4.6.26

• Frontend: anynode frontend 4.6.26

• UCMA: anynode UCMA 4.6.26

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

• Trace: anynode trace 4.6.26

• Administration: anynode ad 4.6.26

Improvements

• The Microsoft Teams node-wizard now also adds the IP-ranges and SAN filters for the Microsoft Government and DoD clouds

• Optionally anynode can add specific SAN-filters to Microsoft Teams nodes that have been created previously to tighten security

• VoIP system profile optimized: Jtel

Bug Fixes

• An issue in the call-history in context with the Microsoft Teams Correlation Id

• A potential deadlock during shutdown of the system

anynode Setup 4.6.25 (August 25, 2022)

Technical Setup

• Core: anynode 4.6.25

• Frontend: anynode frontend 4.6.25

• UCMA: anynode UCMA 4.6.25

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

• Trace: anynode trace 4.6.25

• Administration: anynode ad 4.6.25

New Features:

• New VoIP system: Jtel

Improvements

• The Java runtime that is used by the web frontend on Windows has been updated from 8u332 to 8u342

• The Jetty components used by the anynode frontend has been updated to 9.4.48.v20220622

• When creating Microsoft Teams nodes, the entry sip-all.pstnhub.microsoft.com is no longer written to the Network Peer White list.

• It is now possible to configure the initial value of the Session-Expires header separately from minimum and maximum value

• Application specific tags can now be added to specific address-fields during rewrite operation (allowing immediate redirect to voice mail on Microsoft Teams for example)

Bug Fixes

• The timeout for the export of the call history has been increased to 3 minutes as retrieving the data from the anynode monitor database could takes a long time

• The display texts fail the mapping and use local transport URI were swapped for the Dial string - SIP URI conversion option

• If a problem occurred during retrieval of the configuration, sync of configuration could fail afterwards

• If no connection to an LDAP server was established, every minute a message was written into the event log

• An issue when logging Microsoft Teams calls in the call history

• An issue when showing Microsoft Teams calls in the anynode trace analyzer

anynode Setup 4.6.24 (August 10, 2022)

Technical Setup

• Core: anynode 4.6.24

• Frontend: anynode frontend 4.6.24

• UCMA: anynode UCMA 4.6.24

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.24

• Trace: anynode trace 4.6.24

• Administration: anynode ad 4.6.24

Bug Fixes

• An issue created by recent changes when handling the SDP origin

anynode Setup 4.6.23 (August 08, 2022)

Technical Setup

• Core: anynode 4.6.23

• Frontend: anynode frontend 4.6.23

• UCMA: anynode UCMA 4.6.23

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.23

• Trace: anynode trace 4.6.23

• Administration: anynode ad 4.6.23

Bug Fixes

• A potential crash during execution of a prepared SQL statement

• An issue, where the number of result-columns was zero erroneously after an SQL execution

anynode Setup 4.6.22 (August 05, 2022)

Technical Setup

• Core: anynode 4.6.22

• Frontend: anynode frontend 4.6.22

• UCMA: anynode UCMA 4.6.22

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.22

• Trace: anynode trace 4.6.22

• Administration: anynode ad 4.6.22

Bug Fixes

• A potential issue during decoding of contact or subscription state headers

• An issue when creating IPV6 based web connectors for the anynode frontend

• A potential issue within the configuration of the IP address in the network controller

• A potential display issue of the media trans coding options in the media file recorder

anynode Setup 4.6.21 (August 02, 2022)

Technical Setup

• Core: anynode 4.6.21

• Frontend: anynode frontend 4.6.21

• UCMA: anynode UCMA 4.6.21

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.21

• Trace: anynode trace 4.6.21

• Administration: anynode ad 4.6.21

New Features

• New VoIP provider profile: NTT (SIP Trunk) PRACK disabled

• New VoIP provider profile: NTT (SIP Trunk) PRACK

• New VoIP provider profile: bandwidth.com

• New VoIP provider profile: C4B XPhone Connect

• New VoIP provider profile: C4B XPhone Connect (local host)

Improvements

• More configuration options for SDP origin to increase interoperability with certain peers

• VoIP provider profile optimized: easybell Business basic

anynode Setup 4.6.20 (July 12, 2022)

Technical Setup

• Core: anynode 4.6.20

• Frontend: anynode frontend 4.6.20

• UCMA: anynode UCMA 4.6.20

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.20

• Trace: anynode trace 4.6.20

• Administration: anynode ad 4.6.20

Improvements

• New VoIP provider profile: Deutsche Telekom CompanyFlex

• VoIP provider profile renamed: NetCologne Secure SIPTrunk over Internet to NetCologne Pro Phone SIP TLS

• VoIP provider profile renamed: NETCOLOGNE - Pro Phone SIP to NetCologne Pro Phone SIP

Bug Fixes

• An issue at the end of the wizard creating a CompanyFlex node

anynode Setup 4.6.19 (July 8, 2022)

Technical Setup

• Core: anynode 4.6.19

• Frontend: anynode frontend 4.6.19

• UCMA: anynode UCMA 4.6.19

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.19

• Trace: anynode trace 4.6.19

• Administration: anynode ad 4.6.19

Improvements

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1p

• Improved interoperability with certain Avaya phones with authentication issues

• A wizard to let the user decide to automatically apply necessary configuration-changes for interoperability with German Telekom CompanyFlex accesses has been implemented

• The frontend web server now no longer responds with a Jetty version number

Bug Fixes

• A few minor problems in the call history

anynode Setup 4.6.18 (June 23, 2022)

Technical Setup

• Core: anynode 4.6.18

• Frontend: anynode frontend 4.6.18

• UCMA: anynode UCMA 4.6.18

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.6.14.1 (2.6.14.1)

• Monitor: anynode monitor 4.6.18

• Trace: anynode trace 4.6.18

• Administration: anynode ad 4.6.18

Improvements

• Some changes for the wizard creating German Telekom Company Flex nodes have been implemented

Bug Fixes

• A potential crash when decoding empty MIME multi part messages

• A potential crash during route supervision when a configured database column did not exist

• An unintended re-fetch of the active role in Hot Standby mode during a system restart

• A char set encoding issue when accessing remote databases

anynode Setup 4.6.17 (June 17, 2022)

Technical Setup

• Core: anynode 4.6.17

• Frontend: anynode frontend 4.6.17

• UCMA: anynode UCMA 4.6.17

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.17

• Trace: anynode trace 4.6.17

• Administration: anynode ad 4.6.17

Bug Fixes

• An issue when writing the call history and displaying the session overview in the anynode trace analyzer for calls with Authentication Required

• A potential issue with the SMTP client when the mail server offered StartTLS

• An issue when retrieving the remote server-certificate when configuring an SMTP connection

anynode Setup 4.6.16 (June 14, 2022)

Technical Setup

• Core: anynode 4.6.16

• Frontend: anynode frontend 4.6.16

• UCMA: anynode UCMA 4.6.16

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.16

• Trace: anynode trace 4.6.16

• Administration: anynode ad 4.6.16

Improvements

• Some changes necessary for behaviour changes during re-registrations on German Telekom Company Flex accesses have been implemented

Bug Fixes

• An issue with a configuration option, which prevented the reuse of a prior received challenge

• A potential crash when a Microsoft-Teams tenant was mis configured

• An issue when configuring an ELIN dial string directory for a routing filter

• An issue when configuring event transport for non-local back ends

anynode Setup 4.6.15 (June 7, 2022)

Technical Setup

• Core: anynode 4.6.15

• Frontend: anynode frontend 4.6.15

• UCMA: anynode UCMA 4.6.15

• Java: JRE 8u332 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.15

• Trace: anynode trace 4.6.15

• Administration: anynode ad 4.6.15

New Features

• New scenarios integrated in Wizard:

  Create a relationship between Zoom Phone Premise Peering and a VoIP provider

  Create a relationship between Zoom Phone Premise Peering and a PBX or VoIP system

  Create a relationship between Zoom Phone Premise Peering, a VoIP provider and a PBX or VoIP system

Improvements

• SIP MWI can now be received and forwarded Handling of geolocation headers changed to be more inter operable with specific peers

• Certificate wizard: self-signed certificates now contain key-usage DIGITAL_SIGNATURE and KEY_ENCIPHERMENT

Bug Fixes

• An issue in the anynode trace analyzer when showing integer properties with more than 31bits size

• A possible issue where new conditions were not shown when creating a new route

• A possible issue displaying default values for forwarding from calling entity to called entity

anynode Setup 4.6.14 (May 19, 2022

Technical Setup

• Core: anynode 4.6.14

• Frontend: anynode frontend 4.6.14

• UCMA: anynode UCMA 4.6.14

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2022.5.3.1 (2.5.3.1)

• Monitor: anynode monitor 4.6.14

• Trace: anynode trace 4.6.14

• Administration: anynode ad 4.6.14

Improvements

• Authorizations via LDAP now always update the roles of the user upon every single login.

• Improved performance of drawing charts in the monitor mode of anynode frontend

• The Java Runtime that is used by the anynode frontend on Windows has been updated from 8u322 to 8u332

• The Microsoft Teams SBA component optionally used on Windows has been updated from 2021.11.10.1 to 2022.5.3.1

Bug Fixes

• A potential issue where the anynode frontend would not react anymore when frequently calling REST functions

anynode Setup 4.6.13 (May 10, 2022)

Technical Setup

• Core: anynode 4.6.13

• Frontend: anynode frontend 4.6.13

• UCMA: anynode UCMA 4.6.13

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.13

• Trace: anynode trace 4.6.13

• Administration: anynode ad 4.6.13

New Features

• Received REFER messages can now also be tunneled instead of anynode internally handling them

• New VoIP provider: goetel SIP-Trunk

Improvements

• Some changes to SIP header handling for Microsoft Teams Direct Routing

• Some LDAP handling improvements

• Asserted URI fall back value: The SIP URI editor can now also edit the User Part

• SIP dialog configuration has been extended for RPI-headers

• The Zoom Phone Premise Peering wizard has been extended by further options

• The innovaphone wizard now has new defaults

• The Jetty component used by the anynode frontend has been updated to 9.4.46.v20220331

• Defaults for Contact header mapping have been adjusted

Bug Fixes

• An issue with showing errors within the Network Security Profile configuration

• An issue during textual import of private keys and certificates

anynode Setup 4.6.12 (April 13, 2022)

Technical Setup

• Core: anynode 4.6.12

• Frontend: anynode frontend 4.6.12

• UCMA: anynode UCMA 4.6.12

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.12

• Trace: anynode trace 4.6.12

• Administration: anynode ad 4.6.12

Bug Fixes

• A problem when using the Legacy Wildcard Patterns

• A crash occurring in HTTP event transport. If the HTTP response contained an invalid or no status code the crash occurred

• An error when formatting JSON data in HTTP transport, if the template uses the JSON format. If the content type starts with application/json the conversion of characters that are not allowed in JSON is done for the parameter

anynode Setup 4.6.11 (April 8, 2022)

Technical Setup

• Core: anynode 4.6.11

• Frontend: anynode frontend 4.6.11

• UCMA: anynode UCMA 4.6.11

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.11

• Trace: anynode trace 4.6.11

• Administration: anynode ad 4.6.11

Improvements

• In the Telephony Forwarding settings, one can now also configure a static header that is being sent to the peer within the initial INVITE

• In Directory Route Supervision, multiple attribute names and static text is now supported for Dial-Strings, Display-Names and Tags. When using those multiple attribute names or static text, a dollar-sign must be placed before the attribute name

• SIP handling for multi cast-subscribe during provisioning has been changed to support Grandstream devices

• Added a new certificate for the Microsoft Teams node

• Route Supervision now supports retrieving multiple columns from a database using the $ character

Bug Fixes

• A potential crash in a fringe case in connection with ICE LITE

• An issue where trusted certificates were not place into the Network Security Profile by the Azure Active Directory Assistant

• An issue when saving alternative conditions

• An issue during save/store of unbound settings for the HTTP server config

anynode Setup 4.6.10 (March 30, 2022)

Technical Setup

• Core: anynode 4.6.10

• Frontend: anynode frontend 4.6.10

• UCMA: anynode UCMA 4.6.10

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.10

• Trace: anynode trace 4.6.10

• Administration: anynode ad 4.6.10

Improvements

• Some specific URIs used during provisioning by Grandstream and Mitel devices can now be parsed

• SIP handling for multi cast subscribe during provisioning has been improved

Bug Fixes

• A potential crash during parsing of SIP URIs

• A potential crash during parsing of very specific PCT encoded headers

• A potential crash when committing only partially configured provisioning templates

anynode Setup 4.6.9 (March 23, 2022)

Technical Setup

• Core: anynode 4.6.9

• Frontend: anynode frontend 4.6.9

• UCMA: anynode UCMA 4.6.9

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.9

• Trace: anynode trace 4.6.9

• Administration: anynode ad 4.6.9

New Features

• Support for Ubuntu 22.04 Jammy Jellyfish has been added

Improvements

• The configuration of the authentication profile has been improved

Bug Fixes

• A crash while sending an MWI

• Using the Azure Active Directory wizard will no longer create an unused network controller

anynode Setup 4.6.8 (March 18, 2022)

Technical Setup

• Core: anynode 4.6.8

• Frontend: anynode frontend 4.6.8

• UCMA: anynode UCMA 4.6.8

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.8

• Trace: anynode trace 4.6.8

• Administration: anynode ad 4.6.8

New Features

• Support for Ubuntu 22.04 Jammy Jellyfish has been added

Improvements

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1n

• It is now possible to configure the Q-value for registrations

Bug Fixes

• An issue when parsing lines with CRLF in a specific position

• A potential issue, possibly preventing the anynode frontend service/daemon from shutting down

• A potential issue when storing configurations-changes for tags

anynode Setup 4.6.7 (March 14, 2022)

Technical Setup

• Core: anynode 4.6.7

• Frontend: anynode frontend 4.6.7

• UCMA: anynode UCMA 4.6.7

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.7

• Trace: anynode trace 4.6.7

• Administration: anynode ad 4.6.7

Improvements

• Various changes in the area of Rewriting

• Enhancements to the Microsoft Teams Connectivity Wizard Some updates to the RESTful-API have been implemented

Bug Fixes

• An exception in the anynode trace analyzer which could happen in very rare circumstances

• A potential issue when verifying the signature of update packages

• A potential issue when displaying an event Id in the anynode dashboard

anynode Setup 4.6.6 (March 4, 2022)

Technical Setup

• Core: anynode 4.6.6

• Frontend: anynode frontend 4.6.6

• UCMA: anynode UCMA 4.6.6

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.6

• Trace: anynode trace 4.6.6

• Administration: anynode ad 4.6.6

Improvements

• Various changes in the area of Rewriting

• Enhancements to the Microsoft Teams Connectivity Wizard Some updates to the RESTful-API have been implemented

Bug Fixes

• An issue retrieving statistics under very specific circumstances

• An issue retrieving meta data

• A potential crash during path replacement which could occur in very rare circumstances

• A potential issue in hot standby operation which could cause the main system to always go active

• An issue with the resource monitor for disk space on Linux

• Disabled objects we possibly not stored correctly

anynode Setup 4.6.5 (February 28, 2022)

Technical Setup

• Core: anynode 4.6.5

• Frontend: anynode frontend 4.6.5

• UCMA: anynode UCMA 4.6.5

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.5

• Trace: anynode trace 4.6.5

• Administration: anynode ad 4.6.5

Improvements

• Some further changes for better workflow in fail over configurations for secondary systems being brought into maintenance mode

• anynode frontend web server now supports TLS 1.3

Bug Fixes

• An issue when using virtual IP addresses on images for APU and IPU hardware using network manager

• An issue which disabled monitoring disk usage

• In the Hot Standby object, an issue when showing the state of the main system status in maintenance mode

anynode Setup 4.6.4 (February 21, 2022)

Technical Setup

• Core: anynode 4.6.4

• Frontend: anynode frontend 4.6.4

• UCMA: anynode UCMA 4.6.4

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.4

• Trace: anynode trace 4.6.4

• Administration: anynode ad 4.6.4

Improvements

• Some additional functionality has been added to the RESTful-API

• Protocols TLS 1.0 and TLS 1.1 are now deactivated by default for web connectors

• Default handling of maintenance mode and standby has been improved for better workflow

Bug Fixes

• A potential issue when connecting to anynode frontend via secured TLS

• A potential issue with timeouts during SIP registration

• A potential crash in anynode monitor when using incorrectly configured database user directories

anynode Setup 4.6.3 (February 15, 2022)

Technical Setup

• Core: anynode 4.6.3

• Frontend: anynode frontend 4.6.3

• UCMA: anynode UCMA 4.6.3

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.3

• Trace: anynode trace 4.6.3

• Administration: anynode ad 4.6.3

Bug Fixes

• Fixed a potential endless loop

• Fixed an issue during encoding of IRIs Fixed a potential issue when decoding URIs containing % signs

anynode Setup 4.6.2 (February 14, 2022)

Technical Setup

• Core: anynode 4.6.2

• Frontend: anynode frontend 4.6.2

• UCMA: anynode UCMA 4.6.2

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.2

• Trace: anynode trace 4.6.2

• Administration: anynode ad 4.6.2

Bug Fixes

• Fixed a potential issue where the frontend could not restart an update process

• Fixed an issue where the current versions of anynode modules could not be retrieved

anynode Setup 4.6.1 (February 11, 2022)

Technical Setup

• Core: anynode 4.6.1

• Frontend: anynode frontend 4.6.1

• UCMA: anynode UCMA 4.6.1

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.1

• Trace: anynode trace 4.6.1

• Administration: anynode ad 4.6.1

Improvements

• Better support for 125 percent Windows scaling for the anynode trace analyzer

• Improved IPC between anynode modules Improved RFC4028 configuration options for the SIP user agent implementation

• Improved SDP interoperability with certain NTT trunks

Bug Fixes

• The Provisioning server wizard now also show and configures trusted certificates for certain SIP-phone manufacturers when invoked from SIP phones registrar wizard

anynode Setup 4.6.0 (January 31, 2022)

Technical Setup

• Core: anynode 4.6.0

• Frontend: anynode frontend 4.6.0

• UCMA: anynode UCMA 4.6.0

• Java: JRE 8u312 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.6.0

• Trace: anynode trace 4.6.0

• Administration: anynode ad 4.6.0

New Features

• Dial strings can now be marked by tags to denote specific properties like anonymous or emergency call for example

• Tags are now also supported in Route Supervision Support for external databases (MariaDB, MySQL, PostgreSQL or Microsoft SQL) as source for user directories

• SIP authentication, Register server data and provisioning info can be stored in LDAP, Azure AD and external databases

• Route Supervision now using Azure AD and external databases

• Dialog is now shown upon login if there are important tasks which need taken care of:

• Change password Permission to send anonymized anynode improvement statistics

• Availability of product updates can now be retrieved from TE-SYSTEMS community website taking into account the SUS state of the respective licenses

• Reverse number lookup support Number validation / verification via external service providers added

• Specifically configured SIP headers can now be written into the call history

• An anynode can now contain a system name in its configuration Support for proxy servers when the anynode frontend tries to access web resources (licensing, updates...)

• TLS handshake now stored in trace file in PCAP format

• A WAV file with hold music is now shipped with anynode

Improvements

• Replication and Hot Standby have been improved drastically both in operation, configuration, monitoring and migration

• Manipulations have been renamed to Rewritings and are now much more powerful

• Automatic migration to new DNS-behaviour of Microsoft Teams Direct Routing

• RESTful API has again been improved

• All events handled by the event system can now also be transmitted towards WMI and SNMP

• Implemented Broadsoft specific way to react to hold notifications

• Certificates are now retrieved and placed into trace file as soon as possible during connection establishment

• Maintenance mode can now persist between restarts of anynode

• Optimized creation of target IRI

• Optimized handling when anynode is the registration server

• Optimized loop detection for path replacement in Microsoft Teams environments

• Handling of TLS connections can now be controlled in more detail if the certificate shown does not contain the IP address during a target refresh

• It is now possible to rate limit registrations to spread those over time

• Handling of expires values in responses to REGISTER requests has been improved

• Support of X-MS-TenantID header for Operator Connect support

• Optimization during load and store of config and activation of new configuration

• Contact header generation has been improved. It is now possible to have a user in the contact header

• SIP client registration can now be configured to contain a q-value which will be supplied to the contact header during registration

• VoIP system optimized: Unify OpenScape Voice

• VoIP provider profile optimized: Telekom CompanyFlex

• SIP phones super wizard optimized for use with provisioning

• Various ELIN improvements Various improvements of the call history

• Various improvements of the user interface of the web frontend

• Various improvements in the network security profile wizards

• Various improvements in the anynode trace analyzer

• SmartGWT component used in anynode frontend has been updated to version 12.1p

• Performance of retrieving data for anynode dashboard has been improved

• Before uploading audio files, compatibility for usage in anynode is now checked

• Audio files can now be used as tones

• Improved handling of unexpected responses from Route Supervision HTTP server

• Configuration of certificates for use in SMTP client has been integrated

• Certificate of web server connector of the anynode frontend can now be re-configured using the command line interface

• A collision of system identifiers will now be detected and shown in a dialog with the option to regenerate those ids

• Performance improvements in various areas of the anynode monitor

• Various new events are now being logged

Bug Fixes

• Some minor issues in ELIN environments

• An issue when adding a local user to the anynode frontend via command-line

anynode Setup 4.4.12 (November 21, 2021)

Technical Setup

• Core: anynode 4.4.12

• Frontend: anynode frontend 4.4.12

• UCMA: anynode UCMA 4.4.12

• Java: JRE 8u322 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.11.10.1

• Monitor: anynode monitor 4.4.12

• Trace: anynode trace 4.4.12

• Administration: anynode ad 4.4.12

Improvements

• VoIP system profile optimized: Microsoft Teams

• VoIP provider profile optimized: R-Kom Anlagenanschluss

• VoIP provider profile optimized: NetCologne Secure SIPTrunk over Internet: new TLS certificate

• In case the unique system identifiers of sub products were merely copies from another system, this case will now be detected and a dialogue requests (automatic) re-generation

• Error handling of invalid parameters for specific REST API has been improved

• Detection of operating system now includes Windows 11 and Windows Server 2022

Bug Fixes

• A potential crash while analyzing a trace stream within the anynode monitor

• A potential issue during authentication when connecting to an SMTP server

• A potential issue during TCP connection establishment on Debian systems

anynode Setup 4.4.11 (21. October 2021)

Technical Setup

• Core: anynode 4.4.11

• Frontend: anynode frontend 4.4.11

• UCMA: anynode UCMA 4.4.11

• Java: JRE 8u302 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.5.19.2

• Monitor: anynode monitor 4.4.11

• Trace: anynode trace 4.4.11

• Administration: anynode ad 4.4.11

Bug Fixes

• A potential issue when decoding XML in SIP messages

anynode Setup 4.4.10 (October 5, 2021)

Technical Setup

• Core: anynode 4.4.10

• Frontend: anynode frontend 4.4.10

• UCMA: anynode UCMA 4.4.10

• Java: JRE 8u302 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.5.19.2

• Monitor: anynode monitor 4.4.10

• Trace: anynode trace 4.4.10

• Administration: anynode ad 4.4.10

New Features

• New VoIP provider profile: htp Business FleX SIP-Trunk smart

Improvements

• VoIP system profile optimized: peoplefone SIP Trunk

• anynode trace analyzer now also has improved error-handling of the OAuth client to distinguish specific error-classes like Application disabled, User password expired, Client secret expired and Multi Factor Authentication required

Bug Fixes

• A potential issue with reference counting

• An issue with displaying texts including an ampersand within the anynode trace analyzer

• An issue in the anynode frontend where the timezone of the filter wasn't calculated correctly, if there is a difference between the server and browser timezone

anynode Setup 4.4.9 (September 17, 2021)

Technical Setup

• Core: anynode 4.4.9

• Frontend: anynode frontend 4.4.9

• UCMA: anynode UCMA 4.4.9

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.5.19.2

• Monitor: anynode monitor 4.4.9

• Trace: anynode trace 4.4.9

• Administration: anynode ad 4.4.9

Improvements

• Error-handling of the OAuth client has been improved to distinguish specific error classes like Application disabled, User password expired, Client secret expired and Multi Factor Authentication required

• Azure specific error codes (Azure Active Directory Security Token Service) are now being evaluated Detection of Windows Server 2022 and extended OS information for Debian/Ubuntu and RHEL/CentOS in trace files

• The system ids in the System IDs table for licensing can now be selected and copied with the cursor

• VoIP provider profile optimized: easybell Business basic Profile

• PBX system profile optimized: SwyxWare

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1l

• The Java Runtime that is used by the anynode frontend on Windows has been changed from 8u292 to 8u302

Bug Fixes

• A potential issue when processing the local address

• A potential issue when extracting audio-data within the anynode trace analyzer

• An issue when configuring ToS for Quality-of-Service

anynode Setup 4.4.8 (August 24, 2021)

Technical Setup

• Core: anynode 4.4.8

• Frontend: anynode frontend 4.4.8

• UCMA: anynode UCMA 4.4.8

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.5.19.2

• Monitor: anynode monitor 4.4.8

• Trace: anynode trace 4.4.8

• Administration: anynode ad 4.4.8

New Features

• Support for Debian 11 Bullseye has been added

Improvements

• VoIP provider profile optimized: twilio Elastic SIP

• VoIP provider profile optimized: reventix SIPbase (secure)

• VoIP provider profile optimized: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119)

Bug Fixes

• A rounding error within the tone generator

• An issue with a timer in OAUTH authentication

• An issue with the parser in the HTTP client when receiving an UPGRADE header

• An issue with time tags in external databases on 32bit architectures

• The anynode frontend could possibly show UUIDs instead of the intended names for Announcement Media Source

• Copying of media files during replications now also works if the target directory did not exist yet

• An issue when during display of days in the holiday list

anynode Setup 4.4.7 (July 21, 2021)

Technical Setup

• Core: anynode 4.4.7

• Frontend: anynode frontend 4.4.7

• UCMA: anynode UCMA 4.4.7

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.5.19.2

• Monitor: anynode monitor 4.4.7

• Trace: anynode trace 4.4.7

• Administration: anynode ad 4.4.7

New Features

• New VoIP provider profile: Vodia

Improvements

• It is now possible to configure SIP-transports to terminate existing sessions when the transport is going into non-up state

• VoIP provider profile optimized: Voxbone Trunk

• Optimized Network Security Profile configuration handling

Bug Fixes

• A potential issue with media handling in connection with playing voice-prompts at session-start

• A potential issue with the display of the announcement media source in the anynode frontend

anynode Setup 4.4.6 (July 16, 2021)

Technical Setup

• Core: anynode 4.4.6

• Frontend: anynode frontend 4.4.6

• UCMA: anynode UCMA 4.4.6

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.5.19.2

• Monitor: anynode monitor 4.4.6

• Trace: anynode trace 4.4.6

• Administration: anynode ad 4.4.6

Improvements

• VoIP system profile changed: Unify HiPath 4000-Serie/HG 3500 and Unify OpenScape 4000 now implicitly configured for RFC3891 support

• VoIP system profile changed: MS-Teams added additional IP white list entries

• VoIP system profile changed: MS-Teams now uses 5066 as default TCP/UDP-port

• VoIP system profile changed: Alcatel-Lucent OmniPCX Enterprise (OXE) now negotiates consecutive RTP and RTCP ports by default

• VoIP provider profile changed: B3networks default values for SIP-URI processing have been adjusted

• VoIP provider profile changed: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119) now with better wizard handling

• VoIP provider profile changed: Zoom Phone Premise Peering added additional IP white list entry

• VoIP provider profile changed: Zoom Phone Premise Peering SJ adjusted proxy-server address

• Some optimizations on the anynode dashboard

• Some enhancements to the RESTful-API Some new functions have been added to the PowerShell module.

• Probing of IPC-connections between anynode frontend and the other modules has been implemented

• Some enhancements of status-display in various locations in the anynode frontend have been implemented

• Some optimizations during encoding of configuration have been implemented

Bug Fixes

• A potential issue when using MS-SQL for storing call-history and event-log

• A potential issue when using MS-SQL on Azure-systems

• A potential issue when monitoring calls

• A potential issue in the anynode trace analyzer when switching to detail view

• Some potential issues in the RESTful-API

• A potential race-condition when establishing TCP-connections in the anynode frontend

• A potential issue with showing progress of file-upload in the anynode frontend

anynode Setup 4.4.5 (June 14, 2021)

Technical Setup

• Core: anynode 4.4.5

• Frontend: anynode frontend 4.4.5

• UCMA: anynode UCMA 4.4.5

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.4.5.10

• Monitor: anynode monitor 4.4.5

• Trace: anynode trace 4.4.5

• Administration: anynode ad 4.4.5

Improvements

• The two existing Innovaphone profiles have been consolidated into one

• Some nomenclature has been cleaned up in the REST API

• Saving of very large configurations is now working more smoothly

Bug Fixes

• An issue with monitoring and tracing sessions with path replacement

• An issue when writing into the Linux syslog

• An issue when monitoring disk-space on 32-bit Linux platforms

• A potential issue during clone/remove/export of objects managed by the anynode frontend

• A potential issue during IPC communication with other anynode modules

• An issue in the wizard for LDAP connections

• An issue with access-rights when getting and setting the system-name

anynode Setup 4.4.4 (May 18, 2021)

Technical Setup

• Core: anynode 4.4.4

• Frontend: anynode frontend 4.4.4

• UCMA: anynode UCMA 4.4.4

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.4.5.10

• Monitor: anynode monitor 4.4.4

• Trace: anynode trace 4.4.4

• Administration: anynode ad 4.4.4

Improvements

• The Java Runtime that is used by the anynode frontend on Windows has been changed from 8u282 to 8u292

• The certificate configuration in the Zoom Phone Premise Peering wizard has been optimized

• The CSR configuration in the Network Security Profile certificate wizards has been optimized

• RESTful API:

  When using /objects/get when exporting low-level objects, all fields are now issued as string to prevent problems like exporting an international number prefix like +49... erroneously as number without +

  Retrieval, setting and deleting of individual objects has been changed. Specifically that all internal store-values are now mapped to JSON-Strings. The API parameter completeData and removeSubsequent have been removed, as they could result in issues

  When importing objects, SIP-transport-ports are not automatically re-assigned when a port-collision has been detected. To reactivate this former behavior, the parameter reassignPortsOnCollision has to be specified

• Some help texts have been revised

• Default certificate database

  some expired certificates have been removed

  some new certificates have been added

• Some minor improvements in the anynode trace analyzer

Bug Fixes

• A potential crash during SIP protocol handling

• An issue with editable select-boxes when used with HTML specific special characters (& for example)

• A potential issue in the anynode trace analyzer which could result in the main thread of the application blocking

anynode Setup 4.4.3 (May 12, 2021) internal release

Technical Setup

• Core: anynode 4.4.3

• Frontend: anynode frontend 4.4.3

• UCMA: anynode UCMA 4.4.3

• Java: JRE 8u292 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.4.5.10

• Monitor: anynode monitor 4.4.3

• Trace: anynode trace 4.4.3

• Administration: anynode ad 4.4.3

Release Notes

• Internal only release

anynode Setup 4.4.2 (April 12, 2021)

Technical Setup

• Core: anynode 4.4.2

• Frontend: anynode frontend 4.4.2

• UCMA: anynode UCMA 4.4.2

• Java: JRE 8u282 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.4.5.10

• Monitor: anynode monitor 4.4.2

• Trace: anynode trace 4.4.2

• Administration: anynode ad 4.4.2

New Features

• New Cloud PBX: Zoom Phone Premise Peering

Improvements

• Display colors of condition status in anynode dashboard has been optimized

• Microsoft Teams Survivable Branch Appliance installer upgraded to 2021.4.5.10

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1k

• Some changes when verifying SANs for TLS connections

• Some changes for replication operations

• VoIP provider profile changed: BabyTel renamed to Cloudli

Bug Fixes

• A minor issue in the signalling view of the anynode trace analyzer

anynode Setup 4.4.1 (March 25, 2021)

Technical Setup

• Core: anynode 4.4.1

• Frontend: anynode frontend 4.4.1

• UCMA: anynode UCMA 4.4.1

• Java: JRE 8u282 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.2.23.4

• Monitor: anynode monitor 4.4.1

• Trace: anynode trace 4.4.1

• Administration: anynode ad 4.4.1

New Features

• New VoIP provider profile: Amazon Chime

Improvements

• VoIP provider profile optimized: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119)

• VoIP provider profile optimized: NetCologne Secure SIPTrunk over Internet

• Added extra configuration option to improve interop during call transfer with certain SIP peers

Bug Fixes

• A minor issue in the signalling view of the anynode trace analyzer

anynode Setup 4.4.0 (March 8 2021)

Technical Setup

• Core: anynode 4.4.0

• Frontend: anynode frontend 4.4.0

• UCMA: anynode UCMA 4.4.0

• Java: JRE 8u282 (private install with anynodefe, now based on openJDK)

• Microsoft Teams SBA: 2021.2.23.4

• Monitor: anynode monitor 4.4.0

• Trace: anynode trace 4.4.0

• Administration: anynode ad 4.4.0

New Features

• Enhanced Microsoft Teams SBA support has been integrated

• anynode frontend can now configure the Microsoft Teams SBA service

• Microsoft Teams SBA service can be installed as part of the anynode Windows installer

• Support for RHEL / CentOS 8

• The status of conditions is now shown on the anynode dashboard

• New VoIP provider profile: TwinCap First SIP

• New VoIP provider profile: NetCologne Secure SIPTrunk over Internet

Improvements

• Persisting a configuration now uses a backup file to ensure safekeeping of a configuration in cases like low available disk space

• Header handling for REFER requests has been improved

• Added additional configuration option to improve interoperability with Unify in certain transfer states

• Retry After header is now observed when receiving error response during SIP register

• The source for Diversion and History Info header can now be derived from additional fields

• Date/Time format can now be specified per user Live tracing is now possible for the anynode frontend

• Enhanced replication of configuration from a primary to a replica system

• The sections of the anynode dashboard in the anynode frontend can now be collapsed and their state is stored per user

• Necessary IP addresses used by Office 365 Government are now automatically white listed when creating Microsoft Teams Nodes

• Access of external databases now uses the ISO-format for date time fields

• Enhanced import of configuration, showing overview and potential warnings

Bug Fixes

• A potential crash of the HTTP event transport in the anynode monitor when parsing data not being a JSON schema

• A potential crash when accessing external SQL databases in the anynode monitor

• A potential issue where a user was logged out when the web browser was minimized

anynode Setup 4.2.8 (February 22, 2021)

Technical Setup

• Core: anynode 4.2.8

• Frontend: anynode frontend 4.2.8

• UCMA: anynode UCMA 4.2.8

• Java: JRE 8u282 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.8

• Trace: anynode trace 4.2.8

• Administration: anynode ad 4.2.8

Improvements

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1j

• Various improvements when tracing sessions going over Microsoft Teams Direct Routing

• Various improvements for monitoring session going over Microsoft Teams Direct Routing

Bug Fixes

• A potential crash on the anynode on Raspberry Pi

• A potential issue with escaping characters in URIs

• A problem when storing configuration of certain header rewrites

• A problem with route supervision has been corrected Some configuration issues in the anynode frontend

• An issue with delete operations in the RESTful-API

anynode Setup 4.2.7 (February 4, 2021)

Technical Setup

• Core: anynode 4.2.7

• Frontend: anynode frontend 4.2.7

• UCMA: anynode UCMA 4.2.7

• Java: JRE 8u282 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.7

• Trace: anynode trace 4.2.7

• Administration: anynode ad 4.2.7

Improvements

• The Java Runtime that is used by the web frontend on Windows has been changed from 8u275 to 8u282

Bug Fixes

• A reference counting issue

• Fixed error exporting call history. If a number or node name was used as filter only the first 500 entries were returned

• In the transport connection list, the wrong entry was selected after a double-click in the filtered state

• Unbound settings were visible in the HTTP client configuration even if unbound settings were disabled

• An issue during evaluation of JSON data in the anynode frontend (object instead of expected array)

• An minor issue in the command line of the web frontend

anynode Setup 4.2.6 (January 22, 2021)

Technical Setup

• Core: anynode 4.2.6

• Frontend: anynode frontend 4.2.6

• UCMA: anynode UCMA 4.2.6

• Java: JRE 8u275 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.6

• Trace: anynode trace 4.2.6

• Administration: anynode ad 4.2.6

Improvements

• Some timing optimizations have been implemented for media negotiation in the context of Microsoft Teams Local Media Optimization

• On Linux systems some ARP requests are now sent when a new dynamic IP address has been created

• LDAP authentication is now also possible for external REST access (either via HTTP or Powershell)

• On pre-configured images (APU, IPU, VMWare, Azure and AWS), the anynode internal system ID is now reset upon first boot

• Some additional diagnostics is now traced when using MSSQL as external database

Bug Fixes

• A potential issue in the scenario wizard for Azure AD dial string directories

• A potential issue during activation of tracing

• No longer checking length of passwords when doing LDAP authentication

anynode Setup 4.2.5 (January 15, 2021)

Technical Setup

• Core: anynode 4.2.5

• Frontend: anynode frontend 4.2.5

• UCMA: anynode UCMA 4.2.5

• Java: JRE 8u275 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.5

• Trace: anynode trace 4.2.5

• Administration: anynode ad 4.2.5

New Features:

• New VoIP provider profile: net-sol SIP

• New VoIP provider profile: GlobalConnect SIP-Trunk

Improvements

• VoIP provider profile changed: For Deutsche Telefon (SIP Trunk) only UDP support is now activated and the upgrade to TCP is deactivated

• During route supervision, sending of call state notifications has been activated for more routing types

• Configuration of provisioning in the anynode frontend has been improved

• Security for TLS-based provisioning has been heightened

• Various small improvements in the monitoring subsystem

• Various small improvements in the anynode trace analyzer

Bug Fixes

• A potential crash in the anynode monitor on 32bit platforms

• A memory leak when using an external MariaDB database

• A potential error when allocating consecutive RTP ports

• A potential issue when showing licenses

• A potential issue when retrieving licenses containing special characters

• A potential issue of the test function for the LDAP authentication

anynode Setup 4.2.4 (December 29, 2020)

Technical Setup

• Core: anynode 4.2.4

• Frontend: anynode frontend 4.2.4

• UCMA: anynode UCMA 4.2.4

• Java: JRE 8u275 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.4

• Trace: anynode trace 4.2.4

• Administration: anynode ad 4.2.4

Bug Fixes

• An incorrect ordering of the priority order of data centers to be used for Microsoft Teams

• An issue in the anynode trace analyzer when associating sessions during during a call transfer

anynode Setup 4.2.3 (December 18, 2020)

Technical Setup

• Core: anynode 4.2.3

• Frontend: anynode frontend 4.2.3

• UCMA: anynode UCMA 4.2.3

• Java: JRE 8u275 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.3

• Trace: anynode trace 4.2.3

• Administration: anynode ad 4.2.3

New Features

• A new condition in the SIP transport is now configurable to improve load balancing

• Call history and event log can now also be stored in an external MS SQL database on Windows

• New VoIP provider profile: B3networks

Improvements

• VoIP provider profile optimized: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119)

• VoIP provider profile optimized: Deutsche Telekom DeutschlandLAN SIP-Trunk (1TR118)

• The Java runtime that is used by the web frontend on Windows has been changed from 8u272 to 8u275

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1i

• Some not used HTTP methods in the anynode frontend web server have been disabled explicitly

Bug Fixes

• An issue when trying to access the anynode frontend from macOS/Safari

• A potential crash in the anynode monitor

• A potential issue with the anynode frontend after use of the REST API

• An issue where the anynode frontend did not fully shut down

anynode Setup 4.2.2 (November 30, 2020)

Technical Setup

• Core: anynode 4.2.2

• Frontend: anynode frontend 4.2.2

• UCMA: anynode UCMA 4.2.2

• Java: JRE 8u272 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.2

• Trace: anynode trace 4.2.2

• Administration: anynode ad 4.2.2

Improvements

• Additional logging into the event log for lack of minimum permissions when logging in has been added

Bug Fixes

• An issue when decoding of geolocation routing headers

• An issue during encoding of multi part bodies

• An issue during parsing of XML documents

• An issue when monitoring transports within load-balancing configurations

• A potential memory leak in the UCMA module

anynode Setup 4.2.1 (November 19, 2020)

Technical Setup

• Core: anynode 4.2.1

• Frontend: anynode frontend 4.2.1

• UCMA: anynode UCMA 4.2.1

• Java: JRE 8u272 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.1

• Trace: anynode trace 4.2.1

• Administration: anynode ad 4.2.1

Improvements

• Additional certificates used by Microsoft 365 are now trusted when using Azure AD

• An individual network-configuration can now be configured for use with Azure AD

Bug Fixes

• An issue when decoding of geolocation information

anynode Setup 4.2.0 (November 12, 2020)

Technical Setup

• Core: anynode 4.2.1

• Frontend: anynode frontend 4.2.1

• UCMA: anynode UCMA 4.2.1

• Java: JRE 8u272 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.2.0

• Trace: anynode trace 4.2.0

• Administration: anynode ad 4.2.0

New Features

• Replication of configuration from one master anynode into one or multiple client anynodes has been integrated

• A new media recording subsystem has been integrated:

  enhances the old one by allowing to establish outgoing calls to direct media streams to go to a remote third party

  It is now possible to play a voice-prompt to the recorded party/parties prior to starting the actual recording

• Provisioning server for SIP devices that will register with our SIP registrar

• ELIN can now be evaluated Initial Microsoft Teams SBA support has been integrated

• anynode QoS-aspects like the DiffServ/TOS octet in IP frames can now be configured directly in the anynode frontend

• The anynode frontend can now use an LDAP server for authentication and authorization

• A HTTP REST client has been integrated for event notification

• An SMTP client has been integrated which is currently being used for event notification

• A template parser has been integrated that is being used by the provisioning server and the new event notifications

• An XML parser has been integrated to allow anynode to understand certain XML payloads

• Support for external databases for call history and event log (mariaDB, postgreSQL on Windows also MS SQL) has been added

• Support for JSON during import into and export from the static user directory

Improvements

• The manipulations of a node now also allow the manual configuration of the display name

• Route supervision has been improved to support some additional information elements

• TLS handling has been improved: Certificate validation for TLS connections has been improved in various aspects

  supports SNI in certain cases certificate chains of remote peer can be retrieved

• OpenSSL optimizations:

  The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1h

  The OpenSSL base security level can now be configured ECDH can now be disabled

  The version of the OpenSSL library currently in use by the base anynode is now being shown on the information page of the anynode frontend

• The handling of network interfaces has been improved

• The Java runtime that is used by the Windows version of the web frontend has been updated to 8u272

• Support to be able to use syntactically invalid user agent strings for certain functionality (provisioning and call history for example)

• SDP negotiation has been improved in specific circumstances

• For sessions going over MS Teams nodes the discard reason can now be manually configured

• The directory based on Azure AD now supports various filters based on user attributes, group membership, licenses and service plans

• The Debian install scripts now use the init system helpers to improve make creation of docker containers easier

• Added the ability to delay accepting of a session to be able to improve interoperability with certain third party VoIP systems

• Various small enhancements for the configuration and operation of the SIP user agent to improve interoperability with certain third party VoIP systems

• Interoperability to SwyxWare has been improved Support for RFC3327 (Path Header) has been added

• Some performance improvements in various anynode sub systems have been applied

• VoIP provider profile optimized: Versatel 1&1 Voice Business

• VoIP provider profile optimized: Telecom5

• VoIP provider profile optimized: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119)

• VoIP provider profile optimized: Deutsche Telekom DeutschlandLAN SIP-Trunk (1TR118)

• VoIP provider profile optimized: Deutsche Telekom DeutschlandLAN Cloud PBX (secure)

• VoIP system profile optimized: MS Teams

• VoIP system profile optimized: SIP phones

• Monitoring of calls in certain fringe cases has been optimized Performance improvements in anynode monitoring

• The REST API and the PowerShell scripts for configuration have been extended

• The configuration interface UX has been improved in various places

• Various improvements in call history and call history export

• Various potentially long list based configuration fields can now be filtered with a free text to make it easier to find information

• A user specific name can be set on the configuration interface which is also shown in the title of the web browser

• The session timeout of the configuration web interface is now configurable individually for each user

• The configuration web interface can now also present a certificate chain for HTTPS connections

• Tracing can now also be configured for the other anynode daemons/services

• Various improvements in the anynode trace analyzer:

  now shows HTTP operations

  various fringe cases have been improved

  performance improvements

  many other improvements

Bug Fixes

• A problem with evaluation of the timezone in the anynode monitor

• A potential issue with WMI in the anynode monitor. The number of active calls in the node information was overwritten, if other node parameter changed

• A potential issue when decoding of an audio signal in the anynode trace analyzer

• A potential issue when decoding strings with Germany special characters in the anynode trace analyzer

anynode Setup 4.0.19 (November 16, 2020)

Technical Setup

• Core: anynode 4.0.19

• Frontend: anynode frontend 4.0.19

• UCMA: anynode UCMA 4.0.19

• Java: JRE 8u262 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.19

• Trace: anynode trace 4.0.19

• Administration: anynode ad 4.0.19

Improvements

• Improved LDAP retrieval on Linux where a late protocol error could inhibit already assembled search results

Bug Fixes

• A potential processing audio packets with zero length

anynode Setup 4.0.18 (October 12, 2020)

Technical Setup

• Core: anynode 4.0.18

• Frontend: anynode frontend 4.0.18

• UCMA: anynode UCMA 4.0.18

• Java: JRE 8u262 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.18

• Trace: anynode trace 4.0.18

• Administration: anynode ad 4.0.18

Improvements

• Improved SIP authentication interoperability with Swyx peers

anynode Setup 4.0.17 (October 02, 2020) internal Version

Technical Setup

• Core: anynode 4.0.17

• Frontend: anynode frontend 4.0.17

• UCMA: anynode UCMA 4.0.17

• Java: JRE 8u262 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.17

• Trace: anynode trace 4.0.17

• Administration: anynode ad 4.0.17

Improvements

• The interoperability of RTCP in respect to the CNAME field has been improved

anynode Setup 4.0.16 (September 10, 2020) internal Version

Technical Setup

• Core: anynode 4.0.16

• Frontend: anynode frontend 4.0.16

• UCMA: anynode UCMA 4.0.16

• Java: JRE 8u262 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.16

• Trace: anynode trace 4.0.16

• Administration: anynode ad 4.0.16

Bug Fixes

• A potential busy loop in TLS handling

• A potential deadlock in Windows TCP code

anynode Setup 4.0.15 (September 07, 2020)

Technical Setup

• Core: anynode 4.0.15

• Frontend: anynode frontend 4.0.15

• UCMA: anynode UCMA 4.0.15

• Java: JRE 8u262 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.15

• Trace: anynode trace 4.0.15

• Administration: anynode ad 4.0.15

Improvements

• The Java runtime that is used by the Windows version of the web frontend has been updated from 8u252 to 8u262

Bug Fixes

• An issue within the anynode frontend where certain information was not updated correctly for some time when the underlying system-clock was put back

• An issue with the test function for the Azure AD directory when using group information

anynode Setup 4.0.14 (August 19, 2020)

Technical Setup

• Core: anynode 4.0.14

• Frontend: anynode frontend 4.0.14

• UCMA: anynode UCMA 4.0.14

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.14

• Trace: anynode trace 4.0.14

• Administration: anynode ad 4.0.14

Improvements

• The REST API now supports setting the local SIP domain when creating a provider node

Bug Fixes

• When using the node wizard for the MS Teams Direct Routing Carrier Trunk, the tenants FQDN could remain empty

• Fixed an issue where the selection of objects could be wrong during import

• An issue when comparing phone numbers with wildcards in the Azure AD directory

• Some potential issues with the REST API:

  when creating a provider node, the ports were not set

  during import of an object the result sometimes could be a wrong object

  setting of the AOR for SIP systems did not work

  manipulations in MS Teams nodes can now be changed

  when setting maximum trace size, the value is now interpreted as megabytes instead of bytes

  when issuing REST calls for nodes, references to sub-objects could be lost

• An issue with updating the name of a network controller on the anynode dashboard

anynode Setup 4.0.13 (July 24, 2020)

Technical Setup

• Core: anynode 4.0.13

• Frontend: anynode frontend 4.0.13

• UCMA: anynode UCMA 4.0.13

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.13

• Trace: anynode trace 4.0.13

• Administration: anynode ad 4.0.13

Improvements

• Various additional optimizations for the access to Azure AD have been integrated

Bug Fixes

• Some potential issues during configuration of the access to Azure AD

• Some potential issues with the REST API and the PowerShell scripts

anynode Setup 4.0.12 (July 13, 2020)

Technical Setup

• Core: anynode 4.0.12

• Frontend: anynode frontend 4.0.12

• UCMA: anynode UCMA 4.0.12

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.12

• Trace: anynode trace 4.0.12

• Administration: anynode ad 4.0.12

Improvements

• In the frontend, the node and route select box in the call history filter can now handle special characters in node and route names.

• An optimization for the access to Azure AD has been integrated

• A new version of the web server-component has been integrated into the anynode frontend

Bug Fixes

• A memory leak during establishment of a UDP channel

• A memory leak during certificate validation of a TLS channel

anynode Setup 4.0.11 (June 30, 2020)

Technical Setup

• Core: anynode 4.0.11

• Frontend: anynode frontend 4.0.11

• UCMA: anynode UCMA 4.0.11

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.11

• Trace: anynode trace 4.0.11

• Administration: anynode ad 4.0.11

New Features

• The REST API of the anynode frontend has been extended to be able to configure incoming and outgoing manipulations

• The Azure AD requests now also supported nested names

Improvements

• Additional info is being conveyed in the anynode trace analyzer pertaining to Azure AD connections

• Additional info is being shown in the monitoring for the anynode frontend pertaining to Azure AD connection

• Microsoft-Graph HTTP requests can now restart in case of loss of the HTTP connection

• Performance of Azure AD retrieval in case of large amount of entries has been improved

Bug Fixes

• A potential issue with decoding strings with special characters in the anynode trace analyzer

• A potential issue when configuring white list entries via REST API

• A potential issue during reconfiguration of the MS-Graph layer used for Azure AD

• A potential issue during filtering of Azure AD results

anynode Setup 4.0.10 (June 16, 2020)

Technical Setup

• Core: anynode 4.0.10

• Frontend: anynode frontend 4.0.10

• UCMA: anynode UCMA 4.0.10

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.10

• Trace: anynode trace 4.0.10

• Administration: anynode ad 4.0.10

Bug Fixes

• An issue with the configuration of filters for Azure AD directories

anynode Setup 4.0.9 (June 12, 2020)

Technical Setup

• Core: anynode 4.0.9

• Frontend: anynode frontend 4.0.9

• UCMA: anynode UCMA 4.0.9

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.9

• Trace: anynode trace 4.0.9

• Administration: anynode ad 4.0.9

New Features

• New VoIP provider profile: gnTel SIP-Trunk

Improvements

• Optional filters can now be defined when using an Azure-AD based directory

• Attributes in Azure-AD are now case-insensitive

• The MS-Graph-API version used for Azure-AD operations is now beta by default

• Improved outbound call-failure reporting when the remote registrar answered with an error

• Some REST-APIs of the anynode frontend for use with automatic configuration have been improved

• The PowerShell module provided for remote configuration has been enhanced

• The Microsoft Teams (Local Media Optimization)-profile now has ICE-lite activated for media negotiation

• Outgoing calls now ignore the matching condition for outgoing calls per default

Bug Fixes

• A potential issue with anynode internal IPC

• An issue during digest authentication with some specific peers

• A potential memory leak in the anynode-internal user-directory

• A potential issue when generating HTTP-URIs during Azure-AD operation

• A rare issue that caused the anynode frontend to report a TCP-based SIPtransport being used when it in fact was UDP

• A problem when generating the call-history export in JSON-format

• A problem where setting the local certificate for a node via REST API caused a modification of the list of trusted certificates

anynode Setup 4.0.8 (May 19, 2020)

Technical Setup

• Core: anynode 4.0.8

• Frontend: anynode frontend 4.0.8

• UCMA: anynode UCMA 4.0.8

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.8

• Trace: anynode trace 4.0.8

• Administration: anynode ad 4.0.8

Bug Fixes

• Names of RFC6188-crypto-suites

• Fixed an issue which caused the initial boot of the APU and IPU images to fail

anynode Setup 4.0.7 (May 18, 2020)

Technical Setup

• Core: anynode 4.0.7

• Frontend: anynode frontend 4.0.7

• UCMA: anynode UCMA 4.0.7

• Java: JRE 8u252 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.7

• Trace: anynode trace 4.0.7

• Administration: anynode ad 4.0.7

New Features

• New VoIP provider profile: autphone aut-trunk

• An Asserted URI can now be configured as fall back for incoming calls

Improvements

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1g

• The Java runtime that is used by the Windows version of the anynode frontend has been updated from 8u242 to 8u252

Bug Fixes

• A potential issue when receiving invalid G.722 data

• An issue in media view of the anynode trace analyzer: If the remote IP address for send and received packets was different, the wrong remote address for received packets was shown. (ported back from 4.1.4)

• A potential issue when cloning Media Negotiation

anynode Setup 4.0.6 (April 24, 2020)

Technical Setup

• Core: anynode 4.0.6

• Frontend: anynode frontend 4.0.6

• UCMA: anynode UCMA 4.0.6

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.6

• Trace: anynode trace 4.0.6

• Administration: anynode ad 4.0.6

New Features

• Support for JSON export in Call

Bug Fixes

• A potential issue when receiving invalid G.722 data

• A potential issue with special characters in the Call History

anynode Setup 4.0.5 (April 14, 2020)

Technical Setup

• Core: anynode 4.0.5

• Frontend: anynode frontend 4.0.5

• UCMA: anynode UCMA 4.0.5

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.5

• Trace: anynode trace 4.0.5

• Administration: anynode ad 4.0.5

New Features

• Support for Ubuntu 20.04

Improvements

• For the VoIP system profile Microsoft Teams Direct Routing Carrier the user can now decide in the wizard whether the SBC FQDN should also be entered as tenant FQDN

• VoIP provider profile optimized: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119)

• VoIP provider profile optimized: Telecom5

anynode Setup 4.0.4 (April 6, 2020)

Technical Setup

• Core: anynode 4.0.4

• Frontend: anynode frontend 4.0.4

• UCMA: anynode UCMA 4.0.4

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.4

• Trace: anynode trace 4.0.4

• Administration: anynode ad 4.0.4

New Features:

• The new Microsoft Teams Direct Routing feature Local Media Optimization has been made visible by default

Improvements

• The included PowerShell module now checks whether the necessary version of PowerShell

Bug Fixes

• An potential authentication problem when starting a live-trace from the anynode frontend

anynode Setup 4.0.3 (April 3, 2020)

Technical Setup

• Core: anynode 4.0.3

• Frontend: anynode frontend 4.0.3

• UCMA: anynode UCMA 4.0.3

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.3

• Trace: anynode trace 4.0.3

• Administration: anynode ad 4.0.3

Bug Fixes

• A potential crash of the anynode trace analyzer in the streams view: If entries were available on the properties tab and the mouse was right clicked below the entries the crash occurred

• In the anynode frontend, the media setup and the RTP payload type wizard could not be opened

anynode Setup 4.0.2 (March 30, 2020)

Technical Setup

• Core: anynode 4.0.2

• Frontend: anynode frontend 4.0.2

• UCMA: anynode UCMA 4.0.2

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.2

• Trace: anynode trace 4.0.2

• Administration: anynode ad 4.0.2

Improvements

• VoIP provider changed: Deutsche Telekom CompanyFlex SIP-Trunk (1TR119) adapted to new requirements

Bug Fixes

• Options messages were not sent out in all circumstances

• An issue where the VoIP-providers Deutsche Telekom CompanyFlex SIP-Trunk (1TR119), Deutsche Telekom DeutschlandLAN Cloud PBX (secure), Deutsche Telekom DeutschlandLAN SIP-Trunk (1TR118) and the VoIP system Microsoft Teams Direct Routing Carrier Trunk were not shown correct in the wizard

• An issue where a node was potentially still marked as red in the wizard even though the configuration was correctly completed

• The anynode monitor and the anynode trace analyzer could show wrong information in case of path replacement

• The anynode trace analyzer did not show MWI-messages under all circumstances

anynode Setup 4.0.2 (March 30, 2020)

Technical Setup

• Core: anynode 4.0.1

• Frontend: anynode frontend 4.0.1

• UCMA: anynode UCMA 4.0.1

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.1

• Trace: anynode trace 4.0.1

• Administration: anynode ad 4.0.1

Improvements

• The naming of the Microsoft Teams Media Path Optimization feature has been changed to Local Media Path Optimization

anynode Setup 4.0.0 (March 24, 2020)

Technical Setup

• Core: anynode 4.0.0

• Frontend: anynode frontend 4.0.0

• UCMA: anynode UCMA 4.0.0

• Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

• Monitor: anynode monitor 4.0.0

• Trace: anynode trace 4.0.0

• Administration: anynode ad 4.0.0

New Features

• Support for Microsoft Teams Direct Routing Carrier Trunk

• Support for Microsoft Teams Direct Routing Local Media Optimization

• To optimize the handling of emergency calls, sessions can now be prioritized

• It is now possible to only trace calls going over select routes. This permits to analyze calls on large systems.

• Support for German PSAP specification TR Notruf 2

• Extensive upgrade to REST-interfaces for automated configuration of anynode

• The display-width of the anynode frontend can now be configured

• New VoIP provider profile: CompanyFlex

• New VoIP provider profile: O2

• New VoIP provider profile: reventix SIPbase (secure)

• New VoIP system profile: Microsoft Teams Direct Routing Carrier

• New VoIP system profile: Microsoft Teams Direct Routing (Local Media Optimization)

• New VoIP system profile: Clarity Communication Center

Improvements

• Support for End-To-Access Edge Media Security to support encrypted operation of German Telekom products CompanyFlex and CloudPbx

• Optimized media-handling for T.38

• Enhancement of tracing-system to optimize performance

• Music-on-Hold is now being forwarded by default

• Optimizations to improve support of remote parties behind a NAT

• Improved interoperability with Grandstream devices

• For provider-profiles successive ports for RTP and RTCP are now used by default

• The transmission of RTCP can now be disabled.

• The maximum length of a DTMF forwarded via RFC2833 can now be limited

• When using T.38 and ClearChannel media, this can now be seen on the anynode frontend and in the anynode trace analyzer

• T.38-packets are now shown in the anynode trace analyzer

• The anynode trace analyzer now shows all codecs that have been used in a session Early-media

• audio-data can now be shown in the anynode trace analyzer

• The icons for resources shown on the anynode frontend (CPU/RAM...) are now multi-color to differentiate different warning levels

• Various new options to optimize compatibility of signalling and media-handling in fringe cases

• For each user-account created in the anynode frontend an email-address can now be stored

• VoIP provider profile changed: Deutsche Telefon (SIP Trunk)

• VoIP provider profile changed: Deutsche Telekom DeutschlandLAN Cloud PBX (secure)

• VoIP system profile changed: Grandstream GXW4200 Series

Bug Fixes

• A potential deadlock during client authentication in a SIP dialogue

• An issue when recording non-PCM audio-data

• An issue when showing audio-data in the anynode trace analyzer if codecs used changing sample rates