Installation Manual 1549265793.2696

Installation Manual
Business Communication Server
Model No. KX-NSX1000

KX-NSX2000
Thank you for purchasing this Panasonic product.

Please read this manual carefully before using this product and save this manual for future use.
In particular, be sure to read "1.1 For Your Safety, page 20" before using this product.
KX-NSX series: PNMPR Software File Version 004.00000 or later
Manuals and supporting information are provided on the Panasonic Web site at:
https://panasonic.net/cns/pcc/support/pbx/
System Components
System Components
System Components for KX-NSX1000/KX-NSX2000
KX-NSX1000/KX-NSX2000
Category Model No. Description
Main Unit KX-NSX1000 Main Unit (Up to 1000 users)
KX-NSX2000 Main Unit (Up to 2000 users)
Activation Main KX-NSX101 Activate NSX1000 main features
Key Codes*1 Only for NSX1000 (NSX1000 System
Activation Key)
KX-NSX201 Activate NSX2000 main features
Only for NSX2000 (NSX2000 System
Activation Key)
KX-NSXP101 Ultimate Activation Key for Panasonic Terminal
Users
Maintenance KX-NSX2201 Activate Maintenance features (Capturing
Packet Trace/Expanding system logs/software
upgrade) (Maintenance annual Key)
KX-NSX6211 Activate Remote maintenance features
(Remote Maintenance annual Key)
User KX-NSUN001 Activate 1 Normal user (1-Normal User
Concept Activation Key)
KX-NSUN010 Activate 10 Normal user (10-Normal User
KX-NSUM001 Activate 1 Mobile user from Normal user (1-
Mobile User Concept Activation Key)
KX-NSUM100 Activate 100 Mobile user from Normal user
(100-Mobile User Concept Activation Key)
KX-NSUM500 Activate 500 Mobile user from Normal user
(500-Mobile User Concept Activation Key)
KX-NSUA001 Activate 1 Advanced user from Mobile user (1-
Advanced User Concept Activation Key)
2 Installation Manual
System Components

KX-NSUA010 Activate 10 Advanced user from Mobile user
(10-Advanced User Concept Activation Key)
3rd party SIP - KX-NSXS001 Activate 1 SIP-Phone for 3rd party (1-Channel
Extension SIP Extension Activation Key)
KX-NSXS010 Activate 10 SIP-Phone for 3rd party (10-
Channel SIP Extension Activation Key)
Panasonic KX-NSXN001 Activate 1 Communication Camera/
Peripheral IP-Doorphone (1-Channel Peripheral Device
Activation Key)
KX-NSXN010 Activate 10 Communication Camera/
IP-Doorphone (10-Channel Peripheral Device
Activation Key)
Channel expansion KX-NSXE001 Activate 1 IP-CS for expansion to 8ch
for IP-CS Distributed type of Activation key (1 IP-CS
Channel Expansion Activation Key)
KX-NSXE010 Activate 10 IP-CS for expansion to 8ch
Distributed type of Activation key (10 IP-CS
KX-NSXE050 Activate 50 IP-CS for expansion to 8ch
Distributed type of Activation key (50 IP-CS
IP-Trunk KX-NSXT001 Activate 1ch H.323 IP-GW or 1ch SIP-Trunk (1-
Channel IP Trunk Activation Key)
KX-NSXT010 Activate 10ch H.323 IP-GW or 10ch SIP-Trunk
(10-Channel IP Trunk Activation Key)
KX-NSXT050 Activate 50ch H.323 IP-GW or 50ch SIP-Trunk
(50-Channel IP Trunk Activation Key)
KX-NSXT100 Activate 100ch H.323 IP-GW or 100ch SIP-
Trunk (100-Channel IP Trunk Activation Key)
Installation Manual 3
System Components

Unified messaging KX-NSXU003 UM Message Backup (Activation Key for
Message Backup)
KX-NSXU004 2 way recording (Manager control) (Activation
Key for Two-way Recording)
Networking KX-NSXF006 Expansion GW connection for
NSX1000NSX2000 (Master unit) (Activation
Key for Expansion GW (Master))
Communication KX-NSA401 CA Operator Console (user) (Activation Key for
Assistant (CA) User CA Operator Console (1 user))
Option features KX-NSXF002 Built-in ACD Report, Announcement of waiting
number for queuing (Activation Key for Call
Centre)
KX-NSXF004 Multiple CTI Connection (Activation Key for
Multiple CSTA Connection)
KX-NSXF005 Address book LDAP connection (Activation Key
for LDAP)
KX-NSXF021 Announcement of waiting number for queuing
(Activation Key for Queue Announcement)
KX-NSXF022 Built-in ACD Report (Activation Key for Built-in
ACD report)
KX-NSXF008 Activate redundancy function (Activation Key
for Redundancy)
Physical Cards
DSP Card Slot KX-NS0110 VoIP DSP Card (S Type) (DSP S)

KX-NS0111 VoIP DSP Card (M Type) (DSP M)
KX-NS0112 VoIP DSP Card (L Type) (DSP L)
Storage Memory KX-NSX2135 Storage Memory (S Type) (Storage Memory S)
Card Slot
KX-NSX2136 Storage Memory (M Type) (Storage Memory M)
KX-NSX2137 Storage Memory (L Type) (Storage Memory L)
KX-NSX2138 Storage Memory (LL type) (Storage Memory
LL)
Other KX-A412 AC Power Cord
Accessories
*1 Note that the types of activation keys are subject to change without notice.
System Components for Expansion Gateways

The following table shows which activation keys are available for expansion gateways in a Multi-connection
network.
✓: Available
—: Not available
System Components
KX-NS300/KX-NS500/KX-NS700/KX-NS1000
Category Model No. Description Availability
Expansion KX-NS300 KX-NS300 as Expansion Gateway Unit ✓
Gateways
KX-NS500 KX-NS500 as Expansion Gateway Unit ✓
KX-NS1000xxG*3 NSX Expansion Box ✓
Activation KX-NSXF007 Expansion GW connection for NS300/500/700/1000
✓
Key (Expansion GW (NS))
Codes*1
KX-NSM102 2-Channel IP Trunk Activation Key (2 IP Trunk) —
KX-NSM201 1-Channel IP Softphone/IP Proprietary Telephone/
P-SIP Extension Activation Key (1 IP Softphone/IP —
PT/P-SIP)
KX-NSM205 5-Channel IP Softphone/IP Proprietary Telephone/
P-SIP Extension Activation Key (5 IP Softphone/IP —
PT/P-SIP)
KX-NSM210 10-Channel IP Softphone/IP Proprietary
Telephone/P-SIP Extension Activation Key (10 IP —
Softphone/IP PT/P-SIP)
KX-NSM220 20-Channel IP Softphone/IP Proprietary
Telephone/P-SIP Extension Activation Key (20 IP —
Softphone/IP PT/P-SIP)
KX-NSM501 1-Channel IP Proprietary Telephone/P-SIP Extension
—
Activation Key (1 IP PT/P-SIP)
KX-NSM505 5-Channel IP Proprietary Telephone/P-SIP Extension
—
Activation Key (5 IP PT/P-SIP)
KX-NSM510 10-Channel IP Proprietary Telephone/P-SIP
—
Extension Activation Key (10 IP PT/P-SIP)
KX-NSM520 20-Channel IP Proprietary Telephone/P-SIP
—
Extension Activation Key (20 IP PT/P-SIP)
KX-NSM701 1-Channel SIP Extension Activation Key (1 SIP
—
Extension)
—
Extension)
—
Extension)
—
Extension)
System Components
Category Model No. Description Availability

KX-NSE201 Activate 1 IP-CS for expansion to 8ch Distributed
—
type of Activation key (1 IP-CS channel expansion)
—
—
—
Activation KX-NSF990 Activation key for VoIP/Unified Message (UM)
—
Key feature (for KX-NS300)
Codes*1
KX-NSF991 Expansion Capacity for KX-NS700 (Expansion
—
Capacity)
KX-NSM005 31-50 IP Phone Capacity (Up to 50 IP Phone)*2 —
KX-NSM099 31-640 IP Phone Capacity (System MAX IP Phone)*2 —
KX-NSX910 51-100 IP Phone Capacity (Expansion from
—
NSM005)*2
—
NSM010)*2
—
NSM030)*2
KX-NSN101 Built-in Router (Built-in Router AK)*2 ✓
*1 Note that the types of activation keys are subject to change without notice.
*2 KX-NS1000 only
*3 "xx" indicates the area suffix (e.g., BX).
Physical Cards
KX-NS1000
FAX Card Slot KX-NS0106 FAX Interface Card (FAX)
DSP Card Slot KX-NS0110 VoIP DSP Card (S Type) (DSP S)
KX-NS0112 VoIP DSP Card (L Type) (DSP L)
Storage Memory Card KX-NS0135 Storage Memory (S Type) (Storage Memory S)
Slot
KX-NS0136 Storage Memory (M Type) (Storage Memory M)
KX-NS0137 Storage Memory (L Type) (Storage Memory L)
System Components

Free Slot KX-NS0180 2-Port Analogue Trunk / 2-Port SLT Card (SLC2/
LCOT2)
KX-NS0280 4-Port BRI / 2-Port SLT Card (SLC2/BRI4)
KX-NS0290CE PRI30 / 2-Port SLT Card (SLC2/PRI30)
KX-NS0290 PRI23 / 2-Port SLT Card (SLC2/PRI23)
KX-NS0130 Stacking Master Card (STACK-M)
Doorphone Slot KX-NS0161 Doorphone Interface Card (DOORPHONE)
KX-NS300/KX-NS320/KX-NS500/KX-NS520/KX-NS700/KX-NS720
DSP Card Slot KX-NS5110 VoIP DSP Card (S Type) (DSP S)*1
KX-NS5111 VoIP DSP Card (M Type) (DSP M)*2
KX-NS5112 VoIP DSP Card (L Type) (DSP L)*2
SD Memory Cards Slot KX-NS3134 SD Memory Card (XS Type) (SD XS)*3
KX-NS3135 SD Memory Card (S Type) (SD S)*3
KX-NS3136 SD Memory Card (M Type) (SD M)*3
Expansion Master Slot KX-NS5130 Expansion Master Card (EXP-M)*4
KX-NS7130 Expansion Master Card (EXP-M)*5
Trunk slot KX-NS5162 Doorphone Interface Card (DPH2)
KX-NS5180 6-port Analogue Trunk Card (LCOT6)
KX-NS5282 2-Port BRI Card (BRI2)
KX-NS5284 4-Port BRI Card (BRI4)
KX-NS5290 PRI Card (PRI23)
KX-NS5290CE PRI30 / E1 Trunk Card (PRI30/E1)
Extension Slot KX-NS5170 4-Port Digital Hybrid Extension Card (DHLC4)
KX-NS5171 8-Port Digital Extension Card (DLC8)
KX-NS5172 16-port Digital Extension Card (DLC16)
KX-NS5173 8-Port SLT Card (MCSLC8)
KX-NS5174 16-Port SLT Card (MCSLC16)
*1 For KX-NS300/KX-NS500/KX-NS700 only

*2 For KX-NS500/KX-NS700 only
*3 For KX-NS300 only
*4 For KX-NS300/KX-NS500 only
*5 For KX-NS700 only
System Components for Legacy Gateways

The following components are supported for legacy gateways connected to the KX-NS1000.
For details about supported optional service cards and Power Supply Units (PSUs), refer to the Installation
Manual of the corresponding PBX.
System Components

