anynode Release 3

Version Highlights

  • Media Recording: Media Recording can be activated in the Routing Forwarding Profile to be able to record audio data on all routes associated with that profile. It is possible to configure recording to be either in WAV, raw G.711 or in an internal format. Recordings can downloaded either from the call-history or with a REST API for automated processing. Download of recordings requires a new specific user-permission. It is possible to automatically wipe recordings after a certain number of days. This feature has been implemented to facilitate either the creation legal evidence on threatening calls, measure call quality, optimize processes and quality as well as support training & coaching. This feature requires an additional license.

  • Route Supervision: Route Supervision allows to send meta-data about a call to be routed to an external HTTP/ REST-Server. This server can use this data to either just log the call (including its duration) or pro-actively affect the call by letting the routing take place, prevent routing and even change the target of the call before it is actually routed.

  • REST server: Using the integrated REST-server, administrative tasks can be automated: Importing or exporting configuration-files, activation/deactivation and downloading of anynode-traces, activation/deactivation of maintenance-mode, requesting licenses via LOD-key or uploading license-files, reading the information provided on the dashboard.

  • Azure Active Directory: It is now possible to use data in Azure Active Directory to control the routing of calls.

anynode release 3.20

anynode Setup 3.20.13 (February 26, 2020)

Technical Setup

  • Core: anynode 3.20.13

  • Frontend: anynode frontend 3.20.13

  • UCMA: anynode UCMA 3.20.13

  • Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.13

  • Trace: anynode trace 3.20.13

  • Administration: anynode ad 3.20.13

Improvements

  • The Java runtime that is used by the anynode frontend on Windows has been updated from 8u232 to 8u242

  • The notation of the Plusnet VoIP provider profiles has been adjusted

Bug Fixes

  • A potential issue when forwarding early-media

  • A potential problem during the export of call-history data

  • Some display-issues of wizards in the anynode frontend

anynode Setup 3.20.12 (February 14, 2020)

Technical Setup

  • Core: anynode 3.20.12

  • Frontend: anynode frontend 3.20.12

  • UCMA: anynode UCMA 3.20.12

  • Java: JRE 8u242 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.12

  • Trace: anynode trace 3.20.12

  • Administration: anynode ad 3.20.12

Improvements

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1d

  • Some changes in the trace-subsystem have been implemented to optimize system-load during logging

Bug Fixes

  • A potential crash during use of OpenSSL

anynode Setup 3.20.11 (January 13, 2020)

Technical Setup

  • Core: anynode 3.20.11

  • Frontend: anynode frontend 3.20.11

  • UCMA: anynode UCMA 3.20.11

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.11

  • Trace: anynode trace 3.20.11

  • Administration: anynode ad 3.20.11

Bug Fixes

  • A potential crash of the anynode-monitor during the conversion of the old event-log format

  • A potential memory-leak in the anynode frontend

anynode Setup 3.20.10 (January 07, 2020)

Technical Setup

  • Core: anynode 3.20.10

  • Frontend: anynode frontend 3.20.10

  • UCMA: anynode UCMA 3.20.10

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.10

  • Trace: anynode trace 3.20.10

  • Administration: anynode ad 3.20.10

Bug Fixes

  • The creation of roles in the anynode frontend could fail under certain conditions if the super user is the only existing user in the system.

  • A potential memory-leak for failed registrations in UCMA-nodes

  • A potential synchronisation issue during re-registration in UCMA-nodes

  • A potential crash during validation of the connection to a web server for Route Supervision

anynode Setup 3.20.9 (December 22, 2019)

Technical Setup

  • Core: anynode 3.20.9

  • Frontend: anynode frontend 3.20.9

  • UCMA: anynode UCMA 3.20.9

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.9

  • Trace: anynode trace 3.20.9

  • Administration: anynode ad 3.20.9

Improvements

  • A directory of configured users of a Registrar can now be obtained

Bug Fixes

  • A potential crash when receiving specific redirection history

  • A potential crash when using users in a registrar

  • A problem when forwarding reject reasons for the registrar

  • A problem with the object updater of LDAP user-directories

anynode Setup 3.20.8 (December 09, 2019)

Technical Setup

  • Core: anynode 3.20.8

  • Frontend: anynode frontend 3.20.8

  • UCMA: anynode UCMA 3.20.8

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.8

  • Trace: anynode trace 3.20.8

  • Administration: anynode ad 3.20.8

Bug Fixes

  • A potential crash when using registration transport connections

anynode Setup 3.20.7 (November 29, 2019)

Technical Setup

  • Core: anynode 3.20.7

  • Frontend: anynode frontend 3.20.7

  • UCMA: anynode UCMA 3.20.7

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.7

  • Trace: anynode trace 3.20.7

  • Administration: anynode ad 3.20.7

Bug Fixes

  • A missing initialization of a default timer for SIP-handling

anynode Setup 3.20.6 (November 21, 2019)

Technical Setup

  • Core: anynode 3.20.6

  • Frontend: anynode frontend 3.20.6

  • UCMA: anynode UCMA 3.20.6

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.6

  • Trace: anynode trace 3.20.6

  • Administration: anynode ad 3.20.6

Improvements

  • A protocol-timer used during REFER-handling has been made configurable and its default value has been increased for Microsoft Teams Direct Routing

Bug Fixes

  • A potential problem when displaying the node-status on the anynode dashboard and within the anynode trace analyzer

anynode Setup 3.20.5 (November 20, 2019)

Technical Setup

  • Core: anynode 3.20.5

  • Frontend: anynode frontend 3.20.5

  • UCMA: anynode UCMA 3.20.5

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.5

  • Trace: anynode trace 3.20.5

  • Administration: anynode ad 3.20.5

Bug Fixes

  • Changed some default configuration values for Microsoft Teams Direct Routing to improve interoperability for call-hold & REFER scenarios

anynode Setup 3.20.4 (November 15, 2019)

Technical Setup

  • Core: anynode 3.20.4

  • Frontend: anynode frontend 3.20.4

  • UCMA: anynode UCMA 3.20.4

  • Java: JRE 8u232 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.4

  • Trace: anynode trace 3.20.4

  • Administration: anynode ad 3.20.4

Improvements

  • The route supervision now sets the Reason to not Responding when a call is being canceled by a user

Bug Fixes

  • Corrected a problem with the Load Balancer where configuration-changes were not always adopted on the fly

  • An object-leak in form of a trace-stream has been corrected in the UCMA-module

  • An error closing trace-streams in the anynode trace analyzer

anynode Setup 3.20.3 (November 04, 2019)

Technical Setup

  • Core: anynode 3.20.3

  • Frontend: anynode frontend 3.20.3

  • UCMA: anynode UCMA 3.20.3

  • Java: JRE 8u222 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.3

  • Trace: anynode trace 3.20.3

  • Administration: anynode ad 3.20.3

Improvements

  • The ability that UCMA nodes can now refresh SfB-users that were disconnected due to changes in their back end configuration has been added

Bug Fixes

  • A possible deadlock in the anynode monitor during data-exchange with the anynode frontend

anynode Setup 3.20.2 (October 28, 2019)

Technical Setup

  • Core: anynode 3.20.2

  • Frontend: anynode frontend 3.20.2

  • UCMA: anynode UCMA 3.20.2

  • Java: JRE 8u222 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.2

  • Trace: anynode trace 3.20.2

  • Administration: anynode ad 3.20.2

Improvements

  • Some configuration-defaults have been improved for media negotiation with Microsoft Teams Direct Routing

Bug Fixes

  • A minor issue in the anynode frontend during configuration of media-negotiation with ICE-settings

anynode Setup 3.20.1 (October 24, 2019)

Technical Setup

  • Core: anynode 3.20.1

  • Frontend: anynode frontend 3.20.1

  • UCMA: anynode UCMA 3.20.1

  • Java: JRE 8u222 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.1

  • Trace: anynode trace 3.20.1

  • Administration: anynode ad 3.20.1

Improvements

  • The anynode.mib file for SNMP is now being installed into the RES-folder on all platforms

Bug Fixes

  • Some minor issues during media-negotiation

  • An issue with the monitoring of file-system usage has been corrected for Raspbian

  • Some minor issues of the anynode trace analyzer

  • Some anynode frontend could possibly fail on systems with only one CPU core

anynode Setup 3.20.0 (October 15, 2019)

Technical Setup

  • Core: anynode 3.20.0

  • Frontend: anynode frontend 3.20.0

  • UCMA: anynode UCMA 3.20.0

  • Java: JRE 8u222 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.20.0

  • Trace: anynode trace 3.20.0

  • Administration: anynode ad 3.20.0

New Features

  • anynode can now record media-data of calls going over specific routes

  • anynode can now do route-supervision on specified routes by sending meta-data of calls to an external HTTP/REST-server and use results from same server for actual routing

  • The REST-Server in the anynode frontend was extended to be able to invoke various administrative functions from remote

  • anynode now supports Azure AD as a source for dial-string directories

  • The file system below the directory used to store various runtime-data by various anynodemodules can now be monitored for sufficient free space

  • The rate of SIP-sessions per time-units can now be limited

Improvements

  • The anynode trace analyzer has been extended to include a view that shows SIP-transactions that specially highlights problematic conditions

  • The anynode trace analyzer has been extended to support various new features of the new 3.20 series of anynode ICE/TURN handling has been improved for some specific scenarios

  • Handling of incoming SDP with 0.0.0.0 addresses and 0 ports has been improved.

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.1c

  • Multiple improvements in handling specific SIP-headers and their forwarding have been integrated

  • Negotiating SRTP was improved in some specific circumstances

  • SIP session expiration handling has been improved to accommodate some faulty remote SIP implementations

  • Multiple improvements during UCMA-handling

  • The internal event-log has been reorganized to now use an internal database instead of a text-file

  • The call-history has been extended by various new fields

  • The Java runtime that is used by the anynode frontend has been changed from 8u212 to 8u222

  • VoIP provider profile changed: Deutsche Telekom (IP-basiert)

  • New VoIP provider profile: Tell-Phone SIP Trunk

  • New VoIP provider profile: Grandstream GXW4200 Series

  • New VoIP provider profile: Digium Switchvox

  • An automatic redirection from HTTP to HTTPS is now possible with the anynode frontend

  • It is now possible to automatically obtain a license with updated SUS status by a push of a button from within the anynode frontend

Bug Fixes

  • A problem was corrected where no new session were accepted after reconfiguration in very specific circumstances

  • A problem was corrected where under extreme rare conditions authentication of SIPtransactions was not done properly

  • A potential race-condition during allocation and release of UDP-channels on Windows

  • A problem when routing parallel calls using an empty directory

  • Some minor issues in the anynode monitor

  • A small problem in the anynode frontend was corrected when adding a license and the license-server was not reachable

