SV8100 VoIP Manual v5.0

Voice over IP Manual
SV8100
IP Manual
General Information
Introduction
The UNIVERGE SV8100 system uses IP for various applications. This section describes the procedure for connecting the UNIVERGE SV8100 system to an existing data network and configuring TCP/ IP. This is the first step in implementing VoIP and other IP applications.
Network Addressing Overview

Before connecting the system to a data network, it is necessary to ob tain the relevant IP Addressing information. This information is supplied b y the IT Manager or Network Administrator at the customer site.
IP Addressing 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.22.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. 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. 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.
General IP Configuration
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 in NEC control, it cannot guarantee the performance of the users IP based voice solution. Therefore, NEC recommends connecting the VoIP equipment through a local area network using private IP addresses. For a network to be suitable for VoIP it must pass specific requirements. To make sure that the site meets these requirements an IP ready check and a site survey must be completed at each site before VoIP implementation. One way delay must not exceed 100 ms Round Trip delay must not exceed 200 ms Jitter must not exceed 100ms Packet loss must not exceed 1% Data switches must be manageable Routers must provide QOS
SV8100
Adequate bandwidth for estimated VoIP traffic (see bandwidth calculator) Depending on how QOS policies are built in the network, assignments might be needed in the SV8100 programming.
General Information
Introduction
The UNIVERGE SV8100 system uses IP for various applications. This section describes the procedure for connecting the UNIVERGE SV8100 system to an existing data network and configuring TCP/ IP. This is the first step in implementing VoIP and other IP applications.
Network Addressing Overview

Before connecting the system to a data network, it is necessary to ob tain the relevant IP Addressing information. This information is supplied b y the IT Manager or Network Administrator at the customer site.
IP Addressing 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.22.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. 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. 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.
General IP Configuration
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 in NEC control, it cannot guarantee the performance of the users IP based voice solution. Therefore, NEC recommends connecting the VoIP equipment through a local area network using private IP addresses. For a network to be suitable for VoIP it must pass specific requirements. To make sure that the site meets these requirements an IP ready check and a site survey must be completed at each site before VoIP implementation. One way delay must not exceed 100 ms Round Trip delay must not exceed 200 ms Jitter must not exceed 100ms
SV8100
Packet loss must not exceed 1% Data switches must be manageable Routers must provide QOS Adequate bandwidth for estimated VoIP traffic (see bandwidth calculator) Depending on how QOS policies are built in the network, assignments might be needed in the SV8100 programming.
SV8100 QoS
When transmitting Voice over an IP network it is important to consider Quality of Service (QoS). This is the perceived quality of speech after being transmitted over the network. It is recommended that you consult the "Voice over IP Reference Guide" as this discusses the issues that should be considered when implementing a VoIP network. QoS is implemented by the network hardware, not the SV8100. The SV8100 can "mark" its data with appropriate tags and the network equipment has to be configured to prioritise that data over other (non VoIP) data. The Network Administrator should supply the SV8100 installer with the relevant QoS settings. QoS can be implemented at Layer 2 (within the Ethernet Frame) or Layer 3 (within the IP packet). Wizard Advanced Items/VoIP/QoS Settings/Layer 2 QoS and VLAN. (PRG84-09) QoS is implemented at Layer 2 by using VLAN (IEEE 802.1p/Q) tags. Choose which interface to be programmed: Interface 1 = CP00 Ethernet connection Interface 2 = IPL VoIP connection For any VoIP application interface 2 is used. VLAN Mode - By default the system does not use VLAN tags so these have to be enabled. Once enabled, all frames transmitted by the CP00 and IPL cards use the VLAN tags. VLAN ID - This is the VLAN that the system belongs to. Valid values are 0 to 4094. Priority - The priority should be configured between 0 (no prioritisation) to 7 (highest priority).
Wizard Advanced Items/VoIP/QoS Settings/Layer 3 QoS. (PRG84-10) This is the most common form of QoS. It utilises the Type of Service (ToS) field within the IP packets, and can be configured based on two different QoS standards: IP Precedence and Differentiated Services (Diffserv). Although IP Precedence and Diffserv are both supported on the SV8100, it is becoming more common to use Diffserv only. The two methods of QoS are interoperable (IP precedence values can be mapped to Diffserv values). The ToS value can be set for each type of VoIP packet. ToS Mode Choose Disabled, IP Precedence or Diffserv depending on the network requirements. IP Precedence Priority Only use if the ToS Mode is set to IP Precedence. Enter the required IP Precedence value from 0 to 7. IP Precedence Delay Normally this value is not required. Use only IP Precedence Priority (above). IP Precedence Throughput Normally this value is not required. Use only IP Precedence Priority (above). IP Precedence Reliability Normally this value is not required. Use only IP Precedence Priority (above). IP Precedence Cost Normally this value is not required. Use only IP Precedence Priority (above). Diffserv Use only if the ToS Mode is set to Diffserv. Enter the required Diffserv value from 0 to 63. Below is a table showing which QoS item is required for each particular VoIP feature of the SV8100.
SV8100
Be aware that the RTP/RTCP Layer 3 QoS setting is common to all signalling protocols so if there are several VoIP protocols being used on the same system the speech cannot have different QoS values per protocol. E.g. If an SV8100 is programmed to use NetLink and SIP trunks, the speech will have the same QoS value whether a NetLink call is in progress or a SIP trunk call is in progress. The signalling for both protocols, however, can have different values.
IP Address Collision
Description
This is a new feature for R5 SV8100 system software. The system sends Gratuitous ARP (G-ARP) requests to check whether any other devices in the network have the same IP address as the CCPU, the IPL and the VoIPU Gateways. If an IP address collision is detected an alarm can be triggered.
SV8100 Programming
The only programming required is the Alarm setup, the Alarm Display Telephone and email notification if required. Set up the parameters of the Alarm using Alarm number 57 in Wizard Advanced Items/Maintenance/Alarms/System Alarm Setup (PRG90-10). Assign the extension number for the Alarm Display Telephone in Wizard Advanced Items/Maintenance/Alarms/System Alarm Display Setup (PRG90-50-01).
SV8100 Requirements
The following information provides requirements for IP address collision detection. Main Software IP address collision detection is supported with V5.00 or higher release of the SV8100. Hardware The SV8100 requires the following hardware:
6
CD-CP00 (V5.00 or higher) PZ-32IPL, PZ-64IPL, PZ-128IPL The Alarm can be displayed on the following terminal: DT300 DT700 DTermIP
SV8100
Capacity Up to ten IP addresses can be checked for duplication using this feature. The ten IP addresses are the CCPU, the IPL and up to eight VoIPU Gateway addresses.
Operation The diagram below shows the operational flow for this feature.
SV8100
Conditions/Comments The collision alarm will continue until the IP address conflict is resolved. The collision detection will only occur in the same subnet as the SV8100. The G-ARP packets are sent every 5 minutes, this timer is not programmable. If multiple IP address collisions are detected only one will be shown on the Alarm Display Telephone. The table below shows information about alarm priorities.
8
Command to be checked Alarm display name Collision(01) Collision(02) Collision(03) Collision(04) Collision(05) Collision(06) Collision(07) Collision(08) Collision(09) Collision(10)
SV8100
Alarm display priority
PRG 10-12-01 PRG 10-12-09 PRG 84-26-01 GW 1 PRG 84-26-01 GW 2 PRG 84-26-01 GW 3 PRG 84-26-01 GW 4 PRG 84-26-01 GW 5 PRG 84-26-01 GW 6 PRG 84-26-01 GW 7 PRG 84-26-01 GW 8
10 1 2 3 4 5 6 7 8 9
IPL Differences
Description
The IPLB VoIPDB is a replacement for the IPLA VoIPDB. The main differences are the number of IP address required for the VoIP Gateways is reduced from 8 to 1 and there is an improvement to the echo canceller. Note: The IPLB VoIPU card is not available until June 2011. Note: The SV8100 requires V5.00 (or later) system software to run the IPLB.
IP Address Requirements
IPLB Requirements Card Type 32IPLB 64IPLB 128IPLB Required IP Addresses 2 2 2 Notes One IP address is required regardless of the number of DSPs. One further IP address is required for registration/signalling
IPLA Requirements Card Type 32IPLA 64IPLA 128IPLA Required IP Addresses 3 5 9 Notes One IP address is required per 16 DSPs. One further IP address is required for registration/ signalling
SV8100
Which IPL is Installed
There are several ways to identify which IPL is installed in an SV8100, this varies depending on whether you use a handset, PC Pro or Web Pro.
Handset On a DT300 or DT700 (with display) press Feature 4 The display shows either: E.g. VoIPDBTYPE IPLA 128 MAC: 00:60:B9:00:00:00 DSP:Active/Reserved 000/000 Or E.g. VoIPDBTYPE IPLB 128 MAC: 00:60:B9:00:00:00 DSP:Active/Reserved 000/000
PC Pro Take a full download from the SV8100 and navigate to the System Configuration screen The IPL type and size can be seen in the Version Information box:
This shows that an IPLA128 is installed.
This shows that an IPLB64 is installed.
If NetLink is configured PC Pro will only show the IPL information of the CPU that it is connected to.
Web Pro Connect to the SV8100 and navigate to System Data, PRG90-34
If the above items (circled in red) are populated then this indicates that an IPLB is installed. If they are not populated then this indicates that an IPLA is installed. Note: PRG90-34 can be used to identify whether an IPLA or IPLB is installed using handset programming or PC Pro as well as Web Pro.
Jitter Buffer
The jitter buffer size has been increased on the IPLB compared with the IPLA. The table below shows the adjustment.
10
Codec G.711 G.726 G.729A/B G.723.1 G.722 iLBC T.38 UDPTL T.38 RTP Supported RTP Packet Size (VIF Size) 10, 20, 30, 40ms 10, 20, 30, 40ms 10, 20, 30, 40, 50, 60ms 30, 60ms 10, 20, 30, 40ms 20, 30, 40ms 10, 20, 30, 40ms 10, 20, 30, 40ms
SV8100
IPLA Jitter Buffer Max Size (ms) 160 160 270 270 160 160 Same as used RTP codec Same as used RTP codec IPLB Jitter Buffer Max Size (ms) 255 255 300 300 255 255 Same as used RTP codec Same as used RTP codec
Other information
IPLB NIC Settings The IPLB has a programming option to alter its network speed and duplex settings (PRG10-12-11). The IPLB does not support half duplex so do not use these options. If the IPLB is set to a static value the network switch port must also be set to the same static value.
Voice Activity Detection (VAD) VAD is not supported on the IPLB for the following codecs: G.722 G.723 iLBC
ICMP Redirect The IPLB will follow the programming option for ICMP Redirect. The IPLA ignores the programming option for ICMP Redirect, it is always disabled.
LED Indications
IPLA LED Indications LED Link 10/100 Link 1000 DUPLEX Activity Function 10Base-T/100Base-TX link speed indicator 1000Base-T link speed indicator Duplex Status Link activity or data transmission and reception LED Status On Red On Red On Yellow On Green Operation Status 100Base-TX link up 1000Base-T link up Full duplex operation Link up complete
IPLA Data Activity Indications Link Up LED 1Gbps ACT Duplex Link 1G ON ON ON Auto Negotiation 100Mbps Half ON OFF OFF Full ON ON OFF 10Mbps Half ON OFF OFF Full ON ON OFF ON ON ON 1Gbps Fixed Mode 100Mbps Half ON OFF OFF Full ON ON OFF 10Mbps Half ON OFF OFF Full ON ON OFF
SV8100
Link 10/100 OFF ON ON OFF OFF OFF ON ON ON ON
11
IPLB LED Indications LED Link 10 Link 100 Link 1000 ACT Function 10Base-T link speed indicator 100Base-TX link speed indicator 1000Base-T link speed indicator Link activity or data transmission and reception LED Operation status ACT Off Off On On LINK1000 Off On On Off LINK100 Flash Flash Flash Flash LINK10 Flash Flash Flash Flash State of half duplex transmission (Not supported) Please change Hub or Switch port to full duplex transmission. Flash Blinking one by one The firmware is being updated. Internal Error (Hardware Error) LED Status On Red On Red On Yellow On Green Operation Status 10Base-T link up 100Base-TX link up 1000Base-T link up Link up complete LED flashes when data is transmitted or received
12
SV8100
IPLB Layout Information
IPLA Layout Information
IPL Information
When assigning the IP addresses to the IPL card, the addresses must be in the same network (subnet). The CPU Ethernet connection requires a separate IP address in a different network (subnet). When you have an IPL card attached to the CPU, the CPU NIC is no longer required. All connections that previously terminated to the CPU NIC card can now be terminated to the IPL NIC. For example, PC Pro, Web Pro, SMDR, etc. terminate to the IPL NIC card, when installed. Both the IPL and CPU NIC share the same default gateway assignment. The default gateway command is used by both NICs, allowing only one device, IPL or CPU, to route outside of its own network. The programming information can be found in the relevant section of the IP Manual. When an IP Phone or IP Trunk calls a legacy device (Keyphone, SLT, trunk) the speech has to be converted from IP to TDM technologies. The IPL card provides this function. The IPL card has a number of DSP resources on board; each one can convert a speech channel from IP to TDM and vice versa. Note: It is possible for IP phones to talk directly to other IP phones without using any DSPs. This is referred to as Peer to Peer communication.
SV8100
13
Available Codecs A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPL card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. There are several different codecs available for use on the SV8100 as listed below. G.711 (64kbps) G.722 (64kbps) G.726 (32kbps) iLBC (13.33kbps)* G.729 (8kbps) G.723 (5.3kbps)* *To use either of these two codecs a programming command must be altered (set Codec Mode to G.723/iLBC in Wizard Advanced Items/VoIP/General Settings/VoIP Configuration/IPL Basic Setup. (PRG84-27-02). If this command is enabled the number of VoIP resources will be reduced if using an IPLA VoIP card, the IPLB does not have this limitation. See the IPLA DSP Information or IPLB DSP Information page. Not all of these codecs are available for all VoIP applications, refer to the relevant section of this manual for further information. VoIP Gateways The number of IP addresses required for the VoIP Gateways depends on whether there is an IPLA VoIP card installed or an IPLB VoIP card installed. Please refer to the IPL General Information page for further information. Ethernet Status The connection status of the IPL Ethernet connection can be determined by observing the four LEDs on the IPL VoIP card. The LED indications depend on whether there is an IPLA VoIP card installed or an IPLB VoIP card installed. Please refer to the IPL Differences page for further information.
IPL Basic Setup

Below is information about IPL Basic Setup. Please refer to the comments section as some of the items only apply if an IPLB VoIP card is installed rather than an IPLA VoIP card. Note: The IPLB VoIPU card is not available until June 2011 PRG84-27 Item No 01 Name DTMF Relay Data 0: Disabled 1: In-Band 2: Out of Band 0:default 1:Mode1(G723/iLBC) Default 0 Comments Used for IPLA and IPLB
02
Setup CODEC Mode
IPLB does not restrict the number of available DSPs if this item is enabled. For IPLA restrictions please refer to IPL DSP Information page
03
SRTP Mode Setup
0:disable 1:enable
IPLB does not restrict the number of available DSPs if this item is enabled. For IPLA restrictions please refer to IPL DSP Information page
06 07
H.245 Port Preparation Complete Port
10100 4000
10100 4000
Used for IPLA and IPLB Used for IPLA and IPLB
14
Item No 01 Name DTMF Relay Data 0: Disabled 1: In-Band 2: Out of Band
SV8100
Default 0 Comments Used for IPLA and IPLB
08 09 10 11 12 13
DTMF Duration(Inband) DTMF Pause DTMF Twist Positive Level DTMF Twist Negative Level DTMF Duration(Outband) DTMF Level
0:follow RFC2833 25-2000(ms) 0:follow RFC2833 25-2000(ms) 0-24(dB) 0-24(dB) 30-2000(ms) 1-61(-36db 1: -36 db 2: -35 db 37: 0 db 60: 23 db 61: 24 db -24db)
0 0 5 0 100 25(12db)
Used only for IPLB Used only for IPLB Used only for IPLB Used only for IPLB Used only for IPLB Used only for IPLB
14
ICMP Redirect
0...enable 1...disable
Use only IPLB-A
IPLA DSP Information

With an IPLA VoIP card installed it is possible, depending on system programming, that the number of VoIP resources will be lower than the actual number available on the card. This will occur if sRTP (encryption) is enabled or if the iLBC/G.723 codecs are made available. See the tables below for the actual number of available resources. IPLA Resource Information G.723 32IPLA G.711 G.722 G.726 G.729 iLBC G3 Fax
PRG84-27-02 Enabled
sRTP Disabled sRTP Enabled
32
32
32
32
24
24
32
32
24
24
24
16
16
28
G.723 64IPLA G.711 G.722 G.726 G.729
iLBC G3 Fax
PRG84-27-02 Enabled
sRTP Disabled
64
64
64
64
48
48
64
SV8100
sRTP Enabled 64 48 48 48 32 32 56
15
G.723 128IPLA G.711 G.722 G.726 G.729
iLBC G3 Fax
PRG84-27-02 Enabled
128
128
128
128
96
96
128
128
96
96
96
64
64
112
IPLB DSP Information

With the IPLB VoIP card there are no channel limitations regardless of which codec is used or whether sRTP is enabled. The tables below indicate this improvement. Note: The SV8100 requires software V5.0 or later to run the IPLB card. IPLB Resource Information G.723 32IPLB G.711 G.722 G.726 G.729 iLBC G3 Fax
PRG84-27-02 Enabled 32 32 32 32
32 32
32 32
32 32
32 32
32 32
G.723 64IPLB G.711 G.722 G.726 G.729
iLBC G3 Fax
PRG84-27-02 Enabled 64 64
64
64
64
64
64
64
64
64
64
64
64
64
G.723 128IPLB G.711 G.722 G.726 G.729
iLBC G3 Fax
PRG84-27-02 Enabled 128 128 128 128
128 128
128 128
128 128
128 128
128 128
16
SV8100 IPLB Echo Canceller Setup

This command is only used if an IPLB is installed. PRG84-31 Type No 1...H.323 Trunk 2DtermIP Type 1 3DtermIP Type 2 4DtermIP Type 3 5DtermIP Type 4 6DtermIP Type 5 7...AspireNet 8...SIP Trunk 9...SIP Extension 10...K-CCIS 11...DT700 Type 1 12...DT700 Type 2 13...DT700 Type3 14...DT700 Type4 15...DT700 Type5 16...NetLink
Item No 01 02
Name TDM Echo Canceller mode TDM Echo Canceller NLP mode (2W)
Data 0disable 1enable 0...disable 1...enable 2...Long Echo Path Mode 3...Long Echo Path Auto Detect Mode 0...disable 1...enable 0-15
Default 1 1
Comments Enable/Disable the echo canceller on the receiving (TDM) side. Use to select echo compression mode for remaining echo. Used when PRG84-31-01 is set to 1.
03
TDM Echo Canceller ComfortNoise mode TDM Echo Canceller NLP Threshold
Enable/Disable comfort Noise as background noise. Used when PRG84-31-01 is set to 1. * Use to setup threshold level when using echo compression mode. Used when Program 84-31-02 is set to 1. Used when Program 84-31-01 is set to 1. Use to select length of echo. Used when Program 84-31-01 is set to 1.
04
12
05 06
TDM Echo Canceller Tail Displacement TDM Echo canceller tail length
0-89(0ms 132ms 2...48ms 364ms 4...80ms 5...96ms 6...112ms 7128ms 0-6(-9db 0...-9 db 1...-6 db 2...-3 db : 5...6 db 6...9 db
890ms)
0 7
07
TDM Echo Canceller Default ERL Level
9db)
5(6db)
Used when Program 84-31-01 is set to 1.
08
TDM Echo Canceller Echo Type
0...disable 1... Line echo canceller 2...Acoustic echo canceller
Use to select echo canceller type. 1: Based upon ITU-T G.168 2: Based upon ITU-T G.167 Used when Program 84-31-01 is set to 1.
SV8100
09 TDM Max ERLE 0-10(24-54db) 0...24 db 1...27 db : 9...51 db 10...54 db 0...disable 1...TxLevelControl mode 2...TxAutomaticLevelControl mode 3...TxHLC (HighLevelCompensation) mode 0-16(-24 24db) 0...-24 db 1...-21 db 2...-18 db : 8...0 db : 14...18 db 15...21 db 16...24 db 0-12(-42 -6 dBm) 0...-42 dBm 1...-39 dBm : 7...-21 dBm : 11...-9 dBm 12...-6 dBm 0-42(-42 0dBm) 0...-42 dBm 1...-41 dBm : 42...0 dBm 0disable 1enable 0...-42 dBm 1...-41 dBm : 42...0 dBm 2
17
Use to select maximum echo return loss level. Used when Program 84-31-01 is set to 1.
10
TDM Tx Level Control
Use to select Transmit level control mode.
11
TDM Tx LevelControl Level
Use to select Transmit voice level. Used when Program 84-31-10 is set to 1.
12
TDM Tx AutomaticLevelControl Level
Use to select target gain. Used when Program 84-31-10 is set to 2.*
13
TDM Tx HLC Threshold
41
Use to select HLC threshold level. Used when Program 84-31-10 is set to 3.
14 15
TDM Tx Gain Compression mode TDM Tx Gain Compression Threshold
1 41
Enable/Disable Transmit Gain Compression. Use to select Transmit Gain Compression Threshold level. Used when Program 84-31-14 is set to 1. Use to select Receive level control mode.*
16
TDM Rx Level Control
0...disable 0 1...RxLevelControl mode 2... RxAutomaticLevelControlFlag 0-16(-24 24db) 0...-24 db 1...-21 db 2...-18 db : 8...0 db : 14...18 db 15...21 db 16...24 db 0-12(-42 -6 dBm) 0...-42 dBm 1...-39 dBm : 7...-21 dBm : 8
17
TDM Rx LevelControl Level
Use to select Receive voice level. Used when Program 84-31-16 is set to 1.*
18
TDM Rx AutomaticLevelControl Level
18
11...-9 dBm 12...-6 dBm 19 20 RTP Echo Canceller mode RTP Echo Canceller NLP mode 0disable 1Enable 0...disable 1...enable
SV8100
0 0
Disable/Enable the echo canceller on sending (RTP) side. Disable/Enable the echo compression mode for remaining echo. Used when Program 84-31-19 is set to 1. Enable/Disable comfort Noise as background noise. Used when Program 84-31-19 is set to 1.* Use to setup threshold level when using echo compression mode. Used when Program 84-31-19 is set to 1. Use to set up off-set time of echo canceller window. Used when Program 84-31-19 is set to 1.* Use to select length of echo. Used when Program 84-31-19 is set to 1.*
21
RTP Echo Canceller ComfortNoise mode
0...disable 1...enable
22
RTP Echo Canceller NLP Threshold RTP Echo Canceller Tail Displacement
0-15
12
23
0-89(0ms
890ms)
24
RTP Echo Canceller Tail Length
132ms 2...48ms 364ms 4...80ms 5...96ms 6...112ms 7128ms 0-6(-9db 0...-9 db 1...-6 db 2...-3 db : 5...6 db 6...9 db 9db)
25
RTP Echo Canceller Default ERL Level
5(6db)
Used when Program 84-31-19 is set to 1.*
26
RTP Echo Canceller Echo Type
0...disable 1...Line echo canceller 2...Acoustic echo canceller
Use to select echo canceller type. 1: Based upon ITU-T G.168 2: Based upon ITU-T G.167 Used when Program 84-31-19 is set to 1. Use to select maximum echo return loss level. Used when Program 84-31-19 is set to 1.*
27
RTP Max ERLE
0-10(24-54db) 0...24 db 1...27 db : 9...51 db 10...54 db 0...disable 1...TxLevelControl mode 2...TxAutomaticLevelControl mode 3...TxHLC (HighLevelCompensation) mode 0-16(-24 24db) 0...-24 db 1...-21 db 2...-18 db : 8...0 db : 14...18 db 15...21 db 16...24 db
2(30db)
28
RTP Tx Level Control
Use to select Transmit level control mode.
29
RTP Tx Level Control Level
Use to select Transmit voice level. Used when Program 84-31-28 is set to 1.
SV8100
30 RTP Tx AutomaticLevelControl Level 0-12(-42dBm 0...-42 dBm 1...-39 dBm : 7...-21 dBm : 11...-9 dBm 12...-6 dBm 0-42(-42dBm 0...-42 dBm 1...-41 dBm : 42...0 dBm 0disable 1enable 0-42(-42dBm 0...-42 dBm 1...-41 dBm : 42...0 dBm 0dBm) -6 dBm) 7
19
31
RTP Tx HLC Threshold
0dBm)
42
Use to select HLC threshold level. Used when Program 84-31-28 is set to 3.
32 33
RTP Tx Gain Compression mode RTP Tx Gain Compression Threshold
0 42
Enable/Disable Transmit Gain Compression. Select Transmit Gain Compression Threshold level. Used when Program 84-31-32 is set to 1. Use to select the Receive level control mode.*
34
RTP Rx Level Control
0...disable 0 1...RxLevelControl mode 2... RxAutomaticLevelControlFlag 0-16(-24db 0...-24 db 1...-21 db 2...-18 db : 8...0 db : 14...18 db 15...21 db 16...24 db 24db) 8
35
RTP Rx LevelControl Level
Use to select the Receive voice level. Used when Program 84-31-34 is set to 1.*
36
RTP Rx AutomaticLevelControl Level
0-12(-42 -6 dBm) 0...-42 dBm 1...-39 dBm : 7...-21 dBm : 11...-9 dBm 12...-6 dBm 0...disable 1...enable 2...Long Echo Path Mode 3...Long Echo Path Auto Detect Mode
37
TDM Echo Canceller NLP mode (4W)
Use to select the echo compression mode for remaining echo. Used when Program 84-31-01 is set to 1.*
* Do not change these settings without guidance or instruction from NEC Technical Support.
IPLB SIP MLT Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Codec. (PRG84-24)
20
Item No 04 Name G.711 jitter buffer min Data
SV8100
Default 30 Comments 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 2:Self adjusting(silence period) is not valid for IPLB. If you set this value, operate same as 3: Self adjusting. 0-255ms
05
G.711 jitter buffer average
0-255ms
60
06
G.711 jitter buffer max
0-255ms
120
09
G.729 jitter buffer min
0-300ms
30
10
0-300 ms
60
11
0-300ms
120
17
jitter buffer mode
1...Fixed 2...Self adjusting(silence period) 3...Self adjusting
19
Idle Noise Level
5000-7000 (-5000dbm -7000dbm)
7000
Not used IPLB-A.
20
Echo Canceller Mode
0Disable 1Enable
Not used IPLB-A. Echo canceller setup is 84-31.
21
Signal Limiter
1Mode0 2Mode1 3...Mode2 4...Mode3 5...Mode4 6...Mode5
Not used IPLB-A.
22
Echo canceller NLP mode
0 2 wire and 4 wire 1 2 wire only
24
Echo Canceller NLP Noise Setting
0 1
0Adaptive
SV8100
1Fixed 26 TX Gain 0-40 (-14dbm ~ +14dbm) 20 Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31.
21
27
RX Gain
0-20 dbm 1-19 dbm : 200 dbm : 3919 dbm 4020 dbm
20
33
G.722 VAD mode
0Disable 1Enable
Not used IPLB-A
34
0-255ms
30
0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms Used only for IPLB-A
35
0-255ms
60
36
0-255ms
120
38
DTMF Level mode
0... VOIPU 1... Mainsoft
39
DTMF Level High
0...disable 1...-33dBm : 28...-6dBm
28
Used only for IPLB-A
40
DTMF Level Low
0...disable 1...-33dBm : 28...-6dBm
28
IPLB DtermIP Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red.
22
SV8100
Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Extensions/DTermIP Extension/DTermIP Codec Setup. (PRG84-11)
Item No
04
Name
G.711 Jitter Buffer (min)
Data
0-255ms
Default
30
Comments
0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms 2:Self adjusting(silence period) is not valid for IPLB. If you set this value, operate same as 3: Self adjusting. Not used IPLB-A. Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A.
05
G.711 Jitter Buffer (average) 0-255ms
60
06
G.711 Jitter Buffer (max)
0-255ms
120
09
0-300ms
30
10
G.729 Jitter Buffer (average) 0-300 ms
60
11
0-300ms
120
14
0-300 ms
30
15
G.723 Jitter Buffer (average) 0-300 ms
60
16
0-300 ms
120
17
jitter buffer mode
1...Fixed 2...Self adjusting(silence period) 3...Self adjusting 5000-7000 (-5000dbm 0Disable 1Enable 1Mode0 2Mode1 3...Mode2 4...Mode3 5...Mode4 6...Mode5 0 2 wire and 4 wire 1 2 wire only -7000dbm)
19 20 21
Idle Noise Level Echo Canceller Mode Signal Limiter
7000 1 6
22 24 26 27
1 0 20 20
Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31.
Echo Canceller NLP Noise 0Adaptive Setting 1Fixed TX Gain RX Gain 0-40 (-20dbm ~ + 20dbm) 0 -20 dbm 1 -19 dbm : 20 0 dbm :
SV8100
39 19 dbm 40 20 dbm 33 34 DTMF Level mode DTMF Level High 0... VOIPU 1... Main software 0...disable 1...-33dBm : 28...-6dBm 0...disable 1...-33dBm : 28...-6dBm 0 0 Used only for IPLB-A Used only for IPLB-A
23
35
DTMF Level Low
IPLB SIP Extension Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Extensions/SIP Extensions/SIP Codec Setup. (PRG84-19) Item No 04 05 06 09 10 11 13 14 15 16 17 Name G.711 jitter buffer min G.711 jitter buffer average G.711 jitter buffer max G.729 jitter buffer min G.729 jitter buffer average G.729 jitter buffer max G.723 VAD mode G.723 jitter buffer min G.723 jitter buffer average G.723 jitter buffer max jitter buffer mode Data 0-255ms 0-255ms 0-255ms 0-300ms 0-300ms 0-300ms 0Disable 1Enable 0-300 ms 0-300 ms 0-300 ms 1...Fixed 2...Self adjusting (silence period) 3...Self adjusting 5000-7000 (-5000dbm to 7000dbm) 0Disable 1Enable 1 Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Default 30 60 120 30 60 120 0 30 60 120 3 Comments 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms Not used IPLB-A 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 2: Self adjusting (silence period) is not valid for IPLB. If this value is used it will operate the same as 3: Self adjusting Not used IPLB-A.
19
Idle Noise Level
7000
20
Echo Canceller Mode
24
21 Signal Limiter 1Mode0 2Mode1 3...Mode2 4...Mode3 5...Mode4 6...Mode5
SV8100
6 Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A.
22 24 26
Echo canceller NLP mode Echo Canceller NLP Noise Setting TX Gain
0 2 wire and 4 wire 1 2 wire only 0Adaptive 1Fixed 0-40 (-20dbm ~ +20dbm) 0-20 dbm 1-19 dbm : 200 dbm : 3919 dbm 4020 dbm
1 0
Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Echo canceller setup is 8431.
20
27 34 35 36 37 40 41 42 44 45 46
RX Gain G.722 VAD mode G.722 jitter buffer min G.722 jitter buffer average G.722 jitter buffer max G.726 jitter buffer min G.726 jitter buffer average G.726 jitter buffer max iLBC VAD mode iLBC jitter buffer min iLBC jitter buffer average 0Disable 1Enable 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0Disable 1Enable 0-255ms 0-255ms
20 0 30 60 120 30 60 120 0 30 60
Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Not used IPLB-A 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 2: Self adjusting (silence period) is not valid for IPLB. If this value is used it will operate the same as 3: Self adjusting
47
iLBC jitter buffer max
0-255ms
120
52
Fax Max Rate
0...V.27ter, 2400 bps 1...V.27ter, 4800 bps 2...V.29, 7200 bps 3...V.29, 9600 bps 4...V.17, 12000 bps 5...V.17, 14400 bps 0-600 ms 20-48 bytes
53 54
Fax Playout FIFO Nominal Delay Fax packet size
300 20
Not used IPLB-A. Not used IPLB-A.
SV8100
55 High speed data packet redundancy 1:10ms 2:20ms 3:30ms 4:40ms 0-5 4 Not used IPLB-A.
25
56
low Speed Data Redundancy
Only values 0-2 are valid for IPLB. If a value higher than 2 is used then the effective data is 2. Not used IPLB-A. Not used IPLB-A. Used only for IPLB-A Used only for IPLB-A
59 60 62 63
Maximum low speed data packetization Transmit Network Timeout DTMF Level mode DTMF Level High
1-65535 bytes 10 - 32000sec 0... VOIPU 1... Mainsoft 0...disable 1...-33dBm : 28...-6dBm 0...disable 1...-33dBm : 28...-6dBm
1 150 0 28
64
DTMF Level Low
28
IPLB NetLink Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Codec. (PRG84-25) Item No 04 05 06 09 10 11 13 14 15 16 17 Name G.711 jitter buffer min G.711 jitter buffer average G.711 jitter buffer max G.729 jitter buffer min G.729 jitter buffer average G.729 jitter buffer max G.723 VAD mode G.723 jitter buffer min G.723 jitter buffer average G.723 jitter buffer max jitter buffer mode Data 0-255ms 0-255ms 0-255ms 0-300ms 0-300 ms 0-300ms 0Disable 1Enable 0-300 ms 0-300 ms 0-300 ms 1...Fixed 2...Self adjusting(silence period) Default 30 60 120 30 60 120 0 30 60 120 3 Comments 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms Not used IPLB-A. 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 2:Self adjusting(silence period) is not valid at IPLB. If you set this value, operate same as 3: Self adjusting
26
SV8100
3...Self adjusting 19 20 21 Idle Noise Level Echo Canceller Mode Signal Limiter 5000-7000 (-5000dbm 0Disable 1Enable 1Mode0 2Mode1 3...Mode2 4...Mode3 5...Mode4 6...Mode5 0 2 wire and 4 wire 1 2 wire only 0Adaptive 1Fixed 0-40 (-14db ~ +14db) 0-20 dbm 1-19 dbm : 200 dbm : 3919 dbm 4020 dbm 0Disable 1Enable 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0Disable 1Enable 0-255ms 0-255ms 0-255ms 0... VOIPU 1... mainsoft 0...disable 1...-33dBm : 28...-6dBm 0...disable 1...-33dBm : 28...-6dBm 7000 -7000dbm) 1 6 Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Not used IPLB-A.
22 24 26 27
Echo canceller NLP mode Echo Canceller NLP Noise Setting TX Gain RX Gain
1 0
Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Echo canceller setup is 8431. Not used IPLB-A. Echo canceller setup is 8431.
20 20
34 35 36 37 40 41 42 44 45 46 47 50 51
G.722 VAD mode G.722 jitter buffer min G.722 jitter buffer average G.722 jitter buffer max G.726 jitter buffer min G.726 jitter buffer average G.726 jitter buffer max iLBC VAD mode iLBC jitter buffer min iLBC jitter buffer average iLBC jitter buffer max DTMF Level mode DTMF Level High
0 30 60 120 30 60 120 0 30 60 120 0 28
Not used IPLB-A 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Not used IPLB-A 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Used only for IPLB-A. Used only for IPLB-A.
52
DTMF Level Low
28
Used only for IPLB-A.
SV8100 IPLB AspireNet Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Setup/AspireNet Codec Setup. (PRG84-12) Item No 04 Name Data Default 30 Comments 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 2:Self adjusting(silence period) is not valid at IPLB. If you set this value, operate same as 3: Self adjusting Not used IPLB-A.
27
G.711 jitter buffer min 0-255ms
05
0-255ms
60
06
G.711 jitter buffer max 0-255ms
120
09
30
10
G.729 jitter buffer average G.729 jitter buffer max
0-300ms
60
11
0-300ms
120
14
30
15
G.723 jitter buffer average G.723 jitter buffer max jitter buffer mode
0-300ms
60
16
0-300ms
120
17
1...Fixed 2...Self adjusting (silence period) 3...Self adjusting 5000-7000 (-5000dbm to 7000dbm) 0Disable 1Enable VOIPDB-A1/IPLA/PZ 1Mode0 2Mode1 3...Mode2 4...Mode3 5...Mode4 6...Mode5 -
19
Idle Noise Level
7000
20 21
Echo Canceller Mode Signal Limiter
1 6
Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A.
22 24
Echo canceller NLP mode Echo Canceller NLP Noise Setting
0 2 wire and 4 wire 1 1 2 wire only 0Adaptive 1Fixed 0
Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31.
28
26 27 TX Gain RX Gain 0-40 (-20dbm ~ +20dbm) 0-20 dbm 1-19 dbm : 200 dbm : 3919 dbm 4020 dbm
SV8100
20 20 Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31.
35
30
0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Used only for IPLB-A Used only for IPLB-A
36
G.722 jitter buffer average G.722 jitter buffer max DTMF Level mode DTMF Level High
0-255ms
60
37
0-255ms
120
39 40
0... VOIPU 1... Mainsoft 0...disable 1...-33dBm : 28...-6dBm 0...disable 1...-33dBm : 28...-6dBm
0 0
41
DTMF Level Low
IPLB SIP Trunk Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Networking/SIP Networking/Codec Setup. (PRG84-13) Item No 04 05 06 09 10 11 13 14 Name G.711 jitter buffer min G.711 jitter buffer average G.711 jitter buffer max G.729 jitter buffer min G.729 jitter buffer average G.729 jitter buffer max G.723 VAD mode G.723 jitter buffer min Data 0-255ms 0-255ms 0-255ms 0-300ms 0-300ms 0-300ms 0Disable 1Enable 0-300 ms Default 30 60 120 30 60 120 0 30 Comments 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms Not used IPLB-A 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms
SV8100
15 16 17 G.723 jitter buffer average G.723 jitter buffer max jitter buffer mode 0-300 ms 0-300 ms 1...Fixed 2...Self adjusting (silence period) 3...Self adjusting 5000-7000 (-5000dbm to 7000dbm) 0Disable 1Enable 1Mode0 2Mode1 3...Mode2 4...Mode3 5...Mode4 6...Mode5 0 2 wire and 4 wire 1 2 wire only 0Adaptive 1Fixed 0-40 (-20dbm ~ +20dbm) 0-20 dbm 1-19 dbm : 200 dbm : 3919 dbm 4020 dbm 0Disable 1Enable 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0Disable 1Enable 0-255ms 0-255ms 0-255ms 0...V.27ter, 2400 bps 0 20 20 1 6 Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. 60 120 3 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms
29
2: Self adjusting (silence period) is not valid for IPLB. If this value is used it will operate the same as 3: Self adjusting Not used IPLB-A.
19
Idle Noise Level
7000
20 21
Echo Canceller Mode Signal Limiter
22 24 26 27
Echo canceller NLP mode Echo Canceller NLP Noise Setting TX Gain RX Gain
Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31. Not used IPLB-A. Echo canceller setup is 84-31.
34 35 36 37 40 41 42 44 45 46 47 52
G.722 VAD mode G.722 jitter buffer min G.722 jitter buffer average G.722 jitter buffer max G.726 jitter buffer min G.726 jitter buffer average G.726 jitter buffer max iLBC VAD mode iLBC jitter buffer min iLBC jitter buffer average iLBC jitter buffer max Fax Max Rate
0 30 60 120 30 60 120 0 30 60 120 5
Not used IPLB-A 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Not used IPLB-A 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 2: Self adjusting (silence period) is not valid
30
SV8100
1...V.27ter, 4800 bps 2...V.29, 7200 bps 3...V.29, 9600 bps 4...V.17, 12000 bps 5...V.17, 14400 bps 53 54 55 Fax Playout FIFO Nominal Delay Fax packet size High speed data packet redundancy 0-600 ms 20-48 bytes 1:10ms 2:20ms 3:30ms 4:40ms 300 20 4 for IPLB. If this value is used it will operate the same as 3: Self adjusting
Not used IPLB-A. Not used IPLB-A. Not used IPLB-A.
56
low Speed Data Redundancy 0-5
Only values 0-2 are valid for IPLB. If a value higher than 2 is used then the effective data is 2. Not used IPLB-A. Not used IPLB-A. Used only for IPLB-A Used only for IPLB-A
59 60 62 63
Maximum low speed data packetization Transmit Network Timeout DTMF Level mode DTMF Level High
1-65535 bytes 10 - 32000sec 0... VOIPU 1... Mainsoft 0...disable 1...-33dBm : 28...-6dBm 0...disable 1...-33dBm : 28...-6dBm
1 150 0 28
64
DTMF Level Low
28
IPLB H.323 Trunk Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Networking/H.323 Networking/Basic Information Setup. (PRG84-01) Item No Name 07 G.729 Jitter Buffer (min) Data 0- 300ms Default 30 Comments 0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms
08
G.729 Jitter Buffer (average)
0-300ms
60
0-270 values are valid for IPLA. If you set more 270ms, then buffer size is 270ms
09
0-300ms
120
SV8100
15 jitter buffer mode 1...Fixed 3 2: Self adjusting(silence period) is not valid for IPLB. If you set this value, 2...Self adjusting(silence operate same as 3: Self adjusting. period)
31
3...Self adjusting
16
0-255ms
30
17
0-255ms
60
18
0-255ms
120
19
0-300ms
30
20
0-300ms
60
21
0-300ms
120
23
Idle Noise Level
5000-7000
7000
Not used IPLB-A.
(-5000dbm ~ -7000dbm)
24
Echo Canceller Mode
0Disable
1Enable
25
Signal Limiter
1Mode0
Not used IPLB-A.
2Mode1
3...Mode2
32
4...Mode3
SV8100
5...Mode4
6...Mode5
26
0 2 wire and 4 wire
1 2 wire only
28
Echo Canceller NLP Noise Setting
0Adaptive
1Fixed
30
TX Gain
0-40 (-20db ~ +20db)
20
0-20 dbm 31 RX Gain 20 Not used IPLB-A. Echo canceller setup is 84-31. :
1-19 dbm
200 dbm
3919 dbm
4020 dbm
36
Fax Max Rate
0...V.27ter, 2400 bps
0,2,4 are not used for IPLB.-A.
1...V.27ter, 4800 bps
2...V.29, 7200 bps
3...V.29, 9600 bps
4...V.17, 12000 bps
5...V.17, 14400 bps
37
Fax Playout FIFO Nominal Delay
0-600 ms
300
Not used IPLB-A.
SV8100
38 Fax packet size 20-48 bytes 20 Not used IPLB-A.
33
39
FAX Modem Transmission
0-13(0dBm ~ -13dBm)
Not used IPLB-A.
Level
40
FAX Modem Carrier Signal
0...-26dBm
Not used IPLB-A.
Detection Threshold
1...-33dBm
2...-43dBm
43
High-speed Signal Data (fax
1:10ms
Not used for IPLB-A.
picture signal) Packet Length
2:20ms
3:30ms
4:40ms
44
Low-speed Signal Data (FAX
0-5
Values 0-2 are valid for IPLB. If you set more 2, then 2 will be used.
Procedure Signal)
47
The Maximum, Low-speed
1-65535 bytes
Not used IPLB-A.
Signal Data (Size of Packet)
48
Network Transmission
10-32000 sec
150
Not used IPLB-A.
Time-out
49
Eflag Beginning Timer
0-65535
2600
Not used IPLB-A.
50
Eflag Stop Timer
0-65535
2600
Not used IPLB-A.
51
The Former Line Substitution
0...Disable
Not used IPLB-A.
of Scanning Line
1...Enable
52
Eflag Setting at Head DIS
34
53 TFOP Protocol
SV8100
1
54
NSF Superscription
55
ECM(Error Correction Mode)
Not used IPLB-A.
56
Enable Modified Read Code
57
NSF Country Code Setting
0-65535
Not used IPLB-A.
58
NSF Vendor Code Setting
Not used IPLB-A.
65
0-255ms
30
0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid for IPLA. If you set more 160ms, then buffer size is 160ms Used only for IPLB-A
66
0-255ms
60
67
0-255ms
120
69
DTMF Level mode
0... VOIPU defalt value 1... Mainsoft value
70
DTMF Level High
0...disable 1...-33dBm : 28...-6dBm
71
DTMF Level Low
0...disable 1...-33dBm : 28...-6dBm
IPLB K-CCIS Codec Information

Below is a list of commands that have been altered, added or removed when using an IPLB instead of IPLA. The changes are indicated in red. Note: The SV8100 requires software V5.0 or later to run the IPLB card. Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS codec Setup. (PRG84-21) Item No Name Data Default Comments
SV8100
04 G.711 jitter buffer min 0-255ms 30 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms Not used IPLB-A
35
05
0-255ms
60
06
0-255ms
120
09
0-300ms
30
10
0-300ms
60
11
0-300ms
120
13
G.723 VAD mode
0Disable 1Enable
14
0-300 ms
30
0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms 0-270 values are valid at IPLA. If you set more 270ms, then buffer size is 270ms Not used IPLB-A. Echo canceller setup is 8431.
15
0-300 ms
60
16
0-300 ms
120
17
TX Gain
0-40 (-20dbm ~ +20dbm)
20
18
RX Gain 0-20 dbm
20
Not used IPLB-A. Echo canceller setup is 8431.
1-19 dbm
200 dbm
3919 dbm
4020 dbm
36
22 Jitter Buffer Mode 1...Static
SV8100
3 2: Self adjusting (silence period) is not valid for IPLB. If this value is used it will operate the same as 3: Self adjusting
2...Imme(No tone)
3...Imme
24
Idle Noise Level
0Disable
1Enable
25
Echo Canceller Mode
0 2 wire and 4 wire
1 2 wire only
29 30 31 34 35 36 38
G.722 jitter buffer min G.722 jitter buffer average G.722 jitter buffer max G.726 jitter buffer min G.726 jitter buffer average G.726 jitter buffer max iLBC VAD mode
0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0-255ms 0Disable 1Enable
30 60 120 30 60 120 0
0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Not used IPLB-A
39 40
iLBC jitter buffer min iLBC jitter buffer average
0-255ms 0-255ms
30 60
0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms 0-160 values are valid at IPLA. If you set more 160ms, then buffer size is 160ms Used only for IPLB-A.
41
iLBC jitter buffer max
0-255ms
120
44
DTMF Level mode
0... VOIPU 1... Mainsoft
45
DTMF Level High
0...disable 1...-33dBm : 28...-6dBm
28
SV8100
46 DTMF Level Low 0...disable 1...-33dBm : 28...-6dBm 28 Used only for IPLB-A.
37
IP Extensions
This section gives an overview about IP extensions that can be connected to the SV8100. There are several different types of IP extensions that can be used. SIP MLT (DT700) Standard SIP (3rd Party) MH240 DtermIP H.323 IP DECT
SIP MLT Overview

SIP MLT extensions use an enhanced version of the SIP protocol (iSIP) developed by NEC to communicate with the SV8100 system. This allows the phones to use most of the features available on a normal (TDM) keytelephone. Use the links below for further information. SIP MLT General Information SIP MLT Features SIP MLT Key Kit SIP MLT Adapters SIP MLT Models SIP MLT Firmware Upgrade Prodedure SIP MLT IP Phone Manager
DtermIP Overview
DTermIP extensions are proprietary IP telephones that connect to the Aspire system using the NEC Protims protocol but can also connect to the SV8100 system. These phones can use most of the features that can be found on a standard (TDM) keytelephone. Use the links below for further information. DTermIP General Information
Standard SIP Overview

SIP is an industry standard protocol and therefore there are many different hardware and software based phones. As these phones are not developed by NEC and are not designed specifically for use on the SV8100, they do not support majority of the features that you would find on an SV8100 Keytelephone. The features available to SIP extensions are detailed in the SIP Extension Compatibility Report for the relevant SIP terminal. Use the links below for further information. Standard SIP General Information Standard SIP availab le features
MH240 Overview
MH240 is a WiFi handset which uses the same protocol as the SIP MLT (iSIP) which makes it a very feature rich mobile device. It can only be used in conjuction with the NEC WL 1700/1500 range of WiFi access points. It is possible for the MH240 to roam between access points with ability to handover during a conversation giving a larger coverage area. Use the links below for further information. MH240 General Information MH240 Firmware Upgrade Procedure IP Phone Manager for MH240
38
SV8100
IP DECT Overview
IP DECT is an NEC product that combines the functionality of traditional DECT with the flexibility of the Standard SIP protocol giving a robust and reliable wireless solution. The handsets use the traditional DECT protocol to communicate with the DECT Access Points (DAPs) and the DAPs use the Standard SIP Protocol to communicate with the SV8100. Use the links below for further information. IP DECT General Information
H.323 Extension Overview

H.323 is an industry standard protocol and therefore there are many different hardware and software based phones. As these phones are not developed by NEC and are not designed specifically for use on the SV8100, they do not support majority of the features that you would find on an SV8100 Keytelephone. The SV8100 is compliant with H.323 Version 3. H.323 has, in the most part, been replaced by SIP. NEC strongly recommends the use of SIP in place of H.323 wherever possible. Use the links below for further information. H.323 Extension General Information
SIP Multi-Line Terminals

The SIP MLT (DT700) Series offers a line up of modular telephones. This modular design allows the telephones to be upgraded and customized (except economy version) as required. Optional LCD panels, keypads, handset cradles, face plates and coloured side panels can easily be snapped on and off. See the tables for compatible kits. SIP MLT extensions use an enhanced version of the SIP protocol (iSIP) developed by NEC to communicate with the SV8100 system. This allows the phones to use most of the features available on a normal (non-IP) keytelephone. The phones cannot be used on any system other than the SV8000. The registration procedure for SIP MLT extensions is different to the SIP/H.323 Extensions, and is described in the SIP MLT Extension Registration section below. To run SIPMLT extensions the SV8100 must have: CP00 IPL SIP MLT License(s). Other licenses may be required for extra features/functionality.
Providing Power
SIP MLT's require power to function. This can be provided in various ways: a) Local Power The SIP MLT's have a connector for external power. This is supplied by an AC adapter that has a 27V DC output. This means that a mains socket is required in the vicinity of each SIP MLT and loss of mains power in the building will prevent the phones from working.
b)
Powered Patch Panel (Midspan) A powered patch panel has two RJ-45 connectors per SIP MLT. One port connects to the switch/hub, and the other port connects to the SIP MLT. The patch panel has an integral power supply that adds power to the spare pins of the RJ-45. When the SIP MLT is connected to the powered patch panel, it automatically receives its power via the spare pairs on the Cat-5 cable - there is no need for a local power adapter. c) Power over Ethernet (PoE) A PoE switch is a switched hub that also provides power over the spare pairs. The switch can be used with any device (not just SIP MLT's) and will detect if power is required or not. As all of the phones receive their power from one device, it is easy to protect the SIP MLT's from loss of power (by connecting the PoE switch to a UPS). There are two industry standards for PoE: Cisco Inline Power not supported by the DT700 range of SIP MLTs IEEE802.3af supported by the DT700 range of SIP MLT's
SV8100
SIP MLT Extension registration
SIP MLT ports are allocated in blocks of 2. For example Insert a 16 port extension card (e.g. DLCA, LCA) 1st DT700 to register is set to 1 (default) Configure an SIP MLT and connect to the LAN The SIP MLT will take port 17 (ext 216 in default) Port 18 will also be reserved for use by another IP extension. If a second extension card (e.g. DLCA, LCA) is inserted, it will take ports 19 onwards.
39
When connecting a SIP MLT, the MAC address (ID) is automatically registered in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Extension Setup. (PRG15-05-02) If the MAC address is entered manually, prior to connecting the phone, when the phone is connected, it may (depending on the Register Method) use the port number assigned. The MAC address is printed on the barcode label on the base of the phone. It is a 12-digit alphanumeric number, ranging from 0-9 and A-F. Note: If the port does not have a corresponding extension number assigned to it, the SIP MLT will be assigned to the next available port which does have an extension number. If there are no ports with extension numbers available, the SIP MLT with show "Full Port" on the display. If the extension number is removed from and already registered SIP MLT, it will re-register to the next available extension number. If the SV8100 is being used as a DHCP server and has default IP addresses, no configuration is required on the SIP MLT.
Registration Procedure Plug and Play When the Register Mode is set as Plug and Play in Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/ DT700 HotDesk/DT700 Logon Type. (PRG10-46-01), the following information will apply. Set the Extension Number for the SIP MLT extension against an unused (no associated hardware) port in Wizard Quick Install/ Extensions/Extension Properties (PRG11-02) The SIP MLT should be programmed to register to the IPLA card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09) When an SIP MLT connects to the SV8100, it is assigned the first available port after the value set in Wizard Advanced Items/VoIP/ Extensions/DT700 Setup/DT700 Setup/1st DT700 to register. (PRG10-46-10) If static IP addresses or external DHCP server is in use, follow these steps on the handset itself: Press Menu 0 User Name - ADMIN Password - 6633222 OK Press 1 1 - Choose DHCP on or off (depending on network requirements)Press OK Press 2 - IP Address of phone (if not DHCP) Type in the required IP address using * for . Press OK. Press 3 - Default Gateway of phone if required (if not DHCP) Press OK. Press 4 - Subnet Mask of phone (if not DHCP) Press OK. Press Exit. Press 2 2 1 - Enter the IP address of the SV8100 IPLA card Press OK. Press Exit. Press 4 1 - Enter 5080 (SIP Server port) Press OK. Press Exit several times to get to the main menu. Press Save.
40
SV8100
The SIP MLT will now attempt to connect to the SV8100.
Registration Procedure Automatic When the Register Mode is set as Automatic in Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Type. (PRG10-46-01), the following information will apply. Set the Extension Number for the SIP MLT extension against an unused (no associated hardware) port. Wizard Quick Install/ Extensions/Extension Properties (PRG11-02) The SIP MLT should be programmed to register to the IPLA card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09). Enter a Used ID and Password for each SIP MLT in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Password. It is recommended to use the extension number as the User ID. Take the Personal ID Index from the above command and enter it against the relevant extension number in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Feature. If static IP addresses or external DHCP server is in use, follow these steps on the handset itself: Press Menu 0 User Name - ADMIN Password - 6633222 OK Press 1 1 - Choose DHCP on or off (depending on network requirements) Press OK. Press 2 - IP Address of phone (if not DHCP) Type in the required IP address using * for . Press OK. Press 3 - Default Gateway of phone if required (if not DHCP) Press OK. Press 4 - Subnet Mask of phone (if not DHCP) Press OK. Press Exit. Press 2 1 1 Enter the User ID associated with that extension programmed in the SV8100 (normally the same as the extension number) Press OK. Press 2 Enter the Password associated with that extension programmed in the SV8100 Press OK. Press Exit Press 2 1 Enter the IP address of the SV8100 IPLA card Press OK. Press Exit. Press 4 1 - Enter 5080 (SIP Server port) Press OK. Press Exit several times to get to the main menu. Press Save. The SIP MLT will now attempt to connect to the SV8100.
Registration Procedure Manual This mode of registration gives the ability to Hot Desk from one SIP MLT to another. This means you can move from one handset to another and keep the same extension number and relevant programming. When the Register Mode is set as Manual in Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Type. (PRG10-46-01), the following information will apply. Set the Extension Number for the SIP MLT extension against an unused (no associated hardware) port. Wizard Quick Install/ Extensions/Extension Properties (PRG11-02) The SIP MLT should be programmed to register to the IPLA card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09). Enter a Used ID and Password for each SIP MLT in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Password. It is recommended to use the extension number as the User ID. Take the Personal ID Index from the above command and enter it against the relevant extension number in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Feature. If static IP addresses or external DHCP server is in use, follow these steps on the handset itself: -
SV8100
Press Menu 0 User Name - ADMIN Password - 6633222 OK Press 1 1 - Choose DHCP on or off (depending on network requirements)Press OK Press 2 - IP Address of phone (if not DHCP) Type in the required IP address using * for . Press OK. Press 3 - Default Gateway of phone if required (if not DHCP) Press OK. Press 4 - Subnet Mask of phone (if not DHCP) Press OK. Press Exit. Press 2 2 1 - Enter the IP address of the SV8100 IPLA card Press OK. Press Exit. Press 4 1 - Enter 5080 (SIP Server port) Press OK. Press Exit several times to get to the main menu. Press Save.
41
It is not necessary to enter the User ID and password into the handset programming, this is entered manually by the user each time they log on. The phone will attempt to connect to the SV8100 but will show the following screen: -
Enter the User ID and press the Set softkey
Enter the Password and press the OK softkey
The SIP MLT will now attempt to register to the SV8100. If the login information is accepted the display will change to normal idle status. If the extension you are trying to log on as is already in use you may be prompted with Override? On the display with a Yes and No softkey. Choosing Yes will log off the existing extension and give the extension number to you. This option can be enabled or disabled on a per Personal ID Index using the Log Off option in Wizard Advanced Items/VoIP/ Extensions/DT700 Setup./DT700 Additional features/DT700 HotDesk/DT700 Logon Password (PRG84-22-04) Log the phone off With the phone in an idle state, press the Prog soft key four times, then press the LOGOFF soft key The display shows LOGOFF THE SYSTEM? with a Yes and No soft key Press Yes
42
SV8100
The phone is now logged off and cannot be used until it is logged back on.
SIP MLT Extension registration in a NetLink Environment

