billboard graphic anynode release 3.20

anynode release 3.20

Version Highlights

  • Media Recording: Media Recording can be activated in the Routing Forwarding Profile to be able to record audio data on all routes associated with that profile. It is possible to configure recording to be either in WAV, raw G.711 or in an internal format. Recordings can downloaded either from the call-history or with a REST API for automated processing. Download of recordings requires a new specific user-permission. It is possible to automatically wipe recordings after a certain number of days. This feature has been implemented to facilitate either the creation legal evidence on threatening calls, measure call quality, optimize processes and quality as well as support training & coaching. This feature requires an additional license.

  • Route Supervision: Route Supervision allows to send meta-data about a call to be routed to an external HTTP/ REST-Server. This server can use this data to either just log the call (including its duration) or pro-actively affect the call by letting the routing take place, prevent routing and even change the target of the call before it is actually routed.

  • REST server: Using the integrated REST-server, administrative tasks can be automated: Importing or exporting configuration-files, activation/deactivation and downloading of anynode-traces, activation/deactivation of maintenance-mode, requesting licenses via LOD-key or uploading license-files, reading the information provided on the dashboard.

  • Azure Active Directory: It is now possible to use data in Azure Active Directory to control the routing of calls.

anynode Setup 3.20.13 (February 26, 2020)

Technical Setup

  • Core: anynode 3.20.13

  • Frontend: anynode frontend 3.20.13

  • UCMA: anynode UCMA 3.20.13

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

  • Monitor: anynode monitor 3.20.13

  • Trace: anynode trace 3.20.13

  • Administration: anynode ad 3.20.13

Improvements

  • The Java runtime that is used by the anynode frontend on Windows has been updated from 8u232 to 8u242

  • The notation of the Plusnet VoIP provider profiles has been adjusted

Bug Fixes

  • A potential issue when forwarding early-media

  • A potential problem during the export of call-history data

  • Some display-issues of wizards in the anynode frontend

anynode Setup 3.20.12 (February 14, 2020)

Technical Setup

  • Core: anynode 3.20.12

  • Frontend: anynode frontend 3.20.12

  • UCMA: anynode UCMA 3.20.12

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

  • Monitor: anynode monitor 3.20.12

  • Trace: anynode trace 3.20.12

  • Administration: anynode ad 3.20.12

Improvements

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

  • Some changes in the trace-subsystem have been implemented to optimize system-load during logging

Bug Fixes

  • A potential crash during use of OpenSSL

anynode Setup 3.20.11 (January 13, 2020)

Technical Setup

  • Core: anynode 3.20.11

  • Frontend: anynode frontend 3.20.11

  • UCMA: anynode UCMA 3.20.11

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

  • Monitor: anynode monitor 3.20.11

  • Trace: anynode trace 3.20.11

  • Administration: anynode ad 3.20.11

Bug Fixes

  • A potential crash of the anynode-monitor during the conversion of the old event-log format

  • A potential memory-leak in the anynode frontend

anynode Setup 3.20.10 (January 07, 2020)

Technical Setup

  • Core: anynode 3.20.10

  • Frontend: anynode frontend 3.20.10

  • UCMA: anynode UCMA 3.20.10

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

  • Monitor: anynode monitor 3.20.10

  • Trace: anynode trace 3.20.10

  • Administration: anynode ad 3.20.10

Bug Fixes

  • The creation of roles in the anynode frontend could fail under certain conditions if the super user is the only existing user in the system.

  • A potential memory-leak for failed registrations in UCMA-nodes

  • A potential synchronisation issue during re-registration in UCMA-nodes

  • A potential crash during validation of the connection to a web server for Route Supervision

anynode Setup 3.20.9 (December 22, 2019)

Technical Setup

  • Core: anynode 3.20.9

  • Frontend: anynode frontend 3.20.9

  • UCMA: anynode UCMA 3.20.9

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

  • Monitor: anynode monitor 3.20.9

  • Trace: anynode trace 3.20.9

  • Administration: anynode ad 3.20.9

Improvements

  • A directory of configured users of a Registrar can now be obtained

Bug Fixes

  • A potential crash when receiving specific redirection history

  • A potential crash when using users in a registrar

  • A problem when forwarding reject reasons for the registrar

  • A problem with the object updater of LDAP user-directories

anynode Setup 3.20.8 (December 09, 2019)

Technical Setup

  • Core: anynode 3.20.8

  • Frontend: anynode frontend 3.20.8

  • UCMA: anynode UCMA 3.20.8

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

  • Monitor: anynode monitor 3.20.8

  • Trace: anynode trace 3.20.8

  • Administration: anynode ad 3.20.8

Bug Fixes

  • A potential crash when using registration transport connections

anynode Setup 3.20.7 (November 29, 2019)

Technical Setup

  • Core: anynode 3.20.7

  • Frontend: anynode frontend 3.20.7

  • UCMA: anynode UCMA 3.20.7

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

  • Monitor: anynode monitor 3.20.7

  • Trace: anynode trace 3.20.7

  • Administration: anynode ad 3.20.7

Bug Fixes

  • A missing initialization of a default timer for SIP-handling

anynode Setup 3.20.6 (November 21, 2019)

Technical Setup

  • Core: anynode 3.20.6

  • Frontend: anynode frontend 3.20.6

  • UCMA: anynode UCMA 3.20.6

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

  • Monitor: anynode monitor 3.20.6

  • Trace: anynode trace 3.20.6

  • Administration: anynode ad 3.20.6

Improvements

  • A protocol-timer used during REFER-handling has been made configurable and its default value has been increased for Microsoft Teams Direct Routing

Bug Fixes

  • A potential problem when displaying the node-status on the anynode dashboard and within the anynode trace analyzer

