Logging And Tracing; Lan Port Mirroring; Tracing Capabilities Within The Phone; Basic Troubleshooting - Siemens OpenStage Asterisk Installation And Maintenance Manual

Logging and Tracing

OpenStage phones are perfect. But if something should go wrong anyhow, the customer
service needs tools to focus on the problem. Service effort is needed, but should be
minimized. Therefore, OpenStage phones provide plenty of tools and options to find the
cause of a problem quickly, even if it is not located at the phone.

LAN Port Mirroring

Every OpenStage phone has a built-in Ethernet switch. One of the ports is used to connect
the phone to the local network. The other port is intended for connecting a PC, thus allowing
network connectivity for both devices with only one wire from the desk.
In addition, the PC port enables network monitoring which might be useful for development
and error tracing. For this purpose, the PC port must be configured as a mirror for the LAN
port by setting PC port mode to "mirror" (see [3]). If configured this way, the complete
traffic of the LAN port will be passed through to the PC port, just like with a simple network
hub. Now, a network tracing tool on the PC can trace all IP traffic, like SIP over UDP, or XML
over HTTP, for instance.

Tracing Capabilities within the Phone

OpenStage phones provide strong support for system integration, testing, and
troubleshooting. Besides the Administration Guide [3], the tracing capabilities of the phone
are described in [5].

Basic Troubleshooting

For tracking network issues, the phone can execute ping and traceroute tests; these can be
controlled and viewed online using the WBM.
For elementary troubleshooting, the phone provides an overview about basic issues in the
user menu. The admin can ask the user to read that basic information to get a first hint
about the possible causes of an issue:
Problem Description
Network Problem No network connection
Not Initialised Waiting for data
Unable to use LAN 802.1x error
Unable to use LAN Physical connection missing
Unable to Register Server timeout
Unable to Register Server failed
Unable to Register Authentication failed
Unable to Register No number configured
Unable to Register No server configured
Unable to Register No registrar configured
Unable to Register No DNS domain configured
Unable to Register Rejected by server
Unable to Register No phone IP address set
Survivability Backup route active
Survivability Backup not configured
Survivability Backup timeout
Survivability Backup authentication failed
Open Communications Principles and Best Practices
Error code
LI1
I1
LX1
LP1
RT2
RF2
RA2
RN2
RS2
RG2
RD2
RR2
RI2
B8
RS8
RT8
RA8
19/03/2012, page 14