Reference15r1:IP1202/IP1203 DECT System

There are also other versions of this article available: Reference | Reference15r1 (this version)

This article describes the IP1202/IP1203 DECT system and provides further helpful information.

Applies To

This information applies to:

IP1202, IP1202/4, IP1202/4s, IP1202e
IP1203, IP1203/4, IP1203e
IP64
IP65
Ascom d83
Firmware Version 15

Product Availability

IP-DECT base stations

IP1202/4s: Singlecell DECT basestation, offering up to 4 concurrent DECT-channels. Minimum required firmware 13r1sr8.
IP1203: Multicell capable DECT basestation, offering up to 8 concurrent DECT-channels. Successor of IP1202.
IP1203/4: Multicell capable DECT basestation, offering up to 4 concurrent DECT-channels. Successor if IP1202/4.
IP1203e: Multicell capable DECT basestation, offering up to 8 concurrent DECT-channels, two external antenna connectors and two included dipole omni directional antennas. Successor of IP1202e.

IP-DECT handsets

Current innovaphone portfolio includes the following DECT devices (as of August 2022):

IP64: Entry level handset. Successor of IP61. Labeled as DH6 in WinPDM & IP1203.
IP65: Advanced level handset with messaging abilities. Successor of IP63. Labeled as DH7-M in WinPDM & IP1203.
Ascom d83 Talker: DECT phone for rough environments. Successor of d81. Labeled as d83-Talker in WinPDM & IP1203.
Ascom d83 Messenger: DECT phone for rough environments with messaging functionality. Labeled as d83-Messenger in WinPDM & IP1203.
Ascom d83 Protector: DECT phone for rough environments with alarming and messaging functionality. Labeled as d83-Protector in WinPDM & IP1203.

IP-DECT Antennas

IP1202e/IP1203e includes two dipole omni directional antennas. For special use cases, optionally different directional antenna types are offered for separate order. They are connected to the external MCX-connectors of IP1202e/IP1203e:

Directional dual antenna (50-01202-004)
Directional single antenna (50-01202-005)
Omnidirectional single antenna (50-01202-006)

For details about external antennas and their usage, refer to this article.

Base station housings

innovaphone offers two different types of outdoor housings. For further information, please refer to the documents listed below:

Accessories

simple charger (50-00060-001) for both IP64 and IP65 (DC3-UAAA)
simple charger (50-00083-019) for d83 (DC3-AAAD)
programming device (50-00060-021) for both IP64 and IP65 for administration purposes via WinPDM (DP1-UAAA - same as for Wifi-device IP73, no Firmware Update for the device itself is required)
programming device (50-00083-020) for Ascom d83 for administration purposes via WinPDM (DP1-AAAD)

Remarks:

Chargers and programming devices are not part of the handset delivery and have to be ordered separately.
Any previously available DECT devices are end-of-life and no more supported.

Firmware

Firmware for DECT-basestations (IP1202, IP1202e, IP1202/4, IP1202/4s, IP1203, IP1203e, IP1203/4), handsets (IP61, IP63, IP64, IP65) and WinPDM can be downloaded via the innovaphone AppStore.

IP1203x is supported by major firmware version 13 and higher. It can be operated together with IP1202 devices with the same V13 firmware version.

Starting with 15r1, the VARs flash space for IP1203 base stations was increased. If you want to downgrade an IP1203 base station to prior 15r1 firmware, you have to download the current config, downgrade the IP1203 and upload the config afterward again.

OTA (Over the Air) Features

Important

If you have your IP120x radios already included in an Ascom Unite system, you can't use these features, since the unite module inside the IP120x configuration is used for the innovaphone OTA features also.
So either you use a Unite system (which includes paramter configuration and firmware updates) or our OTA features.

A running call won't be affected by the firmware update and the handset will only restart, if the call is ended. But keep in mind, that the update progress will take much longer, since the resources of the IP120x are primary used for running calls.

Devices App (recommended)

