Reference:IP62 WLAN WiFi Wireless IP-Phone
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
Requirements
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.
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.
Vendor | AP Model(s) | Controller Model(s) | SW Version(s) |
---|---|---|---|
Aerohive Networks | AP 120, 121, 141, 330, 350, 370, 550 | N/A | 5.1r5, 6.1r2, 6.5r10, 6.8r3, 8.0r1, 8.4r5, 18.10.1.10 |
Aruba Networks | AP 60, 61, 65, 70 | 600, 3000, 6000 Series | 3.4.2.0 |
Aruba Networks | AP 105, 120, 121, 124, 125 | 600, 3000, 6000 Series | 5.0.3.0, 6.0.1.0 |
Aruba Networks | iAP 92, 93, 104, 105, 114, 115, 124, 125, 134, 135, 204, 214, 224, 275 | 600, 3000, 6000, 7000, 7200 | 6.2.1.2, 6.3.1.3, 6.4.2.0 6.4.2.6, 6.4.3.4, 6.5.4.0 |
Aruba Networks | iAP 103, 205, 215, 225 | 600, 3000, 6000, 7000, 7200 | 6.2.1.2, 6.3.1.3, 6.4.2.0, 6.4.2.6, 6.4.3.4, 6.4.4.8, 6.5.4.0, 8.2.1.0 |
Aruba Networks | iAP 103, 204, 205, 214, 215, 224, 225, 314, 315, 324, 325 | controllerless | 6.5.4.3 |
Aruba Networks | AP 207, 214, 215, 224, 225, 275, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345 | 7000, 7200 | 6.5.4.0, 8.2.1.0, 8.3.0.3, 8.4.0.1 |
Aruba Networks | AP 324/325 | 600, 3000, 6000, 7000, 7200 | 6.4.4.6, 6.4.4.8, 6.5.4.0, 8.2.1.0 |
Alcatel-Lucent | Same as Aruba Networks | 4000, 6000 Series | Same as Aruba Networks |
Avaya | AP 8020, 8020-E | 8180 | 1.1.0.113, 2.0.0.084, 2.1.0.102 |
Avaya | AP 9132, 9133 | N/A | 7.5.2 |
Brocade | AP 650, 6511, 6532, 7131 | RFS4000, 6000, 7000 NX9000 |
5.1.0.0, 5.4.0.0, 5.4.4.0 |
Cisco (Autonomous) | 1230, 1240 | N/A | 12.4(21a)JY / 12.3(8)JED |
Cisco (Autonomous) | 1140, 1250, 1260 | N/A | 12.4(25d)JA1 |
Cisco | AP 1130, 1230, 1240, 1140, 1250, 1260, 1600, 1700, 2600, 2700, 2800, 3500, 3600, 3700, 3800 | WLC 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.4.100.60, 7.6.100, 8.0.100, 8.1.20, 8.2.110, 8.3.102, 8.3.112, 8.3.121, 8.5.103 |
Cisco | AP 1142, 1252, 1262, 1602, 1702, 2602, 2702, 3502, 3602, 3702, 1832, 1852, 2802, 3802 | WLC 2xxx, 440x, 550x WISM, 3750G Cisco Flex 7500/8500 |
8.5.120, 8.5.140 |
Cisco | AP 1702, 1832, 1852, 2702, 2802, 3702, 3802, 4800, 9115, 9117 | WLC 3504, 5520, 8540 | 8.6.101, 8.7.106, 8.8.111, 8.9.100 |
Cisco | AP 1830/1850 | WLC 2xxx, 440x, 550x WISM, 3750G Cisco Flex 7500/8500 |
8.1.131 |
Cisco | AP 1140, 1250, 1260, 1600, 2600, 2700, 3500, 3600, 3700 | 3650, 3850, 5760 | IOS XE 03.03.04, 03.07.03 |
Extreme Networks (Enterasys/IdentiFi) | AP 3705, 3710, 3715, 3765, 3767, 3801, 3805, 3825, 3865, 3935 | C25, C35, C2110, C5110, C5210, v2110 | 07.41.01, 08.01.04, 08.11.06, 08.31.02, 09.15.06, 10.11.04 10.41.03 |
Extreme Networks (WiNG) | AP 622, 650, 6511, 6522, 6532, 7131, 7522, 7532, 8132, 8432 | RFS/NX/VX/EX | 5.1.0.0, 5.4.0.0, 5.4.4.0, 5.5.5.0, 5.8.3.0, 5.9.1.2 |
Extricom | EXRP-30n, EXRP-40En | MultiSeries 500, 1000 | 4.5.09 |
HP | MSM 422, 430, 460, 466 | MSM710/720/760 | 5.7.1.0 |
HP | MSM 425 and MSM 430/460/466 | MSM830/850/870, WX500x controllers 10500/7500 20G Unified Wires-WLAN modules |
3507P26 |
Juniper (Trapeze) | MP/WLA 321, 322, 422, 522, 532 | MX/WLC 2, 8, 200, 8x0, 2800 | 7.3.4.4, 7.6.2.3, 8.0.2.2 |
Lancom Systems | L-3xx(9.10), L-4xx(9.10), L-8xx(9.18) | WLC 4006+, 4025+, 4100 (9.10) | 9.10/9.18 |
Meraki | MR20, MR30H, MR33 MR42, MR42E, MR52, MR53, MR53E MR70, MR74, MR84 |
N/A | 25.9 |
Meru Networks | AP200, 300 | MC1000, 1500, 3x00, 4x00, 5000 | 4.0-150 |
Meru Networks | AP300, 1000 | MC1500, 3x00, 4x00, 5000 | 5.0-87 5.1-47(Requirement for AP1000) |
Meru Networks | AP300, 332, 1000, 832, 822 | MC1500, 1550, 3x00, 4x00, 5000, 6000 | 5.3.50 (Requirement for AP332) 6.1-3-5 |
Fortinet (Meru Networks) | AP301, 302, 310, 311, 320, AP332 (i/e variants), AP822, 832 (i/e variants), AP1010, 1014, 1020 (i/e variants), U421EV/U423EV | MC1550, 3x00, 4x00, 5000, 6000 | 7.0-8-0, 8.2-4-0, 8.4-0-7, 8.5-0-6 |
Ruckus | ZF 7962, 7363, 7343, 7341, 7372, 7982 | ZD 1X00, 3000, 5000 | 9.1.1.0v, 9.4.2.0, 9.7.0.220, 9.7.1.0.17, 10.2.1.0 |
Ruckus | SmartZone ZF7372, 7982 & R300, R310, T300, R500, R510, R600, R610, R710 | SmartZone platform vSZ-(E,HD), SCG, SZ100 | 3.2.1.0.139, 9.13.0.0.232, 3.5.0.0.808, 3.5.1.0.862, 5.1.1.0.598 |
Xirrus | XR-620, 630 | N/A | 7.5.0 |
Zebra Technologies (Motorola) | AP 622, 650, 6511, 6522, 6532, 7131, 7522, 7532, 8132 | RFS, NX, VX, EX | 5.1.0.0, 5.4.0.0, 5.4.4.0, 5.5.5.0, 5.8.3.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.
Configuration
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-Configuration-Manual
- Installation and Operation Manual of the Portable Device Manager (aka PDM)
ICE/TURN
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.
Troubleshooting
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 http://1.2.3.4/cfg.txt
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: http://1.2.3.4/CMD0/mod_cmd.xml?cmd=xml-config&xsl=tracing.xsl. 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
Shortcuts
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
Support of "802.11d" standard
Some manufacturers do not support the "802.11d" (World Mode) standard.
Currently known Manufacturers:
- "Ubiquiti" disabled 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)
Support of RTCP-MUX
Calls of WebRTC endpoints directly called by the IP62 are not possible.
No support for RTCP-MUX is included in the IP62 prior FW version 6.0.0, so WebRTC endpoints are not supported directly by the IP62 in this case.
A media relay between IP62 and a WebRTC endpoint could be used as workaround.
Solution: Upgrade IP62 firmware to version 6.0.6 or higher
Dropped communication during calls
There are reports about dropped IP62 calls paired with Aruba AP225 in 802.11n mode.
Solution: Associate IP62 in non‐11n mode (Use WinPDM network setting 802.11 protocol:802.11a or 802.11b/g).
Firmware downgrade not possible
Ascom statement about firmware downgrade issues for i62 / innovaphone OEM IP62:
DOWNGRADE RESTRICTIONS OF I62 SOFTWARE Published: 2019-04-23 - Issue: 35:19 Just as any other product, the WiFi phone i62 is upgraded to the latest software when going through the repair process. Normally the software can be downgraded to match the software version for other handsets at a site. If the i62 phone’s PCB is replaced in the repair process, it will be equipped with hardware that is incompatible with older software versions. It will be returned after repair with a software version 6.1.0 (or later), and it cannot be downgraded to software version earlier than 6.0.6. The hardware revision printed on the product label indicates if the software can be downgraded or not. If the revision number is 3A or later, software cannot be downgraded to version prior 6.0.6. An i62 going through the repair process will have the revision number set to the latest if the PCB has been replaced, to keep track of compatibility between the hardware and software version. Note: The same restriction is also valid when adding a new i62 phone to an old system. New phones are delivered with the new hardware revision, and they cannot be downgraded to a software version prior 6.0.6
It is recommended to use the latest official firmware to avoid problems that may have already been solved.
Related Articles
Howto:IP62 WLAN WiFi Handset - innovaphone - H323 Testreport