anynode release 4.6 billboard graphic

anynode release 4.6

Version Highlights

  • User interface improvements: In the new anynode version, we have improved the user interface on our software session border controller, presenting a more compact layout. This new version features more detailed descriptions, and more straightforward wording, in our wizards and notification messages.

  • Built-in anynode update: Wouldn't it be nice if you could see the latest version information directly in anynode and install the appropriate updates right from there? With anynode 4.6 this is now possible! In addition, it also always checks immediately which versions are still supported with your installed LOD key. This feature is currently only unlocked for the Windows version of anynode.

  • Hot standby graphic user interface: With our new hot standby feature, you define important rules to let a secondary anynode system take over in the event of an emergency as part of a high-availability configuration In the graphical user interface of this feature, all conditions for a switchover to the secondary standby system and back can be set. For example, an inactive maintenance mode can be selected for the active role of the anynode system within a hot standby configuration. When the system enters maintenance mode, the secondary anynode then takes over operation after a scheduled system update that also requires a reboot. The system can be configured so that the secondary anynode system retains the active role.

  • Tagging and enhanced dial string rewriting: In order to classify incoming calls even better, version 4.6 now allows you to provide dial strings with tags that you define yourself. The tagging of special incoming calls - like special or emergency numbers for example - enables the application of special rules in the process or routing. With the introduction of tags, you can also eliminate the cumbersome use of prefixes, which always had to be removed after routing so that they would not be transmitted to the remote station.

  • SQL integration and dynamic user directories: Good news: anynode can also retrieve information from SQL databases and use it for routing. Just like it does with Azure and standard Active Directory. In addition, user directories which previously could only be created statically, can now also access dynamic data sources. This greatly simplifies external data maintenance, even by personnel without SBC configuration knowledge.

  • Reverse number lookup (RNL): Dynamic routing via Route Supervision with the REST server is also possible with SQL databases, Azure and standard Active Directory. This enables routing decisions based on individual data record fields, dial string rewriting (rewriting of phone numbers) as well as setting of display names. In practice, a phone number can be assigned a special display name containing name and company, which provides many advantages in day-to-day business operations.

  • Proxy server support for licensing and updates: In practice, in many company networks access to the Internet is only possible via a proxy server. With the new version 4.6, anynode also supports connecting to the Internet via proxy server. This means that updates and licenses can be obtained by the anynode frontend using a configured proxy.

  • Support of numverify and real phone validation services: The support of Number Verification in Route Supervision helps to save unnecessary costs and man-hours. With version 4.6, anynode supports the numverify and Real Phone Validation services. With these services, phone numbers of incoming calls can be checked for validity, number type and affiliation to a specific provider. This allows suspect calls ( e.g., calls with fake phone numbers, etc) to be blocked automatically or forwarded directly to an alternate route.

  • REST API enhancement: The integration of anynode into existing back ends via the REST interface enables a whole range of configuration and access options without the manual use of the graphical user interface.Advanced REST API functions have been added. For example, a new user with adjustable access rights can be added to anynode‘s local user management via PowerShell script, or a certificate can be added to a specific node‘s certificate store.

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