anynode release 3.18

anynode Setup 3.18.6 (October 01, 2019)

Technical Setup

  • Core: anynode 3.18.6

  • Frontend: anynode frontend 3.18.6

  • UCMA: anynode UCMA 3.18.6

  • Java: JRE 8u212 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.18.6

  • Trace: anynode trace 3.18.6

  • Administration: anynode ad 3.18.6

Bug Fixes

  • A problem during upload of certificates

  • A problem where messages were added to the event-log multiple times

  • A problem when configuring the auto-deletion of entries in the call-history

anynode Setup 3.18.5 (September 17, 2019)

Technical Setup

  • Core: anynode 3.18.5

  • Frontend: anynode frontend 3.18.5

  • UCMA: anynode UCMA 3.18.5

  • Java: JRE 8u212 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.18.5

  • Trace: anynode trace 3.18.5

  • Administration: anynode ad 3.18.5

Improvements

  • It is now possible to configure the SIP User Agent object to either forward all, none, the first or last entry of the Diversion or the History-Info header

  • The Contact-Header to be sent can now be configured for special applications within the SIP URI processing section of the SIP User Agent object

Bug Fixes

  • The file-upload in the anynode frontend could fail under certain conditions

  • The change of the operational condition value in the standard transport connection was not applied

  • A potential deadlock in the anynode trace analyzer

anynode Setup 3.18.4 (August 01, 2019)

Technical Setup

  • Core: anynode 3.18.4

  • Frontend: anynode frontend 3.18.4

  • UCMA: anynode UCMA 3.18.4

  • Java: JRE 8u212 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.18.4

  • Trace: anynode trace 3.18.4

  • Administration: anynode ad 3.18.4

New Features

  • The network peer white list now also supports SRV-records

  • SIP-Nodes can now be set to be up or down via condition

Improvements

  • The Java runtime that is used by the anynode frontend has been changed from 8u202 to 8u212

  • The registrar can now optionally reject registrations when in maintenance mode

  • Various improvements of the anynode trace analyzer

  • User-Agent / Server header of remote peers are now being stored in the call-history

anynode release 3.16

anynode Setup 3.16.19 (July 26, 2019)

Technical Setup

  • Core: anynode 3.16.19

  • Frontend: anynode frontend 3.16.19

  • UCMA: anynode UCMA 3.16.19

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.19

  • Trace: anynode trace 3.16.19

  • Administration: anynode ad 3.16.19

Bug Fixes

  • A potential problem for incoming non-audio sessions (chat) on UCMA-nodes

  • WMI is now able to access the anynode-monitor again

anynode Setup 3.16.18 (July 05, 2019)

Technical Setup

  • Core: anynode 3.16.18

  • Frontend: anynode frontend 3.16.18

  • UCMA: anynode UCMA 3.16.18

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.18

  • Trace: anynode trace 3.16.18

  • Administration: anynode ad 3.16.18

Bug Fixes

  • Corrected an issue with setting system-timezone on Linux

  • A problem of time tags in call history having incorrect values on systems with 32bit time_t

  • A potential crash of the anynode trace analyzer

  • Some potential glitches when showing certificates and licenses on the anynode dashboard

  • A potential problem in the license-wizard if the license-server was not reachable

anynode Setup 3.16.17 (July 02, 2019)

Technical Setup

  • Core: anynode 3.16.17

  • Frontend: anynode frontend 3.16.17

  • UCMA: anynode UCMA 3.16.17

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.17

  • Trace: anynode trace 3.16.17

  • Administration: anynode ad 3.16.17

New Features

  • Support for Debian Buster (x64 and Raspbian)

Improvements

  • UCMA-nodes now process the OtherPhoneUri for the number of the remote side if the PhoneUri is empty. This was already done for call signaled on a user endpoint. Now this is also done for calls to the trusted application.

Bug Fixes

  • A potential problem activating changes for transport-connections

  • User-Authentication of the web-frontend is now always active after fresh Linux-installs

anynode Setup 3.16.16 (May 03, 2019)

Technical Setup

  • Core: anynode 3.16.16

  • Frontend: anynode frontend 3.16.16

  • UCMA: anynode UCMA 3.16.16

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.16

  • Trace: anynode trace 3.16.16

  • Administration: anynode ad 3.16.16

New Features

  • Support for Debian Buster (x64 and Raspbian)

Improvements

  • Various improvements during ICE-negotiation, restoring operation with Exchange UM/Azure-VM Performance-improvements during loading of trace-files into analyzer in certain fringe-cases

  • Improved performance in combination with Microsoft-Turn-Server for UCMA-node

Bug Fixes

  • A potential crash in context with TURN/TCP

anynode Setup 3.16.15 (April 30, 2019)

Technical Setup

  • Core: anynode 3.16.15

  • Frontend: anynode frontend 3.16.15

  • UCMA: anynode UCMA 3.16.15

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.15

  • Trace: anynode trace 3.16.15

  • Administration: anynode ad 3.16.15

New Features

  • Support for Debian Buster (x64 and Raspbian)

Improvements

  • The initial login-page now has improved usability

Bug Fixes

  • A potential problem during Path-Replacment

  • A problem with Latching

  • A potential problem when cloning objects in the anynode frontend

  • Some minor issues in the anynode trace analyzer

anynode Setup 3.16.14 (April 18, 2019)

Technical Setup

  • Core: anynode 3.16.14

  • Frontend: anynode frontend 3.16.14

  • UCMA: anynode UCMA 3.16.14

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.14

  • Trace: anynode trace 3.16.14

  • Administration: anynode ad 3.16.14

New Features

  • Support for Debian Buster (x64 and Raspbian)

Improvements

  • RTCP multiplexing is now activated as default only for Microsoft Teams Direct Routing

Bug Fixes

  • A potential issue in the anynode monitor has been fixed when a TCP-connection was blocked due to a white list and did not have a local address

  • A potential issue in the anynode trace analyzer has been fixed when a TCP-connection was blocked due to a white list and did not have a local address

  • The display of some default-values for UDP/TCP transport keep-alive properties in the provider profile

anynode Setup 3.16.13 (April 02, 2019)

Technical Setup

  • Core: anynode 3.16.13

  • Frontend: anynode frontend 3.16.13

  • UCMA: anynode UCMA 3.16.13

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.13

  • Trace: anynode trace 3.16.13

  • Administration: anynode ad 3.16.13

Improvements

  • Monitoring of Nodes with multiple SIP-Load-Balancers has been improved

Bug Fixes

  • Failed DNS-resolving during TLS-validation has not been checked correctly in certain circumstances

  • During TLS-validation the additional list of SANs was not checked in certain circumstances

  • The anynode frontend could possibly not show certain certificate-fields depending on the keyword contained

anynode Setup 3.16.12 (March 27, 2019)

Technical Setup

  • Core: anynode 3.16.12

  • Frontend: anynode frontend 3.16.12

  • UCMA: anynode UCMA 3.16.12

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.12

  • Trace: anynode trace 3.16.12

  • Administration: anynode ad 3.16.12

Improvements

  • Some minor enhancements of the command-line interface of the anynode frontend

  • Some textual enhancements in the anynode frontend

  • Handling of declining calls in the UCMA-modules has been improved in certain scenarios

  • Enumeration of common area-phones in UCMA-modules has been improved

Bug Fixes

  • A potential problem during negotiation of T.38

  • A potential problem in certain REFER-scenarios

  • A potential problem when associating network-interfaces to nodes in the anynode trace analyzer

anynode Setup 3.16.11 (March 12, 2019)

Technical Setup

  • Core: anynode 3.16.11

  • Frontend: anynode frontend 3.16.11

  • UCMA: anynode UCMA 3.16.11

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.11

  • Trace: anynode trace 3.16.11

  • Administration: anynode ad 3.16.11

Improvements

  • QoS-operation for UDP on Windows has been improved

anynode Setup 3.16.10 (March 07, 2019)

Technical Setup

  • Core: anynode 3.16.10

  • Frontend: anynode frontend 3.16.10

  • UCMA: anynode UCMA 3.16.10

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.10

  • Trace: anynode trace 3.16.10

  • Administration: anynode ad 3.16.10

Improvements

  • VoIP provider profile changed: sipcall

  • VoIP provider profile changed: Flowroute SIP Trunking

Bug Fixes

  • An issue has been corrected where the Referrer-Address has been taken from the Source- Address erroneously

  • A potential crash of the anynode trace analyzer

  • A potential IPC-issue of the monitor after clean installation

anynode Setup 3.16.9 (February 22, 2019)

Technical Setup

  • Core: anynode 3.16.9

  • Frontend: anynode frontend 3.16.9

  • UCMA: anynode UCMA 3.16.9

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.9

  • Trace: anynode trace 3.16.9

  • Administration: anynode ad 3.16.9

Improvements

  • The default session-timer for Microsoft Teams has been changed to 1800 to improve interoperability with newest changes by Microsoft.

Bug Fixes

  • A potential problem where navigating through the call history reset the page index every time

  • A potential problem where not all web server-connectors of the anynode frontend where started up

anynode Setup 3.16.8 (February 20, 2019)

Technical Setup

  • Core: anynode 3.16.8

  • Frontend: anynode frontend 3.16.8

  • UCMA: anynode UCMA 3.16.8

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.8

  • Trace: anynode trace 3.16.8

  • Administration: anynode ad 3.16.8

Improvements

  • Improved checks if a FQDN specified in the node-wizard matches a configured certificate

  • To optimize media-interoperability with certain devices it is now possible to configure to let the c-line appear prior to m-lines

  • For inbound requests it can now be optionally checked whether the domain of the Request- URI matches the domain of the Transport-URI

  • Behaviour when ignoring Options has been optimized

  • VoIP provider profile changed: sipcall

Bug Fixes

  • A potential crash during ICE-negotiation

  • The live-trace button will now only appear if live-tracing is actually possible

anynode Setup 3.16.7 (February 14, 2019)

Technical Setup

  • Core: anynode 3.16.7

  • Frontend: anynode frontend 3.16.7

  • UCMA: anynode UCMA 3.16.7

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.7

  • Trace: anynode trace 3.16.7

  • Administration: anynode ad 3.16.7

