Howto:IP62 WLAN WiFi Handset - innovaphone - H323 Testreport
Summary
WLAN Phone IP62.
The IP62 is a WLAN IP phone based on, but not identical to Ascom's i62 product. In contrast to the old IP72 product, the IP62 has no innovaphone firmware running. As such, typical innovaphone features (such as deployment with update server, innovaphone'ish phone user interface including sophisticated function keys etc.) are not available. At the same time, its feature set is not equivalent to the Ascom i62, namely because there are no software-licensable features present and no UNITE support is available (thus no mass deployment, for example). Each IP62 must be configured and maintained with WinPDM. Keep these limitations in mind when you evaluate customer requirements.
To setup the IP62 the programming charger (USB) (order number: 50-00060-021)(Model:DP1-UAAA/1A) and the WinPDM application is needed. The IP62 can not be configured by using a web browser only, as it is with other innovaphone telephones.
It's possible to configure up to four different WLAN's.
The IP62 supports both H.323 and SIP but the following test results relate only to H.323 (in other words, SIP has not been tested).
With firmware 3.4.16 and up, the IP62 will work with myPBX, too.
Certification Status
The tests for this product have been completed and it has been approved as a recommended product (Certification document).
Testing of this product has been finalized December, 2012.
The testing of the Ascom i62 equivalent to innovaphone IP62 is also done by Ascom Wireless Solutions:
Test Setup
PBX: IP800
Phones: IP62, IP222, IP241
Certification Status
Version
Firmware Version / Software:
* IP62 3.4.6 * WinPDM 3.9.4 (Win 7/Win XP)
Hardware Version:
* IP62 HW Type:902202, HW rev: G5, Production date:12w12 * innovaphone WLAN Desktop Programming Charger (Model: DP1)
innovaphone Firmware:
* V9 Hotfix 15
Device Setup
| Tested feature | Result |
|---|---|
| Register Device w/o specific configuration (requires DHCP, GK detection and “magic” alias) | No, it is required to use WinPDM. |
| DHCP is default | Ok |
| DHCP yields timeserver and time displays correctly | Takes time from PBX if no fixed NTP-IP is configured |
| SNTP config has TZ string for timezone/dst autoconfig | Yes. Different time zones are choosable |
| DHCP yields correct default gateway | Yes |
| Device supports magic registration (e.g. by serial) | No |
| GK discovery works | No. Numbers must configured in WinPDM and associate to devices. General settings as language, Network, GK-ID-IP can be deployed with templates, but device must fit in the (programmable)charger |
| Fixed GK registrations works | Yes |
| 2nd GK is supported | Yes |
| Changing registrations between GK1 and GK2 | Yes |
| Registrations supports GK-ID | Yes |
| Device registers w/o Extension (just by name) | No. Number is needed, too. Hardware-ID in User-Object must be the name |
| Device registers by name with non-latin1 characters (e.g. UserÄÖÜ) | Yes |
| Device registers by extension | Yes |
| Device registers with H.235 password | Yes, but it's confusing in WinPDM. UserObject password can found in WinPDM in field gatekeeper password. |
| Device registers multiple identities | No, not within the phone. It's possible to add identities in WinPDM and associate and change them to a phone (reboot after sync. required) |
| Device sends NAT - keepalive messages | Yes |
| PBX redirect (UserObject on Master/Phone at Slave registered) | Yes |
| Physical Location (@PBX) correct? | Yes |
| Device can configure IP address, GK attributes (gk-id, gk-ip, alias) from DHCP (vendor specific) | No. Only domain name. 1stGK, 2ndGK, GK-Identifier where still empty. Codec must be set fix with WinPdm. |
| Device refreshes the PBX registration | Yes |
| Device supports SRTP via SDES | Yes |
| Device supports SRTP via DTLS | No |
| Device supports HTTPS | No |
| Device supports VAD (Voice activity detection) | No |
| Supported menu languages | 18 languages |
Test Results
Basic Call
| Tested feature | Result |
|---|---|
| call using g711a | yes |
| call using g711u | yes |
| call using g729 | yes |
| call using g722 | yes |
| Overlapped sending | yes |
| Early media channel | yes |
| Device shows called id number | yes, if Name is not known or is not saved in contacts. Otherwise only name is displayed |
| Device shows called id name | yes |
| Device shows called id display info | Yes |
| CGPN can be suppressed | No |
| Reverse Media Negotiation | Yes |
| Device shows CDPN/CGPN on incoming call | NO! Internal calls=ObjectName and for external calls -extern- is displayed. But number is saved in call list (if editing the call) |
| Device shows CDPN/CGPN on outgoing call | NO! Internal calls=ObjectName and for external calls -extern- is displayed. But number is saved in call list (if editing the call) |
| Device shows connected number | Yes, if Name is not available. But not name and number. |
| Device shows diverting number | No number. Shows only -redirecting- if call from CFU comes in. If CFU on IP62 is configured target number is displayed |
| Device supports distinctive ringing | Yes |
| Device supports asymmetric codec negotiation | n.a. |
| Device supports codec renegotiation during a conversation | Yes |
| Device shows correct display message in case of busy CDPN | Yes |
| Device shows correct display message in case of not existing CDPN | Yes. -Invalid number- if number doesn't exist or -no response- if number exist but i.e. is not registered |
| Device shows correct display message in case that the call is declined | Yes. Inclusive call back request. |
| SOAP Call works? | Yes, with WH1_v4.1.12.pkg |
| Device supports display updates during call(needed for Directory Search object) | Yes |
| Long Time Call (>30 min) works? | yes. 45 min. tested. |
| Registration redirecting works? | Yes |
| Incoming SRTP call (SDES) - SRTP not enabled on DUT | Yes, call established without SRTP. |
| Incoming SRTP call (SDES) - SRTP enabled on DUT | Yes, call established with SRTP. |
| Incoming SRTP call (DTLS) - SRTP not enabled on DUT | Yes, call established without SRTP. |
| Incoming SRTP call (DTLS) - SRTP enabled on DUT | Yes, call established without SRTP. |
| Voice Quality OK? | Yes, with WH1_v4.1.12.pkg |
DTMF
| Tested feature | Result |
|---|---|
| DTMF tones sent correctly | yes |
| DTMF tones received correctly | Yes (RFC 2833 RTP Event) |
Hold/Retrieve
| Tested feature | Result |
|---|---|
| Device handles incoming hold correctly | Yes, with WH1_v4.1.12.pkg |
| Device can put a call on hold using correctly | Yes |
Transfer with consultation
| Tested feature | Voice Ok? | MoH Ok? |
|---|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes | Yes |
| inno1 calls inno2. inno1 transfers to testphone. | Yes | Yes |
| inno1 calls testphone. inno1 transfers to inno2. | Yes | Yes, if U-APSD is disabled MOH is hearable without cuts. |
| inno1 calls testphone. testphone transfers to inno2. | Yes | Yes |
| testphone calls inno1. inno1 transfers to inno2. | Yes | Yes |
| testphone calls inno1. testphone transfers to inno2. | Yes | Yes |
Transfer with consultation (alerting only)
| Tested feature | Voice Ok? | MoH Ok? |
|---|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes | Yes |
| inno1 calls inno2. inno1 transfers to testphone. | Yes | Yes |
| inno1 calls testphone. inno1 transfers to inno2. | Yes | If U-APSD is disabled MOH and Ringback is hearable without cuts. |
| inno1 calls testphone. testphone transfers to inno2. | No. Transfer with consultation must be connected to transfer. | Yes |
| testphone calls inno1. inno1 transfers to inno2. | Yes | If U-APSD is disabled MOH and Ringback is hearable without cuts. |
| testphone calls inno1. testphone transfers to inno2. | No. Transfer with consultation must be connected to transfer. | Yes |
Blind Transfer
| Tested feature | Voice Ok? |
|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes |
| inno1 calls inno2. inno1 transfers to testphone. | Yes |
| inno1 calls testphone. inno1 transfers to inno2. | Yes |
| inno1 calls testphone. testphone transfers to inno2. | Yes |
| testphone calls inno1. inno1 transfers to inno2. | Yes |
| testphone calls inno1. testphone transfers to inno2. | Yes |
Blind Transfer (alerting only/deflection)
| Tested feature | Voice Ok? |
|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes |
| inno1 calls testphone. testphone transfers to inno2. | No. Call must be established to transfer |
| testphone calls inno1. inno1 transfers to inno2. | No ringback tone hearable on IP62 after inno1 blindtransfer to inno2 (#86202) |
Broadcast Group & Waiting Queue
| Tested feature | Result |
|---|---|
| testphone makes call to a Broadcast Group. inno1 picks up. | Yes |
| inno1 makes call to a Broadcast Group. testphone picks up. | Yes |
| testphone makes call to a Waiting Queue. inno1 picks up before announcement is played. | Yes |
| testphone makes call to a Waiting Queue. inno1 picks up after announcement is played. | Yes |
| inno1 makes call to a Waiting Queue. testphone picks up. | Yes |
DTMF Features
| Tested feature | Result |
|---|---|
| CFU Activate/Deactivate | Yes |
| CFB Activate/Deactivate | Yes, but no icon/info for enabled CFB |
| CFNR Activate/Deactivate | Yes, but no icon/info for enabled CFB |
| Pickup Group | Yes, but no pickup-key and/or Display Info for incoming call |
| Pickup Directed | Yes, but no pickup-key and/or Display Info for incoming call |
| Park/Unpark | Yes |
| Park To/Unpark From | Yes |
| Call Completion Busy | Yes. But with *37*$# the call back number is not shown. Instead you see on IP62 Display "Extern". You can use instead the call-back function from IP62 (shows correct name) |
| Call Completion Cancel | Yes |
| Join Group/Leave Group | Yes |
| Join All Groups/Leave All Groups | Yes |
| Enable mobility/Disable mobility | Yes |
| Enable mobility cw/Disable mobility cw | Yes |
| Set presence | Yes. Our phones can see the presence state of IP62. But, IP62 can't see presence state of our phones. |
Other Features
Directory
| Tested feature | Result |
|---|---|
| Device built-in directory exists | Yes |
| Can be dialled from | Yes |
| Does CLI resolution | Yes |
| display update if directory object is used? | Yes |
| Tested feature | Result |
|---|---|
| External LDAP Server supported | No |
| Can be dialled from | No |
| Does CLI resolution | No |
| display update if directory object is used? | No |
Keys
| Tested feature | Result |
|---|---|
| Device has speed dial keys | Yes |
| Device has programmable function keys | Yes |
| Device has partner keys | No |
CTI Features (with SOAP / TAPI / myPBX)
| Tested feature | Result |
|---|---|
| User Call - outgoing call | OK |
| User Connect - Answer incoming call | NOK - Call it's not answered by the IP62. |
| User Reject - Reject alerting call | OK |
| User Disconnect - Disconnect active call | OK |
| User Hold - Put connected call on hold | OK |
| User Hold Retrieve - Retrieve call on hold | OK |
| User Transfer - Transfer with Consult | NOK - Could not initiate second call. |
| User Transfer - Transfer with Consult (Alerting only) | NOK - Could not initiate second call. |
| User Transfer - Blind Transfer | OK |
| Switch Calls / Held Active Call automatically | NOK - Could not initiate second call |
| 3PTY - Make 3rd Party Call | NOK - Could not initiate second call. |
| Park Call | OK |
| Retrieve Parked Call | NOK - Generates a second redirected call on the IP62. |
| Pickup Call | NOK - Generates a second redirected call on the IP62. |
| Connected Number Update on Display | OK |
| CFU indication on Display | OK |
| Send DTMFs via CTI | NOK |
Note: CTI Features were tested with v11r1 Sr2 and IP 62 sw 5.1.30
Basic-Configuration
This section describes how to configure the innovaphone PBX and WLAN Phone IP62 by using WinPDM and the WLAN programming charger. To find out how to install the WinPDM software and the programming charger on a Windows PC, please take a look into the WinPDM installation manual.
1. Push the IP62 in the programming charger. In the tab "Devices" it's marked as online now.
2. Change to the tab numbers. Here you can see that the IP62 is associated with number 202 at the moment and some other interesting things like; which template is used, last login, etc.
3. How to assign a new number? Click on "New+" and a new window will open...
4. ...where you can set the number...
5. ...which you have configure in the PBX.
6. Then right click on the line with the new number, in our example 204, and click on "Associate with device"
7. In the new window choose you device and click on ok. After it, the IP62 will synchronise with the number and the settings (what we must do in the next steps) for this number
8. Do a right click on our new number and choose "Edit parameters"
9. Set your WLAN configuration (four different networks are possible, the active one of the four can you set under "General") and all other things what are necessary. There is no need to save the configuration as long as you set the configs. Changed settings are dark-blue and after a click on "ok" all saved settings are green.
10. Under "VoIP" -> "H.323" -> "Gatekeeper password" means the password, which you configured at the user object in the PBX.
11. After you plug the IP62 out of the charger, it will restart automatically and the new configuration is active.
Maintenance
There are additional tools and informations for analysing the IP62 in the admin menu. You can reach the menu by entering the Settings menu and type in “40022” on the keypad.
For example, to activate pcap tracing:
- Enable pcap in the IP62 GUI: “Settings -> AdminMenu* -> Logging -> Logging mode
- Choose what should be traced: “Settings -> AdminMenu* -> Logging -> Extended logging
For further configuration and available options take a look in the Installation and Operation Manual of the Portable Device Manager (aka PDM)
Known Issues
The latest firmware version 6.2.7 is based on innovaphone's v12r1 firmware. It is not compatible with v13 WebRTC endpoints (e.g. SoftphoneApp) that use RTCP-MUX. If you plan to use ip62 in a v13 environment, media relay must be enabled at the User object of the IP62 device (Hardware ID).