1.13 P

1.13.1 Paging

Description

An extension user can make a voice announcement to several people at once.

The announcement is heard through the built-in speakers of proprietary telephones (PTs) and/or external pagers (loudspeakers) which belong to a paging group. Up to two external pagers can be connected.

The paged person can answer the page from a nearby telephone.

It is possible to page with a call on hold in order to transfer the call.

Paging Deny It is possible to deny being paged on an extension basis.

Paging Group

Each paging group consists of extension user groups and external pagers. One extension user group or external pager can belong to several paging groups. (→ 1.7.1 GROUP FEATURES) [Example] [Programming Example] : Constituent *1: → 2.10.9 [3-4] Paging Group  or   2.10.10 [3-4] Paging Group—All Setting → [640] Extension User Groups of a Paging Group *2: → 2.10.11 [3-4] Paging Group—External Pager → [641] External Pagers of a Paging Group

Conditions

Programming References

•	PC Programming Manual
•	2.9.9 [2-6-1] Numbering Plan—Main—Features
•	→ Group Paging
•	→ Group Paging Answer
•	→ Paging Deny Set / Cancel
•	2.9.18 [2-9] System Options
•	→ Option 1—PT Fwd / DND—Paging to DND Extension
•	→ Option 3—Confirmation Tone—Tone 2 : Paged / Automatic Answer
•	2.9.20 [2-11-1] Audio Gain—Paging/MOH
•	→ Paging—EPG 1 (External Pager 1)
•	→ Paging—EPG 2 (External Pager 2)
•	→ Paging—Paging Level from PT Speaker
•	2.10.9 [3-4] Paging Group
•	2.10.10 [3-4] Paging Group—All Setting
•	2.10.11 [3-4] Paging Group—External Pager
•	2.11.1 [4-1-1] Wired Extension—Extension Settings—Option 6—Paging Deny
•	PT Programming Manual
•	[640] Extension User Groups of a Paging Group
•	[641] External Pagers of a Paging Group

Feature Manual References

Operating Manual References

1.13.2 Paralleled Telephone

Description

By connecting telephones in parallel, you can increase the number of telephones connected to the PBX without adding additional extension cards.

Both wired and wireless telephones can be connected in parallel. Single line telephones (SLTs), analog proprietary telephones (APTs), and digital proprietary telephones (DPTs) can be connected to other telephones or connectors, allowing up to three telephones to be connected to the PBX through just one extension port. Additionally, portable stations (PSs) can be linked to other telephones wirelessly and used as "paired" extensions.

The different type of parallel connections are described below.

Features Descriptions Connections Parallel Mode Allows an SLT to be connected to an APT or DPT which is connected to a Super Hybrid port of the PBX. When parallel mode is enabled, the two telephones function as follows: • Both share the extension number of the telephone connected directly to the PBX (main telephone). • Either telephone can make or answer a call. EXtra Device Port (XDP) Mode Allows an SLT to be connected to a DPT which is connected to a Super Hybrid port of the PBX. Unlike parallel mode, XDP mode allows each telephone to act as an independent extension with its own extension number. (→ 1.5.7 Extension Port Configuration) Digital XDP   Allows a DPT to be connected to another DPT which is connected to a DPT port or a Super Hybrid port of the PBX. The DPT that is connected directly to the PBX is called the “master DPT”, and the DPT connected to the master DPT is called the “slave DPT”. Similar to XDP mode, each DPT acts as a independent extension with its own extension number. If a master DPT is connected to the PBX by a Super Hybrid port (not a DPT port), a third telephone (SLT) can also be in parallel or XDP mode with the master DPT. Digital XDP connection allows the number of DPTs that the PBX supports to increase. Wireless XDP Parallel Mode For information on this type of parallel connection, refer to the Wireless XDP Parallel mode feature. (→ 1.20.5 Wireless XDP Parallel Mode).

Conditions

Installation Manual References

Programming References

•	PC Programming Manual
•	2.8.21 [1-1] Slot—Port Property - Extension Port
•	→ XDP Mode
•	→ Parallel Telephone Ringing
•	2.9.9 [2-6-1] Numbering Plan—Main—Features—Parallel Telephone (Ring) Mode Set / Cancel
•	PT Programming Manual
•	[600] EXtra Device Port (XDP) Mode

Operating Manual References

1.13.3 Password Security

Description

Programming References

Feature Manual References

1.13.4 Pause Insertion

Description

Conditions

Programming References

•	PC Programming Manual
•	2.8.27 [1-1] Slot—Port Property - LCO Port—Pause Time
•	2.8.33 [1-1] Slot—Port Property - T1 Port—Pause Time
•	2.9.5 [2-3] Timers & Counters—Miscellaneous—During Conversation—Pause Signal Time
•	2.13.4 [6-4] Second Dial Tone
•	PT Programming Manual
•	[416] LCOT Pause Time

1.13.5 PC Console/PC Phone

Description

CTI First Party Call Control can be conducted by connecting a PC with a KX-T7633 or KX-T7636 DPT (equipped with USB module KX-T7601) through USB ports. By using the KX-TDA0350 PC Phone or KX-TDA0300 PC Console CTI application, users can enjoy many of the KX-TDE series PBX features while utilizing the benefits of a CTI solution. PC Console gives users access to certain administrative level features that are not available with PC Phone. The extensions that use PC Console must be assigned through system programming. Along with many KX-TDE PBX features, PC Phone and PC Console offer many specific features, including the following:

• Phone Book: A list of telephone numbers including detailed information pertaining to each entry. This feature allows the user to make calls and send e-mails to each entry. • Outlook Integration: The Microsoft Outlook Address Book can be integrated to be used with the PC Phone or PC Console. • Pop-up Screen: An image containing information about the caller appears when a call is received. • Voice Memo: Conversations are recorded at any time and can be saved, sent by e-mail, etc. • Text Memo: A user can type a short message during a conversation which can be saved, sent by e-mail, etc.

[For PC Phone Only]

• TAM (Telephone Answering Machine): If a call is not answered within a preprogrammed time, callers can leave a message after hearing a greeting message. • Message: TAM messages are played back and/or automatically transferred by phone or by e-mail.

[For PC Console Only]

• Incoming Group Screen: Names, extension numbers, and the status (e.g., busy) of each extension can be monitored on a single screen. Calls can also be made and received on this screen.

Conditions

•	Hardware Requirements: KX-T7633 or KX-T7636 DPT and USB Module KX-T7601

•	System Requirements:
	– Microsoft Windows XP or Windows Vista – Internet Explorer 5.0 or later
	Minimum Requirements:
	– CPU: Intel Pentium II 350 MHz – RAM: 64 MB – HDD: 100 MB available space (when installing) – Display: XGA (1024*768) – Peripheral Devices: Sound Board (for recording and replaying features), Speaker (for listening to voice messages), USB port, CD-ROM drive

Installation Manual References

Programming References

•	PC Programming Manual
•	2.8.21 [1-1] Slot—Port Property - Extension Port
•	→ DPT Type—Type
•	→ DPT Type—Location No.
•	PT Programming Manual
•	[601] Terminal Device Assignment

Feature Manual References

1.13.6 PC Programming

Description

Conditions

Installation Manual References

Programming References

•	PC Programming Manual
•	2.18.1 [11-1] Main
•	→ RS-232C—External Modem Command—Automatic Initialization
•	→ RS-232C—External Modem Command—Manual Initialization 1–Manual Initialization 5
•	→ Remote
•	→ Password—System Password - PC Programming—User Level
•	→ Password—System Password - PC Programming—Administrator Level
•	→ Password—System Password - PC Programming—Installer Level
•	PT Programming Manual
•	[801] External Modem Control
•	[810] Remote Programming
•	[811] Modem Floating Extension Number
•	[812] ISDN Remote Floating Extension Number

Feature Manual References

