anynode Release notes 4.12 - 2.0

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