Version Highlights

  • Microsoft Teams Direct Routing Certification: This is the first public release of anynode 3.16.x after the successful completion of the certification of anynode for use with Microsoft Teams Direct Routing. Even though prior versions of anynode have been used by a multitude of customers successfully with their Direct Routing tenants, we recommend updating to this version to ensure Microsoft support for your deployment. This version is also prepared for seamless upgrade to the upcoming Media Bypass mode of Microsoft Teams Direct Routing.

  • Role based user-management: The user-management built into the anynode frontend has been improved dramatically with this version. It is now possible to configure fine-grained access-rights for the various users that have been added for use on the frontend. This helps to limit access to potentially privacy relevant information to only those employees that need the specific rights.

Bug Fixes

  • A potential problem during update of configuration from an older anynode-version

anynode Setup 3.16.6 (February 13, 2019)

Technical Setup

  • Core: anynode 3.16.6

  • Frontend: anynode frontend 3.16.6

  • UCMA: anynode UCMA 3.16.6

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.6

  • Trace: anynode trace 3.16.6

  • Administration: anynode ad 3.16.6

Bug Fixes

  • A potential problem during update of configuration from an older anynode-version

anynode Setup 3.16.5 (February 11, 2019)

Technical Setup

  • Core: anynode 3.16.5

  • Frontend: anynode frontend 3.16.5

  • UCMA: anynode UCMA 3.16.5

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.5

  • Trace: anynode trace 3.16.5

  • Administration: anynode ad 3.16.5

New Features

  • New VoIP provider profile: sipcall

  • New VoIP provider profile: verizon

  • New VoIP provider profile: Flat Planet Phone

  • New VoIP provider profile: sipcall

  • The Java Runtime that is used by the anynode frontend has been changed from Oracle 8u192 to AdoptOpenJDK 8u202

Improvements

  • When setting the operating system time zone, the UTC offsets are now displayed

  • Mouse-over on the note icon will now display the note as a tool tip

  • Additional optimizations for Microsoft Teams Direct Routing defaults Improved interoperability with 3rd-party

Bug Fixes

  • A potential endless-loop during TCP-handling

anynode Setup 3.16.4 (January 22, 2019)

Technical Setup

  • Core: anynode 3.16.4

  • Frontend: anynode frontend 3.16.4

  • UCMA: anynode UCMA 3.16.4

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.4

  • Trace: anynode trace 3.16.4

  • Administration: anynode ad 3.16.4

New Features

  • New role-based user-management has been integrated

    Allows for fine-grained control to various anynode function-areas

    Four builtin roles

    Administrator - a role that integrates all possible rights

    Call History Exporter - a role that can only be used to export the call-history via REST API

    Configurator - a role that enables to do basic anynode-configuration

    Monitor - a role that enables to use the monitor-section of anynode

    One builtin user

    anadmins

    All users existing before are automatically assigned the admin role

    Additional roles and users can be created

  • Password-policy

    Allows to configure the strength of password required for login

    Minimum length of passwords

    Additional constraints like minimum number of digits, letters (generic, uppercase, lowercase) and special characters

    Heuristic to disallow simple patterns (12345678, abcdefgh...)

    Blacklist of disallowed words

  • Login-policy

    Allows to configure various behaviour in connection with logins:

    Blocking-time after a failed attempt

    Password expiration

  • Authentication for web-frontend is now enabled by default for new installations

    In this case, login is possible with default admin user anadmin and empty password Improvements:

Improvements

  • Various improvements to automatically set optimized defaults for Microsoft Teams Direct Routing

Bug Fixes

  • A potential crash in the UCMA module

anynode Setup 3.16.3 (December 20, 2018)

Technical Setup

  • Core: anynode 3.16.3

  • Frontend: anynode frontend 3.16.3

  • UCMA: anynode UCMA 3.16.3

  • Java: JRE 8u191 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.3

  • Trace: anynode trace 3.16.3

  • Administration: anynode ad 3.16.3

Improvements

  • Some additional functionality has been integrated into the new user-management

  • 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.16.2 (December 19, 2018)

Technical Setup

  • Core: anynode 3.16.2

  • Frontend: anynode frontend 3.16.2

  • UCMA: anynode UCMA 3.16.2

  • Java: JRE 8u191 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.2

  • Trace: anynode trace 3.16.2

  • Administration: anynode ad 3.16.2

Improvements

  • Media-Negotiation has been improved when no compatible codecs were found

Bug Fixes

  • The detection of TLS-usage of sessions and nodes in the anynode trace analyzer

anynode Setup 3.16.1 (December 14, 2018)

Technical Setup

  • Core: anynode 3.16.1

  • Frontend: anynode frontend 3.16.1

  • UCMA: anynode UCMA 3.16.1

  • Java: JRE 8u191 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.1

  • Trace: anynode trace 3.16.1

  • Administration: anynode ad 3.16.1

Improvements

  • Some default-configuration options optimized for Microsoft Teams Direct Routing

anynode Setup 3.16.0 (December 11, 2018)

Technical Setup

  • Core: anynode 3.16.0

  • Frontend: anynode frontend 3.16.0

  • UCMA: anynode UCMA 3.16.0

  • Java: JRE 8u202 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.16.0

  • Trace: anynode trace 3.16.0

  • Administration: anynode ad 3.16.0

New Features

  • Support for repacketizing RTP-data

  • Support for generating CN-events when processing silence

  • Support for handling RTP on TCP

  • Support for Retry After in 500 and 503 responses

  • Support for ICE-LITE

  • Check if anynode is running in a virtual environment and show the environment detected

  • Check if and which firewalls are active on a Windows system

  • Warning for non-installed QoS-role on Windows has been added

  • The timezone of the operating-system can now be configured on the anynode frontend

  • Retry-After header is now evaluated for 500 and 503 responses

  • Initial version of the new user-management

Improvements

  • The implementation of ICE/TURN/MS-TURN and STUN has been refactored

  • Fail over behaviour now supports Microsoft Teams Direct Routing

  • Various changes of default-behaviour for Microsoft Teams Direct Routing

  • The anynode-configuration will now be sent as delta, improving performance when applying changes

  • Interoperability of media-negotiation with old Snom/Polycom Phones on UCMA-node improved

  • Default-payload types for Silk-codecs changed to circumvent a problem during media negotiation in the startup-phase with Microsoft-Teams

  • Various changes to improve interoperability in SIPS/TLS scenarios

  • It is now possible to configure the origin of the referrer-information

  • A new improved trace-format is now used by default

Bug Fixes

  • The trace-filename should now always contain the correct start-time of the trace

anynode release 3.14

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

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

anynode release 3.10

Intro 3.10

Version Highlights

Rolling Traces In addition to storing anynode trace files into a single file now traces can be split into multiple files with a definable number of files and size of each file. In this mode the maximum size on disk is limited and it is possible to do long-term tracing for problems that occur infrequently. Time / Day-of-Week based routing It is now possible to create conditions that trigger based on time-ranges and day-of-week (and additionally manually configured holidays). Those conditions can be used to control routing and thus allow to route calls based on hotline hours for example. Administration / Maintenance The new administration-module allows specific control of the host-system. It is possible to restart or shut down the system. On Linux updates can be applied, the SSH-Daemon and a special system-administrative user can be configured and activated/deactivated. By switching the system to maintenance mode, the system can be shut down gracefully, continuing to service established calls, but not accepting new ones. TAPI Support It is now possible to retrieve busy-states of conventional PBXs via TAPI and replicate this state using UCMA into Skype-for-Business systems. This allows users with Skype-Clients to also detect the complete busy-state of users in hybrid environments.

anynode Setup 3.10.10 (July 09, 2018)

Technical Setup

  • Core: anynode 3.10.10

  • Frontend: anynode frontend 3.10.10

  • UCMA: anynode UCMA 3.10.10

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.10

  • Trace: anynode trace 3.10.10

  • Administration: anynode ad 3.10.10

Improvements

  • A Go Daddy certificate chain has been integrated to automatically create a chain of trust when a single Go Daddy certificate is entered by the user

  • CSR generation now makes the download of the private key mandatory to prevent receiving a signed certificate, but having lost the private key

Bug Fixes

  • A problem when trying to open the anynode frontend on Windows via the start-menu link

  • During Debian system-updates that have been initiated via the frontend, no status-messages did show up on the pop up-windows

  • A couple of potential crashes in anynode UCMA

anynode Setup 3.10.9 (June 18, 2018)

Technical Setup

  • Core: anynode 3.10.9

  • Frontend: anynode frontend 3.10.9

  • UCMA: anynode UCMA 3.10.9

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.9

  • Trace: anynode trace 3.10.9

  • Administration: anynode ad 3.10.9

Bug Fixes

  • A potential crash in the anynode monitor while exchanging data with the UCMA module

  • A potential deadlock in the anynode UCMA module has been corrected which could occur if an unknown trusted application id was configured

anynode Setup 3.10.8 (June 08, 2018)

Technical Setup

  • Core: anynode 3.10.8

  • Frontend: anynode frontend 3.10.8

  • UCMA: anynode UCMA 3.10.8

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.8

  • Trace: anynode trace 3.10.8

  • Administration: anynode ad 3.10.8

Improvements

  • The wizard for creating a Microsoft Teams Direct Routing has been improved to include a page to configure the certificates

Bug Fixes

  • A potential ownership issue for files in the configuration directories on Debian

anynode Setup 3.10.7 (May 31, 2018)

Technical Setup

  • Core: anynode 3.10.7

  • Frontend: anynode frontend 3.10.7

  • UCMA: anynode UCMA 3.10.7

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.7

  • Trace: anynode trace 3.10.7

  • Administration: anynode ad 3.10.7

Improvements

  • The integrated license activation is now done via HTTPS. For privacy reasons, the activation via HTTP is not available anymore

anynode Setup 3.10.6 (May 29, 2018)

Technical Setup

  • Core: anynode 3.10.6

  • Frontend: anynode frontend 3.10.6

  • UCMA: anynode UCMA 3.10.6

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.6

  • Trace: anynode trace 3.10.6

  • Administration: anynode ad 3.10.6

Improvements

  • Upon creation of a Microsoft Teams Direct Routing node through the wizard, the user is redirected to the Network Security Profile page to configure the client-certificates

  • The duration it takes to copy data into the clipboard in the anynode trace analyzer has been improved considerably in certain circumstances

Bug Fixes

  • A potential crash while loading a trace-file into the anynode trace analyzer

anynode Setup 3.10.5 (May 25, 2018)

Technical Setup

  • Core: anynode 3.10.5

  • Frontend: anynode frontend 3.10.5

  • UCMA: anynode UCMA 3.10.5

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.5

  • Trace: anynode trace 3.10.5

  • Administration: anynode ad 3.10.5

New Features

  • A node wizard for Microsoft Teams Direct Routing has been integrated

