Open Communications Principles and Best Practices 24/09/2010, page 14
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 mini-
mized. 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 traf-
fic 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 troubleshoot-
ing. 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 Error code
Network Problem No network connection LI1
Not Initialised Waiting for data I1
Unable to use LAN 802.1x error LX1
Unable to use LAN Physical connection missing
LP1
Unable to Register Server timeout RT2
Unable to Register Server failed RF2
Unable to Register Authentication failed RA2
Unable to Register No number configured RN2
Unable to Register No server configured RS2
Unable to Register No registrar configured RG2
Unable to Register No DNS domain configured RD2
Unable to Register Rejected by server RR2
Unable to Register No phone IP address set RI2
Survivability Backup route active B8
Survivability Backup not configured RS8
Survivability Backup timeout RT8
Survivability Backup authentication failed RA8