•
If no other PBXs are monitoring the selected extension, the monitored PBX stops transmitting status
information for that extension.
•
The monitor PBX stops receiving status information for the selected extension. All NDSS buttons for
that extension stop displaying status information.
However, the related information is not deleted from the Network Monitor Extensions Table. Therefore, if
an extension user at a monitor PBX subsequently goes off-hook and presses the NDSS button for that
extension, monitoring will be reactivated. To completely remove monitoring of an extension, the registration
data must also be deleted from the Network Monitor Extensions Table at each monitor PBX.
The monitor destination of each NDSS button is determined by the registration information for a particular
index number in this table. Therefore, if the registration information for an index number is changed (for
example, the Network Extension Number assigned to Index No. 001 in the example above is changed from
"2001" to "4002"), any NDSS buttons that have been set for that extension will automatically point to the
new monitor destination.
Conditions
•
KX-NSN002 (Activation Key for QSIG Network) is required for each Master unit that will monitor extensions
or have extensions monitored.
A separate activation key is required for non-KX-NS series PBXs. For details, refer to the corresponding
Feature Guide.
•
NDSS buttons will not function on networks using Common Extension Numbering for 2 PBXs, or Common
Extension Numbering for Multiple PBXs.
•
All PBXs in the network must be KX-NS series, KX-NCP series, KX-TDE series, or KX-TDA series PBXs.
For information on the hardware requirements for non-KX-NS series PBXs that will monitor extensions or
have extensions monitored, refer to the corresponding Feature Guide.
•
Each of Network PBX IDs 1-8 can only be assigned to one PBX within a network. Assigning the same
Network PBX ID to two PBXs will cause network data transmission problems.
•
It is only possible to assign NDSS buttons for extensions that have been previously registered in the
Network Monitor Extensions Table.
12.1.4 PBX Configuration—[4-1-4] Extension—Wired Extension—Flexible Button
®
®
12.2.3 PBX Configuration—[4-2-3] Extension—Portable Station—Flexible Button
®
®
•
Extensions connected to one PBX can monitor a maximum of 250 extensions at other PBXs. One extension
can be monitored by multiple extensions at multiple PBXs.
•
To reduce NDSS data traffic, it is recommended that 8 or less extensions in a single Incoming Call
Distribution Group be monitored.
•
Activation of an NDSS button is only required the first time that a button for a newly registered extension
is created. Once an NDSS button has been activated by being pressed the first time, any further NDSS
buttons for the same monitored extension will automatically display the extension status without needing
to be activated.
•
To use the NDSS Monitor Release feature, an extension must be assigned as a manager.
®
10.7.1 PBX Configuration—[2-7-1] System—Class of Service—COS Settings—Manager—
•
A maximum of two ports of each BRI card can be assigned to transmit extension status information
("ON").
•
Through system programming, it is possible to assign a maximum number of "hops" (transfers between
PBXs) that extension status information can travel. Each time a piece of extension status information is
forwarded to another PBX, its counter is increased by one. When this counter reaches the assigned
maximum, the data is discarded. This is used to prevent data from circling unnecessarily around the
network.
Feature Guide
453
4.3.5 QSIG Enhanced Features
Summary of Contents for KX-NS300
Page 14: ...14 Feature Guide Table of Contents ...
Page 15: ...Section 1 For Your Safety Feature Guide 15 ...
Page 18: ...18 Feature Guide 1 1 1 For Your Safety ...
Page 19: ...Section 2 Call Handling Features Feature Guide 19 ...
Page 107: ...User Manual References 1 2 1 Basic Calling Feature Guide 107 2 5 4 Trunk Call Features ...
Page 193: ...User Manual References 1 4 2 Holding a Call Feature Guide 193 2 13 1 Call Hold ...
Page 324: ...324 Feature Guide 2 30 2 Outgoing Message OGM ...
Page 325: ...Section 3 Unified Messaging System Feature Guide 325 ...
Page 375: ...Section 4 Network Features Feature Guide 375 ...
Page 464: ...464 Feature Guide 4 3 6 Network ICD Group ...
Page 465: ...Section 5 System Configuration and Administration Features Feature Guide 465 ...
Page 560: ...560 Feature Guide 5 6 7 PING Confirmation ...
Page 561: ...Section 6 Appendix Feature Guide 561 ...
Page 578: ...578 Feature Guide 6 5 2 PFMPR Software File Version 004 2xxxx ...
Page 579: ...Feature Guide 579 Notes ...