anynode release 4.0
Version Highlights
-
Multi-Tenancy: With this feature anynode and Microsoft Teams Direct Routing can use one Session Border Controller to serve many tenants. This feature is especially interesting for companies such as IT services and carriers that offer managed service platforms to serve multiple clients in an easy fashion.
-
Local Media Optimization: Local Media Optimization is a new feature within Microsoft Teams Direct Routing which enables to keep media local to your network. This enables optimal RTP media flow for in house hosted SBCs with local connections to providers or PBXs around the world.
-
REST API/PowerShell: With the REST API and PowerShell scripts, anynode configurations can be created, controlled and edited in detail, automatically and remotely.
-
E911 Emergency Call: Dynamic emergency calling for Microsoft Teams Direct Routing provides the capability to configure and route emergency calls based on the current location of the Teams client. This feature is only available in select regions (in the United States for example).
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