You can configure an update job to roll out handset updates: Reference15r1:Concept_App_Service_Devices#DECT_handsets.
- After the update job config is pushed to the dect radios, the dect radios need an additional reboot.
You can configure a DECT handset configuration to roll out handset configuration options: Reference15r1:Concept_App_Service_Devices#DECT_handsets_2.
See Supported DECT handsets.

Firmware update (manual configuration)

Firmware of IP64, IP65 and Ascom d81 and d83 handsets can be updated via parameter definition on the dect master.

Upon registering of the handsets, they give the dect master their current firmware version information. If this version differs from the configured firmware version parameter, the base station on which the handset is registered on, starts a download of the firmware.
After the download is completed, the handsets restarts automatically with the new firmware.

The following config lines need to be added to the IP120x configuration, to update all registered IP64 and IP65 handsets, for example to firmware 3.0.16:

!config change DEVMANBW /hs-param-url !config change DEVMANPP /firm-dh7 3.0.16 /firm-dh7-url http:///IP65/DH7-M_v3.0.16.bin /firm-dh6 3.0.16 /firm-dh6-url http:///IP64/DH6_v3.0.16.bin !config write !config activate !reset

Explanation of the parameters

/hs-param-url enables the over-the-air feature in the DEVMANBW module. The firmware parameters need to be configured in the DEVMANPP module.

/firm-dh7 sets the firmware value for IP65 handsets to the wanted firmware version. If the handset already have that firmware, no update is executed.
/firm-dh7-url URL where the firmware binary for IP65 handsets can be downloaded.
/firm-dh6 sets the firmware value for IP64 handsets to the wanted firmware version. If the handset already have that firmware, no update is executed.
/firm-dh6-url URL where the firmware binary for IP64 handsets can be downloaded.

More information

Only the .bin files can be used as download. If you've downloaded the firmware via our store, it is in .pkg format and includes more data. You need to unpack the .pkg (for example via 7zip or WinRAR) to get the .bin file.
For each handset, a separate download of the firmware will be executed. So if you have three IP65 handsets registered on the same IP120x, three downloads will be started.
- The DEVMANPP module in the master will limit it to max 10 downloads in parallel. There are also some limitations in the handset that will make sure that there are not more than 5 downloads per radio.
If a handset is shut down or deregistered while the download is running, the download is cancelled and will be started again, the next time the handset is registered.

Configuration of Handset parameters

Important: This Feature is available with firmware version 4.3.2 onwards for IP64 and IP65 Handsets.

IP64 and IP65 handsets can receive different configurations via a parameter .xml-file from the base station.

The following config lines need to be added to the IP120x configuration:

!config change DEVMANBW /hs-param-url http://<PATH to Webserver>/<parameter-file>.xml
!config write
!config activate

The base station will retrieve the parameter file on restart of the base itself or on the configured timeout value (default is 60 minutes).
You can adjust the default timeout to a lower value, e.g. 1 minute, by adding the following config:

!config add DEVMANBW /cfg-poll-interval 1
!config write
!config activate

For the handsets to get the parameters, they need to be restarted. After connecting to the base station, the handsets will retrieve the parameters.

An example .xml-file can be downloaded here.
This file will set the following parameters on the handset:

Language = German
Date format = DD/MM/YYYY
Voicemail number = 99

A list with all available parameters can be found here.

Explanation of the parameter list

Parameter id range 4-7 is for configuring the call menu options, which comes in pairs. So even numbers define the menu text and odd numbers the action (4 and 5, 6 and 7 etc.). Typically used for defining feature access codes.

Troubleshooting OTA

If the handset is not updated, please send us (support@innovaphone.com) a trace with following options:

All IPv4 TCP/UDP Traffic

All IPv4 TLS Traffic

Also enable further trace options, via commands on the base station:

!config add CUNITE /trace /module-trace verbose
!config add CUNITE FILEGET /trace /module-trace verbose
!config add DEVMANPP /trace /module-trace verbose
!config add DEVMANBW /trace /module-trace verbose
!config add MATP /trace /module-trace verbose
!config write
!reset

