Configuration Manual: Ascom d41 DECT Handset
Configuration Manual: Ascom d41 DECT Handset
Configuration Manual
Ascom d41 DECT Handset
Contents
1 Introduction............................................................................................................. 1
1.1 Abbreviations and Glossary ................................................................................ 1
1.2 Functionality matrix ............................................................................................ 2
3 Installation of Handsets.......................................................................................... 5
3.1 Preparing PDM Windows Version or IMS3 for handling of d41 ........................... 5
3.2 Installation of a new Handset ............................................................................. 5
4 Maintenance............................................................................................................ 8
4.1 Definitions ......................................................................................................... 8
4.2 Upgrade handset software ................................................................................. 8
4.3 View licenses of handset .................................................................................... 9
4.4 Upgrade handset by license ............................................................................... 9
4.5 Perform a Factory reset .................................................................................... 11
4.6 Replacement procedure choice guide ............................................................... 11
4.7 Replacement of handset with the IMS3 ............................................................ 12
4.8 Replacement of the handset with the PDM Windows Version ........................... 13
4.9 Brazil or other Latin America countries – DECT frequency configuration ........... 14
6 Administration ...................................................................................................... 27
6.1 Admin Menu Tree ............................................................................................ 27
6.2 Quick Access to the handset’s Device Information ............................................ 28
6.3 Quick Access to the Handset’s Input Menus ..................................................... 28
6.4 LED indications ................................................................................................ 28
7 Troubleshooting .................................................................................................... 29
7.1 Fault Symptoms ............................................................................................... 29
7.2 Display Information .......................................................................................... 29
1 Introduction
This document is a guide for installing, configuring and maintaining functionality of the
d41 handsets.
The d41 can be used straight away in your system but it is highly recommended to install
the Portable Device Manager (PDM) Windows Version or the Integrated Wireless
Messaging and Services application (IMS3). This enables customization of the behaviour of
the handset to suite each user profile and the specific PBX used in the system.
The PDM Windows Version is aimed for smaller sites where the handsets are within reach.
The IMS3 makes it possible to administrate the handsets centrally via a web interface
without the need to collect the handsets.
It is recommended that the reader has basic knowledge of the Ascom system and basic
knowledge of subscribing handsets to the PBX.
Basic Advanced
Company phonebook Yes Yes
1
Central phonebook Yes Yes
Voice mail access Yes Yes
Base station encryption Yes Yes
Upload language Yes Yes
Audio adjustment (mic gain etc.) Yes Yes
Emergency call number Yes Yes
Own line settings Yes Yes
PBX date format for absence handling Yes Yes
Own/User headset profile Yes Yes
Missed call indication No Yes
Clear lists in charger Yes Yes
Upgradable to Advanced2 Yes No
1.This is a system dependent feature
2. Requires a product license.
In the case of IP-DECT, it is possible to configure the d41 over the air.
This chapter describes how to configure handsets in three different system setups:
• Connect a desktop charger (DC4) or a rack charger (CR3) via USB to the computer
running PDM.
• Start PDM.
• Place the handset in this charger which shall be connected to PDM. The handset can
either be turned off or turned on when placing it in the charger. A handset that is
turned off will start up automatically and the battery charging symbol will be displayed.
For instructions on how to use PDM Windows Version, see Installation and Operation
Manual, Portable Device Manager (PDM), Windows Version, TD 92325EN.
Figure 1.
PDM
For instructions on how to use the IMS3, see Installation and Operation Manual, IMS3,
TD 92762EN.
• Connect a desktop charger (DC4) or a rack charger (CR3) via the Ethernet port to the
network.
The charger is by default configured to connect to the network using DHCP. If DHCP is
not used in the network, connect each charger via USB to a PDM Windows Version
and configure a static IP address.
• Start the IMS3.
• Place the handset in a charger that is connected to the IMS3. The handset can either
be turned off or turned on when placing it in the charger. A handset that is turned off
will start up automatically and the battery charging symbol will be displayed.
Figure 2.
IP
Client
IMS3
There is no external equipment needed besides IMS3 and IP-DECT. Please proceed with
3 Installation of Handsets on page 5.
Figure 3.
Ascom
IP-DECT
System
IPBS
IMS3 Client
3 Installation of Handsets
This section describes the recommended procedure for installing and configuring
handsets. There are several ways to install a handset but the procedures described here
guarantees simple maintenance of the system.
It is recommended to use the IMS3 to install and maintain handsets in a large system. The
reason is that it enables to install, upgrade and configure a large amount of handsets
simultaneously. Another benefit is that the collection of the handsets from the user is not
needed. They can be maintained while placed in network connected desktop chargers
(DC4) on the users desks. Network connected rack chargers (CR3) can also be used, or
over the air in the case of IP-DECT.
For PDM, see Installation and Operation Manual, Portable Device Manager (PDM),
Windows Version, TD 92325EN or Installation and Operation Manual, IMS3, TD 92762EN.
File extensions are further explained in an appendix in Installation and Operation Manual,
Portable Device Manager (PDM), Windows Version, TD 92325EN and Installation and
Operation Manual, IMS3, TD 92762EN.
• Subscription towards the DECT-system – needed to be able to make calls and send
messages (Mandatory).
• Create an identity for the handset in the PDM – needed to be able to configure the
behaviour of the handset and take backups of the handset configuration
(Recommended).
• Configure the handset using PDM – customize the behaviour of the handset to suite
each user profile and the specific PBX used in the system (Recommended).
The installation is described in two different scenarios, see below. Before starting, check
which scenario that suits best.
Note: The handset to be installed must not have any previous valid registrations. If it has a
valid registration, unsubscribe the handset or follow the instructions in 3.2.3 Handset
Installation in DECT or IP-DECT System (release 3.0.x or lower) on page 6.
1 Assign an extension number and register the handset’s IPEI in the IP-DECT system.
See the corresponding Installation and Operation manual for the IP-DECT system.
2 Subscribe the handset towards the IP-DECT system. The subscription procedure is
described in User Manual, Ascom d41 DECT Handset, TD 92582EN.
During the subscription procedure, the handset’s User ID will automatically be set to
the same as the extension number. The User ID is used to identify the handset when
it is connected to PDM/IMS3 and will be visible in the Number column.
Tip: The User ID can be viewed in the handset by navigating to the menu:
Admin menu > Device info > User ID.
See also examples of handset configurations that can be made in chapter 5 Handset
Configuration on page 16.
Note: The handset to be installed must not have any previous valid registrations. If it has a
valid registration, unsubscribe the handset or follow the instructions in 3.2.3 Handset
Installation in DECT or IP-DECT System (release 3.0.x or lower) on page 6.
1 Assign an extension number for the handset in the DECT/IP-DECT system. See the
corresponding manual for the DECT/IP-DECT system.
2 Subscribe the handset towards the IP-DECT system. The subscription procedure is
described in User Manual, Ascom d41 DECT Handset, TD 92582EN.
During the subscription procedure, the handset’s User ID will automatically be set to
the same as the extension number. The User ID is used to identify the handset when
it is connected to PDM/IMS3 and will be visible in the Number column.
Tip: The User ID can be viewed in the handset by navigating to the menu:
Admin menu > Device info > User ID.
See also examples of handset configurations that can be made in chapter 5 Handset
Configuration on page 16.
Create an identity
performed. The handset’s User ID will automatically be set to the same as the
extension number.
Tip: The User ID can be viewed in the handset by navigating to the menu:
Admin menu > Device info > User ID.
See also examples of handset configurations that can be made in chapter 5 Handset
Configuration on page 16.
1 Assign an extension number in the DECT/IP-DECT system for the handset. See the
corresponding manual for the DECT/IP-DECT system.
2 Subscribe the handset towards the DECT/IP-DECT system. The subscription procedure
is described in User Manual, Ascom d41 DECT Handset, TD 92582EN.
In order to easily identify the handset, both the IPDI and the User ID are shown in the
handset when initiating the subscription procedure.
4 Maintenance
4.1 Definitions
In the replacement descriptions, the handsets are defined as:
• "old handset" is the handset to be replaced, possibly damaged but still working
• "new handset" is the replacement handset that will get the settings used in the old
handset
OTA via IPBS OTA via IPBL DC4 Charger connected DC4 Charger connected to
to IMS3 via Ethernet WinPDM via USB.
approx. 17 approx. 102 approx. 5 min. approx. 4 min. 30 sec.
min. min.
The software download capacity depends on call traffic stated below. The table below is not
applicable for DC4 charger connected to WinPDM since IPBS, IPBL or IMS3 is not needed.
See also Installation and Operation Manual, Portable Device Manager (PDM), Windows
Version, TD 92325EN.
Tip: It is also possible to upgrade several handsets of the same device type (d41)
simultaneously using the Baseline function in the IMS3. See Installation and Operation
Manual, IMS3, TD 92762EN.
Use this option if the PDM has an internet connection to the License Server.
Use this option if the PDM has no internet connection to the License Server. A device
information file (.XML) must first be exported from the PDM, and then imported to the
License Web.
See the online help on the License Web, or Function Description, Product Licensing
Overview, TD 92677GB for information on how to use the License Web.
4 When the license file (.XML) containing the license key(s) has been downloaded
from the License Web, select File > Import > Licences in the PDM to import the file.
5 When the file is imported, the license key(s) is downloaded to the handset(s), and
the handset will be restarted. See also 4.3 View licenses of handset on page 9 for
viewing the handset’s license option(s).
Use this option if the serial numbers of the devices cannot be exported to a file due to a
PDM is not in use. The serial number(s) must be manually entered in the License Web to
get the corresponding license key for the handset. The license key must also be manually
entered in the handset. See the online help on the License Web or the Function
Description, Product Licensing Overview, TD 92677GB for information on how to get a
license key.
The license key is added via the Admin menu in the handset, see 6.1 Admin Menu Tree on
page 27 for information on how to activate the Admin menu.
Note: It is also possible to press *#35# in idle mode for quick access to the "Enter license
key" menu.
Note: This feature requires PDM that supports the move license feature, and a connection
to the license server.
It is possible to move a license from one device to another device of the same device type
(d41).
A move license command can only be done to an unlicensed handset of a device type
supporting licensing, that is, d41 Basic.
An example of when to use the Move licence command is when there is an unused d41
Basic and a d41 Advanced with a broken display. Use the Move licence command to move
the Advanced licence to the d41 Basic which becomes a d41 Advanced. Then the broken
handset (which is now a d41 Basic) can be sent for service.
5 In the Licenses menu, select "Refresh" to complete the transfer of the license. The
device is now a d41 Advanced.
See also 4.7 Replacement of handset with the IMS3 on page 12 for information on how to
move user parameters and contacts to another handset.
1 In PDM, click the Device tab and mark the handset to be factory reset. Note that the
handset must be online.
2 In the Device menu, select "Factory reset". Alternatively, right-click the handset and
select "Factory reset".
3 A Reset devices dialog appears, click "Yes". The handset will be restarted.
1 To activate the Admin Menu, enter the Call time screen and press > * < < * <.
2 Select "Factory Reset".
3 A Reset portable? dialogue appears, press "Yes". The handset will be restarted.
• If a handset needs to be replaced due to for example a broken display, see User
Manual, Ascom d41 DECT Handset, TD 92582GB.
• If the electrical connection is damaged, it might not be possible to follow the Easy
Replacement procedure. Depending on fault, it might work to do a replacement via
PDM/IMS3, see 4.7 Replacement of handset with the IMS3 on page 12 or 4.8
Replacement of the handset with the PDM Windows Version on page 13.
• If two handsets and their settings shall be switched between two users, follow 4.7
Replacement of handset with the IMS3 on page 12 or 4.8 Replacement of the handset
with the PDM Windows Version on page 13.
Make sure that the old handset is saved in the IMS3. Start the Device Manager in the IMS3
and navigate to the "Numbers" tab. There shall be a tick in the "Saved" column for the
old handset.
If the handset is not saved, insert it into a desktop charger or rack charger connected to
IMS3 and perform a save, see Installation and Operation Manual, IMS3, TD 92762EN.
If it would be impossible to save the old handset settings, stop this replacement
procedure. Instead unsubscribe the old handset from the PBX, register the new handset
and follow the instructions for installing a handset, see 3.2 Installation of a new Handset
on page 5. When the handset is saved, unsubscribe the old handset from the PBX.The
following steps are described in two different scenarios, check which one suits the best
before proceeding.
• DECT registration
• Call list
• Company phonebook
• Downloaded Language
• Licenses1
4.7.2 Handset Replacement with IMS3 in DECT or IP-DECT System (release 3.1.x or
higher)
Note: The handset to be installed must not have any previous valid registrations. If it has a
valid registration, unsubscribe the handset or follow the instructions in 4.7.3 Handset
Replacement with IMS3 in DECT or IP-DECT System (release 3.0.x or lower) on page 13.
1. A handset’s product license (that is, d41 Advanced) can be moved to a d41 Basic using the Move license function in
the IMS3.
3 Insert the handset into a desktop charger or rack charger connected to IMS3 (not
needed if an over the air connection is used). Navigate to the Numbers tab in IMS3
Device Manager.
The new handset now has the same User ID as the old handset. It will automatically
be synchronized and data and parameter settings from the old handset will be
transferred to the new handset.
The synchronization will take a while if the Contacts in the original handset contains
a large number of contacts.
4.7.3 Handset Replacement with IMS3 in DECT or IP-DECT System (release 3.0.x or
lower)
1 Make a note of the IPDI of the new handset. It is found by pressing *#06# on the
handset.
2 Insert the new handset into a desktop charger or rack charger connected to the IMS3
and navigate to the Numbers tab in the Device Manager in IMS3.
3 In the list, right-click the old handset and select "Associate with device...". Select the
device with an IPDI that matches the new handset from the list that opens.
The new handset is automatically synchronized and all data and parameter settings
will be transferred to the new handset.
The synchronization will take a while if the Contacts in the original handset contains
a large number of contacts.
Subscribe the new handset. The subscription procedure is described in User Manual, Ascom
d41 DECT Handset, TD 92582EN. During the subscription procedure, the handset’s User ID
will automatically be set to be the same as the extension number.
Both the old handset and the new handset must be of the same device type (d41). The
same extension number is assigned to the new handset.
The new handset should not be subscribed towards the PBX yet.
1 Perform a factory reset, see 4.5 Perform a Factory reset on page 11, if the new
handset has been previously used.
2 Make sure that the old handset is saved in the PDM by starting PDM and navigating
to the Numbers tab. There shall be a tick in the "Saved" column for the old
handset.
If the handset is not saved, insert it into a desktop charger or rack charger connected to
the PDM and perform a save.
Note: If it would be impossible to save the old handset settings, stop this replacement
procedure. Instead register the new handset and follow the instructions for installing a
handset, see 3.2 Installation of a new Handset on page 5.
The following steps are described in two different scenarios, check which one suits the
best before proceeding.
4.8.1 Handset Replacement with WinPDM in DECT or IP-DECT System (release 3.1.x or
higher)
Note: The handset to be installed must not have any previous valid registrations. If it has a
valid registration, unsubscribe the handset or follow the instructions in 4.8.2 Handset
Replacement with WinPDM in DECT or IP-DECT System (release 3.0.x or lower) on page 14.
4.8.2 Handset Replacement with WinPDM in DECT or IP-DECT System (release 3.0.x or
lower)
1 Insert the new handset into a desktop charger or rack charger connected to the PDM.
2 A dialogue window will be displayed. Select the option "Associate with number".
Follow the instructions and select the number of the old handset, see Installation and
Operation Manual, Portable Device Manager (PDM), Windows Version, TD 92325EN.
The handset will automatically be synchronized and all data and parameter settings
will be transferred to the new handset. The synchronization will take a while if the
Contacts in the original handset contains a large number of contacts.
3 Subscribe the new handset.
Note: This chapter is only applicable if the handset is used in Brazil or other Latin
American countries.
In order to change the operating frequency band, the following preconditions must be
fulfilled:
• The frequency set to "Not initiated". This can be checked by entering the Admin
menu, see 6 Administration on page 27, follow the path:
Admin menu > Device info > Hardware.
Scroll down to “Frequency band”.
• The handset must not have a DECT registration. If it already has, perform a Factory
reset, see 4.5 Perform a Factory reset on page 11.
5 Handset Configuration
Note: This chapter describes settings in parameter definition files (.def). These files are
regularly updated and settings may change slightly. For example "On" to "Enable" or a
parameter can be moved to another directory.
Templates enables configuration of all aspects of a handset from sound volume to keypad
shortcuts.
Your supplier can provide example templates for different PBX:s. The handset will have full
functionality towards the PBX even without such a template. By using such a template,
though, the handset will be customized for that PBX with menu options for PBX specific
functions such as Callback.
1 Open the PDM Windows version or the Device Manager in the IMS3.
2 Select the Templates tab and open the menu "Template > New...". The Create
Template window is opened.
3 Select the device d41 and parameter version that matches the software version
installed on the handset. Give the template a descriptive name.
The parameters that are not part of the template will be left unchanged on the
handset.
The parameter version of an installed handset is visible under the "Numbers" tab or
the "Devices" tab.
4 Select the checkbox of each parameter that you want to be part of this template
and enter the proper value.
5 Click "OK" to save your template.
1 Open the PDM Windows Version or the Device Manager in the IMS3
2 Open the Numbers tab and select the handsets you want to apply the template to.
3 Make a right-click and select "Run template...".
Only templates with a parameters version matching the selected handsets will be
shown. Select the template you want to apply and click "OK".
4 The template is applied. The number of parameters in the template will affect the
time it takes to apply the template to the selected handsets.
When looking at a handset under the Numbers tab, the column "Last run
template" will show the name of the most recently applied template.
Note: It is also possible to apply a template on several handsets of the same device type
(d41) simultaneously using the Baseline function in the IMS3. See Installation and
Operation Manual, IMS3, TD 92762EN.
It is possible to save all settings of a handset as template. Please note that this does not
include contacts and other personal data. The template will only contain configuration
data.
This template can be used as a backup if you want to restore the configuration of the
handset at a later stage or as a template that can be applied to a number of handsets.
After installing and saving a handset, it will be synchronized each time it is connected to
the PDM. The synchronization transfers parameter changes between the handset and the
PDM and vice versa as follows:
• If a parameter has been changed in the handset, it will be transferred to the PDM/
IMS3.
• If a parameter has been changed in the PDM/IMS3 while the telephone was
disconnected, it will be transferred to the handset.
If the same parameter has been changed in both the PDM/IMS3 and the handset, the
value in PDM/IMS3 will be transferred to the handset.
If the system is not equipped with a Central Phonebook, this menu option can be removed
from the handset by entering an empty value for the corresponding parameter.
The parameter can be set specifically for each PBX subscription on the handset and is
accessed from Systems > System x > PBX Settings > Numbers. "System x" is replaced with
the subscription (System A - System H) that is configured.
The phonebook file (.cpb) is created from an Excel file using a script to extract the
information and create to the phonebook file (.cpb). The Excel file is provided by your
supplier.
In PDM, go to the devices tab and select device(s). In the Device menu, select Upload
phonebook.
See also Installation and Operation Manual, Portable Device Manager (PDM), Windows
Version, TD 92325EN, or Installation and Operation Manual, IMS3, TD 92762EN.
The local phonebook file is created by an Excel file provided by your supplier.
Note: When uploading a local phonebook file, local phonebook entries (if any) in the
handset will be replaced by the entries in the file.
1 In PDM or the Device Manager in the IMS3, go to the Numbers tab and select
handset(s).
2 In the Number menu, select Import contacts > From file.
3 Select the file to be imported and click "Open".
The menu is described in User Manual, Ascom d41 DECT Handset, TD 92582EN.
Besides the default Call services functions, it is possible to define 10 extra system specific
call services by codes. The codes can be programmed with pause (P) and auto
disconnection (H). Both Name and Data must be defined for the option to be displayed.
Possible values: Digits 0-9, #, *, 'P' – pause, H – hook.
The programming of the menu is done with PDM. For instructions on how to work with
PDM, see Installation and Operation Manual, Portable Device Manager (PDM), Windows
Version, TD 92325EN.
Using the PDM and the "Edit template" feature, the parameter can be found at
Systems > Common > Call Services > General Service X
Note: Your supplier may have a template example that will configure the call services
menu for the PBX.
Tip: Beside the default call diversion menus, it is possible to define 10 extra system specific
services codes, see 5.6 Call Services.
The user can now enter the diversion number in the handset.
Beside the default absence menus, it is possible to define 10 extra system specific services
codes, see 5.6 Call Services.
The menu is described in User Manual, Ascom d41 DECT Handset, TD 92582EN.
The programming of the menu is done with PDM. For instructions on how to work with
PDM, see Installation and Operation Manual, Portable Device Manager (PDM), Windows
Version, TD 92325EN.
Ask your supplier for example templates that will configure the in call menu for your PBX.
Note: It is also possible to configure own In call functions, see 5.9.1 Configure Own In Call
Functions on page 21, or create a shortcut to a certain In call function, see 5.9.2 Create/
Hide a Soft Key to an In Call Function on page 21.
Using the PDM and the "Edit template" feature, the parameters can be found at
Tip: Ask your supplier for example templates that will configure the in call menu for your
PBX.
Besides the default In call functions, it is possible to define 10 extra system specific call
services by codes. The codes can be programmed with digits 0-9, #, *, P – pause, and
H – hook (auto disconnection).
1 Select Systems > System X > PBX Settings > In call functionality > General purpose
X
2 In the Name field, enter the name to be displayed in the In call menu.
3 In the Data field, enter the applicable code to be used for the function.
4 Click "OK" to save the settings.
Tip: Your supplier may have a template example that will configure the In call functions
menu for the PBX.
It is possible to configure the right Soft key as a shortcut to a certain In call function, or
hide the Soft key. By default, the right Soft key is configured as R-key.
1 If needed, configure the In Call functionality to be used. See 5.9 In Call Menu on
page 20. This is not needed if the Loudspeaking function or R-key shall be used.
2 Select Systems > System X > PBX Settings > In call functionality > Soft key Right
3 In the Name field, enter a descriptive name of the Soft key. This is not needed if the
functions Loudspeaking function or R-key shall be used.
4 In the Function drop-down list, select the function to be used.
5 Click "OK" to save the settings.
1 Select Systems > System X > PBX Settings > In call functionality > Soft key Right
2 In the Function drop-down list, select "Not used".
3 Click "OK" to save the settings. The Soft key will not be visible during a call.
A missed call is by default indicated by a Missed call window. It is possible to hide this
window and is recommended if a user has, for example, both a DECT handset and a
mobile.
Example:
If configured in the PBX, an incoming call to the DECT handset can either be answered
using the DECT handset or mobile. If the user answer the call using the mobile, the Missed
call window will not be displayed in the DECT handset.
• Calling numbers stored with a "+" sign for the international access code. The same
phonebook can be used in different countries.
• Recognizing incoming internal or external calls as numbers stored on international
format in the phonebook. The same phonebook can be used in different systems.
In order for this feature to work, numbers must be stored in the phonebook in
international format with a "+" sign for the international access code. Also, the Own Line
parameters must be configured via PDM/IMS3.
For instructions on how to work with PDM/IMS3, see Installation and Operation Manual,
Portable Device Manager (PDM), Windows Version, TD 92325EN, or Installation and
Operation Manual, IMS3, TD 92762EN.
Note: If another language file is uploaded, the first additional language is overwritten.
Certain special characters are allowed when generating the language file, see information
in the Excel file.
To upload an additional language, the PDM or IMS3 is used, go to the devices tab and
select device(s). In the Device menu, select "Upload language...".
A parameter can be altered to match the uploaded language: The parameter controls:
Note: It is also possible to upload additional language on several handsets of the same
device type (d41) simultaneously using the Baseline function in the IMS3. See Installation
and Operation Manual, IMS3, TD 92762EN.
See also Installation and Operation Manual, Portable Device Manager (PDM), Windows
Version, TD 92325EN.
Calls can be redirected to another extension when the handset is placed in a charger. In
addition, message absence is also enabled when calls are redirected. When an application/
system sends a message to a handset, it will receive an indication that the handset is
absent. The application/system determines if the message shall be sent to the handset or
not, or redirected to another handset.
The function is automatically cancelled when the handset is removed from the charger.
Note: The settings in the system determines how the incoming calls/messages will be
handled. This is a system dependent feature.
When the handset is placed in the charger it can be switched off. When removed from the
charger it will switch on again.
When the handset is placed in the charger it can be muted while it is charging. When it is
removed from the charger it will switch on the sound again.
• Call list
• Missed calls
Using the PDM and the "Edit template" feature, the parameter can be found at
Connections > In_Charger > Clear_Lists_In_Charger
in a template or parameter definition file (.def).
The default setting for "Clear list in charger" is "Off". The feature is activated by changing
the parameter value to "On". When the feature is enabled, the lists are cleared when the
handset is placed in the charger.
Using the "Edit template" feature in the PDM, the parameter can be found at
Systems > Home_Base_Subscription.
The parameter shall be set to "Enable" for registration of a new base station. The default
value is "Disable".
Requirements:
• The encryption is enabled in the base station. See corresponding manual for the base
station.
• If Ascom´s base station is used, the software version must be 3.1.x or greater.
• The handset software version must be 2.9.7 or greater.
Using the "Edit template" feature in the PDM, the parameter can be found at
Systems > Encryption required.
When the parameter is set to "Yes", it is only possible to establish calls via encrypted base
stations. The default value is "No".
• Normal side tone adjustment - Determines how much of the speakers voice that is fed
back to the speaker.
• Normal mic adjustment - Determines the microphone sensitivity, that is, how much
sound the microphone shall gain.
The parameter settings affect the “normal” mode, that is, not wired headset, and not the
handsfree/loudspeaking mode.
Note: Changing these parameters may result in lower sound quality and high sound level.
Evaluate carefully before applying.
In order to achieve optimal audio quality with the different headset types, it is
recommended to set the corresponding headset type. The default setting is "microphone on
a boom", which means that the audio is optimized for using a headset with microphone on a
boom. The headset type can be changed as follows:
If the preconfigured headset profiles does not match the headset or the audio performance
is bad, it is possible to configure a headset profile.
Note: All settings except the default setting require an IP-DECT system with software
version 5.0.x or higher.
1 Select System X.
2 In the Display Management Layout drop-down list, select one of the following:
• 2x12 characters
• 2x16 characters
• 3x16 characters, remove Owner ID
• 3x16 characters, remove system name
Note: It is also possible to configure the Owner ID via the handset menu. See User
Manual, Ascom d41 DECT Handset, TD 92582EN.
6 Administration
The following figure shows the menu tree for the Admin menu in d41.
Figure 4.
• Logging —>
• No. of events —> • Select
• Restart reason —> • Back
• System —> • Change system —> • Automatically
• System A
Other menues are described in User Manual, Ascom d41 DECT Handset, TD 92582EN.
Information Code
Software version *#34#
Hardware version *#34#
IPEI *#34# or *#06#
IPDI *#34# or *#06#
User ID *#34#
Menu Code
Enter license key *#35#
7 Troubleshooting
This section contains information on how to solve common operational problems, and
information on warnings you may receive.
Go through the following lists if you encounter any problems. If this checklist does not
solve the problem, contact the system administrator.
SERVICE NEEDED Easy replacement procedure Send the handset for service.
Invalid IPDI not followed correctly or
failure during easy
Note: This display message is replacement procedure.
only shown in English.
Enter PIN code Phone lock is activated. Enter the required PIN code.
If the PIN code has been lost,
enter a new PIN code via the
PDM/IMS3 or do a factory
reset via the PDM/IMS3.
Battery low, charge now The battery level is low. Charge the handset, or
replace battery.
Phonebook is not available at The phonebook is not Try again later or if the fault
the moment. activated or does not persists do a factory reset via
respond. the admin menu or via the
PDM/IMS3.
Note that it may take several
minutes for the phonebook
to be available if there are
many entries in Contacts
and/or company phonebook.
Voice mail number not There is no Voice mail Define a Voice mail number
defined number defined in the via the PDM/IMS3.
handset.
Could not encrypt The parameter "Encryption 1) Disable the "Encryption
connection Required" is enabled in the Required" parameter in
handset in combination with; handset; and/or,
1) Unencrypted base
station(s); and/or, 2) Enable the encryption in
the base station(s); and/or,
2) Unsupported base
station(s). Note: If Ascom’s base
station(s) is used, the
software version must be
3.1.x or greater.
License key not accepted 1)The license key is to short/ 1)Make sure that the license
long key consists of 29 digits.
2) The license key is not valid. 2) Generate a valid license
using the License Web.
8 Related Documents
9 Document History
For details, see change bars in the document.
Version Date Description
A 10 February 2009 First released version
B 07 April 2009 Updated for over-the-air connection.
C 15 December 2009 Chapter Easy Replacement moved to the User
Manual.
Chapter 6.4 LED indications on page 28: Easy
Replacement issues moved to the User Manual.
7 Troubleshooting on page 29: Easy Replacement
issues moved to the User Manual.
7.3 LED Error Indications moved to the User
Manual.
See changes bars for more information.
D 28 January 2010 1.2 Functionality matrix updated. See change bars
for more information. Chapter 7.3 Error Messages
in PDM moved to Installation and Operation
Manual for PDM Windows version, 92325GB.
E 21 December 2010 See change bars in the document.
F 08 November 2011 See change bars in the document.
Index
A
Admin menu ................................................. 24
Audio adjustment.......................................... 21
B
Baseline........................................................... 8
C
Call services................................................... 18
Central Phonebook ....................................... 17
Clear lists ...................................................... 20
Company Phonebook.................................... 18
E
Emergency Call Number ................................ 21
F
Factory reset.................................................. 11
H
Hardware version .......................................... 25
Headset configuration ................................... 22
I
Import Contacts ............................................ 23
IMS ................................................................. 1
In Call Menu ................................................. 19
Installation ...................................................... 5
IPDI ........................................................... 1, 25
IPEI............................................................ 1, 25
L
LED indications.............................................. 25
License upgrade .............................................. 9
O
Over-the-air..................................................... 4
Own Line Settings ......................................... 19
Owner identification...................................... 22
P
PDM ............................................................... 1
Protect registration........................................ 21
R
Replacement ................................................. 11
S
Software version ........................................... 25