anynode Setup 3.20.5 (November 20, 2019)

Technical Setup

  • Core: anynode 3.20.5

  • Frontend: anynode frontend 3.20.5

  • UCMA: anynode UCMA 3.20.5

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

  • Monitor: anynode monitor 3.20.5

  • Trace: anynode trace 3.20.5

  • Administration: anynode ad 3.20.5

Bug Fixes

  • Changed some default configuration values for Microsoft Teams Direct Routing to improve interoperability for call-hold & REFER scenarios

anynode Setup 3.20.4 (November 15, 2019)

Technical Setup

  • Core: anynode 3.20.4

  • Frontend: anynode frontend 3.20.4

  • UCMA: anynode UCMA 3.20.4

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

  • Monitor: anynode monitor 3.20.4

  • Trace: anynode trace 3.20.4

  • Administration: anynode ad 3.20.4

Improvements

  • The route supervision now sets the Reason to not Responding when a call is being canceled by a user

Bug Fixes

  • Corrected a problem with the Load Balancer where configuration-changes were not always adopted on the fly

  • An object-leak in form of a trace-stream has been corrected in the UCMA-module

  • An error closing trace-streams in the anynode trace analyzer

anynode Setup 3.20.3 (November 04, 2019)

Technical Setup

  • Core: anynode 3.20.3

  • Frontend: anynode frontend 3.20.3

  • UCMA: anynode UCMA 3.20.3

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

  • Monitor: anynode monitor 3.20.3

  • Trace: anynode trace 3.20.3

  • Administration: anynode ad 3.20.3

Improvements

  • The ability that UCMA nodes can now refresh SfB-users that were disconnected due to changes in their back end configuration has been added

Bug Fixes

  • A possible deadlock in the anynode monitor during data-exchange with the anynode frontend

anynode Setup 3.20.2 (October 28, 2019)

Technical Setup

  • Core: anynode 3.20.2

  • Frontend: anynode frontend 3.20.2

  • UCMA: anynode UCMA 3.20.2

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

  • Monitor: anynode monitor 3.20.2

  • Trace: anynode trace 3.20.2

  • Administration: anynode ad 3.20.2

Improvements

  • Some configuration-defaults have been improved for media negotiation with Microsoft Teams Direct Routing

Bug Fixes

  • A minor issue in the anynode frontend during configuration of media-negotiation with ICE-settings

anynode Setup 3.20.1 (October 24, 2019)

Technical Setup

  • Core: anynode 3.20.1

  • Frontend: anynode frontend 3.20.1

  • UCMA: anynode UCMA 3.20.1

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

  • Monitor: anynode monitor 3.20.1

  • Trace: anynode trace 3.20.1

  • Administration: anynode ad 3.20.1

Improvements

  • The anynode.mib file for SNMP is now being installed into the RES-folder on all platforms

Bug Fixes

  • Some minor issues during media-negotiation

  • An issue with the monitoring of file-system usage has been corrected for Raspbian

  • Some minor issues of the anynode trace analyzer

  • Some anynode frontend could possibly fail on systems with only one CPU core

anynode Setup 3.20.0 (October 15, 2019)

Technical Setup

  • Core: anynode 3.20.0

  • Frontend: anynode frontend 3.20.0

  • UCMA: anynode UCMA 3.20.0

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

  • Monitor: anynode monitor 3.20.0

  • Trace: anynode trace 3.20.0

  • Administration: anynode ad 3.20.0

New Features

  • anynode can now record media-data of calls going over specific routes

  • anynode can now do route-supervision on specified routes by sending meta-data of calls to an external HTTP/REST-server and use results from same server for actual routing

  • The REST-Server in the anynode frontend was extended to be able to invoke various administrative functions from remote

  • anynode now supports Azure AD as a source for dial-string directories

  • The file system below the directory used to store various runtime-data by various anynodemodules can now be monitored for sufficient free space

  • The rate of SIP-sessions per time-units can now be limited

Improvements

  • The anynode trace analyzer has been extended to include a view that shows SIP-transactions that specially highlights problematic conditions

  • The anynode trace analyzer has been extended to support various new features of the new 3.20 series of anynode ICE/TURN handling has been improved for some specific scenarios

  • Handling of incoming SDP with 0.0.0.0 addresses and 0 ports has been improved.

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

  • Multiple improvements in handling specific SIP-headers and their forwarding have been integrated

  • Negotiating SRTP was improved in some specific circumstances

  • SIP session expiration handling has been improved to accommodate some faulty remote SIP implementations

  • Multiple improvements during UCMA-handling

  • The internal event-log has been reorganized to now use an internal database instead of a text-file

  • The call-history has been extended by various new fields

  • The Java runtime that is used by the anynode frontend has been changed from 8u212 to 8u222

  • VoIP provider profile changed: Deutsche Telekom (IP-basiert)

  • New VoIP provider profile: Tell-Phone SIP Trunk

  • New VoIP provider profile: Grandstream GXW4200 Series

  • New VoIP provider profile: Digium Switchvox

  • An automatic redirection from HTTP to HTTPS is now possible with the anynode frontend

  • It is now possible to automatically obtain a license with updated SUS status by a push of a button from within the anynode frontend

Bug Fixes

  • A problem was corrected where no new session were accepted after reconfiguration in very specific circumstances

  • A problem was corrected where under extreme rare conditions authentication of SIPtransactions was not done properly

  • A potential race-condition during allocation and release of UDP-channels on Windows

  • A problem when routing parallel calls using an empty directory

  • Some minor issues in the anynode monitor

  • A small problem in the anynode frontend was corrected when adding a license and the license-server was not reachable