Improvements

  • On all systems using OpenSSL 1.0.2 upwards (Windows, Debian 9, Ubuntu 16.04, Ubuntu 18.04), it is now possible to use non-root certificates as trust-anchor

Bug Fixes

  • A problem with setting correct directory access rights during installation on Debian based systems

  • A potential crash of the UCMA-service during TAPI-enumeration during startup

anynode Setup 3.10.3 (May 23, 2018)

Technical Setup

  • Core: anynode 3.10.3

  • Frontend: anynode frontend 3.10.3

  • UCMA: anynode UCMA 3.10.3

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.3

  • Trace: anynode trace 3.10.3

  • Administration: anynode ad 3.10.3

New Features

  • It is now possible to import additional certificates for ones own certificate to present a complete chain during the TLS-handshake

  • It is now possible to configure certain SIP-components to be able interoperate with Microsoft Teams

Bug Fixes

  • In certain circumstances the anynode monitor could crash when the IPC-connection to the anynode base service is lost while connections were still established

anynode Setup 3.10.0 (May 14, 2018)

Technical Setup

  • Core: anynode 3.10.0

  • Frontend: anynode frontend 3.10.0

  • UCMA: anynode UCMA 3.10.0

  • Java: JRE 8u172 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.10.0

  • Trace: anynode trace 3.10.0

  • Administration: anynode ad 3.10.0

New Features

  • Media-Negotation now also supports TURN

  • Support for Ubuntu 18.04 x64 G.726 codec support on x64 systems (both Linux & Windows)

  • anynode can be put into a maintenance-mode, allowing for soft shutdown of service

  • Computer hosting anynode can be rebooted or shut down using the web-frontend

  • Debian-systems can now be updated (apt-get update / apt-get dist-upgrade) via anynode frontend

  • On all systemd based systems, the openssh-daemon can be activated/deactivated and configured

  • On Debian-based system an specific existing administrative system-account (name: anadmin) can be activated/deactivated and the password reset

  • Rolling Traces are now supported Path replacement detection has been extended to use negotiated media to detect a possible path replacement scenario. Thus media-pass can be shortened even when signalling is running via a third party on both SIP and UCMA nodes

  • PBX-User-state can be retrieved via TAPI and forwarded via UCMA to show the associated Skype-For-Business-User as busy

  • Routing can now be performed conditionally based on time and day of week

  • It is now possible to forward user-specific headers for an initial INVITE.

  • It is now possible to forward the SIP-domain of an incoming call in a user-configurable Header

  • New VoIP system profile: bintec elmeg be.IP Series

  • New VoIP provider profile: WOBCOM

  • New VoIP provider profile: HFO NGN Connect

  • It is now possible to activate live-tracing for UCMA when accessing the anynode frontend from the local system.

Improvements

  • Additional information about SIP and UCMA-nodes is collected and shown in the anynode dashboard of the anynode frontend

  • Media-Sources playing simulated-audio during early-media can now stop media-playback when real media from the other side is received

  • Support for SIP-Header Remote-Party-ID

  • Manual setting of specific SIP-headers and addresses both for incoming and outgoing sessions

  • Forwarding of asserted addresses from one node to the other

  • Forwarding of media-negotiation parameters has been improved

  • Various improvements in wizards to generate configuration

  • CPU-type and Operating-System-Infos are now integrated into trace-files and shown in the analyzer

  • Various additional information is now being written into the event-log

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.0h

Bug Fixes

  • A potential deadlock in SIP-handling was resolved

  • A problem in char-page conversion

  • A potential problem during call-history export

anynode release 3.8

Intro 3.8

Version Highlights

The new anynode version 3.8. now supports the usage of MS-TURN for ICE-negotation on UCMA nodes. This feature eases deployment of anynode in various Skype-for-Business scenarios ( like Exchange UM integration ) dramatically. It is not necessary anymore to configure specific firewall-rules for the anynode computer. Instead anynode can capacities on the pre-existing firewall configuration of the SfB-Edge-Server.

anynode Setup 3.8.14 (April 26, 2018)

Technical Setup

  • Core: anynode 3.8.14

  • Frontend: anynode frontend 3.8.14

  • UCMA: anynode UCMA 3.8.14

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.14

  • Trace: anynode trace 3.8.14

  • Administration: anynode ad 3.8.14

Improvements

  • A configuration-option has been added to not refresh registrations on nodes when maintenance mode has been activated. This is set as default

  • UCMA registrations for users where the only intent is the reception of MWI state now omit INVITE in supported methods to lower load on both anynode and Skype-for-Business server

anynode Setup 3.8.13 (April 10, 2018)

Technical Setup

  • Core: anynode 3.8.13

  • Frontend: anynode frontend 3.8.13

  • UCMA: anynode UCMA 3.8.13

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.13

  • Trace: anynode trace 3.8.13

  • Administration: anynode ad 3.8.13

Improvements

  • In the anynode frontend the performance when processing CPU load, RAM usage and active-session data has been improved

Bug Fixes

  • The assistant creating a connection between a Skype-for-Business node and a SIP-node contained a wrong default causing media not being transmitted correctly

  • Download of very large trace-files could fail

  • An issue when showing condition operators on the Firefox browser

anynode Setup 3.8.12 (March 22, 2018)

Technical Setup

  • Core: anynode 3.8.12

  • Frontend: anynode frontend 3.8.12

  • UCMA: anynode UCMA 3.8.12

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.12

  • Trace: anynode trace 3.8.12

  • Administration: anynode ad 3.8.12

Improvements

  • During CSV-import in the configuration-frontend, empty prefix or suffix strings will not be set explicitly anymore.

Bug Fixes

  • In certain circumstances playback of an audio file as music-on-hold could cause a crash

  • Under certain conditions the anynode trace analyzer could show the wrong trace-stream for the rootnode

  • The value shown for OPUS-encoders on the anynode dashboard was not correct

anynode Setup 3.8.11 (March 16, 2018)

Technical Setup

  • Core: anynode 3.8.11

  • Frontend: anynode frontend 3.8.11

  • UCMA: anynode UCMA 3.8.11

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.11

  • Trace: anynode trace 3.8.11

  • Administration: anynode ad 3.8.11

Improvements

  • During initial call-setup, SDP will be reused when authentication is enforced to improve compatibility to certain peers. This default behavior can be disabled thus newly creating a new SDP in such circumstances

  • Some behavior changes concerning registrations:

    In maintenance mode, registrations are now kept alive as default

    Upon loosing registrations, session are not terminated automatically as default

Bug Fixes

  • In certain circumstances the termination of sessions could be delayed until another processing step was executed

anynode Setup 3.8.10 (March 08, 2018)

Technical Setup

  • Core: anynode 3.8.10

  • Frontend: anynode frontend 3.8.10

  • UCMA: anynode UCMA 3.8.10

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.10

  • Trace: anynode trace 3.8.10

  • Administration: anynode ad 3.8.10

Bug Fixes

  • A memory-leak during cyclic LDAP-queries in UCMA-nodes

anynode Setup 3.8.9 (March 06, 2018)

Technical Setup

  • Core: anynode 3.8.9

  • Frontend: anynode frontend 3.8.9

  • UCMA: anynode UCMA 3.8.9

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.9

  • Trace: anynode trace 3.8.9

  • Administration: anynode ad 3.8.9

Improvements

  • Media-Handling between UCMA-nodes and SIP-nodes improved when negotiation on UCMAside fails

  • Detail-Improvements of default values in UCMA-wizards

Bug Fixes

  • A potential crash during audio-event-handling after an SSRC-change

anynode Setup 3.8.8 (February 28, 2018)

Technical Setup

  • Core: anynode 3.8.8

  • Frontend: anynode frontend 3.8.8

  • UCMA: anynode UCMA 3.8.8

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.8

  • Trace: anynode trace 3.8.8

  • Administration: anynode ad 3.8.8

New Features

  • New VoIP provider profile: NetCologne - Pro Phone SIP

Improvements

  • Audio-Events are now also received from new receive-streams after an appropriate timeout. Previously this was not the case and could cause problems with Skype for Business SIPconnections

  • On the UCMA-node call-setup is continued even if the calling-number is invalid. For text that cannot be used the digit 0 is set as a calling-number instead

  • On the UCMA-node the calling-number handling has been changed. Associating such a number to a UCMA-applicaiton is now only done when it is at least minimumExtensionLength long, default being 3

anynode Setup 3.8.7 (February 19, 2018)

Technical Setup

  • Core: anynode 3.8.7

  • Frontend: anynode frontend 3.8.7

  • UCMA: anynode UCMA 3.8.7

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.7

  • Trace: anynode trace 3.8.7

  • Administration: anynode ad 3.8.7

New Features

  • New VoIP provider profile: ITK

  • New VoIP provider profile: MK-NetzDienste

Improvements

  • Changed handling of media-sessions to adapt for changes in UCMA-nodes for both monitoring and tracing

anynode Setup 3.8.6 (February 13, 2018)

Technical Setup

  • Core: anynode 3.8.6

  • Frontend: anynode frontend 3.8.6

  • UCMA: anynode UCMA 3.8.6

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.6

  • Trace: anynode trace 3.8.6

  • Administration: anynode ad 3.8.6

Improvements

  • In UCMA the media session will be reset if Skype for Business requests a transfer and the Skype for Business call is replaced. If the transfer fails disconnect the call

  • In UCMA the parameter EnableSystemContactConversion has been changed into DisableSystemContactConversion thus changing the default

anynode Setup 3.8.5 (February 05, 2018)

Technical Setup

  • Core: anynode 3.8.5

  • Frontend: anynode frontend 3.8.5

  • UCMA: anynode UCMA 3.8.5

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.5

  • Trace: anynode trace 3.8.5

  • Administration: anynode ad 3.8.5

Bug Fixes

  • An error in UCMA while enabling users for message waiting. If a user name contains special chars, e.g. a hyphen, the name comparison delivered a wrong result and the user was not registered

anynode Setup 3.8.4 (January 31, 2018)

Technical Setup

  • Core: anynode 3.8.4

  • Frontend: anynode frontend 3.8.4

  • UCMA: anynode UCMA 3.8.4

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.4

  • Trace: anynode trace 3.8.4

  • Administration: anynode ad 3.8.4

Improvements

  • Some details of media-negotiating forwarding has been changed back to previous behavior by default

  • Mapping of numbers to SIP-addresses for UCMA has been changed to be OPT-In

  • Diagnostics for potential UCMA-issues have been improved

Bug Fixes

  • A potential issue in LDAP-retrievals for UCMA users

anynode Setup 3.8.3 (January 25, 2018)

