anynode release 4.2 billboard graphic

anynode release 4.2

Version Highlights

  • Multiple Event Notifications: On top of the existing notifications via SNMP and WMI, it is now also possible to push events via SMTP and HTTP/REST. This broadens the ability to distribute events happening in anynode‘s daily operations towards administrators.

  • LDAP based User and Group Management: On top of the existing user management, it is now also possible to use an LDAP directory for authentication and authorization for access to anynode configuration interface. This enables system administrators to use existing rights management in a corporate network to grant/revoke usage right for anynode using their familiar mechanisms.

  • Master/Client Replication: The new master/client replication mechanism allows to share configuration on multiple anynodes. This makes the deployment and maintenance of high availability or load-balanced systems much easier.

  • External Database Support: anynode can now also write all call history and event logs into external databases. This way multiple anynodes can write into a unified destination to consolidate data of high availability or load balanced systems.

  • Provisioning Server: The new provisioning server makes deployment of supported SIP devices a much easier task. Depending on the network size either DHCP options or Zero Touch Configuration can be used to make commissioning a breeze. The devices retrieve their configuration automatically from anynode using encrypted mechanisms by default.

  • Media Recording to external Target: On top of the existing local media recording feature, it is now also possible to divert the media stream(s) of a connection to a third party device via SIP for remote recording.

  • Microsoft Teams SBA: The support of the new Microsoft Teams Survivable Branch Appliance feature allows local Teams users to still achieve basic telephony even if the Teams cloud services are offline or the connection to those services is disturbed.

  • REST API and Powershell: The depth of anynode‘s configuration APIs has been extensively expanded. Much more functionality is available for automatic deployment of anynode in virtual or cloud scenarios.

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