1.13.7 PDN (Primary Directory Number)/SDN (Secondary Directory Number) Extension

Description

Primary Directory Number (PDN) buttons and Secondary Directory Number (SDN) buttons are ideal for use between bosses and secretaries. When a call (intercom or CO) arrives at a PDN button on the boss's extension, the call will ring and the LED of the SDN button will flash at the secretary’s extension as well, indicating that an incoming call is arriving at the boss’s extension. In addition, caller information (e.g., Caller ID) of the incoming call will appear on the secretary’s extension. The secretary can answer the call for the boss by simply pressing the SDN button. Delayed ringing can be set for a PDN or SDN button.

A secretary can hold a call answered on the SDN button, and the boss can retrieve the held call simply by pressing the PDN button, like when answering a call with an S-CO button. In addition, a secretary can transfer calls from an SDN button or other button (e.g., S-CO button) to the boss’s extension with a simple operation, like when using a DSS button.

An extension can have several SDN buttons, each registered to a different boss’s extension. However, only one SDN button can be registered for a single boss at each extension. An extension can have up to eight PDN buttons. PDN buttons can simplify the use of an extension because both intercom and CO line calls can be made and received at a PDN button.

Making Calls with an SDN Button

When Standard SDN Key mode is assigned to an SDN extension (secretary) through COS programming, SDN extensions (secretaries) can make calls for PDN extensions (bosses) on the SDN button. For example, a boss can ask a secretary to make a call and put the call on hold, after which, the boss can retrieve the held call.

Through COS programming, it is possible to allow an SDN extension to make calls using the COS of the PDN extension. All other settings that are available when using the Walking COS feature are also applied (→ 1.20.1 Walking COS).

SDN Direct Dial An SDN extension can call a PDN extension or transfer a call to a PDN extension using an SDN button. In this case:

– Only the PDN extension rings (i.e., other SDN extensions do not ring). – The delayed ringing and DND settings of the PDN extension are ignored.

Depending on the mode selected through COS programming, SDN Direct Dial is performed in one of two ways, as follows:

– Enhanced DSS Key mode: pressing the SDN button once. – Standard SDN Key mode: pressing the SDN button twice (a dial tone is heard the first time the SDN button is pressed).

Calls answered using the SDN button can be transferred to the PDN extension by simply pressing the SDN button once, regardless of the mode.

LED Indication

The LED patterns and the corresponding status of PDN and SDN buttons are as follows:

Light Pattern PDN Button Status SDN Button Status Off This extension is idle. The corresponding PDN extension is idle. Green on The extension is on a call using the PDN button. The extension is on a call using the SDN button. Slow green flashing A call is on hold using the PDN button. A call is on hold using the SDN button. Moderate green flashing • A call on a PDN button is on Exclusive Call Hold or consultation hold. • The PDN extension is adding a member to a conference or using the line for an Unattended Conference, on a PDN button. • A call answered using the SDN button is on Exclusive Call Hold or consultation hold. • The SDN extension is adding a member to a conference, or using the line for an Unattended Conference. Rapid green flashing An incoming call is arriving at this extension. Receiving Hold Recall or automatic callback ringing from a call answered using the SDN button. Red on A corresponding SDN extension is: • on a call. • holding the line using Exclusive Call Hold or consultation hold. • adding a member to a conference. • using the line for an Unattended Conference. • receiving Hold Recall or automatic callback ringing. The corresponding PDN extension or another corresponding SDN extension is: • on a call. • holding the line using Exclusive Call Hold or consultation hold. • adding a member to a conference. • using the line for an Unattended Conference. • receiving an incoming call directed only to the PDN extension (e.g., callback ringing). Slow red flashing A call is on hold by a corresponding SDN extension. A call is on hold by the corresponding PDN extension or another corresponding SDN extension. Rapid red flashing A call is arriving at an Incoming Call Distribution (ICD) group in Ring Distribution method that this extension is a member of. The corresponding PDN extension is receiving an incoming call.

When multiple calls are on a PDN extension, the LED pattern that appears on the corresponding SDN buttons is displayed according to the following priority:

Receiving an incoming call → holding a call → on a call → idle

For example, if a PDN extension receives an incoming call while on a call, the LEDs on the corresponding SDN extensions will show the incoming call.

However, if an SDN extension is handling a call using the SDN button (e.g., on a call, has a call on hold, etc.), the status of that call will be displayed on the SDN button, regardless of the call status of the PDN extension.

Example of a Secretary Handling Calls for Multiple Bosses

The following example shows the LED patterns of the PDN and SDN buttons of each extension and how calls can be handled.

1) A Call From 111-1111 Arrives at Ext. 101

2) The Call From 111-1111 is Answered by Ext. 103

3) The Call From 111-1111 is On Hold by Ext. 103

4) The Call Held by Ext. 103 is Answered by Ext. 101

5) A Call From 222-2222 Arrives at Ext. 101

6) A Call From 333-3333 Arrives at Ext. 102

7) The Call From 333-3333 is Answered by Ext. 103

8) The Call From 333-3333 is Transferred by Ext. 103 to Extension 102

Conditions

Programming References

•	PC Programming Manual
•	2.9.12 [2-7-1] Class of Service—COS Settings—PDN/SDN
•	2.9.17 [2-8-3] Ring Tone Patterns—Call from Others—Extension—Ring Tone Pattern Plan 1–8
•	2.9.18 [2-9] System Options—Option 4—System Wireless—SDN Delayed Ringing with LCD
•	2.11.1 [4-1-1] Wired Extension—Extension Settings—Option 9—PDN Delayed Ringing
•	2.11.5 [4-1-4] Wired Extension—Flexible Button
•	→ Type
•	→ Parameter Selection (for SDN)
•	→ Ext. No. / Floating Ext. No. (for SDN)
•	→ Optional Parameter (Ringing Tone Type Number) (for Loop CO, Single CO, Group CO, G-DN, SDN)
•	2.11.10 [4-2-1] Portable Station—Extension Settings—Option 9—PDN Delayed Ringing
•	2.11.13 [4-2-3] Portable Station—Flexible Button
•	→ Type
•	→ Parameter Selection (for SDN)
•	→ Ext. No. / Floating Ext. No. (for SDN)
•	2.11.17 [4-3] DSS Console
•	→ Type
•	→ Parameter Selection (for SDN)
•	→ Ext. No. / Floating Ext. No. (for SDN)
•	→ Optional Parameter (Ringing Tone Type Number) (for Loop CO, Single CO, Group CO, G-DN, SDN)
•	PT Programming Manual
•	None

Feature Manual References

Operating Manual References

1.13.8 Peer-to-Peer Connection

Description

Conditions

•	Peer-to-peer calls can only be made between extensions connected to the PBX through the IPCMPR card.
•	The following combinations of IP telephones are peer-to-peer compatible:
	: Available
•	The types of CODEC available for peer-to-peer calls depend on the IP telephones being used, as follows:
	The speech quality of the CODECs varies as follows: (High) G.722, G.711, G.729A (Low). When the preferred CODEC of each party differs, the call will be established using the lower CODEC. For example, if the caller prefers G.711 while the called party prefers G.729A, the call will be established using G.729A.
•	G.722 is only available for the KX-NT300 series IP-PTs and some SIP extensions that support this CODEC during peer-to-peer communication.
•	Through system programming, it is possible to assign a specific type of CODEC to be used for each extension.
•	For SIP extensions, the priority of the CODEC that will be used can be specified on a SIP extension basis.
•	For non-peer-to-peer calls via the DSP card, calls cannot be made or received when all of the card's resources are being used.

Programming References

•	2.8.15 [1-1] Slot—Port Property - Virtual IP Extension—Option—IP Codec Priority

Feature Manual References

1.13.9 PING (Packet Internet Groper) Confirmation

Description

Conditions

Programming References

1.13.10 Power Failure Restart

Description

Conditions

