Panasonic KX-TDA50 Feature Manual page 252

13.1.15 Private Network Features—NDSS (Network Direct Station Selection)
The PLMPR/PMPR/PSMPR software file version of all PBXs in the network must be 2.0xxx or later.
The KX-TDA6920, KX-TDA0920, or KX-TDA5920 SD Memory Card for Software Upgrade to Enhanced
Version must be installed in all PBXs that will monitor extensions or have extensions monitored.
If using an IP-GW4E (KX-TDA0484) or IP-GW4 (KX-TDA5480) card, the firmware (not LPR) of the card
must be version 1.2 or later. If using a PRI23 card (KX-TDA0290), the LPR software of the card must be
version 1.009 or later.
•
All PBXs in the network must be KX-TDA series, KX-TDE series, or KX-NCP series PBXs. For information
on the hardware requirements for KX-TDE/KX-NCP series PBXs that will monitor extensions or have
extensions monitored, refer to the corresponding Feature Manual.
•
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.
6.5 [4-1-4] Wired Extension—Flexible Button
→
Type
→
Dial (for NDSS)
6.13 [4-2-3] Portable Station—Flexible Button
→
Type
→
Dial (for NDSS)
6.18 [4-3] DSS Console
→
Type
→
Dial (for NDSS)
•
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.
4.11 [2-7-1] Class of Service—COS Settings—Extension Feature—
[511] Manager Assignment
•
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.
11.2 [9-2] Network Data Transmission—
—Data Transmission Counter
•
If it is not possible to remotely turn off transmission of extension status information using the NDSS Monitor
Release feature because of network conditions, it is possible to perform the same operation directly through
system programming at the monitored PBX.
6.8 [4-1-6] Wired Extension—NDSS Link Data - Send
6.15 [4-2-4] Portable Station—NDSS Link Data - Send
•
When using a VoIP network, if extension status information is lost by the network, in some cases an NDSS
button may not be able to display the status of the relevant extension.
•
NDSS can not be used when two PBXs are networked using the TIE Line Call by Own PBX Extension
Number feature (® 13.1.13 PRIVATE NETWORK FEATURES).
252 Feature Manual
Network Data Transmission for Centralized Operator Feature
Manager
Document Version 2010-11