Technical Setup

  • Core: anynode 3.8.3

  • Frontend: anynode frontend 3.8.3

  • UCMA: anynode UCMA 3.8.3

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.3

  • Trace: anynode trace 3.8.3

  • Administration: anynode ad 3.8.3

Improvements

  • In the anynode trace analyzer session-display the association of caller and called has been improved in certain refer situations

Bug Fixes

  • A potential crash while using SIP transport connections

anynode Setup 3.8.2 (January 22, 2018)

Technical Setup

  • Core: anynode 3.8.2

  • Frontend: anynode frontend 3.8.2

  • UCMA: anynode UCMA 3.8.2

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.2

  • Trace: anynode trace 3.8.2

  • Administration: anynode ad 3.8.2

Improvements

  • An initial version of a filter for SDP has been integrated which currently allows to remove AVP if SAVP is also present

  • If the transfer destination on a UCMA-node is a SIP address and no corresponding phone number is available the transfer is always done to Skype for Business

  • Tracing on the UCMA-node has been improved again

Bug Fixes

  • A potential deadlock in an internal handler

  • In the UCMA node an error while declining a transfer call via anynode. For example when no route is available. Notify UCMA that the transfer failed and reestablish the media

anynode Setup 3.8.1 (January 15, 2018)

Technical Setup

  • Core: anynode 3.8.1

  • Frontend: anynode frontend 3.8.1

  • UCMA: anynode UCMA 3.8.1

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.1

  • Trace: anynode trace 3.8.1

  • Administration: anynode ad 3.8.1

Improvements

  • Some incomplete new features have been removed from the anynode frontend

anynode Setup 3.8.0 (January 12, 2018)

Technical Setup

  • Core: anynode 3.8.0

  • Frontend: anynode frontend 3.8.0

  • UCMA: anynode UCMA 3.8.0

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.8.0

  • Trace: anynode trace 3.8.0

  • Administration: anynode ad 3.8.0

New Features

  • MS-TURN is now also being supported for ICE-negotiation in UCMA nodes

  • The registrar now also supports SIP flow handling

  • New VoIP provider profile: Optus Evolve Voice

  • New VoIP provider profile: Hl komm - HL Phone NG - Professional 4

  • New VoIP provider profile: COMvergence

  • New VoIP system: Oracle Communications SBC

Improvements

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.0g

  • DNS requests are now being treated in a separate process-domain and cannot stall other standard priority tasks on Linux as well

  • During media-negotiation the selection of the channel to be used for sending has been improved

  • Traces now allow to filter the payload of high-volume messages. The text field of a trace message is still available, but the memory-intensive payload is removed. This helps to reduce the size of traces.

  • Various improvements for handling hold-states

  • MaxForwards for sending OPTIONS is now being configurable in the transport-connections

  • The anynode media-pump is now user-configurable to improve TLS-connections to carriers need artificial silence packages to support certain tromboning scenarios

  • The UCMA-subsystem is now able to transmit session-based diagnostic info to the main anynode for easier analysis of problems

  • Benchmark-infos of the internal process-system can now be used for diagnostics

  • A remote anynode-UCMA can now be integrated using a wizard

  • Newly committed configurations are now being inserted into the trace

  • The anynode trace viewer can now show and export multiple configurations that have been committed during a trace-session

  • VoIP provider profile updated: DeutschlandLAN

  • VoIP provider profile updated: equada

  • VoIP provider profile updated: ecotel sipTrunk 2.0

  • Various wizards have been improved

  • The monitor-view in the anynode frontend has been extended by some informations concerning sources and destinations

  • In the configuration of the Load Balancer the entries can now be moved

  • A standard transport connection can now be configured with all options available in plain and registration transport connections

Bug Fixes

  • Microsoft Windows updates causing the GUID of the loop back-interface to change should not cause loss of internal IPC-connections anymore

  • A problem during call-transfer where wrong tags were written in the replaces-header

anynode release 3.6

Intro 3.6

Version Highlights

XXX

anynode Setup 3.6.18 (December 21, 2017)

Technical Setup

  • Core: anynode 3.6.18

  • Frontend: anynode frontend 3.6.18

  • UCMA: anynode UCMA 3.6.18

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.18

  • Trace: anynode trace 3.6.18

  • Administration: anynode ad 3.6.18

Improvements

  • A new options allows to let the session-expiration-timer to continue even when receiving INVITE-messages without session-expiration-header

anynode Setup 3.6.17 (December 15, 2017)

Technical Setup

  • Core: anynode 3.6.17

  • Frontend: anynode frontend 3.6.17

  • UCMA: anynode UCMA 3.6.17

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.17

  • Trace: anynode trace 3.6.17

  • Administration: anynode ad 3.6.17

Bug Fixes

  • A potential crash during configuration update

anynode Setup 3.6.16 (December 15, 2017)

Technical Setup

  • Core: anynode 3.6.16

  • Frontend: anynode frontend 3.6.16

  • UCMA: anynode UCMA 3.6.16

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.16

  • Trace: anynode trace 3.6.16

  • Administration: anynode ad 3.6.16

Bug Fixes

  • A potential problem with REFERS arriving very early in a session has been fixed

anynode Setup 3.6.15 (December 06, 2017)

Technical Setup

  • Core: anynode 3.6.15

  • Frontend: anynode frontend 3.6.15

  • UCMA: anynode UCMA 3.6.15

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.15

  • Trace: anynode trace 3.6.15

  • Administration: anynode ad 3.6.15

Bug Fixes

  • A potential deadlock in connection with load-balancing has been fixed

anynode Setup 3.6.14 (November 23, 2017)

Technical Setup

  • Core: anynode 3.6.14

  • Frontend: anynode frontend 3.6.14

  • UCMA: anynode UCMA 3.6.14

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.14

  • Trace: anynode trace 3.6.14

  • Administration: anynode ad 3.6.14

Improvements

  • An additional RFC-3551 configuration-option has been added to improve refer-interoperability between the combination of XCAPI/anynode with certain remote peers

  • An additional configuration-option has been added to improve interoperability by suppressing from-changes triggered by UPDATE-messages

  • Several improvements of call and transfer-handling for connections established via UCMA-nodes

Bug Fixes

  • In the anynode trace analyzer and the call-history a problem with assignment of node name to session has been fixed

  • For UCMA-connections an issue in media negotiation after a failed call transfer as been fixed. For the outgoing transfer call and offer negotiation was initiated but not finished due to the failed call. When starting the next transfer call no offer was generated. The issue did not happen, if the call was retrieved by the peer after the first call failed

anynode Setup 3.6.13 (November 14, 2017)

Technical Setup

  • Core: anynode 3.6.13

  • Frontend: anynode frontend 3.6.13

  • UCMA: anynode UCMA 3.6.13

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.13

  • Trace: anynode trace 3.6.13

  • Administration: anynode ad 3.6.13

Bug Fixes

  • A crash during shutdown of the UCMA module

  • A problem in media-negotiation of the UCMA module

anynode Setup 3.6.12 (November 13, 2017)

Technical Setup

  • Core: anynode 3.6.12

  • Frontend: anynode frontend 3.6.12

  • UCMA: anynode UCMA 3.6.12

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.12

  • Trace: anynode trace 3.6.12

  • Administration: anynode ad 3.6.12

New Features

  • Lync 2013 support for Exchange UM has been added

Bug Fixes

  • An LDAP-query with empty result is now being correctly processed in teldirLdap

anynode Setup 3.6.11 (November 02, 2017)

Technical Setup

  • Core: anynode 3.6.11

  • Frontend: anynode frontend 3.6.11

  • UCMA: anynode UCMA 3.6.11

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.11

  • Trace: anynode trace 3.6.11

  • Administration: anynode ad 3.6.11

Improvements

  • VoIP provider profile updated: DeutschlandLAN SIP-Trunk

Bug Fixes

  • Some correction in the INVITE state-machine in connection with offer and answer have been applied

  • A reception of a Response-Message does not require an existing CSeq-header in all cases

anynode Setup 3.6.10 (October 25, 2017)

Technical Setup

  • Core: anynode 3.6.10

  • Frontend: anynode frontend 3.6.10

  • UCMA: anynode UCMA 3.6.10

  • Java: JRE 8u152 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.10

  • Trace: anynode trace 3.6.10

  • Administration: anynode ad 3.6.10

Improvements

  • Some interop-improvements between SIP-implementations in connection with multiple m-lines in SDP have been integrated

  • VoIP provider profile updated: DeutschlandLAN

  • VoIP provider profile updated: equada VOIP-Trunk

Bug Fixes

  • The list of available IP addresses of the network interfaces is not displayed again on the anynode dashboard

  • An unselected SIP Transport within a Plain Transport Connection is now allowed if the necessary flags that require this SIP Transport are not set

  • A deadlock in the UCMA during add and remove of registered users, if they are already registered via the message waiting option

anynode Setup 3.6.9 (October 17, 2017)

Technical Setup

  • Core: anynode 3.6.9

  • Frontend: anynode frontend 3.6.9

  • UCMA: anynode UCMA 3.6.9

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.9

  • Trace: anynode trace 3.6.9

  • Administration: anynode ad 3.6.9

Bug Fixes

  • A potential crash during shutdown of the siptp-module

  • A problem during processing of SIP-states

  • A problem during routing has been corrected where only routes with configured condition were processed

anynode Setup 3.6.8 (October 16, 2017)

Technical Setup

  • Core: anynode 3.6.8

  • Frontend: anynode frontend 3.6.8

  • UCMA: anynode UCMA 3.6.8

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.8

  • Trace: anynode trace 3.6.8

  • Administration: anynode ad 3.6.8

Improvements

  • Standard Transport Connection‘s can now be enabled/disabled via conditions

Bug Fixes

  • A problem has been corrected where reject-routes sometimes signalled 603 instead of the configured status

  • A problem has been corrected where incoming session would not be accepted if no IRI-template had been configured

  • A problem has been corrected where a Referred-By-Header in an Invite was not forwarded

anynode Setup 3.6.7 (October 12, 2017)

Technical Setup

  • Core: anynode 3.6.7

  • Frontend: anynode frontend 3.6.7

  • UCMA: anynode UCMA 3.6.7

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.7

  • Trace: anynode trace 3.6.7

  • Administration: anynode ad 3.6.7

Bug Fixes

  • The check boxes Activate fail over operation mode and Select fail over targets sequentially (instead of randomly) are not interchanged anymore

  • Inputs in the non-operational status code field are now correctly saved on commit

anynode Setup 3.6.6 (October 10, 2017)