Legacy Gateways KX-TDE100 KX-TDE100 as Legacy Gateway Unit
KX-TDE200 KX-TDE200 as Legacy Gateway Unit
KX-TDA100 KX-TDA100 as Legacy Gateway Unit
KX-TDA100D KX-TDA100D as Legacy Gateway Unit
Legacy Gateway Cards KX-NS0132 Stacking Card for KX-TDE Series (STACK-S
(TDE))
KX-NS0132xxG*1 Stacking Card for KX-TDE Series (NSX Expansion
Box）
*1 "xx" indicates the area suffix (e.g., BX).

KX-NS0132xxG for NSX Expansion Box can be used only when a KX-NSX series server (software version 2.0 or later) is running
as a Master site. This card cannot be installed in a KX-NS1000 PBX.
Unsupported System Components for Legacy Gateways

The following components are not supported for legacy gateways.
Model No. Description
KX-TDA0105 Memory Expansion Card (MEC)
KX-TDA0191 4-Channel Message Card (MSG4)
KX-TDA0192 2-Channel Simplified Voice Message Card (ESVM2)
KX-TDA0194 4-Channel Simplified Voice Message Card (ESVM4)
KX-TDA0196 Remote Card (RMT)
KX-TDA0410 CTI Link Card (CTI-LINK)
KX-TDA0470 16-Channel VoIP Extension Card (IP-EXT16)
KX-TDA0480 4-Channel VoIP Gateway Card (IP-GW4)
KX-TDA0484 4-Channel VoIP Gateway Card (IP-GW4E)
KX-TDA0490 16-Channel VoIP Gateway Card (IP-GW16)
KX-TDE0110 16-Channel VoIP DSP Card (DSP16)
KX-TDE0111 64-Channel VoIP DSP Card (DSP64)
Equipment Compatibility for KX-NSX1000/KX-NSX2000

The NSX server supports the following equipment:
Cell Stations
DECT
• DECT 4-Channel IP Cell Station Unit Using a V-IPCS16 Card for DECT Portable Station (KX-NS0154CE)
System Components
DECT 6.0
• DECT 6.0 4-Channel IP Cell Station Unit Using a V-IPCS16 Card for DECT 6.0 Portable Station
(KX-NS0154)
Telephones
Panasonic Proprietary Telephones
• IP proprietary telephones (e.g., KX-NT300 series, KX-NT500 series, KX-NT600 series)
• IP Softphone by Panasonic
Note
In the installation methods of KX-NT630 and KX-NT680, KX-NT630 equals to KX-NT553, and
KX-NT680 equals to KX-NT556. KX-NT505 cannot be connected to the KX-NT600 series. The
KX-NT600 series does not support ECO mode. Read the KX-NT500 series as the KX-NT600 series in
this manual. The description of manual may be different from the actual LCD screen of KX-NT600
series.
• Portable stations (e.g., KX-TCA364, KX-WT115)
SIP Phones
• KX-HDV series SIP phones
• KX-TGP600 SIP cordless phones
• IP conferencing phones (e.g., KX-NT700)
• Mobile Softphone by Panasonic (KX-UCMA)
• Third party SIP phones (SIP hardphones/SIP softphones)
Other
• Communication IP camera (e.g., KX-NTV150)
• Video door phone (e.g., KX-NTV160)
Note
• For the equipment (e.g., Add-on Key Module, USB Module, Headset) that can be connected to a
particular telephone, refer to the telephone’s manual.
• For other equipment that can be connected to the NSX server, refer to "2.1.2 System Connection
Diagram".
• Operation of the KX-NTV series depends on the NSX server software file version and the firmware
version of the KX-NTV series. You can confirm the compatibility on the Panasonic Web site at:
https://panasonic.net/cns/pcc/support/pbx/
Trunk Adaptors
• E1 Trunk Adaptor (KX-NS8188)
• PRI Adaptor (KX-NS8290)
Equipment Compatibility for Expansion Gateways

KX-NS series PBXs can be connected to a KX-NSX1000 or KX-NSX2000 ("NSX server") over an IP
network. These KX-NS series PBXs are referred to as "expansion gateways".
You can connect the following PBXs to an NSX server as expansion gateways.
• KX-NS300
• KX-NS500
• KX-NS700
System Components
• KX-NS1000
If an expansion gateway is connected to an NSX sever, the following equipment is also supported.
Note
All software (includes KX-NSX series and KX-NS Expansion Gateway) should install the latest version.
Cell Stations
DECT
• 2-Channel Cell Station Unit Using a DHLC/DLC Card (PT-interface CS) for DECT Portable Station
(KX-TDA0155CE) (Except KX-NS1000.)
DECT 6.0
• DECT 6.0 2-Channel Cell Station Unit Using a DHLC/DLC Card (PT-interface CS) for DECT 6.0 Portable
Station (KX-TDA0155) (Except KX-NS1000.)
Telephones
• KX-NT300 series IP proprietary telephones
• Digital Proprietary Telephone (e.g., KX-DT300 series, KX-DT500 series) (Except KX-NS1000.)
• Analogue Proprietary Telephone (e.g., KX-T7700 series) (Except KX-NS1000.)
• DSS Console (e.g., KX-DT390, KX-DT590) (Except KX-NS1000.)
Other
• Single line telephones
Equipment Compatibility for Legacy Gateways

You can connect the following PBXs to a KX-NS1000 as legacy gateways.
• KX-TDE100, KX-TDE200, KX-TDE600, KX-TDE620
• KX-TDA100, KX-TDA200, KX-TDA600, KX-TDA620
• KX-TDA100D
Connecting legacy gateways expands the usage of legacy terminals and trunks.
If a legacy gateway is connected to a KX-NS1000, the following equipment is also supported.
Cell Stations
DECT
• 2-Channel Cell Station Unit Using a DHLC/DLC Card (PT-interface CS) for DECT Portable Station
(KX-TDA0155CE)
• 4-Channel Cell Station Unit Using a CSIF Card for DECT Portable Station (KX-TDA0156CE)
• 8-Channel High-density Cell Station Unit Using a DHLC/DLC Card (PT-interface CS) for DECT Portable
Station (KX-TDA0158CE)
DECT 6.0
Station (KX-TDA0155)
Station (KX-TDA0158)
Telephones
• Digital Proprietary Telephone (e.g., KX-DT300 series, KX-DT500 series)
System Components
• Portable Station (KX-TD7685, KX-TD7695, KX-TD7696)

• DSS Console (e.g., KX-DT390, KX-DT590)
• Analogue Proprietary Telephone (e.g., KX-T7700 series)
Notice
• In this manual, "NSX server" refers to the KX-NSX1000 and KX-NSX2000 Business Communication
Server.
• This NSX server supports SIP extensions. However, some PBX features (functions provided by the NSX
server) may not be available depending on the type of telephone.
• Under power failure conditions, the connected telephones may not operate. Please ensure that a
separate telephone, not dependent on local power, is available for emergency use.
• Prior to connection of this product, please verify that the intended operating environment is supported.
Satisfactory performance cannot be guaranteed for the following:
– interoperability and compatibility with all devices and systems connected to this product
– proper operation and compatibility with services provided by telecommunications companies over
connected networks
Note
• Some optional hardware, software, and features are not available in some countries/areas. Please
consult your certified Panasonic dealer for more information.
• KX-UT series SIP phones can be connected to an NSX server and used with limited functions as third
party SIP phones. (A SIP extension activation key is required.) Note that you cannot use some
features that are available when using a KX-NS series PBX.
• In this manual, the suffix of each model number (e.g., KX-NSX1000BX) is omitted unless necessary.
List of Abbreviations
• IP-PT → IP Proprietary Telephone
• PS → Portable Station
• SIP Extension → Extensions which use Session Initiation Protocol for communication.
• SLT → Single Line Telephone
• APT → Analogue Proprietary Telephone
• DPT → Digital Proprietary Telephone
• IP-CS → IP Cell Station unit
• P-SIP → Panasonic SIP Phones
– KX-HDV series/KX-TGP600
– KX-NTV150 (Communication IP camera)
– KX-NTV160 (Video door phone)
– KX-UCMA (Mobile Softphone)
Introduction
Introduction
This Installation Manual is designed to serve as an overall technical reference for the Panasonic Business
Communication Server, KX-NSX1000 and KX-NSX2000. It provides instructions for installing the hardware,
and programming the NSX server using Web Maintenance Console.
The Structure of this Manual

This manual contains the following sections:
Section 1 Safety Precautions
Provides important information intended to prevent personal injury and property damage.
Section 2 System Outline
Provides general information on the NSX server, including the system capacity and specifications.
Section 3 Information about the Activation Keys
Provides information on activation keys, including how to obtain activation keys.
Section 4 Installation
Describes the procedures to install the NSX server. Detailed instructions for planning the installation site,
optional service cards, and cabling of peripheral equipment are provided. Further information on system
expansion and peripheral equipment installation is included.
Section 5 Programming Information
Describes the installation procedure, structure, and functions of the Web Maintenance Console for
programming IP telephones and the NSX server. Further information on programming the NSX server
for use with SIP trunks and a VoIP network is included.
Section 6 Networking Information
Provides information about topics such as using the NSX server in a VoIP network, and the TCP ports
used by the NSX server.
Section 7 Troubleshooting
Provides information on the NSX server and telephone troubleshooting.
Section 8 Appendix
Provides information about NSX server Region Suffix Codes and Areas, System Prompt Languages,
and the revision history.
About the Other Manuals

Along with this Installation Manual, the following manuals are available:
Feature Manual
Describes all basic, optional and programmable features of the NSX server.
PC Programming Manual
Provides step-by-step instructions for performing system programming using a PC.
Operating Manual
Provides operating instructions for end users using terminal devices such as IP-PTs, SIP extensions,
and PSs.
About the software version of your NSX server

The contents of this manual apply to an NSX server with a certain software version, as indicated on the
cover of this manual. To confirm the software version of your NSX server, see "How do I confirm the
software version of the PBX or installed cards?" in "2.3 Frequently Asked Questions (FAQ)" of the PC
Programming Manual.
To update the software of your NSX server, see "5.1 System Control—Program Update" in the PC
Programming Manual.
Introduction
Trademarks
• The Bluetooth® word mark and logos are registered trademarks owned by the Bluetooth SIG, Inc., and
any use of such marks by Panasonic Corporation is under licence.
• Microsoft, Outlook, Excel, Active Directory, and Windows are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries.
• All other trademarks identified herein are the property of their respective owners.
• Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.
Introduction
Table of Contents
Table of Contents
1 Safety Precautions ............................................................................... 19
1.1 For Your Safety .............................................................................................................. 20
1.2 Important Safety Instructions ...................................................................................... 25
1.3 Precautions .................................................................................................................... 26
1.4 Data Security ................................................................................................................. 29
2 System Outline ..................................................................................... 31
2.1 Basic System Construction .......................................................................................... 32
2.1.1 System Configurations ................................................................................................. 32
2.1.2 System Connection Diagram ........................................................................................ 36
2.2 Optional Equipment ...................................................................................................... 38
2.2.1 Optional Equipment ...................................................................................................... 38
2.3 Specifications ................................................................................................................ 39
2.3.1 General Description ...................................................................................................... 39
2.3.2 System Capacity ........................................................................................................... 39
3 Information about the Activation Keys ............................................... 55
3.1 Information about the Activation Keys ....................................................................... 56
3.1.1 Type and Maximum Number of Activation Keys ........................................................... 56
3.1.2 Activation Key Code and Key Management System .................................................... 62
3.1.3 Using CTI Applications ................................................................................................. 63
4 Installation ............................................................................................. 65
4.1 Before Installation ......................................................................................................... 66
4.1.1 Before Installation ......................................................................................................... 66
4.2 Installation of the NSX server ...................................................................................... 68
4.2.1 Unpacking ..................................................................................................................... 68
4.2.2 Names and Locations ................................................................................................... 68
4.2.3 Opening/Closing the Top Cover .................................................................................... 70
4.2.4 Frame Earth Connection .............................................................................................. 73
4.2.5 Installing/Removing the Optional Service Cards .......................................................... 73
4.2.6 Installing/Removing an Expansion Storage Memory Card ........................................... 76
4.2.7 Types of Connectors ..................................................................................................... 81
4.2.8 19-inch Rack Mounting ................................................................................................. 81
4.3 The Mother Board and Expansion Cards .................................................................... 82
4.3.1 Mother Board ................................................................................................................ 82
4.3.2 Expansion Storage Memory Card (KX-NSX2135, KX-NSX2136, KX-NSX2137,
KX-NSX2138) ............................................................................................................... 86
4.3.3 DSP S Card (KX-NS0110), DSP M Card (KX-NS0111), DSP L Card (KX-NS0112) .... 87
4.4 Virtual Cards .................................................................................................................. 88
4.5 Connection of Peripherals ............................................................................................ 89
4.6 LAN Connection ............................................................................................................ 90
4.6.1 LAN Connection for the Main Unit ................................................................................ 90
4.6.2 LAN Connections for IP Telephones ............................................................................. 92
4.7 Starting the NSX server ................................................................................................ 93
5 Programming Information ................................................................... 97
5.1 Overview of Web Maintenance Console ..................................................................... 98
5.2 PC Connection ............................................................................................................... 98
5.3 Starting Web Maintenance Console .......................................................................... 101
5.4 Programming the NSX server .................................................................................... 103
5.4.1 Easy Setup Wizard ..................................................................................................... 103
Table of Contents
5.4.2 After the Easy Setup Wizard has been Completed .................................................... 108
5.4.3 Enabling the DHCP Server Feature ........................................................................... 109
5.4.4 Installing the Virtual IP Cards to the NSX server ........................................................ 109
5.4.5 Installing Additional Activation Keys ........................................................................... 109
5.4.6 Configuration of the Activation Keys ........................................................................... 110
5.5 Programming a Multi-connection Network ............................................................... 110
5.6 Programming an H.323 QSIG Network ...................................................................... 112
5.6.1 Assigning the Hunt Pattern ......................................................................................... 113
5.6.2 Programming the Address Translation Table .............................................................. 113
5.6.3 Programming the Network Settings ............................................................................ 114
5.7 Programming SIP Trunks ............................................................................................ 116
5.8 Assigning Networking Information to IP Telephones .............................................. 118
5.8.1 Assigning IP Addressing Information .......................................................................... 118
5.8.2 Setting VLAN Parameters .......................................................................................... 130
5.8.3 Setting LLDP Parameters ........................................................................................... 131
5.8.4 Setting Diffserv Parameters ........................................................................................ 135
5.8.5 Configuration of IP Ports ............................................................................................ 136
5.8.6 ECO mode (KX-NT500 series only) ........................................................................... 140
5.9 Registering IP Telephones ......................................................................................... 141
5.9.1 Registering IP Telephones .......................................................................................... 141
5.9.2 De-registering IP Telephones ..................................................................................... 144
5.9.3 Installing SIP Phones at a Remote Site with an External SBC ................................... 145
5.9.4 Installing IP Phones at a Remote Site with a Built-in Media Relay Gateway ............. 147
5.9.5 Encryption Settings for Internal Calls ......................................................................... 151
5.10 Configuration of Users ............................................................................................... 153
5.11 Programming E-mail Integration for UM Voice/Fax Messages ............................... 158
6 Networking Information ..................................................................... 163
6.1 Information about Using an IP Network .................................................................... 164
6.1.1 Using a VoIP Network with the NSX server ................................................................ 164
6.1.2 DHCP (Dynamic Host Configuration Protocol) Server ............................................... 166
6.1.3 VLAN (Virtual LAN) ..................................................................................................... 167
6.1.4 Jitter Buffer ................................................................................................................. 168
6.1.5 Voice Activity Detection (VAD) .................................................................................... 169
6.1.6 Network Configuration ................................................................................................ 169
6.1.7 Network Devices ......................................................................................................... 173
6.1.8 QoS (Quality of Service) ............................................................................................. 173
6.1.9 Network Time Protocol (NTP) ..................................................................................... 174
6.2 H.323 Trunks ................................................................................................................ 174
6.2.1 Avoid Multiple IP Networks ......................................................................................... 174
6.2.2 Gatekeeper ................................................................................................................. 175
6.2.3 Bandwidth Assessment .............................................................................................. 175
6.2.4 Virtual VoIP Gateway Card Specifications .................................................................. 178
6.3 SIP Trunks .................................................................................................................... 178
6.3.1 IP Telephony Service .................................................................................................. 178
6.3.2 SIP Requirements ...................................................................................................... 181
6.3.3 Router Requirements ................................................................................................. 181
6.3.4 Bandwidth Requirements ........................................................................................... 182
6.3.5 Virtual SIP Trunk Card Specifications ......................................................................... 182
6.4 Types of PBX Networks .............................................................................................. 183
6.4.1 Multi-connection Network ........................................................................................... 183
6.4.2 Multi-connection Networking Survivability .................................................................. 188
6.4.3 Information about Expansion Gateways ..................................................................... 190
6.4.4 H.323 QSIG Network .................................................................................................. 192
6.4.5 Working with Multiple PBX Networks ......................................................................... 193
Table of Contents
6.5 Port Security ................................................................................................................ 194

6.6 Network Security ......................................................................................................... 197
6.6.1 Firewall ....................................................................................................................... 197
6.6.2 Firewall—Packet Filtering ........................................................................................... 198
6.6.3 Firewall—Stateful Packet Inspection .......................................................................... 199
6.7 Hot Standby ................................................................................................................. 199
7 Troubleshooting ................................................................................. 213
7.1 Troubleshooting .......................................................................................................... 214
7.1.1 Installation .................................................................................................................. 214
7.1.2 Operation .................................................................................................................... 216
7.1.3 Restarting the NSX server .......................................................................................... 217
7.1.4 Troubleshooting by Error Log ..................................................................................... 218
8 Appendix ............................................................................................. 221
8.1 NSX server Region Suffix Codes and Areas ............................................................. 222
8.2 System Prompt Languages ........................................................................................ 224
8.3 Revision History .......................................................................................................... 225
8.3.1 PNMPR Software File Version 002.00xxx .................................................................. 225
Table of Contents
Section 1
Safety Precautions
This section provides important information intended to

prevent personal injury and property damage.
1.1 For Your Safety
1.1 For Your Safety

To prevent personal injury and/or damage to property, be sure to observe the following safety precautions.
The following symbols classify and describe the level of hazard and injury caused when this unit is
operated or handled improperly.
This notice means that misuse could result in death

WARNING or serious injury.
This notice means that misuse could result in injury

CAUTION or damage to property.
The following types of symbols are used to classify and describe the type of instructions to be
observed.
This symbol is used to alert users to a specific operating procedure that must not be
performed.
This symbol is used to alert users to a specific operating procedure that must be followed in
order to operate the unit safely.
Notice
Panasonic assumes no responsibility for injuries or property damage resulting from failures arising out of
improper installation or operation inconsistent with this documentation.
WARNING
For All Telephone Equipment
• Do not install the product in any other way than described in relevant manuals.
• Do not install the product in a place exposed to rain or moisture, or a place where water, oil, or other
liquids can drip or splash onto on the product. Such conditions can lead to fire or electric shock, and may
impair the performance of the product.
• Do not install the system in the following locations:
a. Areas where shocks or vibrations are frequent or strong. Such activity may lead to the product falling
over and causing injury, or may impair the product’s performance.
b. Areas with high amounts of dust. High amounts of dust can lead to fire or electric shock, and impair
the performance of the product.
1.1 For Your Safety
• Do not place the product on an unstable or uneven surface. If the product were to fall over, it may cause
injury or damage to the product.
• Do not supply power to a combination of devices that exceeds the total rated capacity of the wall outlets
or extension cables used. If outlets, power strips, extension cords, etc. are used in a manner that exceeds
their rated capacity, they emit large amounts of heat, which could cause a fire.
• The product must only be installed and serviced by qualified service personnel. The product should be
used as-is from the time of purchase; it should not be disassembled or modified. Disassembly or
modification can cause a fire, electric shock, or damage to the product.
• Follow all warnings and instructions marked on the product.
• Small objects, such as the hook clip, pose a choking hazard. Keep small objects out of reach of children.
• Products that require a power source should only be connected to the type of electrical power supply
specified on the product label. If you are not sure of the type of power supply to your home, consult your
dealer or local power company.
• For safety purposes some products are equipped with an earthed plug. If you do not have an earthed
outlet, please have one installed. Do not bypass this safety feature by tampering with the plug.
• Unplug the product from the wall outlet and have it serviced by qualified service personnel in the following
cases:
a. When the power supply cord or plug is damaged or frayed.
b. If liquid has been spilled into the product.
c. If the product has been exposed to rain or water.
d. If the product does not operate according to the operating instructions. Adjust only the controls that
are explained in the operating instructions. Improper adjustment of other controls may result in
damage and may require service by a qualified technician to restore the product to normal operation.
e. If the product has been dropped or the cabinet has been damaged.
f. If product performance deteriorates.
For the Server
• Do not insert foreign objects of any kind into this unit, as they may touch dangerous voltage points or
short out parts that could result in a fire or electric shock.
• Do not pull, bend, rest objects on, or chafe the power cord and plug. Damage to the power cord or plug
can cause fire or electric shock.
• Do not attempt to repair the power cord or plug. If the power cord or plug is damaged or frayed, contact
an authorised Panasonic Factory Service Centre for a replacement.
• Do not mount the unit on a wall; it is designed to be mounted only on a 19-inch rack. If it is mounted on a
wall, it may fall and cause serious injury.
1.1 For Your Safety
• When mounting the unit on a 19-inch rack, only use the 19-inch rack mounting equipment (attachment
bracket, screws) included with the unit.
• If damage to the unit exposes any internal parts, disconnect the power supply cord immediately and
return the unit to your dealer.
• To prevent fires, electric shock, injury, or damage to the unit, be sure to follow these guidelines when
performing any wiring or cabling:
a. Before performing any wiring or cabling, unplug the unit's power cord from the outlet. After
completing all wiring and cabling, plug the power cord back into the outlet.
b. When laying cables, do not bundle the unit's power cord with the power cords of other devices.
c. Do not place any objects on top of the cables connected to the unit.
d. When running cables along the floor, use protectors to prevent the cables from being stepped on.
e. Do not run any cables under carpeting.
• Unplug this unit from the AC outlet if it emits smoke, an abnormal smell or makes unusual noise. These
conditions can cause fire or electric shock. Confirm that smoke has stopped and contact an authorised
Panasonic Factory Service Centre.
• The earthing wire of the AC cable has an effect against external noise and lightning strikes, but it may not
be enough to protect the unit and to ensure electromagnetic compatibility. A permanent connection
between earth and the earth terminal of the unit must be made.
• Proper earthing (connection to earth) is very important to reduce the risk to the user of electrocution or to
protect the unit from the bad effects of external noise in the case of a lightning strike. (See "4.2.4 Frame
Earth Connection".)
• Plug the power cord firmly into an AC outlet. Otherwise, it can cause fire or electric shock.
• Be careful not to drop any components. Dropping components may damage them or cause an injury.
• Make sure that the AC outlet is properly earthed, then securely connect the 3-pin AC plug including the
earthed pin.
• A lithium battery is used in the mother board. There is a risk of explosion if the battery is replaced with an
incorrect type. Dispose of used batteries according to the manufacturer’s instructions.
CAUTION
• The product should be kept free of dust, moisture, high temperature (more than 40 ℃) and vibration, and
should not be exposed to direct sunlight.
• Unplug the product from the wall outlet before cleaning. Wipe the product with a soft cloth. Do not clean
with abrasive powders or with chemical agents such as benzine or thinner. Do not use liquid cleaners or
aerosol cleaners.
For the Server
1.1 For Your Safety
• Do not install the system in the following locations:

a. In direct sunlight and hot, cold, or humid places. (Temperature range: 0 ℃ to 40 ℃)
b. Areas where sulphuric gases may be present, such as near thermal springs.
c. Near devices that generate high frequencies, such as sewing machines or electric welders.
d. Locations where other objects will obstruct the area around the unit. Be especially careful to leave at
least 5 cm to the sides of the unit for ventilation.
e. Locations where condensation can occur.
• When the unit is mounted on a 19-inch rack, allow space of at least 5 cm to the sides of unit and at least
10 cm to the rear of the unit for ventilation of the fan.
• Do not block the vents around the fan with cables or other objects.
• When installing or removing the Expansion Storage Memory Card, do not put pressure on any parts of
the mother board. Doing so may result in damage to the unit.
• When installing or removing the optional service cards, do not put pressure on any parts of the mother
board. Doing so may result in damage to the unit.
• The Storage Memory Cards contain software for all the processes of the unit and all the customer data.
Therefore, do not allow unauthorised access to prevent data leakage.
• Once you have started the unit, if you unplug the unit, do not initialise it again as described in "System
Initialisation Procedure". Otherwise, your programmed data will be cleared. To restart the unit, refer to
"7.1.3 Restarting the NSX server".
• Do not touch the CPU, heat sink, and the Storage Memory Cards during maintenance. Those parts may
get hot.
• Do not replace the CPU, heat sink, the Storage Memory Cards, and cooling fan.
• The Server parts are not hot-swappable. Do not replace parts or cables when the power of the Server is
on.
• Before touching the unit (Server, cards, etc.), discharge static electricity by touching ground or wearing an
earthing strap. Failure to do so may cause the unit to malfunction due to static electricity.
• The power supply cord is used as the main disconnect device. Ensure that the AC outlet is located near
the equipment and is easily accessible.
• Slots and openings in the back and right side of the cabinet are provided for ventilation; to protect it from
overheating, these openings must not be blocked or covered. The openings should never be blocked by
placing the unit on a bed, sofa, rug, or other similar surface while in use. The unit should never be placed
near or over a radiator or other heat source. This unit should not be placed in a sealed environment
unless proper ventilation is provided.
• When this unit is no longer in use, make sure to detach it from the rack.
• A certified power supply cord has to be used with this equipment. The relevant national installation and/or
equipment regulations shall be considered. A certified power supply cord not lighter than ordinary
1.1 For Your Safety
polyvinyl chloride flexible cord according to IEC 60227 (designation H05VV-F 3G 0.75 mm2) shall be
used.
• When the unit is mounted on a 19-inch rack, make sure that the installation of the unit does not cause the
temperature of the rack to exceed its limit.
• Make sure to install all necessary optional service cards in the unit before performing the rack mounting
procedure. If it is necessary to install or remove a card, make sure to remove the unit from the rack before
installing or removing the card.
• When opening the top cover, the power switch must be turned off.
• For safety reasons, close the top cover and tighten the screws before operating the unit.
• If the unit is not installed properly using the securing correct methods, the unit may fall causing serious
damage.
• Do not open the top cover soon after turning off the power. There is a risk of receiving burns.
• It is strongly recommended to use TLS encrypted communication when the PC is accessing the unit via
the Internet. To use TLS encryption, routers must have a port set up for https communication.
• Support TLS versions are TLS 1.1 and TLS.1.2.
• To prevent data leakage, render the Storage Memory Cards physically unusable before disposal.
• Avoid using the same AC outlet for computers and other office equipment, as noise generated by such
equipment may hamper system performance or interrupt the system.
• Unplug the system from its power source when wiring, and plug the system back in only after all wiring is
completed.
• When installing or removing the Expansion Storage Memory Card, the power switch must be turned off
and the AC power cord must be unplugged.
• When installing or removing the optional service cards, the power switch must be turned off.
• For earthing wire, green-and-yellow insulation is required, and the cross-sectional area of the conductor
must be more than 0.75 mm2 or 18 AWG.
• If the heat sensor inside the Server detects abnormally high temperatures, power supply to the unit will be
forcefully stopped. In that case, turn off the Server using the power switch, then turn it on again.
• If the feature is enabled, an error log will indicate when abnormal fan operation is detected in the system
heat control. In that case, consult the system administrator to replace of the fan.
• The operating conditions (e.g., CPU usage percentage, memory usage, and Storage Memory Card
product life) are monitored, and monitoring results will be notified by methods such as the error log, MIB,
and system alarm. For details, consult your system administrator.
Notice
• Read and understand all instructions.
For the Server

• Keep the unit away from heating appliances and devices that generate electrical noise such as
fluorescent lamps, motors and televisions. These noise sources can interfere with the performance of
the unit.
• When the unit is connected to an AC power source, we strongly recommend using an Uninterruptible
Power Supply (UPS) to prevent errors due to a sudden power failure.
• Graphical symbol " " on the nameplate means alternating current.
1.2 Important Safety Instructions
1.2 Important Safety Instructions

When using your telephone equipment, basic safety precautions should always be followed to reduce the
risk of fire, electric shock and injury to persons, including the following:
• Do not use the unit near water, for example, near a bathtub, wash bowl, kitchen sink, or laundry tub, in a
wet basement, or near a swimming pool.
• Avoid using wired telephones during an electrical storm. There is a remote risk of electric shock from
lightning.
• Do not use a telephone in the vicinity of a gas leak to report the leak.
• Rack Mount Instructions—The following or similar rack-mount instructions are included with the
installation instructions:
a. Elevated Operating Ambient—If installed in a closed or multi-unit rack assembly, the operating
ambient temperature of the rack environment may be greater than room ambient. Therefore,
consideration should be given to installing the equipment in an environment compatible with the
maximum ambient temperature (Tma) specified by the manufacturer.
b. Reliable Earthing—Reliable earthing of rack-mounted equipment should be maintained. Particular
attention should be given to supply connections other than direct connections to the branch circuit
(e.g., use of power strips).
SAVE THESE INSTRUCTIONS
1.3 Precautions
1.3 Precautions
For users in the United Kingdom
FOR YOUR SAFETY, PLEASE READ THE FOLLOWING TEXT CAREFULLY.
This appliance is supplied with a moulded three-pin mains plug for your safety and convenience. Should the
fuse need to be replaced, please ensure that the replacement fuse is of the same rating and that it is
approved by ASTA or BSI to BS1362.
Check for the ASTA mark or the BSI mark on the body of the fuse.
If the plug contains a removable fuse cover, you must ensure that it is refitted when the fuse is replaced. If
you lose the fuse cover, the plug must not be used until a replacement cover is obtained. A replacement
fuse cover can be purchased from your local Panasonic dealer.
IF THE FITTED MOULDED PLUG IS UNSUITABLE FOR THE AC OUTLET IN YOUR PREMISES, THEN
THE FUSE SHOULD BE REMOVED AND THE PLUG CUT OFF AND DISPOSED OF SAFELY. THERE IS
A DANGER OF SEVERE ELECTRICAL SHOCK IF THE CUT-OFF PLUG IS INSERTED INTO ANY 13
AMP SOCKET.
WARNING
This appliance must be earthed.
How to replace the fuse: Open the fuse compartment with a screwdriver and replace the fuse and fuse
cover.
The equipment must be connected to direct extension lines, and a payphone should not be connected as an
extension.
999 and 112 can be dialled on the apparatus after accessing the Exchange line for the purpose of making
outgoing calls to the BT emergency services.
During dialling, this apparatus may tinkle the bells of other telephones using the same line. This is not a fault
and we advise you not to call the Fault Repair Service.
For users in Germany only

• Machine Noise Information Ordinance, 3rd GPSGV: The highest sound pressure level is 70 dB (A) or less
according to EN ISO 7779.
• This equipment is not for use at video display work stations according to BildscharbV.
For users in New Zealand only
• This equipment shall not be set to make automatic calls to the Telecom ‘111’ Emergency Service.
• The grant of a Telepermit for any item of terminal equipment indicates only that Telecom has accepted
that the item complies with minimum conditions for connection to its network. It indicates no endorsement
of the product by Telecom, nor does it provide any sort of warranty. Above all, it provides no assurance
1.3 Precautions
that any item will work correctly in all respects with another item of Telepermitted equipment of a different
make or model, nor does it imply that any product is compatible with all of Telecom’s network services.
• This equipment is not capable, under all operating conditions, of correct operation at the higher speeds
for which it is designed. Telecom will accept no responsibility should difficulties arise in such
circumstances.
• Some parameters required for compliance with Telecom’s Telepermit requirements are dependent on the
equipment (Server) associated with this modem. In order to operate within the limits for compliance with
Telecom’s Specifications, the associated Server equipment shall be set to ensure that modem calls are
answered between 3 and 30 seconds of receipt of ringing.
• Using the toll services of a company other than Telecom:
If the Server is set up to use the toll services of a company other than Telecom, the telephone numbers
dialled from the Caller Display listings within the Server will be directed through the toll services of the
other company because the telephone numbers include the toll access digit and area code digit. A toll
charge may be incurred. Please check with the toll carrier concerned.
• APPLICABLE ONLY TO TELECOM CUSTOMERS WHO HAVE AUTOMATIC ACCESS TO OTHER
CARRIERS FOR TOLL CALLS
When calling back a number from the Caller ID list, all numbers prefixed with "0 + AREA CODE" will be
automatically forwarded to your toll carrier. This includes numbers in your local calling area. The zero +
area code should either be removed when calling back local numbers, or check with your toll carrier that a
charge will not be levied.
• All persons using this device for recording telephone conversations shall comply with New Zealand law.
This requires that at least one party to the conversation is to be aware that it is being recorded. In
addition, the principles enumerated in the Privacy Act 1993 shall be complied with in respect to the nature
of the personal information collected, the purpose for its collection, how it is used, and what is disclosed
to any other party.
• The SLT ports are not specifically designed for 3-wire-connected equipment. 3-wire-connected equipment
might not respond to incoming ringing when attached to these ports.
For users in Australia only

• No External TRC Terminal is provided due to an Internal Link between PE and TRC.
For users in Taiwan only
• Lithium batteries can be found in the circuit boards of the mother board of the Server.
Notice
Regarding removing or replacing a battery in the circuit board, consult your dealer.
Note
• When disposing of any of the above products, all batteries must be removed. Follow the applicable
laws, regulations, and guidelines in your country/area regarding disposal of batteries.
• When replacing a battery, use only the same battery type, or an equivalent recommended by the
battery manufacturer.
1.3 Precautions
For Canada Users

Information
This Class B digital apparatus complies with Canadian ICES-003.
Caution:
Users should not attempt to make such connections themselves, but should contact the appropriate electric
inspection authority, or electrician, as appropriate.
Notice:
This product meets the applicable Innovation, Science and Economic Development Canada technical
specifications. This is confirmed by the registration number. The abbreviation, IC, before the registration
number signifies that registration was performed based on a Declaration of Conformity indicating that
Industry Canada technical specifications were met. It does not imply that Industry Canada approved the
equipment.
Renseignements
Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.
Avertissement:
L’utilisateur ne doit pas tenter de faire ces raccordements lui-même; il doit avoir recours à un service
d’inspection des installations électriques, ou à un électricien, selon le cas.
Avis:
Le présent produit est conforme aux spécifications techniques applicables d'Innovation, Sciences et
Développement économique Canada. Cette conformité est confirmée par le numéro d’enregistrement. Le
sigle IC,placé devant le numéro d’enregistrement, signifie que l’enregistrement s’est effectué conformément
à une déclaration de conformité et indique que les spécifications techniques d’Industrie Canada ont été
respectées. Il n’implique pas qu’Industrie Canada a approuvé le materiel.
1.4 Data Security
1.4 Data Security

In order to use the Server safely and correctly, the Security Requirements below must be observed. Failure
to do so may result in:
• Loss, leakage, falsification or theft of user information.
• Illegal use of the Server by a third party.
• Interference or suspension of service caused by a third party.
What is User Information?

User Information is defined as:
1. Information stored on the Storage Memory Cards:
System data, error data and activation key files.
2. Information sent from the Server to a PC or a USB memory device:
System data, sound files for MOH (Music on Hold) and OGM (Outgoing Messages), and activation key
files.
Requirements
1. The Storage Memory Cards contain software for all the processes of the Server and all the customer
data.
Therefore, do not allow unauthorised access to prevent data leakage.
2. Always make backups of data stored on the Storage Memory Cards and/or perform regular system
data backups to a USB memory device or a NAS.
For details about making backups of data automatically, refer to "6.1.3 Tool—System Data Backup—
Auto Backup" in the PC Programming Manual.
For details about making backups of data stored on the Storage Memory Cards, refer to "7.2.2 Utility—
File—File Transfer PBX to PC" in the PC Programming Manual.
For details about backing up the system data to a USB memory device or a NAS, refer to "6.1 Tool—
System Data Backup" in the PC Programming Manual.
3. To prevent illegal access from the Internet, activate a Firewall.
4. To avoid unauthorised access and possible abuse of the Server, we strongly recommend:
a. Keeping the password secret.
b. Selecting a complex, random password that cannot be easily guessed.
c. Changing your password regularly.
5. Perform the following when sending the Server for repair or handing it over to a third party.
a. Make a backup of data stored on the Storage Memory Cards.
b. Using a formatter, format the Storage Memory Cards so that information cannot be retrieved from
it.
6. To prevent data leakage, render the Storage Memory Cards physically unusable before disposal.
7. When user information is sent from the Server to a PC or a USB memory device, the confidentiality of
that information becomes the responsibility of the customer. Before disposing of the PC or the USB
memory device, ensure that data cannot be retrieved from it by formatting the hard disk and/or
rendering it physically unusable.
1.4 Data Security
Section 2
System Outline
This section provides general information on the NSX

server, including the system capacity and specifications.
2.1 Basic System Construction
2.1 Basic System Construction

2.1.1 System Configurations
Main Unit
The main unit contains a mother board for controlling PBX functions (functions provided by the NSX server).
Stand-alone System
A single NSX server can be used as a stand-alone system. A single NSX server used as a stand-alone
system controls all terminals, trunks, and applications.
Multi-Connection Network
*1*2
A KX-NS series PBX connected to an NSX server functions as an expansion gateway to establish a
distributed networked system using a private IP network ("Multi-connection network").
Up to 31 KX-NS series PBXs can be connected to an NSX server, which controls the other PBXs as
expansion gateways.
Up to 31 legacy gateways or expansion units can be connected to expansion gateways to expand the usage
of legacy terminals and trunks.
The following table shows the conditions for connecting legacy gateways or expansion units to an expansion
gateway.
Maximum Number
Maximum Number
Expansion Gateway Available Legacy Gateway or in Multi-
per 1 Expansion
Type Expansion Unit connection
Gateway
Network
KX-TDA100/KX-TDA200/
KX-TDA600/KX-TDA620/
KX-NS1000 KX-TDE100/KX-TDE200/ 2
KX-TDE600/KX-TDE620
*3
KX-TDA100D 31
KX-NS700 KX-NS720
*4
3
KX-NS500 KX-NS520 3
KX-NS300 KX-NS320 3
LAN
Site #2
Expansion Gateway
Site #3
IP Networking Expansion Gateway
Site #1
Legacy Gateway
Site #4
:
NSX server :
Expansion Gateway
Expansion Unit
Expansion Unit
To establish a Multi-connection network, the following activation keys are necessary:

• KX-NSXF006: Activation Key for Expansion GW (Master) (Installed in the NSX server.)
• KX-NSXF007: Expansion GW connection for NS300/500/700/1000 (Installed in each expansion gateway.)
For more information, refer to 3.1.1 Type and Maximum Number of Activation Keys.
For details about connecting legacy gateways and expansion units, refer to the Installation Manual of the
corresponding expansion gateway.
Simplified Isolated Mode

If communication with the NSX server is lost, expansion gateways can continue limited communication
services independently.
For details, see "Simplified Isolated Mode".
Supported System Components for Expansion Gateways

The following components and features are available only when an expansion gateway is connected to the
NSX server in a Multi-connection network.
For details, refer to the Installation Manual for the corresponding expansion gateway.
(Equipment)
– 2-Channel Cell Station Unit Using a DHLC/DLC Card (PT-interface CS) for DECT Portable Station
(KX-TDA0155CE) (Except KX-NS1000.)
– DECT 6.0 2-Channel Cell Station Unit Using a DHLC/DLC Card (PT-interface CS) for DECT 6.0 Portable
Station (KX-TDA0155) (Except KX-NS1000.)
– Single line telephones
– Digital Proprietary Telephone (e.g., KX-DT300 series, KX-DT500 series) (Except KX-NS1000.)
– Analogue Proprietary Telephone (e.g., KX-T7700 series) (Except KX-NS1000.)
– DSS Console (e.g., KX-DT390, KX-DT590) (Except KX-NS1000.)
– Doorphone, Door opener, External sensor
Feature
• Power failure transfer (PFT)
*1 A software upgrade is required for all KX-NS series PBX. For details, refer to "5.5 Programming a Multi-connection Network".
*2 Storage Memory Card (2 G/8 G/16 G/32 G) is required for a KX-NS1000 PBX and 1 SD card is required for a KX-NS300.
*3 If a KX-TDA100D is connected as a legacy gateway, a second legacy gateway must also be a KX-TDA100D.
*4 An activation key (KX-NSF991) is required to connect a KX-NS720 to a KX-NS700.
H.323 QSIG network

The NSX server can be connected to other PBXs (e.g., KX-NS series PBXs, KX-TDE series PBXs) via an
H.323 QSIG connection.
An H.323 QSIG network is preferable if strict resource separation between sites is necessary. Although it is
possible to reserve certain resources for certain extension users in a Multi-connection network, the default is
to share resources. On the other hand, in a QSIG network, resources are not available to extension users of
other PBXs without explicit programming.
Programming and configuring an H.323 QSIG network is much more complex than a Multi-connection
network. It is also possible to connect a Multi-connection network to other PBXs via QSIG. In an H.323
QSIG network, the Multi-connection network appears as one PBX. The NSX server represents the Multi-
connection network.
For details about programming the H.323 QSIG network, refer to "5.6 Programming an H.323 QSIG
Network".
For details about H.323 QSIG network, refer to "4.2.2 Network Type Comparison" in the Feature Manual.
Remote maintenance through Panasonic Cloud

The KX-NSX1000/KX-NSX2000 supports an easy and secure remote maintenance by using the KMS server
and Panasonic Cloud Platform that is remote maintenance server provided by Panasonic. A system
administrator can access end users' NSX server in remote sites and perform maintenance or
troubleshooting.
An activation key (KX-NSX6211) is required for this service. This activation key is valid for 1 year and needs
to be installed every year.
Mobile Softphone by Panasonic

Mobile Softphone can receive push notifications. To use this feature, the following settings are necessary:
– A preferred DNS IP address specified manually through Web Maintenance Console. (→ 28.1 Network
Service—[1] IP Address/Ports—Basic Settings—DNS Setting—Preferred DNS IP Address)
– If a proxy server is used on the IP network where the PBX is installed, proxy settings are required in Web
Maintenance Console. (→ 28.3.5 Network Service—[3-5] Client Feature—HTTP)
2.1.2 System Connection Diagram

[Mobile]
Smartphone
Remote
[Remote Office]
maintenance Cellular NW
Server
KX-NT series
IP Network/
ITSP
PSTN/ 3rd party SIP phone
ISDN
Edge Router
PRI
E1 Trunk Adaptor/
PRI Adaptor
SBC Device
Analogue line
BRI
Networking
PRI
(T1/E1, E&M, ISDN-Qsig)
KX-NSX1000 KX-NSX1000
(Secondary) (Primary) UPS
KX-NT series
KX-HDV series
KX-TGP600 series
(Expansion gateways) KX-NT series

PS
IP-CS
KX-NS1000
KX-NTV series
KX-NS300/500/700 Legacy Gateway Softphone

NS320/520/720
3rd party
SIP phone
Application server
DPT/APT SLT/FAX Door phone MOH/BGM IP-CS/PS Web Maintenance
& Opener Console
USB Memory Device

Storage Memory
DSP S
(KX-NS0110) (KX-NSX2135)
DSP M (KX-NSX2136)
(KX-NS0111)
Uninterruptible Power (KX-NSX2137)
DSP L
Supply (UPS) (KX-NS0112) (KX-NSX2138) SIP Phone IP-CS PS
Station Message LAN

Detail Recording (SMDR)
Virtual Slot
V-SIPGW128 IP-PT IP Softphone PC CTI Server
V-IPGW128
PC
V-IPEXT128
Private IP Router V-SIPEXT128 Trunk Adaptor Trunk Adaptor

Network
V-IPCS16
ISDN PRI Line E1 Line
WAN
(Digital Trunk) (Digital Trunk)
ITSP DCE Router

Network*1 (e.g., ADSL Telephone Company
Modem)*2
Mountable Equipment
*1 ITSP: Internet Telephony Service Provider

*2 DCE: Data Circuit Terminating Equipment
2.2 Optional Equipment
2.2 Optional Equipment

2.2.1 Optional Equipment
Model No. Model Name Description
KX-NS0110 VoIP DSP Card (S Type) (DSP S) A DSP card is a digital signal processor card
with DSP resources that can be used for VoIP
calls, conferences, the Unified Messaging
feature, and the DISA/OGM feature. The DSP
cards are compliant with ITU-T G.729A and
G.711 codec methods.
Depending on the amount of your DSP
resource needs, DSP S, DSP M, or DSP L
cards can be installed. The number of
resources provided by each type of DSP card
is as follows:
• DSP S card: 63
KX-NS0112 VoIP DSP Card (L Type) (DSP L) • DSP M card: 127
• DSP L card: 254
Up to 3 DSP cards can be installed on the
mother board.
To operate the NSX server, at least one
DSP S, DSP M, or DSP L card must be
installed in one of the DSP card slots.
KX-NSX2135 Storage Memory (S Type) Storage memory with maximum of 200 hours
Voice Mail recording time.
KX-NSX2136 Storage Memory (M Type) Storage memory with maximum of 400 hours
KX-NSX2137 Storage Memory (L Type) Storage memory with maximum of 800 hours
KX-NSX2138 Storage Memory (LL type) Storage memory with maximum of 1600
hours Voice Mail recording time.
KX-A412 AC Power Cord AC Power Cord
Note
• For the maximum number of optional service cards that can be installed in the NSX server, refer to
"2.3.2 System Capacity".
• For details about the optional equipment for expansion gateways in a Multi-connection network, refer
to the Installation Manual of the corresponding PBX.
2.3 Specifications
2.3 Specifications
2.3.1 General Description
Main CPU Intel ATOM E3845 (Quad core 1.91 GHz)
Power Input Rated Voltage AC 100 – 240 V
Frequency 50/60 Hz
Current/Power 0.95 - 0.6 A
Power Consumption (when fully 50 W
mounted)
External Backup Battery External battery port is not supported.
Memory Backup Duration 7 years
Operating Temperature 0 ℃ to 40 ℃
Environment
Humidity 10 % to 90 % (non-condensing)
Conference Call Trunk 255 parties
(85 × 3-party conference call, etc.)
RJ45 Port MNT Port Gigabit LAN Interface
(for Maintenance)
LAN1 Port Gigabit LAN Interface
(for IP Trunk/IP Extension/
Expansion Gateway) 10BASE-T/100BASE-TX/
1000BASE-T (Auto MDI/
LAN2 Port Gigabit LAN Interface MDI-X)
(for IP Trunk/IP Extension/
Expansion Gateway)
LAN3 Port Gigabit LAN Interface
(for Hot Standby)
Air-cooling method FAN
Dimension 430 mm (W) × 88 mm (H) × 340 mm (D)
Weight (when fully mounted) Under 5.0 kg
2.3.2 System Capacity

Type and Maximum Number of Slots
The NSX server supports the following type and number of slots.
Maximum Number
Slot Type
Physical Slot Storage Memory Card Slot 2 2
DSP Card Slot 3 3
Virtual Slot Virtual Trunk Card 5 8
Virtual Extension Card 9 17
Virtual IP-CS Card 16 16
Front View Inside View (The top cover is removed.)
A B
C DE F GH I J K E
A. Front panel
B. Top cover
C. DSP Card Slot 1
D. COM Express CPU module
E. FAN
F. DSP Card Slot 2
G. Storage Memory Card Slot 1 (Initial mounted)
H. Storage Memory Card Slot 2 (Optional)
I. Main Board (Mother Board)
J. DSP Card Slot 3
K. PSU (Power Supply Unit)
Maximum Optional Service Cards

The following number of card can be installed in the Physical Slots or Virtual Slots of the NSX server,
expansion gateways, expansion units, and legacy gateways.
Note
• Any card that exceeds the capacity of the unit will be ignored.
• When the unit starts up with an invalid configuration, some cards will be ignored.
For KX-NSX Series
Cards Installed in Physical Slots
Maximum Number
Card Type
DSP Card Slot 3
Maximum Number
Card Type
DSP S
DSP M 3
DSP L
Storage Memory Card Slot 2*1
Storage Memory S
Storage Memory M
1
Storage Memory L
Storage Memory LL
*1 The Main Storage Memory Card is pre-installed in Storage Memory Card Slot 1.
Cards Installed in Virtual Slots

Maximum Number
Card Type
Virtual Trunk Card 5 8
V-IPGW128 2 2
V-SIPGW128 5 8
Virtual Extension Card 9 17
V-IPEXT128 8 16
V-SIPEXT128 8 16
Virtual IP-CS Card 16 16
V-IPCS16 16 16
Maximum Trunks and Devices

This NSX server supports the following number of trunks and devices.
Notice
The capacities shown in these tables are for the largest possible configuration for each unit (i.e. the unit
is equipped with the largest capacity PSU available for that model). For more details about the capacity
of each model, refer to the Installation Manual of the corresponding unit.
Note
The maximum number of "Device for User (Extension)" shown in these tables includes the number of
extensions, PSs, DSS Consoles, and Mobile numbers in a user container.
For KX-NSX1000/KX-NSX2000
Type Multi- Multi-

Stand- Stand-
connection connection
alone alone
Network Network
User 1000 1000 2000 2000
Device for User (Extension)
1000 1000 2000 2000
Wired device
1000 1000 2000 2000
IP device
1000 1000 2000 2000
IP-PT (KX-NT300/
1000 1000 2000 2000
KX-NT500 series)
Third party SIP phones
1000 1000 2000 2000
(Including P-SIP)
Communication IP
128 128 128 128
Camera/IP Doorphone
Legacy device
0 1000 0 2000
SLT 0 1000 0 2000

DPT*1 0 512 (1000) 0 1024 (2000)
APT 0 320 0 640
DSS Console 0 128 0 128
PS 1000 1000 1000 1000
Mobile number in user container 1000 1000 2000 2000
Add-on Key Module (KX-NT505) 64 64 128 128
Add-on Key Module (KX-NT303, KX-NT305) 1000 1000 2000 2000
CS
256 256 256 256
IP-CS 256 256 256 256

PT-interface CS (2-channel) 0 256 0 256
Trunk
640 640 960 960
Type Multi- Multi-

Stand- Stand-
connection connection
alone alone
Network Network
IP Trunk
640 640 960 960
SIP Trunk 640 640 960 960

H.323 Trunk 256 256 256 256
Legacy Trunk
0 640 0 960
LCOT 0 640 0 960

BRI 0 640 0 960
PRI23 0 640 0 960
PRI30 0 640 0 960
T1 0 640 0 960
E1 0 640 0 960
Other I/O
Doorphone 0 124 0 124

Door Opener 0 124 0 124
External Sensor 0 124 0 124
*1 ( ) indicates the capacities using DXDP connections. If using a DXDP connection, the maximum number of devices is limited by
the capacity of a Multi-connection network.
For KX-NS300
KX-NS300
Type Basic unit Basic unit Basic unit

Basic unit + 1 Exp. + 2 Exp. + 3 Exp.
unit units units
User (See capacity for KX-NSX1000/KX-NSX2000)
Device for User (Extension) (See capacity for KX-NSX1000/KX-NSX2000)
KX-NS300

unit units units
Wired device
66 98 130 162
IP device 32
IP-PT 32
32
(Including P-SIP)
Communication IP Camera/IP
32
Doorphone
Legacy device
34 66 98 130
SLT 32 64 96 128
DPT 18 34 50 66
APT 8 16 24 32
DSS Console 8 8 8 8
PS (See capacity for KX-NSX1000/KX-NSX2000)
Mobile number in user container (See capacity for KX-NSX1000/KX-NSX2000)
Add-on Key Module (KX-NT505) 8
Add-on Key Module (KX-NT303, KX-NT305) 32
CS
36 40 44 48
IP-CS 32
Trunk
52 88 124 160
KX-NS300

unit units units
IP Trunk
16
SIP Trunk 16
H.323 Trunk 16
Legacy Trunk
36 72 108 144
LCOT 12 24 36 48
BRI 8 24 40 56
PRI23 23 46 69 92
PRI30 30 60 90 120
T1 0 0 0 0
E1 30 60 90 120
Other I/O
Doorphone 2 4 6 8
Door Opener 2 4 6 8
For KX-NS500
KX-NS500

unit units units
KX-NS500

unit units units
Wired device
162 194 226 258
IP device
128
IP-PT 128
128
(Including P-SIP)
128
Doorphone
Legacy device
34 66 98 130
SLT 32 64 96 128
DPT 18 34 50 66
APT 8 16 24 32
DSS Console 8 8 8 8
CS
36 40 44 48
IP-CS 32
Trunk
100 136 172 208
KX-NS500

unit units units
IP Trunk
64
SIP Trunk 64
H.323 Trunk 32
Legacy Trunk
36 72 108 144
LCOT 12 24 36 48
BRI 8 24 40 56
PRI23 23 46 69 92
PRI30 30 60 90 120
T1 0 0 0 0
E1 30 60 90 120
Other I/O
Doorphone 2 4 6 8
Door Opener 2 4 6 8
For KX-NS700
KX-NS700

unit units units
KX-NS700

unit units units
Wired device
166 198 230 262
IP device
128
IP-PT 128
128
(Including P-SIP)
128
Doorphone
Legacy device
38 70 102 134
SLT 36 68 100 132

DPT 34 66 98 130
APT 8 16 24 32
DSS Console 8 8 8 8
CS
40 48 56 64
IP-CS 32
Trunk
102 138 174 210
KX-NS700

unit units units
IP Trunk
64
SIP Trunk 64
H.323 Trunk 32
Legacy Trunk
38 74 110 146
LCOT 12 24 36 48
BRI 16 32 48 64
PRI23 23 46 69 92
PRI30 30 60 90 120
T1 0 0 0 -
E1 30 60 90 120
Other I/O
Doorphone 2 4 6 8
Door Opener 2 4 6 8
For KX-NS1000
Type KX-NS1000
KX-TDA600/
KX-TDA100/
KX-TDA200/ KX-TDA620,
Type of connected PBX Stand- KX-TDE100/
KX-TDE200 KX-TDE600/
alone KX-TDA100D
KX-TDE620
Number of connected PBX 1 2 1 2 1 2
Type KX-NS1000
KX-TDA600/
KX-TDA100/
alone KX-TDA100D
KX-TDE620
Wired device
640 640 640 640
IP device
640 640 640 640
IP-PT 640 640 640 640

640 640 640 640
(Including P-SIP)
Communication IP
128 128 128 128
Camera/IP Doorphone
Legacy device
2 128 256 168 336 240 480
SLT 2 128 256 168 336 240 480

DPT 128 *1
256 *1
0 256 512 160 320
104*2 208*2
APT 12*1 24*1
0 64 128 80 160
0*2 0*2
DSS Console 0 8 16 8 16 64 64
Add-on Key Module (KX-NT303,
640
KX-NT305)
CS
64 64 64 64
IP-CS 64 64 64 64
PT-interface CS (2-channel) 32*1
0 32 32
26*2
Trunk
256 256 256 256
Type KX-NS1000
KX-TDA600/
KX-TDA100/
alone KX-TDA100D
KX-TDE620
IP Trunk
256 256 256 256
SIP Trunk 256 256 256 256

H.323 Trunk 48 48 48 48
Legacy Trunk
30 120 240 128 256 160 256
LCOT 96*1 192*1

2 128 256 160 256
112*2 224*2
BRI 96*1 192*1
8 128 256 160 256
112*2 224*2
PRI23 23 92 184 92 184 115 230
PRI30 30 120 240 120 240 150 256
T1 0 96 192 96 192 120 240
E1 0 120 240 120 240 150 256
Other I/O
Doorphone 1 17 33 17 33 17 33
Door Opener 1 17 33 17 33 17 33
External Sensor 1 17 33 17 33 17 33
*1 Except KX-TDA100D.
*2 Only KX-TDA100D.
DSP Resources
DSP cards provide digital signal processor (DSP) resources, and the NSX server uses the resources to
perform various PBX operations. The following illustration shows the concept of DSP resource usage. More
complex situations may require additional resources, and in some cases the amount of DSP resources
required may be less than expected.
: Required DSP Resources
0.5
Conference
2
Outgoing Message
1 2.2
(DISA)
G.711 G.729A
1 IP-PT
Music on Hold (MOH)/
External Paging (EPG)
1 Internal MOH
G.711
2.2 1.3
G.729A 1 2.2
Unified Messaging
G.711 G.729A
IP-CS
2
IP Trunk
UM Tone Generator
PS
3
Echo Canceller
NSX server
Note
This is an example for a stand-alone NSX server.
Required DSP Resources Assessment

The maximum number of simultaneous calls, operations and features using IP protocols is determined by
the DSP card installed in the NSX server. According to the number of resources required, you can install up
to 3 DSP cards.
To decide how much resources are required for the NSX server, the DSP Resource Advisor can be useful.
Note
• Calls cannot be made or received when all of the DSP resources are being used.
• The number of required resources must not exceed the DSP resources installed to the NSX server.
• For details about the DSP Resource Advisor, refer to "9.33.1.1 PBX Configuration—[1-5-1]
Configuration—DSP Resource—Setting—DSP Resource Advisor" in the PC Programming Manual.
• For information about installing DSP cards, refer to "4.3.3 DSP S Card (KX-NS0110), DSP M Card
(KX-NS0111), DSP L Card (KX-NS0112)".
• The number of available DSP resources is not restricted by any activation keys.
• DSP resource usage can be confirmed using Web Maintenance Console. For details, refer to "5.5.3.3
Resource Depletion Indication Monitoring" in the Feature Manual.
DSP Resource Reservation

DSP resources can be reserved for certain operations to avoid lack of resources for particular operations.
When the NSX server is connected in a Multi-connection network, you can specify how many resources to
allocate to each branch.
The following examples show cases of allocating and reserving DSP resources.
Note
For details about reserving DSP resources, refer to "5.5.3.1 DSP Resource Reservation" and "5.5.3.2
DSP Resource Advisor" in the Feature Manual, and "9.33.1.1 PBX Configuration—[1-5-1] Configuration
—DSP Resource—Setting—DSP Resource Advisor" in the PC Programming Manual.
Example
In this example, the DSP M (127 DSP resources) is installed and resources are reserved for the following
operations:
Operation Required Resources
VoIP (G.711) Calls 40
Conference Trunks 10
Unified Messaging 8
Two-way Recording Operations 3

OGM Operations 10
UM Tone (Fixed) 2*1
*1 Because the system reserves 2 resources for internal system functions, the total amount of available resources indicated will be 2
less than the total resources of the installed card(s).
Reserved Resources
(40 × 1) + (10 × 0.5) + {(8 - 3) × 1.3} + (3 × 2.3) + (10 × 2) + 2
= 80.4
Free Resources
= 127 - 80.4
= 46.6
Note
This is an example for a stand-alone NSX server.
Section 3
Information about the Activation Keys
This section provides information on activation keys,

including how to obtain activation keys.
3.1 Information about the Activation Keys
3.1 Information about the Activation Keys

Activation keys are required to use IP trunks and IP telephones on a private IP network with an NSX server.
Also, to upgrade the software to use enhanced features, the corresponding activation keys for that feature
are required. Some activation keys are provided by default, some are provided free for a limited period, and
others are provided separately as activation key files.
3.1.1 Type and Maximum Number of Activation Keys

The NSX server supports the following type and number of activation keys.
When the number of preinstalled activation keys is not enough for the desired configuration or when you
wish to use enhanced features, additional activation keys in the form of activation key files can be installed
using Web Maintenance Console.
When the NSX server is connected in a Multi-connection network, activation keys should be installed on the
appropriate NSX server or expansion gateway as shown in the tables below.
Note
• Store the downloaded activation key files in your PC or a memory device. They can then be
reinstalled when changing the Expansion Storage Memory Card or in an emergency situation.
• For information about how to obtain the additional activation keys, refer to "3.1.2 Activation Key Code
and Key Management System".
• For information about how to install the activation key files using Web Maintenance Console, refer to
"5.4.5 Installing Additional Activation Keys".
System
Maximum
Model No. Activation Key Type Description
Activation Keys
KX-NSX101 NSX1000 System Activates KX-NSX1000 main features (For 1 activation key
Activation Key KX-NSX1000 only).
KX-NSX201 NSX2000 System Activates KX-NSX2000 main features (For 1 activation key
Activation Key KX-NSX2000 only).
KX-NSXF008 Activation Key for Activate redundancy (Hot Standby) 1 activation key
Redundancy function.
KX-NSXP101 Ultimate Activation Activate all activation key features at once 1 activation key
Key for Panasonic except for the following keys:
Terminal Users
• System Activation Key (KX-NSX101/
KX-NSX201)
• Maintenance annual Key (KX-NSX2201)
• Remote Maintenance annual Key
(KX-NSX6211)
• SIP Extension Activation Key
(KX-NSXSxxx)
Maintenance
Maximum
Activation Keys
KX-NSX2201 Maintenance annual Activate Maintenance features (Capturing 1 activation key
Key Packet Trace/Expanding system logs/
software upgrade)
This activation key is not required for the
first year of operation.
KX-NSX6211 Remote Maintenance Allows use of the remote maintenance 1 activation key
annual Key annual licence.
Note
• You can be notified of the expiration date of the activation key for annual maintenance by e-mail 10
days before the expiration date.
If this feature is enabled, an e-mail message will be sent once a day until the expiration date. The
notification will be stopped once the activation key is renewed.
• For activation keys with an expiration date, you can extend their activation period by re-installing them
before the expiration date.
For extension before expiration date
• 1 year extension: Extend the activation period by 12 months from the scheduled expiration date.
For extension after expiration date
[For KX-NSX2201 Maintenance annual Key]
– Extension within 1 year after expiration date: Extend the activation period by 12 months from the
original expiration date.
– Extension after 1 year from expiration date: Extend the activation period from the original expiration
date. You will need to purchase activation keys for the invalid period.
[For KX-NSX6211 Remote Maintenance annual Key]
– Extend the activation period by 12 months from the date when an activation key for re-installation is
issued. You will not need to purchase activation keys for the invalid period.
• If the Maintenance Annual Key (KX-NSX2201) has expired, the following features cannot be used:
– Packet trace
– Expanding system logs
IP traffic monitor
Web operation log
Service operation log
IP extension call quality information
User
KX-NSUN001 1-Normal User Concept Activation Key Activates 1 Normal user.
KX-NSUM001 1-Mobile User Concept Activation Key Activates 1 Mobile user from Normal user.

KX-NSUM100 100-Mobile User Concept Activation Key Activates 100 Mobile user from Normal
user.
KX-NSUM500 500-Mobile User Concept Activation Key Activates 500 Mobile user from Normal
user.
KX-NSUA001 1-Advanced User Concept Activation Key Activates 1 Advanced user from Mobile
user.
KX-NSUA010 10-Advanced User Concept Activation Activates 10 Advanced user from Mobile
Key user.
Key user.
Key user.
Key user.
3rd Party SIP-Extension

KX-NSXS001 1-Channel SIP Extension Activation Key Activates 1 SIP-Phone for 3rd party.
Panasonic Peripheral
KX-NSXN001 1-Channel Peripheral Device Activation Activates 1 Communication IP Camera/
Key IP-doorphone.
KX-NSXN010 10-Channel Peripheral Device Activation Activates 10 Communication IP Camera/
Key IP-doorphone.
Channel expansion for IP-CS

KX-NSXE001 1 IP-CS Channel Expansion Increases the number of communication channels
Activation Key from 4 to 8 for 1 IP-CS.
Note
• When performing channel expansion for IP-CSs, change the status of the IP-CS port to OUS, then
enable the channel expansion setting.
• To apply the channel expansion, the IP-CSs must be reset by changing their port status from OUS to
INS.
IP Trunks
KX-NSXT001 1-Channel IP Trunk Activation Key Allows the use of 1 IP trunks (H.323/SIP).
Unified Messaging System

Maximum
Activation Keys
KX-NSXU003 Activation Key for Allows the automatic backup of 1 activation key
Message Backup messages.
KX-NSXU004 Activation Key for Two- Allows a manager/administrator to 1 activation key
way Recording use the Automatic Two-way
Recording feature to record other
users.
Note
To use the Unified Messaging feature, an expansion Storage Memory Card must be mounted.
Networking
Maximum
Activation Keys
KX-NSXF006 Activation Key for Allows a KX-NSX1000/KX-NSX2000 1 activation key
Expansion GW (Master) to use the Multi-connection network
feature.
Communication Assistant (CA) User

Maximum Activation
Keys
KX-NSA401 CA Console Allows the use of CA Client Operator　 8 activation key
Console for 1 user.
Option features
Maximum
Activation Keys
KX-NSXF002 Activation Key for Call Allows the use of the Built-in ACD 1 activation key
Centre Report/Announcement of waiting
number for queuing features.
Maximum
Activation Keys
KX-NSXF004 Activation Key for Multiple Allows the use of multiple CTI 4 activation keys
CSTA Connection connection and built-in FOS interface.
KX-NSXF005 Activation Key for LDAP Allows the use of Address book LDAP 1 activation key
connection.
KX-NSXF021 Activation Key for Queue Allows the use of the Announcement 1 activation key
Announcement of waiting number for queuing
features.
KX-NSXF022 Activation Key for Built-in Allows the use of the Built-in ACD 1 activation key
ACD report Report features.
Note
• To use the Queue Announcement feature, either KX-NSXF002 or KX-NSXF021 is necessary.
• To use the Built-in ACD Report feature, either KX-NSXF002 or KX-NSXF022 is necessary.
• To use UC Pro, KX-NSXF004 is not necessary.
Multi-connection Network for Expansion Gateways

Activation Key Maximum
Model No. Description Target PBX
Type Activation Keys
KX-NSN101 Built-in Router Allows use of the Built-in 1 activation key KX-NS1000
AK Router. per gateway
KX-NSXF007 Expansion GW Enables KX-NS300/ 1 activation key KX-NS300/
(NS) KX-NS500/KX-NS700/ per gateway KX-NS500/
KX-NS1000 to connect to a KX-NS700/
KX-NSX1000/KX-NSX2000. KX-NS1000
Note
When the software of the Expansion Gateway is installed on the NS series PBX, the MPR-ID assigned
for the NS series PBX is switched to the one for the Expansion Gateway. It is necessary for you to input
the MPR-ID for the Expansion Gateway to purchase KX-NSN101 or KX-NSXF007. You can confirm the
MPR-ID on the Web Maintenance Console after installing the software of the Expansion Gateway on the
NS series PBX.
If KX-NSN101 has already been installed in a KX-NS1000, KX-NSN101 remains valid after installing the
Expansion Gateway software on the KX-NS1000.
Preinstalled Activation Keys in the Mother Board

Preinstalled activation keys
The following type and number of activation keys are preinstalled on the mother board.
Activation Key Activated Features Expiration
70 Normal User (for KX-NSX1000) 70 normal users None
50 Normal User (for KX-NSX1000EX) 50 normal users None
100 Normal User (for KX-NSX2000) 100 normal users None
Maintenance Annual Key Annual maintenance After 395 days*1
*1 Expires 395 days after System Activation Key (KX-NSX101 for KX-NSX1000 and KX-NSX201 for KX-NSX2000) is activated.
Example: Preinstalled Activation Keys in the Mother Board
Preinstalled activation keys for free trial

The following activation keys are preinstalled on the mother board for the 60-days free trial. They will expire
60 days after pressing the Activate Pre-installed Activation key button to begin the free trial.
Activation Key Activated Features
Redundancy Activate redundancy function
CA Operator Console (user) CA Operator Console (2 users)
System Multi-Connection Expansion GW connection for NSX Series (Master unit)
UM Message Backup UM Message Backup
Automatic Two-way Recording Automatic Two-way Recording for Manager
Call Centre Feature Enhancement Built-in ACD Report, Announcement of waiting number
for queuing
Multiple CTI Interface Multiple CTI Connection
External Database Synchronisation Integration with LDAP server
(LDAP)
Queue Position Announcement Announcement of waiting number for queuing
Built-in ACD Report Built-in ACD Report
Activation Key Installation Example

The following table shows an example of required activation key when activating user activation keys and
using certain extensions.
Number of Available Required Activation Number of Required
Desired User/Item
Users/Items Key Type Activation Key
KX-NSUN050 Activate
Normal User 50 1
50 Normal user
3.1.2 Activation Key Code and Key Management System
Number of Available Required Activation Number of Required

Desired User/Item
Users/Items Key Type Activation Key
KX-NSUN010 Activate
1
10 Normal user
Mobile User 10 KX-NSUN010 Activate
10 Mobile user from 1
Normal user
KX-NSUN010 Activate
1
10 Normal user
KX-NSUM010 Activate
10 Mobile user from 1
Advanced User 10
Normal user
KX-NSUA010 Activate
10 Advanced user from 1
Mobile user
KX-NSUN010 Activate
1
10 Normal user
Third party SIP phone 10 KX-NSXS010 Activate
10 SIP-Phone for 3rd 1
party
3.1.2 Activation Key Code and Key Management System

To obtain additional activation keys, you need to purchase the appropriate activation key codes and access
the Key Management System. You can download the activation keys as an activation key file from the Key
Management System.
To download the activation keys, enter the MPR ID number shown on the back of the main unit, and
activation key number and registration ID provided on each activation key code.
For information about the type of activation key codes available, refer to "3.1.1 Type and Maximum Number
of Activation Keys".
For details about installing the downloaded activation key file(s) in the directory where the activation key
files are stored, using Web Maintenance Console, refer to "5.4.5 Installing Additional Activation Keys".
Note
• You can only download the activation key file once using the activation key number and registration ID
provided on the activation key code.
• Up to 8 activation keys can be downloaded as one activation key file.
• Up to 997 activation key files can be installed in the Expansion Storage Memory Card.
• It is possible to send the activation key file to a specified e-mail address at the same time as
downloading it to a PC.
• Make sure to backup the downloaded activation key files on your PC.
• When the mother board has to be replaced due to a system malfunction, the MPR ID for the mother
board is no longer valid. In this case, you need a temporary activation key for maintenance purposes.
The temporary activation key can only be used for a limited time period, and can be downloaded from
the Key Management System in the same way as downloading activation key files.
3.1.3 Using CTI Applications

To use CTI applications with the NSX server, KX-NSXF004 (Multiple CTI Connection) is required.
Example 1
NSX server CTI Server
Single CSTA
Connection
Example 2
Panasonic
NSX server CSTA Multiplexer CTI Application Server
Single CSTA
Connection
CTI Application Server
CTI Application Server
Note
• Up to 4 CTI application servers can be used at the same time when using a CSTA multiplexer.
• An Activation Key for Multiple CSTA Connection (KX-NSXF004) is required for each CTI application.
• For details regarding KX-NSXF004, refer to "Option features" in "3.1.1 Type and Maximum Number of
Activation Keys".
• To use UC Pro, KX-NSXF004 is not necessary.
Section 4
Installation
This section describes the procedures to install the NSX

server. Detailed instructions for planning the installation
site, installing the main unit and optional service cards,
and cabling of peripheral equipment are provided.
Further information on peripheral equipment installation
is included.
4.1 Before Installation
4.1 Before Installation

4.1.1 Before Installation
Please read the following notes concerning installation and connection before installing the NSX server and
terminal equipment.
Be sure to comply with all applicable laws, regulations, and guidelines.
Notice
Panasonic assumes no responsibility for injuries or property damage resulting from failures arising out of
improper installation or operation inconsistent with this documentation.
Installation Precautions
The NSX server is suitable for mounting on a 19-inch rack and should be installed in a location where it is
accessible for inspections and maintenance.
To prevent malfunction, noise, or discolouration, follow the instructions below:
WARNING
Do not install the system in the following locations:
• Areas where shocks or vibrations are frequent or strong. Such activity may lead to the product
falling over and causing injury, or may impair the product’s performance.
• Areas with high amounts of dust. High amounts of dust can lead to fire or electric shock, and
impair the performance of the product.
CAUTION
• In direct sunlight and hot, cold, or humid places. (Temperature range: 0 ℃ to 40 ℃)
• Areas where sulphuric gases may be present, such as near thermal springs.
• Near devices that generate high frequencies, such as sewing machines or electric welders.
• Locations where other objects will obstruct the area around the unit. Be especially careful to leave at
least 5 cm to the sides of the unit for ventilation.
• Locations where condensation can occur.
Notice
• On or near computers, or other office equipment, as well as microwave ovens or air conditioners. (It is
preferable not to install the system in the same room as the above equipment.)
• Within 1.8 m of radios and televisions. (Both the NSX server and PTs should be at least 1.8 m away
from such devices.)
Do not perform the following:
• Do not block the openings of the NSX server.
• Do not stack up the optional service cards.
Wiring Precautions
Be sure to follow these instructions when wiring the unit:
4.1.1 Before Installation
CAUTION
• Avoid using the same AC outlet for computers and other office equipment, as noise generated by
such equipment may hamper system performance or interrupt the system.
• Unplug the system from its power source when wiring, and plug the system back in only after all
wiring is completed.
Notice
• Use 1-pair telephone cables when connecting SLTs, data terminals, answering machines, computers,
etc.
• Mis-wiring may cause the NSX server to operate improperly. Refer to "4 Installation" when wiring the
system.
• If an extension does not operate properly, disconnect the telephone from the extension line and
connect it again, or turn off the NSX server using the power switch, then turn it on again.
• Use twisted pair cable for trunk connection.
• To prevent signal noise from interfering with the performance of the product, do not run unshielded
telephone cables near AC power cables, computer cables, AC power sources, etc. When running
cables near other noise-generating devices or cables, use shielded telephone cables or shield the
telephone cables with metal tubing.
Preparing the Network Environment

Be sure to prepare your network’s environment for the installation of the NSX server according to the
intended NSX server networking configuration. For details about NSX server network configurations, refer to
"6 Networking Information".
Hardware Maintenance Precautions

Be sure to follow these instructions when performing hardware maintenance of the unit:
CAUTION
• Do not touch the CPU, heat sink, Main Storage Memory Card, and Expansion Storage Memory Card
during maintenance. Those parts may get hot.
• Do not replace the CPU, heat sink, Main Storage Memory Card, and cooling fan.
• Do not remove the parts for thermal dissipation (e.g., air flow cover for cooling).
• The NSX server parts are not hot-swappable. Do not replace parts or cables when the power of the
NSX server is on.
• If the heat sensor inside the NSX server detects abnormally high temperatures, power supply to the
unit will be forcefully stopped. In that case, turn off the NSX server using the power switch, then turn it
on again.
• If the feature is enabled, an error log will indicate when abnormal fan operation is detected in the
system heat control. In that case, consult the system administrator to replace of the fan.
• The operating conditions (e.g., CPU usage percentage, memory usage, Main Storage Memory Card,
and Expansion Storage Memory Card product life) are monitored, and monitoring results will be
notified by methods such as the error log, MIB, and system alarm. For details, consult your system
administrator.
Notice
• Usage of a high-capacity Expansion Storage Memory Card is recommended for heavy users.
4.2 Installation of the NSX server
• Make backups of data stored on the Expansion Storage Memory Card regularly and replace
Expansion Storage Memory Card based on the monitoring results for the product life. For details
about replacement, refer to "4.2.6 Installing/Removing an Expansion Storage Memory Card".
• The following contents will be recorded in the log:
– Memory usage
– SWAP memory free space
– Page In/Out speed
– Disk memory usage
– Main Storage Memory Card/Expansion Storage Memory Card product life time
– Amount data sent/received per virtual NIC
– Number of sent/received packets and packet loss per virtual NIC
4.2 Installation of the NSX server

4.2.1 Unpacking
Notice
• An AC power cord is not supplied with the NSX server. Refer to "2.2.1 Optional Equipment" for details
and use a power cord that is appropriate for the country/area. Use the AC Power Cord specified in
"2.2.1 Optional Equipment".
Unpack the box and check the items below:

• Main unit
• Manual(s)*1
• Hook clip
• 19-inch rack attachment bracket x 2
• Screw x 6
*1 The number of included manuals varies according to the country/area.
4.2.2 Names and Locations

Front Back
A B C D E F GH J K
I
L M
4.2.2 Names and Locations
Inside
O P
A. STATUS Indicator
B. SYSTEM MODE Indicator*1
C. System Mode Switch
D. USB Port
E. MNT Port
F. LAN 1 Port
G. LAN 2 Port
H. LAN 3 Port
I. BATT ALARM Indicator
J. Power Switch
K. Earth Terminal
L. AC Inlet
M. Hook Clip Hole
N. Top Cover
O. Support Bar
P. Mother Board
*1 For details about the SYSTEM MODE indicator, refer to "LED Indications".
4.2.3 Opening/Closing the Top Cover

Opening the Top Cover
CAUTION
When opening the top cover, the power switch must be turned off.
1. Confirm that the power switch is turned off.
A. Power Switch
Note
In order to turn off the NSX server’s power, a system shutdown using Web Maintenance Console
must first be performed. For details, refer to "5.5 System Control—System Shutdown" in the PC
Programming Manual.
2. Turn the screws anticlockwise to loosen.
3. Slide the top cover then lift it off.
4. Remove the support bar from the NSX server.
Closing the Top Cover

1. Place the support bar onto the NSX server.
2. Place the top cover onto the NSX server. Then slide the top cover until it closes properly.
3. Turn the screws clockwise to tighten.
CAUTION
For safety reasons, close the top cover and tighten the screws before operating the NSX server.
4.2.4 Frame Earth Connection
4.2.4 Frame Earth Connection

1. Loosen the screw. A
2. Insert an earthing wire (user- B
supplied).
3. Tighten the screw.
4. Connect the earthing wire to earth. (1)
A. Screw
B. Earthing wire
(1) To earth
WARNING
• Proper earthing (connection to earth) is very important to reduce the risk to the user of
electrocution or to protect the unit from the bad effects of external noise in the case of a
lightning strike.
• The earthing wire of the AC cable has an effect against external noise and lightning strikes,
but it may not be enough to protect the unit and to ensure electromagnetic compatibility. A
permanent connection between earth and the earth terminal of the unit must be made.
CAUTION
For earthing wire, green-and-yellow insulation is required, and the cross-sectional area of the conductor
must be more than 0.75 mm2 or 18 AWG.
Notice
Be sure to comply with applicable local regulations (e.g., laws, guidelines).
4.2.5 Installing/Removing the Optional Service Cards

CAUTION
• Before touching the unit (Server, cards, etc.), discharge static electricity by touching ground or
wearing an earthing strap. Failure to do so may cause the unit to malfunction due to static electricity.
• When installing or removing the optional service cards, the power switch must be turned off.
• When installing or removing the optional service cards, do not put pressure on any parts of the
mother board. Doing so may result in damage to the unit.
Note
Make sure the AC power cord is not connected to the AC inlet of the Server.
Installing a DSP Card in a DSP Card Slot

1. Position a DSP card in an open DSP card slot. Then holding the card firmly in place, lower the rear end
so that the holes of the card are aligned with the screw holes.
Note
There are 3 DSP card slots on the mother board. When installing only 1 DSP card, only one DSP
card slot will be used.
Back View
C B A
A. DSP Card Slot 1
B. DSP Card Slot 2
C. DSP Card Slot 3
2. Insert the screws into the holes on the card, and tighten the screws to secure the card.
Back View
A. Screws
Note
DSP Card slot 1 and 2 they need to fasten three screws to mount on the motherboard.
Only DSP Card slot 3, it needs to fasten two screws.
Removing a DSP Card Installed in the DSP Card Slot

1. Loosen and remove the screws.
Back View
A. Screws
4.2.6 Installing/Removing an Expansion Storage Memory Card
2. Holding the rear end of the card, pull the card in the direction of the arrows.
Back View

The Main Storage Memory Card is pre-installed in Storage Memory Card Slot 1 of the NSX server.
An Expansion Storage Memory Card is an optional Storage Memory Card that can be installed in Storage
Memory Card Slot 2.
The Main Storage Memory Card is mainly for storing system data (e.g., SMDR or packet trace), and an
Expansion Storage Memory Card is for storing information related to Unified Messaging.
This section explains how to install or remove an Expansion Storage Memory Card.
CAUTION
Do not remove the Main Storage Memory Card. To replace the Main Storage Memory Card with a new
one, make backups of data stored on the Main Storage Memory Card, and then consult your dealer.
Voice Mail recording time varies depending on which Expansion Storage Memory Card you install.
For details about optional Expansion Storage Memory Card, refer to "4.3.2 Expansion Storage Memory
Card (KX-NSX2135, KX-NSX2136, KX-NSX2137, KX-NSX2138)".
System Prompts
Expansion Storage Memory Cards contain system prompts for Unified Messaging.
For information about the system prompt languages in each Expansion Storage Memory Card, refer to
"8.2 System Prompt Languages".
The system prompt language data you are using on the currently installed Expansion Storage Memory
Card must be backed up if you want to continue using that Expansion Storage Memory Card’s system
prompt language data. After backing up the system prompt language data, replace the Expansion
Storage Memory Card, and then restore the backed up system prompt language data to the new
Expansion Storage Memory Card.
This procedure is described below.
Notice
If this is the first time the NSX server is being started, complete the Easy Setup Wizard before
performing the following procedure. For details about Easy Setup Wizard, refer to "5.4.1 Easy Setup
Wizard".
1. Insert a USB memory device into the USB port of the NSX server.
(For details, refer to "Using a USB memory device" in "4.5 Connection of Peripherals".)
2. Back up the desired system prompts to the USB memory device.
(For details, refer to "6.8 Tool—UM Data Backup" in the PC Programming Manual.)
3. Shut down the NSX server, and then turn the power switch off.
(For details about shutting down the NSX server, refer to "5.5 System Control—System Shutdown" in
the PC Programming Manual.)
4. Remove the Expansion Storage Memory Card (currently used), and then install a new Expansion
Storage Memory Card.
5. Start the NSX server as described in "System Initialisation Procedure" in "4.7 Starting the NSX server".
6. Perform Easy Setup Wizard.
(For details, refer to "5.4.1 Easy Setup Wizard".)
7. Restore the system prompts backed up in step Installing/Removing an Expansion Storage Memory
Card. For details, refer to "6.9 Tool—UM Data Restore" in the PC Programming Manual.
Installing/Removing an Expansion Storage Memory Card

CAUTION
• Do not remove the Main Storage Memory Card pre-installed in Storage Memory Card Slot 1.
• Do not insert the Main Storage Memory Card into Storage Memory Card Slot 2.
• Before touching the product (Server, cards, etc.), discharge static electricity by touching ground or
• When installing or removing the Expansion Storage Memory Card, the power switch must be turned
off and the AC power cord must be unplugged.
• When installing or removing an Expansion Storage Memory Card, do not put pressure on any parts of
the mother board. Doing so may result in damage to the unit.
• The Expansion Storage Memory Card contains software for all the processes of the unit and all the
customer data. Therefore, do not allow unauthorised access to prevent data leakage.
• To prevent data leakage, render the Expansion Storage Memory Card physically unusable before
disposal.
Notice
• Use only a Panasonic Expansion Storage Memory Card.
• The Expansion Storage Memory Card is used exclusively for storing information related to Unified
Messaging.
• If it is necessary to replace the pre-installed main Storage Memory Card with a new one, make
backups of data stored on the main Storage Memory Card, and then consult your dealer.
Installing the Expansion Storage Memory Card
1. Place the unit on a desktop. Then remove the top cover and then the support bar.
2. Confirm the position of Storage Memory Card slot 2. (The Main Storage Memory Card is installed in slot
1 by default.)
A. Slot 1
B. Slot 2
3. Insert an Expansion Storage Memory Card into the slot 2 on the mother board. Align the notch on the
edge of the Expansion Storage Memory Card with the convex in the slot 2. (Confirm the angle of the
Expansion Storage Memory Card to the mother board is approximately 30 degrees.)
A
B
A. Convex part
B. Notch part
C. Slot 1
D. Slot 2
E. Approximately 30 degrees
4. Place the Expansion Storage Memory Card by pushing down the card.
5. Confirm the Expansion Storage Memory Card edge is placed firmly into the metal latch on the left.
Replacing the Expansion Storage Memory Card

1. Make a backup of the data stored on the installed expansion Storage Memory Card.
For details on procedures, refer to steps 1-3 in "System Prompts".
2. Pull the latch of Storage Memory Card Slot 2 in the direction of the arrows.
3. Remove the expansion Storage Memory Card.
4.2.7 Types of Connectors
A. Slot 1
B. Slot 2
4. Install a new expansion Storage Memory Card. For procedures, refer to the instructions described in
steps 3-5 in "Installing the Expansion Storage Memory Card".
5. Start the NSX server.
6. Restore the data backed up in step 2. For details, refer to "6.9 Tool—UM Data Restore" in the PC
Programming Manual.
4.2.7 Types of Connectors

Note
• For details about the equipment necessary for expansion gateways, expansion units, or legacy
gateways, refer to the Installation Manual of the corresponding unit.
Connector Type Pin Number Used for
RJ45
• Mother board
1 8
(Twisted pair cable)
4.2.8 19-inch Rack Mounting

WARNING
• Be careful not to drop any components. Dropping components may damage them or cause an
injury.
• When mounting the unit on a 19-inch rack, only use the 19-inch rack mounting equipment
(attachment bracket, screws) included with the unit.
CAUTION
• When the unit is mounted on a 19-inch rack, make sure that the installation of the unit does not cause
the temperature of the rack to exceed its limit.
• When the unit is mounted on a 19-inch rack, allow space of at least 5 cm to the sides of unit and at
least 10 cm to the rear of the unit for ventilation of the fan.
• If the unit is not installed properly using the securing correct methods, the unit may fall causing
serious damage.
• When this product is no longer in use, make sure to detach it from the rack.
Notice
When mounting the unit on a 19-inch rack, confirm that the rated current listed on the unit’s name plate
does not exceed the threshold current for the breaker.
4.3 The Mother Board and Expansion Cards
1. Fix the attachment brackets to the left and right sides of the unit with 3 screws on each side.
(Recommended torque: 0.8 N·m [8.2 kgf·cm] to 1.0 N·m [10.2 kgf·cm])→ 1
2. Place the unit in the 19-inch rack and fix both attachment brackets to the rack with the rack’s proprietary
mounting equipment. → 2
A. Attachment Bracket
B. Screw
4.3 The Mother Board and Expansion Cards

4.3.1 Mother Board
Function
The mother board is the preinstalled processing board with activation keys for 50 normal user
(KX-NSX1000EX), 70 normal users (KX-NSX1000) or 100 normal users (KX-NSX2000). The Virtual Cards
(trunk/extension) can be installed in Virtual Slots of the mother board and can be activated with the
activation keys. Also, the mother board supports LAN connection so that IP telephones (IP-PTs, IP
softphones, SIP phones) and PCs can be connected on a private IP network.
Mountable Cards
• Up to 3 DSP S, DSP M, or DSP L cards (refer to "4.3.3 DSP S Card (KX-NS0110), DSP M Card
(KX-NS0111), DSP L Card (KX-NS0112)")
• Expansion Storage Memory Card (refer to "4.3.2 Expansion Storage Memory Card (KX-NSX2135,
KX-NSX2136, KX-NSX2137, KX-NSX2138)")
4.3.1 Mother Board
G
H
F
I
C
D
E
A. Storage Memory Card Slots

B. DSP Card Slot
C. USB Port
D. System Mode Switch
E. LEDs
F. MNT Port
G. LAN 1
H. LAN 2
I. LAN 3
Note
• Make sure to use the MNT port for PC connection, and the LAN port for LAN connection.
• The maximum length of the CAT 5/CAT 5e cables to be connected to the mother board is 100 m.
• For installing and removing the Expansion Storage Memory Card, refer to "4.2.6 Installing/Removing
an Expansion Storage Memory Card".
• For details about Virtual Slots, refer to "2.3.2 System Capacity".
• If the preinstalled activation keys on the mother board are not enough for the desired configuration,
you need to purchase activation key codes. For details about the activation keys, refer to
"3.1 Information about the Activation Keys".
4.3.1 Mother Board
• For details about connecting to a LAN, refer to "4.6 LAN Connection".

• For details about connecting peripherals, refer to "4.5 Connection of Peripherals".
• For details about System Mode Switch, refer to "4.7 Starting the NSX server".
WARNING
A lithium battery is used in the mother board. There is a risk of explosion if the battery is
replaced with the incorrect type. Dispose of used batteries according to the manufacturer’s
instructions.
Pin Assignments
MNT Port/LAN Port/WAN Port (10BASE-T/100BASE-TX)
No. Signal Name Input (I)/Output (O) Function
1 TPO+ O Transmit data+
2 TPO- O Transmit data-
3 TPI+ I Receive data+
4-5 Reserved – –
1 8
6 TPI- I Receive data-
MNT Port/LAN Port/WAN Port (1000BASE-T)

Input (I)/
No. Signal Name Function
Output (O)
1 TRD0 (+) I/O Transmit and receive data 0 (+)
2 TRD0 (-) I/O Transmit and receive data 0 (-)
1 8
4.3.1 Mother Board
LED Indications
Indication Colour Description
STATUS Green NSX server status indication
• OFF: Power Off
• ON: Power On and running
• Flashing: Starting up/Logging in
Amber NSX server status indication
• ON: Ready to shutdown
• Flashing: Shutting down
Red NSX server status indication
• ON: Alarm
The cause may be one of the following:
– Power was cut without performing the shutdown procedure.
– No IP address(es) assigned for the DSP card(s) by the
DHCP server.
– Alarm for an optional service card.
• Flashing: Initialise failed
BATT ALARM Red Alarm indication
• OFF: Normal (During operation, indicates that the voltage of the
lithium battery is normal.)
• ON: Alarm (During operation, indicates that the lithium battery
needs to be replaced.)
Ready to shutdown (After shutdown, lights when it is safe to
turn off the power.)
SYSTEM MODE Green Primary unit status indication
• ON: Primary
Hot standby status indication
• ON: Active
• Flashing (120/minute): Transferring data
• Flashing (60/minute): Data synchronisation stopped / Data
initial synchronisation not performed
Amber Primary unit status indication
• ON: Ready to shutdown
Hot standby status indication
• ON: Standby
4.3.2 Expansion Storage Memory Card (KX-NSX2135, KX-NSX2136, KX-NSX2137, KX-NSX2138)
4.3.2 Expansion Storage Memory Card (KX-NSX2135,

KX-NSX2136, KX-NSX2137, KX-NSX2138)
Function
Main Storage Memory
Card (Installed by
default)
Storage Memory S: Storage Memory with maximum of 200 hours Voice Mail recording time.
Storage Memory M: Storage Memory with maximum of 400 hours Voice Mail recording time.
Storage Memory L: Storage Memory with maximum of 800 hours Voice Mail recording time.
Storage Memory LL: Storage Memory with maximum of 1600 hours Voice Mail recording time.
A B C D
A. Storage Memory Card Slot 2

B. Storage Memory Card Slot 1
C. Main Storage Memory Card
D. Mother Board
Accessories and User-supplied Items

Accessories (included): none
User-supplied (not included): none
Note
For installing and removing the Expansion Storage Memory Card, refer to "4.2.6 Installing/Removing an
Expansion Storage Memory Card".
4.3.3 DSP S Card (KX-NS0110), DSP M Card (KX-NS0111), DSP L Card (KX-NS0112)
4.3.3 DSP S Card (KX-NS0110), DSP M Card (KX-NS0111), DSP L

Card (KX-NS0112)
Function
A DSP card is a digital signal processor card with DSP resources that can be used for VoIP calls,
conferences, the Unified Messaging feature, and the DISA/OGM feature. The DSP cards are compliant with
ITU-T G.729A and G.711 codec methods.
Depending on the amount of your DSP resource needs, DSP S, DSP M, or DSP L cards can be installed.
Up to 3 DSP cards can be installed on the mother board.
To operate the NSX server, at least one DSP S, DSP M, or DSP L card must be installed in one of the DSP
card slots.
Back View
B
A
A
F
B
F
A
C D
G
G
A. DSP Card
B. Screws
C. DSP Card Slot 1
D. DSP Card Slot 2
E. DSP Card Slot 3
F. FAN
4.4 Virtual Cards
G. Inside
Accessories and User-supplied Items

Accessories (included): Screws × 3
User-supplied (not included): none
CAUTION
When installing or removing the optional service cards, do not put pressure on any parts of the mother
board. Doing so may result in damage to the unit.
Note
The DSP Resource Advisor can be used to calculate DSP resource usage easily. For details, refer to
"9.33.1.1 PBX Configuration—[1-5-1] Configuration—DSP Resource—Setting—DSP Resource Advisor"
in the PC Programming Manual.
DSP Resource Information

The number of resources provided by each type of DSP card is as follows:
DSP Card Type Number of Resources
DSP S 63
DSP M 127
DSP L 254
IP Address Information
Either 1 or 2 IP addresses must be assigned to each DSP card, depending on the type of DSP card. You
can assign IP addresses to the DSP cards during Easy Setup Wizard or through system programming.
For details about Easy Setup Wizard, refer to "5.4.1 Easy Setup Wizard".
For details about assigning IP addresses through System Programming, refer to "Changing IP Address
Settings".
DSP Card Type Number of IP Addresses
DSP S/DSP M 1
DSP L 2
4.4 Virtual Cards

Function
Virtual Cards are programs included with the mother board and that are treated as virtual cards by Web
Maintenance Console for convenience. Those programs can be activated with the appropriate activation key
(apart from V-IPCS16 cards, which do not require activation keys). By installing Virtual Cards in the Virtual
Slots of the mother board using Web Maintenance Console, IP trunks, IP extensions, and IP-CSs can be
used via the mother board.
Virtual Card Description
Virtual 128-Channel SIP Trunk Card Virtual Card for 128-channel SIP trunk. Compliant with RFC
(V-SIPGW128) 3261, 3262, 3264, 3311, 3581, 3960 and 4028 protocols, and
ITU-T G.729A and G.711 codec methods. Also supports T.38
protocol.
4.5 Connection of Peripherals
Virtual Card Description

Virtual 128-Channel VoIP Gateway Virtual Card for 128-channel H.323 trunk. Compliant with VoIP
Card (V-IPGW128) H.323V.5 protocol, and ITU-T G.729A and G.711 codec
methods. Also supports T.38 protocol.
Virtual 128-Channel VoIP Extension Virtual Card for 128 IP-PTs (e.g., KX-NT500 series). Compliant
Card (V-IPEXT128) with Panasonic proprietary protocol, and ITU-T G.729A, G.711
and G.722 codec methods.
Virtual 128-Channel SIP Extension Virtual Card for 128 third party SIP phones/P-SIP Extensions.
Card (V-SIPEXT128) Compliant with RFC 3261, 3264, 3310, 2327 and 4028
protocols, and ITU-T G.729A, G.711 and G.722 codec
methods. Also supports T.38 protocol.
Virtual 16 IP Cell Station Interface Card Virtual Card for 16 IP-CSs. Compliant with ITU-T G.729A and
(V-IPCS16) G.711 codec methods.
4.5 Connection of Peripherals
USB Memory
Device
Maximum Distance
100 m USB Port
MNT Port
PC
PC (via MNT Port)

A PC can be connected to the NSX server via the MNT port of the NSX server. It is used for system
programming, diagnostics and external system database storage (save/load) functions.
Pin Assignments for 10BASE-T/100BASE-TX

No. Signal Name Input (I)/Output (O) Function
1 TPO+ O Transmit data+
2 TPO- O Transmit data-
3 TPI+ I Receive data+
1 8
6 TPI- I Receive data-
4.6 LAN Connection
Pin Assignments for 1000BASE-T

Input (I)/
No. Signal Name Function
Output (O)
1 8
Note
You can use 1000BASE-T cables for 10BASE-T/100BASE-TX connections.
USB Interface for USB Memory Device

The NSX server is equipped with a USB 2.0 interface. This interface provides communication between the
NSX server and user-supplied devices such as a USB memory device.
Using a USB memory device

A USB memory device can be used to backup and restore the system data of the NSX server.
The NSX server supports USB memory devices that meet the following specifications:
• File system: FAT/exFAT
• Maximum capacity: 128 GB
• Maximum current: 500 mA
For details about backing up and restoring using a USB memory device, refer to "6.1.1 Tool—System Data
Backup—Backup to USB" in the PC Programming Manual.
Note
Do not use a USB hub when connecting a USB memory device to the NSX server.
4.6 LAN Connection

4.6.1 LAN Connection for the Main Unit
Connecting the Main Unit to the LAN
The NSX server is equipped with a LAN port for connecting to a LAN so that IP telephones (IP-PTs, IP
softphones, SIP phones), IP-CSs, PCs and a CTI Server can be connected on a private IP network. When
the NSX server is connected to the LAN for the first time, you must assign IP addressing information to the
NSX server. See "5.4 Programming the NSX server" for instructions.
4.6.1 LAN Connection for the Main Unit
IP Softphone CTI Server PC
LAN Port
Switching Hub
IP-PT Ethernet Cable
IP-CS Trunk
Adaptor
SIP Phone
Connection for 10BASE-T/100BASE-TX

Switching Hub NSX server (LAN Port)
Signal Name Pin No. Pin No. Signal Name
TX+ 1 1 RX+
TX- 2 2 RX-
RX+ 3 3 TX+
RX- 6 6 TX-
Connection for 1000BASE-T

Switching Hub NSX server (LAN Port)
Signal Name Pin No. Pin No. Signal Name
TRD0 (+) 1 1 TRD0 (+)
TRD0 (-) 2 2 TRD0 (-)
TRD1 (+) 3 3 TRD1 (+)
TRD2 (+) 4 4 TRD2 (+)
TRD2 (-) 5 5 TRD2 (-)
TRD1 (-) 6 6 TRD1 (-)
TRD3 (+) 7 7 TRD3 (+)
TRD3 (-) 8 8 TRD3 (-)
Note
• Use an Ethernet cable with an RJ45 connector for connection to a switching hub. The cable should be
a CAT 5 (Category 5) or higher for 10BASE-T/100BASE-TX, or CAT 5e (Enhanced Category 5) or
higher for 1000BASE-T.
4.6.2 LAN Connections for IP Telephones
• Make sure that all CAT 5/CAT 5e cables in use are not over 100 m in length.
• Make sure to set the port of the switching hub that connects to the card to operate under "Auto
Negotiation" mode.
• Make sure to create a spanning tree for LAN connection in order to prevent loops from occurring in a
multi-bridged environment. Otherwise, some packets may circulate for long periods of time and
eventually system performance may degrade.
• The CTI server can be used for connecting PCs on a LAN to provide third party call control CTI.
CTI connection uses the CSTA Phase 3 or TAPI 2.1 protocol. The operating system of the PC or CTI
server required for third party call control depends on your CTI application software. For details, refer
to the manual for your CTI application software.
• When using the VLAN feature on the network, make sure that the NSX server is connected to a layer
2 switch that is IEEE 802.1Q compliant, and that is configured for VLANs. In addition, the port of the
switching hub to which the NSX server is connected must be set to "Untagged". Consult your network
administrator for details.
4.6.2 LAN Connections for IP Telephones

When an IP telephone is connected to the LAN and power is supplied for the first time, you will be prompted
to set network parameters. The network parameters must be set for the IP telephone before it can be used.
Refer to "5.8 Assigning Networking Information to IP Telephones" for instructions.
Connecting an IP Telephone to a Switching Hub

When connecting an IP telephone to the LAN, connect it to a switching hub.
Note
• Use an Ethernet straight cable with an RJ45 connector to connect the IP telephone to a switching
hub. The cable should be a CAT 5 (Category 5) or higher for 10BASE-T/100BASE-TX, or CAT 5e
(Enhanced Category 5) or higher for 1000BASE-T.
• When using the VLAN feature on the network, make sure that the switching hub to be connected is
IEEE 802.1Q compliant and is configured for VLANs. In addition, the port of a switching hub that the
IP telephone is connected to must be set to "Trunk" port, to allow VLAN tagging. Consult your network
• Since an IP softphone is installed and operates on a PC, the PC must be connected to the LAN to
use the IP softphone on the network.
For SIP phones, refer to the documentation of your SIP phone.
Connecting an AC Adaptor to an IP Telephone

IP-PTs and some SIP phones comply with the IEEE 802.3af Power-over-Ethernet (PoE) standard. If PoE is
available on your network, these IP telephones can receive the necessary power supply from the network
through the network cable. In this case, no AC adaptor is needed for the IP telephones.
However, if PoE is not available, you will need to connect an AC adaptor to the IP telephone.
Note
Use only the specified type of AC adaptor for each IP telephone. For details, refer to the documentation
of your IP telephone.
Connecting a PC to an IP Telephone
You can connect a PC to some IP telephones (e.g., KX-NT500 series) using the IP telephone’s secondary
port. In this case, only a single port from the LAN’s network interface (switching hub) is required to connect
both the IP telephone and PC to the LAN.
4.7 Starting the NSX server
Note
• Use an Ethernet straight cable with an RJ45 connector to connect a PC to the IP telephone. The
cable should be a CAT 5 (Category 5) or higher for 10BASE-T/100BASE-TX, or CAT 5e (Enhanced
Category 5) or higher for 1000BASE-T.
• Only a PC can be connected to the secondary port of an IP telephone. Other IP telephones, including
IP-PTs, or network devices such as routers or switching hubs, cannot be connected.
• The secondary port does not support PoE for connected devices.
• In cases where a PC is connected to the secondary port, if the IP telephone connection to the NSX
server is disconnected or reset, LAN communication to the PC will also be disrupted.
• Generally, it is recommended that you connect no more than one PC to the secondary port of each IP
telephone.

WARNING
Make sure that the AC outlet is properly earthed, then securely connect the 3-pin AC plug
including the earthed pin.
CAUTION
• Before touching the unit (Server, cards, etc.), discharge static electricity by touching ground or
• Once you have started the unit, if you unplug the unit, do not initialise it again as described in "System
Initialisation Procedure". Otherwise, your programmed data will be cleared. To restart the unit, refer to
"7.1.3 Restarting the NSX server".
• The power supply cord is used as the main disconnect device. Ensure that the AC outlet is located
near the equipment and is easily accessible.
Installing the Hook Clip for the AC Power Cord

1. Insert the hook clip into the hook clip hole.
Note
Use only the hook clip included with the NSX server.
Connecting the AC Power Cord

1. Plug the AC power cord into the NSX server and pass the cord through the hook clip as indicated. Push
the hook clip in the direction of the arrow until it clicks.
Note
For safety reasons, do not stretch or pinch the AC power cord.
(1)
(1) To UPS
2. When not using a UPS (Not recommended):

Plug the other end of the cord into an AC outlet.
When using a UPS (Strongly recommended):
Plug the other end of the cord into the outlet of the UPS.
System Initialisation Procedure

All data, except for system prompts and activation key files, will be erased. Data that is erased includes
Unified Messaging data, call logs, etc. The settings for the NSX server as well as all optional service cards
will be initialised to their default values.
Note
• After the NSX server is initialised, you can restore system data to the NSX server that has been
backed up earlier. For details about backing up and restoring system data, refer to "6.1 Tool—System
Data Backup", "7.2.2 Utility—File—File Transfer PBX to PC" and "7.2.1 Utility—File—File Transfer PC
to PBX" in the PC Programming Manual.
• After the NSX server is initialised, you must set up the mandatory settings required for both stand-
alone NSX server and NSX server in a Multi-connection network with Easy Setup Wizard. For details
refer to "Connecting to Web Maintenance Console" and "5.4.1 Easy Setup Wizard".
• When a UPS is connected, make sure it is started as instructed in the documentation for the UPS.
1. Slide the System Mode Switch to the "SYSTEM INITIALIZE" position.
A B
A. STATUS Indicator
B. System Mode Switch
2. Turn on the power switch of the NSX server. The STATUS indicator will flash green.
3. While the STATUS indicator is flashing green, slide the System Mode Switch back to the "NORMAL"
position. Depending on the configuration, initialisation takes about 2.5 minutes. If successfully executed,
the STATUS indicator will stop flashing and remain lit up.
Section 5
Programming Information
This section describes the installation procedure,

structure, and functions of the Web Maintenance
Console for programming IP telephones and the NSX
server. Further information on programming the NSX
server for use with SIP trunks and a VoIP network is
included.
5.1 Overview of Web Maintenance Console
5.1 Overview of Web Maintenance Console

Web Maintenance Console is designed to serve as an overall system programming reference for the NSX
server. You can programme and control the NSX server over an IP network using Web Maintenance
Console.
This section describes programming basic items using Web Maintenance Console.
A C B
A. Login Status
B. Web Maintenance Console Features
C. Menu Buttons
Note
The contents and design of the software are subject to change without notice.
5.2 PC Connection
NSX server has 4 physical ports for PC and LAN connections. A default IP address is assigned to each port.
You can connect a PC to the NSX server either directly or over a LAN using the appropriate method for the
port being used.
Port Default IP Address Default Subnet Mask

MNT Port 223.0.0.1
255.255.255.0
LAN Port 192.168.0.101
5.2 PC Connection
Direct Connection
MNT Port
To LAN Port
Notice
When connecting the PC to the MNT port, if the PC is set to obtain the IP address automatically, the IP
address of the PC will be set to an appropriate IP address to establish a connection to the NSX server.
Note
• Use an Ethernet cable with an RJ45 connector to connect a PC to the NSX server.
• For pin assignments and maximum cabling distance, refer to "4.5 Connection of Peripherals".
Connection via LAN
LAN
LAN Port
PC
Switching Hub
Note
For details about connecting a switching hub to the NSX server, refer to "4.6.1 LAN Connection for the
Main Unit".
5.2 PC Connection
Connection via Virtual Private Network (VPN)

PC
Router
VPN
LAN
LAN Port
Router
Switching Hub
Notice
To access the NSX server via VPN, the PC must be in the same VPN.
Note
For details about connecting a switching hub to the NSX server, refer to "4.6.1 LAN Connection for the
Main Unit".
Connect via Panasonic Cloud
Panasonic Cloud
(KMS*1)
Internet
LAN Port
LAN
PC Router Router
Switching Hub
*1 KMS: Key Management System

5.3 Starting Web Maintenance Console
Note
• An activation key (KX-NSX6211) is required for this service.
• A preferred DNS IP address must be specified manually through Web Maintenance Console. (→ 28.1
Network Service—[1] IP Address/Ports—Basic Settings—DNS Setting—Preferred DNS IP Address)
• If a proxy server is used on the IP network where the PBX is installed, proxy settings are required in
Web Maintenance Console. (→ 28.3.5 Network Service—[3-5] Client Feature—HTTP)

System Requirements
For the system requirements of the PC (operating system, hardware specifications, supported browsers,
etc.), refer to "1.2.1 Starting Web Maintenance Console" in the PC Programming Manual.
Copyright for MD5

This software uses the Source Code of RSA Data Security, Inc. described in the RFC1321 (MD5 Message-
Digest Algorithm).
Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.
License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc.
MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function.
License is also granted to make and use derivative works provided that such works are identified as
"derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or
referencing the derived work.
RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or
the suitability of this software for any particular purpose. It is provided "as is" without express or implied
warranty of any kind.
These notices must be retained in any copies of any part of this documentation and/or software.
Password Security
CAUTION
To the Administrator or Installer regarding the system password
1. Please provide all system passwords to the customer.
2. To avoid unauthorised access and possible abuse of the NSX server, keep the passwords secret,
and inform the customer of the importance of the passwords, and the possible dangers if they
become known to others.
3. The NSX server has default passwords preset. For security, change these passwords the first time
that you programme the NSX server.
4. Change the passwords periodically.
5. It is strongly recommended that passwords of 10 numbers or characters be used for maximum
protection against unauthorised access. For a list of numbers and characters that can be used in
system passwords, refer to "1.1.3 Entering Characters" in the PC Programming Manual.
Connecting to Web Maintenance Console

• When no operations are performed for more than 60 minutes (default), you will be automatically logged
out from Web Maintenance Console and unsaved data will be lost.

1. Connect the PC to the NSX server:

• Connect the NSX server to a PC with the MNT port and access the NSX server directly from the PC.
For details, refer to "Direct Connection" in "5.2 PC Connection".
• Connect the NSX server to a network with the LAN port and access the NSX server from a PC in your
LAN or VPN. For details, refer to "Connection via LAN", "Connection via Virtual Private Network
(VPN) " and "4.6.1 LAN Connection for the Main Unit".
• Connect the NSX server to a network with the LAN port and access the NSX server from a PC using
an Internet connection. For details, refer to "Connect via Panasonic Cloud" and "4.6.1 LAN
Connection for the Main Unit".
2. Access Web Maintenance Console:
MNT Port Connection:
Launch your Web browser and in the address bar, enter one of the following addresses exactly as
shown:
– 223.0.0.1
Note
• The default subnet mask for the MNT port is 255.255.255.0.
• If connecting using 223.0.0.1 takes a long time, configure a static IP address for the PC.
LAN or VPN Connection:

Launch your Web browser and input the IP address of the NSX server followed by the Web
Maintenance Console port number into the address bar. The input method will differ according to the
PC’s connection to the NSX server.
The default IP address for the LAN port of the NSX server is 192.168.0.101, and the default Web
Maintenance Console port number is 80. Accordingly, the address to enter to connect to the NSX server
for the first time will be as follows (enter the address exactly as shown):
http://192.168.0.101
Note
The default subnet mask for the LAN port is 255.255.255.0.
Internet Connection (TLS Connection):

When the PC is accessing the NSX server from a connection over the internet, the use of TLS is
strongly recommended. When using a TLS encrypted connection, the default port is 443. The format of
the address to enter to connect to the NSX server using a TLS encrypted connection will be as follows:
https://xxx.xxx.xxx.xxx:yyy
• "xxx.xxx.xxx.xxx" is the IP address of a device that can be accessed from the Internet, such as the
IP address of a network router.
• "yyy" is a port number. The network router’s port forwarding settings must be configured so that traffic
arriving at port "yyy" is forwarded to the correct IP address and port of the NSX server in the LAN.
• Port forwarding settings must specify the IP address and the port number of the network router
("xxx.xxx.xxx.xxx:yyy") to transfer the packets to the NSX server in the LAN, so that the packets
sent to the global IP address and specified port of the router will be transferred to the IP address and
specified port of the NSX server in the LAN.
• Note the usage of "https" instead of "http".
• If you connect to Web Maintenance Console using TLS, a security alert window is displayed. Follow
the prompts to install a security certificate. The procedure may vary according to your browser.

5.4 Programming the NSX server
Note
The IP address and Web Maintenance Console port number for the NSX server can be changed
from their default values. If settings for the LAN port’s IP address or port number has been forgotten,
connect using the MNT port connection as described above and confirm the LAN port’s IP address
in "28.1 Network Service—[1] IP Address/Ports—Basic Settings", and the port in "28.2.3 Network
Service—[2-5] Server Feature—HTTP" in the PC Programming Manual.
3. The Web Maintenance Console login screen is displayed. Log in with the Installer level account name
and the default Installer level account password to launch the Easy Setup Wizard. For details about the
Easy Setup Wizard, see "5.4.1 Easy Setup Wizard".
Programming the NSX server data without connecting the NSX server
You can programme the NSX server system settings without using Web Maintenance Console.
NSX server data can be exported in CSV format. You can edit the data with a spreadsheet programme such
as Microsoft® Excel®. When you have finished editing the data, import the data to NSX server.
For information about exporting/importing the NSX server system data, refer to the PC Programming
Manual.
5.4 Programming the NSX server

5.4.1 Easy Setup Wizard
In the Easy Setup Wizard, you will set up the mandatory settings required for the NSX server.
When you log in to Web Maintenance Console for an NSX server that is in its initialised, factory default
state, the Easy Setup Wizard for that NSX server will launch automatically. You must log in using the
Installer level account name and password.
– The Installer level account name is "INSTALLER".
– The default Installer level account password is "1234".
Note
When you log in to Web Maintenance Console, if the NSX product Activation Key has not been installed
yet, a screen for installing the activation key will be displayed. Follow the procedure below to install the
proper activation key.
1. Click Browse….
2. Select the Activation Key file.
3. Click Install.
The System Reset starts automatically. You must log in again in the login screen after the reset.
For more information, consult your dealer.
Welcome to Panasonic NSX server

On this screen, you can either import a previously configured system data file or proceed to manually
configure the NSX server’s settings.
To import a previously configured system data file

1. Log in to Web Maintenance Console (interactive mode).
2. Click File Import.
3. In PBX Offline Data Import screen, click Browse, and then select a preconfigured DNSYS file.
4. Click Execute.
5. When you are prompted to restart the NSX server, click OK.

Note
You can import a DNSYS file of another KX-NSX series to the NSX server. (e.g., KX-NSX1000 →
KX-NSX2000). However, a DNSYS file of KX-NSX2000 cannot be imported to KX-NSX1000.
To configure the NSX server’s settings manually
Note
You can change the display language for Web Maintenance Console by selecting a language in the
WebMC Language drop-down list.
1. Click Install next to PBX installation setup.
2. On the screen that appears, specify the settings as explained below.
Location Setting
– Area: Select your area from the drop-down list.
Note
If Area is changed from its default value, a notice about restarting the NSX server is displayed.
Click OK to restart the NSX server. After the NSX server restarts, start Web Maintenance
Console again (refer to "Connecting to Web Maintenance Console" in "5.3 Starting Web
Maintenance Console"). When you start the Easy Setup Wizard again, you will continue from the
Date & Time screen.
Password Setting
– Installer password: Enter a new password (except default password) for the INSTALLER account.
– Re-enter: Enter the new password (except default password) again for confirmation.
System Multi-Connection (Trial Activation Key)
– Active: Select this option to begin a 60-day trial of the Multi-connection network feature.
– Non Active: Select this option to use the NSX server in stand-alone mode.
3. Click Start Setup Wizard, and then continue the configuration.
Date & Time

On this screen, you can specify the settings for the system date and time.
When you have finished specifying the settings, click Next to continue.
System Time
• Time Zone: Select the time zone from the drop-down list.
• Local Time: Click the Local Time box, and then specify the date and time.
SNTP Setting
• IP Address: Enter the IP Address or host name of the SNTP Server.
• Port: Enter the TCP Port for the SNTP Server.
Daylight Saving
• Select whether to enable or disable summer time (daylight saving time).
Numbering Plan
On this screen, you can specify the settings for the system numbering plan.

Feature No
Specify whether to use feature numbers that are prefixed with an asterisk (*) or not.
Note
If Type2 (without "*") is selected, the other settings are selected automatically:
• CO Access No: Dial "9"
• Operator No: Dial "0"
• Select Default value of Numbering Plan: 4 digits Extension Number, From "1001"
CO Access/Operator No
• CO Access No
Select which digit to dial to seize a trunk (automatic line access number).
• Operator No
When you select an option for CO Access No, the value for Operator Number is selected automatically:
CO access number is 1 or 9
– Operator No: Dial "0"
CO access number is 0
– Operator No: Dial "9"
Select Default value of Numbering Plan
Specify whether to use a 3-digit or 4-digit numbering plan.
• 3 digits Extension Number
• 4 digits Extension Number
After selecting the number of digits for extension numbers, specify the starting extension number.
• 3 digits Extension Number: From "101" or From "201"
• 4 digits Extension Number: From "1001" or From "2001"
Note
If Dial "1" is selected for CO Access No, the starting number is selected automatically:
– 3 digits Extension Number: 201
– 4 digits Extension Number: 2001
Trunk
On this screen, you can configure the settings for SIP trunks.
When you have finished configuring the settings, click Next to continue.
SIP Trunk
1. Click SIP Trunk Setting.
2. On the screen that appears, configure the following items for 1st Account Setting/2nd Account
Setting.
• Number of SIP Trunk: Specify the number of trunks associated with the account.
• User Name (64 characters): Enter the User Name of the account.
• Authentication ID (64 characters): Enter the authentication ID of the account.
• Authentication Password (32 characters): Enter the authentication password of the account.
• SIP Server Name / Outbound Proxy Name ( Max.100 characters): Enter the name and proxy name
of the SIP server.

• SIP Server IP Address: Enter the IP Address of the SIP server.

• SIP Server Domain / Proxy Domain ( Max.100 characters): Enter the domain and proxy domain of
the SIP server.
Notice
The appropriate values for these settings depend on your SIP provider. For details, consult your
network administrator.
3. Click OK when you have finished.
Incoming Call Distribution Group

Select whether to set separate ICD Groups automatically as DIL destinations.
User / Extension
On this screen, you can specify the settings for users and extensions for the NSX server.
Number of Users
• Normal User: specify the number of normal users.
• Mobile User: specify the number of mobile users.
• Advanced User: specify the number of advanced users.
Users Information Setting
• WebMC Language: Select the language for the user portal site from the drop-down list.
• PT Display Language Selection: Select the language of shown on PT displays from the drop-down list.
• Main Device Type: Select the device type from the drop-down list.
IP Terminal Registration Mode
Select the method for registering IP terminals.
LAN
On this screen, you can specify the settings for the LAN the NSX server is on.
The IP addresses for the NSX server, DNS server, and DSP cards can be assigned automatically through a
DHCP server or entered manually.
Notice
• If an external DHCP server is in use, it must be able to use the "client identifier" option specified by
RFC 2131.
• If an external DHCP server is in use, the NSX server DHCP Server feature must be disabled.
• The NSX server will not start properly if IP addresses cannot be assigned automatically by the DHCP
server when the NSX server has been set to obtain IP addresses automatically. In this case, you need
to consult your network administrator because the DHCP server in your network may not be running
or a network failure may have occurred. If the DHCP server is not available, enter IP addresses
manually, then restart the NSX server. If the NSX server cannot be accessed over the network,
connect the PC directly to the NSX server with an Ethernet cable and access Web Maintenance
Console using a direct connection.
For details about connecting the PC directly to the NSX server, refer to "Direct Connection" in "5.2 PC
Connection".

• The appropriate values for these settings depend on your network configuration. For details, consult
your network administrator.
Note
If the IP addresses are changed from their default values, a notice about restarting the NSX server is
displayed at the end of the Easy Setup Wizard. Click OK to restart the NSX server. After the NSX server
restarts, start Web Maintenance Console again (refer to "Connecting to Web Maintenance Console" in
"5.3 Starting Web Maintenance Console").
IP Address for main unit

1. Select the method for setting the IP address information.
• Obtain an IP address automatically
• Use the following IP address
2. If you selected Use the following IP address, specify the following settings.
• IP Address: Enter the IP address for the NSX server.
• Subnet Mask: Enter the subnet mask of the LAN.
• Default Gateway: Enter the IP address of the LAN’s default gateway.
IP Address for DNS
• Obtain DNS server address automatically
• Use the following DNS server address
2. If you selected Use the following DNS server address, specify the following settings.
• Preferred DNS IP Address: Enter the IP Address of the primal DNS server.
• Alternative DNS IP Address: Enter the IP Address of the alternative DNS server.
IP Address for DSP
• Obtain DSP IP address automatically
• Use the following DSP IP address
2. If you selected Use the following DSP IP address, specify the following items for DSP Card #1/DSP
Card #2/DSP Card #3.
• IP Address1: Enter the IP Address 1 of the DSP card.
• IP Address2: Enter the IP Address 2 of the DSP card.
Maintenance Setting
On this screen, you can specify the settings of the maintenance for the system.
When you have finished specifying the settings, click Finish to finish the Easy Setup Wizard.
Remote Access Acceptance

Select the check boxes for the types of users to grant remote access to, if you agree to allow remote
maintenance by maintenance technicians.

5.4.2 After the Easy Setup Wizard has been Completed
SNMP Setting
1. In SNMP Agent Function, specify whether to use the SNMP agent function and the SNMP protocol
version.
• Disable: Do not use the SNMP Agent Function, select this.
To use the SNMP agent function, select the SNMP protocol version.
• SNMPv3
• SNMPv2c
• SNMPv1
2. Depending on the SNMP protocol version, the settings to specify differ.
SNMPv2c/SNMPv1
Specify the settings of the network.
• Port Number (receive): Enter the port number for the SNMP manager.
• MIB - Syscontact: Enter the system contact of the MIB for the SNMP manager.
• MIB - SysName: Enter the system name of the MIB for the SNMP manager.
• MIB - SysLocation: Enter the system location of the MIB for the SNMP manager.
SNMPv3
In addition to the above settings, specify the following network settings.
• User Name: Enter the user name of the SNMP manager.
• Security Level: Select the security level from the drop down list.
• Authentication Method: Select the authentication method from the drop down list.
• Authentication Password: Enter the password for authentication.
• Encryption Method: Displays the encryption method.
• Encryption Password: Enter the password for encryption.
SNMP Manager
1. Select the method for setting the SNMP manager.
• Manager IP Address: Enter the IP address of the SNMP Manager.
• Manager Host Name: Enter the host name of the SNMP Manager.
2. Specify additional information about the SNMP manager.
• TRAP port number (send): Enter the TRAP port number if you selected Manager IP Address
above.
• Community Name: Enter the community name if you selected Manager Host Name above.
5.4.2 After the Easy Setup Wizard has been Completed

Changing IP Address Settings
• Do not change the IP address of the NSX server once IP telephones are registered to the NSX server
using the set IP address. The IP telephones will not operate properly if the IP address of the NSX server
is changed. When an external DHCP server is used to automatically assign IP addresses, it must be
configured to always allocate the same IP address to the NSX server. For details, consult your network
administrator.
IP addressing information for the NSX server can also be changed from Web Maintenance Console. For
details about programming IP address, refer to "28.1 Network Service—[1] IP Address/Ports—Basic
Settings" in the PC Programming Manual.

5.4.3 Enabling the DHCP Server Feature
Changing the Display Language

The language used for Web Maintenance Console can be changed. For details about programming WebMC
Language, refer to "28.1 Network Service—[1] IP Address/Ports—Basic Settings" in the PC Programming
Manual.
5.4.3 Enabling the DHCP Server Feature

This NSX server is equipped with a DHCP Server feature. When the feature is enabled, it allows you to
centrally manage and automate the assignment of IP addresses for the devices located in same LAN using
Web Maintenance Console.
1. Click Setup → Network Service → Server Feature → DHCP.
2. On the DHCP Server tab, select Enable for DHCP Server.
3. Enter valid settings for the IP address auto assignment.
Note
For details about IP address auto assignment settings, refer to "28.2.1 Network Service—[2-1]
Server Feature—DHCP(LAN)" in the PC Programming Manual.
4. Click OK.
Note
If an external DHCP server is in use, do not enable the DHCP Server feature. Doing so may allocate
inappropriate IP addressing information to the devices.
5.4.4 Installing the Virtual IP Cards to the NSX server

1. a. Click Setup → PBX Configuration→ Configuration → Slot.
b. Click Virtual.
2. a. Click on the name of the desired virtual card tab.
b. From the Total number of cards drop-down list, select the desired number of cards.
3. A confirmation message will be displayed. Click OK.
5.4.5 Installing Additional Activation Keys

The corresponding number of IP trunks, IP telephones or enhanced features can be activated by installing
the downloaded activation key file(s) using Web Maintenance Console.
Installing the Activation Key Files

Be sure to connect the PC to the NSX server in advance. For details about Web Maintenance Console, refer
to "5.3 Starting Web Maintenance Console".
1. Log in to Web Maintenance Console using the Installer level account.
2. Click Maintenance → Utility → Activation Key Installation.
Activation Key Installation window will be displayed.
3. Click Browse and specify the directory where the activation key files are stored, and click Open.
4. A list of activation key files stored in the specified directory is displayed. Check the boxes next to the
activation keys to install to the NSX server, and click Install.
5. When installation is complete, the message, "The activation key has been installed and activated
successfully!" is displayed.
6. Click OK.

5.4.6 Configuration of the Activation Keys
Notice
The activation key file can only be installed in the NSX server with the MPR ID number entered when
the activation key file was downloaded. The activation key file cannot be reissued unless the mother
board crashes.
Note
• You can click the provided link to directly access activation key information and programme the
number of activated IP trunks and IP softphones.
• For information about programming activation keys using Web Maintenance Console, refer to "9.3
PBX Configuration—[1-1] Configuration—Slot—Activation Key Status" in the PC Programming
Manual.
5.4.6 Configuration of the Activation Keys

Depending on your configuration, it may be necessary to programme the number of provided IP Trunk
channels to be used for H.323 trunks. By default, all of the provided IP Trunk channels will be used for SIP
trunks.
1. a. Click Setup → PBX Configuration→ Configuration → Slot.
b. Click Activation Key.
2. In Number of IP-GW to be used, type the number of IP Trunk channels to be used for H.323 trunks.
Note
If you have changed the value for Number of IP-GW to be used, you must click Execute to restart
the V-IPGW cards for the change to take effect.
3. Click OK.
5.5 Programming a Multi-connection Network

The Add Site Wizard, which is run from the Home Screen of the NSX server, will add other KX-NS series
PBXs connected to the private IP network to your Multi-connection network as Expansion gateways.
Notice
When using a Multi-connection network, do not disable the NSX server’s FTP server settings. For
details, refer to "28.2.2 Network Service—[2-3] Server Feature—FTP" in the PC Programming Manual.
Note
Before you add a site, you must install the software for KX-NSX series in the PBX you will register as an
expansion gateway.
Log in to the Web Maintenance Console of the KX-NS series PBX and install the software for NSX
server. Install the activation key for Expansion GW connection (KX-NSXF007). For more information,
refer to "6.4.3 Information about Expansion Gateways".
If a temporary, significant increase in the amount of IP packet communication occurs between the sites
where the PBXs are installed utilising a multi-connection network, the IP packets between the PBXs may
not be reached. To prevent the loss and delay of control packets (SSAP/PSAP) between PBXs and
stabilize the operation, the order of priority can be specified. For details, refer to 6.1.8 QoS (Quality of
Service).
There are 2 types of programming for a Multi-connection network.
Configure the system settings of the Expansion Gateway first

1. Start the KX-NS series PBX.
When you log in to the Web maintenance console The Easy Setup wizard will launch.

5.5 Programming a Multi-connection Network
2. Follow the prompts of the Easy Setup wizard. The necessary settings differ depending on the PBX
model.
KX-NS1000
• Location Setting
• PBX Setting
• LAN Setting
• WAN Setting
*1
• Registration Setting
KX-NS300/KX-NS500/KX-NS700
*1
• Location Setting
• Date & Time
• LAN
• VoIP (Ext)
3. Click Finish to complete the wizard.
The preparation for the Expansion Gateway is ready.
4. Log in to the NSX server and follow steps 4. to 7. below to register the expansion gateway to the Multi-
connection network.
*1 To operate the expansion gateway under Simplified Isolated mode, you can upload a pre-configured system setting data file
(DxSYS) for the expansion gateway on this screen. However, a system data file (DxSYS) for software file version 4.2 or 7.0 for
KX-NS series PBXs can be uploaded.
Register the gateway through the NSX server

1. Click the Add Slave icon ( ) on the Home screen to start the Add Site Wizard.
2. Follow the prompts of the Add Site Wizard to complete following settings:
• PBX Setting
• WAN Setting
• Registration Setting
• SNTP / Daylight Saving
• Maintenance Setting
3. Click Finish to complete the wizard.
To set up additional expansion gateways, repeat steps 1 to 3 for each gateway.
4. Click Registration on the Home screen.
A list of KX-NS series PBXs set up as expansion gateways will be displayed under Available Site.
5. Select PBXs by their assigned site names and click the right arrow to move them to Selected Site for
Registration.
6. Click Next to start the registration process.
7. On the Registration screen, the result of the registration process is shown.
Click Cancel to continue.
Registered Expansion Gateways can now be viewed and selected on the Home Screen for programming.
To assign the Sub-Administrator to each site

1. Click Setup → Maintenance Personnel → Sub Administrator Setting → Accounts.
2. Click Edit Sub-Administrator to edit settings for sub administrator account.

5.6 Programming an H.323 QSIG Network
• Default login name is "S-ADMIN001"—"S-ADMIN032".

• Default password is "0001"—"0032".
3. Click OK.
4. Select the Activated checkbox in Sub-Administrator number to validate Sub-administrator account.
5. Click Setup → Maintenance Personnel → Sub Administrator Setting → Site Assignment.
6. In Sub-Administrator column, Select the Sub-Administrator account to maintain each site.
LED Indication
In a Multi-connection network, you can monitor the network condition through the LED indication.
NSX server (in a Multi-
Unit Type NSX server (Stand alone) Expansion Gateway
connection)
LED Name
SYSTEM SYSTEM MASTER/
Network STATUS STATUS STATUS
MODE MODE PBX-MODE
condition
Green Green Amber
Power On OFF Green OFF
(Flashing) (Flashing) (Flashing)
Operating Green Green Green Green Green Amber
Being Green
- - - - Amber
Registered (Flashing)
Registration is
- - - - Green Amber
Completed
5.6 Programming an H.323 QSIG Network

There are 2 methods to programme the Virtual VoIP Gateway Card (V-IPGW card) to establish VoIP
communications between the NSX server (called the "local PBX" in this section) and PBXs at remote
locations ("remote PBX"), as follows:
PBX code method The caller dials the unique PBX code of the unit to which the called party is
connected, in addition to the destination number.
Extension number The caller dials only the destination number of the called party to call through
method units at different locations (hence there are fewer digits to dial than with the
PBX code method).
Conditions
• If you enable Enhanced QSIG functionality and configure a QSIG network, the highest COS number for
all PBXs must be uniform across the network.
Note
• For a detailed explanation about each method, refer to "4.3 Private Network Features" in the Feature
Manual.
• Portions of this software are © 1996–2006 RADVISION Ltd. All intellectual property rights in such
portions of the Software and documentation are owned by RADVISION and are protected by United
States copyright laws, other applicable copyright laws and international treaty provisions. RADVISION
and its suppliers retain all rights not expressly granted.

5.6.1 Assigning the Hunt Pattern
5.6.1 Assigning the Hunt Pattern

The hunt pattern determines how to route incoming calls through virtual IP trunks to the NSX server. The
procedure below demonstrates the process of programming the hunt pattern of the local PBX (NSX server).
After the hunt pattern at the local PBX has been fully assigned, repeat the procedure for the hunt pattern at
the remote PBX with the appropriate setting values.
1. a. Click Setup → PBX Configuration → Configuration → Slot.
b. Click V-IPGW.
c. Click Port Property.
d. Click Incoming Settings.
2. a. When using the PBX code method:
In the Leading Number cell, type the local PBX code and extension starting digit.
When using the extension number method:

In the Leading Number cell, type the local extension starting digit.
b. Click OK to return to the Port Property screen.
Note
For more details about hunt pattern assignment, refer to "9.14.1 PBX Configuration—[1-1] Configuration
—Slot—V-IPGW128—Port Property—DN to Call Distribution Port Group" in the PC Programming
Manual.
5.6.2 Programming the Address Translation Table

The function of an address translation table in a VoIP network is to provide 2-way translation of telephone
*1
numbers and IP addresses . Therefore, a caller can reach the destination by dialling the number without
knowing the destination IP address.
The procedure below demonstrates the process of programming the address translation table at the local
PBX. After the address translation table at the local PBX has been fully programmed, repeat the procedure
for the address translation table at the remote PBX with the appropriate setting values.
b. Click V-IPGW.
c. If the status of the card is INS, click INS in the Status column, and then click OUS in the pop-up
window.
d. Click Port Property.
e. Click Outgoing setting.
f. On the DN to Gateway screen, click Gateway Setting.
Note
To display the DN to Gateway screen, the Gatekeeper Available setting must be set to
Disable on the V-IPGW card’s Card Property screen. Refer to "9.13 PBX Configuration—
[1-1] Configuration—Slot—V-IPGW128—GateKeeper Property" in the PC Programming
Manual.
2. In the MAIN tab, do the following to configure the gateway entry for the remote PBX:
a. In the GW Name cell, type a unique identifier of the destination in the VoIP network.
b. In the GW IP Address cell, type the IP address of the destination gateway device.

5.6.3 Programming the Network Settings
c. In the GW Group cell, select None.

*1 IP address-to-telephone number translation can also be handled by using an H.323 Gatekeeper device. To
configure Gatekeeper devices, refer to the manufacturer’s documentation. This manual focuses on the method
using the V-IPGW card’s internal address translation capabilities.
d. Click OK to return to the DN to Gateway screen.

b. Click V-IPGW.
window.
d. Click Port Property.
e. Click Outgoing setting.
f. When using the PBX code method:
In the Leading Number cell, type the remote PBX code and starting digit of destination extension.
When using the extension number method:

In the Leading Number cell, type the remote extension starting digit.
g. In the Remaining Number of Digits cell, type a number of digits to dial following the leading
number.
h. In GW No./GW Group Selection, select GW No.
i. In the GW No. cell, select 1 (the gateway entry for the destination gateway device at the remote
PBX).
j. Click OK.
Note
Having the value None for GW Group means that the destination gateway device does not belong to
any gateway group. Grouping is useful when installing multiple gateway devices at one location. For
details, refer to "9.14.2 PBX Configuration—[1-1] Configuration—Slot—V-IPGW128—Port Property—DN
to Gateway—GW Settings–Main" in the PC Programming Manual.

For successful operation of a VoIP network using the V-IPGW card, network settings for the unit at each
location must be programmed appropriately. For a detailed discussion of related features, refer to the
Feature Manual.
This section details the procedure to programme the network settings for the local PBX. After the
programming for the local PBX has been done, repeat the procedure for the remote PBX with the
appropriate setting values.
The following procedures describe the process of programming the network settings for each numbering
method.
Programming for the PBX Code Method

b. Click V-IPGW.
window.
d. Repeat step c for each V-IPGW card until all V-IPGW cards are OUS.
Confirm that all V-IPGW cards are OUS.
2. a. Click Setup → PBX Configuration → CO & Incoming Call.

b. Click CO Line Settings.

c. Type the CO Name and assign an unused Trunk Group Number to be used for all IP trunks.
d. Click OK.
3. Note
Before changing Numbering Plan settings, when a V-SIPEXT card is installed, change the status
of the card(s) to OUS.
a. Click Setup → PBX Configuration → System.
b. Click Numbering Plan.
c. Click Main.
d. Click the Features tab.
e. In the TIE Line Access cell, type the dialling number.
f. Click OK.
4. a. Click Setup → PBX Configuration → Private Network.
b. Click TIE Table.
c. In the Own PBX Code cell, type the PBX code of the local PBX in the network.
d. In the first unused Leading Number cell, type the PBX code of the remote PBX in the network.
e. In the corresponding Trunk Group list, select the number of the trunk group to be used when
making calls.
f. If it is necessary to add number(s) to the input number, enter the number(s) to be added in the
desired Added Number cell.
If it is necessary to delete number(s) from the input number, enter the number(s) to be deleted in
the desired Removed Number of Digits cell.
g. Click OK.
b. Click V-IPGW.
c. Click OUS in the Status column, and then click INS in the pop-up window.
d. Repeat step c for each V-IPGW card until all V-IPGW cards are INS.
Programming for the Extension Number Method

b. Click V-IPGW.
window.
d. Repeat step c for each V-IPGW card until all V-IPGW cards are OUS.
Confirm that all V-IPGW cards are set to OUS.
2. a. Click Setup → PBX Configuration → CO & Incoming Call.
b. Click CO Line Settings.
c. Type the CO Name and assign an unused Trunk Group Number to be used for all IP trunks.
d. Click OK.

5.7 Programming SIP Trunks
3. Note
Before changing Numbering Plan settings, when a V-SIPEXT card is installed, change the status
of the card(s) to OUS.
a. Click Setup → PBX Configuration → System.
b. Click Numbering Plan.
c. Click Main.
d. Click the Other PBX Extension tab.
e. In the Dial cell, type a starting digit of destination extension.
f. Click OK.
4. a. Click Setup → PBX Configuration → Private Network.
b. Click TIE Table.
c. In the Leading Number cell, type the starting digit of destination extension.
d. Click OK.
b. Click Virtual → V-IPGW.
c. Click OUS in the Status column, and then click INS in the pop-up window.
d. Repeat step c for each V-IPGW card until all V-IPGW cards are INS.
Note
For details about network parameter settings, refer to the relevant sections of the PC Programming
Manual.

The Virtual SIP Trunk Card (V-SIPGW) is a virtual trunk card which is designed to be easily integrated into
an Internet Telephony Service provided by an ITSP (Internet Telephony Service Provider).
Various settings can be programmed for each virtual SIP gateway port.
Accessing Port Properties

1. Click Setup → PBX Configuration → Configuration → Slot.
2. Click the V-SIPGW tab.
3. If the status of the card is INS, click INS in the Status column, and then click OUS in the pop-up window.
Programming Port Properties

Automatic Programming
Some of the parameters can be automatically programmed by selecting the desired SIP provider for each
virtual SIP gateway port. Available SIP providers can be selected, and a different SIP provider can be
assigned to each virtual SIP gateway port.
Note
It is necessary to import a SIP provider list file (comma-separated value [CSV] file) in advance to use the
automatic programming feature.
Follow the steps below to configure a SIP provider.
1. Click Select Provider.

A dialogue box will appear. Available virtual SIP gateway port numbers are displayed in the list.
2. From the Provider menu, select the desired SIP provider.
Note
If the desired SIP provider is not shown in the drop-down list, it is necessary to programme the
desired parameters manually. For information about the manual programming procedure, refer to
"Programming Port Properties" below.
3. Highlight the desired port numbers or click Select All to select all the virtual SIP gateway port numbers
to be assigned to the SIP provider selected in step 2.
4. Click Execute.
Appropriate setting values designated by the SIP provider will be set in the parameters for the virtual SIP
gateway ports.
Manual Programming
Follow the steps below to programme the parameters which are not automatically programmed by selecting
a provider.
1. Click the desired tab.
2. Enter information or select settings from the drop-down list for each parameter.
• Parameters that Require Manual Programming
Manual programming is compulsory for the following parameters:
– User Name: Specifies the user name (SIP Account) provided by the SIP provider. (Max. 64
characters)
– Authentication ID: Specifies the authentication ID required for registration with the SIP server.
(Max. 64 characters)
– Authentication Password: Specifies the authentication password used for registration with the
SIP provider. (Max. 32 characters)
Follow the steps below to programme these 3 parameters.
1. Click an Account tab.
2. In the User Name column, enter the user name provided by the SIP provider.
3. In the Authentication ID column, enter the authentication ID required for registration with the SIP
server.
4. In the Authentication Password column, the authentication password used for registration with the
SIP provider.
5. Click OK.
Adding Settings to Provider Profiles

1. Click Add Provider.
A dialogue box will appear. Available virtual SIP gateway port numbers are displayed in the list.
2. Highlight the desired port numbers or click Select All to select all the virtual SIP gateway port numbers
to add the settings to provider profiles.
3. Click Execute.
Note
For more details about SIP gateway port settings, refer to the PC Programming Manual.

5.8 Assigning Networking Information to IP Telephones
5.8 Assigning Networking Information to IP

Telephones
For the KX-NSX series, the IP telephone cannot be used unless it is registered in the User Container, even
if the IP addressing information is assigned to the telephone as explained in this section. For more details
about registering to the User Container, refer to "5.10 Configuration of Users".
5.8.1 Assigning IP Addressing Information

The IP telephone’s IP address, subnet mask address and default gateway address, as well as the IP
address of the registering NSX server or expansion gateway (referred to simply as the "server" in this
section) must be assigned to the IP telephone before it can be used on the network. This IP addressing
information can be assigned in the following ways:
For IP-PTs
• Using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-PT is on the
same LAN as the server
The DHCP server automatically assigns the IP address of the IP-PT, the subnet mask address, and the
default gateway address to the IP-PT.
The server’s IP address can also be assigned automatically to the IP-PT in the process of being
registered to the server. For details about registering the IP-PT, refer to "5.9.1 Registering IP Telephones".
Note
For information about the DHCP Server feature, refer to "6.1.2 DHCP (Dynamic Host Configuration
Protocol) Server".
• Using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-PT is on a
remote office LAN
While the DHCP server automatically assigns the IP address of the IP-PT, the subnet mask address, and
the default gateway address to the IP-PT, the server’s IP address must be assigned manually.
Follow the procedure below to assign the server’s IP address.
If you need to set VLAN parameters, follow the procedure described in "5.8.2 Setting VLAN Parameters"
after assigning the IP addresses, without ending programming.
Note
• By assigning the server’s IP address to one IP-PT, it is possible to assign the server’s IP address to
other IP-PTs or IP-CSs on the same LAN through system programming. For details, refer to "9.16
PBX Configuration—[1-1] Configuration—Slot—V-IPEXT128—Port Property—Option—Announce
Mode" in the PC Programming Manual.
• IP-PTs can only receive IP addressing information from a DHCP server on its own LAN. Therefore,
when IP-PTs are located on several LANs, a DHCP server is required on each LAN.
• Since the default setting of the DHCP client function is enabled for IP-PTs, simply connect the
IP-PTs to the LAN to use the DHCP server.

KX-NT500 series (except KX-NT551) and KX-NT300 series (except KX-NT321)
To start programming
SETUP
Supply power to the IP-PT.
Press "SETUP"
when it is displayed.
To enter the IP address of the server
*1
Select "PBX". ENTER Select "PBX IP Address". ENTER Select "Primary PBX".
Server IP Address
ENTER ENTER
*1
To enter the IP address of the Secondary server (optional)
Server IP Address
Select "Secondary PBX". ENTER ENTER
To set VLAN parameters

To the VLAN settings
OR
To end programming
STORE The IP-PT will reboot

and can then be
registered to the server.
Return to the
Menu screen. Press "STORE".
*1 For KX-NT300 series: Software version 2.00 or later only
Note
The illustrations may differ from the buttons on your telephone.

KX-NT551/KX-NT321

Press PROGRAM
while "Searching" is displayed.
Select "PBX". Press SP-PHONE. Select "PBX IP Press SP-PHONE. Select "Primary
Address". PBX".
Server IP Address
Press SP-PHONE. Press SP-PHONE.
To enter the IP address of the Secondary server (if required)
Server IP Address
Select "Secondary Press SP-PHONE. Press SP-PHONE.

PBX".
Press HOLD twice to return

to the Menu screen.

OR
To end programming
The IP-PT will reboot
and can then be
Press STORE.
Note
To confirm the connection to the secondary server after assigning IP addressing information, (1) turn
the IP-PT’s power off, and (2) hold the STORE button and 2 key while turning the power on.
• Not using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-PT is on
the same LAN as the server
Only the server’s IP address can be assigned automatically to the IP-PT in the process of being
registered to the server. For details about registering the IP-PT, refer to "5.9.1 Registering IP Telephones".

Follow the procedure below to assign the IP address of the IP-PT, the subnet mask address, and the
default gateway address manually.
SETUP
Press "SETUP" when it is displayed.
To set the IP address of the IP-PT
Select "Network". ENTER Select "Disable" Select "IP Address". ENTER

for DHCP setting.
IP Address*1
ENTER
To set the subnet mask address
Subnet Mask Address*2

Select "Subnet Mask". ENTER ENTER
To set the default gateway address (if required)
Default Gateway Address*3
Select "Default Gateway". ENTER ENTER
*4
Return to the Select "PBX". ENTER Select "PBX IP ENTER Select "Secondary
Menu screen. Address". PBX".
Server IP Address
ENTER ENTER
Continued on next page

Continued from previous page

Return to the
Menu screen.
OR
To end programming

and can then be
Return to the Press "STORE".
Menu screen.
*1 Valid IP address range: "1.0.0.0" to "223.255.255.255"

*2 Valid subnet mask address range: "0–255.0–255.0–255.0–255" (except "0.0.0.0" and "255.255.255.255")
Note

KX-NT551/KX-NT321

Press PROGRAM
Select "Network". Press SP-PHONE. Select "DHCP (Disable)". Press SP-PHONE

twice.
IP Address*1
Press SP-PHONE.
Select "Subnet Mask". Press SP-PHONE. Press SP-PHONE.
To set the default gateway address (if required)
Select "Default GW". Press SP-PHONE. Press SP-PHONE.
Press HOLD to return Select "PBX". Press SP-PHONE. Select "PBX IP Press SP-PHONE. Select "Secondary
to the Menu screen. Address". PBX".
Server IP Address

to the Menu screen.


OR
To end programming
and can then be
Press STORE.

Note
• Not using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-PT is on a
remote office LAN
All of the IP addressing information must be assigned manually.
Follow the procedure below to assign the IP addressing information.
Note
By assigning the server’s IP address to one IP-PT, it is possible to assign the server’s IP address to
other IP-PTs or IP-CSs on the same LAN through system programming. For details, refer to "9.16
PBX Configuration—[1-1] Configuration—Slot—V-IPEXT128—Port Property—Option—Announce
Mode" in the PC Programming Manual.

SETUP
Press "SETUP" when it is displayed.
Select "Network". ENTER Select "Disable" Select "IP Address". ENTER

for DHCP setting.
IP Address*1
ENTER

Select "Subnet Mask". ENTER ENTER
To set the default gateway address
Select "Default Gateway". ENTER ENTER

*4
Return to the Select "PBX". ENTER Select "PBX IP ENTER Select "Primary
Menu screen. Address". PBX".
Server IP Address
ENTER ENTER


*4
Server IP Address
Select "Secondary PBX". ENTER ENTER

Return to the
Menu screen.
OR
To end programming

and can then be
Menu screen.

Note

KX-NT551/KX-NT321

Press PROGRAM
Select "Network". Press SP-PHONE. Select "DHCP (Disable)". Press SP-PHONE

twice.
IP Address*1
Press SP-PHONE.
Select "Subnet Mask". Press SP-PHONE. Press SP-PHONE.
To set the default gateway address
Select "Default GW". Press SP-PHONE. Press SP-PHONE.
Press HOLD to return Select "PBX". Press SP-PHONE. Select "PBX IP Press SP-PHONE. Select "Primary
to the Menu screen. Address". PBX".
Server IP Address
Server IP Address
Select "Secondary Press SP-PHONE. Press SP-PHONE.

PBX".


to the Menu screen.

OR
To end programming
and can then be
Press STORE.

Note
For SIP Phones (including P-SIP)

Using a DHCP server (DHCP Server feature or an external DHCP server) to automate the assignment
of IP addressing information
The IP address of the SIP phone, the subnet mask address, and the default gateway address can be
assigned to the SIP phone automatically by the DHCP server.
The server’s IP address must be assigned manually on the SIP phone side.
For instructions, refer to the documentation of the SIP phone.
Not using a DHCP server (DHCP Server feature or an external DHCP server) when assigning IP
addressing information
For instructions, refer to the documentation of the SIP phone.
Note
• A SIP phone can only receive IP addressing information from a DHCP server on its own LAN.
Therefore, when SIP phones are located on several LANs, a DHCP server is required on each LAN.
• When the DHCP client function is enabled for SIP phones, simply connect them to the LAN to use the
DHCP server. For details about the DHCP client function setting, refer to the documentation of the
SIP phone.

For IP-CSs
Using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-CS is on the
The DHCP server automatically assigns the IP address of the IP-CS, the subnet mask address, and the
default gateway address to the IP-CS.
The server’s IP address can also be assigned automatically to the IP-CS in the process of being
For details about registering the IP-CS, refer to "5.9.1 Registering IP Telephones" and corresponding
manuals for the IP-CS.
Note
• For information about the DHCP Server feature, refer to "6.1.2 DHCP (Dynamic Host
Configuration Protocol) Server".
Using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-CS is on a
remote office LAN
While the DHCP server automatically assigns the IP address of the IP-CS, the subnet mask address,
and the default gateway address to the IP-CS, the server’s IP address must be assigned manually.
To assign the server’s IP address, refer to corresponding manuals for the IP-CS.
If you need to set VLAN parameters, refer to the corresponding manuals for the IP-CS.
Note
• By assigning the server’s IP address to one IP-CS, it is possible to assign the server’s IP address
to other IP-PTs or IP-CSs on the same LAN through system programming. For details, refer to
"9.20 PBX Configuration—[1-1] Configuration—Slot—V-IPCS16—Port Property—Option—
Announce Mode" in the PC Programming Manual.
• IP-CSs can only receive IP addressing information from a DHCP server on its own LAN.
Therefore, when IP-CSs are located on several LANs, a DHCP server is required on each LAN.
• Since the default setting of the DHCP client function is enabled for IP-CSs, simply connect the
IP-CSs to the LAN to use the DHCP server.
Not using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-CS is on the
Only the server’s IP address can be assigned automatically to the IP-CS in the process of being
For details about registering the IP-CS, refer to "5.9.1 Registering IP Telephones" and corresponding
manuals for the IP-CS.
To assign the IP address of the IP-CS, the subnet mask address, and the default gateway address
manually, refer to corresponding manuals for the IP-CS.
If you need to set VLAN parameters, refer to corresponding manuals for the IP-CS.
Not using a DHCP server (DHCP Server feature or an external DHCP server) when the IP-CS is on a
remote office LAN
To assign the IP addressing information, refer to corresponding manuals for the IP-CS.
If you need to set VLAN parameters, refer to corresponding manuals for the IP-CS.
Note
By assigning the server’s IP address to one IP-CS, it is possible to assign the server’s IP address to
other IP-PTs or IP-CSs on the same LAN through system programming. For details, refer to "9.20 PBX
Configuration—[1-1] Configuration—Slot—V-IPCS16—Port Property—Option—Announce Mode" in the
PC Programming Manual.

5.8.2 Setting VLAN Parameters
5.8.2 Setting VLAN Parameters

To establish voice communications between IP telephones, the primary ports of the IP telephones and the
connected server must belong to the same VLAN. Consult your network administrator and obtain the
appropriate VLAN ID.
If you are using an IP telephone equipped with two ports, it is possible to place primary and secondary ports
of the IP telephone on different VLANs by assigning separate VLAN IDs to each port.
Follow the procedure below for all IP-PTs on the network, using appropriate VLAN IDs.
Note
The procedure for SIP phones may vary depending on the type of the SIP phone being used. Refer to
the documentation of your SIP phone for instructions.
After assigning
the IP addresses
Select "QoS". ENTER Select "VLAN". ENTER Select "Enable" for

VLAN setting.
To set the VLAN ID for the primary port
VLAN ID
1–4094
Select "Primary port". ENTER Select "VLAN ID". ENTER 0–4094 (Only for KX-NT55x)
VLAN Priority*1
ENTER Select "VLAN Priority". ENTER 0–7 ENTER
To set the VLAN ID for the secondary port
Return to the Select ENTER Select "VLAN ID". ENTER

VLAN setting screen. "Secondary port (TO PC)".
VLAN ID 1
VLAN Priority*1
1–4094 ENTER Select ENTER 0–7 ENTER

0–4094 (Only for KX-NT55x) "VLAN Priority".
To end programming

and can then be
Menu screen.
*1 The VLAN priority of the primary port must be set higher than the priority of the secondary port. The larger the number, the higher
the priority.

5.8.3 Setting LLDP Parameters
Note
KX-NT551/KX-NT321
After assigning
the IP addresses
Select "QoS". Press SP-PHONE. Select "VLAN". Press SP-PHONE.
Select "VLAN (Enable)". Press SP-PHONE.
VLAN ID
1–4094
Select "VLAN (Primary)". Press SP-PHONE. Select "VLAN ID". 0–4094 Press SP-PHONE.
(Only for KX-NT551)
VLAN Priority*1
Select "Priority". 0–7 Press SP-PHONE.
VLAN ID
Select "VLAN (Secondary)". Press SP-PHONE. Select "VLAN ID". 1–4094 Press SP-PHONE.
0–4094
(Only for KX-NT551)
VLAN Priority*1
To end programming
and can then be
Press HOLD three Press STORE.

times to return to the
Menu screen.
the priority.

LLDP-MED is a technique for IP telephones to obtain VLAN settings automatically from a network device,
such as a Network Switch.

If you are using an IP telephone equipped with two LAN ports, the primary and secondary ports of the IP
telephone can be placed on different VLANs by assigning a separate VLAN ID to each port. Follow the
procedure below for all IP-PTs on the network, using appropriate VLAN IDs.
Note
• This feature is available only for KX-NT551, KX-NT553, and KX-NT556 IP-PTs.
• VLAN settings configured through PT programming have priority over VLAN settings configured
through the LLDP-MED function.
• To enable or disable the sending of LLDP packets from the server, consult your dealer.

KX-NT553/KX-NT556
After assigning
the IP addresses
Select "QoS". ENTER Select "LLDP". ENTER Select "Enable" for

LLDP setting.
VLAN ID*1
Select "Primary port". ENTER Select "VLAN ID". ENTER 0–4094
VLAN Priority*1*2
Select "VLAN Priority". ENTER 0–7
Return to the Select ENTER Select "VLAN ID". ENTER

LLDP setting screen. "Secondary port".
*1*2
VLAN ID*1 1
VLAN Priority
0–4094 ENTER Select ENTER 0–7 ENTER

"VLAN Priority".
To set the Interval time for LLDP
Return to the Select ENTER Select ENTER

LLDP setting screen. "LLDP (Secondary)". "LLDP (Interval)".
INTERVAL
1–3600 ENTER
To end programming
and can then be
Menu screen.
*1 The VLAN ID and the VLAN priority are set automatically for the primary port; these are reference only. However, the VLAN ID
and the VLAN priority for secondary port must be set manually.
the priority.

KX-NT551
After assigning
the IP addresses
Select "QoS". Press SP-PHONE. Select "LLDP". Press SP-PHONE.
Select "Enable" for Press SP-PHONE.

LLDP setting.
VLAN ID*1
Select "LLDP (Primary)". Press SP-PHONE. Select "VLAN ID". 0–4094
VLAN Priority*1*2
Select "Priority". 0–7
VLAN ID*1
Select "LLDP (Secondary)". Press SP-PHONE. Select "VLAN ID". 0–4094 Press SP-PHONE.
VLAN Priority*1*2
To set the Interval time for LLDP
Select "LLDP (Secondary)". Press SP-PHONE. Select Press SP-PHONE.

"LLDP (Interval)".
INTERVAL
1–3600 Press SP-PHONE.
To end programming
and can then be
Press HOLD three Press STORE.

times to return to the
Menu screen.
*1 The VLAN ID and the VLAN priority are set automatically for the primary port; these are reference only. However, the VLAN ID
and the VLAN priority for secondary port must be set manually.

5.8.4 Setting Diffserv Parameters
the priority.
5.8.4 Setting Diffserv Parameters

Differentiated Services (DiffServ, or DS) is an IP-based QoS technique used to control QoS of VoIP
communications by setting the DS field in the header of IP packets. Consult your network administrator for
the appropriate setting values for the DS field.
Follow the procedure below to set the Diffserv parameters. Only IP-PTs can be used to set the parameters.
SETUP
Press "SETUP" Select "Qos". ENTER Select "Diffserv". ENTER

To set the DS field value for the primary port
Select "Primary Port". ENTER Select "Enable". ENTER
Diffserv
0.0–7.7 ENTER
To set the DS field value for the secondary port (only for KX-NT300 series)
Return to the Select ENTER Select "Enable".

Diffserv setting screen. "Secondary Port (TO PC)".
Diffserv
ENTER 0.0–7.7 ENTER
To end programming

and can then be
Menu screen.
Note

5.8.5 Configuration of IP Ports
KX-NT551/KX-NT321
Press PROGRAM while Select "QoS". Press SP-PHONE. Select "Diffserv". Press SP-PHONE.
"Searching" is displayed.
To set the DS field value for the primary port
Select "Primary Port". Press SP-PHONE. Select "DS (Enable)". Press SP-PHONE.
Diffserv
0.0–7.7 Press SP-PHONE.
To set the DS field value for the secondary port (only for KX-NT300 series)
Press HOLD to return to Select "Secondary Port". Press SP-PHONE. Select "DS (Enable)".
the Diffserv setting screen.
Diffserv
Press SP-PHONE. 0.0–7.7 Press SP-PHONE.
To end programming

and can then be
Press HOLD until the Press STORE.
Menu screen is displayed.

An IP-PT user can configure the port number of PTAP, DHCP, and FTP ports. Consult your network
administrator to check whether the configuration of the IP ports is required.
Follow the procedure below to configure the port number of the IP ports.
Note
• If you wish to change the port number back to default, enter 0 as the port number for the desired port.
• To delete 1 character, use "CLEAR" for IP-PTs, or use [TRANSFER] for KX-NT321 and KX-NT551.


SETUP
Password
Press "SETUP" Select "IP Port". ENTER 7678 ENTER

To configure the port number of PTAP Ports
*1
Select ENTER Select "Primary PBX". ENTER

"PTAP Server Port".
Port No.
1024–65535 ENTER
To configure the port number of PTAP Ports for the Secondary server (optional) *1
Select "PTAP Server Port". ENTER Select "Secondary PBX". ENTER
Port No.
1024–65535 ENTER
Port No.
Return to the Select ENTER 1024–65535 ENTER

Menu screen. "PTAP Client Port".
To configure the port number of DHCP Ports
Port No.
Select "DHCP Server Port". ENTER 67, 1024–65535 ENTER
Port No.
Select "DHCP Client Port". ENTER 68, 1024–65535 ENTER

To configure the port number of FTP Ports
Port No.
Select "FTP Server Ctrl Port". ENTER 21, 1024–65535 ENTER
Port No.
Select "FTP Client Ctrl Port". ENTER 1024–65535 ENTER
Port No.
Select "FTP Client Data Port". ENTER 1024–65535 ENTER
To end programming

and can then be
Menu screen.
Note

KX-NT551/KX-NT321
Password
Press PROGRAM while Select "IP Port". Press SP-PHONE. 7678 Press SP-PHONE.
"Searching" is displayed.
To configure the port number of PTAP Ports
Select "PTAP Server". Press SP-PHONE. Select "Primary PBX". Press SP-PHONE.
Port No.
1024–65535 Press SP-PHONE. Press HOLD.
To configure the port number of PTAP Ports for the Secondary server (if required)
Select "PTAP Server". Press SP-PHONE. Select "Secondary PBX". Press SP-PHONE.
Port No.
1024–65535 Press SP-PHONE. Press HOLD.
Port No.
Select "PTAP Client". Press SP-PHONE. 1024–65535 Press SP-PHONE.
To configure the port number of DHCP Ports
Port No.
Select "DHCP Server". Press SP-PHONE. 67, 1024–65535 Press SP-PHONE.
Port No.
Select "DHCP Client". Press SP-PHONE. 68, 1024–65535 Press SP-PHONE.

5.8.6 ECO mode (KX-NT500 series only)
To configure the port number of FTP Ports
Port No.
Select "FTP Server Ctrl". Press SP-PHONE. 21, 1024–65535 Press SP-PHONE.
Port No.
Select "FTP Client Ctrl". Press SP-PHONE. 1024–65535 Press SP-PHONE.
Port No.
Select "FTP Client Data". Press SP-PHONE. 1024–65535 Press SP-PHONE.
To end programming

and can then be
Press HOLD to return Press STORE.
to the Menu screen.
5.8.6 ECO mode (KX-NT500 series only)

ECO mode allows a KX-NT500 series IP-PT to consume less power than in normal mode.
To start ECO mode, follow the procedure below.
SETUP
Supply power
to the IP-PT.
Press "SETUP" Select "ECO Mode". ENTER Select "On".
when it is displayed.*1
To end programming
STORE The IP-PT will reboot in

ECO mode.

Menu screen.
*1 For KX-NT551 users only

Press PROGRAM when "Searching" is displayed.
Notice
• When an IP-PT is in ECO mode, the following limitations are applied:

5.9 Registering IP Telephones
– The second Ethernet port is disabled.

– The port of the switching hub to which the telephone is connected must be 10 Mbps (Fixed)/full
duplex.
• With software version 1.010 or later, you can specify the connection mode (Auto Negotiation, 10
Mbps/full duplex, 10 Mbps/half duplex, 100 Mbps/full duplex, 100 Mbps/half duplex). If a connection
with Auto Negotiation fails, the connection will be made in either 10 Mbps/half duplex or 100 Mbps/
half duplex.
To exit from ECO mode, turn off the IP-PT, and then follow the procedure below.
SETUP
Supply power
to the IP-PT.
Press "SETUP" Select "ECO Mode". ENTER Select "Off".
when it is displayed.*1
To end programming
STORE The IP-PT will reboot in

normal mode.

Menu screen.
*1 For KX-NT551 users only

Press PROGRAM when "Searching" is displayed.
Note
5.9 Registering IP Telephones

5.9.1 Registering IP Telephones
After the programming of the server and IP telephones is finished (refer to "5.8 Assigning Networking
Information to IP Telephones"), the IP telephones must be registered to the server. The procedure for
registering IP telephones differs according to the IP terminal registration mode specified during the Easy
Setup Wizard. The IP Terminal Registration Mode and IP-CS Registration Mode settings can be changed
in the Site Property—Main screen of the Web Maintenance Console (refer to "9.5.1 PBX Configuration—
[1-1] Configuration—Slot—Site Property—Main—Main" in the PC Programming Manual). Refer to the
following table:
IP Terminal Registration Mode/IP-CS
IP Terminals Registration Mode
Full Automatic Mode Manual Mode
IP-PTs ü ü
SIP phones (including
ü *1 ü
P-SIP)
IP-CSs*2 ü ü
*1 SIP phones must always be registered to the server manually, even if Full Automatic mode is selected.
*2 For details about registering IP-CSs, refer to the Installation Guide for the IP-CS.

ü: Available
Note
• For IP softphones, follow the same registration procedure as IP-PTs.
• To ensure that the necessary IP packets (RTP) are reached even when a temporary, significant
increase in the amount of IP packet communication occurs between the PBX and IP terminals, you
can set a higher priority to the transmission of the IP packets (RTP) communicated between the PBX
and IP terminals. For details, refer to 6.1.8 QoS (Quality of Service).
Full Automatic Mode

If networking settings have been completed, when IP-PTs, or IP-CSs are connected to the same network as
the server, they will be registered automatically. No registration procedure is required.
Manual Mode
For IP-PTs
After connecting IP-PTs to the server over a network, register those IP terminals to the server manually.
Follow the procedure below for registration.
To register the IP-PT by entering the MAC address directly:

1. Do the following settings.
a. Click Setup → PBX Configuration → Configuration → Slot.
b. Click V-IPEXT.
2. If the Connection column for the port is Fault, click Fault, and then click OUS on the dialogue box to
change the port’s status.
3. Enter the MAC address of the IP-PT in the IP Phone Registration ID (MAC Address) cell.
4. Click Apply.
Once the IP-PT is successfully registered, its status will update to show "Registered".
5. In the Connection column for the port, click OUS, and then click INS on the dialogue box to change the
port’s status.
To register the IP-PT using the wizard:

b. Click V-IPEXT.
2. Click Registration.
A dialogue box will appear. Non-registered (available) extension numbers and names are displayed on
the left.
a. Highlight numbers and names and click the right arrow to select them for registration, and then click
Next.

b. Click Next. A screen will appear with information on the current IP-PT extension number and name,
and index number for programming.
Note
• If the IP-PT has been connected to the LAN and power has been turned on, the IP address of
the server will be assigned automatically.
• If not, connect the IP-PT to the LAN and turn the power on within 15 minutes after this
operation is done. The IP address of the server will then be assigned automatically.
c. If the registration is still in progress, the dialogue box will show "Registration Executing".
If the registration is successful, the dialogue box will show "Registration Completed". Click Close.
Once the IP-PT is successfully registered, its status will update to show "Registered".
For SIP Phones (including P-SIP)

After connecting SIP phones to the server over a network, register those IP terminals to the server manually.
Follow the procedure below for registration.
a. Click Setup → PBX Configuration → Configuration→ Slot.
b. Click V-SIPEXT.
2. Assign extension numbers to the SIP extensions.
• If the Automatic Extension Number Set for Extension Card feature is enabled, the extension numbers
of SIP extension are automatically assigned. To programme this feature, refer to "9.31 PBX
Configuration—[1-3] Configuration—Option—New Card Installation—Automatic Extension Number
Set for Extension Card" in the PC Programming Manual.
• If not, enter the extension number for each SIP extension manually.
3. Set passwords for the SIP extensions.
a. Click the cell in the Connection column for each SIP extension you wish to register. The Command
Connection screen appears.
b. Click OUS.
c. Enter a password in the Password cell for each SIP extension.
d. Click Apply.
e. Click the cell in the Connection column for each SIP extension to which a password has been
assigned. The Command Connection screen appears.
f. Click INS.
g. Click OK.
Note
• Alternatively, it is possible to set an extension number as a password for each SIP extension
automatically.
• In order to set the password automatically, do the following in substitution for step c of the
procedure above.
1. Click Copy to. A screen will appear with information on assigned extension numbers for SIP
extensions.
2. Click Select All.

5.9.2 De-registering IP Telephones
3. Click Execute to copy each Extension Number to Password.

• When copying extension numbers to passwords, you can also use the icon on the bottom left
of the Virtual SIP Extension Port Property screen.
4. Programme the SIP extension you wish to register.
a. Set the IP address of the server, extension number, and password in the corresponding fields for
your SIP extension.
b. Send a request from the SIP extension to the server for registration.
• If the authentication information of the SIP extension and the server match, the registration is
successful.
Note
• When programming the SIP extension, the names of the corresponding fields may differ
depending on the type of SIP phone you are using.
• For details about the actual operation of SIP phones, refer to the documentation of the SIP phone.
• For certain SIP phones, you may need to set a Sign-in name, which should consist of the
extension number and the IP address of the server (e.g., 350@192.168.0.101).
• If SIP-TLS is configured as the encryption method for intercom calls in the system, encryption
must be enabled for all KX-HDV series telephones and KX-TGP600 units. Otherwise, these
devices will not work. For more information, see "5.2.7 Internal Call Encryption".
5.9.2 De-registering IP Telephones

Note
For details about de-registering IP-CSs, refer to the documentation for the IP-CS.
De-registration of IP-PTs
1. Make sure the IP Terminal Registration Mode is set to Manual.
a. Click Setup → PBX Configuration → Configuration → Slot → Site Property → Main.
b. In the Main tab, select Manual for IP Terminal Registration Mode.
c. Click OK.
b. Click V-IPEXT.
3. Click De-registration.
A dialogue box will appear. Registered extension numbers and names are displayed on the left.
a. Highlight numbers and names and click the right arrow to select them for de-registration.
b. Click Next.
A dialogue box will appear.
c. Click Confirm.
• If the de-registration is successful, the dialogue box will show "De-registration succeed!".

5.9.3 Installing SIP Phones at a Remote Site with an External SBC
d. Click Close.
Once the IP-PT is successfully de-registered, the status of the IP telephone will update to show "None".
Forced De-registration of IP-PTs

Follow the steps below to forcibly de-register an IP-PT when normal de-registration was unsuccessful.
b. Click V-IPEXT.
2. Click Forced De-registration.
A dialogue box will appear. Registered extension numbers and names are displayed on the left.
a. Highlight numbers and names and click the right arrow to select them for de-registration.
b. Click Next.
c. Click OK.
d. Click Confirm.
• If the de-registration is successful, the dialogue box will show "Forced de-registration succeed!".
e. Click Close.
Once the IP-PT is successfully de-registered, the status of the IP telephone will update to show "None".
De-registration of SIP Phones (including P-SIP)

The de-registration of SIP phones is carried out by deleting either the extension number or password
registered in the server.
b. Click V-SIPEXT.
a. Click the cell in the Connection column for the port of the SIP phone to de-register.
b. In the Command window, click OUS to change the status of the port to "OUS".
3. Repeat step 2 for each SIP phone to de-register.
4. Delete either the extension number or password for the SIP phone to de-register, as shown here.
5. Click OK.
5.9.3 Installing SIP Phones at a Remote Site with an External

SBC
If an SBC (Session Border Controller) is present on the same local network as the server, you can install
SIP phones at remote sites without needing to configure special network settings (NAT traversal, etc.).

5.9.3 Installing SIP Phones at a Remote Site with an External SBC
This section provides information about the procedure for connecting SIP Phones at a remote site that has
SBC hardware.
When SIP phones in remote sites use the internet to communicate with the server, use the HTTPS protocol
for security. If the connection is within a VPN and protected, you may use the HTTP protocol.
Internet
NSX server Switching Hub Switching Hub
Router Router
IP-PT SBC SIP phone
Main Site (Headquarters) Remote Site
: RTP packets
Note
• Install the SBC in the same LAN as the NSX server.
• The NSX server can work with only one SBC. Also, multiple sites can share an SBC.
• The NSX server can support up to 50 remote extensions at the same time via SBC when using the
HTTPS protocol.
• All the RTP packets in between the main site and the remote site is routed to the SBC for security and
for IP address conversion.
• When settings of remote extensions being used at remote sites are changed at the NSX server at the
main site, the reflection of the changes to the remote extension may require some time due to data
transfer protocols.
Programming the SBC

The following items need to be configured on the SBC. For information about configuring the SBC, refer to
the documentation of the SBC.
• IP address of the NSX server
• IP address and subnet mask of the SBC
• LAN side IP address of the router at the main site
• WAN side IP address of the router at the main site
• SIP receiving port settings (For details, refer to the documentation of your SBC)
• RTP Start Port (UDP) and RTP End Port (UDP)
Note
Make sure the RTP Start Port (UDP) and RTP End Port (UDP) specified for the SBC above are in the
range of the RTP port numbers that NSX server uses.
For range of RTP port number of NSX server, refer to "Port Numbers for Optional DSP Cards" in
"6.5 Port Security".
• Firewall settings to allow SIP packets and RTP packets

5.9.4 Installing IP Phones at a Remote Site with a Built-in Media Relay Gateway
Programming the router at the main site

Port forwarding settings (Router – SBC)
Configure the following items for port forwarding in between the SBC and the router.
Application LAN Side Port Number WAN Side Port Number
RTP (UDP) Start/End RTP (UDP) Port No. Start/End RTP (UDP) Port No.
(Use port numbers that are in the (Use port numbers that are in the
range of the RTP ports that the range of the RTP ports that the
NSX server uses.) NSX server uses.)
Make sure the RTP Start Port (UDP) and the RTP End Port (UDP)
specified for the router are in the range of the RTP ports that the NSX
server uses. For the range of RTP port numbers that the NSX server
uses, refer to "Port Numbers for Optional DSP Cards" in "6.5 Port
Security".
Note
For information about configuring port forwarding on the router, refer to the documentation of the router.
5.9.4 Installing IP Phones at a Remote Site with a Built-in Media

Relay Gateway
The NSX server contains a built-in Media Relay Gateway.
You can install and register IP-PTs (KX-NT500 series), Panasonic IP-Softphones, IP-CSs, and SIP phones
at a remote site without adding an SBC (Session Border Controller). Also, you do not need to configure
special network settings (NAT traversal, etc.) at the remote site.
Mobile Softphone
Mobile Internet
PBX
(+ Built-in Media Relay Internet
Gateway) Switching Hub Switching Hub
Router Router
PC IP-PT IP-PT SIP phone

Main Site Remote Site
: LAN
: WAN

Note
• There is no limit to the number of terminals that can use the Media Relay Gateway feature.
However, there are some conditions, as follows:
– DSP resources are required for calls because peer-to-peer communication is not supported for the
built-in Media Relay Gateway.
• For information about which telephone models support the built-in Media Relay Gateway, consult your
dealer.
Programming the NSX server with Built-in Media Relay Gateway

The NSX server programming is required using Web Maintenance Console for the following settings:
• Remote Place
Programming is required for extensions that use the MRG (Media Relay Gateway) feature.
• Site Property
The WAN-side IP address of the router and the WAN-side port number of the router that is used for the
MRG feature must be programmed on the NSX server.
2. Click Virtual.
3. Select one of the following tabs:
– For the KX-NT500 series/IP-Softphones: V-IPEXT
– For IP-CSs: V-IPCS
– For SIP phones: V-SIPEXT
4. Move the mouse pointer over the virtual card. A menu will be shown under the mouse pointer.
5. Click Port Property.
6. Click the Remote Place tab.
7. Configure the items shown below.
• Change the value to Remote + Local for Phone Location.
8. Click OK.
For Site Property Settings

2. Click Site property—Main.
3. Click the Media Relay tab.
4. Programme the WAN side information in Media Relay tab.
a. Programme the following common settings in Common.
WAN Side IP information of the router at the
Web Maintenance Console Parameter
main site
*1
IP Address NAT - External IP Address / FQDN
*1 You can also programme individual items of the NAT - External IP Address / FQDN. For more details, see step d.
b. Programme the following settings according to the protocol used by the KX-NT500 series IP
extensions, IP-Softphones and IP-CSs in the remote site. Configure the following items in IP
Extension / IP-CS.

WAN Side IP information of

the router at the main site
MGCP
Port Number NAT - MGCP Server Port No.

Port Number (for IP-CS) NAT - MGCP Server Port No. for IP-CS
FTP
Port Number NAT - FTP Server Port No.
c. Programme the following settings according to the protocol used by SIP extensions in the remote
site. Configure the following items in SIP Extension.
SIP
Port Number NAT - SIP Proxy Server Port No.

SIP-TLS
Port Number NAT - SIP TLS Server Port No.
d. Programme the following common settings in Option.

RTP
IP Address NAT - RTP IP Address

SIP
IP Address NAT - SIP Proxy Server IP Address
If necessary, you can programme the individual settings here and overwrite the NAT - External IP
Address / FQDN setting programmed in step d.
5. Click OK.
Using an NSX server as an NTP server
When the NSX server will be used as an NTP server, follow the procedures below.
1. Click Setup → Network Service → Server Feature → NTP.
2. Select Enable.
3. Click OK.

Programming the router at the main site with Built-in Media Relay Gateway
Port forwarding settings (Router – NSX server)
Configure the following items for port forwarding between the Media Relay Gateway and the router.
Common Setting:
RTP (UDP) Start/End RTP (UDP) Port No. (Use port numbers that are in the range of the RTP
*1
ports that the NSX server uses.)
Make sure the RTP Start Port (UDP) and the RTP End Port (UDP) specified for the
router are in the range of the RTP ports that the PBX uses. For the range of RTP port
numbers that the PBX uses, refer to "Port Numbers for Optional DSP Cards" in
*1
"6.5 Port Security".
*1 The port number ranges must be within the range of RTP/RTCP for NAT traversal (21000–24071). If you want to change the
starting port number, refer to "9.5.1 PBX Configuration—[1-1] Configuration—Slot—Site Property—Main—Port Number—NAT -
Voice (RTP) UDP Port No." in the PC Programming Manual.
For KX-NT500 series IP-PTs and IP-Softphone:

PTAP Signalling (PTAP) UDP Port No. Signalling (PTAP) UDP Port No.
(Server) (Server)
(refer to PC Programming Manual "9.5.1 (refer to PC Programming Manual "9.5.1
PBX Configuration—[1-1] Configuration— PBX Configuration—[1-1] Configuration—
Slot—Site Property—Main") Slot—Site Property—Main")
MGCP Signalling (MGCP) UDP Port No. NAT - MGCP Server Port No.
(Server) (Use the same value as in step 4-b of "For
(refer to PC Programming Manual "9.5.1 Site Property Settings".)
PBX Configuration—[1-1] Configuration—
Slot—Site Property—Main")
FTP The port number used for the FTP NAT - FTP Server Port No.
protocol. This is used for software (Use the same value as in step 4-b of "For
updates. Site Property Settings".)
For IP-CS:
PTAP Signalling (PTAP) UDP Port No. Signalling (PTAP) UDP Port No.
(Server) (Server)
(refer to PC Programming Manual "9.19 (refer to PC Programming Manual "9.19
PBX Configuration—[1-1] Configuration— PBX Configuration—[1-1] Configuration—
Slot—V-IPCS16—Card Property") Slot—V-IPCS16—Card Property")
MGCP Signalling (MGCP) UDP Port No. NAT - MGCP Server Port No. for IP-CS
(Server) (Use the same value as in step 4-b of "For
(refer to PC Programming Manual "9.19 Site Property Settings".)
PBX Configuration—[1-1] Configuration—
Slot—V-IPCS16—Card Property")
FTP The port number used for the FTP NAT - FTP Server Port No.
protocol. This is used for software (Use the same value as in step 4-b of "For
updates. Site Property Settings".)

5.9.5 Encryption Settings for Internal Calls
For SIP phones:

SIP Proxy UDP Port No. for SIP Extension Server NAT - SIP Proxy Server Port No.
(refer to PC Programming Manual "9.5.1 (Use the same value as in step 4-b of "For
PBX Configuration—[1-1] Configuration— Site Property Settings".)
Slot—Site Property—Main—Port
Number")
SIP TLS TLS Port No. for SIP Extension Server NAT - SIP TLS Server Port No.
(refer to PC Programming Manual "9.5.1 (Use the same value as in step 4-b of "For
PBX Configuration—[1-1] Configuration— Site Property Settings".)
Slot—Site Property—Main—Port
Number")
Installing IP phones at a remote site

For KX-NT500 series and IP-softphones:
In the network settings of the phones, assign the global IP address of the router at the main site as the
destination IP address. (Do not assign the IP address of the NSX server)
For SIP Phones:

In the network settings of the phones, assign the connection destination settings as follows:
Value
Setting Item
SIP TLS is disabled SIP TLS is enabled
SIP Server IP The IP address of the NSX server
(NSX server) Address
Port Same value as follows: Same value as follows:
UDP Port No. for SIP Extension TLS Port No. for SIP Extension
Server Server
(refer to PC Programming Manual (refer to PC Programming Manual
"9.5.1 PBX Configuration—[1-1] "9.5.1 PBX Configuration—[1-1]
Configuration—Slot—Site Property Configuration—Slot—Site Property
—Main") —Main—Port Number")
Proxy server IP The global IP address of the router at the main site
Address
Port Same value as follows: Same value as follows:
NAT - SIP Proxy Server Port No. NAT - SIP TLS Server Port No.
(refer to PC Programming Manual (refer to PC Programming Manual
"9.5.1 PBX Configuration—[1-1] "9.5.1 PBX Configuration—[1-1]
Configuration—Slot—Site Property Configuration—Slot—Site Property
—Main—Media Relay") —Main—Media Relay")

This feature encrypts intercom calls to prevent eavesdropping.
Calls between specific extensions are encrypted. SIP signalling (SIP-TLS) and voice data (SRTP, P2P calls
only) can be encrypted.
SIP signalling encryption (SIP-TLS) is performed between the NSX server and extensions that are located
at all sites.
This feature is available for the following models:

Model SRTP SIP-TLS

KX-HDV100/130 ü
KX-HDV230/330/430 ü ü
KX-TGP600 ü ü
Mobile Softphone (KX-UCMA) ü
ü: available
Note
• By using the Built-in Media Relay Gateway, SIP phones that connected via the internet can use SIP-
TLS feature. (→ 5.9.4 Installing IP Phones at a Remote Site with a Built-in Media Relay Gateway)
• The encryption (SRTP) of the video phone call’s media stream will not function
A SIP-TLS connection is established through authentication with the NSX server. For server authentication,
the NSX server's or the Expansion GW's CA certificate must be set as a root certificate on the devices.
The CA certificate can be exported from Web Maintenance Console.
SRTP encryption is performed only for P2P calls.
Encryption Setting
• For intercom call encryption, encryption settings must be configured for both the NSX server and
extensions.
• Encryption settings for the NSX server are configured through Web Maintenance Console.
• Encryption settings for KX-HDV series/KX-TGP600 are configured using configuration files. For details
about extension settings, refer to the corresponding extension's documentation.
For SRTP
• NSX Server
– No settings are required to use SRTP.
• KX-HDV series/KX-TGP600 (configuration file settings)
– In SRTP_CONNECT_MODE_n, specify "2" (SRTP & RTP).
– In SRTP_MIX_TRANSFER_ENABLE_n, specify "Y" (Enable). This setting is required in order to
allow calls to be transferred to devices that do not support encryption.
Note
• If you are using the KX-HDV1xx series in the same system, set
"SRTP_MIX_TRANSFER_ENABLE_n" to "Y" (Enable) in the KX-HDV1xx configuration file
settings.
• When connecting the KX-HDV230/330 / KX-TGP600 to a PBX for SRTP calling, use SRTP-
compatible firmware. For more information, consult your dealer.
For SIP-TLS
• NSX Server
– To perform server authentication when the device is directly connected to the NSX server, export the
NSX server's CA certificate as follows:
1. Click Maintenance → Tool → P-SIP Option.
2. Click Export.

5.10 Configuration of Users
– To perform server authentication when the device is connected to an expansion gateway, export the
expansion gateway's CA certificate as follows:
1. Click Maintenance → Utility → File → File Transfer PBX to PC.
2. Change the site to an expansion gateway.
3. Select the CA certificate file (Root_CERT_ExpnGW).
4. Click Transfer.
• KX-HDV series/KX-TGP600 (configuration file settings)
– In SIP_TRANSPORT_n, specify "2" (TLS).
– In SIP_TLS_MODE_n, specify "1" (SIP-TLS).
– In SIP_TLS_RANDOM_PORT, specify "N" (No).
– To perform server authentication, configure the following settings.
1. In SIP_TLS_VERIFY_n, specify "1" (Simple verification) or "2" (Precise verification).
2. In SIP_TLS_ROOT_CERT_PATH, specify the URI where the CA certificate is stored.

The NSX server manages the user and device data with the user as the central unit of configuration. This is
called "User Container".
In the user container, one user has one extension number. The specified extension number is used as the
extension number of the main device. With the main extension number, other devices associated with the
user can use the PBX’s functions.
Using user container enables you to manage data and provide services more simply.
User Container
A user container is created for each user. You can configure users’ settings from Web Maintenance
Console. The following information is managed within a user container:
• Name: The user's name
• Extension Number: The user's extension number. It is also used as the Main Device number.
• Main Device: The main device that the user uses as an extension.
• Sub Device: The device that the user uses secondarily. This extension ring in parallel when the main
device receive a call.
• Portable Station: A wireless device (PS) that the user uses.
• Mobile Phone: A cellular phone that the user uses. A maximum of 4 mobile phones can be assigned.
• Unified Messaging Mailbox: The Unified Messaging mailbox for the user.
Note
To use the Unified Messaging features, an expansion Storage Memory Card is required.
Which types of devices a user can use depends on the type of user, as shown in the following table.
User Type Main Device Sub Device Portable Station Mobile Phone
Advanced user Available Available Available Available
Mobile user Available Not available Available Available
Normal user Available Not available Available Not available
For more details about device types, refer to "2.29.1 User Container" in the Feature Manual.

Number of users and devices for NSX server models

The KX-NSX1000 can support up to 1000 devices, and the KX-NSX2000 can support up to 2000 devices.
How these devices are assigned to users determines the number of users for the NSX server.
For example, the following two user configurations use the same number of devices, but the number of
created users is different.
Example A: 475 users

User configuration Capacity used
200 users with 1 main device 200 devices (1 × 200)
200 users with 1 main device and 1 Portable 400 devices (2 × 200)
Station
50 users with 1 main device, 1 sub device, and 1 150 devices (3 × 50)
mobile phone
25 users with 1 main device and 3 mobile phones 100 devices (4 × 25)
Total capacity used 850 devices
Example B: 625 users

User configuration Capacity used
400 users with 1 main device 400 devices (1 × 400)
200 users with 1 main device and 1 Portable 400 devices (2 × 200)
Station
25 users with 1 main device 1 mobile phone 50 devices (2 × 25)
Total capacity used 850 devices
Note
The device capacity also includes the devices that are not assigned to users (e.g., IP Communication
Camera). In the case of Example A, if you use 50 IP Communication Cameras, the number of devices
changes as below, but the number of users remains at 475.
850 devices (the devices assigned to users) + 50 devices (IP Communication Cameras) = 900 devices
Required Activation Keys
NSX server required activation key for each user. User type and required activation keys are shown in the
following table.
Normal user Mobile user Advanced user

User Type
Activation key Activation key Activation key
Advanced user ü ü ü
Mobile user ü ü
Normal user ü
ü: Required
Note
• If an Ultimate Activation Key (KX-NSXP101) is installed to the NSX server, no user activation keys will
be required.

• If the user uses a 3rd party SIP phone, a SIP extension activation key will be required in addition to
the user activation key.
Creation of User Containers

Follow the procedures below to register users (user containers).
1. Click Setup → Users → User Container.
To add a single user
1. Click icon or Add Single User button.
2. In the User Information tab, specify the following values:

• First Name
• Last Name
• Extension Number
• Login ID (max. 16 characters)
• Password (max. 16 characters)
• User PIN / Mailbox Password ["0-9"]
• WebMC Language
• Memo-1/Memo-2
• Type of User
• Admin Capability
• User Group
• Class of Service (COS)
This extension number is also used as the number for the user's Unified Messaging mailbox.
3. In the Device Settings tab, specify the settings for the following devices:
• Main Device
Select device type from the Type drop-down list.
• Sub Device
Enter an extension number, and select the device type and delayed ringing from each drop-down list.
• Portable Station
Enter an extension number and select the delayed ringing from the drop-down list.
• Mobile Phone
– Select the "When the mobile phone started ringing by delayed ringing, ringing of the phone
(Main / Sub / PS) will be terminated." check box to enable this functionality.
– Select the number of mobile phones to assign to the user (max. 4).
4. On the remaining tabs, confirm and/or specify the user information as necessary.
Contact
Register the user’s contact information. Up to 2 telephone numbers and 3 e-mail addresses can be
registered. You can also select whether to send certain notifications to each e-mail address.
• Phone (Home)
• Phone (Mobile)
• Email 1/Email 2/Email 3
Unified Messaging

You can confirm the user's Unified Messaging information.

• Unified Messaging Mailbox
Telephony Feature
You can configure the following features for the user.
• FWD/Do Not Disturb
• Call Waiting Mode
• PT Display Language Selection
• Station Dial Lock
• PT Display Lock
• Speed Dialling View/Edit
• Flexible Button View/Edit for Wired Extension
• Flexible Button View/Edit for PS
5. When you have finished configuring the settings, click OK.
To add multiple users
1. Click icon or Add Multiple Users button.
2. In Extension Number, enter the starting extension number in the From box. This number becomes the
first extension number of the created user containers.
3. In the Number of Users box, enter the number of users to create.
4. If necessary, select the Create User Container Data from other User template check box, and then
select an extension number to use as a template from the drop-down list.
If you select this option, the following settings will be copied from the selected extension's user container
to the new containers:
• User Group
• Class of Service
• WebMC Language
• Admin Capability
• Type of User
• Main Device - Type
• PT Display Language
• Flexible Button Setting for Wired Extension
5. Click OK.
A confirmation message will be displayed.
6. Click OK.
The number of user containers you specified in step 3 will be automatically created.
Synchronising User Information with an LDAP Directory

If you use Active Directory® (Lightweight Directory Access Protocol [LDAP]), you can synchronise user
container information from the LDAP directory.
Requirement
• Activation Key for LDAP (KX-NSXF005)
• One of the following types of LDAP directory:

– Active Directory (Windows Server 2008 R2)*1

– Active Directory (Windows Server 2012)*1
– Active Directory (Windows Server 2016)*1
– OpenLDAP Version 2.4.xx
*1 In accordance with the provisions of the Microsoft Corporation, acquisition of client access licenses (CAL) is separately
required.
• Access settings for the LDAP server must be configured beforehand. See "28.3.4.1 Network Service—
[3-4-1] Client Feature—Directory Service—Server Setting" in the PC Programming Manual.
• Access setting for the LDAP database and User Container synchronisation must be configured
beforehand. See "28.3.4.3 Network Service—[3-4-3] Client Feature—Directory Service—User Container
Sync" in the PC Programming Manual.
• There are some condition as below when the Name information is searched in System Speed Dialling-
External (LDAP) Directory.
a. In order to search the name, available characters are only alphanumeric characters (Capital letter
only).
b. When the Name with small alphabet is searched, it is necessary to set not to distinguish Capital/
Small characters. Consult your network administrator.
1. On the Add User screen, click Database Sync.
2. Enter a name to search for in User name.
3. Click Search. The results are shown in a list.
4. Click the name whose information you want to synchronise.
5. Click Apply.
The following information in the user container will be synchronised with the selected directory entry:
• First Name
• Last Name
• User ID
• Password
• Mobile phone1-4
• E-mail address 1-3
• Phone Number (Home)
• Phone Number (Personal Mobile)
• Memo-1
• Memo-2
6. Click OK.
Activating Users
Follow the procedure below to activate the registered users.
1. Click Setup → Users → User Container.
2. Click Activate User.
3. Select the checkboxes of the users to activate.
4. Click Activate.

5.11 Programming E-mail Integration for UM Voice/Fax Messages
5. Click Continue.
Note
• You can view the number of activated users and the total user capacity (enabled through
Activation Keys) by clicking AK Info on the User Container screen.
• To log in to the user portal, enter the following URL:
http://xxx.xxx.xxx.xxx/WebMC/users_portal/login
Enter your NSX server’s IP address for "xxx.xxx.xxx.xxx".
5.11 Programming E-mail Integration for UM

Voice/Fax Messages
Users with Unified Messaging (UM) mailboxes (referred to below as "subscribers") can receive their voice or
fax messages as data using the following methods:
– Receiving attachments to a POP3 e-mail account
– Accessing data through an IMAP4 e-mail account
Note
To use the Unified Messaging features, an expansion Storage Memory Card is required.
Receiving Attachments to a POP3 E-mail Account

An e-mail can be sent to Unified Message system subscribers, notifying them of a new voice or fax
message. Subscribers can also choose to have the voice message and/or fax data attached to the
notification, as well as choose to have the message deleted from the system after it has been sent.
1. Specify SMTP server settings.
a. Click Setup →Network Service → Server Feature → SMTP.
b. Specify the name to be used for the e-mail messages that will be sent from the system in Mail
sending—Mail sender information name.
c. Specify the e-mail address for the e-mail messages that will be sent from the system in Mail
sending—Mail Address.
d. Specify the IP address or host name of the SMTP server to use in SMTP server for relay—SMTP
server address.
e. Specify the port number of the SMTP server to use in SMTP server for relay—SMTP server Port
number.
f. Specify the following parameters if required.
– SMTP over TLS
– SMTP Authentication
– POP before SMTP
– Receive Port number (SMTP)
– Receive Port number (SMTPs)
Note
For details about these parameters, refer to "28.2.5 Network Service—[2-7] Server Feature—
SMTP" in the PC Programming Manual.
g. Click OK.

2. Specify e-mail options.

a. Click Setup → UM Configuration → System Parameters → Parameters → E-mail Option.
b. Specify the following parameters.
– Mail Address (Up to 128 ASCII characters)
– Full Name (Up to 64 ASCII characters)
– Maximum Message Length (Selection)
– Maximum Message Length (Other) (1-30 min)
c. Click OK.
3. Enable e-mail notification.
a. Click Setup → UM Configuration → Class of Service → General.
b. In E-mail Option, select Yes for all Class of Service members that will receive e-mail notifications.
c. Click OK.
4. Specify notification parameters.
a. Click Setup → UM Configuration → Mailbox Settings → Notification Parameters.
b. Click Edit in E-mail/Text Message Device.
c. Specify the following parameters for Device No. 1, 2, and 3 as required.
– User name
– E-mail Address
– Notification Type
– Only Urgent Messages
– Title Order
– Title String
– Callback Number
– Send Wait Time [0-120 min]
– Attach Voice File
– Attach Fax File
– Use Mode
Note
For details about these parameters, refer to "20.1 UM Configuration—[1] Mailbox Settings—
Notification Parameters" in the PC Programming Manual.
d. Click OK.
Accessing Data Through an IMAP4 E-mail Account

Downloading the IMAP Session Controller Software
When more than 24 users will be accessing data through IMAP4 e-mail accounts, each user must use the
IMAP Session Controller software.
The IMAP Session Controller software can be downloaded from Web Maintenance Console:
1. Log in with a User level account.
The Edit User screen is displayed.

2. Click the Unified Message tab.

3. Click Download for Unified Messaging Plug in to access the download site for the IMAP Session
Controller software.
Note
For details about installing and setting up the IMAP Session Controller software, refer to the
Operating Manual.
Configuring IMAP Accounts

By configuring an IMAP account, subscribers can access the contents of their UM mailboxes through an e-
mail client. All that is necessary is an e-mail client that supports IMAP4.
Once IMAP integration is programmed, users can do the following:
• Listen to voice messages or view fax messages
• Save voice and fax message data to their PCs
• Delete voice and fax messages stored on the NSX server
1. Enable IMAP integration.
a. Click Setup → UM Configuration → Class of Service → General.
b. In Desktop Messaging, select Yes for all Class of Service members that will use IMAP integration.
c. Click OK.
2. Specify the mailbox password.
a. Click Setup → UM Configuration → Mailbox Settings → Mailbox Parameters.
b. Click Edit in Mailbox Password (Message Client).
c. Enter a password in Enter new password.
d. Enter the password again in Confirm new password.
e. Click OK.
f. Click OK.
3. Specify IMAP parameters.
a. Click Setup →Network Service → Server Feature → IMAP4.
b. Specify the following parameters (if required).
– IMAP4 server
– Port Number
– IMAP4 over TLS
– CAPABILITY command
– Authenticated Connection Timeout
Note
For details about these parameters, refer to "28.2.6 Network Service—[2-8] Server Feature—
IMAP4" in the PC Programming Manual.
c. Click OK.

Setting Up the IMAP Account in a Subscriber’s E-mail Client

An account must be set up in each subscriber’s e-mail client for use with the Unified Messaging system. The
setup procedure will vary depending on the e-mail client application used and the configuration of your
network. When adding the account, the settings must be specified as follows:
– The e-mail address will be the subscriber’s existing e-mail address.
– The type of the account must be set to "IMAP".
– The incoming mail server must be set as the IP Address of the NSX server where the subscriber’s UM
mailbox is located.
– The user name/ID will be the subscriber’s UM Mailbox Number.
– The password will be the Mailbox Password (Message Client) set in step Accessing Data Through an
IMAP4 E-mail Account above.
– A valid SMTP server must be used (i.e. the SMTP server used for existing mail accounts).
Note
• To allow faxes to be received and stored in a mailbox:
1. Click Setup → UM Configuration → Class of Service → General.
2. In Fax Option, select Yes for all Class of Service members that will receive faxes.
3. Click OK.
• A FAX card (KX-NS0106) must be installed in a KX-NS1000 expansion gateway to send or receive
faxes.
The following example setup procedure is for Microsoft Outlook® 2010. Subscribers’ e-mail client setting
names and locations may differ.
1. In Outlook 2010, select File, and then Info.
2. Click the Add Account button.
3. Select Manually configure server settings or additional server types.
4. Select Internet E-mail, and then click Next.
5. Configure the server settings as follows:
User Information
– In Your Name, enter the name of the subscriber. (In the example, "John Smith")
– In E-mail Address, enter the existing mail address of the subscriber. (In the example below,
"j.smith@example.com")
Server Information
– Select IMAP for Account type.
– In Incoming mail server, enter the IP address of the NSX server where the subscriber’s UM mailbox
is located. (In the example below, "10.178.19.206")
– In Outgoing mail server (SMTP), enter the SMTP server used for the subscriber’s existing mail
account. (In the example below, "mail.example.com")
Logon Information
– In User Name, enter the subscriber’s Mailbox Number. (In the example below, "407")

– In Password, enter the password for the subscriber specified in Mailbox Password (Message
Client).
6. Click Next and then complete the account settings.
Example IMAP Account Settings (Outlook 2010)

Section 6
Networking Information
This section provides information about topics such as

using the NSX server in a VoIP network, and the TCP
ports used by the NSX server.

6.1 Information about Using an IP Network
6.1 Information about Using an IP Network

This section explains common IP network information necessary for setting up Multi-connection networks
and QSIG networks.
6.1.1 Using a VoIP Network with the NSX server

This NSX server supports Panasonic IP proprietary telephones (IP-PTs), Panasonic IP softphones, and SIP
(Session Initiation Protocol) phones (hardphones and softphones) for communication on a Voice over
Internet Protocol (VoIP) network. These IP telephones can be used as extensions of the NSX server when
the local office LAN is connected to other LANs at different locations.
This NSX server also enables VoIP communication with NSX server's installed at different locations. Since
the communication does not take place over conventional telephone network, the high cost of long distance
communication is virtually eliminated.
To establish a VoIP network, the virtual cards are used according the requirement of the network. For details
about virtual cards, see "4.4 Virtual Cards".
The following diagrams illustrate VoIP network with (i) a remote office LAN and (ii) another NSX server
installed at different location.
Note
Panasonic IP Cell Station (IP-CS) units are also supported by this NSX server for communication on a
VoIP network. For details, refer to the Installation Guide for the IP-CS.
(i) Connection Outline of VoIP Network with Remote Office LAN

Local Office LAN
SIP Phone
Extn. 102
Remote Office LAN

IP Softphone
Extn. 103
IP-PT
Extn. 101 Switching IP Softphone
Hub Extn. 105
SIP Phone
Extn. 106
NSX server with IP-PT
V-IPEXT card/ Router Extn. 104 Switching
V-SIPEXT card
Hub
DHCP Server
Router
Private
IP Network

6.1.1 Using a VoIP Network with the NSX server
(ii) Connection Outline of VoIP Network with NSX server in Other Network
Router Headquarters
NSX server with

V-IPGW card
Switching
Hub
Private IP Network
Router
NSX server with

V-IPGW card
Switching Hub
Branch
Network Parameters
You will need to have the following IP addressing and QoS information to establish VoIP communication on
your network. This information is typically supplied by a network administrator.
Consult your network administrator for specific values.
Parameter Description
Identifies the location of IP telephones on the network. Each IP
IP telephone IP Address
telephone must have a unique IP address.
Defines which digits of an IP address are used for the network
address and the host address at each network location. The IP
Subnet Mask Address addresses of the IP telephones and the NSX server must fall within
the same subnet as that of the default gateway (e.g., router) of the
LAN.
Identifies the IP address of the primary gateway (typically a router
Default Gateway Address or similar device) that exchanges IP packets with the other
gateways on the VoIP network.
Identifies the location of the NSX server in the network during VoIP
IP Address
communications.

6.1.2 DHCP (Dynamic Host Configuration Protocol) Server
Parameter Description
Identifies the ID of the logical segment within the corporate LAN,
VLAN ID through which voice packets from IP telephones travel. For details,
refer to "6.1.3 VLAN (Virtual LAN)".
Identifies the value for the DS field in the header of IP packets,
DiffServ (DS) which determines the priority given to packets travelling from IP
telephones. For details, refer to "5.8.4 Setting Diffserv Parameters".
Types of IP Network
The speech quality depends on the type of IP network in use. Managed IP networks provide better speech
quality compared to unmanaged networks such as satellite communications, where quality of service cannot
be guaranteed.
Examples of recommended IP networks Not recommended
• Digital Leased Line • Satellite communications (Very Small Aperture
Terminal system [VSAT], etc.)
• IP-VPN (Virtual Private Network)
• Frame Relay
Note
• Peer-to-peer calls between IP telephones installed at different locations may not be possible if packet
communication cannot be established between the respective networks. In this case, you need to
configure the network settings (e.g., a VPN router when using an IP-VPN) to establish packet
communication.
• Unlike an IP-VPN, which is set up over a network provider’s own IP network, an Internet VPN is set
up over the Internet. Internet VPNs are not recommended for VoIP communication because
transmission delays and loss of data are likely to occur.
6.1.2 DHCP (Dynamic Host Configuration Protocol) Server

To establish communication over a VoIP network, IP addresses must be assigned to IP telephones and the
NSX server to identify their locations on the network. While these addresses can be assigned manually, it is
also possible to use a DHCP server to automatically assign IP address information. The NSX server has a
DHCP Server feature. Therefore, the NSX server can act as a DHCP server or DHCP client depending on
its settings. When the NSX server’s DHCP Server feature is enabled, it allows you to centrally manage and
automate the assignment of IP addresses with Web Maintenance Console. For details, refer to "28.2.1
Network Service—[2-1] Server Feature—DHCP(LAN)" in the PC Programming Manual.
When the mother board is When an IP telephone is
connected to the network NSX server
connected to the network
(DHCP Server
1 Request IP address feature enabled) 3 Request IP address
information information
2 Assign IP address
information to the
DSP cards
DSP Card
4 Assign IP address
information to an IP IP Telephone
telephone
Note
• The DHCP Server feature is disabled by default. To enable the feature, refer to "5.4.3 Enabling the
DHCP Server Feature".

6.1.3 VLAN (Virtual LAN)
• An IP telephone and the mother board/DSP cards cannot request IP addresses from a DHCP server
on another LAN (connected through an IP network). They can only receive IP addresses from a
DHCP server on the same LAN. Therefore, when IP telephones are located on several LANs, a
DHCP server is required on each LAN. If a DHCP server is not present on the LAN, IP addresses for
IP telephones and the mother board/DSP cards on that LAN must be assigned manually.
• When the NSX server has been set to act as a DHCP client, use an external DHCP server to assign
IP address information automatically.
• When the NSX server is set as the DHCP client and cannot receive appropriate IP addressing
information from an external DHCP server, the NSX server keeps using the previous effective IP
addressing information and checks whether any overlapping of IP addresses exists. If the IP address
of the NSX server overlaps with another IP address, the NSX server displays a warning to encourage
changing the IP address of the NSX server.
6.1.3 VLAN (Virtual LAN)

VLANs are logical segments within a corporate LAN. By assigning VLAN settings to IP telephones, it is
possible to separate the packets transmitted by an IP telephone according to the type of data and specify
which VLAN each data type will be sent over. This allows you to avoid generating unnecessary network
traffic on each segment and to reduce the load on the network. As a consequence, speech quality can be
assured. Therefore, we recommend using the VLAN feature to perform VoIP communication effectively.
Some IP telephones are equipped with 2 ports, primary and secondary, for packet communication.
Allocating these ports to different VLANs enables you to split the paths for packets depending on whether
the packet contains voice signals or data.
VLAN settings (VLAN ID and VLAN priority) for the primary port affect voice data transmitted by the IP
telephone, whereas VLAN settings for the secondary port apply to data transmitted by a PC connected to
the IP telephone. When sending packets, the IP telephone can attach information on which VLAN the
packets are to be transmitted over (VLAN Tagging). The switching hub that receives these packets reads
the VLAN information and sends the packets over the appropriate VLAN. This helps to ensure bandwidth for
IP telephone voice transmissions.
In this way, an IP telephone with 2 ports can transmit voice packets from the primary port with higher priority
than other packets from the secondary port.
Notice
The NSX server’s LAN port does not support VLAN tagging. Therefore, connect the NSX server’s LAN
port to a port of the switching hub that is set to "Untagged", and the IP telephone to a port set to "Trunk",
to allow VLAN tagging. Consult your network administrator for details.

6.1.4 Jitter Buffer
VLAN 1 VLAN 2
Segment for Voice Data Segment for Other Data
VLAN-capable
Switching Hub
VLAN 1 VLAN 1 VLAN 2
Untagged
VLAN 2
NSX server PC
VLAN 1
VLAN 2
Voice Packet
Other Packet
Other Packet
IP Telephone with 2 ports
PC
Primary Secondary
Note
• This VLAN feature complies with IEEE (Institute of Electrical and Electronics Engineers) 802.1Q.
• The NSX server receives VLAN settings only from the connected switching hub. Therefore, VLAN
settings for the NSX server must be assigned at the switching hub.
• When using the VLAN feature on the network, make sure that the main unit is connected to a layer 2
switch that is IEEE 802.1Q compliant, and that is configured for VLANs. In addition, the port of the
switching hub to which the card is connected must be set to "Untagged". Consult your network
• When using the VLAN feature on the network, make sure that the switching hub to be connected is
IEEE 802.1Q compliant and is configured for VLANs. In addition, the port of a switching hub that the
IP telephone is connected to must be set to "Trunk" port, to allow VLAN tagging. Consult your network
• Some PC LAN cards allow VLAN settings to be assigned. However, when using a PC connected to
an IP telephone with 2 ports, the VLAN settings for PC communications must be assigned only to the
secondary port of the IP telephone. Any VLAN settings assigned to the PC LAN card must be
disabled. These settings can usually be identified by "802.1Q", "802.1p", or "VLAN" in their name.
6.1.4 Jitter Buffer

When voice signals are packetised and transmitted, individual packets can take different paths through the
network and arrive at the destination at varied timings. This is referred to as "jitter", and it can cause

6.1.5 Voice Activity Detection (VAD)
degradation in speech quality. To compensate for jitter problems, the "jitter buffer" accumulates the packets
temporarily for processing.
To set the size of the jitter buffer, refer to "9.5.1 PBX Configuration—[1-1] Configuration—Slot—Site
Property—Main—VoIP-DSP Options" in the PC Programming Manual.
6.1.5 Voice Activity Detection (VAD)

VAD conserves bandwidth by detecting silent periods during a call and suppressing the packets of silence
from being sent to the network. This feature can be enabled or disabled for codec G.711.
To configure the VAD feature, refer to the appropriate section in the PC Programming Manual.
6.1.6 Network Configuration

You must evaluate the structure of the existing network to see if a VoIP network can be implemented. Below
are the points that should be evaluated.
Is the IP network a managed network?

A VoIP network should be implemented on a managed IP network such as Frame Relay, Leased Line, or
IP-VPN (Virtual Private Network).
An unmanaged network, such as the Internet (including an Internet VPN), cannot be used to employ a VoIP
network because delays and loss in data transmission can cause huge degradation in speech quality.
Is it possible to have static IP addressing?

IP telephones on the network always perform VoIP communications through the NSX server. Therefore, the
NSX server must be assigned static IP addresses, which must be programmed to each IP telephone on the
network.
Note
When the DHCP Server feature is disabled and external DHCP servers are not used, static IP
addressing must also be enabled for all IP telephones.
Does only a single router provide access to the IP network?

In a dual network, 2 routers provide access to the IP network as shown in the diagram below. However, only
one router can be used as an access point to the network.
Therefore, in the diagram below, if router A, whose IP address is assigned as the default gateway IP
address of the NSX server and the IP telephones, fails, VoIP communications are no longer possible; they
are not able to switch their default gateway from router A to router B to access the IP network.

IP Network
Router A Router B
Default gateway Default

of the NSX server: gateway of the
Router A IP Telephone:
Router A
How is the NSX server connected to remote extensions?

When the NSX server is connected to a remote extensions via public IP network without using IP-VPN,
address translation techniques (e.g., NAT/NAPT) are used. These methods prevent VoIP communications
from being carried out effectively. In such cases, the use of an SBC/Media Relay Gateway will avoid this
problem.
Note
• An SBC/Media Relay Gateway is not required for:
– Connections via a Wide Area Ethernet or LAN
– Connections via IP-VPN
• An SBC/Media Relay Gateway is required for:
– Connections via a public IP network

Connection via Wide Area Ethernet or LAN Connection via IP-VPN
Local IP Local IP Address

Address Domain
Domain
Switching Hub Router
Global IP Address
Domain
Wide Area
Ethernet/ IP-VPN
LAN
Switching Hub
Router
Local IP Address
Domain

Connection via Public IP Network
Local IP Address
Domain
SBC
Built-in Media
Relay Gateway
Router
Global IP Address
Domain
Public
IP Network
Router
Local IP Address
Domain
Are the network devices located appropriately for effective VoIP

communications?
Transmission delays can cause pauses and loss in VoIP communications. The more network devices (e.g.,
routers and switching hubs) there are between the NSX server and IP telephones or the IP network
interface, the longer the transmission delays. This is because a certain amount of delay is inevitable when
packets go through each network device.
To prevent unnecessary delays, it is recommended to connect the NSX server as close to the IP telephones
and the IP network interface as possible so that the number of the network devices is kept to a minimum.
IP Network
Router Router
Switching
Hub
Switching
Hub
Switching
Hub

6.1.7 Network Devices
6.1.7 Network Devices

You must evaluate the network devices that are used in the existing network to see if a VoIP network can be
implemented. Below are the points that should be evaluated.
Can the firewall pass packets appropriately?

If the VoIP network contains a firewall, the firewall must be configured appropriately to allow VoIP packets to
pass through the network without being blocked by filtering. For details about the protocols and port
numbers that the NSX server uses for VoIP communication, refer to "6.5 Port Security".
The ports for which you need to configure the firewall may vary depending on the network conditions.
For more information, consult your network administrator.
Are layer 2 or higher switches used?

Use of repeater hubs can increase the network load, and therefore may result in degradation in speech
quality.
To ensure high speech quality, use only layer 2 or higher switches. Use of layer 2 or higher switches is also
strongly recommended for connecting IP telephones.
Note
Note that the port of the switching hub that connects to the mother board should be set to operate under
"Auto Negotiation" mode.
Does all equipment on the LAN support 1000BASE-T connection?

To use the Gigabit Ethernet feature for the LAN, all equipment on the LAN must support 1000BASE-T. For
more information, consult your network administrator.
Are Category 5 (CAT 5) or higher cables used for 10BASE-T/100BASE-TX?

When connecting network devices, make sure to use CAT 5 or higher cables for 10BASE-T/100BASE-TX
connection. If other types of cables are used, communication may not be carried out normally.
Are Enhanced Category 5 (CAT 5e) or higher cables used for 1000BASE-T?
When connecting network devices, make sure to use CAT 5e or higher cables for 1000BASE-T. If other
types of cables are used, communication may not be carried out normally.
6.1.8 QoS (Quality of Service)

Some routers permit the configuration of priority control features. This allows the router to give higher
priority to voice packets and lower the rate of loss and delays during transmissions, hence improving speech
quality. It is strongly recommended that you use this feature, especially in networks where traffic is heavy.
Typically, a router identifies what packets to pass in priority by checking the value in the ToS field of the
header of IP packets. The V-IPGW card has the ability to set the ToS field of outgoing voice packets. When
the card is appropriately configured, the router can give voice packets from the card higher priority.
Consult your network administrator when setting the ToS field, as the setting value must be followed entire
Network policy.
You can set a higher priority to the transmission of the IP packets (SSAP/PSAP) communicated between
sites.
You can set a higher priority to the transmission of the IP packets (RTP) communicated between the PBX
and IP terminals. The IP terminals are installed in the following virtual cards:
V-IPEXT / V-SIPEXT / V-IPCS

6.1.9 Network Time Protocol (NTP)
Note
• To adjust the value in the ToS field, refer to "9.12 PBX Configuration—[1-1] Configuration—Slot—
V-IPGW128—Card Property" in the PC Programming Manual.
• For the detailed procedure for setting QoS between sites, refer to "9.5.1 PBX Configuration—[1-1]
Configuration—Slot—Site Property—Main—QoS—Setting for multi-connection signalling (SSAP/
PSAP)" in the PC Programming Manual.
• For detailed procedure for QoS setting between the PBX and IP terminals, refer to "9.5.1 PBX
Configuration—[1-1] Configuration—Slot—Site Property—Main—QoS—Setting for extension RTP" in
the PC Programming Manual.
6.1.9 Network Time Protocol (NTP)

The NSX server can be configured to contact an NTP server to receive and update its time setting
automatically.
For a SIP phone to receive and update its time setting via the NSX server, the NTP server feature must be
enabled. To enable this feature refer to "28.2.4 Network Service—[2-6] Server Feature—NTP" in the PC
Programming Manual.
If the NTP server feature is enabled:

• Case 1: An NTP server is specified in Web Maintenance Console.
– The SIP phones use the specified IP address and contact the NTP server directly.
• Case 2: An NTP server is not specified in Web Maintenance Console.
– The SIP phones use the IP address of the NSX server as their NTP server.
(The NSX server acts as an NTP server for the SIP phones.)
To specify the IP address of the NTP server, refer to "10.1.2 PBX Configuration—[2-1-2] System—Date &
Time—SNTP / Daylight Saving" in the PC Programming Manual.
If the NTP server feature is disabled, the SIP phones use their own time settings.
6.2 H.323 Trunks

This section explains information that is necessary for setting up an H.323 QSIG network over an IP
network.
6.2.1 Avoid Multiple IP Networks

A huge degradation in speech quality will be produced when calls are made through multiple IP networks as
shown below; therefore, it is recommended that you avoid establishing a VoIP network in this fashion.

6.2.2 Gatekeeper
PSTN/
BRI QSIG, etc.
IP Network 1 IP Network 2
IP Network 1 IP Network 2
6.2.2 Gatekeeper
The following are the general functions of a gatekeeper:
• Dialled number-to-IP address translation
• Authentication
• Bandwidth control
The gatekeeper provides these network management functions to registered clients. To register with the
gatekeeper, you need to configure the V-IPGW card to use the gatekeeper and programme the GK Settings
table through system programming. For details, refer to "9.12 PBX Configuration—[1-1] Configuration—Slot
—V-IPGW128—Card Property—Main—Gatekeeper Available" and "9.14.3 PBX Configuration—[1-1]
Configuration—Slot—V-IPGW128—Port Property—GK Settings" in the PC Programming Manual. After
programming, the V-IPGW card attempts to register with the gatekeeper using registration information such
as the IP address of the mother board, and destination telephone numbers specified in the GK Settings
table.
Note
• For more information about gatekeeper functions, consult the documentation of the gatekeeper.
• When using a gatekeeper, make sure to choose a compatible model. For more information about
gatekeeper compatibility with the V-IPGW card, consult a certified dealer.
6.2.3 Bandwidth Assessment

When using the IP telephones and V-IPGW card, you must ensure that the IP network in use has enough
bandwidth to support VoIP communications. If the amount of bandwidth required for VoIP communications is
more than the network can accommodate, speech quality will be compromised. In addition, there may be an

adverse effect on the performance of other applications (e.g., e-mail or Web applications) that use the same
network. Therefore, care must be taken when assessing bandwidth requirements.
Inform your network administrator of the required bandwidth, and make sure that the network can support
VoIP communications even under conditions of maximum network traffic.
Bandwidth Assessment for IP Extension Card

Required Bandwidth per IP Telephone for a Call
The required bandwidth depends on what combination of codecs and packet sending intervals is used.
Keep in mind the following points about the type of codecs and packet sending intervals, in terms of speech
quality:
• The speech quality of the codecs varies as follows: (High) G.722, G.711, G.729A (Low)*1
• The shorter the packet sending interval, the higher the speech quality.
• The higher the speech quality the IP telephones provide, the more bandwidth the IP telephones require.
*1 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.
Packet Sending Interval

Codec
20 ms 30 ms 40 ms 60 ms
G.722 /G.711
*1
87.2 kbps 79.5 kbps — —
G.729A 31.2 kbps 23.5 kbps 19.6 kbps 15.7 kbps
*1 G.722 is only available for calls between IP-PTs, and some SIP phones that support this codec during peer-to-peer
communication. For details, refer to "5.2.3 Peer-to-Peer (P2P) Connection" in the Feature Manual.
Required Bandwidth for Each IP Extension Card

To allow all IP telephones to make calls simultaneously, it is necessary to keep available the bandwidth
required by an IP extension card with the maximum number of IP telephones connected.
Provided below is the formula to calculate the amount of bandwidth required for each IP extension card.
When using the V-IPEXT/V-SIPEXT card:
Required Bandwidth = (Required Bandwidth per IP telephone × 32)
Bandwidth Assessment for V-IPGW Card

Required Bandwidth for One VoIP Channel
The required bandwidth depends on what combination of codecs and packet sending intervals is used.
Keep in mind the following points about the type of codec and packet sending interval, in terms of the
speech quality:
• The speech quality of the G.711 codec is higher than that of the G.729A codec.
• The higher the speech quality the V-IPGW card provides, the more bandwidth the card requires.
Via LAN
Codec
20 ms 30 ms 40 ms 60 ms 90 ms
G.711 87.2 kbps 79.5 kbps 75.6 kbps 71.7 kbps —
G.729A 31.2 kbps 23.5 kbps 19.6 kbps 15.7 kbps —

Via WAN (PPP: Point-to-Point Protocol)

Codec
20 ms 30 ms 40 ms 60 ms 90 ms
G.711 84 kbps 77.3 kbps 74 kbps 70.7 kbps —
G.729A 28 kbps 21 kbps 18 kbps 14.7 kbps —
Bandwidth Calculation
Provided below is the formula to find out the amount of bandwidth required for VoIP communications:
Required Bandwidth
= (No. of Fax Machines × Required Bandwidth for the G.711 codec) +
[(16 - No. of Fax Machines) × Required Bandwidth for Voice Communication]
Example
Consider the following case as an example:
• Communication: via LAN
• No. of Fax Machines: 2
• G.711 Packet Sending Interval: 20 ms (requiring 87.2 kbps per channel)
• G.729A Packet Sending Interval for Voice Communication: 20 ms (requiring 31.2 kbps per channel)
In this case, the required bandwidth will be as follows:
Required Bandwidth
= (2 × 87.2) + [(16 - 2) × 31.2]
= 611.2 (kbps)
Therefore, inform your network administrator and make sure that the network can support a bandwidth of
611.2 kbps even when the network is under conditions of maximum traffic.
Note
It is recommended that all cards on a VoIP network have the same packet sending interval.
Additional Information
As described above, it is possible to control the required bandwidth by selecting a certain combination of
codec and packet sending interval. However, it is also possible to control required bandwidth by limiting the
number of available virtual VoIP channels.
The V-IPGW card supports a total of 64 ports, each having 2 separate channels. By disabling some of the
ports, you can reduce the bandwidth required for VoIP communications.
To limit the number of VoIP channels:

Set the status of the ports you wish to disable (starting from the highest-numbered port) to OUS.
For example, if you wish to use only 10 of the available 16 virtual VoIP channels (i.e., disable 6 channels),
set ports 8, 7, and 6 to OUS as shown below:
In this case, the equation for bandwidth calculation, based on the previous example, will change as follows:
Required Bandwidth
= (No. of Fax Machines × Required Bandwidth for the G.711 codec) +
[(10 - No. of Fax Machines) × Required Bandwidth for Voice Communication]
= (2 × 87.2) + [(10 - 2) × 31.2]
= 424 (kbps)

6.2.4 Virtual VoIP Gateway Card Specifications
6.2.4 Virtual VoIP Gateway Card Specifications

For details about the RFCs and protocols for the V-IPGW card, refer to the following specifications.
ITU-T H.323
H.225.0
H.245
Codecs G.711 (a-law and µ-law)
G.729A
Voice Operations Echo Cancellation (48 ms)
Jitter Buffer (200 ms)
VAD (Voice Activity Detection)*1
PLC (Packet Loss Concealment)
DTMF Relay Inband/Outband (RFC2833)/Outband (H.245)
Fax Relay G.711 Inband/T.38
Protocol/Function RTP
RTCP
*1 VAD is only available for codec G.711.
6.3 SIP Trunks

This section provides information on using SIP trunks with the NSX server.
6.3.1 IP Telephony Service

The Virtual SIP Trunk Card (V-SIPGW) is a virtual trunk card which is designed to be easily integrated into
an Internet Telephony Service provided by an ITSP (Internet Telephony Service Provider).
As a major SIP Provider, an ITSP provides its telephony service partly through the conventional telephone
network (e.g., ISDN and Mobile), which is fee-based. An ISP (Internet Service Provider), another major SIP
Provider, does not provide telephone connection itself. However, providing its users with Internet access, an
ISP provides voice communication on the Internet for free. In this way, with VoIP technology based on the
SIP protocol, the cost of voice communication can be much cheaper than conventional telephone networks.
V-SIPGW Connection Outline

The following diagram illustrates a simple VoIP network connecting the V-SIPGW card to the Internet.

WAN (Wide Area Network)
Internet
ITSP
Local
Telephone
ISP
LAN Router
(Local Area Network)
Switching
Hub
PC IP-PT
NSX server with

V-SIPGW Card
Requirements for Internet Telephony Service

• You need to subscribe with an ISP for Internet connection.
• You need to subscribe with an ITSP for telephone connection. The ISP and ITSP may be part of the same
company.
Note
• VoIP communication using the V-SIPGW card may deteriorate depending on the ITSP being used.
• VoIP communication using the V-SIPGW card may deteriorate depending on the network conditions.
DNS (Domain Name System)

A DNS server normally provides the name resolution service for your PC. As domain names are alphabetic,
they are easier to remember. The Internet, however, is based on IP addresses. Therefore, every time a
domain name is used, a DNS server must translate the name into the corresponding IP address, and vice
versa. For example, the domain name www.example.com may be translated to 192.0.34.166. If one DNS
server does not know how to translate a particular domain name, it asks another one, and so on, until the
correct IP address is returned.
NAT Traversal
When NAT/NAPT (Network Address Port Translation) is enabled, the router translates a local IP address
from the NSX server into a global IP address. However, the router with NAT enabled does not translate local
IP addresses stored in SIP messages into global IP addresses.

Therefore, the address which the SIP Server recognises as the destination IP address to reply to is actually
the local IP address of the NSX server, not the global IP address of the router. Therefore, if the SIP Server
receives a SIP message from the NSX server and sends a message back to the NSX server using the
address stored in the SIP message, the packet information will not reach the NSX server.
STUN Servers function to solve the global IP address problem under certain NAT conditions, for example, in
case of full duplex communication. A STUN Server, used alongside the SIP Server, finds out the global IP
address of the router with NAT enabled. With the STUN feature enabled, the packet information sent by the
SIP Server is able to "traverse" NAT and reach the NSX server.
The settings can be configured to specify whether to enable the NAT Traversal feature for each ISP/ITSP. In
addition, the NAT Traversal method can be selected from "STUN" and "Fixed IP Address". NAT-traversal
settings can be programmed for up to 8 ISPs/ITSPs in the NSX server. In an expansion gateway, they can
be programmed for one ISP/ITSP. For details, refer to "9.9 PBX Configuration—[1-1] Configuration—Slot—
V-SIPGW128—Shelf Property—NAT Traversal 1-8" in the PC Programming Manual.
The V-SIPGW card may require the NAT Traversal feature to be enabled to connect to the WAN via a router.
The following diagram illustrates how VoIP communication is enabled between the V-SIPGW card and the
SIP Server (SIP Receiver) via a router with NAT enabled.
WAN
Internet
STUN Fixe
Fi xed IP Address
Fixed Addr
Ad dres
esss
es
STUN SIP SIP
Server Server Server
ISP/ITSP
ISP/ITSP
LAN
Router
(NAT enabled)
Switching
Hub
PC IP-PT
NSX server with

V-SIPGW Card

6.3.2 SIP Requirements
Note
• If an ISP/ITSP uses a device such as SBC (Session Border Controller), you may not have to enable
the NAT Traversal feature.
• A STUN Server is supplied by an ISP/ITSP, and not included with the NSX server.
6.3.2 SIP Requirements

Port Requirements
Required Ports for Each Channel
When configuring a router with NAT enabled, you need to secure a certain number of ports for each SIP and
RTP/RTCP channel. For RTP/RTCP, the number of required ports is double the number of activated SIP
trunks (Ch). For SIP signalling, the number of required ports is always one regardless of the number of
activated SIP trunks (Ch).
[Example]
If 4 SIP trunk channels are activated, you need the following number of ports:
Protocol Type Required Port
RTP 4
RTCP 4
SIP 1
Total 9
Firewall Requirements
pass through the network without being blocked by filtering. For the protocols and port numbers that the
NSX server uses for VoIP communication, refer to "6.5 Port Security".
The ports for which you need to configure the firewall may vary depending on the network conditions.
6.3.3 Router Requirements

• Port Forwarding:
It may be necessary to set the NAT router so that it forwards the incoming packets to the IP address of
the V-SIPGW card if all of the following conditions are met:
– the NSX server uses a STUN server;
– a V-SIPGW card is located under a NAT router;
– incoming packets are routed to a SIP Client port or NAT Voice (RTP) UDP port indicated in "6.5 Port
Security".
• SIP-NAT Feature:
When a V-SIPGW card is located under a NAT router that supports the SIP-NAT feature*1, it is
recommended to disable this feature.
*1 When NAT is enabled, the router translates the IP address stored in the IP header and the port number stored in the UDP header.
When SIP-NAT is enabled, the router also translates the IP address and port number stored in SIP messages.

6.3.4 Bandwidth Requirements
6.3.4 Bandwidth Requirements

When using the V-SIPGW card, you must ensure that the WAN has enough bandwidth to support VoIP
communications. Refer to the table below and ensure that the sum of the required bandwidth for each
channel is smaller than the amount the WAN (e.g., ADSL network) can provide.
Note that the amount in the table is only a guide. Subscribe to a network that has enough bandwidth. If the
amount of bandwidth required for VoIP communications is larger than what the network can accommodate,
speech quality will be compromised.
Required Bandwidth for Each Channel

The required bandwidth depends on what combination of codecs and packet sending interval is used. Keep
in mind the following points about the type of codec and packet sending interval, in terms of the speech
quality:
• The speech quality of the codecs varies as follows: G.711 (High), G.729A (Low)
• The higher the speech quality the V-SIPGW card provides, the more bandwidth the WAN requires.
Codec
10 ms 20 ms 30 ms 40 ms 50 ms 60 ms
G.711 110.4 kbps 87.2 kbps 79.5 kbps 75.6 kbps 73.3 kbps 71.7 kbps
G.729A 54.4 kbps 31.2 kbps 23.5 kbps 19.6 kbps 17.3 kbps 15.7 kbps
6.3.5 Virtual SIP Trunk Card Specifications

For details about the RFCs and protocols for the V-SIPGW card, refer to the following specifications.
Items Specification
SIP RFCs RFC3261 (UDP only)
RFC3262 (PRACK)
RFC3264 (Offer/Answer)
RFC3311 (UPDATE)
RFC3581 (Symmetric Response Routing/rport)
RFC4028 (Session Timer)
Codecs G.711 (a-law and µ-law)
G.729A
Voice Options Echo Cancellation (48 ms)
Jitter Buffer (200 ms)
VAD (Voice Activity Detection)*1
PLC (Packet Loss Concealment)
DTMF Relay Inband/Outband (RFC2833)/Outband (SIP INFO)
Fax Relay G.711 Inband/T.38

6.4 Types of PBX Networks
Items Specification
Protocol/Function RTP
RTCP
DNS (A/SRV)
NAT Traversal (STUN)
QoS (ToS field setting in IP header of RTP/RTCP/TCP)
*1 VAD is only available for codec G.711.
6.4 Types of PBX Networks

This section gives an overview of the types of networks the NSX server can participate in.
6.4.1 Multi-connection Network

This section gives an overview of Multi-connection networks.
Image of a Multi-connection network:

Multi-connection Network
NSX server
Expansion Expansion Expansion

Gateway Gateway Gateway
Features
• A maximum of 32 units can be connected in a Multi-connection network.
• KX-NSX1000/KX-NSX2000 cannot be used as an expansion gateway.
The following PBX models can be used as an expansion gateway:
– KX-NS300
– KX-NS500
– KX-NS700
– KX-NS1000
Note
In this manual, the NSX Expansion Box is treated the same as the KX-NS1000. For details about the
NSX Expansion Box, refer to the NSX Expansion Box manual.
• 31 legacy gateways and expansion units can be stacked to expansion gateways in a Multi-connection
network.

• The PBXs specified as expansion gateways use settings provided by the NSX server, so a considerable
amount of setup is done automatically.
• Some devices are available with the NSX server only through an expansion gateway. For more
information about devices that can be used through expansion gateways, see "Equipment Compatibility
for Expansion Gateways".
• Resource sharing allows users to interact as if they were all connected to one PBX, which eliminates the
need to manage information such as PBX access codes.
• All expansion gateways in a Multi-connection network can be programmed from one location.
• All expansion gateways can be monitored in a Multi-connection network for their keep-alive information.
You can see the information in Web Maintenance Console. For the details, refer to "7.5.7 Utility—Report
—Expansion Gateway Keep Alive Information" in the PC Programming Manual.
Multiple Administrator
In addition to Installer/Administrator level login account, Sub-Administrator account (Max. 32 accounts)
which can be multiple login can be added. A Sub-Administrator can be assigned to each site for
maintenance. For more information about Sub-Administrator settings, refer to 8.9 Maintenance Personnel
—Sub Administrator Setting in the PC Programming Manual.
Following 2 type of management can be provided by the account:
1) Site administration
Sub-Administrators can manage the following program setting and operation related with the assigned site:
– Site related settings
– Extension, trunk, and optional IP device port settings
– IP device registration
– isolated mode recovery
[Example: Case of five sites maintenance by three Sub-Administrators]
NSX1000/2000 Multi-connection
Site #3
Site #2 Site #4
Site #1 (NSX)
Site #5
Administrator #1 Administrator #2 Administrator #3
2) Simultaneous installation
Large amount of setting data menu can be shared with multiple sub-administrators. The items can be
divided and assigned to the responsible sub-administrators. Refer to 5.5.1 PC Programming in Feature
Manual.
[Example: Simultaneous programming by multiple administrator]

Installer Cover for all programming
NSX1000/2000 Administrator #32 responsibility
Administrator #1 responsibility Administrator #2 responsibility

ICDG setting ICDG setting
User setting User setting
#1 - #N #N+1 - #M
#1 - #N #N+1 - #M
DDI table DDI table
#1 - #N #N+1 - #M
Administrator #32
Administrator #1
Administrator #2
Conditions
• The sites that will be included in a Multi-connection network must be connected over a private IP network
before setting up the Multi-connection network.
• All sites must be installed in locations where the time difference is within 24 hours.
Bandwidth Requirements
When implementing a Multi-connection network, you must ensure that the IP network has enough
bandwidth to support both VoIP communication and Multi-connection network signalling between the NSX
sever and expansion gateways. If the amount of bandwidth required for VoIP communications and signalling
is more than the network can accommodate, speech quality will degrade. In addition, there may be an
adverse effect on the performance of other applications (e.g., e-mail or Web applications) that use the same
network. Therefore, care must be taken when assessing bandwidth requirements.
Inform your network administrator of the required bandwidth, and make sure that the network can support
VoIP communications and signalling even under conditions of maximum network traffic.
Required Bandwidth per Call

The required bandwidth depends on the following factors:
• The maximum number of simultaneous calls
• Packet sending interval
• Type of codec used
• Telephone type
Keep in mind the following points about the types of codecs and packet sending intervals, in terms of
speech quality:
• The speech quality of the codecs varies as follows: (High) G.722, G.711, G.729A (Low)*1
• The higher the speech quality an IP telephone provides, the more bandwidth it requires.
*1 When the preferred codec of each party differs, the call will be established using the lower quality codec.

For example, if the caller prefers G.711 while the called party prefers G.729A, the call will be established
using G.729A.
Number of Simultaneous Calls

The number of simultaneous calls is proportional to number of registered extensions, as shown in the chart
below. The proportion is approximately 0.25 when the number of registered extensions is 100. For more
information about the number of simultaneous calls, ask your local Panasonic dealer.
100
Number of Simultaneous Calls
90
80
70
60
50
40
30
20
10
0
10 50 100 150 200 250 300
Number of Registered Extensions
Number of Registered
10 50 100 150 200 250 300
Extensions
Number of Simultaneous
6 16 26 35 44 53 61
Calls
Required Bandwidth per Call for VoIP Communication

The required bandwidth for VoIP communication is determined by the codec used and the packet sending
interval.
Codec
20 ms 30 ms 40 ms 60 ms
G.711/G.722 *1
80 kbps 74.7 kbps 72 kbps 69.4 kbps
G.729A 24 kbps 18.7 kbps 16.0 kbps 13.4 kbps
*1 G.722 is only available for calls between IP-PTs, and some SIP phones that support this codec during peer-to-peer
communication. For details, refer to "5.2.3 Peer-to-Peer (P2P) Connection" in the Feature Manual.
Required Bandwidth per Call for Signalling

In a Multi-connection network, a certain amount of bandwidth is required for the NSX server to handle all the
calls in the network. The required bandwidth depends on the type of IP telephone.
Phone Type Required Bandwidth
IP Telephones (except SIP phones) 43.0 kbps
SIP Phone 16.0 kbps
Example:
The following examples show different cases of assessing bandwidth for a Multi-connection network.

In this example, there are 3 units in a Multi-connection network.

NSX server
Codec: G.711
Packet Interval: 20 ms
IP Network A IP Network B
Expansion Gateway A Expansion Gateway B

- Number of Extensions: 100 - Number of Extensions: 50
- Extension Type: IP-PT - Extension Type: SIP Phone
- Number of Simultaneous Calls: 26 - Number of Simultaneous Calls: 12
Bandwidth assessment for IP network A:

• Bandwidth required for VoIP communication
= Number of simultaneous calls × 2 × Required bandwidth for codecs (kbps)
= 26 × 2 × 80
= 4160 kbps
• Bandwidth required for signalling
= Number of simultaneous calls × Signalling bandwidth per a call for IP telephones (except SIP phones)
(kbps)
= 26 × 43.0
= 1118.0 kbps
• Total required bandwidth for IP network A
= Bandwidth required for VoIP communication (kbps) + Bandwidth required for signalling (kbps)
= 4160 + 1118.0
= 5278.0 kbps
Bandwidth assessment for IP network B:
• Bandwidth required for VoIP communication
= Number of simultaneous calls × 2 × Required bandwidth for codecs (kbps)
= 12 × 2 × 80
= 1920 kbps
• Bandwidth required for signalling
Number of simultaneous calls × Signalling bandwidth per a call for SIP phones (kbps)
= 12 × 16
= 192 kbps
• Total required bandwidth for IP network B
= Bandwidth required for VoIP communication (kbps) + Bandwidth required for signalling (kbps)
= 1920 + 192
= 2112 kbps
Required Items
• KX-NSXF006: Activation Key for Expansion GW (Master)

6.4.2 Multi-connection Networking Survivability
Reference
• You can add expansion gateways to the Multi-connection network using Web Maintenance Console. For
more details, refer to "5.5 Programming a Multi-connection Network".
• For more details about Multi-connection networks, refer to "4.2 Multi-connection Networking" in the
Feature Manual.
• For details about configuring and programming a Multi-connection network, refer to "3.1.1 Home Screen
—Add Site Wizard" in the PC Programming Manual.

Simplified Isolated Mode
When a fault occurs in the NSX server, or when an expansion gateway is isolated because of network
failure, the expansion gateway can continue limited communication services independently at its site.
ITSP ITSP
NSX server NSX server
Fault
Expansion Gateway Expansion Gateway

Multi-connection Network Simplified Isolated Mode
Notice
• The expansion gateway will restart. Depending on the makeup of the network, it may take 15 minutes
or more for the unit to restart in Simplified Isolated mode.
• Simplified Isolated mode operates only for 30 days. Even if the NSX server does not return to service,
the expansion gateway stops its service after this time period.
• Under Simplified Isolated mode, the expansion gateway will operate with limited features.
• System data for each expansion gateway must be configured before it can operate in Simplified
Isolated mode. Using Web Maintenance Console, you can configure the expansion gateway's system
data settings. The resulting DxSYS file can be imported during Easy Setup Wizard. For more details
about importing the NSX server system data, refer to "5.5 Programming a Multi-connection Network".
An expansion gateway will operate in Simplified Isolated mode under the following conditions:
• The NSX server allows expansion gateways to use Simplified Isolated mode.
• The connection to the NSX server has failed.
• Simplified Isolated mode setting is enabled in the expansion gateway.

• In normal mode, the NSX server manually starts the simplified Isolated mode from Web Maintenance
Console of NSX server.
• Expansion gateways continue keep-alive monitoring to the NSX server. A log of this activity can be
confirmed from Web Maintenance Console.
LED Indication
Expansion Gateway
Expansion Gateway
(KX-NS300/KX-NS500/
Operating (KX-NS1000)
KX-NS700)
Status
STATUS MASTER STATUS PBX MODE
LED LED LED LED
Normal Green ON Amber ON Green ON Amber ON
Simplified Green ON Red Green ON Red
Isolated Flashing Flashing
Mode
For more information about LED indications, refer to "4.3.1 Mother Board".
Similarly, the System Alarm button set for the flexible button on the PT lights to indicate the PBX status has
changed, and a message will be displayed on the LCD on the PT.
For details, refer to "5.6.3 Local Alarm Information" in the Feature Manual.
Simplified Isolated Mode Programming Procedure

Enabling Simplified Isolated Mode
The Isolated Mode setting is set to Disable by default.
Follow the procedure below to enable this setting using Web Maintenance Console.
Procedure
1. In Web Maintenance Console for NSX server, click Setup → PBX Configuration →
Configuration → Slot → Site property → Main.
2. Select Enable for Isolated Mode.
3. Click OK.
4. Select the expansion gateway to be programmed by using the site selection drop-down menu.
5. Click Setup → PBX Configuration → Configuration → Slot → Site property → Main.
6. Select Enable for Isolated Mode.
7. Click OK.
Note
The settings in steps 4 to 7 can also be configured directly in the Web Maintenance Console of the
expansion gateway.
Disabling Simplified Isolated Mode
You can disable the Isolated Mode setting using Web Maintenance Console.
Procedure
1. In Web Maintenance Console for NSX server, click Setup → PBX Configuration →
Configuration → Slot → Site property → Main.
2. Select Disable for Isolated Mode.

6.4.3 Information about Expansion Gateways
3. Click OK.
4. Select the expansion gateway to be programmed by using the site selection drop-down menu.
5. Click Setup → PBX Configuration → Configuration → Slot → Site property → Main.
6. Select Disable for Isolated Mode.
7. Click OK.
Note
The settings in steps 4 to 7 can also be configured directly in the Web Maintenance Console of the
expansion gateway.
Recovering from Simplified Isolated Operation

To recover from Simplified Isolated operation, restart the expansion gateway using Web Maintenance
Console or edit the system data for the Simplified Isolated site.
Procedure
1. Log in to the Isolated site using Web Maintenance Console.
2. Right click the Isolated site on the Home screen, and then click Normal Mode.
The Isolated site will start running as an expansion gateway in the Multi-connection network.
Notice
• When recovering from Simplified Isolated Mode to Normal Mode, NSX server does not keep
SMDR data or Call log data.
• A KX-NS1000 expansion gateway can export CDR data using its RS-232C port.
• Web Maintenance Console for a KX-NS300/KX-NS500/KX-NS700 can be accessed remotely to
programme its settings using a Remote Modem card (RMT card). For more information, refer to
the manual for the corresponding PBX.
Reference
For more information about Isolated mode, refer to "4.2.3.1 Simplified Isolated Mode" in the Feature Manual.
For more information about programming Isolated mode, refer to "9.5.1 PBX Configuration—[1-1]
Configuration—Slot—Site Property—Main" in the PC Programming Manual.

The following KX-NS series PBX models can be connected to a Multi-connection network as expansion
gateways.
• KX-NS300, with up to 3 expansion units
• KX-NS1000, with up to 2 stacked legacy gateways
This section explains the conditions and limitations that apply to these PBX models when they are
connected as expansion gateways. For details about individual PBXs’ specifications, refer to the
documentation for the corresponding PBX.
Setting up an Expansion Gateway

Before setting up a PBX as an expansion gateway, do the following:
1. Back up the system data of the unit you will connect as an expansion gateway.

Note
• For KX-NS300/KX-NS500/KX-NS700 users:
When you have used NSVM and continue to use the data on expansion gateway, you must back
up it.
• For details about backing up data and about initialising the PBX, refer to the PC Programming
Manual for the corresponding PBX.
• For details about Easy Setup Wizard, refer to the Installation Manual for the corresponding PBX.
2. Confirm the KX-NS series PBX software (Software File Version 004.30000 or later).
3. Upgrade the firmware for KX-NS series PBXs from KX-NS series firmware to NSX firmware for
expansion gateways. The name of upgrading the firmware as below.
For KX-NS1000 is "PCEXPGW".
For KX-NS300/500/700 is "PFEXPGW".
4. After finishing the firmware upgrade, confirm that the LED(KX-NS1000: MASTER, KX-NS300/500/700:
PBX Mode) is flashing red. Shutdown the KX-NS series PBX using the Web Maintenance Console, and
turn the power switch off.
5. Initialize and restart the KX-NS series PBX.
6. Start up Easy Setup Wizard on the KX-NS series PBX, and set the KX-NS series PBX up as an
expansion gateway.
7. On the Home screen of the NSX server, register the expansion gateway.
For more information, refer to "5.5 Programming a Multi-connection Network".
Conditions for Expansion Gateways

• KX-NSXF007: Activation Key for Expansion GW connection for NS300/500/700/1000
For more information, refer to 3.1.1 Type and Maximum Number of Activation Keys.
• A DSP card must be installed in each Expansion Gateway. For details, refer to the Installation Manual for
the corresponding PBX.
• A Compact Flash Memory card must be installed in a KX-NS1000 PBX when it is connected as an
expansion gateway.
• An SD card must be installed in a KX-NS300 PBX when it is connected as an expansion gateway. If no
SD card is installed, the expansion gateway’s PBX MODE LED will flash red.
• The software must be upgraded from Web Maintenance Console to be connected a to Multi-connection
network.
• When connecting the unit to a Multi-connection network, reinstall any activation keys being used during
stand-alone operation after the unit has been registered to the NSX server. For details, refer to the
Installation Manual for the corresponding PBX.
• When KX-NS1000 is connected a Multi-connection network as an expansion gateway, the following
features are available:
– The built-in router feature (except VPN feature)
An activation key (KX-NSN101) is required.
– The Fax server feature
• The number of available MOH and BGM entries differs depending on the PBX model.
• The number of external pagers that can be connected to each site differs depending on the PBX model.
• The following features are not available in a Multi-connection network:
– SVM (Built-in Simplified Voice Message)
– PT system programming

6.4.4 H.323 QSIG Network
– ISDN/Analogue remote maintenance

However, analogue remote maintenance is available in Simplified Isolated mode.
Notice
About upgrading the firmware for KX-NS series PBXs from KX-NS series firmware to NSX firmware for
expansion gateways:
• To download and upgrade to NSX firmware for expansion gateways, the KX-NS series PBX must be
running in stand-alone. If the PBX is running as a Slave unit, or if it is running as a Master unit with
registered Slave units (including those in Pre-INS status), the firmware cannot be upgraded.
• KX-NS series firmware and NSX firmware for expansion gateways cannot be downloaded and stored
at the same time. For example, if a KX-NS1000 PBX has downloaded an update for KX-NS series
firmware and then downloads NSX firmware for expansion gateways, the KX-NS series firmware
update will be deleted from the PBX.
• While upgrading to NSX firmware for expansion gateways, programme updates for other devices
cannot be performed.
About restoring the firmware for KX-NS series PBXs from NSX firmware for expansion gateways to
KX-NS series firmware:
• Start the expansion gateway in Simplified Isolated mode.
• Log in to Web Maintenance Console for the expansion gateway directly.
• In Web Maintenance Console, perform a programme update to restore the KX-NS series firmware.
6.4.4 H.323 QSIG Network

This section gives an overview of H.323 QSIG networks.
Image of an H.323 QSIG network:
H.323 QSIG
Network
Node 1: Node 2:
NSX server Legacy PBX
Resources for Node 1 Resources for Node 2
Features
• H.323 QSIG networks can include legacy PBXs.
• Resources are not available to extension users of other PBX without explicit configuration.
Conditions
• PBXs in an H.323 QSIG network must be connected over a private IP network.

6.4.5 Working with Multiple PBX Networks
Bandwidth Requirements
Refer to "6.2.3 Bandwidth Assessment".
Required Items
• V-IPGW: Virtual VoIP Gateway Card
Networking Notes
• For more details about H.323 QSIG networks, refer to "4.3.1 TIE Line Service" in the Feature Manual.
• For details about configuring and programming an H.323 QSIG network, refer to "10.6.1 PBX
Configuration—[2-6-1] System—Numbering Plan—Main" in the PC Programming Manual.
6.4.5 Working with Multiple PBX Networks

It is possible to connect a Multi-connection network to other PBXs via H.323 QSIG network. In an H.323
QSIG network, the Multi-connection network appears as one PBX.
Image of multiple PBX networks:
H.323 QSIG
Network
Node 1:
Multi-connection Network
Node 2:
NSX server Legacy PBX
Resources for Node 2
Expansion Expansion Expansion

Gateway Gateway Gateway
The following table shows the maximum number of sites/nodes that can be included in each type of
network.
Maximum Sites/
Network Type Method
Nodes
Private Network Multi-connection Network 32 sites
QSIG Network H.323 QSIG Network 512 nodes
Multiple PBX Networks Multi-connection Network and H.323 QSIG 16,384 sites
Network
Note
For more details about using multiple PBX networks, refer to "4.2.2 Network Type Comparison" in the
Feature Manual.

6.5 Port Security
6.5 Port Security

pass through certain ports of the ports listed below without being blocked by filtering. The ports for which
you need to configure the firewall may vary depending on the network conditions.
The following table shows the NSX server’s ports used for IP communications. Any access to the ports not
in this list is ignored.
Port Numbers for LAN Port

Port Changeable/
Protocol Application Client/Server
Number Fixed
25 TCP/UDP SMTP Server Changeable
53 UDP DNS Server Fixed
67 UDP DHCP Server Changeable
68 UDP DHCP Client Changeable
80 TCP HTTP Server Changeable
123 UDP NTP Server Fixed
143 TCP IMAP Server Changeable
161 UDP SNMP Server Changeable
443 TCP HTTPS Server Changeable
1717 UDP Connectionless UDP - Changeable
1718 TCP Connectionless TCP - Changeable
1719 UDP H.225 RAS - Changeable
1720 TCP H.225 Call Signal - Changeable
2103 TCP CMM Server Fixed
2300 TCP Telnet-SMDR - Changeable
2727 UDP MGCP*1 - Changeable
3493 TCP UPS*2 - Fixed
3702 UDP WSD Server Changeable
4560–4561 UDP PSAP - Changeable
4562 UDP SSAP - Changeable
5060 UDP SIP UA (EXT) - Changeable
5061 TCP SIP-TLS - Changeable
9300 UDP PTAP - Changeable
10000– TCP H.323 Dynamic Port - Changeable
10895 (H.225 Send, H.245 Send/
Receive, Connection-less
[TCP] Send Port)

6.5 Port Security
Port Changeable/
Number Fixed
20000 TCP UM-VMA*3 Server Fixed
30021 TCP/UDP FTP/FTPS Server Changeable
31000 TCP FOS - Changeable
32727 UDP MGCP for IP-CS
*1
- Changeable
33090 UDP ACS-MDW Server Fixed
33091
33092 TCP
33131
33321 TCP Access Point Login (Telnet) Server Changeable
33333 TCP CTI 3rd Party Connection - Changeable
33334 TCP CTI 1st Party Connection - Changeable
33478 UDP STUN Client Changeable
33702 UDP ACS-MDW (WSD) Server Fixed
35060 UDP SIP UA (CO) - Changeable
39300 UDP PTAP for IP-CS - Changeable
40000– TCP/UDP FTP/FTPS-Data Server Changeable
40149
50000– UDP SNMP TRAP Client Fixed
65535
(Ephemeral)
TCP/UDP FTP Client
TCP/UDP FTP/FTPS-Data Client
UDP NTP Client
UDP DNS Client
UDP SYSLOG Client
TCP/UDP SMTP Client
TCP/UDP POP3 Client
TCP/UDP ACS-MDW Server
*1 Media Gateway Control Protocol. Used for call control command data and LCD/LED data transmission.
*2 Used by UPS daemon.
*3 Used by Unified Messaging.
Port Numbers for MNT Port

Port Changeable/
Number Fixed
21 TCP/UDP FTP/FTPS Server Changeable
25 TCP/UDP SMTP Server Changeable

6.5 Port Security
Port Changeable/
Number Fixed
53 UDP DNS Server Changeable
67 UDP DHCP Server Changeable
123 UDP NTP Server Fixed
143 TCP IMAP Server Changeable
161 UDP SNMP Server Changeable
2103 TCP CMM Server Fixed
2300 TCP Telnet-SMDR - Changeable
3493 UDP UPS*1 - Fixed
3702 UDP WSD Server Changeable
8080 TCP Web Maintenance Console - Changeable
33090 UDP ACS-MDW Server Fixed
30091
30092 TCP
33131
33321 TCP Access Point Login (Telnet) Server Changeable
33333 TCP CTI 3rd Party Connection - Changeable
33702 UDP ACS-MDW (WSD) Server Fixed
40000– TCP/UDP FTP/FTPS-Data Server Changeable
40095
50000– UDP SNMP TRAP Client Fixed
65535
TCP/UDP FTP Client
(Ephemeral)
TCP/UDP FTP/FTPS-Data Client
UDP NTP Client
UDP DNS Client
UDP SYSLOG Client
TCP/UDP SMTP Client
TCP/UDP POP3 Client
TCP/UDP ACS-MDW Server
*1 Used by UPS daemon.

6.6 Network Security
Port Numbers for Optional DSP Cards

Port Changeable/
Number Fixed
12000– UDP RTP/RTCP - Changeable
13535
21000– UDP RTP/RTCP for NAT traversal - Changeable
24071
6.6 Network Security

6.6.1 Firewall
Description
The NSX server includes a firewall for inspecting packets at the WAN–LAN boundary and rejecting
unauthorised packets. The firewall can also sense unauthorised access and DoS attacks and take
appropriate measures. This feature applies only to packets routed via IP.
Conditions
• Filter priority
If multiple security settings are enabled, such as Packet Filtering, SPI, and DoS Protection, some filter
settings may conflict with one another. To avoid this, the following priorities are applied to the filters. In the
table, priority 1 has the highest priority, and priority 13 has the lowest priority.
Destination
Priority Security rule NSX server WAN to WAN to LAN to
to WAN NSX server LAN WAN
1 DoS Protection – ü ü ü
2 Stateful Packet Inspection – ü ü ü
Drop
3 IPv4 Packet Filtering ü ü ü ü
(Filter)*1
4 Automatic filtering system ü ü ü ü
reservation port*2
5 VoIP Port Dynamic Settings – – ü ü
6 NET BIOS Packet Filtering – – – –
7 Private IP Address Filtering – ü ü ü
8 ICMP Echo Request Packet – ü – –
Filtering
9 Stateful Packet Inspection – – ü ü
Accept
10 Port Forward – – ü ü
11 Pass Through – – ü ü
12 DMZ Host – – ü ü

6.6.2 Firewall—Packet Filtering
Destination
Priority Security rule NSX server WAN to WAN to LAN to
to WAN NSX server LAN WAN
13 IPv4 Packet Filtering ü ü ü ü
(LAN->WAN Basic Policy)
(WAN->LAN Basic Policy)
ü: Applicable for prioritising

–: Not applicable
*1 Setting the IPv4 Packet Filtering (Filter) to allow full access, may leave your system open to network attacks. Consider this
carefully before configuring this setting.
*2 Depending on system operation, specific ports can be set to allow or disallow network traffic. For details, consult the system
administrator.
6.6.2 Firewall—Packet Filtering

Description
This feature filters IPv4 packets (e.g., user IP data and IP data addressed to the NSX server). You can
configure the LAN → WAN basic policy and WAN → LAN basic policy, which are system wide.
You can also configure filter settings for each entry. If the system-wide and entry-specific settings conflict,
the entry filter is prioritised.
LAN → WAN Basic Policy, WAN → LAN Basic Policy
• Defines the basic policy for IPv4 packets travelling from the LAN to the WAN (allow/deny).
This policy applies to the entire system. If you select "deny", all packets travelling from the LAN to the
WAN will be discarded.
• Defines the basic policy for IPv4 packets travelling from the WAN to the LAN (allow/deny).
This policy applies to the entire system. If you select "deny", all packets travelling from the WAN to
the LAN will be discarded. This policy applies to packets addressed to the NSX server itself.
Filter
• You can configure up to 64 entries. For each entry, you can specify whether it is enabled or disabled.
• Filter rules are prioritised by entry order.
• The following table shows which settings can be configured for a filter rule.
Setting Description
Protocol number Specify a protocol number directly (0–255)
Specify a protocol type (ICMP, TCP, UDP, TCP&UDP)
Originating IP address By specifying a subnet, you can apply the filter to a range of
addresses.
Destination IP address By specifying a subnet, you can apply the filter to a range of
addresses.
TCP/UDP originating port You can specify a range.
TCP/UDP destination port You can specify a range.
Direction LAN->WAN, WAN->LAN
Operation Allow/Deny
Log Record in log or do not record in log

6.6.3 Firewall—Stateful Packet Inspection
PC Programming Manual References

27.9 Router Configuration—Firewall—[2-2] Packet Filtering
6.6.3 Firewall—Stateful Packet Inspection

Description
Stateful Packet Inspection (SPI) is a feature where the firewall inspects the contents of a packet and
determines dynamically whether to allow or deny the packet. If SPI is enabled, packets determined to be
"INVALID" (packets that do not apply to any other state) are denied. On this NSX server, SPI applies to both
incoming (WAN → LAN) and outgoing (LAN → WAN).
Using the following "TCP flag state" as the detection criteria, packets that do not match the TCP state
change are discarded by the SPI feature.
This feature remembers each transmission state, and by predicting the next packet that will arrive, it can
detect unauthorised access and discard packets accordingly.

27.8 Router Configuration—Firewall—[2-1] One Touch Security
6.7 Hot Standby

Keeps an NSX server in standby mode running and synchronised with the NSX server in Active mode.
These NSX servers monitor each other's status, so if a fault occurs in the Active mode server, the standby
mode server immediately takes over operation. Normally, the Primary server operates in Active mode, and
the Secondary server operates in standby mode. However, the modes may switch depending on the
operating conditions (i.e., the Primary server operates in standby mode and the Secondary server operates
in Active mode).
Because both NSX servers (Primary and Secondary) use the same virtual IP address, IP devices (IP-PTs,
etc.) see them as "one" NSX server.
Because the servers are continuously synchronised, switching operation from one NSX server to the other
can be done quickly (in few minutes).
Image of a Hot Standby connection

There are 2 types of a hot standby connection.
Local connection:
Data Transfer
(Active Standby)
LAN3 LAN3
Alive monitoring
Redundancy Switching
Primary LAN1 LAN1 Secondary
Server Server
(Active) (Standby)
L2 Switch

6.7 Hot Standby
• To synchronise data, both NSX servers are connected directly via their LAN3 ports.
– The LAN cable must be a CAT 5e (Enhanced Category 5) cable that supported 1 Gbps.
• Use an intelligent hub that can receive GARP (Gratuitous ARP) packets for the L2 switch.
Remote connection:
Site #1 Site #2
Primary Server (Active) Secondary Server (Standby)
LAN3 LAN1 LAN1 LAN3
Router Router
L2 Network
(e.g., Wide Area Ethernet)
Site #3 Site #4
VLAN1
VLAN2
Important
For security reasons, the communication path for data synchronisation between the LAN ports of the
NSX servers must be encrypted.
Note
• To remotely connect the primary server and the secondary server, the network environment must be
set as specified below.
– Sites are connected with the layer 2 (L2) network (e.g. Wide Area Ethernet).
– The LAN1 ports of all the NSX servers are connected to the same network segment.
– The LAN3 ports of all the NSX servers are connected to the same network segment.
– The LAN3 ports and the LAN1 ports are connected to different network segments.
[Example]
IP address (LAN1): 10.10.1.1/24

6.7 Hot Standby
IP address (LAN3): 192.168.2.1/24
NSX Server Operating Status

Active: Provides services to connected devices as the NSX server
Normally, the Primary server operates in Active mode
Standby: On standby to assume operation if the NSX server in Active mode goes off-line (fault occurs:
Power failure etc.)
Normally, the Secondary server operates in standby mode.
Sharing of Activation Keys

• To enable this feature, Activation Key for Redundancy (KX-NSXF008) is required. Only the Primary server
requires this activation key; it does not need to be installed in the Secondary server.
The NSX servers mostly share the activation keys installed in the Primary server. However, the following
activation keys must be installed separately in the Secondary server.
– System Activation Key (KX-NSX101/KX-NSX201)
– Maintenance Annual Key (KX-NSX2201)
– Remote Maintenance Annual Key (KX-NSX6211): Required if remote maintenance is used
• By holding copies of the activation keys installed in the Primary server, the Secondary server can perform
redundant operations.
If the Primary server’s operating status switches to standby, the Secondary server can provide service by
using the copies of the activation keys.
• If the Primary server has been off-line for 30 days, the Secondary server will stop providing all services
except Web Maintenance Console. The date counter will be reset when the Secondary server receives
transmissions from the Primary server again.
• If the Primary server is replaced with a new NSX server (due to malfunction, etc.), the MPR-ID of the
Primary server will have changed. In this case, because it no longer matches the MPR-ID information of
the activation key that the secondary server holds as a copy, the activation key must be reissued with a
new MPR-ID for Primary PBX, and the activation key must be re-installed.
Conditions
• Data synchronisation is performed only for redundancy between the Primary server and the Secondary
sever.
• The software version number (major and minor) of both the Primary and Secondary servers must be the
same. Otherwise, data synchronisation will not be performed.
• The hardware configuration (type and number of SSD and DSP cards) of the Primary and Secondary
servers must be the same.
• The area setting of both the Primary and Secondary servers must be the same.
• When the data synchronisation is suspended temporarily (due to a communication error, manual stop,
etc.), the data synchronisation can be resumed automatically at the time of day where no user uses the
NSX server. This feature can be enabled/disabled in the system settings. (Refer to 5.6 System Control—
Hot Standby—Data Sync in the PC Programming Manual)
• When both NSX servers (Active and standby) operate normally, data synchronisation is performed
whenever the target data is changed. For details about the target data, refer to "5.6.9 Hot Standby" in the
Feature Manual.
Conditions for Accessing Web Maintenance Console

• When users access Web Maintenance Console, they automatically connect to the NSX server whose
status is Active. To connect to an NSX server whose status is Standby, you need to enter the IP address
of that NSX server. Each of the IP addresses and applications are shown according to the following:

6.7 Hot Standby
– Access by Virtual IP address: Setting of NSX server (Active) and Maintenance (update and log
acquisition, etc.)
– Access by IP address of NSX server (Standby): Maintenance of NSX server (Standby)
Keep-Alive Monitoring
• The Primary and Secondary servers perform keep-alive monitoring with each other through the LAN1
port.
If one server detects a fault in the other server, the first server automatically switches its operating status
(Active ⇔Standby).
In Web Maintenance Console, you can manually switch the status from Active mode to standby mode.
The following illustration shows the patterns of mode switching.
Primary server is now able to monitor Secondary server.
Secondary server goes off-line
Secondary
Primary Server: Primary Server: Primary Server:
server Manual
Active Active Standby
goes off-line switching
Secondary Server: Secondary Secondary Server: Secondary Server:

Off-line server Standby Active
is restored
Primary server
Primary Primary Primary Secondary goes off-line
server server is server server is now
goes off-line restored goes off-line able to monitor
Primary server.
Primary server
is restored
Secondary
Primary Server: server Primary Server:
Off-line goes off-line Off-line
Secondary Server: Secondary Secondary Server:

Off-line server is Active
restored
Off-line: A state in which the operation of NSX server is stopped due to a system failure, etc. (This excludes
cases in which the LAN1 cable is disconnected.)
• In the system settings, the Keep-Alive method (Unicast or Multicast) can be selected. When Unicast is
selected, the IP address of the LAN 1 of the other NSX server must be set.
Confirming the Operating Status

You can confirm the operating status by the SYSTEM MODE LED or the Data Transfer Status indication in
Web Maintenance Console. For details about confirming the status in Web Maintenance Console, refer to

6.7 Hot Standby
5.6 System Control—Hot Standby—Command in the PC Programming Manual. For more information about
LED indications, see 4.3.1 Mother Board.
State Web Maintenance Console
(Data Transfer Status)
Hot Standby is disabled None
Active Available (Sender)
Standby Available (Receiver)
Transferring data Executing
Data synchronisation stopped (during data transmission) Executing
Data synchronisation stopped (data transmission completed) Suspended
Note
If data synchronisation is manually stopped through Web Maintenance Console while data is being
transmitted between the Primary server and the Secondary server, the status of the NSX servers
changes to "Data synchronisation stopped (during data transmission)". When data transmission
completes, the status of the NSX servers changes to "Data synchronisation stopped (data transmission
complete)". If you need to disconnect the LAN cable from the LAN3 port, make sure that the status of
the NSX servers is "Data synchronisation stopped (data transmission completed)".
RTP/RTCP Port Number for DSP Cards

The starting RTP/RTCP port number used by the DSP cards installed in the Primary server can be specified
in NAT - Voice (RTP) UDP Port No.. For details, refer to "9.9 PBX Configuration—[1-1] Configuration—Slot
—V-SIPGW128—Shelf Property—NAT Traversal 1-8" in the PC Programming Manual.
The starting RTP/RTCP port number used by the DSP cards in the Secondary server is calculated by
adding 3072 to the port number set in the Primary server.
[Example]
If the starting port number of the RTP/RTCP port for the Primary server is 21000 (default), the starting port
number for the Secondary server is 24072. In this case, the range of port numbers used by each server’s
DSP cards is as follows:
DSP slot#- DSP L DSP M DSP S

NSX Server
core Start End Start End Start End
Primary DSP#1-1 21000 21511 21000 21511 21000 21511
DSP#1-2 21512 22023 - - - -
DSP#2-1 22024 22535 22024 22535 22024 22535
DSP#2-2 22536 23047 - - - -
DSP#3-1 23048 23559 23048 23559 23048 23559
DSP#3-2 23560 24071 - - - -

6.7 Hot Standby
DSP slot#- DSP L DSP M DSP S

NSX Server
core Start End Start End Start End
Secondary DSP#1-1 24072 24583 24072 24583 24072 24583
DSP#1-2 24584 25095 - - - -
DSP#2-1 25096 25607 25096 25607 25096 25607
DSP#2-2 25608 26119 - - - -
DSP#3-1 26120 26631 26120 26631 26120 26631
DSP#3-2 26632 27145 - - - -
Hot Standby Setup

Because the NSX server cannot provide any services while Hot Standby is being configured, Hot Standby
should be set up during a period when no users are using the NSX server.
Important
• Before the setup, we strongly recommend that you make a backup of all system files. For the backup
procedures, refer to the following sections in the PC Programming Manual:
6.1 Tool—System Data Backup
6.8 Tool—UM Data Backup
• If a failure occurs during the Hot standby setup, you can restore the system to a point before the Hot
standby setup using the system files of the backed up Primary server. After restoring the Primary
server, always perform the Hot standby setup from the beginning. For the restore procedures, refer to
the following sections in the PC Programming Manual:
6.1 Tool—System Data Backup
6.8 Tool—UM Data Backup
• For replacing the Primary server with a new NSX server, we strongly recommend making a backup of
the system file (DNSYS) in the Primary server. For the backup procedures, refer to 7.2.2 Utility—File
—File Transfer PBX to PC in the PC Programming Manual.
• In the Hot Standby, set the virtual IP address and non-virtual IP addresses as below:
[Example]
Stand-alone:
NSX server IP address
Non-Virtual Virtual
NSX server (Stand-alone) 192.168.0.101 –
Hot Standby:
NSX server IP address
Non-Virtual Virtual
NSX server (Primary) 192.168.0.201 192.168.0.101
NSX server (Secondary) 192.168.0.202 192.168.0.101
• In the Hot Standby (Remote connection), set the virtual IP address, non-virtual IP addresses and IP
addresses as below:
[Example]
Stand-alone:

6.7 Hot Standby
NSX server IP address (LAN1) IP address (LAN3)

Non-Virtual Virtual
NSX server (Stand-alone) 10.10.1.1 – –
Hot Standby:
NSX server IP address (LAN1)*1 IP address (LAN3)*1
Non-Virtual Virtual
NSX server (Primary) 10.10.1.2 10.10.1.1 192.168.2.1
NSX server (Secondary) 10.10.1.3 10.10.1.1 192.168.2.2
*1 Subnet masks (LAN1 and LAN3) are set both to 255.255.255.0.
You must set the same IP address that was used for the NSX server in stand-alone mode as the virtual
IP address. If you set a different virtual IP address, you will also need to change the PBX IP address
setting of all IP-PTs connected to the NSX server. Then, specify a new "Non-virtual" IP address for the
each NSX server.
There should be no redundancy between the "Non-virtual" IP address and below:
• Virtual IP address
• IP address of the DSP port of the primary and secondary servers
• IP address of the LAN3 port
Configuring a Hot Standby setup for the first time (Local connection)
1. When switching the NSX server currently operating in Stand-alone mode to Hot standby configuration,
disconnect the NSX server from the network to prevent causing any impact on the network.
2. Install the Activation Key for Redundancy (KX-NSXF008) required for hot standby. For more
information, refer to 5.4.5 Installing Additional Activation Keys.
3. Configure the NSX server as the Primary server.
3-1. Click Setup → Network Service → IP Address/Ports → Basic Settings tab.
3-2. In LAN Setting—IP Address, specify the new IP address (non-virtual). IP address before the
change is used as the virtual IP address.
3-3. Click OK.
3-4. A confirmation message will be displayed. Click OK. (To apply the settings, perform the restart
operation in step 8.)
3-5. Click Maintenance → System Control → Hot Standby → Configuration tab.
3-6. In Hot Standby Mode, select Enable.
3-7. In Setup Position, select Primary.
3-8. In MPR-ID for Secondary, specify the MPR-ID of the NSX server to use as the Secondary server.
3-9. In Virtual IP Address, specify a virtual IP Address.
3-10. In IP address of HA (LAN3 port) for Primary, specify the IP address (LAN3) for the primary
server. If the default is used, this step is not necessary.
3-11. In IP address of HA (LAN3 port) for Secondary, specify the same IP address (LAN3) as that
for the secondary server. If the default is used, this step is not necessary.
3-12. In Subnet Mask of HA (LAN3 port), specify the subnet mask (LAN3). If the default is used, this
step is not necessary.
3-13. If Unicast is selected in Keep Alive Method, specify the non-Virtual IP address (LAN1) for the
secondary server in IP Address for Secondary.
3-14. Click OK.

6.7 Hot Standby
4. Restart the Primary server. For more information, refer to 7.1.3 Restarting the NSX server.
5. Connect the Primary server via their LAN1 port to the L2 switch, and connect to the network again.
6. Configure the other NSX server as a Secondary server.
6-1. Start and initialise the NSX server.
6-2. In Easy Setup Wizard, set the IP Address that is different from the primary server. After complete
the initial NSX server settings, the Secondary server will restart.
6-3. After the Secondary server have restarted, login to the Web Maintenance Console. Also, check
that the software version is the same as the Primary server.
6-6. In Setup Position, select Secondary.
6-7. In MPR-ID for Primary, specify the MPR-ID of the Primary server.
6-8. In Virtual IP Address, specify the same virtual IP address as the Primary server.
6-9. In IP address of HA (LAN3 port) for Primary, specify the same IP address (LAN3) as that for the
primary server. If the default is used, this step is not necessary.
6-10. In IP address of HA (LAN3 port) for Secondary, specify the IP address (LAN3) for the
secondary server. If the default is used, this step is not necessary.
primary server in IP Address for Primary.
6-13. Click OK.
7. Connect the Secondary server via their LAN1 port to the same L2 switch, and connect to the network.
(See the figure "Image of a Hot Standby connection".)
8. Restart the Secondary server. For more information, refer to 7.1.3 Restarting the NSX server. When
the restart is completed, the LED (SYSTEM MODE) of Primary server flashes green (60/minute) and
the LED (SYSTEM MODE) of Secondary server illuminates in amber.
Note
To access to the Web Maintenance Console, use the IP address (non-virtual) of each NSX server.
9. Connect the NSX servers directly via their LAN3 ports. (See the figure "Image of a Hot Standby
connection".)
10. Log in to the Web Maintenance Console using the virtual IP address.
11. A confirmation message will be displayed. Click OK to display Hot Standby—Command screen.
12. Click Data Transfer Start to start data synchronisation. (If the Data Transfer Start button is not
available, click the Data Transfer Stop button first, and then the Data Transfer Start button.)
The LED (SYSTEM MODE) of Primary server flashes green (120/minute) and then bulk data
synchronisation is started. When the bulk data synchronisation is completed, the LED (SYSTEM
MODE) of Primary server illuminates in green and then the Hot standby function becomes available.
Note
Synchronisation time varies depending on the size of SSD. (e.g. For 8 GB, it takes about 60 minutes
and for 64 GB, about 8 hours)
Configuring a Hot Standby setup for the first time (Remote connection)
1. In the NSX server currently operating in Stand-alone mode, install the Activation Key for Redundancy
(KX-NSXF008) required for hot standby. For more information, refer to 5.4.5 Installing Additional
Activation Keys.

6.7 Hot Standby
2. Configure the NSX server as the Primary server.

2-1. Click Setup → Network Service → IP Address/Ports → Basic Settings tab.
2-2. In LAN Setting—IP Address, specify the new IP address (non-virtual). IP address before the
change is used as the virtual IP address.
2-3. Click OK.
operation in step 2-16.)
2-8. In MPR-ID for Secondary, specify the MPR-ID of the NSX server to use as the Secondary server.
2-9. In Virtual IP Address, specify a virtual IP Address.
Secondary server in IP Address for Secondary.
2-11. In IP Address for Secondary, specify the same non-Virtual IP address (LAN1) as the Secondary
server.
2-12. In IP address of HA (LAN3 port) for Primary, specify the IP address (LAN3) for the Primary
server.
2-13. In IP address of HA (LAN3 port) for Secondary, specify the same IP address (LAN3) as the
Secondary server.
2-14. In Subnet Mask of HA (LAN3 port), specify the subnet mask (LAN3). This network segment
must be different from the LAN1 port.
2-15. Click OK.
operation in step 2-16.)
2-17. Restart the Primary server. For more information, refer to 7.1.3 Restarting the NSX server. When
the restart is completed, the LED (SYSTEM MODE) of Primary server flashes green (60/minute).
3. Configure the other NSX server as a Secondary server.
3-1. Start and initialise the NSX server.
3-2. In Easy Setup Wizard, set the IP Address that is different from the primary server. After complete
the initial NSX server settings, the Secondary server will restart.
3-3. After the Secondary server have restarted, login to the Web Maintenance Console. Also, check
that the software version is the same as the Primary server.
Primary server in IP Address for Primary.
3-10. In IP address of HA (LAN3 port) for Primary, specify the same IP address (LAN3) as the
Primary server.
Secondary server.
3-12. In Subnet Mask of HA (LAN3 port), specify the same subnet mask (LAN3) as the Primary
server.
3-13. Click OK.
3-14. A confirmation message will be displayed. Click OK.
3-15. Restart the Secondary server. For more information, refer to 7.1.3 Restarting the NSX server.
When the restart is completed, the LED (SYSTEM MODE) of Secondary server illuminates in amber.
4. Connect the LAN3 port of NSX servers to the L2 Network. (See the figure "Image of a Hot Standby
connection".)

6.7 Hot Standby
6. A confirmation message will be displayed. Click OK to display Hot Standby—Command screen.

The LED (SYSTEM MODE) of Primary server flashes green (120/minute) and then bulk data
MODE) of Primary server illuminates in green and then the hot standby function becomes available.
Note
Synchronisation time varies depending on the size of SSD. (e.g. For 8 GB, it takes about 60
minutes and for 64 GB, about 8 hours)
8. Check the throughput of data synchronisation.
a. Click Maintenance → System Control → Hot Standby → Data Sync tab.
b. Click the Test LAN3 button. The dialogue will display result of a throughput measurement.
c. If the measured throughput is lower than Estimated Throughput (Total) that is displayed in Data
Sync tab, it is necessary to reduce data to be synchronised or increase the capacity of the
Internet line.
Replacing the Primary server with a new NSX server

If a malfunction occurs in the Primary server, it can be replaced using the following procedure:
1. Set up the new NSX server as a Primary server.
1-1. Initialise the new Primary server, and start Easy Setup Wizard.
1-2. In Easy Setup Wizard, import the system back file (DNSYS) for the Primary server.
1-3. Install Activation Key for Redundancy (KX-NSXF008). A separate activation key is required for the
replacement NSX server.
1-7. In MPR-ID for Secondary, specify the MPR-ID of the Secondary server.
1-8. Confirm that Virtual IP Address is same as the virtual IP address of the Secondary server.
1-9. In IP address of HA (LAN3 port) for Primary, specify the IP address (LAN3) for the Primary
server. If the default is used, this step does not necessary.
1-10. In IP address of HA (LAN3 port) for Secondary, specify the same IP address (LAN3) as that
for the secondary server. If the default is used, this step is not necessary.
secondary server in IP Address for Secondary.
1-13. Click OK.
2. Set up the new NSX server as a Secondary server.
2-2. In MPR-ID for Primary, specify the MPR-ID of the new Primary server.
2-3. Click OK.
3. Connect the new Primary server via their LAN1 port to the same L2 switch, and connect to the network.
(See the figure "Image of a Hot Standby connection".)
4. Restart the Secondary server. For more information, refer to 7.1.3 Restarting the NSX server.
5. After the Secondary server has restarted, restart the new Primary server. When the restart is
completed, the LED (SYSTEM MODE) of Primary server illuminates in amber and the LED (SYSTEM
MODE) of Secondary server flashes green (60/minute).

6.7 Hot Standby
Note
To access the Primary server, please use the IP address (non-virtual) of the Primary server.
connection".)
8. Click Maintenance → System Control → Hot Standby → Command tab.
The LED (SYSTEM MODE) of Secondary server flashes green (120/minute) and then bulk data
synchronisation is started. When bulk data synchronisation is completed, the LED (SYSTEM MODE) of
Secondary server illuminates in green and then the Hot standby function becomes available.
10. When synchronisation has started, the operation status of the Primary server changes to standby. To
switch the operation status of the Primary server to Active, refer to 5.6 System Control—Hot Standby—
Command in PC Programming Manual.
Replacing the Secondary server with a new NSX server

If a malfunction occurs in the Secondary server, it can be replaced using the following procedure:
1. Initialise the new Secondary server, and start Easy Setup Wizard.
2. After completing Easy Setup Wizard, confirm the MPR-ID in Web Maintenance Console. And also,
check that the software version is the same as the Primary server.
3. Log in to Web Maintenance Console of the Primary server to change the Hot Standby settings.
3-1. In MPR-ID for Secondary, specify the MPR-ID of the Secondary server.
3-2. Click OK.
4. Set up the new NSX server as a Secondary server.
4-6. In IP address of HA (LAN3 port) for Primary, specify the same IP address (LAN3) as that for the
primary server. If the default is used, this step is not necessary.
secondary server. If the default is used, this step is not necessary.
primary server in IP Address for Primary.
4-10. Click OK.
operation in step 6.).
5. Connect the new Secondary server via their LAN1 port to the same L2 switch, and connect to the
network. (See the figure "Image of a Hot Standby connection".)
6. Restart the Primary server. For more information, refer to 7.1.3 Restarting the NSX server.
7. After the Primary server has restarted, restart the new Secondary server.
When the restart is completed, the LED (SYSTEM MODE) of Primary server flashes green (60/minute)
and the LED (SYSTEM MODE) of Secondary server illuminates in amber.
Note
To access the Secondary server, use the IP address (non-virtual) of the Secondary server.

6.7 Hot Standby
connection".)
10. Click Maintenance → System Control → Hot Standby → Command tab.
The LED (SYSTEM MODE) of Primary server flashes green (120/minute) and then the bulk data
MODE) of Primary server illuminates in green and then the Hot standby function becomes available.
System file Upload

While the Hot Standby feature is active, you can upload the system file (DNSYS) with the following
procedure:
When an administrator is on site:

1. Log in to Web Maintenance Console of the NSX server in Standby mode. You must enter the IP
address of that server. For details about the IP address, refer to "LAN Setting—IP Address" in "28.1
Network Service—[1] IP Address/Ports—Basic Settings" in the PC Programming Manual.
2. Shut down the NSX server in Standby mode, and then turn the power switch off. For details, refer to
"5.5 System Control—System Shutdown" in the PC Programming Manual.
3. Log in to Web Maintenance Console using the Virtual IP Address. You will be connected automatically
to the NSX server in Active mode.
4. Transfer the system file (DNSYS) to the NSX server. For details, refer to "7.2.1 Utility—File—File
Transfer PC to PBX" in the PC Programming Manual.
5. Restart the NSX server in Active mode. For more information, refer to "7.1.3 Restarting the NSX
server".
6. After the NSX server in Active mode has restarted, turn on the power switch of the NSX server in
Standby mode.
When no administrator is on site (an installer remotely uploads the file):

1. Log in to Web Maintenance Console using the Virtual IP Address. You will be connected automatically
to the NSX server in Active mode.
2. Click Maintenance→System Control→Hot Standby→Command tab.
3. Click Data Transfer Stop to stop synchronising the NSX servers.
4. Confirm that Data Transfer Status has changed to Suspended.
If Data Transfer Status shows Executing, the NSX servers are continuing to synchronise data. Wait
until it changes to Suspended.
5. Transfer the system file (DNSYS) to the NSX server. For more information, refer to "7.2.1 Utility—File—
File Transfer PC to PBX" in the PC Programming Manual.
6. Restart the NSX server in Active mode. For more information, refer to "7.1.3 Restarting the NSX
server".
When the restart is completed, the NSX server in Active mode switches to Standby mode, and the NSX
server in Standby mode switches to Active mode automatically.
7. Log in to Web Maintenance Console using the Virtual IP Address.
9. Click Execute to switch the NSX server’s operating status.

6.7 Hot Standby
10. A confirmation message will be displayed. Click Yes. The NSX servers restart automatically.
After both NSX servers have restarted, the NSX server in Active mode switches to Standby mode, and
the NSX server in Standby mode switches to Active mode.
11. Log in to Web Maintenance Console using the Virtual IP Address.
13. Click Data Transfer Start to resume synchronising the NSX servers.
14. Confirm that Data Transfer Status has changed from Suspended to Available (Sender).
Software Update
While the Hot Standby feature is active, you can update programme files with the following procedure.
Note
When updating the NSX server firmware from 002.1xxxx or an earlier version, the NSX server must be
disconnected from the network in advance. For detailed procedure, refer to the installation manual of
002.1xxxx.
1. Log in to Web Maintenance Console.
You will be connected automatically to the "NSX server in Active mode" (hereinafter referred to as
"NSX-A").
3. Click Data Transfer Stop to stop synchronising the NSX servers.
4. Confirm that Data Transfer Status has changed to Suspended.
If Data Transfer Status shows Executing, the NSX servers are continuing to synchronise data. Wait
until it changes to Suspended.
5. Log in to Web Maintenance Console of "NSX server in Standby mode" (hereinafter referred to as
"NSX-B").
You must enter the IP address of that server. For details about the IP address, refer to "LAN Setting—
IP Address" in "28.1 Network Service—[1] IP Address/Ports—Basic Settings" in the PC Programming
Manual.
6. Download the programme file (for the Main Unit) to the NSX-B.
For details, refer to "5.1.1 System Control—Program Update—Download Program File" in the PC
Programming Manual.
7. Update the programme file. NSX-B restarts automatically. For details, refer to "5.1.2 System Control—
Program Update—Update Program File" in the PC Programming Manual. After NSX-B has restarted,
NSX-B enters the "Standby" status.
8. Log in to Web Maintenance Console of the NSX server in NSX-A.
9. Download the programme files to the NSX-A.
10. Update the programme files. NSX-A restarts automatically. After NSX-A has restarted, the NSX-B
status changes the "Active" status, and the NSX-A status changes the "Standby" status.
11. Switch the statuses of the NSX servers. (If NSX-B is operated as the "Active mode" this step can be
skipped.)
• Log in to Web Maintenance Console.
• Maintenance→System Control→Hot Standby→Command tab.
• Click Execute button.
• A confirmation message will be displayed. Click Yes. The NSX servers restart automatically. After
both NSX servers have restarted, the NSX-B status changes the "Standby" status, and the NSX-A
status changes the "Active" status.

6.7 Hot Standby
12. Log in to Web Maintenance Console.

14. Click Data Transfer Start to resume synchronising the NSX servers.
15. Confirm that Data Transfer Status has changed from Suspended to Available (Sender).
Unsynchronised data
If the system goes off-line before data has finished synchronising, it is possible that some data will not be
synchronised. In the case, the data is automatically saved in an external memory device (NAS or USB).
The following are the possible cases where unsynchronised data will be saved:
• The NSX server (Active mode) goes off-line, or a LAN1 network fault occurs while the system is
switching the NSX server status.
• A data transfer error occurs due to a LAN3 connection fault.
If the NSX server determines that there is unsynchronised data, it is logged in the error log ("Data Transfer
Incomplete"). If this occurs, consult your dealer about recovering the data.

Section 7
Troubleshooting
This section provides information on the NSX server

and telephone troubleshooting.

7.1 Troubleshooting
7.1 Troubleshooting
7.1.1 Installation
PROBLEM PROBABLE CAUSE SOLUTION
You cannot make/receive • DSP card malfunction • Replace the corresponding card.
calls via an IP network.
• Mother board • Replace the mother board (be sure to turn
malfunction off the NSX server when replacing).
• Not enough activation • Purchase additional activation key codes.
keys Please consult a certified dealer for
details.
• Poor connection • Make sure that an 8-pin twisted pair cable
is used for connection.
• Make sure that none of the CAT 5/CAT 5e
cables in use are over 100 m in length.
• Make sure that a straight cable is used for
connection to a switching hub.
• Network malfunction • Make sure that all network devices in use
are switched on.
• Make sure that there is no unwanted
firewall in the IP network.
IP-PTs/SIP phones do not • DSP card malfunction • Replace the corresponding card.
operate.
• Mother board • Replace the mother board (be sure to turn
malfunction off the NSX server when replacing).
• Not enough activation • Purchase additional activation key codes.
keys Please consult a certified dealer for
details.
• IP-PT/SIP phone not • Register the corresponding IP-PT/SIP
registered phone.
• IP-PT/SIP phone • Replace the IP-PT/SIP phone.
malfunction
• Poor connection • Make sure that an 8-pin twisted pair cable
are switched on.
• Make sure that the IP-PT/SIP phone is not
blocked by the firewall or other network
devices.

7.1.1 Installation

Extensions (except IP- • Extension card • Replace the corresponding card.
PT/SIP phone) do not malfunction
operate.
• Poor connection • Take the extension and plug it into the
between the PBX and same extension port using a short
the extension telephone cord. If the extension works,
then the connection between the PBX and
the extension must be repaired.
• A telephone with an A- • Make sure that a 2-wire cord is used.
A1 relay is connected.
• Make sure that the A-A1 relay switch of
the telephone is in "OUT" or "OFF"
position.
• Extension malfunction • Take the extension and plug it into
another extension port that is working. If
the extension does not work, replace the
extension.
The NSX server does not • Restart the NSX server (refer to
operate properly. "7.1.3 Restarting the NSX server").
• Turn off the power switch, and then turn it
back on.
• Turn off the power switch, and then
unplug the NSX server. After 5 minutes,
plug the NSX server back in, and turn the
power switch back on.
Noise on external paging. • Induced noise on the • Use a shielded cable as the connection
wire between the NSX wire between the NSX server and
server and the amplifier. amplifier. A short shielded cable is
recommended.
Distorted external music. • Excessive input level • Decrease the output level of the external
from external music music source by using the volume control
source. on the music source.
The STATUS indicator on • A major system error • See the error log using Web Maintenance
the front of the cabinet occurs in the NSX Console (refer to "7.1.4 Troubleshooting
turns on red. server. by Error Log").
The LINK indicator of the • Mother board • Replace the mother board (be sure to turn
mother board does not turn malfunction off the NSX server when replacing).
on.
• Poor connection. • Make sure that an 8-pin twisted pair cable
are switched on.

7.1.2 Operation
7.1.2 Operation
Note
For devices connected to a PBX other than the NSX server, refer to the Troubleshooting for that NSX
server.
• Cannot set the IP • An unusable value is • Set an IP address within the valid range.
address, subnet mask being set. IP address of the IP-PT/NSX server:
address, and NSX "1.0.0.0" to "223.255.255.255" Subnet
server IP address to the mask address: "0–255.0–255.0–255.0–
IP-PT. 255" (except "0.0.0.0" and
"255.255.255.255")
• Cannot register the • The necessary network • When not using the DHCP Server feature
IP-PT. parameters are not set or an external DHCP server, set the IP
to the IP-PT. address, subnet mask address, and enter
the NSX server IP address. If necessary,
also enter the IP address of the default
gateway.
• When using the DHCP Server feature or
an external DHCP server, enter the NSX
server IP address.
• The IP-PT cannot • The wrong IP address, • Check each parameter and enter the
connect to the NSX subnet mask address, correct value.
server. NSX server IP address,
or default gateway
address was entered.
• The Ethernet cable is • Check the Ethernet cable connections.
not connected correctly.
• The DHCP server is not • Restart the external DHCP server.
active.
• Confirm whether the DHCP Server feature
is enabled.
• Disable DHCP and re-enter settings as
appropriate.
• Whenever you try to • The status of the port • Change the port status from Out of
make calls using a SIP that the SIP phone is Service to In Service using Web
phone, a busy tone is connected to is Out of Maintenance Console.
heard. Service.
• The IP-PT does not ring. • The ringer volume is off. • Turn on the ringer volume.
• Originating an outside • The corresponding • Programme the flexible button. Refer to
call, call transfer, or flexible button does not "2.21.1 Fixed Buttons" in the Feature
conference cannot be exist on the PT. Manual.
performed.

7.1.3 Restarting the NSX server

• The IP address of the - • Connect a PC to the MNT port of the NSX
NSX server for server directly and start the Web
networking has been Maintenance Console using the default IP
forgotten. address of the MNT port, and then confirm
the IP address assigned for the LAN port.
For details of connecting the PC directly to
the NSX server, refer to "5.2 PC
Connection".
For details of checking current IP address
of the mother board, refer to "28.1
Network Service—[1] IP Address/Ports—
Basic Settings—LAN Setting—IP
Address" in the PC Programming Manual.
7.1.3 Restarting the NSX server

If the NSX server does not operate properly, restart the NSX server using Web Maintenance Console.
Before restarting the NSX server, try the system feature again to confirm whether there definitely is a
problem or not.
Note
• When the System Mode Switch is set to "NORMAL", restarting the NSX server causes the following:
– Camp-on is cleared.
– Calls on hold are terminated.
– Calls on exclusive hold are terminated.
– Calls in progress are terminated.
– Call park is cleared.
Other data stored in memory, except the above, are not cleared.
• Be aware that restarting the NSX server with the System Mode Switch in the "SYSTEM INITIALIZE"
position clears all data stored in the NSX server. Do not perform this operation unless you intend to
delete all data from the NSX server.
• When the NSX server is set to obtain IP addressing information automatically, and the NSX server is
not able to obtain appropriate IP addressing information from an external DHCP server, the NSX
server starts up with its default IP addresses and the STATUS indicator on the front of the cabinet
turns red. For the default IP addresses, refer to "5.3 Starting Web Maintenance Console".
Operation
If the NSX server does not operate properly:
1. Slide the System Mode Switch to the "NORMAL" position.

7.1.4 Troubleshooting by Error Log
A
A. System Mode Switch
2. Start the Web Maintenance Console.

3. Log in using the Installer level account.
4. On the Home screen, click Maintenance → System Control → System Reset → System Reset.
5. Follow the prompts.
Restarting the NSX server will start.
To reset the system at a preset time:

1. Confirm that the System Mode Switch is in the "NORMAL" position.
2. Start the Web Maintenance Console.
3. Log in using the Installer level account.
4. On the Home screen, click Maintenance → System Control → System Reset → Timed Reset.
5. Set the Site, Reset Mode, and Reset Time for the system reset.
For details about the settings, refer to the PC Programming Manual.
6. Click Apply or OK to set the system reset.
The NSX server will restart at the specified time.

5.4 System Control—System Reset

When a major system error occurs in the NSX server, the STATUS indicator on the front of the cabinet turns
red, and the system logs the error information.
Error Log Display Format

Below is the display format of the error log. For information about how to view the error log using Web
Maintenance Console, refer to "7.3.1 Utility—Log—Error Log" in the PC Programming Manual.

Example: Web Maintenance Console

3 7
1 2 4 5 6
Example: Station Message Detail Recording (SMDR)

01/01/10 01:00AM MJ ALM #014 000 100000 FAN Alarm
01/01/10 01:29AM MN ALM #533 001 504001 Unit start up error
01/01/10 01:39AM MN ALM #091 000 100000 PT connection over
1 2 3 4 5 6
Description
Item Description
1 Date The date of the error detection.
2 Time The time of the error detection.
3 Level Minor (MN ALM) Displays minor errors, which affect only a certain part of
system operation.
Major (MJ ALM) Displays major errors, which affect operation of the whole
system, or result in system failure.
4 Error Code The 3-digit error code assigned by the NSX server. For
details about the error code, refer to item 7 in this table.
5 Sub Code SMDR:
The 10-digit sub code of the relevant hardware
(BBBWXYYZZZ).
Web Maintenance Console:
The 7-digit sub code of the relevant hardware (WXYYZZZ).
(The site number of the NSX server can be confirmed in the
Site column of the Error Log.)
For details about the contents of error sub codes, refer to

"7.3.1 Utility—Log—Error Log" in the PC Programming
Manual.
6 Error Message A description of the error.

Item Description
7 Log Information Clicking this button displays a list of errors and solutions in
PDF format, as shown below.
[Sample] List of Errors and Solutions

For each error code, the error message, probable cause, and solutions are explained.

Section 8
Appendix
This section provides information about NSX server

Region Suffix Codes and Areas, and System Prompt
Languages.

8.1 NSX server Region Suffix Codes and Areas

According to the following table, select the appropriate Suffix Code and Area for your NSX server to localise
NSX server settings to your location.
Depending on the system Activation key's suffix code, the area code you select in the Easy Setup Wizard is
changed.
For KX-NSX1000/KX-NSX2000BX
Suffix of System Area code for Easy
Area Region code
Activation Key setup
None BX Indonesia BX
Philippines BX
Singapore-Regional BX
Thailand BX
Vietnam BX
Mongolia BX
Bahrain BX
Cote d'Ivoire BX
Ghana BX
Iran BX
Iraq BX
Israel BX
Jordan BX
Kenya BX
Lebanon BX
Libyan Arab BX
Morocco BX
Oman BX
Pakistan BX
Qatar BX
Senegal BX
Syrian BX
Tunisia BX
Yemen BX
Chile BX
Kuwait BX
Mexico BX
Nigeria BX
Panama BX


Area Region code
Peru BX
Colombia BX
Uruguay BX
ZA South Africa SA
ML Malaysia ML
XE SG Singapore SN
HK Hong Kong HK
TW ― Taiwan TW
AG ― Argentine AG
BR ― Brazil BR
NE Albania ― CE
Algeria ― BX
Austria ― G
Belgium ― BL
Bosnia ― CE
Bulgaria ― CE
Croatia ― CE
Cyprus ― BX
Czech ― CE
Denmark ― DK
Egypt ― BX
Estonia ― CE
Finland ― FI
France ― FR
Germany ― G
Greece ― GR
Hungary ― CE
Ireland ― UK
Italy ― JT
Latvia ― CE
Lithuania ― CE
Luxembourg ― BL
Netherlands ― NL
Norway ― NO

8.2 System Prompt Languages

Area Region code
Poland ― CE
Portugal ― PT
Romania ― CE
Slovakia ― CE
Slovenia ― CE
Spain ― SP
Sweden ― SE
Switzerland ― SL
Turkey ― TR
UK United Kingdom UK
Yugoslavia (former) ― CE
Other ― CE
AL AL Australia AL
NZ New Zealand NZ
C ― Canada CE
UE ― UAE (AEC) BX
For KX-NSX1000/KX-NSX2000
Area Region code
NA ― United States M
For KX-NSX1000/KX-NSX2000RU
Area Region code
RU ― Russia RU
― Ukraine RU
― Kazakhstan RU
For KX-NSX1000/KX-NSX2000SX
Area Region code
SX ― India BX
8.2 System Prompt Languages

Note
• The following abbreviations are used in the language file names:
– UK: United Kingdom

8.3 Revision History
– US: United States

– LA: Latin America
– CA: Canada
– BR: Brazil
• No. 1 is set by default. For details, see "24.4 UM Configuration—[5-4] System Parameters—
Parameters—Prompt Setting—Prompt Setting" in the PC Programming Manual.
System prompt languages stored in the Storage Memory Card (installed by default)
Suffix of System
None/NE NE AL C
Activation Key
BL/CE/DK/FI/FR/G/
Region code BX/M/SA GR/JT/NL/NO/PT/S AL/NZ C
E/SL/SP/UK/TR
No. 1 (Primary) US-English UK-English UK-English CA-English
No. 2 LA-Spanish Spanish ― CA-French
No. 3 ― French ― ―
No. 4 ― German ― ―
No. 5 ― Dutch ― ―
No. 6 ― Italian ― ―
No. 7 ― Swedish ― ―
Suffix of System
None/XE/TW BR AG RU
Activation Key
Region code HK/ML/SN/TW BR AG RU
No. 1 (Primary) US-English BR-Portuguese LA-Spanish Russian
No. 2 LA-Spanish US-English US-English Ukrainian
No. 3 Mandarin ― ― US-English
No. 4 Taiwan Mandarin ― ― ―
No. 5 Cantonese ― ― ―
No. 6 ― ― ― ―
No. 7 ― ― ― ―
8.3 Revision History

8.3.1 PNMPR Software File Version 002.00xxx
Changed Contents
• Introduction
• System Components
• System Components for Expansion Gateways
• System Components for Legacy Gateways

• 1.3 Precautions
• 1.4 Data Security
• 2.1.2 System Connection Diagram
• 2.3.1 General Description
• 2.3.2 System Capacity
• 3.1.1 Type and Maximum Number of Activation Keys
• 3.1.3 Using CTI Applications
• 4.2.2 Names and Locations
• 4.3.1 Mother Board
• 4.3.3 DSP S Card (KX-NS0110), DSP M Card (KX-NS0111), DSP L Card (KX-NS0112)
• 4.5 Connection of Peripherals
• 5.5 Programming a Multi-connection Network
• 5.9.1 Registering IP Telephones
• 5.9.4 Installing IP Phones at a Remote Site with a Built-in Media Relay Gateway
• 5.9.5 Encryption Settings for Internal Calls
• 5.10 Configuration of Users
• 6.3.1 IP Telephony Service
• 6.4.1 Multi-connection Network
• 6.4.2 Multi-connection Networking Survivability
• 6.4.3 Information about Expansion Gateways
• 6.5 Port Security
• 6.7 Hot Standby

Changed Contents
• 4.3.1 Mother Board

Changed Contents
• 5.10 Configuration of Users-Synchronising User Information with an LDAP Directory
• 6.7 Hot Standby


Changed Contents
• System Components—System Components for KX-NSX1000/KX-NSX2000
• 2.2.1 Optional Equipment
• 8.1 NSX server Region Suffix Codes and Areas
• 8.2 System Prompt Languages

Changed Contents
– Equipment Compatibility for KX-NSX1000/KX-NSX2000
– System Components for KX-NSX1000/KX-NSX2000
– System Components for Legacy Gateways
– Equipment Compatibility for Legacy Gateways
– List of Abbreviations
• 1.1 For Your Safety
• 2.1.1 System Configurations
• 5.2 PC Connection
• 5.4.1 Easy Setup Wizard
• 5.4.1 Easy Setup Wizard—Maintenance Setting
• 5.6 Programming an H.323 QSIG Network
• 5.9.1 Registering IP Telephones
• 5.9.3 Installing SIP Phones at a Remote Site with an External SBC
• 6.2.3 Bandwidth Assessment
• 6.5 Port Security
• 6.7 Hot Standby

• 7.1.3 Error Messages

• 7.1.4 Troubleshooting by Error Log

Changed Contents
• Introduction
• 1.3 Precautions
• 6.3.5 Virtual SIP Trunk Card Specifications
• 6.7 Hot Standby

Note

Note

Note

For information of Compliance with EU relevant Regulatory Directives, Contact to Authorized
Representative:
Panasonic Testing Centre
Panasonic Marketing Europe GmbH
Winsbergring 15, 22525 Hamburg, Germany
For Future Reference
Please print, record, and retain the following information for future reference.
Note
The serial number of this product can be found on the label affixed to the unit. You should record the
model number and the serial number of this unit as a permanent record of your purchase to aid in
identification in the event of theft.
MODEL NO.
SERIAL NO.
DATE OF PURCHASE
NAME OF DEALER
DEALER'S ADDRESS
DEALER'S TEL. NO.
Panasonic Corporation
1006, Oaza Kadoma, Kadoma-shi, Osaka 571-8501, Japan
http://www.panasonic.com/
© Panasonic Corporation 2015
PNQX7657QA PM1115HH9019

Installation Manual 1549265793.2696

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Manual 1549265793.2696

Uploaded by

Copyright:

Available Formats

Installation Manual

Business Communication Server

Model No. KX-NSX1000

Thank you for purchasing this Panasonic product.

KX-NSX series: PNMPR Software File Version 004.00000 or later

Category Model No. Description

Category Model No. Description

DSP Card Slot KX-NS0110 VoIP DSP Card (S Type) (DSP S)

System Components for Expansion Gateways

Category Model No. Description Availability

Category Model No. Description

*1 For KX-NS300/KX-NS500/KX-NS700 only

System Components for Legacy Gateways

Category Model No. Description

*1 "xx" indicates the area suffix (e.g., BX).

Unsupported System Components for Legacy Gateways

Equipment Compatibility for KX-NSX1000/KX-NSX2000

Equipment Compatibility for Expansion Gateways

Equipment Compatibility for Legacy Gateways

• Portable Station (KX-TD7685, KX-TD7695, KX-TD7696)

The Structure of this Manual

About the Other Manuals

About the software version of your NSX server

6.5 Port Security ................................................................................................................ 194

This section provides important information intended to

1.1 For Your Safety

This notice means that misuse could result in death

This notice means that misuse could result in injury

For the Server

For the Server

• Do not install the system in the following locations:

For the Server

1.2 Important Safety Instructions

SAVE THESE INSTRUCTIONS

For users in Germany only

For users in Australia only

For Canada Users

1.4 Data Security

What is User Information?

This section provides general information on the NSX

2.1 Basic System Construction

IP Networking Expansion Gateway

To establish a Multi-connection network, the following activation keys are necessary:

Simplified Isolated Mode

Supported System Components for Expansion Gateways

H.323 QSIG network

Remote maintenance through Panasonic Cloud

Mobile Softphone by Panasonic

2.1.2 System Connection Diagram

(Expansion gateways) KX-NT series

KX-NS300/500/700 Legacy Gateway Softphone

USB Memory Device

Station Message LAN

V-SIPGW128 IP-PT IP Softphone PC CTI Server

Private IP Router V-SIPEXT128 Trunk Adaptor Trunk Adaptor

ITSP DCE Router

*1 ITSP: Internet Telephony Service Provider

2.2 Optional Equipment

2.3.2 System Capacity

Front View Inside View (The top cover is removed.)

Maximum Optional Service Cards

Cards Installed in Virtual Slots

Maximum Trunks and Devices

Type Multi- Multi-

LCOT 961 1921