Aaron

Firmware version
- as of version 1.8.2 (COMtrexx)
- as of version 8.4B 000 (for all other listed PBXs)

Aaron.ai is listed as a VoIP Provider, but Aaron is actually a service provider that offers automated Voice services, as such no calls can be placed or received through a Aaron trunk. Aaron provides their customers with a dedicated number for their SIP services which allows the customers to forward calls to this number (and this number only) on a Aaron trunk.
To make sure that only the dedicated calls a routed to Aaron and no other calls are routed this way some special settings are required.
Step 1: under “Public switched tel. Networks”→ VoIP→ Provider click import and select the Aaron template.
Step 2: under VoIP→ Accounts add a new Account with the credentials provided by Aaron.
Step 3: In “Subscriber (scr.)”→ Profiles → Configuration add a new profile named “No Aaron” based on “Standard Phone”, which has to be assigned to all telephones with outside lines instead of the “Standard Phone” profile. Activate the Profile override for “Exchange line authorisation” and switch it to “Exchange line dependent”. Under “Expert” switch Aaron to “Only internal” and save the settings.
Step 4: Assign the new profile “No Aaron” to all phones.
Step 5: Add a new Dummy Subscriber which will be used to forward calls to Aaron. The Dummy can not use the Profile “No Aaron” but will have to use the Standard phone profile. However in “Subscriber (scr.)”→ Phone numbers → (Dummy Account) → “Exchange line settings”→ “Exchange line authorisation” you have to switch it to “Exchange line dependent” and use the Expert button to set all providers beside Aaron to “Only incomming”. Aaron should be switched to National or International if the number Aaron provided you is not a national number for you.
Further you will have to set and activate “CF (call forwarding) immediately” to the SIP Access number provided by Aaron and activate “cascading” for the Dummy Subscriber.
Save the settings.

Take note: If further subscribers are added you have to make sure they use the “No Aaron” profile.

Use: by setting CF on busy or CF on no reply to the number of the dummy subscriber, calls can now be transferred to Aaron.

The transmission path from the system to the mail server / mail provider is usually encrypted using SSL/TLS.
Encryption of mail and attachments up to the recipient of the mail (end-to-end encryption) is not possible.

Only for external VoIP accounts or on an analogue terminal. On external ISDN connections, to ISDN or VoIP extensions, caller identification cannot be prevented.
In the configuration of the VoIP provider used, a user-defined evaluation can be defined under Evaluation of incoming SIP messages, in which all selections for search prioritization are set to None.
For analog terminals, the CLIP info can be deactivated under Subscriber / Function overview / Analogue settings.

Yes, the recording of incoming and outgoing calls can be deactivated in the COMpact 4000/5000/5200/5500 and COMmander 6000 PBXs under User data / Call data / Settings.

No, all messages are stored on the storage medium (USB stick or SD card) unencrypted. The storage media of COMpact 4000/5000/5200/5500 and COMmander 6000 have the ext4 format and are therefore usually not readable on a Windows PC without additional software.
The storage media of the system telephones are in FAT/FAT32 format and can be read out on a Windows PC without additional software.

Voraussetzungen:

• PBX Call Assist ab Version 5
• .net Framework ab Version 4.8 am UCServer
• PBX Call Assist 5 UCServer mit Internetzugriff zu Microsoft Diensten wie graph.microsoft.com und login.microsoftonline.com
• Ab Office 365 E3 mit Teams, oder vergleichbar
• Zugriff auf Azure Active Directory
• Übereinstimmung der Benutzer in der UCServer Verwaltung und im Azure Active Directory.
• API Berechtigungen im Unternehmen (tenant), zu gewähren sind (Admin und User consent) für die Integration PBX Call Assist 5 in Teams
• admin consent: Zustimmung erforderlich zum Schreiben von Präsenzen
• user consent: Zustimmung erforderlich zum Lesen von Präsenzen

Vorgehensweise:

• Installation von PBX Call Assist 5 als Neuinstallation oder Update
• Tenant-ID im Microsoft Azure Portal auslesen
• Im Azure Portal „User consent und Admin consent“ zulassen
• UCServer Verwaltung öffnen > Services > Integration in MS Teams

Aktivieren Sie die Funktion und tragen Sie die Microsoft Teams Tenant ID ein.

Erteilen Sie nach dem Login die Zustimmung des Benutzers und Administrators:

Hinweis: Bitte beachten Sie, dass bei Passwortänderungen oder für ein abgelaufenes Passwort des Administrator- oder Benutzerkontos, welches für den Admin oder User Consent verwendet wurde, die Berechtigung im UCServer erneut ausgestellt werden muss, um die Funktionalität sicherzustellen.

Bereitstellung der APP:
Im PBX Call Assist 5 Installationspaket finden Sie im Unterordner "MS-Teams" die PBX Call Assist 5 Manifestdatei "AppManifest.zip". Diese kann vom Administrator im Microsoft Teams Admin Center hochgeladen werden und installiert die aktuellste Call Assist App für Microsoft Teams

Nutzung in Microsoft Teams:
Nachdem die PBX Call Assist App für Microsoft Teams vom Administrator im Microsoft Teams Admin Center freigegeben wurde, steht die App allen Mitarbeitern der Organisation im Microsoft Teams App Store unter "Für Ihre Organisation entwickelt" zur Verfügung und kann einfach zum Microsoft Teams Client hinzugefügt werden:

Der Benutzer meldet sich mit seinen Benutzerdaten (UCServer) an.

Die Service URL entspricht der Adresse des UCServers im Netzwerk. Verwenden Sie http://localhost:7225

Danach steht die PBX Call Assist App dem Nutzer zur Verfügung:

Systemphone compatibility-matrix as PDF-file

Preparations

Preparing the PBX for Remote Access

• Activate "Enable dealer access via internet" in "Settings -> Remote Configuration" on the PBX.
• If using method 2 you also have to define a remote switching number as well as an external PIN.

Registering the PBX in ARA

• Go to "Registrierte TK-Anlagen" (registered PBXs)
• Press the "+"-symbol to register a new PBX.
• Enter at least the serial number, a name and the type of PBX of which you want to access.
• Screenshots:

Activating remote access

Method 1: Activation by any internal phone

• Tell your customer to dial the following sequence on any internal phone:  ##8 Admin-PIN | Subadmin-PIN | Benutzer-PIN * 91 # (example: ##8 471208* 91 #)
• Click the refresh- (next to the "+"-symbol) and then the "Verbinden" (connect)-button in ARA.

Method 2: Activation by the dealer from a distance

• Dial the previously configured remote switching number from any external phone.
• After the switching tone enter the following sequence: ##8 external PIN * 91 # (example: ##8 471108* 91 #)
• Click the refresh- (next to the "+"-symbol) and then the "Verbinden" (connect)-button in ARA.

Data privacy

Auerswald takes the protection of personal data very seriously. Please read the internet privacy statement and the general terms and conditions.

In principle, PBX Call Assist 5 can still be used. However, if the software assurance is not extended, the scope of features will be significantly limited: neither the Microsoft Teams app nor the latest versions of the mobile apps will be useable. In addition, systems without software assurance do not receive bug fixes and security updates, and there is no access to subsequent releases with new functions.

Recommended action for systems possibly affected by hacker attacks:

1. Deactivate all port forwarding to the ICT system!
2. Check the log and make sure that the logins are traceable
3. Change the username, PIN and admin password
4. Check whether there are newly created sub-admins, users, participants or groups and change the passwords
5. Change passwords for public VoIP providers
6. Check call deflection

Check the following points for all profiles and properties (users, participants, groups, etc.):

1. Check the dialling privileges
2. Check parallel call
3. Check call deflections
4. Check voicemail boxes, check activation of remote control and change PINs
5. Check the deputy functions of the voicemail boxes and the registered destinations
6. Check Follow-Me settings

Check other configurations:

1. Check whether remote access by telephone (switching functions remotely by telephone) is active. Change PINs or, if unused, switch them off
2. Check automatic reception, check activation and registered destinations
3. Check FMC/call through functions, check users and dialling privileges
4. Check entries in the IP release list

When using Auerswald IP system telephones with integrated voicemail:

1. Check the access data, change the password
2. Check the destinations for call deflections
3. Check the voicemail boxes, check activation of remote control and change PINs

Requirements:

PBX firmware 8.2 or newer

• COMpact 4000
• COMpact 5x00(R)
• COMmander 6000
• COMtrexx firmware 1.6.1 or newer

COMfortel WS-500x firmware 2.48 or newer

• Alarm-Messaging or Alarm-Messaging-Location Licences in the DECT Manager

To use the alarm-messaging or alarm-messaging-location features, the provisioning file for the COMfortel IP DECT system must be supplemented in the telephone system.

Switching on the function:

<!-Switch on alarm messaging and location for all handsets--->.

  <oper name="set_hs_aml" value="@">
   <param name="LocationAML" value="1"/>
   <param name="MessagingAML" value="1"/>
  </oper>

OR

<!-- for individual handsets -->

  <oper name="set_hs_aml" value="IPUI des Handsets">
   <param name="LocationAML" value="1"/>
   <param name="MessagingAML" value="1"/>
  </oper>

Activate alarm server certificate:

  <oper name="set_uci">
   <param name="mosquitto.listener.enabled" value="1" />
  </oper>

Release of the ring tones in the COMfortel DECT handset:

  <settings version="1.0" productID="e2">
   <param name="AmlGlobal.0.HottestAlertNameHigh" value="High prio"/>
   <param name="AmlGlobal.0.HottestAlertNameMid" value="Medium prio"/>
   <param name="AmlGlobal.0.HottestAlertNameLow" value="Low prio "/>
  </settings>

If SIP text messages are to be displayed (e.g. with the call systems GIRA 834 Plus and Hospicall P3 or P7), the following must be added:

<!-- Set display name, priority, display duration, message memory duration and ringtone. -->

   <param name="SipProvider.0.AML_TitleText" value="GIRA Rufsystem"/>
   <param name="SipProvider.0.AML_Prio" value="3"/>
   <param name="SipProvider.0.AML_PresentationTimer" value="10"/>
   <param name="SipProvider.0.AML_TTL" value="3600"/>
   <param name="SipProvider.0.AML_AlertInfo" value="msg_melody_mid"/>

Assigning the AM and AML licenses

Download PDF (German) for setting up the messaging interfaces for the COMfortel® IP-DECT system and the COMfortel® D series via COMtrexx® autoprovisioning

Due to ever-increasing IT security requirements and new specifications from providers, Auerswald cannot guarantee that all telephones from other manufacturers can be put into operation and used permanently with the full range of functions. Especially with older third-party telephones, which no longer receive firmware updates from the respective manufacturer, functions can only be supported to a limited extent or not at all.

Workaround for the COMfortel IP-DECT system

With firmware 2.53 the number of AM and AML licenses present in the COMfortel IP DECT system is checked. If no licenses or less licenses than handsets are active in the system, in rare cases an error message appears in the handsets after some time. In addition, this instruction saves the manual assignment of AM and AML licenses to the handsets in the DECT Manager.
You can remedy this with this workaround:
Please create a new template for COMfortel WS-500 in the phone system. Then click on Edit.
In the provisioning file, search for „<!—Enable AML for all connected handsets".

Change these parameters:

<param name="LocationAML" value="0"/>
<param name="MessagingAML" value="0"/>

In the PBX, assign the provisioning file to the DECT manager. Perform provisioning. Open the provisioning file again.

Now the tag must be commented out:
Please cut out „-->“ in the first line.

<!-- Enable AML for all connected handsets -->
<oper name="set_hs_aml" value="$(m5x0.ipui)">
   <param name="LocationAML" value="0"/>
   <param name="MessagingAML" value="0"/>
</oper>

And add at the end of the tag