From Release 4 software it is possible to register a SIP MLT to any node in a NetLink environment. If the SIP MLT is to register to the Primary system then all above information is correct and no changes are required. If the SIP MLT is to register to a secondary node the only difference is that it should register to the relevant IPL IP address and port number. The IP addresses of connected systems can be found in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Systems (PRG51-11-03). The relevant port numbers can be found in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink DT700 Registrar Ports (PRG51-17).
Conditions It is not possible for the DT700 to use the encryption feature when registered to a Secondary node. This feature is not available for Standard SIP extensions.
SIP MLT Fail-Over Operation

In a NetLink environment it is possible to enter up to 4 registration destinations. This means that if the system that a SIP MLT is registered to is no longer available it can re-register to another node in the network. Furthermore, if the original system recovers the handset may revert back to its original registrar (software release 4 feature). To set the registration destinations and port numbers for each SIP MLT follow these steps: Press Menu 0 User Name - ADMIN Password - 6633222 OK 2. SIP Settings 2. Server Address & URI st nd rd th Choose 1 , 2 , 3 or 4 Server Address in the order you wish to search Enter the IPL IP address and press OK. Press Exit 4. SIP Server Port Enter the relevant port number for each Server (default 5080) and press OK. Press Exit Press Exit Press Save. The IP addresses of connected systems can be found in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Systems (PRG51-11-03). The relevant port numbers can be found in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink DT700 Registrar Ports (PRG51-17).
Conditions NetLink Replication must be enabled for this feature to work correctly. DT700 NAT Terminals cannot use the SIP MLT Fail-Over Operation. R4 software must be installed on all nodes.
SV8100
Delete SIP MLT Registration
Before attempting to delete the registration of a SIP MLT, the IP Phone must be unplugged or powered off. Enter Program 90-23-01 (handset programming or Web Pro only), and enter the extension number of the IP Phone. Press 1 and Transfer to delete the registration.
43
SIP MLT Codec Settings

SIP MLT's can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPL card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for SIP MLT handsets G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.729 8Kbps codec MOS 4.0 To enable either G.723 or iLBC set PRG84-27-02 = 1 The bandwidth values quoted for these codecs are for the digitized speed in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. The codec is programmed against a Type (profile). Up to five Types (profiles) can be set up. The extension is then assigned to particular Type (profile). 1) Program the codec for each Type using the Audio Capability Priority option in Wizard Advanced Items/IP SIP/DT700 Setup (PRG84-24-28) 2) Assign the Type number to the extension using the Codec Type option in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Extension Setup (PRG15-05-15) Please be aware that this codec selection is only a preferred setting. It is possible that a SIP MLT will use one of the other available codecs depending on the destination of the conversation and also who was the originating party of the call.
RTP Alarm
RTP Alarm is an audible indication to a user that the RTP (speech) is not getting through to that user. It can be heard when using SIP MLT Extensions when there are problems on the network between the end points. The alarm is indicated as several short beeps in the ear piece of the receiving user, the beeps may be repeated if the problem continues. The RTP Alarm can be enabled/disabled on a per handset basis using the handset Menu: Menu 5. Setting 1. User Setting 2. Talk 1. RTP Alarm Chose the required setting for the RTP Alarm and press OK Press the Exit key to exit the handset Menu More information regarding packet loss may be obtained by using the QoS option of the SIP MLT Maintenance Menu.
SIP MLT Maintenance Menu

There is a maintenance menu in the SIP MLT. To access it, press the "Help" button for 2 seconds. This menu can only be accessed after the display shows "Connecting..." or the extension is operational. It is possible to use this menu during a call. The menu options are as follows: -
44
SV8100
1. 2. 3. QoS System Information Ping
The QoS option gives information about lost packets, codec in use and the payload size. The System Information option gives various information about the network settings, SIP Settings, Audio & Visual Settings, Maintenance Settings and Terminal Information. The Ping option gives the ability to ping another IP address to check connectivity across the network. Note: The lost packet count can only be updated when the SIP MLT has connectivity with the SV8100, if connection is lost during the call the display will not be updated.
Peer to Peer
By default if two IP extensions are on an internal call together, the RTP will be sent directly between the two endpoints. This reduces the DSP consumption, reduces delay on the VoIP packets and increases voice quality on the call. There may be instances where this operation is not supported. May be the customers network does not allow it. If this is the case it is possible to disable Peer to Peer for SIP MLT extensions. Use the DT700 Peer to Peer option in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup (PRG10-26-04) Be aware that this option controls Peer to Peer for all SIP MLT extensions registered on that system.
License
The SV8100 requires licensing to allow the registration of SIP MLT handsets. One license is required for each registration to the SV8100. If no license is available, the display of the SIP MLT shows:
Up to 512 SIP MLT licenses can be added. License Code: BE107585
SIP MLT Models

There are several types of SIP MLT phone available for the SV8100. The system programming is the same regardless of the IP phone model. The following SIP MLT models are available:
ITL-2E-1. This IP economy non-display Multiline Terminal has two programmable line keys. It does not support headset working
SV8100
ITL-6E-1. ITL-8LD-1. ITL-12D-1. ITL-12PA-1. ITL-24D-1. ITL-32D-1. ITL-320C-1. This This This This This This This
45
IP economy Mutiline Terminal has six line keys with a display. It does not support headset working. IP value Multiline Terminal has eight line keys with DESI-less display and a normal display. IP value Multiline Terminal has 12 line keys with display. IP value Multiline Terminal with Analogue Power Failure adapter has 12 line keys with display. IP value Multiline Terminal has 24 line keys with display. IP value Multiline Terminal has 32 line keys (24 line keys plus an eight line key LK Unit) with display. IP sophisticated Multiline Terminal features a large colour touch panel LCD.
SIP MLT Features

DT700 Encryption
It is possible to encrypt the signalling data and the speech data (RTP) between one or more DT700 extensions and the IPL card. 128 bit AES encryption technique is used. If NetLink is in operation, the DT700 must be registered to the Primary system to be able to use the Encryption feature. It is possible to set only the signalling to be encrypted or the signalling and the RTP together, it is not possible to encrypt only the RTP without encrypting the signalling. If the call is between two DT700's with Peer to Peer enabled and both extensions are set to use encryption, the signalling and RTP will be encrypted regardless of the settings in system programming. Only DT700 extensions can use the encryption feature, it is not supported for Standard SIP extensions or any networking protocol. If the speech is encrypted (sRTP) the number of available DSPs on the IPL card may be reduced (depending on the codec used). See the IPL DSP Information page for more information. Encryption - System Programming Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Additional Features/DT700 Encryption (PRG10-46) Enable Encryption Mode System reboot required Enter a password in One Time Password To enable RTP Encryption, enable SRTP Mode (PRG84-27-03)
Encryption - Handset Programming On each DT700 Enter configuration menu (menu 0) followed by the password. Option 2. SIP Settings. Option 7. Encryption. Option 1. Authentication Mode = Enable Option 2. One Time Password = (As entry in PRG10-46-09) - Save The handset will reboot and attempt to authenticate with the SV8100, if it is successful it will show 'Authentication Accepted'. The handset will reboot again and show the normal display information once it has registered. If RTP encryption is enabled, any call that has encrypted RTP will be indicated with the symbol of a key in the display during the call.
Encryption CAUTION The system and the handset use the one time password to create an authentication key. The authentication key is then used to encrypt the signalling and RTP packets. In the unlikely event that this password or key is compromised it may be required to delete the key and create a new one. The key can be deleted by using PRG90-45-01. BEWARE, using this comand will remove the authentication key used by every IP extension that has encryption enabled. Each handset will then require reprogramming. This programming command is only available through handset programming. If encryption is in use, it may no longer be possible to troubleshoot any problems using network monitoring software e.g. Wireshark. If you need to use Wireshark to diagnose a problem it is recommended to disable encryption. If NetLink is in operation, the DT700 must be registered to the Primary system to be able to use the Encryption feature.
SV8100 Requirements The following information provides requirements for Encryption.
46
SV8100
Main Software Encryption is supported with V2.00 or higher release of the SV8100. Handset Firmware Encryption is supported with V2.2.1.0 handset firmware or later. Hardware The SV8100 requires the following hardware: CD-CP00 (V2.00 or higher) PZ-32IPL, PZ-64IPL, PZ-128IPL License The system must be licensed for this feature with a BE108415 (License 0030). The system must be licensed for DT700 ITL Terminals.
NAPT
The NAPT (Network Address Port Translation) feature gives the SV8100 the ability to traverse its own subnet. With NAPT used in the SV8100, the network administrator can place the CPU and the IPL in the customers LAN while still making it accessible to DT700 users outside the local LAN (e.g. via the internet). This means a VPN is no longer required to place a DT700 on a remote network. (This feature is not available for 3rd Party SIP devices (standard SIP)) A network configuration diagram is shown below
Depending on their locations, terminals are classified into the following four categories: LAN terminals Terminals installed on the LAN where the main device is installed. WAN terminals Terminals directly installed in the global address space. NAT terminals
SV8100
Terminals connected to the main device through a NAT router. LAN terminal via local router Terminals connected to the main device via a local router (non NAT) DT700 NAPT System Programming Additional programming for DT700 operation is still required.
47
Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup/DT700 Additional Features/DT700 NAT/DT700 NAT Setup/ NAT Mode. (PRG10-46-14) = On Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup/DT700 Additional Features/DT700 NAT/DT700 NAT Setup/ NAPT Router IP Address. (PRG10-12-07) = Static public IP address (system side). Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup/DT700 Additional Features/DT700 NAT/DT700 NAT Remote Network Addresses. (PRG10-58) = Network address and Subnet mask of DT700 LAN terminal via local router (if connected see below for further information).
Port forwarding system side On the router connected to the SV8100 network, forward port UDP/5080 and UDP/5081 to the SV8100 IPLA IP address. Also forward the RTP ports (UDP/10020 - 10051) to the first SV8100 VoIP gateway address. More entries may be required depending on the configuration and if NetLink is used. Static or Dynamic NAT There are two options available when programming the handset, Static NAT or Dynamic NAT. The choice depends on the capabilities of the router on the handset network. If UDP Session Detection is supported by the router then Dynamic NAT should be possible. It is recommended, where possible, to use Dynamic NAT.
Dynamic NAT The router on the handset side must support dynamic address and port mapping for outgoing and incoming traffic. Enter the Config Menu of the handset and Enable DHCP Mode in Network Settings/DHCP Mode. This should give an IP Address, Subnet Mask and Default Gateway to the DT700. Be aware, when using NAT the handset does not use the normal SIP Server Settings. There is a new area for NAT addresses. In SIP Settings/NAT Traversal/NAT Traversal Mode - set to Dynamic In SIP Settings/NAT Traversal/WAN Settings/WAN Mate IP Address - Enter the public IP address of the SV8100 Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup/DT700 Additional Features/DT700 NAT/DT700 NAT Setup/NAPT Router IP Address. (PRG10-12-07) In SIP Settings/NAT Traversal/WAN Settings/WAN Mate Port - Set to 5080. In SIP Settings/NAT Traversal/WAN Settings/WAN Self IP Address Leave this blank, the phone will get this address dynamically. Exit and save, the handset will now try and register to the SV8100. If it fails it may be because the router does not support dynamic address and port mapping. If this is the case Static NAT may have to be used.
Static NAT The handset should have a static IP address or if using DHCP then reserve an address using its MAC address (if supported by the DHCP server). Be aware, when using NAT the handset does not use the normal SIP Server settings. There is a new area for NAT addresses. Set IP address, subnet mask and default gateway as usual in Config Menu/Network Settings. In SIP Settings/NAT Traversal/NAT Traversal mode - set to Static In SIP Settings/NAT Traversal/WAN Settings/WAN Mate IP Address - Enter the public IP address of the SV8100 Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup/DT700 Additional Features/DT700 NAT/DT700 NAT Setup/NAPT Router IP Address. (PRG10-12-07) In SIP Settings/NAT Traversal/WAN Settings/WAN Mate Port - Set to 5080. In SIP Settings/NAT Traversal/WAN Settings/WAN Self IP Address - Enter the public IP address of the router on the network where the handset belongs.
Port forwarding handset side On the router connected to the handset network, forward port UDP/5060 to the IP address of the handset. Also forward port UDP/3462 to the IP address of the handset. If you have multiple NAT handsets on the same remote network you will need to change the port numbers on each handset so that
48
SV8100
they are unique on the network. The first handset will be ok with default port numbers. You can change the port numbers in Network Settings/Advanced Settings/Self Port Settings The SIP Port can increment by one, recommend 5061, 5062 etc. The RTP ports must be an even number, recommend 3464, 3466 etc. The relevant port forwarding will then be required on the router on the handset network.
NetLink Considerations When using NAPT in conjuction with NetLink the RTP/RTCP ports on the Primary and Secondary systems must be unique (see table below for an example). This is to facilitate the correct port forwarding in the NAT router when the RTP should be forwarded to the Secondary VoIPU gateway rather than the Primary. Index 1 2 3 4 5 6 PRG 10-12-03 10-12-09 10-12-10 84-26-01 84-26-02 84-26-03 Primary 172.16.0.254 172.16.0.10 255.255.0.0 172.16.0.20 10020 10021 Secondary 172.16.0.254 172.16.10.10 255.255.0.0 172.16.10.20 20020 20021 Remarks LAN IP address of NAT router IP address of CPU Subnet mask of CPU IP address of VoIPDB RTP port number of VoIPDB RTCP port number of VoIPDB
In this example there would be the following port forwarding rules in the NAT router connected to the SV8100: UDP/5080 -> 172.16.0.10 UDP/5081 -> 172.16.0.10 UDP/10020 10051 -> 172.16.0.20 UDP/20020 20051 -> 172.16.10.20 (DT700 signalling to SV8100) (DT700 signalling to SV8100) (DT700 RTP/RTCP to Primary SV8100) (DT700 RTP/RTCP to Secondary SV8100)
DT700 Terminal via Local Router If DT700 NAPT is programmed on an SV8100 it needs to know if there are any DT700 extensions connected via a local (non NAT) router or any remote DT700 which does not require passing through the NAT process. The network address of these extensions must be entered in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup/DT700 Additional Features/DT700 NAT/ DT700 NAT Exempt Networks. (PRG10-58)
SV8100
49
An example of a DT700 via Local Router is if the SV8100 IPLA card is in VLAN 10 and a DT700 extension is in VLAN 20. In this case the network address of VLAN 20 would need to be programmed on the SV8100. These requirements also apply for a local routed network, not just VLAN operation. These requirements do not apply for extensions connected via VPNs
SV8100 Requirements The following information provides requirements for NAPT. Main Software NAPT is supported with V3.00 or higher release of the SV8100. Handset Firmware NAPT is supported with V3.0.0.0 handset firmware or later. Hardware The SV8100 requires the following hardware: CD-CP00 (V3.00 or higher) PZ-32IPL, PZ-64IPL, PZ-128IPL Capacity 512 Extensions (as allowed by hardware and licensing). License The system must be licensed for this feature with a BE108834 (License 0031). The system must be licensed for DT700 ITL Terminals. Conditions License Exceeded will display on the DT700 terminal when trying to register a NAT phone, if the feature is not licensed. The NAPT feature requires CPU software V3.00 or above. Terminals using NAPT must be at firmware V3.0.0.0 or above. The NAT router on the SV8100 side must have a static WAN IP address, UPNP is not supported. Softphone (SP310) is not supported. Wireless phone (MH240) is not supported. If NAT enabled phones become unresponsive after being idle, the timer in Programs 84-23-01 and 84-23-02 may need to be changed to a shorter interval. It is necessary to set Program 10-46-14 to OFF when the IPLA 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 for terminals connected via a local router. NAPT can be used for SIP trunks and terminals on the same system. Multicast RTP packets can not be set to an extension using the NAPT feature (ExMOH, BGM, and Room Monitor). Restrictions Static NAT A contract for static IP addresses is required for a WAN-side IP address specified for the NAT router on the terminal side. 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. The table must be set up so that that the NAT router only converts IP addresses, not port numbers. IP addresses for terminals have to be specified statically. When allocating an IP address using DHCP, the IP address might change. NEC does not guarantee proper operation in this case. If installing multiple terminals in the domain of the NAT router on the terminal side, the SIP port number and RTP/RTCP port number 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.) Restrictions 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 SIP port number and RTP/RTCP port number 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.)
SIP MLT Time Zone Offset

