Ascom Winpdm Software

The Portable Device Manager (PDM) is an all-in-one portable handset management tool for the FreeNET System. The PDM software application, with a web browser-based environment and USB programming cradle, provides a simple administration process for portable handset subscription and configuration. Publisher: ascom.

  1. Ascom Winpdm Software Update
  2. Ascom Winpdm Software Update
  3. Ascom Winpdm Software Free

Ascom software is designed to work specifically with Ascom hardware and solutions. At the same time, our software is open and interoperable, allowing smooth integration with third-party systems, devices and existing ICT infrastructure. Also, having such a broad portfolio of native software means we can customize solutions to. For WinPDM, refer to the Installation and Operation Manual, Portable Device Manager (WinPDM), Windows Version. 3.1 Preparing WinPDM or Device Manager for Handset Handling If the parameter definition file (“.def” file) for the handset is not present in the WinPDM or the Device Manager, it can be added by following the procedure below.

Ascom Equipment Software / Firmware Version Ascom Device Manager running on Windows PC (WinPDM) 3.13.4 Ascom i63 Wireless Handset V2.2.8 Ascom approved Wi-Fi Access Point Ascom approved software version. Ascom WinPDM, Free Download by ascom. PDM is an all-in-one portable handset management tool for the FreeNET System. Description: The Ascom Portable Device Manager (PDM) is a software application that provides firmware updates via a universal serial bus (USB) cradle or over-the-air.

From innovaphone-wiki

Jump to: navigation, search
  • 7Test Results
  • 8Other Features

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:

Ascom Winpdm Software Update

Hardware Version:

innovaphone Firmware:

Device Setup

Tested featureResult
Register Device w/o specific configuration (requires DHCP, GK detection and “magic” alias)No, it is required to use WinPDM.
DHCP is defaultOk
DHCP yields timeserver and time displays correctlyTakes time from PBX if no fixed NTP-IP is configured
SNTP config has TZ string for timezone/dst autoconfigYes. Different time zones are choosable
DHCP yields correct default gatewayYes
Device supports magic registration (e.g. by serial)No
GK discovery worksNo. 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 worksYes
2nd GK is supportedYes
Changing registrations between GK1 and GK2Yes
Registrations supports GK-IDYes
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 extensionYes
Device registers with H.235 passwordYes, but it's confusing in WinPDM. UserObject password can found in WinPDM in field gatekeeper password.
Device registers multiple identitiesNo, 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 messagesYes
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 registrationYes
Device supports SRTP via SDESYes
Device supports SRTP via DTLSNo
Device supports HTTPSNo
Device supports VAD (Voice activity detection)No
Supported menu languages18 languages

Test Results

Basic Call

Tested featureResult
call using g711ayes
call using g711uyes
call using g729yes
call using g722yes
Overlapped sendingyes
Early media channelyes
Device shows called id numberyes, if Name is not known or is not saved in contacts. Otherwise only name is displayed
Device shows called id nameyes
Device shows called id display infoYes
CGPN can be suppressedNo
Reverse Media NegotiationYes
Device shows CDPN/CGPN on incoming callNO! 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 callNO! Internal calls=ObjectName and for external calls -extern- is displayed. But number is saved in call list (if editing the call)
Device shows connected numberYes, if Name is not available. But not name and number.
Device shows diverting numberNo number. Shows only -redirecting- if call from CFU comes in. If CFU on IP62 is configured target number is displayed
Device supports distinctive ringingYes
Device supports asymmetric codec negotiationn.a.
Device supports codec renegotiation during a conversationYes
Device shows correct display message in case of busy CDPNYes
Device shows correct display message in case of not existing CDPNYes. -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 declinedYes. 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 DUTYes, call established without SRTP.
Incoming SRTP call (SDES) - SRTP enabled on DUTYes, call established with SRTP.
Incoming SRTP call (DTLS) - SRTP not enabled on DUTYes, call established without SRTP.
Incoming SRTP call (DTLS) - SRTP enabled on DUTYes, call established without SRTP.
Voice Quality OK?Yes, with WH1_v4.1.12.pkg

