KX-NS1000 Version1.0 Networking Features
Introduction KX-NS1000 provides two methods of private networking; 1. One-Look Networking 2. QSIG Networking (via ISDN and H.323) This part will focus on the new NS1000 feature One-Look Networking. The main benefits of One-look networking are; It looks like one PBX system, even though two or more PBXs are networked together. The system can be expanded easily via a Web based maintenance console. No additional servers are required for call control. The main differences between One-look and QSIG are; For One-look, the Master PBX controls all extensions within the network. In a QSIG network, each PBX controls its own extensions. For QSIG, each PBX needs to be programmed individually. For One-look, almost all settings are made in the master PBX only. QSIG is suitable for connecting the NS1000 to the existing KX-TDE/NCP systems, or when there are 17 or more NS1000s in the network. One-Look is available for up to 16 connected NS1000 systems (Max) Microsoft, Internet Explorer, Outlook, Windows, Windows XP, Windows Vista, and Windows 7 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks identified here in are the property of their respective owners. Microsoft product screen shots reprinted with permission from Microsoft Corporation.
Table of Contents Chapter 1) One Look Networking : Overview 1-1 One Look Networking Concept 1-2 One Look Networking Overview 1-3 Master Unit and Slave Unit 1-4 Main Features 2) One Look Networking : System Design 2-1 IP Capacity Expansion : IP Trunks 2-2 IP Capacity Expansion : IP Extensions 2-3 Site Expansion 2-4 Activation Keys 3) How to configure One Look Networking 3-1 Registration of New Slave Units 3-2 Easy Setup Wizard : Slave side 3-3 Add Site Wizard : Master side 3-4 Slave Unit Registration Wizard : Master side 3-5 Configuration for the slave units 3-6 About the Site ID 3-7 Changing the Master PBX IP Address 4) QSIG Networking 4-1 Overview
Chapter 1 One-Look Networking : Overview
1-1 One-look Networking Concept It looks like one PBX, even when connected through an IP Network. Conceptual View of One-look Networking Head Office The PBX located at the head office controls all of the extensions. Ext.1001 Ext.1002 Branch Office IP Network Branch Office Ext.1101 Ext.1102 Ext.1201 Ext.1202 All extensions within the One-look Network behave as if they were part of the Main Office, regardless of their actual location. * The network can be easily expanded with simple programming. - up to 1,000 extensions can be configured easily.
1-2 One-look Networking Overview (1) Master Unit controls one or more Slave Units (up to 15). Physical Connection of One-look Networking Head Office Master Unit The PBX located at the head office is called the Master Unit. PTSN Branch Office Slave Unit IP Network Branch Office Slave Unit PTSN The PBX located at the branch office is called the Slave Unit. If Slave units are installed in Branch Offices, local calls can be made using local trunks. The Slave units can also support additional extensions and UM features.
1-2 One-look Networking Overview (2) Specifications * The maximum number of units within an one-look networking is 16. - Master : 1 - Slave : 15 * The maximum number of extensions within an one-look networking is 1,000. - Max. 1,000 extensions / networked system - Max. 640 extensions * / site (unit) * SIP Phone : 640 * IP-PT and IP Softphone : 128 * Extension (Physical Extension Card) : 2 * Network Protocol : NS-Net - NS-Net is a network protocol only used for Panasonic products. * No external (additional) server for network call control is required. - Major competitors need server for 5 or more PBXs.
1-3 Master Unit and Slave Unit (1) Master and Slave units are the same physical PBX model. The PBX mode (Master or Slave) is set via system programming (Installation). The key parameters assigned to each unit are; - Master : PBX Type=Master, Own IP address - Slave : PBX Type=Slave, Own IP address, IP address of the master unit The PBX mode (Master or Slave) is indicated by the MASTER LED on the front of the unit. Indicators STATUS BATT ALARM MASTER Master : Green ON Slave : Amber ON
1-3 Master Unit and Slave Unit (2) Software Version between the Master unit and the Slave unit. The one-look network should be consist of the PBXs which have the same software version. (The revision may differ.) Maintenance -> System Control -> 1.2 Update Program File Now operating software Software Revision may differ. Software Version must be the same.
1-4 Main Features (1) System Expansion with Simple Setup Master Unit Slave Unit One-look Networking 2. Automatically access to the master, and configures itself. 1. Expand New Slave Unit
1-4 Main Features (2) Trunk call through Remote Units. An extension user can access trunks connected to remote units. International Call Master Unit PSTN München Local Call Paris PTSN Slave Unit Internal Company Call (Free charge) Total call charges can be reduced. * Long-distance and international call charges can be reduced.
1-4 Main Features (3) Simplified Programming Web MC connected to the main unit can set all the settings of the slave units. Web MC Master Unit Slave Unit One-look Networking Slave Unit Web MC * When you configure the UM data on Slave units, etc., you must log in to the corresponding Slave unit directly. You can also log in to the Slave unit directly. However, you can configure only the Slave unit s local data.
This Chapter is now complete. Go to Next Chapter.
Chapter 2 One-Look Networking : System Design
2-1 IP Capacity Expansion : IP Trunks The overall IP trunk capacity does not increase in proportion to sites. Type Stand Alone One-Look Network N sites (N>=2) Upper Limit Total Number of Trunks 256 256 x N 600 Trunk (Virtual Trunk Card) 256 256 256 H.323 Trunks 48 96 96 SIP Trunks 256 256 256 Trunk (Physical Trunk Card) 30 30 x N 480 SIP Trunks example 100ch SIP Provider SIP Provider 100ch One-Look Networking Max. / Networked System ->256ch. Max. / Site -> 256 56ch SIP Provider * The maximum number of Sites within an one-look networking is 16.
2-2 IP Capacity Expansion : IP Extensions The IP extension capacity does not increase in proportion to sites. Type Stand Alone One-Look Network N sites (N>=2) Upper Limit Total Number of Extensions 640 1,000 1,000 Extension (Virtual Extension Card) 640 1,000 1,000 IP-PT and IP Softphone 128 128 x N 1,000 SIP Phone 640 1,000 1,000 Extension (Physical Extension Card) 2 2 x N 32 SIP-Extension example 300 Max. / Networked System -> 1,000 640 Max. / Site -> 640 One-Look Networking 60 * The maximum number of Sites within an one-look networking is 16.
2-3 Site Expansion (1) Bandwidth (1/2) Bandwidth for voice data, call control (signalling), and system control between units must be considered when site planning. Required Bandwidth per Call for Voice : Determined by CODEC and Packet Sending Interval CODEC Required Bandwidth per Call for Signalling Packet Sending Interval 20ms 30ms 40ms 60ms G.711 / G.722 80kbps 74.7kbps 72kbps 69.4kbps G.729A 24kbps 18.7kbps 16kbps 13.4kbps Phone Type IP Telephones (except SIP phones) SIP Phone Required Bandwidth 43.0kbps 16.0kbps Required Bandwidth for System Control * In addition to the above, Basic Ethernet frame, VPN headers, Required Bandwidth for System Control, etc., should also be considered.
2-3 Site Expansion (2) Bandwidth (2/2) Assessing bandwidth - Example; Master Unit IP Network CODEC : G.711 Packet Interval : 20ms Slave Unit Number of Extensions : 50 Extension Type : SIP Phone Number of Simultaneous Calls : 16 Bandwidth required for Voice data = Number of simultaneous calls x 2 x Required bandwidth for codecs (kbps) = 16 x 2 x 80 = 2560kbps Bandwidth required for Signalling = Number of simultaneous calls x signalling bandwidth per call for SIP phones (kbps) = 16 x 16 = 256kbps Total required bandwidth = Bandwidth required for Voice data (kbps) + Bandwidth required for signalling (kbps) = 2560 + 256 = 2816kbps * In this example, Basic Ethernet frame, VPN headers, system control data, etc., are not considered.
2-3 Site Expansion (3) The Number of Simultaneous Calls To fully assess the total bandwidth required, the number of simultaneous calls must also be considered. A guideline of the number of simultaneous calls based on the general call traffic. Number of Registered Extensions 10 50 100 150 200 250 300 Number of Simultaneous Calls 6 16 26 35 44 53 61 * This chart does NOT show the upper limit of simultaneous calls. * This chart is just an example. Actual number depends on each customer.
2-4 Activation Keys (1) Centralized and Distributed Activation Key - Overview There are 2 types of Activation Key as follows. Centrilized Activation Key : These Keys are needed only for the Master Unit. Distributed Activation Key: These Keys are needed for each Unit. Following diagram shows how to install Centrized/Distributed Activation Key. Image of Activation Keys Installation Centralized/Distributed
2-4 Activation Keys (2) Centralized Activation Key List QSIG Network Item Unified Messaging System (Two-way Recording / Two- way Transfer Users) CTI Licence Cellular Phone Extension Communication Assistant (CA) User Overview Allows the use of enhanced QSIG network features (NDSS, Centralised Voice Mail, etc.). Allows the use of Two-way Recording/Two-way Transfer Allows the use of the 3rd Party CTI interface. Allows the use of cellular phone extensions. CA Pro CA Supervisor CA Operator CA Network CA Thin Client CSTA Multiplexer Console
2-4 Activation Keys (3) Distributed Activation Key List Item Overview Type/Note IP Trunks Allows the use of IP trunks H.323 / SIP IP Telephone Capacity Allows the ports of IP Telephones 30 ports are pre-installed (*1) IP Telephone Allows the use of IP Telephones 8 telephones are pre-installed (*1) One-look Network Unified Messaging System (Features) Unified Messaging System (UM Ports) Unified Messaging System (UM Ports) Allows the use of multi-site connections using One-look network feature. REC Time Expansion / Two-way REC Control / Message Backup Allows the use of Unified Messaging (UM) ports Allows the use of an e-mail (IMAP4) client and e-mail notification (voice/fax messages). Note: (*1) Up to 30 IP-Extensions can be used without needing any of the optional IP Telephone Capacity activation keys. However, when using IP extensions (over 8), you must purchase IP Telephone Activation Keys.
2-4 Activation Keys (4) How to Configure Activation Key (Example) System Configuration Master Unit ISP SIP Trunk Service and peripheral System Master Unit Slave Unit Equipment/Service 1) One-Look Networking 2) 38 IP(NT,UT) Extension 3) 10 IP(H323/SIP) Trunk 4) 4channel,15H-UM Recording 5) 30 2way-Recording users 1) One-Look Networking 2) 30 3 rd vender SIP Extension 3) 1 PRI30 Slave Unit IP Network PTSN ISDN/PRI Necessary Activation Keys System Item Model Number 1) One-Look Networking KX-NSN001 2) 50 IP Phone Installation KX-NSM005 3) 16 IP Trunk KX-NSM116 Master 4) 10+20 IP PT (8 free) KX-NSM510,520 Unit 5) 2 channel UM ports KX-NSU102 6) Record time Expansion KX-NSU001 7) 2Way REC all users KX-NSU399 Slave Unit 1) One-Look Networking KX-NSN001 2) 10+20 SIP Extension KX-NSM710,720
This Chapter is now complete. Go to Next Chapter.
Chapter 3 How to Configure One-look Networking
3-1 Registration of New Slave Units Procedure to register a New Slave Unit. To add (register) a slave unit to the master unit, the master unit must be in slave unit registration mode. Adding the slave unit flow chart 1 Launch the KX-NS1000 as a Slave unit (Easy Setup Wizard). -> Slave side 2 Add a slave unit to the master unit on Web MC (Add Site Wizard). -> Master side 3 Set the master unit to Slave unit registration mode (Slave Unit Registration Wizard). -> Master side * No.1 is available after No.2. Anyway, the KX-NS1000 to be configured as a slave unit must be running while the master unit is in Slave unit registration mode. * Activation Keys (KX-NSN001) are required for both the Master unit and the slave unit. For details, refer to the Activation Key part.
3-2 Easy Setup Wizard : Slave side (1) 1 Connect the PC to the KX-NS1000, and launch the Easy Setup Wizard. For details about the Easy Setup Wizard, refer to the Initial Set Up part. In this part, only different points from configuring the Master unit are explained. 2 Location Setting Screen 1. Select Slave as a PBX type. 2. Specify the IP address of the Master unit. - If the Slave is located on the same network with the Master, leave the default value (0.0.0.0). * 2. Click Next. * If the Slave is located on a separate network with the Master, it is necessary to specify the IP address of the Master.
3-2 Easy Setup Wizard : Slave side (2) 3 PBX Setting Screen 1. Site name is fixed. (Will be downloaded from the Master.) 2. Set Time Zone and Local Time. 3. Click Next. 4 LAN Setting Screen 1. Set the LAN settings for the slave unit. 2. Click Next.
3-2 Easy Setup Wizard : Slave side (3) 5 Registration Setting Screen 1. Select Active to enable One-look networking in the One-look network (Trial Activation Key) column. * You can also enable One-look networking by installing an optional Activation Key file after using the Easy Setup Wizard. In either case, Activation Keys (Trial or Optional Key File) are required to use One-look networking. 2. To finish the Easy setup wizard, click Finish. * Be sure to install optional Activation Key (KX-NSN001) after the One-look networking is established. * If a warning message (One-look network licence expired.) is displayed, install the optional Activation Key(KX-NSN001) after the Easy setup wizard. * Refer to the next slide for installing the optional Activation Key. 6 1. To reboot the slave unit, click OK. When the Easy Setup Wizard is finished, the slave unit will reboot automatically (because the LAN setting has been changed), and try to access the Master.
3-2 Easy Setup Wizard : Slave side (4) After the Easy setup wizard is finished, install the optional Activation Key to the corresponding PBX with Web MC. When One-look networking is established by using the trial Activation key. Login to the Master unit, and then install the optional Activation key (KX-NSN001). The Activation key is automatically installed to the slave unit. When the trial Activation key is not activated or expires on the slave unit. Login to the Slave unit, and then install the optional Activation key (KX-NSN001) directly. Maintenance -> Utility -> 6 Activation Key Installation 1. Specify (Select )the folder and the target Activation Key file on the PC. (You can use Browse button.) 2. Click Install. 3. When successfully installed, the message window will be opened.
3-3 Add Site Wizard : Master side (1) 1 Home Screen of the Master unit Click Add Site.
3-3 Add Site Wizard : Master side (2) 2 PBX Setting Screen 1. Specify a Site name. 2. Set Time Zone and Local Time. 3. Click Next. 3 Registration Setting Screen 1. Select an IP terminal registration mode. 2. Click Next.
3-3 Add Site Wizard : Master side (3) 4 SNTP Daylight Saving Screen 1. Set SNTP parameters. 2. Click Next. 5 Maintenance Setting Screen 1. Set SNMP parameters. 2. Click Finish.
3-3 Add Site Wizard : Master side (4) 6 2. Click List View. 1. The new slave unit is added. 7 1. Please note the Site ID. * * The Site ID is used when making settings with the units identified.
3-4 Slave Unit Registration Wizard : Master side (1) 1 Home Screen of the Master unit Click List View. * Be sure to activate the pre-installed Activation key (for One-look Network) or install optional Activation Key (KX-NSN001). How to install optional Activation Key to the Master unit is similar to the Slave unit. Refer to Chapter 3-2. (4)
3-4 Slave Unit Registration Wizard : Master side (2) 2 Click Registration. 3 1. Select the slave units to be registered. 2. Click ==> to move them to Selected sites for registration.
3-4 Slave Unit Registration Wizard : Master side (3) 4 1. Confirm the slave units. 2. Click Next 5 The Registration process will start.
3-4 Slave Unit Registration Wizard : Master side (4) 6 The slave unit to be added will access the Master unit. (It is also available to launch the Easy Setup Wizard after launching the Slave Unit Registration Wizard.) 7 The Registration process will be completed. After registration is completed, the slave unit will reboot automatically.
3-4 Slave Unit Registration Wizard : Master side (5) 8 After the slave unit reboots and accesses the Master unit completely, the slave unit will be INS (In-Service). Home Screen List View Screen
3-5 Configuration for the slave units (1) Common and Individual Unit Settings To configure One-Look Networking, some setting items must be configured for each individual unit. Main Settings Common Settings (Master) - Numbering Plan - COS - Group Settings - Extension Settings - Co Line Settings - DDI/DID Table - TRS - ARS - etc. Individual Settings (Master & Slave) - Slot (Installing Physical and Virtual card) *1 - Card and port property *1 - IP Terminal Registration *1 - Network service (IP address, DHCP server, etc.) *2 - UM *3 - etc. *1 via Master unit *2 via Master unit and direct log in *3 direct log in
3-5 Configuration for the slave units (2) How to configure each individual unit To configure each unit, select the unit via Web MC. There are two ways to select the desired unit. 1 Via Home Screen Right-click the unit to be configured, and select Maintenance or Setup or Direct Login. 2 Via Drop-Down Menu Select the unit to be configured from the pull-down menu.
3-6 About the Site ID The Site ID is used for Common settings. The Site ID is assigned to each unit via the Add Site wizard. On the PBX setting screen, the Site ID is used instead of Site name. Extension Setting example Site column - The Site ID is shown. * The Site ID is used for CO Line Settings, DIL Table & port Settings, Doorphone, External Relay, External Sensor, etc. * To confirm the Site ID, click List View on the Home screen.
3-7 Changing the Master PBX IP Address When When the the IP address IP address of the of the Master Master unit on on an an One-look network is is changed. changed, the Master PBX IP address setting of the Slave units must be changed. 1 Login to the Slave unit directly via MNT port or LAN port. - When using MNT port ; http://kx-ns1000. - When using LAN port ; http://ip address of the Slave/WebMC 2 Setup -> PBX Configuration -> 1.1 Slot Click System Property. 3 Multisite Tab. Specify the IP address of the Master unit. - If the Slave is located on the same network with the Master, select Obtain an IP address automatically.
This Chapter is now complete. Go to Next Chapter.
Chapter 4 QSIG Networking
4-1 Overview Connections between different PBX systems / types via QSIG PBXs (KX-NS1000, KX-TDE, KX-NCP) can be connected to each other via ISDN private network or VoIP network (H.323), and provide QSIG features. Programming is same as existing NCP/TDE programming. KX-NS1000 (Master) KX-TDE/NCP QSIG Networking KX-NS1000 (Master) - When using QSIG enhanced features, activation keys are needed. - When using QSIG enhanced features, KX-TDE / NCP must be with MPR software version 4.1000 or later.
Thank you! The END
KX-NS1000 Version2.0 Networking Survivability Features
Introduction This document explains KX-NS1000 series PBXs, and is composed of the following chapters. Chapter 1 System Overview Chapter 2 Backup Master Mode Chapter 3 Isolated Mode Chapter 4 Automatic rerouting to Secondary PBX For further information about feature implementation and specifications, refer to the following manuals. Installation Manual / Feature Guide / Getting Started Microsoft, Internet Explorer, Outlook, Windows, Windows XP, Windows Vista, and Windows 7 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. All other trademarks identified here in are the property of their respective owners. Microsoft product screen shots reprinted with permission from Microsoft Corporation.
Table of Contents Chapter 1) System Overview 1-1 What is a Survivability feature 1-2 Backup-master 1-3 Isolated Mode 1-4 Automatic re-routing to secondary PBX 1-5 Case study 3) Isolated Mode 3-1 Change to Isolated mode 3-2 Programming 3-3 Alert Message 2) Backup Master Mode 2-1 Change from Master to Backup-master 2-2 Supported features by the Backup Master 2-3 Supported devices by the Backup Master 2-4 Programming 4) Automatic rerouting to Secondary PBX 4-1 Change to Secondary PBX 4-2 Supported IP terminals 4-3 KX-NT Operation 4-4 KX-NT Programming 4-5 KX-UT Operation 4-6 KX-UT Programming 4-7 Data Migration to Backup-Master
Chapter 1 System Overview
1 2 1.1 What is a Survivability feature? (1) Redundancy of One-look Network Backup-master Mode - When the Master unit stops working or cannot communicate, one of Slave unit become Backup-master and continue One-look network service. [Master unit : Primary call management PBX] [Backup-master : Secondary call management PBX] Max. one Back-up Master can be assigned. - There is no additional hardware or Activation Key required to use Backup Master feature. Isolated Mode - When the Master and Secondary unit stop working or cannot communicate, a Slave unit become independent system to continue own telephone system. (In this case, a Slave unit have some limitation of feature.) - There is no additional hardware or Activation Key required to use Isolated Mode feature.
3 1.1 What is a Survivability feature? (2) Redundancy of IP-phone Automatic Rerouting to Secondary PBX - When the IP-phone can not communicate with the primary registered NS1000, those IP-phone will connect to secondary registered NS1000. [IP-Phone : UT/NT/UDT(SIP-DECT) except IPCS] - This feature can work by each extension settings regardless of whether using the One-look network feature.
1.2 Backup-Master 4 NS1000 are connected as One-look network. And Slave 1 is assigned as Backup Master. Master NS failed!! Master [Trouble Example] - Equipment trouble - Power Failure - Cable damage Slave2 Slave1 (Backup Master) Private IP Network (Including VPN) Slave3 1) Master NS failed. NS1000 assigned as Backup-Master start to work like stand by CPU. 2) Slave 2 and 3 switch to connect with Backup-Master NS1000. * All AK information transfer to Back up Master from Master and Temporary AK will be act based on information from Master. Temporary AK valid 10 days from when Back up Master start to act.
1.3 Isolated Mode 4 NS1000 are connected as One-look network. Slave2 Isolated mode Master Network failed!! Local Trunks Slave1 (Backup Master) Private IP Network (Including VPN) Slave3 Isolated mode Slave mode Local Trunks When the Master unit and a Slave unit can not communicate each other, a Slave unit will become independent system to continue own telephone system. Isolated Mode. In this mode, some of the features in PBX are limited. * When a network was recovered, it is necessary to return the first system by manual operation. (not automatic)
1.4 Automatic re-routing secondary PBX When a IP-phone can not communicate with the primary NS1000, those IP-phone will connect to secondary registered NS1000. (IP-Phone : UT/NT/UDT(SIP-DECT) except IPCS.) LAN Master (Secondary PBX for IP-phone) Private IP Network (Including VPN) Primary NS failed!! Slave1 LAN 110 112 214 110 112 213 213 214 1) Primary registered NS1000 failed. 2) Connect to Secondary registered PBX when a network is available. When the secondary registered PBX is Master NS1000, Activation key is not required. (If not, it may be necessary to prepare a activation key in the Secondary registered NS1000 for backup.) 3) Registration in advance. IP extension of 213 and 214 are necessary to register at Secondary NS1000 in advance. (Those are the reserved number for backup.)
1.5 Case Study Master NS failed!! Master Slave2 Slave1 Backup Master Private IP Network (Including VPN) Slave3 1) Master NS failed. NS assigned as Backup-Master start to work like stand by CPU. 2) Slave 2 and 3 switch to connect with Backup-Master NS. 3) EXT under Master switch to connect with Backup-Master as Secondary PBX. (Automatic rerouting) 4) Also, when the network has failed, the slave 2 and slave 3 will become a independent system (isolated mode).
Chapter 2 Backup Master Mode
2.1 Change from Master to Backup-master (1) When the Master unit is affected by a system, network or electrical failure, a Slave unit which has been pre-programmed as the Backup Master can take control of the remaining Slave units and PBX services can continue. The Master/Slaves keep synchronization by regular Keep-Alive and Keep-Alive Ack packets. If the flow of these packets to/from the Master is interrupted, the Backup Master and Slave re-registration process starts as shown below; <1>After Keep-Alive Timeout expires, Slave1 restarts as Backup Master. (MASTER LED = Green Flashing) Master failed!! Slave1 (Backup Master) Slave2 Private IP Network (Including VPN) Slave3 <2>After Keep-Alive Timeout expires, Slaves 2&3 restart and register to Backup Master.
2.1 Change from Master to Backup-master (2) The Backup Master copies the Master system program periodically to ensure that it is always ready to take over if necessary. Master failed!! When the Master unit is a normal mode, the data is transferred periodically. Slave1 (Backup Master) NB: Data which is held on the SRAM of the Master, is not transferred to the Backup Master. SMDR Error Log EXT setting like Timed Reminder Remote Station Lock Check-In/Out Ready/Not Ready/Clean Up Login/Logout EXT, CO, Verified Code base Charge Total Slave2 Private IP Network (Including VPN) Slave3 The alert message (email) can be sent from the Backup Master to alert the dealer that the system has entered Backup Master Mode.
2.2 Supported features by the Backup Master The following features / resources can be supported by the Backup-Master; Resource Available on Backup Master Note Configuration Data YES Any programming changes made to the Backup Master will not be copied back to the Master when it is brought back into service. SMDR Data YES SMDR data can be obtained from the Backup Master. Data can be merged via PC. Call Log YES Supported by KX-UT series only (Internal Call Log) CA (built-in) NO *1 CA Client needs to change to Backup Master PBX IP Address manually. This is not changed automatically. CA (Server) NO *1 Additional CA Server is required for Backup. CA Client needs to change to Backup Master PBX IP Address manually. This is not changed automatically. IMAP4 YES Need to assign 2 accounts. One on Master and One on Backup Master. Activation Keys YES All activation keys on Master will operate on Backup Master for 10 days. *1. IP address of Master PBX and Back-up PBX are not same. So CTI application cannot work automatically.
2.3 Supported devices by the Backup Master The following features / resources can be supported if the Master fails; Device/Resource Survivability Note IP-PTs YES Use Automatic Rerouting to Secondary PBX feature on the IP-PT. IP-Trunk YES IP-Trunk can be switched to Backup Master automatically. (Or ITSP Failover service can be employed) OGM NO OGMs must be manually copied to Backup Master. Legacy Trunk / SLT Legacy-GW NO NO UM Mailbox NO Left message in Built-in VM for Master PBX cannot be transferred to Back-up PBX. UM Group YES Any calls terminating on UM:500(Master) will be automatically diverted to UM:501(Backup Master). FAX Server NO
2.4 Programming The following system programming needs to be set in the Master System to allow Backup Master operation 1. Home Screen List View <1> Assign which Slave will be act as Back up Master. <2> Configuration Screen > Slot -> System Property -> Multisite 40s 300 1. Multisite Keep alive Time-out time is used for Alive check for both Master and Slave. 2. Multisite startup monitoring time is the time used by the Slave to decide if to start with Master/Back up Master or Isolated mode*.
Chapter 3 Isolated Mode
3.1 Change to Isolated mode If the Network fails, the isolated slave unit(s) can be configured to enter Isolated mode. The isolated Slave unit can provide local services via directly connected Extensions and Trunks. (Via local LAN etc) Master Master Unit system programming is copied to each Slave units every hour. (One - by - One) Slave1 (Backup Master) Slave2 Isolated mode Private IP Network (Including VPN) Slave3 Master and Slaves 1&3 can operate normally. MASTER LED = Red Flashing - AK for IP ch in Master PBX is not transferred to slave PBX. - AK for other such as Cellular Link feature is transferred to slave PBX. It works for 10 days as temporal AK after master PBX stops working. - If extension in slave PBX uses VM mail box in master PBX, VM cannot work. VM in same PBX should be used. * No Additional Activation Keys required.
3.2 Programming (1) The following system programming needs to be set in each Slave System to allow Isolated operation. Configuration Screen > Slot -> System Property -> Main Change to Enable (Default = Disable) The alert message (email) can be sent from the Isolated Slave unit to alert the dealer that the system has entered Backup Master Mode. * This is the only setting to use Isolated mode.
3.2 Programming (2) The Slave Unit will not automatically return to Normal mode after the problem has been resolved. The Unit will need to be put back into Normal mode manually. 1. Directly Log-in to the Isolated mode system. 2. In the Home screen, select Slave ICON and right click. 3. Select Normal Mode 4. Confirmation window will appear This site will re-start. OK? 5. The Slave will re-start and start to send Start Ack to Master or Backup Master.
3.3 Alert Message Reference The alert message can be sent from the Stand-Alone to alert the dealer that the system has entered Isolated Mode. Subject KX-NS1000 System alarm#2 text [System Name] : KX-NS1000 [MPR-ID] : AAAA-BBBB-CCCC-DDDD [Date] : 11/12/31 [Time] : 23:59:59 [Error Code] : 537 [Sub Code] : 50400 [Error Message] : Change into ISOLATED Mode Also, the alert message can be sent from the Backup Master to alert the dealer that the system has entered Backup Master Mode. [Error Message] : Change into Backup Master Mode
Chapter 4 Automatic rerouting to Secondary PBX
4.1 Change to Secondary PBX IP-PTs and KX-UT Series SIP Phones can be programmed with the IP Address information of two PBX systems (Primary and Secondary). Depending on the status of the Primary PBX system (in-service or out-of-service), the terminal can automatically switch to the Secondary PBX system. LAN Master (Secondary PBX for IP-phone) Private IP Network (Including VPN) Primary NS failed!! Slave1 LAN 110 112 214 110 112 213 213 214 NB:The Secondary PBX needs sufficient port and Activation keys installed to support the additional terminals. [Example] Unit-1 use 200 IP-phone. / Unit-2 use 300 IP-phone. If the unit2 is failed, the unit1 manage the 500 IP-phone. (Pre-registration and Activation key is required.)
Type Model Supported Recommended Firmware IP-PT KX-NT3xx, NT5xx YES V2.011 IP Conference Phone 4.2 Supported IP terminals The following IP Terminals can support the Automatic Rerouting feature; KX-NT136, NT265 NO n/a KX-NT700 NO n/a IP-CS KX-NCP0158 NO n/a IP-Softphone KX-NCS8100 NO n/a SIP-MLT KX-UT133/136/248/670 YES V1.206 SIP-SLT KX-UT113/123 YES V1.206 SIP-CS KX-UDS118/124 YES 1 st Release [Primary/Secondary PBX IP address to the terminals] NT is set via the LCD screen of the each terminal. UT is set in the Virtual UT Card Port Properties.
4.3 KX-NT Operation (1) The KX-NT3xx terminals support rerouting in the following way; Secondary PBX Private IP Network (Including VPN) Primary PBX <3>IP-PT starts register to Secondary PBX Secondary PBX IP-PT(NT) Primary PBX ARP Keep Alive (every 5 sec) Answer for Keep Alive Keep Alive (every 5 sec) Answer for Keep Alive ARP (9 times) ARP (every 60sec) <1>LAN connection of Primary PBX fails. <2>IP-PT(NT) starts reboot When IP-PT is connected to the Primary PBX and the Primary PBX stays alive, the IP-PT does not switch to Secondary PBX. If the Primary PBX fails, then the IP-PT sends an ARP to the Secondary PBX.
4.3 KX-NT Operation (2) There is no Mailbox Survivability, a Mailbox will need to be created on the secondary PBX. There is no integration of Primary and Secondary mailboxes, they work independently; Secondary PBX Private IP Network (Including VPN) Primary PBX Mail Box 201 Independent Mail box Mail-Box 201 Secondary PBX IP-PT(NT) Primary PBX Keep Alive (every 5 sec) Answer for Keep Alive ARP (every 60 sec) ARP Restore LAN connection of Primary PBX Keep Alive (every 60sec) Stop communication <1>Answer for Keep Alive <2>IP-PT(NT) starts reboot <3>IP-PT(NT) starts to register to Primary PBX Keep Alive (every 5sec) Answer for Keep Alive When IP-PT is connected to the Secondary PBX, the IP-PT keeps sending an ARP to the Primary PBX. When the Primary PBX is restored, the IP-PT reboots and connects back to the Primary PBX.
4.4 KX-NT Programming (1) The KX-NT terminals Primary/Secondary PBX assignment is set via the LCD screen of the terminal. V2.xxx KX-NT Firmware is required to utilize this feature. KX-NT Setting(1) Primary/Secondary PBX IP Address 1. Set both the Primary and Secondary PBX IP Addresses. PBX -> Primary PBX -> Secondary PBX NEXT EXIT ENTER PBX IP Address? 192.168.0.x EXIT CLEAR ENTER When the KX-NTxxx loses link with the Primary PBX, it can re-register with the Secondary PBX if the correct IP Address is programmed.
4.4 KX-NT Programming (2) The KX-NT terminals Primary/Secondary PBX assignment is set in the Virtual IPEXT32 Card Port Properties. System Setting (1) Secondary PBX; Configuration Screen > Virtual Slot -> Secondary PBX -> VIPEXT32-> Secondary Setting 1) Select which free ports will be used as Backup (Secondary) Ports. No Extension Number or Name need be entered. 2) Click OK
4.4 KX-NT Programming (3) The KX-NT terminals Primary/Secondary PBX assignment is set in the Virtual IPEXT32 Card Port Properties via a Wizard. System Setting (2) Primary PBX; Configuration Screen > Virtual Slot -> Primary PBX -> VIPEXT32-> Secondary Setting NB: NT terminals must first be registered to the system before using the Wizard. 3) Ensure the desired NTxxx is registered to the Primary PBX system. 4) Click Set Secondary to start the Wizard. The Secondary Port Wizard lets you assign which extension needs a Secondary connection to a specific NS1000.
4.4 KX-NT Programming (4) The KX-NT terminals Primary/Secondary PBX assignment is set in the Virtual IPEXT32 Card Port Properties via a Wizard. System Setting (3) Primary PBX; Configuration Screen > Virtual Slot -> Primary PBX -> VIPEXT32-> Secondary Setting -> Set Secondary 5) Select the desired Secondary site and assign the NT Terminal to a free Secondary port. 6) The Secondary port is assigned and the number of free secondary ports reduces. 7) Click Execute. There must be sufficient Secondary ports assigned on the Secondary PBX for each NT Terminal requiring this feature.
4.4 KX-NT Programming (5) The KX-NT terminals Primary/Secondary PBX assignment can be confirmed as follows; System Setting (4) Primary/Secondary PBX; Configuration Screen > Virtual Slot -> Primary PBX -> VIPEXT32-> Secondary Setting -> Set 8) Confirm the Primary/Secondary assignment on each PBX.
4.5 KX-UT Operation (1) The KX-UT terminals support rerouting in the following way; Secondary PBX Private IP Network (Including VPN) Primary PBX Secondary PBX KX-UT Primary PBX Periodic (Inform Interval) <1>LAN connection of Primary PBX fails. Periodic (Inform Interval) <2>KX-UT starts to reboot Periodic (5sec) Periodic Periodic (10sec) (20sec) <3>Resend times (5 times) <4>KX-UT starts register to Secondary PBX ARP Inform (BOOTSTRAP) Periodic (40sec) When KX-UT is connected to the Primary PBX and the Primary PBX stays alive, the KX-UT does not switch to Secondary PBX. If the Primary PBX fails, then the KX-UT sends an ARP to the Secondary PBX.
Secondary PBX 4.5 KX-UT Operation (2) The KX-UT terminals recovers the Primary PBX in the following way (Controlled by Master / Backup Master); Private IP Network (Including VPN) Primary PBX Master or Backup Master <1>Retrieve Primary PBX Secondary PBX KX-UT Primary PBX Inform (Periodic) Inform Res. (Periodic) <2>Set Parameter Values Device.Management Server.URL Stop communication <3>ARP Retrieve Primary PBX Management Server change <4>Inform (BOOTSTRAP) <5>Inform Res. (BOOTSTRAP) KX-UT starts registration to Primary PBX When KX-UT is connected to the Secondary PBX and the Primary PBX recovers (Master or Backup-master get start ack from primary), then the Master or Backup-master sends Set Parameter Value to UT. The UT sends an ARP to the Primary, Registers to the Primary and then reboots.
4.6 KX-UT Programming (1) The KX-UT terminals Primary/Secondary PBX assignment is set in the Virtual UT Card Port Properties. System Setting (1) Secondary PBX; NB: UT terminals must not be registered to the system before using the Wizard. Configuration Screen > Virtual Slot -> VUTEXT32 -> Secondary PBX-> Secondary Setting 1) Select which free ports will be used as Backup (Secondary) Ports. No Extension Number or Name need be entered. 2) Click OK The Secondary Port Wizard lets you assign which extension needs a Secondary connection to a specific NS1000.
4.6 KX-UT Programming (2) The KX-UT terminals Primary PBX assignment is set in the Virtual UTEXT32 Card Port Properties via a Wizard. System Setting (2) Primary PBX; Configuration Screen > Virtual Slot -> Primary PBX -> VUTEXT32 -> Secondary Setting 3) Ensure the desired UTxxx is not registered to the Primary PBX system. 4) Click Set Secondary to start the Wizard. The Secondary Port Wizard lets you assign which extension needs a Secondary connection to a specific NS1000.
4.6 KX-UT Programming (3) The KX-UT terminals Primary/Secondary PBX assignment is set in the Virtual UTEXT32 Card Port Properties via a Wizard. System Setting (3) Primary PBX; Configuration Screen > Virtual Slot -> Primary PBX -> VUTEXT32 -> Secondary Setting -> Set Secondary 5) Select the desired Secondary site and assign the UT Terminal to a free Secondary port. 6) The Secondary port is assigned and the number of free secondary ports reduces. 7) Click Execute. There must be sufficient Secondary ports assigned on the Secondary PBX for each UT Terminal requiring this feature.
4.6 KX-UT Programming (4) The KX-UT terminals Primary/Secondary PBX assignment can be confirmed as follows; KX-NT Setting(1) Primary/Secondary PBX; Configuration Screen > Virtual Slot -> Primary PBX -> VUTEXT32 -> Secondary Setting -> Set Secondary 8) Confirm the Primary/Secondary assignment on each PBX.
4.6 KX-UT Programming (5) The KX-UT terminals can then be registered to the Primary system; System Setting (7) UT Registration; Configuration Screen > Virtual Slot -> Primary PBX -> VUTEXT32 -> Registration 9) Register the UT terminal to the Primary PBX. When the KX-UT Terminal is registered for the first time, the IP Addresses of both the Primary and Secondary PBXs are uploaded to it. If the Primary PBX fails, then the UT can find the Secondary PBX.
4.6 KX-UT Programming (6) The KX-UT Keep-Alive parameters are set in the Virtual UT Extension Card Properties. Master PBX Private IP Network (Including VPN) Slave PBX Configuration Screen > Virtual Slot -> VUTEXT32 -> Card Property * [PERIODIC Inform] is the keep alive of UT terminal. For KX-UT Series 1) UT sends PERIDIC Inform packet to NS1000. 2) NS1000 reply to UT. 3) If the UT does not receive a reply packet from Primary PBX, then the UT look for Secondary PBX and reboots. NB : NT can not move back to the Primary system if the Primary system is running in Isolated Mode. : UT can be programmed with Primary/Secondary NS1000 in One-look environment only.
4.7 Data Migration to Backup-Master NB: It takes a few minutes from Logout for the data from the Master system to be copied to it s own internal CF Card before the data can then be uploaded to the Backup Master system. This means that the Survivability Functions are not available immediately after programming. Two Minutes after Master Logout will be sufficient for the feature to propagate throughout the One-Look network.
Thank you The END