DECT Manager Manual PDF
DECT Manager Manual PDF
1. INTRODUCTION........................................................................................................ 5
1.1. GENERAL ............................................................................................................... 5
1.2. THE DECT SYSTEM .............................................................................................. 5
1.3. DECT Manager MAIN FUNCTIONS ....................................................................... 6
1.4. BASIC MODULES IN THE DECT Manager ............................................................ 7
1.4.1. Additional Modules for Performance Management ................................................. 8
1.5. DECT MANAGER INTERFACE TYPES ................................................................. 9
1.6. PROCEDURES FOR USING THE DECT Manager .............................................. 11
2. INSTALLATION ....................................................................................................... 12
3. CONNECTION CONFIGURATION .......................................................................... 13
3.1. GENERAL ............................................................................................................. 13
3.2. WHICH CONNECTION MANAGER TYPE TO USE ............................................. 14
3.3. CONNECTION MANAGER ................................................................................... 15
3.4. CM@Net CONNECTION SETUP ......................................................................... 16
4. LICENCE MECHANISMS ........................................................................................ 19
4.1. INTRODUCTION................................................................................................... 19
4.2. LICENCE MANAGER ........................................................................................... 19
4.3. HOW TO USE THE LICENCE MANAGER ........................................................... 20
5. USING DECT Manager ........................................................................................... 21
5.1. GENERAL ............................................................................................................. 21
5.2. LOGIN MODULE................................................................................................... 21
5.2.1. General ................................................................................................................. 21
5.2.2. Using the User Administrator .............................................................................. 22
5.3. DATABASE STRUCTURES ................................................................................. 23
5.3.1. General ................................................................................................................. 23
5.3.2. Keeping Databases Consistent............................................................................. 26
5.4. STARTING-UP THE DECT Manager.................................................................... 26
5.4.1. For The First Time on a Specific DECT System ................................................... 26
5.4.2. Starting DECT Manager for Known DECT System ............................................... 31
5.4.3. Advanced BUTTON ............................................................................................ 32
5.5. DECT Manager SCREEN LAYOUT ...................................................................... 34
6. SUBSCRIPTION MANAGEMENT ........................................................................... 36
6.1. GENERAL ............................................................................................................. 36
6.2. MULTI-SITE MOBILITY ........................................................................................ 37
6.3. SUBSCRIPTION STATUSES ............................................................................... 40
6.4. SUBSCRIPTION SCREEN ................................................................................... 42
6.5. HOW TO SUBSCRIBE A HANDSET .................................................................... 44
6.6. HOW TO DE-SUBSCRIBE/DISABLE A HANDSET.............................................. 45
7. BOARD MANAGEMENT ......................................................................................... 46
7.1. SCREEN ............................................................................................................... 46
7.2. MENU OPTIONS .................................................................................................. 48
8. RADIO MANAGEMENT........................................................................................... 49
8.1. SCREEN ............................................................................................................... 49
This manual is valid for the DECT Manager Module Version 3.1.3 which supports DCC-
8(R).
This DECT Manager version is available under SMPC 5.3 and Management@Net 3.1.
1.1. GENERAL
The DECT Manager is a Management tool for the integrated DECT functionality in the
SOPHO ISPBX. This management tool runs on a PC under Windows 2000 Professional or
Server.
The DECT Manager is a module in Management@Net and the SMPC (SOPHO
Maintenance PC). The DECT Manager will never exist as stand alone module.
Installation of the DECT Manager is part of the installation of the SMPC or
Management@Net and therefore the installation of the DECT Manager is not described in
this manual. For installation, consult the manuals for SMPC or Management@Net
This manual describes how to use the DECT Manager.
The DECT System is a mobile communication system which provides DECT (Digital
Enhanced Cordless Telecommunications) facilities integrated in an ISPBX. The following
figure gives an overview of the system configuration.
ISPBX
Trunk lines
ALC
Handsets
DCC RFP
RFP
DECT Manager
Mobile users carry a portable DECT handset. This handset communicates with the ISPBX
via radio transceivers. The radio transceivers are connected to (one of the) DCC (DECT
Cluster Controller) boards in the ISPBX.
This identifier is always transmitted by all RFPs as a beacon. The handset recognises this
beacon and will be listening to that signal, to see if there is a call for it.
The DECT Manager is connected to the DECT System for management purposes.
The DECT Manager is connected to one of the DCC boards in the DECT System. This can
be a direct connection (with barrier box) or via modems. During normal operation, it is not
necessary to have the DECT Manager connected to the DECT System.
- Subscription Handling
This allows you to register (Subscribe) a PP to the system, or to de-register (de-
subscribe) a PP from the system.
- Board Management
This allows you to view the status of the board(s) and to make a backup of the
subscription data (registration data of the PPs) which is stored in the boards. As a matter
of fact you can also restore the subscription data to the board.
- Radio Management
This allows you to display the radio statuses and you can inform the system about the
required status.
- Configuration Management
This function is used to enter the DECT extension numbers.
The Connection Manager is also used for dialled connections via a modem when
you have a so called DCMIP connection, consult section 1.5 for more information.
When you are using an SNMP connection (see section 1.5), you must install the
modem software under Windows.
- Subscription Handling.
- Board Management.
- Radio Management
- Configuration Management.
- Subscription
Management
- Board
Configurator
Management
- Radio
Management Connection
To DECT
- Config. Manager System
Management Module
Besides the basic modules, there are tools to handle performance data. However, there is
a difference in performance data handling between the two types of interfaces that can
exist between the DECT System and the DECT Manager. For information on these two
types of interfaces consult section 1.5.
The DECT Performance Manager is licensed by means of the License Manager. The
License Manager is automatically installed during installation of the DECT Manager.
However, the License Manager requires a dongle and a license file, to enable the
Performance Manager.
The DECT Manager can work with two different types of Interface Protocols to the
DCC(s) in the DECT System:
Note, that the DCC-8 uses SNMP over TCP/IP and the DCC-8(R) uses DCMIP over
TCP/IP.
Note: The DECT Manager under SMPC 5.3 and Management@Net 3.1 will select the
higher layer protocol (either SNMP or DCMIP) automatically when connection
is made. You dont need to set this up in the configuration!
The connection configuration of a DECT Manager using DCMIP with V-modem over
V.24 (using DCMIP protocol) is straight forward and is depicted in Figure 2.
Interworking between the DECT Manager Modules.
Note: The DECT Manager under the SMPC umbrella supports all protocols and
connection types and therefore all DCC board types.
The DECT Manager under Management@Net (latest version) only supports TCP/IP
protocol. The means that all DCC types are supported except for DCC-4 boards
with firmware package F43040 and F43140.
Windows Environment
DECT Manager
- Subscription
DECT Man.
Management
Connections
- Board Configurator
Management
- Radio
Management
Connection
- Config. Manager TCP/IP
Management Module Protocol Stack
Dial-Up
Adaptor
To DECT
System
Figure 3. Interworking between the DECT Manager Modules (without License Manager
and Performance Manager and based on TCP/IP protocol).
1. Make sure that the DECT System is correctly installed (consult the DECT CE Manual).
2. Make sure that the DECT Manager is correctly connected to the DECT System (consult
the DECT CE Manual).
3. Install the DECT Manager under Windows. (Consult chapter 2 in this manual).
4. If you are using your DECT Manager with a TCP/IP connection to the DECT System via
V.24, you must configure the (null) modem configuration and the Dial-Up adaptor under
Windows first before continuing with the next step. Configuring the modem and Dial-Up
adaptor under Windows is described in Appendix B.
5. Configure the Connection Manager to specify the connection to the DECT System(s)
that you want to manage (see chapter 4 in this manual).
7. Start-up the DECT Manager Module and make it ready for use. (see chapter 4 in this
manual.)
8. Subscribe the handsets (see chapter 5 in this manual). For a step by step subscription
procedure, consult the DECT CE Manual.
For more information on the hardware aspects or on the functionality of DECT, consult the
DECT CE Manual.
Consult the SMPC or Management@Net CE Manuals for the installation procedure of the
DECT Manager.
3.1. GENERAL
You use the Connection Manager to specify details of connections and set-up connections
between your PC and DECT Systems. These details are used by the DECT Manager
module to establish a connection with the DECT System. The Connection Manager also
co-operates with the Licence Manager, to check the licence of an application before it may
run.
This chapter does not give a detailed step-by-step description on how to set up the
connections, because that is described in the On-line Help. However, this chapter
provides insight in a number of aspects of the connection set-up.
CM@Net
This is the current type of Connection Management tool. The configuration is stored in
an SQL database. Therefore it requires that you have an SQL Server or MSDE Server
running on your computer. You can set up IP connections only via this tool. The IP
connection can be over Ethernet, or V.24 using a Dial-Up adaptor (via modem, null-
modem or direct cable connection). The configuration tool for the CM@Net can be
started via the following icon, which is present in the Configurators icon / directory.
When you start up this SMPC Configuration Manager, you are guided through a couple of
windows to set up configuration details. This is not described in this manual, because it is
SMPC specific. However, when you come to the point where you have to set up the
Connection Manager items, you must choose between the Connection Manager for V.24 or
CM@Net for IP connections. This selection must be made by means of the following
screen:
If you select the option V.24, you will create a configuration via the Connection Manager for
V.24 connections (and limited types of IP connections). If you select TCP/IP connections,
you will create a configuration via the CM@Net module for TCP/IP connections.
The following table gives an overview of the Connection Manager types and the Board
types that there are.
Connection CM@Net
Board type Firmware and Interface
Manager
Protocol
* = In the Windows configuration in the Manager PC, you must setup a Dial-Up adaptor
The following sections give information on how to set up a connection with the Connection
Manager for various types of DCC boards.
To setup a connection to a DECT System over V.24 using to a DCC-4 with firmware
package F43040 or F43140, follow the following procedure:
1. Startup the Connection Manager Configurator, either via the SMPC Configuration
Manager or via the CM Database Configurator.
For a direct V.24 connection, use the Direct connection to ISPBX without buffer or port-
selector.
To set up a connection to a DCC System using TCP/IP over V.24 or Ethernet, follow the
following procedure:
Note: This procedure assumes that there is only one connection, which is exclusively
used for the DECT System. If you want to set up more than one connections to
more destinations or devices, the configuration set up is more complex and not
described in this manual.
1. Start up the CM@Net Configurator, either via the SMPC Configuration Manager or via
the CM@Net Database Configurator.
3. After creating the PBX CPU3000 item, you will see a configuration with an item
iSPBX. Right mouse click this item and select Create and then DAS-iS. The window
should look like the following:
Here you must fill in the IP address or the Host Name of the DCC board to which you
want to set up a connection. (Host Name is only possible if there is a reference in a
DNS server to the DCC. This is normally not the case.)
The default values in the other fields in this screen are generally correct and do not
need to be changed. However, if the connection goes via a Proxy Server, you must
check the box Use Proxy. Then you will see more fields that should be filled in. The
information should come from the IT Manager for the network.
Note: If you have a V.24 connection, you still need to set up the Dial-Up adaptor in the
Windows environment. This is explained in Appendix B. If you have an Ethernet
connection, make sure that the Ethernet adaptor card settings are correct.
Note: Besides setting up the connection configuration, you need to set up the DECT
Manager. (See chapter 5)
4.1. INTRODUCTION
Licence Manager
The License Manager is part of the Management@Net or SMPC software. It enables
the functions of your DECT Manager to be used.
Handset licensing
Handset licensing is a function of the DECT Manager Module itself. It determines the
maximum number of handsets that can be used on your DECT System.
This type of licensing is mentioned in the chapter 5, "USING DECT Manager and in
chapter 10, CHANGING OPTIONS in this manual.
You use the Licence Manager to activate the licences for the functions in the DECT
Manager module.
By means of the Licence Manager, you can load and display the licences.
Subscription Man.
Application Functional (Tab)
Dongle
License Level License
No - -
Yes - -
Board Man. (Tab)
DECT
Yes Subscription
Man.Mod.
Subscription Man.
How to use the Licence Manager is described in the dedicated manuals for
Management@Net or SMPC. (Getting Started and the CE Manual.)
5.1. GENERAL
The DECT Manager can be used to manage a multiple of DECT Systems. It allows remote
connections. The general characteristics of the DECT Manager are as follows:
The DECT Manager creates and maintains a Database of each DECT System to which it
has been connected. This means that the Database in the DECT Manager must be kept
consistent with the Database in the DECT System. Therefore read the section Database
Structures in this chapter carefully.
5.2.1. General
The Login Module is a back ground module which is fully integrated with the DECT
Manager Module. It provides personalised access protection on user level. It also provides
personal definition of the language for each individual user. The background process of the
Login Module presents a login screen to the DECT Manager user and to the DECT
Manager Connections configurator user.
System administrator
The system administrator level is the first entry for the Login Module. So, the first time
that you use the Login Module, you must login on this level by means of the name
System Administrator and an empty password field. It gives you full access (same as
1
An un-concentrated DECT System allows you to have a maximum of 32 extension
numbers on one DCC. A concentrated DECT System allows you to have more than 32
extension numbers on one DCC.
Administrator
The administrators are allowed to manage ordinary users and their profile, and have full
subscription and configuration authority for the DECT Manager. Users, logging in as
administrator are able to:
Ordinary users
Ordinary users have usage authority for the DECT Manager as assigned by the
administrator. This authority can be:
The Login Module is a background process. However, the background process uses a
database file in which the users are specified. To configure the user database file, you
must use the User Administrator.
- Add users,
- Delete users,
- Change user profiles,
- Print users,
- Change options
- Find users.
5.3.1. General
There are Databases at two sides: the boards in the DECT System and the DECT
Manager. The Databases contain configuration information as well as subscription
information.
The two data bases should contain exactly the same information (should be consistent).
The DECT Manager uses the following mechanism to keep the Database consistent with
the DECT System:
- At the very first time connection to a DECT System, the Database is copied from the
System to the DECT Manager.
- If you make any changes, the DECT Manager will take care that the content of its
Database is kept consistent with the DECT System.
If somebody else is using another DECT Manager on the DECT System, and makes
changes, then your DECT Manager is not capable anymore to keep its Database
consistent with the System. The DECT Manager does NOT notice that the Database is not
consistent any more, so the information on you DECT Manager screen is not reliable
anymore !
DECT
SYSTEM
(Operational
DataBase Updates DECT Man.
per Board) Local
DataBase
If you are not sure, that you have a recent copy of the operational
DataBase, you can make a backup of one or more DECT boards
DECT
Local DataBase only refreshed if
SYSTEM
you make a backup of the
(Operational
operational DataBase per DECT DECT Man.
DataBase
Board in the system Local
per Board)
DataBase
Make sure that no other DECT Manager will ever be used on your DECT System.
You can do this by make firm agreements with all other possible DECT Manager users
in the environment.
If you are not sure that you are the only one with a DECT Manager that has
access to the DECT System, make sure that you always make a backup first, after
establishing a connection or before you are making any changes by means of the
DECT Manager.
The Database file in the DECT Manager is related to other files, so dont try to store the
Database file on floppy or other medium.
If you want to make a backup of the database, use the Advanced button.
Note: If the Database on a board is not reliable anymore you can execute a Clean Board
for that specific board. This means that all the subscription data will be removed
from that board! Then you can restore the Database on the board from the DECT
Manager Database.
To start-up the DECT Manager for the first time on a specific DECT System, execute the
following procedure:
1. Make sure that you have configured your Connection Manager for the DECT System
that you want to manage.
4. Check that you are in screen. DECT Manager DAS Install Wizard Step 1 If so, click
button Next. If you are not in this screen, then you are in DECT Manager DAS Install
Wizard Step 2. Continue with the next step in this procedure.
6. Now you are in screen. DECT Manager DAS Install Wizard Step 3 Name of DAS.
Enter a Unique name for the DECT System. This can be any given name. Click Next.
7. Now you are in screen. DECT Manager DAS Install Wizard Step 4 Login.
The DECT Manager tries to establish a connection to the DECT System. It may show
the connection status in a special Connection Status information Window.
8. If the connection is established, it will retrieve information (PARI, type of system etc.)
from the DECT System. You are now in the DECT Manager DAS Install Wizard Step
5. Fill in the PARI. If the PARI that you filled in matches with the PARI in the system,
you can continue. Click Next.
Here you must enter the License string for the handset license together with the
maximum number of handsets that can be subscribed. Besides that you can (if
applicable) enter the license string for the handsets used with Multi-site subscription.
The handset licence string and the maximum number of extensions/handsets are
related to the unique system identifier, the PARI (Primary Access Rights Identifier). The
licence information is written on a licence agreement that comes with the DECT
System.
Check that the PARI that is displayed, agrees with the PARI that you have on your
licence agreement. If not, you have the wrong licence agreement OR you have set-up a
connection to the wrong system.
Enter the Licence string. This string consists of 16 hexadecimal characters. The
characters have to be entered as lower case characters.
Enter the maximum number of extensions.
If you use handsets on more than one DECT system (Multi-site) using a SARI, then
enter the Multi-site handset licence string as well as the number of extensions that is
associated with it. The licence string consists of 32 hexadecimal characters (letters in
the string are always lower case). Note that the licence string for Multi-site subscription
If the licence information is valid, the button Next will be enabled. So, click Next.
10. Now the Dect Manager Das Install Wizard Step 8 is displayed.
This window is the same as the one that is available in the Options menu. Therefore
consult section 10.5 for more information on this. If you want to use the defaults, click
Next to continue.
Note: If you start-up the DECT Manager for that DECT System, and there are no
extension numbers visible in the Subscriptions tab you have to enter them via
the Configuration tab. Continue with chapter 9, CONFIGURATION
MANAGEMENT.
To start-up the DECT Manager for DECT System that has been accessed before via the
DECT Manager, execute the following procedure:
3. The DECT Manager will start-up with the local Database. Generally, it will not set-up a
connection to the DECT System.
The DECT Manager will only (automatically) set-up a connection when it is required to
exchange data between the DECT System and the DECT Manager.
Note: In this stage, you must make sure that nobody else has made changes in the
System via another DECT Manager. If you are not sure, you must make a
backup of all DECT Boards in the System ! Use the menu option Backup in the
Boards menu.
4. Now you can make changes locally. If necessary, the DECT Manager will automatically
set-up a connection to the System, to implement your changes on subscription data.
5. If you need any help, consult the Help feature in the DECT Manager. It contains Help
information to lead you through the actions that you want to do.
6. The Advance button is described in the following subsection. If you dont need the
functions under this button, continue with section 5.5
When you are in the Select DECT System window, the Advanced button is available.
When you click this button, you are in the following screen.
Export
This button allows you to export the entire database of a DECT System from your
DECT Manager database. You can select the drive/directory where you want to move
the database to. Note that this is a move function. After an export, the database of
that DECT System is no longer in the DECT Manager, and therefore you do not see this
DECT System anymore in the Select DECT System window. (The moved database is
an MS Access database.)
Note that when you want to import this database back into the DECT Manager, you
need to enter the PARI. If you put the database on floppy, also write down the PARI on
the floppy.
Copy Comments
This function allows you to copy the comment field information of one DECT System
database to another DECT System database. The comment info is the information
that you see in the DECT Manager Windows in the column comment.
Note that this function is enabled only when you have more than one DECT System in
the List of available DECT Systems in the Export/Import field.
When you have started-up the DECT Manager, you will see the following screen layout:
Buttons, depending on
selected Tab
Primary
Licence information access rights key
Information Screen (depending
on selected Tab
Screen filters
PC Date
Operational Status and Time
The Connect (Disconnect) button in the tool bar is a general item and needs explanation:
The Connect button is used to establish a connection manually and keeping this
connection open.
After clicking the Connect button, this button changes to Disconnect. The
Disconnect button means that the DECT Manager opens a connection automatically
when it needs a connection for subscription handling. It automatically disconnects when
it does not need a connection anymore.
So, basically, this button allows you to toggle between manual (permanent) connection
set up and automatic connection set up.
Under normal circumstances, the DECT Manager sets up and breaks down a
connection automatically when a connection to the system is required (e.g. for
Subscription handling).
Other functions (e.g. Radio Status change, Clear board) require a manual connection
set-up. So, for these functions you must use this Connect button to establish a
permanent connection.
However, for Subscription handling you can use this button to ensure a continuous
connection. When the connection is established manually, the button changes into a
Disconnect button. When the connection is established automatically, the button does
not change into Disconnect because it does not reflect the status of the connection.
The actual status of the connection is displayed in the left bottom corner of the screen.
6.1. GENERAL
Before a handset can be used, it must be subscribed (registered) to the system. That
means that a relation must be defined between the DECT System and the handset.
Subscription
Handset
DECT
System
During subscription, information about the handset is stored in the DECT System and
information about the DECT System is stored in the handset. So, at both sides (handset
and System), subscription information is stored.
For the subscription procedure the DECT Manager must be used, where you can select an
extension number for a handset. Then you enable the Subscription Procedure and the
DECT Manager generates a code (PIN code or Authentication Code). This code must be
entered in the handset within a certain time period. If the operation has been completed
successfully, the handset is subscribed to the system and is allowed to make and receive
calls.
A handset can be subscribed to more than one DECT System. Therefore, it can be used in
areas covered by different DECT Systems or in different areas with their own DECT
System. For example, this allows you to use the same handset for the DECT System,
which is operational in your company and also for your home DECT. Also if the company is
located at different sites, it is possible to use the same handset at the different sites, if
DECT Systems are present on these sites. It has a different extension number for each
DECT System. It cannot roam from one of these areas to the other, while busy with a
conversation.
The user of the handset must ensure that his set is communicating with the required DECT
System, when making calls in a certain area. This may be done manually by a selection
key, depending on the type of the handset. There are also handsets, which select a DECT
System automatically
Multi-site Mobility allows a user to roam from one DECT system (site) to another. It does
not support handover when the user is in a conversation!
Only if the DECT systems (sites) support Multi-site mobility with External handover (as
additional feature) and use a SARI (Secondary Access Rights Identifier), handover is
supported between the sites but it is not seamless handover.
Multi-site Mobility requires that the handset is subscribed to all DECT systems that are
involved in the Multi-site Mobility.
There are two ways for using a handset on more than one system:
- Subscribe the handset to all DECT systems individually. In that case you must go to
each individual system and execute the subscription procedure for the handset. The
handset carriers as many subscription records as the number of systems to which it is
subscribed. Each subscription for this handset requires a handset licence in the each
system.
The PARI is a unique identifier belonging to one DECT system only. The SARI is an
identifier used in more than one DECT system. The DECT system transmits both PARI
and SARI as identification signals.
If the handset detects a DECT signal in the air, it checks whether the PARI in that signal
matches with its own PARI data in the subscription record. If so, the handset "locks"
(listens) to that signal. If not, the handset does a second check but now on the received
SARI. If that matches, the PP "locks" (listens) to that signal.
For using a SARI, you must subscribe your handset to one system using the Multi-site
Subscription function. Then you must copy the subscription record to other systems, all
having the same SARI. You don't need to subscribe that handset anymore to the other
systems.
Figure 7. Three DECT systems using SARI gives an example of three different DECT
systems (three different PARIs) and one SARI. In this example the handset is
subscribed to the SARI of system X. This SARI is not unique because the other
systems have the same SARI. Therefore the subscription record can be copied from
DECT System X to the other DECT Systems. (The DECT Manager allows you to copy
the subscription record from one DECT System to another.) When the handset receives
radio signals from system Y or system Z, it first checks the PARI of that system and if
that doesn't match with its Access Rights Identifier (ARI - also referred to as PARK) it
will do a check for the SARI of that system. The SARI matches with the ARI in the
handset. Then the handset does a check if the subscription data in the system matches
with its stored subscription data. This matches because the subscription data was
copied from the system to which the original subscription was made. So, the handset
can also be used on systems Y and Z.
DECT System Z
PARI = 10009E35
RFP
SARI = 1000900A
Available: The extension number is not in use. It is available for a new subscription.
Busy: A new subscription request was started at the DECT Manager but is not yet
sent to the DECT System or confirmed by the DECT System. Only when the
DECT Manager gets a confirmation back from the DECT Manager, the
status changes from Busy to Enabled.
Enabled: The subscription process is started in the DECT System. A pin code is
displayed. This pin code (sometimes referred to as Authentication Code)
must be entered at the handset that is going to be subscribed. The System
is waiting for a subscription from the handset for a maximum of 16 minutes.
If the system does not receive a subscription confirmation from a handset
within 16 minutes, the Enable status is withdrawn and the extension
number goes back to the status Available
Subscribed: Extension is known to the System and can be used for calls.
Black listed: The DECT Manager user has disabled an extension that had the status:
Subscribed. After clicking on Disable the status changes from
Subscribed to Black Listed. Depending on the software in the System,
one of the following things will happen:
Note: If you dont see extension numbers in your screen, they are most likely not entered
via the Configuration Tab. Also check the filter options in the bottom left of the
screen.
Note: There are small differences between the window that is displayed for DCMIP
interface and SNMP interface. However, there are no functional differences.
Add Comment
Enable multi-site
subscription: handset
will be subscribed to
the SARI Disable
Subscription
Enable Subscription: handset
will be subscribed to the PARI
The function of the Enable and the Enable Multi-site option is as follows:
Disable: Removes the Subscription data from the handset as well as from the DECT
System, so from both sides. The handset must be within reach of the radio
signals and must be switched on. In some system types you also need to go
off-hook with the handset or call the handset to activate the de-subscription
process.
If the Disable cannot be performed at the handset side, a Remove
(subscription data is removed form the System and not from the handset) can
be performed automatically after a specified time period (see chapter 9).
Remove: Subscription data is removed from the System only and NOT from the
handset. That must be done manually, if possible on the handset !
1. Make sure that the extension number of the handset is assigned via the Configuration
Tab.
2. Make sure that you have the User Guide of the handset, to see how the Subscription
procedure must be executed at the handset side.
3. Go to the Help Menu option and select the help information on how to Subscribe an
extension. (If you want to subscribe more than one extension in one go, you can select
multiple extensions).
You can start the Subscription for a range of extension numbers. (This is done
according to the normal Windows method using the <Shift> key.) However, for practical
reasons, do not start the Subscription process for more than 10 extensions at the time.
If you try to enable subscription for more than 10 extensions at the time you will get the
following popup message:
2. Select an extension number and click on Disable. Now the subscription data is
automatically removed from the DECT Manager, the DECT system and the handset.
The Subscription states must go via black-listed to available.
If you disabled a handset with Multi-site subscription on one DECT system, you must
remove the subscription record(s) from other DECT systems as well, but with the
Remove button. Disable does not work on the other systems for the Multi-site handset
anymore, because there is no subscription record in the handset anymore.
Note: If the Disable procedure is successful, the subscription data is removed from the
handset as well as from the DECT System. If the handset is not available anymore
because it is broken or lost, you could remove subscription data from the DECT
System only by means of the Remove option in the Subscriptions menu. You
should use this option only if everything else failed, because it does not remove
subscription data from the handset.
You can start the De-subscription for a range of extension numbers. (This is done
according to the normal Windows method using the <Shift> key.)
If you do this, the system asks for a confirmation by means of the following popup
screen:
7.1. SCREEN
When you select the Boards tab you will see the Boards screen.
Note: There are small differences between the window that is displayed for V-
modem/DCMIP interface and TCP/IP interface. However, there are no functional
differences.
Address
This is the board address in the system. The address range for TCP/IP interface is as
follows:
First BackBone Section: 18
Second BackBone Section: 9 16
Third BackBone Section: 17 24
Fourth BackBone Section: 25 32
Operational
Board operational Yes/No
Users
Total Number of extensions on the board that has the status: Enabled, Subscribed, or
Black listed.
Comment
Here you can add comment information. If the comment field is empty for the Relay
board, then the DECT Manager enters automatically the text: Relay board.
The relay board is the board to which the DECT Manager is connected.
If you have entered text manually and the board is the relay board, then the DECT
Manager does not enter Relay board. However, the DECT Manager highlights the
comment line of the Relay board as an indication that this is the relay board.
Backup button
This button allows you to make a backup of the configuration and subscription data of
the board. The backup is stored in the Database in your DECT Manager. Normally the
DECT Manager takes care that the data in the board remains consistent with the data in
the DECT Manager. However if you are not sure that the data in the Database in your
system is not up to date anymore, you must make a backup. (See chapter 5.3,
DATABASE STRUCTURES for an explanation of the Database mechanism)
Note: Comment information is not stored in the DECT System. So, the comment
information does not change when you execute a Backup.
Restore button
This button restores configuration and subscription data from the Database in your
DECT Manager. If you need to replace a board, then you need to restore the
subscription data to the board, otherwise the handsets subscribed to the previous board,
need to be subscribed again.
Note: Make sure that the connection to the System is open before executing the
Restore, and make sure that there are no subscription actions in progress on the
selected board (all extensions in subscription status Available or Subscribed).
The menu options are self explaining except for the option: Clear Board. This option is
displayed if the connection is established with the DECT System. If the connection is not
established, the option Clear Board is NOT displayed!!
Caution: The Clear Board REMOVES ALL subscription data from the board.
- Subscription data on the board is corrupt and a Restore does not solve the problem.
- A board has been received from the repair store and still contains subscription data from
a previous life. In this case, first try to do a Restore. If the board remains faulty, then
execute a Clear board and try to do a Restore again.
Note that the Clear Board option does not remove the subscription data from the
DataBase in the DECT Manager. If you execute a Backup for a board that has been
cleared, the subscription information is removed from the DECT Manager DataBase as
well.
8.1. SCREEN
When you select the Radios tab, the following screen is displayed when you are
connected to a DECT System with V-modem/DCMIP interface protocol.
Radio Id
This is the Radio address in the System. Consult Appendix A for addressing structures.
If, the option Convert to Ids in the menu is switched off, then you see a radio
numbering from 1 4 per DCC4 board and 1 8 per DCC8 board.
Installed
This is a software indication, whether the Radio is expected to be installed or not. It
doesnt say anything about the actual status of the Radio. If you change the setting from
Installed to Not Installed, the Radio will stay operational !
Note, that in case of a DCC-8, the power to the RFP is switched off when set to Not
Installed. So, that means that the RFP will go down if it is not locally powered!
However, if set to Installed and the Radio is not operational an alarm will be generated in
the DECT System: RFP Malfunctioning.
Not Installed
This is a software indication, whether the Radio is expected to be Not Installed. It doesnt
say anything about the actual status of the Radio. If you change the setting from
Installed to Not Installed, the Radio will stay operational !
9.1. GENERAL
The Configuration Management screen is used to enter extension numbers. This means
that, before you can subscribe an extension, it must have been entered in the configuration
screen.
Each extension that you enter in this screen must be an extension number that is known in
the PABX (host system) as well. So make sure that the extension numbers that you enter
here match with the extension numbers (range) that have been defined in the PABX (host
system).
Note, that the DECT Manager detects automatically whether your DECT System is a
concentrated or an un-concentrated version. The DECT Manager displays the screen that
is appropriate for the DECT System type.
Note: The board address ranges which are displayed in the configuration screen, are
different for the two system (protocol) types: V-modem/DCMIP protocol and TCP/IP
protocol.
When you select the Configuration tab you will see the Configuration screen.
Note: There are small differences between the window that is displayed for V-
modem/DCMIP interface and TCP/IP interface. However, there are no functional
differences.
Select Board
Fill Down
When you need to enter a sequence of extension numbers, you can use the Fill Down
menu option. This allows you to fill down a range of extensions.
To use Fill down, do the following:
- Double click the most down extension number in the list of numbers.
- The button Fill Down must be enabled now. Click this button. And automatically the
list is filled down.
Delete Extensions
You can easily delete an extension by selecting the extension number and then press
the <Delete> button.
The column of extensions may have gaps between the extension numbers. However, it
is advised to keep the extension numbers as one column without gaps. It is also
advised to start from the top of a column.
These two advises are important to decrease the Backup time when you do a
Backup.
When you select the Configuration tab you will see the Configuration screen.
Note: There are small differences between the window that is displayed for V-
modem/DCMIP interface and TCP/IP interface. However, there are no functional
differences.
Select Board
Fill Down
When you need to enter a sequence of extension numbers, you can use the Fill Down
menu option. This allows you to fill down a range of extensions.
To use Fill down, do the following:
- The button Fill Down must be enabled now. Click this button. And automatically the
list is filled down.
Delete Extensions
You can easily delete an extension by selecting the extension number and then press
the <Delete> button.
The column of extensions may have gaps between the extension numbers. However, it
is advised to keep the extension numbers as one column without gaps. It is also
advised to start from the top of a column.
These two advises are important to decrease the Backup time when you do a
Backup.
10.1. GENERAL
The DECT Manager allows you to change options. There are four main categories:
- General
- Logging
- Demo Mode
- Board Addresses
2. Now you are in the options screen and you can select four different tabs.
Maximum XXX connections at the same time (only visible with V-modem protocol)
This is the maximum number of DECT Systems that can have a connection to the
DECT Manager at the same time. The limit for this number is the number of available
COM ports. This parameter sets a limit on the number of COM ports that can be used
at the same time for DECT Management. This can be useful if the COM port(s) may
also be required for other applications.
Note that if you change a timer setting, it will only be activated after the previous timer
setting has expired!
License String
There are two types of licences that can be entered:
Handset Licence
This is the licence string that is used for the maximum number of handsets (users)
on the DECT System. The licence string consists of 16 hexadecimal digits. The
characters must be entered as lower case characters.
The licence string is related to the PARI (Primary Access Rights Identifier) and the
maximum number of users (handsets).
After you have entered the handset licence, click the Set Licence button to activate
it.
Set License
Click on the Set License button after entering the licence string and the maximum
number of users.
Note: Depending on the version of the DECT Manager, one or more options might have
been left out of this screen.
If one or more of these options are turned on, the DECTTrace.dfl file is
generated with logging information. This file is stored in the following directory:
C:\Program Files\Philips\diagnostics\dect-management\DECTTrace.dfl
Note that if you turn on one of these options, records will be written to the
DECTTrace.dfl file. This file is a cyclic file and the size is limited to 10 Mb. So, make
sure that you have sufficient hard disk space.
WARNING: If you turn configuration licensed off, it will disable the options menu. This
means that you cannot make any changes anymore in the Options menu
when in Demonstration mode.
The Board Addresses tab allows you to adapt the board addresses that are displayed in
the User Interface of the DECT Manager.
Default, the Board Addresses for a DECT System with a V-modem interface are the
following ranges:
Default, the Board Addresses for a DECT System with a TCP/IP interface are the following
ranges:
However, these addresses are defined by the internal DECT System configuration. If you
want to use your own addressing structure, then you can convert these DECT System
addresses into address range(s) that you want. This Board Addresses tab allows you to
create a conversion table, to convert the internal addresses into physical addresses of your
choice.
The address conversion is used only in the DECT Manager User Interface. It is not
uploaded to the DECT System.
Manually
Enter the conversions in table that is displayed. Then click OK.
By means of a file.
You can prepare a file with a conversion table. This file must be have the file extension
.brd. Use the Load button to start loading the file. See the description of the load
button in this section.
Here you can enter information to set up a table that translates the alternative board
addresses/numbers into conventional ISPBX addresses.
Load
The Load button allows you to load the conversion table from a predefined file
(*.brd) into the Database of the DECT Manager. If you click the Load button, you
can select a file, from which you want to load address conversion data.
Appendix D gives a description of the file contents.
Save
Click the Save button to save the information to disk. The *.brd is the default file
extension.
Default
If you click the Default button, the adddress conversion will be one-to-one, which
means that the software addresses are exactly the same as the physical addresses.
Note: Copy & Move Subscription is only available for TCP/IP systems!!!
Pre-subscribe
The Pre-subscribe function allows you to make subscriptions on a host DECT System,
and then export the subscription data together with the subscribed handsets to the
destination DECT System.
The subscription data is exported in a file and can be imported into the DCC in the
destination DECT System (by means of the DECT Manager).
When imported, you can use the previously subscribed handsets on the destination
DECT System without executing a subscription procedure.
This can be useful when the customer wants to have extra handsets on its DECT
System, but you cannot go to the customer to subscribe the handsets. You can
subscribe them locally (on your own system) and send the subscribed handsets to the
customer. You can send the file with subscription data to the customer or import that
file into the DECT System via a remote connection.
The pre-subscription procedure is based on the PARI of the destination system, and is
therefore regarded as a single site subscription. Note that the latest version of the
DECT Manager under Management@Net allows you to execute a pre-subscription
based on a SARI for multi-site subscription.
Import Subscription
This function allows you to import subscription data from a file (generated by means of
Pre-subscribe or Move subscription outside the system) into an iSMobile system.
Note, that when you import a subscription, you must assign a DNR (BSP-ID) in the
ISPBX for that subscription as well!!
You will find the Copy and Move Subscription facility under the File menu.
Pre-subscription
Portables that must be subscribed, must be within reach of the radio signals of the
host.
Host system systems remains fully operational during the pre-subscription process.
The result is a file (e.g. on memory stick) with a subscription data file (type *.xml)
and a set of subscribed portables. Subscription data can be imported by means of
the Import Subscription function.
No extra handset licenses required in the Host DECT Manager
No extra extension numbers required in the host DECT System.
A pre-subscription can be done for a PARI.
The PARI of the Host System differs from the PARI in the Destination System.
You must enter the PARI of the Destination system in the DECT Manager when
it asks for it.
A pre-subscription can be done for a SARI.
You must enter the SARI of the Destination systems in the DECT Manager when
it asks for it.
Import Subscription
When importing, you can change the board number, so that you can import the
subscription data into any DCC in the system.
Note: There are two different types of Performance Managers. One for the V-modem
protocol based systems, and a newer one for the TCP/IP protocol based systems.
This chapter deals with the Performance Manager for the TCP/IP protocol based
systems. The Performance Manager for the V-modem protocol based systems is not
described here.
12.1. GENERAL
The Performance Manager allows you to analyse your system performance in detail. The
Performance manager itself does not get data from the DECT System. It uses .xml files as
input. These .xml files must be retrieved from the DECT System by means of the
Performance Data Retrieval tool. So, there are two programs involved in the managing the
performance data:
The programs are easy to use and intuitive. However you need to know a few hints and tips
to avoid pitfalls. The following sections give you these hints and tips.
The Performance Data Retrieval tool is just a shell to make changes in the Task Scheduler
in Windows. The task that is performed at regular intervals (e.g. 15 minutes), is getting
performance data from the DECT System.
The scheduler task does not open a connection to the DECT System automatically. So,
make sure that you have an active (open) TCP/IP connection to the DECT System (via
Dial-Up Adapter in Windows). If you are using an Ethernet connection, make sure that
the connection is open and stable.
When the Scheduler is active to a certain DECT System, it is advised not to use the
DECT Manager for that specific DECT System. If you need to use the DECT Manager
anyhow on that system, pause the Scheduler via the Scheduler icon in the Windows
Tray (generally at the right-bottom corner).
The Start time which you fill in, in the Performance Data Retrieval tool must be a later
time than the actual PC time (on the same date).
Trends
Shows the average values for all time slices.
E.g. average channel occupation over the time slices
Imported items:
Licensed via the Licence Manager. So, make sure that you have a dongle and a license
file.
2. Fill the Database with retrieved data. Use Menu option File and then Import. It is
advised to import all .xml files from the <DAS name> directory.
3. Now you can use the Performance Manager to generate reports, graphs etc. You
can export the results to commonly used formats for MS Excel, MS Word etc.
Each module: the Connection Manager, the Licence Manager and the DECT Manager
provide diagnostic information. Also overall (SysManager) diagnostic in formation is
generated. Each module stores its diagnostic information in a set of four files:
dfSetup.dfl
In the file dfSetup.dfl the information about the installation of the modules is logged.
dfEvent.dfl
In the file dfEvent.dfl you find information about each attempt to set-up a
connection and each disconnection. The information contains the time and the date, the
application name, client and server name and a comment if applicable. Commas
separate the information.
Note: If an error occurs during the attempt to set-up a connection, it is logged in the
subsequent disconnect event.
dfExcept.dfl
In the file dfExcept.dfl all the failures in the hardware, software and connections are
logged. The information contains the time and the date, the application- and client
name if available, the server name and a comment on the failure.
dfConfig.dfl
In the file dfConfig.dfl you find information about the version of the application and the
loaded DLLs. Whenever the log-button in the about-box of an application is pressed,
information is stored in this file.
The files have a fixed length: if the last line in the file is written, the first one will be
overwritten next. You can always recognise the last line that is written in the file, by the line
with the plus signs (+++++++++) under it.
The files as mentioned in section 10.1 are stored in separate subdirectories for the various
modules (Connection Manager, Licence Manager, DECT Manager and Sysmananger)
C:\Philips\Data Files\diagnostics\Common
\Connection-Manager
\dect-management
\performance-manager
\licence-manager
\login-module
Beside the files mentioned in the previous sections, the DECT Manager is able to generate
Third Line information. This information is stored in the file:
DECTTrace.dfl
This file contains third line information. So, it should be send to the third line maintenance
centre on request. It is created in the DECT Manager diagnostics directory (see section
13.2)
This file is generated if you have enabled one or more of the options in the Logging Tab
in the Options menu (in the View menu). (See section 10.3.)
A.1. GENERAL
- Radio Id.
This number is unique for each RFP in the system. It is related to the DCC card position
and the RFP connection on the DCC. It appears in the following cases:
Radio Id.
DCC DCC DCC DCC
Shelf Address
01 09 11 19
Shelf address consists of : 03 0B 13 1B
Shelf address (S) is 0 ...3 05 0D 15 1D
07 0F 17 1F
Board address
Board address.
Used in DECT Board Address 00 01 02 03 04 05 06 07
Manager Board Address 00 01 02 03
(In case of a DCC-8 you will see eight Radio Ids per board.)
01 02 03 04 Position
00 01 Unit Group
00 01 DCC Addr.
RFP ids
11 P
S.G. 13 S
Shelf 2 0920 15 U
(SSW805) 17
or
S.G.
6204
(SSW810)
01 02 03 04 Position
02 Unit Group
02 DCC Addr.
01 09 11 19 21
IS3030 S.G. 03 0B 13 1B 23
0920 05 0D 15 1D 25
(SSW805)
07 0F 17 1F 27
or P
Shelf 1 S.G. S
6204 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 Position
00 01 02 03 04 Unit Group
00 01 02 03 04 DCC Addr.
29 31 39
S.G. 2B 33 3B
0920 2D 35 3D
(SSW805)
2F 37 3F
or
Shelf 2 S.G.
6204
(SSW810)
01 02 03 04 05 06 07 08 09 Position
05 06 07 Unit Group
05 06 07 DCC Addr.
IS3050 / 01 09 11 19 21 29 31 39
iS3070 / S.G.
iS3090 0920 03 0B 13 1B 23 2B 33 3B
(SSW805) 05 0D 15 1D 25 2D 35 3D
or 07 0F 17 1F 27 2F 37 3F
BACKBONE P
SECTION S.G.
6204 S
0 U
(SSW810) RFP ids
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
00 01 02 03 04 05 06 07 DCC Addr.
41 49 51 59 61 69 71 79
S.G.
0921 43 4B 53 5B 63 6B 73 7B
(SSW805) 45 4D 55 5D 65 6D 75 7D
or 47 4F 57 5F 67 6F 77 7F
BACKBONE P
SECTION S.G.
6205 S
1 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
16 17 18 19 20 21 22 23 DCC Addr.
81 89 91 99 A1 A9 B1 B9
S.G.
83 8B 93 9B A3 AB B3 BB
0922
(SSW805) 85 8D 95 9D A5 AD B5 BD
or 87 8F 97 9F A7 AF B7 BF
BACKBONE P
S.G.
SECTION S
2 6206
(SSW810) U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
32 33 34 35 36 37 38 39 DCC Addr.
C1 C9 D1 D9 E1 E9 F1 F9
S.G.
0923 C3 CB D3 DB E3 EB F3 FB
(SSW805) C5 CD D5 DD E5 ED F5 FD
or C7 CF D7 DF E7 EF F7 FF
BACKBONE P
S.G.
SECTION S
6207
3 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
48 49 50 51 52 53 54 55 DCC Addr.
01 09 P
- Possible DCC positions
- Signalling Groups (S.G.) For DCCs iS3010 S.G. 03 0B S
- DCC Addresses (for reference in DECT Manager) 0920 05 0D U
- RFP ids (as can be displayed on handset) (SSW805) 07 0F
or
S.G.
Shelf 1
6204
(SSW810)
01 02 03 04 Position
00 01 Unit Group
1 2 DCC Addr.
RFP ids
11 P
S.G. 13 S
Shelf 2 0920 15 U
(SSW805) 17
or
S.G.
6204
(SSW810)
01 02 03 04 Position
02 Unit Group
3 DCC Addr.
01 09 11 19 21
IS3030 S.G. 03 0B 13 1B 23
0920 05 0D 15 1D 25
(SSW805)
07 0F 17 1F 27
or P
Shelf 1 S.G. S
6204 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 Position
00 01 02 03 04 Unit Group
1 2 3 4 5 DCC Addr.
29 31 39
S.G. 2B 33 3B
0920 2D 35 3D
(SSW805)
2F 37 3F
or
Shelf 2 S.G.
6204
(SSW810)
01 02 03 04 05 06 07 08 09 Position
05 06 07 Unit Group
6 7 8 DCC Addr.
IS3050 / 01 09 11 19 21 29 31 39
iS3070 / S.G.
iS3090 0920 03 0B 13 1B 23 2B 33 3B
(SSW805) 05 0D 15 1D 25 2D 35 3D
or 07 0F 17 1F 27 2F 37 3F
BACKBONE P
S.G.
SECTION S
0 6204
(SSW810) RFP ids U
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
1 2 3 4 5 6 7 8 DCC Addr.
41 49 51 59 61 69 71 79
S.G.
0921 43 4B 53 5B 63 6B 73 7B
(SSW805) 45 4D 55 5D 65 6D 75 7D
or 47 4F 57 5F 67 6F 77 7F
BACKBONE P
SECTION S.G.
6205 S
1 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
9 10 11 12 13 14 15 16 DCC Addr.
81 89 91 99 A1 A9 B1 B9
S.G.
83 8B 93 9B A3 AB B3 BB
0922
(SSW805) 85 8D 95 9D A5 AD B5 BD
or 87 8F 97 9F A7 AF B7 BF
BACKBONE P
S.G.
SECTION S
6206
2 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
17 18 19 20 21 22 23 24 DCC Addr.
C1 C9 D1 D9 E1 E9 F1 F9
S.G.
0923 C3 CB D3 DB E3 EB F3 FB
(SSW805) C5 CD D5 DD E5 ED F5 FD
or C7 CF D7 DF E7 EF F7 FF
BACKBONE P
S.G.
SECTION S
6207
3 U
(SSW810)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
25 26 27 28 29 30 31 32 DCC Addr.
01 09 P
- Possible DCC positions
- Signalling Groups (S.G.) For DCCs iS3010 S.G. 03 0B S
- DCC Addresses (for reference in DECT Manager) 0920 05 0D U
- RFP ids (as can be displayed on handset) (SSW805) 07 0F
or
00 08
S.G.
Shelf 1 02 0A
6204
(SSW810) 04 0C
06 0E
01 02 03 04 Position
00 01 Unit Group
1 2 DCC Addr.
11 P
S.G. 13 S
0920 15 U
(SSW805) 17
or
10
S.G.
Shelf 2 12
6204
(SSW810) 14
RFP ids 16
01 02 03 04 Position
02 Unit Group
3 DCC Addr.
01 09 11 19 21
IS3030 S.G. 03 0B 13 1B 23
0920 05 0D 15 1D 25
(SSW805)
07 0F 17 1F 27
or P
S.G. 00 08 10 18 20
Shelf 1 S
6204 02 0A 12 1A 22 U
(SSW810) 04 0C 14 1C 24
06 0E 16 1E 26
01 02 03 04 05 06 07 08 09 10 Position
00 01 02 03 04 Unit Group
1 2 3 4 5 DCC Addr.
29 31 39
S.G. 2B 33 3B
0920 2D 35 3D
(SSW805)
2F 37 3F
or
S.G. 28 30 38
Shelf 2
6204 2A 32 3A
(SSW810) 2C 34 3C
2E 36 3E
01 02 03 04 05 06 07 08 09 Position
05 06 07 Unit Group
6 7 8 DCC Addr.
Figure 13. Addressing in the iS3010 / iS3030 Systems with DCC-8 / DCC-8(R).
01 09 11 19 21 29 31 39
S.G.
0920 03 0B 13 1B 23 2B 33 3B
(SSW805) 05 0D 15 1D 25 2D 35 3D
or 07 0F 17 1F 27 2F 37 3F
BACKBONE P
SECTION S.G. 00 08 10 18 20 28 30 38
6204 S
02 0A 12 1A 22 2A 32 3A U
(SSW810)
04 0C 14 1C 24 2C 34 3C
06 0E 16 1E 26 2E 36 3E
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
0 1 2 3 4 5 6 7 8 DCC Addr.
41 49 51 59 61 69 71 79
S.G.
0921 43 4B 53 5B 63 6B 73 7B
(SSW805) 45 4D 55 5D 65 6D 75 7D
or 47 4F 57 5F 67 6F 77 7F
BACKBONE P
SECTION S.G. 40 48 50 58 60 68 70 78
6205 S
42 4A 52 5A 62 6A 72 7A U
(SSW810)
44 4C 54 5C 64 6C 74 7C
46 4E 56 5E 66 6E 76 7E
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
1 9 10 11 12 13 14 15 16 DCC Addr.
81 89 91 99 A1 A9 B1 B9
S.G.
0922 83 8B 93 9B A3 AB B3 BB
(SSW805) 85 8D 95 9D A5 AD B5 BD
or 87 8F 97 9F A7 AF B7 BF
BACKBONE P
SECTION S.G. 80 88 90 98 A0 A8 B0 B8
6206 S
82 8A 92 9A A2 AA B2 BA U
(SSW810)
84 8C 94 9C A4 AC B4 BC
86 8E 96 9E A6 AE B6 BE
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
2 17 18 19 20 21 22 23 24 DCC Addr.
C1 C9 D1 D9 E1 E9 F1 F9
S.G.
0923 C3 CB D3 DB E3 EB F3 FB
(SSW805) C5 CD D5 DD E5 ED F5 FD
or C7 CF D7 DF E7 EF F7 FF
BACKBONE P
SECTION S.G. C0 C8 D0 D8 E0 E8 F0 F8
6207 S
C2 CA D2 DA E2 EA F2 FA U
(SSW810)
C4 CC D4 DC E4 EC F4 FC
C6 CE D6 DE E6 EE F6 FE
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 Position
00 01 02 03 04 05 06 07 Unit Group
3 25 26 27 28 29 30 31 32 DCC Addr.
Figure 14. Addressing in the iS3050 / iS3070 Systems with DCC-8 / DCC-8(R).
B.1. GENERAL
The DCC-8 / DCC-8(R) and the 24-DCC/32-DCC with firmware F43240.xxx supports
TCP/IP protocol over V.24 instead of the V-modem protocol used in the previous firmware
packages.
This means that the Connection Set-up in the Connection Manager must be adapted to the
new protocol environment for the DECT Manager.
Also in the Windows environment, adaptations must be made to make the protocol running
over V.24 or, in case of the DCC-8 or DCC-8(R), over Ethernet.
On top of the TCP/IP protocol stack, SNMP (Simple Network Message Protocol) or DCMIP
(DECT Cluster Management Interface Protocol) is used, depending on the type of DCC
board.
The following sections in this document describe how to set-up a TCP/IP connection over
V.24.
To set the IP address in the DCC, consult Chapter 6 in the Customer Engineer Manual
for Business Mobility DECT systems, either for DCC-4 or DCC-8 / DCC-8(R).
The connection via Ethernet is a straightforward connection. Make sure that the IP
addresses at both sides are part of the same subnet.
TCP/IP
Ethernet (LAN)
The direct V.24 connection between the 24-DCC (firmware F43240.xxx), 32-DCC (firmware
F43240.xxx) or DCC-8 / DCC-8(R) and the DECT Manager PC uses TCP/IP. The
configuration and the protocol stack are depicted in the following figure.
DECT Manager PC
DCC-8
Protocol (SMPC Rel. 5.0 or Management@Net)
DCC-8(R)
Or 24-DCC / 32- Stack
DCC with Dial-up Adaptor with TCP/IP configuration.
firmware (Phone numbers are ignored)
F43240 xxx SNMP
DCMIP
Null Modem Configuration in Windows
TCP/IP
PPP V.24 Com Port
To set up a Null modem configuration in the Windows environment, you need to set-up:
Note: Before you start-up the SMPC Configurator to set up a connection between the
DECT Manager and the DCC, you must establish a connection by means of the
Dial-up Adapter.
After closing down the DECT Manager, you must close down the connection that
you have made via the dial-up adapter.
The modem connection between the 24-DCC (firmware F43240.xxx), 32-DCC (firmware
F43240.xxx) or DCC-8 / DCC-8(R) and the DECT Manager PC uses TCP/IP. The
configuration and the protocol stack are depicted in the following figure.
DECT Manager PC
DCC-8
(SMPC Rel. 5.0 or Management@Net)
dcc-8(R) Protocol
Stack
Or
Dial-up Adaptor with TCP/IP configuration.
24-DCC / 32- SNMP
DCC with or
firmware
DCMIP Modem Configuration in Windows with
F43240.xxx TCP/IP Modem Driver for your Modem.
To set up a Null modem configuration in the Windows environment, you need to set-up:
Modem Configuration.
You must assign your modem in the Windows Control Panel. As modem driver you
must use the modem driver file that you get with the modem.
Dial-up Adapter.
You will find this adapter in the icon My Computer.
To set up the Dial-up Adapter, consult section B.4.2 Windows NT or section B.5.2 for
Windows 2000 or section SETTING UP A DIRECT V.24 PPP CONNECTION:
WINDOWS XP PROF..
Retrieving performance data is different compared to the previous firmware versions of the
DCCs. There are two ways to retrieve two different types types of performance data:
For instructions, how to retrieve the data, consult section C.1 USE TELNET
SESSION UNDER WINDOWS NT and C.2 USE TELNET SESSION UNDER
WINDOWS 2000 in this manual.
For instructions, how to retrieve the data, consult the next release of this document,
probably available on NSO net, under FAQs.
Note: From technical point of view, it is possible to get files from the DCCs via an FTP
(File Transfer Protocol) session that you have set-up manually. However, doing this,
you inhibit the DECT Manager from accessing the DCC via FTP, because a DCC
can handle only one FTP client at the time. Therefore it is strongly recommended
that you do not set-up an FTP session manually.
Note: In case you are using a V.24 connection, be aware that you must establish a
connection via the dial-up adapter first, before starting-up the Telnet session or the
Performance Data Retrieval Tool. During the period that the Performance Data
Retrieval Tool is scheduled to retrieve data (at specified intervals), you must make
sure that there is a connection active (via Dial-up adapter) to retrieve the data. The
connection is NOT set-up automatically, neither closed down automatically.
After closing down the Telnet Session or when you dont need to retrieve data
anymore, you must also close down the connection that you have made via the dial-
up adapter.
Username: dasuser This is the fixed username. It is case sensitive, and must
be entered in lowercase.
Note: If you are connected to the LAN you dial out via a Proxy server, you need to have
extra information about the settings in the Proxy server. Your local IT Manager has
to supply the settings.
B.4.1. General
This chapter assumes that the DCC is already up and running and that the V.24 null
modem cabling is already installed.
Dial-up Networking
Dial-Up networking is used to connect to the DCC board. Windows NT needs a modem
installed in order to use Dial-Up Networking. Instead of two modems (the most common
way to set up a PPP link), we use a crossover cable called a null modem cable.
The trick is to use a driver installation file that installs the regular Windows NT modem
driver, but which also tells Windows not to use the regular AT commands for handshaking.
The driver installation file that accomplishes this is called DAS.inf.
Double click on the My Computer icon, the Control Panel icon, and then on the Modems
icon. If there are other modems already installed, they will be shown on the 'Modems
Now, it is important to check the box Dont detect my modem; I will select it from a list.,
because automatically scanning for a null-modem will never work (since it wont respond to
any of the normal AT commands). Having done this, click on the Next button.
To continue, you must have the file DAS.inf on a floppy (make sure that it ends on .INF,
because otherwise the installation program will not recognise it as a driver installation file),
insert the floppy, and click on the Have disk button. The Install From Disk window that
follows this should show A:\ in the Copy manufacturers files from: selection box. If this is
the case, click on the OK button. The following window should appear:
Choose the communications port that you connected the null modem cable to, and click on
the Next button. This will take a while (depending on the speed of your machine). The last
window in this sequence you can click away with the Finish button.
Double click on the Dial-Up Networking icon in the My Computer window. If Dial-Up
Networking is not installed on your system, you must install it using the Windows NT
installation CD-ROM.
Note: If you use a real modem with remote connection, you should select your modem
instead of Null modem in the procedure. You also need to fill in the telephone
number in case of a remote connection.
If dial-up networking is not yet installed, NT asks you for the I386 driver directory on the
WinNT CD-ROM. Let Windows install the required files.
In the Window that appears, select the DAS Null Modem in the RAS Capabilities.
The 'Remote Access Set-up' window will be shown. Click the 'Continue' button to proceed.
Click Restart.
When the system is up again, double click the icon Dial-up Networking (in My computer)
Enter a City code. This can be any given digit. Click Close. (Note, that if you use a
modem with modem driver, then you must enter the correct city code.)
Now you will see a window that asks you to create a phone book.
Click OK. You will see the next window.
Click Next
In the Server window that is displayed, select I am calling the Internet. Click Next. Click
again Next and then click Finish.
On the 'Dial-Up Networking' window select the phonebook entry that you have created and
click the More button. On the popup menu that is shown, select the option 'Edit Entry and
Modem Properties'. The following window should appear:
From the list box select 'DAS Nullmodem Connection' and click the 'Configure' button.
Make sure the settings are exactly like the window shown here, so only TCP/IP. The DCC
boards do not support NetBEUI or IPX/SPX, if you select these, the PPP handshake will
fail.
The only thing you need to do here is to specify an IP address for the Windows NT side of
the PPP link. Now click on OK for all windows that are left open, and youre set up for
direct cable PPP.
B.5.1. General
This chapter assumes that the DCC is already up and running and that the V.24 null
modem cabling is already installed.
Dial-up Networking
Dial-Up networking is used to connect to the DCC board. Windows 2000 needs a modem
installed in order to use Dial-Up Networking. Instead of two modems (the most common
way to set up a PPP link), we use a crossover cable called a null modem cable.
The driver for a null modem connection is already available in Windows 2000 as the
Connection between two computers option.
Double click on the My Computer icon, the Control Panel icon, and then on the Phone
and Modems icon. Click on the Modems tab. If there are other modems already installed,
they will be shown on the 'Modems Properties' window.
Click Finish.
Click Next.
Click on Configure.
Check the settings. Do NOT click OK. Select the Networking tab.
B.6.1. General
This chapter assumes that the DCC is already up and running and that the V.24 null
modem cabling is already installed.
The connection that needs to be established is a direct cable connection between two
computers over V.24. The requires a crossover cable called a null modem cable. This
cable is the normal DECT Manager cable from F122 connector to 9-pin D-connector (see
Customer Engineer Manual for 32-DCC manual or DCC-8.
The driver for a null modem connection is already available in Windows XP Professional as
the Connection between two computers option.
Click Network and Internet Connections. The following window will be displayed:
Select Setup an advanced connection and click Next. The following window will be
displayed:
Click the radio button: Guest. Then click Next. The following window is displayed:
Select the Communications cable between two computers (COMx) and click Next.
Check the check box Add a shortcut to this connection to my desktop. Click Finish
Double click the icon on the Desktop that represents the new connection. You will see the
following window displayed.
Select Typical (recommended settings) and allow unsecured password. Do NOT click
OK. Select the Networking tab.
Select Internet Protocol (TCP/IP) and click on Properties. The following window will be
displayed:
If you dont need the firewall you could disable it, but be careful, your computer might be
at risk on the network. If you need the Firewall to be enabled, it doesnt harm because all
traffic is outgoing.
Click OK. Now you are back in the Properties window. Click OK. You see the following
window:
Enter the Administrators password. Make sure that you have a null-modem connection to
the DCC. When you click Connect the connection is set up.
If the computer is connected to an ethernet network with TCP/IP and you use the Dial-up
adapter as well for TCP/IP, most likely you cannot start-up a connection between your
DECT Manager and the iSMobile system!!! To avoid problems, you need to take the
following into account:
DECT Manager PC
DCC
IP add.
192.12.48.2
Subnetmask:
255.255.255.0
DECT Manager PC
Router
LAN
IP add. 192.168.100.254
Subnetmask: 255.255.255.0 Null modem cable or
IP add. 192.17.80.254 real modem connection
Subnetmask: 255.255.255.0
DCC
DCC DCC
If you want to make the route permanent, you can add the parameter -p at the end
of the command.
In case the DCC is connected via Ethernet but on a different subnet then both in de PC
and the DCC a routing setting has to be made. The PC has to know what gateway to use
to get to the DCC and the DCC has to know what gateway to use to get to the PC. The
figure below gives an example.
DECT Manager PC
Router
IP add. 192.168.100.254
Subnetmask: 255.255.255.0 Null modem cable or
IP add. 192.17.80.254 real modem connection
Subnetmask: 255.255.255.0
DCC
DCC DCC
>CHPERD:2,<shelf>,<brd>;
8800; (set IP configuration command)
C011500E; (DCC IP address = 192.168.80.14)
FFFFFF00; (netmask = 255.255.255.0)
C01150FE; (gateway = 192.168.80.254)
After restart, the DCC has configured its Ethernet adapter accordingly.
If you need to check what the default gateway address is for your PC, you can execute the
following procedure:
If you want to add a route, execute the following steps each time you want to reach
a DCC via the Ethernet adapter after you restarted your system.
If you want to make the route permanent, you can add the parameter -p at
the end of the command.
First read section B.2.4 Retrieving Performance Data via the TCP/IP Connection in this
document.
Note that the performance data that you will retrieve via a telnet session is used for third
line maintenance only (development level). It is not the performance data that you retrieve
via the Performance Data Retrieval Tool! The performance data that you retrieve via the
Performance Data Retrieval Tool, gives you information about the behaviour of you system,
in terms of channel occupation etc.
Make sure that you have a connection to the DCC, either via Ethernet or via V.24.
In case you have a V.24 connection, make sure that the connection is active.
Step 2. Set Local Echo on, via the menu Terminal - "Preferences".
Now the connection is open and all characters that you type in are immediately sent to the
DCC. The Backspace key can not be used to make a correction.
You need to enter commands to retrieve data. You find the available commands in the next
section.
First read section B.2.4 Retrieving Performance Data via the TCP/IP Connection in this
document.
Note that the performance data that you will retrieve via a telnet session is used for third
line maintenance only (development level). It is not the performance data that you retrieve
via the Performance Data Retrieval Tool! The performance data that you retrieve via the
Performance Data Retrieval Tool, gives you information about the behaviour of you system,
in terms of channel occupation etc.
Make sure that you have a connection to the DCC, either via Ethernet or via V.24.
In case you have a V.24 connection, make sure that the connection is active.
Step 2. You are now in the Connection Description window to set up a new connection.
Step 3. Enter a name for your new connection (e.g. My IP connection) and click OK.
Step 4. Now you are in the Connect to window. In the field Connect Using select TCP/IP
(Winsock): The window contents changes.
Step 5. Enter the IP address of the DCC to which you are connected and click OK
Step 6. Go to the File menu and select Save. Now your Hyperterminal configuration is saved.
Next time you start your Hyperterminal, you can select this configuration from the list of
HyperTerminals.
Now the connection is open and all characters that you type in are immediately sent to the
DCC. The Backspace key can not be used to make a correction.
You need to enter commands to retrieve data. You find the available commands in the next
section.
By means of a telnet session, you can retrieve performance data. The following table
explains the commands that must be executed to retrieve data.
COMMAND RESULT
event on<cr> Turn event mode on.
The prompt changes to:
event>
pdc <board address> 83 0 0 1<cr> Retrieve TBC performance
data.
Now the Firmware is displayed.
When you make a call,
performance data is displayed.
However, this is used for third
line trouble shooting only.
Switch logging on via the Terminal menu Put the data into file.
pdc <board address> 84 0 0 1<cr> Retrieve MBC performance
data as well.
pdc <board address> 83 0 0 0<cr> Switch retrieving TBC
performance data off.
pdc <board address> 84 0 0 0<cr> Switch retrieving MBC
performance data off.
event off Finish your telnet session.
First switch performance data
retrieval off, then switch off the
Event mode.
Now you can disconnect your
Telnet session.
If you have a dial-up
connection, do not forget to
hang up the connection
Remarks:
The board address is the backbone address in Hexadecimal:
- range 1, 2, 3, 4, 5, 6, 7, 8 for backbone section 0;
- range 9, A, B, C, D, E, F, 10 for backbone section 1;
- range 11, 12, 13, 14, 15, 16, 17, 18 for backbone section 2;
- range 19, 1A, 1B, 1C, 1D, 1E, 1F, 20 for backbone section 3.
The following step by step procedure shows how to upgrade your SMPC 5.1.0 or
SysManager 410.
1. Make sure that you have either SMPC version 5.1.0 or SysManager 410 version 4.5.4.
2. Get the DECT Manager Patch for Multi-site subscription from the NSOnet Software
database.
3. Stop running processes. Stop the foreground processes by closing the open windows.
Use the Process Guard tray icon to stop the background processes.
4. Open a Command Prompt window in Windows (using Start, Run enter cmd). Go
to the directory where you have stored the DECT Manager Patch.
5. In the DECT Manager Patch directory, go to the Disk1 directory. In this directory you
will see the setup.exe file