1.13.11 Power Failure Transfer

Description

Conditions

Installation Manual References

Programming References

1.13.12 Predialing

Description

Conditions

Operating Manual References

1.13.13 Printing Message

Description

Conditions

Programming References

•	PC Programming Manual
•	2.9.9 [2-6-1] Numbering Plan—Main—Features—Printing Message
•	2.13.2 [6-2] Hotel—Main—SMDR for External Hotel Application 2—Printing Message 1–8
•	PT Programming Manual
•	None

Feature Manual References

Operating Manual References

1.13.14 Privacy Release

Description

Conditions

Programming References

•	PC Programming Manual
•	2.9.18 [2-9] System Options—Option 1—PT Operation—Privacy Release by SCO key
•	2.11.5 [4-1-4] Wired Extension—Flexible Button—Type
•	2.11.13 [4-2-3] Portable Station—Flexible Button—Type
•	2.11.17 [4-3] DSS Console—Type
•	PT Programming Manual
•	None

Feature Manual References

Operating Manual References

1.13.15 PRIVATE NETWORK FEATURES

Description

A TIE line is a privately leased communication line between two or more PBXs, which provides cost effective communications between company members at different locations. The TIE lines can be used to call through the PBX to reach another switching system (PBX or telephone company). By using TIE lines, the PBX can support not only communications with the public network but with other company members in the private network where the PBX is included.

Interface

The following interfaces can be used to establish a private network:

Interface Network Type T1 (TIE [E & M]) Digital (64 kbps × 24 channels) PRI (QSIG) Digital (ISDN 23B+D) VoIP Internet Protocol (IP)

The available interfaces depend on the cards installed in the PBX.

Explanation

1.	TIE Line Routing Flowchart
	[Making a TIE Line Call from an Extension] [Receiving a Call through a TIE Line]
2.	Making a TIE Line Call One of the following two methods can be used to make a TIE line call.
	a) Extension Number Method (Access without PBX Code) Dial the [Extension Number] only. [Example] Explanation: To use this method, it is necessary to change the first one or two digits of extension numbers of either PBX (e.g., 10XX for PBX-1, 20XX for PBX-2) to allow calls to be routed properly. Case 1: Extension 1012 of PBX-1 dials extension number "2011". → Extension 1012 of PBX-1 is connected to extension 2011 of PBX-2. Case 2: Extension 1011 of PBX-1 dials extension number "3011". → Extension 1011 of PBX-1 is connected to extension 3011 of PBX-3. b) PBX Code Method (Access with PBX Code) Dial the [TIE Line Access Number] + [PBX Code] + [Extension Number]. → 2.9.9 [2-6-1] Numbering Plan—Main—Features—TIE Line Access → 2.16.1 [9-1] TIE Table—Own PBX Code [Example] Explanation: To use this method, it is necessary to know each PBX code in order to identify the location of an extension. Case 1: Extension 1012 of PBX-1 dials TIE line access number "7", PBX code "952", and extension number "1011". → Extension 1012 of PBX-1 is connected to extension 1011 of PBX-2. Case 2: Extension 1011 of PBX-1 dials TIE line access number "7", PBX code "953", and extension number "1011". → Extension 1011 of PBX-1 is connected to extension 1011 of PBX-3.
3.	TIE Line and CO Line Connection
	To connect the TIE line with the CO line, the following patterns are available: 1) CO Line-to-TIE Access 2) TIE-to-CO Line Access 3) CO Line-to-TIE-to-CO Line Access
	2.1 CO Line-to-TIE Access It is possible to assign an extension of another PBX as the destination of incoming CO line calls to the own PBX. It is also possible to forward calls using a virtual PS. Using this method, CO line calls received at PBX-1 are forwarded directly to the extension at PBX-2, even when using the PBX Code method. a) Incoming CO Line Call Destination Assignment [Example] Explanation: An outside caller dials "123-4567". The call is sent to extension "2011" of PBX-2 through the TIE line according to the assignment of the DID or DIL call destination of PBX-1. (→ 1.4.6 DID (Direct Inward Dialing)) → 2.17.3 [10-3] DID Table —DID Destination—Day, Lunch, Break, Night → [453] DID Destination b) FWD/Call Transfer/Intercept Routing to the TIE Line [Example] Explanation: An outside caller dials "123-4567". The call reaches the destination (extension 1011 of PBX-1), and the call is forwarded, transferred, or intercepted to extension "2011" of PBX-2 through the TIE line. 2.2 TIE-to-CO Line Access The PBX sends TIE line calls to the CO lines of another PBX through the TIE lines. a) CO Line Call through Other PBXs—by Making a TIE Line Call Method [Example] <Extension Number Method (Access without PBX Code)> Explanation: 1. Extension 1011 of PBX-1 dials the Trunk Group Access number of PBX-1 "8", trunk group number "02" (TRG2), Idle Line Access number of PBX-2 "9", and telephone number "211-4567". → 2.9.9 [2-6-1] Numbering Plan—Main—Features—Trunk Group Access 2. PBX-1 sends the call to PBX-2 through the trunk group (TRG) 2 (TIE line). 3. PBX-2 sends the call to the outside party "211-4567". <PBX Code Method (Access with PBX Code)> Explanation: 1. Extension 1011 of PBX-1 dials the TIE line access number "7", PBX code "952", Idle Line Access number of PBX-2 "9", and telephone number "211-4567"; or dials the Trunk Group Access number of PBX-1 "8", trunk group number "02" (TRG2), PBX code "952", Idle Line Access number of PBX-2 "9", and telephone number "211-4567". 2. The call is connected to the outside party "211-4567" through PBX-2 which has PBX code "952". b) CO Line Call through Other PBXs—by the ARS feature [Example] <Extension Number Method (Access without PBX Code)> Explanation: 1. Extension 1011 of PBX-1 dials the Idle Line Access number of PBX-1 "9" and telephone number "211-4567". 2. PBX-1 modifies the call (adds the Idle Line Access number of PBX-2 "9") and sends the call to PBX-2 through the TIE line (trunk group [TRG] 2) according to the ARS programming of PBX-1. 3. PBX-2 sends the call to the outside party "211-4567". <PBX Code Method (Access with PBX Code)> Explanation: 1. Extension 1011 of PBX-1 dials the Idle Line Access number of PBX-1 "9" and telephone number "211-4567". 2. PBX-1 modifies the call (adds "952" and the Idle Line Access number of PBX-2 "9") and sends the call to PBX-2 which has PBX code "952" through the TIE line (trunk group [TRG] 2) according to the ARS programming of PBX-1. 3. PBX-2 sends the call to the outside party "211-4567". c) Blocking CO line calls made through another PBX and how to override it: Whether an incoming TIE line call can make a CO line call through this PBX (i.e., PBX-2), depends on the COS that is assigned to the trunk group of this PBX, that the incoming TIE line is connected to. If the COS of the trunk group is unable to make outgoing calls by the TRS or External Call Block feature, CO line calls made through this PBX will be prohibited. To override this prohibition, an extension of PBX-1 must enter a verification code assigned to PBX-2 to change the COS temporarily. It is also possible to override the prohibition by specifying an extension at PBX-2 with the Walking COS feature, to temporarily switch to that extension's COS. → 2.9.12 [2-7-1] Class of Service—COS Settings—TRS—TRS Level—Day, Lunch, Break, Night → 2.9.13 [2-7-2] Class of Service—External Call Block → 2.10.1 [3-1-1] Trunk Group—TRG Settings—Main—COS → 2.13.3 [6-3] Verification Code → [500] Trunk Group Number [Programming Example of PBX-2] [Example] <Extension Number Method (Access Without PBX Code)> Explanation: Case 1: 1. Extension 1011 of PBX-1 dials the Trunk Group Access number of PBX-1 "8", TIE line trunk group number (TRG 2), Idle Line Access number of PBX-2 "9", and the telephone number "211-4567". 2. The call is not connected to the outside party through PBX-2 because the COS of TRG 1 (COS 3) is blocked from accessing TRG 3 of PBX-2. Case 2: 1. Extension 1012 of PBX-1 dials the Trunk Group Access number of PBX-1 "8", TIE line trunk group (TRG2), verification code entry feature number , , verification code, verification code personal identification number (PIN), Idle Line Access number of PBX-2 "9", and the telephone number "211-4567". 2. If the specified verification code applies COS 2 of PBX-2, the call is connected to the outside party through PBX-2, because COS 2 is not blocked from accessing TRG 3 of PBX-2. <PBX Code Method (Access with PBX Code)> Explanation: Case 1: 1. Extension 1011 of PBX-1 dials the TIE line access number "7", PBX code "952", Idle Line Access number of PBX-2 "9", and the telephone number "211-4567". 2. The call is not connected to the outside party through PBX-2 because the COS of TRG 1 (COS 3) is blocked from accessing TRG 3 of PBX-2. Case 2: 1. Extension 1012 of PBX-1 dials the TIE line access number "7", PBX code "952", verification code entry feature number, , verification code, verification code personal identification number (PIN), Idle Line Access number of PBX-2 "9", and the telephone number "211-4567". 2. If the specified verification code applies COS 2 of PBX-2, the call is connected to the outside party through PBX-2, because COS 2 is not blocked from accessing TRG 3 of PBX-2. d) FWD/Call Transfer/Intercept Routing to the CO Line [Example] Explanation: 1. Extension 1011 of PBX-1 dials the TIE line access number "7", PBX code "952", and extension number "1011". 2. The call reaches the destination (extension 1011 of PBX-2) through the TIE line, and the call is forwarded, transferred or intercepted to the outside party "211-4567" through the CO line. 2.3 CO Line-to-TIE-to-CO Line Access An outside caller can be connected to an outside party through the TIE line by using the DISA feature. [Example] Explanation: 1. The outside caller dials the "DISA phone number of PBX-1", Idle Line Access number of PBX-1 "9", and telephone number "1-333-123-4567". 2. PBX-1 modifies the call (adds "952" and the Idle Line Access number of PBX-2 "9") and sends the call to PBX-2 which has PBX code "952" through the TIE line (trunk group [TRG] 2) according to the ARS programming of PBX-1. 3. PBX-2 sends the modified call to the outside party "333-123-4567" according to its ARS programming.
