The current Version 2.6

Help > About ... > The current Version 2.6

New or revised features published with this release are listed here.

You will find further information about new features in the firmware and the associated documentation on the Internet under Auerswald Support/FONtevo Support.

Important Update Information

Versions 2.6.1 to 2.6.4 were not available on the update server due to extensive changes. As of version 2.6.5, the update is possible via the update server again.

When updating to a version 2.6.x, in some cases it may be necessary to make changes to the configuration. Please refer to the notes in the release notes of versions 2.6.1 and higher.

Logging in

Improved security when logging in to the web interface.

Avahi daemon

The Avahi daemon can now be disabled to prevent the local domain from being resolved:

•Network > Server Service > Zeroconf > Enable Avahi daemon

COMfortel Softphone 2

The softphone is now also supported on the second network interface (LAN 2).

New option ICE for finding the best possible transmission route to be found between the softphone and PBX:

•Administration > VoIP > VoIP configuration > Proxy server for Online services > Use ICE

Note: If you experience audio issues, this option should remain disabled.

Improved communication between COMtrexx and COMfortel SoftPhone 2 resolves issues with loading voicemails on the softphone.

Requirement:COMfortel SoftPhone 2 as of version 1.4.0.

Important: Support for the COMfortel SoftPhone (1st generation) will be discontinued on 31 December 2025. This version can therefore only be used to set up the COMfortel SoftPhone 2.

Further help under Softphones

Further help under Network interface (second)

COMtrexx Control Center

Improved security when pairing with the COMtrexx Control Center and when checking the associated access data.

COMtrexx VM

There is now just one COMtrexx VM firmware file (*.rom) for all COMtrexx VM variants (and COMtrexx Advanced).

A new COMtrexx VM variant is now available with COMtrexx VM for Proxmox VE.

Further help under COMtrexx VM variants

External Devices

New and optimised settings pages:

•External Devices > ...

External Telephony

Internal adjustment of SIP processing for improved performance and stability, as well as more reliable operation under high loads. This is accompanied by higher provider compatibility thanks to more flexible setting options.

Note: Provider templates used to date will continue to function after the update.

Note: Provider templates exported after the update are not compatible with older firmware versions.

Note: If available, please use the latest provider templates provided by us:

•Exchange lines > Providers and Accounts > Import > Online configuration

Important: For a stable internet connection, we recommend using the DNS servers provided by your internet service provider:

•Exchange lines > Providers and Accounts >

> SIP > Name resolution > Use own DNS (via IAD)

•If provider-specific DNS servers are not available or known, ensure that only a single DNS server is used for telephony. If two DNS servers are used in the IP configuration, you can, for example, enter one of them in the provider configuration:

•Exchange lines > Providers and Accounts >

> SIP > Name resolution > Use own DNS (via IAD)

Note: The configuration of the providers changes as follows with the update:

•More flexible and new setting options for

•Number presentation (outgoing) and

•Number presentation (redirect)

•New RTP customisation options

•RTCP (Real-time Transport Control Protocol)

•SSRC (Synchronization Source)

•Bandwidth

•X-nat

•Connection information in media level

•Elimination of setting options that have become superfluous

•NAT traversal | use parameters ';alias' and ';keep' in the VIA header

•Automatic silence suppression

•Codec settings | Compromise

•STUN server | Interval for STUN server query

•Use URI parameter (user)

•Support T.38 for providers

•Evaluation of incoming SIP messages

Further help under VoIP telephony

Device Support

Additional RTP configuration options for internal VoIP devices

•Administration > VoIP > VoIP configuration > RTP

−RTCP (Real-time Transport Control Protocol)

−SSRC (Synchronization Source)

−Bandwidth

−X-nat

−Connection information in media level

Network

A USB network adapter connected to the COMtrexx Next can now be configured as a second network interface (LAN 2).

Important: You can find the technical requirements and a list of compatible USB network adapters at: Auerswald Support

The softphone is now also supported on the second network interface (LAN 2).

New and optimised settings pages:

•Network > ...

Important: Network settings from backups of older firmware versions (older than 2.6.1) can no longer be used. When importing such a backup, deactivate the restoration of network settings.

Further help under Network interface (second)

Further help under Network

Further help under Backup

OpenVPN

Improved security when importing OpenVPN configuration files.

System components

Updated system components close known security vulnerabilities.

VoIP registration

If a provider requests a different registration time with the SIP message 423 Interval Too Brief, this is now automatically applied to the configuration of the provider.

After a VoIP account is logged out, the associated TCP connection is now closed immediately.

Web interface

Improved security of the web interface through stricter checking of inputs, limitation of the access rate and additional security headers.

Certificate for SIPS/SRTP

Improved security through stronger encryption of the SIP connection. As of version 2.6.1, the COMtrexx generates root certificates with a 4096-bit RSA key.

Important: If the existing certificate for SIPS/SRTP was already generated in an older firmware version (up to version 2.4.6), the certificate must be deleted and regenerated after the update (to version 2.6.1 or higher). The old certificates will no longer be supported with future firmware versions (higher than 2.6.5). Encrypted connections will then no longer be established. It may no longer be possible to make calls.

Important: Even without actively renewing the certificate, for phones that have not been provisioned the root certificate must be exported once and imported into the relevant phones.

Further help under Certificates