Avaya R300 用户手册
DEFINITY Enterprise Communication Server Release 9
Getting Started with the Avaya R300 Remote Office Communicator
Getting Started with the Avaya R300 Remote Office Communicator
Issue 1
November 2000
Maintaining and Troubleshooting the Avaya R300
90
Troubleshooting
6
■
If endpoint being tested is in TTI mode, refer to section TTI Endpoint Not
Registered with DEFINTIY.
Registered with DEFINTIY.
■
If endpoint being tested is in Named mode, refer to section Named Endpoint Not
Registered with DEFINITY.
Registered with DEFINITY.
TTI endpoint not registered with DEFINITY
If the TTI endpoint you are testing is not registered with DEFINITY, do the following:
■
Verify that registration attempts are being made. Enter the diagnostic prompt, and
type “roRAS rasdebug.” Every 30 seconds you should see messages printing out
indicating that registration attempts are being made. If you do not see these
messages, registration attempts are not being made. One possible source of this
problem would be if the endpoint being tested is a digital (DCP) phone, and the
phone is not communicating successfully with the combo blade. Try a different
phone. If still unsuccessful, reset the Avaya R300.
type “roRAS rasdebug.” Every 30 seconds you should see messages printing out
indicating that registration attempts are being made. If you do not see these
messages, registration attempts are not being made. One possible source of this
problem would be if the endpoint being tested is a digital (DCP) phone, and the
phone is not communicating successfully with the combo blade. Try a different
phone. If still unsuccessful, reset the Avaya R300.
■
Verify that TTI is enabled on the DEFINITY. TTI is enabled on page 2 of the
Change System-Parameters Features screen.
Change System-Parameters Features screen.
Named endpoint not registered with DEFINITY
If the Named endpoint being tested is not registered with DEFINITY, do the following:
■
Verify that registration attempts are being made. Enter the diagnostic prompt, and
type “roRAS rasdebug.” Every 30 seconds you should see messages printing out
indicating that registration attempts are being made. If you do not see these
messages, registration attempts are not being made. Try a different phone. If still
unsuccessful, reset the Avaya R300.
type “roRAS rasdebug.” Every 30 seconds you should see messages printing out
indicating that registration attempts are being made. If you do not see these
messages, registration attempts are not being made. Try a different phone. If still
unsuccessful, reset the Avaya R300.
■
Verify that the extension number and password administered on the Avaya R300
match the extension number and security code administered on the DEFINITY.
match the extension number and security code administered on the DEFINITY.
■
Analyzing the “roRAS rasdebug” messages at the diagnostic prompt. You should
see registration attempts every 30 seconds. Be sure to type “roRAS rasdebug”
again when finished troubleshooting. This will turn off the debug prints to not
“clutter” the diagnostic prompt.
see registration attempts every 30 seconds. Be sure to type “roRAS rasdebug”
again when finished troubleshooting. This will turn off the debug prints to not
“clutter” the diagnostic prompt.
NOTE:
The endpoint numbers shown in registration attempts are computed as
follows:
follows:
— Analog Trunks: Port number - 1 (range is 0 to 1)
— Analog Lines: Port number + 1 (range is 2 to 3)
— DCP Lines: Port number + 3 (range is 4 to 27)