4.	TIE Line Routing and Modification Table
	3.1 To Make a TIE Line Call The TIE Line Routing and Modification Table is referenced by the PBX to identify the CO line route when an extension user makes a TIE line call. It is necessary to make unified tables with all PBXs in the TIE line network. The routing pattern appropriate for each call is decided by the dialed number. There are two system programs for the tables: TIE Line Routing Table: used to assign the leading numbers (PBX code or extension number) and trunk group hunt sequence. → 2.16.1 [9-1] TIE Table—Leading Number TIE Modify Removed Number of Digits/Added Number: used to remove digits from and add a number to the dialed number of the TIE line call. This modification may be needed depending on the TIE line network configuration. 2.16.1 [9-1] TIE Table    → Removed Number of Digits    → Added Number    → Trunk Group [Programming Examples] Your PBX is PBX-1 and there are four PBXs in your TIE line network. To identify the CO line route as illustrated, you should make the following tables. a) Extension Number Method (Access without PBX Code) 2.9.9 [2-6-1] Numbering Plan—Main—Other PBX Extension—Dial [TIE Line Routing and Modification Table of PBX-1] Location No. Leading No. Priority 1 Priority 2 . . TRG Dial Modification TRG Dial Modification . . Removed No. of Digits Added No. Removed No. of Digits Added No. . . 01 2 1 0 . . 02 3 1 0 2 0 . . 03 4 2 0 . . : : : : : : : : : Explanation: Location 01: The hunt sequence by dialing [2XXX]: The 1st route—trunk group (TRG) 1 Sending no. to PBX-2: 2XXX Location 02: The hunt sequence by dialing [3XXX]: The 1st route—trunk group (TRG) 1 Sending no. to PBX-2: 3XXX The 2nd route—trunk group (TRG) 2 Sending no. to PBX-4: 3XXX Location 03: The hunt sequence by dialing [4XXX]: The 1st route—trunk group (TRG) 2 Sending no. to PBX-4: 4XXX b) PBX Code Method (Access with PBX Code) → 2.9.9 [2-6-1] Numbering Plan—Main—Features—TIE Line Access → 2.16.1 [9-1] TIE Table—Own PBX Code [TIE Line Routing and Modification Table of PBX-1] Location No. Leading No. Priority 1 Priority 2 . . TRG Dial Modification TRG Dial Modification . . Removed No. of Digits Added No. Removed No. of Digits Added No. . . 01 952 1 0 . . 02 953 1 0 2 3 953# . . 03 954 2 3 954# . . : : : : : : : : : Explanation: Location 01: The hunt sequence by dialing [7+PBX Code 952+XXXX]: The 1st route — trunk group (TRG) 1   Sending no. to PBX-2: 952–XXXX Location 02: The hunt sequence by dialing [7+PBX Code 953+XXXX]: The 1st route — trunk group (TRG) 1   Sending no. to PBX-2: 953–XXXX The 2nd route — trunk group (TRG) 2   Sending no. to PBX-4: 953#–XXXX Location 03: The hunt sequence by dialing [7+PBX Code 954+XXXX]: The 1st route — trunk group (TRG) 2   Sending no. to PBX-4: 954#–XXXX 3.2 To Receive a TIE Line Call a) Extension Number Method (Access without PBX Code) [Example] A TIE line call is sent to PBX-2 from PBX-1. If the number sent from PBX-1 is an extension number of PBX-2 (e.g., 2011), the call will be received at extension "2011". If not, PBX-2 checks the number in the TIE Line Routing and Modified Table of PBX-2. If the match is found in the table, the call will be modified according to the table and send to the corresponding PBX (PBX-3). The number sent from PBX-2 "3011" is an extension number of PBX-3. The call is received at extension "3011". Note When a TIE line call is sent from one PBX to another, the receiving PBX first modifies the received number according to the assignment for the CO line port: the number of digits removed, and the number added, are determined by this assignment. Then the PBX checks whether the completed number is an existing extension number at that PBX. b) PBX Code Method (Access with PBX Code) [Example] A TIE line call is sent to PBX-2 from PBX-1. If the number sent from PBX-1 has the PBX code of PBX-2 "952", the call will be received at the corresponding extension of PBX-2 (e.g., 1011of PBX-2). If not, PBX-2 checks the number in the TIE Line Routing and Modified Table of PBX-2. If the match is found in the table, the call will be modified according to the table and send to the corresponding PBX (PBX-3). The number sent from PBX-2 "953-1011" has the PBX code of PBX-3 "953". The call is received at extension "1011" of PBX-3. Note When a TIE line call is sent to a PBX from another PBX, first the PBX modifies the number sent to the PBX according to the assignment for each CO line port of the PBX: the removed number of digits from and/or added number to the number sent to the PBX is determined by the assignment. Then the PBX starts to check the number whether the number has the PBX code of the PBX.

Conditions

•	A CO line which is used for a private network should be assigned "Private" as the networking type. (→ 1.9.10 INCOMING CALL FEATURES)
•	To establish a QSIG network (→ 1.13.20 PRIVATE NETWORK FEATURES—QSIG), each ISDN (QSIG) connection in a TIE line network must have the port on one PBX assigned as a master port, and the port on the other PBX assigned as a slave port. PBXs that support this feature are the KX-TDE series PBX and KX-TDA series PBX.
	[TIE Line Network Connection Example]
