anynode Release notes 4.12 - 2.0

anynode Setup 2.2.10 (January 31, 2017)

Technical Setup

• Core: anynode 2.2.15

• Frontend: anynode frontend 2.2.7

• UCMA: anynode UCMA 2.2.4

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

• Monitor: anynode monitor 2.2.6

• Trace: anynode trace 2.2.1

Bug Fixes

• A problem with internal node-states has been fixed that prevented fail over-routes to work under certain circumstances

anynode Setup 2.2.9 (January 11, 2017)

Technical Setup

• Core: anynode 2.2.14

• Frontend: anynode frontend 2.2.7

• UCMA: anynode UCMA 2.2.4

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

• Monitor: anynode monitor 2.2.6

• Trace: anynode trace 2.2.1

Improvements

• The Media-forwarding-domain now operates in transcoding mode instead of bypass-mode by default

• Improved interoperability with Snom devices by adapting to some problematic Refer-Toheaders

Bug Fixes

• OPTIONS can now be received on SIP-Dialogs without problems

• A potential crash during reception of SIP INFO messages without message-body

anynode Setup 2.2.8 (December 20, 2016)

Technical Setup

• Core: anynode 2.2.12

• Frontend: anynode frontend 2.2.6

• UCMA: anynode UCMA 2.2.4

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

• Monitor: anynode monitor 2.2.6

• Trace: anynode trace 2.2.1

Bug Fixes

• Some specific variations of Licence files can now be imported correctly

anynode Setup 2.2.6 (December 15, 2016)

Technical Setup

• Core: anynode 2.2.11

• Frontend: anynode frontend 2.2.5

• UCMA: anynode UCMA 2.2.4

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

• Monitor: anynode monitor 2.2.6

• Trace: anynode trace 2.2.1

Improvements

• Early-Media handling has been improved in context with carrier Deutsche Telefon

anynode Setup 2.2.5 (November 30, 2016)

Technical Setup

• Core: anynode 2.2.10

• Frontend: anynode frontend 2.2.5

• UCMA: anynode UCMA 2.2.4

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

• Monitor: anynode monitor 2.2.6

• Trace: anynode trace 2.2.1

Improvements

• Monitoring of SIP-transactions for display in frontend

Bug Fixes

• A small memory leak during iteration of LDAP-result-sets

anynode Setup 2.2.2 (November 17, 2016)

Technical Setup

• Core: anynode 2.2.7

• Frontend: anynode frontend 2.2.3

• UCMA: anynode UCMA 2.2.4

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

• Monitor: anynode monitor 2.2.5

• Trace: anynode trace 2.2.1

New Features

• New VoIP provider profile: DSCI iPBX SIP Trunking

Improvements

• Resolving DNS has been improved à Encrypted LDAP-connections on Linux work again à

• VoIP provider profile updated: Telekom (IP-based) renamed to Deutsche Telekom (IP-based)

Bug Fixes

• A potential crash in DNS

• A potential crash in SDES-negotiation

• A potential deadlock in the anynode frontend during shutdown

• A potential offset of the display of audio-signals in the anynode trace analyzer

anynode Setup 2.2.1 (November 07, 2016)

Technical Setup

• Core: anynode 2.2.3

• Frontend: anynode frontend 2.2.1

• UCMA: anynode UCMA 2.2.2

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

• Monitor: anynode monitor 2.2.4

• Trace: anynode trace 2.2.0

Improvements

• The anynode monitor now has improved locking-behaviour during long-running background operations to not interfere with the anynode frontend

• The performance of retrieving the call-history was optimized

Bug Fixes

• An endless loop was corrected, which leads into high CPU load, when the function Terminate Session was activated in the anynode frontend

• A problem where peers could not hear each other was fixed which could happen when a session switched between locally generated tones and remote-media-data

• A crash in handling of SIP dialogs

• A problem during SDES-negotiation

• An erroneous notification of IP address mismatch on the dashboard

• A wrong pre-selection of US-ASCII during CSV-import

• A shutdown issue in the anynode monitor

anynode Setup 2.2.0 (October 28, 2016)

Technical Setup

• Core: anynode 2.2.0

• Frontend: anynode frontend 2.2.0

• UCMA: anynode UCMA 2.2.0

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

• Monitor: anynode monitor 2.2.0

• Trace: anynode trace 2.2.0

New Features

• A comprehensive LDAP-configuration wizard has been introduced

• The current configuration is now being stored in the trace-file

• New VoIP provider profile: DSCI iPBX SIP Trunking

• New VoIP provider profile: Sonetel

• New VoIP provider profile: Dokom21 SIP Trunk

• New VoIP provider profile: Gamma

• New VoIP provider profile: toplink Xpress

• New VoIP provider profile: wtSIPfon

• New VoIP system profile: Lancom VoIP Router