Technical Setup

  • Core: anynode 3.6.6

  • Frontend: anynode frontend 3.6.6

  • UCMA: anynode UCMA 3.6.6

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.6

  • Trace: anynode trace 3.6.6

  • Administration: anynode ad 3.6.6

Improvements

  • In the frontend and the anynode trace analyzer the dialed SIP-address is now also shown for UCMA calls

Bug Fixes

  • A potential deadlock during TLS-handshake

anynode Setup 3.6.5 (September 22, 2017)

Technical Setup

  • Core: anynode 3.6.5

  • Frontend: anynode frontend 3.6.5

  • UCMA: anynode UCMA 3.6.5

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.5

  • Trace: anynode trace 3.6.5

  • Administration: anynode ad 3.6.5

Improvements

  • An autoAttendantNumber can be configured for UCMA Nodes. If no suitable Skype for Business user can be associated, the SfB-autoAttendant is dialed instead

Bug Fixes

  • In some operation-modes using SIP-Flows an unnecessary configuration-prerequisite was checked and caused calls to fail

anynode Setup 3.6.4 (September 19, 2017)

Technical Setup

  • Core: anynode 3.6.4

  • Frontend: anynode frontend 3.6.4

  • UCMA: anynode UCMA 3.6.4

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.4

  • Trace: anynode trace 3.6.4

  • Administration: anynode ad 3.6.4

Improvements

  • If multiple channels are available for use by anynode‘s media-pump, encrypted channels will now be favored

  • If a user cannot be be found in the Active directory by the UCMA node, it will now signal 404 (not found) instead of 403 (forbidden)

Bug Fixes

  • A potential crash during reception of G.729 silence packages has been fixed

  • A mis-configuration while reading route-filters

anynode Setup 3.6.3 (September 13, 2017)

Technical Setup

  • Core: anynode 3.6.3

  • Frontend: anynode frontend 3.6.3

  • UCMA: anynode UCMA 3.6.3

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.3

  • Trace: anynode trace 3.6.3

  • Administration: anynode ad 3.6.3

Bug Fixes

  • A potential crash during ICE-negotiation has been fixed

anynode Setup 3.6.2 (September 11, 2017)

Technical Setup

  • Core: anynode 3.6.2

  • Frontend: anynode frontend 3.6.2

  • UCMA: anynode UCMA 3.6.2

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.2

  • Trace: anynode trace 3.6.2

  • Administration: anynode ad 3.6.2

Improvements

  • More detailed failure descriptions are now issued in case the startup of UCMA-node should fail

Bug Fixes

  • A potential minor memory-leak during TLS-protected SIP-connections has been fixed

  • A potential deadlock during startup of a UCMA-node has been fixed

anynode Setup 3.6.1 (September 05, 2017)

Technical Setup

  • Core: anynode 3.6.1

  • Frontend: anynode frontend 3.6.1

  • UCMA: anynode UCMA 3.6.1

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.1

  • Trace: anynode trace 3.6.1

  • Administration: anynode ad 3.6.1

Improvements

  • anynode trace analyzer now also support 16 kHz sample rate codecs

Bug Fixes

  • An issue in the frontend where changes in the router filter assistant were not applied if no condition was set has been fixed

  • An issue where the anynode trace analyzer did not display dynamic payloads correct has been fixed

  • An issue while writing trace-files in the anynode trace analyzer has been fixed

anynode Setup 3.6.0 (September 04, 2017)

Technical Setup

  • Core: anynode 3.6.0

  • Frontend: anynode frontend 3.6.0

  • UCMA: anynode UCMA 3.6.0

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.6.0

  • Trace: anynode trace 3.6.0

  • Administration: anynode ad 3.6.0

New Features

  • Support for generating MWI-notifications on SIP-nodes

  • Support for retrieving MWI-information on UCMA-nodes

  • Route-filters can now include conditions

  • Support for RFC-4040 (clearmode) has been added

  • Privacy properties can now be forwarded and / or included

Improvements

  • The μ-law and the A-law codec can now be set with variable frame rate

  • Some optimizations in sending RTCP have been applied

  • Further optimizations in ICE-negotiation

Bug Fixes

  • In the anynode trace analyzer calls with multiple sip-sessions will now show information of all sessions

  • A potential crash in the anynode trace analyzer when decoding special characters was fixed

  • A problem of failed UCMA user-registrations not being shown in the system view of the anynode trace analyzer has been fixed

  • A problem of failed SIP-registrations not being shown in the frontend has been fixed

anynode release 3.4

Intro 3.4

Version Highlights

MS-Turn

anynode Setup 3.4.10 (August 30, 2017)

Technical Setup

  • Core: anynode 3.4.10

  • Frontend: anynode frontend 3.4.10

  • UCMA: anynode UCMA 3.4.10

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.10

  • Trace: anynode trace 3.4.10

  • Administration: anynode ad 3.4.10

Improvements

  • The SIP-transport can now be configured to also use incoming SIP-flows to send new requests

anynode Setup 3.4.9 (August 23, 2017)

Technical Setup

  • Core: anynode 3.4.9

  • Frontend: anynode frontend 3.4.9

  • UCMA: anynode UCMA 3.4.9

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.9

  • Trace: anynode trace 3.4.9

  • Administration: anynode ad 3.4.9

Bug Fixes

  • When forwarding an asserted address the destination-address was used erroneously

anynode Setup 3.4.8 (August 22, 2017)

Technical Setup

  • Core: anynode 3.4.8

  • Frontend: anynode frontend 3.4.8

  • UCMA: anynode UCMA 3.4.8

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.8

  • Trace: anynode trace 3.4.8

  • Administration: anynode ad 3.4.8

New Features

  • New VoIP provider profile: ecotel sipTrunk 2.0

Improvements

  • Added the ability to enable strict number-comparison in UCMA-configuration for association of numbers to users

  • The UCMA-assistant was enhanced to allow reservation of media-ports

  • The UCMA-assistant was extended by an option to define LDAP-attributes which are used to associate number to Skype-for-Business users

  • LDAP-attributes names are now being parsed and erroneous input is flagged in the edit-field

  • The configuration of the Asserted URI in the node-assistant was separated into user- and a host-part

  • When creating a new node, the creation of a new network-controller is now selected by default

  • The update of SIP-transport-instances when network-options changed has been improved

  • VoIP provider profile updated: QSC IPfonie extended connect

  • VoIP provider profile updated: QSC IPfonie extended connect TLS

Bug Fixes

  • A problem in the detection of network status-changes was corrected both in anynode trace analyzer and status-monitor on the web-frontend

  • A problem in establishment of a media-session when using policy options was corrected

  • A memory leak when using IP-address-filters was corrected

  • A problem during shutdown of UDP-receivers was corrected on the Windows platform

anynode Setup 3.4.7 (August 15, 2017)

Technical Setup

  • Core: anynode 3.4.10

  • Frontend: anynode frontend 3.4.7

  • UCMA: anynode UCMA 3.4.7

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.7

  • Trace: anynode trace 3.4.7

  • Administration: anynode ad 3.4.7

Improvements

  • A SfB UCMA Node can now be configured to only allow outgoing calls if the destination user can be found during the search with one of the specified LDAP attributes

anynode Setup 3.4.6 (August 11, 2017)

Technical Setup

  • Core: anynode 3.4.10

  • Frontend: anynode frontend 3.4.6

  • UCMA: anynode UCMA 3.4.6

  • Java: JRE 8u144 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.6

  • Trace: anynode trace 3.4.6

  • Administration: anynode ad 3.4.6

Improvements

  • new SIP-configuration allows to start SIP-dialogs with a Cseq of 1 instead of a random value

anynode Setup 3.4.5 (August 10, 2017)

Technical Setup

  • Core: anynode 3.4.10

  • Frontend: anynode frontend 3.4.5

  • UCMA: anynode UCMA 3.4.5

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.5

  • Trace: anynode trace 3.4.5

  • Administration: anynode ad 3.4.5

Improvements

  • A new media-configuration allow to let anynode use the payload-types proposed by the other side instead of the local configured ones for interoperability with certain SIP implementations

  • The ICE-candidates are now being decimated during handshake

anynode Setup 3.4.4 (August 09, 2017)

Technical Setup

  • Core: anynode 3.4.10

  • Frontend: anynode frontend 3.4.4

  • UCMA: anynode UCMA 3.4.4

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.4

  • Trace: anynode trace 3.4.4

  • Administration: anynode ad 3.4.4

Bug Fixes

  • A minor memory-leak in the anynode monitor was corrected

anynode Setup 3.4.3 (August 07, 2017)

Technical Setup

  • Core: anynode 3.4.3

  • Frontend: anynode frontend 3.4.3

  • UCMA: anynode UCMA 3.4.3

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.3

  • Trace: anynode trace 3.4.3

  • Administration: anynode ad 3.4.3

Improvements

  • In the SfB UCMA Node, one or more LDAP attribute names can now be specified. An attribute name is used for an Active Directory query and identifies the attribute that contains the phone number of a Skype for Business user

anynode Setup 3.4.2 (August 02, 2017)

Technical Setup

  • Core: anynode 3.4.2

  • Frontend: anynode frontend 3.4.2

  • UCMA: anynode UCMA 3.4.2

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.2

  • Trace: anynode trace 3.4.2

  • Administration: anynode ad 3.4.2

Bug Fixes

  • In rare circumstances nodes did enter up-state directly after system boot due to the networklayer coming up in an odd way on Windows

  • In rare circumstances the web-fronted of anynode was not reachable directly after systemboot due to the network-layer coming up in an odd way on Windows.

anynode Setup 3.4.1 (July 26, 2017)

Technical Setup

  • Core: anynode 3.4.1

  • Frontend: anynode frontend 3.4.1

  • UCMA: anynode UCMA 3.4.1

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.1

  • Trace: anynode trace 3.4.1

  • Administration: anynode ad 3.4.1

Bug Fixes

  • During configuration-import using network-controller mapping the activation-state of reverse-DNS lookup was inverted inadvertently

anynode Setup 3.4.0 (July 25, 2017)

Technical Setup

  • Core: anynode 3.4.0

  • Frontend: anynode frontend 3.4.0

  • UCMA: anynode UCMA 3.4.0

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.4.0

  • Trace: anynode trace 3.4.0

  • Administration: anynode ad 3.4.0

