bilboard graphic anynode release 3.6

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