Diagnostics Enabled - Avaya 3641 Administration Manual

Ip wireless handset with session initiation protocol (sip)
Table of Contents

Advertisement

Diagnostics enabled

Diagnostics is used to evaluate the overall quality of the link between the handset, AP,
and infrastructure side equipment, such as IP PBX, Avaya SVP Server, and gateways.
Unlike Site Survey, Diagnostics is used while the functional code is running, and
during a call.
When you enable Diagnostics in the Admin menu, the handset can display diagnostic
screens when it is in active mode. However, navigation among calls cannot be done as
the Nav keys are used to display diagnostic screens.
You can initiate the display of information when in a call, by pressing the Nav◄ or
Nav► key. Only one of the six diagnostic screens listed below can be shown at a time.
Pressing the Nav keys multiple times will cycle through the various diagnostics screens
and the normal off-hook (IP-PBX) display. The numeric icon at the top of the display
indicates the screen number is being displayed.
For example: The first time you press the Nav key, the icon for 1 is shown, and the first
of six diagnostics screens are displayed. The next time it you press the Nav key, the icon
for 2 is displayed and the next of six diagnostics screens are displayed. The counters will
be cycled through in this fashion until there are no more counters to be displayed. After
all the diagnostics screens have been displayed, the screen returns to the normal off-
hook IP-PBX screen.
The text portion of each debug display is read from the language translation file, and
therefore may be translated to the language the phone would otherwise use. The
examples in this document reflect the debug displays as shown in English.
The debug displays refresh once per second, although the information displayed may
take longer to update.
Unless otherwise noted, all numbers are displayed as 16-bit unsigned integers, which
will wrap from 65535 to 0.
The information provided by Diagnostics includes:
Diagnostic display #1:
MissedRcvCnt: The number of 10 ms audio frames for which audio was not present
when the phone tried to play it. The phone therefore used its ClearTalk algorithm to
fill in the missing audio. Note this is NOT the same as the missed audio payloads
reported in the Syslog audio statistics messages.
86
Avaya 3641/3645/6120/6140 IP Wireless Handset SIP Administration Guide
1........
MissedRcvCnt 00075
MissedXmtCnt 00024
RxRetryCount 00041
TxRetryCount 00142
June 2012

Advertisement

Table of Contents
loading

This manual is also suitable for:

364561206140

Table of Contents