•	TIE Line Call by Own PBX Extension Number TIE line calls can be made using your own PBX extension numbering scheme (1–64).
	Explanation: The PBX first searches local extensions for a matching number. If a dialed number is not found at the local PBX, the call can then be sent to a remote PBX, and the remote PBX checks the TIE Line Routing Table for a corresponding entry. Case 1: Extension 1012 of PBX-1 dials extension number "1011". → The dialed number is found at the local PBX, and extension 1012 of PBX-1 is connected to extension 1011 of PBX-1. Case 2: Extension 1012 of PBX-1 dials extension number "1033". → The dialed number is not found at the local PBX, so the call is redirected to the specified TIE Line, and extension 1012 of PBX-1 is connected to extension 1033 of PBX-2. Case 3: A public CO line call directed to extension 1033 arrives at PBX-1. → The target extension number is not found at the local PBX, so the call is redirected to the specified TIE Line, and the call is connected to extension 1033 of PBX-2.
	– The KX-NCS4910 (Activation Key for Software Upgrade to Enhanced Version) is require to use this feature. – System programming is required to enable this feature. – If a dialed number is not found at a remote PBX, the call cannot be redirected to the local PBX to search for a matching number.
•	When a TIE line call arrives at a busy extension which has disabled Call Waiting, the caller will hear a busy tone. If required, Intercept Routing can be activated.
•	The Inter-digit time can be assigned for TIE line calls. → 2.9.5 [2-3] Timers & Counters—Miscellaneous—Incoming Call Inter-digit Timer—TIE

Programming References

•	PC Programming Manual
•	2.8.30 [1-1] Slot—Port Property - PRI Port—Network Numbering Plan—Trunk Property
•	2.8.33 [1-1] Slot—Port Property - T1 Port—Trunk Property
•	2.9.5 [2-3] Timers & Counters—Miscellaneous—Incoming Call Inter-digit Timer—TIE
•	2.9.9 [2-6-1] Numbering Plan—Main—Features
•	→ Idle Line Access (Local Access)
•	→ Trunk Group Access
•	→ TIE Line Access
•	2.9.9 [2-6-1] Numbering Plan—Main—Other PBX Extension
•	2.9.12 [2-7-1] Class of Service—COS Settings—TRS—TRS Level—Day, Lunch, Break, Night
•	2.9.18 [2-9] System Options—Option 4—Private Network—TIE Call by Extension Numbering (Optional SD Card Required)
•	2.10.1 [3-1-1] Trunk Group—TRG Settings—Main—COS
•	2.16.1 [9-1] TIE Table
•	2.17.2 [10-2] DIL Table & Port Settings
•	→ DIL—Trunk Property
•	→ DIL—DIL Destination—Day, Lunch, Break, Night
•	→ DID/TIE
•	2.17.3 [10-3] DID Table —DID Destination—Day, Lunch, Break, Night
•	PT Programming Manual
•	[453] DID Destination
•	[500] Trunk Group Number

Feature Manual References

Operating Manual References

1.13.16 Private Network Features—Centralized Voice Mail

Description

Up to 8 PBXs connected in a VoIP or ISDN private network can share the services of a VPS connected to another PBX in DPT integration. This VPS can provide voice mail for extensions attached to any of the PBXs in the network, as if the VPS were connected to the local PBX. In addition, the VPS can send Message Waiting notifications to extensions at any PBX, and users can access their mailboxes directly using the Message Waiting button.

The VPS features available at extensions in a network are shown below.

No. Feature Remote VPS Local VPS 1 Automatic Configuration—Quick Setup No Yes 2 FWD to a Mailbox of the VPS Yes Yes 3 Intercept Routing to a Mailbox of the VPS Yes Yes 4 Transferring to a Mailbox of the VPS No Yes 5 Transfer Recall to a Mailbox of the VPS No Yes 6 Listening to Recorded Messages (Direct Mailbox Access) Yes Yes 7 VPS CO Line Service & Automatic Time Mode Notification Yes Yes 8 Caller's Identification Notification to the VPS Yes Yes 9 DID Number Notification to the VPS Yes Yes 10 Status Notification to the VPS Yes Yes 11 Paging by the VPS No Yes 12 Live Call Screening (LCS) No Yes 13 Two-way Recording into the VPS No Yes 14 VPS Data Control by the PBX No Yes 15 Remote FWD Setting by the VM No Yes 16 VM Menu No Yes 17 Message clear on Check Out No Yes 18 Voice message number display Yes Yes

[CO Line Call Answered by the VPS, Transferred to Extension at Other PBX (Extension Number Method)]

[Explanation] A CO line call is answered by the AA service of the VPS. The caller enters extension number 201, so the call is transferred over the private network to extension 201. If extension 201 does not answer, mailbox 201 in the VPS will answer it and play the appropriate message.

[CO Line Call to an Extension Not Answered, Forwarded to Mailbox (Extension Number Method)]

[Explanation] Extension 201 does not answer the CO line call, so the call is forwarded to the VPS, and answered by mailbox 201. If the outside caller leaves a message, the VPS sends a Message Waiting notification to the extension using Enhanced QSIG information over the private network. When forwarding the call, PBX-2 sends any received call information (Caller ID number/name, etc.) along with the VM trunk group number to use, applicable time mode, and extension number and forwarding reason of the original destination extension to PBX-1 as Enhanced QSIG information.

PBX Code Method

[Explanation] Extension 102 does not answer the CO line call, so the call is forwarded to the VPS, using a VPS mailbox number containing the TIE line access number, the PBX code of the PBX that received the call, and the extension number that received the call. This mailbox number is the same as if an extension connected to PBX-1 called extension 102 of PBX-2. This mailbox number should be programmed as the mailbox number and owner extension number on the VPS.

Multiple VPSs

More than one PBX in the network can have a VPS connected, and each VPS can provide voice mail services for extensions connected to other PBXs in the network.

Conditions

Programming References

•	PC Programming Manual
•	2.8.45 [1-3] Option—New Card Installation—ISDN Standard Mode for PRI23 Card
•	2.16.1 [9-1] TIE Table—Centralized VM
•	2.16.2 [9-2] Network Data Transmission
•	→ Network MSW Data Transmission for Centralized VM Feature—Data Re-transmission : Repeat Counter
•	→ Network MSW Data Transmission for Centralized VM Feature—Data Re-transmission : Repeat Timer
•	2.18.1 [11-1] Main—Maintenance
•	→ Error Log for Centralized VM—Network MSW Transmission (Counter)
•	→ Error Log for Centralized VM—Network MSW Transmission (Buffer)
•	PT Programming Manual
•	None

Feature Manual References

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

Description

When PBXs are networked using ISDN or IP-GW cards, it is possible to assign flexible buttons as Network Direct Station Selection (NDSS) buttons. These buttons are used to monitor the status of extensions connected to up to seven other PBXs in the network, and to make or transfer calls to those extensions with one touch, like normal DSS buttons. This allows operator functions to be centralized even when there are offices in remote locations.

NDSS buttons show the status of the monitored extension as follows:

Light pattern Status Off The monitored extension is idle. Red on The monitored extension is busy or has set DND for CO line calls.

[Example Network]

[Programming Procedure]
1.	Routing Table Assignment TIE Line Routing and Modification tables must have been programmed in advance for all PBXs in the network, to allow calls to be made and transferred between PBXs (→ 1.13.15 PRIVATE NETWORK FEATURES). In the programming example that follows, the PBXs in the network use the Extension Number method, as shown in the illustration above. However, the PBX Access Code method can also be used.
2.	Network PBX ID Assignment Assign a Network PBX ID to each PBX in the network. → 2.16.2 [9-2] Network Data Transmission—Network Data Transmission for Centralized Operator Feature—Network PBX ID
	• IDs 1-8: Can monitor extensions at other PBXs, and transmit monitor data about local extensions. Each ID number can be assigned to one PBX within the network. • ID 0: Retransmits monitor data throughout the network. This ID number can be assigned to multiple PBXs.
