Avaya 1000 Installation And Commissioning Manual page 196

Maintenance and diagnostics
When a login is attempted and one of the messages provided in
troubleshooting on page 196 through
appears on the telephone display, there can be more than one reason.
Table 33: Normal Operation troubleshooting
Message
Local Mode
Local Mode Server
Unreachable (1)
Local Mode Server
Unreachable (2)
Local Mode Invalid
ID (1)
Local Mode Invalid
ID (2)
Branch Office Installation and Commissioning
196
Table 35: Branch User Config troubleshooting
Probable Cause
Test Local mode
Incorrect Primary or Alternate
NCS IP address configured.
Primary or Alternate NCS IP
address unreachable from this
endpoint.
NCS port number is not
properly configured.
NCS is down.
Link to NCS is down.
Main office TPS is
unreachable from the MG
1000B TPS.
Main office TPS is down.
Link to main office TPS is
down.
Main office Call Server is
down.
Main office node is not
registered as a SIP or H.323
endpoint to the NCS.
Branch User ID endpoint is not
in NCS database.
Incorrect Branch User ID
configured.
Branch User ID not found in
any equipped TN.
Incorrect Branch User ID
configured.
Comments? infodev@avaya.com
Table 33: Normal Operation
Actions
Press Services key (key with Globe icon), and select
Resume Normal Mode. Use the STAT c u
command in LD 32 to show the reason why the
Branch User stays in Local Mode.
Correct Primary or Alternate NCS IP address.
Check network configuration and update as required.
Correct main office and MG 1000B NCS port
numbers.
Restore NCS.
Possible additional action required. The Branch
office is not registered with the NCS; Check virtual
trunks configuration, H.323 ID for each server and/or
NCS configuration.
Check network configuration, and update as
required.
Restore main office Signaling Server.
Restore Link to main office TPS.
Restore main office Call Server.
Register the main office node to the NCS.
Check NRS database and update as required.
Correct Branch User ID configuration in Branch
Office TN.
Check main office Branch User configuration, and
update as required.
Correct Branch User ID configuration in Branch
Office TN.
on page 198
June 2014