If a SIP MLT is located in a different time zone to the system it is registered to the time and date may be incorrect. This can be resolved by offsetting the time and date on each handset compared to the system. Use the Time Zone(hour) and Time
50
SV8100
Zone(minute) options in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Extension Setup. (PRG15-05-41/42). The default hour setting is 12, this means 0 hours offset (equal to the system). The default minute setting is 60, this means 0 minutes offset (equal to the system). Possible entries are 0 to 24 hours (-12 to +12 hours) and 0 to 120 minutes (-60 to +60 minutes.
Unicast Paging
Previous to system software V3.0, internal paging to DT700 extensions could only be done uning IP Multicast. From system software V3.0 onwards there is a choice between IP Multicast, Unicast or Automatic on a per extension basis. This is of benefit when the DT700 extensions reside on a remote network where the routers do not support IP Multicast relay. Previous operation (e.g. V2.0)
In the above scenario the Paging speech would not be presented to the extension in Subnet 2 if the router does not support Multicast relay.
New operation 1 (e.g. V3.0)
In the above example two extensions are set to use Multicast and two are set to use Unicast. The two extensions set to use Multicast will work because they belong to the same network as the IPL. The two extensions set to Unicast will also work as the router does not need to support Multicast relay for the speech to be presented to the extension on Subnet 2.
SV8100
51
New operation 2 (e.g.V3.0)
In the above example all extensions have the Paging Mode is set to Automatic. The system will reference the Subnet of the IPLA and the Subnet of the extensions in the Paging Group. If they belong to the same network then IP Multicast will be used. If they are in different networks then Unicast will be used and the router does not need to support Multicast relay.
SV8100 Programming Use the Paging Protocol Mode option in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Extension Setup. (PRG1505-38) Set to Multicast, Unicast or Auto on a per extension basis.
Related programming PRG10-19 IPL DSP Resource Selection. Three new options, 6 Common without Unicast Paging, 7 Multicast Paging, 8 Unicast Paging.
Limitations One DSP is required for each extension using Unicast Paging Mode where as only one DSP is required for all extensions using Multicast Paging Mode. Unicast Paging is not executed to an extension which can not get access to a DSP. Unicast can only be used for the Paging feature. Other Multicast features are not affected (MOH, Room Monitor, BGM). MH240 is not supported for Unicast Paging Mode.
Security Button
Above the display of a DT730 or DT750 SIP MLT handset there is a button marked Security. This allows the handset to be locked as and when the user requires it. The Security button can be enabled or disabled on a per extension basis using the Protection Service option in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional features/DT700 Security Button. (PRG15-05-24)
To enable the Security feature on the handset: Press the Security button The display shows Security Lock? (for about 5 seconds) Press the OK softkey within this time The display changes and scrolls the screen with the text Security lock, the red light next to the Security button is also illuminated.
52
SV8100
To disable the Security feature on the handset: Press any button on the handset The display changes and shows Security lock will be released. Please input a password. Enter the password (default 0000) and press the OK softkey. The phone is now unlocked. The password can be changed on a per handset basis using the following steps: Press Menu Dial 5 1 4 Enter the old password (default 0000) Press the Set softkey Enter the new password Press the Set softkey Enter the new password again Press the OK softkey The display says Complete Press the OK softkey then Back several times until the idle screen is displayed.
Security Lock Override It is possible to enter three pre-programmed numbers into a SIP MLT so that if the Security Lock is enabled the phone can still be used to call emergency numbers. If a trunk must be accessed to call the emergency number, the trunk access digit must be set as part of the emergency number programmed into the handset. To call the emergency numbers the handset must be used, pressing the Speaker key will not allow the emergency numbers to be dialled. Upto 32 digits can be entered in each of the Emergency Dial locations. e.g. If the emergency number to dial is 112 via a trunk with a trunk access code of 9, the number programmed into the handset must be 9112. Lift the handset and dial 9112, the call will proceed. If the trunk access code is 0, the number programmed into the handset must be 0112. Lift the handset and dial 0112, the call will proceed. Once the Emercency number has been called the Security Lock is switched off until it is enabled again by the user.
Programming the Emergency Numbers On the SIP MLT Press Menu 0 User Name - ADMIN Password - 6633222 OK Dial 6 5 Choose the Emergency Dial entry (1, 2 or 3) Enter the dial string for the emergency number (including trunk access digit) Press the OK softkey Repeat this procedure for the remaining two entries (if required) Press the Exit softkey twice Press the Save softkey The phone will restart with the new settings.
LLDP
Description Link Layer Discovery Protocol (LLDP) is used to transmit and receive information about neighboring network devices and IP telephones. Some SIP MLT settings can be automatically specified according to the LLDP data received from the network switch. LLDP operates at layer 2 so the IP address of the terminal does not need to be specified until after the LLDP operation has completed. LLDP uses IP Multicast to transmit/receive information so this must be taken into account on the customers network.
SV8100
LLDP Standards The supported standards are: IEEE802.1AB:2005 ANSI/TIA-1057 LLDP-MED (LLDP for media endpoint discovery). The device class is Endpoint Class III
53
Requirements The SIP MLT must have firmware V4.0.0.0 or later to use the LLDP feature. The SV8100 should have V4.0 software or later to use the LLDP feature. The SIP MLT must be factory defaulted after the firmware upgrade to use the LLDP feature. The network switch must support LLDP and be configured accordingly. The network switch configuration varies depending upon the manufacturer and model. Consult the network administrator/ maintainer for further information. If the LLDP information becomes unavailable from the network the terminal will continue to operate unless it is rebooted. It will then use the settings from the terminals own configuration rather than the LLDP settings.
SIP MLT LLDP Menu Default settings indicated in red Press Menu 0 Enter the User Name and Password 1. Network Settings 6. Advanced Settings 6. LLDP Settings o 1. LLDP Mode (Enable/Disable) (Enable) o 2. Auto Setting Mode (Enable/Disable) (Enable) o 3. RX Waiting Time (1 60 Seconds) (15 Seconds) o 4. Transmit Interval (5 32768 Seconds) (30 Seconds) o 5. Hold Multiplier (2 10) (4) o 6. Fast Start Count (1 10) (3) o 7. Transparent Mode (Enable/Disable) (Enable) o 8. Asset ID (Input an Asset ID) (-)
Note: Non-display IP Terminals should be configured using the Web interface or Auto Config. All LLDP configuration items except Asset ID are available via Auto Config in IP Phone Manager.
LLDP information sent from SIP MLT Example: Chassis id: Port id: Port Description: System Name: System Description: Time remaining: System Capabilities: Enabled Capabilities: Auto Negotiation: Physical media capabilities:
172.16.0.100 (Terminal IP address) 0060.b9xx.xxxx (Terminal MAC address) LAN Port NEC IP Phone DT700 Series xx seconds Bridge, Telephone Bridge, Telephone supported, enabled 100base-TX (Full Duplex) 100base-TX (Half Duplex) 10base-T (Full Duplex) 10base-T (Half Duplex) 10 H/W revision: 9.1.3.4 F/W revision: 4.0.0.0 S/W revision: -
Media Attachment Unit type: MED Information:
Serial number: Manufacturer: Model:
NEC DT700 Series
54
Asset id: ASSET001
SV8100
(Assigned in handset config) LLDP information sent from Network Switch Example (switch type and configuration dependant): Chassis Subtype 18:EF:63:xx:xx:xx Port Subtype Fa 0/2 Time to Live xx Seconds System Name Lab Switch System Description Cisco IOS V12.2 (55) SE Port Description Fast Ethernet 0/2 Capabilities Bridge, Router Management Address 172.16.255.254 Media Capabilities LLDP-MED Network Policy Location Identification Extended Power Inventory Hardware Revision WS-C3560-8PC Software Revision 12.2(55) SE Manufacturer Name Cisco Systems Model Name WS-C3560-8PC Network Policy (Voice) (VLAN ID, CoS, DSCP etc.) Network Policy (Voice Signal) (VLAN ID, CoS, DSCP etc.) Extended Power Via MDI Power priority Location ID Road, City, Post Code, Country etc. Port VLAN ID VLAN ID MAC/PHY Configuration/Status Speed, Duplex
SIP MLT Maintenance Menu Received LLDP information can be viewed in the Maintenance Menu: Press and hold the Help key for 2 seconds 2. System Information 6. LLDP Receive Information o LLDP Receive Data (Valid/Invalid) o Manufacturer Name o Model Name o System Name o System Description o Chassis ID o Port ID o Port Description o PHY Auto-nego status o Speed & Duplex o Unknown Flag (Voice) o VLAN Tag Flag (Voice) o VLAN ID (Voice) o L2 Priority (Voice) o DSCP Value (Voice) o Unknown Flag (VoiceSignal) o VLAN Tag Flag (VoiceSignal) o VLAN ID (VoiceSignal) o L2 Priority (VoiceSignal) o DSCP Value (VoiceSignal) o Location ID (Civic) o Location ID (ECS ELIN) o Asset ID If the information received by LLDP changes whilst viewing this menu it will not refresh automatically. Exit and re-enter the Maintenance Menu to confirm the information is up to date.
SV8100 Spare/Backup IP
55
Description This facility allows the SIP MLT handset to use alternate network information which is used in the event of the DHCP server becoming unavailable. There are two options for the alternate information: 1. Spare IP. This is where each terminal is preconfigured with static network information which is used in case the DHCP server is unavailable. 2. Backup IP. This is where the terminal saves the network information that it receives from the DHCP server and uses it when the DHCP server is unavailable. If Spare IP is used the network information that can be preconfigured is: IP Address Default Gateway Subnet Mask DNS Address 2nd SIP Server Address 3rd SIP Server Address 4th SIP Server Address 2nd SIP Server Port 3rd SIP Server Port 4th SIP Server Port The above settings can be found in the handset Config Menu: 1. Network Settings 6. Advanced Settings 7. Spare IP Settings If Backup IP is used the following information is saved to the handset flash memory: IP Address Default Gateway Subnet Mask DNS Address The following information needs to be preconfigured (if required) 2nd SIP Server Address 3rd SIP Server Address 4th SIP Server Address 2nd SIP Server Port 3rd SIP Server Port 4th SIP Server Port If Spare IP or Backup IP is being used by the handset because the DHCP server is unavailable the usual SIP server addresses programmed in to the handset are not used. Instead it uses the settings in: 2. Network Settings 6. Advanced Settings 7. Spare IP Settings 3. SIP Settings At least the 2nd SIP Server Address and the 2nd SIP Server Port number needs to be configured if Spare IP or Backup IP is to be utilised.
SV8100 Requirements Main Software Spare/Backup IP is supported on any version of SV8100 software. Firmware Spare/Backup IP is supported on SIP MLT firmware V4.0.0.0 onwards
56
SV8100
Conditions/Comments If using a spare or backup IP address, the same address might be used by a different device making it impossible to communicate with the SV8100. If using a spare or backup IP address, Auto configuration cannot be executed. If the Auto Configuration mode is enabled, the spare or backup IP address operating mode setting are initialised to the defaults. The backup IP service data previously acquired from the DHCP server is retained. The backup data previously acquired from the DHCP server is deleted when the configuration data clearing (initialisation of the terminal setting data) is executed. If using a spare or backup IP address, services other than the telephone function of programs such as XML applications might not work correctly. The backup data is also backed up or restored when the configuration data is backed up or restored. If the alternate IP address mode is backup IP data is saved to flash memory when the IP address is acquired from the DHCP server at the specified time. If the IP telephone is turned off while saving to flash memory, it might become impossible to start up the phone.
Configuration Enter the handset Configuration Menu by pressing Menu 0 and enter the Username and Password. Press 1. Network Settings Press 6. Advanced Settings Press 7. Spare IP Settings Press 1. Spare/Backup IP Mode o Press 1. Disable o Press 2. Spare IP o Press 3. Backup IP o Press OK If using Spare IP Press 2. Network Settings o Press 1. IP Address and enter the static Spare IP address o Press OK o Press 2. Default Gateway and enter the IP Address of the Default Gateway o Press OK o Press 3.
SIP MLT Quality of Service

The SIP MLT handsets support Layer 2 (IEEE 802.1p/Q) or Layer 3 Quality of Service. The programmable items are: VLAN tag for handset VLAN Priority for handset VLAN tag for PC port VLAN Priority for PC port ToS setting for RTP ToS setting for SIP signalling
VLAN Settings
It is possible for the SIP MLT to have specific VLAN and Priority settings. It is also possible for the PC uplink connection to have different VLAN and Priority settings. The VLAN and Priority settings must be made by programming each individual handset. Setting VLAN Values for the SIP MLT 1. 2. 3. 4. 5. 6. 7. 8. Press Menu, then 0 (Config) to enter the terminal program mode. At the Login screen, enter the user name (default = ADMIN) and password (default = 6633222) and press the OK softkey. Press 1 for Network Settings. Press 6 for Advanced Settings. Press 1 for LAN Port Settings. Press 2 for VLAN Mode. Press 2 to Enable and press the OK softkey. Press 3 for VLAN ID.
SV8100
9. 10. 11. 12. 13. 14. Enter the required VLAN information and press the OK softkey. Press 4 for VLAN Priority. Enter the require VLAN Priority information and press the OK softkey. Press the Exit softkey three times. Press the Save softkey. The handset will reboot and reconnect to the SV8100.
57
Setting VLAN Values for the PC Port 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Press Menu, then 0 (Config) to enter the terminal program mode. At the Login screen, enter the user name (default = ADMIN) and password (default = 6633222) and press the OK softkey. Press 1 for Network Settings. Press 6 for Advanced Settings. Press 2 for PC Port Settings. Press 2 for Port VLAN Mode. Press 2 to Enable and press the OK softkey. Press 3 for Port VLAN ID. Enter the required VLAN information and press the OK softkey. Press 4 for Port VLAN Priority. Enter the require VLAN Priority information and press the OK softkey. Press the Exit softkey three times. Press the Save softkey. The handset will reboot and reconnect to the SV8100.
ToS Settings
It is possible for the SIP MLT to have specific Layer 3 QoS (ToS) values. It is possible to set the SIP signalling and RTP ToS values independently allowing for different values for each. There are two ways to set the ToS values in a SIP MLT handset: By programming each handset through its menu. By programming the SV8100 which the SIP MLT then reads on registration. In both cases the QoS value must be set by using a hexadecimal value. Setting ToS Values using the SIP MLT Menu 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Press Menu, then 0 (Config) to enter the terminal program mode. At the Login screen, enter the user name (default = ADMIN) and password (default = 6633222) and press the OK softkey. Press 1 for Network Settings. Press 6 for Advanced Settings. Press 4 for Type Of Service. Press 1 for RTP. Enter the hexadecimal value for the required ToS and press the OK softkey. Press 2 for SIP. Enter the hexadecimal value for the required ToS and press the OK softkey. Press the Exit softkey three times. Press the Save softkey. The handset will reboot and reconnect to the SV8100.
Setting ToS Values using the SV8100 Programming There are two items in system programming, one for SIP signalling and one for RTP. For SIP signalling use the Type of Service option in: Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup. (PRG84-23-06) For RTP use the Media ToS item in: Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup. (PRG84-23-13) When the SIP MLT registers to the SV8100 it will read these ToS values and use them from that point onwards. Using this method every SIP MLT registered to the SV8100 will have the same ToS values.
Considerations
If the SIP MLT is set to mark the frames/packets with QoS information this is only applied to the information being sent from the SIP MLT. The SV8100 must also be set to mark the frames/packets that it sends out to the SIP MLT.
58
SV8100
For any type of QoS to function correctly the network that the devices are connected to must support the same protocol that the devices are using. The network must also be set up correctly to allow priority for this traffic over other traffic on the network. This must be done throughout the entire network. Liaise with the network administrator to ensure this is implemented correctly.
SIP MLT Adapters

The following table shows the compatibility between adapters and SIP MLT terminals.
ADA-L APR-L ILPA PSA-L BCH-L BHA-L GBA-L
Conversation recording adapter Analogue extenson adapter In Line Power Adapter (for adding PoE to the Ethernet connecton) Power fail adapter Bluetooth Cordless Handset interface Bluetooth Hub Adapter Gigabit Adapter
Gigabit Adapter
The Gigabit Adapter (GBA-L) is a device that fits to the base of a SIP MLT to provide a Gigabit Ethernet connection to the desktop along with an Ethernet connection for the handset when only one Gigabit connection is available from the customers network. Please refer to the SV8100 Hardware manual for installation instructions. The SIP MLT can not be wall mounted with a Gigabit adapter fitted.
LED Display The following provides a list of each LED and associated operation and status indications.
SV8100
59
Power supply The Gigabit adapter can be powered by PoE (802.3af) or by 27v mains adapter. When using PoE to power the Gigabit adapter and the SIP MLT, it is possible that the PoE switch may not be able to supply enough power. In this case it is recommended that the 27v AC adapter is used instead of PoE. See the table below to indicate when the AC adapter is recommended. TEL Type -> ITL-2E ITL-6DE ITL-12D ITL-24D ITL-32D ITL-8LD ITL-320
Adapter Type No Adapter APR ADA PSA 8LK 16LK BCH BHA No AC N/A N/A N/A N/A N/A N/A N/A No AC N/A N/A N/A N/A N/A N/A N/A No AC AC AC AC AC AC AC AC No AC AC AC AC AC AC AC AC AC AC AC N/A N/A N/A N/A AC AC AC AC N/A N/A N/A N/A AC AC AC AC N/A N/A N/A AC AC
AC = 27v AC mains adapter is recommended. No AC = 802.3af PoE is sufficient. N/A = This particular combination is not available with the specified handset.
60
SV8100
SIP MLT PSA-L Unit

The PSA-L UNIT (Power Save Adapter), an optional adapter for the DT700 range terminals (SIP MLT's), is used with SIP MLT's to make or receive a call using the Public Switched Telephone Network (PSTN) when a call cannot be made or received using the Local Area Network (LAN). When a power failure occurs, the SIP MLT is automatically switched to the PSTN. When power is restored, the SIP MLT restarts and connects to the network unless a conversation is in progress on PSTN. The PSTN call must be completed by going on-hook before the connection to the LAN is restored. Before installing or removing the PSA-L adapter, remove the line cord, LAN cable, and AC adapter from the outlet. For further information about instalation of the PSA-L Unit, see the hardware manual.
SV8100
61
62
SV8100
SIP MLT Key Kit

The SIP MLT (DT700) Series offers a line up of modular telephones. This modular design allows the telephones to be upgraded and customized. Optional LCD panels, keypads, handset cradles, face plates and coloured side panels can easily be snapped on and off (except value models).
SV8100
63
64
SV8100
Configuring the IP Telephone for the Correct Number of Line Keys

1. Press Menu, then 0 (Config) to enter the terminal program mode. 2. At the Login screen, enter the user name (default = ADMIN) and password (default = 6633222) and press the OK Softkey. 3. Press 3 for Maintenance Setting. 4. Press 4 for Adjust. 5. Press 2 for KeyKit Type. 6. Press the Up/Down key to select the Key Kit.
7. Press Softkey 4 for Next. 8. Press the Up/Down key to select the Line Key kit.
SV8100
65
9. Press Softkey 4 for OK to complete. 10. Continue pressing Softkey 4 to exit (Exit-Exit-Save). The terminal resets automatically.
SIP MLT IP Phone Manager

IP phone manager is a maintenance application for SIP MLT extensions. It can be used for several functions such as initiating file downloads, creating configs, changing settings, backing up configs etc.
INSTALLATION
Follow these steps for installation of the IP Phone Manager. 1. Double Click Setup.exe icon to initiate the installation. 2. After installation, a Shortcut is placed on your PC Desktop. This icon can be used to run the IP Phone Manager application. 3. At the elect Interface Pop Up, select the active Network Interface Card that your PC is currently using.
4.
IP Phone Manager now opens on your PC.
66
SV8100
SEARCHING FOR TERMINALS

There are three methods to search for active terminals on your network.
1. Search The IP Phone manager sends a broadcast over the network in search of terminals. Active terminals respond to this broadcast with terminal information. There are three settings that change the Search Frequency and timing of the IP Phone Manager broadcast. 2. Direct When an IP Address of the terminal is known, it is possible to search for it independently. This is commonly used to for a quick search of a specific terminal or a terminal that may be in a different network or subnet.
SV8100
67
3. Import PBX System configuration applications may export a list of registered terminals in a CSV file format. This CSV file can be imported to the IP Phone Manager Application. This import can now be used to Search and Connect the registered terminals indicated in the imported file. The IP Phone Manager allows an active list of terminals to be exported in CSV format for later import or to save a current database for examination.
Terminal Connection
After terminals are discovered by the IP Phone Manger Search functionality, they must be connected to before any action can take place. For terminals that need maintenance or further information communicated between them, select the check box and press Connect. When the Status Field indicates OK, the terminal is in active communication with IP Phone Manager.
68
SV8100
IP Phone Manager Commands
1. 2.
SwitchPortCtrl Switch Port Control can enable or disable the PC Port on the connected IP Terminal(s). Reset This function resets the terminal(s) connected to the IP Phone Manager. Two options for resetting the Connected terminal(s) are available: Soft Reset Application layer of the terminal Hard Reset Full hardware reset of the terminal SecurityLock This feature can lock or unlock the Connected Terminal(s), and has two modes: Enable allows the user to change the status of the terminal security. o All Clear Returns the terminal password to default value o Unlock One-time security release on the terminal o Lock Locks the Connected terminal(s) Disable disables the SecurityLock feature from being set from the terminal.
3.
SV8100
4. Data Reset Data Reset erases the configuration stored in terminal memory. Three terminal memory locations can be reset. IP Phone Settings Terminal Configuration Data that is set in terminal programming under the Config menu tree Personal Settings Personal Data Data that the user has personally set (holding tone, ring tone, and telephone book) o Factory Value resets all three data settings
69
5.
Download This feature downloads various file types via a FTP/TFTP server. Select the server type to be used for downloads and the parameters that are required (IP Address of server, authentication name and passwords). Download Option: Use the Download Option Field to select the Terminal File type and enter a File name as required. Use the Simultaneous Downloads to select the quantity of terminals that access and attempt downloads at the same time. All remaining terminals are put into queue for the next available position. Some server applications can handle only limited simultaneous connections consult your server documentation for any limitations. IP Phone Information IP Phone Information is a search tool to help organize a large database of terminals into more manageable groupings. Terminals can be grouped in categories by Type, Hardware Version, or Firmware Version.
6.
Backup & Restore Backup and Restore functionality allows terminal data to be sent to or received from a network server. Data Backup is used to copy the current terminal data and configuration to an FTP/TFTP server for archiving. File names for the restored data can be saved as the terminal MAC address, IP Address or Extension number for easy user management. Data Restore is used to copy a preexisting archived file to a terminal to restore its previous settings. Simultaneous Download can be selected according to the limitations of the FTP/TFTP server that you have selected to use.
7.
Error Log Error Log information is a useful tool that can be used by developers for troubleshooting. Terminal log information can backup an FTP/TFTP server and is saved under the terminal MAC Address, IP Address or Extension number of the selected terminal(s). Simultaneous Download can be selected according to the limitations of the FTP/ TFTP server that you have selected to use.
Config Application
70
SV8100
1.
Web Config The IP terminal has an HTTP server for web programming. Selecting this button starts a session with Internet Explorer (or the default web browser installed on the local PC) for all the connected and selected terminals. You have one browser session started for every selected terminal this feature is used on an individual terminal. Auto Config The Auto Config button is a direct link to the Auto Configuration Tool. Auto Configuration Tool is used to build a master terminal configuration file for terminal initial setup Plug and Play purposes.
2.
Toolbar Features
1. 2. Search Sets the frequency and timing that the IP Phone Manager attempts to search and discover IP terminals on the network. Port Set Port Set allows the customization for Port Numbers that the IP Phone Manager Application and IP Terminals use for communication. Default IP Phone = 3530 IP Phone Manager = 20111 Interface Select or change the active PC NIC card that IP Phone Manager needs to use. ListCtrl List Control is used to select and organize the fields to be viewed in the active IP Phone Manager home layout screen.
3. 4.
Select 5. 6. 7. 8.
Help Displays Version information of IP Phone Manager. Select ALL Selects ALL discovered terminals. Clear ALL Unselects all preselected terminals on the home screen. Quit Terminates all communication between IP Phone Manager and closes the application.
Firmware Upgrade
Below is an example of how to use IP Phone Manager to upgrade the firmware of SIP MLTs Conditions 1. The terminals must be operational. 2. The IPPhoneManager must be located in the same network segment the terminals are in (only if using the Search function). 3. Running FTP/TFTP Server containing correct firmware files. Procedure: 1. Start up the IPPhoneManager 2. Press Search in Registration (Import or Direct may also be used)
SV8100
3. 4. 5. 6. 7. 8. 9. 10. Press Select ALL (or individually select the phones to be upgraded) Press Connect Select Download in Command Press Execute Enter information in FTP/TFTP Server Select Boot&Program in Download File Type Press Select All Press Download.
71
The handsets will now download and save the firmware then reboot and reconnect to the SV8100.
SIP MLT Firmware Upgrade

From time to time it may be necessary to upgrade the firmware on the SIP MLT handsets, possibly to introduce new features. There are several ways in which the upgrade can be performed, these are listed below. Using IP Phone Manager (TFTP/FTP server required) Using the SIP MLT menu (TFTP/FTP server required) Automatic upgrade whilst the phone is registering to the SV8100 (SV8100 programming and TFTP/FTP server required) To show the current firmware version of a SIP MLT on its display use the following steps: 1. Press and hold the Help key for two seconds. 2. Press 2 for System Information. 3. Press 5 for Terminal Information. The Hardware Version is displayed at this point. 4. Press the Down softkey several times until Firmware Version is displayed. 5. To exit the menu press the Exit key or press the Prev softkey twice then the Exit softkey. For instructions on using the IP Phone Manager please refer to the IP Phone Manager page.
Upgrade using the SIP MLT Menu

Before following the upgrade procedure, the firmware files must be loaded onto a TFTP/FTP server. There are three firmware files depending on the type of handset being upgraded: itlisipe.tgz (for use with ITL-2E/6E handsets) itlisipv.tgz (for use with ITL-8/12/24/32D handsets) itlisips.tgz (for use with ITL-320C handsets) Each type of handset will request the correct file name by default. This procedure must be performed on each handset that requires upgrading. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. Press Menu, then 0 (Config) to enter the terminal program mode. At the Login screen, enter the user name (default = ADMIN) and password (default = 6633222) and press the OK Softkey. Press 3 for Maintenance Setting. Press 1 for Download Menu. Press 2 for Download Address and enter the IP address of the TFTP/FTP server Press the OK softkey. Press 3 for Protocol and choose either TFTP or FTP depending on what type of server you have available. Press the OK softkey. If using an FTP server press 4 for FTP Settings then enter the FTP User ID/Password/Folder and press the OK softkey after each entry. Press the Exit softkey to get back to the Download Menu. Press 1 for Download Files. Press 3 for Boot & Program. Leave the default file name as it is. Press the Exec softkey. The screen will flash Downloading whilst the file is downloaded from the TFTP/FTP server. When the download is complete the screen will show Saving with a progress indicator. When the save is complete the screen will show Download Complete! Press the Exit softkey to Reset. Press the Exit softkey to reset the terminal.
72
19. The upgrade procedure is complete.
SV8100
Automatic Firmware Upgrade

The following procedure should only be performed using Handset Programming or Web Pro It is possible for the handset to check whether its firmware requires upgrading when it registers to the SV8100. It does this by checking its firmware against the version set in system programming. A TFTP/FTP server is required for this operation, see the information about TFTP/FTP server and firmware file names in the above method.
1. 2. 3. 4. 5. 6.
PRG84-07-01. Set to 0 to use TFTP or 1 to use FTP. If using FTP you must set the FTP Login Name in PRG84-07-03 and the FTP Password in PRG84-07-04. PRG84-07-02. Enter the TFTP/FTP server IP address. PRG84-28-02. Enter the firmware filename for each terminal type (see above). If using FTP you must enter the FTP directory in PRG84-28-01. PRG90-42-01. Enter the firmware version that the handset should compare with. This is the version that the handsets will be upgraded to (e.g. 03.00.00.00). PRG90-42-02. Enter the hardware version of each type of handset (see below for hardware version information) Reboot the SIP MLT to start the upgrade process.
SIP MLT Hardware Versions: ITL-2E/6E 09.01.03.00 ITL-8/12/24/32D 09.01.03.03 ITL-320C 09.01.03.04 WARNING: If the firmware version set in PRG90-42-01 is different to the actual version loaded onto the TFTP/FTP server, the download by the SIP MLT will be repeated in an endless loop. WARNING: The firmware download feature does not support flow control so it is possible that the TFTP/FTP server may not be able to handle the number of download requests. To minimize this problem do not restart a large number of SIP MLTs at the same time. Also using a high spec PC or server may reduce the problem.
SIP MLT Auto Configuration

It is possible for a DT700 to download a configuration file from an FTP server when it initializes. To use this feature the following equipment is required: IP Phone Manager software FTP Server DHCP Server supporting the following: o Vendor Class o Option Codes
Building the Configuration File 1. Launch the IP Phone Manager software 2. Click Auto Config
SV8100
73
3.
Click Terminal
4. 5.
Click 1st Server Address Assign the 1st Server Address using the IPLA IP Address, Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09)
74
6. Click OK
SV8100
7. 8.
Click 1st Server Port. Assign port 5080. Click OK.
9. After the changes are made click Save. 10. When the Save window opens, click Save as...
SV8100
75
11. In the Save as...window, name the file xxx.gz Example: To name the file test, enter test.gz 12. Place this file in the FTP Server Note: With the above config each handset will try and download the config every time it is reset which may be undesirable. To stop this from happening, set the Auto Config option to Disable in the Auto Config file.
Configuring an FTP Server The file generated in the IP Phone Manager must be placed in an anonymous login folder. The FTP server must be configured with an anonymous login account. The configuration of the FTP server will vary depending of the FTP server software. Refer to the manufactures instructions for further details.
76
SV8100
DHCP Server Setup Windows 2003 Server Defining Vendor Classes 1. In the DHCP server highlight the server machine on the left side. Right click on the server and select Define Vendor Classes. 2. Click ADD. 3. Display Name = NECDT700 4. Description = auto config 5. In the same window down below there is a section that shows ID, Binary, and ASCII. Click under ASCII. 6. Enter NECDT700. This should have also added 4E 45 43 44 54 37 30 30 under the binary section. 7. Click OK and close.
Setting Predefined Options 1. Highlight the server again. Then right click and select Set Predefined Options. 2. Change the option class to NECDT700. 3. Click ADD, and provide the following information: Name = FTP Address Data Type = IP address Code = 141 4. Click OK, and start the process over again. 5. Click ADD, and provide the following information: Name = Auto Config File Name Data Type = String Code = 151 Click on ADD, and give the following information: Name = Download Protocol Data Type = Byte Code = 163 6. Click OK.
Configuring Options 1. Highlight scope options on the left side. Then right click and choose Configure Options. 2. Click Advanced and change the vendor class to NECDT700. 3. Place a check mark next to 141 FTP Address. Down below assign the IP address of the FTP server. Then click Apply. 4. Place a check mark next to 151 auto config file name. Enter the name of the config file created using IP Phone Manager. Then click Apply. 5. Place a check mark next to 163 download protocol. Down below change the HEX address to be 0x1. 6. Click on Apply and OK.
SIP MLT Factory Default

SIP MLT handsets can be restored to factory default settings in several ways: Handset programming Web Programming IP Phone Manager Be aware that a default SIP MLT terminal requires a DHCP server to obtain its network information. As the ITL-2E terminal does not have a display it is not possible to use handset programming in the same way as the display terminals, there is a specific key press sequence which can be used to default this type of terminal.
Service Code Factory Default ITL-2E (2 Key DT700)

Under normal circumstances the ITL-2E SIP MLT handsets would be programmed using the web browser. If the IP address of the terminal is unknown and cannot be discovered by other means (i.e. system programming, Wireshark etc), the handset may required to be defaulted. Be aware that a default SIP MLT terminal requires a DHCP server to obtain its network information. Follow these steps to default the handset: -
SV8100
Key Press Hold Conf * * 331# Line key 1 Function Enter programming mode Default terminal Save settings Result = Pass Result = Fail Line key 1 Reset terminal* failed then the terminal is reset with existing Line Key 1 Green Green Red Red Red Line Key 2 Green Flashing green Red Red Red MW Lamp Off Off Off Green after a delay Red
77
* If default was successful then the terminal is reset with default values. If default settings.
Handset Programming Factory Default (ITL-6, ITL-8, ITL-12, ITL-24, ITL-32, ITL-320C)
This must be performed on each handset: Enter handset programming by pressing Menu 0 Enter the correct User Name and Password 3. Maintenance Settings 3. Data Clear Factory Value OK Wait..... Exit Exit Save
Web Interface Factory Default (All Terminals)

This must be performed on each handset: Browse to the IP address of the handset. Enter the correct User Name and Password Maintenance Settings Data Clear Factory Value OK OK Wait..... OK Save OK
IP Phone Manager Factory Default (All Terminals)

This can be used to control up to 8 handsets at a time. Use the Search, Import or Direct function to locate the handsets Tick the handsets that you wish to connect to and click Connect Click Execute Click Yes Click OK Click Close In the Command box choose DataReset and click Execute Click Factory Default and click Execute Click Yes The selected terminals will now reboot with default settings. Close IP Phone Manager
78
SV8100
MH240
MH240 is a WiFi handset which uses the same protocol as the DT700 (iSIP) which makes it a very feature rich mobile device. It can be used in conjuction with the NEC WL1700/1500 range of WiFi access points using the 802.11b/g protocols. It is possible for the MH240 to roam between access points with ability to handover giving a larger coverage area. These handsets cannot be used on any system other than the SV8000. To run MH240 extensions the SV8100 must have: CP00 IPL SIP MLT License(s). The registration procedure for MH240 extensions is described in the MH240
Extension Registration section below.
MH240 Extension Registration

The MH240 registration procedure is the same as that for SIP MLTs except the Manual method is not supported. Also the programming of the handset itself is different to a SIP MLT. If the SV8100 is using the manual registration method, MH240s must be programmed with a User ID and Password as per the Automatic registration method. MH240 ports are allocated in blocks of 2. For example Insert a 16 port extension card (e.g. DLCA, LCA) 1st DT700 to register is set to 1 (default) Configure an MH240 and connect to the WLAN The MH240 will take port 17 (ext 216 in default) Port 18 will also be reserved for use by another IP extension. If a second extension card (e.g. DLCA, LCA) is inserted, it will take ports 19 onwards. When connecting a MH240, the MAC address (ID) is automatically registered in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Extension Setup. (PRG15-05-02)
SV8100
If the MAC address is entered manually, prior to connecting the phone, when the phone is connected, it may (depending on the Register Method) use the port number assigned. The MAC address is printed on the barcode label on the base of the phone. It is a 12-digit alphanumeric number, ranging from 0-9 and A-F. Note: If the port does not have a corresponding extension number assigned to it, the MH240 will be assigned to the next available port which does have an extension number. If there are no ports with extension numbers available, the MH240 with show "Full Port" on the display. If the extension number is removed from and already registered MH240, it will re-register to the next available extension number.
79
Registration Procedure Plug and Play When the Register Mode is set as Plug and Play in Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/ DT700 HotDesk/DT700 Logon Type. (PRG10-46-01), the following information will apply. Set the Extension Number for the MH240 extension against an unused (no associated hardware) port in Wizard Quick Install/ Extensions/Extension Properties (PRG11-02) The MH240 should be programmed to register to the IPL card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09) When an MH240 connects to the SV8100, it is assigned the first available port after the value set in Wizard Advanced Items/VoIP/ Extensions/DT700 Setup/DT700 Setup/1st DT700 to register. (PRG10-46-10)
If static IP addresses or external DHCP server is in use, follow these steps on the handset itself: Press Menu 5 3 1 Password 1234 (or as specified by the installer) Press OK Press 1 1 1 2. Choose Fixed IP or DHCP depending on your network requirements Press OK. If using Fixed IP enter the relevant IP address, Subnet Mask etc here. Press 1. Enter the Wireless network settings in this area (Profile Name, SSID, Security Settings etc). Press HOLD several times to get back to the Config menu. From the main Config menu: Press 2 1 2. Enter the IP address of the IPL card Press OK (SIP Proxy) Press 4. Enter the IP address of the IPL card Press OK (SIP Registrar) Press 9. Enter the iSIP port for the SV8100 (5080) Press OK. Press HOLD three times. Press 2 to save. Press the red hang up key The MH240 will now attempt to connect to the SV8100.
Registration Procedure Automatic When the Register Mode is set as Automatic in Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Type. (PRG10-46-01), the following information will apply. Set the Extension Number for the MH240 extension against an unused (no associated hardware) port. Wizard Quick Install/ Extensions/Extension Properties (PRG11-02) The MH240 should be programmed to register to the IPLA card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09) Enter a Used ID and Password for each MH240 in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Password. It is recommended to use the extension number as the User ID. Take the Personal ID Index from the above command and enter it against the relevant extension number in Wizard Advanced Items/VoIP/Extensions/DT700 Setup./DT700 Additional Features/DT700 HotDesk/DT700 Logon Feature. If static IP addresses or external DHCP server is in use, follow these steps on the handset itself: Press Menu 5 3 1 Password 1234 (or as specified by the installer) Press OK
80
SV8100
Press 1 1 1 2. Choose Fixed IP or DHCP depending on your network requirements Press OK. If using Fixed IP enter the relevant IP address, Subnet Mask etc here. Press 1. Enter the Wireless network settings in this area (Profile Name, SSID, Security Settings etc). Press HOLD several times to get back to the Config menu. From the main Config menu: Press 2 1 2. Enter the IP address of the IPL card Press OK (SIP Proxy) Press 4. Enter the IP address of the IPL card Press OK (SIP Registrar) Press 6. Enter the User ID associated with that extension programmed in the SV8100 (normally the same as the extension number) Press OK. Press 7. Enter the Password associated with that extension programmed in the SV8100 Press OK. Press 9. Enter the iSIP port for the SV8100 (5080) Press OK. Press HOLD three times. Press 2 to save. Press the red hang up key The MH240 will now attempt to connect to the SV8100.
Delete MH240 Registration

Before attempting to delete the registration of an MH240, the IP Phone must be powered off. Enter Program 90-23-01 (handset programming or Web Pro only), and enter the extension number of the IP Phone. Press 1 and Transfer to delete the registration.
MH240 Codec Settings

MH240's can have a choice of two CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPLA card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for MH240 handsets G.711 64Kbps codec MOS 4.4 G.729 8Kbps codec MOS 4.0 The bandwidth values quoted for these codecs are for the digitized speed in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. The codec is programmed against a Type (profile). Upto five Types (profiles) can be set up. The extension is then assigned to particular Type (profile). 1) Program the codec for each Type using the Audio Capability Priority option in Wizard Advanced Items/IP SIP/DT700 Setup (PRG84-24-28) 2) Assign the Type number to the extension using the Codec Type option in Wizard Advanced Items/VoIP/Extensions/DT700 Extension Setup (PRG15-05-15) Please note that it is possible to set codecs in these commands which are not supported by the MH240. If this occurs a mutually compatible codec will be negotiated instead. To avoid this, a separate profile should be set for use with MH240 handsets with a compatible codec. Please be aware that this codec selection is only a preferred setting. It is possible that a MH240 will use the other available codec depending on the destination of the coversation and also who was the originating party of the call.
RTP Alarm
RTP Alarm is an audible indication to a user that the RTP (speech) is not getting through to that user. It can be heard when using MH240 Extensions when there are problems on the network between the end points. The alarm is indicated as two short beeps in the ear piece of the receiving user, the two beeps may be repeated if the problem continues.
SV8100
The RTP Alarm can be enabled/disabled on a per handset basis using the handset Menu: Menu 5. Setting 1. User Setting 2. Talk 1. RTP Alarm Chose the required setting for the RTP Alarm and press OK Press the Hang Up key to exit the handset Menu More information may be obtained by using the QoS Monitor during a call: During a call press Menu on the MH240, the QoS Monitor is displayed. The display shows three values: o LostPacket shows the number of lost RTP packets on that call o Codec shows the codec in use on that call o Payload shows the payload or VSI in use on that call To switch off the QoS Monitor during a call press the Hold key or the Hang Up key (this will not hold or disconnect the call) Note: The LostPacket indication only shows the number of packets that are lost in the WiFi network (between the MH240 and WiFi access point), not on the LAN. The lost packet count can only be updated when the MH240 has connectivity with the SV8100, if connection is lost during the call the display will not be updated.
81
Peer to Peer
By default if two IP extensions are on an internal call together, the RTP will be sent directly between the two endpoints. This reduces the DSP consumption, reduces delay on the VoIP packets and increases voice quality on the call. There may be instances where this operation is not supported. May be the the customers network does not allow it. If this is the case it is possible to disable Peer to Peer for MH240 extensions. Use the SIP Peer to Peer option in (PRG10-26-04) Be aware that this option controls Peer to Peer for all MH240 extensions and SIP MLT extensions registered on that system.
License
The SV8100 requires licensing to allow the registration of MH240 handsets. One license is required for each registration to the SV8100. If no license is available, the MH240 will fail to register. Up to 512 SIP MLT licenses can be added. The recommended number of MH240 registrations is 128. License Code: BE107585
IP Phone Manager for MH240

IP Phone Manager for MH240 is a maintenance application for MH240 handsets. It is a separate application from the SIP MLT IP Phone Manager. It can be used for several functions such as initiating file downloads, creating configs, changing settings, backing up configs etc. The application can be used to communicate with the MH240 via the WiFi network or via a direct USB connection. Some options can only be performed using the USB direct connection.
Installation
Follow these steps to install the IP Phone Manager for MH240. 1. Double click IP_Phone_Manager_for_MH240_Setup-x.x.x.x.exe The installer Language screen appears
82
SV8100
2. 3. 4. 5. 6. 7. 8.
Choose the required language and click OK. The Setup Wizzard screen appears, click Next. Check I accept the terms in the License Agreement, and click Next. Check all of Select components to install, and click Next. In the Choose Install Location screen, Click Browse..., and choose where you wish to install the application and click Install. When the Installation Complete screen appears, click Next. In the Completing the Setup Wizard Screen, click Finish.
Install OpenSSL
If you need to create licenses for use with 802.1X then you will need to install OpenSSL. To install OpenSSL, access the following URL and follow the prompts. ***** http://www.slproweb.com/products/Win32OpenSSL.html *****
Install the USB Driver

After IP Phone Manager for MH240 starts, the installation of the application (and OpenSSL if required) is complete. When the USB cable is connected to an MH240 for the first time after IP Phone Manager for MH240 is started, the driver's installation is demanded by Windows. Please select "Software is automatically installed" according to the instruction of the Windows side.
Starting IP Phone Manager for MH240

Access Account / Login 1. Double-click the IP Phone Manager for MH240 icon located on the desktop. 2. Click Administrator, enter the password adminuser and click OK. 3. When the Start FTP Server screen appears click OK. 4. An IP Phone Manager screen appears displaying the account menu.
SV8100
83
Exit Account /Logout 1. In the Terminal Settings window click Exit. 2. When the Exit screen appears, click OK.
3.
When the Exit FTP Server screen appears click OK.
84
SV8100
MH240 Firmware Upgrade

From time to time it may be necessary to upgrade the firmware on the MH240 handsets, possibly to introduce new features. The firmware is upgraded using the IP Phone Manger for MH240 via the WLAN network or via direct USB connection. If the handset is connected to the WLAN network and is registered to the SV8100 correctly it is easier to upgrade the handset using the WLAN network. Follow the IP Phone Manager for MH240 section for details on how to install and run the application.
USB Cable Connection

Follow these steps to connect the USB cable to an MH240: 1. Connect a USB cable to the PC USB port. 2. On the MH240 press Menu 5 3 4. 3. Unplug the USB cable from the handset (if connected). Press OK. 4. Connect the USB cable to the handset and press OK.
Firmware Upload via WLAN