• CSV-import added to static dial-string directory and static user-directory

• This version of anynode allows much more fine-grained configuration of forwarding of information during calls between different nodes. This can either be on an abstract layer as well as down to the SIP-layer

• The ability to configure standard-monitor-options like the size of the call-history, warning intervals and presentation-options from the frontend has been added

• Initial support for TEL-IRIs

Improvements

• The trace can be deactivated on the website header. When deactivating it will be asked if you want to open the trace immediately.

• Various improvements in the connection-management of the anynode trace analyzers for live-trace-connections with anynode

• The anynode trace analyzer can now show various error conditions in the node-overview

• Various improvements in parsing trace-streams to relate various information to each other to improve tracing in many situations

• Improved presentation of properties in trace-streams

• Traced configuration-options are now placed into machine-readable properties instead of text-lines

• UDP and TCP port ranges are now displayed in the anynode dashboard

• The PAI-header can now be forwarded early-on

• A user-dependent dial sting manipulation was integrated into the user directory

• Sending of a re-Invite caused by the initial changes of the local address will now be suppressed by default

• Sending of a re-Invite minimized by taking account information already sent in previous responses

• Some optimizations concerning handling for remote transport iris Target-Refresh optimized

• SIP-URIs can now be created automatically based on the peer-registration

• A node can now report that it is up or down based on various criteria. This allows nonfunctional routes to be automatically ignored for better automatic fail over

• The transfer of calls has been improved by optionally accepting replaces without authentication

• SIP-Transport-Option added to insist on SRV-record resolving even if the target-URI already contains a port.

• In authentication for session and registrations the digest nonce, cnonce & oqaue have been truncated down to 32 bytes from 48, since some specific devices had problem with longer strings

• Multiple optimizations for LDAP-connections

• VoIP system profile updated: AVM FRITZ!Box

• VoIP provider profile updated: QSC IPfonie extended connect

• New defaults for Microsoft Skype for Business in several anynode-modules

• The OpenSSL library integrated into the Windows version of anynode has been updated to version 1.0.2j

• Added a media configuration option to let SDES communicate a lifetime to optimize Skype for Business interoperability

• Enhanced the options for media-negotiation

• The display of error-conditions on the dashboard have been improved (nodes, routes, network instances, IP-addresses & transport)

• The respective version-numbers of the various services (anynode core, anynode monitor and anynode frontend) are now shown in the footer of the anynode frontend

• The Node configuration page has been revised:

  A new section with policy settings have been added

  Media Sources are now available as a separate section

  Media Sources settings were provided with better descriptions

• Improved the interpretation of UTF8 characters in anynodemonitor

• Improved detection and display of end of connection for cancelled calls

• Enhance the detection to which CAPI node a call is attached

• Improved performance of anynode monitor by caching various information instead of reading from embedded database

• High-priority thread-pools now better match the actual CPU in order to improve performance on anynode systems with a high number of sessions

Bug Fixes

• SIP-messages will now only be sent to IP-version-compatible peers

• An issue was corrected if the remote peer sent a PPreferredIdentity-header but no PCalledPartyId-Header

• An issue during store/restore of media-options has been fixed

• An issue during the reception of dialog-establishing request without remote tag has been fixed.

• A reference-counting issue during REFER-handling was corrected

• Several REFER-handling issues have been corrected

• Fixed issue with path replacement in connection to registered peers

• Fixed a possible crash during registration

• Fixed a potential memory-leak in the front-end

• Network interfaces / IP addresses are now correctly synchronized with anynode so after changes the select boxes are always showing updated values

• The displayed network speed in the dashboard could differ slightly from the actual network speed

• When a LOD key was inserted into the text field of the license wizard using copy and paste within the Edge browser the page in the wizard remained in red state

• Fixed and endless loop, which led into high CPU load, when the function Terminate Session was selected in the anynode frontend

• Corrected an issue during shutdown of anynode monitor demon that could cause a reset of node and route statistics

• Fixed a monitor-crash when calls were cancelled and a registration was used for the outgoing call.

• Fixed a problem with assignment of registered clients to the Node. Depending on the timing the relation was not recognized

• Various issues have been fixed in the anynode trace analyzer that could cause deadlocks or crashes

anynode Setup 2.0.1 (June 14, 2016)

Technical Setup

• Core: anynode 2.0.1

• Frontend: anynode frontend 2.0.1

• UCMA: anynode UCMA 2.0.1

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

• Monitor: anynode monitor 2.0.1

• Trace: anynode trace 2.0.1

New Features

• Added a context menu to anynode trace analyzer for the connection status to reconnect to anynode

Improvements

• Mark connection status in status bar of anynode trace analyzer when the connection could not be established or was released by anynode

• Improved checking of the initial SDP-offer in LYNC environment.

• VoIP provider profile updated: QSC IPfonie extended connect