3.	QSIG Port Setting [Monitored PBX] ISDN-QSIG (PBX Direct Connection) Each QSIG port of a PRI card that will be used to transmit extension status information must be set to do so through system programming. Even if a port is set to not transmit information, it will still receive information from other PBXs. → 2.8.30 [1-1] Slot—Port Property - PRI Port—CO Setting—Networking Data Transfer
	Transmit Extension Status Information Functions Enabled • Transmit information on own PBX extensions • Receive information from other PBXs; forward it to other QSIG ports of the PBX • Re-transmit information received by other QSIG ports of the PBX Disabled • Receive information from other PBXs; forward it to other QSIG ports of the PBX
	Set the transmission setting for each port according to the layout of your network, so that extension status information can travel between NDSS monitor PBXs. [Example ISDN Network Port Setting] IP-GW-QSIG IP data is routed through the network according to the routing tables of the IP-GW cards. When using VoIP, it is necessary to identify the monitor PBXs, to which to transmit extension status information, for each card that will be used. This is done by specifying the extension number of any extension (for example, the PBX operator) at the monitor PBX as a Network Operator extension for that IP-GW card. [Example VoIP Network] Mixed Network When using the NDSS feature over a mixed network containing both VoIP portions and ISDN line portions, it is possible to set whether status information will be transferred between VoIP and ISDN cards within each PBX. For example, if the monitor PBX is on a VoIP network, and monitored PBXs are on an ISDN network, the PBX that acts as a gateway between the VoIP and ISDN networks must have this setting enabled for ISDN to VoIP.
4.	Network Monitor Extension Registration [Monitor PBX] Register the extensions (attached to other PBXs) that will be monitored. A maximum of 250 extensions can be registered. Only extensions that have been registered here can be assigned to NDSS buttons. → 2.16.4 [9-4] NDSS Key Table—Network Extension No.
	Network Monitor Extensions Table
	Index No. Network Extn. No. Network Extn. Name 001 2001 Branch 1: T. Jones 002 2002 Branch 1: M. Davidson 003 4001 Branch 2: R. Powell : : : 250
	When using the PBX Access Code numbering method, the relevant access code must be added before the extension number registered here.
5.	NDSS Button Customization [Monitor PBX] At any extension attached to a monitor PBX, customize a flexible button as an NDSS button for an extension registered above. Then go off-hook, press this button once, and go on-hook again. This activates the monitoring function. The monitored PBX will begin to transmit information about the status of that extension, and the monitor PBX will begin to receive the information. The button light will display the status of the extension connected to another PBX.
	Removing or Editing a Registered Extension [Monitor PBX] To monitor a new extension when 250 extensions are already being monitored, it is necessary to remove the registration of an existing extension. The NDSS Monitor Release feature is used to stop monitoring a certain extension. When this feature is performed at a monitor PBX: • 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

•	The KX-NCS4910 (Activation Key for Software Upgrade to Enhanced Version) is required for all KX-TDE series PBXs that will monitor extensions or have extensions monitored.
•	Hardware Requirements: If using an IP-GW4E card (KX-TDA0484), 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-TDE or KX-TDA series PBXs. For information on the hardware requirements for KX-TDA series PBXs that will monitor extensions or have extensions monitored, refer to the KX-TDA 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. 2.11.5 [4-1-4] Wired Extension—Flexible Button    → Type    → Dial (for NDSS) 2.11.13 [4-2-3] Portable Station—Flexible Button    → Type    → Dial (for NDSS) 2.11.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. → 2.9.12 [2-7-1] Class of Service—COS Settings—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 maximum, the data is discarded. This is used to prevent data from circling unnecessarily around the network. → 2.16.2 [9-2] Network Data Transmission—Network Data Transmission for Centralized Operator Feature—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. → 2.11.8 [4-1-6] Wired Extension—NDSS Link Data - Send → 2.11.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 (→ 1.13.15 PRIVATE NETWORK FEATURES).

Programming References

•	PC Programming Manual
•	2.8.30 [1-1] Slot—Port Property - PRI Port—CO Setting—Networking Data Transfer
•	2.9.12 [2-7-1] Class of Service—COS Settings—Extension Feature—Manager
•	2.11.5 [4-1-4] Wired Extension—Flexible Button
•	→ Type
•	→ Dial (for NDSS)
•	2.11.8 [4-1-6] Wired Extension—NDSS Link Data - Send
•	2.11.13 [4-2-3] Portable Station—Flexible Button
•	→ Type
•	→ Dial (for NDSS)
•	2.11.15 [4-2-4] Portable Station—NDSS Link Data - Send
•	2.11.17 [4-3] DSS Console
•	→ Type
•	→ Dial (for NDSS)
•	2.16.2 [9-2] Network Data Transmission
•	2.16.3 [9-3] Network Operator (VoIP)
•	2.16.4 [9-4] NDSS Key Table
•	PT Programming Manual
•	[511] Manager Assignment

Feature Manual References

Operating Manual References

1.13.18 Private Network Features—Network ICD Group

Description

An Incoming Call Distribution (ICD) Group can include up to 4 destinations at other PBXs in a private network, including the floating extension number of another ICD Group. This is done by assigning a virtual PS as a member of the ICD Group, and then setting the number of a destination at another PBX as the forwarding destination for that virtual PS. This allows multiple ICD groups at remote locations to receive calls together.

Conditions

Programming References

•	PC Programming Manual
•	2.9.18 [2-9] System Options—Option 4—Send CLIP of CO Caller to ISDN—when ICD Group with Cellular Phone
•	PT Programming Manual
•	None

Feature Manual References

1.13.19 Private Network Features—PS Roaming by Network ICD Group

Description

One PS can be registered to up to 4 PBXs in a private network, and a Network ICD group created for the PS at each PBX, with virtual PSs set to forward to the other PBXs in the network. When a call to the PS is received at one of the PBXs, the call rings simultaneously at all PBXs in the network to which that PS is registered.

Each virtual PS is set to forward calls to the extension number of the actual PS as registered at one of the other PBXs.

Then, an Incoming Call Distribution (ICD) Group is created containing the registered PS and the virtual PSs.

When a call is received at one of the PBXs, it is forwarded to all of the other PBXs. One private network channel is used to forward an incoming call to one other PBX. Therefore, if a PS is registered at 3 other PBXs, 3 private network channels are needed to forward a single call to all of the PBXs.

Each PBX can store the current communication status of each PS (In Range or Out of Range). If the status of the PS is set to Out of Range when a call is received, the call will be refused and the private network channel will be released immediately. Since the PS can only be set to In Range at a single PBX at one time, any other PBXs to which the call is transferred will refuse the call, releasing the VoIP or ISDN channels.

Conditions

Programming References

•	PC Programming Manual
•	2.9.5 [2-3] Timers & Counters—Miscellaneous—System Wireless—PS Out of Range Timer
•	2.9.18 [2-9] System Options—Option 4—System Wireless—Out of Range Registration
•	2.10.12 [3-5-1] Incoming Call Distribution Group—Group Settings—Main
•	→ Floating Extension Number
•	→ Distribution Method
•	2.10.13 [3-5-1] Incoming Call Distribution Group—Member List
•	PT Programming Manual
•	[620] Incoming Call Distribution Group Member
•	[622] Incoming Call Distribution Group Floating Extension Number
•	[624] Incoming Call Distribution Group Distribution Method

Feature Manual References

1.13.20 PRIVATE NETWORK FEATURES—QSIG

Description

Feature Manual References

1.13.21 Private Network Features—QSIG—CCBS (Completion of Calls to Busy Subscriber)

Description

Conditions

Programming References

•	PC Programming Manual
•	2.8.30 [1-1] Slot—Port Property - PRI Port—Supplementary Service—COLP, CLIR, COLR, CNIP, CONP, CNIR, CONR, CF (Rerouting), CT, CCBS, E911
•	2.8.45 [1-3] Option—New Card Installation—ISDN Standard Mode for PRI23 Card
•	PT Programming Manual
•	None

