Technical data

Important Information
5
Proper Use
Important: Auerswald products are not designed, manufactured, or
intended for use or resale in environments requiring fail-safe performance,
such as in the operation of life-support systems and/or nuclear facilities.
Use or sale of our products for these purposes is only allowed with prior
written permission by Auerswald for each individual incident.
Important: Improper use may cause, for example, functional restrictions or
interference, the destruction of the device or, in a worst case scenario, per-
sonal injury.
씮 If you are still not sure of the intended use of the product after reading
the following section, please contact your vendor.
The COMfortel VoIP 2500 AB is a VoIP system telephone. The device is
designed to be integrated in a local network (LAN) as a VoIP end device on one
of the following Auerswald PBXs:

COMmander Basic.2 (19")

COMmander Business (19")

COMpact 5010 VoIP

COMpact 5020 VoIP
Important: To support internal IP telephony, the PBX needs firmware ver-
sion 3.0.
Note: This device is not designed to be connected to a PBX from another
manufacturer.
The system telephone is not cordless and is intended for use in closed, dry
rooms.
The system telephone is different from “normal telephones” connected to PBXs
in that it is especially easy to use, among other things. Most of the functions
available on the PBXs such as internal and external calls, call protection and call
forwarding can be operated over the display or by simply pressing previously
programmed buttons. In addition, the PBX system telephone supports offered
functions for telephone switch boards (for example, the Waiting Field) and var-
ious telephone number lists (for example, the telephone book or call list).
The system telephone can be configured either using the menu on the tele-
phone display or via the configuration manager that is accessible via the web
server integrated in the telephone. The required PC is connected either directly
to an Ethernet port on the telephone (see Fig. 6 on page 20) or must be in the
same network.