• VoIP system profile updated: AVM FRITZ!Box

Bug Fixes

• An endless loop was corrected, which leads into high CPU load, when the function Terminate Session was activated in the anynode frontend

• Corrected decoding of the network interface link speed for speeds higher than 2 GBit/s

• A problem with the progress bar was corrected that could occur if the loading was interrupted

anynode Setup 2.0.0 (June 10, 2016)

Technical Setup

• Core: anynode 2.0.0

• Frontend: anynode frontend 2.0.0

• UCMA: anynode UCMA 2.0.0

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

• Monitor: anynode monitor 2.0.0

• Trace: anynode trace 2.0.0

New Features

• A status page (named anynode dashboard) has been added which shows all relevant information about the current system state

• The Active Charts page has been added, which shows the progress of active calls, cPU load and memory usage

• A complete registrar has been integrated which includes the following changes:

  The SIP „User Agent“ and „Registration“ objects each now have a new element to configure authentication properties

  The Node“ and Registration assistants have been enhanced

  An Authentication Profile object now exists to configure options for various security values

  The configuration page of the Registration object has been redesigned to fit the new presentation style (see SIP User Agent configuration)

• Server side authentication of sessions and registrations is now supported

• A static „user management“ has been integrated for authentication purposes

• An aggregating dialstring directory has been added

• The ability to use live tracing has been integrated.

• An new node type named CAPI Client has been added; this can be used together with XCAPI to integrate H.323 controllers as nodes within anynode

• DTLS has been added as a supplemental means for encrypted media exchange

• New VoIP provider profile: CenturyLink

• New VoIP provider profile: my Tweak SIP Trunk

• New VoIP provider profile: sipload trunk

• New VoIP provider profile: twilio Elastic SIP Trunking

• New VoIP provider profile: virtuTEL

• New VoIP provider profile: VoIPRabbit

• New VoIP provider profile: Vodafone

• New VoIP provider profile: peoplefone

• A note can now be added to each configuration object for documentation purposes

• Raspbian on Raspberry PI2 and PI3 is now supported

Improvements

• Disabled configuration objects are now also updated (if necessary) during a version upgrade of anynode

• Only the version of the trace analyzer that matches the operating system on which the browser is running, is offered for download

• LDAP has been fundamentally reworked, and is now part of the core anynode service

• Transmission of large amounts of data between the frontend service and the web browser has been greatly improved

• The User Agent string that is being transmitted to the VoIP peer can now be freely configured

• The Node assistant now contains a white list which is preset by the various provider profiles to prevent unauthorized remote entities from sending signaling data to anynode

• Configuration objects in the left navigation tree are now sorted without case sensitivity

• An installation of anynode that does not have licenses now will be reconfigured automatically with the integrated demo license

• The display on the headline of the configuration now shows an active demo license; this area is now click able for easy launching of the license assistant

• Within the anynode trace analyzer, the Call History and Active Session screens now display lock symbols to indicate that the SIP signaling and media channels are encrypted (if applicable)

• When starting the web frontend, the Scenario Assistant is opened automatically if no nodes exist yet

• Additional options have been integrated into the SIP Transport element to improve compatibility to peers in case of UDP-to-TCP switchovers

• Reception of media data can now be restricted to peers that have been agreed upon during the signaling phase

• The assistant which defines the structure of dial strings can now define simple dial string lists

• Incoming and outgoing manipulation entries can now be cloned

• A new object graph has been implemented which automatically hides non existing objects, hints to mis configurations, etc.; this has also been complemented by additional objects to reduce the need to jump using open buttons

• The Node assistant now provides options to configure the node as a trunk, a registration server or a registration client

• The actions of storing the configuration (aka, clicking the Commit button), and activating or deactivating the trace, are now written to the event log

• The Scenario assistant now requires a number prefix, when Direct Routing is selected when connecting to a provider

• The Node assistant no longer prompts for routing domains when started from the Scenario wizard; those are set automatically

• When creating new routes, the Route Display Name is now preset automatically when Route Call has been selected prior

• The Min-Expires default value for SIP registrations is now 20 seconds

• In the Delete Object dialog, there is now text that explains why certain check boxes are disabled and unable to be deleted

Bug Fixes

• In the anynode monitor, the Transport protocol and Signaling protocol now show TLS as Transport protocol, not Signaling protocol

• If the anynode frontend had been configured on a network interface and the preferred IP address then became unavailable, anynode may have bound to another IP address; if the preferred IP address then became available, sometimes the anynode frontend would not switch back

• In the Chrome and Firefox browsers, text entered in edit boxes could be erroneously reverted when clicking on a checkbox immediately afterwards

• A problem while locating the Java virtual machine on Debian was fixed

• When not having write access in the frontend, a message box indicating this was displayed, even if no values were about to be changed.