Reference:IP73 WLAN WiFi Wireless IP-Phone
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)
Requirements
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.
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 |
Although the IP73 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
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.
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 | 8.6.0.5 |
Aruba | AP 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 554, 555 | 7000/7200/9000/MX-VA-xxx | 8.7.1.1 |
Cisco | AP 1702, 2702, 3702, 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130 | 3504, 5520, 8540, vWLC, Mobility Express Solution | 8.10.105 |
Cisco | AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130 | 3504, 5520, 8540, vWLC, Mobility Express Solution | 8.10.162 |
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.7.1 |
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 20.1.1.3 |
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 | 05.16.01.0025 |
Extreme Networks (Enterasys/IdentiFi) | AP305c/cx, 410c, 460c, 510c/cx, 650 | Extreme Cloud C25, C35, C2110, C5110, C5210, v2110 | AP 10.2.4.0, Cloud 20.1.1.3 |
Extreme Networks (Enterasys/IdentiFi) | AP310i/e, 410i/e, 460i/e, 510i/e, 650i | Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000 | 7.5.2.0 |
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 |
8.5-2-5 |
Ruckus | SmartZone ZF R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720 | SmartZone platform, vSZ-(H,E,D), SZ100/300 | 5.2.0.0.699 |
as of February 2022.
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.
Configuration
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/TURN
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.
Troubleshooting
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.
Shortcuts
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
- A registration via Reverse Proxy with TLS authentication is not supported at the moment. A workaround with username/password can be implemented. A fix of the PBX software will follow.