New Features

  • The new scenario Create a relationship between a Microsoft SfB Voice mail System and a PBX or VoIP System has been added

  • The UCMA-node can now be configured to forward calls for specific users directly to voice mail

  • ICE negotiation is now being supported

  • Skype-for-Business specific adaptations for ICE-negotiation have been integrated

  • SIP-Transport-Layer alternatives have been extended in a major way

  • SDP is now also being accepted in multi-part bodies

  • Geolocation-informationen in PIDF+XML-multipart-bodies and in P-Access-Network-Infoheaders can now be relayed

  • RFC3323 SIP Privacy can now be transmitted

  • New VoIP provider profile: Swisscom Enterprise SIP

  • New VoIP provider profile: New Horizon

  • New VoIP provider profile: reventix SIPbase

  • New PBX system: SwyxWare 2015

Improvements

  • Circumvented some DTLS issues with OpenSSL

  • Forwarding of 488 responses is now supported

  • Creation of UDP-channels with strict RTP/RTCP semantics is now also supported on mapped address-ranges

  • Some optimizations in handling SDP-offers have been implemented

  • Various additional information is now being forwarded from UCMA-nodes to the SIP-node being routed to

  • Improved the registration for large number of Skype-for-Business users on the UCMA-node

  • Network-interfaces can now be defined using a specific subnet

  • The ability to customize the source number by source or destination number was added

  • The call-history has been extended by

    peak and average CPU usage

    the name of the used client-registration (if used)

    the memory-usage

    currently active sessions

    unique system- and session-identifiers

  • White list handling and configuration has been improved

  • Enhance trace-decoder for UCMA transfer streams

  • The anynode trace analyzer now shows memory-usage, average and peak CPU-usage and session-count in the session-view

Bug Fixes

  • The anynode trace analyzer now clears data in streams view before setting the selected stream. Prior to this fix the data from the last selected stream was shown

  • Renegotiation of media has been corrected for UCMA nodes when in hold-state

anynode release 3.2

Intro 3.2

Version Highlights

XXX

anynode Setup 3.4.1 (July 26, 2017)

Technical Setup

  • Core: anynode 3.2.7

  • Frontend: anynode frontend 3.2.7

  • UCMA: anynode UCMA 3.2.7

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.7

  • Trace: anynode trace 3.2.7

  • Administration: anynode ad 3.2.7

Bug Fixes

  • During configuration-import using network-controller mapping the activation-state of reverse- DNS lookup was inverted inadvertently

anynode Setup 3.2.6 (July 22, 2017)

Technical Setup

  • Core: anynode 3.2.6

  • Frontend: anynode frontend 3.2.6

  • UCMA: anynode UCMA 3.2.6

  • Java: JRE 8u141 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.6

  • Trace: anynode trace 3.2.6

  • Administration: anynode ad 3.2.6

Bug Fixes

  • A problem in the context of creating offers concerning hold-states

anynode Setup 3.2.5 (June 26, 2017)

Technical Setup

  • Core: anynode 3.2.5

  • Frontend: anynode frontend 3.2.5

  • UCMA: anynode UCMA 3.2.5

  • Java: JRE 8u131 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.5

  • Trace: anynode trace 3.2.5

  • Administration: anynode ad 3.2.5

Bug Fixes

  • A potential memory leak in the Windows LDAP implementation was corrected

anynode Setup 3.2.4 (June 16, 2017)

Technical Setup

  • Core: anynode 3.2.4

  • Frontend: anynode frontend 3.2.4

  • UCMA: anynode UCMA 3.2.4

  • Java: JRE 8u131 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.4

  • Trace: anynode trace 3.2.4

  • Administration: anynode ad 3.2.4

Bug Fixes

  • A potential memory leak in the Windows SNMP plugin-dll was corrected

anynode Setup 3.2.3 (June 08, 2017)

Technical Setup

  • Core: anynode 3.2.3

  • Frontend: anynode frontend 3.2.3

  • UCMA: anynode UCMA 3.2.3

  • Java: JRE 8u131 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.3

  • Trace: anynode trace 3.2.3

  • Administration: anynode ad 3.2.3

Bug Fixes

  • A potential busy-loop in a thread handling RTP with UDP-errors was corrected

anynode Setup 3.2.2 (June 02, 2017)

Technical Setup

  • Core: anynode 3.2.2

  • Frontend: anynode frontend 3.2.2

  • UCMA: anynode UCMA 3.2.2

  • Java: JRE 8u131 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.2

  • Trace: anynode trace 3.2.2

  • Administration: anynode ad 3.2.2

Improvements

  • The RTP-configuration option Negotiate consecutive RTP and RTCP ports will now also be honored if a static port-mapping has been configured for that node

anynode Setup 3.2.1 (May 31, 2017)

Technical Setup

  • Core: anynode 3.2.1

  • Frontend: anynode frontend 3.2.1

  • UCMA: anynode UCMA 3.2.1

  • Java: JRE 8u131 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.1

  • Trace: anynode trace 3.2.1

  • Administration: anynode ad 3.2.1

Improvements

  • In the node-interconnection-wizard the Remote-SIP-Domain and other data fields are now shown

Bug Fixes

  • Removed non-functional wizard intended for version 3.4.x

anynode Setup 3.2.0 (May 29, 2017)

Technical Setup

  • Core: anynode 3.2.0

  • Frontend: anynode frontend 3.2.0

  • UCMA: anynode UCMA 3.2.0

  • Java: JRE 8u131 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.2.0

  • Trace: anynode trace 3.2.0

  • Administration: anynode ad 3.2.0

New Features

  • The new scenario Create a relationship between a Microsoft UCMA Application Node and a PBX or VoIP System has been added

  • The Destination-URI can now be derived from the From header or the first/last entry of the diversion history

  • The Asserted-URI can now be derived from the first/last entry of the diversion history

Improvements

  • The Media Source subsystem has been re-organized and now supports a variety of countryspecific audio-signals

  • The UCMA-node can now be configured to explicitly set the state of a user to online

  • Various new information-elements can now be forwarded between nodes:

    hold-state

    transferrer dial string

    referrer-uri

    referred-by header

  • Routing now has ability to generate the source number by source or destination number

  • Each route can now contain multiple filters

  • It is now possible to use the transferrer dial string in routing

  • In the web-interface, the list of registered clients on a node now contains a column that shows the registered user

  • Various improvements in call-history-export:

    the char set can now be set

    date and time now also available as separate fields

    better machine-readable default encoding for date and time

    Basic authentication method added

    New fields have been added: CPU-usage and name of client-registration used for call

  • A warning message will be displayed if the browser does not meet the required prerequisites

  • A switch to enable or disable the call history has been added

  • A switch to enable or disable the regular clean-up of the call history has been added

  • A switch to enable the anonymization of dial strings in the Active Sessions and the Call History has been added

  • Information written into the event-log has been expanded:

    Successful login and logout of users on the frontend

    State of the UCMA-Node like successful or failed startup, connection-loss to SfB server, state of users etc.

    SIP-Nodes that switch to in operational due to missing response to Option-headers

    Failed Registrations at anynode‘s registrar due to forbidden or decline

Bug Fixes

  • A potential problem during establishment of IPC-connections between anynode‘s separate modules

anynode release 3.0

Intro 3.0

Version Highlights

UCMA Node

The new anynode version 3.0 now introduces the new UCMA node-type. With the UCMA node anynode integrates much deeper into a Skype for Business Environment thanks to this internal Microsoft API. UC Solutions based on SIP can use this new node-type to integrate much more seamless into Skype for Business. The SIP based UC-solution can trigger a real call-transfer within the Skype for Business Server. Thus both signalling and media-streams will be cut short. Skype for Business functions like chat, desktop-sharing and video are available once again if both parties are Skype for Business users. One additional important area is the direct integration of SIP based terminals. The UCMA node-type allows for easy integration of phones like DECT-devices into Skype for Business environments.

Wizards for Registration and Users

Wizards have been added for registering many SIP-phones and also the entry, editing an removal of users in anynode‘s static user-directory. Those wizards simplify the task of integrating SIP-phones with their respective user-credentials either into SIP or Skype-For- Business environments.

Export of Call-History

anynode‘s call history can now be exported into custom-formatted CSV files. Filters for the actual data-set to be exported can be specified. This feature is available both via a REST API and for human access on the frontends website.

Linux improvements

This version of anynode is the first one with support of the upcoming Debian 9 Stretch which should be available some time in March. While adapting anynode to run on this new platform, explicit support for systemd has been added which will also be used on Debian 8, Raspbian and Ubuntu 16.04. On the older Debian 7 and Ubuntu 14.04, the old System V init is still being used.

anynode Setup 3.0.15 (May 15, 2017)

Technical Setup

  • Core: anynode 3.0.15

  • Frontend: anynode frontend 3.0.15

  • UCMA: anynode UCMA 3.0.15

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.15

  • Trace: anynode trace 3.0.15

  • Administration: anynode ad 3.0.15

Bug Fixes

  • A Potential crash in media-negotiation was corrected

anynode Setup 3.0.14 (May 05, 2017)

Technical Setup

  • Core: anynode 3.0.14

  • Frontend: anynode frontend 3.0.14

  • UCMA: anynode UCMA 3.0.14

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.14

  • Trace: anynode trace 3.0.14

  • Administration: anynode ad 3.0.14

Improvements

  • Some improvements in the call-history export

Bug Fixes

  • A potential problem during connection establishment for IPC-communication between the individual anynode-modules

  • Route names are not overwritten/reset anymore when editing establishment properties

anynode Setup 3.0.13 (April 12, 2017)

Technical Setup

  • Core: anynode 3.0.13

  • Frontend: anynode frontend 3.0.13

  • UCMA: anynode UCMA 3.0.13

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.13

  • Trace: anynode trace 3.0.13

  • Administration: anynode ad 3.0.13

Bug Fixes

  • Corrected a potential crash that could occur during a connection-attempt using a registration containing nor AOR-address

anynode Setup 3.0.12 (April 12, 2017)

Technical Setup

  • Core: anynode 3.0.12

  • Frontend: anynode frontend 3.0.12

  • UCMA: anynode UCMA 3.0.12

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.12

  • Trace: anynode trace 3.0.12

  • Administration: anynode ad 3.0.12

New Features

  • New VoIP provider profile: RelAix

Improvements

  • Display-positions within streams of the Trace-Analyzer are stored and reused upon reentering the specific stream

Bug Fixes

  • In rare cases it could happen on complexly configured notes that registar-infos did not show on anynode dashboard and within the trace analyzer

  • Corrected a problem with selection of RTP packets within the trace analyzer

  • Call-History-Export failed in rare occasions due to exceeding an internal IPC-buffer-size.

anynode Setup 3.0.11 (April 04, 2017)

