Panasonic KX-TDA50 manual Hardware Requirements

13.1.15Private Network Features—NDSS (Network Direct Station Selection)

•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

•Hardware Requirements:

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.17[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—COSSettings—Extension Feature— Manager

[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

Document Version 2008-11 Feature Manual

249