Release 6 – IP DECT - NEC : Welcome interop... · Web view(Digital Enhanced Cordless...

NEC Technical Assistance Centre

NEC Australia

au.nec.com

Technical Information Bulletin

Release 6 – SV8500 IP DECT

Technical Information BulletinRelease 6 – IP DECT

Table of Contents

Revision History................................................................................................................8

Overview............................................................................................................................9

1 Introduction..............................................................................................................10

1.1 General Description..........................................................................................10

1.2 RFP-PP Communication...................................................................................12

1.3 Beacon Signal...................................................................................................13

1.3.1 General..............................................................................................................13

1.3.2 Beacon Signal and PP.......................................................................................13

1.4 Cluster Arrangement.........................................................................................14

1.5 Handover..........................................................................................................14

2 Configurations..........................................................................................................15

2.1 Typical Configuration........................................................................................15

2.2 Simple Configuration........................................................................................16

2.2.1 Network Configuration.......................................................................................16

2.2.2 Settings in DAP Configurator.............................................................................17

2.3 Branch Office Solution......................................................................................18


2.3.2 Settings in DAP Configurator.............................................................................19

2.4 Routed Head Quarter.......................................................................................20


2.4.2 Settings in DAP configurator..............................................................................21

2.5 Routed Head Quarter with Branch Offices.......................................................22


2.5.2 Settings in the DAP Configurator.......................................................................23

2.6 Routed Head Quarter with Routed Branch Offices...........................................24


2.6.2 Settings in the DAP Configurator.......................................................................25

3 Specifications...........................................................................................................26

3.1 DAP Characteristics..........................................................................................26

3.1.1 General..............................................................................................................26

3.1.2 Common Characteristics....................................................................................26

Document ID: NEC Australia Pty. Ltd. © 2013 2


4 Licenses....................................................................................................................30

4.1 General.............................................................................................................30

4.2 Functional Licenses..........................................................................................30

4.2.1 Maximum number of DAPs................................................................................30

4.2.2 For Future use: CAT-iq Data Licenses..............................................................30

4.2.3 Redundancy Central Site...................................................................................30

4.2.4 Branch Office Survivability.................................................................................30

4.2.5 Software Upgrade Allowance.............................................................................31

4.2.6 Messaging License............................................................................................31

4.2.7 System Assurance License................................................................................31

4.2.8 Upgrading from Release 5 to Release 6............................................................32

4.2.9 DMLS Licenses..................................................................................................33

5 PBX Features............................................................................................................34

5.1 Service Conditions............................................................................................34

5.2 Supported Features..........................................................................................34

5.3 Handset Specifications.....................................................................................35

5.3.1 G266 Handset....................................................................................................35

5.3.2 G266 Features...................................................................................................36

5.3.3 G566 Handset....................................................................................................37

5.3.4 G566 Features...................................................................................................38

5.3.5 I755 Handset.....................................................................................................39

5.3.6 I755 Features.....................................................................................................40

5.3.7 M155 DECT Messenger....................................................................................41

5.3.8 M155 Main Features..........................................................................................41

6. Description................................................................................................................42

6.1 DAP Start-up Process.......................................................................................42

6.2 Handset Subscription/Registration...................................................................43

6.3 Automatic Distribution When DAP Down..........................................................47

6.4 Incoming call to DECT handset........................................................................47

6.5 Outgoing call from DECT Handset...................................................................48

6.6 Handover Operation.........................................................................................49

7. Installation................................................................................................................50

7.1 Customer Requirements / Site Survey.............................................................52

7.2 VoIP Readiness................................................................................................53



7.3 PBX Programming for the SV8500...................................................................54

7.3.1 Service Conditions.............................................................................................54

7.3.2 SV8500 Features...............................................................................................54

7.3.3 Programming.....................................................................................................55

7.3.4 Step-by-Step Procedure....................................................................................55

7.3.5 Call Forward Logout..........................................................................................56

7.3.6 Number Sharing Example..................................................................................57

7.3.7 Digit to Soft key Translation...............................................................................58

7.4 Installing the DAP Controller / Manager...........................................................60

7.5 DAP Configurator..............................................................................................68

8. Setting up the DAP Configurator............................................................................69

8.1 Using the DAP Configurator.............................................................................69

8.2 System Control Section....................................................................................72

8.2.1 General................................................................................................................... 72

8.2.2 System Status Window...........................................................................................74

8.3 Single Site / Multi Site..........................................................................................76

9 DAP CONFIGURATOR SETTINGS..............................................................................77

9.1 Settings Buttons...................................................................................................77

9.2 General Settings..................................................................................................78

9.3 IP Settings............................................................................................................79

9.3.1 The Window............................................................................................................79

9.3.2 IP Settings, tab “DAPs IP Configuration”.................................................................80

9.3.3 IP Settings, tab “DAP Controller IP Configuration”..................................................80

9.3.4 IP Settings, tab “PBX IP Configuration”...................................................................84

9.3.5 CDA IP Configuration........................................................................................86

9.4 Network Settings..................................................................................................87

9.4.1 Network Settings, tab “Network Card Settings”.......................................................87

9.4.2 Network Settings, tab “DHCP Settings”...................................................................88

9.4.3 Network Settings, tab “TFTP Settings”....................................................................90

9.4.4 Network Settings, tab “Leased IP Addresses”.........................................................92

9.4.5 Network Settings, tab “QoS Settings”......................................................................93

9.4.6 Network Settings, tab “Boot options”.......................................................................94

9.5 System Configuration...........................................................................................95

9.5.1 Simple Configuration...............................................................................................95

9.5.2 Multiple Subnets......................................................................................................96

9.5.3 Routed Head Quarter..............................................................................................98



9.6 DECT Settings....................................................................................................100

9.6.1 DECT Settings, tab “DECT Settings”.....................................................................100

9.6.2 DECT Settings, tab “Handset Settings”.................................................................101

9.6.3 DECT Settings, tab “DAP Settings”.......................................................................102

9.6.4 DECT Settings, tab “Synchronization Settings”.....................................................104

9.7 PBX Settings......................................................................................................104

9.7.1 PBX Settings, tab “Handset Sharing”....................................................................104

9.7.2 PBX Settings, tab “Three Party Conference Settings”...........................................105

9.7.3 PBX Settings, tab “NEC PBX Settings”.................................................................106

9.8 “Performance / E-mail Settings”.........................................................................108

9.8.1 Performance / E-mail Settings, tab “PCR Settings”...............................................108

9.8.2 Performance / E-mail Settings, tab “Alarm Settings”.............................................109

9.8.3 Performance / E-mail Settings, tab “Archive Settings”...........................................111

9.8.4 Performance / E-mail Settings, tab “E-mail Settings”............................................112

10.9.5 Performance / E-mail Settings, tab “Miscellaneous Settings”..............................113

9.9 Customer Information.........................................................................................114

9.10 Save System and Start System.......................................................................114

9.11 Finishing Advice...............................................................................................115

9.12 License Handling..............................................................................................115

9.12.1 Install a new License File....................................................................................115

9.12.2 Reading out the Licenses....................................................................................116

10 USING OTHER TFTP SERVER................................................................................119

10.1 General.............................................................................................................119

10.2 Prepare files for TFTP Upload to DAPs...........................................................119

11 DAP Manager – Web Interface........................................................................121

11.1 PROCEDURE: “Opening the DAP Manager WEB Interface”......................121

11.1.1 Actions.............................................................................................................121

11.2 Checking Synchronisation...........................................................................126

11.3 Handover Testing........................................................................................129

12 DAP Controller Redundancy...........................................................................136

12.1 General........................................................................................................136

12.2 DAP Controller Redundancy – How does it work........................................137

12.3 How to Set-Up.............................................................................................139

12.4 DECT Management.....................................................................................141

12.5 Actual Status Indication...............................................................................142



13. Appendix A.......................................................................................................143

13.1 General FAQ’s.............................................................................................143

What is DECT?..............................................................................................................143

What is CAT-iq?.............................................................................................................143

What do I need to order for a new IP DECT installation?...............................................143

What is a PARI?.............................................................................................................143

How many handsets can be supported?........................................................................143

Can the DAPs be mounted outdoors?............................................................................143

How scalable is the IP DECT system?...........................................................................144

What PBX systems are supported?...............................................................................144

What type of durability tests have been done on the handsets?....................................144

AP400 versus AP300.....................................................................................................145

What is the talk and their standby times of the handsets?.............................................146

Li-ion Battery life time.....................................................................................................146

How can the system be expanded?...............................................................................146

Is the NEC IP DECT system GAP compliant?................................................................146

What is a multi-site license?...........................................................................................146

Differences between IP DECT versus VoWLAN............................................................147

13.2 Installation FAQ...........................................................................................148

What is required for Installation of IP DECT?.................................................................148

What if I don’t have a Multicast capable router?.............................................................148

What is the DAP Manager?............................................................................................148

What is the minimum PC requirements for the DAP Manager?.....................................148

Is the DAP Manager required for normal operation?......................................................148

Can I run other software on the DAP Manager PC?......................................................149

What Codecs are supported by the NEC IP DECT system?..........................................149

What is G.729?..............................................................................................................149

When do I need a G.729 license?..................................................................................149

What extra hardware is required for installation?...........................................................149

Is a DHCP / TFTP server permanently required?...........................................................150

DAP does not download configuration file from the TFTP server?.................................150

Installed the DAP’s but handover does not work when walking around?.......................150

Cannot make call on DECT handset?............................................................................151

Poor voice quality on DECT handset?...........................................................................152

How can I determine if the DAPs are synchronized?.....................................................153

What happens if there is not enough signal strength between the DAP’s for synchronization?............................................................................................................153

How can I check the Radio Signal Strength?.................................................................153

How can I check what firmware version the DAPs are running?....................................153



How can I upgrade the firmware on the DAPs?.............................................................153

Can the DECT handsets move between sites?..............................................................153

What is required to run a DAP in a Branch Office?........................................................154

When will the DAP select G.711 and when will it select G.729?....................................155

If I am running a DAP in a Branch Office, what happens if there are no G.729 licenses?....................................................................................................................................... 155

What happens if a DAP goes down?..............................................................................155

How can Handover be checked?...................................................................................156

When I answer an incoming call on the handset by pressing the off-hook button after removing it from the charger the call is dropped............................................................156

Deadlock situation on Gx55 (PIN code forgotten)..........................................................156



Revision History


Version Number Revision Date Summary of Changes Author

1.01 12 June 2014 Updated IP DECT TIB Brett Byleveld


Overview

Title Release 6 – IP DECT

Product Category IP DECT Mobility

Product IP DECT

System Type / Application SV8500

Software Version / Application 6.00.100 NEC_INT

Distribution ☐ Internal Only ☒ External or General Release

General Information System Installation, Configuration and Maintenance

Other Supporting Document

Author Brett Byleveld



1 Introduction

1.1 General Description

The DECT (Digital Enhanced Cordless Telecommunication) System allows mobile users to use the switched telecommunication facilities provided by a PABX / SIP Proxy system. Such a mobile user can make or receive calls by using a cordless handset. Many call handling facilities of the SIP Proxy are available on the cordless handset. As the cordless connection is a digital connection, other services will also be possible in the future.

Mobile users carry a portable handset which uses a radio transceiver to communicate with the DECT System. The portable handset is called a Portable Part (PP) according to the DECT standard.

A radio transceiver in the DECT System is called the Radio Fixed Part (RFP) according to the DECT Standard. The RFP is also referred to as a base station. However, in the Business Mobility IP DECT configuration, the RFP is comprises more than just a transceiver, and is therefore called: DAP (DECT Access Point).

Figure 1-1 shows a general DECT system setup.

Figure 1-1 “DECT System Parts (General)”



Figure 1-2 shows a general IP DECT Solution. It shows the basic system setup for the Business Mobility IP DECT system.

Note: - This Figure shows a general system set-up. If applied to the NEC IP DECT configuration, then:

DECT System IP Based = DAP Controller

PBX = PBX type that is supported by NEC IP DECT

RFP = DAP (DECT Access Point)

Figure 1-2 “DECT System Parts in an IP Solution as Add-on to a PBX”

The radio area covered by a single RFP (DAP) is called a cell. The RFPs (DAPs) are located so that the cells overlap slightly and the PP can remain in contact with the DECT system when moving from one cell to another. A group of cells belonging to one DECT system is called a cluster. According to the DECT standard, the maximum number of simultaneous calls per RFP can be 12. (The DAP in the Business Mobility IP DECT supports up to 12 simultaneous calls, depending on the licenses.)

The number of RFPs (DAPs) needed to cover a certain area (within which the mobile telephone users might roam) depends on many factors such as:

- The size of the area.

- The nature of the area:

o The number and the size of buildings in the area.

o The radio propagation characteristics of the building(s).

o Materials used for walls, floors, elevator shafts, reinforced glass, doors etc.

o Strong magnetic fields in the area (e.g. as result of welding equipment, radar, etc.).

- The amount of telephone users in an area, and how often they make or receive calls.

The speech signal through the air will be encrypted, if the portable handset allows it, to ensure the privacy of the conversation. This encryption is done fully automatically, without the intervention of a technician.



1.2 RFP-PP Communication

The radio link between the RFP and a PP can carry information on any one of ten carrier frequencies and in one out of twelve pairs of time slots (12 in each direction). The ten carrier frequencies are separated by 1728 kHz. The frequency range depends on the region where DECT is used:

- 1880 MHz - 1900 MHz for European countries (Used here in Australia)- 1910 MHz - 1930 MHz for Latin America region - 1900 MHz - 1920 MHz for China - 1920 MHz – 1930 MHz North America (lower transmission power, –3 dB)

The modulated date rate is 1152 kb/s. DECT uses in the OSI physical layer the following multiplexing techniques:

- FDMA (Frequency Division Multiple Access); - TDMA (Time Division Multiple Access); - TDD (Time Division Duplex).

The RFP-PP communication radio signal carries time division multiplexed frames; each frame is 10ms long. Each frame contains 12 time slots which carry data from RFP to the PPs, and 12 time slots which carry data from PPs to the RFP. This means that two time slots in every frame are needed for a full duplex connection to a PP. See Figure 1-3

0 1 2 3 4 9 10

11 12 13

14 15

16 21 22 23

Figure 1-3 “Carriers and Timeslots in the DECT Air Interface”

Each time slot may carry 32kbs Adaptive Differential Pulse Code Modulated (ADPCM) speech/user data. Each time slot pair can contain ADPCM speech/user data on any one of the ten carrier frequencies so that the RFPs carrier frequency often needs to be changed between time slots: Refer to Figure 1-4. The information within the time slot does not completely fill the time slot; time is allowed for propagation delays, ramp up and ramp down of the transmitter and for switching of the carrier synthesizer between slots.

0 1 2 3 4 5 6 7 8 9 10 11

12 13

14 15

16 17 18

19 20

21 22 23

F2 F7 F5 F2 F9 F3 F6 F8 F4 F6 F2 F7 F2 F7 F5 F2 F9 F3 F6 F8 F4 F6 F6 F7


F1

F10

10 ms frame

12 timeslots RFP to PP 12 timeslots PP to RFP

Time slot

Frequency

10 ms frame

12 timeslots RFP to PP 12 timeslots PP to RFP


Figure 1-4 "Each time slot can use any of the 10 Carrier Frequencies”

A PP can use any of the 12 time slots (in each direction) on any of the 10 frequencies for a full duplex connection. So a maximum of 120 full duplex channels are available for connections to the PPs, within a cluster of a micro-cellular DECT system. In fact, this is only possible under ideal conditions; no disturbance, no interference, no other channels used, etc. Normally the conditions are not ideal in office or factory buildings, but the number of channels available will still be more than sufficient.

Note that there is always a fixed relation between the downstream timeslot number (from RFP to PP) and the upstream timeslot number (from PP to RFP) in one connection:

- Upstream timeslot number = downstream timeslot number +12. - Upstream and downstream timeslot in one connection use always the same carrier

frequency.

1.3 Beacon Signal

1.3.1 General

The beacon signal is a signal which is transmitted by an RFP in case the RFP is idle (no active calls).

This beacon signal contains the System Identifier of the DECT System, the so called PARI (Primary Access Rights Identifier) and the number of the RFP, the RPN (Radio Part Number). By means of this information the PP recognizes to which system a signal belongs, and whether it is subscribed to that system or not. When there is a call for a PP, it also contains paging information.

When the RFP is not idle (there is an active call via the RFP), the beacon signal information is also transmitted in the call connection. Therefore, the beacon signal is not necessary at an RFP which has one or more calls active. In the DECT application in the Business Mobility IP DECT, there are two beacon signals transmitted per RFP (DAP) when the RFP (DAP) is in idle condition. If there is a call only one beacon signal remains active. When there are a number of calls via the RFP (DAP), no beacon signal is transmitted anymore.

1.3.2 Beacon Signal and PP

When the PP is in idle condition (not involved in a conversation) it scans the environment for the signals of a nearby RFP (DAP). It locks onto the best signal that can be found. This signal can be a beacon or a channel which is used for a call, because such a channel contains the beacon signal information.

The PP uses the signal to synchronize its timing with the central system, and then it monitors the information transmitted via that RFP for calls to itself.

If the PP detects too many errors in the received signal (due to interference or weak signal) the PP tries to find another better signal and locks onto another RFP.

In this way, the PP user can move around the area from cell to cell and remain in contact with the DECT system via a radio link with a very good quality.



1.4 Cluster Arrangement

A cluster is defined as a logical group of radio cells belonging to one DECT system. Within this arrangement bearer handover is possible. Figure 1-5 shows an ideal cluster arrangement of radio cells in which each cell has a boundary with a number of other cells. An omnidirectional radio signal is transmitted equally in all directions so that the actual radio signal from the RFP in cell 1 overlaps slightly into cell 2, cell 3, cell 4, and so on. Similarly, the radio signal from the adjacent cells overlaps into cell 1. So, cell 1 can be seen as the centre of a cluster of cells. If a certain frequency is used in a certain timeslot in cell 1, it cannot be used in any of the adjacent cells in the same timeslot because of interference at the cell boundary. But that same frequency can be used in cell 8.

Thus, within a cluster a certain channel/frequency combination can be used again, simultaneously, only if the cell which uses such a combination does not interfere with another cell which uses the same combination.

Figure 1-5 “Cluster Arrangement”

1.5 Handover

Both the RFP and PP monitor the quality of the radio link. If the interference on a certain carrier frequency and timeslot combination causes problems, it might be necessary to switch to another frequency and/or timeslot at that same base station. This is called intra-cell handover. This handover procedure requires that the connection can be supported on 2 channels simultaneously, for a while, to allow a "seamless handover" (no breaks and hiccups during the handover). First, the new channel is chosen and the connection is set up via this channel, while the old channel is still in use. Then the old channel is disconnected.

If the mobile user roams from one cell to another, during the conversation, they go out of range of the first RFP and into the range of the second. When this happens, the quality of the transmission requires it to switch over to the radio link to the new RFP. This is called inter-cell handover. Once again it is a seamless handover.


88

Overlapping radio signals(In a real installation, this area would be wider)

1

Radio Signal Interface from one cell into another cell

3

4 2


Note: A handover is always initiated by the PP!



2 Configurations

The NEC IP DECT system delivers all the benefits of IP-based converged communications with the convenience of wireless communications. Designed to support a large number of DECT Access Points (DAP’s) to cover multi-site business or campus environments, the NEC IP DECT system allows mobile users to carry a wireless DECT phone and have access to most of the features they are accustomed to at their desk. The system can be configured to provide connection for remote offices by simply installing a DAP at the remote office with no additional equipment required.

The NEC IP DECT system consists of the following components:

DECT Access Points (DAP’s)

DECT Handsets (G266, G566 and I755 models)

M155 Messenger for Health Care

DAP Controller software for Configuration and Maintenance.

DECT Messaging and Location Server (DMLS)

2.1 Typical Configuration

The IP DECT system must be implemented in a company infrastructure. All configurations are based on using one IP DECT system (DECT Cluster) in the network. You should consider which configuration you must implement at the customer site.

DAP Lite System Simple Configuration Branch Office Solution Routed Head Quarter Routed Head Quarter with Branch Offices Routed Head Quarter with Routed Branch Offices

Note 1:- All IP switches that are involved must support IP multicast, with “IGMP snooping” disabled.

Note 2: - Furthermore, disable “Spanning Tree Protocol” on ports that are used for DAPs and set the switch ports to “fast forwarding”.



2.2 Simple Configuration

2.2.1 Network Configuration

Figure 2-2-1 shows an example of a simple configuration. All IP DECT devices are put in one subnet. This subnet is based on one or more IP switches. If the switches serve more than one VLAN, all IP DECT devices are put in one VLAN (therefore behaving as one subnet).

Figure 2-2-1 “Simple IP DECT configuration”

The subscription data is stored in the DAP’s.

All of the IP DECT Access Points are connected to the same network segment / VLAN.

Seamless handover is supported across all DAP’s.

The DAP Manager is temporary needed in the following cases:

- During InstallationDuring installation the DAP manager is needed to enter license information, extension numbers, subscribe handsets etc.

- ManagementFor any System Management action, the DAP Manager is required.

- Replacing a DAPWhen you replace a DAP be aware that it may contain subscription data. Therefore, you need to open the DAP Manager WEB interface and execute a delete DAP. Then the subscription data that was in this DAP is put into the remaining DAP’s. If you put a new DAP in place, initially it will contain no subscription data. Only after executing a subscription procedure, will it contain subscription data.



2.2.2 Settings in DAP Configurator

Figure 2-2-2 is an example of a setup for simple configuration for the DAP Configurator.

Figure 2-2-2 “Simple DAP Configuration”



2.3 Branch Office Solution


Figure 2-3-1 is an example of a Branch Office configuration with a main office (head quarter) and a Branch Office. The Main Office and the Branch Office are in different subnets connected via routers. Routers can be connected over the WAN.

Figure 2-3-1 "Example of an IP DECT configuration with a Branch Office"

The general characteristics of an IP DECT configuration with Branch Offices are as follows:

- Allows interconnections with limited bandwidth between Head Quarter and Branch office(s).

- Allows interconnections with poor QoS between Head Quarter and Branch office(s). (Radio Links, ADSL etc.)

- No PBX needed in Branch Office (!). - Seamless handover is supported in Branch Offices and in Main Office. - No handset handover between Head Quarters and (individual) Branch Offices. - Head Quarter and individual Branch Offices must be in separate subnets (router(s)

needed). - No IP multicast support required for Routers. - Multicast TTL = 1, which means that IP multicast packages does not cross a router.



2.3.2 Settings in DAP Configurator

Figure 2-3-2 is an example of a setup for Branch Office configuration for the DAP Configurator.

Figure2-3-2 “Branch Office Configuration”



2.4 Routed Head Quarter


Figure 2-4-1 shows an example of a Routed Head Quarter configuration with a head quarter and two subnets connected via one or more routers. The subnets in the network are part of one company network.

Figure 2-4-1 “Example of an IP DECT Routed Head Quarter Configuration”

The general characteristics of an IP DECT Routed Head Quarter configuration are as follows:

- Used for a Large Campus network that is split up into different (geographical) subnets.

- The network supports QoS and IP connectivity all over the Campus.

- IP DECT configuration behaves as one large IP DECT system.

- Full support of seamless handover between all DAPs in the IP DECT system.

- Routers must support IP Multicast routing.

- The IP Multicast address for IP DECT is the same in all segments.

- Multicast TTL > 1, which means that the routers pass on the IP multicast packages.

- In the IP DECT configuration, you must enter the subnet mask that is needed to cover all networks (e.g. 255.255.252.0) for up to four subnets as in the previous example.



2.4.2 Settings in DAP configurator

Figure 2-4-2 is an example of a setup for Routed Head Quarter configuration for the DAP Configurator.

Figure 2-4-2 “Routed Head Configuration”

Please note that the TTL is the TTL value for IP Multicast, which must allow Multicast traffic over the Routers in the Routed Head Quarter. That should be higher than 1, but based on the TTL settings in the Router, it is advised to use a TTL value of 32.

Please note that the aggregated subnet mask is the subnet mask that includes all three networks in the Head Quarter. So, this is NOT the IP subnet mask on the Network adaptors on the IP Network segments. Please do not mix up the Aggregated Subnet Mask and the normal IP Subnet mask.



2.5 Routed Head Quarter with Branch Offices


Figure 2-5-1 "Example of an IP DECT Routed Head Quarter configuration with Branch Office" shows an example of a Routed Head Quarter configuration with a head quarter, one subnet connected via one or more routers and a Branch Office. The subnets in the network are part of one company network, the Branch Office is connected over the WAN (or low throughput LAN).

Figure 2-5-1 "Example of an IP DECT Routed Head Quarter configuration with Branch Office"

The general characteristics of an IP DECT Routed Head Quarter configuration with Branch Office(s) are as follows:

- Hybrid of Routed Head Quarter and Branch Offices (see previous sections).

- Used for a Large Campus network that is split up into different (geographical) subnets in combination with (remote) Branch Offices.

- In the Routed Head Quarter part, all characteristics which are mentioned previously for the Routed Head Quarter are applicable.

- For the Branch Office, all characteristics which are mentioned in the section covering the Branch Offices are applicable.

- In the Head Quarter the Multicast TTL >1, in the branch Office the Multicast TTL =1(!).

- Edge Router, connected to the WAN, should not forward Multicast packages to the WAN.

- Full support of seamless handover between all DAPs in the Head Quarters configuration with the subnet.

- Routers in the Head Quarter must support IP Multicast routing.



- In the IP DECT configuration, you must define which subnets are in the Head Quarters and which subnet(s) is/are Branch Office subnets. You must do that by means of specifying the subnet mask that is needed to cover all Head Quarters sub-networks (e.g. 255.255.252.0 for in this example.).

2.5.2 Settings in the DAP Configurator

Figure 2-5-2 “Routed Head Quarter with Branch Office Configuration” is an example of a setup for a Routed Head Quarter with Branch Office configuration for the DAP Configurator.

Figure 2-5-2 “Routed Head Quarter with Branch Office Configuration”



2.6 Routed Head Quarter with Routed Branch Offices


Figure 2-6-1 shows an example of a Routed Head Quarter configuration with a head quarter, one subnet connected via one or more routers and a Branch Office. The subnets in the network are part of one company network, the Branch Office is connected over the WAN (or low throughput LAN).

Figure 2-6-1 "Example of an IP DECT Routed Head Quarter configuration with Branch Office"

The general characteristics of an IP DECT Routed Head Quarter configuration with Routed Branch office are as follows:

- Hybrid of Routed Head Quarter and Branch Offices (see previous sections).

- Used for a Large Campus network that is split up into different (geographical) subnets in combination with remote Routed Branch Offices.

- In the Routed Head Quarter part, all characteristics which are mentioned previously for the Routed Head Quarter are applicable.

- In the Routed Branch Office part, all characteristics which are mentioned previously for the Routed Head Quarter are applicable, except for that the Routed Branch Office must be in different subnets than the Routed Head Quarter.

- In the Head Quarter the Multicast TTL >1, and in the branch Office the Multicast TTL >1(!).

- Edge Router, connected to the WAN, should not forward Multicast packages to the WAN.

- The Routers between the Routed Head Quarter and the Routed Branch Office should block Multicast!



- Full support of seamless handover between all DAPs in the Head Quarters configuration with the subnet. Full support of hand over in the Routed Branch Office. No handover between the Routed Head Quarter and the Routed Branch Office.

- Routers in the Head Quarter must support IP Multicast routing.

- Routers in the Routed Branch Office should support IP Multicast Routing.

- In the IP DECT configuration, you must define which subnets are in the Head Quarters and which subnet(s) is/are Branch Office subnets. You must do that by means of specifying the aggregated subnet mask that is needed to cover all Head Quarters sub networks (e.g. 255.255.252.0 for in this example.). Also in the Routed Branch Office, you must calculate the aggregated subnet mask that covers all subnets in the Routed Branch Office.

2.6.2 Settings in the DAP Configurator

Figure 2-6-2 is an example of a setup for a Routed Head Quarter with Routed Branch Office configuration for the DAP Configurator.

Figure 2-6-2 “Routed Head Quarter with Routed Branch Office Configuration”

Note: The Netmask Length in both items in the screenshot above is the Aggregated Subnet Mask, not the real subnet mask.



3 Specifications

3.1 DAP Characteristics

3.1.1 General

The following DAP type exists:

- AP200 Series, no longer available.- AP300 Series, no longer available.- AP400 Series, current.

All of these DAPs share common characteristics. These characteristics are described in section 3.1.2 “Common Characteristics”

Note: - With Version 6 DAP Controller, The AP400 / 300 / 200 will all operate together.

3.1.2 Common Characteristics

Features

Note: The following list contains features that are only supported if the PBX supports it at well.

DECT GAP and CAP compatible.

DECT Seamless handover.

DECT Low Rate Messaging Service (LRMS) (Max. number of characters depends on the type of handset used.)

CLIP and Name Display.

Enquiry

Call Progress tones.


AP400 AP300 AP200


DTMF tones.

Message Waiting indication.

DAP Software downloadable.

Capacity Max. Number of simultaneous calls: 12 Please note that this maximum number of calls is

only applicable when the DAP is synchronization source/master. If the DAP is not the synchronization master, the maximum number of simultaneous calls is 11. Also note that the maximum number of simultaneous calls per DAP is also limited by licenses in a licensed version of IP DECT.

Max. number of simultaneous calls: 11

Max. number of simultaneous call in HD-Voice Quality (G722): 5

Max. number of DAPs: 750

Max. Number of extensions is 18750 (this number is restricted by the maximum number of extensions supported by the host PBX system)

IP Interface Characteristics 100 Base-T Full duplex, full support of auto-negotiation in Ethernet Switch

Maximum cable length according to the IEE802.3 specification (100 meters).

Audio Coding: G711, G729ab and G722 for CAT-iq.

DTMF generation: H.245

Call control protocol: Proprietary.

IP protocols: DHCP and TFTP

Multicast: IEEE 802

SIP Protocol Support – Refer to SIP RFC Support

SIP RFC Support

RFC2246 – TLS RFC3325 – Asserted ID

RFC2327 – SDP RFC3428 – Instant Messaging

RFC2822 – Date & Time RFC3515 – REFER

RFC2833 – DTMF in RTP RFC3578 – Overlap Signalling to SIP

RFC2976 – INFO RFC3665 – Basic Call Flow example

RFC3261 – SIP Basic Call RFC3711 – Secure RTP

RFC3264 – Answer-Offer RFC3842 – MWI

RFC3265 – MWI RFC3891 – Replaces Header

RFC3311 – Established Session Modification RFC4568 – SDP

Environmental Conditions Storage temperature range: -25º to +60º Celsius

Transport temperature: -40º to +70º Celsius



Operational temperature: 5º to +45º Celsius

With optional outdoor box: -20º to +45º Celsius

The temperature ranges of the AP400: Temperature range AP400: -5 º to 45 º Celsius.

The AP400 should not be exposed to sunlight!

The outside temperature range for the AP400 (all types) mounted in the Outdoor Cabinet is as follows:

Minimum outside temperature: -20 º C

Maximum outside temperature: 45 º C

Note: The Outdoor Cabinet should not be exposed to sunlight!

DAP Manager Platform Windows 2003 Server SP2 or higher Windows 2008 SP2 Windows 2008 R2 Windows XP Professional SP2 or higher Windows 7 (Professional, Enterprise and Ultimate) Browser: Internet Explorer 6.0 or higher CPU: Minimum 2.4 GHz RAM: Minimum 1 Gb

Air Interface DECT operation in dedicated frequency band 1880 – 1900 MHz Dual Omni-directional internal Antennas. RF output: 10mW average per channel at antenna connection. Sensitivity: Typical -90dBm measured at antenna connection at BER = 0.001 Location Detection Optional AP400E allows for external antenna connection. 8dBi directional antenna available Typical range: Indoor 50m max, Outdoor 300m max Note: - The radio coverage of DECT equipment depends on the environment and

presence of obstacles. Channels: 12 channels providing max. 11 simultaneous calls per AP400. Roaming and seamless handover. Secure DECT authentication on all channels.

Power Supply Power over Ethernet (PoE): 36-57V over spare wire pairs and phantom feed: IEEE802.3af

(Class 2)

Service / Maintenance Software upgrading via air interface Software upgrading via headset connector (2.5mm) Software upgrading of handsets via air interface LED status indicator WEB access (via DAP Manager)



Direct access from DAP Manager application PC

Physical Characteristics 146x174x43 mm (wxhxd) including antenna part mounted horizontally 146x147x69 mm (wxhxd) including antenna part mounted vertically Weight: 302 grams / 306 grams for AP400E ABS/Polycarbonate Housing: White (RAL9010), antenna part light grey (RAL7035) Optional outdoor housing box class IP66 Package contains AP400 mounting materials



4 Licenses

4.1 General

From IP DECT Release 6.0 onwards, licenses are introduced. All licenses has to be entered into the DAP Controller.

4.2 Functional Licenses

The following functional Licenses are available:

4.2.1 Maximum number of DAPs

You must have a license for the number of DAPs. Please note that the total number of DAPs that you specify in this license is the sum of license unities of 10 and 50 licences. E.g. when you have 70 DAPs, you need one license for 50 DAPs and 2 licenses for 10 DAPs. (1x50) + (2x10).

The maximum number of DAPs in a certain configuration is as follows:

- 256 (type: AP400, AP400E) - 750 (type: AP400, AP400E) in case you also have the “Big Projects License”.

Refer to section 4.2.5 Software Upgrade Allowance

4.2.2 For Future use: CAT-iq Data Licenses

Please note that this license is not yet available and is planned for future use.

4.2.3 Redundancy Central Site

This license is required to have a redundant DAP Controller in the Central site. Ensure that the redundant DAP Controller would be on a separate server.

4.2.4 Branch Office Survivability

You need this license to allow Local DAP Controllers in one or more Branch Office locations. You need one license per Branch Office.



4.2.5 Software Upgrade Allowance

To upgrade a Release 6.0 system to a higher version, you need an Upgrade License. The Software Upgrade license shows you a date. DAP firmware released before that date can be installed in the system at any time. DAP firmware released after that date cannot be installed on the system.

Please note that this license is made dependant on the system size. The steps are:

10 DAPs

50 DAPs

100 DAPs

256 DAPs

Please note that the total number of DAPs is the sum of the licences. E.g. when you have 70 DAPs, you need one license for 50 DAPs and 2 licenses for 10 DAPs. (1x50) + (2x10).

4.2.6 Messaging License.

Messaging is licensed in the DMLS (DECT Message and Location Server) and in the DAP Controller. Licenses are exchangeable between the DMLS and the DAP Controller, so if you have a licence for DMLS, you can import that license into the DAP Controller and vice versa. In the DAP Controller, the license is related to the number of DAPs in the system and should be the same number as specified in the first item in this list of licenses.

Location Detection License, on top of the Messaging License. This license is available on the DMLS and also in the DAP Controller. Licenses are exchangeable between the DMLS and the DAP Controller, so if you have a licence for DMLS Location Detection, you can import that license into the DAP Controller and vice versa. The Location detection license is applicable for single point and multipoint on the DMLS. When you order the license, you must order it on top of the Messaging License. In the DAP Controller, the license is related to the number of DAPs in the system and should be the same number as specified in the first item in this list of licenses.

4.2.7 System Assurance License

The system assurance license is a license to allow software upgrading from Release 6.0 to higher versions. The license is based on the number of DAPs.

Note that there are two ways to get the Software Upgrade License:

- By means of the NEC ordering tool.

When you get a license, it shows you an upgrade date. At any time, you can install new DAP firmware that has a release date that lies before the date in your license.



4.2.8 Upgrading from Release 5 to Release 6

IP DECT Release 5 was license free, in IP DECT Release 6.0 and higher you need license for the various functions and features.

When you upgrade from Release 5 to Release 6, the system will automatically generate a license file with all the features that your system had in Release 5. So, you do not need to have a license prior to upgrading.

This license has the following characteristics:

- It will cover all existing system configuration.

- It is Free of Charge.

- It shows an upgrade date of one month after you have done the upgrade. This means that you can install DAP firmware with a release date that lies before the upgrade date of one month that is shown in your license.

You must send the license file that is generated to NEC for registration.

For new features, you must order a new license.



4.2.9 DMLS Licenses

From Release 6 onwards, the DMLS is licensed in the DAP Controller License mechanism. You don’t need a dedicated license for the DMLS anymore. The license is based on the number of DAPs.

In the DAP Controller, there is a license for “DECT Messaging” and for “DECT Location detection”. The Location Detection license is on top of the Messaging License.

There are two options to enable the DMLS Messaging/Location feature:

DMLS License String When you already have a DMLS license string, you can use that license in the DMLS and you can import that license string into the DAP Controller License mechanism by means of the button “Add DMLS”. Please note that this is applicable for the Messaging license as well as for the Location license.

DAP Controller License for Messaging and perhaps also Location detection. When you have a license for Messaging or Location detection on the DAP Controller, you can synchronize the DMLS application with it. The DMLS can retrieve the license data from the DAP Controller license mechanism by means of one button.



Note: - When you have a “CTI license” for Messaging on the DAP Controller, you do not need to have the Messaging license in the DAP Controller.

5 PBX Features

5.1 Service Conditions

ACD and Hotel features are not supported for IP DECT handsets. Not all IP DTerm features are supported of IP DECT handsets. See feature list below

for supported features

5.2 Supported Features

Call Forwarding (All / Busy / Nans / Logout) Call Park

Call Pickup Groups / Direct Call Transfer / Consultation hold

3 Party Conference 8 / 16 / 32 Party Conference

Music on Hold Call Waiting

Executive Override / Right of Way Distinctive Ringing

Account Codes Authorisation Codes

Night Connection Station Station Hunting (UCD / Hunt Groups)

Message Waiting Indication Name Display

Terminal Logout Mute Key

Hotline System Speed Dial

Call Back – Note Call Waiting Originating - Note

Note: - Supported DAP Configurator soft key feature.



5.3 Handset Specifications

5.3.1 G266 Handset



5.3.2 G266 Features



5.3.3 G566 Handset



5.3.4 G566 Features



5.3.5 I755 Handset



5.3.6 I755 Features



5.3.7 M155 DECT Messenger

5.3.8 M155 Main Features

The main features of the M155 are: - Illuminated LCD display with 1 icon line and 3 texts lines (each 42 characters) - Messaging (LRMS) - Message Broadcast support (incoming messages) - Message Waiting Indication - Predefined set of messages for sending (5) - SOS call or message - Personal phone book with 5 entries - Always loud speaking for hands free communications - Reject incoming call - Auto answer for all incoming calls or for internal incoming calls only - Ringer melody selection (12) - Silent charging - Separate ring melodies for urgent and emergency messages (not changeable) - Vibrator function - 5 selectable languages - Up to 8 Hrs. Talk time and 80 Hrs. Standby time - Firmware upgrading over the DECT air interface (needs to be supported by the DECT

system as well)



6. Description

6.1 DAP Start-up Process

The DECT Access Point must be configured by using a DHCP Server and TFTP Server. The following are the steps required to configure a DAP.

1. DHCP Server is configured to assign network settings to the DAP as well as inform the DAP of the Address of the TFTP server and name of the configuration file to download. This is programmed in option code 66 (Referred to as “Next Server Address”) and option code 67 (Referred to as “Boot file name”) respectively.

2. The configuration file is generated using the DAP Configurator tool and copied to the TFTP server.

3. On powering up, the DAP will act as a DHCP client to obtain network settings from the DHCP Server. It will broadcast a DHCP Discover message.

4. The DHCP Server will then offer an IP Address to the DAP and inform it of other settings and options.

5. Once the network settings have been obtained from the DHCP Server, the DAP, which now knows the Address of the TFTP server and the name of the file to download, will act as a TFTP client and request to download the configuration file from the TFTP Server.

6. The TFTP server will then transfer the configuration file to the DAP. Once the file has been transferred the DAP will contact the DAP Controller (DC) and the connected PBX.

For small installations where a customer might not have a DCHP / TFTP Server, the DAP Configurator Tool can be used to provide both or one of these functions on the network. Refer to Section 7.6 for details.

Note: It is important that the In-built DHCP server in the DAP Manager is not used on the same network segment as another DHCP server. Only one DHCP server can be used on a network segment at once.


1. IP Address2. Subnet Mask3. Default Gateway4. TFTP ServerName (Option 66)5. Boot File Name(Option 67)

DHCP Server

TFTP Server

DAP Configurator DAP

Config.txt

(1)

(2) (1)

(6)

(5)

(4)

(3)


6.2 Handset Subscription/Registration

Before you can use a handset, the handset must be subscribed to the DECT system. Besides that the handset must be registered in the SV7000/SV8500. Subscription requires manual intervention, registration is done automatically. Figure 6-2 shows the phases in the subscription process in a SV7000/SV8500 environment.

Figure 6-2 “Phases in the Subscription Process in SV7000/SV8500 environment”

The following phases are distinguished in the subscription process.

1. The administrator starts a subscription process via the DECT Manager WEB page. This WEB page is accessible from a WEB browser in the network. Please refer below:



2. The administrator “enables” a subscription, which means that the subscription process is started. The IP DECT System is now waiting for action from a handset.

3. Now the subscription must be executed from the handset. The handset user must enter the PIN code that is displayed on the DECT Manager WEB page. When the PIN code is entered on the handset, the subscription record is created in the DAP Manager Database.

4. The DAP Manager will distribute the subscription data to one of the DAPs. Distribution has the following characteristics:

- The DAP Manager tries to distribute the subscription records equally over the DAPs. - The maximum number of subscription records per DAP is 25. - Once a subscription record is stored into a DAP, it will normally not be moved to another

DAP anymore. There are two exceptions on this: If you “Delete” a DAP manually from the DAPs list in the DECT Manager, the subscription records of that DAP will be distributed over the remaining DAPs. If the handset moves to/from a branch office, the subscription record moves with the handset to/from the branch office. Moving subscription between main site and branch office(s) is activated when the handset does a “location registration” in the main site or branch office.

Note: - The DAP Manager must be active to make this moving possible.

- If DAPS are connected in a Branch office, the Branch office is regarded as a subscription island. The subscription record for a handset is either in a DAP at the main site or in a DAP at (one of) the branch office(s). When a handset executes a “location registration” at the main site or one of the branch offices, the subscription record is moved to the island where the location registration was done.


PIN Number


5. The DAP sends a Registration to the SV7000 / SV8500 using the Protims protocol.

After the subscriptions are executed, each DAP contains a number of subscription records. The DAP Manager contains subscription data of all handsets in the system. If the DAP Manager is disconnected, the system remains operational.

The subscription records in the DAPs are stored in Flash Memory.



Figure 6-3 “Subscription Locations”



6.3 Automatic Distribution When DAP Down

When a DAP goes down, the subscription records in that DAP are no longer accessible and therefore, the associated handsets cannot be used anymore. However, the subscription records of a broken DAP are automatically distributed over other DAPs after 10 minutes down time. This time is adjustable; the shortest time is 5 minutes.

This automatic distribution requires that the DAP Manager must be up and running. If not, automatic distribution does not take place!

When you connect the DAP Manager after a DAP went down, the timer starts from the moment that the DAP Manager is up and running. This means that you can replace the faulty DAP with a new one, moving the original subscriptions to the new DAP within those 10 minutes. This time is configurable.

6.4 Incoming call to DECT handset

The following describes the operation of the DAP’s when a DECT handset receives an incoming call.

1. The Dterm user initiates a call to the DECT handset. The Dterm sends a call setup request to the PBX for the DECT extension number.

2. The PBX with knowledge of the IP Address of the DECT user, being the DAP that is storing the subscription record of the handset and has sent the DRS login message to the PBX, sends a call setup request to the DAP.

3. The DAP receives the call setup request and needs to locate the handset in the building. It thus sends a Multicast packet to all other DAP’s to determine which DAP currently has the handset locked.


PABX

Signalling

RTP

Who has the handset

locked?

(1)

(2)

(3) Multicast


4. The DAP which currently has the handset locked onto the Air interface will respond and setup an RTP stream (voice connection) with the peer endpoint being the Dterm. The DAP with the subscription record will continue to handle the signalling to the PBX.

6.5 Outgoing call from DECT Handset

The following describes the operation of the DAP’s when a DECT handset generates an outgoing call.

1. The DECT user initiates a call to the Dterm handset. The DAP which currently has the DECT handset locked will send a Multicast to all other DAP’s to find out which DAP is currently storing the subscription record of the handset.

2. The DAP that is storing the subscription record will respond. 3. The DAP with the subscription record will then send a call setup request to the PBX. 4. The PBX sends a call setup request to the Dterm handset. The RTP stream will be setup

by the DAP that currently has the handset locked via the air interface. All signalling will continue to be handled by the DAP with the subscription record.


PABX

Signalling

RTP

Who has subscription

record?

(4)(3)

(1) Multicast

(2)


6.6 Handover Operation

The following describes the operation of the DAP’s when a DECT handset handover occurs.

1. The DECT user has an existing voice connection with the Dterm user. 2. The DECT user moves out of radio coverage of the first DAP and into coverage of the

second DAP. The handset needs to initiate handover. 3. The 2nd DAP detects that the handset is requesting a handover and sends a Multicast

packet to all other DAP’s to determine which DAP currently has the existing voice connection.

4. The DAP with the existing voice connection responds and establishes a new RTP stream with the other DAP and then begins to relay the RTP information over the network to the new DAP. This DAP will continue to relay the information for the duration of the call. This operation is necessary to support seamless handover since the existing RTP stream cannot be released.


PABX

Signalling

RTP

Who has voice

connection?

(3) MulticastRTP stream is relayed to the DAP

User moves from one DAP to another

(1) Existing

(4)

(2)

1st 2nd


7. Installation


START

Customer Requirement

Ensure the DHCP server has option 66 (Next Server Address) configured as the TFTP Server address and option 67 (Boot File name) configured as “dapcfg.txt”

Site Survey

VoIP Readiness

PABX Programming

Can Dterm IP Handset

Register?

Does Customer have DHCP &

TFTP Servers?

Configure DHCP and TFTP server provided by DAP Configurator S/W

Use DAP Configurator to create dapcfg.txt file

Copy dapcfg.txt file and DAP F/W file in TFTP root

folder.

A

NO

NO

YES

YES



DAPs should now download configuration file and firmware

necessary.

A

Plug in DAPs. DAPs should boot and get IP Address and TFTP server

address from DHCP server.

Is LAMP on DAP lit solid?

Enter License Information and Subscribe Handset

Can IP DECT handset

subscribe?

Can IP DECT handset make

calls?

B

Confirm DHCP & TFTP server configuration

Troubleshoot DAP Configuration

Troubleshoot PBX Configuration

NO

NO

NO

YES

YES

YES


7.1 Customer Requirements / Site Survey

A DECT installation can only perform well when the DECT APs are installed on the correct locations and cover together the area without any gaps. Since this is crucial for meeting the required level of service, a site survey kit is available containing a DECT AP, tripod, calibrated handsets and batteries allowing for surveys even in new buildings.

The following points should be considered for customer requirements;

Number of handsets required Handset models and features Required PBX Features Required Coverage Licensing PBX / IP DECT Network infrastructure requirements for IP DECT

The following points should be considered as part of a site survey;

Environment

Document the general materials used in the construction of the site, which areas are indoor, outdoor, and anything that might affect the operation of the system.

DAP mounting positions

Determine exactly where DAP’s will be mounted, and any additional mounting requirements for the DAP at the time of installation.

Cabling

Determine where any pre-existing cable runs are, new cable runs required, and termination points for Ethernet cabling.


B

Use DAP Viewer Software to confirm handover.

Confirm coverage and Synchronisation structure.

Confirm the Customers satisfaction with operation and quality.

END


Confirm where the existing data equipment resides, port availability, and model numbers for later reference.

Determine if there is sufficient physical space and the positioning for the DAP manager server.

Determine if there is specific traffic issues requirements from user density perspective at the site (e.g. Canteen and places where lots of users may reside at the same time).

Complete a site survey report

This will be used to determine a bill of materials for the job, and to maintain a record of the site.

Site survey kits can be ordered from NEC Australia. Please contact the IP DECT product management team for further details.

For detailed information on how to complete a site survey refer to the IP DECT Site Survey Manual NEC-9976.

7.2 VoIP Readiness

Before installation it is important to ensure that the network infrastructure is capable of supporting Voice. The following items need to be considered:

QoS

IP Network should support QoS. This could be via various methods including Diffserv and 802.1p.

Network Equipment

Ensure there is an understanding of the networking equipment being used. Does the equipment support multicast traffic?

Multicast and Logical IP addressing

Understand how the customers IP addressing scheme has been designed. In order to ensure that handover between DAP’s will work, it is necessary to understand how the network has been segmented.

PoE

Confirm that Power over Ethernet is available directly from the LAN equipment; if not a mid-span PoE solution will be required.

DHCP Server – Prior to installation it is necessary to know if a DHCP server is already in use, or if the DHCP server in-built as part of the DAP Configurator is needed.

TFTP Server

If the customer already maintains a TFTP server then this may be used in preference to the DAP Configurator TFTP server.

Ethernet switches must be 100Mbps or better and capable of supporting VLAN’s.

If a Branch office configuration is used, sufficient Bandwidth between the Main office and Branch office is required.



Ensure that IGMP (Internet Group Management Protocol) snooping is disabled on any switch connecting DAP’s.

o IGMP Snooping is a feature in some Ethernet switches that allows the Switch to listen for IGMP Join messages coming from Multicast capable hosts to allow Multicast traffic to traverse these ports. DAP’s send IGMP join messages when starting up, however if the switch misses this message it will not allow Multicast traffic to that port and handover and DAP synchronization will not be possible.

7.3 PBX Programming for the SV8500

7.3.1 Service Conditions

- ACD and Hotel features are not supported for IP DECT handsets.- Not all DtermIP handset features are supported for IP DECT handsets.

7.3.2 SV8500 Features

Call Forwarding (All / Busy / Nans / Logout) Call Park

Call Pickup Groups / Direct Call Transfer / Consultation hold

3 Party Conference 8 / 16 / 32 Party Conference

Music on Hold Call Waiting

Executive Override / Right of Way Distinctive Ringing

Account Codes Authorisation Codes

Night Connection Station Station Hunting (UCD / Hunt Groups)

Message Waiting Indication Name Display

Terminal Logout Mute Key

Hotline System Speed Dial

Call Back – Note Call Waiting Originating - Note

Note: - Supported DAP Configurator soft key feature.



7.3.3 Programming

Setting up the SV8500 for your IP DECT system is basically the same as setting up the SV8500 for an IP Dterm. Be aware of the fact that the procedure does not tell in detail which commands should be used. Consult the SV7000/SV8500 manuals for the appropriate commands and command interfaces.

Make sure that you have the sufficient licences for "IP Dterm" extensions. Each DECT telephone extension is regarded as one IP Dterm extension. If you do not have sufficient licenses, you can subscribe a handset, but you do not get dial tone when going off-hook.

7.3.4 Step-by-Step Procedure

The following procedure guides you through setting up the SV7000/SV8500 for Business Mobility IP DECT.

PROCEDURE: “Setting up the SV7000/SV8500” Actions

1. Make sure that the system is configured for "ALaw" coding. If not, the speech path cannot be established.

2. Make sure that System Data Type 1, index 384, bit “0” is set to “0” (use command: ASYD). If not set correct, calls from the handset will work fine, however, calls to the handset will fail.

3. Make sure that the system is configured for "Login/Logout" for IP Dterms. This allows the DECT handsets to login automatically in the SV7000/SV8500. (Do not use the option of using "Fixed MAC addresses")

Note: The SV8500 uses encryption for lP DTerm login passwords. Make sure that “Proprietary” password encryption (option in SV7000/SV8500) is enabled in the SV7000/SV8500! To enable, change Option 848 to “80” (bit 7 must be a “1”) However, DAP Controller Release 3.2 and higher supports automatic password encryption detection, and therefore accepts both MD5 and Proprietary password encryption.

4. Make sure that the SV7000/SV8500 has a correct IP configuration (IP address, subnet mask and default gateway) for your network.

5. Make sure that the SV7000/SV8500 has the default RAS (Registration Admission Status) UDP port. The default port number is 3456.

6. Make sure that your number plan in the SV7000/SV8500 is correct for the station numbers that you are going to assign. Use command ANPD to enter the number plan data and command ASPA to assign the first digit of the station numbers.

7. Assign the extension numbers (station numbers) of the DECT handsets to the SV7000/SV8500, in the same way as assigning station numbers for IP Dterms. Use commands: ASDT and AISTL.



8. Assign the own Station number as "My Line" to "Key number 16" of the Stations. Use command: AKYD.

9. Assign "Logout" to "Key number 15" of the Stations. Use command: AKYD.

10. Note, this step is only required in case you want to implement Location diversity. Assign Key number 14 as “Visitor Key". Use command: AKYD.

11. The following VoIP parameters must be set correctly in the (SV7000) Location Group that you use for Business Mobility IP DECT:

- CODEC Priority: First priority = G.711 aLaw Second priority = G.729

- Payload: 40 msec.

Note: The advised payload is 40 msec. Other payload settings are possible; however, make sure that the payload is always equal for G.729 and G.711!

Use the following commands to setup the Location Group(s): AIVCL, AMGIL, and ALOCL.

12. Now your system is setup for Business Mobility IP DECT handsets. When you subscribe a handset it is automatically logged in (registered) in the SV7000/SV8500.

Note: If only G.729 is set in the AIVCL list then the SV8500/SV7000 will force calls to use G.729. Each call that runs using G.729 will consume a G.729 license from the DAP Manager G.729 license pool. If there are no licenses available (or the DAP Manager is not turned on) then the call will fail.

7.3.5 Call Forward Logout

An IP DECT terminal can be logged out of the system a number of ways:

If the handset fails 4 polling intervals (I E. has gone out of range).

If the handset is out of range when someone rings it (using the Action on Incoming call feature of the DAP Configurator).

If the handset is turned off and key 15 is programmed as a logout key.

Once in logout state the system can be set to forward calls to another station using the following command:

ACFS – Assignment of Call Forward Data

TN: Tenant of IP DECT handset

STN: Station number of IP DECT Handset

SRV: L: Station number where the call is to be forwarded.



7.3.6 Number Sharing Example

It is often a requirement that a user have the same extension number for their desk phone and their IP DECT handset. The best way to do this is to make the prime line of the Dterm the same as the physical number (AISTL number) that’s associated with the IP DECT terminal. So whilst both terminals have different physical numbers, when the user goes off hook on either handset they appear to have the same number. In addition it might also be necessary to have the same SMDR, MCI, and message wait indication, for both terminals.

Note: This will mean that the Login for the DtermIP will be the real number (assigned in AISTL) of the phone. This will be different than the prime line number of the phone.

Example:In the following example the IP DECT extension number is 1000 and the DtermIP handset will be programmed in the system to share this number.

Note: It is important that the main number of the IP DECT terminal is the known indial number for the user, because the handsets Low Rate Messaging Service (LRMS) uses this number for text messaging to the handset. The LRMS is controlled by the DAP manager which means that the number used for messaging will be the same as is subscribed in the DAP manager.

AISTL – Assignment of IP Station Data:

Assign 1000 (IP DECT):

IP STN: 1000, KIND: DtermIP, TEC: 12

Assign 2000 (DtermIP):

IP STN: 2000, KIND: DtermIP, TEC: 12

Note: The number used for subscription in the DAP manager for the IP DECT handset will be 1000 in this case.


Off Hook uses 1000 on both stations

Desk Phone Dterm Extn 2000 DECT handset

Extn 1000


AKYD – Assignment of Key Data:

IP DECT: 1000:

PRI: 0, PL TN: 1, PL STN: 1000, S: 0, MWD: 0, LN PRE: 0

KYN: 15, KYI: 1, FKY: 142

KYN: 16, KYI: 2, KD: 0, TN: 1, STN: 1000, RG 7

DtermIP: 2000:

PRI: 0, PL TN: 1, PL STN: 1000, S: 0, MWD: 0, LN PRE: 0 TP: 1



Note: In the above example the real (AISTL) number of the DtermIP has been programmed outside of the key range of a 16 button terminal. This is because the real number is not going to be used to dial the DtermIP; the user will instead be reached on the prime line number which will be the same as the IP DECT (1000) terminal.

ALGSL/N – Assignment of Telephone Station Data:

This command must be assigned in order to use the ALGSL/N command.

Assign logical numbers for both phones.

ANSDL/N – Assignment of Number Sharing Data:

This command will link the SMDR data of the IP DECT and DtermIP to be the same.

M_TELN = 1000, S_TELN = 2000, OD = 0, MW = 0, LM = 0

7.3.7 Digit to Soft key Translation.

When an IP DECT handset calls a station and receives busy tone, using the “Digit to Soft key” feature, it is able to invoke features using the first 4 digit keys on the handset. The features that are available are:

[C-1D] Call Back – Dterm.

[C-31] Call Waiting – Originating.

[E-1D] Executive Right-of-Way – Dterm.

Note: These features should only be assigned as necessary, and users need to understand the functionality (E.g. Only assign Executive Right-of-Way on handsets of users that require it, as this feature allows the user to listen to other users conversations).

Soft keys on a DtermIP are the four keys that are associated with the LCD display. The translation between these keys and digit 1, 2, 3, 4 on the IP DECT handset are made in the DAP Configurator as shown below:



ADSL – Assignment of Dterm Soft Key on LCD Data:

SKP: 1 – Pattern Number

SN 3 – Station Busy

FKY: 3 – Executive Over ride

FKY 4 – Call waiting (originating)

FKY: 5 – Call Back

Note: The default configuration of the system has the soft keys assigned as MIC, CB, CW, >>>. If left as the default only the CB and CW keys will have any effect with the IP DECT handset.

ADKS – Assignment of Dterm Key Status Data.

TN: 1

STN: 1000

SKP: 1

LKP: 1

PG: 0

For additional programming requirements for each of these features consult the Business Feature Programming Manual.


1:21 PM THU 27 June 2013

CB CW E-OVR >>>>


7.4 Installing the DAP Controller / Manager

Note 1: - Make sure that you have decided which DHCP Server you are going to use.

Note 2: - Make sure that you have decided which TFTP Server you are going to use.

Note 3: - Make sure that the network components (Switches / Routers) are correctly configured for VoIP and IP Multicast. Ensure that the network supports IP Multicast between all network components that are used for Business Mobility IP DECT.

Actions1. Make sure that you are logged onto the computer with Administrator Rights.



2. Un-zip the DAP Installer package.

3. Double click setup.exe or setup.

4. Depending on the version of your Windows Operating System, you will see a security screen form Windows saying “Do you want to allow the following program to make changes to your computer?” Click “Yes”

5. You will see the following window:

It indicates that the DAP Controller Software support your version of Windows. Click “Next” to continue.



6. Now the installation of the “Prerequisites” starts.

Note: - This can take several minutes.

When all required prerequisites are installed, you will see the following window.

In case of Windows XP or Windows 2003, the system may ask for the Windows Operating System CD/DVD-ROM.

Click “Next”



7. The following screen is displayed. It indicates that the system is ready to start the installation of the DAP Controller.

Click “Next”



8. In the window that is displayed, please select the system type that you prefer. “Multiple System” or “Single System”

Select Single System if you only want to manage one IP DECT system.

Select Multiple System if you want to manage more than one IP DECT system.

Click “Next”

Note 1: - If you select “Single System” the DHCP and TFTP Servers are not installed by default. However, if you do want to install these servers, select the option “Custom” in step 9 and select DHCP and TFTP Servers to install.

Note 2: - If you select “Multiple System”, the services that are installed for IP DECT are installed with start-up parameters of “Manual”. Only “Single System” is the services installed with the start-up parameter of “Automatic”.

Note 3: - You can always change the setting from Single to Multiple systems and vice versa later on. See Section 9.2 Single / Multi Site.



9. The following window is displayed.

The window “InstallShield Wizard” you should specify the “Setup Type”. Select Standard and click “Next”.

Note: - If you require to fine tune the installation, you should select “Custom” and click “Next”



10. The system has collected sufficient information to start the installation.

Click “Install”



11. When installation is finished, you will see the following window.

When the checkbox “Launch DAP Configurator” is checked, the DAP Configurator will start after clicking “Finish”.



7.5 DAP Configurator

The DAP Configurator application is used to generate the configuration file that is loaded into the DAPs as well as starting and stopping the following services:

DECT Data Service (DDS) –

Main DAP Controller Service which communicates with the DAP’s and handles handset subscription etc.

Performance Counter Retrieval (PCR) Service –

This service allows for Equipment Performance and User Performance data to be collected from the system and at regular intervals and inform a Network Administrator of potential problems via email.

DHCP Service –

Can be used to run the DAP Configurator as the DHCP Server in small installations where the customer might not have a DHCP Server on the network.

TFTP Service –

Can be used to run the DAP Configurator as the TFTP Server in small installations where the customer might not have a TFTP Server on the network.

DAP Manager –

This is a web page (http://localhost/cds ) on the DAP Controller PC that is used for general Maintenance of the DECT System such as Subscribing and Deleting handsets, Entering Licensing information, rebooting DAP’s etc. When this is turned on in the DAP Configurator it simply loads the DAP manager in a web browser. Note, this setting in the Configurator, it does not control the actual web server; it is just a means of loading the browser to the CDS web page on the local machine.

DiagMonitor Service –

The Diagnostic file captured for analysis by NEC Engineering.

The following sections will detail some of the configuration parameters setup in the DAP Configurator to setup the DECT System in one of three possible configurations. Depending on the required configuration and whether the customer already has a DHCP / TFTP Server, some of these parameters may not be required.

The IP DECT System requires a DHCP / TFTP Server as well as a Server running the DAP Controller software.


http://localhost/cds


8. Setting up the DAP Configurator

The DAP Configurator is a tool for creating the configurations files for the DAP Manager and DAPs. It is automatically installed when you install the DAP Controller/Manager. It is also automatically started up during the installation of the DAP Controller/Manager. After you went through the DAP Configurator windows and you have entered the correct data, a number of configuration files are created.

You can always start-up the DAP Configurator tool using the shortcut to the DAP Configurator tool in the “Start”, “All Programs”, “DAP Controller”, “DAP Application”, DAP Configurator” menu.

8.1 Using the DAP Configurator

PROCEDURE: “Setting up the Configuration” Actions

1. Make sure that the installation of the DAP Manager was successfully executed. If you selected to start the DAP Configurator automatically after the installation, continue with step 3 in this procedure. If not, continue with the next step in this procedure.

2. Start the DAP Configurator tool, via Start, All programs, DAP Controller, DAP Applications, DAP Configurator.



3. If there is a problem with your network card (e.g. no cable connection), you will get a message. Please solve the problem. If you do not see this message, continue with the next step in this procedure.

4. If you start-up the DAP Configurator for the first time, the system asks you for the license file.



5. Select the license file and click open. If you do not have a license file, the system allows only up to 4 AP400S DAPs. However, the SV8700 / SV8500 do not support the AP400S, so, in case of the SV7000 / SV8500, you will always need a license.

6. You will see the following window displayed.

Note that there are three sections in this window:

- System Control section at the left side.

- Settings Buttons at the top part of the window.

- Data information part in the middle of the window.

If you start-up the DAP Configurator after configuring a system, you will see one or more extra buttons highlighted.

The way the buttons are greyed out, may be different in your system.

1. In the System Control section (left side) click the button that is applicable to your need. For a new installation it will be New System.

Note 1: If you don’t want to start a new system installation, consult Section 8.1 “System Control Section” for more information on the buttons.

Note 2: If you want to change system settings, you must use the buttons in the top part of the window. These buttons are described in Section 9.1 “Settings Buttons”.

Continue with the section that is applicable for your situation.


Setting Buttons

System Control

Data Area


8.2 System Control Section

8.2.1 General

The System Control section is located at the left side of the IP DECT Configurator window.

Using one PC, you can manage more than one IP DECT system. For such an IP DECT system you must setup a configuration on your PC. For each individual system, you can change settings, using the buttons in the top part of the window. However, you can have only one IP DECT system configuration active at the time. Therefore, you can start or stop an IP DECT system.

Note: When you “Stop” an IP DECT system, the DAPs remain up-and-running. This means that you can still make and receive phone calls. However, the DAP Controller/Manager function is stopped, which means that some functionality (e.g. messaging or moving between Branch Offices) does not work anymore.

The System Control part consists of the following buttons:

Home Returns you back to the “start” screen.

New System Allows you to create a new system configuration.

Modify System Allows you to Select a system configuration, and then manipulate or modify the system.

Import System Allows you to import a system configuration that has previously been exported. You can import individual files from the exported .zip file or you can import the exported .zip file in one go.

Activate - Deactivate - System Status The system status button leads you to a window in which you can control the system status. See Section 8.2.2 “System Status Window”.

Export System Allows you to export a system configuration. The exported file is always a .zip file and contains all relevant system configuration files, including subscription data, DAP configuration, DHCP data etc. The generated file can be imported later or can be imported on another PC that you want to use as DAP Controller/Manager PC.

Note that this file can be used as a backup of your entire system configuration. Note that you must select a System (configuration) first, using the “Modify System” button.

Delete System This removes the System (configuration) from your PC. Please note that all your subscription data is removed with it. So, make sure that you have a backup of your system, before you execute delete system



Upgrade Installation This allows you to upgrade the installation in a convenient way. You are guided through the Upgrade procedure.

Save System This saves the changes that you have made on a System (configuration) to files on your PC. Note that after you saved the System (configuration), you can go to the System Status button and then make the system active.

Default Return to default settings.

Only comes up when you’ve used the “settings button”.



8.2.2 System Status Window

When you click the “System Status” button, the following windows is displayed:

Note: - When you have more than one IP DECT system (configuration) you must select the System you want first. When using the “Modify System” button ensure that you have saved your new configuration before starting it.

DAP Controller SV7000/SV8500

Note 1: Make sure that you have stopped a previously running system.

Note 2: If you have made a new configuration, or if you have changed the configuration settings, make sure that you have saved the configuration first, using the “Save System” button.

Note 3: Starting or stopping the system, only starts or stops the services and applications running on the DAP Manager PC. This means that the DAPs remain operational. Basic call handling is still possible if the DAPs are up and running.

The following services can be started or stopped:

DDS DDS (DECT Data Server) takes care of all DECT processes to and from the DAPs.

PCR PCR (Performance Counter Retrieval) must be running to retrieve performance data files and to enable sending an e-mail when performance thresholds are exceeded or when a DAP goes down.



FWU Firmware Upload must be running if you want to use Firmware Upload.

TFTP The TFTP Service refers to the TFTP server that was automatically installed with the DAP Controller/Manager software. Note that this is not the MS Windows TFTP server. A TFTP Server must be running when one or more DAPs start-up. The TFTP server supplies the DAPcfg.txt configuration file to the DAP(s). Note that there can be only one TFTP server running on your PC. If you start the TFTP service make sure that there is no other TFTP server running on your PC.

DAP Manager (SV7000/SV8500 systems)Starts up the WEB service for IP DECT in IIS and opens the WEB Page of the DAP Manager in Internet Explorer.

DHCP The DHCP server runs as an application. It can be started or stopped. Make sure that you are allowed to use a DHCP server on the Network.

DiagMonitor (SV8300 systems)The DiagMonitor is used to collect diagnostics data.

In addition to the services and applications on the PC, you can also reboot the DAPs.

When you start a System, the IP DECT Configurator may ask you if you want to reboot the DAPs as well. Note that this can be necessary, because the configuration changes must be uploaded to the DAPs as well. This requires a reboot!



8.3 Single Site / Multi Site

If you use the DAP Manager PC to manage one IP DECT system only, you can create a single site system. If you want to use your DAP Manager PC to manage more than one IP DECT system you can setup the DAP Configurator to manage more than one site, “multi-site”. You have made a selection during the installation.

However, if you want to change the single site or multi-site setting, execute the following procedure:

PROCEDURE: “Switching between Single Site and Multi Site”

Actions 1. Make sure that the IP DECT Configurator is open. If not open the IP DECT

Configurator/DAP Configurator. See Section 9.0 Using the DAP Configurator.

2. Using the DAP Configurator Left mouse click the top left IP DECT Configurator icon. See icon below.

3. In the window that is opened, click "More". You should see the window below;



4. You can switch to “Multiple system Support” or “Single System” by means of the check box in the window. Click Apply or OK to activate your selection.

9 DAP CONFIGURATOR SETTINGS

9.1 Settings Buttons

In the top part of the IP DECT Configurator window, you see a number of buttons that allows you to change settings in the system. In the following subsections these settings are explained.



9.2 General Settings

When you click the “General Settings”, the following window is displayed:


The following items must be entered:

System Name Can be given any name. Note that this name will be used for a directory on the hard disk. This means that the name must comply with the requirements for Windows directory names.

PBX Type (SV7000/SV8500/SV8300 systems)Select the platform to which the IP DECT system is (going to be) connected. In this case it will be “SV8500/SV7000”

AP200/300 Package Here you must enter the firmware file specification for the firmware package for the AP200 and AP300. For SIP, the file name should look like this: 4910dxyz.dwl (e.g. 4910d611.dwl).



AP400 Package Here you must enter the firmware file specification for the firmware package for the AP400. For SIP, the file name should look like this: 4920dxyz.dwl (e.g. 4920d611.dwl).

AP400 Loader Here you must enter the Loader file specification for the firmware package for the AP400. For SIP, the file name should look like this: 49920201.dwl.

When finished, click “Apply” and continue with clicking button “IP Settings”.

9.3 IP Settings

9.3.1 The Window

When you click the “IP Settings” button, the following window is displayed:




9.3.2 IP Settings, tab “DAPs IP Configuration”

Please click the tab: DAPs IP configuration. Now the following fields can be edited:

DAPs Multicast IP address Specify a Multicast IP address. If the network for your IP DECT system is used for other purposes than IP DECT as well or if the network has a connection to the company network or external network(s), you must ask the local IT manager for a multicast address. If your IP DECT system is in a closed network, you can click the button “Default IP” to use the default IP multicast address.

Port range from By default the port range on the DAPs will start at port 3000. Please note that you cannot change port range.

9.3.3 IP Settings, tab “DAP Controller IP Configuration”

Please click the tab: DAPs Controller IP configuration.

Note 1: Depending on the Licenses that you have, the screen may vary.

If you have a multiple DAP Controller system (IE: - Redundancy), see section 12, DAP Redundancy.



Step 1



Step 2



Step 3

Note: You fill in the data of all DAP Controllers in the DAP Configurator of the Primary DAP Controller.

DAP Controller IP Address DAP Controller / Manager PC IP address. You can easily click the button “This PC IP” to copy the IP address of your PC into this field.

Port range from Start of port range in use for IP DECT on the DAP Controller/Manager PC.

Note: - This port range is automatically filled in. Please do not change manually.

Enter the IP Addresses of the DAP Controllers that are in your system.

Note: When you enter more DAP Controllers than your License allows, you will get the message “License Violation”.



9.3.4 IP Settings, tab “PBX IP Configuration”

Please click the tab: PBX IP configuration. Now the following fields can be edited:

Single Gate Keeper Click this radio button to select a system type with only one gatekeeper.

MP (DRS) IP address

Enter the Local Processor (LP) IP address of the SV7000/SV8500.

DRS port number Enter DRS (D-term Registration) port on the LP in the SV7000/SV8500. The default port is 3456.

Multiple gatekeepers. When you click this radio button, you are able to enter more than one DRS address. This can be useful for redundancy reasons, when having a dual SV7000/SV8500. You can add as many addresses as you want. If you have only one SV7000/ SV8500, you should not click this Radio Button.



Multiple Gatekeeper settings. When you select “Multiple Gatekeepers”, the table in which you can add gatekeepers is activated. Right mouse click inside the table and select “new” to add a gatekeeper. The following items needs to be entered.

Index This is a unique identifier per SV7000/SV8500. This is used to specify priorities in Gatekeepers

IP Address Enter the IP address of the next SV7000/SV8500. Note that the first DRS are already in the list.

Port Enter the port number for the SV7000/SV8500.

DNR Prefix Not applicable for the SV7000/SV8500.

Domain Not applicable for the SV7000/SV8500.

PBX Not applicable for the SV7000/SV8500.



9.3.5 CDA IP Configuration

Please click the tab: CDA IP Configuration. The following window is displayed:


Corporate directory IP Address The IP address of the Central / Corporate Directory Server (if applicable)

Corporate Directory port number The Port number of the Central Directory server. Default port number is 30160.

When you use the Central / Corporate Directory Access application, you must enter the IP address of the server where the Central / Corporate Directory Access software is running.

If you do not have the Central / Corporate Directory Access software, these fields can be left blank.

Click Apply



9.4 Network Settings

9.4.1 Network Settings, tab “Network Card Settings”

Please click the tab: Network card settings. The following window is displayed;


Now the following fields can be edited:

Select network card connected to the IP DECT system. If you have more than one network card in your system, select the network card that you want to use here.

The network card data is displayed. Please note that you cannot change the network card data here!

Change IP address, subnet mask and default gateway of this PC in the following values on system activation.

If this box is checked, the IP address, subnet mask and default gatekeeper of your network card is automatically changed to the DAP Controller IP address that you have specified in Sub-section 9.3 “IP Settings”. This can be useful when you manage more than one IP DECT system with your computer. The moment that you start up one of your DECT system configurations, the IP settings of your network card are automatically changed to the right settings for that particular system. Please note that the IP settings on the network card are automatically changed, but are not changed back to the previous settings.



9.4.2 Network Settings, tab “DHCP Settings”

Please click the tab: DHCP Settings. The following window is displayed:


Run DHCP Server on this PC If you check this box, the DHCP Server that is installed on your PC for IP DECT will be activated. Note that this DHCP Server accepts DHCP requests from DAPs only if you check the checkbox “DAP IP range exclusive for DAPs only”. In that case it will ignore other DHCP requests. When you use the DHCP Server it will issue addresses in the range that you specify in the “DAP IP Range”.

When enabled, it runs as an Application under MS Windows. The settings are stored in the file dhcpsrv.ini in the system directory.

DAP IP Range Specify IP address range that will be issued to the DAPs.

DAP IP Address range exclusive for DAPs only. If checked, the DHCP server will respond to DAP requests only. This is based on the “Vendor Class ID” that the DAPs issue when they do a DHCP request.

Subnet Mask. Self-explanatory



Default Gateway Self-explanatory

Ask for confirmation before starting the DHCP server When this box is checked, you’ll be asked for confirmation to start the DHCP Server.

Monitor DHCP Server This allows you to monitor the DHCP activity of the built-in DHCP server. You see the results in the System Status Window, which is opened when you click the button “Activate / Deactivate / System Status”.

Note 1: - The built-in DHCP issues an “unlimited” lease time.



9.4.3 Network Settings, tab “TFTP Settings”

Please click the tab: TFTP Settings. The following window is displayed:


Run TFTP Server on this PC If this box is checked, a TFTP Server will be running on your PC as “Service”. The settings for the TFTP Server are automatically set correct for your configuration. Note that a TFTP Server is needed when a DAP starts up, unless the configuration file is stored in the DAP.

TFTP Server Select the TFTP Server that you want to use for the IP DECT Configuration. If you select the “3Com Tftp Server on this PC” it enables the TFTP server that is part of the DAP Controller/Manager software package. When enabled, it runs as “Service” under MS Windows. The settings are stored in the file 3CTftpSvc.ini

TFTP Folder Automatically filled in. The TFTP folder is the folder where all system information is stored. Default folder is: C:\Documents and Settings\All Users\Application data\Nec\DAP Controller\<system name>. When you are using Windows 7 or Windows 2008, the directory is C:\ProgramData\Nec\DAP Controller\<system name>



TFTP Server IP Address. This is the IP address of the machine where the TFTP server is running. When you have chosen to use the built-in TFTP server, you cannot change this IP address because it is the IP address of your machine.

Monitor TFTP Server This allows you to monitor the TFTP activity of the built-in TFTP server. You see the results in the System Status Window, which is opened when you click the button “Activate / Deactivate / System Status”.



9.4.4 Network Settings, tab “Leased IP Addresses”

Please click the tab: Leased IP Addresses. Now you see a list of Leased IP addresses in the Built-in DHCP Server.

In this window, you can delete/change/add the relationship between MAC addresses and leased IP addresses. You have access to these settings by means of right mouse clicking a line in the Leased IP Addresses window.



9.4.5 Network Settings, tab “QoS Settings”

Please click the tab: QoS Settings. Now the following fields can be edited:

QoS on Layer 2 When you check this checkbox, the IEEE802.1p/q field in the layer 2 data package will be used. If enabled, you must specify the Priority level for Layer 2 (IEEE802.1p) and the VLAN ID (IEEE802.1Q).

User Priority The Priority value is a three bit value which must be entered as decimal value 0 ... 7, where 7 is the highest priority.

VLAN ID Here you can specify a VLAN ID. Note that “0” means no VLAN specified.

QoS on Layer 3 Here you can enable Quality of Service on Layer 3.



DSCP If you have enabled QoS on layer 3, you must specify the DiffServCode Point (DSCP) value in decimal, in the range 0 ... 63. Note that this is not the AF (Assured Forwarding) class selector/service level or EF (Expedited Forwarding) class selector/service level. This means that if you want to apply the “EF” class selector/service level (53), you should enter the DSCP decimal value “46” (binary 101110).

9.4.6 Network Settings, tab “Boot options”

Please click the tab: Boot Options. Now the following fields can be edited:

DAP Boot options. This allows you to store the IP address data and Configuration data into Flash memory in the DAP. When stored, a DAP does not need a DHCP/TFTP server anymore. Note that you can “Store” or “Erase” data.

Note: Data is stored when you have selected to store data AND when the DHCP server issues an “Infinite” lease time.

When finished, click “Apply” and continue with clicking button “System Configuration”.



9.5 System Configuration

When you click the “System Configuration” button, the following window is displayed:

You can select the type of system that you want to use. Please consult Section 2 “CONFIGURATIONS” for more information. Once you have decided which network configuration you need, continue with the information in this chapter and setup the configuration as needed.

When you click the pull down icon, you will see the following options displayed.

9.5.1 Simple Configuration

A simple configuration consists of one network segment. All IP DECT components are in that segment, including the PBX.



9.5.2 Multiple Subnets

This configuration allows you to have the IP DECT system over various subnets. A number of configurations are possible. You will need this configuration window to setup:

A Head Quarter with Branch Office.

A Routed Head Quarter with Branch Office.

A Routed Head Quarter with a Routed Branch Office.

Consult Section 2 “CONFIGURATIONS” for more information.

The window “Multiple Subnets” offers the possibility to specify a certain RPN (Radio Part Number) range per Branch Office Subnet. Note that you should set the RPN range wide enough to allow future system expansion.

You will see the following screen:

In this window you can right mouse click a line in the shown table. Then you can add, edit or delete a Branch Office configuration. The following items must be specified:

Subnet In almost all configurations, this is the subnet address. It is the first address in the subnet range, e.g. 192.168.1.0/24.



However, note that this subnet can also be an Aggregated Subnet. An “Aggregated Subnet” is a Virtual network definition which determines the network boundaries for an IP DECT Network in which seamless handover is possible AND which is running over more than one IP subnet, An Aggregated Subnet is a kind of “virtual” subnet that combines several real subnets This is used when your IP DECT system is operational on one location on more than one subnet, with seamless handover. All DAPs within the Aggregated Subnet allow seamless handover between each other, although they are spread over different real subnets with Routers in between.

So, if you have IP DECT running on more than one IP subnet, where seamless handover is required, you must calculate the Aggregated subnet and fill it in, in this window

Example of an Aggregated Subnet:

There are two subnets in which IP DECT is installed. The Router supports IP Multicast and there is seamless handover between the DAPs in different IP subnets. One subnet is 192.168.1.0/24 and the other is 192.168.40.0/24. The aggregated subnet is 192.168.0.0/21. This covers both subnets.

All subnet addresses outside the Aggregated subnet, will be regarded as Branch Offices.

Note: The Aggregated Subnet, together with the Aggregated Subnet Mask is only applicable for IP DECT. So, never use Aggregated Subnet mask on your Network card or other network devices.

NetMask Length This is the subnet mask length, the number of bits used to identify the network part. In general, this will be a real Netmask length, applicable for one network segment.

Example: When your subnet mask is 255.255.255.0, it means 24 bits for the network part and 8 bits to identify the host part. So, in this example you must fill in 24.

Note: The NetMask Length can be the Aggregated subnet mask length. See the bullet above (Subnet) where the Aggregated subnet is explained.

RPN range Lowest RPN and highest RPN in this Branch Office.

Note: Make sure that you enter all subnet. DAP in subnets, not included in this list will fail to complete the boot process.

Time to Live value

The Time to Live value is used for the Multicast traffic. If the Time to Live for the Multicast is set to “1”, Router(s) will not forward multicast traffic for the associated Multicast Group. If the Time to Live is higher than “1”, Router(s) will forward multicast traffic for the associated Multicast Group (depending on settings in a Router). If you are using an



Aggregated subnet (see bullet “Subnet” above), multicast routing is required between the different Subnets and therefore the TTL must be set to a value higher than 1 (advised 32).

If the subnet that you have filled in is a real subnet, not Aggregated, you must make sure that the Time to Live is always 1.

Gate Keeper This is the Proxy address for the DAPs in this Subnet.

Subnet name Can be given any name. It is used to identify the Branch Office.

Time Offset The Time Offset is for use when the Branch Office is in a different Time Zone compared to the main Office. IE: Melbourne and Perth.

9.5.3 Routed Head Quarter

In this configuration, there are more than one network segments in the Head Quarter. The routers in this configuration must forward IP Multicast packages.



The following settings can be entered / changed:

Time to Live value The Time to Live value is used for the Multicast traffic. If the Time to Live for the Multicast is set to “1”, multicast traffic will not be forwarded by a Router. If the Time to Live is higher than “1”, multicast packages might be forwarded by the Router, depending on settings in the Router. Because you have selected the Router Head Quarter configuration, the Time to Live will always be higher than one. Advised value is 32.

Aggregated Subnet mask The “Aggregated subnet mask” is the subnet mask for the DAPs to determine the network boundaries for an IP DECT Network in which seamless handover are possible. It should cover the network segments that are connected together using routers that support IP Multicast. If there are DAPs outside this Aggregated Subnet Mask, the DAP(s) is/are regarded as in a Branch Office. If the IP addresses are in the same Aggregated Subnet, according to this mask, the system assumes that they are in the same subnet. The term “Aggregated” means that the subnet consists of smaller subnets which are connected over a router, but according to the subnet mask, all behaving as one subnet. This is applicable for the “Routed Head Quarter” network solution either with or without Branch Offices; see Section 2.4 Routed Head Quarter and Section 2.5 “Routed Head Quarter with Branch Offices”.



9.6 DECT Settings

9.6.1 DECT Settings, tab “DECT Settings”

Please click the tab: DECT Settings. The following window is displayed:


Now the following fields can be edited:

Country Code The Country code specifies the tone plan for IP DECT and also selects the correct frequency range and transmitter output power.

PARI Primary Access Rights Identifier. This is the Unique DECT System Identifier. It is an 8 digit hexadecimal string. It is a worldwide Unique Identifier which you should have received together with your DECT system.

SARI



The SARI is the Secondary Access Rights Identifier, which is only needed if you use Multi-Site subscriptions. If you do not use multi-site Subscriptions, leave this field to the default “FFFFFFFF”.



Frequency Table This shows which DECT frequency range is used. This differs per part of the world.

Note that you cannot change the setting here, it is a result of the country that you have selected.

Used carriers By means of this field you can enable/disable the DECT carriers. Leave all carriers enabled to make sure maximum bandwidth is available.

9.6.2 DECT Settings, tab “Handset Settings”

Please click the tab: Handset Settings. Now the following fields can be edited:

Handset Page Timer The Page Timer specifies the time in seconds between two page requests (retries).

Page timer retry value The Page Retry Value specifies the maximum number of paging retries that are issued, if paging a handset fails.



Display handset name in DAP Manager INT When enabled, the handset name (if present in the handset) will be displayed in the DAP Manager, in the Subscriptions window, in the Comment field. The handset name will be displayed between brackets.

Handset Polling time interval This is a mechanism to check if the handset is still reachable. Here you specify the polling interval time. If the handset is does not respond, it will be switched absent in the IP DECT system.

9.6.3 DECT Settings, tab “DAP Settings”

Please click the tab: DAP Settings. Now the following fields can be edited:

Broadcast Messaging This enables broadcast messaging.



Local Message relay override When “Local Message Override” is not checked, and the TCP/IP DECT Messaging port (default 28001) is in state “Connected” (from e.g. a Messaging device) it is not possible to do handset-to-handset messaging anymore without intervention of an external messaging system. However, if you check the “Local Message override” check box, handset-to-handset messaging remains possible even if the TCP/IP port is in the state “connected”. This setting can be required for the messaging functionality of “Business Connect” however; it should not be checked in case of the Messenger@Net.

SMS Presence Send the absent/present status to dedicated applications via DMLS.

Move subscriptions non-operational DAP after When a DAP is down and the DAP Controller is up- and-running the subscription records from that DAP will be moved to other DAPs. The time interval can be specified here.

Absent DAP Threshold When the number of absent DAPs is more than 2, the subscription data will NOT be moved to other DAPs. Please note that this is a fixed system parameter, and cannot be changed.

G729 mode: The following items can be selected:

o G.729 not supported = never use G.729

o Use G729 when required = Setting as in previous versions of IP DECT. G.729 used in case of connection to Branch Office DAPs.

o Preferred use of G.729 = IP DECT will always issue G.729 as preferred codec over G.711.

o Only use G.729 = Do not use this setting!

Note: G.729 voice compression (G7A unit installed in AP300/AP400) could be the answer for applying DECT in networks with limited bandwidth. The downside however is that the voice quality will be less compared to uncompressed voice. But under more demanding circumstances like environments with background noise, the voice quality may become unacceptable if used in combination with G.729. Therefore we advise not to apply G.729 on sites with a background noise.

When finished, click “Apply” and continue with clicking button “PBX Settings”.



9.6.4 DECT Settings, tab “Synchronization Settings”

When you see a tab called “Synchronization Settings”, it indicates that you have a license for IP DECT in an environment with a lot of metal causing reflections. The license offers additional functionality to reduce the effects of the reflections. However, it is only available on “Project Base” which means that it has to be installed by special maintenance engineers. Therefore the Synchronization Settings window is not explained here:

9.7 PBX Settings

9.7.1 PBX Settings, tab “Handset Sharing”

When you click the "Handset Sharing" tab, the following window is displayed:

Handset sharing Checking this box, enables Portable/handset sharing.

Subscription prefix First digit(s) of the subscribed number. If the first digit(s) of a subscription matches with the digit(s) defined here, the handset is enabled for portable sharing.



Closing digit Digit that must be entered on the handset after entering the extension number at login. Default is "#". Normally there is no need to change this digit.

9.7.2 PBX Settings, tab “Three Party Conference Settings”

When you click the "Three party conference Settings" tab, the following windows is displayed:


Initiation digit Digit that must be dialled to start the three party conferences. The default setting is: *.



9.7.3 PBX Settings, tab “NEC PBX Settings”

When you click the "NEC PBX Settings" tab, the following window is displayed:

The following items can be set or changed (the greyed out option is not applicable for SV7000/SV8500):

Handset rejects an incoming call: Select the preferred action in case the handset rejects an incoming call.

Call to not reachable handset: Select the preferred action in case the handset is not reachable.

Multiline mode In the multiline mode, you can select:

o “No multiline support” No multi line support.

o “Multiline enabled Call Pickup mode e.g. for MRG” Multiline mode for MRGs up to three members.



o “Multiline with line pre-selection” When there is a call, the CLI of the calling party is displayed and the call can be picked up by means of the off-hook key. IP DECT responds to the SV7000/SV8500 as if the call was picked up by means of the line key on which the call was coming in. When the call is answered (with the off-hook key) after a few seconds, IP DECT picks up the call with the my line key (16) to the SV7000/SV8500. This setting is the DEFAULT for SV7000/SV8500.

o “Multiline enabled with delayed setup and release for MRG” This should be used for MRG with more than 3 members.

o “Multi line with pre-selection only “The call can only be picked up by means of the off-hook key. IP DECT responds with line key 2, to the SV7000/SV8500/SV8300. This setting can be used for a twinning configuration in the SV7000/SV8500.

Ring Pattern This is greyed out, so, not applicable for SV7000/SV8500.

Incoming call without CLI When there is an incoming call without CLI, the information entered in this field will be displayed on the handset.

MWI mode: The setting that you select here, should match with the setting in the SV7000/SV8500.

Digit to Soft key translation This simulates the function of the soft keys on an IP DTerm when having busy tone.

Swap g711aLaw/uLaw codec values for H.245. This is only applicable for the SV7000/SV8500/SV8300 in combination with IP D-Terms from the years 2003 and 2004.In those versions, the aLaw and uLaw notations were swapped. So, when aLaw was requested, uLaw was actually performed. If you do not get speech between IP DECT and IP D-Terms from the years 2003 and 2004, you should check this box, in order to swap the aLaw and uLaw codec values.

Display own number when going off-hook. Self-explanatory

When finished, click “Apply” and continue with clicking button “Performance / Email Settings”.



9.8 “Performance / E-mail Settings”

9.8.1 Performance / E-mail Settings, tab “PCR Settings”

When you click the “PCR Settings” (Performance Call Recording) tab, the following windows is displayed:


The following parameters are available:

Interval UPM generation every: With this interval, User Performance Measurement files are generated. Default value is 1440 minutes (one day)

Interval EPM generation every: With this interval, Equipment Performance Measurement files are generated. Default value is 15 minutes.

Keep Performance data for . . . days The number of days that the performance data should be kept on the Hard Disk.



Start measurement at: Each day performance measurement should take place; the performance measurement will start at the time specified here.

Stop measurement at: Each day performance measurement should take place; the performance measurement will stop at the time specified here.

Create Performance counters every: Specify the days that performance counter retrieval should take place.

9.8.2 Performance / E-mail Settings, tab “Alarm Settings”

When you click the “Alarm Settings” tab, the following window is displayed:

E-mails can be send automatically when a DAP goes down or when the channel occupation threshold is exceeded for more than a number of seconds or when the DDS goes down. Note that this will only work when the PCR service is running on the DAP Controller/Manager PC.

Alarm Notification Alarm notification can be send as an e-mail and/or to the Windows Event Log. Please note that it is possible to convert the events, written to the event log, into SNMP Traps.



E-mail addresses Enter the destination email address (es). Note that you can enter more than one email address. Separate the individual addresses with a; (semi colon).

Channel occupation Threshold If the channel occupation is higher than this percentage of the available channels for a specified time period, an email and or Event is generated. The threshold is specified in percentage, the time is specified in seconds.

Channel occupation time If the channel occupation is higher than a percentage of the available channels for a specified time period, an email is generated. The time is specified in seconds.

Alarm reaction time Time interval for sending emails. Default 24 hours, which means that the time interval between two emails will be 24 hours. Note that this is not a repetition timer. Once an email is sent, it will not be repeated anymore.



9.8.3 Performance / E-mail Settings, tab “Archive Settings”

When you click the “Archive Settings” tab, the following window is displayed:

The following parameters can be adjusted:

Max. attachment size This is the maximum attachment size. If the archive is larger than the size specified here, it will be chopped into pieces of the specified size.

E-mail nightly created archive This enables automatic sending an email with the nightly created archive file as attachment.

E-mail address(es) Enter the destination email address(es) as destination for the nightly created archive. Note: - You can enter more than one email address separated by “;” (semi colon).

Send archive every Specify the days that the Archive should be send.

Stop sending archive after



After this date, archives are not automatically sent anymore.

9.8.4 Performance / E-mail Settings, tab “E-mail Settings”

When you click the “E-mail Settings” tab, the following window is displayed:

The following items are available:

SMTP Server Enter the DNS name or the IP address of the SMTP mail server.

E-mail from Enter the originators email address. Note that normally the SMTP server does not check the originators email address, which means that you can enter any email address here.

Send test e-mail to Select the addresses to which an e-mail should be send. Please note that these addresses come from the Alarm Settings and Archive settings.

Test e-mail Click this button to send an email to the addresses that have checked checkboxes.



10.9.5 Performance / E-mail Settings, tab “Miscellaneous Settings”

When you click the “Miscellaneous” tab, the following window is displayed:

CDS port Here you can change the port number of the CDS. The CDS takes care of showing the WEB pages. When you change the port here, the port of the WEB server (IIS) for CDS is changed. This means that you must enter the new port number in the URL that you use to reach the WEB page.

HTTP execution time out This is a guarding timer for the ASP scripts. E.g. if the ASP web pages try to send an archive and it takes longer than the time specified here, it will be terminated.

The time is specified in seconds.

Use client resolution If you check this box, you cannot scroll anymore through lists but the available information is chopped up into pages. You can select pages using tabs. If this box is unchecked, information is presented in a way that you can scroll through it using the



scroll bar. Note the information is still chopped up into pages, but the pages contain (much) more information.

Redundancy Time out value This value is the polling time from the DAPs to the DAP Controller. When it times out, the DAPs will try to connect to another redundant DAP Controller

When finished, click “Apply” and continue with clicking button “Customer Information”.

9.9 Customer Information

When you click the “Customer” button, the following window is displayed:

In this window, you can enter customer information. It is only for administrative purposes. The system does not use this information.

When finished, click “Apply”. Continue with Subsection 9.10 “Save System and Start System”.

9.10 Save System and Start System

When you have finished with setting up the configuration, you must do the following:



Note: If you use another TFTP server or DHCP server than the build in TFTP/DHCP server, consult Section 11 “USING OTHER TFTP SERVER" first.

1. Click the Save System button (left side of the DAP Configurator window), to save the changes you have made.

2. If the firmware file is not yet in the TFTP directory, copy the firmware file(s) 4910avxx.dwl (AP200/300) and/or 4920avxx.dwl (AP400) into the TFTP directory. When having AP400, also copy the Loader file 49920201.dwl into the TFTP directory. This directory will normally be the following directory: C:\Documents and Settings\All Users\Application Data\Nec\DAP Controller\<system name>\. When you are using Windows 7 or Windows 2008, the directory is: C:\ProgramData\Nec\DAP Controller\<system name>.

3. Activate the system, using the Activate / Deactivate / System Button.

4. Check the System Status in the System Status Window.

5. Check that the DAPs become operational.

9.11 Finishing Advice

When the system is running correctly, generate a visadm.txt file (in the WEB Page http://<DAP Controller IP Address>/cds/perfform.aspx) and analyse the file, using the SyncAnalyser tool.

If necessary, re-arrange the synchronization structure.

9.12 License Handling

9.12.1 Install a new License File

You can easily install a new license file by means of the “Import license file” which is available at the bottom side of the DAP Configurator.

The license file should have a file extension: .txt



9.12.2 Reading out the Licenses

You can read out the license data by means of the License button in the General Settings window.

Behind the “License” button, you see the date limit for upgrading the DAP Firmware. It means that you can upgrade the DAP firmware with the firmware packages that has been released before the license date. So, the date displayed here does not mean that you cannot upgrade anymore after the date displayed. It means that you cannot upgrade to firmware packages that has been released after this date.



When you click the “License” button, you will see the licenses presented as shown in the following sub-section.



The items in the windows have the following meaning:

ITEM EXPLANATION License Type

DAPS Number of DAPs Allowed Number of DAPs in steps of 10

DCATD For Future use: CAT-iq Data allowed 0 = no

1 = yes

DMESS DECT Messaging allowed on DMLS Number of DAPs in steps of 10

DLOCI DECT Messaging and Location allowed on DMLS

Number of DAPs in steps of 10

DREDND DAP Controller Redundancy (Central DAP Controller)

0 = no

1 = yes

DLSURV Survivability (Local DAP Controllers) 0…10

DCRUISE Special functionality for Cruise Lines 0 = no

1 = yes

DBIGPRJ Special functionality for configurations with more than 256 DAPs in one system with seamless hand-over

0 = no

1 = yes

DXLIC License for using NEC ATEX (Atmospheres Explosive) handsets

0 = no

1 = yes

DREFL Reflective environment licenses. Allows additional settings for reflective environments.

0 = no

1 = yes

DSWU DECT Software upgrade license.

Please note that the date for firmware upgrading is not the actual date limit, but it allows firmware package upgrades with a release date before the upgrade date that is shown here

Number of DAPs + maximum date to upgrade the firmware

Note 1: Please note that the licenses DAPS, DMESS, DLOCI and DSWU are based on the number of DAPs.

Note 2: Licenses that are based on the number of DAPs must always have the same number of DAPs as licensed in the first item: DAPS. So, if the number of DAPS is 40, the other licenses (if required) that are based on the number of DAPs should be forty as well. They cannot be less than the number of DAPs.

Note 3: When you have a DMLS license for the DAP Controller License mechanism, the license information is automatically copied into the DMLS, when the DMLS starts up (make sure that you have the latest DMLS.) When you have a DMLS license for the DMLS itself, (to import into the DMLS directly), you can enter that license into the DAP Controller, by means of the button “Add DMLS”.



10 USING OTHER TFTP SERVER

10.1 General

The previous sections assume that you are using the built in TFTP Server in the DAP Controller/Manager Software. That is the easiest way because paths etc. are automatically set correct. However, if you have chosen to use another TFTP server, paths must be set correct and files needs to be copied into the TFTP root directory. Consult the following section.

10.2 Prepare files for TFTP Upload to DAPs

The DAPs will only become operational if they can load the required files via TFTP. This requires that the DHCP server and the TFTP server are up-and-running with the correct configuration and it requires that the files for the DAP are available in the TFTP directory.

PROCEDURE: “Copying files to the TFTP directory” Actions

1. Determine which TFTP Server you are using. There are four options:

3com TFTP Server on this PC.

Windows TFTP Server on this PC.

Other TFTP Server on this PC.

Other TFTP Server running on other PC.



2. In the following steps you must copy the firmware file (and configuration file) to the upload directory of the TFTP Server. Therefore, you must know the path settings of the TFPT Server that you are using. In the following table an overview is given of the TFTP Servers and the path settings.

TFTP Server Default Path Preferred Path

3com C:\Documents and Settings\All Users\Application Data\Nec\DAP Controller\<system name>\

OR for Windows 7 and 2008:C:\ProgramData\Nec\DAP Controller\<system name>

C:\Documents and Settings\All Users\Application Data\Nec\DAP Controller\<system name>\


Windows C:\tftpdroot\ C:\tftpdroot\

Other Unknown C:\Documents and Settings\All Users\Application Data\Nec\DAP Controller\<system name>\


Table 10-2 "Overview of TFTP Servers"

The two files that need to be in the TFTP directory are:

Firmware file: 4910dvxx.dwl (the one that you have specified in Section 9.2 General Settings.

The configuration file: dapcfg.txt.

Copy the firmware file to the TFTP directory of the TFTP Server that you are using.

If you are using the 3com TFTP server that came with the IP DECT installation (default!) the default path equals the preferred path.

3. The dapcfg.txt file is by default stored in the directory: C:\Documents and Settings\All Users\Application Data\Nec\DAP Controller\<system name>\. OR when you are using Windows 7 or Windows 2008, the directory is C:\ProgramData\Nec\DAP Controller\<system name>. This is the default directory for the “3com TFTP” server that came with the installation of the IP DECT system. If you are using the “3com TFTP” server, no manual action is needed anymore. However, if you are using another TFTP server, copy the dapcfg.txt from the directory C:\Documents and Settings\All Users\Application Data\Nec\DAP Controller\<system name>\ to the TFTP directory that your TFTP Server is using as upload directory. For Windows 7 or Windows 2008, the path is: C:\ProgramData\Nec\DAP Controller\<system name>.

4. Make sure that the option “Next Boot Server” in the DHCP Server that you are using, points to the IP address of the PC where your TFTP Server is running.

5. The DAPs should be able to start-up now.



11 DAP Manager – Web Interface

You can open the DAP Manager Window using Internet Explorer 6.0 or higher.

11.1 PROCEDURE: “Opening the DAP Manager WEB Interface”

11.1.1 Actions

1. Open the MS Internet Explorer WEB browser on your DAP Controller/Manager PC. Enter an URL that points to the /CDS/ directory/file on the DAP Controller/Manager PC. (e.g. http://127.0.0.1/CDS/) It is also possible to open the WEB interface from another PC in the network. However, you must know the right path. This could be e.g. http://192.168.4.80/CDS/, where “192.168.4.80” is the IP address of the DAP Controller/Manager PC.

2. Now, you should see the "DECT Manager" main screen. If not, then check if your IIS is running on the DAP Controller/Manager PC. Also check if the default.aspx file is present in the C:\Inetpub\wwwroot\CDS directory.



3. From the main screen, you can verify that the DAPs have downloaded the correct firmware file version by checking the firmware columns for each DAP.

4. If you have a licensed configuration, assign licenses to your IP DECT system via the DECT Manager interface.

Note: The DECT Manager interface is described in the IP DECT Manager Administrator Guide.



5. Enter the extension number range via the DECT Manager interface.



6. Check that the DAPs are operational.



7. Subscribe the handsets.

Note: - A handset can be subscribed to the IP DECT system before the corresponding extension number is programmed in the PABX. Going off-hook on the handset will fail to register with the PABX until the programming in the PABX is complete.

A 4 digit Authentication Code (PIN) will be generated. This code will be active for 5 minutes before being cancelled. This gives the installer 16 minutes to subscribe the handset to this extension number.

Manually subscribe the handset to the DECT system by traversing to the System – Subscriptions menu on the relevant phone. If there is more than one DECT system in range of the handset, the system PARK may need to be entered. This is displayed above on the web page.

Enter the Authentication Code when prompted.

If successful the phone will prompt for the name of the system. Each of the handsets supplied can be subscribed to more than one DECT system. Enter a descriptive name to identify the system. If left blank “A” will be assigned.

Enter the number of the DECT handset. This number will be displayed on the LCD while the handset is idle and does not need to correspond to the extension number of the PBX. It is not necessary to enter this parameter to subscribe a handset. The PABX extension number that will be used by the DECT handset is the number that the handset is subscribed to in the DAP Manager screen as shown above.



11.2 Checking Synchronisation

Synchronisation between DAP’s in an IP DECT is done via the air interface, and as a result it is critical that DAPs are in close enough proximity to be able to synchronise to each other. It is not possible to achieve handover between two DAP’s that are not synchronised.

The synchronisation structure may be checked using the Sync Analyzer tool.

The Sync Analyzer tool offers a tree diagram that shows how all DAP’s synchronise back to the DAP providing the master clock source.

The synchronisation structure for a system can be outputted via the DECT Performance Manager web interface.

The Performance manager interface can be found at the following address “http: // <server> / CDS / perfform . aspx”, or by depressing the performance manager icon on the main screen as above.



Simply press the “Update Visibility” button which will prompt you to save a file called “visadm.txt” to a directory. Once this file is saved then it can be opened in the “DAP Sync Analyzer” tool, which is included with the DAP manager software.

Select File->Open from the “DAP Sync Analyzer” menu and open the visadm.txt file.

In diagram above, it can be seen that the synchronization structure is represented in a tree format, also that RPN 10 is providing the master clock source for RPN 12, and 13. As a rule the DAP with the lowest RPN will be the master clocking source for the rest of the DAP’s. The first DAP that was


Sync Tree Structure


originally connected to the system after installation will automatically be given the lowest RPN value, making it the master clock source.

The synchronisation structure is dynamically controlled by the DAP firmware, the only way to change it is by either physically moving the DAP’s, or by changing which DAP is the master clock source. Moving the DAP’s would only be under extreme circumstances, however, selecting the best master clock source is critical and should be done for every installation. To find out which DAP should be used as the master, select “View->Best Master”, the RPN that the system calculates as being the best master will be highlighted in the tree view.

Now that the best master has been determined it is necessary to go into the DAP Manager web interface and change the RPN of the best master (as calculated by the sync analyser tool) to be the new RPN 10. To change the RPN’s do the following;

Unplug the DAP that is currently RPN 10


Disconnect current RPN 010


Edit the RPN Number of the Sync Analyzer best master to be “010”, and then click “OK”

Now plug the old RPN 010 DAP back in and it will be allocated a new RPN number.

Once this process is complete, confirm that the new RPN 010 is the best master in the Sync Analyzer by downloading a new “visadm.txt” file.

11.3 Handover Testing

In order to test that the handover between all the Access Points works correctly a tool called “DAP Viewer” must be used. DAP viewer is included as part of the DAP manager software bundle.

DAP Viewer is a tool that polls the DAPs on the network for information on their current operating status. This process requires a substantial amount of network traffic, which on an active network will be undesirable. Ensure that the DAP viewer tool is only used during installation of the system and that it is disconnected prior to the system being operational. When running the DAP Viewer tool it will request that a One Day License Code needs to be entered, as shown below:

Select Yes. A dialog box that prompts for a licensing string to be entered will now be displayed:


Set best master to be new RPN 010

Click OK


The One Day License Code can be generated by a separate tool that is called the One Day Licensing Tool. This tool is shown below:

Press the Generate button. Then press the copy button.

Paste the license string into the Licensing string dialog box.

Press OK

Read the message and press Yes.




Select this to open the system.

Directory that DAP information will be loaded into the DAP Viewer from.

Click the Load Files icon to load the local system information into the DAP Viewer.


Highlight the DAP’s that are to be monitored (Press shift to select more than one). Press the Add button to add them to the view. Click OK.


Select the DAPs that are to be monitored

Click AddClick OK


From the DAP pool select the DAP’s that are to be monitored (Press the Shift key to select multiple DAP’s).

Click the Channel Overview Icon from the toolbar.

The Channel Overview gives a breakdown of every channel in each DAP and tells the user exactly what each channel is doing. (Refer to section 1.2) Items shown above include:


Click for Channel Overview.

Select the DAPs to be monitored

1. RPN 2. Beacon 3. Sync Channel


1. RPN: The column on the far left lists the RPNs of the DAPs. RPN numbers that are in red are currently being used as the Master Clocking Source. Blue RPNs are currently synced to another Master Clocking Source.

2. Beacon: Channels that are highlighted in a pink / orange colour are currently being used to send out beacon information to all of the handsets. For each DAP that has no calls currently on it there will be 2 beacon signals.

3. Sync Channel: DAP’s that are not a Master Clocking source will be in slave mode, where they get their clocking from another DAP, this requires the use of 1 channel. The Channels that are highlighted in blue are used as sync channel. The number displayed in the sync channel details the RPN that it is currently synced to.

Channels that are currently on calls will display in green. By default the number displayed in the channel will be the TPUI of the IP DECT handset, to make this display the station number instead tick the “Translate TPUI into DNR” check box.

4. Handover can be confirmed by setting up a call and walking around the site, whilst someone else watches the calling channel move between the different DAP’s. If a call is able to handover to all of the DAP’s in the system then the handover is working successfully.


Calling Channels Display Station Number


Other useful section that is part of the DAP Viewer is the Registration Overview. This section tells the administrator how many subscription records each of the DAP’s contains, and also in which DAP’s specific extension numbers are connected. This can allow the administrator to know exactly which handsets will not be operational anymore once a DAP is taken off the air.

Note: - Please ensure that you shut down the DAP Viewer Application when finished.


Location Overview

IP DECT Handset on which DAP

IP DECT Handsets to Locate


12 DAP Controller Redundancy

Note: DAP Controller Redundancy is licensed!

12.1 General

DAP Controller Redundancy means that you will have one or more redundant DAP Controller(s) in you network. If the main DAP Controller goes down, another DAP Controller takes over the functionality.

Please note that there are various configurations possible.

Central DAP Controllers A Central DAP Controller controls the entire IP DECT system, so the main site and, if present, Branch Offices. As Central DAP Controller, there is always a Primary DAP Controller and there can be a Secondary DAP Controller for redundancy. As a matter of fact, the Secondary DAP Controller will take over when the Primary fails or is not reachable anymore. The maximum number of Central DAP Controllers is two. For additional redundancy in Branch Office locations, there can be Local DAP Controllers, see next bullet.

Local DAP Controllers A local DAP Controller is located in a Branch Office, and controls its own Branch Office in case the Central DAP Controller(s) cannot be reached anymore. A Local DAP Controller never controls another Branch Office other than its own. So, it operates in a Survivability mode for the Branch Office. The maximum number of Local DAP Controllers is 10.

The difference between a Central and a Local DAP Controller is determined by the configuration that you setup in the “DAP Configurator” in the Primary DAP Controller.

Below, you see the DAP Configurator screen in which you must setup the configuration. Please note that you determine the difference between the Central and the Local DAP Controller here together with the priority.

So, for the Central DAP Controller, you specify a Primary and if required, a Secondary DAP Controller.



A special “service” (Redundancy Service) in the DAP Controller takes care of the redundancy tasks.

Note: All configuration actions are done by means of the DAP Configurator in the Primary DAP Controller

12.2 DAP Controller Redundancy – How does it work

In the DAP Controller Redundancy, there is a Primary DAP Controller and a Secondary DAP Controller. Please note that in an operational configuration, both DAP Controllers are up-and-running. The Primary DAP Controller contains the actual and up-to-date configuration. The Secondary DAP Controller keeps itself updated with the configuration data from the Primary by means of a Presence Check and info exchange. See Below.



Figure 14-2 DAP Controller Redundancy.

The DAPs select to which DAP Controller they will connect, The DAPs select to which DAP Controller they will connect, based on the priorities in the list of DAP Controllers. A DAP will try to connect to the DAP Controller that is first in the priority list (Primary DAP Controller). If that fails, it will try to connect to the second DAP Controller in the list (Secondary DAP Controller). If that fails it will try to connect to the Local DAP Controller that is in the list (see the screen capture in Section 14.1 General.)

The Messaging Application. In the Messaging Application configuration, most likely, one of the Applications is operational, the other stand-by. The Messaging Application is able to detect if Primary DMLS/DAP Controller is active or not. If operational, the primary Messaging Application will be active. If the Primary DMLS/DAP Controller is not active, the Messaging Application detects that, and will make the secondary Messaging Application active.

When the Primary DAP Controller Fails If the Primary DAP Controller fails, the DAPs will notice that the DAP Controller, is not operational anymore, and therefore, the DAPs will try to connect to the Secondary DAP Controller, based on the on-board priority list of DAP Controllers. See Figure 14-2 DAP Controller Redundancy. The Secondary DAP Controller detects that the Primary is not reachable anymore, and will not allow any manual changes in subscriptions anymore.

When the Primary DAP Controller becomes operational gain. When the Primary becomes operational again, the following will happen:

- The DAPs continuously poll the Primary DAP Controller to check if it is back again. Because of that, they will detect that the Primary DAP Controller is up again. Then they will “lock” on the Primary DAP Controller. Then the Primary DAP Controller will retrieve the configuration data (subscription data etc.) from the DAPs, to make the system consistent again.

- The Secondary DAP Controller polls the Primary DAP Controller continuously. When it detects that the Primary DAP Controller is back again, it will request for



configuration data from the Primary DAP Controller. The Primary DAP Controller already received the latest configuration data from the DAPs, and is up-to-date. The Secondary DAP Controller will get the configuration data from the Primary, and then the IP DECT System is consistent again.

What happens when there is a change in the configuration data in the Primary DAP Controller. When there is a change in the configuration data in the Primary DAP Controller (e.g. a handset is subscribed, the Redundancy Service sends a notification to all other DAP Controllers (Secondary and Local DAP Controllers).

12.3 How to Set-Up

PROCEDURE: “Setting up the Redundant Configuration” Actions

1. Make a drawing of the redundant configuration. Determine if you need to have a Secondary DAP Controller and determine if you need to have one or more Local DAP Controllers, and where in the network.

2. If not yet done, open the DAP Configurator and go to “IP Settings” “DAP Controller IP Configuration”.

3. Select Redundant DAP Controller. See the screen capture below.

4. In the list of “Central DAP Controllers, enter the IP address of the Central, Primary DAP Controller in the row Index 1.



5. If you have a secondary DAP Controller, enter the IP Address of the Secondary DAP Controller under Index 2.

6. If you have one or more “Local DAP Controllers”, enter the IP addresses in the table of the Local DAP Controllers.

7. When done, click the Apply button and after that, the Save System button. 8. Finish all other settings for the Primary DAP Controller. When done, click Export System

and save the configuration in a file. 9. Install the other (Central and or Local) DAP Controllers and Import the

Configuration file from the Primary DAP Controller. 10. Now when you can start the DAP Controllers and the Redundant configuration will not

work.

Note: - When the DAP Controller starts, the RDS will show that it is not installed. Refer to example below.

11. Right mouse click the RDS line in the DAP configurator.12. You will now see the following window pop up.

13. Select “Install RDS service”. The service will be installed.14. Close the DAP Configurator Windows by pressing the “Exit” button.15. Open the DAP Configurator.16. Repeat steps 11 to 15 for the Redundant and Local DAP Controllers.



17. Check that the “Redundancy” service called “Redundant DAP Controller” is running as a service under Windows, and check that the “Redundant DAP Controller” service is set to “Automatic”.

12.4 DECT Management

At the Primary DAP Controller Normally you will do DECT Management on the Primary DAP Controller, and you will have full DECT Management functionality available.

At the Secondary DAP Controller When you open the WEB page on the Secondary DAP Controller with address “Localhost”, you will be redirected to the Primary DAP Controller and you will have full DECT Management functionality available. When the Primary DAP Controller is not up-and-running, you will not be redirected, but you will see the Secondary DAP Controller DECT Manager window in Read Only mode. When the Primary DAP Controller comes back again, you will automatically be redirected to the Primary DAP Controller.



12.5 Actual Status Indication

In the top right corner of the DECT Manager WEB interface, the Active status is displayed in red and the Switch to Primary icon is greyed out. The redundancy status is either a Red “Active” or a Green “Standby”. See screen capture below.



13. Appendix A

13.1 General FAQ’s

What is DECT?

DECT stands for Digital Enhanced Cordless Telecommunications and is a standard developed by the European Telecommunications Standards Institute (ETSI) for cordless telephony and messaging in residential and corporate environments.

What is CAT-iq?

CAT-iq stands for Cordless Advanced Technology – internet and quality and enables new features and services like G.722 HD-Voice.

What do I need to order for a new IP DECT installation?

For each IP DECT system to be installed a starter kit must be ordered as this contains the Primary Access Rights Identifier (PARI) required for DECT operation. This includes one DECT Access Point (DAP), four handsets, a PARI and a CD containing necessary software and documentation. A unique PARI is required for each IP DECT installation.

Please refer to e-sales studio for starter kit descriptions.

What is a PARI?

The Primary Access Rights Identifier (PARI) is a unique number that identifies a particular DECT system. It is used to determine which handsets have access to a particular DECT system.

Note 1: - From DAP Controller v4.20.211 to v5.20.103, only a PARI is required to activate a new IP DECT system.

Note 2: - DAP Controller versions prior to v4.20.211 required a PARI and Licenses.

Note 3: - The newest release of DAP Controller v6.00.067 requires a PARI and Licenses.

How many handsets can be supported?

Handsets that are subscribed to the IP DECT system will behave as a Dterm IP extension on the PBX and hence capacity and licensing on the PBX will be required to support each handset that is subscribed. This number can be as large as 6000 handsets for each IP DECT system.

Can the DAPs be mounted outdoors?

A DECT Access Point (DAP) can be mounted externally if installed inside an Outdoor Box.



How scalable is the IP DECT system?

The DECT system can be expanded by adding extra DAPs or handsets are required. A maximum of 750 DAPs (since the release of AP300 and DAP Manager 5.0) can be installed per IP DECT system with each supplying up to 11 channels for voice communication.

What PBX systems are supported?

IP DECT is supported on the UNIVERGE 2000 IPS, UNIVERGE SV7000/MPS/IPX, SV8100 / 8300 /8500. IP DECT integrates to the connected NEC PBX using NEC’s proprietary Protims Over IP protocol. This tight integration to the PBX allows for many of the NEC PBX features to be accessed using the DECT handset.

What PBX Features are supported?Refer to section 5

What type of durability tests have been done on the handsets?

The I755 handset has been tested against Ingress Protection 54 (IP54) classification. This includes dust and water spray testing.



AP400 versus AP300

From July 2013 onwards, the AP300 will no longer be available and the AP400 will be introduced as its successor.

The differences between the two AP types are shown in the table below;

ITEM AP300 AP400

Outside Temperature 0 C 45 C -5 C 45 C

CAT-iq Data facilities - Not applicable yet.

DAP Type:

Generic type, NEC branded

AP300 AP400

DAP Type:

Generic Type with connectors for external antennas

AP300E AP400E

Boot Package In Read Only Memory In Flash Memory.

Name: 49920xxx.dwl

Firmware Package Name: 4910dxxx.dwl Name: 4920dxxx.dwl

IGMP Version IGMPv2 IGMPv3



What is the talk and their standby times of the handsets?

Handset G355

No Longer Available

G955

No Longer Available

I755 G266 G566 M155

Positioning Office Hi-Office Industry Healthcare

Office Hi-Office Messenger for Healthcare

Talk time Up to 12 hours

Up to 12 hours

Up to 10 hours

Up to 20 hours

Up to 20 hours

Up to 8 hours

Standby time

Up to 120 hours

Up to 120 hours

Up to 120 hours

Up to 160 hours

Up to 160 hours

Up to 80 hours

Li-ion Battery life time

The life of a Lithium-Ion battery (applied in the G355, G955, I755 and M155) is about 300 – 500 charge cycles (fully charged to fully discharged). Depending on the way the DECT handset is used (and the battery is charged / discharged) a typical life expectancy for the Li-ion batteries is 2 to 3 years.

Note: - The rechargeable Lithium-Ion batteries have a limited life time and will gradually lose their capacity (aging), resulting in shorter talk- and stand-by times for the DECT handset.

How can the system be expanded?

Further DAPs can be ordered to expand the coverage area or increase the number of channels in a particular area. Further handsets can be ordered as required.

Is the NEC IP DECT system GAP compliant?

NEC’s IP DECT Access Points (DAPs) comply with the Generic Access Profile (GAP) standard allowing GAP compatible handsets to be registered to NEC’s IP DECT system. Contact NEC product Management if this functionality is required.

What is a multi-site license?

NEC’s DECT handsets can be subscribed to more than one IP DECT system. A multi-site license can be used when a large number of DECT handsets need to be used on two or more independent DECT systems. This license allows the handset to be subscribed only once to gain access to more than one DECT system, considerably reducing the time required for installation.



Differences between IP DECT versus VoWLAN

IP-DECT VoWLAN

Air Interface DECT (like GSM) is a Micro Cellular Network.

Wi-Fi Interface

Frequency Range Bandwidth Dedicated for DECT. Free to Air

Risk of Interference Dedicated Bandwidth, so no other applications using the same frequency range.

Shared Frequency Range

Security DECT standard incorporates built-in security protocols that eliminates eavesdropping, impersonation and other security breaches by:

PARI – Unique Identifier to the system.

IPUI – International Portable User Identifier

UAK – User Authentication Key

- 128-bit key that is created at subscription and not transmitted.

PCK – DECT Ciphering Key

- 64-bit key transmitted over the air.

WEP – Wireless Equivalent Privacy

IPEI – International Portable Equipment Identifier or (MAC)

802.11i standard

Intercell Handover Seamless Handover. Prior to replacing the existing connection in the air, a new and better connection is established.

There will never be a gap in connection during handover.

At handover, the existing connection is broken down in the air and also in the IP Network.

Then a new connection is established via another access point.

Using the 802.11i security standard, handover can be extended to over 70 milliseconds.

Breaks in conversations are noticed at 50 milliseconds.

Intra Cell Handover Yes, seamless No

Dynamically better Channel Selection

Yes No



13.2 Installation FAQ

What is required for Installation of IP DECT?

Site survey to determine the number of DECT Access Points (DAP’s) required to cover a certain area.

Network readiness assessment needs to be performed to determine if the customer’s network can support voice.

Multicast capable routers are required to support seamless handover between the DAP’s. DHCP server to assign IP settings to the DAP’s. TFTP server to download the configuration file to the DAP’s. PC with DAP Manager Software installed.

What if I don’t have a Multicast capable router?

Multicast packets are transmitted between the DAP’s to facilitate seamless handover. In some situations a multicast capable router is not required. For example, if all DAP’s are connected to the same network segment via Ethernet switches. Or if DAP’s are connected on different network segments and Unicast Routing is provided between the networks.

Note: When DAP’s are connected to a different network segment to the main site they are regarded as Branch office DAP’s and no handover is possible between the Branch office and Main site.

What is the DAP Manager?

The DAP Manager Software is used during installation to:

Subscribe Handsets Perform DAP maintenance

The DAP Manager Software is used during operation to:

Facilitate Portable Sharing and Handset to Handset messaging Allow DAP’s to be connected in a Branch office Capture debug / system information.

NEC recommends running the DAP Manager Software at all times that the DECT system is operational.

What is the minimum PC requirements for the DAP Manager?

Refer to section 3

Is the DAP Manager required for normal operation?

NEC recommends running the DAP Manager Software at all times that the DECT system is operational.



Can I run other software on the DAP Manager PC?

The DAP Manager service is not memory or processor intensive and hence other software can be running concurrently on the same PC.

What Codecs are supported by the NEC IP DECT system?

NEC’s IP DECT solution supports G.711, G.729A codec.

What is G.729?

G.729 is an audio data compression algorithm for voice that is mostly used in Voice Over IP (VoIP) applications that require low bandwidth.

When do I need a G.729 license?

If a call between an IP DECT Access Point is setup to an endpoint on a different network segment over the Wide Area Network (WAN) and sufficient Bandwidth does not exist between the two networks to support the G.711 codec. Typically a call using the G.711 codec will consume about 80kbps of bandwidth in one direction. Conversely, a call using the G.729 codec will consume about 24kbps of bandwidth. The speech quality of G.729 calls is marginally worse. The availability of Bandwidth as well as traffic density across the WAN needs to be considered when assessing the requirement for a G.729 license. This license is sold per call that is in progress across the WAN.

What extra hardware is required for installation?

Dynamic Host Configuration Protocol (DHCP) server is required to assign IP network settings to the DAP’s.

TFTP server is required to download the configuration file to the DAP’s. A Server PC running the DAP Manager Software. For large installations a Site Survey Kit is required for accurate measurements.

Note: It is possible to operate the DAP’s without a DHCP/TFTP server. Consult the IP DECT Installation manual for further details.



Is a DHCP / TFTP server permanently required?

A DHCP / TFTP server is required at least once to assign the IP address and configuration parameters to the DAP’s. Once these parameters have been assigned it is possible to remove the DHCP / TFTP server form the network. To do this the following must be done:

Setup the DHCP server to assign network settings (IP Address, Subnet Mask, Default Gateway, TFTP server address etc.) with an Infinite Lease Time.

Setup the Configuration file to include Config File = Replace, and IP Config = replace. This can be found under “Boot Options” in the DAP Configurator.

On receiving a configuration file with Boot Options = Replace and Network settings from the DHCP server with an Infinite lease time, the DAP will save the configuration and network parameters in flash memory. The DHCP server and TFTP server is no longer required.

DAP does not download configuration file from the TFTP server?

Some TFTP Servers will show a log of requests. Check to see if the TFTP server is receiving the read request from the DAP in question.

The DAP’s obtain the IP Address of the TFTP server from option 66 in the DHCP server setup.

Ensure that option 66 is enabled on the DHCP server for the particular scope that is to service the DAP’s. Option 67 can also be setup to tell the DAP’s the name of the configuration file to download. This field is optional. The DAP’s will request “dapcfg.txt” as a default if option 67 does not exist.

Check that the TFTP server software is running and that the path for the configuration file is setup correctly.

If the TFTP server IP Address obtained from Option 66 of the DHCP server is on a different network segment to the DAP’s, ensure that there is Unicast routing between the network segments.

Ensure that the TFTP server software is capable of simultaneous TFTP requests to service the number of DAP’s connected. The maximum number of requests is configurable on some TFTP Servers.

Installed the DAP’s but handover does not work when walking around?

To Achieve handover IP DECT Access Points (DAP’s) must belong to the same DECT system and be transmitting the same Primary Access Rights Identifier (PARI).

Ensure that all DAP’s in a DECT cluster are downloading the same dapcfg.txt configuration file from the TFTP server. The dapcfg.txt file will contain the DAP Manager IP address.

Ensure that all DAP’s have contacted the DAP Manager successfully. This can be checked by browsing to http://localhost/cds on the DAP Manager PC and clicking on the Access Points link. The DAP’s need to contact the DAP Manager at least once during installation to receive the PARI information located in the ds.txt file.




To Achieve handover IP DECT Access Points (DAP’s) must be synchronized via the Air Interface.

Check the synchronization structure of the DAP’s in a DECT cluster. This can be done by browsing to http://localhost/cds/perfform . aspx on the DAP Manager PC and clicking on “Save Visibility”. This generates a text file that contains synchronization information. Use the “DAP Sync Analyser” tool to analyse this information and ensure that all DAPs are synchronized to one Master.

In a DAP Cluster one DAP will be synchronization Master and all other DAP’s will be slaves. Slave DAP’s need to utilize an Air channel for synchronization. Ensure that all DAP’s have sufficient channels available to allow for synchronization. This can be checked by browsing to http://localhost/cds on the DAP Manager PC and clicking on the “Access Points” link. Check the available channels for each DAP. A DAP must have at least 2 channels available to be able to synchronize to another DAP.

A Slave DAP must be able to receive the synchronization signal via the Air. Ensure that sufficient signal strength exists for synchronization. The Radio Signal Strength Indicator (RSSI) between DAP’s cannot be lower than -80dbm.

To Achieve handover IP DECT Access Points (DAP’s) send information using Multicast.

If the DAP’s are connected to the same Network Segment via 100Mb Ethernet Switches then ensure that “IGMP Snooping” is disabled on the Switch. IGMP Snooping is a feature in some Ethernet switches that allows the Switch to listen for IGMP Join Messages coming from Multicast Capable hosts to allow Multicast traffic to traverse these ports. DAP’s send IGMP Join Messages when starting up, however if a Switch misses this message it will not allow Multicast traffic on that port.

Cannot make call on DECT handset?

Each DAP stores the subscription record of a small number of handsets during the subscription process. This DAP is then responsible for performing the NEC Protims signalling to the PBX. Determine which DAP holds the subscription record of the handset in question and ensure that this DAP is operational. This can be checked by browsing to http://localhost/cds on the DAP Manager PC and clicking on “Subscriptions”.

Check that the handset has sufficient signal strength from at least one Access Point. If the handset does not have sufficient signal from an Access Point “Searching System” will be displayed on the LCD of the phone. The handset can be placed in Site Survey Mode temporarily to check the Radio Signal Strength Indicator (RSSI) from the surrounding DAP’s.

Check that the handset is subscribed to the DECT system and that the Number is a valid PABX DtermIP Protims Extension number.




http://localhost/cds/perfform%20.%20aspx


Poor voice quality on DECT handset?

Ensure that the handset has sufficient signal strength from at least one DAP. An accurate Site Survey may be required to determine if cell coverage is sufficient. Alternatively the G955 / I755 / G266 / G566 handsets can be placed into Site Survey Mode temporarily to determine the Radio Signal Strength Indicator (RSSI). This is done by pressing the following keys: <menu> *789872*.

Ensure that the DAPs are connected to 100M Ethernet switches.

Ensure that the DAP has negotiated 100M Full Duplex with the connected switch. The switch port must be configured for “Auto Negotiate” since the DAP is also configured for “Auto Negotiate”. Do no fix the speed and duplex settings of the switch port.

Ensure that the IP DECT system is installed on a separate dedicated VLAN. The Access Points support 802.1q VLAN tagging and hence can be connected to a switch trunk port. Alternatively the switch port connecting the Access Point can be fixed to a particular VLAN.

Ensure that there is sufficient bandwidth between the Endpoints involved in the conversation. IP DECT Access Points support a payload of 20, 30, 40, 50, and 60ms. It is recommended to use a payload cycle of 40ms.

For a payload cycle of 40ms the following is an estimate of the required bandwidth per call (in one direction) for the negotiated codec.

40ms payload = 1 packet sent every 40ms = 25 packets/s

G.711Payload = 64,000 / 25 = 2560 bits/packet = 320 octets + 78 octets (headers) = 398 octets.

Bandwidth = 398 x 25 x 8 = 79600bps.

G.729APayload = 8000 / 25 = 320 bits/packet = 40 octets + 78 octets (headers) = 118 octets. Bandwidth = 118 x 25 x 8 = 23600bps

Ensure that QoS is configured in the network to support prioritization of voice packets. IP DECT Access Points support L2 802.1p and L3 Diffserv (RFC2474)



How can I determine if the DAPs are synchronized?

The synchronization structure can be determined by browsing to http://localhost/cds/perfform.aspx on the DAP Manager PC and clicking on “Save Visibility”. A text file will be generated that will contain all synchronization information. This file can be loaded into the “DAP Sync Analyser tool” for easy interpretation.

What happens if there is not enough signal strength between the DAP’s for

synchronization?

Within a DECT cluster there is one synchronization Master and all other DAPs are slaves. If a DAP powers up and cannot see any other DAP’s to synchronize off then it will become its own Master and a new DECT Cluster is formed. There will be no handover between the Clusters however.

How can I check the Radio Signal Strength?

The Radio Signal Strength Indicator can be checked on any of the NEC IP DECT handsets. (G955 / I755 / G266 / G566) Press <menu> *789872*.

How can I check what firmware version the DAPs are running?

The firmware version of the DAP’s can be checked by browsing to http://localhost/cds on the DAP Manager PC and clicking on “Access Points”.

How can I upgrade the firmware on the DAPs?

To upgrade the DAP’s execute the following procedure:o Load the current configuration using the DAP Configurator tool. o Change the firmware file name to the new firmware. o Save the configuration. o Ensure that the new configuration file is in the TFTP root directory and that the

TFTP server is running. o Ensure that a DHCP server is running on the network connecting the DAP’s and

that option 66 and 67 are configured with the IP Address of the TFTP server and the name of the configuration file.

o Reboot the DAP’s by browsing to http://localhost/cds on the DAP Manager PC and selecting “Access Points”.

o Select the DAP you wish to reboot and click on reboot DAP.

Can the DECT handsets move between sites?

The NEC IP DECT handsets can be subscribed to more than one IP DECT system and can automatically select the IP DECT system that is in radio range. The G266, G566 and I755 handset can be subscribed to 10 independent systems.




http://localhost/cds/perfform.aspx


What is required to run a DAP in a Branch Office?

There must be Unicast Routing between the Branch office and the Main Head Quarters.

There must be a local DHCP server at the Branch office to assign network settings to the DAP’s. This DHCP server must be configured with option 66 and 67 to inform the DAP’s of the IP address of the TFTP server from which it can download the configuration file.

There must be a DAP Manager running on the network.

On connecting the DAP in the Branch office:

o The DHCP server will assign an IP Address and Subnet mask to the DAP. o It will also inform the DAP of the IP Address of the TFTP server in option 66 and

the name of the configuration file in option 67. o The DAP will download the configuration file from the TFTP server. o The configuration file will contain the IP Address of the DAP Manager and the

PBX. o The DAP will then contact the DAP Manager PC. o If the DAP is on a different network segment to that of the PBX as determined by

the IP Address, Subnet Mask and Aggregate Mask (In the Configuration file), then the DAP Manager will regard this DAP as a Branch office DAP and will consume a Branch office DAP license. There are 255 of these licenses available to support the maximum number of DAP’s.



When will the DAP select G.711 and when will it select G.729?

During the call setup phase between an IP DECT handset and a PBX extension, the PBX will inform both endpoints of the allowed Codec that can be used by each end point and the priority of each Codec. This is determined by the location group settings in the PBX programming. Each endpoint will then select the preferred Codec for the connection and inform the peer party of its choice.

An IP DECT Access Point, as the Endpoint in a connection, will check to see if the peer endpoint is on the same network segment, as determined by the IP Address, Subnet Mask and Aggregate Mask (in the configuration file). If it determines that the peer endpoint is on the same network segment and G.711 is one of the Codec offered by the peer it will select G.711. Conversely, if it determines that the peer endpoint is on a different network segment, it will select G.729 as the Codec, provided that it was offered by the peer endpoint and that there are G.729 licenses available. The table below gives a summary of the different situations.

Codec list offered by Peer Endpoint Same Segment Different Segment

1st G.729

2nd G.711 G.711 G.729

1st G.711

2nd G.729 G.711 G.729

G.729 License Available G.729 G.729

G.711 G.711 G.711

G.729 No License Call Fails Call Fails

G.729 No License

G.711 G.711 G.711

If I am running a DAP in a Branch Office, what happens if there are no G.729 licenses?

See answer for the question above.

What happens if a DAP goes down?

Each DAP stores subscription records for DECT handsets during subscription. A maximum of 25 subscription records can be stored per DAP. This DAP is then responsible for performing all the signalling to the PBX for that particular DECT handset. If a DAP goes down, all the handsets that are stored in the DAP will be unable to make calls. If the DAP Manger PC is installed and operational the subscription records for those handsets will be moved to another DAP, restoring normal operation. This process can take several minutes.



How can Handover be checked?

During installation it is recommended to use the DAP Viewer debugging tool to check handover. This tool is capable of displaying the channel usage on the DAP’s and will show active calls in progress. Consult the documentation for further information.

When I answer an incoming call on the handset by pressing the off-hook button after

removing it from the charger the call is dropped.

The C944 / C244 / I600 DECT handsets have a feature called “Charger Answer”. This feature allows the user to answer an incoming call automatically by removing the handset from the charger. It therefore not necessary to press the off-hook button to answer the call. In fact, doing so will disconnect the call.

Deadlock situation on Gx55 (PIN code forgotten)

When a user has forgotten his PIN code, there is no way to use the handset again (only send in for repair).

Now the following procedure is implemented to "unlock" the handset:

1. Switch on the handset and when the (forgotten) PIN code is requested, you enter a wrong or no PIN code.

2. The display shows "Wrong PIN code".3. Press "OK".4. Again the PIN code is requested.5. Now it is possible to enter a special code (*reset* or *73738*).6. The display will show "OK to reset?"7. Press "Yes"

Note: - The handset will be reset (phone book and caller lists are cleared, etc.).The subscription remains. However, the subscription name and the user name in the handset are also cleared (can be edited on the handset).



For more information, visit au.nec.com, email [email protected] or call 131 632

Australia Corporate Headquarters (Japan) North America (USA) Asia Pacific (AP) Europe (EMEA)

NEC Australia Pty Ltd NEC Corporation NEC Corporation of America NEC Asia Pacific NEC Unified Solutions

au.nec.com.au www.nec.com www.necam.com www.nec.com.sg www.nec-unified.com

About NEC Australia Pty Ltd. NEC Australia is a leading technology company, delivering a complete portfolio of ICT solutions and services to large enterprise, small business and government customers. NEC Australia helps customers gain greater business value from their technology investments.

NEC Australia specialises in communications solutions and services in multi-vendor environments, including systems integration, specialist communications solutions, data networking, unified communications and collaboration, biometrics, digital signage and display solutions. Its IT solutions services comprise business and IT transformation consultancy, professional services, application and solutions development and infrastructure and applications managed services. For more information, visit NEC Australia at au.nec.com

NEC Australia Pty Ltd reserves the right to change product specifications, functions, or features, at any time, without notice. Please refer to your local NEC representatives for further details. Although all efforts have been made to ensure that the contents are correct, NEC shall not be liable for any direct, indirect, consequential or incidental damages resulting from the use of the equipment, manual or any related materials. The information contained herein is the property of NEC Australia Pty Ltd and shall not be reproduced without prior written approval from NEC Australia Pty Ltd.

Copyright © 2013 NEC Australia Pty Ltd. All rights reserved. NEC, NEC logo, and UNIVERGE are trademarks or registered trademarks of NEC Corporation that may be registered in Japan and other jurisdictions. All other trademarks are the property of their respective owners. All rights reserved. Printed in Australia. Note: This disclaimer also applies to all related documents previously published.


Release 6 – IP DECT - NEC : Welcome interop... · Web view(Digital Enhanced Cordless...

Documents

Transcript of Release 6 – IP DECT - NEC : Welcome interop... · Web view(Digital Enhanced Cordless...