Technical Setup

  • Core: anynode 3.0.11

  • Frontend: anynode frontend 3.0.11

  • UCMA: anynode UCMA 3.0.11

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.11

  • Trace: anynode trace 3.0.11

  • Administration: anynode ad 3.0.11

New Features

  • New VoIP provider profile: Pure IP VoIP platform

Improvements

  • A session on the SIP registrar can now support early media

  • New IPC-connection certificates are now always signed with SHA-256

  • Enhanced error detection for sent SIP messages in trace-analyzer. When a SIP message could not be sent, this is now visible via red messages in the SIP call flow and SIP details view

  • In the anynode trace analyzer, the default time to insert a marker when a configured time difference between two SIP messages is reached is no one second (only for new installations)

Bug Fixes

  • A problem causing a node to hang during disabling of said node

  • Corrected some display-issues for nodes on anynode dashboard that were configured in a peculiar way

  • In the anynode trace analyzer a problem with assignment of a registrar to a node

anynode Setup 3.0.10 (March 29, 2017)

Technical Setup

  • Core: anynode 3.0.10

  • Frontend: anynode frontend 3.0.10

  • UCMA: anynode UCMA 3.0.10

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.10

  • Trace: anynode trace 3.0.10

  • Administration: anynode ad 3.0.10

Improvements

  • A session on the SIP registrar can now support early media

  • New IPC-connection certificates are now always signed with SHA-256

Bug Fixes

  • A problem while reading configuration for SIP authentication

  • A problem during export of call-history for calls going over a UCMA-node

anynode Setup 3.0.9 (March 27, 2017)

Technical Setup

  • Core: anynode 3.0.9

  • Frontend: anynode frontend 3.0.9

  • UCMA: anynode UCMA 3.0.9

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.9

  • Trace: anynode trace 3.0.9

  • Administration: anynode ad 3.0.9

Improvements

  • Enhanced error detection for nodes that support a limited amount of sessions

  • Add result code for the call history, when a call is rejected due to limited amount of concurrent sessions

  • Evaluate route type, when a connection could not be established. If the route type is reject, set the result code in the call history to rejected

  • In the anynode trace analyzer potential limits for a node are now displayed in the system view

  • On the UCMA-node, an additional info Phone URI is now added to trace-information

Bug Fixes

  • Corrected a problem during re-authentication

  • Forwarding of display name and caller number of the calling side on a UCMA node now also works in Connected State

anynode Setup 3.0.8 (March 15, 2017)

Technical Setup

  • Core: anynode 3.0.8

  • Frontend: anynode frontend 3.0.8

  • UCMA: anynode UCMA 3.0.8

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.8

  • Trace: anynode trace 3.0.8

  • Administration: anynode ad 3.0.8

New Features

  • New VoIP provider profile: M-net SIP-Trunk

Improvements

  • Improvements during handling of from-header

  • The frontend command line now has --ipv4 and --ipv6 parameters to make the web interface easier to bind to a corresponding IP version

anynode Setup 3.0.7 (March 09, 2017)

Technical Setup

  • Core: anynode 3.0.7

  • Frontend: anynode frontend 3.0.7

  • UCMA: anynode UCMA 3.0.7

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.7

  • Trace: anynode trace 3.0.7

  • Administration: anynode ad 3.0.7

New Features

  • New VoIP provider profile: M-net SIP-Trunk

Improvements

  • Display of nodes on anynode dashboard and in anynode trace analyzer was improved

anynode Setup 3.0.6 (March 07, 2017)

Technical Setup

  • Core: anynode 3.0.6

  • Frontend: anynode frontend 3.0.6

  • UCMA: anynode UCMA 3.0.6

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.6

  • Trace: anynode trace 3.0.6

  • Administration: anynode ad 3.0.6

Improvements

  • UCMA

    UCMA nodes now have a new potential error-state No Endpoint on anynode dashboard when no endpoint is configured for a trusted application

    Store information about trusted applications in trace properties to improve diagnostic capabilities

    Detect if an audio MCU is available and signal in anynode monitor status store

    Clear state of registered users, when the application name is changed, to ensure they are registered again

  • Policy can now be configured for the SIP-registar as well

  • When the static Asserted-URI is set, the userinfo field is now also displayed in the input editor

  • The SQLite library integrated into the Windows version of anynode has been updated to version 3.17.0

  • Various improvements in anynode trace analyzer

    Improve performance when loading traces containing huge store-properties

    Ensure the initial SIP transaction is added to the call instance. If this does not happen, the transport protocol is not detected or later during the call

    If multiple RTP receive streams belong to one RTP session that audio signal was shown with a gap. In addition, the warning in the media view about packet receive time difference was missing

    Show warning and error conditions in system view by changing the icon in the ribbon bar

    Show if a SIP node is out of service” because OPTION packets were not answered. Show if such a condition was detected previously

Bug Fixes

  • A potential busy-loop in the SIP registrar was corrected

  • A potential crash in the policy module was corrected

  • An erroneous display of the overall network status for all nodes was corrected

  • A potential crash in the anynode monitor when trace messages are enabled was corrected

  • A crash while decoding audio signal in the trace-analyzer was corrected

  • A crash in UCMA node was corrected when an incoming call was rejected by anynode

anynode Setup 3.0.4 (March 01, 2017)

Technical Setup

  • Core: anynode 3.0.4

  • Frontend: anynode frontend 3.0.4

  • UCMA: anynode UCMA 3.0.4

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.4

  • Trace: anynode trace 3.0.4

  • Administration: anynode ad 3.0.4

New Features

  • A static configurable fullback-number can be set to be used as P-Asserted for transmission to the peer of the node

Bug Fixes

  • Some configurations-defaults for Skype for Business

  • A problem during DNS-query

  • A problem in the configuration-import

anynode Setup 3.0.3 (February 20, 2017)

Technical Setup

  • Core: anynode 3.0.3

  • Frontend: anynode frontend 3.0.3

  • UCMA: anynode UCMA 3.0.3

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.3

  • Trace: anynode trace 3.0.3

  • Administration: anynode ad 3.0.3

Bug Fixes

  • The Remote SIP domain of a node could possibly be empty on anynode dashboard. That has been fixed

  • A potential crash of anynode monitor with IPC-misconfiguration has been fixed

anynode Setup 3.0.2 (February 16, 2017)

Technical Setup

  • Core: anynode 3.0.2

  • Frontend: anynode frontend 3.0.2

  • UCMA: anynode UCMA 3.0.2

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.2

  • Trace: anynode trace 3.0.2

  • Administration: anynode ad 3.0.2

Improvements

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.0e

Bug Fixes

  • The call history filter will not show an empty node-name anymore

  • An possible crash during shutdown of a UCMA-node has been fixed

anynode Setup 3.0.1 (February 14, 2017)

Technical Setup

  • Core: anynode 3.0.0

  • Frontend: anynode frontend 3.0.0

  • UCMA: anynode UCMA 3.0.0

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.0

  • Trace: anynode trace 3.0.0

  • Administration: anynode ad 3.0.0

Improvements

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.0e

Bug Fixes

  • A problem in the test-function of data-retrieval via LDAP was corrected

anynode Setup 3.0.0 (February 10, 2017)

Technical Setup

  • Core: anynode 3.0.0

  • Frontend: anynode frontend 3.0.0

  • UCMA: anynode UCMA 3.0.0

  • Java: JRE 8u121 (private install with anynodefe, now based on openJDK)

  • Monitor: anynode monitor 3.0.0

  • Trace: anynode trace 3.0.0

  • Administration: anynode ad 3.0.0

New Features

  • The new UCMA node type was established

  • Three new scenario-wizards for use with the UCMA node type have been added

  • One scenario-wizard to allow simple registration of SIP phones has been added

  • One scenario-wizard to add, edit or configure users of an existing user-directory has been added

  • An import wizard for the configuration has been added. If necessary, the network controllers can be adapted to your local system when importing

  • The call history can now be retrieved as a file via HTTP request. With the help of an export wizard, this can also be done by using the web page

  • The content of password fields can now made visible via an extra button

  • Edit fields have been unified and revised. Most fields now display immediately if an input is incorrect

  • New VoIP provider profile: T-Systems Corporate SIP

  • New VoIP provider profile: handSIP T.38 Fax SIP

  • New VoIP provider profile: handSIP VoIP SIP

  • New VoIP provider profile: equada

  • New VoIP provider profile: ThinkTel SIP

  • New VoIP provider profile: Voxbone Trunk

  • The anynode trace analyzer now shows packet loss for RTP send streams by interpreting the RTP receiver reports. Show packet loss in separate columns for the incoming and outgoing call

  • The anynode trace analyzer now shows SIP OPTIONS packet in the Failure view that have a negative or no response. Those packets are decoded and shown while processing the trace

  • Information about packet-loss during media-exchange has been integrated into the call history in the anynode frontend

  • Support for Debian 9 Stretch has been added

  • Support for systemd has been added for Debian 8, 9, Raspbian and Ubuntu 16.04

Improvements

  • VoIP provider profile updated: QSC IPfonie extended connect 1.6

  • The filter-function in the trace-analyzer has been improved in various ways

  • Certificates that are not used internally will now be removed as expected in the overview on the anynode frontend

  • The filter function in the trace-analyzer has been improved in various ways

  • Certificates that are not used internally will now be removed as expected in the overview on the anynode frontend

  • Deleted licences will now be removed as expected in the overview on the anynode frontend

  • When the anynode monitor looses the connection to the core anynode, the anynode frontend is notified to refresh various information (like nodes, network interfaces...)

  • Automatic port assignment can now reuse ports depending on the network controller configuration

  • The anynode wizard for creating new users is now available in a basic and extended version

  • An import-wizard for manipulations has been added

  • The User-Agent/Server header can now also be configured for the SIP registrar

  • In the Telephony Forwarding object, a setting was added, so a Proceeding can be forwarded as Ringing

  • Added setting in SIP user agent to support Call Completed Elsewhere

  • Setting in the SIP User Agent for the support of Call Completed Elsewhere added

  • Performance of transfer binary data in browser improved - Internet Explorer 10 is now mandatory

  • In the SIP User Agent, you can now configure for outgoing messages that the PAI and PPI headers can be set to information from the redirection history

  • A SIP-registrar can now serve as directory to base routing decisions on registration-states of specific users

  • The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.1.0d

  • The event log can be filtered by event IDs

Bug Fixes

  • Some display-updates (disconnected, active session tool tips) on the frontend now refresh correctly

  • An empty IPv6-address in short notation :: will now be recognized as a valid IPv6-address

  • A potential crash in the anynode dbg-module

  • An internal error in the trace-system

  • A small error in the Load Balancer

  • Several issues in connection management of LDAP