1. 2. Click Firmware Upload in the Terminal Settings Menu. Click IP and click Next.
3.
Click the Browse button and specify the file to be uploaded. Or, enter path of upload file in the text box. Click Next.
SV8100
85
4.
Locate the MH240 handsets by clicking Direct and entering the IP address of each handset in the search box.
5.
Place a tick next to the handset you wish to upgrade. Two handsets can be selected for upgrade at the same time if required.
86
SV8100
6. 7. 8.
Click Open PC Port. Click Next. If required set the Start Time, End Time and Retry count, click Upload.
9.
Verify that the upload was successful, click Finish.
SV8100
87
Firmware Upload via USB Connection 1. 2. Click Firmware Upload in the Terminal Settings Menu. Click USB and click Next.
3.
Click the Browse button and specify the file to be uploaded. Or, enter path of upload file in the text box. Click Next.
88
SV8100
4.
Connect the USB cable to the MH240 (refer to the USB Cable Connection section) and click Start
5.
Verify the upload was successful. Click Finish to return to the Terminal Settings Menu or click Continue if you need to upgrade additional MH240 handsets.
DtermIP General Information

DTermIP extensions are proprietary IP telephones that connect to the SV8100 using the NEC Protims protocol. They were originally designed for use on the Aspire system. These phones can use most of the features that can be found on a standard (TDM) key telephone. To run a DTermIP the SV8100 must have:
SV8100
CP00 IPL ME50 DTermIP License(s)
89
Providing Power
DTermIPs require power to function. This can be provided in various ways: a) Local Power The DTermIPs have a connector for external power. This is supplied by an AC adapter that has a 27V DC output. This means that a mains socket is required in the vicinity of each telephone and loss of mains power in the building will prevent the phones from working. Powered Patch Panel (Midspan) A powered patch panel has two RJ-45 connectors per telephone. One port connects to the switch/hub, and the other port connects to the DTermIP. The patch panel has an integral power supply that adds power to the spare pins of the RJ-45. When the DTermIP is connected to the powered patch panel, it automatically receives its power via the spare pairs on the Cat-5 cable - there is no need for a local power adapter. Power over Ethernet (PoE) A PoE switch is a switched hub that also provides power over the spare pairs. The switch can be used with any device (not just DTermIPs) and will detect if power is required or not. As all of the phones receive their power from one device, it is easy to protect the telephones from loss of power (by connecting the PoE switch to a UPS). There are two industry standards for PoE: Cisco Inline Power supported on the 24TIXH and IP ADAPTER IEEE802.3af supported on the 24BTIXH and 4TIXH
b)
c)
DTermIP Extension Registration

The ports are allocated in blocks of 2. For example Insert a 16 port extension card (e.g. DLCA, LCA) Station Port is set to 1 (default) Configure a DTermIP and connect to the LAN The DTermIP will take port 17 (ext 216 in default) Port 18 will also be reserved for use by another IP extension. If a second extension card (e.g. DLCA, LCA) is inserted, it will take ports 19 onwards. When connecting a DTermIP, the MAC address (ID) is automatically registered in Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Extension Setup. (PRG15-05-02) If the MAC address is entered manually, prior to connecting the phone, when the phone is connected, it may use the port number assigned. The MAC address is printed on the barcode label on the base of the phone. It is a 12-digit alphanumeric number, ranging from 0-9 and A-F. Note: If the telephone display goes blank after "DRS(1st)Connecting..." is displayed, the port that has been assigned may not have a corresponding extension number assigned to it. The DTermIP has to be configured with an IP Address, Subnet Mask, Default Gateway and the address of the SV8100 IPL. This IP information can be supplied by DHCP or can be manually configured on the DTermIP. There are two program levels available for individual phone programming - the User Menu and the Maintenance Menu. Each program mode is accessed differently. To navigate around the menu use the numeric keypad to enter the corresponding menu item. Use the soft keys to OK or Cancel any changes that you make When finished, the SAVE soft key will save the settings and restart the DTermIP. Note: When entering IP addresses, use the * key for "." Note: When using a 4TIXH handset use FLASH in place of CONF to enter the handset menu.
90
SV8100
If the SV8100 is being used as a DHCP server and has default IP addresses, no configuration is required on the DTermIP.
Registration Procedure DtermIP extensions can only use the Plug & Play method of registration so they will ignore the Register Mode setting, this is only for SIP MLT/MH240 extensions. Set the Extension Number for the DTermIP extension against an unused (no associated hardware) port in Wizard Quick Install/ Extensions/Extension Properties (PRG11-02) The DTermIP should be programmed to register to the IPLA card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09) When a DTermIP connects to the SV8100, it is assigned the first available port after the value set in Wizard Advanced Items/VoIP/ Extensions/DTermIP Extensions/DTermIP Extension Basic Setup/Start Port. (PRG84-03-09) If static IP addresses or external DHCP server is in use, follow these steps on the handset itself: Press HOLD CONF * # (Hot Keypad must be disabled on SV8100) Press 1.DHCP Mode Choose to Enable or Disable DHCP (depending on network requirements) Press OK Press 2.DRS Address Primary Enter the IP address of the SV8100 IPL card Press OK. Press 4.IP Address Enter the static IP address of the DTermIP if not using DHCP Press OK. Press 5.Default Gateway Enter the IP address of the Default gateway (if required) if not using DHCP Press OK. Press 6.Subnet Mask Enter the Subnet Mask for the DTermIP if not using DHCP Press OK. Press Save. The DTermIP will now attempt to connect to the SV8100 Error Messages Below is a table containing some error messages that may appear on the display of the DTermIP and some hints on how to resolve the problem. Error DRS Connect Timeout Cause The SV8100 has not responded to the registration message Measures Check the SV8100 config, IP phone config, and network connectivity Configuration SV8100: Check 10-12-02, 03, 09 and 10 IP Phone: DRS Address does this match 10-12-09 IP Address, Subnet Mask, Default Gateway check that these are valid Try pinging from IP phone and from LAN to ensure data connectivity DHCP Server Not Found DHCP Server not responding If using Aspire as DHCP Server If using external DHCP Server Illegal LEN The MAC address of Check the Ext the IP Phone has programming been manually assigned to a port, but there is no extension number assigned to that port All extension ports are Check port used assignments Check 10-13-01 is enabled (reboot required if this command is changed) Check config of external DHCP server. Has Option 161 been enabled? 11-02-01 Valid Ext Number for selected port?
Capability Exceeded
SV8100
When using automatic Check programming registration, a port has been selected, but no extension number is assigned to the port. Resource Unavailable The IP phone is trying to connect to a port that is already in use (by DECT, Keytelephone, etc). Check port assignments
91
11-02-01 Is there an extension port assigned? 84-03-09 Check which port will be used for automatic registration
Accessing the User Menu On the DTermIP, enter the phone's programming mode by entering HOLD TRANSFER * #. (Hot Keypad must be disabled on SV8100) The following shows the menu items available in the phone's programming.
92
SV8100
SV8100
93
Accessing the Maintenance Menu Enter the phone's programming mode by pressing HOLD TRANSFER * # (Hot Keypad must be disabled on SV8100). This enters into the User Menu. Press HOLD # 0 to then enter the Maintenance Menu. The following shows the menu items available in the phone's programming.
DTermIP Codec Settings

DTermIP's can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPL card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for DTermIP handsets G.711 64Kbps codec MOS 4.4
94
SV8100
G.729 8Kbps codec MOS 4.0 G.723 6.3Kbps codec MOS 3.9 The bandwidth values quoted for these codecs are for the digitized speed in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. The codec is programmed against a Type (profile). Upto five Types (profiles) can be set up. The extension is then assigned to particular Type (profile). 1) Program the codec for each Type using the Audio Capability Priority option in Wizard Advanced Items/VoIP/Extensions/ DTermIP Extensions/DTermIP Codec Setup (PRG84-11-28) 2) Assign the Type number to the extension using the Codec Type option in Wizard Wizard Advanced Items/VoIP/ Extensions/DTermIP Extensions/DTermIP Extension Setup (PRG15-05-15) Please be aware that this codec selection is only a preferred setting. It is possible that a DTermIP will use one of the other available codecs depending on the destination of the coversation and also who was the originating party of the call.
RTP Alarm
RTP Alarm is an audible indication to a user that the RTP (speech) is not getting through to that user. It can be heard when using DTermIP Extensions when there are problems on the network between the end points. The alarm is indicated as several short beeps in the ear piece of the receiving user, the beeps may be repeated if the problem continues. More information may be obtained by using a Dterm IP Call Log key (Function Code 82): During a call press the programmable function key (Dterm IP Call Log) The display shows three values: o LostPacket shows the number of lost RTP packets on that call o Codec shows the codec in use on that call o Payload shows the payload or VSI in use on that call To return the display to normal press the Exit softkey Note: The lost packet count can only be updated when the DTermIP has connectivity with the SV8100, if connection is lost during the call the display will not be updated.
Peer to Peer
By default if two DTermIP extensions are on an internal call together, the RTP will be sent directly between the two endpoints. This reduces the DSP consumption, reduces delay on the VoIP packets and increases voice quality on the call. There may be instances where this operation is not supported. May be the customers network does not allow it. If this is the case it is possible to disable Peer to Peer for SIP MLT extensions. Use the Peer to Peer Mode option in Wizard Advanced Items/VoIP/Extensions/DTermIP Extensions/DTermIP Extension Basic Setup (PRG10-26-01) Be aware that this option controls Peer to Peer for all DTermIP extensions registered on that system.
License
The SV8100 requires licensing to allow the registration of DTermIP handsets. One license is required for each registration to the SV8100. If no license is available, the display of the DTermIP shows Capability exceeded. Up to 512 DTermIP licenses can be added. License Code: BE107585
Standard SIP Extensions

Standard SIP (also referred to as 3rd Party SIP) is an industry standard protocol and therefore there are many manufacturers hardware and software based phones. As these phones are not developed by NEC, and are not designed specifically for use on the SV8100, they do not support majority of the features that you would find on an SV8100 Keytelephone. The features available to SIP extensions are detailed in the SIP Extension Compatibility Report for the relevant SIP terminal.
SV8100
The SV8100 is compliant with the RFC3261 SIP standard. To run Standard SIP extensions the SV8100 must have: CP00 IPL Standard SIP License(s). Various types of SIP phones are available, including: Standard SIP Softphone (not SP310) Software application for PC's (usually used on laptop computers) Messaging software with integrated SIP capability (e.g. Windows Messenger) Hardware based telephone Analogue adapter - allows connection of analogue SLT telephone to SIP/H.323 network WiFi telephones Portable WiFi devices with SIP clients (some GSM phones) DECT phone IP DECT uses the SIP protocol to communicate with the SV8100
95
The SIP extension will register itself to the SV8100 system. The registration creates a map between the SIP phone and an extension port on the SV8100. This means that any programming related to that extension port (for example, Class of Service) will apply to the SIP extension. To allow registration of an SIP extension to a particular extension port it is necessary to assign an extension number to the port, this will be the extension number assigned to the SIP extension. The SIP extension should be configured with a valid IP Address and should be connected to the same data network as the SV8100. The procedure for configuring the SIP extension varies depending on the manufacturer - this guide does not cover the configuration of third party equipment. Precaution Correct programming of any system or application is, obviously, essential at any time, however. some support issues have shown the effects that incorrect programming can cause in the specific areas where an IP address is assigned to multiple devices. It is essential that careful planning and deployment regarding IP addressing is performed to avoid the many problems caused when there are IP address conflicts. Please be aware that IP Duplication Groups should be programmed before the device(s) register to the switch, never afterwards. Please make sure that only the required SIP ports belong to IP Duplication Groups Especially please do not change SIP timers unless advised by NEC Technical Support Department. For example, changing PRG 10-33-01 (Registration Expiry Time) on the SV8100 is currently not necessary or recommended for IP DECT as it is naturally set at the correct default for present purposes. Altering this and some associated commands such as in PRG 84-20 (SIP Extension Basic Set Up) has been shown in some cases to have serious consequences for customers IP DECT. The defaults are; PRG 10-33-01 (Registration Expiry Time) 3600 PRG 84-20-02/03/05/06 (SIP Extension Basic Set Up) 180 The correct methods of implementation for various systems and applications are covered in our relevant training courses.
SIP Extension Registration

Before attempting to register any SIP extensions to the SV8100 check whether the SIP device requires IP Duplication Allowed Group setting or not. This is very important because if IP Duplication Allowed Group setting is required it must be programmed before the SIP device registers to the SV8100. Please refer to the SIP Extension Features page for more information about IP Duplication Groups. Enter the extension number for the SIP extension in Wizard Quick Install/Extensions/Extension Properties (PRG11-02) against an unused port with no associated hardware. Program the SIP device to register to the IPL card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09) Program the SIP device with its "username" or "SIP ID" as the required extension number in Wizard Quick Install/Extensions/ Extension Properties (PRG11-02) The actual terminology used by the third-party device varies depending on the manufacturer. The SV8100 uses port UDP/5070 for SIP Extension registrations. Most SIP Extensions use port UDP/5060 by default so this needs to
96
be changed on the SIP device.
SV8100
Authentication
The SV8100 can be set so that the SIP device is required to authenticate its self using a password before the registration is complete. This option is disabled by default. Enable Authentication Mode by ticking the box in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Authentication (PRG1033-02) It is also required to enter a password per SIP extension using the Authentication Password option in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Terminal Setup (PRG15-05-16) The password entered in system programming is then required to be entered in to the SIP device. Note: If a password is not entered, per extension, in the SV8100 system programming the SIP device will be able to register without a password even if Authentication Mode is enabled. It is recommended to enter a password for every free extension number that, in theory, could have a SIP device registered to it. This gives some security against unsolicited SIP registrations. It is also recommended to check the Toll Restriction class assigned to each extension number, whether it has a registered device or not, to make sure is has the correct dialling permissions.
Delete SIP Extension Registration

Before attempting to delete the registration of a SIP extension, the SIP device must be unplugged or powered off. Enter Program 90-23-01 (handset programming or Web Pro only), and enter the extension number of the SIP device. Press 1 and Transfer to delete the registration.
SIP Extension Codec Settings

SIP Extensions can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPL card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for SIP Extensions G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.726 32Kbps codec MOS 4.2 iLBC 13.33Kbps codec MOS 4.1 G.729 8Kbps codec MOS 4.0 G.723 5.3Kbps codec MOS 3.9 T.38 Fax Relay SIP Video*1
*1 SIP Video cannot pass through the IPLA but may work Peer to Peer. See the SIP Video section on the SIP Extension Features page.
To enable either G.723 or iLBC set Codec Mode to G.723/iLBC in Wizard Advanced Items/VoIP/General Settings/VoIP Configuration/IPL Basic Setup. (PRG84-27-02) The bandwidth values quoted for these codecs are for the digitized speech in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. The codec is programmed against a Type (profile). Only one Type (profile) can be set up. The extension is then assigned to Type 1. 1) Program the codec for each Type using the Audio Capability Priority option in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Extension Codec (PRG84-19-28) 2) Assign the Type number as 1 to the extension using the Codec Type option in Wizard Advanced Items/VoIP/Extensions/ DT700 Extension Setup (PRG15-05-15)
SV8100
Please be aware that this codec selection is only a preferred setting. It is possible that a SIP extension will use one of the other available codecs depending on the destination of the conversation and also who was the originating party of the call.
97
License
The SV8100 requires licensing to allow the registration of Standard SIP handsets. One license is required for each registration to the SV8100. If no license is available, the SIP extension will fail to register. Other licenses may be required for certain Standard SIP features (i.e. SIP Video). Up to 512 Standard SIP licenses can be added. License Code: BE107586
SIP Extension Features

The following is a list of features supported by the system when using SIP extension, any feature not listed here should be assumed to be not supported. Outgoing Enblock sending Service Code (see Service Code List below) Account Code Abbreviated Dial Service code list Night Mode Switching (own group) Record/Erase VRS Message General Message Playback (VRS) Record and Erase General Message (VRS) Call Forward Immediate/Busy/No Answer/Busy-No Answer/Dual Ring Dial Block Temporary Toll Restriction Override Walking Toll Restriction VRS/Off Premise Call Forward Transfer Dial setting for out of range DND/FWD Override (Bypass call) Conference Call Waiting (not receive) Barge In Last Number Redial Saved Number Dialling Clear LND Clear SND Specified Trunk Answer Call Park Group Hold Station Park Hold Common Cancelling Code Personal Speed Dial Call Own Mailbox (Inskin Voice Mail) Live Recording (Inskin Voice Mail) Tandem Trunking (Unsupervised Conference) Incoming Extension Normal Trunk VRS/DISA DID DIL Leased Line (Tie Line) Door Phone (operation explained below) Hold/Transfer Normal Hold Park Hold
98
Group Hold Station Park Hold Type of transfer service Call Forward Immediate Call Forward Both Ring Call Forward No Answer Call Forward Busy Call Forward Busy/No Answer Follow Me Fixed Call Forward Fixed Call Forward Off Premise Call Forward to Device Automated Attendant Transfer operation ISDN Normal Transfer ISDN Blind Transfer SLT Normal Transfer SLT Blind Transfer DSPDB VM Normal Transfer DSPDB VM Blind Transfer
SV8100
CLI/Name Display CLIP Display Extension Name Display*1 Nickname Display*1 Extension Number Display*1 SIP Display Field Display*1 Abb Dial Name Display Door Phone Name Display Voicemail Name Display*2 CLI Update after transfer (IP DECT) *1 One of these options can be displayed depending on system programming and the received SIP information. *2 Dependant on the type of Voicemail system in use. Others Can belong to an Incoming Ring Group Can belong to Department Group, however all ring mode not supported Peer to Peer Mode (allows RTP to be sent directly between SIP endpoints) Voice Mail Message Waiting Assign as Virtual Extension Conference Barge In/Monitor T.38 Fax Relay Video Support*3 *3 Please refer to the SIP Video section below. Conditions The above list of features are supported by the system for SIP extensions, however, this does not mean the device will work for all of these features. The SIP extension certificate confirms which features are supported in Peer to Peer mode and non Peer to Peer mode for the specific device. Operation The operation for each feature is as described in each specific feature section.
Doorphone
To allow the SIP extension to operate the door lock PRG90-03-01 needs to be enabled. This command can only be accessed via
SV8100
99
handset programming. A SIP extension can be long to a Doorphone ring group but the operation differs slightly from that of an SLT telephone. The operation has been tested using an NEC IP DECT handset: Doorphone call button is pressed IP DECT handset rings IP DECT user answers the Doorphone IP DECT user and the Doorphone user speak IP DECT user presses R (green button) to operate the lock IP DECT user presses R again to speak to the Doorphone user IP DECT user hangs up. Note: If the IP DECT user does not press the R button for the second time before hanging up the call, the Doorphone may recall back to the IP DECT user.
Peer to Peer
By default if two IP extensions are on an internal call together, the RTP will be sent directly between the two endpoints. This reduces the DSP consumption, reduces delay on the VoIP packets and increases voice quality on the call. There may be instances where this operation is not supported. May be the SIP terminal does not support this operation or the customers network may not allow it. If this is the case it is possible to disable Peer to Peer for SIP extensions. Use the SIP Peer to Peer option in Wizard Advanced Items/VoIP/Extensions/SIP Extensions/SIP Codec Setup (PRG10-26-03) Be aware that this option controls Peer to Peer for all SIP extensions registered on that system.
DTMF Relay (RFC2833)

By default any DTMF tones transmitted from a SIP extension will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors on the IP network. DTMF relay is a way of converting the DTMF tone into a signal then sending the signal across the IP network instead of the actual tone. To use this feature both devices (SV8100 and the SIP device) must support DTMF relay (RFC2833). To enable this feature set the DTMF Relay Mode option to RFC2833 in Wizard Advanced Items/VoIP/Extensions/SIP Extensions/ SIP Codec Setup (PRG84-19-32)
T.38 Fax Relay

This is a new feature for Release 4 software. Standard SIP extensions now have the ability to communicate using the T.38 Fax Relay protocol. By default any Fax tones transmitted to or from a Standard SIP extension will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. T.38 Fax Relay is a way of converting the Fax tones into a signal then sending the signal across the IP network where the signals are converted back to Fax tones. The Standard SIP device must be compatible with T.38 for this to work. Enable Fax Relay by using the Fax Relay Mode option in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Extension Codec (PRG84-19-50). The SIP extension must also be set as a Special using the Terminal Type option in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Terminal Setup (PRG15-03-03). There are several other options to do with T.38 Fax relay that can also be found in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Extension Codec (PRG84-19-51 to 61), these commands would usually be left at the default settings but may occasionally need altering depending on the SIP device, fax machine and network connection.
IP Duplication Allowed Groups

By default the SV8100 allows one SIP registration per IP address. In certain circumstances multiple extension numbers may be required to be registered via the same IP address, e.g. Cisco ATA has two extension connections but only one IP address. With this scenario the second registration from the same IP address would overwrite the first registration. To overcome this limitation it is necessary to put the SIP extensions into a particular IP Duplication Allowed Group. This allows multiple registrations from a single IP address and also allows the SIP registration to be overwritten by another IP address. There are 10 groups available. e.g. If a Cisco ATA is to have extensions 250 and 251 registered from the same IP address, put extension 250 and 251 into the same IP Duplication Allowed Group in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Terminal Setup (PRG15-05-18). This command should be done before the SIP extensions are registered to the SV8100.
100
SV8100
Automatic IP Duplication Allowed Group Assignment

This is a new feature for Release 4 software. It automatically assigns the IP Duplication Allowed Group when registering IP DECT, UCB or BCT SIP extensions. This means that the IP Duplication Allowed Group setting does not need to be programmed prior to registering the extensions to the SV8100. The SV8100 detects that the registration request is from one of the above devices and assigns the SIP extensions to an available group (starting with Group 10 and working down) accordingly. If the IP Duplication Group has been set manually prior to the registration request then the feature will not be activated for that SIP extension, it will keep its manual group assignment. Be aware that this feature will only work for IP DECT, UCB and BCT. Other devices that require IP Duplication Groups will need assigning manually as before.
SIP Video
This is a new feature for Release 4 software. It is possible to communicate between Standard SIP extensions using Video. This is only possible if SIP Peer to Peer is enabled and SIP CTI is disabled, if any of these conditions are not met video communication will fail. Check the SIP Peer to Peer and SIP CTI settings in Wizard Advanced Items/VoIP/Extensions/SIP Extensions/Codec Setup To enable SIP Video on a per extension basis, use the Video Mode option in Wizard Advanced Items/VoIP/Extensions/SIP Extensions/SIP Extension Setup. A SIP Video licence is required for this feature. Only one license is required regardless of the number of Standard SIP terminals. Conditions/Comments The video stream cannot pass through the IPLA card, SIP Peer to Peer must be enabled. SIP CTI must be disabled. Video communication between a Standard SIP terminal and the SP310 Softphone is not possible. The SIP terminal must pass interoperability testing by NEC before it can be supported. The video codec is not supported by the IPLA card. The video codec information from the received SDP message will be forwarded to the destination terminal. The communicating video terminals must support common audio and video codecs. SIP Video is not supported across AspireNet or K-CCIS as the communication between the SIP terminals is not Peer to Peer. Be aware of bandwidth requirements of video communication, this will be considerably higher than a voice call. Bandwidth is dependent on codec selection, frame rate and resolution. Check the manufacturers data sheet for the relevant terminal for further details. There must be a STD SIP Video license installed on the SV8100 along with the Standard SIP Terminal licenses.
Call Waiting
SIP Call Waiting is designed for use with NEC IP DECT, the operation of this feature cannot be guaranteed with other Standard SIP Terminals. This is a new feature for Release 5 software. It allows a busy IP DECT user to receive a second call indication by a beep in the ear and some display information. The IP DECT user has several options when they receive a second call indication: Ignore the second call and continue with the first. Hold the first call and answer the second (toggle between the callers is also possible). Hang up the first call and answer the second.
SV8100 Requirements
Main Software SIP Call Waiting is supported with V5.00 or higher release of the SV8100. Firmware SIP Call Waiting is supported on any release of IP DECT handset firmware and any DAP firmware. Conditions/Comments R5 advanced feature license is required for the call waiting feature. Call Waiting is not supported on the C124 IP DECT handset. M155 handset cannot hold the first call and answer the second or toggle between the calls. It is not possible to transfer a call to an IP DECT handset if it arrives at the IP DECT as the second call.
SV8100
101
A Doorphone call cannot be answered as a second call. To answer the Doorphone the first call must be cleared then wait for the Doorphone call to ring the IP DECT handset and answer as normal. If there are no DSPs available when a user sends a second call to an IP DECT user Call Waiting is not possible and the caller will hear busy tone. When an IP DECT user is talking to the second call with the first call on hold, if the second call is cleared the first call will then recall to the IP DECT user as a new call. It is not possible to send Call Waiting indication to an IP DECT handset if the first call is either a Doorphone or Voicemail. Programming The Call Waiting feature needs to be allowed by Class of Service programming on a called extension basis. To enable SIP Call Waiting on a per CoS basis, use the Call Waiting for standard SIP Terminal option in Wizard Advanced Items/ IP DECT/IP DECT Features/IP DECT COS Features. (PRG20-13-54) Apply the relevant CoS to each extension in Wizard Advanced Items/IP DECT/IP DECT Features/COS Per Mode. (PRG20-06) The calling extension also needs to be able to send a Call Waiting event to the IP DECT extensions. This is done by allowing Intercom Off-hook Signalling or Automatic Off-hook Signalling by Class of Service in Wizard COS. (PRG20-13-05/06) The CoS is applied to the extension in Wizard- Extensions/Extension/Extension Properties/Class of Service Per Night Mode. (PRG2006) If Automatic Off-hook Signalling is used then the calling party will not hear busy tone, Call Waiting is automatically sent. If Intercom Off-hook Signalling is used then the calling party will hear busy tone and they will have to use the Override function (SC809 or Function Key 33) to send Call Waiting. To allow Call Waiting from a trunk Call Queuing or Second Call for DDI/DISA/DIL/E&M may be required in Wizard COS. (PRG2009-01/07) Programming of the IP DECT system is also required. In the DAP Configurator go to the SIP Settings tab and change the multiple_call_appearance option to =yes. It is also possible to alter what appears on the display of the IP DECT handset during a Call Waiting event. Chose the call_waiting_indication option to the required text. Beware that if this text is too long the extension name that is waiting may not fit on the display at the same time. It is recommended to leave this setting at its default value of waiting. Operation When a Call Waiting event is sent to an IP DECT handset the IP DECT user will hear a tone in the earpiece and some text on the display including the calling party information. To hang up the first call and answer the Call Waiting: 1. Press the red Hang Up key this clears the first call 2. Wait for the second call to ring the handset 3. Answer the ringing second call by pressing the green Answer button 4. Talk to the calling party To hold the first call and answer the Call Waiting: 1. Press the * key this holds the first and answers the second 2. Talk to the calling party 3. The first call will then indicate as a Call Waiting 4. Toggle between the callers by pressing the * key If the IP DECT user doesnt answer the Call Waiting the tone will stop and the display will return to show the information of the first call.
Caller ID Update after Transfer

Caller ID Update after Transfer is designed for use with NEC IP DECT, the operation of this feature cannot be guaranteed with other Standard SIP Terminals. This is a new feature for Release 5 software. It allows the CLI displayed on an IP DECT handset to be updated to show the transferred partys name or CLI after the call has been transferred. Prior to this feature the IP DECT display would show the information from the transferor rather than the transferee.
102
SV8100
Existing Operation (Prior to V5.00)
New Operation (V5.00 onwards)
SV8100 Requirements
Main Software
SV8100
Caller ID Update after Transfer is supported with V5.00 or higher release of the SV8100. Firmware Caller ID Update after Transfer is supported from DAP firmware V4910b510.dwl onwards and on any handset firmware. Conditions/Comments R5 advanced feature license is required for the caller update after transfer feature. Extension name or CLI to name conversion is not supported for this feature, only the extension number or CLI. If no CLI is available on the trunk call Anonymous is displayed on the IP DECT handset. Programming There is no programming required on the SV8100 or on the IP DECT system to activate this feature.
103
H.323 Extensions
H.323 is an industry standard protocol and therefore there are many manufacturers hardware and software based phones. As these phones are not developed by NEC, and are not designed specifically for use on the SV8100, they do not support majority of the features that you would find on an SV8100 Keytelephone. The SV8100 is compliant with H.323 Version 3. H.323 has, in the most part, been replaced by SIP. NEC strongly recommends the use of SIP in place of H.323 wherever possible. The H.323 extension will register itself to the SV8100 system. The registration creates a map between the H.323 phone and an extension port on the SV8100. This means that any programming related to that extension port (for example, Class of Service) will apply to the H.323 extension. To allow registration of an H.323 extension to a particular extension port it is necessary to assign an extension number to the port, this will be the extension number assigned to the H.323 extension. The H.323 extension should be configured with a valid IP Address and should be connected to the same data network as the SV8100. The procedure for configuring the H.323 extension varies depending on the manufacturer - this guide does not cover the configuration of third party equipment.
H.323 Extension Registration