<!-- Enable AML for all connected handsets
<oper name="set_hs_aml" value="$(m5x0.ipui)">
   <param name="LocationAML" value="0"/>
   <param name="MessagingAML" value="0"/>
</oper>
-->

Perform provisioning.

Subsequently, in the DECT Manager under

Settings -> Handsets

Edit the appropriate handsets and enable and save messaging:

Messaging -> Yes

Setting up the alarm-messaging or alarm-messaging-location function via provisioning

From Q1/24 onwards, it will be possible to extend software assurance beyond January 1st, 2025.

The price for software assurance will be around 20% of the full license price per user and year.

Yes, this will be possible. Additional costs will arise though if the software assurance is resumed after a break. We will provide more detailed information as soon as the software assurance prolongation is available in Q1/2024.

Requirements:

• Auerswald COMpact 4000, COMpact 5000/5000R, COMpact 5200/5200R, COMpact 5500R, COMpact 5010/5020 VoIP or COMmander 6000/6000R/6000RX
• LAN-TAPI-driver from version 2.4.0.6 and up installed

Configuration:

If not already done so, enter your dialing rules and location information in the telephone-/modem options (Windows Control Panel). Enter the connection information (IP-address, port, LAN-TAPI-password) in the LAN-TAPI-driver's settings.

On the PBX's menu check or otherwise change the LAN-TAPI-settings (IP-address, port, LAN-TAPI-password) according to the driver's settings.

Make sure that any necessary dongle licenses were purchased and also create a list of LAN-TAPI subscribers in the PBX's LAN-TAPI-settings.

Deactivate the RAS-service in your server's admintrative tools and reboot the machine. After the reboot restart the server's telephony service.

Test:

Run the Windows dialer and set the subscriber you want to test in the options.

Enter a destination number and dial.

Network and computers

• Maintain a stable network environment. The TAPI-server needs to have a permanent connection to the PBX.
• Remove any unnecessary TAPI-related entries (e.g. HID, 323 etc.) in the advanced Telephone-/Modem options (Windows Control Panel).
• Check if the operating system of the participating computers is supported by our driver or software.
• Operation of LAN-Tapi services on several clients is possible if a domain controller (DC) with configured telephone service is available and the clients connect to this DC.
• Operation of LAN-Tapi services on a single client is possible if the driver is installed on this client.
• Please ensure that the LAN-Tapi-driver is only installed once across the network.
• On a terminal server it is not possible to control access rights to subscriber lines. For this reason this type of installation is not recommended.

PBX

• Check whether the PBX supports LAN-Tapi. For information see the features summary for the PBX on www.auerswald.de.
• By default our PBXs come with a certain number of LAN-tapi lines that can be used. Additional lines can be purchased in the Auerswald online shop shop.auerswald.de.

Telephones

Depending on the phone the full extent of the LAN-Tapi functions may not be available. For example, among others, automatic call setup, toggling and forwarding calls is not supported with standard phones (non systemphones). For more detailed information please see the description of the LAN-Tapi driver on www.auerswald.de.

Software

• CTI software usually requires separate paid licenses from the manufacturer. These licenses must be purchased in addition to the licenses for the PBX's LAN-Tapi lines.
• With PBX-Call Assist the purchase of the software licenses is necessary from the first subscriber (the LAN-TAPI activation for the PBX is already included in the same number).
• When using PBX Call Assist in a terminal server environment, please note that the PBX Call Assist client can only be used without TAPI or with standard TAPI (outgoing dialling only). Using the extended remote TAPI driver (outgoing dialing and display of incoming calls) in such an environment is not possible (will be queried during the installation of the client software).

PBXs with external ISDN connection

If you have a router that supports IP-telephony which also offers an internal ISDN-port (S0-port) you can generally connect the PBX's external ISDN-port to it. It is to note however that the PBX is now operated as a sub-PBX behind your router. Various features which are controlled by the network provider and operated by the PBX (such as call-forwarding via provider) can no longer be used. Since this is also dependent on the router we can't provide a listing of what exact features these are.

PBXs with external analog connection