Licensing

innovaphone DECT devices are only operational with innovaphone PBX licenses. Operation without innovaphone PBX is not possible.

Compatibility Statements

IP1202 and IP1203 base stations are compatible to each other and can be used in mixed systems in V12 and V13 innovaphone PBX environments (with most recent FW version). When adding an IP1203 to an IP1202 installation, an update of the DECT devices to a V13 firmware is required (PBX can remain on V12 firmware).

No Base Station and No Handset Compatibility

The IP1202/IP1203-based IP-DECT solution is not compatible to IP1200 based IP-DECT solution.

The old DECT handset IP50, IP52, IP54, IP55, IP56 will not operate on new IP1202/IP1203-based IP-DECT system, since not only GAP compliance is required, but also CAP compliance (DECT external handover CAP-N.1).

The DECT handset must support GAP and CAP for operation on IP1202/IP1203 based DECT system.

The new DECT handsets IP61, IP63, IP64 and IP65 will not operate on old IP1200 based IP-DECT system.

The new DECT base stations IP1202/IP1203 and IP1202e/IP1203e can not be used to extend an existing old IP1200 based IP-DECT system.

=> This means NO HANDOVER between different systems (move with active call on a specific handset from an IP1200-system to an IP1202/IP1203-based-system or vice versa)

=> This means NO ROAMING between different systems (usage of a specific handset in a non-compatible IP-DECT system - see above)

Mixed Ascom/innovaphone Environments

It is generally not supported to mix Ascom (or any of their OEM-products) and innovaphone DECT products in a single installation, e.g.

Combination of IP120x and Ascom IPBSx base stations is neither allowed nor supported
Usage of IP61/IP63/IP64/IP65 with Ascom IPBSx based networks is not supported
Usage of non-innovaphone handsets in IP120x based networks is not supported
Usage of innovaphone firmware at Ascom devices (bases and/or handsets) is neither allowed nor supported

Exception: Operation of Ascom d8x in an IP1202/IP1203 environment is supported.
Exception: Usage of IP61/IP63/IP64/IP65 with Ascom UNITE Alarm/Messaging Server is supported. Pay attention to special terms and conditions for usage.

No Multicell License Required

The Multicell License is obsolete for IP1202-based IP-DECT systems.

For IP1202/IP1203-based IP-DECT systems a SARI (Secondary Access Right Identity for DECT) certificate is required. The SARI activates an IP-DECT Master based on IP1202/IP1203. One single SARI certificate is required for a single IP-DECT system, regardless how many base stations are used. Also for IP-DECT systems with one single base station and single-cell base stations a SARI certificate is required. The SARI certificate is not an innovaphone license and only required to make sure the DECT Radio Fixed Part Identity used in the DECT system is worldwide unique one.

A Multicell License can not be converted to a SARI certificate (and there is also no need to do so).

Note: Multicell capability does not apply to IP1202/4s. IP1202/4s is a single cell basestation without expansion capability for another base station. It does not offer handover and roaming capabilities.

Certifications and Test Reports

The innovaphone PBX was tested and certified by Ascom Wireless Solutions with Ascom IPBS based IP-DECT System, on which IP1202 is based (but is not the same product). A Certificate and a Test Report of this certification are available for download.

Wired Headset Support for IP64/IP65

The IP64 and IP65 DECT handsets offer a 4-pole 3.5mm phone jack for headset connection.

Following headsets are tested by the manufacturer:

in-ear headset, incl. cable with phone jack - order no. 50-00060-29
headset with mic on boom, quick disconnect - order no. 50-00060-30 (needs additional adapter for QD to 3.5mm phone jack - order no. 50-00060-032)

There's no technical support in case of issues for use of other headsets.

3rd party products

Partner reports successful testing of following products:

Sennheiser 506090 CMB 01 CRTL - 4-pole 3.5mm adapter to connect Sennheiser headsets at IP64
Apple iPhone Headset with 4-pole 3.5mm jack, Tested answer and disconnect by pressing button in headset cord.

