billboard graphic anynode release 3.18

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