DTMF

Tested featureResult
DTMF tones sent correctlyyes
DTMF tones received correctlyYes (RFC 2833 RTP Event)

Hold/Retrieve

Tested featureResult
Device handles incoming hold correctlyYes, with WH1_v4.1.12.pkg
Device can put a call on hold using correctlyYes

Ascom Winpdm Software Update

Transfer with consultation

Tested featureVoice Ok?MoH Ok?
inno1 calls inno2. inno2 transfers to testphone.YesYes
inno1 calls inno2. inno1 transfers to testphone.YesYes
inno1 calls testphone. inno1 transfers to inno2.YesYes, if U-APSD is disabled MOH is hearable without cuts.
inno1 calls testphone. testphone transfers to inno2.YesYes
testphone calls inno1. inno1 transfers to inno2.YesYes
testphone calls inno1. testphone transfers to inno2.YesYes

Transfer with consultation (alerting only)

Tested featureVoice Ok?MoH Ok?
inno1 calls inno2. inno2 transfers to testphone.YesYes
inno1 calls inno2. inno1 transfers to testphone.YesYes
inno1 calls testphone. inno1 transfers to inno2.YesIf 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.YesIf 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 featureVoice 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 featureVoice 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)
Software

Broadcast Group & Waiting Queue

Tested featureResult
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 featureResult
CFU Activate/DeactivateYes
CFB Activate/DeactivateYes, but no icon/info for enabled CFB
CFNR Activate/DeactivateYes, but no icon/info for enabled CFB
Pickup GroupYes, but no pickup-key and/or Display Info for incoming call
Pickup DirectedYes, but no pickup-key and/or Display Info for incoming call
Park/UnparkYes
Park To/Unpark FromYes
Call Completion BusyYes. 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 CancelYes
Join Group/Leave GroupYes
Join All Groups/Leave All GroupsYes
Enable mobility/Disable mobilityYes
Enable mobility cw/Disable mobility cwYes
Set presenceYes. Our phones can see the presence state of IP62. But, IP62 can't see presence state of our phones.

Other Features

Directory

Tested featureResult
Device built-in directory existsYes
Can be dialled fromYes
Does CLI resolutionYes
display update if directory object is used?Yes


Tested featureResult
External LDAP Server supportedNo
Can be dialled fromNo
Does CLI resolutionNo
display update if directory object is used?No

Keys

Tested featureResult
Device has speed dial keysYes
Device has programmable function keysYes
Device has partner keysNo

CTI Features (with SOAP / TAPI / myPBX)

Ascom Winpdm Software
Tested featureResult
User Call - outgoing callOK
User Connect - Answer incoming callNOK - Call it's not answered by the IP62.
User Reject - Reject alerting callOK
User Disconnect - Disconnect active callOK
User Hold - Put connected call on holdOK
User Hold Retrieve - Retrieve call on holdOK
User Transfer - Transfer with ConsultNOK - Could not initiate second call.
User Transfer - Transfer with Consult (Alerting only)NOK - Could not initiate second call.
User Transfer - Blind TransferOK
Switch Calls / Held Active Call automaticallyNOK - Could not initiate second call
3PTY - Make 3rd Party CallNOK - Could not initiate second call.
Park CallOK
Retrieve Parked CallNOK - Generates a second redirected call on the IP62.
Pickup CallNOK - Generates a second redirected call on the IP62.
Connected Number Update on DisplayOK
CFU indication on DisplayOK
Send DTMFs via CTINOK

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.

Ascom Winpdm Software Free


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)

Retrieved from 'http://wiki.innovaphone.com/index.php?title=Howto:IP62_WLAN_WiFi_Handset_-_innovaphone_-_H323_Testreport'