Note though, that innovaphone gives no technical support in case of malfunction.

Bluetooth Headset Support for IP63 / IP65

IP63 and IP65 DECT handsets support handsfree and headset profiles for Bluetooth.

Following headsets are tested by the manufacturer - for some models restrictions have been reported to us (as of 11/20/18):

Jabra EVOLVE 65 MS Stereo
Jabra EVOLVE 75
Jabra MOTION UC+ MS
Jabra STEALTH
Jabra SUPREME UC MS (audio not working correct on outgoing calls with various CTI clients)
Peltor WS Headset XP (MT H7 WS5)
Plantronics B825-M Voyager Focus
Plantronics BackBeat GO 2
Plantronics Blackwire 710
Plantronics Explorer 500 Bluetooth Headset Black
Plantronics ML20 (not for IP65)
Plantronics M70
Plantronics M90
Plantronics Voyager 5200 BT Headset EU
Plantronics Voyager Edge
Plantronics Voyager Legend UC (audio not working correct on outgoing calls with various CTI clients)

DECT In-Call Features

IP1202 and IP61/63/64/65 handsets offer In-Call features by R-Key handling accoring to this description.

3PTY (3 party conference)

Starting with version 9 firmware, the IP1202 DECT system supports 3PTY (3 party conference) on DECT phones. However, be aware that this requires innovaphone CONF/SCNF interfaces as part of the system. Such CONF/SCNF interfaces may or may not be present on a gateway device running the PBX, depending on the model used. See respective gateway datasheets for voice/audio conference channels provided by the device. Note that the CONF/SCNF interface used does not need to be present in the PBX device, it can be provided by just any gateway platform available in the system. There are no conference channels available in the IP1202/IP1203 though.

For details about configuration please refer to the relevant training document.

Usage in non-EU countries

innovaphone DECT prodcuts of type IP1202x, IP1203x, IP64 and IP65 can technically be operated in most countries of the world, as the hardware supports all relevant DECT frequencies (software configurable).

However, the devices are approved in EU/EFTA states only! Use in other countries will probably be illegal thus.

Test-SARI

DECT Systems are using a worldwide unique system identification (SARI) to be separated from each other.

For test and training purposes, innovaphone offers the following SARI:

31100422072149

This SARI is intended for use in test/training systems only!

Usage within productive systems is prohibited and not recommended.

If the SARI is changed, all handsets have to be subscribed again.

DECT systems which are near to each other and are using the same test-SARI, may disturb each other.

DECT Service Codes

IP64

*#34# - Displays the Device Info
*#06# - Displays the IPEI/IPDI

IP65

*#34# - Displays the Device Info
*#06# - Displays the IPEI/IPDI 
*#77# - Site Survey Tool

Admin Menu

The handset has a hidden menu for system administrators. The Admin menu contains:

Software and hardware information, IPEI/IPDI, and User ID
DECT link and system information
Site survey tool
Fault logging
Enhanced system menu with ability to alter protection
Factory reset option

To activate the Admin Menu, enter the Call time screen via "Menu->Call list->Call time" and press > * < < * <

> or < means pressing the rocker key in the indicated direction ;-)

Status indication LED

The IP1202/IP1203 has one RGB LED to indicate its current status.

Each blink pattern is represented by a number of blocks where each block is 100 ms. Light grey blocks means that the LED is off. Whenever the indication is changed the new pattern always starts from the first block.

Following status are indicated:

Idle/OK "Solid blue"

IP1202 operational and no traffic on the IP1202/IP1203.

Starting up/ searching "100 ms blue, 100 ms off"

The IP1202 is in start-up phase, e.g. waiting for parameters from PARI Master, or is searching for air synchronization.

Active traffic "400 ms off, 2000 ms blue"

IP1202/IP1203 operational and traffic on the IP1202/IP1203.

Fully occupied "400 ms red, 2000 ms blue"

