billboard graphic anynode release 3.8

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