1.13.22 Private Network Features—QSIG—CF (Call Forwarding)

Description

The PBX forwards the call to a destination extension in another PBX in the QSIG network. The destination can be set on your own PBX on an extension basis as the forward destination of CO line calls (→ 1.6.6 FWD (Call Forwarding)).

If the same trunk group is used for the incoming call and the forwarded call, the following situation will be possible.

[Example]   Extension 1000 of PBX-1 dials extension number "2000", and the call is sent to extension "2000" of PBX-2 through QSIG network. The call is forwarded to the forward destination of CO line calls of extension 2000, which is extension "1001" of PBX-1. The call between PBX-1 and PBX-2 is released, and the call is connected directly to the forward destination of extension 2000.

Conditions

Programming References

•	PC Programming Manual
•	2.8.30 [1-1] Slot—Port Property - PRI Port—Supplementary Service—COLP, CLIR, COLR, CNIP, CONP, CNIR, CONR, CF (Rerouting), CT, CCBS, E911
•	2.8.45 [1-3] Option—New Card Installation—ISDN Standard Mode for PRI23 Card
•	PT Programming Manual
•	None

Operating Manual References

1.13.23 Private Network Features—QSIG—CLIP/COLP (Calling/Connected Line Identification Presentation) and CNIP/CONP (Calling/Connected Name Identification Presentation)

Description

Calling Line Identification Presentation (CLIP) and Calling Name Identification Presentation (CNIP): The PBX can send a preprogrammed extension number and/or name to the QSIG network when an extension user makes a call. The called party can see the number and/or name on his telephone display before answering the call.

Connected Line Identification Presentation (COLP) and Connected Name Identification Presentation (CONP): The PBX sends a preprogrammed extension number and/or name to the QSIG network when the extension user answers an incoming call. The caller can see the number and/or name of the answering party on his telephone display when the call is answered.

[CLIP/CNIP Example]

[COLP/CONP Example]

CLIP/COLP Number: The extension number sent to the QSIG network for CLIP/COLP can be assigned for each extension through system programming.

CNIP/CONP Name: The extension name sent to the QSIG network for CNIP/CONP can be assigned for each extension through system programming.

Calling/Connected Line Identification Restriction (CLIR/COLR): It is possible for each extension to restrict the sending of its extension number to the QSIG network by pressing the CLIR button, COLR button, or entering the feature number.

Calling Name Identification Restriction (CNIR) and Connected Name Identification Restriction (CONR) It is possible for each extension to restrict the sending of its extension name to the QSIG network. When CLIR is activated, CNIR becomes active automatically. When COLR is activated, CONR becomes active automatically.

Conditions

Programming References

•	PC Programming Manual
•	2.8.30 [1-1] Slot—Port Property - PRI Port—Supplementary Service—COLP, CLIR, COLR, CNIP, CONP, CNIR, CONR, CF (Rerouting), CT, CCBS, E911
•	2.9.9 [2-6-1] Numbering Plan—Main—Features
•	→ COLR Set / Cancel
•	→ CLIR Set / Cancel
•	2.11.1 [4-1-1] Wired Extension—Extension Settings—Main
•	→ Extension Number
•	→ Extension Name
•	2.11.10 [4-2-1] Portable Station—Extension Settings—Main
•	→ Extension Number
•	→ Extension Name
•	PT Programming Manual
•	[003] Extension Number
•	[004] Extension Name

Feature Manual References

Operating Manual References

1.13.24 Private Network Features—QSIG—CT (Call Transfer)

Description

The PBX transfers the call to a destination extension in another PBX in the QSIG network.

If the same trunk group is used for the incoming call and the transferred call, the following situation will be possible.

[Example]   Extension 1000 of PBX-1 dials extension number "2000", and the call is sent to extension "2000" of PBX-2 through QSIG network. The call is transferred from extension 2000 to extension "1001" of PBX-1. The call between PBX-1 and PBX-2 is released, and the call is connected directly to the transfer destination of extension 2000.

Conditions

Programming References

•	PC Programming Manual
•	2.8.30 [1-1] Slot—Port Property - PRI Port—Supplementary Service—COLP, CLIR, COLR, CNIP, CONP, CNIR, CONR, CF (Rerouting), CT, CCBS, E911
•	2.8.35 [1-1] Slot—Card Property - IP Gateway—QSIG-CT
•	2.8.45 [1-3] Option—New Card Installation—ISDN Standard Mode for PRI23 Card
•	PT Programming Manual
•	None

Operating Manual References

1.13.25 Private Network Features—VoIP (Voice over Internet Protocol)

Description

The PBX can connect to another PBX via a private IP network. In this case, voice signals are converted into IP packets (VoIP) and sent through this network. VoIP networks support private network communications using TIE line service.

[Example]

Required Programming

• PBX For making a call: ARS programming (→ 1.1.3 ARS (Automatic Route Selection)) or TIE line service programming For receiving a call: TIE line service programming [TIE Line Routing and Modification Table] Location No. Leading No. Priority 1 Priority 2 . . TRG Dial Modification TRG Dial Modification . . Removed No. of Digits Added No. Removed No. of Digits Added No. . . 01 2 2 (VoIP port) 0 . . 02 3 2 0     . . : : : : : : : : : [Explanation] Calls to destinations with leading number "2" or "3" are automatically routed through the VoIP ports, designated as trunk group 2. • IP-GW IP address assignment for the local PBX and other PBXs. [Programming Example] Destination Leading No. IP Address 2 200.45.11.35 3 199.176.64.1 : : [Explanation] Calls are routed to the IP address of each IP-GW card based on the leading number dialed.

Gateway Groups

It is possible to automatically reroute outgoing VoIP calls according to preassigned gateway groups.

When using the V-IPGW16 card, a gateway device can be assigned a gateway group number, based on its IP Address. When a call is made using a leading number allocated to a gateway group, it is routed to the lowest-numbered available device within that group. In other words, if the lowest-numbered device is busy or not available, the call slides to the next available device.

[Example]

When "123XXX" is dialed, the call is routed to GW Group-1. However the lowest-numbered device (IP-GW(1)) is busy or not available, so the call is rerouted to IP-GW(2).

Note

For information about assigning groups when using the IP-GW card, refer to the Programming Guide of the VoIP Gateway Card.

Automatic Rerouting of VoIP Calls to Public CO Lines

When a VoIP call cannot be completed successfully, the PBX can automatically attempt to make the call using a public CO line instead. This provides a backup method of making calls in cases when IP network transmission cannot be completed successfully.

[Example]

The leading numbers of extensions accessed through the VoIP network are added as entries to the Quick Dialing table, in addition to being registered as Other PBX Extension Numbers, as shown below:

[Programming Example]

Number to dial to call an extension at another PBX using VoIP network: 7 (TIE line access number) + 20 (PBX Code) + 1011 (extension number)

Number to dial to call that extension using a public CO line: 9 (CO line access number) + 1-333-123-1011

[Quick Dialing Table] Quick Dialing No. Destination No. 720 91333123

If the call cannot be completed using the VoIP network, and the dialed leading number is found in the Quick Dialing Table, the call will be automatically rerouted to a CO line and as specified by the corresponding destination number.

When a call is made using the VoIP network, if the PBX does not receive a reply from the other PBX within about 4 seconds of making the call, or an error is returned, the call is rerouted to a public CO line as specified.

Sending Faxes Through the Network

Through system programming, it is possible to select whether faxes are sent using analog or T.38 protocol signals. To use T.38 protocol signals, the program software file version of the installed DSP card must be 56.000 or later.

Conditions

Programming References