Fully occupied with speech traffic.

Software download "400 ms blue, 600 ms off"

Firmware download in progress.

Mini firmware "100 ms yellow, 100 ms off"

The IP1202 is in mini firmware mode.

TFTP mode "Solid yellow"

TFTP mode.

Error "100 ms red, 100 ms off"

No Ethernet connection.

Fatal error "Solid red"

Fatal hardware error.

Deployment: Good sync "2000 ms blue, 400 ms yellow"

The IP1202/IP1203 is in deployment mode and has good air sync coverage.

Deployment: Bad sync "400 ms blue, 600 ms off, 400 ms blue, 600 ms off, 400 ms yellow"

The IP1202/IP1203 is in deployment mode and does not have adequate air sync coverage.

Deployment: No sync "2000 ms red, 400 ms yellow"

The IP1202/IP1203 is in deployment mode and has no air sync coverage

Known Problems

H.323/TLS Registrations

If you want to use H.323/TLS as Registration Protocol for the Dect-Handsets on an IP1202/IP1203, there are a few things to consider. Using the TLS only Flag in the corresponding User Object will not work, because the CN (Common Name) of the IP1202/IP1203-Certificate doesn't match, with the Username and therefore the Registration at the PBX will fail.

If you still want to use a H.323/TLS Connection between IP1202 and PBX, you have to use other Mechanics to authenticate the DECT-Handsets. This can be done either by using the User Objects Password (not recommended) or activate the Flag PBX Pwd at the corresponding User Object (recommended). You have to enable Registration with system password at the IP1202/IP1203

With this Setup, you have H.323/TLS based communication between the IP1202/IP1203 and your PBX and the user himself is authenticated via the PBX Password.

incoming calls limited to number of radio/DSP channels

Each incoming call towards a radio base station (IP1202/IP1203 or IP1202/4,IP1203/4) allocates a DSP channel during the alert state.

If more DECT-handsets are subscribed to this base than DSP/radio channels are available, call setup will fail for surplus devices, and result in no audio (just noise).

Example: Call Broadcast to 5 DECT users subscribed in a IP1202/4,IP1203/4. One out of these 5 users will alert but without any DSP allocation (random). Answering such a call results in no audio for this user.

Blind Transfer

Internal ring tone after external call is blind-transferred to C, which does not save external number in call list (per IPBS design)

No number resolution from local contacts

In case numbers of local contacts are not resolved in incoming call screen but in call list only, adjust display management settings via WinPDM:

Firmware Compatibility

Newer IP1202 hardware (such with product code IPBS2-M3A , IPBS2-M4A or IPBS2-M5A on the back, introduced 2Q2015) need at least firmware V11r1 SR3 or V10 SR22. Older versions are not supported!

Choppy voice on handsets in noisy environments

If DECT handsets are used in noisy environments (e.g. industry), gaps in the voice can appear, the syllables appear to be dropped from time to time.

This is caused by the echo canceller on the radio (IP1202/IP1203) serving the connection for the DECT handset.

A config switch for noise optimised echo canceller mode can be used in this case for IP1202:

!config add MSP0 /ec-type 1

and for IP1203 a different command:

!config add SOFT-DSP0 /ec-type 1

This config switch should be distributed to the base stations serving the radio connections for the DECT handsets in noisy environments only.

The ec-type parameter can be configured with values 0-2, 2 being currently (12r2SR14) the default value.

According a report from a customer, setting the ec-type value to 0 (i.e. disable the echo canceller) at the base-stations in the noisy environment (and only there) helped. So if setting ec-type 1 doesn't help, you can try ec-type 0.

Phone book search of users with * or # is not possible

The phone book search is realized via SMS messages. This protocol defines and works with digits only. Therefore, this function cannot be used by users who contain a * or # in their number. In other words, users who perform the phonebook search cannot use * or # in their number.

Remarks

For a successful registration to the PBX, it is mandatory that an entry with the user's Name as Hardware Id value exists in the Devices section of the PBX user.