Reference:IP73 WLAN WiFi Wireless IP-Phone

From innovaphone wiki
Jump to navigation Jump to search

This article describes the IP73 WLAN/WiFi wireless IP phone, differences to the deprecated IP62 Wireless IP phone and a list of compatible WLAN infrastructures.

Applies To

This information applies to:

  • innovaphone IP73 (50-00073-001)


To perform configuration changes on the IP73 device a desktop programming kit (IP62/IP64/IP65/IP73) (Art.No. 50-00060-021 / Prod.ID DP1-UAAA/1A1) is required. The programming kit enables to connect the IP73 handset to a PC in order the configuration changes can be done using WinPDM software.

Feature Comparison

This chapter describes the differences in the feature sets between old and new WiFi handsets.

Handset Features Matrix
Feature IP62 IP73 Description
Signaling Protocols H.323/SIP SIP only
Codecs G.711, G.722, G.729 A Opus Wideband, G.711, G.722, G.729 A/B/AB
Talk Time/ Standby Time 15 h / 100 h 10 h / 100 h with U-APSD
WiFi Standards 802.11 a/b/g/n 802.11 a/b/g/n/ac, 802.11r, 802.11k MCS 0-7 only, Fast BSS Transition (FT or 802.11r)
SSL Certificates customer managed preinstalled by innovaphone/customer managed
call diversion ok only with DTMF
Headset Connector 2,5 mm 3,5 mm

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the corresponding section below.

WLAN Infrastructure Compatibility

IMPORTANT: Ask innovaphone Presales Team for possible interop configuration recommendations and pitfalls before you order the WiFi equipment and start with the roll-out.

Note that availability and combinations of controllers and access points may be subject to change by the manufacturer and are not in the responsability of innovaphone. Errors and omissions excepted.

innovaphone does not support WLAN infrastructures not listed in this document.

Certified WLAN Platforms
Vendor AP Model(s) Controller Model(s) latest tested SW Version
Aruba AP 207, 214, 215, 224, 225, 275 7000/7200/9000/MX-VA-xxx
Aruba AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 615, 635, 655 7000/7200/9000/MX-VA-xxx
Cisco AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130 WLC 3504, 5520, 8540, vWLC, Mobility Express Solution 8.10.162
Cisco AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852 WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC 8.5.182
Cisco AP 1702, 2702, 3702 Catalyst 9800 17.3.3
Cisco AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136 Catalyst 9800 17.9.3
Cisco Meraki MR20/MR30H/MR33/MR42/MR42E/MR52/MR53/MR53E/MR70/MR74/MR84 (802.11ac wave 2);MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax) - MR 27.7.1
Extreme Networks (Enterasys/IdentiFi) AP 3801, 3805, 3825, 3865, 3935 Extreme Wireless C25, C35, C2110, C5110, C5210, v2110 10.51.10
Extreme Networks (Enterasys/IdentiFi) AP 122, 130, 230, 250, 550, 650 Extreme Cloud AP 10.0r8, Cloud
Extreme Networks (Enterasys/IdentiFi) AP 310i/e, 410i/e, 505i/e, 510i/e, 360i/e, 460i/e, 560 XCC Controllers E1120, E2120, E3120, VE6120/VE6125, VE6120H
Extreme Networks (Enterasys/IdentiFi) AP305c/cx, 410c, 460c, 510c/cx, 650 Extreme Cloud C25, C35, C2110, C5110, C5210, v2110 AP, Cloud
Extreme Networks (Enterasys/IdentiFi) AP310i/e, 410i/e, 460i/e, 510i/e, 650i Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
Fortinet AP1010/1014/1020/822/832, APU221EV/U223EV/U321EV/U323EV/U421EV/U423EV MC1550/3x00/4x00/5000/6000
FortiWLC-50D ,200D, 500D, 1000D, 3000D
FWC- VM-50, 200, 500, 1000, 3000
Huawei AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus V200R022C10SPC100
Juniper Mist AP34, AP45
AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
Mist Cloud 0.12.26354
Ruckus SmartZone ZF R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720 SmartZone platform, vSZ-(H,E,D), SZ100/300

as of September 2023.

DAS Compatibility

Distributed Antenna Systems (DAS) provide a cost-effective solution for extending radio coverage inside large facilities. Simply put, a DAS can be seen as a long cable starting at a base station or access point to which many antennas are connected. While the architecture can be utilized to mitigate certain coverage issues, the innovaphone IP73 was not designed to accommodate for such RF environments. Furthermore it is difficult to ascertain and ensure WLAN reliability in regard to interference, capacity, roaming, location-based services, and some important 802.11n features, such as MIMO. As a consequence thereof, innovaphone will not endorse nor provide RF support for WiFi deployments over any Distributed Antenna System.

WPA3 Compatibility

The IP73 already supports the configuration option for WPA3. However, this should not yet be actively used.
WPA3 is currently only recommended for demo purposes. Support for WPA3 is implemented, but no successful interoperability tests have been performed. WPA3 is not recommended being used except for demo purposes.

U-APSD Required

U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.


IP73 configuration is done via WinPDM-application available at the Software section of the innovaphone App Store. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

PBX Registration

Authentication via client certificate

The recommended way to register an IP73 handset at the innovaphone PBX is SIP over TLS with authentication by a client certificate. The IP73 handset is delivered with a preinstalled device certificate already trusted by an innovaphone PBX.

Prerequisites on the PBX for such type of authentication are:

  • The issuer of the IP73 client certificate is on the Trust List of the PBX gateway
  • The CN of the client certificate used by IP73 equals the MAC address of the IP73 itself (alternatively other CN and registration identity can be used)
  • User Object contains a Device with a Hardware Id matching the MAC address of the IP73

On the IP73 following settings must be configured:

  • VoIP->SIP
    • SIP TLS client certificate: <select certificate with MAC address as CN> or <Automatic if preinstalled certificate is used>
    • SIP Transport: TLS
    • Primary SIP proxy: <IP-address of the PBX>
    • SIP proxy ID: <PBX system name>
    • SIP proxy password: <no password is required>
    • Registration and Authentication identity: MAC address

Authentication via username/hardware id and password

  • VoIP->General->Endpoint ID: username or hardware id on User Object
  • VoIP->SIP
    • SIP Transport: TCP or UDP
    • SIP proxy password: <password on the User Object or PBX System password, depending on Users Device configuration>
    • Registration and Authentication identity: Endpoint ID


ICE is enabled by default. It is required to provide STUN and TURN server configuration under VoIP->General to secure correct negotiation of media channels.

Factory Reset

You can use the local Admin menu on the Phone or the WinPDM Software (Rightclick on the device) to make a Factory Reset.

MWI for IP73

The IP73 can be configured to display a message waiting indication / MWI. You need a programming shell and the WinPDM software (available for download in our Store under the Software tab).

  • Connect programming cradle to the administration PC
  • Install WinPDM and start the application
  • Place IP73 into the programming cradle
  • If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
  • select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
  • Select menu Device (4) and step to Message Centre (5)
  • Insert the number of the voicemail object for the Message Centre Number (6)
  • Insert the user number for the voice mail number (7)

Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.


Central Phonebook Access

Starting with firmware 4.0.0, the device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

Device Configuration via the WinPDM application

  • Device has to be plugged into programming cradle and edited via WinPDM
  • Open Section Device and step to central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried:

Ip73 winpdm centralphonebook config.png

As the bind request generated by the device contains specific formattings such as a prefixed "uid=" , a mandatory organizational unit (ou) parameter and the search base, these must be accepted by the ldap server.

When using innovaphone products as a central telephone directory, the following settings are required:


  • At Services/LDAP add a further query account containing the configured parameters for uid, ou and search base. Example: uid=<userid>,ou=<ou>,<search base dn>


  • Within the PBXManager-Plugin for Contacts, adjust in the configuration settings the used User(LDAP) accordingly.
  • Note: As Contacts only offers one dedicated User(LDAP) setting, this must also be used by other LDAP clients such as desk phones e.g. via configuration templates.


Log Options can be configured in the WinPDM software, under Device->Log.

Remote PCAP Tracing

You can activate the remote PCAP interface and Trace flags directly in the phone configuration (Admin Menu :: Logging :: Mode) or via WinPDM under Device->Log->PCAP capturing: RPCAP.

Only IP traces are available via RPCAP, no innovaphone or device internal traces are logged.

PCAP to file via USB Tracing

It is possible to store PCAP trace file in the pcap folder on the handset by setting in the phone configuration (Admin Menu :: Logging :: Mode) or via WinPDM under Device->Log->PCAP capturing the option "PCAP to file".

To access the file set Device -> General -> USB behavior to "Ask" and select "File transfer", when connect the handset to the WinPDM. Navigate to the folder pcap on the Handset diagnostics drive.

Trace Options

Following additional trace options are available:

  • WLAN Trace
  • Configuration Trace
  • GUI Trace
  • GLI Trace
  • Unite Trace
  • VoIP Trace
  • System Trace
  • Protector Trace
  • SaS Trace
  • Bluetooth Trace
The resulting traces are available via USB file transfer and are encrypted. The encrypted log files can be encrypted by support only.

Logging via Syslog, SFTP or logfile

The handset can be configured to send Syslog messages to a Syslog server, an SFTP server or to a local logfile located in the folder tracelog.

The configuration is available via WinPDM Device -> Log -> Syslog or SFTP.

Handset Error Messages

No network

The No network message indicates missing WLAN connection. It can be caused by wrong settings for SSID, Security, reg. domain and WLAN channels or lack of coverage.

No access

The No access message is caused by missing IP connectivity to the PBX or wrong configuration for authentication at the PBX.


There are additional hidden tools for information and analysing are available.

Handset Device Information
*#34# in the main display
RSSI Indicator
*#76# in the main display. Type again to exit.
Here you find the following information in the display:
  • Line 1: SSID
  • Line 2: Current AP
  • Line 3: Current AP MAC
  • Line 4: Previous AP
  • Line 5: Previous AP MAC
Site Survey Tool
*#77# in the main display.
Admin Menu
Go to the Settings menu and type in 40022

Known Problems

Packet loss and voice quality issues with non-tested WLAN AP and IP73

Issuer: Ascom

Published: 2022-12-07

It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v. there is a critical issue affecting clients using power save (U-APSD).
Data packets will not be transmitted properly to clients in power save.

Affected Ascom Certified Aruba Access Points:
7000/7200/9000/MX-VA-xxx Controllers
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345,
504, 505, 514, 515, 534, 535, 554, 555, 635

Typical symptoms are:
Poor voice quality issues.

Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments.
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point.

The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba.
Should you have any further questions, feel free to reach out to

Bluetooth automatically disabled

Issuer: Ascom

Handset Firmware 4.0.6

Detailed Information
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive.
You can disable WLAN 2.4 band over the WinPDM tool.

Related Articles