Actions

Difference between revisions of "TCIS Indication LEDs"

From Zenitel Wiki

(Power LED on the circuit board)
(LED indistors on the printed circuit board)
Line 32: Line 32:
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
==LED indistors on the printed circuit board ==
+
==LED indicators on the printed circuit board ==
 
===Power LED on the circuit board ===
 
===Power LED on the circuit board ===
 
[[File:Turbine PowerLED.png|thumb|300px|left|Power LED]]
 
[[File:Turbine PowerLED.png|thumb|300px|left|Power LED]]

Revision as of 11:37, 13 December 2019

APS.png

LEDs on Front Panel

Status LEDs

  • Bell icon lights yellow when a call is placed and ringing
  • Talk icon lights green when a call is active and in conversation
  • Door icon lights red when the door is unlocked or relay is active
TCIS Indications 1.PNG



Talk Icon: Flashing at 1 second intervals:
Station has no connection to the server.

Possible reasons:

  • No connection to Ethernet
  • Wrong server IP address configured
  • Invalid IP address
  • No default gateway address or wrong gateway configured
TCIS Indications 2.PNG



Talk Icon: Flashing at 5 second intervals:
Station has TCP connection to the server, but fail to register.

Reason:

  • Station has not been programmed in AlphaPro
TCIS Indications 3.PNG


LED indicators on the printed circuit board

Power LED on the circuit board

Power LED


  • Steady blue light: The station receives power

Registration status LEDs on the circuit board

TCIS Board Indications 1.png


  • Flashing 2 red + 1 green: Station has no connection to the server.
  • Flashing 1 red + 2 green: Station has TCP connection to the server, but fail to register.
  • Flashing 3 green: Station connected and registered in the server.

Ethernet Activity & Speed LEDs

TCIS Board Indications 2.png


Green LED

  • Steady light: Ethernet connection OK
  • Flashing: Ethernet data traffic
  • No light: No Ethernet connection

Yellow LED

  • Steady light: 100 Mbit Ethernet connection
  • No light: 10 Mbit Ethernet connection