If you have a router that supports IP-telephony which also offers internal analog ports you can generally connect the PBX's external analog port to it. It is to note however that the PBX is now operated as a sub-PBX behind your router. Various festure which are controlled by the network provider and operated by the PBX (such as call-forwarding via provider) can no longer be used. Since this is also dependent on the router we can't provide a listing of what exact features these are.

PBXs with external VoIP connection

If your network provider also provides you the necessary data (e.g. username, password) and allows operating alternate hardware, the VoIP-accounts can be configured directly in your PBX. A converter/gateway (e.g. VoIP-to-ISDN gateways) is not necessary. For this the PBX just has to be integrated in your network, so it can access the internet.

Note: These settings apply to all Auerswald PBXs that provide external internet telephony (VoIP).

COMpact 3000:

In "configuration -> Voice over IP (VoIP) -> VoIP provider" enter a name for the new account, select the according VoIP provider as well as the connection type and click on the green plus-symbol to generate the account.

COMpact 5010/5020, COMmander Basic2/Business:

In "COMset -> external numbers -> Voice over IP (VoIP) -> Provider" click on "online configurations" to download the appropriate provider template (if available).

Afterwards switch action to "import", select the downloaded template und import it.

In "configuration -> Voice over IP (VoIP) -> Accounts" enter a name for the new account, select the appropriate provider as well as the connection type and click on "execute" to generate the account.

COMpact 4000, COMpact 5000, COMmander 6000:

In "Public switched tel. networks -> Voice over IP (VoIP) -> Provider" click on "online configurations", select the according provider template (if available) and "load configuration".

In "Public switched tel. networks -> Voice over IP (VoIP) -> Accounts" click on "New", enter a name for the new account, select the appropriate provider as well as the connection type and click on "save" to generate the account.

Under the following conditions the PBX can signal the busy-tone for addional incoming callers:

1. The external call is distributed to only one subscriber; call-waiting must be disabled. Also no parallel call or call-forwarding on busy must be enabled for the internal or external number.
2. Busy-on-busy is enabled for the external or internal group-number (depending on the PBX). In current systems the maximum number of connections before the busy-tone is played back can be set.

 If these conditions are met, additional incoming callers get the busy-tone. If it doesn't work it is not the PBX's fault anymore. What could be the cause now?

