SL2100 Networking Manual

Networking Manual
GVT-010798-301-00 NA
ISSUE 1.0
Copyright
NEC Corporation reserves the right to change the specifications, functions, or features at any time,
without notice.
NEC Corporation has prepared this document for use by its employees and customers. The
information contained herein is the property of NEC Corporation and shall not be reproduced without
prior written approval of NEC Corporation.
Dterm is a registered trademarks of NEC Corporation. Windows is a registered trademark of Microsoft

Corporation. AT&T is a registered trademark of AT&T Wireless Services, Inc. All other brand names
and product names referenced in this document are trademarks or registered trademarks of their
respective companies.
Copyright 2017
NEC Corporation
ISSUE 1.0 SL2100
TABLE OF CONTENTS
Chapter 1 Introduction
Section 1 GENERAL OVERVIEW...................................................................................... 1-1
Section 2 COMMON TERMS............................................................................................. 1-1
Chapter 2 General Information

Section 1 VOICE OVER IP................................................................................................ 2-1
Chapter 3 IP Networking
Section 1 INTRODUCTION................................................................................................ 3-1
Section 2 IP TRUNKS........................................................................................................ 3-1
Chapter 4 General IP Configuration

Section 2 NETWORK ADDRESSING OVERVIEW............................................................ 4-1
Section 3 CONFIGURATION EXAMPLES......................................................................... 4-2
Section 4 TESTING THE NEC SL2100 NETWORK CONNECTION................................. 4-4
Chapter 5 PROGRAMMING
Section 1 BEFORE YOU START PROGRAMMING.......................................................... 5-1
Section 2 HOW TO USE THIS MANUAL........................................................................... 5-1
Section 3 HOW TO ENTER PROGRAMMING MODE...................................................... 5-2
Section 4 HOW TO EXIT PROGRAMMING MODE........................................................... 5-2
Section 5 USING KEYS TO MOVE AROUND IN THE PROGRAMS................................ 5-3
Section 6 PROGRAMMING NAMES AND TEXT MESSAGES......................................... 5-4
Section 7 USING SOFTKEYS FOR PROGRAMMING...................................................... 5-5
Section 8 WHAT THE SOFTKEY DISPLAY PROMPTS MEAN......................................... 5-5
Section 9 PROGRAMMING YOUR SYSTEM.................................................................... 5-5
Program 10 : System Configuration Setup.................................................................. 5-6
10-12 : CPU Network Setup............................................................................... 5-6
10-13 : In-DHCP Server Setup........................................................................... 5-9
10-14 : Managed Network Setup..................................................................... 5-10
10-15 : Client Information Setup....................................................................... 5-11
10-16 : Option Information Setup..................................................................... 5-12
10-19 : VoIP DSP Resource Selection............................................................. 5-15
10-62 : NetBIOS Setting................................................................................... 5-16
10-63 : DHCP Client Setting............................................................................ 5-17
Program 15 : Extension, Basic Setup........................................................................ 5-18
15-05 : IP Telephone Terminal Basic Data Setup............................................. 5-18
Program 84 : Hardware Setup for VoIPDB................................................................ 5-22
84-09 : VLAN Setup......................................................................................... 5-22
84-10 : ToS Setup............................................................................................ 5-23
Program 90 : Maintenance Program.......................................................................... 5-24
90-23 : Deleting Registration of IP Telephones................................................ 5-24
90-34 : Firmware Information........................................................................... 5-25
Chapter 6 Network Design Considerations

Networking Manual i
SL2100 ISSUE 1.0
Section 2 QoS.................................................................................................................... 6-1

Section 3 INTERNET BASED CONNECTIONS (XDSL, CABLE, ETC.)........................... 6-4
Section 4 FIREWALLS AND NAT...................................................................................... 6-5
Section 5 CODEC AND BANDWIDTH............................................................................... 6-7
Section 6 QUALITY OF SERVICE (QoS) IMPLEMENTATION.......................................... 6-9
Section 7 PORT DESIGNATIONS................................................................................... 6-21
Chapter 7 SIP Trunking

Section 1 VoIP................................................................................................................... 7-1
Section 2 IP NETWORKING.............................................................................................. 7-1
Section 3 SIP TRUNKING................................................................................................. 7-1
Section 4 SIP TRUNK OVERVIEW.................................................................................... 7-3
Section 5 SUPPORTED SIP TRUNKING FUNCTIONS.................................................... 7-4
Section 6 SIP TRUNK PROGRAMMING........................................................................... 7-6
Section 7 SIP TRUNK E.164 SUPPORT......................................................................... 7-17
Section 8 SIP TRUNK E.164 CLIP ENHANCEMENT...................................................... 7-19
Section 9 SIP TRUNK KEEP ALIVE USING OPTION MESSAGE.................................. 7-23
Chapter 8 DHCP Client

Section 1 DHCP CLIENT................................................................................................... 8-1
Section 2 DHCP SERVER CONFIGURATION EXAMPLE................................................ 8-2
Chapter 9 IP Multiline Station (SIP)

Section 2 IP TO TDM CONVERSION................................................................................ 9-1
Section 3 PROVIDING POWER........................................................................................ 9-3
Section 4 PEER-TO-PEER................................................................................................ 9-3
Section 5 PROGRAMMING............................................................................................... 9-4
Section 6 CONFIGURATION EXAMPLES......................................................................... 9-4
Section 7 IP PHONE PROGRAMMING INTERFACE........................................................ 9-8
Section 8 DHCP SERVER CONFIGURATION.................................................................. 9-8
Section 9 CONFIGURING QUALITY OF SERVICE.......................................................... 9-8
Section 10 IP TELEPHONE REGISTRATION AND DELETION........................................ 9-9
Section 11 SYSTEM IP PHONES AND ANALOG TRUNKS............................................ 9-10
Section 12 FIRMWARE UPGRADE PROCEDURE......................................................... 9-10
Section 13 IP STATION (SIP MULTILINE TELEPHONE)................................................ 9-11
Chapter 10 IP Single Line Telephone

Section 1 INTRODUCTION.............................................................................................. 10-1
Section 2 PROGRAMMING............................................................................................. 10-2
Chapter 11 NAPT
Section 1 NAPT................................................................................................................ 11-1
Section 2 CONDITIONS................................................................................................... 11-3
Section 3 RESTRICTIONS............................................................................................... 11-3
Section 4 MINIMUM REQUIRED PROGRAMMING........................................................ 11-4
Chapter 12 All DSP Busy Indication

Section 2 SERVICE CONDITIONS.................................................................................. 12-1
ii Networking Manual
ISSUE 1.0 SL2100
Section 3 RELATED FEATURES..................................................................................... 12-2

Section 4 GUIDE TO FEATURE PROGRAMMING......................................................... 12-2
Chapter 13 SL Net
Section 2 System Capacity.............................................................................................. 13-1
Section 3 Network Requirements.................................................................................... 13-2
Section 4 QUALITY OF SERVICE SETTINGS (QOS)..................................................... 13-3
Section 5 IP PRECEDENCE............................................................................................ 13-3
Section 6 DIFFSERV....................................................................................................... 13-4
Section 7 GUIDE TO FEATURE PROGRAMMING......................................................... 13-8
Section 8 PROGRAMMING EXAMPLES....................................................................... 13-18
Section 9 LIST OF SUPPORTED FEATURES IN A NETWORKED SYSTEM.............. 13-22
Networking Manual iii

SL2100 ISSUE 1.0
LIST OF TABLES
Table 1-1 Common Terms and Associated Abbreviations................................................. 1-1
Table 2-1 VoIP Specifications............................................................................................ 2-1
Table 5-1 Keys for Entering Data (Digital (2W) Multiline Terminal, IP Multiline
Terminal)..................................................................................................... 5-3
Table 5-2 Keys for Entering Names................................................................................... 5-4
Table 5-3 Softkey Display Prompts.................................................................................... 5-5
Table 6-1 Protocol Structure for Layer 2 QoS.................................................................. 6-12
Table 6-2 Layer 3 QoS Example...................................................................................... 6-14
Table 6-3 Type of Service Field (IP Precedence - i Ref. REC 1349)............................... 6-15
Table 6-4 Diffserv Parameters.......................................................................................... 6-16
Table 6-5 IP Precedence and Diffserv Values Comparison............................................. 6-17
Table 6-6 Cisco Router Configuration Example............................................................... 6-21
Table 7-1 Delete + from Incoming SIP INVITE................................................................. 7-21
Table 7-2 Delete + and Country Code from Incoming SIP INVITE.................................. 7-22
Table 7-3 Delete + and Country Code from Incoming SIP INVITE.................................. 7-22
Table 9-1 IP Phone Programming Options User Menu ..................................................... 9-8
Table 9-2 8IPLD Supported Encryption............................................................................ 9-13
Table 9-3 Common IP Precedence/Diffserv Values and Hexadecimal Equivalent........... 9-24
Table 9-4 IP Phone Relocation........................................................................................ 9-45
Table 10-1 ※1................................................................................................................... 10-6
Table 12-1 Alarm Types................................................................................................... 12-1
Table 13-1 Diffserv Parameters........................................................................................ 13-4
iv Networking Manual
ISSUE 1.0 SL2100
LIST OF FIGURES
Figure 3-1 Example of SL2100 IP Network Configuration................................................. 3-2
Figure 4-1 Example Configuration 1 - Existing Network with Static IP Address................ 4-3
Figure 4-2 Example Configuration 1 - Adding the NEC SL2100 Chassis to the
Network....................................................................................................... 4-4
Figure 4-3 Testing the Network Connection....................................................................... 4-5
Figure 6-1 Layer 2 Diagram (802.1Q)................................................................................ 6-3
Figure 6-2 Virtual Private Network (VPN) Example........................................................... 6-7
Figure 6-3 Network Bottleneck Example.......................................................................... 6-10
Figure 6-4 Voice and Data Network Implementation........................................................ 6-11
Figure 6-5 Priority Queuing on Voice and Data Networks................................................ 6-11
Figure 6-6 Common Network with Cisco Router.............................................................. 6-20
Figure 7-1 Common IP Network using NEC SL2100 SIP Trunk........................................ 7-2
Figure 8-1 DHCP - Set Predefined Options....................................................................... 8-3
Figure 8-2 DHCP - Predefined Options and Values........................................................... 8-4
Figure 8-3 DHCP - Scope Options..................................................................................... 8-5
Figure 8-4 DHCP - Data Entry for 1st DHCP Server......................................................... 8-6
Figure 9-1 8IPLD Telephone.............................................................................................. 9-2
Figure 9-2 Typical Network IP Connection......................................................................... 9-3
Figure 9-3 Example Configuration 1 - Static IP Addressing, One LAN.............................. 9-5
Figure 9-4 Example Configuration 2 - Dynamic IP Addressing, One LAN......................... 9-6
Figure 9-5 Example Configuration 3Static IP Addressing, Routed WAN........................... 9-7
Figure 9-6 8IPLD Encryption............................................................................................ 9-14
Figure 9-7 Log In to IP Phone.......................................................................................... 9-16
Figure 9-8 LAN Port Settings Window............................................................................. 9-17
Figure 9-9 VLAN Mode.................................................................................................... 9-17
Figure 9-10 VLAN ID........................................................................................................ 9-17
Figure 9-11 VLAN Priority................................................................................................ 9-18
Figure 9-12 PC Port Settings Window............................................................................. 9-18
Figure 9-13 Port VLAN Mode........................................................................................... 9-19
Figure 9-14 Port VLAN ID................................................................................................ 9-19
Figure 9-15 Port VLAN Priority........................................................................................ 9-19
Figure 9-16 Save Network Settings................................................................................. 9-20
Figure 9-17 Save Confirmation Window.......................................................................... 9-20
Figure 9-18 84-10: ToS Setup.......................................................................................... 9-23
Figure 9-19 SIP MLT Basic Setup.................................................................................... 9-24
Figure 9-20 Type of Service Window............................................................................... 9-25
Figure 9-21 RTP - Voice Packets..................................................................................... 9-26
Figure 9-22 SIP - Signaling Packets................................................................................ 9-26
Figure 9-23 NEC SL2100 Network Example No. 1.......................................................... 9-29
Figure 9-24 NEC SL2100 Network Example No. 2.......................................................... 9-30
Figure 9-25 IP System Operation Setup.......................................................................... 9-30
Figure 9-26 System Data 10-12: CPU Network Setup..................................................... 9-37
Figure 9-27 System Data 84-26: VoIPDB Basic Setup (DSP)......................................... 9-38
Figure 9-28 System Data 11-02: Extension Numbering................................................... 9-39
Figure 9-29 IP Phone List................................................................................................ 9-40
Figure 9-30 IP Phone List................................................................................................ 9-41
Figure 9-31 8IPLD Server Information Setup................................................................... 9-41
Figure 9-32 Automatic Registration Basic Setup............................................................. 9-42
Figure 9-33 Automatic Registration Personal ID Index.................................................... 9-42
Figure 9-34 Automatic Registration User Name and Password Assignment................... 9-42
Figure 9-35 8IPLD Server Information Setup................................................................... 9-43
Networking Manual v
SL2100 ISSUE 1.0
Figure 11-1 NAPT Configuration Example....................................................................... 11-1

Figure 13-1 IP Precedence.............................................................................................. 13-4
Figure 13-2 Setup Example............................................................................................. 13-5
Figure 13-3 Programming Example............................................................................... 13-18
vi Networking Manual
Introduction
SECTION 1 GENERAL OVERVIEW 1
This manual provides information for networking for the NEC SL2100 system.
Introduction
SECTION 2 COMMON TERMS
The following terms and the associated abbreviations or alternate nomenclature may be found
throughout this document.
Table 1-1 Common Terms and Associated Abbreviations
Term Abbreviation Description

IP7XX-CPU-C1 CPU-C1 CPU-C1 with main software
SL2100 CPU
CPU
IP7WW- VOIPDB- C1 VOIPDB Mount this card onto the CPU card (VoIPDB slot) at Main Chassis.
VOIP Daughter Board Max. 128 channels by license control.
IP7WW-3COIDB-C1 3COIDB The 3COIDB provides three analog trunks and is mounted on the
082U, 008U or 000U card.
IP7WW-082U-B1 082U card 8-digital station + 2 Analog station interface card
IP7WW- 12TXH- B1 TEL 2-wire Digital Multiline Tele- 12TXH-B1 TEL 12-button digital telephone
IP7WW- 24TXH- B1 TEL phone 24TXH-B1 TEL 24-button digital telephone
IP7WW-8IPLD-C1 TEL IP Multiline Telephone 8IPLD-C1 TEL 8-button IP DESI-Less telephone
Networking Manual 1-1

SL2100 ISSUE 1.0
MEMO
1-2 Introduction
General Information
SECTION 1 VOICE OVER IP 2
Voice over IP (VoIP) is a technology that converts speech into data packets and transmits these
packets over TCP/IP networks. The technology also facilitates compression and silence suppression
to reduce network bandwidth demands.
General Information
As most organizations already have existing data networks in place, considerable cost savings can be
achieved by utilizing spare bandwidth on these networks for voice traffic.
NEC SL2100 supports the use of IP Phones. These telephones provide the same functionality as a
multiline telephone but use the data network rather then the traditional telecoms infrastructure. This
can reduce costs and allow the use of NEC SL2100 telephones in locations that would not normally be
supported by multiline telephones.
Table 2-1 Table 2-1 VoIP Specifications on page 2-1 lists the specifications for various aspects of
NEC SL2100 VoIP system.
Table 2-1 VoIP Specifications
Category Feature Notes

IP Address DHCP Server *1 CPU-C1/VoIPDB
DHCP Client *1 VoIPDB/IP Phone
QoS 802.1p/1q CPU-C1
L3 QoS (ToS) Diffserv/IP Precedence
Maintenance HTTP Server CPU-C1/VoIPDB
VLAN Tag and port-based VLAN
VoCoder G.711 µ-law/A-law
G.729a
G.722
G.726
Jitter Buffer Size Set by system programming
RTP Length Set by system programming
Echo Canceller Tail Size Set by system programming
Level Adjustment Set by system programming
IP Phone SIP Phone SIP Phone
SIP Trunk SIP Trunk Maximum 128 Trunks
*1. DHCP Server and DHCP Client cannot be used at the same time. When the DHCP Server is enabled the
DHCP Client function cannot be activated.
When the VoIPDB is installed, the CPU-C1 is no longer active, all IP connections go through the VoIPDB.

SL2100 ISSUE 1.0
MEMO
2-2 General Information

IP Networking
SECTION 1 INTRODUCTION 3
IP Networking uses VoIP technology to connect two or more telephone systems together. This allows
calls to be made between sites without using the public telephone network. This saves considerable
money, and makes communication between sites much easier.
IP Networking
The voice quality of VoIP is dependent on variables such as available bandwidth, network latency and
Quality of Service (QoS) initiatives, all of which are controlled by the network and Internet Service
Providers. Because these variables are not in NEC control, it cannot guarantee the performance of the
user’s IP-based remote voice solution. Therefore, NEC recommends connecting VoIP equipment through a
local area network using a Private IP address.
SECTION 2 IP TRUNKS
The SIP Trunks method of networking allows connection to SIP devices. This could be a PBX system
or a third-party product. When using SIP, the feature set is limited and the advanced networking
features cannot be used.
Refer to SIP Trunking on page 7-1 for a a detailed description of SIP trunking and for set up
instructions.
To set up IP trunks:
1. Connect the system to the Data Network. (Refer to General IP Configuration on page 4-1 for
detailed instructions.)
2. Configure the IP trunks.
3. Configure the SIP information.
4. Configure the F-Route.
2.1 Configure IP Trunks

When installing a VoIP daughter board in the NEC SL2100 system, external line ports are allotted in
accordance with the number of Licensed ports for the particular IP Application.
The NEC SL2100 system now has the required information about the remote destinations and the SIP
configuration is complete. The only remaining task is to configure F-Route to route calls to remote
destinations via the IP trunks. F-Route configuration is discussed in detail in the Automatic Route
Selection (ARS) feature in the NEC SL2100 Programming Manual.

SL2100 ISSUE 1.0
Office A Office B
IP Address: IP Address:
172.16.0.10 192.168.0.20
Ext 1000 Ext 1100
Network
Office C Office D
IP Address: IP Address:
10.6.0.10 10.0.0.100
Ext 1200 Ext 1300
Figure 3-1 Example of SL2100 IP Network Configuration
3-2 IP Networking
General IP Configuration
The NEC SL2100 system uses IP for various applications, including:
• System Programming
• Voice Over IP
General IP Configuration
This section describes the procedure for connecting the NEC SL2100 system to an existing data
network and configuring TCP/IP. This is the first step in implementing VoIP and other IP applications.
SECTION 2 NETWORK ADDRESSING OVERVIEW

Before connecting the system to a data network, it is necessary to obtain the relevant IP Addressing
information. This information is supplied by the IT Manager or Network Administrator at the customer
site.
2.1 IP Address
All equipment/devices used in the LAN setup must have an IP address assignment. An IP address
assigns a unique address for each device. There are two types of IP addresses: Private and Global. A
Private IP address is not accessible through the Internet; a Global IP address can be accessed
through the Internet.
In most cases, a Private address is used, as LAN devices are not usually directly connected to the
Internet. Private addresses are usually taken from the following ranges:
• Class A 10.0.0.0 ~ 10.255.255.255
• Class B 172.16.0.0. ~ 172.31.255.255
• Class C 192.168.0.0 ~ 192.168.255.255
A Public address is normally only used when a device is directly connected to the Internet. This is
unlikely in the case of the equipment. If Public addressing is used, the numbers are normally allocated
by an ISP.
2.2 Subnet Mask

As the IP address includes information to identify both the network and the final destination, the
Subnet Mask sets apart the network and destination information. The default subnet masks are:
• Class A 255.0.0.0
• Class B 255.255.0.0
• Class C 255.255.255.0
The Subnet Mask is made up of four groups of numbers. When a group contains the number 255, the
router ignores or masks that group of numbers in the IP address as it is defining the network location
of the final destination.

SL2100 ISSUE 1.0
For example, if the IP address is: 172.16.0.10 and the Subnet Mask used is Class B (255.255.0.0), the
first two groups of numbers (172.16) are ignored once they reach the proper network location. The
next two groups (0.10) are the final destination within the LAN to which the connection is to be made.
For sub-netted networks, the subnet mask may be different from the default subnet masks listed above.
2.3 DHCP
Dynamic Host Configuration Protocol (DHCP) assigns a dynamic IP address. Network control may be
easier with DHCP as there is no need to assign and program individual IP addresses for the LAN
equipment. To use a dynamic IP address, a DHCP server must be provided. The SL2100 can be
configured to be the DHCP server for the customers network. Before the DHCP server in the SL2100
can be enabled, the DHCP client function must first be disabled.
When equipment, which is connected to the LAN (the DHCP client), is requesting an IP address, it
searches the DHCP server.
When the request for an address is recognized, the DHCP server assigns an IP address, Subnet
mask, and the IP address of the router, based on NEC SL2100 system programming.
SECTION 3 CONFIGURATION EXAMPLES

The following configuration examples illustrate a typical network configuration for an existing network
that uses a static address and a typical configuration for a new network that uses a dynamic address.
3.1 Example Configuration 1 - Existing Network with Static Addressing

Figure 4-1 Example Configuration 1 - Existing Network with Static IP Address on page 4-3 shows a
typical network configuration that uses Static IP Addressing.
Each client device has a manually assigned IP address in the 192.168.1.0/24 network (i.e.,
192.168.1.1 to 192.168.1.254 with a subnet mask of 255.255.255.0). They also have a default
gateway address configured (192.168.1.254) this allows the device to route packets to destinations
that exist outside of their own LAN.
4-2 General IP Configuration

ISSUE 1.0 SL2100
WAN,
Internet, etc.
Router
(Default Gateway)
192.168.1.254
Switch
192.168.10.11 192.168.1.10
192.168.1.50
192.168.1.32
Figure 4-1 Example Configuration 1 - Existing Network with Static IP Address
Assume that a NEC SL2100 is added to the existing data network. The Network Administrator (or IT
Manager) should provide the following:
• IP Address (for the CPU-C1)
• IP Addresses (for the VoIP daughter board)
• Subnet Mask
• Default Gateway
• A spare switch
First, program the NEC SL2100:

• 192.168.1.200
• 255.255.255.0
• PRG10-12-03: 192.168.1.254
A system reset is required for the IP Address changes to take effect.
Now connect the CPU-C1/VoIPDB Ethernet Port to the switch port, using a standard Cat-5 patch
cable. The NEC SL2100 is now configured on the network and should be accessible by other devices
on the network. Refer to Figure 4-2 Example Configuration 1 - Adding the NEC SL2100 Chassis to the
Network on page 4-4.

SL2100 ISSUE 1.0
WAN,
Internet, etc.
NEC SL2100 Chassis

with CPU Installed
Router
(Default Gateway) Chassis
192. 168. 1. 254
Switch
192. 168. 1. 200
192. 168. 1. 50 192. 168. 1. 11 192. 168. 1. 10
192. 168. 1. 32
Figure 4-2 Example Configuration 1 - Adding the NEC SL2100 Chassis to the Network
SECTION 4 TESTING THE NEC SL2100 NETWORK CONNECTION

To test the NEC SL2100 network connection, it is possible to use the ICMP (Internet Control Message
Protocol) Ping command. This basically sends a small amount of data from one device to another and
then waits for a reply. This test confirms that the IP addressing and physical connection are good. To
perform this test, from a Windows PC:
1. Click Start.
2. Click Run... .
3. In the Open dialogue box, enter command.
4. Click OK. A Command prompt window opens.
5. Type ping 192.168.1.200.
Figure 4-3 Testing the Network Connection on page 4-5 shows that the NEC SL2100 system has
replied to the Ping request – this indicates that the NEC SL2100 system is correctly connected to the
network.

ISSUE 1.0 SL2100
Figure 4-3 Testing the Network Connection

SL2100 ISSUE 1.0
MEMO

PROGRAMMING
The remainder of this chapter provides instructions for programming individual program blocks. 5
SECTION 1 BEFORE YOU START PROGRAMMING
PROGRAMMING
This chapter provides you with detailed information about the NEC SL2100 program blocks that may
be required to connect the NEC SL2100 to a data network and to configure the VoIP function. The
configuration and programming examples, found in the earlier chapters, can be a useful reference
when programming the data.
SECTION 2 HOW TO USE THIS MANUAL

This section lists each program in numerical order. For example, Program 10-01 is at the beginning of
the section and Program 92-01 is at the end. The information on each program is subdivided into the
following headings :
Description describes what the program options control. The Default Settings for each program are
also included. When you first install the system, it uses the Default Setting for all programs. Along with
the Description are the Conditions which describe any limits or special considerations that may apply
to the program.
The program access level is just above the Description heading. You can only use the program if your
access level meets or exceeds the level the program requires. Refer to How to Enter Programming
Mode on page 5-2 for a list of the system access levels and passwords.
Feature Cross Reference provides you with a table of all the features affected by the program. You
will want to keep the referenced features in mind when you change a program. Customizing a feature
may have an effect on another feature that you did not intend.
Telephone Programming Instructions shows how to enter the program data into system memory.
For example :
1. Enter the programming mode.
2. 15-07-01
15-07-01 TEL
KY01 = *01
- +
Digital (2W) Multiline Terminal
15-07-01 TEL
KY01 = *01
- +
IP Multiline Terminal

SL2100 ISSUE 1.0
tells you to enter the programming mode, dial 150701 from the telephone dial pad. After you do, you
will see the message “15-07-01 TEL” on the first line of the telephone display. This indicates the
program number (15-07), item number (01), and that the options are being set for the extension. The
second row of the display “KY01 = *01” indicates that Key 01 is being programmed with the entry of
*01. The third row allows you to move the cursor to the left or right, depending on which arrow is
pressed. To learn how to enter the programming mode, refer to How to Enter Programming Mode on
page 5-2.
SECTION 3 HOW TO ENTER PROGRAMMING MODE

To enter programming mode :
1. Go to any working display telephone.

In a newly installed system, use extension (port 1).
2. Do not lift the handset.

3. Press Speaker.
4. # * # *.
5. Dial the system password + Hold.

Refer to the following table for the default system passwords. To change the passwords, use
90-02 : Programming Password Setup.
Program Mode
Base Service OP1 OP2
Digital (2W) Multiline Terminal, IP Multiline Terminal
Password User Name Level Programs at this Level

12345678 tech 2 (IN) Installation (IN) :
IN, SA and SB levels defined by 90-26 are available.
0000 ADMIN1 3 (SA) System Administrator - Level 1 (SA) :
10-01, 10-02, 10-12, 10-13, 10-14, 10-15, 10-16, 10-23, 10-27, 10-28,
10-29, 10-45, 10-67, 10-73, 12-02, 12-03, 12-04, 12-08, 15-01, 15-07,
15-09, 15-10, 15-11, 20-16, 20-34, 20-57, 20-63, 20-64, 20-66, 20-70,
21-07, 21-14, 22-04, 22-11, 22-17, 25-08, 30-03, 30-04, 32-02, 41-02,
41-03, 41-04, 41-05, 41-06, 41-07, 41-08, 41-09, 41-11, 41-12, 41-13,
41-14, 41-16, 41-17, 41-18, 41-19, 41-20, 45-02, 84-16, 84-22, 90-03,
90-04, 90-06, 90-07, 90-16, 90-19, 90-57, 90-58, 90-59, 90-65, 93-01,
93-02, 93-03, 93-04, 93-05, 93-06
9999 ADMIN2 4 (SB) System Administrator - Level 2 (SB) :
13-04, 13-05, 13-06, 13-11, 15-14, 21-20
SECTION 4 HOW TO EXIT PROGRAMMING MODE

To exit the programming mode :
When you are done programming, you must be out of a program option to exit (pressing the Mute key
will exit the program option).
5-2 PROGRAMMING
ISSUE 1.0 SL2100
1. Press Mute key to exit the program options, if needed.
Program Mode
Digital (2W) Multiline Terminal, IP Multiline Terminal
2. Press Speaker. If changes were to the system programming, "Saving System Data" is displayed.
3. The display shows "Complete Data Save" when completed and exits the telephone to an idle
mode.
To save a customer’s database, a blank SD Card is required. Insert the SD Card into the CPU and, using
Program 90-03, save the software to the SD Card. (Program 90-04 is used to reload the customer data if
necessary.) Note that a SD Card can only hold one customer database. Each database to be saved requires
a separate drive.
SD slot (J12)
CPU board
Blank SD Card
SECTION 5 USING KEYS TO MOVE AROUND IN THE PROGRAMS

Once you enter the programming mode, use the keys in the following chart to enter data, edit data and
move around in the menus.
Table 5-1 Keys for Entering Data (Digital (2W) Multiline Terminal, IP Multiline Terminal)
When you want to ... Telephone Programming

Enter Data into program 0 ~ 9, *, # Line Key (1 ~ 6)
Next Index Cursor Key (Up)
Prior Index Cursor Key (Down)
Select Data Line Key (1 ~ 6)
All Clear Flash
Apply Hold
Enter
Go Back to Prior Screen Mute
Clear / Back
Move Cursor Jump Up/Down DND
Delete single character Clear / Back

SL2100 ISSUE 1.0
When you want to ... Telephone Programming

Next Page Help
Toggle between Number/Character
While in a Entering Number
Prior Page Transfer
Quit the programming Speaker
Exit
Move Cursor to Left Cursor Key (Left)
Soft Key1
Change Program Number Soft Key2
Change Index Number
Change Program Number Soft Key3
Change Index Number
Move Cursor to Right Cursor Key (Right)
Soft Key4
SECTION 6 PROGRAMMING NAMES AND TEXT MESSAGES

Several programs (e.g., Program 20-16 : Selectable Display Messages) require you to enter text. Use
the following chart when entering and editing text. When using the keypad digits, press the key once
for the first character, twice for the second character, etc. For example, to enter a C, press the key 2
three times. Press the key six times to display the lower case letter. The name can be up to 12 digits
long.
Table 5-2 Keys for Entering Names
Use this keypad digit ... When you want to ...

1 Enter characters : 1 @ [ ¥ ] ^ _ ` { | } ÁÀÂÃÅÆÇÉÊìó0
2 Enter characters : A-C, a-c, 2.
3 Enter characters : D-F, d-f, 3.
4 Enter characters : G-I, g-i, 4.
5 Enter characters : J-L, j-l, 5.
6 Enter characters : M-O, m-o, 6.
7 Enter characters : P-S, p-s, 7.
8 Enter characters : T-V, t-v, 8.
9 Enter characters : W-Z, w-z, 9.
0 Enter characters : 0 ! “ # $ % & ’ ( ) ô õ ú å ä æ ö ü α ε θ В
* Enter characters : * + , - . / : ; < = > ? π Σ σ Ω ∞ ¢ £

# # = Accepts an entry (only required if two letters on the same key are needed - ex : TOM).
Pressing # again = Space. (In system programming mode, use the right arrow Softkey in-
stead to accept and/or add a space.)
Clear/Back or DND (2W Digital/IP Clear the character entry one character at a time.
Multiline Terminal)
Flash Clear all the entries from the point of the flashing cursor and to the right.
5-4 PROGRAMMING
ISSUE 1.0 SL2100
SECTION 7 USING SOFTKEYS FOR PROGRAMMING

(This Feature is available for Digital (2W) Multiline Terminal and IP Multiline Terminal Only.)
Each Display telephone with Softkeys provides interactive Softkeys for intuitive feature access. The
options for these keys will automatically change depending on where you are in the system
programming. Simply press the Softkey located below the option you wish and the display will change
accordingly.
_
Program Mode
Pressing the Cursor key Up or Down will scroll between the menus.
_
Program Mode
Hard Mtnance
SECTION 8 WHAT THE SOFTKEY DISPLAY PROMPTS MEAN

(This Feature is available for Digital (2W) Multiline Terminal and IP Multiline Terminal Only.)
When using a display telephone in programming mode, various Softkey options are displayed. These
keys will allow you to easily select, scan, or move through the programs.
Table 5-3 Softkey Display Prompts
Softkey Display Prompts

If you press this Soft- The system will ...
key ...
back Go back one step in the program display.
You can press Cursor Key (UP) or Cursor Key (Down) to scroll forward or backward through a
list of programs.
Scroll down through the available programs.
Scroll up through the available programs.
select Select the currently displayed program.

Move the cursor to the left.
Move the cursor to the right.
-1 Move back through the available program options.
+1 Move forward through the available program options.
SECTION 9 PROGRAMMING YOUR SYSTEM

This sections describes the programs used to connect the NEC SL2100 to a data network and to
configure the VoIP functions.

SL2100 ISSUE 1.0
Program 10 : System Configuration Setup

10-12 : CPU Network Setup
Level:
SA
Description
Program Use Program 10-12 : CPU Network Setup to setup the IP Address, Subnet-Mask, and Default
Gateway addresses.
10
Caution!
If any IP Address or NIC settings are changed, the system must be reset for the changes to take affect.
Input Data
Item Item Input Data Description Default

No.
01 IP Address 0.0.0.0 ~ Set for CPU. 192.168.0.10
126.255.255.254
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
02 Subnet Mask 128.0.0.0 | 192.0.0.0 | The setting of Subnet Mask is invalid when 255.255.255.0
224.0.0.0 | 240.0.0.0 | all Host Addresses are 0.
248.0.0.0 | 252.0.0.0 | If the network section is:
254.0.0.0 | 255.0.0.0 | 0,
255.128.0.0 | 127,
255.192.0.0 | 128.0,
255.224.0.0 | 191.255,
255.240.0.0 | 192.0.0,
255.248.0.0 | 223.255.255
255.252.0.0 | The setting of Subnet Mask is invalid.
255.254.0.0 |
255.255.0.0 |
255.255.128.0 |
255.255.192.0 |
255.255.224.0 |
255.255.240.0 |
255.255.248.0 |
255.255.252.0 |
255.255.254.0 |
255.255.255.0 |
255.255.255.128 |
255.255.255.192 |
255.255.255.224 |
255.255.255.240 |
255.255.255.248 |
255.255.255.252 |
255.255.255.254 |
255.255.255.255 |
03 Default Gateway 0.0.0.0 ~ Assign the default gateway IP address. 0.0.0.0
126.255.255.254
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
5-6 Program 10 : System Configuration Setup

ISSUE 1.0 SL2100

No.
05 NIC Interface 0 = Auto Detect NIC Auto Negotiate 0
1 = 100Mbps, Full Du- (CPU)
plex
2 = Reserved When this programming was changed,
3 = Reserved the LAN cable must be unplugged and
4 = Reserved then reconnected.
5 = Reserved
07 NAPT Router IP Ad- 0.0.0.0 ~ Set the IP address on the WAN side of 0.0.0.0
dress 126.255.255.254 router.
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254 Program
08 ICMP Redirect 0 = Enable When receiving ICMP redirect message, 0
1 = Disable this determines if the IP Routing Table up-
10
dates automatically or not.
09 VoIP IP Address 0.0.0.0 ~ Assign the IP Address for the VoIPDB. 172.16.0.10
126.255.255.254
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
10 VoIP Subnet Mask 128.0.0.0 | 192.0.0.0 | Assign the subnet mask for the VoIPDB. 255.255.0.0
224.0.0.0 | 240.0.0.0 |
248.0.0.0 | 252.0.0.0 |
254.0.0.0 | 255.0.0.0 |
255.128.0.0 |
255.192.0.0 |
255.224.0.0 |
255.240.0.0 |
255.248.0.0 |
255.252.0.0 |
255.254.0.0 |
255.255.0.0 |
255.255.128.0 |
255.255.192.0 |
255.255.224.0 |
255.255.240.0 |
255.255.248.0 |
255.255.252.0 |
255.255.254.0 |
255.255.255.0 |
255.255.255.128 |
255.255.255.192 |
255.255.255.224 |
255.255.255.240 |
255.255.255.248 |
255.255.255.252 |
255.255.255.254 |
255.255.255.255 |
11 NIC Setup 0 = Auto Detect Set for VoIPDB. 0
1 = 100 Mbps, Full Du-
plex
2 = Not Used
3 = Not Used
4 = Not Used
5 = 1 Gbps, Full Duplex
13 DNS Primary Address 0.0.0.0 ~ In the future, use this system data when 0.0.0.0
126.255.255.254 add a function with DNS.
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254

SL2100 ISSUE 1.0

No.
14 DNS Secondary Ad- 0.0.0.0 ~ In the future, use this system data when 0.0.0.0
dress 126.255.255.254 add a function with DNS.
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
15 DNS Port 1 ~ 65535 In the future, use this system data when 53
add a function with DNS.
17 VoIP NIC Port Setting 0 = MDI 0
1 = MDI-X
18 CPU MTU 1000 ~ 1500 The MTU value of CPU NIC. 1450
Program
19 VoIP MTU 1000 ~ 1500 The MTU value of VoIP NIC. 1450
20 SSLv3 Setting 0 = Disable Set whether to use the SSLv3 in SMTP. 0
10
1 = Enable 0 (Disable) is encrypted with TLSv1.
This data requires a reset to apply
changed data to the system.
Conditions
• The system must be reset for these changes to take affect.
Feature Cross Reference

None

ISSUE 1.0 SL2100

10-13 : In-DHCP Server Setup
Level:
SA
Description
Use Program 10-13 : In-DHCP Server Setup to setup the DHCP Server built into the CPU. Program
Input Data
Item
No.
Item Input Data Description Default
10
01 DHCP Server Mode 0 = Disable Enable or disable the use of the built-in 0
1 = Enable DHCP Server. This program cannot be
enabled if PRG10-63-01 is enabled.
02 Lease Time Days 0 ~ 255 Lease Time of the IP address to a cli- 0 day
ent.
Hour 0 ~ 23 0 hour
Pressing the Hold Key increments to
Minutes 0 ~ 59 the next setting data. 30 minutes
05 Last DHCP Data 0 = Disable If 10–13–01 is enabled, this setting de- 1

1 = Enable termines if DHCP resource is enabled
or disabled.
Conditions
None

None

SL2100 ISSUE 1.0

10-14 : Managed Network Setup
Level:
SA
Description
Program Use Program 10-14 : Managed Network Setup to set up the range of the IP address which the
DHCP Server leases to a client.
10 Input Data
Item Item Input Data Description Default Related Pro-

No. gram
01 The Range of the IP Minimum : When Maximum has 172.16.0.100 10-13-04
address to Lease. 0.0.0.0 ~ 126.255.255.254 not been entered, the
128.0.0.1 ~ 191.255.255.254 maximum value equals
192.0.0.1 ~ 223.255.255.254 the minimum value.
Maximum : 172.16.5.254
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
Conditions
None

None

ISSUE 1.0 SL2100

10-15 : Client Information Setup
Level:
SA
Description
Use Program 10-15 : Client Information Setup to set up the client information when the DHCP Program
server needs to assign a fixed IP address to clients.
Input Data
Client Number 1 ~ 128

10
Item No. Item Input Data Description Default
01 MAC Address MAC : 00-00-00-00-00-00
00-00-00-00-00-00 ~
FF-FF-FF-FF-FF-FF
IP Address 1.0.0.0 ~ The IP address should be 0.0.0.0
126.255.255.254 assigned out of the scope
128.0.0.1 ~ range set up in Program
191.255255.254 10-14.
192.0.0.1 ~
223.255.255.254
Conditions
None

None

SL2100 ISSUE 1.0

10-16 : Option Information Setup
Level:
SA
Description
Program Use Program 10-16 : Option Information Setup to set up the option given from the DHCP server to
each client.
The items highlighted in gray are read only and cannot be changed.
10 Input Data

No.
01 Router Code number 0 ~ 255 Set the Router IP ad- 3 (Fixed)
dress.
IP address 0.0.0.0
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
02 DNS Server Code number 0 ~ 255 Set IP address of DNS 6 (Fixed)
Server.
IP address 0.0.0.0
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
03 TFTP Server Name Code number 0 ~ 255 Set the name for the 66 (Fixed)
TFTP Server.
Maximum 64 character strings No Setting
05 MGC IP Address Code number 0 ~ 255 129 (Fixed)
IP address 172.16.0.10
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
06 Client Host Name Code number 0 ~ 255 Set the Client Host 12 (Fixed)
Name.
07 DNS Domain Name Code number 0 ~ 255 Set the DNS Domain 15 (Fixed)
Name.
08 Download Protocol Code number 0 ~ 255 Set Download Protocol 43 (Fixed)
used for AutoConfig (for
Sub code number DR700 Series). 163 (Fixed)
1 = FTP 1
2 = HTTP
09 Encryption Information Code number 0 ~ 255 Set an Encryption Infor- 43 (Fixed)
mation used for Auto-
Sub code number Config (for DR700 ser- 164 (Fixed)
Fixed 128 character strings ies). No Setting

ISSUE 1.0 SL2100

No.
10 FTP Server Address Code number 0 ~ 255 Set a FTP Server Ad- 43 (Fixed)
dress used for AutoCon-
Sub code number fig. 141
IP address 0.0.0.0
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
11 Config File Name Code number 0 ~ 255 Set a File Name used for 43 (Fixed)
AutoConfig.
Sub code number 151
12 Vender Class ID Code number 0 ~ 255 60 (Fixed) Program
Maximum 256 character strings NEC DT700
10
13 SNMP Server IP Address Code number 0 ~ 255 69 (Fixed)
IP address 0.0.0.0
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
14 POP3 Server IP Address Code number 0 ~ 255 70 (Fixed)
IP address 0.0.0.0
0.0.0.0 ~ 126.255.255.254
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
16 SIP Server (IP Address) Code number 0 ~ 255 120 (Fixed)
IP address
0.0.0.0 ~ 126.255.255.254
172.16.0.10
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
17 SIP Server (Domain Name) Code number 0 ~ 255 If there is setting in 120 (Fixed)
10-16-16 this setting will
Maximum 20 character strings be ignored No Setting
18 FTP Server IP Address Code number 0 ~ 255 141 (Fixed)

IP address
0.0.0.0 ~ 126.255.255.254
0.0.0.0
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
19 Config File Name Code number 0 ~ 255 151 (Fixed)
20 LDS Server 1 IP Address Code number 0 ~ 255 162 (Fixed)
IP address
0.0.0.0 ~ 126.255.255.254
0.0.0.0
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
IP address
0.0.0.0 ~ 126.255.255.254
0.0.0.0
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
IP address
0.0.0.0 ~ 126.255.255.254
0.0.0.0
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254

SL2100 ISSUE 1.0

No.
IP address
0.0.0.0 ~ 126.255.255.254
0.0.0.0
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
24 Next Server IP Address IP address
0.0.0.0 ~ 126.255.255.254
0.0.0.0
128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
27 SIP Server Receive Port Code number 0 ~ 255 168 (Fixed)
Program Port: 1 ~ 65535 5080
28 Configuration File Name Code number 0 ~ 255 43 (Fixed)
10
Sub Code number 0 ~ 255 152
Up to 15 characters No Setting
29 Configuration File Name Code number 0 ~ 255 43 (Fixed)
Sub Code number 0 ~ 255 153
Up to 15 characters No Setting
Conditions
None

None

ISSUE 1.0 SL2100

10-19 : VoIP DSP Resource Selection
Level:
IN
Description
Use Program 10-19 : VoIP DSP Resource Selection to define the criteria for each DSP resource on Program
the VoIPDB.
Input Data
Slot Number 0
10
DSP Resource Number 1 ~ 128

No.
01 VoIP DSP Resource 0 = Common use for This program is used to assign the 128 re- Resource 1 = 1
Selection both IP extensions and sources of the VoIPDB. Resource 2 ~
trunks NEC recommends leaving the default set- 128 = 0
1 = Use for IP exten- tings as system default.
sions
2 = Use for SIP trunks
3 = Use for Networking
5 = Blocked
6 = Common without
unicast paging
7 = Multicast paging
8 = Unicast paging
Conditions
None

None

SL2100 ISSUE 1.0

10-62 : NetBIOS Setting
Level:
IN
Description
Program Use Program 10-62 : NetBIOS Setting to set the data of NetBIOS.
Input Data
10 Item
No.
01 NetBIOS Mode 0 = Disabled 1

1 = Enabled
02 NetBIOS Name Maximum 15 characters Please avoid using Space between the SL2100
words. Also when you create name
please use all upper letters.
Conditions
None

None

ISSUE 1.0 SL2100

10-63 : DHCP Client Setting
Level:
IN
Description
Use Program 10-63 : DHCP Client Setting to set the data of DHCP Client. Program
Input Data
Item
No.
10
01 DHCP Client Mode 0 = Disabled If you are using IP phones/trunks it is rec- 1
1 = Enabled ommended to not use the DHCP client
function, a static IP address would be pre-
ferred. If you are going to still use the
DHCP client function then the DHCP serv-
er should be setup so that the same IP ad-
dress is always provided to the system.
Conditions
None

None

SL2100 ISSUE 1.0
Program 15 : Extension, Basic Setup

15-05 : IP Telephone Terminal Basic Data Setup
Level:
IN
Description
Program Use Program 15-05 : IP Telephone Terminal Basic Data Setup to set up the basic settings for an IP
telephone.
15 Input Data
Extension Number Maximum eight digits
Item Item Input Data Description Default Related

No. Program
01 Terminal Type 1 = H.323 3
2 = SIP
3 = None
4 = DT800/DT700
02 IP Phone Fixed MAC address MAC Address of registered SIP MLT 00-00-00- 15-05-01
Port Assignment 00-00-00-00-00-00 ~ phone is stored and/or can input the 00-00-00
FF-FF-FF-FF-FF-FF MAC address of an SIP MLT phone
so when it comes online it is provi-
ded with the extension in which the
MAC address matches.
04 Nickname Up to 48 characters Nickname section on Invite mes- No Setting 15-05-17
sage.
Example :
Extension 100 has a Nickname set
to PAUL.
Extension 101 has command
15-05-17 set to Nickname.
The inbound call to extension 101,
from 100, shows PAUL.
Nickname must be unique in the
system.
07 Using IP Address 0.0.0.0 ~ - 15-05-01
255.255.255.255
09 Call procedure 0 ~ 65535 - 15-05-01
port
11 DT800/DT700 0 ~ 65535 -
C/CTR Port
15 CODEC Type 1 = Type 1 Assign the CODEC Type of the SIP 1 84-24
2 = Type 2 MLT. 84-11
3 = Type 3 15-05-01
4 = Type 4
5 = Type 5
16 Authentication Up to 24 characters Assign the authentication password No Setting 15-05-01
Password for SIP single line telephones.
Web pro indicates password as *
mark.
5-18 Program 15 : Extension, Basic Setup

ISSUE 1.0 SL2100

No. Program
18 IP Duplication Al- 0 = Disable When this program is 1: Enable, the 0 15-05-01
lowed Group 1 = Enable duplication of an IP address is al-
lowed at the time of SIP/DT700 ter-
minal registration. This PRG is valid,
when PRG15-05-01 is SIP or
DT800/DT700.
19 Side Option In- 0 = No Option 0
formation 1 ~ 3 = Not used
4 = EHS
20 Bottom Option 0 = No Option Shows the type of adapter installed. 0 10-03-10
Information 1 ~ 2 = Not Used
3 = WHA Program
4 = BCA
26 DT700 Terminal 0 = Not Set 0
15
Type 1 = Not Used
2 = ITL-**D-1D/
ITL-24BT-1D/
ITL-24PA-1D (without
8LKI (LCD) -L)
3 = UT880
4 = Not Used
5 = Softphone
6 = CTI
7 ~ 8 = Not Used
9 = IP4WW-24TIXH
10 ~ 12 = Not Used
13 = ITZ-*-*D
14 = ITZ-*CG
15 ~ 17 = Not Used
18 = IP7WW-8IPLD-C1
27 Personal ID In- 0 ~ 128 When the SIP Multiline telephone is 0 84-22
dex using manual/auto registration, as-
sign each phone a unique personal
index. Then go to command 84-22
to assign the user name and pass-
word.
28 Addition Infor- 0 = Do not inform Select whether to inform of addition- 0 15-01-01
mation Setup 1 = Inform al information or not. 15-02-13
15-02-15
15-02-34
29 Terminal WAN- 0.0.0.0 ~ 0.0.0.0
side IP Address 255.255.255.255
30 DTMF Play dur- 0 = Do Not Play 0
ing Conversation 1 = Play
at Receive Exten-
sion
31 Alarm Tone dur- 0 = Off 1
ing Conversation 1 = On
(RTP packet loss
alarm)
33 LAN Side IP Ad- 0.0.0.0 ~ 0.0.0.0.
dress of Terminal 255.255.255.255
35 Encryption Mode 0 = Off 0
On/Off 1 = On
36 DT800/DT700 00.00.00.00 ~ ff.ff.ff.ff Indicate a current firmware Version. 00.00.00.00
Firmware Ver-
sion
38 Paging Protocol 0 = Multicast Sets the protocol mode for the Pag- 0
Mode 1 = Unicast ing function.
2 = Auto
39 CTI Override 0 = Disable 0
Mode 1 = Enable

SL2100 ISSUE 1.0

No. Program
40 Calling name dis- 0 = Both name and * Trunk name is the first priority and 0
play info via number abbreviated (SPD) name is second
trunk for stand- 1 = Name only priority
ard SIP 2 = Number only
3 = None
41 Time Zone(hour) 0 ~ 24 12
(- 12 ~ + 12 hour)
43 Video Mode 0 = Disable 0
1 = Enable
44 Using STD-SIP 0 = Disable 0
Display for CPN 1 = Enable
Program
45 NAT plug & play 0 = OFF Effect this program only when PRG 1 10-46-14
1 = ON 10-46-14 (for IP Multiline Terminals)
or PRG 10-33-05 (for Standard SIP
15 Terminal) are set to NAT mode.

Effect this program only when PRG
10-46-14 (for IP Multiline Terminals)
is set to NAT mode.
If you are setting the SIP Terminal
using remote router by turning this
setting ON you don't need to set the
Port Forward on remote router side.
Select sending RTP port number to
remote Router, use from negotiation
result (0) or received RTP packet (1)
46 Door Phone 0 = Not door phone 0
Number 1 ～ 6 = Door phone
number
47 Registration Ex- 0 = Disable On a per station basis, this setting 180 84-23-01
pire Timer for 60 ~ 65535 (sec) defines the SIP registration expiry
NAT timer. This setting applies to IP Mul-
tiline Terminals or Standard SIP Ter-
minal connected via NAPT. If this
value is set to 0, for a NAPT termi-
nal, the value in PRG 84-23-01 (for
IP Multiline Terminals) or PRG
10-33-01 (for Standard SIP Termi-
nal) are applied.
48 Subscriber Ex- 0 = Disable On a per station basis, this setting 180 84-23-02
pire Timer for 60 ~ 65535 (sec) defines the SIP subscribe expiry
NAT timer. This setting only applies to IP
Multiline Terminals or Standard SIP
Terminal connected via NAPT. If this
value is set to 0, for a NAPT termi-
nal, the value in PRG 84-23-02 (for
IP Multiline Terminals) or PRG
10-33-01 (for Standard SIP Termi-
nal) are applied.
49 Receiving SIP IN- 0 = Disable Enables to receive a SIP INFO mes- 2
FO 1 = Allowed any time sage from a standard SIP phone as
2 = Allowed while RTP a dial information.
is not available
50 Peer to Peer 0 = Off 1
Mode 1 = On
51 Transport Proto- 0 = UDP This program is the transport proto- 0
col 1 = TCP col. (Read only)
Conditions
None
5-20 Program 15 : Extension, Basic Setup

ISSUE 1.0 SL2100

None
Program
15

SL2100 ISSUE 1.0
Program 84 : Hardware Setup for VoIPDB

84-09 : VLAN Setup
Level:
IN
Description
Program Use Program 84-09 : VLAN Setup to set up the VLAN data.
Input Data
84 Interface Number 1~2
Item Item Input Data Default

No.
01 VLAN 0 = Disable (Off) 0
1 = Enable (On)
02 VLAN ID 0 ~ 4094 0
03 Priority 0~7 0
Interface No.2: The packets send from LAN I/F on VoIPDB is set the VLAN Tag (VoIPDB 32ch/64ch/
128ch).
Conditions
• System programming must be exited before these program options take affect.

None
5-22 Program 84 : Hardware Setup for VoIPDB

ISSUE 1.0 SL2100
Program 84 : Hardware Setup for VoIPDB

84-10 : ToS Setup
Level:
IN
Description
Use Program 84-10 : ToS Setup to set up the Type of Service data. Program
Input Data
1 = Not Used
2 = Not Used
84
3 = Reserved
4 = H.323
5 = RTP/RTCP
Protocol Type 6 = SIP
7 = Reserved
8 = SIP MLT
9 = SIP Trunk
10 = Reserved
11 = Reserved

No.
01 ToS Mode 0 = Disable (Invalid) When Input Data is set to 1, Item No. 07 is 0
1 = IP Precedence invalid. When Data is set to 2, Item No. 02
2 = Diffserv ~ 05 are invalid.
02 Priority, IP Prece- 0~7 1 = Router queuing priority 0
dence 0 = Low
7 = High
03 Low Delay 0~1 1 = Optimize for low delay routing 0
0 = Normal Delay
1 = Low Delay
04 Wideband (Through- 0~1 1 = Optimize for high bandwidth routing 0
out) 0 = Normal Throughput
1 = High Throughput
05 High Reliability 0~1 1 = Optimize for reliability routing 0
0 = Normal Reliability
1 = Low Reliability
07 Priority (D.S.C.P. - Dif- 0 ~ 63 DSCP (Differentiated Services Code Point) 0
ferentiated Services
Code Point)
Conditions
• The system must be reset for these program options to take affect.

None

SL2100 ISSUE 1.0
Program 90 : Maintenance Program

90-23 : Deleting Registration of IP Telephones
Level:
IN
Description
Program This program is available via telephone programming and not through PC Programming.
Use Program 90-23 : Deleting Registration of IP Telephones to delete the registered IP telephone
90 from the system.
Input Data
Extension Number Up to eight digits

No.
01 Delete IP Telephone 1→Hold This assignment removes the station num- -
ber association with the MAC address of
the IP station.
[Del.IP-Phone] : Dial 1 + press Hold
(Press Hold only to cancel.)
Conditions
None

None
5-24 Program 90 : Maintenance Program

ISSUE 1.0 SL2100
Program 90 : Maintenance Program

90-34 : Firmware Information
Level:
IN
Description
Use Program 90-34 : Firmware Information to list the package type and firmware boards installed in Program
the system.
Input Data
Slot Number 00 ~ 12
90
Item Item Input Data Default
No.
01 Package Name PKG Name (Up to 15 characters) -
02 Firmware Version Number 00.00 ~ 15.15 -
03 VOIPDB Software Version DEV/PR/REL - 00.00.00.00.00.00 -
DEV/PR/REL - FF.FF.FF.FF.FF.FF
04 DSP Project Number 00000000 - FFFFFFFF -
05 Vocoder Firmware Version 00.00.00.00 - FF.FF.FF.FF -
06 OCT1010ID Version 00.00.00.00 - FF.FF.FF.FF -
Conditions
None

None

SL2100 ISSUE 1.0
MEMO
Program
90
5-26 Program 90 : Maintenance Program

Network Design Considerations
This chapter explains some issues that should be considered when planning a NEC SL2100 VoIP
installation. This is a generalized explanation and therefore does not discuss vendor-specific issues
and solutions. Typically, different solutions are implemented by different manufacturers.
Network Design Considerations

SECTION 2 QOS
Quality of Service (QoS) is one of the most important factors for VoIP. This refers to the perceived
quality of speech and the methods used to provide good quality speech transmission. Several factors
that affect speech quality and several mechanisms can be used to ensure QoS.
This chapter also describes the problems that can occur and some possible solutions. Each network
equipment manufacturer (NEC, 3Com, Cisco, etc.) has slightly different methods of implementing QoS
and these are not discussed in this document. This chapter provides an overview to classify voice
traffic on the NEC SL2100 so that the network equipment can impose QoS.
2.1 QoS Definitions

This section lists common definitions used with QoS for VoIP.
Latency (Delay):
If at any point the usage on the network exceeds the available bandwidth, the user experiences delay,
also called latency. In more traditional uses of an IP data network, the applications can deal with this
latency. If a person is waiting for a web page to download, they can accept a certain amount of wait
time. This is not so for voice traffic. Voice is a real time application, which is sensitive to latency. If the
end-to-end voice latency becomes too long (150ms, for example), the call quality is usually considered
poor. It is also important to remember that packets can get lost. IP is a best effort networking protocol.
This means the network tries to get the information there, but there is no guarantee.
Delay is the time required for a signal to traverse the network. In a telephony context, end-to-end
delay is the time required for a signal generated at the talker's mouth to reach the listener's ear.
Therefore, end-to-end delay is the sum of all the delays at the different network devices and across
the network links through which voice traffic passes. Many factors contribute to end-to-end delay,
which are covered next.
The buffering, queuing, and switching or routing delay of IP routers primarily determines IP network
delay. Specifically, IP network delay is comprised of the following:
• Packet Capture Delay
Packet capture delay is the time required to receive the entire packet before processing and
forwarding it through the router. This delay is determined by the packet length and transmission
speed. Using short packets over high-speed networks can easily shorten the delay but potentially
decrease network efficiency.

SL2100 ISSUE 1.0
• Switching/Routing Delay
Switching/routing delay is the time the router takes to switch the packet. This time is needed to
analyze the packet header, check the routing table, and route the packet to the output port. This
delay depends on the architecture of the switches/routers and the size of the routing table.
• Queuing Time
Due to the statistical multiplexing nature of IP networks and to the asynchronous nature of packet
arrivals, some queuing, thus delay, is required at the input and output ports of a packet switch. This
delay is a function of the traffic load on a packet switch, the length of the packets and the statistical
distribution over the ports. Designing very large router and link capacities can reduce but not
completely eliminate this delay.
Jitter
Delay variation is the difference in delay exhibited by different packets that are part of the same traffic
flow. High frequency delay variation is known as jitter. Jitter is caused primarily by differences in queue
wait times for consecutive packets in a flow, and is the most significant issue for QoS. Certain traffic
types, especially real-time traffic such as voice, are very intolerant of jitter. Differences in packet arrival
times cause choppiness in the voice.
All transport systems exhibit some jitter. As long as jitter falls within defined tolerances, it does not
impact service quality. Excessive jitter can be overcome by buffering, but this increases delay, which
can cause other problems. With intelligent discard mechanisms, IP telephony/VoIP systems try to
synchronize a communication flow by selective packet discard, in an effort to avoid the walkie-talkie
phenomenon caused when two sides of a conversation have significant latency. NEC SL2100
incorporates a Jitter Buffer to avoid these problems.
Packet Loss
During a voice transmission, loss of multiple bits or packets of stream may cause an audible pop that
can become annoying to the user. In a data transmission, loss of a single bit or multiple packets of
information is almost never noticed by users. If packet drops become epidemic, the quality of all
transmissions degrades. Packet loss rate must be less than five percent for minimum quality and less
than one percent for toll quality.
2.2 Voice Quality Improvements

This section describes various techniques that can be used to improve the voice quality.
• Increase available bandwidth:
This can sometimes be the most basic solution and the easiest of the solutions. If running a System
IP Phone using G.711 with a 30ms fill time over Ethernet, for only one call, 90Kbps of bandwidth is
needed. If that same user only has a 64K line, they do not have a decent IP voice call. The user can
increase the available bandwidth to slightly exceed the 90Kbps requirements and their voice quality
dramatically increases. This solution might not be viable if no more bandwidth is available.
• Use a different CODEC:
The CODEC contains possible compression algorithms to be used on the voice. Let’s take the
example above again. The user only wants one voice line over a 64Kbps data connection. They
also want to maintain their current fill time of 30ms. Change to a G.729. For one line, only 34Kbps is
required for a call. This fits well within the 64Kbps of available bandwidth.
• Increase the number of frames per packet:
To continue with the example above, the user has moved to a G.729 CODEC. But now, the user
wishes to add two more System IP Phones. Their current 64Kbps line can handle one call, because
it is only 34Kbps. Two more System IP Phones would increase the total to 102Kbps so obviously
there is not sufficient bandwidth.
The user can now increase the fill time to 50ms. This reduces the bandwidth per call to 19.8Kbps
(3x 19.8 = 59.4Kbps). The savings in bandwidth comes from the fact that with a longer fill time,
fewer packets are needed to send the voice. With fewer packets, less header information needs to
be attached and transmitted.
6-2 Network Design Considerations

ISSUE 1.0 SL2100
• Change Layer 2 Protocols:

Ethernet is most commonly used for IP packets. Unfortunately, Ethernet has a fairly large overhead
of 34 bytes. So every IP voice packet going over Ethernet has a 34-byte Ethernet header attached
to it. As the number of packets add up, this header data can become significant. Frame Relay has a
7-byte header and Point-to-Point Protocol (PPP) has a 6-byte header. With this decrease in header
length at layer 2, some significant savings in bandwidth use can be achieved.
The down side to this is that most networks may not have these services available, where Ethernet
is very widely used. This is usually outside the control of the installer and therefore NEC strongly
advises users to do more research on other layer 2 protocols before trying to implement them in
their voice network.
• Implement Quality of Service (QOS):
Now, assume a derivative of the above example. The user needs only one voice line over their
64Kbps connection. They are using G.729 with a 30ms fill time. This requires 34Kbps of their
available bandwidth. Also assume that this line is used at certain times of the day for data
connectivity. This data connectivity is very light, only 20Kbps or so during most of the day, but does
spike to 50Kbps during certain points of the day. This data is not time sensitive like the voice data,
so if necessary it could be forced to wait.
Therefore, the user can implement a Quality of Service mechanism on the IP network. At its most
basic form, this denotes certain IP packets as being more important than others. So they would tell
this 64Kbps line that IP packets with voice deserve a higher priority than those without voice. This
allows the network devices to give priority to the other data, so the quality of the call is not
compromised.
2.3 Types of Classifications for Traffic for QoS

Classification uses information from a packet (or frame) to define the type of data and therefore how
the data should be handled for QoS on the network. Using packet classification, you can partition
network traffic into multiple priority levels or Types of Service (ToS). NEC SL2100 supports methods of
marking a packet with its classification information in the Layer 2 or 3 headers.
• VLAN (802.1Q):
Virtual LANs work at Layer 2 of the OSI model and can be equated to a broadcast domain. More
specifically, VLANs can be seen as a group of end stations, perhaps on multiple physical LAN
segments that are not constrained by their physical location and therefore, communicate as if they
were on a common LAN. Packets can be marked as important by using layer 2 classes of service
(CoS) settings in the User Priority bits of the 802.1Pq header. Refer to Program 84-09 : VLAN
Setup on page 5-22 for information for VLAN configuration.
Layer 2
802.1Q/p
TAG
PREAM SFD DA SA Type PT Data FCS
4 Bytes
PRI CFI VLAN ID
Three bits used for CoS

(user priority)
Figure 6-1 Layer 2 Diagram (802.1Q)

SL2100 ISSUE 1.0
• IP Precedence - Layer 3 QoS:

Allows you to specify the class of service for a packet. You use the three precedence bits in the IPv4
header type of service (ToS) field for this purpose. Using the ToS bits, you can define up to six
classes of service. Other devices configured throughout the network can then use these bits to
determine how to treat the packet in regard to the type of service to grant it. These other QoS
features can assign appropriate traffic-handling policies including congestion management and
bandwidth allocation. By setting IP Precedence levels on incoming traffic and using them in
combination with QoS queuing features, you can create differentiated service. (Refer to Program
84-10 : ToS Setup on page 5-23 for detailed programming information.)
• Differentiated service (Diffserv) - Layer 3 QoS:
Provides services differentiated on performance using weighted priority queuing. DiffServ requires
that edge routers classify traffic flows into a member from a set of categories based on the TCP/IP
header fields in what is called a micro flow. Because the Diffserv is present in every packet header,
each node can provide differentiated services per-hop. Refer to Program 84-10 : ToS Setup on
page 5-23 for detailed programming information.
SECTION 3 INTERNET BASED CONNECTIONS (XDSL, CABLE,

ETC.)
Internet-based connections are becoming increasingly popular. This is mainly due to the speed and
cost of xDSL and cable modem connections. For data applications, these types of connection are
generally acceptable. For Voice over IP applications several issues should be taken into consideration.
Asymmetric Data Rates
On many Internet based connections, there are different data rates for upstream and downstream. For
example 1Mbps down and 256Kbps up. This works well for Internet access, as generally you
download files from the Internet to your PC and transmit less information in the other direction. For
VoIP, speech uses the same amount of bandwidth in both directions, which means that the amount of
simultaneous calls can not exceed the amount of “upstream” bandwidth available.
Contention
Most Internet based connections specify a contention ratio. This is typically 50:1 for home users or
20:1 for business users. This specifies the number of users subscribed to a single connection to the
Internet Service Provider (ISP). This indicates how many users share the bandwidth with other users
on the Internet, which means that the speeds that you are quoted are not necessarily accurate – you
receive less than these figures.
It is unlikely that all subscribers are using a connection at the same time, so these figures are not quite as
bad as they first seem.
Network Address Translation (NAT)
Usually, the equipment that your ISP provides (cable modem, ADSL router, etc.) uses Network
Address Translation. This allows several devices to share one public IP address. The issues relating
to the use of NAT are outlined in Firewalls and NAT below.
VPN
Due to the use of NAT, and non-routable IP addressing, it may be necessary to implement a VPN
solution. This is outlined in VPN Tunneling below. (Refer to Virtual Private Network (VPN)
Tunnelling on page 6-6.)
QoS
As discussed earlier, it is essential to have some form of Quality of Service implemented. With Internet
based connections, we are not in control of the many routers, switches and other network hardware

ISSUE 1.0 SL2100
that reside between our two VoIP endpoints. This means that we cannot specify any QoS parameter
on these devices.
The only point where the QoS can be controlled is at the VPN or firewall. This allows VoIP traffic to be
prioritized over any other data that is sent out to the Internet. This helps to maintain reasonable quality
speech – but once the data has exited the local router/cable modem it is at the mercy of the Internet.
When implementing NEC SL2100 IP over Internet based connections it is very important that these
factors are considered, and that the customer is made aware that neither the installer nor NEC are
held responsible for any quality issues experienced.
SECTION 4 FIREWALLS AND NAT

The ways in which networks are designed to be secure (firewall, VPN services, proxy servers, etc.)
and integration of NAT create problems for VoIP. This is due in part, to the endless number of different
scenarios for non-real time protocols and their limited solutions.
4.1 Understanding the Infrastructure

The networks in place today look very different than the networks of yesterday. In the past, only
computers and servers were connected to the network. The network was built to be as a best effort
delivery mechanism, where delay and lost of information between devices was something we dealt
with. Today, there is an over saturation of devices needing to gain access to the IP network. Desktop
computers, fax machines, wireless PDAs, Servers, home appliances, video servers and now VoIP
terminals all are fighting for bandwidth, precedence, and addresses on this converged network.
It is necessary to create some kind of Intranet environment (across the Internet), with fixed network
characteristics, where VoIP solutions can tolerate some minor variations. IT personnel have been
tasked with implementing different mechanisms in the network to support the new demands required
on the converged network. Some solutions that have been implemented are:
• QoS devices to support precedence settings of voice packets.
• Elimination of hubs in place of switches to support 100Mbps full-duplex transmission.
• Firewall integration to protect the internal network from external attack.
• Network Address Translation (NAT) devices are widely deployed to support the addressing issues.
• Virtual Private Network (VPN) Servers were added to Enterprise networks to support the security
and connectivity issues for remote users.
Some solutions, such as the hub replacement and integration of QoS, are done behind the scenes
and should have no effect on the voice application. Other solutions such as NAT and Firewall cause
major disturbance to VoIP.
4.2 Firewall Integration

Network security is always a concern when connecting the Local Area Network (LAN) to the Wide
Area Network (WAN). There are many ways to integrate security in the network – the most popular are
Firewalls and Proxy servers.
• Firewalls
Firewalls can be implemented in both hardware and software, or a combination of both. Firewalls
are frequently used to prevent unauthorized Internet users from accessing private networks
connected to the Internet, especially Intranets. All messages entering or leaving the Intranet pass
through the firewall, which examines each message and blocks those that do not meet the specified
security criteria.
• Proxy Server
Proxy server intercepts all messages entering and leaving the network. The proxy server effectively
hides the true network address.

SL2100 ISSUE 1.0
What should be noted is that no matter which security measure is implemented, the VoIP must have
TCP/UDP ports open in the security wall (e.g., firewall/proxy) for the media and control streams to
flow. If any point in the network prevents the ports from flowing from end-to-end, the VoIP application
does not work.
The ports that need to be open on the firewall/proxy vary depending on the particular application being
used. A list of these ports is shown below, however it should be noted that the preferred solution would
be to allow all ports on the NEC SL2100 device to be open, or to place the NEC SL2100 outside of the
firewall.
Applications Rx Port NEC SL2100 Programming

PC Programming 8000 90-54-02
Web Programming 80 90-54-01
DHCP Server 67
SIP MLT Listening Port 5080 10-46-06
5081 10-46-13
SIP Trunk Listening Port 5060 10-29-04
SIP Single Line Stations 5070 84-20-01
Realtime Transport Protocol 10020~10082 84-26-01
Realtime Transport Control Protocol (RTCP) 10021~10083 84-26-02
4.3 Virtual Private Network (VPN) Tunnelling

A Virtual Private Network is a private data network that maintains privacy through using a tunneling
protocol and security procedures. Allowing for remote networks (including VoIP devices), which reside
behind NATs and/or Firewalls to communicate freely with each other.
The idea of the VPN is to connect multiple networks together using public (i.e., Internet) based
connections. This type of connection is ideal for those commuters, home workers, or small branch
offices needing connectivity into the corporate backbone. It is possible to connect these remote
networks together using private links (such as leased lines, ISDN, etc.) but this can be very expensive
and there is now a high demand for low cost Internet connectivity.
Companies today are exploring the use of VPN for a variety of connectivity solutions, such as:
• Remote User to Corporate Site VPN
Allows employees to use their local ISP fastest connection such as cable modems, DSL, and ISDN.
For traveling users, all they need to do is dial into their ISP local phone number.
• Site-to-site VPN
Allows companies to make use of the Internet for the branch-to-branch connections, cutting the cost
of the expensive point to point leased line service.
• Extranet
Extranet describes one application using VPN technology. The concept allows a company and a
vendor/supplier to access network resources at each site. For example, a customer may have
access to a suppliers intranet for access to product information.
VPNs can be implemented in hardware or software. Single users, such as traveling sales personnel,
may have a software based VPN client on their laptop computer. This connects back to the Head
Office VPN server. For larger sites, the VPN is typically implemented using a hardware VPN – this is
often incorporated in to a firewall solution.
The diagram below is example of how a VPN tunnel may be implemented. The red lines in the
diagram show the tunnels that are created through the Internet. Each network can connect to the
others as though they are connected with private connections (kilostream, etc.), without the issues
relating to NAT.

ISSUE 1.0 SL2100
Internet
L AD
DS SL
A
ADSL ADSL
Router Router
DSL / Cable / Dialup

Firewall / Firewall /
VPN VPN
Chassis
Home Office LAN
SL2100 Mobile Workers

(Software VPN Client)
Head Office LAN
Figure 6-2 Virtual Private Network (VPN) Example
When IP address translation is applied to a VoIP packet, the application fails and the communication
path is broken. VoIP packets contain the IP address information and the ports used as part of its
payload. When NAT is applied, only the header parameter is changed, not the payload data that
affects the process of data packets within the VoIP switch and terminal.
The common scenario for remote IP deployment is:

• Implementation of an IP Phone with a public IP address talking with an NEC SL2100 behind NAT.
An example would be a telecommuter.
Implementation of an IP Phone behind a NAT, which connects to the Internet, terminates in a NEC
SL2100 behind a different NAT.
When selecting VPN equipment it is important to consider Quality of Service. Generally, VPN
hardware is connected to Internet connections which are unreliable and out of the control of the
customer. However, it is possible to set prioritization on some VPN units for voice traffic. This does
not solve the unreliability of the Internet, but helps to ensure that the data traffic to and from the LAN
do not impair the quality of the voice traffic. (Refer to QoS on page 6-1).
NEC strongly recommends that any VPN hardware used for VoIP has the facility to prioritize voice
traffic.
SECTION 5 CODEC AND BANDWIDTH

This section describes CODEC and bandwidth and their application with the NEC SL2100 system.

SL2100 ISSUE 1.0
5.1 CODECs
CODEC (COder/DECoder) uses the technology of encoding and decoding a signal. For VoIP, this
specifically refers to the algorithm used to convert analog speech to digital data for transmission on an
IP network.
The NEC SL2100 system supports three different CODECs:

• G.711
This is the ITU-T recommendation for coding of speech at 64kbps using PCM (pulse code
modulation). This CODEC is often described as uncompressed as it uses the same sampling rate as
Time-Division Multiplexing (TDM). G.711 has a MOS**1 score of 4.2 but uses a large bandwidth for
transmission. This CODEC is not commonly used due to the bandwidth required, although it can be
acceptable in LAN environment (i.e., IP Phones connected over a 100Mbps LAN).
• G.722
G.722 is an ITU standard CODEC that provides 7kHz wideband audio at data rates from 48 to
64kbps. This is useful in a fixed network Voice Over IP applications, where the required bandwidth
is typically not prohibitive, and offers a significant improvement in speech quality over older
narrowband CODECs such as G.711, without an excessive increase in implementation complexity.
• G.726
G.726 is an ITU-T ADPCM speech CODEC standard covering voice transmission at rates of 16, 24,
32, and 40kbit/s. It was introduced to supersede both G.721, which covered ADPCM at 32kbit/s,
and G.723, which described ADPCM for 24 and 40kbit/s. G.726 also introduced a new 16kbit/s rate.
The four bit rates associated with G.726 are often referred to by the bit size of a sample as 2-bits, 3-
bits, 4-bits, and 5-bits respectively.
• G.729A
This ITU-T recommendation describes the algorithm for coding of speech signals at 8kbps using
CS-ACELP (conjugate-structure algebraic code-excited linear prediction). This CODEC samples the
analog signal at 8000Hz and uses a frame size of 10ms. This CODEC has a MOS score of 4.0.
G.729 is the most commonly used CODEC for NEC SL2100 VoIP installations. This is due to the
fact that it offers high compression (and therefore low bandwidth) while maintaining good speech
quality.
Packet Size:
Each CODEC has a set frame length. This is the time that the frame encapsulates. For G.729 and G.
711 the frame length is 10ms. It is possible to configure the packet size in the NEC SL2100
programming. To do this, we tell the NEC SL2100 how many frames to encapsulate into each packet
for transmission.
For example, the G.729 has a frame length of 10ms - the packet size is set to 3 (in Program 84-11-01).
This gives a 10ms x 3 = 30ms packet.
5.2 Bandwidth
The bandwidth required for VoIP calls depends on several factors, including:
• Number of simultaneous calls
• CODEC used
• Frame Size
• Data Networking Protocol used
The more frames encapsulated into each packet, the less bandwidth is required. This is because each
packet transmitted has the same header size. Therefore, if numerous very small packets are sent then
**1. The Mean Opinion Score (MOS) provides a numerical measure of the quality of human speech at the
destination end of the circuit. The scheme uses subjective tests (opinionated scores) that are mathematically
averaged to obtain a quantitative indicator of the system performance.

ISSUE 1.0 SL2100
bandwidth is also being used for a large amount of header information. If we add several frames to the
packet, less packets are transmitted and therefore have less header information sent.
If we add many voice frames to each packet, less bandwidth is being used. However, this does have
disadvantages. If there is a large packet size, and a particular voice packet is lost, this has a greater
impact on the speech quality. If a small quantity of voice frames per packet is being used, the effect of
losing a packet is reduced.
As a general rule: The more frames per packet, the less bandwidth is used, but the quality is also
lower.
Examples:
Example 1: CODEC: G.729 Frame Size: 10ms Voice Frames per Packet: 2 Voice Sample Size: 20ms
(frame size x Voice Frames) Bandwidth Required: 24Kbps
Example 2: CODEC: G.729 Frame Size: 80ms Voice Frames per Packet: 8 Voice Sample Size: 80ms
(frame size x Voice Frames) Bandwidth Required: 12Kbps
SECTION 6 QUALITY OF SERVICE (QOS) IMPLEMENTATION

Section Voice Quality Improvements on page 6-2 discusses some of the problems associated with
voice quality. This section describes how QoS can be implemented on data networks to provide the
“best case” for VoIP traffic.
Not all network hardware supports QoS and each manufacturer has their own methods of
implementing QoS. The explanations below are as generic as possible. The installer/maintainer of the
data network should be familiar with the QoS characteristics of their equipment and should be able to
configure the equipment accordingly.
Quality of Service is commonly used to describe the actual implementation of prioritization on network
hardware. This prioritization (at Layer 2 and Layer 3 of the OSI model) is described in Figure 6-1 Layer
2 Diagram (802.1Q) on page 6-3.
6.1 Prioritization
When data is transmitted through a network, bottlenecks can occur causing the available bandwidth to
be reduced or the data to increase. This impacts the packet delivery.
Consider data communication between the two computers shown in the diagram Figure 6-1 Layer 2
Diagram (802.1Q) on page 6-3. The Hosts can transmit data at 100 Mbps. When a packet from Host
A, destined for Host B, reaches the router, the available bandwidth is reduced to 256Kbps and the
packet flow must be reduced. Figure 6-3 Network Bottleneck Example on page 6-10 shows a
diagram of this condition.

SL2100 ISSUE 1.0
Host A Host B
100Mbps
100Mbps
256Kbps
Private Circuit
(Leased Line)
100Mbps 100Mbps
Data Switch Router Router Data Switch
Figure 6-3 Network Bottleneck Example
For this example, each end of the network has only one host. Typically, many hosts are sending data
over the narrow bandwidth. The routers buffer packets and transmit them over the WAN lines as
efficiently as possible. When this occurs, certain packets are dropped by the router and some packets
are delayed.
For most data applications this packet loss/delay is not critical. For example, a delay of one to five
seconds to transmit an email is imperceptible. When VoIP is implemented, this loss/delay has a
massive impact on the voice quality. The resulting gaps in speech, distortion and delay are
unacceptable for voice traffic.
To avoid this problem, it is possible to prioritize the VoIP packets. The router examines all packets
received, determines the priority level of the packet, and forwards it accordingly. The data**1 is
assigned lower priority and the voice is transmitted before the data. This can have a negative impact
on the data network if a lot of voice is transmitted.
Figure 6-4 Voice and Data Network Implementation on page 6-11 shows how a voice and data
network can be implemented.
**1. This description discusses voice and data. These terms are commonly used when describing QoS, although
in the case of VoIP, the voice is actually converted to IP and transmitted as data. Therefore, everything
transmitted on a Data Network is data, but logically we think of this as voice and data traffic.

ISSUE 1.0 SL2100
Host A Host B
100Mbps
100Mbps
256Kbps
Private Circuit
(Leased Line)
100Mbps 100Mbps

100Mbps
100Mbps
Chassis Chassis
Telephone Telephone
System A System B
Figure 6-4 Voice and Data Network Implementation
After the router is configured for QoS, it examines incoming packets and allocates a priority to the
packet. Figure 6-5 Priority Queuing on Voice and Data Networks on page 6-11 shows the affect
priority queuing has on voice and data networks. The packets arrive randomly. They are processed
and output according to the QoS policy. The VoIP traffic is output first.
Packet from VoIP Device
Packet from PC
E thernet (100Mbps ) L ea s ed L ine (256K bps )
Router with QoS

Policy Applied
Direction of IP Traﬃc
Figure 6-5 Priority Queuing on Voice and Data Networks
To enable this type of queuing it is necessary to:

1. Configure the VoIP equipment to mark its packets with a specific value so that the switches/
routers can identify that it is voice – Called Marking.
2. Configure the network equipment to recognize the difference between the different Marked
packets – Called Classification. (i.e., informs the router what a voice packet looks like.
3. Configure the network equipment to give priority to the packets that have been classified as voice
– Called Priority Queuing.
6.2 Layer 2 QoS (802.1pq)

QoS is most commonly implemented at Layer 3 of the OSI model. This layer deals with IP addresses,
and is usually handled by Routers. However, sometimes it is necessary to implement Layer 2 QoS –
usually in large LAN environments with many IP phones.

SL2100 ISSUE 1.0
Layer 2 devices work with Ethernet frames (encapsulated IP packets) rather than IP addresses. Layer
2 QoS uses the Priority field of the Ethernet frame. This field has three bits and can have eight
possible values (000 to 111 in binary). Some switches can be configured to prioritize traffic based on
these values. This field is available only if the Ethernet device is configured for VLAN (IEEE 802.1q)
operation (VLAN is outside the scope of this document).
Protocol Structure - IEEE 802.1p: LAN Layer 2 QoS
Table 6-1 Protocol Structure for Layer 2 QoS on page 6-12 shows the format of an Ethernet frame
and the User Priority field that is used for Layer 2 QoS.
Table 6-1 Protocol Structure for Layer 2 QoS
IEEE 802.1Q Tagged Frame for Ethernet

7 Bytes 1 Byte 6 Bytes 6 Bytes 2 Bytes 2 Bytes 2 Bytes 42~1496 4 Bytes
Bytes
Preamble SFD DA SA TPID TCI Type Length Data CRC
Expanded View of TCI Field

3 Bits 1 Bit 12 Bits
User Priority CFI Bits of VLAN ID (VID) to identify possible VLANs
The following define the fields used for the protocol structure:
Preamble (PRE) - The PRE is an alternating pattern of ones and zeros that tells receiving stations a
frame is coming, and synchronizes frame-reception portions of receiving physical layers with the
incoming bit stream.
Start-of-frame delimiter (SFD) - The SOF is an alternating pattern of ones and zeros, ending with two
consecutive 1-bits indicating that the next bit is the left-most bit in the left-most byte of the destination
address.
Destination Address (DA) - The DA field identifies which station(s) should receive the frame.
Source Addresses (SA) - The SA field identifies the sending station.
Tag Protocol Identifier (TPID) - The defined value of SL2100 in hex. When a frame has the
EtherType equal to SL2100, this frame carries the tag IEEE 802.1Q / 802.1P.
Tag Control Information (TCI) - The field including user priority, Canonical format indicator and VLAN
ID.
User Priority - Defines user priority, giving eight priority levels. IEEE 802.1P defines the operation for
these three user priority bits.
CFI - Canonical Format Indicator is always set to zero for Ethernet switches. CFI is used for
compatibility reason between Ethernet type network and Token Ring type network.
VID - VLAN ID is the identification of the VLAN, which is basically used by the standard 802.1Q. It
allows the identification of 4096 VLANs.
Length/Type - This field indicates either the number of MAC-client data bytes that are contained in the
data field of the frame, or the frame type ID if the frame is assembled using an optional format.
Data - Is a sequence of bytes of any value. The total frame minimum is 64 bytes.
Frame Check Sequence (FCS) - This sequence contains a 32-bit cyclic redundancy check (CRC)
value, which is created by the sending MAC and is recalculated by the receiving MAC to check for
damaged frames.

ISSUE 1.0 SL2100
Example Ethernet Frame with Layer 2 QoS Enabled
The example below shows an Ethernet Frame containing one RTP (speech) packet. The Frame is
VLAN tagged, has a VLAN ID of 99 and a VLAN Priority of 5. It is also possible to see that the Layer 3
QoS has not been set.
Ethernet Frame Example - Layer 2 QoS Enabled
Source Destination Protocol

172.16.0.101 172.16.0.21 RTP
Info
Payload type=ITU-T G.729, SSRC=701655963, Seq=28165, Time=21520
Frame 160 (78 bytes on wire, 78 bytes captured)
Arrival Time: Jan 18, 2005 13:55:44.842738000
Time delta from previous packet: 0.008241000 seconds
Time since reference or first frame: 2.910072000 seconds
Frame Number: 160
Packet Length: 78 bytes
Capture Length: 78 bytes
Ethernet II, Src: 00:60:b9:c6:6e:45, Dst: 00:60:b9:c1:ab:a3
Destination: 00:60:b9:c1:ab:a3 (Nitsuko_c1:ab:a3)
Source: 00:60:b9:c6:6e:45 (Nitsuko_c6:6e:45)
Type: 802.1Q Virtual LAN (0xSL2100)
802.1q Virtual LAN
101. .... .... .... = Priority: 5 (Layer 2 Priority = 5)
...0 .... .... .... = CFI: 0
.... 0000 0110 0011 = ID: 99
Type: IP (0x0800)
Internet Protocol, Src Addr: 172.16.0.101 (172.16.0.101), Dst Addr:
172.16.0.21 (172.16.0.21)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default
(0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 60
Identification: 0x0086 (134)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 30
Protocol: UDP (0x11)
Header checksum: 0x4391 (correct)
Source: 172.16.0.101 (172.16.0.101)
Destination: 172.16.0.21 (172.16.0.21)
User Datagram Protocol, Src Port: 10022 (10022), Dst Port: 10020 (10020)
Source port: 10022 (10022)
Destination port: 10020 (10020)
Length: 40
Checksum: 0x0581 (correct)
Real-Time Transport Protocol
Stream setup by SDP (frame 1)
Setup frame: 1
Setup Method: SDP
10.. .... = Version: RFC 1889 Version (2)
..0. .... = Padding: False
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
0... .... = Marker: False
.001 0010 = Payload type: ITU-T G.729 (18)
Sequence number: 28165
Timestamp: 21520
Synchronization Source identifier: 701655963
Payload: 76AC9D7AB6ACE2510B3A3338646DA738...

SL2100 ISSUE 1.0
6.3 Layer 3 QoS

QoS is most commonly implemented at Layer 3. This allows the VoIP packets to be prioritized by
routers, before they are forwarded to their next hop.
Layer 3 QoS uses the Type of Service (ToS) field of the IP packet. This is an 8-bit field in the header of
the IP packet. The field can be used by Diffserv or IP Precedence. Although these are two different
standards, the actual field in the IP packet is the same – Only the method of evaluating the bits differs.
QoS does not function only by using the ToS field (i.e., Marking the VoIP packets). It is an end-to-end
process and requires configuration on all networking devices.
Packet Marking is the first step in this process and is often the only step that the NEC dealer performs.
Table 6-2 Layer 3 QoS Example

Protocol Structure - IP/Pv4 Header (Internet Protocol Version 4)
4 Bits 4 Bits 8 Bits 16 Bits

Version IHL Type of Service Total Length
Identification Flags Fragment Offset
Time to Live Protocol Header Checksum
Source Address
Destination Address
Option + Padding
Data
Type of Service Field (Diffserv)
6 Bits 2 Bits
Differentiated Services Code Point ECN (Not QoS related)
Type of Service Field (IP Precedence - Ref. RFC 1349)
3 Bits 1 Bit 1 Bit 1 Bit 1 Bit 1 Bit

IP Precedence Value Delay Throughput Reliability Cost MBZ (must be zero)
Listed below are the fields used in Table 6-2 Layer 3 QoS Example on page 6-14.
Version – the version of IP currently used.
IP Header Length (IHL) – datagram header length. Points to the beginning of the data. The minimum
value for a correct header is 5.
Type-of-Service – Indicates the quality of service desired by specifying how an upper-layer protocol
would like a current datagram to be handled, and assigns datagrams various levels of importance.
This field is used for the assignment of Precedence, Delay, Throughput and Reliability.
Total Length – Specifies the length, in bytes, of the entire IP packet, including the data and header.
The maximum length specified by this field is 65,535 bytes. Typically, hosts are prepared to accept
datagrams up to 576 bytes.
Identification – Contains an integer that identifies the current datagram. This field is assigned by
sender to help receiver to assemble the datagram fragments.
Flags – Consists of a 3-bit field of which the two low-order (least-significant) bits control fragmentation.
The low-order bit specifies whether the packet can be fragmented. The middle bit specifies whether

ISSUE 1.0 SL2100
the packet is the last fragment in a series of fragmented packets. The third or high-order bit is not
used.
Fragment Offset – This 13-bit field indicates the position of the fragment data relative to the
beginning of the data in the original datagram, which allows the destination IP process to properly
reconstruct the original datagram.
Time-to-Live – This is a counter that gradually decrements down to zero, at which point the datagram
is discarded. This keeps packets from looping endlessly.
Protocol – Indicates which upper-layer protocol receives incoming packets after IP processing is
complete.
Header Checksum – Helps ensure IP header integrity. Since some header fields change, e.g., Time
To Live, this is recomputed and verified at each point that the Internet header is processed.
Source Address – Specifies the sending node.
Destination Address – Specifies the receiving node.
Options – Allows IP to support various options, such as security.
Data – Contains upper-layer information.
6.4 IP Precedence
IP Precedence is a QoS method that combines a priority value with different on/off parameters; Delay,
Throughput, Reliability and Cost. The MBZ (Must be Zero) bit is not used.
Using the ToS bits, you can define up to eight classes of service. Other devices configured throughout
the network can then use these bits to determine how to treat the packet in regard to the type of
service to grant it. These other QoS features can assign appropriate traffic-handling policies including
congestion management and bandwidth allocation. By setting IP Precedence levels on incoming traffic
and using them in combination with QoS queuing features, you can create differentiated service.
Table 6-3 Type of Service Field (IP Precedence - i Ref. REC 1349)
3 Bits 1 Bit 1 Bit 1 Bit 1 Bit 1 Bit

IP Precedence Value Delay Throughput Reliability Cost MBZ (must be zero)
IP Precedence Value
Value Binary Value Description

0 000 Routine
1 001 Priority
2 010 Immediate
3 011 Flash
4 100 Flash Override
5 101 CRITIC/ECP
6 110 Internetwork Control
7 111 Network Control

SL2100 ISSUE 1.0
Throughput
Value Description
0 Normal Throughput
1 High Throughput
Reliability
Value Description
0 Normal Reliability
1 High Reliability
Delay
Value Description
0 Normal Delay
1 Low Delay
Cost
Value Description
0 Normal Cost
1 Low Cost
6.5 Diffserv (Differentiated Service)

Differentiated Services (Diffserv) uses the ToS field in an IP header. Diffserv is now commonly used
instead of IP Precedence (refer to IP Precedence on page 6-15) as it provides greater flexibility. This
method uses six bits of the ToS field to determine the priority – which provides up to 64 possible
values. The combination of binary digits is known as the Diffserv Codepoint (DSCP).
Table 6-4 Diffserv Parameters
6 bits 2 bits
Differentiated Services Code Point ECN (Not QoS related)
The example below shows an Ethernet Frame containing one RTP (speech) packet. The IP Packet
has the ToS field set to 101000 (binary) which is the equivalent of Class Selector 5. The router(s) in
this network should be programmed to prioritize based on CS5.
Ethernet Frame Example - Containing One RTP (Speech) Packet
Source Destination Protocol

172.16.0.21 172.16.0.101 RTP
Info
Payload type=ITU-T G.729, SSRC=732771006, Seq=30885, Time=20560
Frame 159 (65 bytes on wire, 65 bytes captured)
Arrival Time: Jan 18, 2005 13:55:44.834497000
Time delta from previous packet: 0.000445000 seconds
Time since reference or first frame: 2.901831000 seconds
Frame Number: 159
Packet Length: 65 bytes
Capture Length: 65 bytes
Ethernet II, Src: 00:60:b9:c1:ab:a3, Dst: 00:60:b9:c6:6e:45
Destination: 00:60:b9:c6:6e:45 (Nitsuko_c6:6e:45)
Source: 00:60:b9:c1:ab:a3 (Nitsuko_c1:ab:a3)

ISSUE 1.0 SL2100
Type: IP (0x0800)
Internet Protocol, Src Addr: 172.16.0.21 (172.16.0.21), Dst Addr: 172.16.0.101
(172.16.0.101)
Version: 4
Header length: 20 bytes
Diff Services Field: 0xa0 (DSCP 0x28: Class Selector 5; ECN: 0x00)
1010 00.. = Diff Services Codepoint: Class Selector 5 (0x28)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 44
Identification: 0x0069 (105)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 30
Protocol: UDP (0x11)
Header checksum: 0x431e (correct)
Source: 172.16.0.21 (172.16.0.21)
Destination: 172.16.0.101 (172.16.0.101)
User Datagram Protocol, Src Port: 10020 (10020), Dst Port: 10022 (10022)
Source port: 10020 (10020)
Destination port: 10022 (10022)
Length: 24
Checksum: 0x5293 (correct)
Real-Time Transport Protocol
Stream setup by SDP (frame 112)
Setup frame: 112
Setup Method: SDP
10.. .... = Version: RFC 1889 Version (2)
..1. .... = Padding: True
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
0... .... = Marker: False
.001 0010 = Payload type: ITU-T G.729 (18)
Sequence number: 30885
Timestamp: 20560
Synchronization Source identifier: 732771006
Payload: 3ED0
Padding data: 00
Padding count: 2
6.6 Comparison of IP Precedence and Diffserv Values

As stated earlier, IP Precedence and Diffserv use the same 8-bit ToS field in the IP header to mark
packets. It is possible to have the same ToS value for either method which means that the two
methods can work alongside each other.
For example, if the VoIP equipment supports IP Precedence and the router can prioritize only using
the DSCP they can be set to the same value. Refer to Table 6-5 IP Precedence and Diffserv Values
Comparison on page 6-17 for the values.
Table 6-5 IP Precedence and Diffserv Values Comparison
DSCP Decimal DSCP Binary IP Precedence Description

0 000000 0 Class Selector 0
1 000001
2 000010
3 000011
4 000100
5 000101
6 000110
7 000111

SL2100 ISSUE 1.0

9 001001
10 001010 AF11 (Assured Forwarding)
11 001011
13 001101
15 001111
17 010001
19 010011
21 010101
23 010111
25 011001
27 011011
29 011101
31 011111
33 100001
35 100011
37 100101
39 100111
41 101001
42 101010
43 101011
44 101100
45 101101
46 101110 EF (Expedited Forwarding)
47 101111
49 110001
50 110010

ISSUE 1.0 SL2100

51 110011
52 110100
53 110101
54 110110
55 110111
57 111001
58 111010
59 111011
60 111100
61 111101
62 111110
63 111111
6.7 Programming QoS in the NEC SL2100 System

6.7.1 Marking Voice Traffic - Program 84-10-XX
Before programming the NEC SL2100 system, discuss the requirements with the network engineering
staff or the managed network provider. If the ToS markings that are used are not specifically
configured into the network equipment, the voice traffic is handled by the default queue and is given
lowest priority.
6.7.2 NEC SL2100 Voice Protocols
The NEC SL2100 system supports the following types of VoIP traffic.
Number Protocol Type Description

1 H.323 Communication from VoIPDB to Network
2 RTP/RTCP Voice (RTP) and Call Quality Data (RTCP)
3 SIP Communication from VoIPDB to Standard SIP device.
4 SIP MLT Communication from VoIPDB to SIP Multiline Terminal.
5 SIP Trunks Communication from VoIPDB to Network
6.7.3 Configuring Diffserv
Use Program 84-10-10 to select the logic for marking the ToS field. The choices are:
Number ToS Mode Programs Enabled

0 None None – ToS bits are: 00000000

SL2100 ISSUE 1.0
Number ToS Mode Programs Enabled

1 IP Precedence 84-10-02 Priority – 0=Lowest ~ 7=Highest
(ToS bits: 0~2)
84-10-03 Delay – 0=Normal, 1=Low
(Tos Bit: 3)
84-10-04 Throughput – 0=Normal, 1=High
(Tos Bit: 4)
84-10-05 Reliability – 0=Normal, 1=High
(ToS Bit: 5)
ToS Bit 7: Always 0
Typically, only one of bits 3~6 is set to 1 and the other three bits are set to 0. For example,
to maximize route reliability, set 84-10-05 to 1 and leave 84-10-03, 84-10-04 and 84-10-06
at 0 (default).
2 Diffserv 84-10-07 DSCP Value in Decimals: 0~63
(ToS bits: 0~5)
ToS Bits 6 & 7 are not evaluated
6.7.4 Configuration Examples for Classification and Queuing
Figure 6-6 Common Network with Cisco Router on page 6-20 shows a typical network scenario and
an example of a Cisco router configuration.
This document provides a general description of VoIP technology, but it does not discuss individual
manufacturer solutions. This sample configuration is provided as a common scenario. It is a good example
of how QoS can be implemented on a router.
NEC does not endorse or provide support on any third party equipment unless it is supplied by NEC.
PC PC
192.168.1.50 192.168.2.50
Dallas Fort Worth

100Mbps
100Mbps
256Kbps
Private Circuit
(Leased Line)
100Mbps 10.0.0.1 10.0.0.2 100Mbps
192.168.1.1 192.168.2.1
100Mbps
100Mbps
Chassis Chassis
Telephone System Telephone System

192.168.1.10 192.168.2.10
Figure 6-6 Common Network with Cisco Router
See Table 6-6 Cisco Router Configuration Example on page 6-21 for configuration information about
the Cisco 2621 router. A description of key commands follows.

ISSUE 1.0 SL2100
Table 6-6 Cisco Router Configuration Example

Current Configuration : 2023 bytes
version 12.3
hostname Cisco2621
|
class-map match-any VoIPClass (1)
match ip dscp cs5 (2)
policy-map VoIPPolicy (3)
class VoIPClass(4)
priority 50(5)
class class-default(6)
fair-queue(7)
|
interface FastEthernet0/0
description Connects to Dallas LAN
ip address 192.168.1.1 255.255.255.0
|
interface Serial0/0
description Connects to Fort Worth via Kilostream
bandwidth 256(8)
ip address 10.0.0.1 255.255.0.0
service-policy output VoIPPolicy(9)
encapsulation ppp
|
ip route 0.0.0.0 0.0.0.0 10.0.0.2
Configuration Example Explanation:
1. Defines a Class Map called VoIPClass.

2. Matches any packets that have the ToS field set to IP Precedence 5 / DSCP 40 and assigns them to VoIPClass.
3. Defines a Policy Map called VoIPPolicy.
4. Creates a Class called VoIPClass and assigns this to the VoIPPolicy.
5. Allocates 50Kbps of bandwidth to the VoIPClass.
6 & 7. Determines that any data that does not match VoIPClass should be processed using the “fair-queue” method (i.e.,
No Prioritization).
8. Determines the amount of bandwidth available on the Serial interface – essential for the QoS calculations.
9. Applies the VoIP Policy to any packets that exit the serial interface. This means that data being received (input)
does not use this policy.
SECTION 7 PORT DESIGNATIONS

IP Application IP Port Numbers Comments
SIP Trunk
SIP Trunk Signaling 5060 UDP
SIP Trunk Voice 10020~10083 UDP
3rd Party SIP
SIP SLT Signaling 5070 UDP
SIP SLT Voice 10020~10083 UDP
NEC Proprietary SIP (SIP MLT)
SIP MLT Signaling 5080 and 5081 UDP
SIP MLT Voice 10020~10083 UDP

SL2100 ISSUE 1.0
MEMO

SIP Trunking
SECTION 1 VOIP 7
VoIP (Voice over Internet Protocol or Voice over IP) allows the delivery of voice information using the
Internet protocol (sending data over the Internet using an IP address). This means that digital voice
information can be sent in packets over the Internet rather than using the traditional public switch
SIP Trunking
telephone network (CO lines). A major advantage of VoIP is that it avoids the tolls charged by ordinary
telephone service.
Using VoIP equipment at a gateway (a network point that acts as an entrance to another network), the
packetized voice transmissions from users in the company are received and routed to other parts of
the company intranet (local area or wide area network) or they can be sent over the Internet using CO
lines to another gateway.**1
SECTION 2 IP NETWORKING
IP Networking uses VoIP technology to connect two or more telephone systems together. This allows
calls to be made between sites without using the public telephone network. This can save money and
make communication between sites much easier.
The following Networking modes are available on the NEC SL2100 system:
• SIP TIE lines
• SIP Trunks (to a SIP Trunk Provider)
SECTION 3 SIP TRUNKING

3.1 Introduction
SIP (Session Initiation Protocol) is used for Voice over IP. It is defined by the IETF (Internet
Engineering Task Force) in RFC2543 and RFC3261. SIP trunking is the term used for linking a PBX,
such as the NEC SL2100 system, to the public telephone network by means of VoIP. This provides the
ability for users to place and receive communications and services from any location and for networks
to identify the users wherever they are located.
SIP analyzes requests from clients and retrieves responses from servers then sets call parameters at
either end of the communication, handles call transfer and terminates.
The NEC SL2100 system implementation and programming for SIP are very similar. The call routing,
call features and speech handling (RTP) are the same. Only the signaling protocol is different.
**1. The voice quality of VoIP depends on variables such as available bandwidth, network latency and Quality
of Service (QoS) initiatives, all of which are controlled by the network and Internet Service Providers. Because
these variables are not in NEC control, it cannot guarantee the performance of the user’s IP-based remote voice
solution. Therefore, NEC recommends connecting VoIP equipment through a local area network using a Private
IP address.

SL2100 ISSUE 1.0
With the NEC SL2100 system, SIP trunks can receive incoming calls with Caller ID, place outgoing
calls, and transfer SIP trunks to IP, SIP, analog and digital stations, and across a network.
Currently, however, SIP Centrex Transfer is not supported.
If a common carrier supports SIP, the NEC SL2100 can connect the SIP Carrier and outgoing calls to
the PSTN (Public Switched Telephone Network) network and the common IP network using an NEC
SL2100 SIP trunk.
SIP CARRIER
PSTN
SIP Registrar
SIP Proxy
DNS
Chassis
SIP
Internet /
IP VPN
NAPT
SIP UA
SIP Multiline
Terminal
Figure 7-1 Common IP Network using NEC SL2100 SIP Trunk
3.1.1 SIP Trunking Requirements
The following are required when using the SIP trunk on the NEC SL2100 system:
• CPU-C1 software
• VOIPDB (VoIP Daughter Board) Programming Conditions
The following conditions apply when programming the NEC SL2100 system for SIP Trunking:
• If entries are made in Program 10-29-xx for a SIP Server and the SIP Server is then removed or not
used, the entries in Program 10-29-xx must be set back to their default settings. Even if Program
10-29-01 : SIP Proxy Setup – Outbound Proxy is set to 0, the NEC SL2100 system checks the
settings in the remaining 10-29 programs.
• SIP Multi-profile support is added. The simultaneous use of a SIP trunk interconnection and a SIP
trunk carrier connection or six SIP carriers at the same time is supported.
Limitations:
- Each profile requires a different number for every SIP trunk port set in PRG 84-14-06.
- Six carriers must be connected using a single route. The system only supports one gateway.
- Only one DNS server can be set for the SL2100 to connect to six different SIP Carriers.
7-2 SIP Trunking

ISSUE 1.0 SL2100
• The NEC SL2100 system restricts an outgoing call under the following conditions:
- SIP configuration failed
- SIP registration failed
- CPU-C1/VOIPDB daughter board link down
- Lack of VOIPDB DSP resource
- Lack of bandwidth
3.1.2 SIP Trunking Setup
Use the following steps to initially set up SIP Trunking for the NEC SL2100 system:
1. By default, the NEC SL2100 is assigned a static IP address and runs behind a NAT router.
When using an NEC SL2100 on a LAN behind an NAPT router, forward port 5060 to the IP address of
the NEC SL2100 CPU-C1 (commonly called the SL2100 CPU) since the signaling is handled by the
CPU-C1. Then, since the media stream (the speech) uses a large range of ports for the RTP packages,
forward the ports (10020~10083) to the IP address of the VOIPDB. Or, use the DMZ option for the
VOIPDB. This means that the VOIPDB is not actually behind the firewall. This is achieved by
connecting the VOIPDB to a physical or virtual DMZ port. You can also achieve the same result by
port forwarding 10020 to 10083.
2. Define the SIP Carrier account information (user name, password, domain name/IP address to
the provider).
3. Define the trunk ports as SIP.
4. Set the Expire Time.
SECTION 4 SIP TRUNK OVERVIEW

This section is an overview of basic SIP trunk behavior, protocols, supported SIP trunking methods
and options, supported CODEC as well as other supported functions of SIP Trunking.
4.1 General Information

The NEC SL2100 SIP Trunks behave like some SIP User Agents (UA). UA is the client application
used with a particular network protocol.
The NEC SL2100 provides a maximum of 31 register IDs and can register these IDs with any SIP
server.
A maximum number of 128 SIP trunks can be used with the NEC SL2100 system. The maximum
number of simultaneous VoIP calls is determined by the number of resources available on the
VoIPDB.
The NEC SL2100 can connect any SIP server over a NAPT router by one static global IP address.
The NEC SL2100 system supports a DNS resolution access and an IP address direct access for SIP
servers and supports the sub-address feature with SIP trunk interconnection.
4.2 Supported Protocols

The following protocols are supported:
• SIP (RFC2543 bis04)
• SIP RFC3261 Supported [updated version of RFC2543]
• The SIP stack has been updated from RFC2543 Base to RFC3261 Base
• SDP

SL2100 ISSUE 1.0
• RTP/RTCP
• UDP
• IPv4
• T.38 (draft-ietf-sipping-realtimefax-02.txt)
4.3 Supported SIP Methods

The following SIP methods are supported with the NEC SL2100 system:
• REGISTER
• INVITE
• BYE
• CANCEL
• ACK
• PRACK
• Response 1xx 2xx, 3xx, 4xx, 5xx, 6xx
The following features are available:

• Support the 401 response for the Initial Invite
If 401 message is sent for the Initial Invite, with previous software, the system cannot respond to the
message correctly.
• Support the 401/407 response for the Invite of Session Timer
If 401/407 response is sent for the invite of Session Timer, the system can send the Invite message
with Authentication header.
• Support the 128 byte size of Nonce max value sent by the 401/407 message
The Nonce maximum size sent by the 401/407 message is expanded to 128 byte. With previous
software, 64 byte size can be received.
4.4 Supported SIP Trunking Options

The options listed below are supported with SIP Trunking.
• 100rel
• Session Timer
• Early Media
4.5 Supported CODEC

SIP Trunking can use the following CODECs.
• G.729. Low bandwidth requirement, and is used on most Wide Area Network links.
- VAD
- VIF size 20ms~30ms
• G.711 – High bandwidth requirement – usually used on Local Area Networks.
• G.722 – This CODEC is useful in fixed network, Voice over IP applications, where the required
bandwidth is typically not prohibitive.
• G.726 – is an ITU-T ADPCM speech coded standard covering the transmission of voice at rates of
16, 24, 32, and 40Kbps.
SECTION 5 SUPPORTED SIP TRUNKING FUNCTIONS

The functions in this section are supported by NEC SL2100 SIP Trunking.
7-4 SIP Trunking

ISSUE 1.0 SL2100
5.1 Address Resolution

If using any SIP Proxy Server, the NEC SL2100 always sends messages to an external SIP server.
If not using any SIP Proxy Server, the NEC SL2100 uses the internal address table (Program 10-23 :
SIP System Interconnection Setup).
When a user creates an interconnection network with SIP trunks, Program 10-29-14 : SIP Server
Information Setup - SIP Carrier Choice must be set to 0 (default).
5.2 Authentication Process

When using an external SIP Server provided by a carrier, an authentication process is usually needed.
NEC SL2100 SIP trunks support HTTP digest authentication process (MD5). This process is done on
a Register process and Initial INVITE process.
5.3 Caller ID
Caller ID for SIP Trunks is set by Program 21-17 : IP Trunk (SIP) Calling Party Number Setup for
Trunk.
Caller ID for SIP Extensions is Program 21-19 : IP Trunk (SIP) Calling Party Number Setup for
Extension.
Programs follow program priority as follows: 21-19 > 21-17 > 10-36-02
With a trunk-to-trunk transfer and Trunk-to-Trunk Outgoing Caller ID Through Mode enabled (Program
14-01-24), the Caller ID/sub-address (received from the incoming trunk) is sent. If a SIP trunk is
connected to any SIP carrier, the sub-address is not transferred.
Calling Party Name is not provided for outgoing calls on SIP trunks.
5.4 Carrier Support

If a common carrier supports SIP, the NEC SL2100 can connect:
• the SIP Carrier
• the outgoing call to the PSTN network
• the common IP network via an NEC SL2100 SIP trunk.
A conformity test with a carrier’s SIP server is recommended.
5.5 Early Media

When the NEC SL2100 receives the response 18x w/SDP and the CODEC negotiation is a success,
the NEC SL2100 starts to send/receive RTP packets.
5.6 Fault Tolerance

When the NEC SL2100 uses an external SIP Server and if the registration process fails, the NEC
SL2100 blocks outgoing calls with SIP trunks. All SIP trunk ports are placed into a busy status.
If the NEC SL2100 has trunk groups that include both SIP trunks and ISDN trunks, and all SIP trunks
are busy, a user can make an outgoing call using an ISDN trunk as a bypass.

SL2100 ISSUE 1.0
5.7 Network Address Port Translation (NAPT)

NEC SL2100 SIP trunk can pass through a NAPT router. The related system data is Program
10-12-06 : CPU-C1 Network Setup – NAPT Router (On/Off) and Program 10-12-07 : CPU-C1
Network Setup – NAPT Router IP Address (do not set with a dynamic router IP address).
Incorrect settings with these two programs can cause one-way audio problems.
The WAN global IP is set in the system data by the user or automatically using the NAT traversal
feature (UPnP). The related system data is 10-37-01 : UPnP Setup – UPnP Mode (On/Off) and
10-37-02 : UPnP Setup – UPnP Interval (polling timer).
5.8 Quality of Service (QoS)

NEC SL2100 SIP trunks support Type of Service (ToS) (Program 84-10 : ToS Setup, protocol type =
9 (SIP Trunk).
5.9 Registration
5.9.1 Registration Process
When the NEC SL2100 system registers its own IDs with an external SIP server, the following system
data are sent:
Register ID # User ID Authentication ID Authentication Password

Register ID 0 10-36-02 10-36-03 10-36-04
Register ID 1 10-36-02 10-36-03 10-36-04
: 10-36-02 10-36-03 10-36-04
:
Register ID 31 10-36-02 10-36-03 10-36-04
The NEC SL2100 sends the REGISTER Message when the system starts up, register timer expires,
CPU LAN links and recover timer expires.
5.9.2 Registration Recover Process
The NEC SL2100 has a registration recovery process for registration failure. When a registration fails,
the NEC SL2100 sets an internal recover timer. When the timer expires, the NEC SL2100 sends a
REGISTER message per register ID again.
The recover timer is either five minutes or 30 minutes. Typically, five minutes is used.
SECTION 6 SIP TRUNK PROGRAMMING

6.1 SIP Trunk Basic Setup
Program/ Description/ Assigned Data Comments

Item No. Selection
10-28-01 SIP System Information Set- 64 characters maximum Define the domain name. This informa-
up – Domain Name Default not assigned tion is generally provided by the SIP
carrier.
Select SIP Profile 1-6.
7-6 SIP Trunking

ISSUE 1.0 SL2100

Item No. Selection
10-28-02 SIP System Information Set- 48 characters maximum Define the Host name. This informa-
up – Host Name Default not assigned tion is generally provided by the SIP
carrier.
10-28-03 SIP System Information Set- 0 = UDP Define the Transport type. This option
up – Transport Protocol 1 = TCP will always be set to UDP.
2 = TLS
Default = 0
10-28-05 SIP System Information Set- 0 = IP Address Define the Domain Assignment. This
up – Domain Assignment 1 = Domain Name entry is determined by what informa-
Default = 0 tion the SIP carrier provides. If the SIP
carrier provides a server name:
Select SIP Profile 1-6. SIPconnect-sca@L0.cbeyond.net
the domain would be:
@L0.cbeyond.net
and the host name would be:
SIPconnect-sca.
10-29-14 SIP Server Information Setup 0 = Default Define the SIP Carrier Choice.
– SIP Carrier Choice 1 = Carrier A
2 = Carrier B
3 = Carrier C
4 = Carrier D
5 = Carrier E
6 = Carrier F
7 = Carrier G
8 = Carrier H
9 = Carrier I
10 = Carrier J
11 = Carrier K
12 = Carrier L
13 = Carrier M
14 = Carrier N
15 = Carrier O
16 = Carrier P
17 = Carrier Q
18 = Carrier R
19 = Carrier S
20 = Carrier T
21 = Carrier U
22 = Carrier V
23 = Carrier W
24 = Carrier X
25 = Carrier Y
26 = Carrier Z
Default = 0
10-68-01 IP Trunk Availability – Trunk 0 = None Assign the trunk type as (1) SIP.
Type 1 = SIP
2 = H.323
3 = Reserved
10-68-02 IP Trunk Availability – Start 0~128 Assign the Start Port for your SIP
Port trunks.
10-68-03 IP Trunk Availability – Num- 0~128 Assign the number of SIP port trunks.
ber of Port
14-18-05 IP Trunk Data Setup – SIP 1 = Profile 1 Define the SIP profile for each SIP
Profile (SIP Only) 2 = Profile 2 trunk.
3 = Profile 3
4 = Profile 4
5 = Profile 5
6 = Profile 6
Default = 1

SL2100 ISSUE 1.0

Item No. Selection
22-02-01 Incoming Call Trunk Setup 0 = Normal Define the SIP trunks as type 3 (DID).
1 = VRS (second dial tone if no VRS In addition to the SIP trunk program-
installed) ming, refer to the Direct Inward Dialing
2 = DISA (DID) feature in the NEC SL2100 Fea-
3 = DID tures and Specifications Manuals and
4 = DIL the NEC SL2100 Programming Man-
5 = Tie line ual for detailed information.
6 = Delayed VRS
7 = ANI/DNIS
8 = DID Mode Switching
Default = 0
6.2 IP DSP Resource

If any IP Address or NIC settings are changed, the system must be reset for the changes to take affect.

Item No. Selection
10-03-01 VoIPDB Configuration – Log- 0 ~ 128 The CPU-C1 automatically assigns
ical Port Number each blade during installation. READ
ONLY
10-03-02 VoIPDB Configuration – 0 = H.323 Assign each trunk type for each DSP
Trunk Type 1 = SIP Resource.
Default = 1
10-19-01 VoIP DSP Resource Selec- 0 = Commonly used for both IP Exten- Define the criteria for each DSP re-
tion –VoIP DSP Resource sions and Trunks source on the VoIP blade.
Selection 1 = Use for IP Extensions
2 = Use for SIP Trunks
5 = Blocked
6 = Common without Unicast Paging
7 = Multicast Paging
8 = Unicast Paging
Default:
Resource 1 = 1
Resources 2~128 = 0
14-05-01 Trunk Group Trunk Group = 0~50 Default priorities for trunks 1~128 is
Priority = 1 ~ 128 1~128.
Default = Group1 for all trunk ports Assign Trunks to Trunk Groups/
and priorities Outbound Priority
22-02-01 Incoming Call Trunk Setup 0 = Normal Set the feature type for the trunk you
1 = VRS (second dial tone if no VRS are programming.
installed) (Second dial tone for option 1 if no
2 = DISA VRS is installed)
3 = DID
4 = DIL
5 = Tie line
6 = Delayed VRS
7 = ANI/DNIS
8 = DID Mode Switching
Default = 0
84-26-01 VoIP Basic Setup – IP Ad- XXX.XXX.XXX.XXX Assign the VOIPDB Gateway IP Ad-
dress dress.
172.16.0.20
84-26-02 VoIP Basic Setup – RTP Port 0 ~ 65534 Default: 10020
Number
84-26-03 VoIP Basic Setup – RTCP 1 ~ 65535 Default: 10021
Port Number
(RTP Port Number + 1)
7-8 SIP Trunking

ISSUE 1.0 SL2100
6.3 SIP Caller ID
Program/Item Description/ Assigned Data Comments

No. Selection
14-01-24 Basic Trunk Data Setup – 0 = Disable Enable/Disable the Trunk-to-
Trunk-to-Trunk Outgoing Caller 1 = Enable Trunk Outgoing Caller ID
ID Through Mode Default = 0 Through Mode. This option al-
lows Caller ID from the original
outside caller to be displayed
when a trunk is forwarded off
premise. This option can be used
only with PRI and SIP trunks.
21-17-01 IP Trunk (SIP) Calling Party 1 ~ 0, *, # (to equal up to 16 digits) This program assigns the Caller
Number Setup for Trunk Default not assigned Party Number for each IP trunk.
The assigned number is sent to
the central office when the caller
places an outgoing call. If the
Calling Party Number is assigned
by both 21-17 and 21-18/21-19,
the system uses the entry in
21-18/21-19.
21-19-01 IP Trunk (SIP) Calling Party 1 ~ 0, *, # (to equal up to 16 digits) Assign the Calling Party Number
Number Setup for Extension Default not assigned for each extension. The assigned
number is sent to the central of-
Select SIP Profile 1-6. fice when the caller places an
outgoing call. If the Calling Party
Number is assigned by both Pro-
gram 21-17 and 21-18/21-19, the
system uses the data in Program
21-18/21-19.
6.4 SIP CODEC Trunk

No. Selection
84-13-01 SIP Trunk CODEC Information 1 = 10ms Set the G.711 Audio Frame Num-
Basic Setup – G.711 Audio 2 = 20ms ber.
Frame Number 3 = 30ms
4 = 40ms
Default is 2
84-13-02 SIP Trunk CODEC Information 0 = Disable Enable/Disable the G.711 VAD
Basic Setup – G.711 Voice Ac- 1 = Enable Detection Mode.
tivity Detection Mode Default is 0
84-13-03 SIP Trunk CODEC Information 0 = A-law Define the G.711 type.
Basic Setup – G.711 Type 1 = μ-law
Default is 1
84-13-04 SIP Trunk CODEC Information 0 ~ 255ms Set the minimum G.711 Jitter
Basic Setup - G.711 Jitter Buf- Default is 20 Buffer.
fer (min)
84-13-05 SIP Trunk CODEC Information 0 ~ 255ms Set the average G.711 Jitter Buf-
Basic Setup – G.711 Jitter Buf- 40ms = Default is 40 fer.
fer (average)

SL2100 ISSUE 1.0

No. Selection
84-13-06 SIP Trunk CODEC Information 0 ~ 255ms Set the maximum G.711 Jitter
Basic Setup – G.711 Jitter Buf- Default is 80 Buffer.
fer (max)
84-13-07 SIP Trunk CODEC Information 1 = 10ms Set the G.729 Audio Frame Num-
Basic Setup – G.729 Audio 2 = 20ms ber.
Frame Number 3 = 30ms
4 = 40ms
5 = 50ms
6 = 60ms
Default is 2
84-13-08 SIP Trunk CODEC Information 0 = Disable Enable/Disable the G.729 VAD
Basic Setup – G.729 Voice Ac- 1 = Enable Detection Mode.
tivity Detection Mode Default is 0
84-13-09 SIP Trunk CODEC Information 0 ~ 300ms Set the minimum G.729 Jitter
Basic Setup –G.729 Jitter Buf- Default is 20 Buffer.
fer (min)
84-13-10 SIP Trunk CODEC Information 0 ~ 300ms Set the average G.729 Jitter Buf-
Basic Setup – G.729 Jitter Buf- Default is 40 fer.
fer (average)
84-13-11 SIP Trunk CODEC Information 0 ~ 300ms Set the maximum G.729 Jitter
Basic Setup – G.729 Jitter Buf- Default is 80 Buffer.
fer (max)
84-13-17 SIP Trunk CODEC Information 1 = Static Set the Jitter Buffer Mode.
Basic Setup – Jitter Buffer 3 = Self adjusting
Mode Default is 3
84-13-18 SIP Trunk CODEC Information Entries 0 ~ 30 (-20dBm~10dBm) Set the VAD (voice activity detec-
Basic Setup – VAD Threshold 1 = -19dB (-49dBm) tion) threshold.
:
20 = 0dB (-30dBm)
:
29 = 9dB (-21dBm)
30 =10dB (-20dBm)
Default is 20
84-13-28 SIP Trunk CODEC Information 0 = G.711_PT Define the CODEC Priority.
Basic Setup – Audio Capability 1 = Not Used
Priority 2 = G.729_PT
3 = G.722
4 = G.726
5 = Not Used
6 = G.711 Only
7 = G.729 Only
Default is 0
7-10 SIP Trunking

ISSUE 1.0 SL2100

No. Selection
84-13-33 SIP Trunk CODEC Information 1~4
Basic Setup – Number of G. 1 = 10ms
722 Audio Frames 2 = 20ms
3 = 30ms
4 = 40ms
Default is 3
84-13-35 SIP Trunk CODEC Information 0~300ms

Basic Setup – G.722 Jitter Buf- Default is 30
fer (min)
84-13-36 G.722 Jitter Buffer (average) 0~300ms

Default is 60
84-13-37 G.722 Jitter Buffer (max) 0~300ms

Default is 120
84-13-38 Number of G.726 Audio 1 = 10ms

Frames 2 = 20ms
3 = 30ms
4 = 40ms
Default is 3
84-13-39 G.726 VAD Mode 0 = Disable

1 = Enable
Default is 0
84-13-40 G.726 Jitter Buffer (min) 0~300ms

Default is 30
84-13-41 G.726 Jitter Buffer (average) 0~300ms

Default is 60
84-13-42 G.726 Jitter Buffer (max) 0~300ms

Default is 120
84-13-49 RTP Filter 0 = Disable Set the FAX Relay Mode.

1 = IP
2 = IP + SSRC
Default is 1
84-33-01 FAX Relay Mode 0 = Disable

1 = Enable
2 = Each Port Mode
Default is 0

SL2100 ISSUE 1.0

No. Selection
84-33-02 T.38 Protocol mode 0 = R/U
1 = U/R
2 = RTP
3 = UDPTL
Default is 1
84-33-05 T.38 RTP Format Payload 96 ~ 127

Number Default is 100
84-33-06 T.38 FAX Max Speed 0 = V.27ter: 4800 bps

1 = V.29: 9600 bps
2 = V.17: 14400 bps
Default is 2
84-33-08 T.38 Error protection depth for 0~2

Signaling Default is 0
84-33-09 T.38 Error protection depth for 0~2

Data Default is 0
84-33-10 T.38 TCF Method 1 = VOIPDB

2 = G3FE
Default is 1
84-13-65 VAD Negotiation on SDP 0 = Disable

1 = Enable
Default is 0
84-13-66 Voice Band Data (VBD) 0 = Disable

1 = Enable
Default is 0
84-13-67 VBD Payload Type 96 ~ 127

Default is 97
84-34-01 DTMF Relay Mode 0 = Disable

1 = RFC2833
2 = H.245
Default is 0
84-34-02 DTMF Payload Number 96 ~ 127

Default is 110
7-12 SIP Trunking

ISSUE 1.0 SL2100
6.5 SIP NAPT Router Setup

No. Selection
10-12-07 CPU Network Setup – NAPT 0.0.0.0 ~ 126.255.255.254 Set the NAPT Router IP address.
Router IP Address 128.0.0.1 ~ 191.254.255.254 With SIP trunking, the IP address
192.0.0.1 ~ 223.255.255.254 of the WAN side of the router
Default is 0.0.0.0 must be entered.
10-12-08 CPU Network Setup – ICMP 0 = Disable Enable/Disable ICMP (Internet
Redirect 1 = Enable Control Message Protocol) Redi-
Default is 0 rect.
6.6 SIP System Interconnection Setup

No. Selection
10-23-01 SIP System Interconnection 0 = Disable Enable/Disable system intercon-
Setup – System Interconnec- 1 = Enable nection.
tion Default is 0
10-23-02 SIP System Interconnection 0.0.0.0 ~ 126.255.255.254 Define the IP address of another
Setup – IP Address 128.0.0.1 ~ 191.255.255.254 system.
192.0.0.1 ~ 223.255.255.254
Default is 0.0.0.0
10-23-04 SIP System Interconnection Up to 12 digits (0 ~ 9) Determine another system call
Setup – Dial Number Default not assigned control port number.
6.7 SIP Protocol

No. Selection
84-14-06 SIP Trunk Basic Information 1 ~ 65535 Set the SIP UA (User Authorized)
Setup – SIP Trunk Port Num- Default is 5060 = Profile 1 Trunk port number (Receiving
ber 5062 = Profile 2 Transport for NEC SL2100 SIP).
5090 = Profile 3
5092 = Profile 4
5094 = Profile 5
5096 = Profile 6
84-14-07 SIP Trunk Basic Information 0 ~ 65535 seconds Set the Session Timer Value.
Setup – Session Timer Value Default is 0 0 means session timer is Off
84-14-08 SIP Trunk Basic Information 0 ~ 65535 seconds Set the Minimum Session Timer
Setup – Minimum Session Tim- Default is 1800 Value.
er Value
84-14-09 SIP Trunk Basic Information 0 = Request URI Set the Called Party Information.
Setup – Called Party Informa- 1 = To Header
tion Default is 0

SL2100 ISSUE 1.0

No. Selection
84-14-10 SIP Trunk Basic Information 0 = SIP-URL
Setup – URL Type 1 = TEL-URL
Default is 0
84-14-11 SIP Trunk Basic Information 0 = Proxy Server Domain

Setup – URL/To HeaderSetting 1 = SIP UA Domain
Information Default is 0
84-14-15 SIP Trunk Basic Information 0 = Use Default Settings (100rel in-
Setup – 100rel Settings cluded)
1 = Use Opposite Settings (100rel
not included)
Default is 0
6.8 SIP Server Information Setup

No. Selection
10-29-01 SIP Server Information Setup – 0 = Off Define the SIP Proxy setup, De-
Default Proxy (Outbound) 1 = On fault Proxy (Outbound).
Default is 0 When SIP trunking is used, this
must be on.
Select SIP Profile 1-6. If entries are made in Program
10-29-xx for a SIP Server and the
SIP Server is then removed or
not used, the entries in Program
10-29-xx must be set back to
their default settings. Even if
10-29-01 is set to 0, the NEC
SL2100 still checks the settings
in the remaining 10-29 programs.
10-29-02 SIP Server Information Setup – 0 = Off Define the Default Proxy (in-
Default Proxy (Inbound) 1 = On bound).
Default is 0
10-29-03 SIP Server Information Setup – 0.0.0.0 ~ 126.255.255.254 Enter the default Proxy IP Ad-
Default Proxy IP Address 128.0.0.1 ~ 191.255.255.254 dress if the SIP carrier is using an
192.0.0.1 ~ 223.225.255.254 IP Address for the Proxy. In most
Default is 0.0.0.0 cases, this is left at the default
entry as the domain name is
Select SIP Profile 1-6. used.
10-29-04 SIP Server Information Setup – 0 ~ 65535 Define the Proxy Port Number.
Default Proxy Port Number Default is 5060
10-29-12 SIP Server Information Setup – 64 characters maximum Define the Proxy Domain Name
Proxy Domain Name Default not assigned (NEC SL2100 domain name).
7-14 SIP Trunking

ISSUE 1.0 SL2100

No. Selection
10-29-13 SIP Server Information Setup – 48 characters maximum Define the Proxy Host name
Proxy Host Name Default not assigned (NEC SL2100 proxy name).
6.9 SIP Registrar Setup

No. Selection
10-29-05 SIP Server Information Setup – 0 = None Define the Registrar Mode. This
Registrar Mode 1 = Manual should always be set to manual
Default is 0 when using SIP trunking.
10-29-06 SIP Server Information Setup – 0.0.0.0 ~ 126.255.255.254 Define the Registrar IP Address. The
Registrar IP Address 128.0.0.1 ~ 191.255.255.254 carrier may provide an IP address. In
192.0.0.1 ~ 223.255.255.254 most cases, a domain name will be
Default is 0.0.0.0 used so this entry will be left at the
default.
10-29-07 SIP Server Information Setup – 0 ~ 65535 Define the Registrar Port Numbers.
Registrar Port Number Default is 5060
10-29-11 SIP Server Information Setup – 128 characters maximum Define the Registrar Domain Name
Registrar Domain Name Default not assigned (normally provided by the SIP carri-
er).
Select SIP Profile 1-6. Example:
SIPconnect-sca@L0.cbeyond.net
10-29-15 SIP Server Information Setup – 120 ~ 65535 seconds Define the Registration Expire time –
Registration Expiry (Expire) Default is 3600 the time allowed to register with the
Time SIP carrier.
Select SIP Profile 1-6. This should stay at the default entry.
10-29-20 Authentication Trial 0~9

0 = No Authentication
Default is 1 (1 Authentication At-
tempt)
10-29-21 NAT Router 0 = Disabled

1 = Enabled
Default is 0

SL2100 ISSUE 1.0
6.10 SIP Server Status

Item No. Selection
90-10-01 System Alarm Setup – Alarm 14 - CPU-LAN Link Error (IP Layer 1) Define alarms 14
Alarm Type Assign a Major or Minor alarm status for the LAN link. This and 60.
program also assigns whether or not the alarm is displayed to
a key telephone and whether or not the alarm information is
reported to the predefined destination.
Alarm 60 - SIP Registration Error Notification
Assign a Major or Minor alarm status for the SIP Registration
Error. This program also assigns whether or not the alarm is
displayed to a key telephone and whether or not the alarm in-
formation is reported to the predefined destination.
6.11 SIP Trunk Registration Information Setup

No. Selection
10-36-01 SIP Trunk Registration Infor- 0 = Disable Enable/Disable the SIP trunk reg-
mation Setup – Registration 1 = Enable istration.
Default is 0
10-36-02 SIP Trunk Registration Infor- 32 characters maximum Define the user ID.
mation Setup – User ID Default not assigned
10-36-03 SIP Trunk Registration Infor- 64 characters maximum Define the authentication user ID.
mation Setup – Authentication Default not assigned
User ID
10-36-04 SIP Trunk Registration Infor- 32 characters maximum Define the authentication pass-
mation Setup – Authentication Default not assigned word.
Password
6.12 SIP UPnP

No. Selection
10-37-01 UPnP Setup – UPnP Mode 0 = Disable Determine whether UPnP (Universal
1 = Enable Plug and Play) task starts. If UPnP task
Default is 0 starts, it obtains a NAPT router WAN IP
Address by using NAT traversal and
saves it in Program 10-12-07 automati-
cally.
10-37-02 UPnP Setup – Retry Time 0~3600 UPnP (Universal Plug and Play) task
1~59 cannot be used. tries to obtain the WAN IP Address of
Default is 60 the NAPT router at the interval defined
in this option.
7-16 SIP Trunking

ISSUE 1.0 SL2100
SECTION 7 SIP TRUNK E.164 SUPPORT

7.1 Description
With SIP Trunk E.164 Support enabled, the PBX is able to support SIP configurations where the
number presentation within the SIP messages is formatted using the E.164 international numbering
scheme. Specifically the system is able to handle the + digit when required as the International Access
Code.
For example, a normal international SIP call can be dialed and displayed as follows:
Number dialed = 00441202223344
Request-URI: Invite sip: 00441202223344@172.16.18.100 SIP/2.0
With SIP Trunk E.164 Support enabled, the SIP call can be displayed once dialed as:
Request-URI: Invite sip:+441202223344@172.16.18.100 SIP/2.0
This display is a requirement of certain SIP ITSPs (Internet Telephony Service Providers) and may
require that PBX handle these calls and modify any SIP messages to the correct format accordingly.
This feature uses the following SIP header fields:
To
From
P-Asserted Identity
P-Preferred Identity
7.1.1 Condition
• E.164 support is applied on the SIP trunk interface.

• E.164 is supported for all carrier choices (Program 10-29-14).
• Netlink multi-carrier support uses E.164 support across all carrier configurations at the secondary
nodes.
7.1.2 Default Settings
Disabled
7.2 System Availability

7.2.1 Terminals
All Multiline Terminals
7.2.2 Trunks
IP SIP
7.2.3 Required Component(s)
IP7( )-CPU-C1

SL2100 ISSUE 1.0
IP7WW-VoIPDB-C1
SL2100 IP CHANNEL-16 LIC
SL2100 IP TRUNK-01 LIC
7.3 Programming
Program Program Name/Description Input Data Assigned Data Level

Number
1 2 3
10-02-01 Location Setup – Country Code Dial (maximum of four digits) 1 ✓
Enter the country code. 0 ~ 9, *, #
10-02-02 Location Setup – International Ac- Dial (maximum of four digits) No Setting ✓
cess Codes 0 ~ 9, *, #
Enter the international access
code.
44-01-02 System Options for ARS/F-Route Dial (maximum of one digit) No Setting ✓
– Dial Tone Simulation 0 ~ 9, *, # cannot be used Profile
Dial digits to be analyzed by the (1 ~ 6)
system. Numbering plan for the di-
al needs to be configured as F-
Route in Program 11-01.
44-01-03 System Options for ARS/F-Route 0 = Internal Dial Tone 0 ✓
– Tone Type 1 = External Dial Tone
Set simulated DT to type which
can change the tone used in Pro-
gram 44-01-02 and Program
44-02-04.
84-14-13 SIP Trunk Basic Information Setup 0 = Off 0 ✓
– Incoming/ Outgoing SIP Trunk 1 = Mode 1
for E.164 2 = Mode 2
When this data is set to 1, then for 3 = Mode 3
any outbound SIP calls a + is add- Profile (1 ~ 6)
ed as a prefix to the Request-URI,
To and From header fields of the
SIP message.
When it is set to 2 then if the di-
aled international access code
matches the value in Program
10-02-02 this value is removed
from the number dialed and the +
added as a prefix to the Request-
URI, To and From header fields of
the SIP Message.
7.4 Operation
7.4.1 To Transfer a Call into a Conference:
1. While on a call, press Hold key.

2. Dial the Transfer to Conference service code (PRG 11-12-58, default = 624).
If the telephone does not have the proper COS, a warning tone is sent. After the user hangs up, the
system automatically places a Callback to the extension.
The display shows the line Number, Number/Name and Extension Name/Number.
7-18 SIP Trunking

ISSUE 1.0 SL2100
3. Dial the extension number or press a DSS key of a telephone in a Conference call.
If an error tone is heard, Barge-In is disable for the extension and the call cannot go through. Retrieve
the call by pressing the flashing line Key or hang up and the call recalls the extension.
When the call is transferred into the Conference, an intrusion tone is heard by all parties in the
conference, depending on the entries in PRG 20-13-17 and PRG 80-01, and all display Multiline
Terminals show the joined party.
To cancel the transfer, press the flashing line Key to retrieve the call.
4. Hang up.
SECTION 8 SIP TRUNK E.164 CLIP ENHANCEMENT

8.1 Description
With SIP Trunk E.164 Support enabled, the PBX is able to support SIP configurations where the
number presentation within the SIP messages is formatted using the E.164 international numbering
scheme. Specifically the system is able to handle the + digit when required as the International Access
Code.
For example, a normal international SIP call can be dialed and displayed as follows:
Number dialed = 00441202223344
Request-URI: Invite sip: 00441202223344@172.16.18.100 SIP/2.0
With SIP Trunk E.164 Support enabled, the SIP call can be displayed once dialed as:
Request-URI: Invite sip:+441202223344@172.16.18.100 SIP/2.0
This display is a requirement of certain SIP ITSPs (Internet Telephony Service Providers) and may
require that PBX handle these calls and modify any SIP messages to the correct format accordingly.
This feature uses the following SIP header fields:
To
From
P-Asserted Identity
P-Preferred Identity
8.1.1 Condition
• E.164 support is applied on the SIP trunk interface.

• E.164 is supported for all carrier choices (Program 10-29-14).
• Netlink multi-carrier support uses E.164 support across all carrier configurations at the secondary
nodes.
Disabled

SL2100 ISSUE 1.0

8.2.1 Terminals
All Multiline Terminals
8.2.2 Trunks
IP SIP
IP7( )-CPU-C1
IP7WW-VoIPDB-C1
8.3 Programming

Number
1 2 3
10-02-01 Location Setup – Country Code Dial (maximum of four digits) 1 ✓
Enter the country code. 0 ~ 9, *, #
10-02-02 Location Setup – International Ac- Dial (maximum of four digits) No Setting ✓
cess Codes 0 ~ 9, *, #
Enter the international access
code.
10-02-03 Location Setup – Other Area Ac- Dial (maximum of four digits) 9
cess Code 0 ~ 9, *, #
Enter the other area access code.
84-14-13 SIP Trunk Basic Information Setup 0 = Off 0 ✓
– Incoming/ Outgoing SIP Trunk 1 = Mode 1
for E.164 2 = Mode 2
When this data is set to 1, then for 3 = Mode 3
any outbound SIP calls a + is add- Profile (1 ~ 6)
ed as a prefix to the Request-URI,
To and From header fields of the
SIP message.
When it is set to 2 then if the di-
aled international access code
matches the value in Program
10-02-02 this value is removed
from the number dialed and the +
added as a prefix to the Request-
URI, To and From header fields of
the SIP Message.
7-20 SIP Trunking

ISSUE 1.0 SL2100

Number
1 2 3
84-14-16 SIP Trunk Basic Information Setup 0 = Disable 0 ✓
– SIP Trunk SIP-URI E.164 Incom- 1 = Mode 1
ing Mode 2 = Mode 2
When this data is set to 1, then for Profile (1 ~ 6)
any inbound SIP calls that include
a + and a country code not defined
in Program 10-02-01, delete the +
and add the International Access
Code in Program 10-02-02. If the
country code is a match then de-
lete both the + and country code
but do not add the International
Access code.
When it is set to 2, then for any in-
bound SIP calls that include a +
and a country code not defined in
Program 10-02-01, delete the +
and add the International Access
Code in Program 10-02-02. If the
country code is a match then de-
lete both the + and country code
and add the Caller ID Edit Code
from Program 10-02-03.
8.4 Operation
8.4.1 Delete the + only from an incoming SIP INVITE using E.164 numbering scheme:
Table 7-1 Delete + from Incoming SIP INVITE
Program 84-14-16 Program 84-14-13 Description

0: Off 0: Off When a + is presented as the international access code in a SIP INVITE
Or for incoming calls then delete the + only.
1: On
<Example Output>
Incoming call from: +4902131795770
Displayed in terminal incoming caller history as:

SL2100 ISSUE 1.0
8.4.2 Delete and replace the + and matched country code from an incoming SIP
INVITE using E.164 numbering scheme:
Table 7-2 Delete + and Country Code from Incoming SIP INVITE

1: Mode 1 1: On With a SIP INVITE for incoming calls. When a + is presented as the inter-
national access code along with a country code that DOES NOT match the
value in Program 10-02-01, then delete the + and add the international ac-
cess code value in Program 10-02-02 only.
- Or -
With a SIP INVITE for incoming calls. When a + is presented as the inter-
national access code along with a country code that DOES match the val-
ue in Program 10-02-01, then delete the + and country code but DO NOT
add the international access code value.
<Example Output>
Program 10-02-02 = 00
Table 7-3 Delete + and Country Code from Incoming SIP INVITE

2: Mode 2 1: On With a SIP INVITE for incoming calls. When a + is presented as the inter-
national access code along with a country code that DOES NOT match the
value in Program 10-02-01, then delete the + and add the international ac-
cess code value in Program 10-02-02 only.
- Or -
With a SIP INVITE for incoming calls. When a + is presented as the inter-
national access code along with a country code that DOES match the val-
ue in Program 10-02-01, then delete the + and country code but DO NOT
add the international access code value.
<Example Output>
Program 10-02-02 = 00
Program 10-02-03 = 9
8.4.3 Making an outgoing call from history of incoming calls:
1. From an idle multiline terminal.

2. Press soft key List.
7-22 SIP Trunking

ISSUE 1.0 SL2100
3. Press soft key CID.

4. Press Speaker.
SECTION 9 SIP TRUNK KEEP ALIVE USING OPTION MESSAGE

9.1 Description
The SL2100 provides support for “SIP Trunk Keep Alive” using OPTION message for all six SIP
Profiles, applicable to both IP System Interconnection and SIP Carrier mode.
9.1.1 Condition
• OPTION Keep Alive works for all SIP Carrier Type (PRG 10-29-14).
• Program 10-29-19 must be enabled for making OPTION Keep Alive to work for SIP Carrier mode.
• Program 10-23-05 must be enabled for making OPTION keep alive to work for IP system
Interconnection mode.
• SL2100 sends the OPTION message at the interval of the value set in program 84-14-18.
• OPTION Keep Alive can be sent to the SIP carrier or IP system Interconnection of Net Link
Secondary System.
• OPTION Keep Alive Call Restriction and Alarm of Net Link Secondary System are not supported.
• If SL2100 does not receive the 200-OK response from the SIP server then SL2100 would retry
sending of OPTION message for 32 seconds.
None

9.2.1 Terminals
None
9.2.2 Trunks
SIP Trunks
IP7WW-VoIPDB-C1

SL2100 ISSUE 1.0
9.3 Programming
Program Program Name/Description Input Data Default

Number
10-23-05 SIP System Interconnection Setup – 0 = Disable 0
Keep Alive Mode for SIP 1 = Option Keep Alive Mode
Enable/Disable OPTION Keep Alive
Mode for IP system interconnection.
10-23-06 SIP System Interconnection Setup – 1 = Profile 1 1
SIP Profile 2 = Profile 2
Assign the Interconnection to a SIP Pro- 3 = Profile 3
file. 4 = Profile 4
5 = Profile 5
6 = Profile 6
10-29-19 SIP Server Information Setup – Keep 0 = Disable 0
Alive by OPTION Message 1 = Enable
Enable/Disable support of keep alive by Profile (1 ~ 6)
OPTION Message for SIP carrier mode.
84-14-18 SIP Trunk Basic Information Setup - 60 ~ 3600 (seconds) 180
Keep Alive by OPTION Interval Timer Profile (1 ~ 6)
Define Keep Alive by OPTION Interval
Timer.
SL2100 sends the OPTION message at
the interval of the value set in this pro-
gram.
84-14-19 SIP Trunk Basic Information Setup - 1~5 1
Keep Alive by OPTION Fail Limit Profile (1~6)
Define Keep Alive by OPTION fail limit.
84-14-20 SIP Trunk Basic Information Setup - Max. 32 String ping
Option Keep Alive User ID Profile (1 ~ 6)
Define Option Keep Alive User ID which
is set in SIP URL of OPTION message.
9.4 Operation
None
7-24 SIP Trunking

DHCP Client
SECTION 1 DHCP CLIENT 8
Warning: When the VoIPDB is installed on the CPU, the built-in LAN port on the CPU becomes
disabled. Only the LAN port on the VoIPDB is operational.
DHCP client function is applicable to the CPU LAN port only. This function is enabled by default. If
DHCP Client
VoIPDB is installed then CPU LAN port will be disabled and DHCP client function will not be used
even if it is enabled.
The system can receive the following information from the DHCP server: IP Address, Subnet Mask,
and Default Gateway.
1.1 Conditions
• DHCP client function only applies to the CPU LAN port and is applicable only when VoIPDB is not
installed.
• The CPU LAN port will receive the IP address information from DHCP server without having to
reboot.
• PRG 10-12-13 and PRG 10-12-14 are not populated by DHCP assignment.
• It is mandatory to disable PRG 10-63-01 to change PRG 10-12-01 and PRG 10-12-02 manually.
• It is mandatory logout from WebPro after applying changes so as to write those changes.
• The DHCP Server should be configured to provide the system the same IP address every time. For
example in the DHCP server extend the lease time to infinite or setup the server to provide the
same IP address based on the systems MAC Address.
• DHCP client can set following programs automatically; however other IP related programs (such as
PRG 84-26) have to set manually as required.
- IP Addresses: PRG 10-12-01 (CPU)
- Subnet Masks: PRG 10-12-02 (CPU)
- Default Gateway: PRG 10-12-03
• DHCP Client (PRG 10-63) and existing DHCP Server feature (PRG 10-13) can not be used at the
same time.
1.2 Default Settings

Enabled

IP7[ ]-CPU-C1
IP7WW-VOIPDB-C1

SL2100 ISSUE 1.0
1.4 Guide to Feature Programming
Program Program Name Description/Comments Assigned Data Level

Number
1 2 3
10-63-01 DHCP Client Setting - DHCP Enable/disable the DHCP Client 0 = Disable ✓
Client Mode feature. 1 = Enable
(default = 1)
10-12-01 CPU Network Setup - IP Ad- Assigns the IP address of the CPU 192.168.0.10 ✓
dress card.
10-12-02 CPU Network Setup - Subnet Assigns the Subnet Mask of the 255.255.255.0 ✓
Mask CPU card.
10-12-03 CPU Network Setup – Default Assign the default gateway IP ad- 0.0.0.0 ~ ✓
Gateway dress for the CPU. 126.255.255.254
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
(default = 0.0.0.0)
10-12-09 CPU Network Setup – VoIP IP Set for VoIPDB. 0.0.0.0 ~ ✓
Address 126.255.255.254
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
(default = 172.16.0.10)
10-12-10 CPU Network Setup – Subnet Define the Media Gateway Subnet 128.0.0.0 ✓
Mask-VoIPDB Mask Address. 192.0.0.0
224.0.0.0
240.0.0.0
248.0.0.0
252.0.0.0
254.0.0.0
255.0.0.0
255.128.0.0
255.192.0.0
255.224.0.0
255.240.0.0
255.248.0.0
255.252.0.0
255.254.0.0
255.255.0.0
255.255.128.0
255.255.192.0
255.255.224.0
255.255.240.0
255.255.248.0
255.255.252.0
255.255.254.0
255.255.255.0
255.255.255.128
255.255.255.192
255.255.255.224
255.255.255.240
255.255.255.248
255.255.255.252
255.255.255.254
255.255.255.255
(default = 255.255.0.0)
SECTION 2 DHCP SERVER CONFIGURATION EXAMPLE

The example below shows the necessary steps to add options to a Windows server so that the server
will provide the IP Address of the SL2100 (PRG 10-12-09).
8-2 DHCP Client

ISSUE 1.0 SL2100
1. In the DHCP Server, right click on the actual server and select Set Predefined Options.
Figure 8-1 DHCP - Set Predefined Options

SL2100 ISSUE 1.0
2. After clicking Set Predefined Options, a new window pops up. Select Add to create the new entry
for the SL2100 system. Once the option type window is available, assign the following
information:
• Name = SIP Server
• Data Type = Binary
• Code = 120
• Description = Any description you would like to enter
Figure 8-2 DHCP - Predefined Options and Values
8-4 DHCP Client

ISSUE 1.0 SL2100
3. In the DHCP server, select the scope of options for the DHCP scope that is being configured.
Right click on the Scope Options, and select Configure Options.
Figure 8-3 DHCP - Scope Options
4. In the Scope Options window, scroll down and place a check mark next to 120 SIP Server. Once
the server is added, the data field needs to be changed. In the Data Entry default delete the

SL2100 ISSUE 1.0
default value 00 and add the IP address of the SL2100 system as a Hex value preceded by a 01,
for the first SIP server. Listed is an example of what data is to be entered:
• 01 = 1st SIP Server
• AC = Hex for 172
• 10 = Hex for 16
• 00 = Hex for 0
• 0A = Hex for 10
This tells the system that the first SIP server’s IP address is: 172.16.0.10. Once assigned, click on
Apply to update the DHCP server.
Figure 8-4 DHCP - Data Entry for 1st DHCP Server
8-6 DHCP Client

IP Multiline Station (SIP)
The NEC SL2100 system supports IP extensions. These telephones have the same look and
functionality as typical multiline telephones, but they are connected to the CPU via IP rather than by a
hardwired connection to a station card.
IP Multiline Station (SIP)

The following terminal is supported.
• IP7WW-8IPLD-C1 TEL
The voice quality of VoIP is dependent on variables such as available bandwidth, network latency and
Quality of Service (QoS) initiatives, all of which are controlled by the network and Internet Service
Providers. Because these variables are not in NEC control, it cannot guarantee the performance of the
user’s IP-based remote voice solution. Therefore, NEC recommends connecting VoIP equipment through a
local area network using a Private IP address.
SECTION 2 IP TO TDM CONVERSION

When an IP telephone calls a [ ]TXH-B1 multiline telephone, single line telephone or trunk, the speech
must be converted from IP to TDM (Time Division Multiplexing) technology. The VoIPDB daughter
board provides this function.
It is possible for 8IPLD IP Phones to talk directly to other 8IPLD IP Phones without using a VoIP DSP
resource. For more information, refer to Peer-to-Peer on page 9-3.
2.1 8IPLD IP Multiline Telephones

The IP multiline telephone operates in the same way as a digital multiline telephone. It has all features
and flexibility you expect from a digital multiline telephone. The difference is that the IP telephone has
an RJ-45 for connection to an IP network, rather than an RJ-11 for connection to a digital extension
port.

SL2100 ISSUE 1.0
Figure 9-1 8IPLD Telephone
2.2 Conditions
When using 8IPLD IP phones, it is not recommended to assign the following features to a large
number of phones (16 or more):
• The same Trunk Line assignment (squared key system)
• The same Virtual Extension assignment
• Paging key with LED ON assignment
• The same location Park key
• The same BLF key assignment
• Day Night Mode Change key assignment
• The same VM Mail Box key assignment
• Trunk Group key
• Trunk Group All Line Busy Indication
• One call cannot ring more than 8 simultaneous IP extensions at the same time if the call originates
from a ring group or a virtual.
2.3 LAN Connection

As illustrated in Figure 9-2 Typical Network IP Connection on page 9-3, the IP telephone has two
RJ-45 connections on the back side marked PC and LAN. This allows the IP telephone and a PC to
share one cable run and switch/hub port.
9-2 IP Multiline Station (SIP)

ISSUE 1.0 SL2100
Ethernet
Straight-Thru IP7[ ]-4KSU-C1 Chassis
Cable
Therminal
LAN
PC Connection
Ethernet PC Straight-Thru CPU
Cable IP7WW-VOIPDB-C1
Figure 9-2 Typical Network IP Connection
If installing an IP telephone at a location that already has a PC connected to the data network, it is
possible to use either of the following methods:
• Use a different cable and complete the following steps:
- Leave the PC connected to the LAN.
- Patch a switch port to a new cable run.
- Connect a CAT 5 straight-through cable from the wall outlet to the LAN port on the IP telephone.
• Share the existing cable and complete the following steps:
- Unplug the cable from the PC network card (NIC).
- Connect that cable to the LAN port on the IP telephone.
- Connect a new straight-through patch lead from the PC NIC to the PC port on the IP telephone.
SECTION 3 PROVIDING POWER

IP telephones require power to function. This can be provided by PoE only.
3.1 Power Over Ethernet (PoE)

A PoE switch provides power over the spare pairs. The switch can be used with any device (not just IP
phones) and detects whether or not power is required. As all phones receive their power from one
device, it is easy to protect the IP phones from loss of power (by connecting the PoE switch to a UPS).
SECTION 4 PEER-TO-PEER
An IP telephone can send and receive RTP packets to or from another IP telephone without using
DSP resources on a VoIPDB. This operation supports only Intercom calls between the IP telephones.
If a 8IPLD IP multiline telephone or trunk line is required, a DSP resource is needed and a VoIPDB
must be installed. If a conference call is initiated while on a peer-to-peer call, the peer-to-peer
connection is released and a new non peer-to-peer connection is created using the VoIPDB. If the
third party drops out of the conversation, the call reverts to a peer-to-peer call. There is silence while
this conversion is made by the system.
Although the peer-to-peer feature is supported for IP Station-to-IP Station calls, the NEC SL2100
Chassis must still have a registered VoIPDB installed in the system.

SL2100 ISSUE 1.0
With Barge-In, a short silence may occur if the following occurs:

• Peer-To-Peer call receives a Barge-In without a Barge-In tone.
• Peer-To-Peer call receives a Barge-In with Monitor mode.
• Established Barge-In is disconnected.
• The Peer-to-Peer feature is a programmable feature that may be enabled or disabled by accessing
Data Program 15-05-50 - Peer-to-Peer Mode.
SECTION 5 PROGRAMMING
The first step to connecting IP telephones to the NEC SL2100 system is to connect the NEC SL2100
system to the customer data network. Refer to General IP Configuration on page 4-1. Next, program
the VoIPDB and associated IP telephone settings. To complete the installation, program the IP
telephone.
The programming commands required to complete this installation are located in Programming on
page 5-1. This section provides a brief description of the commonly used commands:
• 10-12-03 CPU Network Setup - Default Gateway
If required, select the default gateway IP address to use when using a router (default: 0.0.0.0).
• 10-12-09 CPU Network Setup - IP Address
Select the IP address for the IP connection
• 10-12-10 CPU Network Setup - Subnet Mask
Assign the subnet mask for the VoIPDB
• 15-05-50 Peer to Peer Mode
Enable/Disable the Peer-to-Peer feature between IP Stations.
Disabling this feature results in IP Station-to-IP Station calls using DSP Resources.
• 15-05-15 IP Telephone Terminal Basic Data Setup - CODEC Type

For each IP telephone, set which CODEC Type to use.
• 84-26-01 VoIPDB Basic Setup - IP Address
Enter the IP address for the VoIPDB.
• 84-26-02 VoIPDB Basic Setup - RTP Port Number
Enter the RTP port number range.
5.1 Music on Hold

Music on Hold is provided by the IP telephone. The settings in Program 10-04 : Music on Hold Setup
are ignored except to determine whether or not music is to be provided. If 10-04-02 is set to 0, no
Music on Hold is heard. If 10-04-02 is set to 1 or 2, music is provided by the IP telephone.
SECTION 6 CONFIGURATION EXAMPLES

The examples below show typical scenarios and basic programming required. These examples
assume that the programming steps below are performed on a default system (i.e., no existing
configuration).
6.1 Example Configuration 1 - Static IP Addressing, One LAN

This example shows IP Phone connected to a single LAN (no routers), with static IP Addresses.

ISSUE 1.0 SL2100
Chassis
CPU-C1
PoE Switch
VoIP
NEC SL2100
VoIPDB IP Address
192.168.1.20
VoIP DSP: 192.168.1.21
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.254
IP Phone 1 IP Phone 2
192.168.1.200 192.168.1.201
Extension: 100 Extension: 101
Figure 9-3 Example Configuration 1 - Static IP Addressing, One LAN
Programming - CPU:
10-12-01 : CPU Network Setup - IP Address (for CPU) 0.0.0.0
10-12-10 : CPU Network Setup - Subnet Mask 255.255.255.0
10-12-03 : CPU Network Setup - Default Gateway 192.168.1.254
10-12-09 : CPUNetwork Setup - VoIPDB IP Address 192.168.1.20
(This assignment is for CPU-C1 when the VoIPDB daughter board is installed.)
Programming - VoIP DSP Resource:
84-26-01 : VoIP Basic Setup - IP Address (Slot # - DSP) 192.168.1.21
Programming - IP Phones:
DHCP Mode Disabled
IP Address 192.168.1.200
Subnet Mask 255.255.255.0
Default Gateway 192.168.1.254
1st Server Address 192.168.1.20
1st Server Port 5080
6.2 Example Configuration 2 - Dynamic IP Addressing, One LAN

This example shows System IP Phones connected to a single LAN (no routers) with dynamic IP
Addresses. The DHCP server could be:
• Customer supplied (e.g., Windows server)
• inDHCP internal DHCP server
In this case, additional programming would be required. Refer to General IP Configuration on

page 4-1.

SL2100 ISSUE 1.0
Chassis
CPU-C1
PoE Switch
VoIP
NEC SL2100
VoIPDB IP Address
192.168.1.20
VoIP DSP: 192.168.1.21
Subnet Mask: 255.255.255.0
192.168.1.200 192.168.1.201
Extension: 200 Extension: 201
Figure 9-4 Example Configuration 2 - Dynamic IP Addressing, One LAN
Programming - CPU:
10-12-01 : CPU Network Setup - IP Address 0.0.0.0
10-12-09 : CPU Network Setup - VoIPDB Address 192.168.1.20
(This assignment is for CPU-C1 when the VoIP daughter board is installed.)
10-13-01 : In-DHCP Server Setup - DHCP Server Mode Enable
10-14-01 : Managed Network Setup (Min) 192.168.1.200 Min
10-14-02 : Managed Network Setup (Max) 192.168.1.250 Max
10-16-16 : SIP Server Address 192.168.1.20
10-16-27 : SIP Server Port 5080
Programming - VoIP DSP:
84-26-01 : VoIP Basic Setup - IP Address 192.168.1.21
DHCP Mode (Ext. 200): Enabled
6.3 Example Configuration 3 - Static IP Addressing, Routed WAN

This example shows IP Phones connected to an NEC SL2100 system over a Wide Area Network
(WAN), with static IP addressing. This is a typical scenario - a small branch office connecting to the
main office.

ISSUE 1.0 SL2100
Chassis
CPU-C1
Switch
VoIP
VoIPDB IP Addres: 192.168.1.20

VoIP DSP: 192.168.1.21 Router VPN
Subnet Mask: 255.255.255.0 192.168.1.254
WAN
(Leased Line, Frame
Relay, etc.)
Router VPN
PoE Switch/Hub
192.168.2.254
192.168.2.200 192.168.2.201
Figure 9-5 Example Configuration 3Static IP Addressing, Routed WAN
Programming - CPU:
10-12-01 : CPU Network Setup - IP Address 0.0.0.0
10-12-09 : CPU Network Setup - VoIPDB IP Address 192.168.1.20
(This assignment is for CPU-C1 when the VoIP daughter board is installed.)
Programming - VoIPDB DSP:
84-26-01 : VoIPDB Basic Setup - IP Address (Slot # - DSP) 192.168.1.21
DHCP Mode: Disabled
IP Address: 192.168.2.200
Subnet Mask: 255.255.255.0
1st Server Address: 198.168.1.20
1st Server Port: 5080

SL2100 ISSUE 1.0
SECTION 7 IP PHONE PROGRAMMING INTERFACE

This section describes how to access the programming interface for IP Phones. The following
describes how to access the User Menu.
1. Using a 8IPLD telephone, press HOLD-Transfer-*-# buttons to enter program mode. The IP User
Menu is displayed.
2. On the IP User Menu, enter the user name and password for the IP Phone. Settings are listed in
Table 9-1 IP Phone Programming Options User Menu on page 9-8.
Table 9-1 IP Phone Programming Options User Menu
Programming Option Default

UserName ADMIN
Password 6633222
SECTION 8 DHCP SERVER CONFIGURATION

It is possible to use either an external DHCP server (e.g., Windows Server) or the NEC SL2100
internal DHCP server. With IP Phones, either of these options requires the DHCP server to be
configured to supply the IP terminal options.
If using the internal DHCP server, enable the DHCP server. Refer to Example Configuration 2 -
Dynamic IP Addressing, One LAN on page 9-5.
When using an external DHCP server, you must add a new Option Code to the DHCP scope for the
VoIPDB IP address. The method for adding this service varies depending on the DHCP server used.
SECTION 9 CONFIGURING QUALITY OF SERVICE

NEC recommends configuring Quality of Service (QoS) to ensure that the speech quality is not
affected by other data on the network. QoS is discussed further in Network Design Considerations on
page 6-1.
The NEC SL2100 system supports:

• IEEE802.1q (VLAN Tagging)
• IEEE802.1p (Priority)
With the VLAN tagging mode, the NEC SL2100 system can handle packets with or without a VLAN
tag. If the VLAN ID of a packet is different from the registered one, that packet is dropped.
9.1 Layer 2 Priority Control

Layer 2 priority control can be enabled on an Ethernet switch, if it supports VLAN tagging. This allows
layer 2 prioritization.
Using a switch that supports 802.1p allows:

• priority control
• reduction of unnecessary packets (e.g., broadcast packets) and provides circuitry by restricting a
broadcast domain

ISSUE 1.0 SL2100
9.1.1 Programming Layer 2 Priority Control
To program Layer 2 Priority Control for IP Phones VLAN/QoS:
1. Press the Menu button on the IP Phone to enter the telephone program mode.
This enters the IP program mode to select the settings for the individual phone. The flashing item is
the current selection.
1. Network 1. DHCP Mode

Settings 1. Speed & Duplex
: 2. VLAN Mode Set VLAN Disable/Enable
: 3. VLAN ID Set same ID as 87-09-02
: 4. VLAN Priority Set VLAN Priority
:
6. Advanced Setting
2. Press OK, EXIT, SAVE softkeys to save the entries and return the telephone to idle.
9.2 Layer 3 (ToS) Priority Control

The router-supported ToS controls routing priority of packets by following the ToS field. You can give
priority to the voice packet using the ToS field.
There are two types of ToS formats: DiffServ and IP Precedence. Before programming the router,
make sure to check which type is supported by the router.
The NEC SL2100 system can set the ToS value for each protocol, and Voice Control. This setting
allows flexible prioritization.
9.2.1 Programming Layer 3 Priority Control
To program Layer 3 VLAN/QoS use the following programs.

• 84-10-01 ToS Setup – ToS Mode
For the Protocol type (1= Not Used, 2= Not Used, 3= Reserved, 4= H.323, 5= RTP/RTCP, 6= SIP,
7= Reserved, 8= SIP MLT, 9= SIP Trunk, 10=Reserved, 11=Reserved), select the ToS mode
(Disable, IP Precedence or Diffserv).
• 84-10-07 ToS Setup – Priority (D.S.C.P. - Differentiated Services Code Point)
For the Protocol type (1= Not Used, 2= Not Used, 3= Reserved, 4= H.323, 5= RTP/RTCP, 6= SIP,
7= Reserved, 8= SIP MLT, 9= SIP Trunk, 10=Reserved, 11=Reserved), if Program 84-10-01 is set to
2, select the Diffserv priority (0~63).
SECTION 10 IP TELEPHONE REGISTRATION AND DELETION

When an IP Phone connects to the NEC SL2100 system, it is assigned the first available port, starting
from the value set in Program 11-02-01.
The ports are allocated in blocks of two.
For example:
• Insert a VoIPDB.
• Program 11-02-01 Extension Numbering.
• Configure a System IP Phone and connect to the LAN.
When connecting an IP Phone, the MAC address (ID) is automatically registered in Program 15-05-02.
If the registration in Program 15-05-02 is made manually (before connecting the telephone) it uses the

SL2100 ISSUE 1.0
assigned port number when the telephone is connected. The MAC address is printed on the barcode
label on the bottom of the telephone. It is a 12-digit alphanumeric number, ranging from 0~9 and A~F.
To delete a telephone registration:
Enter Program 90-23-01, and enter the extension number of the IP Phone. If connected to the SL2100
via Telephone Programming, enter a 1 to delete the IP phone and then press Hold. If connected to the
SL2100 via Web Pro, place a check next to the extension and click Apply.
SECTION 11 SYSTEM IP PHONES AND ANALOG TRUNKS

Due to the nature of analog-to-digital conversion, considerable echo may be encountered when using
Analog Trunks with IP Phones.
Due to all Analog trunks being different, padding of the Analog Trunks in PRG 81-07 and 14-01 may
be necessary. Even after the pad changes are made, echo may still be present the first few seconds of
the call while the echo cancellers are learning the characteristics of the circuit on this call.
It is recommended to use digital trunks when using IP phones for best performance.
Digital (ISDN, T-1, and SIP) trunks do not suffer from this problem.
When analog trunks are installed in an SL2100, PRG 90-68 (Side Tone Auto Setup) must be used.
This program will automatically change the setting of 81-07 after multiple tests are performed on the
analog line. During these tests the system will not be usable, and the system must be reset once the
test are finished.
Anytime new analog trunks are added to the system, PRG 90-68 MUST be used.
SECTION 12 FIRMWARE UPGRADE PROCEDURE

A new version of NEC firmware for the IP Phones can be applied automatically or manually.
The upgrade requires using an FTP/TFTP server. This is a software package that runs on a PC.
(These can be downloaded from the Internet, usually as freeware or shareware.)
12.1 Manually Upgrading Firmware

Manually upgrading the firmware uses an FTP/TFTP server, but requires the engineer visit each IP
Phone individually. This may take longer, but is more controlled as the downloads can be staggered to
avoid excessive bandwidth utilization.
To manually upgrade the firmware:
1. Install and configure an FTP/TFTP server.

2. Copy the firmware file itlisipr.tgz to the default FTP/TFTP directory.
3. To enter Programming Mode, press the Hold, Transfer, *, # button on the IP Phone.
4. To enter Maintenance Mode, press 3: Maintenance Settings.
5. To access the Download menu, press 1.
6. Enter the FTP/TFTP server IP address in Option 2 - Download Address.
7. To enter the protocol, press #3 (Protocol FTP or TFTP).
8. To select download by file, press option 1 (Download File).
9. To boot the program, press 2 (Boot & Program).
10. Press the softkey.

ISSUE 1.0 SL2100
The IP Phone downloads the firmware from the FTP/TFTP server and reboots when the download is
complete.
12.2 Checking the Firmware Version

To check the IP Phone firmware version:
1. Press and hold the HELP button on the IP Phone.

2. Press 2 (System Information).
3. Press 5 (Keyset Information).
4. Press the Next softkey two times.
12.3 Upgrading Automatically

This procedure causes all IP Phones to attempt firmware upgrade the next time they connect to the
CPU. This can make the upgrade procedure easier, as it is not necessary to visit every telephone to
perform the upgrade.
This can cause problems if, for example, a PoE (Power over Internet) switch is used. When the PoE
switch is powered up, all telephones connect to the FTP/TFTP server at the same time. This causes a
large amount of data for the FTP/TFTP server to transfer over the data network.
To avoid this, connect the telephones to the PoE switch gradually, to allow time for each telephone to
upgrade before connecting the next.
To enable automatic upgrade:
1. Install and configure an FTP/TFTP server.

2. Copy the firmware file itlisipr.tgz to the default FTP/TFTP directory.
3. Set the server mode to FTP/TFTP in Program 84-07-01 and specify the IP address of the FTP/
TFTP server (this is the PC where the FTP/TFTP software is installed) in Program 84-07-02.
4. In Program 84-28 program the Firmware Directory path on the FTP/TFTP server and assign the
file name (itlisipr.tgz).
5. In Program 90-42, assign the software and hardware versions. An example of the hardware
assignment would be 09.01.03.06, this is Hardware Version 9.1.3.6.
SECTION 13 IP STATION (SIP MULTILINE TELEPHONE)

13.1 Description
The NEC SL2100 system supports IP phones using Session Initiation Protocol (SIP). These IP
telephones have the same look and functionality as typical multiline telephones, but they are
connected to an VoIPDB card in the CPU rather than hardwired to a Digital Station port.
Some of the benefits of an IP phone over a traditional TDM phone are described in the following list:
• Reduced telephone re-location costs. Unplug an IP telephone at one location and plug it into
another VoIP ready jack at another location. The extension number can stay with the telephone, if
programmed to do so.
• Multiple users can share the same IP telephone but keep their own personal extensions. With an IP
phone you have the ability to log the phone out, then log back in with another extension number. All
of your personal settings follow the login ID of your extension.

SL2100 ISSUE 1.0
• The cabling infrastructure can be simplified. There is no longer a need for separate cabling for the
phone system. Built into the IP phones is a 2 port 10/100 manageable data switch. The data
connection for the PC is available on the back of the IP phone. This built in data switch also
supports 802.1Q and 802.1 P VLAN tagging abilities. The data and the voice can be tagged
separately.
• Allows you to connect remote office workers with a telephone that has the look and same
functionality as the telephones connected at the office.
SIP is used for VoIP as defined by the IETF (Internet Engineering Task Force) RFC3261. The NEC
SIP MLT uses IP Multiline Station (SIP) (proprietary enhanced SIP protocol) to facilitate the
multifunction, multiline telephone.
The SIP Multiline Telephone interfaces directly to the CPU that houses the VoIPDB daughter board.
The VoIPDB provides the digital signal processors (DSPs) for IP stations and trunks.
• VoIPDB provides 128 DSPs
A DSP provides format conversion from circuit switched networks (TDM) to packet switched networks
(IP). Each voice channel from the circuit switched network is compressed and packetized for
transmission over the packet network. In the reverse direction, each packet is buffered for de-jittering,
decompressed and sent to the circuit switched network. Each DSP converts a single speech channel
from IP to TDM and vice versa.
The following are examples of DSP allocation.

• Calling from an IP phone to a TDM phone uses one DSP.
• Calling from an IP phone to another IP phone, registered to the same CPU, uses no DSPs.
• Calling from a TDM phone to another TDM phone uses no DSPs.
• Calling from a TDM phone and out an IP trunk uses one DSP.
An IP to IP call is peer-to-peer, and no DSP resource is used. When this feature is deactivated, an IP to IP
call consumes two DSP resources.
13.2 IP Addressing
When a VoIPDB daughter board is installed in an SL2100 two IP addresses, in the same network, will
be required. One IP Address will be for the VoIPDB and this address is assigned in Program 10-12-09.
This IP Address is used for IP Phones/Trunks to register and pass signaling messages. The other IP
Address is for the DSP’s and this address is assigned in Program 84-26-01. This IP Address is used to
pass voice traffic.
By default when an SL2100 with a VoIPDB is installed in a customer’s network, the SL2100 will try and
request IP Addressing information from the local DHCP server (DHCP Client Feature). The DHCP
server can provide the SL2100 with the following information:
• IP Address for VoIPDB (PRG 10-12-09)
• Subnet Mask for VoIPDB (PRG 10-12-10)
• Default Gateway for VoIPDB (PRG 10-12-03)
The DHCP server will NOT provide the IP address for the DSP’s (PRG 84-26-01). This IP Address will
have to be manually configured.
The DHCP Client Feature can be disabled in Program 10-63-01. When this program is changed a
reset of the SL2100 is required.
When the VoIPDB is installed, in the SL2100, the CPU NIC card is no longer available. All connections
that previously were terminated to the CPU will now terminate to the VoIPDB. It is recommended when
adding the VoIPDB to change the IP Address of the CPU NIC card (PRG 10-12-01) to be 0.0.0.0.

ISSUE 1.0 SL2100
13.3 IP Phone Registration Modes

The SIP MLT supports three different registration modes.
• Plug and Play
• Automatic Login
• Manual Login
Plug and Play Registration
Plug and play registration mode allows for no authentication. As long as an IP terminal is configured
with the proper IP addressing scheme, and plugged into the network, the phone comes on-line. In plug
and play mode you may assign an extension number into the IP terminal or allow the system to
automatically set an unused extension number for the station. When the system assigns unused
extension numbers it starts searching for the first available port or starts at a preassigned port and
works its way up from there.
Automatic Login
When set to automatic login the SIP user name and password must be entered in the configuration in
the IP terminal. When the phone tries to register with the CPU it checks the user name and password
against its database. If the user name and password match, the phone is allowed to complete
registration. If the user name and password do not match, the phone cannot register with the CPU.
The IP terminal displays an error message: Unauthorized Auto Login.
Manual Login
When set to manual login, no user name, password, or extension number is entered into the
configuration of the telephone. The user is prompted to enter this user name and password into the IP
phone. This information is cross referenced in the phone system to an associated extension number. If
a match is found, the phone comes online. If there is no match, the phone cannot complete
registration with the CPU. The IP terminal either returns to the login/password screen, or locks out the
user and requires the administrator to unlock the IP terminal. Lockout on failed attempts is dependent
on system programming. Manual mode is good for an environment where multiple users share the
same IP phone at different times. As one user logs out the next user can login with their credentials
and all of their associated programming follows.
In Manual mode a user can also logoff the IP phone to allow another user to login with their own login
ID and password.
To logoff the IP Phone when the terminal is set to "Standard" softkey mode (PRG 15-02-60) use the
following operation: Press the "Prog" softkey, press the "Down Arrow", press the "Down Arrow", press
the "Down Arrow", and then press "Logoff". The IP Phone can also be logged off by resetting the IP
terminal.
To logoff the IP Phone when the terminal softkey is set to "Advanced Mode 1/2" (PRG 15-02-60) the IP
terminal must be reset.
Encryption
The SL2100 Supports AES 128-bit encryption between 8IPLD terminals and the VoIPDB.
Table 9-2 8IPLD Supported Encryption
Source Destination SRTP Comment

8IPLD STD SIP (P2P) N
8IPLD STD SIP (Non P2P) S The encryption will be between the IP terminal and the
VoIPDB. Once the voice leaves the SL2100 to third party SIP
terminal the voice cannot be encrypted.
8IPLD 8IPLD S

SL2100 ISSUE 1.0
Source Destination SRTP Comment

8IPLD PSTN S The encryption will be between the IP terminal and the
VoIPDB. Once the voice leaves the SL2100 to the public net-
work it cannot be encrypted.
8IPLD IP Network (SIP) S The encryption will be between the IP terminal and the
VoIPDB. Once the voice leaves the SL2100 to the SIP net-
work it cannot be encrypted.
8IPLD Encryp- 8IPLD Encryption Off N‘
tion On
S = Supported N = Not Supported
Chassis
PSTN
IP Network
8IPLD/DT800 8IPLD/DT800 8IPLD/DT800 STD SIP

Not Encrypted
Encrypted SRTP
Figure 9-6 8IPLD Encryption
Conditions
• Encryption is not supported on 8IPLD series phones that are connected via NAPT.
• If the encryption feature is enabled in terminal programming but not licensed, the terminal displays
“Invalid server” and will not function.
13.4 General IP Configuration

The voice quality of VoIP depends on variables such as available bandwidth, network latency, and
quality of service initiatives (QOS). These variables are controlled by the network and Internet service
providers. Because these variables are not in NEC control, NEC cannot guarantee the performance of
the users IP based voice solution. NEC recommends connecting the VoIP equipment through a local
area network using private IP addresses.
To ensure a network meets the specific requirements for VoIP implementation, an IP ready check and
a site survey must be completed at each site before VoIP implementation.
• One way delay must not exceed 100ms.
• Round trip delay must not exceed 200ms.
• Packet loss must not exceed 1%.
• Data switches must be manageable.
• Routers must provide QOS.
• There must be adequate bandwidth for estimated VoIP traffic. Refer to Section Bandwidth on
page 9-26.
Depending on how QOS policies are built in the network, assignments may be needed in both the
CPU and IP terminal. The NEC SL2100 supports the flagging of packets at layer 2 (VLAN tagging
802.1Q/802.1P) and at layer 3 levels.

ISSUE 1.0 SL2100
13.5 VLANs
A VLAN is used to logically break up the network and minimize broadcast domains. Without VLANS,
the network must be physically segmented to break up broadcast domains. Each network segment is
then connected through a routing device adding latency and cost. Latency is a delay in the
transmission of data and is caused by routing packets from one LAN to another. In a VoIP
environment latency must be kept to a minimum.
802.1Q allows a change in the Ethernet Type value in the Ethernet header tagging the Protocol ID
0x8100, identifying this frame as an 802.1Q frame. This inserts additional bytes into the frame that
composes the VLAN ID (valid IDs = 1 ~ 4094).
802.1P allows you to prioritize the VLAN using a 3-bit priority field in the 802.1Q header. Valid VLAN
priority assignments are 0 ~7. A tag of 0 is treated as normal data traffic giving no priority. Under
normal circumstances the higher the tag numbers, the higher the priority. However this is left up to the
network administrator as they could set the exact opposite where the lower tag numbers have a higher
priority.
Tagging Voice and Data Packets
Built into the IP phones is a 2 port 10/100 manageable data switch allowing for a PC connection on
the back of the IP phone. This built in data switch also supports 802.1Q and 802.1P VLAN tagging
capabilities.
The following procedures describe two methods for tagging the voice packets and the data packets
separately, using the PC, or using the phone keypad.
13.5.1 Logging In on the PC
1. Web browse to the IP address of phone.

2. To log in, enter default user name: ADMIN
3. Enter default password: 6633222

SL2100 ISSUE 1.0
4. Click OK.
Figure 9-7 Log In to IP Phone
13.5.2 Tagging Voice Packets Using IP Phone
1. To apply a tag to the voice packets only, go to Network Settings>Advanced Settings>LAN port
settings.

ISSUE 1.0 SL2100
2. Access the following three menus to select options for LAN Port Settings:
• VLAN Mode
• VLAN ID
• VLAN Priority
Figure 9-8 LAN Port Settings Window
3. Select the VLAN Mode to enable or disable this feature.

4. Select either Enable or Disable (default) and click OK.
Figure 9-9 VLAN Mode
5. VLAN ID allows an entry of 1~4094 for the VLAN ID. VLAN Mode must be enabled for this entry
to be valid.
Enter the VLAN ID and click OK.
Figure 9-10 VLAN ID

SL2100 ISSUE 1.0
6. VLAN Priority allows an entry of 0~7 for the VLAN Priority. VLAN mode must be enabled for this
entry to be valid.
Enter the required priority, and click OK.
Figure 9-11 VLAN Priority
13.5.3 Tagging Data Packets Using IP Phone
1. While logged in to the IP address of the phone on the PC, go to Network Settings>Advanced
Settings>PC Port Settings. Refer to Section Logging In on the PC on page 9-15.
2. Access the following three menus to select options for PC Port Settings:
• Port VLAN Mode
• Port VLAN ID
• Port VLAN Priority.
Figure 9-12 PC Port Settings Window
3. Select the VLAN Mode to enable or disable this feature.

ISSUE 1.0 SL2100
4. Select either Enable or Disable (default) and click OK.
Figure 9-13 Port VLAN Mode
The remaining data packets settings for VLAN on the PC Port are the same as those for the voice
packets.
5. VLAN ID allows an entry of 1~4094 for the VLAN ID. VLAN Mode must be enabled for this entry
to be valid.
Enter the VLAN ID, and click OK.
Figure 9-14 Port VLAN ID
6. VLAN Priority allows an entry of 0~7 for the VLAN Priority. VLAN mode must be enabled for this
entry to be valid.
Enter the required priority, and click OK.
Figure 9-15 Port VLAN Priority

SL2100 ISSUE 1.0
7. Click Save.
Figure 9-16 Save Network Settings
8. After saving settings, click OK to confirm. Telephone reboots and applies the VLAN settings.
Figure 9-17 Save Confirmation Window
13.5.4 Entering VLAN Settings by Phone (Voice Packets Only)
1. Press Hold, Transfer, *, # to enter programming mode.

2. Enter the user name of ADMIN and password of 6633222, then press the OK softkey.
3. Dial 1 for Network Settings.
4. Press 6 on the dial pad for Advanced Settings
5. Press 1 on the dial pad for LAN Port Settings (VLAN for the voice packets only)
6. Press 2 on the dial pad for VLAN Mode
7. Press 1 or 2 to disable/enable the VLAN for the voice packets. Press the OK soft key after the
setting is changed.
8. Press 3 on the dial pad for VLAN ID
9. Enter a valid VLAN ID of 1~4094. Press the OK soft key after the setting is changed.
10. Press 4 on the dial pad for VLAN Priority
11. Enter the VLAN priority of 0~7. Press the OK soft key after the setting is changed.
12. If no more changes are made, press the Exit soft key three times. Then press the Save soft key,
and the phone reboots.

ISSUE 1.0 SL2100
13.5.5 Entering VLAN Settings for PC Port by Phone (Data Packets Only)
1. Press Hold, Transfer, *, # to enter programming mode.

2. Enter the user name of ADMIN and password of 6633222, then press the OK softkey.
3. Press 1 on the dial pad for Network Settings.
4. Press 1 or 2 to disable/enable the VLAN for the data packets. Press the OK soft key after the
setting is changed.
5. Press 3 on the dial pad for Port VLAN ID.
6. Enter a valid VLAN ID of 1~4094. Press the OK soft key after the setting is changed.
7. Press 4 on the dial pad for Port VLAN Priority.
8. Enter the VLAN priority of 0~7. Press the OK soft key after the setting is changed.
9. If no more changes are made, press the Exit soft key three times. Then press the Save soft key,
and the phone reboots.
13.6 ToS Settings (Layer 3 QoS)

The marking of packets at layer 3 is done by marking the ToS byte in the IP header of the voice
packet. The NEC SL2100 supports two methods for marking the ToS byte:
• IP precedence
• DSCP (Diffserv)
IP Precedence
IP Precedence uses the first 3 bits of the ToS field to give eight possible precedence values (0~7).
Under normal circumstances the higher the number the higher the priority. However this is left to the
network administrator for setup. The administrator may assign this in exactly the opposite manner with
the lower values having a higher priority. Below are the eight common values for IP precedence.
• 000 is an IP precedence value of 0, sometimes referred to as routine or best effort.
• 001 is an IP precedence value of 1, sometimes referred to as priority.
• 010 is an IP precedence value of 2, sometimes referred to as immediate.
• 011 is an IP precedence value of 3, sometimes referred to as flash.
• 100 is an IP precedence value of 4, sometimes referred to as flash override.
• 101 is an IP precedence value of 5, sometimes called critical.
• 110 is an IP precedence value of 6, sometimes called internetwork control.
• 111 is an IP precedence value of 7, sometimes called network control.
Working in conjunction with IP precedence, the next 4 bits in the ToS field are designed to influence
the delivery of data based on delay, throughput, reliability, and cost. However these fields are typically
not used.
The following table shows the 8-bit ToS field and the associated IP precedence bits.
IP Prece- IP Prece- IP Prece- Delay Through- Reliability Cost Not Used

dence dence dence put
1(on) here = 1(on) here = 1(on) here =
value of 4 value of 2 value of 1
Differential Services Code Point (DSCP)
DSCP stands for Differential Services Code Point (or Diffserv for short). It uses the first 6 bits of the
ToS field therefore giving 64 possible values.
The following list shows the most common DSCP code points with their binary values and their
associated names:

SL2100 ISSUE 1.0
DSCP Code Points Binary Values Names

000000 0 Best Effort (BE)
001000 8 Class Selector 1 (CS1)
001010 10 Assured Forwarding 11 (AF11)
100110 38 Assured Forwarding 43 (AF 43)
101110 46 Expedited Forwarding (EF)
The following table shows the 8 bit TOS field and the associated Diffserv bits.
Diffserv Diffserv Diffserv Diffserv Diffserv Diffserv Not Used Not Used
1(on) here = 1(on) here = 1(on) here = 1(on) here = 1(on) here = 1(on) here =
value of 32 value of 16 value of value of value of value of
8 4 2 1
IP Precedence/Diffserv Values Submitted in Command 84-10
Assignments for the IP Precedence/Diffserv values in the system are submitted in command 84-10.
This setting data affects only the packets sent by the VoIPDB card. This does not affect the packets
sent from the IP terminals.

ISSUE 1.0 SL2100
Figure 9-18 84-10: ToS Setup
To set the IP Precedence/Diffserv bits for packets leaving the IP terminal there are the following two
options:
• System wide. If all IP phones use the same ToS value, this can be assigned in commands
84-23-06 and 84-23-12. When an IP phone registers with the CPU, it looks for settings in these
commands. If these are found, they override any previous individual settings.
• Individual. If different IP phones require different ToS assignments, due to the network
configuration, these assignments must be set at each individual station
Command 84-23 requires a Hexadecimal representation of the 8 bit ToS field. For example, to assign
the signaling packets an IP precedence value of 4 and the voice packets an IP precedence value of 5,
it would be as follows. Refer to Figure 9-19 SIP MLT Basic Setup on page 9-24.
• 80 in Hex is 10000000 - This represents the signaling packets leaving the IP phone
• A0 in Hex is 10100000 - This represents the voice packets leaving the IP phone

SL2100 ISSUE 1.0
Figure 9-19 SIP MLT Basic Setup
The following table shows the common IP Precedence/Diffserv values and their hexadecimal
equivalent.
Table 9-3 Common IP Precedence/Diffserv Values and Hexadecimal Equivalent
IP Precedence Name Hex Value

IP Precedence 1 20
IP Precedence 2 40
IP Precedence 3 60
IP Precedence 4 80
IP Precedence 5 A0
IP Precedence 6 C0
IP Precedence 7 E0
DSCP Name Hex Value
DSCP 10 28
DSCP 12 30
DSCP 14 38
DSCP 16 40
DSCP 18 48
DSCP 20 50
DSCP 22 58
DSCP 24 60

ISSUE 1.0 SL2100
DSCP 26 68
DSCP 28 70
DSCP 30 78
DSCP 32 80
DSCP 34 88
DSCP 36 90
DSCP 38 98
DSCP 46 B8
DSCP 48 C0
DSCP 56 E0
13.6.1 Enter Values on a Per Phone Basis
• By the web browser

• By configuration mode through the dial pad
To enter the values per phone, browse to the individual phone or enter the configuration mode through
dial pad.
The following example describes assigning these fields via the web browser.
1. Log in on PC. Refer to Section Logging In on the PC on page 9-15.

2. Go to Network Settings >Advanced Settings >Type Of Service.
Figure 9-20 Type of Service Window

SL2100 ISSUE 1.0
3. There are two choices: RTP and SIP. RTP = voice packets and SIP = signaling packets.
Select each field and assign the appropriate value. Then select OK.
These fields are also looking for a Hexadecimal value as with command 84-23. Refer to
Table 9-3 Common IP Precedence/Diffserv Values and Hexadecimal Equivalent on page 9-24.
Access the following menus to select options:
• RTP - Voice Packets
• SIP - Signaling Packets
Figure 9-21 RTP - Voice Packets
Figure 9-22 SIP - Signaling Packets
4. After selecting Save, the following message appears.

5. Select OK and the phone reboots. Once online, the phone tags all packets with the applied
settings.
13.6.2 Assign Values on IP Terminal
The following is an example of assigning fields on the IP terminal.
1. Press Hold, Transfer, *, #.

2. Enter the user name of ADMIN and password of 6633222, and press the OK softkey.
3. Press 1 on the dial pad for Network Settings.
4. Press 6 on the dial pad for Advanced Settings.
5. Press 4 on the dial pad for Type of Service.
6. There are two options (1) is RTP and (2) is SIP.
7. Press 1 on the dial pad for RTP (voice packets), enter the hexadecimal value, and then press the
OK soft key.
8. Press 2 on the dial pad for SIP (Signaling packets), enter the hexadecimal value, and then press
the OK soft key.
9. If no more changes are to be made, press the Exit soft key three times, and then press the Save
soft key. The phone reboots.
13.7 Bandwidth
The bandwidth required for VoIP calls depends on the following factors.
• Layer 2 media
• CODEC
• Packet Size
• RTP Header Compression

ISSUE 1.0 SL2100
• Voice Activity Detection (VAD)

• Number of simultaneous calls
Layer 2 media is concerned with moving data across the physical links in the network. A few of the
most common layer 2 media types are Ethernet, PPP, and Frame Relay.
CODEC stands for Coder/Decoder and is the conversion of the TDM signal into an IP signal and vice
versa. A CODEC can also compress/decompress the voice payload to save on bandwidth.
Packet Size is the amount of audio in each PDU (protocol data unit) measured in milliseconds. The
larger the packet the less bandwidth used. This is because sending larger packets (more milliseconds
of voice) requires, overall, less packets to be sent. The downside of this practice is if a packet is
dropped/lost a larger piece of voice is missing from the conversation as the system waits the
additional delay for the next packet arrival.
RTP Header Compression compacts the RTP header from 40 bytes in size to 2 ~ 4 Bytes in size.
RTP header compression is used only on low speed links. Regularly on every voice packet there is an
IP/UDP/RTP header that is 40 bytes in length. Compressing this header, down to 2 ~ 4 bytes, can
save a considerable amount of bandwidth. The following is an example of a VoIP packet without RTP
header compression and one of a packet with RTP header compression.
Notice that the overall packet size, when using RTP header compression, is considerably smaller.
• VoIP packet without RTP header compression
IP Header UDP Header RTP Header VOICE PAYLOAD

20 bytes 8 Bytes 12 bytes
• VoIP packet with RTP header compression
Compressed VOICE PAYLOAD

Header 2 ~ 4 bytes
Voice Activity Detection (VAD) is suppression of silence packets from being sent across the network.
In a VoIP network all conversations are packetized and sent, including silence. On an average a
typical conversation contain anywhere from 35% ~ 45% silence. This can be interrupted as 35% ~
45% transmission of VoIP packets, as having no audio, using valuable bandwidth. With the VAD option
enabled, the transmitting of packets stops after a threshold is met determining silence. The receiving
side then injects comfort noise into the call so it does not appear the call has dropped.
Bandwidth Calculations
The first step in calculating the bandwidth of a call is determining how many bytes the voice payload is
going to use. The amount is directly affected by the CODEC and packet size. Below are the supported
default CODEC speeds for SIP Multiline telephones.
• G.711 = 64000bps
• G.722 = 64000bps
• G.729 = 8000bps
Payload Calculation Voice
• (Packet size * CODEC bandwidth) / 8 = Voice Payload in Bytes

• Example of G.711 with a 20ms packet size
• (.020 * 64000) /8 = 160 Bytes
• Example of G.729 with a 30ms packet size
• (.030 * 8000) /8 = 30 Bytes
Now that you have the voice payload in bytes you can calculate the overall bandwidth including the
layer 2 media. Below are some of the common layer 2 media types and their overhead.

SL2100 ISSUE 1.0
• Ethernet = 18 Bytes
• 802.1Q/P Ethernet = up to 32 bytes
• PPP = 9 Bytes
• Frame Relay = 6 Bytes
• Multilink Protocol = 6 Bytes
Bandwidth Calculation
( [ Layer 2 overhead + IP/UDP/RTP header + Voice Payload ] / Voice Payload ) * Default CODEC
speed = Total Bandwidth
Example of a G.711 call over Ethernet using a 20ms packet size and not using RTP header
compression
(.020 * 64000) / 8 = 160 Bytes for Voice Payload
([ 18 + 40 + 160] / 160) * 64000 = 87200bps
If VAD is not enabled each side of the conversation would be streaming 87.2kbps in one direction for a
total of 174.4kbps.
The following chart shows the supported CODECS for IP phones with different packet sizes over PPP
and Ethernet.
CODEC Packet Size PPP Ethernet

G.711 10 103.2 kbps 110.4 kbps
G.711 20 83.6 kbps 87.2 kbps
G.711 30 77.1 kbps 79.5 kbps
G.711 40 73.9 kbps 75.6 kbps
G.722 10 103.2 kbps 110.4 kbps

G.722 20 83.6 kbps 87.2 kbps
G.722 30 77.1 kbps 79.5 kbps
G.722 40 73.9 kbps 75.6 kbps
G.729 10 47.2 kbps 54.4 kbps

G.729 20 27.6 kbps 31.2 kbps
G.729 30 21.1 kbps 23.5 kbps
G.729 40 17.8 kbps 19.6 kbps
G.729 50 15.9 kbps 17.3 kbps
G.729 60 14.5 kbps 15.7 kbps
13.8 Some Network Considerations

When adding the SL2100 to a customers network there are many things to be aware of. Before
implementation a detailed network diagram of the existing network must be obtained from the
customer. This diagram may provide you with information about possible network conditions that can
prevent or hinder the VoIP equipment from functioning correctly.

ISSUE 1.0 SL2100
Firewalls
Another regular device in customer networks that can hinder VoIP performance is a firewall. Most
corporate LANs connect to the public Internet through a firewall. A firewall is filtering software built into
a router or a stand alone server unit. It is used to protect a LAN it from unauthorized access, providing
the network with a level of security. Firewalls are used for many things, but in its simplest form, a
firewall can be thought of as a one way gate. It allows outgoing packets from the local LAN to the
Internet but blocks packets from the Internet routing into the local LAN, unless they are a response to
query.
A firewall must be configured to allow specific traffic from the Internet to pass through onto the LAN. If
an IP phone is deployed out over the Internet there is a very good chance it is passing through a
firewall, either at the MAIN, the remote, or both locations.
The following diagram shows two IP phones on the corporate local LAN and one IP phone on a
Remote network connected via the Internet. The two phones that are installed on the local LAN are
functioning correctly. The IP phone at the remote site cannot register therefore it is not working.
Headquarters
Internet
Local LAN
Remote Network
Firewall Firewall
Figure 9-23 NEC SL2100 Network Example No. 1
The green arrow in the diagram above represents the data packets leaving the IP phone destined for
the SL2100 on the Headquarters LAN. The firewall on the Headquarters network is not configured to
recognize the UDP ports used by the NEC equipment thus blocking them and resulting in registration
failure. To solve this issue the ports used by the NEC VoIP equipment must be opened in the firewall
allowing the NEC traffic to pass through onto the SL2100.
The ports that are required to be opened on the headquarters locations are:
5080 and 5081 (UDP) for Signaling and 10020 ~ 10275 (UDP) for Voice.
The ports that need to be opened on the Remote network are 5060 (UDP) for signaling and ports 3462
and 3463 for voice (UDP).
VPN
Another common feature is the use of the Internet as the WAN between customer locations. When this
is done VPNs are typically used between the locations. A VPN (Virtual Private Network) is a private
data network that maintains privacy through the use of tunneling protocols and security features over
the public Internet. This allows for remote networks (with private addresses), residing behind NAT
routers and/or firewalls, to communicate freely with each other. When building the VPN tunnels,
throughout the network, they must be assigned as a fully meshed network. This means that every
network is allowed direct connection to each and every other network in the topology. Network
equipment limitations may sometimes restrict this ability resulting in no voice path on VoIP calls
between sites. When this happens Peer-to-Peer must be disabled in the SL2100. The downside to
disabling Peer-to-Peer is using more DSPs and consumption of additional bandwidth at the MAIN
location.

SL2100 ISSUE 1.0
The following diagram shows three sites connected together via VPN. This network is not fully meshed
due to the lack of a VPN tunnel between Sites B and C.
VoIPDB IP Address =
Figure 9-24 NEC SL2100 Network Example No. 2
With Peer-to-Peer enabled, the IP phones on site A can communicate with IP phones on sites B and
C. IP Phones on sites B and C cannot communicate directly with each other though. The IP phone
from site B can set up a call to the IP phone at site C, but there is no speech path. Here are the steps
in the call scenario leading to the failed call.
• Extension 120 goes off hook and dials ext 130.
• An initial invite message is sent from 192.168.2.15 (ext 120) to 192.168.1.10 (VoIPDB).
• 192.168.1.10 (VoIPDB) forwards that message to 192.168.3.26 (ext 130).
• In the original setup message there is a field labeled SDP (Session Description Protocol). The SDP
portion informs the IP phone where to send the media (voice) to. The SDP portion of this invite
message contains the IP address of 192.168.2.15 (ext 120).
• 192.168.3.26 (ext 130) sends a 200 OK message to 192.168.1.10 (VoIPDB). In the 200 OK
message is the SDP field reporting the IP address of 192.168.3.26 (ext 130).
• 192.168.1.10 (VoIPDB) forwards this message to 192.168.2.15 (ext 120).
• 192.168.2.15 (ext 120) sends an ACK message to 192.168.1.10 (VoIPDB).
• 192.168.1.10 (VoIPDB) forwards this message to 192.168.3.26 (130).
• At that point the two IP phones attempt to send voice packets directly to each other. As there is no
VPN connection between these sites the call is set up with no voice path.
To correct this issue another VPN connection between sites B and C is required. If an additional VPN
cannot be implemented, due to network limitations, the Peer-to-Peer feature can be disabled in the
NEC SL2100. With Peer-to-Peer disabled, all packets (Signaling and Voice) route through the VoIPDB
card. This also affects IP phones at the REMOTE locations calling other IP phones at the same
location. Without Peer-to-Peer enabled the voice path must route to the MAIN location and then back
to the REMOTE instead of directly between the two stations on the REMOTE network. This forces the
use of additional bandwidth on the MAIN, and REMOTE locations. Peer-to-Peer is disabled in
command 15-05-50 per IP Phone.
Figure 9-25 IP System Operation Setup

ISSUE 1.0 SL2100
13.9 Guide to Feature Programming
Program Program Name Description/Comments Assigned Data 1 2 3

Number
10-12-03 CPU Network Setup – VoIPDB uses the Default Gateway 0.0.0.0~ X
Default Gateway that is assigned here. 126.255.255.254
128.0.0.1~
191.255.255.254
192.0.0.1~
223.255.255.254
Default is 0.0.0.0
10-12-09 CPU Network Setup – Assign Layer 3 IP Address to the 0.0.0.0~ X
IP Address VoIPDB connected to CPU. 126.255.255.254
128.0.0.1~
191.255.255.254
192.0.0.1~
223.255.255.254
Default is 172.16.0.10
10-12-10 CPU Network Setup – Assign Subnet Mask to the VoIPDB Default is 255.255.0.0 X
Subnet Mask connected to CPU.
84-26-01 VoIPDB Basic Setup – Assign an IP Address for the VoIPDB Default Values: X
IP Address DSP's. Slot 1 = 172.16.0.20
84-26-02 VoIPDB Basic Setup – Range: 0 ~ 65534 X
RTP Port Number Default Values:
VoIP GW1 = 10020
84-26-03 VoIPDB Basic Setup – Range: 1 ~ 65535 X
RTP Port Number Default Values:
(RTP Port Number +1) VoIP GW1 = 10021
VoIP GW2 = 10053
VoIP GW3 = 10085
VoIP GW4 = 10117
VoIP GW5 = 10149
VoIP GW6 = 10181
VoIP GW7 = 10213
VoIP GW8 = 10245
10-46-01 DT800/DT700 Server Define which of the three Registration 0 = Plug and Play X
Information Setup – modes you wish the SIP MLTs to use. 1 = Automatic
Register Mode Plug and Play 2 = Manual
When the phone boots up it will report Default is 0
the ext assigned in the phone or
choose the next available extension in
the system. No password required.
Auto
If set to auto then the SIP user name
and password must be entered into
the actual IP phone. These settings
have to match Programs
84-22/15-05-27 or the phone does not
come on-line.
Manual
When the phone boots up it prompts
you to enter a user ID and password
before logging in. It checks this user
ID/password against Programs
84-22/15-05-27. If there is not a
match, the phone does not come on-
line.
10-46-04 DT800/DT700 Server USER ID of the SIP URL if Program Up to 32 characters. X
Information Setup – 10-46-05 is set to domain name. Default is sipphd
Server Name A SIP URL is made up of three parts.
Domain name, host name, and server
name.
e.g. At default the server name is
sipphd. The URL could look like the
following:
sipphd@voipu.nec.com

SL2100 ISSUE 1.0

Number
10-46-06 DT800/DT700 Server Port the SIP messages are sent to on Range = 0 ~ 65535 X
Information Setup – the VoIPU card. This same port num- Default is 5080
Register Port ber must be assigned in the SIP Multi-
line terminals.
Changing this command also re-
quires a CPU reset.
10-46-07 DT800/DT700 Server Enable or disable encryption mode. 0 = Off X
Information Setup – En- 1 = On
cryption Mode 1 = Default
10-46-08 DT800/DT700 Server Assign the encryption type. 0 = Mode 1 X
Information Setup – En- Default is 0
cryption Type READ ONLY
10-46-09 DT800/DT700 Server Password used when Program Valid Characters X
Information Setup – 10-46-07 is set to ON. Assign a char- (0~9, *, #)
One-Time Password acter string of 10 characters or less. Default Not assigned
10-46-10 DT800/DT700 Server With Automatic logon the starting port Range = (1 ~ 128) X
Information Setup – number for automatic port allocation. Default = 1
Start Port
15-05-01 IP Telephone Terminal Type of IP terminal registered with the 1 = H.323 X
Basic Data Setup – Ter- specified extension number. 2 = SIP
minal Type 3 = None
4 = SIP MLT
Default is 3
READ ONLY
15-05-02 IP Telephone Terminal Allow association of a MAC Address 00.00.00.00.00.00~ X
Basic Data Setup – Ter- to an extension. When the IP phone FF.FF.FF.FF.FF.FF
minal MAC Address sends a register message to the CPU Default is
the CPU responds back with the ex- 00.00.00.00.00.00
tension number associated to the
MAC address.
15-05-07 IP Telephone Terminal IP address the IP Terminal is using for 0.0.0.0~ X
Basic Data Setup – Us- the specified extension number. 255.255.255.255.
ing IP Address Default is 0.0.0.0
READ ONLY
15-05-15 IP Telephone Terminal Assign CODEC type for IP Terminal. If 1 = Type 1 X
Basic Data Setup – SIP SLT, use Program 84-19. If SIP 2 = Type 2
CODEC Type MLT, use Program 84-24. 3 = Type 3
4 = Type 4
5 = Type 5
1 = Default is 1
15-05-20 IP Telephone Terminal Read Only CM showing type of adapt- 0 = No Option X
Basic Data Setup – er installed on the ITH-style tele- 1 = ADA
Bottom Option Informa- phone. 2 = BHA
tion Default is 0
READ ONLY
15-05-26 IP Telephone Terminal Assign type of SIP MLT terminal con- 0 = Not Set X
Basic Data Setup – nected. 1 = Not Used
DT700 Terminal Type 2 = ITL Series-12/24 But-
ton without 8LK Unit
3 = Not Used
4 = Not Used
5 = Softphone
6 = CTI
7 = Not Used
8 = Not Used
9 = IP4WW-24TIXH
Default is 0
10 ~ 17 = Not Used
18 = IP7WW-8IPLD-C1

ISSUE 1.0 SL2100

Number
15-05-27 IP Telephone Terminal For SIP Multiline phone using Manual/ 0 = Not Set X
Basic Data Setup –Per- Auto registration. Assign each phone 1-128 = Set
sonal ID Index a unique personal index. When com- Default is 0
plete go to command 84-22 and set
the user name and password.
15-05-28 IP Telephone Terminal 0 = Disable X
Basic Data Setup –Ad- 1 = Enable
ditional Information Set- Default is 0
up
15-05-29 IP Telephone Terminal 0.0.0.0 ~ X
Basic Data Setup –Us- 255.255.255.255
ing Router Default is 0.0.0.0
READ ONLY
Basic Data Setup – 1 = Enable
DTMF Play During Default is 0
Conversation at Re-
ceive Extension
Alarm Tone During Default is 1
Conversation (RTP
packet loss alarm)
15-05-33 IP Telephone Terminal 0.0.0.0~ X
Basic Data Setup – Us- 255.255.255.255
ing IP Address Default is 0.0.0.0
READ ONLY
15-05-35 IP Telephone Terminal 0 = Off X
Basic Data Setup – En- 1 = On
cryption Mode On/Off Default is 0
READ ONLY
15-05-36 IP Telephone Terminal 00.00.00.00~ X
Basic Data Setup – FF.FF.FF.FF
DT800/DT700 Firm- Default is
ware Version 00.00.00.00
READ ONLY
15-05-38 IP Telephone Terminal Sets the protocol mode for the Paging 0 = Multicast X
Basic Data Setup – function. 1 = Unicast
Paging Protocol Mode 2 = Auto
Default is 0
Basic Data Setup – CTI 1 = Enable
Override Mode Default is 0
15-05-40 IP Telephone Terminal 0 = Both Name and Num- X
Basic Data Setup – ber
Calling Name Display 1 = Name only
Info via Trunk for 2 = Number only
Standard SIP 3 = None
Default is 0
15-05-41 IP Telephone Terminal 0~24 X
Basic Data Setup – (-12 ~ +12 hour)
Time Zone (Hour) Default is 12
Video Mode Default is 0
Basic Data Setup – Us- 1 = Enable
ing STD-SIP Display for Default is 0
CPN

SL2100 ISSUE 1.0

Number
15-05-45 IP Telephone Terminal Effective when Program 10-46-14 is 0 = Off X
Basic Data Setup – set to NAT Mode. Select sending RTP 1 = On
NAT Plug and Play port number to remote router, use Default is 0
from negotiation result (0) or received
RTP packet (1).
15-05-47 IP Telephone Terminal On a per station basis, this setting de- 0 = Disable X
Basic Data Setup – fines the SIP registration expiry timer. 60 ~ 65535 (sec)
Registration Expire If this value is set to 0, for a NAPT ter- Default is 180
Timer for NAT minal, the value in Program 84-23-01
is applied.
15-05-48 IP Telephone Terminal On a per station basis, this setting de- 0 = Disable X
Basic Data Setup – fines the SIP Subscribe expiry timer. 60 ~ 65535 (sec)
Subscribe Expire Timer If this value is set to 0, for a NAPT ter- Default is 180
for NAT minal, the value in Program 84-23-02
is applied.
84-10-XX ToS Setup Assignments deal with setting of the Protocol Type X
Layer 3 IP Header ToS field as it 1 = Not Used
leaves the VoIPDB unit. 2 = Not Used
Specify the protocol to assign the ToS 3 = Reserved
field for, and select the populated field 4 = H.323
to conform to either IP Precedence or 5 = RTP/RTCP
Differentiated Services. 6 = SIP
When setting IP Precedence, assign 7 = Reserved
Priority, Delay, Throughput, and Relia- 8 = SIP MLT
bility in Programs 9 = SIP Trunk
84-10-01/02/03/04/05. 10 = Reserved
When setting DiffServ, only assign the 11 = Reserved
DSCP in Program 84-10-07.
84-22-01 DT800/DT700 Multiline User ID for Manual or Auto registra- Assign up to 32 Alpha/ X
Logon Information Set- tion (Program 10-46-01). Numeric Characters
up – User ID Default is No Setting
84-22-02 DT800/DT700 Multiline Password for Manual or Auto registra- Assign up to 16 Alpha/ X
Logon Information Set- tion (Program 10-46-01). Numeric Characters
up – Password Default is No Setting
84-22-03 DT800/DT700 Multiline When set to manual login mode, the 0 = Off X
Logon Information Set- user ID is omitted from the display 1 = On
up – User ID Omission during entry by the user. Default is 0
84-22-04 DT800/DT700 Multiline Allow the ability to log off from the IP 0 = Off X
Logon Information Set- terminal when using manual registra- 1 = On
up – Log Off tion mode. Default is 1
84-22-05 DT800/DT700 Multiline Assign up to 32 Alpha/Numeric char- Assign up to 32 Alpha/ X
Logon Information Set- acters. Numeric Characters
up – Nickname Default is No Setting
84-23-01 DT800/DT700 Multiline At half the value of this timer the IP Range: 60~65535 Sec. X
Basic Information Set- terminal sends another registration Default is 180
up –Registration Expire message to the CPU.
Timer
Basic Information Set- terminal sends another Subscribe Default is 3600
up – Subscribe Expire message to the CPU.
Timer
Basic Information Set- terminal sends a re-invite message. Default is 180
up – Session Expire
Timer
84-23-04 DT800/DT700 Multiline Minimum time the CPU accepts a ses- Range: 0~65535 Sec. X
Basic Information Set- sion timer for a new call. Default is 180
up – Minimum Session
Expire Timer

ISSUE 1.0 SL2100

Number
84-23-05 DT800/DT700 Multiline When INVITE message received from Range: 0~65535 Sec. X
Basic Information Set- SIP MLT does not contain Expires Default is 180
up – Invite Expire Timer header, the CPU uses this value for
timeout of outgoing call. E.g. The SIP
MLT hears RBT for duration of this
timer and then is disconnected.
84-23-06 DT800/DT700 Multiline Used for updating the IP terminals Range: 0x00 ~ 0xFF X
Basic Information Set- SIGNALING TOS values. Default is 00
up – Signal Type of
Service
84-23-07 DT800/DT700 Multiline The time that an IP terminal holds an Range: 0 ~ 65535 Sec. X
Basic Information Set- error message in the display. Setting 0 Default is 0
up – Error Display Tim- holds the error message indefinitely.
er
84-23-08 DT800/DT700 Multiline When Digest Authentication mode is Range: 0 ~ 4294967295 X
Basic Information Set- ON, this value is available. Default is 0
up – Digest Authoriza- After receiving Initial INVITE without
tion Registration Expire authentication information, CPU will
Timer send 401 message to the SIP MLT,
then waits for an INVITE message
with the authentication message from
SIP MLT within this timer.
Additionally, after receiving Re-REG-
ISTER message for Keep Alive pur-
pose, the CPU sends a 401 message.
84-23-10 DT800/DT700 Multiline The number of times an incorrect Range: 0 ~ 255 X
Basic Information Set- password can be entered when the Default is 0
up – Number of Pass- security key is pressed.
word Retries If set to (1), only one attempt is al-
lowed. When number of password re-
tries is met an error message displays
on the phone: Incorrect security code
password entered, press call key to
contact an administrator
84-23-11 DT800/DT700 Multiline Time to leave the terminal Locked Out Range; 0 ~ 120 X
Basic Information Set- after entering the wrong security code. Default: 0
up – Password Lock Default is 0
Time
84-23-12 DT800/DT700 Multiline Assign the network admin telephone Up to 32 Digits X
Basic Information Set- number. When the user presses the (0~9, *, #, P, R, @)
up – Reference Num- Call key to contact the network admin- Default is No Setting
ber istrator, this number is dialed.
84-23-13 DT800/DT700 Multiline Assign the IP terminals MEDIA TOS Range: 0x00 ~ 0xFF X
Basic Information Set- values. (0~9, A~F)
up – Media Type of Default is 00
Service
84-23-14 DT800/DT700 Multiline The valid period of the REFER sub- Range: 0 ~ 65535 Sec. X
Basic Information Set- scription. Default is 60
up – Refer Expire Tim-
er
84-24-01 DT800/DT700 Multiline Amount of audio in each RTP packet. Range: 1~4 X
CODEC Basic Informa- 1 = 10ms
tion Setup – Number of 2 = 20ms
G.711 Audio Frames 3 = 30ms
4 = 40ms
Default is 2
84-24-02 DT800/DT700 Multiline Select whether to compress silence 0 = Disable X
CODEC Basic Informa- with G.711. When there is silence, the 1 = Enable
tion Setup - G.711 Si- RTP packet is not sent. Default = 0
lence Detection Mode When VAD is enabled the CPU will
stop sending packets but the IP
Phone will continue to transmit silence
packets.

SL2100 ISSUE 1.0

Number
84-24-03 DT800/DT700 Multiline μ-law used in N.A. 0 = A-law X
CODEC Basic Informa- 1 = μ-law
tion Setup – G.711 Default is 1
Type
84-24-04 DT800/DT700 Multiline Minimum value of the dynamic jitter Range: 0 ~ 255ms X
CODEC Basic Informa- buffer. Default is 20
tion Setup – G.711 Jit-
ter Buffer Minimum
84-24-05 DT800/DT700 Multiline Average value of the dynamic jitter Range: 0 ~ 255ms X
ter Buffer Average
84-24-06 DT800/DT700 Multiline Maximum value of the dynamic jitter Range: 0 ~ 255ms X
ter Buffer Maximum
tion Setup – Number of 2 = 20ms
4 = 40ms
Default is 2
84-24-08 DT800/DT700 Multiline Select whether to compress silence 0 = Disable X
CODEC Basic Informa- with G.729. When there is silence, the 1 = Enable
tion Setup – G.729 RTP packet is not sent. Default is 0
Voice Activity Detection When VAD is enabled the CPU will
stop sending packets but the IP
Phone will continue to transmit silence
packets.
84-24-09 DT800/DT700 Multiline Minimum value of the dynamic jitter 0~300ms X
ter Buffer Minimum
84-24-10 DT800/DT700 Multiline Average value of the dynamic jitter 0~300ms X
ter Buffer Average
84-24-11 DT800/DT700 Multiline Maximum value of the dynamic jitter 0~300ms X
ter Buffer Maximum
84-24-17 DT800/DT700 Multiline 1 = Static X
CODEC Basic Informa- 2 = Not used
tion Setup – Jitter Buf- 3 = Adaptive immediate
fer Mode Default is 3
84-24-18 DT800/DT700 Multiline 0 ~ 30 X
CODEC Basic Informa- Default is 20
tion Setup - Voice Ac-
tivity Detection Thresh-
old
84-24-28 DT800/DT700 Multiline This assign the CODEC to be used. Range: 0~3 X
CODEC Basic Informa- 0 = G.711_PT
tion Setup – Audio Ca- 1 = Not Used
pability Priority 2 = G.729_PT
3 = G.722_PT
Default is 0
tion Setup – G.722 Au- 2 = 20ms
dio Frame Number 3 = 30ms
4 = 40ms
Default is 3

ISSUE 1.0 SL2100

Number
84-24-34 DT800/DT700 Multiline Minimum value of the dynamic jitter Range: 0 ~ 255ms X
ter Buffer Minimum
84-24-35 DT800/DT700 Multiline Average value of the dynamic jitter Range: 0 ~ 255ms X
ter Buffer Average
84-24-36 DT800/DT700 Multiline Maximum value of the dynamic jitter Range: 0 ~ 255ms X
ter Buffer Maximum
84-28-01 DT800/DT700 Multiline Maximum 64 characters. Default is No Setting X
Firmware Name Setup
– Firmware Directory
84-28-02 DT800/DT700 Multiline Maximum 30 characters. Default is No Setting X
Firmware Name Setup
– Firmware File Name
13.10 SIP MLT Quick Startup Guide

The following guides describe the setup for a SIP MLT from a default state for these modes:
• Plug and Play
• Automatic Registration
• Manual Registration
13.10.1 Plug and Play
1. Program 10-12
Assign the VoIPDB registration/signaling IP address, subnet mask, and default gateway. If no
customer provided default gateway is provided, leave Gateway IP address at 0.0.0.0.
Figure 9-26 System Data 10-12: CPU Network Setup

SL2100 ISSUE 1.0
2. Program 84-26
Assign the IP addresses that the DSP is going to use. The IP address assigned must be in the
same subnet as the address in Program 10-12-09.
After these commands are uploaded to the CPU, a system reset must be applied.
Figure 9-27 System Data 84-26: VoIPDB Basic Setup (DSP)

ISSUE 1.0 SL2100
3. Program 11-02
SIP MLT Stations are assigned to non-equipped hardware ports.
Physical Station ports are assigned automatically from lowest number ascending as cards are
added to the system.
Because of this you should assign SIP MLT Stations starting with the higher number ports. By
default all Station Ports are assigned numbers in the SL2100. These are easily changed in
Program 11-02 to the required station number as long as the leading digit/digits are set in
Program 11-01 as Extension.
Ports are dedicated to VoIP stations in groups of 2. E.g. In the image below if port 84 (Extension
184 ) is used for a SIP MLT Station that group of 2 ports (Ports 83 and 84) is now dedicated to
VoIP use only.
After one port in a block of two is used by a VoIP station, the remaining port can be used only for
another VoIP Extension.
Figure 9-28 System Data 11-02: Extension Numbering
4. This step is optional. To enable Key data and other station feature programming (before IP Phone
is brought online) the extensions must be identified as IP Phones. Once checked in the IP Phone

SL2100 ISSUE 1.0
List in PC-Pro, the extensions are available for selection in Program 15 and other station related
Programs.
Figure 9-29 IP Phone List
5. The SIP MLT Station requires assignments to be made in the phone itself. Enter the Program
Mode in the station using the following steps.
The station does not require an Ethernet connection to enter the program mode. Only power is
required. Power can be provided by POE provided by a data switch. If the data switch is providing
POE it must be using the 802.3AF standard.
For Basic bench testing only the following assignments are required:
• At this point you are prompted with a User Name and Password. These are the defaults:
User Name: ADMIN
Password: 6633222
The user name should already be entered in the terminal.
• Press Set soft key to step down to the password field.

• After you enter the password, press OK soft key.
Network Settings
• DHCP Mode – DHCP Disable. Click OK.
• IP Address – Enter the IP Address for the station, and click OK.
• Default Gateway – Enter the Default Gateway Address, and click OK. If you are testing without a
router/gateway, this must be left at the default 0.0.0.0
• Subnet Mask - Enter the Subnet Mask for the station, and click OK.
SIP Settings
• SIP User – Intercom Number
Enter the extension number for the IP station, and click OK.
• Server Address & URI – 1st Server Address
Enter the IP address assigned in command 10-12-09, and click OK.
• SIP Server Port - 1st Server Port
Enter port 5080, and click OK.
• Press the EXIT key until you are back at the Main menu.

ISSUE 1.0 SL2100
• Press the SAVE key and the phone saves the configuration to memory, reboots itself and registers
with the CPU.
13.10.2 Automatic Registration
1. Steps 1~3 are the same as for Plug and Play mode. Step 4 is not optional and MUST be assigned
when using Automatic Registration.
2. Same as Plug and Play mode.
3. Same as Plug and Play mode.
4. To enable key data and other station feature programming before IP Phone is brought online, the
extensions must be identified as IP Phones. Once checked in the IP Phone List in PC-Pro (see
images below), the extensions are available for selection in Program 15 and other station related
Programs.
Figure 9-30 IP Phone List
5. Program 10-46
Change Program 10-46-01 to Automatic.
Figure 9-31 8IPLD Server Information Setup

SL2100 ISSUE 1.0
6. Program 15-05-27
Each IP phone requires a unique personal ID index. Valid settings are 1 ~ 512.
Figure 9-32 Automatic Registration Basic Setup
Figure 9-33 Automatic Registration Personal ID Index
7. Program 84-22-01
Assign the user ID and password to be associated with the Personal ID Index assigned in Step 6.
Figure 9-34 Automatic Registration User Name and Password Assignment
required. Power can be provided by an AC adapter plugged into the phone or by POE provided by a
data switch. If the data switch is providing POE it MUST be using the 802.3AF standard.
For Basic bench testing, only the following assignments are required:
• At this point, you are prompted with a User Name and Password. These are the defaults:
User Name: ADMIN
Password: 6633222


ISSUE 1.0 SL2100
Network Settings
• DHCP Mode - DHCP Disable. Click OK.
• IP Address - Enter the IP Address for the station, and click OK.
• Default Gateway - Enter the Default Gateway Address, and click OK. If you are testing without a
router/gateway, this must be left at the default 0.0.0.0.
SIP Settings
• SIP User
- User ID - Enter User ID assigned in command 84-22. Click OK.
- Password - Enter the password assigned in command 84-22. Click OK.
- Incom Number - Enter the extension number for the IP station. Click OK.
• Server Address & URI - 1st Server Address
Enter port 5080. Click OK.
• Press the SAVE key, and the phone saves the configuration to memory, reboots itself and registers
with the CPU.
13.10.3 Manual Registration
Steps 1~4 are the same as for Section Automatic Registration on page 9-41.
1. Same as for Automatic Registration Mode.

5. Program10-46 – ChangeProgram10-46-01 to Manual.
Figure 9-35 8IPLD Server Information Setup


SL2100 ISSUE 1.0
required. Power can be provided by an AC adapter plugged into the phone or by POE provided by a
data switch. If the data switch is providing POE it must be using the 802.3AF standard.
For Basic bench testing only the following assignments are required.
• At this point, you are prompted with a User Name and Password. These are the defaults:
User Name: ADMIN
Password: 6633222

Network Settings
• DHCP Mode - DHCP Disable. Click OK.
• IP Address - Enter the IP Address for the station, and click OK.
• Default Gateway - Enter the Default Gateway Address, and click OK. If you are testing without a
router/gateway, this must be left at the default 0.0.0.0
SIP Settings
• Do not enter any information in the SIP user field. When the phone boots up, it requires a user
name and password. These are preassigned in the system. When entered correctly, the phone is
provided an extension number.
• Server Address & URI - 1st Server Address
Enter port 5080, and click OK.
• Press the SAVE key, and the phone saves the configuration to memory, reboots itself and registers
with the CPU.
13.11 IP Phone Relocation

The IP Phone Relocation feature gives users access to their IP telephone from any location by using
the override login function. Users have the flexibility of logging into their IP Station in the office as well
as remotely at the home office.
IP Phone Relocation Override
IP Phone Relocation is a feature for overriding the registration of an IP phone from various locations.
To override the registration of an IP phone, you must have the login ID and Password of that IP phone.
Conditions
• Multiple IP Phones cannot use the same user ID and the same password at the same time.
• When a user is using multiple IP Phones at the same time, the user ID and password must be
different for each phone.
• When a user is using SoftPhone (CTI mode) and controlling the IP Phone by this SoftPhone, the
user ID and password should be different for the SoftPhone and IP Phone.
• An IP Phone (IP Phone and Soft phone) with DSS console cannot override another IP Phone.

ISSUE 1.0 SL2100
• An IP Phone (IP Phone and Soft phone) with DSS console cannot be overridden from another IP
Phone.
• The login ID and Password are programmed in Program 15-05-27 and Program 84-22.
• IP Phone Relocation can be used only in Manual Registration Mode.
• Two ports of the same terminal type (Program 15-05-26) cannot be assigned to the same Personal
ID index (Program 15-05-27).
• When using Override with an active CTI connection, Program 15-05-39 must be enabled for the
extensions that will be overridden. The overriding terminal must be of the same type and number of
line keys as the terminal to be overridden. If the types of terminals and number of keys are different
between overriding and overridden phones, the Telephony Service Providers (1st Party and 3rd
Party) may not function properly.
Table 9-4 IP Phone Relocation

No. Selection
10-46-01 DT800/DT700 Server Informa- 0 = Plug and Play Set up the information of the SIP Multiline
tion Setup – Register Mode 1 = Automatic (8IPLD series) Server.
2 = Manual This Program is a system-wide setting.
Default is 0
15-05-27 IP Telephone Terminal Basic 0~128 Used when the SIP Multiline telephone is
Data Setup – Personal ID In- 0 using manual/
dex Default is 0 auto registration. Assign each phone a
unique personal index. Then go to com-
mand 84-22 to assign the user name and
password.
84-22-01 DT800/DT700 Multiline Logon Up to 32 characters Input the User ID when using manual or
Information Setup – User ID Default not assigned auto registration (Program 10-46-01).
84-22-02 DT800/DT700 Multiline Logon Up to 16 characters Input the Password when using manual or
Information Setup – Password Default not assigned auto registration (Program 10-46-01).
84-22-04 DT800/DT700 Multiline Logon 0 = Off Input the Personal ID from terminal auto-
Information Setup – Log Off 1 = On matically when log on again.
Default is 1 If set to 0, IP Phone Relocation fails.

SL2100 ISSUE 1.0
MEMO

IP Single Line Telephone
Session Initiation Protocol (SIP) Station feature provides Voice over Internet Protocol (VoIP) for IP
stations. This feature is defined by the Internet Engineering Task Force (IETF) RFC3261.
SIP analyzes requests from clients and retrieves responses from servers, then sets call parameters at
IP Single Line Telephone

either end of the communication, handles call transfer and terminates. Typically, Voice over IP services
are available from an SIP service provider.
With the VoIPDB up to 128 TDM talk paths are supported. This total may be shared among SIP
stations or SIP trunks. Registered SIP stations and/or SIP trunks require a one-to-one relation with the
VoIPDB DSP Resource. This is a required component of SIP implementation in the NEC SL2100. The
NEC SL2100 VoIPDB contains a regular TCP/RTP/IP stack that can handle real-time media and
supports industry standard SIP (RFC3261) communication on the WAN side.
For this feature, the VoIPDB is installed and assigned. The VoIPDB supports IP signaling for up to 128
(SIP Trunks and/or SIP Stations) and reduces the maximum capacity of system stations and/or Trunks
in accordance with the number of registered SIP Stations.
The NEC SL2100 supports the following CODECS that are considered to provide toll-quality
equivalent speech path.
The following voice compression methods are supported for the IP Station SIP feature:
• G.729. Low bandwidth requirement used on most Wide Area Network links.
• G.711. μLaw – High bandwidth requirement usually used on Local Area Networks.
• G.722 This CODEC is useful in fixed network, Voice over IP applications, where the required
bandwidth is typically not prohibitive.
• G.726 is an ITU-T ADPCM speech-coded standard covering the transmission of voice at rates of
16-, 24-, 32-, and 40Kbps.
The SIP Station feature set supports the HOLD and TRF features based on RFC draft.
• Draft-IETF-sipping-service-examples-09.txt.
• Section 2.5 Draft-ietf-sipping-service-examples- (Transfer - Attended) 15.txt
• IETF RFC is defined as: Internet Engineering Task Force (RFC) Request for Comments.
• The SIP Station feature set supports the Message Waiting Indication (MWI) based on RFC3842.
• SIP INFO works independent from other DTMF methods such as RFC2833. This means SIP
Terminals should send DTMF information by a single method, otherwise the system will receive both
separately causing double digits.
• When PRG 15-05-49 is set to 2: Allowed while RTP is not available, SIP INFO will be received while
RTP is not established. In-band method such as RFC2833 will be used once voice path is
established.
• When PRG 15-05-49 is set to 1: Allowed any time, SIP INFO will be received whenever they arrive.
NAT Mode for SIP Phone

• NAT mode for SIP Phone which can not use SIP P2P mode and standard SIP video call feature
uses P2P mode cannot establish in same system.
• When PRG 10-33-05 NAT mode for SIP phone is set to 1 - Enable, P2P mode for SIP Phone
becomes always Off regardless PRG 15-05-50 setting.

SL2100 ISSUE 1.0
• The system time can be provided using NTP time server updates to standard SIP terminals.
• When connecting multiple SIP Phones via NAT, PRG 15-05-18 has to be set to admit the
registration of multiple SIP Phones which are using the same IP address. For example, if you had a
STD SIP Terminal that had two lines registering with the same IP Address, you would need to flag
PRG 15-05-18 for both Extension numbers.
• In the router/firewall that the SL2100 resides behind port forwarding is required. Port forwarding at
the SIP Terminal end is not required as long as PRG 15-05-45 (Plug and Play) is enabled, which it is
by default. The ports that must be forwarded to the SL2100 are as follows:
- UDP Port 5070 MUST be forwarded to the IP Address assigned in PRG 10-12-09. UDP Ports
10020 ~ 10083 MUST be forwarded to the IP Address assigned in PRG 84-26-01.
SECTION 2 PROGRAMMING
2.1 Card Setup

Number
10-03-01 IPL Configuration - VoIP VoIPDB Type 0 ~ 3 = Not Used X
Type 4 = Built-in VoIP
5 = VoIPDB
10-03-02 IPL Configuration - Number VoIPDB Channel Built-in VoIP = 8 X
of Channel VoIPDB = 16 ~ 128
10-03-03 IPL Configuration - Number Voice Channel on VoIPDB DSP 0 ~ 128 (Read Only) X
of Voice Channel Resource
2.2 Configure VoIPDB Networking Information

The VoIPDB DSP's (PRG 84-26-01) should be connected to the same IP Subnet as the VoIPDB
signaling address (PRG 10-12-09).
If any IP Address or NIC setting is changed, the system must be reset for the changes to take affect.

Number
10-12-03 CPU Network Setup – Assign the IP Address for 0.0.0.0 ~ 126.255.255.254 X
Default Gateway the Router. 128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
Default is 0.0.0.0
10-12-09 CPU Network Setup – Assign the IP Address of the 0.0.0.0 ~ 126.255.255.254 X
IP Address VoIPDB. 128.0.0.13~191.255.255.254
192.0.0.1~223.255.255.254
10-12-10 CPU Network Setup – Assign the Subnet Mask of 255.255.0.0 X
Subnet Mask the VoIPDB. Default is 255.255.0.0
10-2 IP Single Line Telephone

ISSUE 1.0 SL2100
2.2.1 VoIPDB (DSP) Basic Setup
Program Number Program Name Description/ Assigned Data 1 2 3

Comments
84-26-01 VoIP Basic Setup – IP Assign the IP Address for Default: X
Address the DSP resource. Slot 1 = 172.16.0.20
Note: The VoIPDB IP Ad-
dresses must be statical-
ly assigned.
84-26-02 VoIP Basic Setup – RTP Assign the RTP Port 0~65534 X
Port Number Number. Default for DSP1 is
10020
84-26-03 VoIP Basic Setup – Assign the RTCP Port 0~65534 X
RTCP Port Number Number. Default for DSP1 is
(RTP Port Number + 1) 10021
2.2.2 VoIP ToS Setup
Program Program Name Description/ Assigned Data 1 2 3

Number Comments
84-10-01 ToS Setup – ToS Mode Use this field to define 0 = Disabled (Invalid) X
your SIP QoS marking 1 = IP Precedence
for ToS or Diffserv. 2 = Diffserv
When Input Data is set to Default is 0
1, Item No. 07 is invalid.
When Data is set to 2,
Item No. 02 ~ 06 are in-
valid.
2.2.3 SIP Peer to Peer

Number Comments
15-05-50 IP Telephone Terminal Basic Enable or disable Peer- 0 = No (Disable) X
Data Setup – Peer to Peer to-Peer mode for SIP 1 = Yes (Enable)
Mode phones. When PRG (default is 0)
10-33-05 NAT mode is
set to 1 (Enable), P2P
mode for SIp phones al-
ways set to Off automati-
cally regardless of this
program setting.
2.2.4 IP Extension Numbering

Number Comments
11-01-01 System Numbering Refer to the SL2100 Pro- 1 = 3 Digit; Intercom X
gramming Manual for all Default is 3 Digit; Intercom
options and default set-
tings.
11-02-01 Extension Numbering Assign up to eight digits Dial (Up to eight digits) X
for extension numbering Default
Ports 1~84 = 101~184

SL2100 ISSUE 1.0
2.2.5 SIP Extension CODEC Information

Number Comments
84-19-01 SIP Extension CODEC Informa- Define the G.711 audio 1~4 X
tion Basic Setup –Number of G. Frame Size 1 = 10ms
3 = 30ms
4 = 40ms
Default is 2
84-19-02 SIP Extension CODEC Informa- Enable/Disable Voice Ac- 0 = Disable X
tion Basic Setup – G.711 Voice tivity Detection for G.711. 1 = Enable
Activity Detection Mode Default is 0
84-19-03 SIP Extension CODEC Informa- Define the G.711 Type – 0 = A-law X
tion Basic Setup – G.711 Type μ-law is recommended in 1 = μ-law
USA. Default is 1
84-19-04 SIP Extension CODEC Informa- Define G.711 Jitter Buffer 0~300ms X
tion Basic Setup – G.711 Jitter minimum accepted val- Default is 20
Buffer (min) ue.
tion Basic Setup – G.711 Jitter setting. Default is 40
Buffer (Average)
tion Basic Setup – G.711 Jitter maximum accepted val- Default is 80
Buffer (max) ue.
84-19-07 SIP Extension CODEC Informa- Define the G.729 audio 1~6 X
tion Basic Setup – Number of Frame Size. 1 = 10ms
3 = 30ms
4 = 40ms
5 = 50ms
6 = 60ms
Default is 2
84-19-08 SIP Extension CODEC Informa- Enable/Disable Voice Ac- 0 = Disable X
tion Basic Setup – G.729 Voice tivity Detection for G.729. 1 = Enable
tion Basic Setup – G.729 Jitter minimum accepted val- Default is 20
Buffer (min) ue.
tion Basic Setup – G.729 Jitter setting. Default is 40
Buffer (average)
tion Basic Setup – G.729 Jitter maximum accepted val- Default is 80
Buffer (max) ue.
84-19-17 SIP Extension CODEC Informa- Define the Jitter Buffer 1 = Static X
tion Basic Setup – Jitter Buffer mode – supported Static 2 = Not used
Mode or Immediate. 3 = Adaptive Immediately
Default is 3
84-19-18 SIP Extension CODEC Informa- Define the VAD Thresh- 0~30 X
tion Basic Setup – VAD Thresh- old. Default is 20
old
84-19-28 SIP Extension CODEC Informa- Define Audio capability 0 = G.711_PT X
tion Basic Setup – Audio Capa- priority. 1 = Not Used
bility Priority 2 = G.729_PT
3 = G.722
4 = G.726
5 = Not Used
Default is 0

ISSUE 1.0 SL2100

Number Comments
84-19-33 SIP Extension CODEC Informa- 1~4 X
tion Basic Setup – Number of 1 = 10ms
3 = 30ms
4 = 40ms
Default is 3
84-19-35 SIP Extension CODEC Informa- 0~255ms X
tion Basic Setup – G.722 Jitter Default is 30
Buffer (min)
Buffer (Average)
Buffer (max)
84-19-38 SIP Extension CODEC Informa- 1~4 X
tion Basic Setup –Number of G. 1 = 10ms
3 = 30ms
4 = 40ms
Default is 3
84-19-39 SIP Extension CODEC Informa- 0 = Disable X
tion Basic Setup – G.726 Voice 1 = Enable
Buffer (min)
Buffer (Average)
Buffer (max)
84-19-49 SIP Extension CODEC Informa- 0 = Disable X
tion Basic Setup – RTP Filter 1 = Enable
Default is 1
84-19-65 SIP Extension CODEC Informa- This setup specifies the 0 = mode1
tion Basic Setup – Video Quali- maximum capacity of vid- 1 = mode2
ty Mode eo. Default is 0
Refer to following ※
about the definition in
each mode.
84-19-66 SIP Extension CODEC Informa- 0 = H.264
tion Basic Setup – Video codec Default is 0
84-19-67 SIP Extension CODEC Informa- This setup specifies the 0 = Static
tion Basic Setup – Jitter Buffer jitter buffer mode of the 1 = Self Adjusting
Mode for Video video stream. Jitter buffer Default is 2
size adjustment method
decides depending on
the mode setting. Please
set to 2 (Self adjusting)
usually.
84-19-68 SIP Extension CODEC Informa- This setup specifies the 0 ~ 1000 (ms)
tion Basic Setup – Minimum Jit- minimum value of jitter Default is 70
ter Buffer for Video buffer for the video
stream.
This value must be
smaller than the value of
the maximum jitter buffer.

SL2100 ISSUE 1.0

Number Comments
tion Basic Setup – Initial Jitter initial value of jitter buffer Default is 140
Buffer for Video for the video stream.
This value must be
smaller than the value of
the maximum jitter buffer
and be bigger than the
value of the minimum jit-
ter buffer.
tion Basic Setup – Maximum maximum value of jitter Default is 210
Jitter Buffer for Video buffer for the video
stream. It is used only
when "67-Jitter Buffer
Mode for video" is
1:Fixed.
This value must be big-
ger than the value of the
minimum jitter buffer.
Table 10-1 ※1
Codec Video Quality Mode Frame rate (fps) bit rate (bps)
H264 Mode1 15 384
Mode2 15 768
2.2.6 SIP Extension Basic Information Setup

Number Comments
84-20-01 SIP Extension Basic Informa- Define SIP station Proxy 1~65535 X
tion Setup – Registrar/Proxy Port. Default is 5070
Port
84-20-02 SIP Extension Basic Informa- Define the periodic re- 0~65535 X
tion Setup – Session Timer Val- fresh time that allows Default is 180
ue both user agents and
proxies to determine if
the SIP session is still
active.
84-20-03 SIP Extension Basic Informa- Define to convey the 0~65535 X
tion Setup – Minimum Session minimum allowed value Default is 180
Timer Value for the SIP session timer.
84-20-04 SIP Extension Basic Informa- Define the SIP Extension 0 = Request URI X
tion Setup – Called Party Info presented Caller ID infor- 1 = To Header
mation. Default is 0
84-20-05 SIP Extension Basic Informa- Define the time out re- 0~256 seconds X
tion Setup – Expire Value of In- sponse value for SIP in- Default is 180
vite vite.
84-20-06 Expire Value of Invite (send) The expiration time is set 1~3600 seconds X
for the Invite message. Default is 180

ISSUE 1.0 SL2100
2.2.7 IP Phone Configuration

Number Comments
15-05-01 IP Telephone Terminal Basic Review the type protocol 0 = NGT X
Data Setup – Terminal Type support by the IP Phone. 1 = H.323
Viewing Only – No 2 = SIP
changes permitted. 3 = MEGACO
4 = SIP-MLT
READ ONLY
Default = 3
15-05-02 IP Telephone Terminal Basic MAC Address of regis- MAC address X
Data Setup – Terminal MAC tered MLT SIP phone is 00-00-00-00-00-00 to
Address stored and/or can input FF-FF-FF-FF-FF-FF
the MAC address of an Default is
MLT SIP phone so when 00-00-00-00-00-00
it comes online it is provi-
ded with the extension in
which the MAC address
matches.
15-05-07 IP Telephone Terminal Basic Informational Only regis- 0.0.0.0~255.255.255.255 X
Data Setup – Using IP Address tered IP Phones Default is 0.0.0.0
15-05-16 IP Telephone Terminal Basic Assign the authentication Up to 24 characters X
Data Setup – Password password for SIP single Default not assigned
line telephones.
15-05-18 IP Telephone Terminal Basic If an adapter has one IP 0 = Not Used X
Data Setup – IP Duplication Al- address coming into it 1 = Group 1
lowed Group but multiple extensions 2 = Group 2
off of it, assign all exten- 3 = Group 3
sions to a group so the 4 = Group 4
CPU knows that the one 5 = Group 5
IP address is assigned to 6 = Group 6
multiple extensions. 7 = Group 7
8 = Group 8
9 = Group 9
10 = Group 10
Default is 0
15-05-40 IP Telephone Terminal Basic 0 = Both Name and Number X
Data Setup – Calling Name Dis- 1 = Name only
play 2 = Number only
3 = None
Default = 0
15-05-41 IP Telephone Terminal Basic 0 ~ 24 X
Data Setup – Time Zone (-12 ~ +12 hour)
Default = 12
15-05-43 IP Telephone Terminal Basic 0 = Disable X
Data Setup – Video Mode 1 = Enable
Default = 0
15-05-44 IP Telephone Terminal Basic 0 = Disable X
Data Setup – Using STD-SIP 1 = Enable
Display for CPN Default = 0
15-05-49 IP Telephone Basic Setup - Re- Determines whether SIP 0 = Disable
ceiving SIP INFO INFO messages are re- 1 = Allowed any time
ceived by the system. 2 = Allowed while RTP is
not available
Default = 2

SL2100 ISSUE 1.0
2.2.8 NAT Mode for Standard SIP terminal

Number
10-12-03 CPU Network Setup – Assign the IP Address for 0.0.0.0 ~ 126.255.255.254 X
Default Gateway the Router. 128.0.0.1 ~ 191.255.255.254
192.0.0.1 ~ 223.255.255.254
Default is 0.0.0.0
10-12-07 CPU Network Setup - Define the IP Address of the 0.0.0.0 ~ 126.255.255.254 X
NAPT Router IP Ad- WAN side of the router. 128.0.0.1 ~ 191.255.255.254
dress (Default Gate- 192.0.0.1 ~ 223.255.255.254
way [WAN]) Default is 0.0.0.0
10-12-08 CPU Network Setup - When receiving ICMP redi- 0 = Enable X
ICMP Redirect rect messages, this deter- 1 = Disable
mines of the IP Routing Ta- Default is 0
ble updates automatically or
not.
10-12-09 CPU Network Setup – Assign the IP Address of the 0.0.0.0 ~ 126.255.255.254 X
IP Address VoIPDB. 128.0.0.13~191.255.255.254
192.0.0.1~223.255.255.254
10-12-10 CPU Network Setup – Define the Media Gateway 128.0.0.0 X
Subnet Mask Subnet Mask Address. 192.0.0.0
224.0.0.0
240.0.0.0
248.0.0.0
252.0.0.0
254.0.0.0
255.0.0.0
255.128.0.0
255.192.0.0
255.224.0.0
255.240.0.0
255.248.0.0
255.252.0.0
255.254.0.0
255.255.0.0
255.255.128.0
255.255.192.0
255.255.224.0
255.255.240.0
255.255.248.0
255.255.252.0
255.255.254.0
255.255.255.0
255.255.255.128
255.255.255.192
255.255.255.224
255.255.255.240
255.255.255.248
255.255.255.252
255.255.255.254
255.255.255.255
default is 255.255.0.0
10-12-11 CPU Network Setup - Define the LAN interface 0 = Auto Detect X
NIC Setup speed and mode of the VoIP 1 = 100Mbps, Full Duplex
application supported. 2 = 10Mbps, Full Duplex
3 = 1Gbps, Full Duplex
default is 0
15-05-50 IP System Operation Enable or disable Peer-to- 0 = No (Disable) X
Setup – SIP Peer to Peer mode for SIP phones. 1 = Yes (Enable)
Peer Mode When PRG 10-33-05 NAT default is 0
mode is set to 1 (Enable),
P2P mode for SIp phones
always set to Off automati-
cally regardless of this pro-
gram setting.

ISSUE 1.0 SL2100

Number
10-33-02 SIP Registrar/Proxy When connecting STD SIP 0 = No (Disable) X
Information Basic Set- Terminal via NAT, this option 1 = Yes (Enable)
up – Authentication must be enabled to prohibit default is 1
Mode illegal SIP phone registra-
tion.
10-33-05 SIP Registrar/Proxy When system controls re- 0 = No (Disable) X
Information Basic Set- mote SIP phone via NAT 1 = Yes (Enable)
up NAT Mode router, set this program to 1 default is 0
= Enable.
10-37-01 UPnP Setup – UPnP Default Gateway (WAN), 0 = No (Disable) X
Mode PRG 10-12-07 can be set 1 = Yes (Enable)
automatically when this pro- default is 0
gram is set to 1 = Enable.
10-58-01 Network Address – If there are other networks Assign a valid IP Address or as- X
Network Address connected to this system sign a valid Network Address.
that are not to be routed default is 0.0.0.0
through NAPT translations,
then these networks must
be identified in PRG 10-58.
Use this PRG to assign the
individual IP Address (e.g.
192.168.1.100) or assign the
whole network address (e.g.
192.168.1.0).
10-58-02 Network Address – If there are other networks Assign a valid subnet mask. de- X
Subnet Mask connected to system that fault is 0.0.0.0
are not to be routed through
NAPT translations, then
these networks must be
identified in PRG 10-58. Use
this PRG to assign the sub-
net mask for the IP Address
entered in PRG 10-58-01.
15-05-16 IP Telephone Terminal Assign the authentication Up to 24 characters X
Basic Data Setup – password for SIP single line Default not assigned
Password telephones.
15-05-45 IP Telephone Terminal Per IP Single line telephone, 0 = No (Disable) X
Basic Data Setup- enable NAT Plug and Play 1 = Yes (Enable)
NAT Plug & Play so that port forwarding is default is 1
NOT required in the router
the IP single line telephone
resides behind. Effective on-
ly when PRG 10-46-14 is set
to 1 = Enable.
15-05-47 IP Telephone Terminal On a per station basis, this 0 = User Timer in Program X
Basic Data Setup – setting defines the SIP reg- 84-23-01 60~65535(sec)
Registration Expire istration expiry timer. If this default is 180 seconds
Timer for NAT value is set to 0, for the ter-
minal, the value in PRG
84-23-01 is applied.
15-05-48 IP Telephone Terminal On a per station basis, this 0 = User Timer in Program X
Basic Data Setup – setting defines the SIP sub- 84-23-01 60~65535(sec)
Subscribe Expire Tim- scribe expiry timer. If this default is 180 seconds
er for NAT value is set to 0, for the ter-
minal, the value in PRG
84-23-02 is applied.
84-26-01 VoIPDB Basic Setup Assign the IP Address for xxx.xxx.xxx.xxx X
– IP Address each DSP resource on the Default:
VoIPDB Slot 1 = 172.16.0.20
84-26-02 VoIPDB Basic Setup Assign the RTP Port Num- 0~65534 X
– RTP Port Number ber. Default for DSP1 is 10020

SL2100 ISSUE 1.0

Number
84-26-03 VoIPDB Basic Setup Assign the RTCP Port Num- 0~65535 X
– RTCP Port Number ber. Default for DSP1 is
10020~10083
2.2.9 NTP Time Server

Number Comments
10-65-01 NTP Server Set 1 when you want to 0 = Disable (Stop)
start the NTP Server. 1 = Enable (Start)
default is 0 (Stop)
10-65-02 NTP Server Port Set the receiving port of 1 ~ 65535
the NTP Server. default is 123
2.3 SIP Phone Example

NEC SL2100
Chassis
Switch
VoIP
VoIPDB 192.168.1.20
VoIPDB DSP: 192.168.1.21
Subnet Mask: 255.255.255.0
SIP Soft Phone SIP Phone

NAPT
SECTION 1 NAPT 11
1.1 Introduction
NAPT, or Network Address Port Translation, is a method by which a private address (or addresses)
NAPT
and their TCP/UDP ports are translated into a single public address and its TCP/UDP ports. In the
case of IP phones with the SL2100 it allows their connection to a public (Internet) IP address which is
then converted back to the private (non-Internet) IP address on the customer’s network. The
translation is available at the SL2100 end as well as at the remote IP Phone end of the connection if
required.
IP Phones connected via NAPT
SL1100
192.168.1.10/24 VoIP Gateway RTP = 10020 RTCP = 10021
192.168.1.1 (Gateway)
192.168.1.11 (VoIP Gateway)
192.168.1.2/24
NAPT
Router
Port Forwarding in this router should be set
as follows.....
UDP ports 5080~5081 to 192.168.1.10
UDP ports 10020~10083 to 192.168.1.11
1.1.1.1
Public IP
Public IP Port Forwarding in this router (if necessary) is as follows.....

UDP ports 5060 to 192.168.4.2 (IP Phone control)
UDP ports 3462 to 192.168.4.2 (IP Phone Voice)
192.168.4.1/24
Voice for a call is sent to Public IP

Address 1.1.1.1.
ports 10020~10083.
192.168.4.2/24
IP Phone
Figure 11-1 NAPT Configuration Example

SL2100 ISSUE 1.0
1.2 SL2100 Requirements

The following information provides requirements for NAPT.
Main Software
NAPT is supported with the V1.00 or higher release of the SL2100.
Hardware
The SL2100 requires the following hardware:

• CPU (V1.00 or higher)
• VoIP Daughter Board
Capacity
A maximum of 112 IP phones can be connected.
1.3 Installation
The following settings have been added for NAT traversal in the 8IPLD IP Terminal.
To enter IP phone programming at the terminal, press HOLD, TRANSFER, *, #. User name is ADMIN
and password is 6633222 (NEC).
1.3.1 Settings for terminals
Setting location: 0. Config/ 2. SIP Settings/ 8. NAT Traversal
Number and Setting Val- Default Factory Auto Con- Description

Name of Set- ue Value Value fig
ting
1. NAT Traver- 1. Disable 1. Disable Available Available Settings for NAT Traversal:
sal Mode 2. Dynamic Disable: Disables NAT Traversal
3. Static Dynamic: Performs NAT Traversal using a dy-
namic conversion table.
Static: Performs NAT Traversal using a static
conversion table and requires the WAN IP Ad-
dress to be entered into the IP Terminal.
2.Network Area A character No value Available Available The name of the network area to which termi-
Name string nals belong. Specify up to 32 alphanumeric
characters. Step is optional.
3.WAN Settings See table below.
Setting location: 0. Config/ 2. SIP Settings/ 8. NAT Traversal/ 3. WAN Settings
Number and Setting Value Default Factory Auto Config Description

Name of Set- Value Value
ting
1. WAN Mate IP IP Address 0.0.0.0 Available Available WAN Address of the router that the SL2100
Address resides behind. This setting must match
what is programmed in PRG 10-12-07.
2. WAN SIP Mate 1024~65535 5060 Available Available Port number the SL2100 uses for SIP reg-
Port istration in PRG 10-46-06.
3. WAN Self IP IP Address 0.0.0.0 Available Available Only used when Static NAT is enabled.
Address This setting is the WAN address of the
router that the NAPT Terminal resides be-
hind.
11-2 NAPT
ISSUE 1.0 SL2100
Setting location: 0. Config/ 1. Network Settings/ 6. Advanced Settings/ 5. Self Port Settings
Number and Setting Value Default Factory Auto Config Description

Name of Set- Value Value
ting
1. RTP Self Port 1024~65528 3462 Available Not available The number of the port receiving RTP
(Even numbers data.
only) At default this is assigned to port 5060.
The First IP phone on this local LAN can
use this port. The second IP phone
would need to be changed to port 5062.
2. SIP Self Port 1024~65535 5060 Available Not available The number of the port receiving SIP
data.
At default this is assigned to port 3462.
The first IP phone on this local LAN can
use this port. The second IP phone
would need to be changed to port 3464.
SECTION 2 CONDITIONS
• The NAPT feature supports CPU software V1.00 or higher.
• Terminals using NAPT must be at firmware V1.0.0.0 or higher.
• IP terminals can be connected via NAT router or WAN (direct connection).
• The NAT router on the SL2100 side must have a static WAN IP address.
• The software change Programs 15-05-47 and 15-05-48 to a shorter interval. These programs are
changed on a per station basis. Non NAPT phones will still use Programs 84-23-01 and 84-23-02
while only NAPT phones will use Programs 15-05-47 and 15-05-48.
• It is necessary to set Program 10-46-14 to OFF when the VoIPDB is assigned a global (public) IP
address.
• When Program 10-46-14 is set to ON, it references programs 10-58-01 and 10-58-02. These
programs are used to define any destination networks that do not get sent through the NAPT
translations.
• UDP ports in the remote routers may be required to be forwarded to the IP Terminals.
• NAPT can be used for SIP trunks and terminals on the same system.
SECTION 3 RESTRICTIONS
• With static NAT, the terminal needs a static IP Address assigned to it, or entries in the DHCP must
be made to provide the same IP Address to the terminal.
• The NAT router on the terminal side must have the function for setting up static NAT.
• A conversion table must be manually set up for the NAT router on the terminal side.
• If installing multiple terminals in the domain of the NAT router on the terminal side, the RTP Self port
and SIP Self port for each terminal must be specified so as to avoid overlapping.
• The SIP server cannot be switched. (Only one address can be registered as the SIP server.)
Dynamic NAT
• The NAT router on the terminal side must have the function for setting up dynamic NAT.
• It is assumed that port numbers are not changed by the NAT router on the terminal side. If a port
number is changed by NAT router, NEC does not guarantee proper operation.
• If installing multiple terminals in the domain of the NAT router on the terminal side, the RTP Self port
and SIP Self port for each terminal must be specified so as to avoid overlapping.
• The SIP server cannot be switched. (Only one address can be registered as the SIP server.).

SL2100 ISSUE 1.0
SECTION 4 MINIMUM REQUIRED PROGRAMMING

The Level 1, Level 2 and Level 3 columns indicate the programs that are assigned when
programming this feature in the order they are most commonly used. These levels are used with
PCPro and WebPro wizards for feature programming.
• Level 1 – these are the most commonly assigned programs for this feature.
• Level 2 – these are the next most commonly assigned programs for this feature.
• Level 3 – these programs are not often assigned and require an expert level working knowledge of
the system to be properly assigned.

Number
1 2 3
10-12-01 CPU Network Setup - IP Address Assign the IP Address for the 0.0.0.0 ~ ✓
CPU's NIC card. If a VoIPDB is in- 126.255.255.254
stalled in the system it is recom- 128.0.0.1 ~
mended to set this to 0.0.0.0 and 191.255.255.254
all connections to the system will 192.0.0.1 ~
be made through the VoIPDB. 223.255.255.254
(default =192.168.0.10)
10-12-03 CPU Network Setup – Default Assign the default gateway IP ad- 0.0.0.0 ~ ✓
Gateway dress for the CPU. 126.255.255.254
128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
(default = 0.0.0.0)
10-12-07 CPU Network Setup – NAPT Rout- Define the IP Address of the WAN 0.0.0.0 ~ ✓
er IP Address side of the router. 126.255.255.254
(Default Gateway [WAN]) 128.0.0.1 ~
191.255.255.254
192.0.0.1 ~
223.255.255.254
(default = 0.0.0.0)
10-12-09 CPU Network Setup – IP Address Assign the IP Address for the 0.0.0.0 ~ ✓
VoIPDB. If a VoIPDB is installed 126.255.255.254
in the system it is recommended 128.0.0.1 ~
to set PRG 10-12-01 to 0.0.0.0 191.255.255.254
and all connections to the system 192.0.0.1 ~
will be made through the VoIPDB. 223.255.255.254
(default = 172.16.0.10)
11-4 NAPT
ISSUE 1.0 SL2100

Number
1 2 3
10-12-10 CPU Network Setup – Subnet Define the Media Gateway Sub- 128.0.0.0 ✓
Mask net Mask Address. 192.0.0.0
224.0.0.0
240.0.0.0
248.0.0.0
252.0.0.0
254.0.0.0
255.0.0.0
255.128.0.0
255.192.0.0
255.224.0.0
255.240.0.0
255.248.0.0
255.252.0.0
255.254.0.0
255.255.0.0
255.255.128.0
255.255.192.0
255.255.224.0
255.255.240.0
255.255.248.0
255.255.252.0
255.255.254.0
255.255.255.0
255.255.255.128
255.255.255.192
255.255.255.224
255.255.255.240
255.255.255.248
255.255.255.252
255.255.255.254
255.255.255.255
(default = 255.255.0.0)
10-46-06 Register Port 0~65535 5080 ✓
Assign the port number to which
the SIP messages are sent to on
the VoIPDB. This same port num-
ber must be assigned in the SIP
Multiline terminals. If this com-
mand is changed, it requires a
CPU reset.
10-46-13 Subscribe Session Port 0~65535 5081 ✓
10-46-14 NAT Mode Turns On/Off the NAT mode of the 0 = Off ✓
system. 1 = On
Default = Off
15-05-45 NAT Plug&Play Effective when PRG 10-46-14 is 0 = Off ✓
set to NAT Mode. Select sending 1 = On
RTP port number to remote rout- Default = Off
er, use from negotiation result (0)
or received RTP packet (1).
15-05-47 IP Telephone Terminal Basic Data On a per station basis, this setting 0 = Disable ✓
Setup - Registration Expire Timer defines the SIP registration expiry 60 ~ 65535 (sec)
for NAT timer. This setting only applies to Default = 180
8IPLD stations connected via
NAPT. If this value is set to 0, for
a NAPT terminal, the value in
PRG 84-23-01 is applied.
15-05-48 IP Telephone Terminal Basic Data On a per station basis, this setting 0 = Disable ✓
Setup - Subscriber Expire Timer defines the SIP subscribe expiry 60 ~ 65535 (sec)
for NAPT timer. This setting only applies to Default = 180
8IPLD stations connected via
NAPT. If this value is set to 0, for
a NAPT terminal, the value in
PRG 84-23-02 is applied.

SL2100 ISSUE 1.0

Number
1 2 3
84-26-01 VoIPDB Basic Setup (DSP)– IP Assign the IP address for the Default = 172.16.0.20 ✓
Address VoIP Gateway.
84-26-02 VoIPDB Basic Setup (DSP)– RTP Assign the RTP port number to be VoIP GW = ✓
Port Number used for the DSP on the VoIPDB. 10020~10083
84-26-03 VoIPDB Basic Setup (DSP)– Define the port number for RTCP VoIP GW = 10021 ✓
RTCP Port Number (RTP Port to use for each DSP.
Number + 1)
11-6 NAPT
All DSP Busy Indication
The All DSP Busy feature is used to alert users via telephone displays and/or Alarm reports when all
DSP (VoIP) resources in the system are being used. This can be used to trouble shoot issues or to
alert when the current hardware might need to be upgraded to a higher capacity.
All DSP Busy Indication

Alarm Message Format:
The Alarm message for will vary depending on what type of resource is unavailable, and will be
displayed on display telephones and included in reports.
Table 12-1 Alarm Types
Parameters Description
STA DSP for IP Station Calls Were All Busy.
TRK DSP for Trunk Calls Were All Busy, includes SIP.
Alarm Report Example:
The report example below shows an alarm for all busy Station and Trunk DSPs.
<< ALARM REPORT >> 01/22/2009 23:37

LVL NO STAT DATE TIME ITEM UNIT SLT PRT PARAMETER
MAJ 0068 ERR 01/22/09 09:30 VoIP All DSP Busy VoIPDB 01 00 STA
MAJ 0068 ERR 01/22/09 09:31 VoIP All DSP Busy VoIPDB 01 00 TRK
MIN 0002 REC 01/22/09 09:32 PKG Installation PRIU 02 00
LCD Display
LCD Display Indication Note

Clock/Calendar XX = Slot number of CPU with VoIPDB.
VoIP All Busy XX
Soft Key
SECTION 2 SERVICE CONDITIONS

• When using IP Phones, the alarm is shown on both terminals involved in that call if they are both on
the same system.
• The alarm cannot be displayed on Standard SIP Phones or Single Line phones.
• If a call from a Standard SIP telephone to a Multiline telephone cannot be established due to an All
DSP Busy condition, the Multiline telephone will not display the “All DSP” busy message.
• If a SIP trunk call is sent to the SL2100 when all DSP resources are busy, the call is rejected but the
alarm is not displayed on any system telephone.

SL2100 ISSUE 1.0
• The default alarm setting is Minor.
SECTION 3 RELATED FEATURES

• IP Multiline Station (SIP)
• IP Trunk – (SIP) Session Initiation Protocol
SECTION 4 GUIDE TO FEATURE PROGRAMMING

Number
1 2 3
20-13-52 VoIP All DSP Busy Display Set on a per station class of serv- 0 = Off ✓
ice basis, whether the “All DSP 1 = On
Busy” alarm displays on the LCD (default = 1)
when the caller makes an IP call
and there is no VoIP DSP re-
source.
90-10-01 System Alarm Setup Alarm Number 68 is used for All 0 = Not set ✓
DSP Busy. 1 = Major
2 = Minor
(default = 2)
12-2 All DSP Busy Indication

SL Net
The software provides a maximum of 256 ports in the entire network.
This SL Net feature is only supported when networked with another SL2100 or SL1100; no other
13
system types are available.
SL Net
SECTION 1 INTRODUCTION
SL Net allows networking between multiple SL2100’s and SL1100's to act as a single “virtual” SL2100
system. Interconnected with VoIP, each phone system becomes a node on the network that can
communicate with any other phone system node. Systems can be installed separately in the same
building, or in Remote Offices connected via a qualified network.
A few benefits of SL Net are:

• Centralized Network Attendant
Centralized Network Attendant allows multiple networked systems to share a single centralized
attendant. The centralized attendant can receive calls from and transfer calls to any destination
throughout the whole network. This allows calls to route as if they were part of a single, much larger
system.
• Centralized Voice Mail
Centralized Voice Mail allows one voice mail system to be installed in a single node. Centralized
Voice Mail does not have to be used in an SL Net network. Each system can still have its own
independent voice mail.
• ICM calling between all sites
Users may place an intercom call or transfer a call to any location by simply dialing an extension
number.
• Sharing Trunk Lines between all sites
Users may access trunks at any site and make calls as if they were calling from their own local
system. Inbound calls can come into one central location and then be routed to any destination
extension number in the network. At the same time each site can still have their own independent
trunks. It is recommended that each site have at least one analog trunk to dial 911 in the case of an
emergency.
• Network BLF Indication/Centralized Call Park Orbits
Users can see the status of other extensions throughout the network as if they were all in the same
system. Park orbits can also be shared and viewed by all users in the network.
SL Net requires a system license per node, the license is: SL2100 SL NET-08 LIC. This license is a
Channel license. License would be required per channels which are used for SL Net in each system.
SECTION 2 SYSTEM CAPACITY

SL Net allows a maximum of 51 systems to be networked together without exceeding a maximum of
256 ports in the entire network. The 256 port capacity is a sum of station and trunk ports in all nodes.
When the capacity is exceeded, all systems will enter a standalone mode and will not be able to
communicate with each other. At this point the systems can only utilize resources within their own

SL2100 ISSUE 1.0
location. Below is an example showing a network that exceeds the 256 port maximum capacity when
site 5 is added to the network.
Site 1 Site 2
20 Station Ports + 12 CO 16 Station Ports + 4 CO

Lines = 32 Total Ports Lines = 20 Total Ports
Network
Site 3 Site 5
Site 4
12 Station Ports + 4 CO 12 Station Ports + 4 CO
Lines = 16 Total Ports Lines = 16 Total Ports
32 Station Ports + 8 CO
Lines = 40 Total Ports
When the capacity is exceeded, an alarm report is generated and the message "NW port limit
exceeded" is displayed on an Alarm indication telephone. To restore the network, so all systems can
communicate with each other, the system totals need to be brought below the 256 port maximum.
After the necessary ports (station or trunk) are removed from a system, a restart of the SL2100 is not
required. Every time a system in an SL Net network is reset, a port count is performed. If the network
port count is below 256, all systems are allowed to communicate.
InMail ports are not counted against the 256 port maximum capacity.
Each system will require a CPU-C1 and VoIPDB, which by default will provide 8 channels (by CPU-C1
only) and 16 channels (by CPU-C1 + VoIPDB) to be shared for all IP related devices (e.g. IP Phones,
IP Trunks, SL Net). If more than 16 channels are required at any site, the system must have the
following license: SL2100 IP CHANNEL-16 LIC (5103). With this license installed, the system will now
have 32 channels to share for all IP devices. Every system that requires 32 ports must purchase and
install this license. Up to 256 channels can be set per system.
SECTION 3 NETWORK REQUIREMENTS

The voice quality of VoIP depends on variables such as available bandwidth, network latency, and
quality of service initiatives (QoS), all of which are controlled by the network and internet service
providers. Because these variables are not within NEC's control, the performance of the users IP-
based voice solution cannot be guaranteed. Therefore, NEC recommends connecting the VoIP
equipment through a fully managed data network with Quality of Service (QOS) implemented.
For a network to be suitable for VoIP it must pass specific requirements. The requirements are:
• One way delay must not exceed 150 ms
• Round trip delay must not exceed 300 ms
• Packet loss must not exceed 1 %
• Data switches must be manageable
• No half-duplex equipment may be present in the network
• Routers must provide QOS
Depending upon how the QOS policies are built in the network, assignments may be needed in the CPU
(PRG 84-10).
13-2 SL Net
ISSUE 1.0 SL2100
• Adequate bandwidth for the estimated VoIP traffic must be available

See below chart for bandwidth calculations.
Below is a chart that shows the average bandwidth per VoIP call over Ethernet.
Codec Packet Size Bandwidth Codec Packet Size Bandwidth

Used Used
G.711 10 ms 110.4 kbps G.729 10 ms 54.4 kbps
G.711 20 ms 87.2 kbps G.729 20 ms 31.2 kbps
G.711 30 ms 79.5 kbps G.729 30 ms 23.5 kbps
G.711 40 ms 75.6 kbps G.729 40 ms 19.6 kbps
G.722 10 ms 110.4 kbps G.729 50 ms 17.3 kbps
G.722 20 ms 87.2 kbps G.729 60 ms 15.7 kbps
G.722 30 ms 79.5 kbps
G.722 40 ms 75.6 kbps
For example, if one site plans on making a maximum of 16 calls across the network using G.729 with
a 30 ms packet size, there must be a minimum of 376 kbps available for voice traffic. The QOS policy
for this network should allow for 376 kbps to be set aside for voice prioritization.
SECTION 4 QUALITY OF SERVICE SETTINGS (QOS)

Quality of Service (QOS) is one of the most important factors for VoIP. QOS is used to prioritize voice
packets over data packets during times of network congestion. There are many ways that QOS can be
implemented in the network and one of the most common ways QOS is implemented is by using IP
Precedence or Diffserv. If the networks QOS policy is based on IP Precedence or Diffserv then there
are settings required in the SL2100.
Program 84-10 is used to assign the IP Precedence or Diffserv Values per Protocol Type. For SL Net
only two protocol types will be selected. All signaling packets will be marked with the values assigned
for protocol type “H.323”. All voice packets will be marked with the values assigned for protocol type
“RTP/RTCP”.
SECTION 5 IP PRECEDENCE
IP Precedence uses the first 3 bits of the TOS field to give eight possible precedence values (0 ~ 7).
Under normal circumstances the higher the number the higher the priority. However this is left to the
network administrator for setup. When assigning IP Precedence values (for SL Net) go to program
84-10-01 and change the type from Disabled to IP Precedence. Then in program 84-10-02 assign the
value for the signaling (H.323) and voice (RTP/RTCP) packets. Below is an example where the
signaling packets are to be tagged with an IP Precedence of 4 and the voice packets are to be tagged
with an IP Precedence of 5.

SL2100 ISSUE 1.0
Figure 13-1 IP Precedence
After changes are made to Program 84-10 the system will need to be reset before the proper values are
inserted into the IP packets.
SECTION 6 DIFFSERV
Diffserv is also known as Differential Services Code Point (or DSCP for short). It uses the first 6 bits of
the TOS field, therefore giving 64 possible values. The following list shows the most common Diffserv/
DSCP Code Points and their names along with the proper setting in the SL2100.
Table 13-1 Diffserv Parameters
SL2100 Setting (DSCP Code Point) Name

0 Best Effort (BE)
8 Class Selector 1 (CS1)
10 Assured Forwarding 11 (AF11)
46 Expedited Forwarding (EF)
13-4 SL Net
ISSUE 1.0 SL2100
SL2100 Setting (DSCP Code Point) Name

When assigning Diffserv values (for SL Net) go to program 84-10-01 and change the type from
Disabled to Diffserv. Then in program 84-10-07 assign the value for the signaling (H.323) and voice
(RTP/RTCP) packets. The next table shows an example where the signaling packets are to be tagged
as Class Selector 4 and the voice packets are to be tagged as Expedited Forwarding.
Figure 13-2 Setup Example
After changes are made to Program 84-10 the system will need to be reset before the proper values are
inserted into the IP packets.
6.1 Conditions
• A maximum of 50 nodes and a total of 256 ports throughout the network.
InMail ports do not count against the 256 port capacity.
• This feature is only supported when networked with another SL1100 or SL2100; no other system
types are available.
• Each system must be individually licensed for this feature with the following license: SL2100 SL
NET-08 LIC.
• The system requires a VoIPDB daughter board on the CPU-C1 when more than nine VoIP channels
are used in the system. The CPU-C1 is initially available a maximum of eight VoIP channels.
• Each site must have different extension numbers assigned. The same extension number cannot
exist at multiple sites.
• Call redirect is not supported with SL Net networking.
• Dual Hold across the network is not supported.
• If calls across SL Net are to follow the local ARS routing, all sites must use ARS routing.
• SL Net is not supported through NAT.
• A Trunk Access via Networking key (*06) will not light up when all trunks in the Remote site trunk
group are busy. If a user tries to access a trunk, when they are all busy, the word “Busy” will be in
the display and the user will hear Busy Tone but the key will not light up.
• Camp On across SL Net is only supported to a Busy extension.

SL2100 ISSUE 1.0
• Hold, Transfer, and Park recall timers will follow the timer of the system where the call is on hold
(Trunk and Station). For example, a user in Site A calls a user in Site B. Site B answers the call and
places the call on hold. The hold recall time is based on Site A because the call on hold is in Site A
and not site B.
• The allowing or denying of Class of Service features in an SL Network must be performed network
wide. For example, if users in Class of Service 1 at site 1 want to block the Camp On feature a
change will have to be made in Class of Service 1 of all systems in the network.
• Paging to a networked system can only be activated by dialing a service code and the target
network’s system ID.
• When a terminal or trunk is placed on hold, the Music on Hold comes from the system where the
terminal or trunk resides.
• When the Hold recall times out, the call will recall to the operator in the system where the CO trunk
resides. Hold recall timeout to the operator is controlled in Class of Service program 20-11-13.
• Forced Account Codes are not applied to calls across SL Net.
• When Multiple Voice Mails are installed in the network, each site must have a unique Voice Mail
pilot number. The pilot number assigned must be within the routable extension number range in all
sites throughout the network.
• When each site has its own Voice Mail system, a user in one location cannot call the Voice Mail pilot
number that resides in another system.
• When each site has its own Voice Mail system, a Voice Mail Message Line key (PRG 15-07 key 77)
cannot be programmed for an extension in a Remote system.
• When using centralized voice mail in a network that has both SL2100 and SL1100 systems the
voice mail department group must be 32 or lower in order to work with the SL1100.
• Virtual Loopback trunks are not supported across SL Net.
• Code Restriction is not applied for CO trunks accessed across the SL Net network.
• When a network has both SL2100 and SL1100 systems PRG 84-34-02, Profile 1, Type 2 (DTMF
Payload Number - Networking) must be set to 96 for all SL2100 systems.
• When using centralized voice mail it is strongly recommended that the main SL2100 containing the
central voice mail be populated with a IP7WW-EXIFB-C1 and IP7WW-SDVMS-C1 (1G) or IP7WW-
SDVML-C1 (4G) SD Drive.
• Network ports (extension or trunk) cannot land on a virtual extension key. When PRG 15-18 is set to
“land on key” the virtual extension will still ring. When the call is answered the virtual key will go
back to an idle state.
• SMDR information is collected in the system where the trunk resides. If a user in Site A accesses a
CO trunk out of Site B, this call is reported in Site B’s SMDR and not in Site A’s SMDR.
• When a networked ICM call forwards to Voice Mail (Centralized or Individual Voice Mail) the user will
not be able to perform any dialing options to dial out of the mailbox. The associated dial action table
cannot be accessed unless the call originates from a CO trunk.
• If you use the Make Call feature while listening to a Voice Mail message, the first few seconds of the
call may be silent if the call is routed across the SL Net network.
• When using Loop Keys to make outgoing CO calls via the network, the loop key will not light. If ARS
is enabled, and an outgoing CO call via the network is placed, the loop key will light for the first few
seconds until the system determines which trunk to seize.
• When a CO call via the network is put on hold, the call is placed onto the users Hold key. To retrieve
this call the user must press the Hold key. If one call is already on Hold the user cannot place a
second call on hold, the second call must be placed into a park orbit or transferred to another
station.
• Built-in Automated Attendant and Centralized Voice Mail cannot be used in the same system.
• Calls (Intercom or Trunk) routed across the SL Net network cannot be answered by the Built-In
Automated Attendant.
• Caller ID Flexible Ringing does not work for incoming calls via the SL Net network. For the calls to
route based on caller ID, the programming must be performed in the system that contains the CO
trunks. Routing to other system’s extensions is available; however the ringing patterns will not be
followed.
• Directory Dialing will not list extension numbers in remote SL Net systems.
13-6 SL Net
ISSUE 1.0 SL2100
• Distinctive Ringing patterns will only work in the system where the trunk resides.
• A Drop Key (PRG 15-07 key 84) or the Flash Key will not function for calls routed across the SL Net
network.
• Long conversation cutoff will not disconnect a trunk call if a user accesses a trunk out of a
networked system.
• An operator extension (PRG 20-17) cannot be assigned to an extension in a Remote SL Net
system. The operator for each site must reside in their own local system.
• Calls routed across the SL Net network cannot use the Repeat Redial function
• A Reverse Voice Over key (PRG 15-07 key 47) cannot be programmed for an extension in a
Remote SL Net system.
• Room Monitor cannot be used to monitor an extension in a Remote SL Net system.
• A Saved Number Dialed key (PRG 15-07 key 30) cannot be used to save a number if the call is
routed across the SL Net network.
• A Secondary Incoming Extension cannot be programmed for a station in a Remote SL Net system.
• A Secretary Call Buzzer and Secretary Call Pickup key (PRG 15-07 key 41 and key 42) cannot be
programmed for a station in a Remote SL Net system.
• A Serial Call cannot be performed to a station in a Remote SL Net system.
• Tandem Ringing cannot be set to an extension in a Remote SL Net system.
• If an extension is using a CO trunk in a Remote SL Net system, the Tone Override feature is not
supported. In this scenario the busy station will receive the Tone Override but will not be able to
answer the caller.
• Trunk Queuing/Camp-On cannot be performed to a busy CO trunk in a Remote SL Net system.
• Voice Over to a busy extension is not supported across the SL Net network.
• Personal Park (PRG 15-07 key *07 or Service Code 757) is not supported for calls across the SL
Net network.
• Mobile Extension is not supported for calls across the SL Net network.
• When a call is transferred to a Department Group with All Ring, there is a difference in operation. In
a single system, an extension within the same system can transfer a call to a Department Group.
The call will ring an extension within the Department Group once the transferring user hangs up. In
a networked system, the transfer will not go through and the call will recall the extension performing
the transfer.
• Live Monitor is not supported for users in remote systems.
None

6.2.1 Terminals
All Terminal types are supported
IP7[ ]-4KSU-C1
IP7[ ]-CPU-C1
IP7WW-VOIPDB-C1
Each active SL Net call requires one of the following licenses in both end point systems:
• SL2100 SL NET-08 LIC (5091)
• SL2100 IP CHANNEL-16 LIC (5103)

SL2100 ISSUE 1.0
6.3 Related Features

None
SECTION 7 GUIDE TO FEATURE PROGRAMMING

The programs listed below indicate the most commonly used programs required for this feature. The
programs are listed in the order that the installer should follow. Refer to the PCPro wizards for further
detailed programming.
When a * is listed next to the Program Number it indicates a program that MUST be set (from a default
state) for this feature to be enabled.
7.1 Basic Setup
Program Program Name/Description Assigned Data

Number
10-12-09 VoIPDB IP Address 0.0.0.0~126.255.255.254
Assign the IP Address for the VoIPDB. 128.0.0.1~191.255.255.254
If a VoIPDB is installed in the system, NEC recommends 192.0.0.1~223.255.255.254
setting program 10-12-01 to 0.0.0.0. All connections to (default =172.16.0.10)
the system will be made through the VoIPDB.
10-12-10 VoIPDB Subnet Mask Refer to the programming manual for all the
Assign the subnet mask for the VoIPDB card. possible valid subnet mask entries.
(default =255.255.255.0)
10-12-03 Default Gateway 0.0.0.0~126.255.255.254
Assign the SL2100’s default gateway IP address. 128.0.0.1~191.255.255.254
192.0.0.1~223.255.255.254
(default =0.0.0.0)
84-26-01 VoIP Basic Setup (DSP) 0.0.0.0~126.255.255.254
Assign the IP address that is used for Voice Communica- 128.0.0.1~191.255.255.254
tions across the network. The IP address assigned here 192.0.0.1~223.255.255.254
MUST be within the same network as the IP address as- (default =172.16.0.20)
signed in PRG 10-12-09.
11-01-01 * System Numbering 0 = Not Used
Assign the leading digit/digits of the remote SL Net sys- 1 = Service Code
tems as: (8) Networked System Access. 2 = Extension Number
Example 1: The Remote SL Net system is going to use 3 = Trunk Access Code
extensions 200 ~ 299 then the digit 2 would be assigned 4 = Individual Trunk Access Code
as: (8) Networked System Access. 5 = Operator Access
Example 2: The Remote SL Net system is going to use 6 = F-Route
extensions 1200 ~ 1299 then the digits 12 would be as- 8 = Networked System Access
signed as: (8) Networked System Access. 9 = Dial Extension Analyze
(Refer to the SL2100 programming manual for
the default values.)
11-01-01* System Numbering 0 = No Remote Network
Once the leading digits/digits are assigned as network 1 = Remote Network 1
access, you must then assign them to a valid Network ID 2 = Remote Network 2
(1~4). 3 = Remote Network 3
Note: the 1st remote system would be network ID 1, the 4 = Remote Network 4
second would be network ID 2, the 3rd would be network (default =0)
ID 3, and the 4th would be network ID 5. The network ID’s
at each remote location do not have to match; they are
system dependent.
For example, if the Remote SL Net system uses exten-
sions 200 ~ 299, then digit 2 would be assigned as: (8)
Networked System Access and digit 2 would be assigned
as network ID 1.
13-8 SL Net
ISSUE 1.0 SL2100

Number
10-27-01* Network System ID Assignment 0.0.0.0 ~ 126.255.255.254
Define the IP Address of the Remote SL Net system 128.0.0.1 ~192.255.255.254
where the call is routed for the system ID assigned in 192.0.0.1 ~ 223.255.255.254
PRG 11-01-01. (default =0.0.0.0)
20-01-04 Network BLF Indication 0 ~ 64800 seconds
Assign how often the SL2100 updates the DSS key BLF (default =0)
indications for remote SL Net systems (expressed in sec-
onds).
To provide BLF lamping indications across the network,
this timer must be adjusted. NEC recommends a value of
3 seconds.
10-19-01 VoIPDB DSP Resource Selection 0 = Commonly used for IP extensions, trunks,
This program is used to assign the 16 or 32 resources of and networking
the VoIPDB. 1 = Use for IP extensions
NEC recommends leaving the default settings as system 2 = Use for SIP trunks
default. 3 = Use for networking (SL Net)
5 = Blocked
6 = Common without unicast paging
7 = Multicast paging
8 = Unicast paging
(defaults: resource1 = Use for IP extensions, re-
source 2 ~ 128 = Common)
10-20-01 External Equipment LAN setup 1 = CTI Server (default = 8181)
Device type 4 (networking system) must be assigned to 2 = ACD MIS (default = 4000)
the same port number in ALL SL Net systems. 4 = Networking System (default = 30000)
5 = SMDR Output (default = 0)
6 = DIM Output (default = 0)
8 = UC Web Application
9 = 1st Party CTI (default = 8282)
11 = O&M Server (default = 8010)
12 = Traffic Report Output (default = 0)
13 = Room Data Output for Hotel Service (de-
fault = 0)
14 = IP-DECT Directory Access (default = 0)
15 = Presence (default = 0)
Available values are: 0 ~ 65535
90-10-01 System Alarm Setup 0 = No Setting
Two Alarms were added for SL Net and they are: 1 = Major Alarm
Alarm 15 – Networking keep alive error 2 = Minor Alarm
Alarm 59 – Networking port limit exceeded (Refer to the SL2100 programming manual for
the default values.)
90-10-02 Report 0 = No (alarm disabled)
This program is used to assign if the alarm is displayed 1 = Yes (alarm enabled)
on a key telephone if the alarm information is reported to (Refer to the SL2100 programming manual for
the pre-defined destination. the default values.)
7.2 Codec Assignment

Number
84-12-28 Audio Capability Priority 0 = G.711
This program assigns the Codec that is used when call- 1 = Not Used
ing across the SL Net network. 2 = G.729
Refer to the above bandwidth chart when making the Co- 3 = G.722
dec selection. (default = 0)
84-12-01 G.711 Audio Frame Size 1 = 10ms
Assign the G.711 Audio Frame Size. 2 = 20ms
The smaller the packet sizes the more bandwidth that is 3 = 30ms
consumed. However when a smaller packet is lost in a 4 = 40ms
network a smaller amount of the voice is lost with it. (default = 3)

SL2100 ISSUE 1.0

Number
84-12-02 G.711 Voice Activity Detection 0 = Disable
This program is used to enable or disable the G.711 Co- 1 = Enable
dec to use silence detection. When silence detection is (default = 0)
enabled the SL2100 can detect the absence of audio and
conserve bandwidth by preventing the transmission of
"silent packets" over the network.
When this program is enabled, it can save on bandwidth.
However, it can also affect the quality of the call. VAD
may have trouble detecting the start and end of silence
and therefore may cut off the beginning and/or the end of
a word.
84-12-03 G.711 Audio Type 0 = A-law
In North America do not change this setting, only u-law is 1 = U-law
supported. (default = 1)
84-12-04 G.711 Minimum Jitter Buffer size 0 ~ 255ms
This program assigns the minimum size that the jitter buf- (default = 30ms)
fer will use.
84-12-05 G.711 Average Jitter Buffer size 0 ~ 255ms
This program assigns the average size that the jitter buf- (default = 60ms)
fer will use.
84-12-06 G.711 Maximum Jitter Buffer size 0 ~ 255ms
This program assigns the maximum size that the jitter (default = 120ms)
buffer will use.
Assign the G.729 Audio Frame Size 2 = 20ms
network a smaller amount of the voice is lost with it. 5 = 50ms
6 = 60ms
(default = 3)
84-12-08 G.729 Voice Activity Detection 0 = Disable
This program is used to enable or disable the G.729 CO- 1 = Enable
DEC to use silence detection. When silence detection is (default = 0)
enabled, the SL2100 can detect the absence of audio
and conserve bandwidth by preventing the transmission
of "silent packets" over the network. When this program
is enabled, it can save on bandwidth however it can also
affect the quality of the call. VAD may have trouble de-
tecting the start and end of silence and therefore may cut
off the beginning and/or the end of a word.
fer will use.
fer will use.
buffer will use.
84-12-17 Jitter Buffer Mode 1 = Static
If the jitter buffer is set to adaptive, the buffer is adjusted 3 = Adaptive Immediately
(larger/smaller), depending upon network conditions. (default = 3)
If the jitter buffer is set to static, it will never adjust and al-
ways have the same size buffer.
13-10 SL Net
ISSUE 1.0 SL2100

Number
84-12-18 Voice Activity Detection Threshold 0~30 = -19dB~+10dB
This program is used to set the threshold of the db level 0 = Adaptec
that the system uses to determine silence. If VAD is ena- Threshold
bled and this threshold is reached, the system will stop 1 = -19dB(-49dBm)
transmitting “silence packets” across the network. :
20 = 0dB (-30dBm)
:
29 = 9dBm(-21dBm)
30 = 10dBm(-20dBm)
(default = 20)
Assign the G.722 Audio Frame Size 2 = 20ms
network a smaller amount of the voice is lost with it. (default = 3)
fer will use.
fer will use.
buffer will use.
84-12-38 RTP Filter 0 = Disable
This program is used to avoid audio path problems in 1 = Enable
times of heavy RTP traffic. (default = 1)
When enabled, the system will check the sender’s IP ad-
dress that is sending RTP packets. If it does not match
with the IP address of the actual caller, the system will ig-
nore it.
84-34-01 VoIPDB Setup DTMG Relay Mode (02-Networking) 0 = Disable
Select DTMF Relay Mode. 1 = RFC2833
2 = H.245
Profile (1 ~ 6)
(default = 0)
84-34-02 This program assigns the way the system handles DTMF 96 ~ 127
across the SL Net network. For profile 1, Type 2 (Net- (default = 110)
working) this value should match in all SL Net systems.
7.3 Call Routing - Outbound

Number
11-01-01 System Numbering 0 = Not Used
This program is used to assign the Trunk Access code (9 1 = Service Code
by default) and the special trunk access code (unas- 2 = Extension Number
signed at default). 3 = Trunk Access Code
The trunk access code used to make alternate calls must 4 = Individual Trunk Access
be set to a type 4 (special trunk access code). 5 = Operator Access
6 = F-Route Access
8 = Networking System Access
9 = Dial Extension Analyze
(Refer to the SL2100 programming manual for
the default values of all tables)
11-09-01 Trunk Access Code Maximum of 4 digits (0~9, *, #,)
Use this program to assign the trunk access code defined (default =9)
in program 11-01-01. This is the access code that users
will dial to make outbound calls.

SL2100 ISSUE 1.0

Number
11-09-02 2nd Trunk Route Access Code Maximum of 4 digits (0~9, *, #,)
Use this program to assign the special trunk access code (default =not assigned)
defined in program 11-01-01. Users dial this access code
to make outbound calls from a different trunk group rath-
er than using the primary trunk group access code.
21-02-01 Trunk Group Routing for Extensions 0 = No Setting (Calls will not route)
This assigns extensions per day/night mode to a route ta- 1~50 = Route Table 1~50
ble (program 14-06-01). (default =1)
This program follows the trunk access code in PRG
11-01-01 and 11-09-01.
21-15-01 Individual Trunk Group Routing for Extensions 0 = No Setting (Calls will not route)
This assigns extensions per day/night mode to a route ta- 1~50 = Route Table 1~50
ble (program 14-06-01). (default =0)
This program follows the “special trunk” access code
from PRG 11-01-01 and 11-09-02.
14-06-01 Trunk Group Routing 0 = No Setting (Calls will not route)
With SL Net, four new trunk group routing options have 001 ~ 050 = Trunk Group 1~50
been added and they are 101 ~ 150. These options allow 101 ~ 150 = 100+Networking System No.
the caller to access and make calls using one of the Re- 1001 ~ 1050 = 1000+Route Table No.
mote Systems Trunks. (default =1)
101 will access trunks from Remote system 1 that is pro-
grammed in 10-27-01.
:
150 will access trunks from Remote system 50 that is
programmed in 10-27-01.
21-16-01 Trunk Group Routing for Networks 0 = No routing (Calls will not route)
If a call comes in from across the network, this program 1 ~ 50 = Route table 1 ~ 50 (PRG 14-06-01)
determines the route table (PRG 14-06-01) that will be (default =1)
accessed in the local system.
15-07-01 Programmable Function Keys *06 = Trunk Access via Networking
This program is used on a per-station basis to assign dif- Secondary Settings:
ferent function keys to the multiline terminals. 1 = Remote System 1 from PRG 10-27
Function key (*06) is used to assign a key on a phone 2 = Remote System 2 from PRG 10-27
that will allow a user to access trunks out of a remote 3 = Remote System 3 from PRG 10-27
system just by pressing the key. 4 = Remote System 4 from PRG 10-27
When this key is assigned, an additional data of 1~50 is :
required. The additional data specifies which Remote 50 = Remote System 50 from PRG 10-27
system you will access trunks from. (Refer to the SL2100 programming manual for
When this key is used to access trunks out of a Remote the default values and for all other available op-
System, it will look at PRG 21-16-01 of the system where tions in this program.)
the CO Line resides.
11-12-16 Trunk Access via Networking Default Access Code = 726
This code allows the user to dial the access code (default
726), then the two-digit remote system number (01 ~ 04
from PRG 10-27), and then the telephone number to
complete a call from a destination systems trunk.
An example of dialing this code and calling out of Remote
system 1 would be:
User goes off hook and dials access code 726 .
13-12 SL Net
ISSUE 1.0 SL2100

Number
26-02-03 ARS/LCR additional data If 26-02-02 is set to Trunk Group
If using ARS for the trunk group routing, four new items 0 = No Routing (Calls will not route)
have been added to the additional data field. The options 1 ~ 50 = Trunk Groups 1 ~ 50
are 101 ~ 150 and these options allow the caller to ac- 101 ~ 150 = Remote Systems 1 ~ 50
cess and make calls out of one of the Remote Systems If 26-02-02 is set to F-Route
Trunks. 0 = No Routing (Calls will not route)
101 will access trunks from Remote system 1 that is pro- 1 ~ 100 = F-route tables 1 ~ 100
grammed in 10-27-01. 101 ~ 150 = Remote Systems 1 ~ 50
102 will access trunks from Remote system 2 that is pro- (default =0)
:
44-05-01 F-Route trunk group number 0 = No Setting (Calls will not route)
If using F-Route for the trunk group routing, four new 1 ~ 50 = Trunk Group 1 ~ 50
items have been added to the trunk group field. The op- 101 ~ 150 = Remote Systems 1 ~ 50
tions are 101 ~ 150 and these options allow the caller to 255 = Intercom
access and make calls from a Remote System Trunk. (default =0)
:
7.4 Call Routing - Inbound Analog Trunk

Number
22-02-01 Incoming Call Trunk Setup 0 = Normal
Analog trunks at any location can be set to DIL to any ex- 1 = VRS
tension number in the SL Net network. 2 = DISA
For an analog trunk to be DIL it must be set as a type (4) 3 = DID
DIL. 4 = DIL
Once the trunk type is set to DIL the destination can be 5 = Tie Line
assigned in program 22-07-01. 6 = Delay VRS
Analog trunks can also be set as Normal (type 0) to be 7 = ANI/DNIS
routed following the ring group settings in PRG 22-05-01. 8 = DID (DDI) Mode Switching
(default =0)
22-07-01 DIL Assignment Maximum of 8 digits (0~9, *, #,)
For each trunk and day/night mode assignment, desig- (default =Not Assigned)
nate the destination extension or pilot number where the
trunk is routed.
Trunks can be routed to any valid extension number in all
SL Net systems.
22-05-01 Incoming Trunk Ring Group Assignment 1~50 = Ring Group 1~50
SL Net calls can be routed to a Centralized Voice Mail 102 = Voice Mail (Call goes to the VM pilot as-
from any location using a setting data of 103. When 103 signed in program 45-01-01)
is assigned, calls will be routed to the pilot number de- 103 = Centralized Voice Mail (if centralized VM
fined in PRG 45-01-07. is enabled this setting is used to route calls to
the VM)
(default =1)

SL2100 ISSUE 1.0

Number
22-08-01 DIL/IRG No Answer Destination 0 = No Setting
After the timer in program 22-01-04 expires the call will 1~50 = Ring Group 1~50
overflow to the pre-defined location defined in this pro- 102 = Voice Mail (Call goes to the VM pilot as-
gram. signed in program 45-01-01)
SL Net calls can overflow to a Centralized Voice Mail 103 = Centralized Voice Mail (if centralized VM
from any location using a setting data of 103. When 103 is enabled this setting is used to route calls to
is assigned, calls will overflow to the pilot number defined the VM)
in PRG 45-01-07. (default =1)
22-01-04 DIL/IRG No Answer Destination Timer 0 = No Overflow
A call will ring the DIL or Ring Group destination for the 1~64800 = 1~64800 seconds
specified amount of time programmed. Once the timer (default =0)
expires, and the call was not answered, the call will now
overflow to the destination set in program 22-08-01.
7.5 Call Routing - Inbound (DID)

Number
22-02-01* Incoming Call Trunk Setup 0 = Normal
ISDN PRI or SIP trunks at any location can send a DID 1 = VRS
directly to any extension number in the SL Net network. 2 = DISA
Trunks must be set to type (3) DID to follow the digit con- 3 = DID
version tables. 4 = DIL
5 = Tie Line
6 = Delay VRS
7 = ANI/DNIS
8 = DID (DDI) Mode Switching
(default =0)
22-11-01* Received Number Maximum of 8 digits (0~9, *, #,)
Enter the digits received from the Telco that are going to (default =Not Assigned)
be translated.
The amount of digits entered should be equal to the set-
ting assigned in program 22-09-01.
22-11-02* Target Number Maximum of 8 digits (0~9, *, #,@)
Enter the destination number where the DID is sent. (default =Not Assigned)
The destination can be any valid extension number in the
SL Net network.
22-11-04 Transfer Operation Mode 0 = No Transfer
The transfer operation mode allows DID calls to have 1 = Busy
more routing options than just the target number. If the 2 = No Answer
transfer operation mode is set to “No Transfer”, calls will 3 = Busy/No Answer
only be delivered to the Target Number specified in pro- (default =0)
gram 22-11-02. If set to one of the three other modes, it
will follow that mode through all assigned transfer desti-
nations.
22-11-05 Transfer Destination Number 1 0 = No Setting
SL Net allows calls to overflow to a Centralized Voice 1~50 = Ring Group 1~50
Mail from any location using a setting data of 103. When 102 = Voice Mail (Call goes to the VM pilot as-
103 is assigned, calls will overflow to the pilot number designed in program 45-01-01)
fined in PRG 45-01-07. 103 Centralized Voice Mail (if centralized VM is
If the transfer operation mode is set (PRG 22-11-04), and enabled this setting is used to route calls to the
one of the conditions is met, calls will overflow from the VM)
target number to the destination in this program. If this 201~250 = Department Group 1~50
was a No Answer condition, calls would overflow to this 400 = VRS
program after the timer in 22-01-06 expires. 401 = DISA
501~599 = DISA/VRS Message (VRS message
number 1~99)
1000~1999 = Speed Dial Bins 000~999
(default =0)
13-14 SL Net
ISSUE 1.0 SL2100

Number
22-11-06 Transfer Destination Number 2 0 = No Setting
SL Net allows calls to overflow to a Centralized Voice 1~50 = Ring Group 1~50
Mail from any location using a setting data of 103. When 102 = Voice Mail (Call goes to the VM pilot as-
103 is assigned, calls will overflow to the pilot number designed in program 45-01-01)
fined in PRG 45-01-07. 103 Centralized Voice Mail (if centralized VM is
If the transfer operation mode is set (PRG 22-11-04), and enabled this setting is used to route calls to the
one of the conditions is met, calls will overflow from the VM)
target number to the destination in this program. If this 201~250 = Department Group 1~50
was a No Answer condition, calls would overflow to this 400 = VRS
program after the timer in 22-01-06 expires. 401 = DISA
501~599 = DISA/VRS Message (VRS message
number 1~99)
1000~1999 = Speed Dial Bins 000~999
(default =0)
22-12-01 DID Intercept Ring Group 0 = Not Set
If the transfer operation mode is set (PRG 22-11-04), and 1~50 = Ring Group 1~50
the call has overflowed through 102 = Voice Mail (Call goes to the VM pilot as-
Transfer Destination Number 1 and 2, and Incoming Ring signed in program 45-01-01)
Group Transfer is enabled, calls will be routed to the des- 103 Centralized Voice Mail (if centralized VM is
tination in this program. enabled this setting is used to route calls to the
SL Net allows calls to overflow to a Centralized Voice VM)
Mail from any location using a setting data of 103. When (default =1)
103 is assigned, calls will overflow to the pilot number de-
fined in PRG 45-01-07.
22-01-06 DID Ring-No-Answer Time 0~64800 seconds
Use this program to assign the amount of time that a call (default =20 seconds)
will ring the DID Transfer Target before overflowing to
Transfer Destination Number 1.
22-01-07 DID Incoming Ring Group No Answer Time 0~64800 seconds
Use this program to assign the amount of time that a call (default =20 seconds)
will ring the Transfer Destination Number 1 before over-
flowing to Transfer Destination Number 2.
This timer also controls the amount of time that a call will
ring the Transfer Destination Number 2 before overflow-
ing to the DID Intercept Ring Group.
7.6 Centralized Voice Mail

Number
11-07-01* Department Group Pilot Number Maximum of 8 digits (0~9, *, #,)
Assign the Voice Mail pilot number to the group that is to Default:
be used. A pilot number must fall within the valid number- Department Group No. 1~49: No Setting
ing plan assigned in program 11- 01-01. Department Group No. 50: 5999
NEC recommends that you do not use department group
01 because by default all extensions are assigned to this
group.
This program is only assigned in the system that has the
Voice Mail.

SL2100 ISSUE 1.0

Number
16-01-02 Department Group Calling Cycle 0 = Normal Routing (Priority)
This program is used to define what happens when the 1 = Easy UCD routing (Circular)
department group pilot number is called. (default = 0)
If this is set to priority, every new call to the pilot number
will search an idle phone in order of the extensions priori-
ty (set in program 16-02-02). The lower the number the
higher the priority for that extension. For example, if two
phones are idle and one phone has a priority of a 1 and
the other phone has a priority of a 2, the phone with the
priority 1 will receive the call.
If this is set to circular, every new call to the pilot number
will cycle to an idle extension in a circular order. The pri-
ority of the extension is not used.
When using a department group for Voice Mail, this pro-
gram must be set to (0) priority.
16-01-04 Department Group Hunting Mode 0 = Last extension is called and hunting stops
This program sets what happens when an unanswered 1 = Circular (Hunting will continue)
call to a department group pilot number reaches the last (default = 0)
member of the group.
If this is set to (0), once the last extension is called the
hunting will stop.
If this is set to (1), once the last extension is called the
hunting will continue to look for an idle member to receive
the call.
NEC recommends setting this to (1) Circular when using
a department group for Voice Mail.
16-01-10 Department Group Enhanced Hunting 0 = No Hunting
This program defines the conditions by which calls to the 1 = Hunting when Busy
pilot number will hunt to the available extensions in the 2 = Hunting when Not Answered
group. 3 = Hunting when Busy/No Answer
For a description on all the hunting types, see the Depart- (default = 0)
ment Group feature.
NEC recommends setting the Voice Mail department
group as (3) Busy/No Answer.
16-02-01* Department Group Assignment for Extensions 1~50
This program is used to assign the extensions to the de- Default:
partment group. Department Group No. 1: Extension No.
When using a department group for Voice Mail, you must 101~199, 200~271, 3100~3112
have licenses to cover every extension assigned. Department Group No. 50: Extension No.
3113~3128
16-02-02 Department Group Priority Assignment 1~200
This program sets the extensions priority within the de- Extension 101~199 = Priority 1~99
partment group. The lower the number that is assigned Extension 200~271 = Priority 1~16
the higher the priority. Extension 3100~3112 = Priority 100~112
When using a department group for Voice Mail, the low- Extension 3113~3128 = Priority 129~200
est voice mail port must have the lowest priority number (Refer to the SL2100 programming manual for
in the group. the default values of all extensions)
For example if the VM had system ports 65~68 and used
extensions 165~168 the following would be the assign-
ment.
Ext 165 = Priority 1
45-01-01 Voice Mail Department Group Number 0 = No Voice Mail Assigned
When using Centralized Voice Mail in an SL Net network, 1~50 = Department Group 1~50
this program MUST be left unassigned in all sites that will (default = 50)
access the VM.
45-01-10* NSL Protocol 0 = Off (Disable)
All sites using the Centralized Voice Mail must enable 1 = On (Enable)
this program for proper integration. (default = 0)
14-01-22 Caller ID to Voice Mail 0 = Disable (Caller ID not sent to VM)
This command enables or disables the ability for the sys- 1 = Enable (Caller ID is sent to VM)
tem to send the caller ID information to the Voice Mail. (default = 0)
This command is for ALL trunk types (analog, digital, and
IP).
13-16 SL Net
ISSUE 1.0 SL2100

Number
84-34-01* DTMF Relay Mode 0 = Disable
This program assigns the way the system handles DTMF 1 = RFC 2833
across the network. 2 = H.245
When Centralized VM is required this program must be Profile (1 ~ 6)
set to (1) RFC2833 in all systems. (default = 0)
84-34-02 DTMF Payload Number 96 ~ 127
This program assigns the way the system handles DTMF (default = 110)
across the SL Net network. For profile 1, Type 2 (Net-
working) this value should match in all SL Net systems.
7.7 Alarm Setup

Number
90-10-01* Alarm Type 0 = Not Set (No Alarm Generated)
Per Alarm Number (1 ~ 100) specify an alarm type. If an 1 = Major Alarm
alarm is set to “Not Set” then NO alarm information will 2 = Minor Alarm
be generated. Default Alarm Settings
If an alarm is set to “Major Alarm” or “Minor Alarm” then Alarm 15 = 0
alarm data will be presented when an error occurs. The Alarm 17 = 1
alarm report will be labeled with the “Major Alarm” or “Mi- Alarm 57 = 2
nor Alarm” tag in the report. Alarm 59 = 2
The following Alarms are suggested when troubleshoot- Alarm 64 = 1
ing an SL Net network: Alarm 65 = 0
Alarm 15 – Network Keep Alive Alarm 68 = 2
Alarm 17 – Denial of Service Attack (Refer to the SL2100 programming manual for
Alarm 57 – IP Address Collision (Duplicate IP Assign- the default values of all Alarms)
ment)
Alarm 59 – SL Net port count exceeded
Alarm 64 – VoIPDB LAN link error
Alarm 65 – VoIPDB trouble information
Alarm 68 - VoIPDB DSP all Busy
10-31-01 Keep Alive Interval 0 = Disabled
This PRG is used to set the Interval in which the system 1~65535 = 1~65535 seconds
will send a Keep Alive message to Remote SL Net sys- (default =0)
tems.
When set to 0 a Keep Alive will not be sent across the
network and Alarm 15 will not be reported on.
When set to (1 ~ 65535 seconds) the system will send a
Keep Alive to the Remote SL Net systems at this interval.
When the system does not receive a response to one of
these Keep Alive messages an Alarm 15 will be gener-
ated and labeled as a Warning.
An example of this alarm is: MIN 0015 WAR 11/07/11
14:07 NW KeepAlive -none- ID:02-004
MIN = Minor Alarm, this is because the Alarm was flag-
ged as minor.
0015 = Alarm number 15.
WAR = Warning, indicating the network is still up but a
keep alive was missed.
11/07/11 = Date the Warning was generated
14:07 = Time in 24 hour format that the Warning was
generated
NW KeepAlive = Alarm Name
None = Field not used
ID:02-004 = System ID 02 (from PRG 10-27) did not re-
spond to 4 Keep Alive messages.

SL2100 ISSUE 1.0

Number
10-31-02 Keep Alive Retry Timer 1 ~ 255 = How many retries are transmitted be-
This program is used to set the amount of times the sys- fore the link is taken out of service
tem will resend a Keep Alive message when there is no (default =5)
response from the other side.
If the response is not received within the specified num-
ber of retries, the networking link will be taken out of
service. When the link is taken out of service an Alarm 15
will be generated and labeled as an Error.
An example of this alarm is: MAJ 0015 ERR 11/07/11
14:10 NW KeepAlive -none- ID:02
MAJ = Major Alarm, this is because the Alarm was flag-
ged as major.
0015 = Alarm number 15.
ERR = Error, indicating the network link was taken out of
service.
11/07/11 = Date the Error was generated.
14:10 = Time in 24 hour format that the Error was gener-
ated.
NW KeepAlive = Alarm Name.
None = Field not used.
ID:02 = System ID 02 (from PRG 10-27) was taken out of
service.
SECTION 8 PROGRAMMING EXAMPLES

The following examples will all be based off of two sites connected together with SL Net. Site A will
have extension numbers in the 1XX range and site B will have extension numbers in the 2XX range.
The diagram below shows the IP Addressing information for each site.
Site A Site B
VoIPDB IP Address: 172.16.0.10 VoIPDB IP Address: 10.0.0.10
VoIPDB Subnet mask: 255.255.0.0 VoIPDB Subnet mask: 255.0.0.0
DSP IP Address: 172.16.0.11 DSP IP Address: 10.0.0.11
Default Gateway: 172.16.0.1 Default Gateway: 10.0.0.1
Network
Ext 101 Ext 201
Figure 13-3 Programming Example
8.1 Basic SL Net Setup
Program Site A Site B Notes

10-12-09 172.16.0.10 10.0.0.10 IP address of VoIPDB
10-12-10 255.255.0.0 255.0.0.0 Subnet Mask of VoIPDB
10-12-03 172.16.0.1 10.0.0.1 Default Gateway
84-26-01 172.16.0.11 10.0.0.11 DSP IP Address
13-18 SL Net
ISSUE 1.0 SL2100

11-02-01 Default Change extensions to 201 ~ Extension numbering
284
11-01-01 Digit (2X) set to 3 digit Digit (1X) set to 3 digit Define the digit length for the remote destina-
length length tion extension numbers.
11-01-01 Digit (2X) set to Network Digit (1X) set to Network Set the leading digits of the remote destina-
System Access System Access tion as Network System Access.
11-01-01 Digit (2X) set to Network ID Digit (1X) set to Network ID Set the leading digits of the remote destina-
1 1 tion as the first available network ID.
10-27-01 Set system ID 1 = 10.0.0.10 Set System ID 1 = Define the IP Address of the destination sys-
172.16.0.10 tem.
System ID 1 was used because this was the
ID assigned in PRG 11-01-03.
20-01-04 3 3 Allows the sites to see BLF status of exten-
sions across the network.
10-20-01 Device Type 4 = Default Device Type 4 = Default Verify that both sites still have the default val-
ue of 30000 assigned.
Port numbers other than default can be used
but all sites must use the same port number.
8.1.1 Centralized VM
In the example below site A will be using an InMail with 16 ports as the Centralized VM. The InMail will
use station ports 69 ~ 84 and have a pilot number of 100.

11-02-01 Default Verify the InMail extension numbers are 169
~ 184
11-07-01 Group 32 = 100 NA Assign the VM pilot Number to group 32
15-03-01 Ext’s 169 ~ 184 = DP NA Change ALL VM extensions to DP
15-03-03 Ext’s 169 ~ 184 = Special NA Change ALL VM extensions to special
16-01-02 Group 32 = Priority NA Change VM groups calling cycle
16-01-04 Group 32 = Circular NA Change VM groups hunting mode
16-01-10 Group 32 = BNA NA Change VM groups enhanced hunting
16-02-01 Ext’s 169 ~ 184 = Group 32 NA Assign ALL VM extensions to the VM group
16-02-02 Change the 1st VM ext NA Assign the priority to ALL VM extensions.
(169) to Priority 1, 2nd to
Priority 2, etc.
45-01-01 DO NOT ASSIGN DO NOT ASSIGN Leave this Unassigned when usingCentral-
ized VM
45-01-07 100 100 Assign the VM pilot number to ALL sites
45-01-08 32 NA Assign the VM department group only in the
site with the VM
45-01-10 ON ON Enable NSL protocol on ALL sites
84-34-01 RFC2833 RFC2833 Set all sites in the network to RFC2833.
8.1.2 Network BLF Indication
In the following example ext 101 will have a DSS/BLF of extension 201 on the phone. When ext 201 is
Busy, the user at extension 101 will see the DSS/BLF key is lit indicating that ext 201 is in use.

SL2100 ISSUE 1.0
Extension 102 will have a DSS console and the first two keys on the DSS console will provide Network
BLF indication for extension 201 and 202.
Extension 201 will have a DSS/BLF of extension 101 on the phone. When ext 101 is Busy, the user at
extension 201 will see the DSS/BLF key is lit indicating that ext 101 is in use.

If the port numbers at each location donot
match or are unassigned calls will still be
completed across the network however BLF
indication will not function properly.
20-01-04 3 3 Allows the sites to see BLF status (on line-
keys or DSS consoles) across the network.
15-07-01 On ext 101 assign key 1 as: On ext 201 assign key 1 as: PRG 15-07-01 is assigned per phone. All
01- DSS/One-Touch 201 01- DSS/One-Touch 101 phones wanting to see network BLFindication
will have to be assigned individually.
30-02-01 DSS console 01 = 102 NA This associated ext 102 with the first DSS
console in the system.
30-03-01 DSS Console 1 NA Keys 1 &2 of the DSS console now will dis-
DSS Key 001 = 01 – DSS/ play Network BLF indication for ext 201 and
One-Touch 201 202.
DSS Key 002 = 01-DSS/
One-Touch 202
8.1.3 Network Call Park
In the following example extension 101 and 201 will have Call Park orbit 01 on line key 1 of their
phones. When a call is parked in this orbit (Park 01) both of these line keys will indicate that a caller is
parked. The call can be picked up from these two stations by pressing the key or the call can be
retrieved from any user in the network using an access code.
-Note- By default Call Park bins are shared with every phone throughout the network. This can be
changed so that each site has their own call park locations and will not be shared throughout the
network.

If the port numbers at each location do not
match or are unassigned calls will stillbe com-
pleted across the network however Call Park
indication and retrieval will not function prop-
erly.
20-01-04 3 3 Allows the sites to see Park status (on line
keys or DSS consoles) across the network.
15-07-01 On ext 101 assign key 1 as: On ext 201 assign key 1 as: PRG 15-07-01 is assigned per phone.
*04- Park Key 01 *04- Park Key 01 All phones wanting to see network CallPark
indication will have to be assigned individual-
ly.
11-12-31 NA NA Default Service Code = #6.
By default any user in the network canpark a
call using this service code.
13-20 SL Net
ISSUE 1.0 SL2100

11-12-32 NA NA Default Service Code = *6.
By default any user in the network canretrieve
a parked call from anywhere inthe network
using this service code.
24-03-01 NA NA This program is used to change the exten-
sions Park Group. By default all users in the
network are in group 1. If the users do not
want to share the Park bins throughout the
network move them to another group (valid
options 1~64).
8.1.4 Call Routing - Outbound
In the following example users in Site B will access the trunks from site A by dialing an access code of
8. When a user in site B dials 8 and a phone number the call will be processed across the network and
out the trunk in site 1. Users in Site B will still be able to dial 9 and make calls out their own local
trunks.

11-01-01 NA Digit (8X) set to 1 digit Define the digit length for the special trunk
length access code.
11-01-01 NA Digit (8X) set to Individual Set the leading digit as special trunk access.
Trunk (Special Trunk Ac-
cess)
11-09-02 NA 8 This assigns the special trunk access code
defined in PRG 11-01-01.
21-15-01 NA All Stations = 2 Assign all stations in all modes to Route Ta-
ble 2.
14-06-01 NA Route Table 2 = 101 101 will access trunks from Remote system 1
that is programmed in 10-27-01.
21-16-01 NA NA When a call comes in from across the net-
work, this program determines the route table
(PRG 14-06-01) that will be accessed in the
local system.
In Site A, by default, all networked systems
are set to route table 1. Route table 1, by de-
fault, is assigned to trunk group 1 (PRG
14-06-01).
8.1.5 Paging across the network - Internal and External
A user can perform and Internal, External, or Combined page to any system in the SL Net network. To
page a remote SL Net system, follow the operation below.
Internal Page – Dial internal paging access code (701 at default) + # + two digit system ID code
(01~04) + two digit Page Zone (00~32). The following is an example of paging internal zone 1 in
remote system 1. User goes off hook and dials 701 + # + 01 + 01 and begins paging. When the user is
finished paging, go back on hook to end the page.
External Page – Dial the external paging access code (703 at default) + # + two digit system ID code
(01~04) + single digit external zone (0~3). The following is an example of paging external zone 1 in
remote system 1. User goes off hook and dials 703 + # + 01 + 1 and begins paging. When the user is
finished paging, go back on hook to end the page.
Combined Page – Dial the combined paging access code (*1 at default) + # + two digit system ID
code (00~04) + single digit external zone number (0~3).

SL2100 ISSUE 1.0

11-12-19 NA NA Default internal page code is 701
11-12-20 NA NA Default external page code is 703
11-12-24 NA NA Default combined page code is *1
31-02-01 NA NA Per site assign phones to an Internal Paging
group.
By default the first 16 ports are in group1.
31-04-01 NA NA Per site assign each External Pagingzone to
an external paging group.
By default Zone 1 = Group 1, Zone 2 =Group
2, and Zone 3 = Group 3.
31-07-01 NA NA Per site assign External Paging group (0~3)
to an Internal Paging group (0~50) to be used
for combined paging.
By default all External Groups are set to Inter-
nal Page group 1.
SECTION 9 LIST OF SUPPORTED FEATURES IN A NETWORKED

SYSTEM
Feature Name Supported in Comment
Networked Sys-
tem
Abbreviated Dialing/Speed dial No
Account Code Forced/Verified/Unverified No
Account Code Entry No
ACD No
Alarm/Alarm Reports No
Answer Hold/Automatic Hold No
Attendant Call Queuing Yes
Automatic Release Yes
Automatic Route Selection (ARS) Yes
Background Music No
Barge In Yes
Built In Automated Attendant No
Call Arrival Keys Yes
Call Duration Timer Yes
Call Forwarding Yes
Call Forwarding with Follow Me Yes
Call Forwarding Off Premise Yes
Call Forwarding/DND Override Yes
Call Monitoring Yes
Call Redirect No
Call Waiting/Camp-On * Yes Camp On across SL Net is only supported to a
Busy extension
Callback * Yes Callback across SL Net is only supported to
aBusy extension
Caller ID Call Return Yes
13-22 SL Net
ISSUE 1.0 SL2100

Networked Sys-
tem
Caller ID Yes
Caller ID Flexible Ringing No
Caller ID Shared Logging No
Central Office Calls, Answering Yes
Central Office Calls, Placing Yes
Class of Service Yes
Clock/Calendar Display/Time and Date No
Code Restriction No
Conference Yes
Continued Dialing Yes
Delayed Ringing Yes
Department Calling Yes
Department Step Calling Yes
DHCP Client No It is recommended to disable this feature when
using networking.
Dial Pad Confirmation Tone Yes
Dial Tone Detection Yes
Dial Number Preview Yes
Direct Inward Dialing (DID) Yes
Direct Inward Line (DIL) Yes
Direct Inward System Access (DISA) Yes
DSS Console Yes
Directed Call Pickup No
Directory Dialing No
Distinctive Ringing No
Do Not Disturb (DND) Yes
Door Box No
Drop Key No
Ecology No
E911 Compatibility No Each site must have at least one local central
office trunk for 911 dialing.
Flash No
Flexible System Numbering Yes
Flexible Timeouts Yes
Forced Trunk Disconnect No
Group call Pickup No
Group Listen Yes
Handset Mute/Handset Cutoff Yes
Hands free and Monitor Yes
Hands free Answerback/Forced ICM Ringing Yes
Headset Operation Yes
Hold * Yes Dual Hold is not supported across thenetwork.
Hotel/Motel No

SL2100 ISSUE 1.0

Networked Sys-
tem
Hot Key-Pad Yes
Hotline Yes
Howler Tone Service Yes
InMail * Yes Each site can have its own VM or one Central-
ized VM can be used.
Intercom Yes
IP Multiline Station Yes
IP Single Line Station Yes
IP Trunk – SIP Yes
ISDN Compatibility Yes
Last Number Redial Yes
Licensing Yes
Line Preference Yes
Long Conversation Cutoff No
Loop Keys * Yes When using loop keys to make outgoing calls
via the network, the loop key will not light.
Meet Me Conference Yes
Meet Me Paging Yes
Memo Dial Yes
Message Waiting Yes
Microphone Cutoff Yes
Mobile Extension No
Multiple Trunk Types Yes
Music on Hold No Each site would requireits own music source.
When a trunk call is placed on hold it will hear
the MOH of the system that the trunk resides in.
Name Storing Yes
Navigation Key Yes
Night Service No
Off Hook Signaling Yes
One Touch Calling Yes
Operator No
Paging, External * Yes Paging to a networked system can only be acti-
vated by dialing a service code and the target
Paging, Internal * Yes Paging to a networked system can only be acti-
vated by dialing a service code and the target
Park * Yes Personal Park (PRG 15-07 key *07 or Service
Code 757) is not supported for calls across the
SL Net network.
PBX Compatibility/behind PBX Yes
PC Programming Yes
Power Failure Transfer No
Prime Line Selection Yes
Private Line No
13-24 SL Net
ISSUE 1.0 SL2100

Networked Sys-
tem
Programmable Function Keys Yes
Redial Yes
Remote System Upgrade Yes
Repeat Dial No
Reverse Voice Over No
Ring Group Yes
Ring Down Extension Yes
Room Monitor No
Saved Number Dialed No
Secondary Incoming Extension No
Secretary Call (Buzzer) No
Secretary Call Pickup No
Security No
Selectable Display Messaging Yes
Selectable Ring Tones Yes
Serial Call No
Single Line Terminals Yes
SL Desktop Suite Yes
Soft keys Yes
Station Hunt Yes
Station Message Detail Recording (SMDR) No
Station name Assignment – UserProgrammable No
Station Relocation No
T1 Trunking Yes
Tandem Ringing No
Tandem Trunking (Unsupervised Conference) Yes
Tone Override No
Traffic Reports No Each site requires its own SMDR
Transfer Yes
Trunk Group Routing Yes
Trunk Queuing/Camp On No
Unicast/Multicast Paging * Yes Only Unicast paging is supported across the
network
Uniform Call Distribution (UCD) No
User Programming Ability Yes
Virtual Extensions * Yes Network ports (ICM or Trunk) cannot land on
the Virtual extension key.
Virtual Loopback Trunk No
Voice Mail Integration (Analog) No Only InMail issupported as a centralized VM.
Voice Mail Indication on Line Keys Yes
Voice Over No
VRS No
Volume Controls Yes

SL2100 ISSUE 1.0

Networked Sys-
tem
Warning Tone for Long Conversation Yes
13-26 SL Net
ISSUE 1.0 SL2100
MEMO

Networking Manual
NEC Corporation
ISSUE 1.0

SL2100 Networking Manual

Uploaded by

Copyright:

Available Formats

SL2100 Networking Manual

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

SL2100 Networking Manual

Uploaded by

Copyright:

Available Formats

Networking Manual

Dterm is a registered trademarks of NEC Corporation. Windows is a registered trademark of Microsoft

Chapter 2 General Information

Chapter 4 General IP Configuration

Chapter 6 Network Design Considerations

Section 2 QoS.................................................................................................................... 6-1

Chapter 7 SIP Trunking

Chapter 8 DHCP Client

Chapter 9 IP Multiline Station (SIP)

Chapter 10 IP Single Line Telephone

Chapter 12 All DSP Busy Indication

Section 3 RELATED FEATURES..................................................................................... 12-2

Networking Manual iii

Figure 11-1 NAPT Configuration Example....................................................................... 11-1

Table 1-1 Common Terms and Associated Abbreviations

Term Abbreviation Description

Networking Manual 1-1

Table 2-1 VoIP Specifications

Category Feature Notes

Networking Manual 2-1

2-2 General Information

2.1 Configure IP Trunks

Networking Manual 3-1

Ext 1000 Ext 1100

Ext 1200 Ext 1300

Figure 3-1 Example of SL2100 IP Network Configuration

SECTION 2 NETWORK ADDRESSING OVERVIEW

2.2 Subnet Mask

Networking Manual 4-1

SECTION 3 CONFIGURATION EXAMPLES

3.1 Example Configuration 1 - Existing Network with Static Addressing

4-2 General IP Configuration

Figure 4-1 Example Configuration 1 - Existing Network with Static IP Address

First, program the NEC SL2100:

Networking Manual 4-3

NEC SL2100 Chassis

192. 168. 1. 254

192. 168. 1. 200

192. 168. 1. 50 192. 168. 1. 11 192. 168. 1. 10

SECTION 4 TESTING THE NEC SL2100 NETWORK CONNECTION

4-4 General IP Configuration

Figure 4-3 Testing the Network Connection

Networking Manual 4-5

4-6 General IP Configuration

SECTION 2 HOW TO USE THIS MANUAL

Networking Manual 5-1

SECTION 3 HOW TO ENTER PROGRAMMING MODE

1. Go to any working display telephone.

2. Do not lift the handset.

5. Dial the system password + Hold.

Password User Name Level Programs at this Level

SECTION 4 HOW TO EXIT PROGRAMMING MODE

1. Press Mute key to exit the program options, if needed.

SECTION 5 USING KEYS TO MOVE AROUND IN THE PROGRAMS

When you want to ... Telephone Programming

Networking Manual 5-3

When you want to ... Telephone Programming

SECTION 6 PROGRAMMING NAMES AND TEXT MESSAGES

Table 5-2 Keys for Entering Names

Use this keypad digit ... When you want to ...