anynode release 3.12
Intro 3.12
Einleitung
anynode Setup 3.12.9 (November 19, 2018)
Technical Setup
-
Core: anynode 3.12.9
-
Frontend: anynode frontend 3.12.9
-
UCMA: anynode UCMA 3.12.9
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.9
-
Trace: anynode trace 3.12.9
-
Administration: anynode ad 3.12.9
Improvements
-
The Silk-codec default bit rates have been tweaked to match the MS-Teams defaults, rather than the Skype for Business defaults
Bug Fixes
-
A problem during processing of response-codes for OPTIONS-packets has been corrected in the anynode trace analyzer and the anynode monitor module
-
A potential problem during file-upload on systems with two or less CPU-cores
-
A potential problem during playback of audio-signals
anynode Setup 3.12.8 (November 07, 2018)
Technical Setup
-
Core: anynode 3.12.8
-
Frontend: anynode frontend 3.12.8
-
UCMA: anynode UCMA 3.12.8
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.8
-
Trace: anynode trace 3.12.8
-
Administration: anynode ad 3.12.8
Improvements
-
The Silk-codec default bit rates have been tweaked to match the MS-Teams defaults, rather than the Skype for Business defaults
Bug Fixes
-
A potential crash of anynode during shutdown while an LDAP-operation was ongoing
-
A potential crash of the anynode monitor during shutdown
-
A potential problem when monitoring nodes via WMI or SNMP
-
In the anynode trace analyzer an error during decoding of RTP packets for audio view has been corrected: If a new SDP negotiation for dynamic codecs was done during the call, the packets from the RTP send stream were discarded.
-
A problem during call-transfer on UCMA-nodes
anynode Setup 3.12.7 (October 26, 2018)
Technical Setup
-
Core: anynode 3.12.7
-
Frontend: anynode frontend 3.12.7
-
UCMA: anynode UCMA 3.12.7
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.7
-
Trace: anynode trace 3.12.7
-
Administration: anynode ad 3.12.7
Bug Fixes
-
A problem with day/time-conditions
-
A problem with audio-level scaling when using G.722 codec
-
A problem when activating UCMA live-trace with enabled authentication in anynode frontend
anynode Setup 3.12.6 (October 17, 2018)
Technical Setup
-
Core: anynode 3.12.6
-
Frontend: anynode frontend 3.12.6
-
UCMA: anynode UCMA 3.12.6
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.6
-
Trace: anynode trace 3.12.6
-
Administration: anynode ad 3.12.6
Improvements
-
The Silk codec default bit rates have been tweaked to match the MS-Teams defaults, rather than the Skype for Business defaults
Bug Fixes
-
A potential problem during redirection of a call on a registrar-node
-
A potential problem when setting the busy-state on a UCMA-node
-
When retrieving a subscription license failed, the status Updating was still displayed in the frontend
anynode Setup 3.12.5 (October 09, 2018)
Technical Setup
-
Core: anynode 3.12.4
-
Frontend: anynode frontend 3.12.4
-
UCMA: anynode UCMA 3.12.4
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.4
-
Trace: anynode trace 3.12.4
-
Administration: anynode ad 3.12.4
Bug Fixes
-
Another scenario that could produce an abort of the UCMA-module
-
An issue with detection of ended sessions in the anynode monitor
anynode Setup 3.12.4 (October 02, 2018)
Technical Setup
-
Core: anynode 3.12.4
-
Frontend: anynode frontend 3.12.4
-
UCMA: anynode UCMA 3.12.4
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.4
-
Trace: anynode trace 3.12.4
-
Administration: anynode ad 3.12.4
Bug Fixes
-
Various fringe-scenarios that could produce aborts of the UCMA module
-
An issue with lingering calls that remained after termination on UCMA nodes
anynode Setup 3.12.3 (September 27, 2018)
Technical Setup
-
Core: anynode 3.12.3
-
Frontend: anynode frontend 3.12.3
-
UCMA: anynode UCMA 3.12.3
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.3
-
Trace: anynode trace 3.12.3
-
Administration: anynode ad 3.12.3
Bug Fixes
-
When an incoming call over UCMA was terminated immediately, this could cause an abort of the UCMA-module
-
A problem in the IPC-communication to the anynode UCMA module
anynode Setup 3.12.2 (September 21, 2018)
Technical Setup
-
Core: anynode 3.12.2
-
Frontend: anynode frontend 3.12.2
-
UCMA: anynode UCMA 3.12.2
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.2
-
Trace: anynode trace 3.12.2
-
Administration: anynode ad 3.12.2
Bug Fixes
-
The Microsoft UCMA-framework may throw an undocumented exception during parsing of incoming signalling-messages
anynode Setup 3.12.1 (September 19, 2018)
Technical Setup
-
Core: anynode 3.12.1
-
Frontend: anynode frontend 3.12.1
-
UCMA: anynode UCMA 3.12.1
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.1
-
Trace: anynode trace 3.12.1
-
Administration: anynode ad 3.12.1
Bug Fixes
-
SNMP-issue on Linux corrected: Requesting active sessions on node returned with error
-
WMI requests could not be executed due to a file-access issue
anynode Setup 3.12.0 (September 10, 2018)
Technical Setup
-
Core: anynode 3.12.0
-
Frontend: anynode frontend 3.12.0
-
UCMA: anynode UCMA 3.12.0
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.12.0
-
Trace: anynode trace 3.12.0
-
Administration: anynode ad 3.12.0
New Features
-
New VoIP provider profile: M-net SIP-Trunk (secure)
-
Silk codec is now supported, configured as one of the default codecs for Microsoft Teams
-
TLS & DTLS now support usage of elliptic curves for operation in environments where no RSAkeys are used
-
It is now possible to configure fail over for registered devices to support session-distribution to multiple registered devices
-
Audio-Files can now be uploaded to be used as media-source
-
An alternative domain and LDAP-server can be configured for use on UCMA-nodes
-
Support for Azure-AD for UCMA-nodes has been integrated
-
Support for Skype-For-Business 2019 added
-
The anynode trace analyzer can now decode, display and play compressed codecs like G.722, G.729, G.726, Opus & Silk
Improvements
-
Configuration for SIP address mapping has been reorganized
-
Registration-handling has been improved while being in maintenance mode
-
TLS-channels now log the certificate of remote-party into trace when available
-
Added the ability to only accept certificates containing certain Subject/AltNames
-
Commodo-Intermediate certificate added to simplify Microsoft-Teams node-setup
-
The Microsoft-Teams Direct Routing profile assistant has been improved to simplify configuration
-
The import of PKCS7 files is now able to incorporate a complete chain
-
Various improvements in anynode frontend to increase security
-
Automatic redirecting from HTTP to HTTPS for frontend connectors has been added
-
Improved handling of media-negotiation with encrypted peers. Improved information forwarding during session-routing.
-
Added the ability to configure complexity and target-bitrate for Opus-codec encoder
-
Conditions now also support the operational-state of transport-connections
-
Call-History export has been improved in terms of performance
-
Various new information has been added into the event-log
-
Various new information has been added to SNMP and WMI
-
Various optimizations during startup, shutdown and reconfiguration of UCMA-nodes.
-
Various new logging and runtime infos to improve management of UCMA-nodes
-
UCMA-nodes can now also access LDAP on sub-domains
-
The function to associate TAPI-state of 3rd party PBXs towards UCMA-users now only takes into account active connections and won‘t show the user as busy when an incoming call is ringing
-
VoIP provider profile updated: For DeutschlandLAN SIP-Trunk profile, the Max-Expires value of the Standard Transport Connection is now defaults to
-
VoIP provider profile updated: Voxbone Trunk
-
VoIP system profile updated: Alcatel-Lucent OmniPCX Office (OXO)
-
VoIP system profile updated: Alcatel-Lucent OXO Connect From-Change (RFC4916) is now disabled by default
-
The uptime and specific CPU and operating-system infos are now shown in the footer of the anynode frontend
-
anynode trace analyzer and call-history now show if calls have failed due to IP-whitelist or DNS issues
-
The anynode trace analyzer now show SIP-messages that it could not transport to the peer in the message-flow overview. Those messages not sent displayed in red
-
The anynode trace analyzer can now show RTP content as hex-data (even for SRTP streams)
-
The anynode trace analyzer now has buttons that allow to directly jump to the next place of interest (packet-loss, high latency...)
-
Improved interop with SRTP for Avaya Session Manager
Bug Fixes
-
P-Remote-Party-Id header encoding/decoding
-
Corrected a potential deadlock in timer subsystem
-
Corrected a potential deadlock during OPTIONS-processing