Symptoms:
Facts:
Causes: Attendant consoles are NOT standalone devices, but must be associated with an existing telephone. An attendant console counts as one device against the total devices on the system, but you may have one for each phone if you wish.
Attendant Consoles must be connected on the SAME LAN SEGMENT as the telephone device they are associated with. Preferably, they connect directly to the telephone and are not in another room, although this is possible for monitoring purposes.
Attendant console must be both ONLINE and associated with an existing working telephone before it will work, as seen in NetSet Device Configuration, Adjunct / Attendant Console Modify and Status
Fixes: Ensure that Auto Discover Adjuncts / Attendant Consoles is enabled when installing a new one. Turn auto discover OFF after device has been added. By default, all existing telephone extensions will be automatically programmed to buttons on the DSS.
INSTRUCTIONS FOR INSTALLING REMOTELY AS AN IP-BASED DSS/BLF:
[ ] You must first install the device on the SAME SUBNET as the NCP, and auto discover it. It will automatically associate with the lowest numbered extension on the system.
[ ] After it is up and running on the same subnet as the NCP, use NetSet IP Settings button to program the IP information that it will be using on the REMOTE network. Use an IP address, subnet, and gateway for the FAR END network where the unit will reside. Put this information in the Manually Assigned Settings, and click “OK”
NOTE: As of R4.1 software release for the SuperStack 3 NBX and NBX 100, the Attendant Console now supports the mapping of analog phones to the console.
For odd problems such as lights not lighting properly, or staying on, this is almost always due to network multicast issues on the customer's switches or routers. To verify this, connect the Console, associated telephone, and a test phone to a small hub connected directly to the NCP uplink port, and disconnect the NBX from the customer's network temporarily. See if the problem is resolved. May require a reboot of the NBX after connecting all devices to the small test hub and removing NBX from customer network. If the problem persists, it is definitely NOT the customer's network switches or a multicast issue. Ensure power adapter is snug.
— David Gonzalez 2021/04/13 10:57