1. The PBX is not operating directly on the public line and might be connected to the internal ISDN-port of a VoIP-router for example. In this case the PBX is signaling busy to the router. The router on the other hand only recognizes a busy device and eventually calls other devices (depending on the router's own call-distribution). Here it should be checked whether the router also provides a suitable setting or if the PBX can be connected directly to the public line without router.
2. Another possibility is that another device is operating in parallel to the PBX (e.g. an alarm-system). Here the PBX signals busy to the provider but the other device is available for incoming calls and therefore rings; the caller gets the ringing-tone, not busy. In this case it should be checked if it is possible to disconnect the parallel device from the public line and connect it as internal subscriber to the PBX or the device must be set to not react to incoming calls. For further information the manufacturer of the device should be contacted.

How can I verify that the PBX is correctly signaling busy?

The PBX's call-distribution should be set to signal more than one subscriber, busy-on-busy is enabled or set to "from 1st connection on" (depending on the PBX). For the first incoming call all the configured subscribers ring and one of them takes the call. For the second incoming call no additional subscribers should ring. If they do the PBX's configuration should be checked. If the caller gets a ring-tone but the PBX's subscribers don't ring, one of the above described examples applies. If the caller gets the busy-tone, the function is ok.

In order to select several subscribers in the PBX's call-distribution settings, a group has to be generated with the respective subscribers as members. The group can then be selected in the call-distribution settings.

Storage specifications (USB stick, SD-card)

USB-stick

SD-card

Info for using 16GB SD-cards:

Please note that the device's operating speed can get reduced due to the larger storage size.

In this case it is recommend to format the SD-card to 4GB with a PC.

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.

Current ICT systems:

• COMpact 4000
• COMpact 5000 (R)
• COMpact 5200 (R)
• COMpact 5500R
• COMmander 6000 (R) (RX)

Note the following points in the configuration:

• Under public networks, VoIP, provider, configure the appropriate provider. The default value 5060 must be set as 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.

Early generations of hybrid telephone systems:

• COMpact 3000 analogue, ISDN and VoIP
• COMpact 5010/5020 VoIP
• COMmander Basic.2 / Basic.2 19“
• COMmander Business / Business 19“

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.

Important information about "Emergency calls"

As installer and operator (customer) of telecommunication equipment you are legally obligated (Telekommunikations­gesetz § 108) to ensure the unhindered and prioritized routing of emergency calls (numbers 110 and 112).

Therefore please note the following essentials:

1. In order to be able to make emergency calls without any special knowledge at any time, the PBX's emergency numbersmust not be deleted. Otherwise the number is called wrong or is not possible at all!
2. Furthermore the funcion "emergency call has priority" must stay enabled.
3. From firmware version 6.6B on it is no longer possible to delete the statutory emergency numbers on the Auerswald PBXs COMpact 4000/5000 and COMmander 6000/6000R/6000RX. To use internal numbers beginning with 11... the optional setting to only call emergency numbers with exchange line access number can be enabled. If this special setting is enabled instruct every user of the PBX on how to dial emergency numbers and also label the phone accordingly to not violate § 108 Telekommunikationsgesetz
4. Also check whether the number 116117 (emergency medical services) is already configured. On new installations this number must be configured as a service number. On older systems, where there are no service numbers, configure this number as emergency number also.

Note: Update your COMpact 4000/5000/5000R or COMmander 6000/R/RX to the current firmware as soon as possible and on older systems check the configured emergency numbers 110 and 112 as well as the emergency medical services 116117.

Since the annoucement before answering is only configurable for groups, the waiting field has to configured for a group. If the waiting field is configured for a single subscriber, an announcement before answering can't be configured.

Until the maximum number of call data records is exceeded or the entries are manually deleted from the call data list.
If the maximum number of call data records is exceeded, the oldest entries are overwritten.
It is not possible to define a time period after which the call data is automatically deleted.

This FAQ describes the simple first setup of Auerswald VoIP systemphones by using zero-touch configuration thus setting the phone's provider and account configuration by the PBX (basic provisioning).

Supported by the following PBXs (from version 6.6D):

• COMpact 4000
• COMpact 5000/5000R
• COMmander 6000/6000R(X)

Supported by the following IP systemphones (from version 2.6B):

• COMfortel 1400IP
• COMfortel 2600IP
• COMfortel 3600IP

Technical requirements:

• Active DHCP server on the network
• Phones are integrated into the network (e.g. by PoE Switch)
• Phones are in factory default settings
• Phones network-settings have been assigned by DHCP

Screenshot of the phone's Zero-Touch-configuration (only displayed in factory default):

Procedure:

1. Create a VoIP-subscriber
2. Grant access authorisation to the provisioning file (standard.xml) for the subscriber:

Note:

The Phone language can be set in the pbx:

A static IP address of http://192.168.1.111 is preset in the delivery state. The access data:
User name: admin
Password: admin
The current IP address can be queried on an ISDN telephone using the code ##8*941#.

The IP address is only displayed on the directly connected ISDN telephone, not on the internal S0 bus of our telephone systems.
Info: Display messages are used
COMmander Business and COMmander Basic.2 only: A replacement option is the automatic callback from the VoIP/ISDN gateway. With this callback, the IP address is then transmitted as the phone number.

Translated with www.DeepL.com/Translator (free version)

Until they are deleted as part of the automatic cleanup or manually. Automatic purging deletes the oldest messages read when a definable percentage threshold is exceeded, e.g. at 80% of the memory space allocated to the box.

Hackers always use the same method: they are looking for companies whose PBX has an integrated voicemail function (answering machine) in order to manipulate it via remote access. All PBXs that have been recently manipulated showed poor security measures such as insecure PINs. Auerswald PBXs have sufficient security mechanisms. But they have to be used!

Therefore, please follow the following recommendations to protect your Auerswald PBX against such attacks:

1. The admin PIN, the user PIN or the voice mailbox PIN can be used for the remote access. Do not make it easy for the attacker and use complex PINs (The PINs in the PBXs consist of six digits. Number sequences such as "123456" or "111111" or birthdays are NOT secure. It makes more sense to use random number sequences.
2. If possible, use the blocking functions for incoming calls (e.g. block calls from abroad).
3. It is more secure to use message forwarding via email and to disable the remote access.
4. For outgoing calls, prefixes (010…) in order to make the call cheaper are often used so that the protections of the Telekom (detection of high costs in a short time) are not effective. You can secure your PBX by using the blocking functions for outgoing calls (e.g. for calls that begin with 010).

Creating an SD card for the Auerswald PBX operating system from an SD card image in Windows
 

1. Connect an SDHC card reader to your PC. Wait for the driver to be installed.
2. Have a 4 GB SDHC card ready. We expressly recommend using a new SDHC card to avoid any hardware problems with the existing card. The card should be a high-quality card for industrial use. We recommend the following brands for this:
   Swissbit, Transcend, Cactus, Apro, Delkin Industrial, ATP
3. Upload the relevant Auerswald image file to your PC as a ZIP file.
   
   Here is the download for:
    
   
   COMpact 4000
   
   COMpact 5000
   
   COMmander 6000
   
   
   notes:
    
4. Data protection
   
   Auerswald-License
   
   Licence Information
   
   Open Source Code for GPL, LGPL and other Licences (ISO Image)
    
5. Installing the USB Image Tool program
   
   You need the "USB Image Tool" program from Heise website:
   
   https://www.heise.de/download/product/usb-image-tool-83646
   
   Extract the program to a suitable folder on your hard disk (e.g. c:\USBImageTool)
    
6. Run the program
   
   Open the folder and right-click on USB Image Tool.exe and select "Run as administrator". Select "Device Mode" at the top left. Insert the 4GB SDHC card in the card reader and click Rescan

Select the card reader:

Now click Restore:

Select the previously saved image file and click Open:

Confirm the following dialogue with Yes:

 The image will now be written to the SD card. Wait until the green progress bar reaches 100%.

Remove the SD card. Switch the write-protect switch on the SD card to the lock position: Lock

You can now use the card in the PBX.

Preparations

Preparing the PBX for Remote Access

• Activate "Enable dealer access via internet" in "Settings -> Remote Configuration" on the PBX.
• If using method 2 you also have to define a remote switching number as well as an external PIN.

Registering the PBX in ARA

• Go to "Registrierte TK-Anlagen" (registered PBXs)
• Press the "+"-symbol to register a new PBX.
• Enter at least the serial number, a name and the type of PBX of which you want to access.

Activating remote access

Method 1: Activation by any internal phone

• Tell your customer to dial the following sequence on any internal phone:  ##8 Admin-PIN | Subadmin-PIN | Benutzer-PIN * 91 # (example: ##8 471208* 91 #)
• Click the refresh- (next to the "+"-symbol) and then the "Verbinden" (connect)-button in ARA.

Method 2: Activation by the dealer from a distance

• Dial the previously configured remote switching number from any external phone.
• After the switching tone enter the following sequence: ##8 external PIN * 91 # (example: ##8 471108* 91 #)
• Click the refresh- (next to the "+"-symbol) and then the "Verbinden" (connect)-button in ARA.

Data privacy

Auerswald takes the protection of personal data very seriously. Please read the internet privacy statement and the general terms and conditions.

Extension possibilities (point system)

The maximum number of individual modules can be calculated using the following table. Each module has a value and can be used in the COMmander 6000 at a defined frequency. The sum of all values must not exceed the maximum value of 188.

Example:

COMmander 6000 with 2x COMmander 8S0 module (2*16 points = 32 points) and 1x COMmander VMF module (16 points).

With this extension 32+16=48 points are achieved. 140 points can still be used. Here, however, the max. module extension of 5 modules should be considered additionally.

The following SD cards were tested and released for the COMmander VMF module: