Reference:IP62 WLAN WiFi Wireless IP-Phone

From innovaphone-wiki

Jump to: navigation, search

This article describes the IP62 WLAN/WiFi wireless IP-Phone, differences to the deprecated IP72 Wireless IP-Phone and a list of compatible WLAN Infrastructures.


Applies To

This information applies to:

  • innovaphone IP62


To perform configuration changes on the IP62 device a desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required. The programming kit enables to connect the IP62 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 IP72 IP62 Description
Messaging YES NO
LDAP Phone Book YES NO
Talk Time/ Standby Time 10 h / 40 h 15 h / 100 h with U-APSD
WiFi Standards 802.11 a/b/g 802.11 a/b/g/n
Supported Languages Latin-1 only UTF-8, 18 Languages

Although the IP62 does not have access to a central LDAP phone book, the solution described in Reference9:PBX/Objects/Directory_Search can be used.

WLAN Infrastructure Compatibility

Note: Update of this list is discontinued and represents latest state as mentioned below.

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) SW Version(s)
Aerohive Networks AP 120, 121, 141, 330, 350, 370, 550N/A5.1r5, 6.1r2, 6.5r10,
6.8r3, 8.0r1, 8.4r5,
Aruba NetworksAP 60, 61, 65, 70600, 3000, 6000 Series3.4.2.0
Aruba NetworksAP 105, 120, 121, 124, 125600, 3000, 6000 Series5.0.3.0,
Aruba NetworksiAP 92, 93, 104, 105, 114, 115, 124, 125, 134, 135, 204, 214, 224, 275600, 3000, 6000, 7000, 72006.2.1.2,,,,
Aruba NetworksiAP 103, 205, 215, 225600, 3000, 6000, 7000, 72006.2.1.2,,,,,,,
Aruba NetworksiAP 103, 204, 205, 214, 215, 224, 225, 314, 315, 324, 325controllerless6.5.4.3
Aruba NetworksAP 207, 214, 215, 224, 225, 275, 304, 305, 314, 315, 324, 325, 334, 335, 344, 3457000, 72006.5.4.0,,,
Aruba NetworksAP 324/325600, 3000, 6000, 7000, 72006.4.4.6,,,
Alcatel-LucentSame as Aruba Networks4000, 6000 SeriesSame as Aruba Networks
AvayaAP 8020, 8020-E81801.1.0.113,,
AvayaAP 9132, 9133N/A7.5.2
BrocadeAP 650, 6511, 6532, 7131RFS4000, 6000, 7000
Cisco (Autonomous)1230, 1240N/A12.4(21a)JY / 12.3(8)JED
Cisco (Autonomous)1140, 1250, 1260N/A12.4(25d)JA1
CiscoAP 1130, 1230, 1240, 1140, 1250, 1260, 1600, 1700, 2600, 2700, 2800, 3500, 3600, 3700, 3800WLC 2xxx, 440x, 550x
WISM, 3750G
Cisco Flex 7500/8500
6.0.196, 7.0.98, 7.0.220,
7.2.110, 7.3.101,,
7.6.100, 8.0.100, 8.1.20,
8.2.110, 8.3.102, 8.3.112,
8.3.121, 8.5.103
CiscoAP 1142, 1252, 1262, 1602, 1702, 2602, 2702, 3502, 3602, 3702, 1832, 1852, 2802, 3802WLC 2xxx, 440x, 550x
WISM, 3750G
Cisco Flex 7500/8500
8.5.120, 8.5.140
CiscoAP 1702, 1832, 1852, 2702, 2802, 3702, 3802, 4800, 9115, 9117WLC 3504, 5520, 85408.6.101, 8.7.106, 8.8.111,
CiscoAP 1830/1850WLC 2xxx, 440x, 550x
WISM, 3750G
Cisco Flex 7500/8500
CiscoAP 1140, 1250, 1260, 1600, 2600, 2700, 3500, 3600, 37003650, 3850, 5760IOS XE 03.03.04, 03.07.03
Extreme Networks (Enterasys/IdentiFi) AP 3705, 3710, 3715, 3765, 3767, 3801, 3805, 3825, 3865, 3935C25, C35, C2110, C5110, C5210, v211007.41.01, 08.01.04, 08.11.06,
08.31.02, 09.15.06, 10.11.04
Extreme Networks (WiNG) AP 622, 650, 6511, 6522, 6532, 7131, 7522, 7532, 8132, 8432RFS/NX/VX/EX,,,,,
ExtricomEXRP-30n, EXRP-40EnMultiSeries 500, 10004.5.09
HP MSM 422, 430, 460, 466 MSM710/720/760
HP MSM 425 and MSM 430/460/466 MSM830/850/870, WX500x controllers
10500/7500 20G Unified Wires-WLAN modules
Juniper (Trapeze)MP/WLA 321, 322, 422, 522, 532MX/WLC 2, 8, 200, 8x0, 28007.3.4.4,,
Lancom SystemsL-3xx(9.10), L-4xx(9.10), L-8xx(9.18)WLC 4006+, 4025+, 4100 (9.10)9.10/9.18
MerakiMR20, MR30H, MR33
MR42, MR42E, MR52, MR53, MR53E
MR70, MR74, MR84
Meru NetworksAP200, 300MC1000, 1500, 3x00, 4x00, 50004.0-150
Meru NetworksAP300, 1000MC1500, 3x00, 4x00, 50005.0-87
5.1-47(Requirement for AP1000)
Meru Networks AP300, 332, 1000, 832, 822MC1500, 1550, 3x00, 4x00, 5000, 6000 5.3.50 (Requirement for AP332)
Fortinet (Meru Networks)AP301, 302, 310, 311, 320, AP332 (i/e variants), AP822, 832 (i/e variants), AP1010, 1014, 1020 (i/e variants), U421EV/U423EVMC1550, 3x00, 4x00, 5000, 6000 7.0-8-0, 8.2-4-0, 8.4-0-7,
RuckusZF 7962, 7363, 7343, 7341, 7372, 7982 ZD 1X00, 3000, 50009.1.1.0v,,,,
RuckusSmartZone ZF7372, 7982 & R300, R310, T300, R500, R510, R600, R610, R710SmartZone platform vSZ-(E,HD), SCG, SZ1003.,,,,
XirrusXR-620, 630 N/A7.5.0
Zebra Technologies (Motorola)AP 622, 650, 6511, 6522, 6532, 7131, 7522, 7532, 8132RFS, NX, VX, EX5.1.0.0,,,,
Zyxel NWA5123-AC, WAC5302D-S, NXC2500, NXC5500, WAC6100 series, WAC6500 series V5.0.0

as of October, 21st 2019.

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 IP62 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.


IP62 configuration is done via WinPDM-application available at wireless package on download-page. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

For offered configuration options refer to


IP62-firmware 6.0.0 and higher supports TURN and TLS-registration with certificate.

By default, ICE mechanism is deactivated. Activation can be done via WinPDM according to following screenshot. ICE activation also enables TURN-configuration field.


NB: Use of ICE also requires active STUN Server to be configured.

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.


You can access the light WebUI on the Device with the default login credentials Username: admin and Password: changeme

Local Syslog

The local Syslog file of the handset can be downloaded via Web UI of the IP62.

Config Download

You can download the configuration via

Remote PCAP

You can activate the remote pcap interface and Trace flags directly in the phone configuration (Admin Menu :: Logging :: Mode) or remote with the following commands.

config add PCAP0 /enable on
config add IP0 /ip-trace on
config write
config activate

If you need specific tracing flags you can activate it here: Dont use Enable RPCAP or Write PCAP to URL on the WebUI, it will not work.

After Tracing you should deactivate all activated Flags and deactivate the rpcap interface. To deactivate the remote pcap interface you can setup the following commands or easyliy reboot the device

config rem PCAP0 /enable
config write
config activate


There are additional hidden tools for information and analysing in the IP62.

Handset Device Information
*#34# in the main display
RSSI Indicator
*#76# in the main display. Type agagin to exit.
Here you 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

It is recommended to use the latest official firmware to avoid problems that may have already been solved.

Log-in or roaming may not work in 802.11d "World Mode"

Some manufacturers do not support the "802.11d" (World Mode) standard. This has been reported for Ubiquiti, which disabled support for this since firmware 3.1.12 (2014)

Solution: If your clients show problems when logging in or roaming, try to disable the "World Mode" via WinPDM. (Network::Network-X::World mode regulatory domain)

Calls to WebRTC endpoints do not work prior to firmware version 6.0.6

Calls of WebRTC endpoints directly called by the IP62 are not possible as there is no support for RTCP-MUX in the IP62 prior FW version 6.0.6.

Workaround: Use a media relay performing entity between IP62 and a WebRTC endpoint.

Solution: Upgrade IP62 firmware to version 6.0.6 or higher

Dropped calls with 802.11n

Some manufacturers do not support the "802.11n" standard. This has been reported for Aruba AP225.

Solution: Associate IP62 in non‐11n mode (Use WinPDM network setting 802.11 protocol:802.11a or 802.11b/g).

Firmware downgrade may not be possible after repair

During a repair in an RMA process, the IP62 firmware is generally updated to the then-current version. Normally the software can be downgraded to match the software version for other handsets at a site. However, if during the repair process the PCB needs to be replaced, it may happen that the previous firmware does not support the new PCB. In this case the downgrade is not possible obviously.

Note that this also may apply to new handsets added to an existing installation.

As mentioned above, it is recommended to use the latest official firmware anyway to avoid problems that may have already been solved.

Related Articles

Howto:IP62 WLAN WiFi Handset - innovaphone - H323 Testreport

Howto:WLAN Interop Test Description

Howto:MXR-2 Mobility Exchange - Trapeze - Testreport

Personal tools