Enter the extension number for the H.323 extension in Wizard Quick Install/Extensions/Extension Properties (PRG11-02) against an unused port with no associated hardware. Program the H.323 device to register to the IPLA card on the SV8100. Wizard Advanced Items/IP SIP/Blades/CCPU IP Address. (PRG10-12-09) Program the H.323 device with its "alias", "username" or "UID" as the required extension number in Wizard Quick Install/Extensions/ Extension Properties (PRG11-02) The actual terminology used by the third-party device varies depending on the manufacturer. The SV8100 uses port TCP/1719 for H.323 RAS. This means that most H.323 IP Phones should be able to connect to the SV8100 using their default port settings. It is important to note that third-party H.323 phones have many configuration items, and some of these are given slightly different names by different manufacturers. The list below shows some common items and the suggested setting, to allow compatibility with the SV8100. Fast Start H.245 Tunnelling Enabled Disabled
104
H.245 in Setup DTMF - Q.931 Keypad DTMF - H.245 Signal DTMF - H.245 Alphanumeric DTMF - In Band Disabled Disabled Disabled Enabled
SV8100
Enabled (if no other supported option is available Enabled
DTMF - RFC2833
Delete H.323 Extension Registration

Before attempting to delete the registration of an H.323 extension, the H.323 device must be unlpugged or powered off. Enter Program 90-23-01 (handset programming or Web Pro only), and enter the extension number of the H.323 device. Press 1 and Transfer to delete the registration.
H.323 Extension Codec Settings

H.323 Extensions can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPLA card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for H.323 Extensions G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.729 8Kbps codec MOS 4.0 G.723 6.3Kbps codec MOS 3.9 To enable either G.723 set PRG84-27-02 = 1 The bandwidth values quoted for these codecs are for the digitized speed in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. H.323 Extensions use the same codec setting as AspireNet. The codec is programmed against a Type (profile). Only one Type (profile) can be set up. The extension is then assigned to Type 1. 1. 2. Program the codec using the Audio Capability Priority option in Wizard Advanced Items/VoIP/Extensions/H.323 Extensions/H.323 Codec Setup (PRG84-12-28) Assign the Type number as 1 to the extension using the Codec Type option in Wizard Advanced Items/VoIP/Extensions/ H.323 Extensions/H.323 Extension Setup (PRG15-05-15)
Please be aware that this codec selection is only a preferred setting. It is possible that an H.323 extension will use one of the other available codecs depending on the destination of the coversation and also who was the originating party of the call.
Peer to Peer
Peer to Peer is not supported on H.323 extensions, this means that the RTP can not be sent directly between endpoints and the IPLA card must be involved in the communication.
SV8100
This also means that DSPs will be used for the duration of each call. If Peer to Peer is required then another device/protocol must be implemented (Standard SIP or iSIP).
105

By default any DTMF tones transmitted from an H.323 extension will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors on the IP network. DTMF relay is a way of converting the DTMF tone into a signal then sending the signal across the IP network instead of the actual tone. To use this feature both devices (SV8100 and the H.323 device) must support DTMF relay (RFC2833). To enable this feature set the DTMF Relay Mode option to RFC2833 in Wizard Advanced Items/VoIP/Extensions/H.323 Extensions/ H.323 Codec Setup (PRG84-12-31)
Fax Relay (T.38)

By default any Fax tones transmitted from an H.323 extension will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors on the IP network. Fax relay is a way of converting the Fax tones into a signal then sending the signal across the IP network instead of the actual tone. To use this feature both devices (SV8100 and the H.323 device) must support Fax relay (T.38). To enable this feature set the Fax Relay Mode option to Enabled in Wizard Advanced Items/VoIP/Extensions/H.323 Extensions/ H.323 Codec Setup (PRG84-12-32)
IP DECT
IP DECT is an NEC product that combines the functionality of traditional DECT with the flexibility of the Standard SIP protocol giving a robust and reliable wireless solution. The handsets use the traditional DECT protocol to communicate with the DECT Access Points (DAPs) and the DAPs use the Standard SIP Protocol to communicate with the SV8100. To run IP DECT extensions the SV8100 must have: CP00 IPLA IP DECT License(s).
General Information
IP DECT handsets are seen as Standard SIP extensions by the SV8100 so the registration process is the same. See the Standard SIP Extension page for more details. The SV8100 can support upto 512 IP DECT handsets (license dependant). One DAP can support upto 25 IP DECT registrations so multiple DAPs may be required even if the coverage area does not warrant it. One DAP will support upto 12 simultaneous calls. The AP200s DAPs can be powered by PoE 802.3af or by local mains power supply. The AP300 and AP300c can be only only be powered by 802.3af. IP DECT handsets can only use the G.711 codec. The supported IP DECT terminals are C124, G355, G955, i755 and M155.
IP DECT Configuration
All IP DECT configuration information is given on the IP DECT training course. No support can be provided if this course has not been followed by the installer. The IP DECT manuals can be found on the SV8100 Tech DVD.
License
The SV8100 requires licensing to allow the registration of IP DECT handsets. One license is required for each registration to the SV8100. If no license is available, the handset will fail to register. Up to 512 IP DECT licenses can be added. License Code: EU000080
106
SV8100
Networking Overview
The following networking protocols are supported by the SV8100: NetLink Proprietary connection of several systems to make one large distributed system. Very feature rich. SV8100 only. AspireNet Proprietary connection of several systems to make one large virtual system with a unified numbering plan. Feature rich. SV8100 and Aspire can be connected. System Feature Networking This is another name for AspireNet (see above) and will be referred to as AspireNet in this manual. K-CCIS Proprietary connection of several systems to make one large virtual system with a unified numbering plan. Feature rich. SV8100 only. SIP Networking Standards based (RFC 3261) connection of any system that supports the SIP protocol (compatibility testing may be required) H.323 Networking Standards based (ITU-T) connection of any system that supports the H.323 (version 3) protocol (compatibility testing may be required)
All the above networking protocols are only supported over an IP connection.
NetLink
NetLink provides a seamless connection, using an IP network, to join multiple SV8100 communication servers into what would appear to be a single communications server. With a unified numbering plan, users can access any extension in the network as if they were in the same location. NetLink differs from other networking protocols because all slots, trunk ports and station ports belong to, and are controlled by, the Primary system. This makes the numbering plan and trunk routing much simpler. NetLink allows the connection of up to 16 systems, each must have a unique Node ID. Each system in the network must have: CP00 ME50 IPL Although 16 systems can be connected together, the maximum number of station and trunk ports is limited to the maximum for one system. This is due to the fact that all stations and trunks are allocated ports from the Primary system. NetLink can control a maximum of 240 slots (including CP00's). This may reduce the maximum number of nodes in the network depending on the number of slots used per node. From Release 4 software it is possible to register a SIP MLT to any node in a NetLink environment. Please refer to the SIP MLT section for further information.
NetLink Wizard Programming

Wizard Advanced Items/VoIP/Networking/NetLink
NetLink Primary Settings

Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Primary Settings NetLink System ID - Used to assign all systems in the network with a unique node ID (1 50). (PRG51-01-01) Primary Candidate Priority - Used to assign the Primary Candidate Priority. The number the system uses to elect the Primary System. (1 being the highest priority) (PRG51-01-02) Primary System Selection Method - The method used for electing the Primary System. (PRG51-01-03) IP Address The IP address of the system which is nominated as the Primary when the Primary System Selection Method is set to Top Priority Primary System. (PRG51-04-01)
SV8100
107
Automatic IP Address List Update Controls whether to update the NetLink Systems list automatically or not. (PRG51-13-01) Time Zone Method Controls which features are adjusted to the correct time zone for a specific node. (PRG51-13-02) MAC Address Authorization If this is enabled, the system will check the MAC address of a system before allowing it to connect to the NetLink network. (PRG51-13-03)
NetLink Systems
Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Systems IP Address A list of IP addresses of each node in the network. (PRG51-03) Name - Used to give a name to each node in the network. (PRG51-02-01) Time Zone Hour - Used to set the time zone hour of where the particular node is located. (PRG51-02-02) Time Zone Minute - Used to set the time zone minute of where the particular node is located. (PRG51-02-03) MAC Address - Used to assign the MAC address of the node. Can be used to allow or deny connection to the network. (PRG51-0204)
NetLink Replication
Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Replication Automated Primary System Integration - Used to enable Automated Primary System Integration. When enabled, if the Primary System is available, it will take control of the NetLink network automatically. (PRG51-06-01) System Package Reset Method - Used to control whether the system waits for all cards to be idle before resetting or anytime (even if calls are in progress) after automatic integration. (PRG51-06-02) Enforced Primary System Integration - Used to allow or deny the ability to force Primary System Integration (by programming command). (PRG51-07-01) System Package Reset Method - Used to control whether the system waits for all cards to be idle before resetting or anytime (even if calls are in progress) after enforced integration. (PRG51-07-02) Replication Mode This command controls whether Database Replication is done by time of day, by interval or disabled completely. (PRG51-16-01) Replication Time If the Replication Mode is set to Time Setting, this command tells the system to replicate the database at this time every day. (PRG51-16-02) Replication Interval If the Replication Mode is set to Interval, this command controls how often (in minutes) the database is replicated. (PRG51-16-03) Replication Timestamp This read only command displays the Date and Time of the last database replication event. (PRG51-1604) Replication Commencement Time This tells the system how long to wait (in seconds) after a new NetLink node has joined the network before replicating the database to it (if enabled). (PRG51-16-05) Node Replication Delay If there are multiple Secondary Systems in the network, this is the delay (in seconds) between the replication from the Primary System to each Secondary System. (PRG51-16-06) NetLink Fail-Over Limit If this number of Fail-Over conditions is met within one hour the systems will not automatically re-integrate, they will stay as standalone systems until either forced integration is used or the systems are reset. If this command is set to 0 the systems will always try to re-integrate regardless of the number of Fail-Over conditions. This command should be set to the required value on each node before the first NetLink integration occurs. (PRG51-18-01)
NetLink Timers
Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Timers This is a list of the timers used by NetLink. The only timer that should be changed from default is KeepAlive Waiting Response Time. It is recommended to set this timer to 20 seconds. (PRG51-05-02)
NetLink Codec
Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Codec NetLink can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPL card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for NetLink G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.726 32Kbps codec MOS 4.2 iLBC 13.33Kbps codec MOS 4.1 G.729 8Kbps codec MOS 4.0 G.723 5.3Kbps codec MOS 3.9 To enable either G.723 or iLBC set Codec Mode to G.723/iLBC in Wizard Advanced Items/VoIP/General Settings/VoIP Configuration/IPLA Basic Setup. (PRG84-27-02) The bandwidth values quoted for these codecs are for the digitized speech in one direction only. The actual bandwidth required for a
108
SV8100
call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. To change the codec in use in a NetLink network use the Audio Capability Priority setting in Wizard Advanced Items/VoIP/ Networking/NetLink/NetLink Codec
NetLink Information
Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Information These are read only commands where information about the NetLink network can be found. Primary Information Displays information about the Primary System. Node ID, IP address and MAC address etc. (PRG51-12) NetLink Systems Information Displays information about all nodes in the NetLink network. (PRG51-11) NetLink Remaining Slots Displays the number of remaining virtual slots. This number decreases every time a new card is installed from 240 down to Zero. When there are zero slots available no more cards can be installed.
NetLink TCP Ports

Wizard Advanced Items/VoIP/Networking/NetLink/NetLink TCP Ports This is a list of TCP ports used by the NetLink protocol. There is normally no need to change these, they are for information only. (PRG51-09)
NetLink DT700 Registrar Ports

Wizard Advanced Items/VoIP/Networking/NetLink/NetLink DT700 Registrar Ports This is a list of port numbers to define the Registrar and Session UDP port numbers on a per node basis. These are the port numbers that SIP MLT extensions use for registration and session communication. There is normally no need to change these from default. (PRG51-17)
Configuration Examples Example 1

The example below shows the basic programming required for a three node NetLink network. Each system is on a separate network. They are configured using the Top Priority Primary System method with system A being the preferred Primary System. Automatic Primary Integration is enabled and the NetLink keep alive timer is set to the recommended 20 seconds. No other advanced options are included here. System A 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 51-01-01 51-01-03 51-04-01 51-05-02 51-06-01 84-26-01 192.168.0.10 255.255.0.0 172.16.0.1 172.16.0.10 255.255.0.0 1 1 172.16.0.10 20 1 172.16.0.20 172.16.0.21 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 51-01-01 51-01-03 51-04-01 51-05-02 51-06-01 84-26-01 System B 192.168.0.10 255.255.0.0 172.17.0.1 172.17.0.10 255.255.0.0 2 1 172.16.0.10 20 1 172.17.0.20 172.17.0.21 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 51-01-01 51-01-03 51-04-01 51-05-02 51-06-01 84-26-01 System C 192.168.0.10 255.255.0.0 172.18.0.1 172.18.0.10 255.255.0.0 3 1 172.16.0.10 20 1 172.18.0.20 172.18.0.21
Additional programming may be required if there is a larger IPL installed With the above programming the systems will automatically integrate and the cards will be reset when they are idle. If the network is lost, the systems will revert to stand alone systems. System A (172.16.0.10) will always be the Primary System when the network is up. If Top Priority system is not available in the network, Primary System is elected by highest Primary Candidate Priority (lowest number). If this value is equal on all systems then the lowest Node ID will be elected as the Primary. After programming NetLink, on exiting programming you will be asked if you wish to reset the system. Always choose yes
SV8100
otherwise the NetLink programming may be lost.
109
Example 2
With the programming below the first system to be powered on will be the Primary System. This is because the systems are not set to look for a specific IP address to be the Primary and when the first system is powered on there are no other systems available to be the Primary. When the other two systems are powered on they do a search and find there is already a Primary System so they accept that. If the network is lost, the systems will revert to stand alone systems. When the network comes back up, nothing will change automatically, NetLink will not be operational. Enforced Primary Integration can be used (if enabled), or the Secondary systems can be reset to bring NetLink back up again.
System A 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 51-01-01 51-01-03 51-03-01 51-05-02 51-06-01 84-26-01 192.168.0.10 255.255.0.0 172.16.0.1 172.16.0.10 255.255.0.0 1 0 1 172.16.0.10 2 172.17.0.10 3 172.18.0.10 20 0 172.16.0.20 172.16.0.21 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 51-01-01 51-01-03 51-03-01 51-05-02 51-06-01 84-26-01
System B 192.168.0.10 255.255.0.0 172.17.0.1 172.17.0.10 255.255.0.0 2 0 1 172.16.0.10 2 172.17.0.10 3 172.18.0.10 20 0 172.17.0.20 172.17.0.21 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 51-01-01 51-01-03 51-03-01 51-05-02 51-06-01 84-26-01
System C 192.168.0.10 255.255.0.0 172.18.0.1 172.18.0.10 255.255.0.0 3 0 1 172.16.0.10 2 172.17.0.10 3 172.18.0.10 20 0 172.18.0.20 172.18.0.21
Additional programming may be required if there is a larger IPL installed Be aware that the above operation is not recommended as it is possible for the Primary System to move from one node to another if the Primary is reset.
Database Backup
Prior to setting up NetLink, a recovery database should be created for each system. This is used when you wish to remove a system from NetLink. From handset programming: Create recovery database PRG90-57 Restore recovery database PRG90-58 Delete recovery database PRG90-59 All recovery databases on a particular CP00 will be lost if the system is defaulted.
Remove a NetLink Node

If it is required to remove a NetLink node from the network it should be deleted from the Primary Systems database. From handset programming: Delete system information PRG51-14 The system must be disconnected from the network before this command is executed.
Handset Information
Pressing Feature 5 on a DT300 phone will show the following information about the system that the extension is connected to: IPL IP Address System ID Primary or Secondary Pressing Feature 5 on a DT700 phone will show the information from the system that it is registered to. On a DtermIP (Aspire) phone, press Check Hold 5 instead of Feature 5
110
SV8100
Recommendations
Use Top Priority Primary System rather than Dynamic for the Primary System Selection Method. Wizard Advanced Items/ VoIP/Networking/NetLink/NetLink Primary Settings (PRG51-01-03) Enable Automated Primary System Integration. Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Replication (PRG51-06-01) Set the Keep Alive Response Waiting Time to 20 seconds. Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Timers (PRG51-05-02) These settings will allow the nominated Primary System to take control of the NetLink network whenever it (and the network) is available. It will also allow the Secondary Systems to select another Primary System or operate as a standalone system if the original Primary is not available.
Asynchronous Settings
The following programming commands are not sent from the Primary System to the Secondary Systems when Database Replication occurs: PRG10-01, PRG10-02, PRG10-12, PRG10-13, PRG10-14, PRG10-15, PRG10-16, PRG10-45, PRG51-01, PRG90-01, PRG90-09.
SRAM Database
The information held in SRAM is not transferred to Secondary Systems. So if a Fail-Over situation occurs terminals may lose DND, Caller ID History, etc.
Considerations
Almost all features available at a single system are available via Net-Link. All IP trunks must register from Primary system. Centralised Voice Mail programming is not required because all extensions belong to the Primary system. If there is a Voice Mail installed at the Primary system, this will service all nodes as a local Voice Mail. InMail must be installed in the Primary system. LAN/WAN connection Is the IP connection between all systems suitable for NetLink. QoS NetLink signalling should have the highest priority possible followed by the speech data (RTP). The general data on the network should have the lowest priority or no priority.
Applications/Devices
Below is a list of applications or devices that would be affected if the Primary System changed to a different node, this is because the communication is between the device or application and the IP address of the Primary System or the hardware is installed in the Primary System: InMail IP extensions registered to the Primary system All IP Trunks SMDR/P Event Applications (MyCalls) CTI Applications (TAPI/OAI) Desktop Applications IP DECT AspireNet K-CCIS PMS
Licensing
All nodes in a NetLink network must be licensed except for the Primary System. The licenses for all Secondary Systems are loaded onto the Primary System CP00. E.g. If there is a ten node NetLink network, there must be a license for nine Secondary Systems loaded onto the Primary Systems CP00. In the event of a Fail-Over situation, the licenses from the original Primary System will be copied to the new Primary System for a maximum of seven days. After the seven days have elapsed, the licenses will be removed from the new Primary System so it is imperative that the original Primary System is restored to this role. License Code: BE107574
SV8100
111
Netlink Advanced Features

Fail-Over
An added feature of NetLink is the Fail-Over feature. If the Primary System is turned off or disconnected, without the Fail-Over feature, all communication servers would stop working. With Fail-Over, one of the Secondary Systems, depending on the SV8100 programming, will take over as the Primary System allowing the other linked nodes to continue functioning. Enable Fail-Over by changing KeepAlive Response Waiting Time in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Timers (PRG51-05-02) to 20 seconds.
Automated Primary System Integration

This feature allows the Primary System to always take back control of the network automatically after it has been unavailable. E.g. If the Primary System had a power failure, one of the Secondary Systems would take over as the Primary (if Fail-Over is enabled). Without this feature enabled, when the original Primary System comes back on line, it would continue to run as a Secondary. This operation may be undesireable, so, if Primary System Automatic Integration is enabled it would take over as the Primary System once it is back on line. It is enabled using Automated Primary System Integration in Wizard Advanced items/VoIP/Networking/NetLink/NetLink Replication. (PRG51-06-01) There is an option System Package Reset Method in Wizard Advanced items/VoIP/Networking/NetLink/NetLink Replication (PRG51-06-02) to wait until all cards are idle before the system resets or to do it immediately. Fail-Over must be enabled for this feature to work.
Enforced Primary Integration

If Automated Primary System Integration is not used (see above), it is possible to manually select a new Primary System by entering the IPLA IP address of the new Primary System into a programming command. This feature must be enabled in Wizard Advanced items/VoIP/Networking/NetLink/NetLink Replication. (PRG51-07-01) Enforced Primary Integration should only be used when Primary Candidate Priority is in use or when the the Top Priority System is unavailable. To change the Primary System, enter programming mode (handset only). Enter PRG51-08-01, type in the IPLA IP address of the system you wish to be the Primary and press Transfer. The system will reset and the change will take place.
Database Replication
Once NetLink is operational, the database can be replicated from the Primary system to the Secondary system(s). This database will be used if a Fail Over condition occurs. The database Replication can be done by time of day or by interval. This is controlled by the Replication options in Wizard Advanced items/VoIP/Networking/NetLink/NetLink Replication If Database Replication is not used and a Fail-Over condition occurs, the new Primary System will use the configuration that was stored in its own CP00 for the whole NetLink database. This means that the database is completely different from the original config.

By default any DTMF tones transmitted across NetLink will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. DTMF relay is a way of converting the DTMF tone into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the DTMF Relay Mode option to RFC2833 in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Codec. (PRG84-25-31)
Fax Relay (T.38)

By default any Fax tones transmitted across NetLink will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression.
112
SV8100
Fax relay is a way of converting the Fax tones into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the Fax Relay Mode option to Enabled in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Codec. (PRG84-25-32)
Time Zone Offset

This is used if one or more of the NetLink nodes are in a different time zone than the Primary System. Set the relavent Hours and minutes offset against each node in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Systems. (51-02-02/03) The following features can be adjusted to be in line with the Time Zone Offset: Time Display Incoming/Outgoing Call History VRS Time Announcement Date and Time Setting by Service Code Alarm Clock It is possible to select which features the Time Zone Offset is applied to. This is done using the Time Zone Method in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Primary Settings. (51-13-02)
MAC Address Authorization

The Primary System is able to reject a NetLink connection request if the MAC address of the requesting system does not match the MAC address set in system programming. Enable MAC Address Authorization in Wizard Advanced Items/VoIP/Networking/NetLink/NetLink Primary Settings. (51-13-03) Enter the MAC address to be authorised into the MAC Address item against the system number in Wizard Advanced Items/VoIP/ Networking/NetLink/NetLink Systems. (51-02-04) The MAC address can be seen by pressing Feature 3 on a display telephone on the system that wants to join the NetLink network.
Netlink DSP Zones

Description
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 packetised 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. A DSP is used on the system CP00 which has the call. For instance, when a trunk on System ID 2 uses a receiver, a DSP on System ID 2 is used. The Primary System must control DSP resources on the Secondary Systems but it cannot control all of them. There are five zones to handle DSP resources in NetLink. The zone number depends on the System ID number. In the same Zone, the communication servers must share the DSP resource number. For instance, if a user in System ID 1 is using DSP resource 1, resource 1 becomes busy in Zone 1 (System ID 1, 6, 11, 16, 21, 26, 31, 36, 41 and 46). Zone 1 2 3 4 5 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 System ID 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
SV8100
All nodes in the NetLink network follow the DSP Setting in Program 10-09 of the Primary System.
113
AspireNet
The SV8100 uses the IPL card or PRI card to connect multiple systems together over a Data Communication IP Network (Intranet). AspireNet is used to provide telephony services between the SV8100 and other SV8100s or Aspire systems. There can be up to 16 Nodes in an AspireNet Network. The station and trunk ports are allocated from the local CP00 so up to 512 extensions and 200 trunks can be connected to each Node depending on the licenses installed on each system. Each system in the network must have: CP00 IPL or PRI card ME50 AspireNet license(s) It is advisable to have compatible levels of system software installed on all systems within the Network. Although the basic AspireNet will operate correctly there could be problems with features that are only available from a given level of software.
AspireNet Wizard Programming

AspireNet IP Setup
Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Setup/AspireNet IP Setup IPL IP Address This is the signalling address of the SV8100s own IPL card (PRG10-12-09) IPL Subnet Mask This is the subnet mask of the SV8100s own ILP card (PRG10-12-10) Default Gateway This is the IP address of the default gateway on the SV8100s own network (PRG10-12-02) Subnet Mask This is the subnet mask of the default gateway on the SV8100s own network (PRG10-12-03) Networking System This is the TCP port that the SV8100 uses Fast Start This is a component of the H.323 protocol. This must be enabled for AspireNet
AspireNet address for Remote

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Setup/AspireNet address for Remote (PRG10-12-27) Against the Networking System ID (1 50) enter the IP address of the remote systems IPL or CPU
AspireNet VoIP card setup

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Setup/AspireNet VoIP card setup (PRG84-26) For each 16 DSP ports of the IPL card enter one IP address. E.g. for a 32 port IPL enter two IP addresses. For a 128 port IPL enter eight IP addresses. For the RTP and RTCP ports enter the starting port number for each IP address. Each DSP requires one RTP port and one RTCP port. Under normal circumstances there is no need to change these settings from default.
AspireNet ISDN setup

For configuration of the PRI card for AspireNet connection refer to the following wizard page: Wizard Blade Configuration/ISDN Port Setup/PRT Port Setup
ISDN Line Mode - Set to one of the three available NW mode as follows: 3 - NW Mode (Leased Line) 4 - NW Mode (Interconnected Line) (generally used if the connected systems are directly connected via a fixed cable) 5 - NW Mode (Interconnected Line), (Fixed Layer 1 Forced NT Mode) NW Mode (Leased Line) The ISDN interface is Slave mode and must receive a clock signal from the network. System connection diagram.
System 1 NW Leased --- Netw ork Termination Unit --BRI Leased Line --- Netw ork Termination Unit --System 2 NW Leased
114
Line Master side
SV8100
Line Slave side
Clock signal diagram.

System 1 Slave --- NTU (Clock signal generator) --BRI Leased Line --- NTU (Clock signal generator) --System 2 Slave
NW Mode (Interconnected Line) The ISDN interface is Slave mode at one end and Master mode at the other. The maximum length of the interconnected cable should not exceed 200 metres for PRI using CAT5 cable. System connection diagram.
System 1 NW Interconnected Line Master side System 2 NW Interconnected Line Slave side
------
Interconnected Line
------

System 1 Master (Clock signal generator) System 2 Slave
------
Interconnected Line
------
NW Mode (Interconnected Line, Layer 1=NT) The ISDN interface is Slave mode at one end and Master mode at the other. The Layer 1 of the ISDN interface is fixed at NT (Network Termination - Master mode). System connection diagram.
System 1 NW Interconnected Line Master side System 2 NW Interconnected Line Slave side
---Gatew ay---
Interconnected Line
---Gatew ay---

System 1 Clock signal generator System 2 Clock signal generator
---Gatew ay (Slave)---
---Interconnected Line---
---Gatew ay (Slave)---
NW Mode Master/Slave System - set one side of the PRI link to Master and the other to Slave NW Mode Networking System - The networking system ID number is used to select the access route for dialled digits. You can choose any number from 0 to 50. (0 equals no operation) The commands below are to set up the local and remote extension number ranges for each system. Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Numb ering Plan
System Numbering
Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Numb ering Plan/System Numb ering (PRG11-01) Set the relevant digits for the remote systems extension range to the correct length using 1st Dial Digit, 1st and 2nd Dial Digit and Dial Digit Length. Set the Type to be Networking System Access and the Networking ID should match the Networking System ID in AspireNet address for Remote.
Extension Numbers
Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Numb ering Plan/Extension Numb ers (PRG11-02) Assign extension numbers to port numbers for the local system
F-Route
Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Numb ering Plan/F-Route (PRG44-XX) Digits dialled by a user can be sent to the F-Route tables and specified as an AspireNet number by entering the Networked node ID (Trunk Group 101-150 correspond to Network IDs 1-50) as the target trunk group number, calls will be routed to the target system via the node ID specified. The dialled digits will then be analysed by the F-Route tables in the target system. At the target system the call will be analysed within F-Route for the following call types: Outgoing call to a trunk Extension access call (you must translate the dialled digits)
SV8100
115
Access to the other system via AspireNet No defined dial Alternate route selection is not available when the primary network route is busy. When all channels are busy the call will return busy tone.
Compared With Single System Configuration In a single system with F-Route used, the dialling is analysed when the call is initially dialled. Operation The operation is automatic once configured in F Route programming. The commands below are to allow extensions on one system use the trunks on another system to dial out. Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Remote Trunk Access
Trunk Group Routing For Extensions

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Remote Trunk Access/Trunk Group Routing For Extensions (21-02) Enter the Trunk Route Number (see below) per Night Service Mode against each extension.
Trunk Group Routing

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Remote Trunk Access/Trunk Group Routing (PRG14-06) Against the relevant Route Table enter the Trunk Group Number for access to the relevant remote system (Trunk Group 101-150 correspond to Network IDs 1-50).
AspireNet Incoming Trunk Access Route

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Remote Trunk Access/AspireNet Incoming Trunk Access Route (PRG21-16) This controls which local Trunk Route an incoming AspireNet call has access to for outgoing trunk calls. Set the Trunk Route on a per AspireNet Networking System ID.
AspireNet Busy Lamp Information

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Busy Lamp Information (PRG20-01-04) This is a timer that controls the frequency of Busy Lamp updates between AspireNet nodes. Enter a value (in 100ms increments) of how often the local system should send out BLF updates to all other systems in the network. 1 = 100ms, 5 = 500ms etc.
AspireNet Park Hold Operation

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Park Hold Operation (PRG24-03) Park Hold information is shared between all nodes in an AspireNet network so any user can pick up a Parked call from any system. In some circumstances this operation may be undesirable and each system may wish to see only its own Parked calls. To do this put all extensions from each system into its own Park Hold Group. E.g. put all extensions on System ID 1 into Park Group 1 and all extensions on System ID 2 into Park Group 2 etc.
Centralised Voicemail
Wizard Advanced Items/VoIP/Networking/AspireNet CVM/Centralised Voicemail (PRG45-XX) AspireNet will support the use of a single voicemail system for the entire network. A user may call into the voicemail from anywhere in the network and perform most functions as if the voicemail were located on their premises. Please see the Centralised Voicemail page for further details.
AspireNet Codec
Wizard Advanced Items/VoIP/Networking/AspireNet CVM/AspireNet Setup/AspireNet Codec setup AspireNet can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPLA card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for AspireNet G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.729 8Kbps codec MOS 4.0 G.723 5.3Kbps codec MOS 3.9 To enable either G.723 set Codec Mode to G.723/iLBC in Wizard Advanced Items/VoIP/General Settings/VoIP Configuration/IPLA Basic Setup. (PRG84-27-02)
116
SV8100
The bandwidth values quoted for these codecs are for the digitized speech in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. To change the codec in use in an AspireNet network use the Audio Capability Priority setting in Wizard Advanced Items/VoIP/ Networking/AspireNet CVM/AspireNet Setup/AspireNet Codec setup

By default any DTMF tones transmitted across AspireNet will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. DTMF relay is a way of converting the DTMF tone into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the DTMF Relay Mode option to RFC2833 in Wizard Advanced Items/VoIP/Networking/AspireNet CVM/ AspireNet Setup/AspireNet Codec setup. (PRG84-12-31)
Fax Relay
By default any Fax tones transmitted across AspireNet will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. Fax relay is a way of converting the Fax tones into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the Fax Relay Mode option to Enabled in Wizard Advanced Items/VoIP/Networking/AspireNet CVM/ AspireNet Setup/AspireNet Codec setup. (PRG84-12-32) Note: The SV8100 uses T.38 for its Fax Relay protocol but the Aspire uses a proprietary protocol. This means that Fax Relay cannot be used between the two systems. Node 1 SV8100 SV8100 Node 2 Aspire Fail Pass Pass Aspire Fail
Configuration Example
The examples below shows the basic programming required for an SV8100 AspireNet network. Each system is on a separate network. No other advanced options are included here. Example A This example shows the configuration necessary for an AspireNet over IP 3 node network. System A 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-27-01 192.168.0.10 255.255.0.0 172.16.0.1 172.16.0.10 255.255.0.0 ID 1 = 172.17.0.10 ID 2 = 172.18.0.10 1 = 3 Digit Type 2 2 = 3 Digit Type 8 ID 1 3 = 3 Digit Type 8 ID 2 1XX 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-27-01 System B 192.168.0.10 255.255.0.0 172.17.0.1 172.17.0.10 255.255.0.0 ID 1 = 172.16.0.10 ID 2 = 172.18.0.10 1 = 3 Digit Type 8 ID 1 2 = 3 Digit Type 2 3 = 3 Digit Type 8 ID 2 2XX 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-27-01 System C 192.168.0.10 255.255.0.0 172.18.0.1 172.18.0.10 255.255.0.0 ID 1 = 172.16.0.10 ID 2 = 172.17.0.10 1 = 3 Digit Type 8 ID 1 2 = 3 Digit Type 8 ID 2 3 = 3 Digit Type 2 3XX
11-01 11-02
11-01 11-02
11-01 11-02
SV8100
84-26-01 172.16.0.20 172.16.0.21 84-26-01 172.17.0.20 172.17.0.21 84-26-01 172.18.0.20 172.18.0.21
117
Example B Each system must have a dedicated ISDN circuit for each AspireNet over ISDN connection. Therefore, for a system to connect to 2 different nodes via ISDN AspireNet 2 seperate PRI cards must be used. The example below describes connection to a single node. System A 10-03-01 10-03-10 10-03-11 11-01 11-02 4 = Network Mode Interconnected Line 1 = Master Network ID = 1 1 = 3 Digit Type 2 2 = 3 Digit Type 8 ID 1 1XX 10-03-01 10-03-10 10-03-10 11-01 11-02 System B 4 = Network Mode Interconnected Line 0 = Slave Network ID = 2 1 = 3 Digit Type 8 ID 2 2 = 3 Digit Type 2 2XX
Licensing
Each SV8100 need to be licensed to use AspireNet. One license gives that system the ability to use one channel for AspireNet. E.g. in the configuration example above, if each system needs the ability to have 4 concurrent conversations over AspireNet then each node must have four AspireNet licenses. Licence Code: BE107584
AspireNet Features
The following system features are available between systems that are networked using AspireNet.
Features Available via AspireNet

ARS/F-Route Barge In Busy Lamp Indication Call Forwarding Override Caller ID Display Call Forwarding: Immediately, Busy, No Answer, Both Ring Call Forwarding, Follow Me Call Forwarding, Off-Premise Call Waiting / Camp On Central Office Calls, Placing: Seizing a trunk in networked system Conference Department Calling Department Step Call Direct Dial In (DDI) Direct Inward Line (DIL) Direct Inward System Access (DISA) Hold DSS Console Intercom: Change Voice/Signal Ring Keep Alive Operation Last Number Redial Message Waiting Operator, Centralised Paging Park
118
Ringdown Extension, Internal/External (Hotline) Selectable Display Messaging Toll Restriction Transfer Voice Mail, Centralised
SV8100
ARS/F-Route
Digits dialled by a user can be sent to the F-Route tables and specified as a AspireNet number by entering the Networked node ID (Trunk Group 101-150 correspond to Network IDs 1-50) as the target trunk group number, calls will be routed to the target system via the node ID specified. The dialled digits will then be analysed by the F-Route tables in the target system. At the target system the call will be analysed within F-Route for the following call types: Outgoing call to a trunk Extension access call (you must translate the dialled digits) Access to the other system via AspireNet No defined dial Alternate route selection is not available when the primary network route is busy. When all channels are busy the call will return busy tone. Compared With Single System Configuration In a single system with F-Route used, the dialling is analysed when the call is initially dialled. Operation The operation is automatic once configured in F-Route programming.
Barge In
Barge In is available in the Networking feature with the following options: Barge into a conversation between an extensions own system and a networked system Barge into a conversation between callers in a networked system Barge into a call between two networked systems Barge In can be used in either Monitor Mode (Silent Monitor) or Speech Mode depending on system programming Barge In cannot barge into calls across the network in the following instances: Conference calls Off hook signalling a telephone in the other system
Operation To Barge In after calling a busy extension: (An analogue trunk call must be set up for 10 seconds before you can Barge In). Listen for busy/ring or busy tone. 1. Dial Barge In service code 810 OR 2. Press Barge In key (SC 851: 34).
Call Forwarding
Call Forwarding Immediate / Busy / No Answer / Busy-No Answer / Both Ring options are available with the Networking feature. With a networked system, when Call Forwarding enabled, there is a slight difference in the telephones display. With a single system, the extension name is displayed on the extension which has Call Forwarding. With a networked system, the extension number is displayed. Operation To activate or cancel Call Forwarding: 1. Press Speaker (or lift handset) + Dial 888. Also allowed are 848 (Call Forward Immediate), 843 (Call Forward Busy), 845 (Call Forward No Answer, 844 (Call Forward, Busy/No Answer, or 842 (Call Forward Both Ring). OR Press Call Forwarding key (SC 851: code 16). 2. Dial Call Forwarding condition: 1 = Personal Answering Machine Emulation (then skip to step 4 - refer also to Voice Mail). 2 = Busy or not answered 4 = Immediate 6 = Not answered 7 = Immediate with simultaneous ringing (not for Voice Mail)
SV8100
0 = Cancel 3. Dial destination extension, Voice Mail master number or press Voice Mail key. 4. Dial Call Forwarding type: 2 = All calls 3 = Outside calls only 4 = Intercom calls only When you enable Call Forwarding, your Call Forwarding key flashes slowly. If you dont have a Call Forwarding key, DND flashes slowly. OR 1. Press Call Forwarding key. SC 851: code 10 for Forward All Calls Immediately SC 851: code 11 for Forward when Busy SC 851: code 12 for Forward when Unanswered SC 851: code 13 for Forward Busy/No Answer SC 851: code 14 for Forward with Both Ringing SC 851: code 15 for Follow Me SC 851: code 16 for Forward to Station (forward type is selected at the time the option is set by the user) SC 851: code 17 for Forward to Device 2. Dial 1 plus extension to enable; dial 0 to disable. Once you activate Call Forwarding, only your Call Forwarding destination can place an Intercom call to you. 3. Dial destination extension, Voice Mail master number or press Voice Mail key. Youll hear stutter dial tone when placing a new call.
119
Call Forwarding / Do Not Disturb Override

The extension user may be able to call an extension which has Call Forwarding or Do Not Disturb set.
Operation To override an extensions Call Forwarding or Do Not Disturb: 1. Call the forwarded or DND extension. 2. Dial Call Forward / DND Override service code 807 OR 3. Press Override key (SC 851: 37).
Call Forward, Off-Premise

Off-Premise Call Forwarding allows an extension user to forward their calls to an off-site location. This feature works the same in a networked system as it does in a single system. A call to an extension at a remote system will forward to the Abbreviated Dial bin using a trunk at the remote system.
Operation To activate Call Forwarding Off-Premise 1. At system phone, press Speaker + Dial Call Forward Service Code (848, 843, 844, 845). OR Press Call Forward key (SC 851: 10, 11, 13 or 12) OR At an SLT, lift handset Dial 848, 843, 844 or 845. 2. Dial 1. 3. Dial the Abbreviated Dial Bin number (000 to 999) which your calls should be forwarded. 4. Press SPK (or hang up at SLT) to hang up. Your DND and Call Forwarding Programmable Function Key flashes. To cancel Call Forwarding Off-Premise 1. At system phone, press idle CALL key + Dial 848, 843, 844 or 845. OR Press Call Forward key (SC 851: 10, 11, 13 or 12) OR At an SLT, lift handset and dial 848, 843, 844 or 845. 2. Dial 0. 3. Press SPK (or hang up at SLT) to hang up. Your DND or Call Forwarding Programmable Function Key stops flashing.
120
SV8100
Call Forwarding with Follow Me

The extension user can program Call Forward Follow-Me to extension in a networked system. When the extension with the Follow Me setting receives an incoming call, both the original extension and the programmed destination extension starts ringing. With a networked system, when Call Forward Follow-Me is enabled, there is a slight difference in the telephones display. With a single system, the destination extension displays the extension name for the phone with Follow-Me enabled. With a networked system, the extension number is displayed.
Operation To activate Call Forward Follow Me: 1. At a system phone other than your own, press Speaker and dial 888. OR Press Call Forward (Station) key (SC 851: 15). OR At an SLT other than your own, lift handset and dial 888. 2. Dial 3 + Dial your own extension number (i.e., the source). 3. Dial Call Forwarding Type: 2 = All Calls 3 = Outside calls only 4 = Intercom calls only 4. SPK (or hang up at SLT) if you dialled 888 in step 1. Your Call Forwarding (Station) Programmable Function Key flashes when Call Forwarding is activated. To cancel Call Forward Follow Me: 1. At system phone, press Speaker and dial 888. OR Press Call Forward (Station) key (SC 851: 15). OR At an SLT, lift handset and dial 888. 2. Dial 0. 3. SPK (or hang up at SLT) if you dialled 888 in step 1. Your Call Forwarding (Station) Programmable Function Key goes out.
Camp On
With Camp On, an extension user may call a busy extension and wait in line (Camp-On) without hanging up. The call goes through when the busy extension becomes free. Camp On helps extension users to get through as soon as a busy extension becomes free. It also lets callers wait in line for a busy extension without being forgotten. When you have set Camp-On you can choose to wait off hook or go on hook. If you go on hook your phone will ring when the extension becomes free. With a networked system, camping on to an idle extension and Trunk Queuing/Camp On for a trunk port are not supported. With a networked system, when Camp On is enabled, there is a slight difference in the telephones display. With a single system, the target extensions name is displayed on the phone which has enabled Call Waiting. With a networked system, the extension number is displayed.
Operation To Camp-On to a busy extension: 1. Call busy extension. 1. Dial Camp-On service code 850 OR 2. Press Camp-On key (SC 851: 35). 3. You can choose to hang up or not. To cancel a Camp-On request: 1. Hang up. 2. At system phone, press Speaker and dial 870. OR At system phone, press Camp-On key (SC 851: 35). OR At single line set, lift handset and dial 870.
Caller ID Display
Caller ID information can be sent to the target extension in a networked system and show the Caller ID on the phones display. The Abbreviated Dial Name is also shown on LCD by searching Abbreviated Dial Table at the target system.
SV8100
121
Operation A DDI call routed directly to a remote extension will send the Caller ID information to the remote system. The DDI name set in the system programming is also sent to the remote system. At the remote system the Caller ID information will be displayed or, if the Caller ID number matches an Abbreviated Dial entry the Abbreviated Dial name will be displayed. A trunk call that is first answered and then transferred to a remote extension will display the Caller ID number and the DDI name. The Abbreviated Dial name will NOT be displayed.
Central Office Calls, Placing: Seizing a trunk in a networked system

The system allows a user to seize a trunk in a networked system using the following methods: Trunk Route Access (Dial trunk access code). F-Route (F-Route seizes a trunk at another system). The following are not available: Specified Trunk Access (805 + trunk number). Specified Trunk Group Access (804 + Trunk Group number). Operation The operation is automatic, the user dials the trunk access code in the normal way. Abbreviated Dial numbers will follow the trunk routing if set to TRG 0. For AspireNet ensure that the VOIPU trunk ports are in their own trunk group, do not create a trunk group with a mix of VOIP trunk ports and any other trunk port type. VOIP trunk ports should not be seized directly via line keys or trunk access (SC 9, 805 or 804).
Conference
The user can create a Conference call to include a user in a networked system. Operation To establish a Conference: Keyphone 1. Establish Intercom or trunk call. 2. Press CONF or Conference key (SC 851: 07) or press HOLD and dial 826. 3. Dial extension you want to add. OR Access outside call OR Retrieve call from Park orbit. To get the outside call, you can either press a line key or dial a trunk/trunk group code. You can optionally go back to step 2 to add more parties to your Conference. 4. When called party answers, press CONF or Conference key twice or HOLD key twice. If you cannot add additional parties to your Conference, you have exceeded the systems Conference limit. 5. Repeat steps 2-4 to add more parties. Single Line Telephone 1. Establish Intercom or trunk call. 2. Single Line Set Hook flash and dial 826. 3. Dial extension you want to add. OR Access trunk call. OR Retrieve call from Park orbit. 4. Hook flash and repeat step 3 to add more parties. OR Hook flash twice to set up the Conference. If you cannot add additional parties to your Conference, you have exceeded the systems Conference limit.
Department Calling
Department Group access is available via Networking. When the extension at System A tries to make a Department Call to System B, System A should have a numbering plan which defines the Department Access code at System B. The following Department Calling options are supported with the Networking feature. Department Calling Cycle Department Routing When Busy
122
SV8100
The following options are not available Hunting Mode No All Ring Mode 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 and 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. STG Withdraw Mode Call Recall Restriction for STG Maximum Queuing Number Enhanced Hunting Mode Operation 1. When dialling the Department access code for the networked system, the call is dialled in the same way as normal.
Department Step Call

After calling a busy Department Calling Group member in a networked system, an extension user can have Department Step Calling Quickly call another member in the group. Operation To make a Step Call: You step through Extensions within a Group. 1. Place call to busy Department Group member. OR Place call to Department Group pilot number. 2. Press Step Call key (SC 851: 36). 3. Repeat step 2 to call other Department Group members.
Direct Inward Dialling (DDI)

An incoming DDI call can be routed to an extension in a networked system. Operation For incoming DDI calls, the system uses DDI programming to determine how to route the call. If the extension number is determined to be in the networked system, the call will be routed to the appropriate system node. It is possible to route to a Department Group Pilot number at a remote system. It is not possible to route a DDI call to an IRG at the remote system. The timer values are determined at the system for the incoming trunk.
Direct Inward Line (DIL)

A Direct Inward Line (DIL) is a trunk that rings an extension, virtual extension or Department Group directly. The DIL trunk can call an extension at a networked system, if the DIL trunk is set to route to an extension number at the other system. Operation 1. An outside caller places a call to a DIL trunk. 2. The call will be routed to the networked system if the DIL target is defined as an extension at another system.
Direct Inward System Access (DISA)

Networking allows DISA callers to place a call to an extension in a networked system. Some system features can also be accessed from the networked system. The Class of Service is determined by the password entered by the DISA caller. The password table is referred to by the system on the incoming trunk side. The Networking feature allows the following DISA Class of Service Options. Trunk Route Access Operator access External Paging The following are not available. Trunk Group Access Common Abbreviated dialling Internal Paging Specified trunk access Forced trunk disconnect Call Forward setting Break In
SV8100
123
Operation To place a DISA call into the system: 1. Dial the telephone number that rings the DISA trunk. 2. Wait for the DISA trunk to automatically answer with a unique dial tone. 3. Dial the optional 6-digit DISA password. 4. Wait for a second unique dial tone (if password was required). 5. Dial an extension number. OR Dial 9 for Trunk Group Routing or ARS. OR Dial Alternate Trunk Route Access Code (if enabled). OR Dial 805 + a trunk number (1-200) for an outside call. OR Dial 0 for the operator. OR Dial 803 + an External Paging Zone number (1-8 or 0 for All Call). If the received digits are analysed as a networked extension number, the call is routed to the appropriate system within the network.
Hold
This feature is available with no changes in programming or operation. The MOH tone is sourced at the local system where the caller is hearing the hold tone. For example a user at System A places a call to system B and puts the call on hold, the MOH source at system B will be heard by the held user. Whilst the caller is on hold the network speech path will be reserved, waiting for the call to be taken off hold.
Direct Station Selection (DSS)

An extension user can have a DSS key to a networked extension. The DSS console keys can display the status lamp indication of an extension in a networked system. The key will show the status for idle, busy, DND set and Call Forward Immediate set. Lamp status may not be updated immediately. Status will be updated in the time interval specified in system programming, this setting should be consistent at all connected sites. The status for ACD extensions or Virtual extensions will not be sent via AspireNet. It is still possible to have a DSS key for an ACD or Virtual extension but it will not show any BLF information, the key can only be used to call the extension. The basic status for a Hotel extension is sent via AspireNet e.g. idle, busy, DND set, Call forward set. The Hotel room status is not sent e.g. check in/out, room status etc. Operation To Set a Function Key to your Hotline partner: 1. Press Speaker to go off hook. 2. Dial service code 851. 3. Press Hotline key + partners extension number + HOLD. To place a call to your Hotline partner: 1. Press Hotline key You can optionally lift handset after this step for privacy. To transfer your outside call to your Hotline partner: 1. Press Hotline key. 2. Announce call and press the Transfer button. OR Press Transfer to have the call wait at your Hotline partner unannounced. If unanswered, the call recalls like a regular transferred call. To answer a call from your Hotline partner: 1. If you hear two beeps, speak toward phone. OR 2. If your telephone rings, lift handset. Calling an extension from your 110 button DSS Console: 1. Press EXT.1 or EXT.2 to select the range. 2. Press DSS Console key. If the call voice-announces, you can make it ring by dialling 1. If you dont have Handsfree, you must lift handset to speak.
124
SV8100
Intercom
An extension user can make an intercom call to a networked system if the networked extensions are defined in system programming. A user can change the signalling type for the intercom call they place to either a voice announce or ringing call when calling an extension in a networked system. Operation To place an Intercom call: 1. At system phone, press Speaker. OR At single line telephone, lift handset. 2. Dial extension number (or 0 for your operator). Your call may voice-announce or ring the called extension. Dial 1 to change the way your call alerts the called extension. If the extension you call is busy or doesnt answer, you can dial another extension without hanging up.
Keep Alive Operation

The Keep Alive operation will check that the distant end is available. A message is sent that the distant end must respond to, if no response is received the line will be taken out of service. Operation The response to the keep alive message is automatic. The generation of the keep alive message is set in system programming. If the timer is set to 0 the keep alive generation is turned off. The retry count for a keep alive message that is not responded to is also set at the originating system. The line will be placed back in service when the line is active and a keep alive message is responded to. The keep alive operation will only take place if the message is sent and not responded to by the distant end, if the message is not sent (for example if the Ethernet cables are unplugged from the system) then the keep alive operation will not take place. When the keep alive operation occurs the link will be taken out of service: Any calls that are in progress will be released. Park Hold orbits will be released. No further Park Hold information will be sent until the link is active.
Last Number Redial

Last Number Redial allows an extension user to quickly redial the last number dialled. When used with a networked system, the system can use the same trunk route on which the call was originally placed, even if the trunk is a trunk in another system. Operation To redial your last call: 1. Without lifting the handset, press Redial. The last dialled number is displayed. 2. To redial the last number, press #. OR Search for the desired number from the Redial List by pressing the LND or VOLUME UP or VOLUME DOWN keys. 3. Lift the handset or press Speaker to place the call. The system automatically selects a trunk from the same group as your original call and dials the last number dialled. OR 1. At system phone, press idle line key (optional). The system automatically selects a trunk from the same group as your original call. 2. Press Redial. OR 1. At system phone, press Speaker. OR At single line telephone, lift handset. 2. Dial 816. The system automatically selects a trunk from the same group as your original call and dials the last number dialled.
Message Waiting
This feature can be used when placing an intercom call to a networked extension and you receive either no answer or a busy tone. With a networked system, when a Message Waiting has been left, there is a difference in the telephones display. With a single system, the extensions name which left the message is displayed. With a networked system, the extension number is displayed. Operation To leave a Message Waiting: 1. Call busy or unanswered extension.
SV8100
2. Dial the Message Waiting service code 841 OR 3. Press Message Waiting key (SC 851: 38) 4. Hang up. With keyphones, the MW LED lights.
125
To answer a Message Waiting: At keyphones when you have a message your MW LED flashes fast. 1. At a keyphone, press Speaker and dial 841. OR Press Message Waiting key (SC 851: 38). OR At single line telephones, lift the handset and dial 841. Normally, your MW LED goes out. If it continues to flash, you may have new messages in your Voice Mail mailbox or a new General Message.
Operator, Centralised
It is possible to have a centralised network operator extension that can be dialled with the operator access code (0). Calls to the operator will be queued and answered in order. Up to 32 calls can be queued at the operator extension. The quantity of network calls that can queue at the operator may be limited by the quantity of networking channels available. Operation The network numbering plan must be set up to route the operator access code (0) to the system that has the operator extension. The operator extension must be set in system programming. If the operators extension is connected to system A the following settings are required: At System A the required extension must be set as the operator extension. At system A dial 0 must be set as Operator. At system B dial 0 must be set as Networking System Access and routed to the node ID of System A. Users at System A and B can access the operator by dialling 0.
Paging
An extension user can make internal or external pages to a networked system. Paging to a networked system can only be activated by dialling a service code and the target networks system ID. Operation To Make an Internal Page 1. Dial 801. 2. Dial # and the system ID (01 to 50). The system ID must be dialled as 2 digits (ex: #02). 3. Dial the Paging Zone number (00-64). Dialling 00 calls All Call Internal Paging. 4. Make announcement to the networked system. 5. Press SPK to hang up. To Make an External Page 1. Dial 803. 2. Dial # and the system ID. The system ID must be dialled as 2 digits (ex: #02). 3. Dial the Paging Zone number (0-9). Dialling 0 calls All Call External Paging. 4. Make announcement to the networked system. 5. Press SPK to hang up. To Make a Combined Page 1. Dial 751. 2. Dial # and the system ID. The system ID must be dialled as 2 digits (ex: #02). 3. Dial the Paging Zone number (0-9). Dialling 0 calls All Call Combined Paging. 4. Make announcement to the networked system. 5. Press SPK to hang up.
Park
Park places a call in a waiting state (called a Park Orbit) so that an extension user may pick it up.
126
SV8100
Any extension user who is in the same Park Group as the extension which placed the call in Park can answer the call. This includes extension users in a networked system. For example, when an extension user in Park Group 3 within System A places a call in Park, the extension users in Park Group 3 at any connected system can retrieve the call by pressing the flashing park key or dialling a service code. If you do not want the park hold orbits to be available to other users within the network then place the extension at each site in a different park hold group. With a single system, when two users within the same Park Group try to place a call in the same park orbit at the same time, one user will get the orbit while the other users call will either ring back or it will remain an active call, depending on how the park orbit was accessed. With AspireNet, if both users try to access the same orbit, one user will get the orbit, while the other will hear ring back, at which time they can park the call in a different orbit. Operation To Park a call in a system orbit: You can Park Intercom or trunk calls. 1. Press Park key (SC 852: *04 + orbit). The Park key LED lights. If you hear busy tone, the orbit is busy. Try another orbit. 2. Use Paging to announce call. 3. Press SPK to hang up. If not picked up, the call will recall to you. OR 1. At system phone or 2-Button telephone, press HOLD. OR At a SLT single line telephone, hook flash. 2. Dial 831 and the Park orbit (1-64). If you hear busy tone, the orbit is busy. Try another orbit. 3. Use Paging to announce call. 4. Press SPK to hang up. If not picked up, the call will recall to you. Note: The parked call recalls after the Park Hold Timer. To pick up a parked call: 1. Lift handset. 2. Press Park key (SC 852: *04 + orbit). OR 1. At system phone or 2-Button telephone, press idle CALL key. OR At single line telephone, lift handset. 2. Dial 861 and the Park orbit (1-64).
Ringdown Extension, Internal/External (Hotline)

A networked system can have a phone defined as a Ringdown Extension to dial either an internal or external number. Operation To place a call if your extension has ringdown programmed: 1. Lift handset. If you want to place a trunk call, press a line key before lifting the handset. Depending on the setting of your ringdown timer, you may be able to dial an Intercom call before your ringdown goes through. If the destination has Handsfree Answerback enabled, your call will voice announce. If the destination has Forced Intercom Ringing enabled, your call will ring.
Selectable Display Messaging

An extension user can select a pre-programmed Selectable Display Message for their extension. This message will be displayed on an incoming intercom callers keyphone display when they call the extension in a networked system. Operation To select a message: 1. Press Speaker + dial 713. OR Press Call Forward (Device) key (SC 851: 17). OR Press Speaker + press Text Message key (SC 851: 18) + enter digits to append, if needed + Speaker to hang up. Skip the remaining steps.
SV8100
2. Dial 3 + Message number (01-20). Use VOL UP or VOL DOWN to scroll through the messages. 3. (Optional for messages 1-8 and 10) Dial the digits you want to append to the message. You can append messages 1-8 and 10 with digits (e.g., the time when you will be back). You enter the time in 24-hour format, but it displays in 12-hour format. 4. Press Speaker to hang up. To cancel a message: 1. Press Speaker + dial 713. OR Press Call Forward (Device) key (SC 851: 17). OR Press Speaker+ press Text Message key (SC 851: 18) + Speaker to hang up. 2. Dial 3. 3. Press Speaker to hang up.
127
Toll Restriction
Toll Restriction limits the numbers an extension user may dial. When accessing a trunk at another system the Toll Restriction Class of Service is defined by the calling extensions system, but the Toll Restriction tables will be used from the system which has the outgoing trunk. The Toll restriction class number is sent to the other system, the other system will use the class number to define the Toll Restriction tables to use. Since the restriction table is used for the system which has the outgoing trunk, the definition of the Class of Service may be different, unless all Toll Restriction Classes of Service and Toll Restriction Tables are defined the same between systems. Operation Example: The extension user in System A, which has a Toll Restriction Class 2, dials an outside party after seizing a trunk from a networked system (System B). The dialled digits are compared to the Class 2 Restriction Table in System B. The call is then either allowed or rejected based on this table.
Transfer
The following types of Transfer are available with Networking: Screened Transfer Unscreened Transfer Transfer to busy extension Operation Transferring Trunk Calls To Transfer a trunk call to a co-workers extension: 1. At system phone or 2-Button telephone, press HOLD. OR At a single line telephone, hook flash. You hear Transfer dial tone. 2. Dial co-workers extension number. If the extension is busy or doesnt answer, you can dial another extension number or press the line key to return to the call. SLT users can retrieve the call by pressing hook flash. If a call has been transferred and the SLT user has hung up the handset, the call be can retrieved by dialling 715 and the extension number to which it had been transferred. 3. Announce call and hang up. If you dont have Automatic On Hook Transfer, you must press CONF or your Transfer Programmable Function Key to Transfer the call. If your co-worker doesnt want the call, press the flashing line key to return to the call. SLT users can retrieve the call by pressing hook flash. If a call has been transferred and the SLT user has hung up the handset, the call be can retrieved by dialling 815 and the extension number to which it had been transferred. If you dont want to screen the call, hang up without making an announcement. Transferring to a b usy extension Will require the Transfer to Busy Extension option enabled in system programming at the originating system and the target system. 1. Dial the co-workers extension number. Busy tone is heard. 2. Press the Transfer button. 3. The call will wait for the busy co-worker to become free and then will ring. Transferring Intercom Calls To Transfer your Intercom call:
128
SV8100
1. At system phone, press HOLD. OR At single line telephone, hook flash. 2. Dial extension to receive your call. If the extension is busy, doesnt answer or does not want the call, you can dial another extension number or press the lit CALL key to return to the call. In addition, you may be able to transfer the call to the busy extension. SLT users can retrieve the call by pressing hook flash. If a call has been transferred and the SLT user has hung up the handset, the call be can retrieved by dialling 715 and the extension number to which it had been transferred. 3. Announce your call and hang up. With Automatic On Hook Transfer When you hang up, the call is automatically transferred. Without Automatic On Hook Transfer You must press your Transfer Programmable Function Key to Transfer the call. To Transfer the call unscreened, press your Transfer Programmable Function Key and hang up without making an announcement.
Centralised Voice Mail

AspireNet will support the use of a single voicemail system for the entire network. A user may call into the voicemail from anywhere in the network and perform most functions as if the voicemail were located on their premises.
Supported Configurations
If the AspireNet network consists entirely of SV8100 systems then the Centralised Voicemail can be provided by: InMail UM8000 External Voicemail If the AspireNet network has a mix of SV8100 systems and Aspire systems the Centralised Voicemail must be provided by one of the Aspire systems using: AspireMail DMS FMSU VMSU External Voicemail
Centralised Voice Mail Wizard Programming

Wizard Advanced Items/VoIP/Networking/AspireNet CVM/Centralised Voicemail Department Group Assignment Wizard Advanced Items/VoIP/Networking/AspireNet CVM/Centralised Voicemail/Department Group Assignment Department Group Set the Voice Mail ports into the relevant Department Group e.g.64 (PRG16-02) Terminal Type Set the Voice Mail ports to Special (PRG15-03-03) Centralised Voicemail Setup Voice Mail Department Group - This must be set to 0 otherwise the voice mail will not operate as a Centralised Voice Mail. (PRG4501-01) Centralised Voice Mail Pilot - Enter the Pilot Number that a user at any system within the network can dial to access to Centralised Voice Mail. Note - The pilot number must be within the network numbering plan. (PRG45-01-07) This setting must be the same at all systems within the network. Centralised Voice Mail Department group - Enter the Department group number that contains the InMail ports or SLIU ports connected to the voice mail system. (You should also ensure that this Department group does not have a pilot number assigned in Department Group Options). This setting is not required at any system(s) within the network that do not have the Centralised Voice Mail installed. (PRG45-01-08) Centralised Voice Mail Master Name - Give the Centralised Voice Mail a name that will be shown at the display keyphone while accessing the voice mail. (PRG45-01-09) NSL Protocol - Required for softkey integration. (PRG45-01-10) Centralised Voice Mail Type - Required to be set to 'retro' if InMail used for voicemail. (PRG45-01-19)
SV8100
129
Node 1 (VM Installed) Department Group Assignment Voice Mail Department Group Department Group Pilot Number Centralised Voice Mail Pilot Centralised Voice Mail Department Group Numbering Plan Group 64 Department Group Assignment
Node 2 None
Voice Mail Department Group Department Group Pilot Number Centralised Voice Mail Pilot Centralised Voice Mail Department Group Numbering Plan
None
Group 64 = 0
None
600
600
64
None
Dial 6XX = Extension
Dial 6XX = Networking System Access
SIP Trunking
SIP (Session Initiation Protocol) is a protocol used for Voice over IP. It is defined by the IETF (Internet Engineering Task Force) in RFC3261. The SV8100 can use SIP to connect to another SV8100 system, an Aspire, an XN120 or a third party SIP enabled product. SIP can also be used to provide external trunks to the SV8100 from ITSPs (Internet Telephony Service Providers). The SV8100 must be certified to connect to a particular ITSP or PBX, there is a list of certified carriers available, please refer to your support partner for more information. From the SV8100s point of view there are two types of SIP Trunks, Networking Mode and Carrier Mode. Each system in the network must have: CP00 IPL IP Trunk License(s)
Networking Mode
This mode is usually used to connect to other NEC systems (SV8100, Aspire, XN120) using SIP although some SIP Carriers use this mode to provide external SIP Trunks. The systems connect to each other using an internal routing table. The call is always attempted even if the remote end point is down. Each system does not know the state of the other because there is no registration procedure. If this method is used to connect to an ITSP, the customers public IP address will be used as a security measure.
Carrier Mode
This mode is usually used to connect the SV8100 to an ITSP to provide external SIP Trunks. The SV8100 uses the customers internet connection to register to the ITSPs SIP server (although some ITSPs provide a dedicated circuit just for voice). The SV8100 registers to the ITSP using a User ID and Password for security, this registration is constantly maintained. If the registration is lost the trunk ports will return busy tone allowing an overflow trunk group to be utilised.
130
SV8100
Network Address Translation (NAT)

NAT will cause a problem for SIP Trunks if the SV8100 has been assigned private IP addresses. The problem is that the SV8100s IP address is embedded in the SIP signalling messages which cannot be manipulated by the NAT router. The NAT router can only change the IP header information. When an outgoing packet arrives at a SIP server, the SIP server reads the SV8100 IP address from the SIP information which will be an internal private IP address. This address is not routable on the Internet resulting in communication problems. This problem is resolved by entering the public IP address in the SIP signalling messages instead of the private IP address. This is done by enabling the NAPT Router option and entering the Public IP address of the router using NAPT Router IP Address in - Wizard Advanced Items/VoIP/General Settings/IP Addressing/CCPU IP Network Setup. (PRG10-12-06/07) Port forwarding will also be required in the customers router. Forward the SIP Signalling port (default UDP/5060) to the IPL IP address. Forward the RTP port range (default UDP/10020 -> 10275 (depending on IPL size)) to the VoIP Gateway IP addresses. Port Forwarding Example (Default Settings) Port Number (UDP) 5060 10020 10051 10052 10083 10084 10115 10116 10147 10148 10179 10180 10211 10212 10243 10244 10275 Destination IP Address (IPLA) 172.16.0.10 172.16.0.20 172.16.0.21 172.16.0.22 172.16.0.23 172.16.0.24 172.16.0.25 172.16.0.26 172.16.0.27 Description (IPLA) IPL (Signalling) VoIP Gateway 1 (RTP) VoIP Gateway 2 (RTP) VoIP Gateway 3 (RTP) VoIP Gateway 4 (RTP) VoIP Gateway 5 (RTP) VoIP Gateway 6 (RTP) VoIP Gateway 7 (RTP) VoIP Gateway 8 (RTP) Destination IP Address (IPLB) 172.16.0.10 172.16.0.20 172.16.0.20 172.16.0.20 172.16.0.20 172.16.0.20 172.16.0.20 172.16.0.20 172.16.0.20 IPLB only uses one IP address so all RTP/ RTCP ports should forward to the same IP address Description (IPLB) IPL (Signalling)
SIP Trunk Codec

Wizard Advanced Items/VoIP/Networking/SIP Networking/Codec Setup SIP Trunks can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPLA card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for SIP Trunks G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.726 32Kbps codec MOS 4.2 iLBC 13.33Kbps codec MOS 4.1 G.729 8Kbps codec MOS 4.0 G.723 5.3Kbps codec MOS 3.9 To enable either G.723 set Codec Mode to G.723/iLBC in Wizard Advanced Items/VoIP/General Settings/VoIP Configuration/IPLA Basic Setup. (PRG84-27-02) The bandwidth values quoted for these codecs are for the digitized speech in one direction only. The actual bandwidth required for a
SV8100
131
call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. To change the codec in use for SIP Trunks network use the Audio Capability Priority setting in Wizard Advanced Items/VoIP/ Networking/SIP Networking/Codec Setup. (PRG84-13-28)

By default any DTMF tones transmitted across SIP Trunks will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. DTMF relay is a way of converting the DTMF tone into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the DTMF Relay Mode option to RFC2833 in Wizard Advanced Items/VoIP/Networking/SIP Networking/ Codec Setup. (PRG84-13-31)
T.38 Fax Relay

This is a new feature for Release 4 software. SIP Trunks now have the ability to communicate using the T.38 Fax Relay protocol. By default any Fax tones transmitted to or from a SIP Trunk will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. T.38 Fax Relay is a way of converting the Fax tones into a signal then sending the signal across the IP network where the signals are converted back to Fax tones. The SIP Carrier or Server must support T.38 for this to work. Enable Fax Relay by using the Fax Relay Mode option in Wizard Advanced Items/VoIP/Networking/SIP Networking/Codec Setup (PRG84-13-50). There are several other options to do with T.38 Fax relay that can also be found in Wizard Advanced Items/VoIP/Networking/SIP Networking/Codec Setup (PRG84-13-51 to 61), these commands would usually be left at the default settings but may occasionally need altering depending on the SIP Carrier/Server, fax machine and network connection.
SIP Certificate of Compatibility

All of the required information and programming commands for a particular SIP carrier can be found on the relevant SIP Certificate of Compatibility, please refer to your support partner for access to these documents.
Licensing
Each SV8100 need to be licensed to use IP Trunks. One license gives that system the ability to use one IP Trunk. Up to 128 IP Trunk licenses can be added. Licence Code: BE107582
Multiple SIP Carriers

Description
This allows the systems to register or connect to several different SIP Carriers or SIP servers. This means that SIP trunks can be used in multiple locations. This also means that the DSP consumption can be reduced when a SIP trunk is used by an extension on a Secondary system. This feature can only be used when NetLink is deployed. If NetLink is not deployed only one SIP carrier can be configured. The number of SIP carriers available depends on the number of NetLink nodes up to a maximum of 16. This can be a combination of Carrier Mode and Networking Mode. Each node can only have one SIP Carrier configured. Existing operation (Previous to R5)
132
SV8100
New Operation (R5 onwards)
Requirements SV8100 R5 32/64/128IPL ME50 (required for NetLink) SIP Trunk License(s) R5 advanced feature license
SV8100
Capacity Up to 200 SIP trunks can be configured across the NetLink network.
133
Configuration Certain commands must be programmed on the Primary system and some commands must be programmed on the relevant Secondary system. The table below shows which commands should be programmed where. To program a Secondary system PC Pro or Web Pro must be used by connecting directly to the specific CP00. Programming Command 10-03 10-12 10-19 10-23 10-26 10-28 10-29 10-30 10-36 10-37 10-40 14-12 15-16 21-17 21-19 84-09 84-10 84-13 84-14 84-16 84-26 84-27 90-10 Note: X X X X X X X X X X X Program Primary Only Program each Secondary Replication (if enabled) X X X X
Certain command settings may be removed when NetLink is first configured if SIP trunks are already enabled. Be sure to check all SIP trunk programming after configuring NetLink. The order of programming SIP trunks and NetLink are shown in the following table.
134
SV8100
Example Configuration The following programming details use the diagram below for SIP Trunk information (NetLink programming is not listed)
SV8100
135
Primary System 10-12-01 10-12-02 10-12-03 10-12-06 10-12-07 10-12-09 10-12-10 10-28-01 10-28-02 10-28-04 10-28-05 10-29-03 10-29-05 10-29-06 10-30-02 10-30-03 10-40-01 10-40-04 192.168.0.10 255.255.0.0 172.16.0.1 Enable 20.20.20.1 172.16.0.10 255.255.0.0 com aaa.sip 1111 Domain name 10.10.10.1 Manual 10.10.10.1 1111 1111 Enable 4 10-12-01 10-12-02 10-12-03 10-12-06 10-12-07 10-12-09 10-12-10 10-28-01 10-28-02 10-28-04 10-28-05 10-29-03 10-29-05 10-29-06 10-30-02 10-30-03 10-40-01 10-40-04
Secondary System 192.168.0.10 255.255.0.0 172.16.1.1 Enable 20.20.20.2 172.16.1.10 255.255.0.0 com bbb.sip 2222 Domain name 10.10.10.2 Manual 10.10.10.2 2222 2222 Enable 4
136
84-26-01 172.16.0.20
SV8100
84-26-01 172.16.1.20
SIP Register ID
32 Register IDs can be programmed on each NetLink system that has SIP Trunks configured. Register ID 0 uses the User ID programmed in PRG10-28-04 and PRG10-30-02/03. Register ID 1 to 31 uses the User IDs programmed in PRG10-36. Trunks SIP Register IDs for trunks can only be applied to trunks that belong to the same system as the Register ID. Stations SIP Register IDs for Stations will only be applied when dialling out on a trunk from the Primary system. If a station dials out using a trunk on a Secondary system the Station Register ID is not applied. Alarms SIP Trunk problems can be indicated on the PC Pro alarm report and on the display of a handset (if configured). The information below details the alarms from the DIM (alminfo), PC Pro will also show similar information:
The information below details the alarms shown on a display telephone (this may differ slightly depending on the size of the display): Register Time Out Error Format NetLink Disabled NetLink Enabled Register Error Format NetLink Disabled NetLink Enabled ###:SIP(XX) REG FAILED($$$) ###:SIP(XX) REG NG($$$) -%% Key ###:Alarm number (60) XX:Register ID (1-32) $$$:Err code (000-999) %% System ID (1-16) Terminal LCD Example 60:SIP(07) REG FAILED(403) 60:SIP(07) REG NG(403) -02 Key Terminal LCD Example 60:SIP(05) REG REQ TIMEOUT 60:SIP(05) REG TIMEOUT -02
###:SIP(XX) REG REQ TIMEOUT ###:Alarm number(60) XX:Register ID(1-32) %%:System ID(1-16) ###:SIP(XX) REG TIMEOUT -%%
Register Authentication Error Format NetLink Disabled NetLink Enabled ###:SIP(XX) AUTH FAILED($$$) ###:SIP(XX) AUTH NG($$$) -%% Key ###:Alarm number (60) XX:Register ID (1-32) $$$:Error code (000-999) %% System ID(1-16) Terminal LCD Example 60:SIP(20) AUTH FAILED(401) 60:SIP(20) AUTH NG(401) -02
SV8100
137
Comments It is not possible to program a Secondary system via handset programming when NetLink is operational. SIP trunk port numbers are assigned from the next available port number (the same as current operation). Previous assignments of SIP Trunk ports may be disabled when NetLink is first configured. The total number of SIP trunks assigned to all systems in the NetLink network must not exceed the number of licenses installed on the Primary system. If the number of trunk ports exceeds the number of licenses then the SIP trunks will fail to be assigned port numbers. Any node in NetLink can use the SIP trunks on its own node or on any other node (depending on system programming).
SIP Trunks - Carrier Mode

All information about a specific SIP carrier can be found on the relevant SIP Certificate of Compatibility. The information below gives general information about programming SIP Trunks Carrier Mode.
SIP Trunk Wizard Programming

Wizard Advanced Items/IP SIP/SIP Trunks Enable IP Trunk Availability and select the required number of SIP trunk ports using IP Trunk Port Count in Wizard Advanced Items/IP SIP/SIP Trunks/ SIP Trunk Assignment (PRG10-40) Set the Trunk Type to SIP in Wizard Advanced Items/IP SIP/SIP Trunks/VoIP Trunk Type (PRG10-03) Set the trunk Incoming Type as required (usually DID) for each Trunk Port and Mode Number in Wizard Advanced Items/IP SIP/SIP Trunks/Incoming Type VoIP) (PRG22-02) Carrier Mode IP Address Wizard Advanced Items/IP SIP/SIP Trunks/Carrier Mode/Carrier Mode IP Address Use this set of commands if the ITSP has provided you with an IP address for their SIP server rather than a DNS address. Domain Name This is part of the SV8100s SIP ID which must be set to be able to communicate using SIP Trunks. This may be provided by the ITSP. (PRG10-28-01) Host Name This is part of the SV8100s SIP ID which must be set to be able to communicate using SIP Trunks. This may be provided by the ITSP. (PRG10-28-02) User ID This is the Username (or User ID) that is supplied by the ITSP. It is part of the authentication details. This is usually the same as the Username. (PRG10-28-04) Domain Assignment This item tells the system whether an IP address or DNS address will be used to register to the SIP Server. Set to IP Address. (PRG10-28-05) IP Trunk Port Binding This item is used to tie a specific SIP account to a trunk port number. (PRG10-28-06) Outbound Default Proxy and Inbound Default Proxy These items indicate whether a Proxy Server will be used for the outgoing and incoming calls. Calls may be restricted only to/from the specified address. (PRG10-29-01/02) Default Proxy Address This is the IP address of the SIP Server where the outgoing calls will be routed to. (PRG10-29-03) Default Proxy Port This is the UDP port number that is used on the ITSPs SIP Server. (PRG10-29-04) Register Mode This switches the system between Networking Mode and Carrier Mode. For Carrier Mode use Manual. (PRG10-2905) Registrar IP Address This is the IP address of the ITSP that the SV8100 will register to. This is usually the same as the Default Proxy Address. (PRG10-29-06) Registrar Port This is the UDP port number that is used on the ITSPs SIP Registrar. (PRG10-29-07) SIP Carrier Choice This defines the layout of the SIP messages, mainly for CLI purposes. (PRG10-29-14) Username This is the Username (or User ID) that is supplied by the ITSP. It is part of the authentication details. (PRG10-30-02) Password This is the password that is supplied by the ITSP. It is part of the authentication details. (PRG10-30-03) Audio Capability Priority This is the preferred codec for the SIP Trunk call. It is possible that this codec is not used depending on the settings of the ITSP. (PRG84-13-28) DTMF Payload Number This value is used when DTMF Relay is enabled. The ITSP and the SV8100 must have equal values. If this is not the case, a common equal value will be negotiated. (PRG84-13-31) DTMF Relay Mode This item is to enable or disable DTMF Relay. To use DTMF Relay set to RFC2833. (PRG84-13-32)
Carrier Mode DNS Wizard Advanced Items/IP SIP/SIP Trunks/Carrier Mode/Carrier Mode DNS Use this set of commands if the ITSP has provided you with a DNS address for their SIP server rather than an IP address.
138
SV8100
Domain Name This is part of the SV8100s SIP ID which must be set to be able to communicate using SIP Trunks. This may be provided by the ITSP. (PRG10-28-01) Host Name This is part of the SV8100s SIP ID which must be set to be able to communicate using SIP Trunks. This may be provided by the ITSP. (PRG10-28-02) User ID This is the Username (or User ID) that is supplied by the ITSP. It is part of the authentication details. This is usually the same as the Username. (PRG10-28-04) Domain Assignment This item tells the system whether an IP address or DNS address will be used to register to the SIP Server. Set to Domain Name. (PRG10-28-05) IP Trunk Port Binding This item is used to tie a specific SIP account to a trunk port number. (PRG10-28-06) Outbound Default Proxy and Inbound Default Proxy These items indicate whether a Proxy Server will be used for the outgoing and incoming calls. Calls may be restricted only to/from the specified address. (PRG10-29-01/02) Default Proxy Port This is the UDP port number that is used on the ITSPs SIP Server. (PRG10-29-04) Register Mode This switches the system between Networking Mode and Carrier Mode. For Carrier Mode use Manual. (PRG10-2905) Registrar Port This is the UDP port number that is used on the ITSPs SIP Registrar. (PRG10-29-07) DNS Mode When using Carrier Mode DNS this item must be enabled. (PRG10-29-08) DNS IP Address Enter the IP address of the customers (or ISPs) DNS server. (PRG10-29-09) DNS Port This is the port number used by the customers (or ISPs) DNS server. (PRG10-29-10) Registrar Domain Name Enter the Fully Qualified Domain Name address of the ITSPs SIP registrar server. (PRG10-29-11) Proxy Domain Name Enter the Domain Name part of the ITSPs SIP server. (PRG10-29-12) Proxy Host Name Enter the Host Name part of the ITSPs SIP server. Together with the Proxy Domain Name will make up the Fully Qualified Domain Name address of the SIP server. (PRG10-29-13) SIP Carrier Choice This defines the layout of the SIP messages, mainly for CLI purposes. (PRG10-29-14) DNS Source Port This is the source port number of the customers (or ISPs) DNS server. (PRG10-29-17) Username This is the Username (or User ID) that is supplied by the ITSP. It is part of the authentication details. (PRG10-30-02) Password This is the password that is supplied by the ITSP. It is part of the authentication details. (PRG10-30-03) Audio Capability Priority This is the preferred codec for the SIP Trunk call. It is possible that this codec is not used depending on the settings of the ITSP. (PRG84-13-28) DTMF Payload Number This value is used when DTMF Relay is enabled. The ITSP and the SV8100 must have equal values. If this is not the case, a common equal value will be negotiated. (PRG84-13-31) DTMF Relay Mode This item is to enable or disable DTMF Relay. To use DTMF Relay set to RFC2833. (PRG84-13-32) Note: PRG10-29-16 (handset programming only), if enabled might cause the SV8100 to reject incoming SIP Trunk calls depending on other settings. If problems are experienced with incoming calls being rejected turn this item off.
Configuration Examples
The examples below are for general information only, they will not work for all SIP carriers. Please refer to the relevant SIP Certificate of Compatibility for specific information. Carrier Mode IP Address Command 10-12-01 10-12-02 10-12-03 10-12-06 10-12-07 10-12-09 10-12-10 10-28-01 10-28-02 10-28-04 10-28-05 Entry 192.168.0.10 255.255.0.0 172.16.0.1 Enabled <Public IP Address> 172.16.0.10 255.255.0.0 NEC SV8100 <User ID supplied by ITSP> IP Address
SV8100
10-29-01 10-29-02 10-29-03 10-29-05 10-29-06 10-30-02 10-30-03 10-40-01 10-40-02 10-03 Enabled Enabled <ITSP IP Address> Manual <ITSP IP Address> <User ID supplied by ITSP> <Password supplied by ITSP> Enabled 4 ports Set IP Trunk Ports to SIP VoIP Gateway 1 = 172.16.0.20 84-26 VoIP Gateway 2 = 172.16.0.21
139
Carrier Mode DNS Command 10-12-01 10-12-02 10-12-03 10-12-06 10-12-07 10-12-09 10-12-10 10-28-01 10-28-02 10-28-04 10-28-05 10-29-01 10-29-02 10-29-03 10-29-05 10-29-08 Entry 192.168.0.10 255.255.0.0 172.16.0.1 Enabled <Public IP Address> 172.16.0.10 255.255.0.0 NEC SV8100 <User ID supplied by ITSP> Domain Name Enabled Enabled <ITSP IP Address> Manual Enabled
140
10-29-09 10-29-11 10-29-12 10-29-13 10-30-02 10-30-03 10-40-01 10-40-02 10-03
SV8100
<DNS Server IP Address> <ITSP FQDN Address> <ITSP Domain Address> <ITSP Host Address> <User ID supplied by ITSP> <Password supplied by ITSP> Enabled 4 ports Set IP Trunk Ports to SIP VoIP Gateway 1 = 172.16.0.20 84-26 VoIP Gateway 2 = 172.16.0.21
SIP Trunks - Networking Mode

All information about a specific SIP carrier can be found on the relevant SIP Certificate of Compatibility. The information below gives general information about programming SIP Trunks Networking Mode.
SIP Trunk Wizard Programming

Wizard Advanced Items/IP SIP/SIP Trunks Enable IP Trunk Availability and select the required number of SIP trunk ports using IP Trunk Port Count in Wizard Advanced Items/IP SIP/SIP Trunks/ SIP Trunk Assignment (PRG10-40) Set the Trunk Type to SIP in Wizard Advanced Items/IP SIP/SIP Trunks/VoIP Trunk Type (PRG10-03) Set the trunk Incoming Type as required (usually DID) for each Trunk Port and Mode Number in Wizard Advanced Items/IP SIP/SIP Trunks/Incoming Type VoIP) (PRG22-02) For each remote system enable System Interconnection, enter the destination IP Address and the Dial number to reach the destination system in Wizard Advanced Items/IP SIP/SIP Trunks/Networking Mode/Networking Mode (PRG10-23) It is also required to set up the SIP ID of the local system. Enter the Domain Name, Host Name and User ID in Wizard Advanced Items/IP SIP/SIP Trunks/Networking Mode/ Networking Mode (PRG10-28). This command requires a system reboot. There are some optional items (SIP Carrier Choice, Audio Capability Priority, DTMF Payload Number and DTMF Relay Mode) available in Wizard Advanced Items/IP SIP/SIP Trunks/Networking Mode/ Networking Mode (PRG10-29-14, PRG84-13). Set these as required for the specific configuration. Some other general VoIP programming will also be required such as IPLA IP Address, Subnet Mask, Default Gateway and VoIP Resource IP Address. These can be programmed in Wizard Advanced Items/IP SIP/Blades (PRG10-12, PRG84-26)
The below configuration shows the programming required to connect three SV8100 systems together using SIP Trunks Networking Mode. This programming allows desk to desk dialling to/from each system but without any extra functions. System A System B System C
SV8100
10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-23-01 10-23-02 10-23-04 10-28-01 10-28-02 10-28-04 10-40-01 10-40-02 10-03 192.168.0.10 255.255.0.0 172.16.0.1 172.16.0.10 255.255.0.0 System 1 and 2 = Enabled System 1 = 172.17.0.10 System 2 = 172.18.0.10 System 1 = 2 System 1 = 3 SV8100 SystemA 100 Enabled 4 ports Slot 1 IP Trunk Ports = SIP 1 = 3 Digit Type 2 2 = 3 Digit Type 6 3 = 3 Digit Type 6 1XX SIP trunk Ports = Group 20 Table 1 Dial = 2 Table 2 Dial = 3 Table 1 = FRoute Table 2 = FRoute Table 1 = 1 Table 2 = 2 Table 1 = TRK Group 20 Table 2 = TRK Group 20 172.16.0.20 172.16.0.21 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-23-01 10-23-02 10-23-04 10-28-01 10-28-02 10-28-04 10-40-01 10-40-02 10-03 192.168.0.10 255.255.0.0 172.17.0.1 172.17.0.10 255.255.0.0 System 1 and 2 = Enabled System 1 = 172.16.0.10 System 2 = 172.18.0.10 System 1 = 1 System 1 = 3 SV8100 SystemB 200 Enabled 4 ports Slot 1 IP Trunk Ports = SIP 1 = 3 Digit Type 6 2 = 3 Digit Type 2 3 = 3 Digit Type 6 2XX SIP trunk Ports = Group 20 Table 1 Dial = 1 Table 2 Dial = 3 Table 1 = FRoute Table 2 = FRoute Table 1 = 1 Table 2 = 2 Table 1 = TRK Group 20 Table 2 = TRK Group 20 172.17.0.20 172.17.0.21 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-23-01 10-23-02 10-23-04 10-28-01 10-28-02 10-28-04 10-40-01 10-40-02 10-03 192.168.0.10 255.255.0.0 172.18.0.1 172.18.0.10 255.255.0.0 System 1 and 2 = Enabled System 1 = 172.16.0.10 System 2 = 172.17.0.10 System 1 = 1 System 1 = 2 SV8100 SystemC 300 Enabled 4 ports Slot 1 IP Trunk Ports = SIP 1 = 3 Digit Type 6 2 = 3 Digit Type 6 3 = 3 Digit Type 2 3XX SIP trunk Ports = Group 20 Table 1 Dial = 1 Table 2 Dial = 2 Table 1 = FRoute Table 2 = FRoute Table 1 = 1 Table 2 = 2 Table 1 = TRK Group 20 Table 2 = TRK Group 20 172.18.0.20 172.18.0.21
141
11-01 11-02 14-05 44-02-01 44-02-02 44-02-03 44-05
11-01 11-02 14-05 44-02-01 44-02-02 44-02-03 44-05
11-01 11-02 14-05 44-02-01 44-02-02 44-02-03 44-05
84-26-01
84-26-01
84-26-01
The following extra programming allows the dialling extension to send its own extension number as CLI to the remote system. System A 10-29-14 Carrier B Enter the extension number as the Calling Party Number against each extension. 10-29-14 System B Carrier B Enter the extension number as the Calling Party Number against each extension. 10-29-14 System C Carrier B Enter the extension number as the Calling Party Number against each extension.
21-19
21-19
21-19
The following extra programming allows the incoming CLI from a remote system to be converted to name which will be displayed on the called partys display. System A Enter the remote extension numbers along with the remote users name System B Enter the remote extension numbers along with the remote users name System C Enter the remote extension numbers along with the remote users name
13-04
13-04
13-04
The following extra programming changes the Codec which is used between systems.
142
System A 84-27-02 84-13-28 G.723/iLBC* Choose from G.711, G.722, G.726, G.729, iLBC, G.723 84-27-02 84-13-28
SV8100
System B G.723/iLBC* Choose from G.711, G.722, G.726, G.729, iLBC, G.723 84-27-02 84-13-28 System C G.723/iLBC* Choose from G.711, G.722, G.726, G.729, iLBC, G.723
*This command only needs changing if it is required to use either the G.723 or iLBC codec. The following extra programming enables DTMF Relay (RFC2833). System A 84-13-32 RFC2833 84-13-32 System B RFC2833 84-13-32 System C RFC2833
K-CCIS
Description
IP trunk connections over CCIS Networking via IP are used to connect multiple systems together over a Data Communication IP Network (Intranet). Key-Common Channel Interoffice Signalling (K-CCIS) is used to provide telephony services between the SV8100 and another SV8100. The SV8100 uses the NEC proprietary CCIS Peer to Peer protocol over IP to communicate between systems. An IPL daughter board is required for connections between IP terminals and IP trunks. A maximum of one IPL daughter board can be accommodated per system with a maximum of 128 DSP Resources per system. Each system in the network must have: CP00 IPL IP Trunk license(s)
K-CCIS Wizard Programming

Wizard Advanced Items/VoIP/Networking/K-CCIS
K-CCIS Setup Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Assignment IP Trunk Port Availability Enable IP trunk ports (PRG10-40-01) CCISoIP Port Count Enter the required number of CCIS trunk ports (PRG10-40-04) Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS IP Setup IPL IP Address This is the signalling address of the SV8100s own IPL card (PRG10-12-09) IPL Subnet Mask This is the subnet mask of the SV8100s own ILP card (PRG10-12-10) Default Gateway This is the IP address of the default gateway on the SV8100s own network (PRG10-12-02) Subnet Mask This is the subnet mask of the default gateway on the SV8100s own network (PRG10-12-03) CCIS Availability Enable the availability of K-CCIS networking (PRG50-01-01) Point to Point Connection Enable the availability of K-CCIS Peer To Peer (PRG50-15-01) Server TCP Port This is the TCP port number used by the server side for K-CCIS (PRG50-15-02) Client TCP Port This is the TCP port number used by the client side for K-CCIS (PRG50-15-03) Connection Method for DT700 This enables peer to peer communication between DT700 extensions on different K-CCIS nodes (PRG50-15-04) Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS VoIP Card Setup (PRG84-26) For each 16 DSP ports of the IPLA card enter one IP address. E.g. for a 32 port IPLA enter two IP addresses. For a 128 port IPLA enter eight IP addresses. For an IPLB card only one address is required regardless of the number of DSPs. For the RTP and RTCP ports enter the starting port number for each IP address. Each DSP requires one RTP port and one RTCP port. Under normal circumstances there is no need to change these settings from default.
SV8100
Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Trunks (PRG10-03) This is a read only command which show which trunk port numbers have been assigned to the K-CCIS trunks Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Trunk Groups (PRG14-05) Assign a unique trunk group to the K-CCIS trunk ports and set them as Tie Line for the relevant mode of service Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Local ID (PRG50-02-03) Assign the Origination Point Code for Route ID 9 for the local SV8100 Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Remote ID (PRG50-03) Set the Destination Point Code and the IP Address of each remote node
143
Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Codec Setup (PRG84-21) K-CCIS can use various CODECs. A CODEC is a standard for converting an analogue signal to digital. This conversion process is handled by the DSP (Digital Signal Processors) on the IPLA card. Each CODEC has different voice quality and compression properties. The correct choice of CODEC will be based on the amount of bandwidth available, the amount of calls required and the voice quality required. Available Codecs for K-CCIS G.711 64Kbps codec MOS 4.4 G.722 64Kbps codec MOS 4.4 G.726 32Kbps codec MOS 4.2 iLBC 13.33Kbps codec MOS 4.1 G.729 8Kbps codec MOS 4.0 G.723 5.3Kbps codec MOS 3.9 To enable either G.723 set Codec Mode to G.723/iLBC in Wizard Advanced Items/VoIP/General Settings/VoIP Configuration/IPLA Basic Setup. (PRG84-27-02) The bandwidth values quoted for these codecs are for the digitized speech in one direction only. The actual bandwidth required for a call will depend on many other factors and will be much higher than these figures. The above MOS values are quoted for ideal network conditions. The value could be lower depending upon the network performance. It is possible to change the first and second priority codec in use in a K-CCIS network. Use the Audio Capability 1st Priority and Audio Capability 2nd Priority settings as required.
K-CCIS Numbering Plan Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Numb ering Plan/System Numb ering (PRG11-01) Assign local node digits as Extension Assign the remote node digits as F-Route Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Numb ering Plan/Extension Numb ers (PRG11-02) Assign the ports on the local node with extension numbers as required Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Numb ering Plan/F-Route (PRG44-XX) Use F-Route programming to route the required extension digits to the K-CCIS Trunk Group and to the relevant Destination Point Code. See the configuration example below.
K-CCIS Busy Lamp Field

K-CCIS can be programmed to send busy lamp field information to remote nodes. Up to 120 extensions can be set to send their BLF status information to up to 8 different nodes. The BLF updates can be sent at programmable intervals of 4, 8, 12 or 16 seconds. K-CCIS BLF Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS BLF/K-CCIS BLF Destination (PRG50-08) Set the Destination Point Code per Sending Group of which node the BLF information will be sent to Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS BLF/K-CCIS BLF Extensions (PRG50-09) Assign the extension numbers which wish to send their BLF status information and enable for the relevant Sending Group
144
SV8100
Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS BLF/K-CCIS BLF Timer (PRG50-10) Set the interval for when the BLF updates will be sent out to the destination nodes
K-CCIS Night Mode Switching Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Night Mode Switching It is possible to control the night mode switch of other nodes from a central location using K-CCIS. All nodes that are controlled centrally must use the same mode number. There can only be two modes when switching is controlled centrally. Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Night Mode Switching/K-CCIS Night Mode Destinations (PRG50-11) Enter the Destination Point code of the system to be controlled. Up to sixteen destination point codes can be entered Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Night Mode Switching/K-CCIS Night Switching Mode (PRG50-12) Enter the required mode settings for Day Mode and Night Mode
K-CCIS Misc Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Misc Link Reconnect This allows the system to drop redundant K-CCIS lines. E.g. If a K-CCIS call is transferred back to the originating system the K-CCIS links will be dropped. (PRG50-06-01) Centralized Day/Night Switching This allows the system to receive a signal to change the mode of service. (PRG50-06-02) CCIS Office Code This is the systems access code when using an open numbering plan. (PRG50-04-01) Maximum Hop Count This is the maximum number of hops (tandem systems) a call that is forwarded (Call Forward All Calls) can make. If the destination is via a sixth hop it will not be forwarded and will ring on the last extension. (PRG50-05-01) IAI Response Time This is the amount of time (in seconds) the system will wait for a response to a K-CCIS request. (PRG50-1301)

By default any DTMF tones transmitted across K-CCIS will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. DTMF relay is a way of converting the DTMF tone into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the DTMF Relay Mode option to RFC2833 or H.245 (all nodes should have the same setting) in Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Codec Setup (PRG84-21)
Fax Relay (T.38)

By default any Fax tones transmitted across K-CCIS will be sent as audio tones in the speech path. It is possible that these tones can be misinterpreted by the receiving device because of packet loss or errors due to the codec compression. Fax relay is a way of converting the Fax tones into a signal then sending the signal across the IP network instead of the actual tone. To enable this feature set the Fax Relay Mode option to Enabled in Wizard Advanced Items/VoIP/Networking/K-CCIS/K-CCIS Setup/K-CCIS Codec Setup (PRG84-21)
The example below shows the basic programming required for a three node SV8100 K-CCIS network with a closed numbering plan. Each system is on a separate network. No other advanced options are included here. System A 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-40-01 192.168.0.10 255.255.0.0 172.16.0.1 172.16.0.10 255.255.0.0 Enable 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-40-01 System B 192.168.0.10 255.255.0.0 172.17.0.1 172.17.0.10 255.255.0.0 Enable 10-12-01 10-12-02 10-12-03 10-12-09 10-12-10 10-40-01 System C 192.168.0.10 255.255.0.0 172.18.0.1 172.18.0.10 255.255.0.0 Enable
SV8100
10-40-04 11-01 11-02 14-05 22-02 44-02 44-05-01 44-05-09 44-05-10 50-01-01 50-02-03 50-03-01 50-03-03 84-26-01 CCIS Trunk Ports = Tie Line Dial 2 = FRoute, Data 1 Dial 3 = FRoute, Data 2 FRoute 1 = TRKGRP 20 FRoute 2 = TRKGRP 20 FRoute 1 = Digit 3 FRoute 2 = Digit 3 FRoute 1 = DPC 02 FRoute 2 = DPC 03 On Route ID 9 = 01 System ID 1 = DPC 02 System ID 2 = DPC 03 22-02 44-02 44-05-01 44-05-09 44-05-10 50-01-01 50-02-03 50-03-01 CCIS Trunk Ports = Tie Line Dial 1 = FRoute, Data 1 Dial 3 = FRoute, Data 2 FRoute 1 = TRKGRP 20 FRoute 2 = TRKGRP 20 FRoute 1 = Digit 3 FRoute 2 = Digit 3 FRoute 1 = DPC 01 FRoute 2 = DPC 03 On Route ID 9 = 02 System ID 1 = DPC 01 System ID 2 = DPC 03 22-02 44-02 44-05-01 44-05-09 44-05-10 50-01-01 50-02-03 50-03-01 50-03-03 84-26-01 CCIS Trunk Ports = Tie Line Dial 1 = FRoute, Data 1 Dial 2 = FRoute, Data 2 FRoute 1 = TRKGRP 20 FRoute 2 = TRKGRP 20 FRoute 1 = Digit 3 FRoute 2 = Digit 3 FRoute 1 = DPC 01 FRoute 2 = DPC 02 On Route ID 9 = 02 System ID 1 = DPC 01 System ID 2 = DPC 02 System ID 1 = 172.16.0.10 System ID 2 = 172.17.0.10 172.18.0.20 172.18.0.21* 4 1 = 3 Digit Type 2 2 = 3 Digit Type 6 3 = 3 Digit Type 6 1XX 10-40-04 11-01 11-02 4 1 = 3 Digit Type 6 2 = 3 Digit Type 2 3 = 3 Digit Type 6 2XX 10-40-04 11-01 11-02 4 1 = 3 Digit Type 6 2 = 3 Digit Type 6 3 = 3 Digit Type 2 3XX
145
System ID 1 = 172.17.0.10 System ID 1 = 172.16.0.10 50-03-03 System ID 2 = 172.18.0.10 System ID 2 = 172.18.0.10 172.16.0.20 172.16.0.21* 84-26-01 172.17.0.20 172.17.0.21*
*Only one IP address is required for this command if an IPLB is used instead of an IPLA.
Licensing
Each SV8100 need to be licensed to use IP Trunks for K-CCIS. One license gives that system the ability to use one IP Trunk. Each KCCIS node requires the relevant number of IP Trunk licenses. Up to 200 IP Trunk licenses can be added. Licence Code: BE107582
K-CCIS Features
The following system features are available between systems that are networked using K-CCIS.
Features Available via K-CCIS

Automatic Recall Brokerage Hotline Call Back (R5) Call Forwarding All Calls Call Forwarding Busy/No Answer Call Park Retrieve Call Transfer All Calls Calling Name Display Calling Number Display Calling Party Number Presentation from Station Centralised BLF Centralised Day/Night Mode Change Centralised E911
146
Dial Access to Attendant Direct Inward Dialling Dual Hold Elapsed Time Display Flexible Numbering of Stations Handsfree Answerback Hot Line Link Reconnect Multiple Call Forwarding All Calls Multiple Call Forwarding Busy/No Answer Paging Access Quick Transfer to Voice Mail Station-to-Station Calling Uniform Numbering Plan Voice Call Voice Mail, Centralised
SV8100
Automatic Recall K-CCIS

Feature Description This feature allows a call to be release transferred to another station in another office in the K-CCIS network and recall back to the originator of the transfer after a programmed time. System Availability All Terminals Required Components PZ-(X)IPL Operating Procedures Using a multiline terminal with a call in progress (Closed Numbering Plan): 1. Press Transfer. Internal dial tone is heard. The call is placed on Common Hold. 2. Dial the distant K-CCIS station number where the call is to be transferred. 3. Wait for the ringback tone. 4. Hang up. - OR 1. When the party answers, announce the transfer. 2. Restore the handset (transfer is completed). Using a multiline terminal with a call in progress (Open Numbering Plan): 1. Press Transfer, and receive internal dial tone. The call is placed on Common Hold. 2. Dial the trunk Access Code. 3. Dial the Office Code number. 4. Dial the distant K-CCIS station number where the call is to be transferred. 5. Wait for the ringback tone. 6. Hang up. Service Conditions If PRG 34-07-05 is left at default (30) the transferred call recalls to the station that performed the transfer when not answered. A UNIVERGE SV8100 station can receive a K-CCIS transferred call as a camp-on call if allowed by Class of Service. Restrictions: PRG 34-07-05 cannot be set based on a Timer Class of Service in PRG 20-31. Trunk-to-Trunk Transfer must be allowed in Program 14-01-13 (Trunk-to-Trunk Transfer Yes/No Selection). A blind transfer across a K-CCIS link cannot be completed until ringback tone is received at the transferring station. Related Feature List Link Reconnect K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS Call Transfer All Calls K-CCIS
SV8100
147
Brokerage Hotline K-CCIS

Feature Description This feature provides a ringdown connection between two stations, each using a multiline terminal, in different offices in the CCIS network. System Availability All Terminals Required Components: PZ-(X)IPL Operating Procedures To use this feature at any terminal: 1. Lift the handset or press Speaker. 2. Press the line/feature key associated with the pre-assigned station. 3. The destination station is automatically dialled, ring back tone is heard and the destination station answers. 4. After completion of conversation, hang up or press Speaker. To make another Brokerage-Hot Line-CCIS call immediately, press another line/ feature key without going on hook and off hook. Service Conditions Either multiline terminal in a Brokerage - Hot Line (K-CCIS) pair may transfer a Hot Line call to another station in the KCCIS network using the Call Transfer All Calls - (K-CCIS) feature. Restrictions: None Related Feature List Call Transfer All Calls - K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS
Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
Call Back K-CCIS

Feature Description This feature allows a station to set a Call Back after dialling across K-CCIS to a busy destination. The station that set the Call Back will receive a call as soon as the busy station becomes idle.
System Availability Terminal Type All Multiline Terminals
148
SV8100
Required Components PZ-(X)IPL R5 system software or later R5 advanced feature license
Operating Procedure To set Call Back K-CCIS from a multiline telephone (Closed Numbering Plan only): 1. Call destination extension number (across K-CCIS), busy tone is heard. 2. Calling party presses Camp On/Call Back Function Key. 3. Calling Party hangs up and waits for Call Back.
Service Conditions Restrictions This feature can only be set or received by a Multiline Terminal. This feature is only supported using a closed numbering plan. This feature can only be set by pressing a programmable key, soft key or service code is not supported. This feature can only be set when the calling party hears busy tone from the called party. The calling party must hang up after setting the Call Back. K-CCIS Trunks must be available on both systems for the operation to be successful. One terminal can set one Call Back. One system can have a maximum of 50 Call Back/Camp On reservations at the same time. Any Call Backs that are set will be removed by a system reset. One extension can receive Call Back settings from multiple extensions. In this case the ring back will occur in the order they were set. If the Call Back destination has a Call Forward set the operation is as follows: o o If the Call Forward destination is an internal extension Call Back will be established to the Call Forward destination. If the Call Forward destination is another system or trunk Call Back will not be established.
Related Feature List Station-to-Station Calling K-CCIS Uniform Numbering Plan
Guide to Feature Programming This guide provides a list of associated Programs that support this feature. PRG15-07 (Code: 35). PRG20-01-07 Camp On Extension Call Back Time. PRG20-01-09 Camp On Cancel Time. PRG20-13-35 Block Camp On.
Call Forwarding All Calls K-CCIS

Feature Description This feature allows all calls destined for a particular station to be routed to another station or to an Attendant, in another office in the
SV8100
K-CCIS network, regardless of the status (busy or idle) of the called station. The activation and cancellation of this feature may be accomplished by either the station user or an Attendant position if allowed by Class of Service (COS). Attendant Positions can be used to cancel Call Forward All Call system-wide. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components PZ-(X)IPL Operating Procedures To set Call Forward All Calls K-CCIS from a multiline telephone (Closed Numbering plan): 1. Press the Call Forward All ON/OFF key. 2. Dial 1 to set, then enter the remote K-CCIS station number. 3. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 848 (default), then 1 to set. 3. Dial the remote K-CCIS station number. 4. Restore handset or press Speaker. To set Call Forward All Calls K-CCIS from a Multiline Telephone (Open Numbering Plan): 1. Press the Call Forward All ON/OFF key. 2. Dial 1 to set. 3. Dial the trunk Access Code. 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Restore handset or press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 848 (default), then 1 to set. 3. Dial the trunk Access Code. 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Restore handset or press Speaker. To cancel Call Forward All Calls K-CCIS from a Multiline Telephone: 1. Press Call Forward All ON/OFF key. 2. Dial 0 to cancel. 3. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 848(default), then dial 0. 3. Restore the handset or press Speaker. Service Conditions General: Any station or Call Arrival (CAR) key can be set for Call Forwarding All Calls K-CCIS.
149
Restrictions: Call Forward Off-Premise must be allowed in PRG 20-11-12 (Class of Service External Call Forward) to set call forwarding to a remote K-CCIS station number. Trunk-to-Trunk Transfer must be allowed in PRG 14-01-13 (Trunk-to-Trunk Transfer Yes/No Selection). A Single Line Telephone user can transfer a trunk call to another internal station that is set for Call Forwarding All Calls K-CCIS, however, when the distant party answers the call, a conference cannot be established. The destination station in the distant system is the only station that can call a station with Call Forwarding All Calls KCCIS set. Call Forwarding with Both Ringing (All Calls) is not supported. Call Forward Split Internal/External is not supported. Forwarding to Voice Mail is not included in the Maximum Hop Count. Call Forward continues to operate to a MLT that has been removed. Related Feature List Call Forwarding Busy/No Answer K-CCIS
150
SV8100
Multiple Call Forwarding All Calls K-CCIS Multiple Call Forwarding Busy/No Answer K-CCIS Link Reconnect K-CCIS Uniform Numbering Plan K-CCIS
Call Forwarding Busy/No Answer K-CCIS

Feature Description This feature permits a call to a Busy or unanswered station to be forwarded to another station or an Attendant, in another office in the K-CCIS network. The activation and cancellation of this feature may be accomplished by either the station user or an Attendant position, if allowed by Class of Service (COS). For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL
SV8100
Operating Procedures To set Call Forward Busy/No Answer K-CCIS from a Multiline Telephone (Closed Numbering Plan): 1. Press the Call Forward Busy/No Answer ON/OFF key. 2. Dial 1 to set. 3. Dial the remote K-CCIS station number. 4. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 844 (default), then 1 to set. 3. Dial the remote K-CCIS station number. 4. Restore handset or press Speaker. To set Call Forward Busy/No Answer - K-CCIS from a Multiline Telephone (Open Numbering Plan): 1. Press the Call Forward Busy/No Answer ON/OFF key. 2. Dial 1 to set 3. Dial the trunk Access Code. 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 844 (default), then Dial 1 to set. 3. Dial the trunk Access Code. 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Restore handset or press Speaker. To cancel Call Forward Busy/No Answer K-CCIS from a Multiline Telephone: 1. Press Call Forward Busy/No Answer On/Off key. 2. Dial 0 to cancel. 3. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 844 (default), then Dial 0 to cancel. 3. Restore handset or press Speaker. Service Conditions General: Any station or Call Arrival (CAR) key can be set for Call Forwarding Busy/No Answer K-CCIS.
151
Restrictions: Call Forward Off-Premise must be allowed in Class of Service (PRG 20-11-12) External Call forward to set call forwarding to a remote K-CCIS station number. Trunk-to-Trunk Transfer must be allowed in PRG 14-01-13 for each trunk (Trunk-to-Trunk Transfer Yes/No Selection). A Single Line Telephone user can transfer a trunk call to another internal station that is set for Call Forwarding All Calls - KCCIS, however, when the distant party answers the call, a conference cannot be established. The destination station in the distant systems is the only station that can call a station with Call Forwarding All Calls KCCIS set. Call Forwarding with Both Ringing (All Calls) is not supported. Call Forward Split Internal/External is not supported. Forwarding to Voice Mail is not included in the Maximum Hop Count. Call Forward continues to operate to a MLT that has been removed. Related Feature List Call Forwarding Busy/No Answer K-CCIS Multiple Call Forwarding All Calls K-CCIS Multiple Call Forwarding Busy/No Answer K-CCIS Link Reconnect K-CCIS Uniform Numbering Plan K-CCIS
152
SV8100
Call Park Retrieve K-CCIS

Feature Description This feature allows a station user to retrieve Parked Calls at remote sites across K-CCIS. Locally parked calls can be retrieved from a remote system, connected via K-CCIS, by dialling the Call Park Hold Group Number, plus the park orbit location. System Availability Terminal Type: All Terminals Required Components: PZ-(X)IPL Operating Procedures Retrieve Park Call at remote location: 1. Go off-hook, and wait for internal dial tone. 2. Dial the Call Park Retrieve Access Code 861 (default) + Park Hold Group Number (1~64) + Park Orbit Number (1~64) of the call to be retrieved. Call (Park Retrieve access codes cannot be the same at all locations in the K-CCIS Network.) 3. Talk with party.
SV8100
Service Conditions General:
153
A different Call Park Retrieve Access Code must be programmed for each system in the K-CCIS network. The Park Group Number and Park Orbit Number must be dialled immediately following the Park Retrieve Service Code. When two or more stations attempt to retrieve the parked call, only one station can retrieve the call. A station connected to a PBX can retrieve a parked call in an UNIVERGE SV8100, but the station connected to the UNIVERGE SV8100 system cannot retrieve a parked call in a PBX. A Park Hold key cannot be used to retrieve a parked call from a distant system. F-Routes are required to route Call Park Retrieve Access Code to proper system in the K-CCIS network. When a remote location retrieves a call from another location, the call is treated as if it were transferred from the distant location. SMDR reports the retrieved call from the distant location as if it were a transferred call. When a call that has Caller ID Information is retrieved at the distant location the Caller ID information is treated as if it were a transferred call. Link Reconnect operates when the trunk is retrieved back to the origination system. Restrictions: A Call cannot be placed into remote systems Call Park Location. Call Park Retrieve K-CCIS is only a Key System-to-Key System supported feature. The digit (# or *) cannot be used in conjunction with IP K-CCIS. When the UNIVERGE SV8100 is connected to the Electra Elite IPK II, the maximum digits assignment in the UNIVERGE SV8100 is determined by Program 44-05-09. Call Park Searching is supported in the local system only. Related Feature List Call Park System Guide to Feature Programming This guide provides a list of associated Programs that support this feature. Park Originate System
Remote System (Call Park Retrieve)
154
SV8100
Call Transfer All Calls K-CCIS

Feature Description This feature allows a station user to transfer incoming or outgoing Central Office, intraoffice and interoffice calls to another station in the K-CCIS network without Attendant assistance. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures Using a Multiline Terminal with a call in progress (Closed Numbering Plan): 1. Press Transfer, and internal dial tone is heard. The call is placed on Common Hold. 2. Dial the distant K-CCIS station number where the call is to be transferred. 3. Wait for the ringback tone. 4. Hang up. - OR 1. When the party answers, announce the transfer. 2. Restore the handset (transfer is completed). 1. 2. Using a Multiline Terminal with a call in progress (Open Numbering Plan): Press Transfer, and receive internal dial tone. The call is placed on Common Hold.
SV8100
3. 4. 5. 6. 7. - OR 1. 2. Dial the trunk Access Code. Dial the Office Code number. Dial the distant K-CCIS station number where the call is to be transferred. Wait for the ringback tone. Hang up. When the party answers, announce the transfer. Restore the handset (transfer is completed).
155
Service Conditions General: A UNIVERGE SV8100 station can receive a K-CCIS transferred call as a camp-on call if allowed by Class of Service. Restrictions: Trunk-to-Trunk Transfer must be allowed in Program 14-01-13 (Trunk-to-Trunk Transfer Yes/No Selection). A blind transfer across a K-CCIS link cannot be completed until ringback tone is received at the transferring station. Related Feature List Link Reconnect K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS
Calling Name Display K-CCIS

Feature Description This feature permits the station name of a calling or called party at another switching office to be displayed on a multiline terminal, through the K-CCIS network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual.
156
SV8100
System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General: Both the caller/calling station name and number can be displayed on an UNIVERGE SV8100 station if allowed by Class of Service. For incoming or outgoing K-CCIS calls, the Calling/Called Name and Number are displayed for the entire length of the call including the Elapsed Call Time. RESTRICTIONS: In the UNIVERGE SV8100 system, only 12 digits/characters can be entered for each station name. Related Feature List Calling Number Display K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
Calling Number Display K-CCIS

Feature Description This feature permits the number of a calling or called party at another switching office, to be displayed on a multiline terminal through the K-CCIS network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual.
SV8100
System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General:
157
Both the caller/calling station number and name can be displayed on an UNIVERGE SV8100 station if allowed by Class of Service. For incoming or outgoing K-CCIS calls, the Calling/Called Name and Number are displayed for the entire length of the call including the Elapsed Call Time. For an open numbering plan the Office Code number and station number are displayed for caller/calling station number. Restrictions: The UNIVERGE SV8100 supports 2 to 8-Digit station numbers. When calling over a K-CCIS tandem connection, the calling party number (CPN) is transferred to the ISDN network. Related Feature List Calling Name Display K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
Calling Party Number (CPN) Presentation from Station K-CCIS

Feature Description Calling Party Number (CPN) Presentation from Station K-CCIS feature allows each station of the remote systems a unique 10-digit number (the DID number of the originating station) to be sent out over the PRI circuit of the main system.
158
SV8100
System Availability Terminal Type: All Terminals Required Components: PZ-(X)IPL Operating Procedures Placing a call with CPN: Lift the handset or press Speaker. Dial 9 + the number. Converse with caller. Hang up the handset. Service Conditions Restrictions: A maximum of 16 digits can be assigned as the Calling Party Number (CPN) in Program 21-12-01 and Program 21-13-01. The PRI provider must provision for the CPN used for E911. The CPN must be within the allowable range. For more information please contact your local ISDN provider regarding allowable ranges. The Calling Party Number (CPN) is sent only to the network when the calling party from the remote system dials a trunk access code of 9 when making an outbound call. The Calling Party Number (CPN) is not sent to the network when the originating station of the remote system calls a station in the main system that is call forwarded off site. Related Feature List ISDN Compatibility Automatic Route Selection Central Office Calls, Placing Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
SV8100
Centralised BLF (K-CCIS)
159
Feature Description This feature provides a busy indication for another station across the K-CCIS network on programmed Direct Station Selection/Busy Lamp Field (DSS/BLF) keys. The busy indication is a red LED associated with a Feature Access or One-Touch key programmed for Centralised BLF (K-CCIS). Pressing the Centralised DSS/BLF key allows direct access to the station through the K-CCIS network. Do Not Disturb and Voice Mail Message Waiting on Line key indications are also supported. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Attendant Add-On Console Required Components: PZ-(X)IPL Operating Procedures To program a Feature Access or One-Touch key for Centralised DSS/BLF: 1. Press Speaker. 2. Dial 851. 3. Press the key to be programmed. 4. Dial 01 to assign a DSS/One Touch Key. 5. Dial the station number. 6. Press Hold. Using a Feature Access or a One-Touch key programmed for Centralised DSS/BLF: 1. Press the programmed Feature Access or One-Touch key. Hear ringback tone. 2. When the called party answers, lift the handset or talk using handsfree if allowed. Service Conditions General: Voice Mail Message Waiting on Line Key indication is supported for Centralised DSS/BLF keys if PRG 20-13-41 [Class of Service Options (Supplementary Service)] VM Message Indication on DSS/BLF key (VMS Message Indication) is allowed. If Voice Mail Message Waiting on Line Key indication is allowed and a VM Message Waiting indication is provided (a new message is stored), pressing the Centralised DSS/BLF key performs the following; At system with Voice Mail installed, the user is logged into the owner mail box. At remote systems, the station is called. BLF Sending Service Conditions: The maximum number of destination offices for sending BLF messages is eight per system. Up to 120 Extension Numbers (entries into the table) can be assigned for sending BLF messages. With each assigned Extension Number, up to eight destination offices can be selected until a maximum of 240 total sending Extension Numbers are assigned. A maximum of 240 total sending Extension Numbers (BLF messages) can be assigned. If 30 Extension Numbers (entries into the table) are assigned with each set for all eight groups (systems), the 240 limit is reached and no more Extension Numbers can be entered. The BLF messages are sent in a four-second cycle (at default), so some delay occurs to change the indication in the destination office. In the network configured with two systems, it can take about four to five seconds (at default) to change the BLF indication in the destination office. This feature is provided with DSS/One-Touch Keys on multiline terminals and with an Attendant Add-On Console. When the button on the Attendant Add-On Console has a Mail Box button of a remote user programmed and the button is pressed the call is placed to the station on the remote side. BLF Receiving Service Conditions: BLF information can be received for up to 120 remote extensions per system. All multiline terminals in the system can assign Centralised DSS/BLF keys for the supported remote extensions. The LED indication of the DSS/BLF button on a multiline terminal is as follows: Idle No lamp indication Busy Steady red lamp Do Not Disturb Flashing red lamp VM Message Waiting Fast flashing red lamp The LED indication of the DSS/BLF button on the Attendant Add-on Console is as follows:
160
SV8100
Idle No lamp indication Busy Steady red lamp Do Not Disturb Flashing red lamp VM Message Waiting Fast flashing red lamp The BLF Information expels when data cannot be sent because of link disconnect. Status changes of BLF information while the system could not send data are not indicated on restoration. The Voice Mail MSG Waiting has priority over any other state of the flashing line key or One-Touch key.
Restrictions: This feature is not supported between UNIVERGE SV8100 and NEAX PBXs. This feature is supported with a Closed Numbering Plan only (not available with an Open Numbering plan). The same extension line from a remote site can be assigned to multiple DSS/One Touch keys. The BLF information is expelled when data cannot be sent if the K-CCIS link is down. The UNIVERGE SV8100 does not send BLF information again when the K-CCIS link is restored. BLF messages can be forwarded up to eight times in the network. When designing the K-CCIS network, this should be a consideration. When a Centralised DSS/BLF key is first programmed on a Feature Access or One Touch key, the BLF status does not change (update) until new BLF information is received from the remote system. Related Feature List Do Not Disturb (DND) Feature Access User Programmable Voice Mail Message Indication on Line Keys Guide to Feature Programming (FOR MAIN SYSTEM) This guide provides a list of associated Programs that support this feature. (For Sending System)
SV8100
161
(For Receiving System)
Centralised Day/Night Mode Change K-CCIS

Feature Description This feature switches the Day/Night mode of a remote office that is linked to a main office using K-CCIS, in accordance with the Day/ Night mode switching from an Attendant Position at the main office. When a UNIVERGE SV8100 system is connected to another UNIVERGE SV8100 system, the main office can control remote offices. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components PZ-(X)IPL Operating Procedures To set or cancel Night Transfer system-wide from an Attendant Position:
162
SV8100
Main Office: 1. Press Speaker. 2. Dial Access Code 818. 3. Dial the Night service Code: 1. Day 1 mode 2. Night 1 mode 3. Midnight 1 mode 4. Rest 1 mode 5. Day 2 mode 6. Night 2 mode 7. Midnight 2 mode 8. Rest 2 mode Press Speaker or hang up. Press the Night Transfer key on the Attendant Add-On Console.
4. - OR 1.
Remote Office: No manual operation is required. Service Conditions General: A maximum of 16 remote offices can be controlled by one main office. If Automatic Day/Night Mode Switching is assigned in the main office, all remote offices change the mode, if assigned. If the remote office is to be restricted from overriding the Day/Night Mode setting, the following Programming Commands should be assigned: 12-01-01 Night Mode Function Setup Manual Night Service enable 20-07-01 Class of Service Options (Administrator Level) Manual Night Service enable When the remote office is in Night Mode (as assigned in the Centralised Day/Night Mode - K-CCIS feature), normal Night Mode indications are provided. The Night Mode indication is the first word (Night) on the second row of the multiline terminal LCD. The LED for any Feature Access key assigned for Night Mode transfer and the Night Mode key on the Attendant console are On. If the K-CCIS link is not available due to network trouble, the UNIVERGE SV8100 main office resends the K-CCIS Day/Night Mode switch command every 16 minutes. Restrictions: Centralised Day/Night Mode switching from a main office can send a system-wide K-CCIS Day/Night mode switch command only. Individual Night Service Groups Mode switching is not supported. When an UNIVERGE SV8100 receives the K-CCIS Day/Night Mode switch command from a main office, the remote office changes all Night Service Groups to the requested mode. Program 50-03-01 (Destination Point Code Transfer Assignment) must be set for all offices for the Centralised Day/Night Mode feature. Related Feature List Assigned Night Answer (ANA) Authorisation Code Automatic Day/Night Mode Switching Centralised Billing K-CCIS Code Restriction Dial Access to Attendant K-CCIS Direct Inward Termination (DIT) Flexible Ringing Assignment Night Call Pickup Night Chime Night Transfer Voice Mail Integration K-CCIS
SV8100
Centralised Day/Night Mode Change
163
164
SV8100
For Night Transfer Feature
Centralised E911 K-CCIS

Feature Description This feature allows a remote system to transmit a Calling Party Number to the 911 Emergency System over a K-CCIS direct or tandem connection. System Availability Terminal Type: All Stations
SV8100
Required Components PZ-(X)IPL Operating Procedures To use this feature at any terminal: 1. Lift the handset, and wait for internal dial tone. 2. Dial 911. - OR 1. Dial 9 911.
165
Service Conditions General: If you want to send your phone number via CCIS, please refer to Calling Party Number (CPN) Presentation from Station KCCIS The Calling Party Number (CPN) is sent only to the network when the remote system accesses an ISDN PRI trunk in the distant system and the ISDN PRI trunk has Calling Party Number (CPN) Presentation and Screening service enabled from the network. If Program 21-01-10 is programmed with an entry other than 0, a call does not have a talk path unless the user dials at least the number of digits entered in this option when placing an outgoing call. This means that an entry of 4 or higher in this program causes a problem when dialling 911. Since it is only a 3-digit number, the call does not have a talk path preventing the emergency dispatcher from hearing the caller. It is recommended that this option be kept at its default setting of 0 to prevent any problems with dialling 911. The attendant receives a notification each time a co-worker dials an emergency 911 call. This notification is the co-worker name and number display optionally accompanied by an audible alarm. Notification occurs regardless of whether the attendant is idle or busy on a call. You can optionally extend this ability to other supervisory extensions as well. The PRI provider must provision for the CPN used for E911. The CPN must be within the allowable range. For more information please contact your local ISDN provider regarding allowable ranges. Virtual Extensions notify the attendant with the stations name and number when an emergency 911 call is originated from the Virtual Extension. Restrictions: Centralised E911 (outgoing with CES-ID) is not supported. A maximum of 16 digits can be assigned as the Calling party Number (CPN) in Program 21-13-01. If Virtual Extensions are used to make E911 calls, they provide the information for the VE key.
Related Feature List ISDN Compatibility Calling Party Number (CPN) Presentation from Station K-CCIS E911 Compatibility Automatic Route Selection Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
166
SV8100
Dial Access to Attendant K-CCIS

Feature Description This feature allows a station user to call an Attendant by dialling a call code through the K-CCIS network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To call an Attendant Position: 1. Lift the handset or press Speaker. 2. Dial 0 or the operator call code if it is different from 0. Service Conditions General: The operator call code must be for an individual Attendant Access Code number. When calling to a UNIVERGE SV8100 Attendant Position, the SV8100 sends Operator to the call originator as the name. Shows Office Code if using Open Numbering Plan. If using an Open Numbering Plan and a call is made to an UNIVERGE SV8100 Attendant Position, the operator office code is included with the name. When making a call from a UNIVERGE SV8100 Attendant Position across a K-CCIS network, the Caller ID Name and Number display is the same as for a station-to-station call. In a Closed Numbering Plan network, a station can call an Attendant in the K-CCIS network by dialling 0. In an Open Numbering Plan network, a station user can call an Attendant within the K-CCIS network by dialling: Access Code + Office Code + 0. Restrictions: Operator Calling, PRG 20-14-05, does not keep a Tie Line caller from dialling 0 for the operator.
Related Feature List Attendant Positions Calling Name Display K-CCIS
SV8100
Calling Number Display K-CCIS Centralised Day/Night Mode Change K-CCIS Voice Calls K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature. For Main System
167
For Remote System
168
SV8100
Direct Inward Dialling K-CCIS

Feature Description This feature allows an incoming DID call (centralised DID) to be routed directly across a K-CCIS link to reach a station in the remote system without Attendant assistance. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All Stations Required Components: PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General: Call billing to the outside party starts when the incoming call connects to the K-CCIS trunk. When an incoming DID call from the CD-PRTA card with Caller ID information is transferred to the station in K-CCIS network, the Caller ID Name and Number follow across the K-CCIS network to the distant system. This feature is supported when a Closed Numbering Plan or Open Numbering is used. The UNIVERGE SV8100 system supports DID Digit Conversion when using station numbers with 2 to 8 digits. An extension on a remote system can be the destination for the DID Received Vacant Number Operation Assignment (Program 22-09-02). Restrictions: Program 20-02-15 (Caller ID Display Mode) must be set to 0 to display the DID Name on incoming DID calls. Refer to the Key-Common Channel Interoffice Signalling (K-CCIS) feature for more details related to Single Line Telephone
SV8100
and IP (K-CCIS) support. Related Feature List Key-Common Channel Interoffice Signalling (K-CCIS) Flexible Numbering of Stations K-CCIS Uniform Numbering Plan K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
169
Dual Hold K-CCIS

Feature Description This feature allows two connected Multiline Telephones to be placed on hold simultaneously over the K-CCIS link. This enables the held parties to answer or originate a call from a secondary line or intercom path. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General: This feature is available for interoffice calls through K-CCIS. Both Common Hold and Exclusive Hold can be used for Dual Hold K-CCIS. The K-CCIS call is held on a Call Appearance key. Restrictions: None
Related Feature List Station-to-Station Calling K-CCIS
170
SV8100
Elapsed Time Display K-CCIS

Feature Description This feature provides an Elapsed Call Time on the LCD which shows the duration of time that a multiline terminal is connected to any call through the K-CCIS network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All Display multiline terminals Required Components: PZ-(X)IPL Operating Procedures No manual operation is required. Service Conditions General: When a call is retrieved from Exclusive Hold and/or Common Hold from the same station, the elapsed call timer begins at 0. When a call is transferred, the elapsed time of the party receiving the transfer begins at zero.
Restrictions: For calls across a K-CCIS link, the Elapsed Call timer begins only after receiving answer supervision from the distant system. For Voice Calls across the K-CCIS link, the Elapsed Call timer does not begin until the distant station answers. For conference calls established across a K-CCIS link, the elapsed call timer does not start during an active conference call. Related Feature List Station-to-Station Calling K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
SV8100
171
Flexible Numbering of Stations K-CCIS

Station numbers can be assigned by the 10's group for 4-digit station numbers, 100's group for 5-digit, 1,000's group for 6-digit station numbers, and 10,000's group for 7-digit station numbers. Example:
Feature Description This feature allows telephone numbers to be assigned to any stations in the K-CCIS network, based solely upon numbering plan limitations. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All Stations Required Components: PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General: Give careful consideration to the network numbering plan to avoid needless loss of Access Codes or duplication of telephone numbers. The first digit or first two digits of a telephone number distinguishes one system from another system. Station Numbering Plan can have 2 to 8 digits. Restrictions: Tenant service is not provided, i.e., numbers cannot be duplicated for different tenants. Extension numbers should not start with 0, 9, * or #. For non-K-CCIS feature support, refer to the UNIVERGE SV8100 Features and Specifications Manual, Flexible Numbering Plan feature. Related Feature List Key-Common Channel Interoffice Signalling (K-CCIS) Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS
172
SV8100
Handsfree Answerback K-CCIS Feature Description This feature allows Multiline Telephone station users to respond to voice calls through a K-CCIS network without lifting the handset. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To turn the microphone On/Off: 1. Press Feature. 2. Dial 1. - OR Press the programmable line key assigned as the MIC On/Off key.
SV8100
Service Conditions Restrictions Handsfree Answerback (K-CCIS) can be used only when responding to Voice Calls (K-CCIS) from a remote user. After a user changes ring back tone to voice call, it cannot be changed back to ringing. Voice Call cannot be set as the initial call across K-CCIS. The initial call must be a ringing call. Related Feature List Voice Calls K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
173
Hot Line K-CCIS

Feature Description This feature allows two stations at different nodes in the K-CCIS network to be mutually associated on automatic ringdown through the K-CCIS network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To execute at any station programmed for Hot Line: 1. Lift the handset or press Speaker. 2. The remote K-CCIS station is called.
Service Conditions General: Any multiline terminal (a maximum number of 512 stations) can be assigned for Hot Line (K-CCIS). Either multiline terminal in a Hot Line (K-CCIS) pair may transfer a Hot Line call to another station in the K-CCIS network using the Call Transfer All Calls - (K-CCIS) feature.
174
SV8100
Restrictions: None Related Feature List Call Transfer All Calls - K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS
Link Reconnect K-CCIS

Feature Description This feature provides the system that is connected to a K-CCIS network with the ability to release the redundant K-CCIS link connections and reconnect the link with the system for efficient usage of the K-CCIS trunks. System Availability Terminal Type: All multiline terminals Required Components PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General: The link reconnect ability is provided for a station call over K-CCIS that is transferred or forwarded to another station or trunk in the same office as the call originating station.
SV8100
Example:
175
A trunk call (CO/PBX/TIE/DID/K-CCIS) over a K-CCIS network is transferred or forwarded to another station or trunk within the same office as the original incoming trunk. Call Forward to Trunk Line
176
SV8100
Link reconnect occurs after answering a transferred or forwarded K-CCIS call.
Restrictions: Answer supervision is required for Link Reconnect to occur. For outgoing calls on analogue trunks, Answer supervision is based on the Elapsed Call Time - Program 21-01-03 (Trunk Interdigit Time). When a call is on hold, or in a conference, and is transferred back across the K-CCIS link, Link Reconnect is not provided. Related Feature List Call Forwarding All Calls K-CCIS Call Forwarding Busy/No Answer K-CCIS Call Transfer All Calls K-CCIS Multiple Call Forwarding All Calls K-CCIS Multiple Call Forwarding Busy/No Answer K-CCIS Station-to-Station Calling K-CCIS Uniform Numbering Plan K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
SV8100
Multiple Call Forwarding All Calls K-CCIS
Feature Description This feature allows a Multiple Call Forwarding All Calls sequence to be forwarded over a K-CCIS network to a station in another office. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To set Call Forward All Calls K-CCIS from a Multiline Telephone (Closed Numbering Plan): 1. Press the Call Forward All ON/OFF key. 2. Dial 1 to set. Then enter the K-CCIS station number. 3. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 741 (set as default). Then Dial 1 to set. 3. Dial the remote K-CCIS station number. 4. Restore handset or press Speaker. To set Call Forward All Calls K-CCIS from a Multiline Telephone (Open Numbering Plan): 1. Press the Call Forward All Call ON/OFF key, and Dial 1 to set. 2. Dial the trunk Access Code (normally 8). 3. Dial the Office Code number. 4. Dial the distant K-CCIS station number. 5. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 741 (set as default), and Dial 1 to set. 3. Dial the trunk Access Code (normally 8). 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Restore handset or press Speaker. To cancel Call Forward All Calls K-CCIS from a Multiline Telephone: 1. Press Call Forward All Call On/Off key. 2. Dial 0 to cancel. 3. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 741 (set as default), and Dial 0 to cancel. 3. Restore handset or press Speaker.
177
Service Conditions General: Multiple Call Forwarding All Calls K-CCIS can forward a call up to seven times across K-CCIS links (up to seven hops) depending on system data. Multiple Call Forwarding over a K-CCIS link is combined with Multiple Call Forwarding All Calls/Busy/No Answer. If the calling station is set as the destination in a multiple hop scenario, Multiple Call Forwarding All Calls K-CCIS is not performed (i.e., an infinite loop does not occur). For multiple Call Forwarding All Calls/Busy (Immediate) calls, the display on the calling party Multiline Telephone displays the terminating station user name and the station number for the first station of a distant system in the Multiple Call Forwarding group. For the terminating station, the telephone display indicates the name and the number of the calling party and the trunk number of the incoming call. When a calling station has been Call Forwarding All Calls K-CCIS to the maximum times assigned in Program 50-05-01 (K-CCIS Maximum Call Forwarding Hop Assignment) and encounters another Call Forwarding All Calls K-CCIS condition, the calling station is not forwarded and rings at the last destination.
178
SV8100
If the destination station in a Multiple Call Forwarding All Calls K-CCIS situation is busy and has not set Call Forwarding Busy and has Call Alert Notification disabled, the calling party receives busy tone. When combining Call Forwarding Busy and Call Forwarding All Calls K-CCIS, if the destination station is busy and has Call Alert Notification disabled, the calling party hears busy tone after the maximum hops assigned in Program 50-05-01 (KCCIS Maximum Call Forwarding Hop Assignment). Multiple Call Forwarding All Calls -K-CCIS and Call Forwarding Busy K-CCIS may be mixed; up to seven combined multiple forwardings may occur. An example of Multiple Call Forwarding over a K-CCIS link is shown below
Related Feature List Call Transfer All Calls K-CCIS Call Forwarding All Calls K-CCIS Call Forwarding Busy/No Answer K-CCIS Multiple Call Forwarding Busy/No Answer K-CCIS Link Reconnect K-CCIS Uniform Numbering Plan K-CCIS
SV8100
179
Multiple Call Forwarding Busy/No Answer - K-CCIS Feature Description This feature allows a Multiple Call Forwarding Busy/No Answer sequence to be forwarded over a K-CCIS network to a station in another office. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To set Call Forward Busy/No Answer - K-CCIS from a Multiline Telephone (Closed Numbering Plan): 1. Press the Call Forward Busy/No Answer ON/OFF key. 2. Dial 1 to set. 3. Dial the remote K-CCIS station number. 4. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 844 (default), then 1 to set. 3. Dial the remote K-CCIS station number. 4. Restore handset or press Speaker.
180
SV8100
To set Call Forward Busy/No Answer - K-CCIS from a Multiline Telephone (Open Numbering Plan): 1. Press the Call Forward Busy/No Answer ON/OFF key. 2. Dial 1 to set. 3. Dial the trunk Access Code. 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 844 (default), then dial 1 to set. 3. Dial the trunk Access Code. 4. Dial the Office Code number. 5. Dial the distant K-CCIS station number. 6. Restore handset or press Speaker. To cancel Call Forward Busy/No Answer K-CCIS from a Multiline Telephone: 1. Press Call Forward Busy/No Answer On/Off key. 2. Dial 0 to cancel. 3. Press Speaker. - OR 1. Lift the handset or press Speaker. 2. Dial Access Code 844 (default), then Dial 0 to cancel. 3. Restore handset or press Speaker. To set for any station for Attendant Positions only (Closed Numbering Plan): 1. Lift the handset or press Speaker. 2. Dial the Call Forward Busy/No Answer for any Extension to Destination 3. Service Code (default: 793). 4. Dial 1 (Set). 5. Dial the extension number to be forwarded and then the destination number. 6. Press Speaker or hang up. To cancel for any station for Attendant Positions only: 1. Pick up the handset or press Speaker. 2. Dial the Call Forward Busy/No Answer for any Extension to Destination 3. Service Code (default: 793). 4. Dial 0 (Cancel). 5. Dial the station number, which is forwarded. 6. Press Speaker or hang up.
Service Conditions General: Multiple Call Forwarding Busy/No Answer Calls - K-CCIS can forward a call up to five times across K-CCIS links (up to five hops) depending on systems data. Multiple Call Forwarding over a K-CCIS link is combined with Multiple Call Forwarding All Calls/Busy/No Answer. If the calling station is set as the destination in a multiple hop scenario, Multiple Call Forwarding Busy/No Answer Calls K-CCIS are not performed, i.e., an infinite loop does not occur. For multiple Call Forwarding All/Busy (Immediate) calls, the display on the calling partys Multiline Telephone indicates the terminating station users name and the station number for the first station of a distant system in the Multiple Call Forwarding group. For the terminating station, the telephone display indicates the name and the number of the calling party and the trunk number of the incoming call. For multiple Call Forwarding No Answer/Busy (Delay) calls, the display on the calling partys Multiline Telephone indicates the name and number of the first station of a distant system in the Multiple Call Forwarding group. For the terminating station, the telephone display indicates the name and the number of the calling party and the trunk number of the incoming call. When a calling station has been Call Forwarding Busy/No Answer Calls K-CCIS to the maximum times assigned in Program 50-05-01 (K-CCIS Maximum Call Forwarding Hop Assignment) and encounters another Call Forwarding Busy/No Answer Calls K-CCIS condition, the calling station is not forwarded and rings at the last destination. When the destination station in a Multiple Call Forwarding Busy/No Answer Calls K-CCIS situation is busy and has not set Call Forwarding Busy and has Call Alert Notification disabled, the calling party receives busy tone. When combining Call Forwarding Busy and Call Forwarding All Calls K-CCIS and the destination station is busy and has Call Alert Notification disabled, the calling party hears a busy tone after the maximum hops assigned in Program 50-0501 (K-CCIS Maximum Call Forwarding Hop Assignment). Multiple Call Forwarding All Calls K-CCIS can forward a call a maximum of five times across K-CCIS link (maximum of
SV8100
five hops) depending on system data assignments. An example of Multiple Call Forwarding over a K-CCIS link as shown
181
Restrictions: Trunk-to-Trunk Transfer must be allowed in Program 20-11-14 [Class of Service Options (Hold/Transfer Service) Trunk-toTrunk Transfer Restriction]. Related Feature List Call Forwarding All Calls K-CCIS Call Forwarding Busy/No Answer K-CCIS Multiple Call Forwarding All Calls K-CCIS Link Reconnect K-CCIS Uniform Numbering Plan K-CCIS
182
SV8100
Paging Access K-CCIS

Feature Description This feature allows users to access internal or external paging from remote sites across the K-CCIS network. Local stations where the external paging equipment is installed can use the Meet-Me Answer feature to answer the page and establish a station-to-station K-CCIS call. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To access internal or external paging across a K-CCIS network: 1. Lift the handset or press Speaker.
SV8100
2. Dial the Access Code for the required zone, or press the programmed Feature Access or One-Touch key.
183
Service Conditions General: The single external paging zone output built into the basic B64-U20 KSU can be used for Paging Access (K-CCIS). Program 31-01-02 (Paging Announcement Duration) applies to Paging Access (K-CCIS). If a user dials during Paging Access (K-CCIS), DTMF tones are heard from the external paging equipment at the remote site. Program 31-02-01 (Internal Paging Group Number) applies to Paging Access (K-CCIS). Program 31-02-02 (Internal All Call Paging Receiving) applies to Paging Access (K-CCIS). Restrictions: Amplifiers and speakers must be locally provided. Combined Paging is not supported over K-CCIS. Internal Paging across K-CCIS is supported only between UNIVERGE SV8100 and UNIVERGE SV8100. Related Feature List Background Music Over External Speakers External Zone Paging (Meet-Me) Internal Zone Paging (Meet-Me)
Guide to Feature Programming This guide provides a list of associated Programs that support this feature. For Paging Installation
184
SV8100
SV8100
185
186
SV8100
For Remote System
Quick Transfer to Voice Mail K-CCIS Feature Description A station user transferring a call can force the call to be transferred to the called party voice mail box after the transferred call recalls, after an internal station number is dialled while performing a screened transfer, or during intercom calls. System Availability Terminal Type: All multiline terminals allow either operation. Single line telephones may perform the Quick Transfer only during screened transfer operations. They may not perform Quick Transfer after recall.
SV8100
Required Components PZ-(X)IPL Operating Procedures Quick Transfer Across K-CCIS: To Quick Transfer a call while talking with an outside or internal party: 1. Press Transfer, and wait for an internal dial tone. 2. Enter a station number, and wait for a ring back tone. 3. Dial the Quick Transfer Access Code. The outside party is transferred to the station user Voice Mail box. 4. Hang up. 5. The Voice Mail answers. To leave a message using Quick Transfer to voice mail during an intercom call: 1. Make the intercom call. 2. Dial the Quick Transfer Access Code. 3. Leave a voice mail message. 4. Hang up. Service Conditions General: The Quick Transfer to Voice Mail feature is allowed when: Listening to the ring back tone (RBT) Listening to the call waiting tone (CWT) In Handsfree Answerback Mode In Voice Over Mode This feature is allowed from a single line telephone (SLT) until the PBR times out (default: 10 sec). An SLT may perform the Quick Transfer only during screened transfer operations. With v3.00 or lower, VM8000 InMail is not supported in a KTS to KTS network for K-CCIS. With v4.00 or higher, VM8000 InMail is supported in a KTS to KTS network for K-CCIS. Related Feature List Digital Voice Mail
187
188
SV8100
Station-to-Station Calling K-CCIS

Feature Description This feature permits any multiline terminal user to dial another multiline terminal directly through a K-CCIS network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures Normal call handling procedures apply. Service Conditions General: If the called station is off-hook and has Call Queuing disabled, the originating station receives a busy tone. If the called station is idle, the called station rings and the caller hears ringback tone. If the called station is off-hook on a call and has Call Queuing enabled, the originating station receives ringback tone and the called station receives call alert tone. Station-to-Station Calling between tenants in the K-CCIS network is not restricted. The release process is First Party Release. Restrictions: The same telephone numbers cannot be duplicated in the same system.
Related Feature List Call Transfer All Calls - K-CCIS Calling Name Display K-CCIS Calling Number Display K-CCIS Dual Hold K-CCIS Elapsed Time Display K-CCIS Flexible Numbering of Stations K-CCIS Hands-Free Answerback K-CCIS Key-Common Channel Interoffice Signalling (K-CCIS) Uniform Numbering Plan K-CCIS Guide to Feature Programming This guide provides a list of associated Memory Blocks that support this feature.
SV8100
Uniform Numbering Plan K-CCIS
189
Feature Description In a K-CCIS network, a Uniform Numbering Plan enables a multiline terminal user to call any other multiline terminal in the network. Two types of numbering plans are provided. In the first plan, the station user dials any telephone number from two to eight digits. The location of the office is identified by the first digit or first two digits of the telephone number. In the second plan, the station user dials a one-, two- or three-digit office code and a telephone number from two to eight digits. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures To call a station at another office using Numbering Plan 1 (Closed Numbering Plan): 1. Lift the handset or press Speaker. 2. Dial the remote K-CCIS station number. To call a station at another office using Numbering Plan 2 (Open Numbering Plan): 1. Lift the handset or press Speaker. 2. Dial the trunk Access Code. 3. Dial the Office Code number. 4. Dial the remote K-CCIS station number. Service Conditions General: In a closed numbering plan, the location of the office can be identified by the first digit or first two digits of the telephone number. In an open numbering plan, each office in the K-CCIS network is assigned a one-, two- or three-digit office code and each station in the office is assigned telephone numbers from two to eight digits. In the same office, a station-to-station call is made by dialling the telephone number of the desired station. Restrictions: For a Closed Numbering Plan network, a maximum of 255 systems can be connected per K-CCIS Network. When a Closed Numbering plan is used the extensions in the network cannot have the same prefix number. For an Open Numbering Plan network, the Automatic Route Selection (ARS)/ Flexible Routing (F-Route) feature must be used to place Station-to-Station calls over K-CCIS. When an Open Numbering plan is used, the extensions in the network can have the same prefix number, however the office location number cannot be the same.
Related Feature List Call Transfer All Calls K-CCIS Flexible Numbering of Stations K-CCIS Key-Common Channel Interoffice Signalling (K-CCIS) Station-to-Station Calling K-CCIS Guide to Feature Programming Refer to Flexible Numbering of Stations feature
Voice Call K -CCIS

Feature Description This feature provides a voice path, through the K-CCIS network, between a MLT in one office and a MLT in another office. This path is established from the calling party to the called party built-in speaker. If the called party MIC is on, the called party can converse handsfree.
190
SV8100
System Availability Terminal Type: All multiline terminals Required Components: PZ-(X)IPL Operating Procedures From one MLT to another MLT: The originating MLT user dials the desired station number in a different office and receives ring back tone. Calling party dials 1. A signal tone is transmitted over the K-CCIS network to the called party speaker. The called party can press MIC, or press FEATURE and dial 1 (if the MIC LED is not on) to allow two-way conversation with the calling party.
Service Conditions General: The UNIVERGE SV8100 can assign a Feature Access/One Touch Button as a Voice Call key. This performs the same operation as pressing 1. Any station in the same system can use Directed Call Pick Up to retrieve the Voice Call over K-CCIS. When a Voice Call is sent to a station that is unable to receive voice announcement, RST is displayed on the originator display. During Voice Call, the ICM Key is flashing (Red). Restrictions: The calling party must wait for at least one ring back before Voice Call is attempted. After the calling party changes ring back to Voice Call, it cannot be changed back to tone. Voice Call cannot be set as the initial call across K-CCIS. Group Call Pick Up is not allowed to retrieve voice calls over K-CCIS. Single Line terminals can be used to originate a Voice Call Over K-CCIS. However, they are not allowed to receive a voice call. Related Feature List Station-to-Station Calling K-CCIS Handsfree Answerback K-CCIS Guide to Feature Programming This guide provides a list of associated Programs that support this feature.
Voice Mail Integration K-CCIS

Feature Description This feature allows any station user in the K-CCIS network to use the Voice Mail System (VMS) in another office in the K-CCIS network. New for v4.00 software: VM8000 In-Mail voice mail is supported for centralised voice mail in a KTS to KTS network for K-CCIS. VM8000 In-Mail voice mail is supported for centralised voice mail in a Netlink network. For more details, refer to the UNIVERGE SV8100 Features and Specifications Manual. System Availability Terminal Type: All Stations
SV8100
REQUIRED COMPONENTS: VM8000 InMail PZ-(X)IPL Operating Procedures To access voice mail from a Multiline Telephone in the Main system: 1. Lift the handset or press Speaker. 2. Dial pilot number for voice mail. 3. When voice mail answers use soft keys to navigate. - OR 4. Wait for soft keys to time out and listen to voice prompts to navigate. 5. When finished hang up. To access voice mail from a Multiline Telephone in the Remote system: 1. Lift the handset or press Speaker. 2. Dial extension number for voice mail. 3. When voice mail answers listen to voice prompts to navigate. 4. When finished hang up. To program a One-Touch/Feature Access key for easy message access: 1. Press Feature. 2. Dial 751. 3. Press One-Touch/Feature Access key. 4. Dial 1, followed by Voice Mail extension number. 5. Press Hold. Service Conditions General:
191
Any station or Call Arrival (CAR) key can be set for Call Forwarding Busy/No Answer to voice mail. The following features are supported for voice mail users in remote systems: Message Waiting Indication Automated Attendant Auto Login center Call Forward Busy/No Answer to voice mail Call Forward All Call to voice mail A voice mail with at least eight ports should be used in any K-CCIS system with a shared voice mail. When using v4.xx or higher software, InMail is supported for centralised voice mail in a NetLink and KTS to KTS CCIS network. When using v3.xx or lower software, InMail is not supported in a NetLink or KTS to KTS CCIS network. With v4.xx or higher software, a maximum of 16 VM8000 InMail ports are supported. When InMail is used as centralised voice mail in a KTS to KTS CCIS system, remote mailbox users cannot access End User Web Pro for telephone and InMail configuration. Restrictions: In the voice mail, only release transfer type is supported for mail boxes of stations in Remote systems. In a KTS to KTS Network, only digital voice mails are supported for K-CCIS. In a KTS to KTS network, Centralised Voice Mail is supported only via closed numbering plan and only up to 7-digit station numbers. In a PBX to KTS network, Centralised Voice Mail is supported only via closed numbering plan. In a PBX to KTS network, Centralised Voice Mail is supported using the PBX voice mail. Single Line Telephones (SLTs) connected to the AP(A)-R Unit/AP(R)-R Unit or APA-U Unit/APR-U Unit cannot be used to transfer a Trunk call across the K-CCIS Network to another station or Voice Mail. When a call is forwarded to voice mail by multiple call forwarding, the message is left in the mailbox of the first forwarded station. Call Forward Off-Premise must be allowed in Class of Service Feature Selection to set call forwarding to main KCCIS voice mail. Trunk-to-Trunk Transfer must be allowed in Program 14-01-13 (Trunk-to-Trunk Transfer Yes/No Selection). A remote system can have only Message Waiting LED on Line key for extensions in the remote system. Remote system users cannot press a flashing Line key to route to voice mail or the message box of an extension on Message Waiting LED on the Line key. The following features are not supported for voice mail users in remote systems: Live Record Live Monitoring Caller ID Display Soft keys Await Answer transfer from voice mail
192
SV8100
Call Holding Constant Message Count Indication Call Back to VM Live Transfer (Caller ID Return Call) The Dial Access Code for Single Line Telephone Hook flash is supported for trunk calls into the main system only. The voice mail must be installed in the PBX (NEAX system) when 5-, 6-, or 7-digit station numbers are used. Centralised Voice Mail and Local Voice Mail cannot be mixed in a K-CCIS network.
Related Feature List Key-Common Channel Interoffice Signalling (K-CCIS) Call Forwarding All Calls - K-CCIS Call Forwarding Busy/No Answer - K-CCIS Multiple Call Forwarding All Calls - K-CCIS Multiple Call Forwarding Busy/No Answer - K-CCIS
Guide to Feature Programming This guide provides a list of associated Memory Blocks that support this feature.
SV8100
193
194
SV8100
SV8100
195
Networking IPL DSP Usage

NetLink IPL DSP Usage
Peer to Peer is enabled where possible
Primary System DT70 DTerm 0 IP DT700 0 P=2 0 P=2 P=1 P=2 P=1 S1=2 S1=1 S1=1 S2=2 S2=1 S2=1 STD SIP 0 P=2 0 P=1 P=2 P=1 0 S1=1 S1=1 0 S2=1 S2=1 TDM Ext P=1 P=1 P=1 0 P=1 0 P=1 P=1 S1=1 P=1 S1=1 P=1 P=1 S2=1 P=1 S2=1 SIP Trunk P=2 P=2 P=2 P=1 P=2 P=1 P=2 P=2 S1=1 P=2 S1=1 P=2 P=2 S2=1 P=2 S2=1 TDM Trunk P=1 P=1 P=1 0 P=1 0 P=1 P=1 S1=1 P=1 S1=1 P=1 P=1 S2=1 P=1 S2=1
Secondary System 1 DT70 TDM 0 Ext 0 P=2 0 P=1 P=2 P=1 0 P=1 S1=1 0 S2=1 S2=1 S1=1 S1=1 S1=1 P=1 S1=1 P=2 S1=1 P=1 S1=1 S1=1 0 0 S1=1 S1=1 S2=1 S1=1 S2=1 TDM Trunk S1=1 S1=1 S1=1 P=1 S1=1 P=2 S1=1 P=1 S1=1 S1=1 0 0 S1=1 S1=1 S2=1 S2=1 S2=1
Secondary System 2 DT70 0 0 P=2 0 P=1 P=2 P=1 0 P=1 S1=1 0 S2=1 S2=1 TDM Ext S2=1 S2=1 S2=1 P=1 S2=1 P=2 S2=1 P=1 S2=1 S2=1 S1=1 S2=1 S1=1 S2=1 S2=1 0 0 TDM Trunk S2=1 S2=1 S2=1 P=1 S2=1 P=2 S2=1 P=1 S2=1 S2=1 S1=1 S2=1 S1=1 S2=1 S2=1 0 0
DTermI P=2 P STD SIP Primary System TDM Ext SIP Trunk TDM Trunk DT700 Second ary System 1 TDM Ext TDM Trunk DT700 Second ary System 2 TDM Ext TDM Trunk 0 P=1 P=2 P=1 0 P=1 S1=1 0 S2=1 S2=1
P = Number of DSPs in use on the Primary System S1 = Number of DSPs in use on Secondary System 1 S2 = Number of DSPs in use on Secondary System 2
AspireNet IPL DSP Usage

Node 1 DT70 0 Node 1 DT700 0 TD M N1= 1 SIP Trunk N1=2 TDM Trunk N1=1 DT70 0 TD M
Node 2 SIP Trunk N1=2 N2=2 TDM Trunk N1=2 N2=1 DT70 0 TD M
Node 3 SIP Trunk N1=2 N3=2 TDM Trunk N1=2 N3=1
N1= N1=2 2 N2=2 N2= 1
N1= N1=2 2 N3=2 N3= 1
196
SV8100
TDM N1=1 0 N1=1 0 N1= N1=1 1 N2=2 N2= 1 N1= N1=2 2 N2=2 N2= 1 N1= N1=1 1 N2=2 N2= 1 0 N2= 1 N1=1 N2=2 N1=1 N2=1 N1= N1=1 1 N3=2 N3= 1 N1= N1=2 2 N3=2 N3= 1 N1= N1=1 1 N3=2 N3= 1 N2= N2=2 2 N3=2 N3= 1 N2= N2=1 1 N3=2 N3= 1 N2= N2=2 2 N3=2 N3= 1 N2= N2=1 1 N3=2 N3= 1 0 N3= 1 N1=1 N3=2 N1=1 N3=1
SIP Trunk
N1= N1=2 1
N1=2
N1=1
N1=2 N2=2
N1=2 N2=1
N1=2 N3=2
N1=2 N3=1
TDM Trunk
N1=1
N1=1
N1=1 N2=2
N1=1 N2=1
N1=2 N3=1
N1=1 N3=1
DT700
N2= N2=2 2 N1=2 N1= 1 N2= N2=1 1 N1=2 N1= 1 N2= N2=2 2 N1=2 N1= 1 N2= N2=1 1 N1=2 N1= 1 N3= N3=2 2 N1=2 N1= 1 N3= N3=1 1 N1=2 N1= 1 N3= N3=2 2 N1=2 N1= 1 N3= N3=1 1 N1=2 N1= 1
N2=2 N1=2
N2=2 N1=1
N2=2
N2=1
N2=2 N3=2
N2=2 N3=1
TDM Node 2 SIP Trunk
N2=1 N1=2
N2=1 N1=1
N2=1
N2=1
N2=1 N3=2
N2=1 N3=1
N2=2 N1=2
N2=2 N1=1
N2= N2=2 1
N2=2
N2=1
N2=2 N3=2
N2=2 N3=1
TDM Trunk
N2=1 N1=2
N2=1 N1=1
N2=1
N2=1
N2=1 N3=2
N2=1 N3=1
DT700
N3=2 N1=2
N3=2 N1=1
N3= N3=2 2 N2=2 N2= 1 N3= N3=1 1 N2=2 N2= 1 N3= N3=2 2 N2=2 N2= 1 N3= N3=1 1 N2=2 N2= 1
N3=2 N2=2
N3=2 N2=1
N3=2
N3=1
TDM Node 3 SIP Trunk
N3=1 N1=2
N3=1 N1=1
N3=1 N2=2
N3=1 N2=1
N3=1
N3=1
N3=2 N1=2
N3=2 N1=1
N3=2 N2=2
N3=2 N2=1
N3=2
N3= 1
N3=2
N3=1
TDM Trunk
N3=1 N1=2
N3=1 N1=1
N3=1 N2=2
N3=1 N2=1
N3=1
N3=1
N1 = Number of DSPs in use on Node 1 N2 = Number of DSPs in use on Node 2 N3 = Number of DSPs in use on Node 3
SV8100
K-CCIS IPL DSP Usage
197
Node 1 DT70 0 DT700 0 TD M N1= 1 0 SIP Trunk N1=2 TDM Trunk N1=1 DT70 TD 0 M 0 N2= 1
Node 2 SIP Trunk N2=2 TDM Trunk N2=1 DT70 TD 0 M 0 N3= 1
Node 3 SIP Trunk N3=2 TDM Trunk N3=1
TDM Node 1
N1=1
N1=1
N1= N1= 1 1 N2= 1 N1= N1= 2 2 N2= 1 N1= N1= 1 1 N2= 1 0 N2= 1 0
N1=1 N2=2
N1=1 N2=1
N1= N1= 1 1 N3= 1 N1= N1= 2 2 N3= 1 N1= N1= 1 1 N3= 1 0 N3= 1
N1=1 N3=2
N1=1 N3=1
N1= SIP Trunk N1=2 1
N1=2
N1=1
N1=2 N2=2
N1=2 N2=1
N1=2 N3=2
N1=2 N3=1
TDM Trunk
N1=1
N1=1
N1=1 N2=2
N1=1 N2=1
N1=2 N3=1
N1=1 N3=1
DT700
N1= 1
N1=2
N1=1
N2=2
N2=1
N3=2
N3=1
TDM Node 2
N2= 1 N2=1 N1= 1
N2=1 N1=2
N2=1 N1=1
N2= 1
N2=1
N2= N2= 1 1 N3= 1 N2= N2= 2 2 N3= 1 N2= N2= 1 1 N3= 1 0 N3= 1
N2=1 N3=2
N2=1 N3=1
N2= 2 SIP Trunk N2=2 N1= 1 TDM Trunk N2= 1 N2=1 N1= 1 0 N1= 1
N2=2 N1=2
N2=2 N1=1
N2= N2= 2 1
N2=2
N2=1
N2=2 N3=2
N2=2 N3=1
N2=1 N1=2
N2=1 N1=1
N2= 1
N2=1
N2=1 N3=2
N2=1 N3=1
DT700
N3=2 N1=2
N1=1
N3= 2 N2= 1
N3=2 N2=2
N3=2 N2=1
N3=2
N3=1
TDM Node 3
N3= 1 N3=1 N1= 1
N3=1 N1=2
N3=1 N1=1
N3= N3= 1 1 N2= N2= 2 1 N3= N3= 2 2 N2= N2= 2 1 N3= N3= 1 1
N3=1 N2=2
N3=1 N2=1
N3= 1
N3=1
N3= N3=2 2 SIP Trunk N1=2 N1= 1 TDM Trunk N3=1 N3= 1
N3=2 N1=2 N3=1 N1=2
N3=2 N1=1 N3=1 N1=1
N3=2 N2=2 N3=1 N2=2
N3=2 N2=1 N3=1 N2=1
N3= N3= 2 1 N3= 1
N3=2
N3=1
N3=1
198
SV8100
N1= 1
N1 = Number of DSPs in use on Node 1 N2 = Number of DSPs in use on Node 2 N3 = Number of DSPs in use on Node 3
N2= 1
TCP_UDP Port Numbers
Application
NetLink Primary to Secondary Signalling NetLink Secondary to Secondary Signalling NetLink Replication AspireNet Signalling AspireNet Keep Alive K-CCIS Server Signalling K-CCIS Client Signalling DHCP Server DIM H.323 Extension GRQ H.323 Extension RAS H.323 H.245 H.323 Trunk RAS H.323 Trunk Signalling DTermIP DRS (Registration) DTermIP H.245
Type
TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP UDP TCP
Port
58000 58001 58002 1730 30000 57000 59000 67 5964 1718 1719 5600 20001 1720 3458 10100
SV8100
DTermIP Ready/Answer DTermIP Signalling (handset) DTermIP RTP (handset) SIP MLT Signalling (handset) SIP MLT RTP (handset) IPL RTP UDP UDP UDP UDP UDP UDP 4000 3456 3462 5060 3462 10020 (increment by two per call) 10021 (increment by two per call) 5070 5080 5081 5060 80 8000
199
IPL RTCP Standard SIP Extension Signalling (system) SIP MLT Extension Signalling (system) SIP MLT Extension Session (system) SIP Trunk Signalling WebPro PC Pro
UDP UDP UDP UDP UDP TCP TCP
IPLA Card Size

32IPLA/B 64IPLA/B 128IPLA/B
Type
UDP UDP UDP
Port Range
10020 10083 10020 10147 10020 10275
SIP Configuration Example

SIP Softphone Configuration (CounterPath, X-Lite)
X-Lite is a software based SIP phone, available from CounterPath Corporation. The software is freely available from their website. XLite is a reduced feature version of their commercial software, eyeBeam. If G.729 CODEC is required it is necessary to use the eyeBeam software. 1. 2. Install the application using the Installation Wizard The SIP Accounts dialog will open. Click the Add button
200
SV8100
3.
Configure the Account Properties as per the example below:
Display Name: The name that will appear on the Softphone display User name: The extension number assigned to the extension port Password: The password assigned in Authentication Password in Wizard Advanced Items/IP SIP/SIP Terminal Options/SIP Terminal Setup. (PRG15-05-16) Authorization User name: Same as User name Domain: The IPLA card IP address and port number. 4. 5. Click on OK and Close to exit the configuration dialog The Softphone should register to the telephone system
SV8100
201
Please refer to http://www.counterpath.com/ for further information on this product
ToS Field Values
202
SV8100
Notes: *1 - The description field lists commonly used "code-points". Other values can be implemented but it is unusual for a Network Maintainer to use anything other than the code-points listed. *2 - Layer 3 QoS. These are the values that would be entered into the Priority (Diffserv) area in Wizard Advanced Items/VoIP/ QoS Settings/Layer 3 QoS. (PRG84-10) *3 - IP Ext QoS. These are the values that would be entered into the Type of Service fields in: Wizard Advanced Items/VoIP/Extensions/DTermIP Extensions/DTermIP Extension Basic Setup. (PRG84-03-07/08) for DTermIP extensions, or using the Type of Service and Media ToS fields in: Wizard Advanced Items/VoIP/Extensions/DT700 Setup/DT700 Setup. (PRG84-23-06/13) for DT700 extensions.
SV8100
These values can also be used if the TOS values are manually entered into an IP Keyphone.
203
*4 - This column is provided for information only. It shows the actual bit pattern for the ToS byte. Note that the last two bits are not used for QoS.
Configuration of External DHCP Server

Note: - Although the SV8100 supports DHCP Server functionality, it is only designed for demonstration or test purposes. Please be aware that no support can be offered if the DHCP Server is used on a customers site. It is possible to use either an external DHCP server (e.g. Windows 2003 Server) or the SV8100 internal DHCP server, to provide IP details to the DT700 or DTermIP phones. If you are using an external DHCP server, it is necessary to add a new Option Code to the DHCP scope for the SIP Server (DT700) and/or DRS (DTermIP) address. The method for adding this service varies dependent on the DHCP server used. The example below shows the necessary steps to add Option 120 (SIP Server) to a Windows 2003 Server. 1. Enter DHCP via Administrative Tools. 2. Right click on the relevant DHCP server and click on "Set Predefined Options"
3. When the "Predefined Options and Values" dialogue box opens, click on "Add" 4. Enter the information below in to the "Option Type" dialogue box.
204
SV8100
5. Click OK and this will create a new Option type for the DHCP server.
6. Enter each octet of the SV8100 IPLA card IP address, click "Add" after each octet. The digit 1 must precede the IP Address as shown above. 7. Reorder the octets into the correct sequence using the up and down buttons. Click OK when complete. 8. Right click on "Server Options in the left hand pane and choose "Configure Options".
9. Scroll down the Available Options list and tick "120 SIP Server", click OK.
SV8100
205
10.The DHCP server is now ready to provide DT700 phones with the SIP Server address.
The example below shows the necessary steps to add Option 168(SIP Server Port) to a Windows 2003 Server. 1. In the DHCP server, highlight the server machine on the left hand side. Right click on the server and select Define Vendor Classes.
206
SV8100
2. Click ADD and enter the information show below. The ID and Binary information is entered automatically when you enter the Display name, Description and ASCII value.
3. Click OK
SV8100
207
4. Click Close 5. Highlight the server again, then right click and select Set Predefined Options. 6. Change the Option class to NECDT700.
7. Click ADD and enter the information show below.
208
SV8100
8. Click OK. 9. In the Word box, enter 0x13d8 as shown below.
10.Click OK. 11.Highlight scope options on the left hand side. Then right click and choose Configure Options. 12.Click Advanced and change the vendor class to NECDT700. 13.Place a check mark next to 168 SIP Port, check that 0x13d8 is in the Word box.
SV8100
209
14.Click OK. The DHCP server is now ready to provide IP Phones with the SV8100 SIP Port 5080.
The example below shows the necessary steps to add Option 161(DRS) to a Windows 2003 Server. 1. Enter DHCP via Administrative Tools. 2. Right click on the relevant DHCP server and click on "Set Predefined Options"
210
SV8100
3. When the "Predefined Options and Values" dialogue box opens, click on "Add" Enter the information below in to the "Option Type" dialogue box. Only tick "Array" if multiple DRS servers are required.
4. Click OK and this will create a new Option type for the DHCP server. 5. Enter the IP address of the SV8100 IPLA card in the box labelled "IP Address". (Single address only) 6. If you ticked "Array" in step 2, click "Edit Array" then enter the IP Address of each system and click "Add" after each address. 7. You will need to have the addresses in the correct order in the list so move them up or down using the relevant buttons. The Primary address should be at the top followed by the 2nd and 3rd etc.
SV8100
211
8. Right click on "Server Options in the left hand pane and choose "Configure Options".
9. Scroll down the Available Options list and tick "161 DRS Server", click OK.
212
SV8100
10.The DHCP server is now ready to provide DTermIP phones with the DRS address.

SV8100 VoIP Manual v5.0

Uploaded by

Copyright:

Available Formats

SV8100 VoIP Manual v5.0

Uploaded by

Document Information

Original Description:

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

SV8100 VoIP Manual v5.0

Uploaded by

Copyright:

Available Formats

Voice over IP Manual

Network Addressing Overview

Network Addressing Overview

This shows that an IPLA128 is installed.

This shows that an IPLB64 is installed.

IPLB Layout Information

IPLA Layout Information

IPL Basic Setup

Setup CODEC Mode

SRTP Mode Setup

H.245 Port Preparation Complete Port

Use only IPLB-A

IPLA DSP Information

sRTP Disabled sRTP Enabled

G.723 64IPLA G.711 G.722 G.726 G.729

G.723 128IPLA G.711 G.722 G.726 G.729

sRTP Disabled sRTP Enabled

IPLB DSP Information

sRTP Disabled sRTP Enabled

G.723 64IPLB G.711 G.722 G.726 G.729

sRTP Disabled sRTP Enabled

G.723 128IPLB G.711 G.722 G.726 G.729

PRG84-27-02 Enabled 128 128 128 128

sRTP Disabled sRTP Enabled

SV8100 IPLB Echo Canceller Setup

TDM Echo Canceller Default ERL Level

Used when Program 84-31-01 is set to 1.

TDM Echo Canceller Echo Type

0...disable 1... Line echo canceller 2...Acoustic echo canceller

TDM Tx Level Control

Use to select Transmit level control mode.

TDM Tx LevelControl Level

TDM Tx AutomaticLevelControl Level

TDM Tx HLC Threshold

TDM Tx Gain Compression mode TDM Tx Gain Compression Threshold

TDM Rx Level Control

TDM Rx LevelControl Level

TDM Rx AutomaticLevelControl Level

RTP Echo Canceller ComfortNoise mode

RTP Echo Canceller Tail Length

RTP Echo Canceller Default ERL Level

Used when Program 84-31-19 is set to 1.*

RTP Echo Canceller Echo Type

0...disable 1...Line echo canceller 2...Acoustic echo canceller

RTP Max ERLE

RTP Tx Level Control

Use to select Transmit level control mode.

RTP Tx Level Control Level

RTP Tx HLC Threshold

RTP Tx Gain Compression mode RTP Tx Gain Compression Threshold

RTP Rx Level Control

RTP Rx LevelControl Level

RTP Rx AutomaticLevelControl Level

TDM Echo Canceller NLP mode (4W)

IPLB SIP MLT Codec Information

G.711 jitter buffer average

G.711 jitter buffer max

G.729 jitter buffer min

G.729 jitter buffer average