anynode release 3.14
Intro 3.14
Einleitung
anynode Setup 3.14.5 (January 31, 2018)
Technical Setup
-
Core: anynode 3.14.5
-
Frontend: anynode frontend 3.14.5
-
UCMA: anynode UCMA 3.14.5
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.14.5
-
Trace: anynode trace 3.14.5
-
Administration: anynode ad 3.14.5
Improvements
-
For Microsoft Teams Direct Routing the Silk-Codec is now enabled by Default
-
The default payload types for Silk-codecs changed to circumvent a problem during media negotiation in the startup-phase with Microsoft-Teams
-
Logging during startup of anynode UCMA-module has been improved
Bug Fixes
-
A problem when using UCMA with Skype for Business 2019 due to using an outdated Microsoft assembly
anynode Setup 3.14.4 (January 17, 2018)
Technical Setup
-
Core: anynode 3.14.4
-
Frontend: anynode frontend 3.14.4
-
UCMA: anynode UCMA 3.14.4
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.14.4
-
Trace: anynode trace 3.14.4
-
Administration: anynode ad 3.14.4
Bug Fixes
-
A potential crash in the UCMA module
anynode Setup 3.14.3 (December 20, 2018)
Technical Setup
-
Core: anynode 3.14.3
-
Frontend: anynode frontend 3.14.3
-
UCMA: anynode UCMA 3.14.3
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.14.3
-
Trace: anynode trace 3.14.3
-
Administration: anynode ad 3.14.3
Improvements
-
VoIP provider profile changed: Deutsche Telekom (IP based) (1TR114): Additional IP-addresses to the white-list
Bug Fixes
-
A potential crash during certificate validation
-
A problem in the anynode trace analyzer during parsing of trace-files
anynode Setup 3.14.2 (December 04, 2018)
Technical Setup
-
Core: anynode 3.14.2
-
Frontend: anynode frontend 3.14.2
-
UCMA: anynode UCMA 3.14.2
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.14.2
-
Trace: anynode trace 3.14.2
-
Administration: anynode ad 3.14.2
Improvements
-
VoIP provider profile changed: Deutsche Telekom (IP based) (1TR114): Additional IP-addresses to the white-list
Bug Fixes
-
A potential deadlock while handling TLS-channels
-
A potential crash on UCMA-nodes of users only registered for MWI
-
A problem when showing information about enabled transport protocols for a node were
anynode Setup 3.14.1 (November 27, 2018)
Technical Setup
-
Core: anynode 3.14.1
-
Frontend: anynode frontend 3.14.1
-
UCMA: anynode UCMA 3.14.1
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.14.1
-
Trace: anynode trace 3.14.1
-
Administration: anynode ad 3.14.1
Improvements
-
VoIP provider profile changed:Deutsche Telekom (IP based) (1TR114): Additional IP-addresses to the white-list
Bug Fixes
-
A problem while processing a 488 Not Acceptable Here-Response
-
A problem in the frontend, where the configuration value that controls how the Destination- URI is derived from incoming messages was not saved, has been fixed
anynode Setup 3.14.0 (November 23, 2018)
Technical Setup
-
Core: anynode 3.14.0
-
Frontend: anynode frontend 3.14.0
-
UCMA: anynode UCMA 3.14.0
-
Java: JRE 8u181 (private install with anynodefe, now based on openJDK)
-
Monitor: anynode monitor 3.14.0
-
Trace: anynode trace 3.14.0
-
Administration: anynode ad 3.14.0
New Features
-
Support for TLS 1.3 on platforms supporting OpenSSL 1.1.1
-
New VoIP provider profile: R-Kom Anlagenanschluss
-
New VoIP provider profile: MyRepulic SIP Trunking
Improvements
-
The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1
-
The certificate validator for TLS has an improved ip-/hostname check now supporting forward and reverse lookup
-
The behavior concerning fail over-conditions can now be configured in much higher granularity
-
The UCMA-node now checks if a registered endpoint is being terminated by Skype-for-Business. This fact can now be seen within the UCMA-status on the anynode frontend
-
Time-Conditions now also support a start-time after the end-time, therefore allowing to reverse the time-range which triggers a condition.
-
The source of the referrer-information can now be configured Some defaults for Microsoft Teams Direct Routing have been changed
-
The old LDAP-updater that had been deprecated for some time now has been removed
-
VoIP provider profile changed: QSC renamed to plusnet
-
It is now possible to turn on normal routing even when the maintenance mode is activated.
-
anynode trace analyzer has many improvements:
3-way signalling-view has been extended to allow more parties to be displayed at the same time
Show IP-address and port of peers in the signalling-view
Grouping of session that belong to replaced or transferred calls
More diagnostic information in the system view
Time can now be shown in am/pm format as well
Support for tracing TURN/UDP & TURN/
Bug Fixes
-
A problem of calls having one-way audio due to an issue in the way the stashing of SDP was handled
-
A potential problem with time-conditions
-
The timezone-mapping for FLE Standard Time