•	PC Programming Manual
•	2.9.10 [2-6-2] Numbering Plan—Quick Dial—Use quick dial for rerouting to public CO when TIE line does not work
•	PT Programming Manual
•	None

Feature Manual References

1.13.26 PS Connection

Description

A Panasonic portable station (PS) can be used in place of a proprietary telephone (PT), providing wireless access to PBX features and call handling.

Cell Stations (CSs) allow PSs to receive reception within a designated area.

1.	Registration
	Before a PS can be used, it must be registered with the PBX through system programming and assigned an extension number. → 2.8.44 [1-2] Portable Station—PS Registration and De-registration—Registration → [690] PS Registration Because a PS transmits radio waves, it is possible that a PS belonging to a neighboring PBX can be registered to your PBX. To prevent this sort of unauthorized registration, a personal identification number (PIN) can be programmed for this PBX that must be entered on the PS during registration. This PIN, if programmed, is only used during the PS registration process. → 2.8.44 [1-2] Portable Station—PS Registration and De-registration—Personal Identification Number → [691] PS Termination Each PS can be registered to more than one PBX if necessary, and registration can be canceled if a PS will no longer be used with one of these PBXs. → 2.8.44 [1-2] Portable Station—PS Registration and De-registration—De-registration → [692] Personal Identification Number (PIN) for PS Registration
2.	Connection
	There are two ways a PS can be used. As an Extension A PS is assigned its own extension number when it is registered to a PBX. The PS can use this extension number to make and receive calls, just as a wired telephone can. A PS can be a member of an incoming call distribution (ICD) group, can be assigned as the destination for redirected calls, etc., just as a wired telephone can. A PS can also be a member of a PS ring group (→ 1.13.29 PS Ring Group). A PS ring group is a way for several PSs to be notified of an incoming call simultaneously, but does not offer all of the features provided by an ICD group. (→ 1.9.1 ICD GROUP FEATURES) In Wireless XDP Parallel Mode A PS can share an extension number with a wired telephone, allowing extension users to use their PSs when they are away from their desks to answer or make calls as if they were using their wired telephones. (→ 1.20.5 Wireless XDP Parallel Mode)
3.	PS Interaction with CS
	Each PS communicates with the PBX wirelessly through a cell station (CS). Each CS is connected to the PBX and sends and receives radio waves to and from different PSs within its range, using different channels for different PSs. Each CS has three channels, i.e., up to three calls (conversations) can be handled simultaneously by one CS. A PS must be within range of a CS in order to be used, however, multiple CSs can be used with the same PBX to offer a greater area of wireless coverage. Additionally, a PS does not need to be used with a specific CS; any PS can communicate with any CS provided the PS is registered to the PBX, and provided the CS has at least one channel available. Handover If a PS is within range of more than one CS, the PS will communicate with the CS which has the greatest signal strength and an available channel. When a PS user moves out of range of one CS and moves in range of another CS, the PS will "hand over" its communications to the new CS. Handover is possible when:
	a) The PS is on an intercom call or on a call with an outside party. (The call will not be disconnected during the handover.) b) A call is ringing at the PS. (The call will continue to ring after the handover.) c) The PS is in idle status (i.e., waiting to receive calls).
	[Example of Handover] Handover is not possible when the PS is:
	a) Not within range of another CS. b) Within range of another CS but that CS is busy. c) Screening a call via Live Call Screening (LCS) or recording a call via Two-way Record (→ 1.19.4 Voice Mail DPT (Digital) Integration) d) Paging other extensions. (→ 1.13.1 Paging) e) On a doorphone call. f) Dialing digits to make a CO line call. g) On a call with an extension which is recording the conversation via PC Console or PC Phone.

Conditions

Installation Manual References

Programming References

Feature Manual References

1.13.27 PS Directory

Description

Programming References

•	PC Programming Manual
•	2.13.1 [6-1] System Speed Dial
•	→Name
•	→CO Line Access Number + Telephone Number
•	2.11.1 [4-1-1] Wired Extension—Extension Settings—Main—Extension Name
•	2.11.10 [4-2-1] Portable Station—Extension Settings—Main—Extension Name
•	PT Programming Manual
•	[001] System Speed Dialing Number
•	[002] System Speed Dialing Name
•	[004] Extension Name

1.13.28 PS Feature Buttons

Description

1.13.29 PS Ring Group

Description

A PS ring group is a way for several portable stations (PSs) to be notified of an incoming call simultaneously, while using only one channel of a cell station (CS).

Normally when a PS receives a call, one channel of a CS is used to ring the PS (→ 1.13.26 PS Connection). If several PSs are members of an incoming call distribution (ICD) group, the available channels of a CS will become busy just by ringing each PS. Assigning a group of PSs to a PS ring group alleviates this strain on the CS because only one channel is needed to ring a PS ring group's members.

PS ring group members and related parameters are assigned through system programming, as explained below.

a) Floating Extension Number: When this number is called, all PSs in the group ring. b) Group Name: Can be displayed on a ringing PS to indicate that the incoming CO line call is a group call, and not a call directed to the PS's extension number. This is only available when Incoming CO Line Call Information Display is set to "Called Number". c) Incoming CO Line Call Information Display: Determines which information is shown on the PS display when a group call is received. Select "Caller ID" to display the caller's telephone number or name, or "Called Number" to display the name of the PS ring group which is receiving the call. d) Member PSs: Select each PS that will be a member of the corresponding PS ring group. Note that a PS can belong to more than one PS ring group.

[Programming Example: PS Ring Group]

[Example of PS Ring Groups 1 and 2]

Explanation:

PS Ring Group 1 PS 1, PS 2, and PS 3 will ring simultaneously when a call is directed to floating extension number 301, and, in the case of a CO line call, will display the Caller ID information for the call. These PSs will ring individually when a call is directed to their assigned extension numbers (programming not shown here).

PS Ring Group 2 PS 3, PS 4, and PS 5 will ring simultaneously when a call is directed to floating extension number 302, and, in the case of a CO line call, will display "Sales 2". These PSs will ring individually when a call is directed to their assigned extension numbers (programming not shown here).

ICD Groups vs. PS Ring Groups

Assigning PSs to either an ICD group or a PS ring group will allow multiple PSs to receive group calls simultaneously. The differences between the two are highlighted below:

Features PS Ring Group ICD Group Members can ring simultaneously when a call is received Calls can be distributed to member extensions using different methods The CS is less likely to be busy; ringing all member PSs uses only one CS channel Members can log-in, log-out, and use Wrap-up time, ICD Group button Both PTs and PSs can belong to the same group Each member can belong to more than one group Calls can wait in a queue if they cannot be answered

[Example of CS Channels Used for PS Ring Group Calls and ICD Group Calls]

Explanation:

The PS ring group has six members which are in range of two different CSs. When a call arrives, each CS uses one channel to ring all member PSs within its range.

The ICD group has one proprietary telephone (PT) member, as well as six PS members which are in range of two different CSs. When a call arrives, each CS uses three channels to ring each of the member PSs within its range.

Conditions

Programming References

•	PC Programming Manual
•	2.10.12 [3-5-1] Incoming Call Distribution Group—Group Settings—Main—Distribution Method
•	2.10.24 [3-9] PS Ring Group
•	2.10.25 [3-9] PS Ring Group—Member List
•	PT Programming Manual
•	[620] Incoming Call Distribution Group Member

Feature Manual References

1.13.30 PT Programming

Description

Conditions

Programming References

•	PC Programming Manual
•	2.9.12 [2-7-1] Class of Service—COS Settings—Extension Feature—Programming Mode Level
•	2.18.1 [11-1] Main—Password
•	→ System Password - PT Programming—Prog ** : User Level
•	→ System Password - PT Programming—Prog *# : Administrator Level
•	→ Manager Password - PT Programming—Prog *1
•	PT Programming Manual
•	2.1 PT Programming
•	[516] Programming Mode Limitation

Feature Manual References

Operating Manual References