COMtrexx® Next

The cost-effective, powerful COMtrexx Next is the ideal solution for business communication with up to 40 participants. It offers all the advantages of the COMtrexx platform in an uniquely compact and energy-saving format.

Downloads

Designation
Operating system

Version 2.4.6 (Stable) | 05.06.2025
2025.11.11 (Stable) | 29.01.2026
Google Android
Apple iOS
V8.9.3.11556 (Stable) | 12.03.2026
Windows Server 2016
Windows Server 2019
Windows Server 2022
Windows 11
macOS 14 "Sonoma"
macOS 13 "Ventura"
Windows 10 (ab Version 1903)
Windows Server 2025
macOS 26 "Tahoe"
macOS 15 "Sequoia"
1.4.9 (Stable) | 25.02.2026
macOS
Windows
Apple iOS
Google Android
V 2.4.2.43 (Stable) | 17.12.2025
Windows Server 2019
Windows 10 32-/64-Bit
Windows Server 2016
Windows 11
Windows 8.1 32-/64-Bit (Windows RT is not supported)
Windows Server 2022
V1.4.4.3 (Stable) | 25.07.2023
Windows 10 32-/64-Bit
Windows 7 32-/64-Bit SP1
Windows Server 2008 R2
Windows 2012 Server
Windows 2012 Server R1
Windows 11
Windows Server 2022
Windows Server 2012 R2

Documentations

LanguagesCurrent version
COMtrexx Migrationstool - Operation Manual V01 02/2026 Online
V01 02/2026 Online
Operation Instructions V13 06/2025 Online PDF
V13 06/2025 Online PDF
Privacy Policy V10 12/2025 PDF
COMtrexx Control Center - Operation Manual V09 03/2026 Online PDF
V09 03/2026 Online PDF
Instructions V04 01/2025 PDF
COMmander/COMpact PBX as a/b gateway V02 11/2022 PDF
V02 11/2022 PDF
V02 11/2022 PDF
Statements of conformity V01 08/2023 PDF

Operation Instructions

General information

Help/Instructions for COMtrexx from firmware version 2.4.6


Changed descriptions

Firewall releases

Updated/extended addresses.

Call forwarding

Updated/extended information on multi-level call forwarding and call forwarding loops.

Block- and allowlist

Updated information on the changed web interface.

Prevent update messages

Updated information on the changed setting.


Removed descriptions

Short Reference Identification

Query and programming digit sequences no longer supported removed.


Instructions

Version V04 01/2025

General information

Help/Instructions for COMtrexx Next from firmware version 2.4


Changed descriptions

Data protection

Notes updated regarding MFA, system events and sequence.

Initial Commissioning

Additional information on the display during the start process.

Version V03 01/2024

General information

Help/Instructions for COMtrexx Next from firmware version 2.2


Changed descriptions

Technical Data

Wall-mounted power supply type 2 and data.

Version V02 11/2023

General information

Help/Instructions for COMtrexx Next from firmware version 2.2


Changed descriptions

Technical Data

Wall-mounted power supply type and data.


COMmander/COMpact PBX as a/b gateway

General information

Instructions for COMmander/COMpact PBXs as a/b gateway on a COMtrexx


Changed descriptions

Overview of Functions

Information on the firmware version added.

Configuration of Subscribers

Information on the setting of exchange line authorisation added.

Privacy Policy

For the following products:

  • COMtrexx Advanced
  • COMtrexx Business
  • COMtrexx Flex
  • COMtrexx Next
  • COMtrexx VM Hyper-V
  • COMtrexx VM VirtualBox
  • COMtrexx VMware ESXi

 

Language:

  • German
  • English
  • French

FAQs

Due to the increased volume of telephone traffic, the transfer points of VoIP providers may reach their capacity limits. A solution is sought by the providers through load balancing. The load distribution is done with a DNS SRV query. The DNS SRV is used to enable the provider to notify the registrars prioritised by him. The DNS resolution must be carried out by the provider. For this purpose, the router must use the DNS servers of the provider.

Early generations of hybrid telephone systems:

  • COMpact 3000 analog, ISDN und VoIP
  • COMpact 5010/5020 VoIP
  • COMpact 5000 (R)
  • COMmander Basic.2 / Basic.2 19“
  • COMmander Business / Business 19“
  • COMmander 6000 (R) (RX)

These systems do not support the dynamic procedure and can therefore no longer be operated on the respective VoIP account after platform changeover. In these cases, the ICT system must be replaced by a compatible system.

 

Current ICT systems:

  • COMpact 4000
  • COMpact 5200 (R)
  • COMpact 5500R
  • COMtrexx alle Varianten

Note the following points in the configuration:

  • Configure the corresponding provider under Public networks, VoIP, Provider. The default value 5060 must be set as the registrar port and for the outbound proxy. The current templates are already preset for this.
  • Under Administration, IP configuration, the IP of the router or gateway must be entered in the 1st DNS server field.


 

Requirements

  • Each user must have a valid PBX Call Assist 5 license with active software maintenance.
  • The UCServer must be on the latest release (version 8.8.3 or higher).
  • The UCServer's operating system is MS Windows Server 2016 or higher. The .NET Framework 4.8 is installed.
  • The UCServer must be accessible from the internet:

via UCConnect / Mobility Services (a paid additional service from Estos)

- or -

configured according to the Estos best practice article https://support.estos.de/en/procall-enterprise/best-practice-ucserver-fuer-procall-mobile-apps-einrichten

 

Compatible web browsers

Chromium-based browsers, for example:

  • Google Chrome™
  • Microsoft® Edge
  • Mozilla Firefox®
  • Apple Safari

The following are not supported:

  • Microsoft® Internet Explorer
  • Google Chrome or Mozilla Firefox on mobile devices such as iOS
  • Old versions of Microsoft® Edge (without Chromium)

 

PBX Call Assist Web does not support use on mobile devices such as smartphones or tablets running Android or iOS.
The respective PBX Call Assist Mobile App (for Android or iOS) should be used.

Note: The PBX Call Assist Client for Windows should be closed before using PBX Call Assist Web, if necessary.

Port Forwarding

The PBX Call Assist Web WebRTC application runs as a website (https://auerswald.procall.de) within a web browser and is delivered via the https protocol. This requires the https port (443, outbound) to be forwarded.
In summary, the most common port forwarding requirements for WebRTC are:

  • Ports 80 and 443 for signaling
  • Port 3478 (UDP and possibly TCP) for STUN
  • Port 5349 (TCP) for STUN over TLS
  • Ports for TURN relays, if required

Technical requirement: Asix AX88772B chipset

The following USB network adapters have been successfully tested:

  • EDIMAX EU-4208 USB 2.0 Ethernet Adapter
  • i-tec USB 2.0 Ethernet Adapter