Auerswald COMmander Basic.2, Installation And Commissioning Instructions

Page: 71 / 84

Service and Maintenance
71
The overview on page Administration Monitoring
Status VoIP accounts indicates whether a VoIP account
configured on the PBX has been successfully registered
with the VoIP provider. See also
Page 74 .
Service data
If the PBX ever displays a malfunction, various reports
can be recorded. These reports can then be forwarded to
technical departments (Service, Development) to help
find the cause of the malfunction.
To make control and administrative information about the
connections on the PBX, e.g.,visible, a D-channel log is
started. The type of error and perhaps the cause can be
determined by looking at the list of transmitted informa-
tion. See also
Page 80 .
Log-in tracking is logged in the configuration manager. It
can be viewed on the page Administration
Log files
Log in tracking.
If the PBX exhibits a malfunction which is not caused by
incorrect operation or external influences, a PBX unit
image can be used to diagnose the malfunction. See also
Page 80 .
To log the Ethernet data stream, a network protocol in
PCAP format can be recorded. This protocol can then be
evaluated (e.g.,with Wireshark/Ethereal), for instance, to
determine the cause any malfunctions which may have
occurred. See also
Page 80 .
Network Diagnosis
By sending a ping to a remote host (e.g. computer, PBX)
in the network, you can check whether this host is reach-
able and how long the routing takes (there and back). See
also
Page 80 .
Querying Firmware Versions/Serial Numbers
Requirements
– Opened configuration manager (with an existing con-
nection to the PBX web server)
Steps to Take
1.
Click the Auerswald logo at the top left in the
configuration manager.
This opens a dialogue window. Besides the PBX
data
(e. g. firmware version, serial numbers) also
the data of the operator and the dealer are
displayed.
LED Functions on the Mainboard
Version
Serial numbers
“Status” LED Menu prompt (after pressing the “Default”
and the “Alternate” buttons)
Red (blinks 50/50 ms) Pressing the “Default” button has been
detected.
Red (blinks 0.5/0.5 s) “Default” button has been pressed long
enough.
Orange (blinks 50/
50 ms) Pressing the “Alternate” button has been
detected.
Orange (blinks 0.5/
0.5 s) “Alternate” button has been pressed long
enough.
“Status” LED “Power” LED PBX status (after restart)
Red Red The boot partition is being tested.
Orange Red The kernel is being loaded from the
boot partition.
Green Red The kernel is being initialised.
Green Orange The kernel modules are being
loaded.
Green Orange
(blinking) The database is being initialised/
converted.
Green Green The PBX is ready for operation.
“Status” LED “Power” LED PBX status (errors)
Red (blinks 1/
1 s) Red No valid boot partition was found.
System is paused.
Orange (blinks
1/1 s) Red No consistent kernel data has been
found on either boot partition.
System is paused.
“Status” LED “Power” LED PBX status (after restart)