innovaphone wiki - User contributions [en]

Reference16r1:Concept App Service Devices

2026-04-14T07:00:52Z

Vsc: /* Supported DECT handsets */

[[Category:Concept|Apps]]
The App Service Devices is an App Service which can be installed on an innovaphone App Platform. It is used to administrate the innovaphone devices which belong to the whole installation.
== Applies To ==

* innovaphone PBX from version 13r1

== Apps ==

=== Devices App (innovaphone-devices) ===
This is the standard UI App for Devices.

Parameters:

;Websocket: to publish the com.innovaphone.devicesui-API, which can be used to link directly to devices (which is done e.g. inside the Events app)

=== Devices API (innovaphone-devices-api) ===
This is a hidden App, which provides the Devices API (com.innovaphone.devices). This API can be used to find and communicate with devices which are registered to the Devices App.

Additionally it acts as a provider of the Search API (com.innovaphone.search). So you can find devices and domains in other apps like the Search App.

Parameters:

;Hidden: DevicesApi must be a hidden App
;Websocket: to get the URL of the Devices App itself which is used for provisioning

== PBX Manager Plugins ==

=== Devices ===

With the Devices plugin App objects can be created, edited and deleted for Devices and the Devices API on the PBX.

== Concepts ==
All innovaphone hard phones and gateways starting from version 13r1 can establish a registration inside the Devices App and therefor administrative tasks can be performed through the App.

=== Domains ===

In a hosted environment, it might be needed to add multiple domains to the Devices App. 
After the initial installation of Devices through Install, you have administrative rights and can add more domains.

==== Administrative rights ====
You have administrative rights if the configured PBX App object for Devices uses the password of the instance which is configured in the Manager App and the PBX uses the same domain as this instance.

==== Domain local rights ====
You have just rights to a certain domain if the configured PBX App object for Devices uses the domain password which can be configured in Devices for each domain and the PBX uses the same domain name as configured in Devices.

==== Assign rights to other domains ====
Domains can gain access to other domains by configuring these access rights in the Devices App.

==== Deploy passwords and access rights ====
During install, a domain is created inside the Devices App. There is a checkmark Deploy the domain password on all devices which is set by default and which is the same as the administrative password.
If you change the domain password, all passwords on all administrative devices and app platforms which are connected to this domain will be also changed. 
Since 13r2sr25/13r3sr7/14rx: devices which are auto provisioned or provisioned through the Profile/Users Admin App will get a random password instead of the domain password.
If you add a phone device manually to a domain inside the Devices App, this phone device will also get a random password. Other device types added manually or devices added with a provisioning code which has been created within the Devices App directly, will get the domain password instead as long as you do not tick the checkmark '''Provision device with a random password'''. 
 
This will also set the manager password and the SSH passwords of App Platforms. 
 
The clear text random passwords can be requested and viewed in the settings of a device in the Devices App.

Attention: If you untick the '''Deploy administrative devices passwords''' checkmark, the password won't be deployed anymore, but also not reconfigured to the default password!

Attention: After each reconnect of a client, the password will be deployed again.
This means, if the checkmark is set and you set another password somewhere else (e.g. under General::Admin),
this password will be just valid until the next reboot or reconnect to the Devices App!

;Create new random passwords
You can rollout new random passwords by unticking the '''Deploy administrative devices passwords''' checkmark and ticking it again. 

;Changing a device from random to domain password
Starting with 16r1, you can edit a device and un-/tick "Use random password" to change the password method for each device separately.

;Devices with multiple domains (Cloud)
In a hosted environment, you can use the Devices App with multiple domains. The corresponding instance of Devices has a configured domain and an instance password set inside the manager. 

The hosting PBX has a domain inside Devices with a specific password. 
If this domain name matches the instance domain of the Devices instance and the password matches either the instance password or the domain password, you will be logged in as admin and have access to all domains. 

Each newly created domain has its own password inside Devices. If you create an App Object inside a PBX with this domain and the password of this domain (inside Devices), you will just have access to this single domain. 

Devices also has the possibility to grant access to other domains for a specific domain.

=== Categories ===

There are two types of categories:
* provisioning category: used for device configurations and provisioning
* standard category: used for update/backup jobs and device management

Each device can have just a '''single''' provisioning category, as it receives it's configuration by all configured device configurations for this provisioning category.

In addition, a provisioning category, which is used inside an analogue phone/phone device configuration '''cannot''' be used to provision a gateway.

=== Device connections ===
The Devices registration is done through a websocket connection to the webserver of the App Platform and the Devices instance (standard HTTP/s port). 
The URL used can be configured manually under [http://wiki.innovaphone.com/index.php?title={{NAMESPACE}}:General/Devices_Registration Devices Registration] or through a new provisioning mechanism. 
 
A binary protocol is used to transfer information between the device and the devices App. The MAC address is the unique key to identify a device. 
 
If a device is added to a domain in Devices, the device gets a unique random password. Without such a password, a device shows up as '''unassigned''' in the Devices app.
This is also the case after a long reset or when the device lost its configuration. 
 
In such a case, the device has to be manually added again to a domain or it has to be provisioned again.

If a device is not assigned to a domain or provisioning category, it won't receive any configurations.

==== Devices Registrations ====
See [http://wiki.innovaphone.com/index.php?title={{NAMESPACE}}:General/Devices_Registration Devices Registration]

==== Second Devices Registration URL ====

The firmware has a second SYSCLIENT2 module, which can be configured to point to a different Devices instance and the AP Manager also has a second Devices Registration URL. 
 
If you use this configuration option, you should take care and consider:

* if the Devices domain from the second configuration provides a password for all devices, the password is ignored, as it would lead to inconsistend passwords otherwise (from 13r1 SR12 on)
* the Devices domain from the second configuration should not provide Devices Configurations or Update Jobs as these might collide with configurations from the first Devices instance!

Generally, only one of the two ''Devices'' App instances connected to the device must apply changes to the device.

We strongly discourage the usage of this second configuration option due to unexpected behaviour if incorrectly used!
Never use the second URL if you use software or hardware rental!

==== Device information ====

The following data is transferred:
* MAC address
* device type (e.g. IPVA, AppPlatform, IP112)
* IP addresses (IPv4, IPv6)
* version (not searchable)

You can also search for this data inside the devices tab in the App.


=== Provisioning ===
Devices can be added by provisioning (both phones and gateways).
The standard online provisioning looks like this:
* a user or administrator creates a provisioning code in the Devices or Users App (this stores the Devices URL on the provisioning server side)
* a device with 13r1 or newer is connected to the network after a long reset
* the provisioning code has to be entered within one hour (after one hour, the Update URL isn't polled anymore)
* the device sends this code to config.innovaphone.com and retrieves the Devices URL
* the device connects to the Devices URL and is added to the domain where the code has been created

There is also an [http://wiki.innovaphone.com/index.php?title={{NAMESPACE}}:Concept_Offline_Provisioning offline provisioning mode]. 
There is also an [http://wiki.innovaphone.com/index.php?title={{NAMESPACE}}:Concept_Provisioning#Automatic_provisioning automatic provisioning mode].

Note: provisioning is cancelled if the device already belongs to another domain in the same Devices instance! This prevents the unauthorized move of a device between different domains.

==== Devices Registration URL ====

The Devices Registration URL which is set through the provisioning process, always starts with '''wss'''. This is not dependent anymore on the App URL which is configured inside the PBX Devices App object.

=== Updates ===
The Devices App can be used to rollout updates. 

==== JSON files ====
The update files have to be acccessible on a webserver without authentication and four json files are used:
* firmware.json: innovaphone device firmware
* apps.json: Apps for the App Platform
* software.json: contains software for DECT handsets
** just IP64 and IP65 are used and supported
* phoneplatform.json: contains the phone platform image for e.g. the IP270

You can either use the standard innovaphone App Store for these files or your own local webserver. 

==== Update jobs ====
You can configure several update jobs with different categories to organize your updates. 
Update jobs are always sequentially processed and inside one update job, just '''20''' devices are updated at the same time.

==== Device update check after the update job has been already executed====
If a device goes online, the newest suitable update job is searched for this device (depending on the categories). 
If an update job is found, the update is just performed, if there has been '''no''' successfull update for this device in this job before and the version does not match (simply string compare).

====Update errors====
If an update fails, the Devices App shows an error. You may have to enable further tracing on the updated device itself to find out the reason of the failure. 
 
* on a gateway/phone add a trace flag to the UP1 and HTTPCLIENT0 module and take a look at the events which may already tell you the reason
* on an App Platform, enable the App and HTTP Client trace flag on the manager

An update job is retried '''two''' times if updates inside this job failed. The retry is done '''ten''' minutes after the update job finished previously.

====innovaphone myApps====
The path to the App Store and the used innovaphone myApps version is updated to the version of the gateway on gateways with an enabled PBX after a successfull update. 
This configuration can be found [http://wiki.innovaphone.com/index.php?title={{NAMESPACE}}:PBX/Config/myApps here]

Inside the configuration on an update job, the flag "Do not update myApps launcher software" disables the update of the innovaphone myApps version inside PBXes.

====DECT handsets====
If you check the update DECT handsets checkmark, all DECT devices will be configured to rollout updates to DECT handsets. 
See [[{{NAMESPACE}}:Concept_App_Service_Devices#Supported_DECT_handsets | Supported DECT handsets]].

The DECT handset firmware will be searched inside the configured software.json.

=== Backups ===
The Devices App can be used to backup the configuration and data of Apps and devices. 

====Webserver requirements====
Backups are stored on a webserver with or without Digest/Basic authentication and with the '''webdav PUT''' method.

====Backup jobs====
Backup jobs are executed sequentially. Inside one backup job, just '''20''' backups are performed at the same time.

====Phones or gateways====
The configuration file is stored. Therefor the Devices App tells the device to store the configuration with a !mod cmd UP0 /sync prot URL.

====Apps on an App Platform====
The databases of all existing instances and the manager are stored. 
Each installed App Service can have multiple instances and each App instance has its own database. 
A database contains '''both''' configuration and data of an App instance! 
The manager database contains the webserver certificate and further manager related configuration settings.

The Devices App establishes a websocket connection to the manager and tells the manager where to store the backups. 
The manager on the backuped App Platform itself performs the HTTP requests to store the files.

====Backup errors====
If a backup fails, the Devices App shows an error. You may have to enable further tracing on the backuped device itself to find out the reason of the failure.

* on a gateway/phone add a trace flag to the UP1 and HTTPCLIENT0
* on an App Platform, enable the App and HTTP Client trace flag on the manager

=== Restore ===
====Phones or gateways====
Just as always under [http://wiki.innovaphone.com/index.php?title={{NAMESPACE}}:Administration/Upload/Config Upload Config].

====Apps====
The App Service itself has to be installed on the App Platform prior restoring of a single instance. 
The restoring is done in the Manager App on the App Platform itself. 
The instance settings, the configuration and data are restored in a single process.

=== Device Configurations ===

You can define several device configurations. These configurations are either applied to all devices inside this domain or to selected categories. 
Configurations are applied on creation and on every reconnect of a matching device.

==== Transfer checkmarks ====

Some configuration options have a specific checkmark to enable the transfer of the option. 
 
* Checkmark disabled:
** configuration option field(s) are disabled
** option values are '''not''' transferred at all
* Checkmark enabled:
** configuration option field(s) are enabled
** option values are transferred, even if field values are empty

==== Expert configuration ====

The expert configuration can be used to configure different settings which are not available inside the other device configurations. 
You can use the standard syntax of an update server script (see [[ {{NAMESPACE}}:Concept_Update_Server | Concept Update Server ]] for a general overview and the section on [[Howto:PHP_based_Update_Server_V2#Hints_for_writing_your_update_snippets | Hints for writing your update snippets ]] (note that the remainder of this article relates to the now deprecated old mechanism, so please disregard the rest)). 
 
Some hints:
* the expert configuration is just executed once after a device restarted and on change of the expert configuration itself
* the expert configuration is executed after all other device configuration types, so that you can override changes
* to make configuration changes effective, you may also need to issue a final ''config write'', ''config activate'' and ''iresetn'' command (see the [[ {{NAMESPACE}}:Concept_Update_Server#Check_command | ''check'' command]] for details)
* some commands shouldn't be used inside the script:
** [[ {{NAMESPACE}}:Concept_Update_Server#Times_command |''times'']]: since the expert configuration is executed only once after a reboot of the device and when changes are made, it does not make sense to use the ''times'' command
** [[ {{NAMESPACE}}:Concept_Update_Server#Prot_command |''prot'']]|[[ {{NAMESPACE}}:Concept_Update_Server#Boot_command |''boot'']]: use an update job instead
** [[ {{NAMESPACE}}:Concept_Update_Server#Scfg_command |''scfg'']]: use a backup job instead
** [[Howto:PHP_based_Update_Server_V2#Using_vars_create|''vars create'']]: this cmd will always raise the ''reset needed condition'' and the aforementioned ''iresetn'' command would always execute therefore. As a result, the devices would enter a boot loop. Be sure to avoid this using an appropriate [[ {{NAMESPACE}}:Concept_Update_Server#Check_command |''check'' command ]] and update its ''<serial>'' properly whenever the expert configuration is changed

==== Certificates configuration ====
You can use this configuration to rollout certificates to the trust list of your devices. 

* Manual upload certificates.
* Configure up to five URLs which are polled every 24 hours. They must return files with PEM formatted public keys (one or more) which are then rolled out.
** certificates are just rolled out if differences are determined, so if URLs are polled and no changes are detected, certificates are not rolled out again. Changes are detected by fingerprint comparison of each embedded certificate
** if a device restarts, the configuration is applied again. Just the fingerprints of the device trust list are checked against the configuration trust list and just on differences, certificates are rolled out again
* Configure https://download.innovaphone.com/certificates/innovaphone.pem to always have the innovaphone public keys in your trust list (e.g. used for our push service).
* Configure https://download.innovaphone.com/certificates/ca.pem to always have the innovaphone Device Certification Authority certificates in your trust list.
* Configure https://download.innovaphone.com/certificates/ca-unverified.pem to always have the innovaphone Unverified Device Certification Authority certificates in your trust list.
** The Unverified CA is used for non hardware devices, e.g. IPVAs, which are not shipped with an official innovaphone Device Certification Authority certificate, as innovaphone has no control over the serial number here.
* Configure https://curl.se/ca/cacert.pem to always have the public Root Certifications Authorities in your trust list.

Using this configuration, the trust list can only be managed through ''Devices'' because it is cleared before each rollout.

==== DECT Handsets ====

This configuration can be used to configure specific options like language, voicemail number etc. for DECT handsets. 
 
* all DECT devices like IP1202, IP1203 etc. will receive this configuration (of course just if the configured categories match)
* Devices configures a URL like https://domain.com/domain.com/devices/parameters/id.xml on the specific DEVMANBW module.
* This file is then polled by the basestations and the read values are transfered to the DECT handsets.
* see [[{{NAMESPACE}}:IP1202/IP1203_DECT_System#Configuration_of_Handset_parameters]]

See [[{{NAMESPACE}}:Concept_App_Service_Devices#Supported_DECT_handsets | Supported DECT handsets]].

=== Software rental ===
Regarding the Software Rental program and the Payment Method, please refer to:
* [[{{NAMESPACE}}:Concept_Software_Rental|Concept Software Rental]]

Software rental can be done for innovaphone Cloud installations or for software, which operates on the customer premisis. This could eventually be customer owned hardware or a privat virtual machine, managed by the customer.

==== Hardware licenses ====
Hardware licenses have to be bound on the specific device in my.innovaphone itself and currently can't be handled within the Devices App itself. So you also need to download the licenses from my.innovaphone and upload them on the device with the already known methods.

===== Hardware licenses with software rental =====
If your device has software rental licenses, you can bind hardware licenses within my.innovaphone in the software rental project itself.

===== Hardware licenses without software rental =====
If your device does not have software rental licenses, you should bind hardware licenses in a separate non rental project in my.innovaphone.

==== innovaphone Cloud ====
Inside the innovaphone Cloud, you just have to upload your activation keys with iSCs to add licenses to one or more gateways. 

==== Email expiry notifications ====
You will receive an email notification if the rental of a project expires. This notification will be sent '''seven''' weeks before the expiry and then once a week until the rental expires. 
You can configure one or more email recipients in the domain settings. 
If no email address is configured, the email address of the logged in user account is used.

==== History ====
You can download the history in the Devices App. You'll get a CSV file (semicolon separated). The date and number format depends on the selected language in the UI. 
There is also an API available for automated downloas, which is described [[ {{NAMESPACE}}:Concept_App_Service_Devices#API_to_download_rental_history|here ]].

====Own installation====
Inside your own installation, you have to register a new my.innovaphone account or you can use an existing account inside the Devices App. 
One domain inside Devices belongs to one project inside your my.innovaphone company, so you can handle multiple domains with one my.innovaphone account.

====Technical aspects====
A new rental expiration date is calculated on each license or balance change in the domain. 
So after each change new licenses with a new date are transfered to the gateways and also stored in the Devices App itself. 
If the rental expires, the gateway reboots and the licenses are not available anymore. 
The licenses are also transfered after each reconnect of a gateway to the Devices App. 
 
For license and balance changes, the Devices App must be online and have access to my.innovaphone.com!

====Usage====
You have to add (use the + symbol) a PBX and select all licenses you want to rent. 
Use the '''apply''' button to really bind these licenses. Without usage of the apply button, you can just see a precalculation of the iSCs/month and the rental end date, but nothing is really charged from your balance.

===Change of IP address/DNS name in PBX object===
If the IP address or DNS name inside the PBX object of the Devices App changes, all currently connected clients get a new Devices Registration URL and also all clients, which connect afterwards with the old host name.

== Appendix ==
=== Sample firmware.json ===
<code type="javascript">
{
"devices": [
{ "id": "IP0010", "versions": [ "13r1" ] },
{ "id": "IP0011", "versions": [ "13r1" ] },
{ "id": "IP101", "versions": [ "13r1" ] },
{ "id": "IP102", "versions": [ "13r1" ] },
{ "id": "IP1060", "versions": [ "13r1" ] },
{ "id": "IP110", "versions": [ "13r1" ] },
{ "id": "IP110A", "versions": [ "13r1" ] },
{ "id": "IP111", "versions": [ "13r1" ] },
{ "id": "IP112", "versions": [ "13r1" ] },
{ "id": "IP1130", "versions": [ "13r1" ] },
{ "id": "IP1260", "versions": [ "13r1" ] },
{ "id": "IP150", "versions": [ "13r1" ] },
{ "id": "IP2000", "versions": [ "13r1" ] },
{ "id": "IP200A", "versions": [ "13r1" ] },
{ "id": "IP22", "versions": [ "13r1" ] },
{ "id": "IP222", "versions": [ "13r1" ] },
{ "id": "IP230", "versions": [ "13r1" ] },
{ "id": "IP232", "versions": [ "13r1" ] },
{ "id": "IP24", "versions": [ "13r1" ] },
{ "id": "IP240", "versions": [ "13r1" ] },
{ "id": "IP241", "versions": [ "13r1" ] },
{ "id": "IP29", "versions": [ "13r1" ] },
{ "id": "IP3010", "versions": [ "13r1" ] },
{ "id": "IP3011", "versions": [ "13r1" ] },
{ "id": "IP302", "versions": [ "13r1" ] },
{ "id": "IP305", "versions": [ "13r1" ] },
{ "id": "IP311", "versions": [ "13r1" ] },
{ "id": "IP411", "versions": [ "13r1" ] },
{ "id": "IP6000", "versions": [ "13r1" ] },
{ "id": "IP6010", "versions": [ "13r1" ] },
{ "id": "IP800", "versions": [ "13r1" ] },
{ "id": "IP810", "versions": [ "13r1" ] },
{ "id": "IP811", "versions": [ "13r1" ] },
{ "id": "IPVA", "versions": [ "13r1" ] }
],
"versions": [
{ "id": "13r1", "build": "131705", "text": "13r1 dvl [131705]", "wiki": "" }
]
}
</code>

=== Sample apps.json ===
<code type="javascript">
{
"apps": [
{
"id": "apidemo",
"folder": "apidemo",
"binary": "apidemo",
"versions": [
{ "id": "13r1", "build": "131705", "label": "dvl" }
],
"manufacturer": "innovaphone",
"title": "Apidemo",
"description": "The Apidemo"
},
{
"id": "appstore",
"folder": "appstore",
"binary": "appstore",
"versions": [
{ "id": "13r1", "build": "131705", "label": "dvl" }
],
"manufacturer": "innovaphone",
"title": "AppStore",
"description": "AppStore"
}
]
}
</code>

=== Sample software.json ===
<code type="javascript">
{
"software": [
{
"id": "myappsandroid",
"folder": "myappsandroid",
"binary": "myapps.apk",
"versions": [
{ "id": "13r1", "build": "131705", "label": "dvl" }
],
"manufacturer": "innovaphone",
"title": "myApps Android",
"description": "myApps for Android"
},
{
"id": "myappswindows",
"folder": "myappswindows",
"binary": "myAppsSetup.msi",
"versions": [
{ "id": "13r1", "build": "131705", "label": "dvl" }
],
"manufacturer": "innovaphone",
"title": "myApps Windows",
"description": "myApps for Windows"
}
]
}
</code>

=== Sample phoneplatform.json ===
<code type="javascript">
{
"phoneplatforms": [
{
"id": "arm64",
"text": "Phone Platform",
"file": "phone-platform.img",
"folder": "yocto2",
"version": "2063"
}
],
"devices": [
{
"id": "IP270",
"phoneplatforms": [
"arm64"
]
}
]
}
</code>

=== API to download rental history ===

You can download the history as a UTF-8 CSV file with simple '''HTTP GET''' requests with '''digest''' authentication. 
The CSV file uses the semicolon as delimiter. 
 
The URL to download the history is e.g.: 
'''<code>https://mydomain.com/mydomain.com/devices/csvapi?...</code>'''

You can find this path by editing the instance in the AP manager.
In the listed paths, you'll find something which ends with csvapi

In the innovaphone Cloud environment, the URL can be retrieved by taking a look at the Devices App object inside the cloud PBX and replacing the ending '''innovaphone-devices''' with '''csvapi''' inside the App URL, so it looks e.g. like this:

https://cloud-apps0.innovaphone.com/cloud.innovaphone.com/devices/csvapi

====CSV columns====
Most columns should be self explaining, but the column '''invoice reference''' refers to a value which you can configure manually in the domain settings in the Devices App!

====Digest authentication====
You can login with two different username/password combinations, while the domain is the digest username:

* If you use the domain and password of your Devices App instance inside the AP Manager, you have automatically access to all domains. 
* If you use the domain name of any domain as digest username and the configured domain password, you'll have access to this domain and all domains to which this domain has access to

====Query parameters====
The following query parameters can be used (don't forget to URL encode the parameter values, if neccessary!):
* all: if '''1''' or '''true''', the history is queried for all domains where the digest user has access to
* domain: required, if ''all'' is not set
* lang: the output language of the CSV file, which also controls date and number formats, e.g. '''en''', '''de''', ...
* tz: the timezone for dates, e.g. '''Europe/Berlin'''
* type: two types are available:
** '''history''': history which contains changes
** '''overview''': a monthly overview with the iSC costs at the first of the last months
* from: unix timestamp (UTC) in milliseconds, ignored for type=overview
* to: unix timestamp (UTC) in milliseconds, ignored for type=overview

====Example requests====
* <code>https://mydomain.com/mydomain.com/devices/csvapi?domain=mydomain.com&type=overview&lang=en&tz=Europe%2FBerlin</code>
* <code>https://mydomain.com/mydomain.com/devices/csvapi?domain=mydomain.com&type=history&lang=en&tz=Europe%2FBerlin&from=1601903431000&to=1601903385000</code>
* <code>https://mydomain.com/mydomain.com/devices/csvapi?all=1&type=overview&lang=en&tz=Europe%2FBerlin</code>

=== Supported DECT handsets ===

The following handsets are supported for update jobs and the DECT handsets configuration:

* IP64
* IP65
* D83

== Known issues ==

===SoftwarePhone===
The Devices App is not meant to be used with the windows SoftwarPhone standalone installation.

== Related Articles ==
* [[Howto:Software_Rental]]

Reference16r1:Apps/PbxManager/Email

2026-04-13T09:57:36Z

Vsc:

{{FIXME|reason=This product is in the beta phase and is not yet finished}}
This PBX Manager Plugin configures the E-Mail Account of all PBXes in the system. The same configuration can be found in the advanced UI of the individual PBXes at [[{{NAMESPACE}}:PBX/Config/Authentication|PBX/Config/Authentication]].

== Add Email Account ==
; SMTP Server
: Your SMTP Server

; Email Address
: The used From Address

; Username
: The username for the authorization

; Password
: The password for the authorization

; Sender's name
: The used Name in the From field

; OAuth2
: Alternatively OAuth2 credentials to authenticate for e-mail sending. See [[Howto16r1:Configure_OAuth2_E-Mail]].

Reference15r1:Concept Conference

2026-04-13T08:47:59Z

Vsc:

[[Category:Concept Conference]]

= Applies To =

* innovaphone PBX from version 13r3
* innovaphone devices supporting a CONF or SCNF interface

= Overview =
The innovaphone conference is provided by the [[{{NAMESPACE}}:PBX/Objects/Conference| PBX Conference Object]]. It is used to create conference rooms which allows audio, video, application sharing and chat between all participants. The conference rooms can be joined via phone, WebRTC using any browser or myApps.

= Requirements =
* innovaphone PBX
* A multi-point control unit (MCU) or an innovaphone device with CONF or SCNF interface with [[Howto:Conferences, Resources and Licenses| appropriate channel licensing]]
* Optional Conference App licenses (App(innovaphone-pbx-conferencing)13). This license is necessary to create HTTP links that invite external participants.

= Configuration =
The configuration of the conference object is described in [[Courseware:IT_Connect_-_08.1_Conferencing| this wiki article]].

= Features =
* Audio Conferencing
* Multi Video as described in [[{{NAMESPACE}}:Concept Multi-Video-Conference| this wiki article]]
* Application sharing
* Chat
* Apps
* Using an innovaphone conference interface according to [[{{NAMESPACE}}:Gateway/Interfaces| this wiki article]]
* Various voice prompts listed in [[{{NAMESPACE}}:PBX/Objects/Conference/Announcement types| this wiki article]]
* PBX Manager Plugin as described in [[{{NAMESPACE}}:Apps/PbxManager/Conference| this wiki article]]
* Web Access as described in [[{{NAMESPACE}}:Concept Conference Web Access| this wiki article]]
* Meeting scheduling as described in [[{{NAMESPACE}}:Concept Conference Meeting Invitations| this wiki article]]

== Codec-Filtering ==
If an innovaphone device is used, the video codec must be filtered, because these devices do not support transcoding. Each room can be configured to either H.264 or VP8 is to be filtered out. The most devices support VP8, so this is the normally selected codec which is to be passed.

== Chat ==
Chat messages can be exchanged between all participants of a conference room. The participant device must support instant messaging with the call signaling.

Chat messages are not stored permanently even for users with premium chat license. As long as one participant remains in the conference room, new participants receive the last 100 instant messages. When all participants of a room have left, all chat messages temporarily saved in this room are deleted.

= Apps =
The PBX conference object's name (H.323) must be SIP-compatible and must not start with a digit, otherwise the apps are not accessible.

== Conference Search API (innovaphone-pbx-conferencing-search) ==
The conference object provides a search app. This is a hidden app which provides the Search API (com.innovaphone.search) used by other apps. The app responses to search requests with matching room contacts. The contact data includes the default innovaphone conference icon. All conference rooms are also found with the translated words ''conference'' and ''room'' of the user's language as the search string.

The app searches only for static rooms, not for dynamically created rooms like meeting rooms. Therefore the app caches the conference object data for one hour and disconnects the connection to the PBX again.

The innovaphone PBX conferencing license is not necessary for this app.

== Conference App (innovaphone-pbx-conferencing-one) ==
The conference object provides an app for each configured static room. One innovaphone PBX conferencing license is necessary for each PBX user which uses these apps.

The apps show all participants of the conference room. Participants can be muted or thrown out. The room PIN can be changed.

The web access of the room can be configured, this link shown or mailed, as described in [[{{NAMESPACE}}:Concept Conference Web Access| this wiki article]].
In addition, meeting links can be created, as described in [[{{NAMESPACE}}:Concept Conference Meeting Invitations| this wiki article]].

== Conference App (innovaphone-pbx-conferencing-access) ==
The conference object provides also an app for ad hoc rooms created with the conference operator. One innovaphone PBX conferencing license is necessary for each PBX user which uses this app.

The app shows all participants of an ad hoc conference room. Participants can be muted or thrown out. The room PIN can be changed. Access to an existing ad hoc conference room is granted upon knowing the room number.

The name of the app is <object-h323>.access and it must be added to the user with the 'temporary' mode to have access to ad hoc conferences. Other modes are reserved for future use.

= Troubleshooting =
'''Conference object'''

The conference object has a trace option (Options tab). This option allows to investigate problems with the announcements or resource allocation. If you activate this option, innovaphone debug messages are created which can be seen in a trace.

'''SCNF/CONF interface'''

The conference interfaces (CONF/SCNF) have a trace option. This trace flag provides more information about the various calls connected to the conference interface.

Reference15r1:Concept Conference

2026-04-13T08:46:47Z

Vsc: /* Conference App (innovaphone-pbx-conferencing-one) */

[[Category:Concept Conference]]

= Applies To =

* innovaphone PBX from version 13r3
* innovaphone devices supporting a CONF or SCNF interface

= Overview =
The innovaphone conference is provided by the [[Reference13r1:PBX/Objects/Conference| PBX Conference Object]]. It is used to create conference rooms which allows audio, video, application sharing and chat between all participants. The conference rooms can be joined via phone, WebRTC using any browser or myApps.

= Requirements =
* innovaphone PBX
* A multi-point control unit (MCU) or an innovaphone device with CONF or SCNF interface with [[Howto:Conferences, Resources and Licenses| appropriate channel licensing]]
* Optional Conference App licenses (App(innovaphone-pbx-conferencing)13). This license is necessary to create HTTP links that invite external participants.

= Configuration =
The configuration of the conference object is described in [[Courseware:IT_Connect_-_08.1_Conferencing| this wiki article]].

= Features =
* Audio Conferencing
* Multi Video as described in [[Reference13r3:Concept Multi-Video-Conference| this wiki article]]
* Application sharing
* Chat
* Apps
* Using an innovaphone conference interface according to [[Reference13r1:Gateway/Interfaces| this wiki article]]
* Various voice prompts listed in [[Reference13r3:PBX/Objects/Conference/Announcement types| this wiki article]]
* PBX Manager Plugin as described in [[Reference13r3:Apps/PbxManager/Conference| this wiki article]]
* Web Access as described in [[Reference13r3:Concept Conference Web Access| this wiki article]]
* Meeting scheduling as described in [[Reference13r3:Concept Conference Meeting Invitations| this wiki article]]

== Codec-Filtering ==
If an innovaphone device is used, the video codec must be filtered, because these devices do not support transcoding. Each room can be configured to either H.264 or VP8 is to be filtered out. The most devices support VP8, so this is the normally selected codec which is to be passed.

== Chat ==
Chat messages can be exchanged between all participants of a conference room. The participant device must support instant messaging with the call signaling.

Chat messages are not stored permanently even for users with premium chat license. As long as one participant remains in the conference room, new participants receive the last 100 instant messages. When all participants of a room have left, all chat messages temporarily saved in this room are deleted.

= Apps =
The PBX conference object's name (H.323) must be SIP-compatible and must not start with a digit, otherwise the apps are not accessible.

== Conference Search API (innovaphone-pbx-conferencing-search) ==
The conference object provides a search app. This is a hidden app which provides the Search API (com.innovaphone.search) used by other apps. The app responses to search requests with matching room contacts. The contact data includes the default innovaphone conference icon. All conference rooms are also found with the translated words ''conference'' and ''room'' of the user's language as the search string.

The app searches only for static rooms, not for dynamically created rooms like meeting rooms. Therefore the app caches the conference object data for one hour and disconnects the connection to the PBX again.

The innovaphone PBX conferencing license is not necessary for this app.

== Conference App (innovaphone-pbx-conferencing-one) ==
The conference object provides an app for each configured static room. One innovaphone PBX conferencing license is necessary for each PBX user which uses these apps.

The apps show all participants of the conference room. Participants can be muted or thrown out. The room PIN can be changed.

The web access of the room can be configured, this link shown or mailed, as described in [[{{NAMESPACE}}:Concept Conference Web Access| this wiki article]].
In addition, meeting links can be created, as described in [[{{NAMESPACE}}:Concept Conference Meeting Invitations| this wiki article]].

== Conference App (innovaphone-pbx-conferencing-access) ==
The conference object provides also an app for ad hoc rooms created with the conference operator. One innovaphone PBX conferencing license is necessary for each PBX user which uses this app.

The app shows all participants of an ad hoc conference room. Participants can be muted or thrown out. The room PIN can be changed. Access to an existing ad hoc conference room is granted upon knowing the room number.

The name of the app is <object-h323>.access and it must be added to the user with the 'temporary' mode to have access to ad hoc conferences. Other modes are reserved for future use.

= Troubleshooting =
'''Conference object'''

The conference object has a trace option (Options tab). This option allows to investigate problems with the announcements or resource allocation. If you activate this option, innovaphone debug messages are created which can be seen in a trace.

'''SCNF/CONF interface'''

The conference interfaces (CONF/SCNF) have a trace option. This trace flag provides more information about the various calls connected to the conference interface.

Howto:Trio - Enghouse Interactive - 3rd Party Product

2026-04-07T13:15:43Z

Vsc: /* Configuration */

[[Image:EnghouseTrio.png||200px|right]]

==Product Name==


[https://www.enghouseinteractive.com/products/call-center-solutions/trio/ Enghouse Interactive Trio]

==Certification Status==

{{Template:Compat_Status_referral_product_new}}

Testing of this product has been finalized September, 2024.

==Category==

{{Category:3rdParty Contact Center Applications}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Contact Center Applications|{{PAGENAME}}]]

==Vendor==
[[Image:Enghouselogo.png|150px]]

Enghouse Interactive (EI), a subsidiary of Enghouse Systems Limited (TSX: ENGH), is a leading global provider of contact center software, services, and video solutions, serving thousands of customers for over 35 years. Enghouse Interactive solutions enable customers to deliver winning customer experiences by transforming the contact center from a cost center into a powerful growth engine.

Enghouse Interactive’s core values – Reliability and Choice – are key differentiators in the global marketplace. Reliability speaks to Enghouse Interactive’s reputation for consistently honoring its commitments to its customers, staff, partners, and investors. Choice is reflected in the unparalleled breadth of its CX portfolio, which enables customers to choose from a wide array of solutions, whether deployed on-premise, in the cloud, or on a hybrid platform. By leveraging a broad range of technologies and capabilities based on open standards, Enghouse Interactive simplifies the advanced integrations customers require.

Respecting local regulatory requirements, and supporting any telephony technology, Enghouse Interactive ensures that its customers can be reached by their customers – anytime, anywhere, and via any channel.

==Description==



[[Media:EXTERNAL ProductDescription Trio 9 3 0 ENG.pdf|'''Product description''']]

=== Enghouse Trio ===
Enghouse Trio is an all in one communication solution, for medium to large organisations. Enghouse Trio product portfolio consists of three main product suites
* Trio Customer Interaction products
* Trio User products
* Trio Services products 
The Enghouse Trio solution is the first product on the market to deliver these product suites in one integrated
package, enabling customers to integrate and utilise internal resources in the best possible way, in order to
deliver excellent customer service.

=== Connecting people and information ===
Today’s businesses change quickly and there is a need to be agile and adapt to the ever-changing requirements
of customers. In today’s extremely competitive environment, it is too costly to have customer calls connected
to the wrong people within the company. Employees have to be able to work together productively, wherever
located, physically or within the organisation. The constant flow of phone calls, e-mails, Social Media and voice
mails need to be managed, prioritised and connected to the right people, at the right time - every time.
This is why Enghouse Interactive has created Enghouse Trio, which is the result of decades of innovation in
enterprise telephony and communications. Enghouse Trio combines enterprise-class communication
technologies into a single unified communications platform that works seamlessly with major existing PBX,
CRM, ERP, Social Media, e-mail and back office systems. Enghouse Trio coordinates all business
communications, so that employees can focus on what they do best.

=== The Business Benefits of Enghouse Trio ===
* Optimises the Use of Business Resources
* Reduces staff cost
* Increases productivity
* Increases customer loyalty
* Connects all communications to the right contact point, at the right time, based on existing company business rules
* No dropped calls, lost e-mails or Social media posts.
* Improves Productivity and Efficiency
* Provides full awareness of each resource’s status, task queue, skills, role, and availability to the entire organisation.
* Provides streamlined communication processes that can adapt in real-time.
* Increases resource utilisation, by pooling resources across the entire enterprise around the globe. No matter where they are located geographically.
* Unified Communications Management
* Reduced infrastructure maintenance
* Lower prioritisation costs by having a single unified communications platform that handles all business-critical communications.

==Functions==
=== Customer Interaction ===
This is Industry-leading customer service technology that coordinates all of your self-service and manual communication processes. The product suite offers a wide range of different options to ensure that an enterprise can create and design their own unique solution that meets their needs.

'''Features'''
* Premium Contact Center Features: IVR, complex scripting, call blending, inbound call management, prioritisation, mobile handover, and distributed site management. All in one single, scalable platform.
* Centralized universal queue: manages all the different tasks such as calls,video, e-mail, social media,fax, SMS, tasks, call-back, chat, web call-back, telemarketing in one centralized module
* Smart Features: “Call me back” ensures that callers don’t need to wait
* Call blending: of inbound and outbound communications. Maximizes the value of your available resources during peak demand.
* Communications workflow engine: automatically assigns communications, to resource task queues, based on defined business rules. Automatically routes e-mails and faxes based on designated key words and business identifiers.
* Virtual Office: Ensures unlimited access to the company telephony system, from any phone, anywhere.
* IVR: Advanced possibilities for setting up call distribution and queue rules. TE can offer automatic services in the queue, combining IVR, text to speech, or speech recognition. Enables trained technical personnel to set up self service applications and advanced call routing scenarios based on DTMF or voice input.
* Visit Management: is an extensive and professional system for visitor handling, which automates the processing and registration of on-site visitors. Furthermore, the system can coordinate the handling of visitors with your other communications tasks.
* Auto Attendant: Enables the caller to get automatic attendant and referral functionality, by voice commands.

=== Trio Users ===
Enghouse Trio user products are the result of over 20 years of dedicated focus in creating the best user experience. The products range from simple clients to manage presence and communication profile management to advanced clients for Agents and Attendants where all incoming business communications are managed from one single user-friendly, Windows-based client a web based agent.

'''Features'''
* Enterprise Attendants and Agents: Communications are assigned and prioritised, based on resource status and availability. This ensures a streamlined workflow and high productivity.
* Remote work support: Possibility for both agents and attendants to work from any device, both mobile and fixed.
* Unified Desktop: High productivity with Trio’s user-friendly Windows-based or Web based client.
* Integrated toolbar to manage the prioritisation and completion of all incoming communications.
* Profile Management: All resources can change their profiles, skills, current services, communication methods and other criteria, to update company communications processes automatically.

=== Enterprise Services ===
Enterprise Services are the core product suite that enables Enterprises to experience full services integration.
By selecting and composing the preferred options the Enterprise can create their unique solution that meets their specific requirements and ensures the best possible customer experience

'''Features'''
* Enterprise Directory: Enghouse Trio provides functionality that extends your business communication environment beyond the confines of your enterprise
* Presence management: Resource availability based on information from calendar servers, web clients or third-party presence products. Information can be retrieved from both mobile and fixed devices. The feature that makes it possible to allow coordination of tasks, based on resource availability and schedule
* Integration with ERP/CRM system: Provides real-time business intelligence and automation, to increase productivity. Provides the benefits of CTI without the difficulty associated with integrating your back-office systems with your PBX. Extensive integration towards Microsoft Dynamics
* High-level and detailed reporting: allows auditing of communications history, statistics, and call recordings. Identifies communications issues/gaps by status code, business service, customer id, or resource. Identifies process and resource issues, to quickly improve efficiency.
* System Configurations: Multiple options for how the system can be configured are presented in a range from system scaling options to enterprise cooperation.

==Version==




Product versions used for interop testing:

* Enghouse Interactive Trio Version 10.0

* innovaphone V14r1 sr6

==Configuration==





===On Premise Installation===
[[Media:Trio 10.0 and Innovaphone v14R1 SCG R1.pdf|innovaphone OnPremise PBX Configuration Guideline]]
===Cloud Installation===
[[Media:EnghouseTrioCloudPBXConfiguration.pdf|innovaphone Cloud PBX Configuration Guideline]]

==Contact==


{|
| colspan=99 | Enghouse Interactive
|-
| colspan=99 | Jonny Fransson
|-
| Tel: || +46 730668815
|-
| Mail: || [mailto:jonny.fransson@enghouse.com jonny.fransson@enghouse.com]
|}

Datasheet IP73

2026-04-01T11:31:46Z

Vsc: /* Connectors */

{{datasheet_header|innovaphone IP73|WiFi phone for use in office environments}}
<div class="datasheets-mehrspaltig">
[[Image:IP65.png]]
===Housing===
Dimensions (l × w × d): 137 x 52 x 21 mm / 5.4 x 2 x 0.8 inch (excl. clip)

Weight: 135 g / 4.8 oz (excl. clip)

Material: Case: PC; Keypad: coated vulcanized silicone; Clip: PA

Color: Black

Display: Size (w × h): 31 x 41 mm / 2.0 inch, TFT; Multiple colors with high resolution, 262 K individual colors; 240 × 320 pixel LCD with white LED backlight

Clip: Hinge-type (standard) or swivel-type

===User Interface===
Indicator: Illuminated display for visual indication of incoming call, and charging.

Vibrator: Incoming call

Keyboards: Illuminated keys; 3 function keys, Multifunction key, On hook, Off hook / Power; 4 direction navigation; Numeric block; Volume + and –; Ringtone on / off

===Battery & Charging===
Type: Li-polymer 3.7V 920 mAh

Speech time: 10 h during optimal condition

Stand-by time: 100 h during optimal condition (with screen saver)

Charge time: < 4 hours

===Connectors===
Multi-purpose connector for fast software download, configuration and battery charging via separate USB-desktop programmer.

Headset connector: Bluetooth and Standard 3.5 mm

===Radio===
Receiver sensitivity (typical values):
* −87 dBm (802.11a, 6 Mbps), −93 dBm (802.11b, 1 Mbps)
* −87 dBm (802.11g, 6 Mbps), −86 dBm (802.11n, MCS0)
Frequency range EU:
* b/g: 2.4–2.4835 GHz (Ch 1–13)
* a: 5.1700–5.3300 GHz (Ch 36–64), 5.4900–5.71000 GHz (Ch 100–140), 5.7350 – 5.8350 GHz (Ch 149-165)
Modulation speed:
* b: 1, 2, 5.5, 11Mbps
* a, g: 6, 9, 12, 18, 24, 36, 48, 54 Mbps
* n: MCS-0–MCS-7
* ac: MCS-0–MCS-9
Bluetooth radio spectrum: ISM 2.4000–2.4835 GHz

Bluetooth output power: Maximum 3 dBm (Class 1)

===WiFi===
Number of networks: 4 systems, auto selection or manual selection

Quality of Service (QoS): WMM, TSPEC-based CAC

Supported networks: 802.11 a/b/g/n/ac (MCS0-7)

Reg. domain: 802.11 d/h

Security standard: 802.11i, 802.11w

Supported encryption methods: AES-CCMP, TKIP

Supported authentication methods: Open, WPA/WPA2-PSK, PEAP-MSCHAPv2, EAP-TLS

Roaming extensions: 802.11r, 802.11k, Opportunistic key caching, PMKSA caching

Bluetooth: 5.0, headset and hands-free profile

===Environmental===
Operating temperature: -5 °C to +45 °C

Storage temperature: -20°C to +60°C

Charging temperature: +0°C to +45°C

Enclosure protection: IP44, IEC 60529

===VoIP Protocols===
SIP Version 2, conform RFC 3261

SIP over UDP, TCP, TLS

RTP, SRTP (SDES, DTLS), RTCP, ICE

===Voice Codecs===
G.711 A-law / µ-law, G.729, G729A, G.729B, G.729AB, G.722, Opus-WB

===Network===
STUN, TURN over UDP/TCP

DHCP, NTP

===Supplemental Services===
* Telephony: Toggle, Consultation call, Number- and name display, DTMF tone support
* Internal phone book: 250 entries, 48 characters for name and 30 digits for number, 30 digits for mobile number, 30 additional characters
* Selectable ring tones per contact
* Languages: Arabic, Chinese (simp.), Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hungarian, Italian, Norwegian, Polish, Portuguese, Russian, Slovakian, Spanish, Swedish, Turkish

Additional functions
* 9 programmable hot keys
* Call list with 25 last calls
* 14 ring tones - external and internal distinguishable, Ring signal volume in 8 steps, LED display, vibration
* Automatic answer
* Loudspeaker, Mute function

{{Template:Leistungsmerkmale EN - Lizenzen Telefone}}
{{Template:CE-Decl_DECT|Conformities|see separate information sheet}}
===Order number Handset: 50-00073-001===
===Order number Single Charger: 50-00060-001===
===Order number Programming charger: 50-00060-021===
</div>
{{Template:Datasheet_footer|EN}}
[[Category:Technical Data Phones EN|{{PAGENAME}}]]

Datasheet d83

2026-04-01T11:31:28Z

Vsc: /* Interfaces */

{{datasheet_header|d83 / d83 EX|Robust IP DECT handset for hazardous locations}}
<div class="datasheets-mehrspaltig">
[[Image:D83_D83EX.png]]
===Housing===
Size 150 x 64 x 23 mm

Color Handset: grey/black, Front plate: steel grey (standard), black, turquoise, green, orange

Build: Case: PC/ABS, Keypad: PC, Clip: PA Case: Hinge type (standard), swivel type or no clip

TFT display with more than 262000 individual colors, 40 x 50 mm (240 x 320 pixel), white LED backlight

Weight: 175 g (incl. battery and clip)

===Keyboards===
3 function keys

Off hook key

combined on-hook/power-on/off key

4-way navigation

Numeric book

Volume + and –

Sound off key / Mute multifunction button

Alarm button / Push-to-talk multifunction button
===Battery===
Li-Ion type 3.7 V, 920 mAh
Speech times:
* LF location disabled: up to 18h Bluetooth disabled, up to 12h Bluetooth enabled
* LF location enabled: up to 16h Bluetooth disabled, up to 10h Bluetooth enabled
Standby times:
* up to 120h (with black screen saver activated and LF location disabled)
* up to 60h (with black screen saver activated and LF location enabled) 
< 4h charging time

===Interfaces===
Multi-purpose connector for headset, battery charging and software download / configuration

Screw-locked 3.5mm standard headset connector for Peltor/3M headset cable

Bluetooth version 5.0

GAP / CAP compliant DECT, EN 301 406, TBR22

1880-1900 MHz frequency range

GFSK modulation

Integral antenna

-93 dBm sensivity

Radiated power: 250mW (EU)

===Environmental===
Operating temperature: -10 °C to +55 °C.

Storage temperature: -20 °C to +60 °C.

Charging temperature: +5 °C to +40 °C.

Enclosure protection: IP65, IEC EN60529.

Immunity to ESD: 8 kV contact discharge, 16 kV air discharge (EN61000-4-2).

Free fall test:
* IEC 60068-2-31, procedure 1, dropped 12 times, specification extended to 2 meters
* IEC 68-2-32, procedure 2, dropped 1,000 times from 0.5 meter.

Accelerated life test

Chemical stress: Handset exposed to oleic acid.

Keypad action test: Keys pressed 15.0000 times with a force of 13 N.

Squeeze test: Handset squeezed 1000 times with a force of 130 N.

===Audio===
8-step adjustable ring signal

8-step adjustable earpiece of 3dB each

Max. sound ring signal level: 100 dBspl (90 dBspl for d81ex) @ 10 cm

Duplex loud speaking function

Wideband audio: Support of voice codecs G.722.2 and G.726.

Background noise reduction: Two microphones and adaptive noise reduction

15 predefined ringtones + 10 freely definable ringtones

Mute button

===Supplementary Services Telephony===
* Hold, retrieve, Consultation call
* Number display, Name display
* DTMF tone support

===Phone Books===
Central phone book: unlimited no. of entries, max. 40 characters in name and 20 digits in phone number

Company phone book: 1,000 entries, max. 24 characters in name and 24 digits in phone number

Internal phone book: 250 entries, max. 48 characters in name and 24 digits in phone number

===Languages===
23 Menu and message languages:
* Arabic, Czech, Danish, Dutch, English, Finnish, Flemish, French, German, Greek, Hungarian, Italian, Norwegian, Polish, Portuguese (Brazil & Europe), Russian, Simplified Chinese, Slovakian, Spanish, Swedish, Turkish
* +1 downloadable language

===Additional Functions===
9 programmable hot keys

Call list with 50 last calls

Automatic answer

Vibration

===Featureset===
all device versions:
* Telephony
* Shock, vibration, drop, temperature and chemical resistant
* Centralized device management*
* Central phone book
* Bluetooth 5.0 for wireless headsets
* 3.5 mm contact for wired headsets
* Shared Phone*
additionally for versions Messenger & Protector:
* Advanced messaging including priority**, confirmation, call setup, colors on display and LED
* Services and shortcuts to phone calls, messaging, sending data, etc*
* Location with BLE, DECT, IR and LF Technologies*
additionally version Protector:
* Push-button, man-down, no-movement and pull-cord alarms*
<nowiki>*</nowiki>Features only available with Ascom UNITE and/or use of Ascom IMS3 Gateway. 
<nowiki>**</nowiki>feature only available with Ascom IPBS
{{Template:CE-Decl_DECT|Conformities|see separate information sheet}}

===Order Number d83 Talker: 50-00083-013===
===Order Number d83 Messenger: 50-00083-014===
===Order Number d83 Protector: 50-00083-015===
===Order Number d83 Messenger EX: 50-00083-025===
===Order Number d83 Protector EX: 50-00083-026===
</div>
{{Template:Datasheet_footer|EN}}
[[Category:Technical Data Phones EN|{{PAGENAME}}]]

Datasheet IP65

2026-04-01T11:30:58Z

Vsc: /* Connectors */

{{datasheet_header|innovaphone IP65|IP DECT handset with large colour display and Bluetooth}}
<div class="datasheets-mehrspaltig">
[[Image:IP65.png]]
===Housing===
Dimensions (l × w × d): 137 x 52 x 21 mm / 5.4 x 2 x 0.8 inch (excl. clip)

Weight: 135 g / 4.8 oz (excl. clip)

Material: Case: PC; Keypad: coated vulcanized silicone; Clip: PA

Color: Black

Display: Size (w × h): 31 x 41 mm / 2.0 inch, TFT; Multiple colors with high resolution, 262 K individual colors; 240 × 320 pixel LCD with white LED backlight

Clip: Hinge-type (standard) or swivel-type

===User Interface===
Indicator: Illuminated display for visual indication of incoming call, and charging.

Vibrator: Incoming call

Keyboards: Illuminated keys; 3 function keys, Multifunction key, On hook, Off hook / Power; 4 direction navigation; Numeric block; Volume + and –; Ringtone on / off

===Battery & Charging===
Type: Li-polymer 3.7V 920 mAh

Speech time: 20 h during optimal condition

Stand-by time: 240 h during optimal condition

Charge time: < 4 hours

Discharge/charge cycles: >=80% capacity left after 400 full charge/discharge cycles
===Connectors===
Multi-purpose connector for fast software download, configuration and battery charging via separate USB-desktop programmer.

Headset connector: Bluetooth and Standard 3.5 mm

===Audio===
* 23 ring signals, distinguishable by internal, external and callback calls; 8 volume steps
* Earpiece: Adjustable in 8 steps of 3dB each
* Maximum sound ring signal level: 88 dBA @ 10 cm
* Loudspeaker: Duplex loudspeaking function

===Localization===
Menu and message languages: Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hungarian, Italian, Norwegian, Polish, Portuguese (Brazilian), Russian, Slovakian, Spanish, Swedish, and Turkish

===Phonebook===
*Central: max. name length: 40 characters, max. number length: 20 digits
*Company: max entries: 1000, maximum name length: 24 characters, maximum number length: 24 digits (one number per name)
*Local: max entries: 250, max name length: 48 characters, max number length: 24 digits (three numbers per name - work/mobile/other)
*Selectable ring tones per contact
===Telephony===
Indication: 23 ring signals, illuminated display and vibrator

Answer call: Button press or auto answer

Call list storage capacity: 25 calls (received, dialled and missed) with time stamp

===Radio/BT===
GAP/CAP compliant

Automatic DECT protocol detection: Automatic detection and configuration for US DECT and EU DECT at first registration.

Frequency range:
*EU: 1880-1900 MHz
*US: 1920-1930 MHz
*LA: 1910-1930 MHz
*BR: 1910-1920 MHz
Bluetooth radio spectrum: ISM 2.4000-2.4835 MHz

Modulation: GFSK

Channel spacing: 1.728 MHz

Antenna: Integral

Sensitivity: -93 dBm

Dynamic output power:
*EU/LA/BR: 10 mW (maximum average power)
*US: 4 mW (maximum average power)

===Environmental===
Operating temperature: 0°C to +40°C (32° to 104°F)

Storage temperature: -20°C to +60°C (-4° to 140°F)

Charging temperature: +5°C to +40°C (41° to 104°F)

Enclosure protection: IP44, IEC EN60529

Immunity to electromagnetic fields: 3V/m EN61000-4-3

Immunity to ESD: 4 kV contact discharge and 8 kV air discharge (EN61000-4-2)

Free fall test:
*IEC 60068-2-32, procedure 1, dropped 12 times from 1 metre.
*IEC 60068-2-32, procedure 2, dropped 1000 times from 0.5 metre.

{{Template:Leistungsmerkmale EN - Lizenzen Telefone}}
{{Template:CE-Decl_DECT|Conformities|see separate information sheet}}
===Order number Handset: 50-00065-004===
===Order number Single Charger: 50-00060-001===
===Order number Programming charger: 50-00060-021===
</div>
{{Template:Datasheet_footer|EN}}
[[Category:Technical Data Phones EN|{{PAGENAME}}]]

Datasheet IP64

2026-04-01T11:30:25Z

Vsc: /* Connectors */

{{datasheet_header|innovaphone IP64|IP DECT handset with large colour display}}
<div class="datasheets-mehrspaltig">
[[Image:IP64.png]]
===Housing===
Dimensions (l × w × d): 137 x 52 x 21.5 mm / 5.4 x 2 x 0.8 inch (excl. clip)

Weight: 114 g / 4,0 oz (excl. clip)

Material: Case: PC/ABS; Keypad: hard coated silicon; Clip: POM

Color: Black

Display: Size (w x h): 28 x 35 mm / 1.8 inch, TFT; Multiple colors with high resolution, 262 K individual colors; 128 x 160 pixel LCD with white LED backlight

Clip: Hinge-type (standard)

===User Interface===
Indicator: Illuminated display for visual indication of incoming call, and charging.

Vibrator: Incoming call

Keyboards: 3 function keys; On hook, Off hook / Power; 4 direction navigation; Numeric block; Manual and automatic keypad lock

===Battery & Charging===
Type: Li-lon 3.7V 650 mAh 2.40Wh

Speech time: 16 h during optimal condition

Stand-by time: 180 h during optimal condition

Charge time: < 4 h

Discharge/charge cycles: >=65% capacity left after 500 full charge/discharge cycles

===Connectors===
Multi-purpose connector for fast software download, configuration and battery charging via separate USB-desktop programmer.

Headset connector: Standard 3.5 mm

===Audio===
* 14 ring signals, distinguishable by internal, external and callback calls; 8 volume steps
* Earpiece: Adjustable in 8 steps of 3dB each
* Maximum sound ring signal level: 88 dBA @ 10 cm
* Loudspeaker: Duplex loudspeaking function

===Localization===
Menu and message languages: Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hungarian, Italian, Norwegian, Polish, Portuguese (Brazilian), Russian, Slovakian, Spanish, Swedish, and Turkish

===Phonebook===
*Central: max. name length: 40 characters, max. number length: 20 digits
*Company: max entries: 500, maximum name length: 24 characters, maximum number length: 24 digits (one number per name)
*Local: max entries: 250, max name length: 48 characters, max number length: 24 digits (three numbers per name - work/mobile/other)

===Telephony===
Indication: 14 ring signals, illuminated display and vibrator

Answer call: Button press or auto answer

Call list storage capacity: 25 calls (received, dialled and missed) with time stamp

===Radio===
GAP/CAP compliant

Automatic DECT protocol detection: Automatic detection and configuration for US DECT and EU DECT at first registration.

Frequency range:
*EU: 1880-1900 MHz
*US: 1920-1930 MHz
*LA: 1910-1930 MHz
*BR: 1910-1920 MHz
Modulation: GFSK

Channel spacing: 1.728 MHz

Antenna: Integral

Sensitivity: -93 dBm

Dynamic output power:
*EU/LA/BR: 10 mW (maximum average power)
*US: 4 mW (maximum average power)

===Environmental===
Operating temperature: 0°C to +40°C (32° to 104°F)

Storage temperature: -20°C to +60°C (-4° to 140°F)

Charging temperature: +5°C to +40°C (41° to 104°F)

Enclosure protection: IP40, IEC EN60529

Immunity to electromagnetic fields: 3V/m EN61000-4-3

Immunity to ESD: 4 kV contact discharge and 8 kV air discharge (EN61000-4-2)

Free fall test:
*IEC 60068-2-32, procedure 1, dropped 12 times from 1 metre.
*IEC 60068-2-32, procedure 2, dropped 1000 times from 0.5 metre.

{{Template:Leistungsmerkmale EN - Lizenzen Telefone}}
{{Template:CE-Decl_DECT|Conformities|see separate information sheet}}
===Order number Handset: 50-00064-004===
===Order number Single Charger: 50-00060-001===
===Order number Programming charger: 50-00060-021===
</div>
{{Template:Datasheet_footer|EN}}
[[Category:Technical Data Phones EN|{{PAGENAME}}]]

Reference16r1:Concept App Service Connector for Microsoft 365

2026-04-01T07:10:32Z

Vsc: /* Technical Overview */

{{FIXME|reason=This article is still work in progress}}

[[Category:Concept|Apps]]
== Applies To ==

* Connector for Microsoft 365 from Version 16r1

= Overview =

Connector for Microsoft 365 synchronizes Microsoft Teams presences with the innovaphone PBX and back, and optionally additionally Calendar presence from Exchange Online (part of the Microsoft 365 Cloud Services).
It is also possible to search for your own contacts.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform (minimum version 120004)
* V16r1
* App(Connector for Microsoft 365)
* PBX-App(innovaphone-microsoft365) license per user - order no. 02-00050-009

== Concept ==

=== User Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure User Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph API.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made periodically.

The app synchronises the PBX presence with Teams through the Graph Api. The on-the-phone presence will be renewed every 5 minutes. The other presences have a lifetime of 1 day but the away has a lifetime of 7 days.
The lifetimes are described [https://learn.microsoft.com/en-us/graph/api/presence-setuserpreferredpresence?view=graph-rest-1.0&tabs=http here]

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

===== User Matching =====
You now can choose the fields used for user matching on either side from the following options:
* PBX
** CN (Long Name property from the PBX user object)
** h323 (Name property from the PBX user object)
* Azure Portal
** displayName
** mail
** mailNickname
** onPremisesDistinguishedName
** onPremisesSamAccountName
** onPremisesUserPrincipalName
** userPrincipalName

Additionally, you have the possibility to remove a possibly contained domain from the Azure fields content. 
Example: 'user@domain.tld' is transformed to 'user', if this option is checked.

===== Mapping Table =====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

===== Master/Slave =====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

=== Calendar Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure_Calendar_Presence_Sync_by_Connector_for_Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 15r1 the Connector for Microsoft 365 will offer a possibility to sync Azure Portal calendar events (Teams, Exchange online) via the Graph API with the PBX presence. 
For now the [https://wiki.innovaphone.com/index.php?title=Reference13r3:Concept_App_Service_Calendar Calendar App] is (along with other functions) also capable of syncing calendar events, but using the old EWS mechanism, which Microsoft announced as end of life starting from 2026. 
'''Warning:''' Please make sure to not use both apps for syncing calendar events in parallel, this is not supported and will most likely lead to conflicts and unexpected behaviours. 
 
When the configuration of the connector for Microsoft 365 Calendar Presence Sync is complete, the app connects to Microsoft to receive a token with the calendar app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, a subscription for calendar events is created at Microsoft to receive event changes in Microsoft Calendar for these users. 
 
A user subscription is also started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 
If a calendar event has been started or ended, it is forwarded to the PBX. 

* User subscriptions are renewed every 60 minutes.
* Event subscriptions are renewed every day.
* License Check is made every hour.

=== Contact Search ===

==== Configuration ====
Please have a look into our [[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 16r1 the Connector for Microsoft 365 will offer a possibility to search for your own contacts (Teams, Exchange online) via the Graph API.

When the configuration of the connector for Microsoft 365 Contact Search is complete, the app connects to Microsoft to receive a token with the contact search app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, the user can search with the Phone App, for example (a myApps search provider will be provided for all apps looking using search providers looking up contacts). The search string is made available to the Connector for Microsoft 365 via the microsoft365-api. The results are sent to the consumer, e.g. the Phone App and presented there. 
 
A user subscription is started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 

* User subscriptions are renewed every 60 minutes.
* License Check is made every hour.

'''Be aware:''' Since the Connector for Microsoft 365 is an app in the Scope of myApps App Platform, IP Phones and other services not using Apps cannot benefit from this search service.

== Related Articles ==

=Known Limitation=

== General ==
''Applies to the User Presence and the Calendar Presence''

=== Synchronization Delay ===
In the official Graph-API documentation, Microsoft is providing an overview about expected latencies for change notifications. 
You can find a whole overview table here: 
https://learn.microsoft.com/en-us/graph/change-notifications-overview#latency 
 
For the user presences the resource "presence" is used and an average latency of 10 seconds but a maximum up to 1 minute is provided. 
Such a delay in syncing changed presences from Teams down to the PBX are considered normal and are caused by the Microsoft Graph-API. 
 
In case of calendar events the average is provided as "less than 1 minute" and the maximum to 3 minutes. 

== User Presence ==
=== Line states set by the PBX does not block calls in Teams ===
Line states set by a 3rd party application (like the Connector for Microsoft 365) through the graph API are currently '''only for display purpose and do not block new calls''' in Teams. 
 
https://techcommunity.microsoft.com/t5/teams-developer/ms-graph-setpresence-problems/m-p/2798805/highlight/true#M3957 
As you can see in the above linked discussion, there once existed a feature request on Microsoft Voice, which is no longer available since it was not voted.
=== Maximum number of supported users ===
The connector now supports multiple Microsoft Teams communication users, which is the prerequisite to subscribe for more than 650 users. There is a new ribbon (Manage Teams Accounts) that allows you to configure as many communication users as you need. Every configured communication user can be used to subscribe 650 users, for example:

*3 configured communication users x 650 licensed users = 1950 users can be subscribed
'''Please be aware''': Each communication user must have a Teams license applied.

This limitation is caused by Microsoft. 
In the documentation of the Graph-API you will find a hint to this limitation: 
https://learn.microsoft.com/en-us/graph/changenotifications-for-presence#subscribe-to-multiple-users-presence 
Trying to subscribe more than 650 users (with one communication user) by using the presence subscription API will be declined by the graph API with an error message, that too many users are requested. 

=== Communication User (UserSynctoPbx) ===
Users with MFA (multi-factor-authentication) are not supported as technical communication user for the Connector.

=== Multiple sites / instances require multiple communication users ===
Each instance or each site must have separate communication users, as Microsoft only allows one concurrent subscription per communication user. (otherwise an HTTP 409 conflict will occur)

This means that if you want to subscribe to the same Azure Portal backend from two different sites (or instances), you will need to have multiple communication users (each with an applied Teams licence) in order to be able to subscribe from all endpoints.

=== Subscription Timeout ===

==== Situation ====
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

==== Impact ====
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=
== General ==

===Creating an app trace===
For further analysis and creating a support ticket it will be useful to have a suitable app trace. 
Before creating the trace please make sure the following trace flags are activated for the app instance:
* App
* Database
* HTTP client
* TLS
* TCP
* App WebSocket
* Config
* Webserver

After setting the config flags, please make sure to
* stop the instance
* deleting the current instance log
* start the instance
'''Now please wait at least 5 Minutes before you save the log''', otherwise we could not have the whole picture in the trace.

The restart and deletion of the the old log is useful the see the complete initialization process right away.

===SSL Certificate for notification URL===
It also is useful to make sure the notification URL has a valid and public signed certificate. 
You can do that, using an SSL-Checker, for example: https://www.sslshopper.com/ssl-checker.html 
Without a valid, public signed certificate, Microsoft will decline the connection since it will not be possible to establish a trust relationship for the SSL/TLS secure channel.

===Correctness of notification URL===
You can try to open the notification URL in your Browser 
Most likely you will see a HTTP 404 (Not Found) error message, which is the expected behavior since we are not providing an HTML website, the HTTP GET request from the browser will not be answered with content. 
This is perfectly fine since Microsoft will send presence updates with HTTP POST and will not try to request content from our app. 
 
What you can find out by trying to open the URL in your browser are the two following things: 
* If you receive a HTTP 404 error message you are most likely connected to an App Platform, if not you need to check your DNS (and maybe also reverse proxy) settings.
* If the URL is modified and the used build number is added, an app has answered your request
** Example: <code>https://public.dns/your.domain/microsoft365/subscriptions</code> is modified to <code>https://public.dns/your.domain/microsoft365/1510411/subscriptions</code>
** If this is not the case, your URL is wrong. (Be aware: The URL depends on the settings of the web server path of your app instance)

'''Be aware:''' The URL-Recognition in the Application Platform is '''case sensitive'''.

=== Activation of "Public client flow" for the registered app in Azure Portal===
If the subscription is not working at all, please make sure "Public client flow" is activated for the registered app in the Azure portal (as described in our [[Howto16r1:Configure User Presence Sync by Connector for Microsoft365#Create_an_App_for_syncing_Teams_to_PBX|HowTo article]]). 
 
The App Service trace will contain the following message if this is not the case: 
<code>AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'.</code>

== User Presence ==
===GUI Feedback===
The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. 
Sometimes it needs a little bit time until the states are changed. 
If the states remain, it is mandatory to enable logs on the app platform and check for more information. 
([[Howto13r3:Configure Connector for Microsoft365#Creating an app trace|Concept App Service Connector for Microsoft 365: Creating an app trace]])

====No connection to Master PBX====
Check the MasterPBX name. 
The field must only contain the name [pbx], '''not the full domain''' [pbx.domain.tld]. ([[Howto13r3:Configure Connector for Microsoft365#Synchronization from Teams to the PBX|Synchronization from Teams to the PBX - Master PBX field]])

====Presence subscription failed====
There are many reasons why the "Presence subscription failed" message could be displayed. 
We try to list the most common reasons:
* The permission for the registered app in the Azure portal are not correctly set ([[Howto13r3:Configure Connector for Microsoft365#Create an App for syncing Teams to PBX|Howto: Create an App for syncing Teams to PBX]])
* The Notification URL is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The App service is not reachable from the internet ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The certificate for the public endpoint (e.g. reverse proxy) is not valid, or not publicly signed ([[Reference13r3:Concept App Service Connector for Microsoft 365#SSL Certificate for notification URL|Concept App Service Connector for Microsoft 365: SSL Certificate for notification URL]])
* The user from PBX and the Azure Portal cannot be matched ([[Reference13r3:Concept App Service Connector for Microsoft 365#User Matching|Concept App Service Connector for Microsoft 365: User Matching]])
* The App Platforms clock time is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#App Platform clock time is wrong|Concept App Service Connector for Microsoft 365: App Platform clock time is wrong]])
* No user has a valid Connector for Microsoft 365 App license ([[Reference13r3:Concept App Service Connector for Microsoft 365#Requirements|Concept App Service Connector for Microsoft 365: Requirements]])

===Teams License for communication user===
If presence subscription does not work, please check if all of the configured communication users have a Microsoft Teams license applied and no multifactor authentication is in use for this particular user. 
Also please make sure you can login with the configured credentials. (If you have set a password as an Administration, the user needs to change the password during the first login, therefore the given password will be invalid for API access). 
''Sometimes, after changing setting or after the instance has restarted it can take up to 12 minutes until the presence subscription is working correctly. (Due to the subscription timeout)''

= Known Issues =
== Special Characters In Password ==
If you are using special characters (*, &, (, ), etc.) in your password you could run into a problem with the authentication of the communication user. 
The authentication failed status is being displayed. 
For the moment the only workaround is to eliminate special characters from your password.

==App Platform clock time is wrong==
If the clock time at the App Platform is not correct, this will lead to an unstable behaviour of the Connector for Microsoft 365. 
Since the Connector for Microsoft 365 is using the Microsoft Graph APIs presence subscription function, it needs to provide in its request a precise time until the subscription validity will be expired. 
The app service is handling subscription and will automatically recreate a new subscription each time the previous one has expired. 

A wrong clock time will lead to false expiration times and thus
* the subscription will be expired earlier than expected (synchronisation is not working because there is no valid subscription)
* the subscription will be valid longer than expected (the app service is trying to create a new subscription because it is expecting the previous one to be expired - will lead to a 409 conflict error, because only one subscription can be valid at a time)

If you are not sure about the current time of the App Platform, you can login via SSH into the App Platform and execute the <code>date</code> command to check the current time. 
You will receive an output like:
Tue Mar 12 13:38:57 UTC 2024
Please be aware: The time is displayed in UTC, so please make sure to convert to your local time zone.

==Geoblocking==
Since there might be no reliable country assignment for Microsoft addresses, all Microsoft addresses must be enabled on the upstream firewall in the event of geoblocking in order to ensure functionality of the Office365 Connector. 
As an alternative you might be able to configure your firewall to bypass the geoblocking for the configured notification URL.

= Related Articles =
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Contact Search by Connector for Microsoft365]]

[[Category:Howto|{{PAGENAME}}]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T13:46:22Z

Vsc: /* Certified WLAN Platforms */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.

Wi-Fi infrastructures not listed in this document are not supported. Use of the IP73 in unsupported infrastructures is at your own risk.

{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_8_10_0_13.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_central_10_4_1_3.pdf}}]]
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_10_162.pdf}}]]
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_5_182.pdf}}]]
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_3_3.pdf}}]]
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_9_3.pdf}}]]
|-
! colspan="5" |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
|29-Sept-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_meraki_mr_27_7_1.pdf}}]]
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_meraki_mr_30_7.pdf}}]]
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_fortinet_wlc_8_5_2_5.pdf}}]]
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_huawei_airengine_V200R022C10SPC100.pdf}}]]
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45
|Mist Cloud
|0.12.26354
|Aug-2023
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_juniper_0_12_26354.pdf}}]]
|-
|AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.27139
|Feb-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_juniper_0_12_27139.pdf}}]]
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_ruckus_smartzone_5_2_0_0.pdf}}]]
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_ruckus_smartzone_6_1_2_0.pdf}}]]
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

File:I63 interop ruckus smartzone 6 1 2 0.pdf

2026-03-31T13:09:01Z

Vsc:

File:I63 interop ruckus smartzone 5 2 0 0.pdf

2026-03-31T13:08:51Z

Vsc:

File:I63 interop juniper 0 12 26354.pdf

2026-03-31T13:08:40Z

Vsc:

File:I63 interop juniper 0 12 27139.pdf

2026-03-31T13:08:29Z

Vsc:

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T13:07:55Z

Vsc: /* Certified WLAN Platforms */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_8_10_0_13.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_central_10_4_1_3.pdf}}]]
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_10_162.pdf}}]]
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_5_182.pdf}}]]
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_3_3.pdf}}]]
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_9_3.pdf}}]]
|-
! colspan="5" |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
|29-Sept-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_meraki_mr_27_7_1.pdf}}]]
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_meraki_mr_30_7.pdf}}]]
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_fortinet_wlc_8_5_2_5.pdf}}]]
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_huawei_airengine_V200R022C10SPC100.pdf}}]]
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45
|Mist Cloud
|0.12.26354
|Aug-2023
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_juniper_0_12_26354.pdf}}]]
|-
|AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.27139
|Feb-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_juniper_0_12_27139.pdf}}]]
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_ruckus_smartzone_5_2_0_0.pdf}}]]
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_ruckus_smartzone_6_1_2_0.pdf}}]]
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

File:I63 interop huawei airengine V200R022C10SPC100.pdf

2026-03-31T13:01:05Z

Vsc:

File:I63 interop fortinet wlc 8 5 2 5.pdf

2026-03-31T13:00:54Z

Vsc:

File:I63 interop meraki mr 27 7 1.pdf

2026-03-31T12:58:28Z

Vsc:

File:I63 interop meraki mr 30 7.pdf

2026-03-31T12:58:16Z

Vsc:

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T12:57:47Z

Vsc: /* Certified WLAN Platforms */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_8_10_0_13.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_central_10_4_1_3.pdf}}]]
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_10_162.pdf}}]]
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_5_182.pdf}}]]
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_3_3.pdf}}]]
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_9_3.pdf}}]]
|-
! colspan="5" |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
|29-Sept-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_meraki_mr_27_7_1.pdf}}]]
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_meraki_mr_30_7.pdf}}]]
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

File:I63 interop cisco catalyst 17 9 3.pdf

2026-03-31T12:55:18Z

Vsc:

File:I63 interop cisco catalyst 17 3 3.pdf

2026-03-31T12:55:07Z

Vsc:

File:I63 interop cisco wlc 8 5 182.pdf

2026-03-31T12:54:55Z

Vsc:

File:I63 interop cisco wlc 8 10 162.pdf

2026-03-31T12:54:41Z

Vsc:

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T12:54:13Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_8_10_0_13.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_central_10_4_1_3.pdf}}]]
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_10_162.pdf}}]]
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_wlc_8_5_182.pdf}}]]
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_3_3.pdf}}]]
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_cisco_catalyst_17_9_3.pdf}}]]
|-
! colspan="5" |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
|29-Sept-2021
|
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T12:48:11Z

Vsc: /* Certified WLAN Platforms */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_8_10_0_13.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_central_10_4_1_3.pdf}}]]
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|
|-
! colspan="5" |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
|29-Sept-2021
|
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T12:45:42Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 207, 214, 215, 224, 225, 275
|7000/7200/9000/MX-VA-xxx
|8.10.0.6
|20-Mar-2023
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_aos_8_10_0_6.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_8_10_0_13.pdf}}]]
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_aruba_networking_central_10_4_1_3.pdf}}]]
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|
|-
! colspan="5" |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
|29-Sept-2021
|
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

File:I63 interop aruba networking 8 10 0 13.pdf

2026-03-31T12:45:23Z

Vsc:

File:I63 interop aruba networking central 10 4 1 3.pdf

2026-03-31T12:45:10Z

Vsc:

File:I63 interop extreme wireless 10 51 10.pdf

2026-03-31T12:16:22Z

Vsc:

File:I63 interop extreme cloud 10 0r8.pdf

2026-03-31T12:16:10Z

Vsc:

File:I63 interop extreme xcc 05 16 01 0025.pdf

2026-03-31T12:15:56Z

Vsc:

File:I63 interop extreme cloud 10 2 4 0.pdf

2026-03-31T12:15:42Z

Vsc:

File:I63 interop extreme wing 7 5 2 0.pdf

2026-03-31T12:15:25Z

Vsc:

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T12:14:25Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

===Certified WLAN Platforms===
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 207, 214, 215, 224, 225, 275
|7000/7200/9000/MX-VA-xxx
|8.6.0.5
|22-Dez-2020
|
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|
|-
! colspan="5" |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
|29-Sept-2021
|
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|AP:10.51.10
|03-Feb-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wireless_10_51_10.pdf}}]]
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_0r8.pdf}}]]
|-
|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
|10-Dec-2020
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_xcc_05_16_01_0025.pdf}}]]
|-
|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
|20-Jan-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_2_4_0.pdf}}]]
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_wing_7_5_2_0.pdf}}]]
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T10:28:09Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 207, 214, 215, 224, 225, 275
|7000/7200/9000/MX-VA-xxx
|8.6.0.5
|22-Dez-2020
|
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|
|-
! colspan="5" |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
|29-Sept-2021
|
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|10.51.10
|03-Feb-2020
|
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|
|-
|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
|10-Dec-2020
|
|-
|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
|20-Jan-2021
|
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link={{fullurl:Special:FilePath/i63_interop_extreme_cloud_10_8_3_0.pdf}}]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T10:19:39Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.
{| class="wikitable"
|+Certified WLAN Platforms as of March 2026
!AP Model
!Controller Model
!SW Version
!Test date
!Report
|-
! colspan="5" |Aruba
|-
|AP 207, 214, 215, 224, 225, 275
|7000/7200/9000/MX-VA-xxx
|8.6.0.5
|22-Dez-2020
|
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|7000/7200/9000/MX-VA-xxx
|8.10.0.13 LSR
|09-Sep-2024
|
|-
|AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655
|Networking Central
|10.4.1.3_90100
|12-Aug-2024
|
|-
! colspan="5" |Cisco
|-
|AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130
|WLC 3504, 5520, 8540, vWLC, Mobility Express Solution
|8.10.162
|04-Feb-2022
|
|-
|AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852
|WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC
|8.5.182
|14-Feb-2022
|
|-
|AP 1702, 2702, 3702
|Catalyst 9800
|17.3.3
|01-Jun-2021
|
|-
|AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136
|Catalyst 9800
|17.9.3
|20-Jun-2022
|
|-
! colspan="5" |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
|29-Sept-2021
|
|-
|MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)
CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)
| -
|MR 30.7
|Nov-2024
|
|-
! colspan="5" |Extreme Networks (Enterasys/IdentiFi)
|-
|AP 3801, 3805, 3825, 3865, 3935
|Extreme Wireless C25, C35, C2110, C5110, C5210, v2110
|10.51.10
|03-Feb-2020
|
|-
|AP 122, 130, 230, 250, 550, 650
|Extreme Cloud
|AP 10.0r8, Cloud 20.1.1.3
|19-Mar-2020
|
|-
|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
|10-Dec-2020
|
|-
|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
|20-Jan-2021
|
|-
|AP310i/e, 410i/e, 460i/e, 510i/e, 650i
|Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000
|7.5.2.0
|12-Apr-2021
|
|-
|AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010
|Extreme Cloud iQ
|AP 10.8.3.0, Cloud 25.4.3-40
|Aug-2025
|[[File:P2pdf.png|40px|link=Media:i63_interop_extreme_cloud_10_8_3_0.pdf]]
|-
! colspan="5" |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
|03-Jun-2021
|
|-
! colspan="5" |Huawei
|-
|AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E
|AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus
|V200R022C10SPC100
|10-May-2023
|
|-
! colspan="5" |Juniper Mist
|-
|AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63
|Mist Cloud
|0.12.26354 0.12.27139
|10-Feb-2024
|
|-
! colspan="5" |Ruckus
|-
|SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ100/300
|5.2.0.0.699
|27-Apr-2024
|
|-
|SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720
|SmartZone platform, vSZ-(H,E,D), SZ144/300
|6.1.2.0.404
|29-Apr-2024
|
|}

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png|ip73_703_winpdmauth.png/]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG|wifimwi.png/]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png|ip73_pbx_query.png/]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png|ip73_certificate.png/]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T08:12:23Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Certified WLAN Platforms
! Vendor !! AP Model(s) !! Controller Model(s) !! latest tested SW Version !! Test date
|-
| Aruba ||AP 207, 214, 215, 224, 225, 275||7000/7200/9000/MX-VA-xxx||8.6.0.5||22-Dez-2020
|-
| Aruba ||AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655||7000/7200/9000/MX-VA-xxx||8.10.0.13 LSR||09-Sept-2024
|-
| Aruba ||AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655||Networking Central||10.4.1.3_90100||12-Aug-2024
|-
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130||WLC 3504, 5520, 8540, vWLC, Mobility Express Solution||8.10.162||04-Feb-2022
|-
| Cisco||AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852||WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC||8.5.182||14-Feb-2022
|-
| Cisco||AP 1702, 2702, 3702||Catalyst 9800||17.3.3||01-June-2021
|-
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136||Catalyst 9800||17.9.3||2022-06-20
|-
| 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||29-Sept-2021
|-
| Cisco Meraki||MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax); CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)||-||MR 30.7||Nov-2024
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 3801, 3805, 3825, 3865, 3935|| Extreme Wireless C25, C35, C2110, C5110, C5210, v2110||10.51.10||03-Feb-2020
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 122, 130, 230, 250, 550, 650|| Extreme Cloud ||AP 10.0r8, Cloud 20.1.1.3||19-March-2020
|-
| 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||10-Dec-2020
|-
| 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||20-Jan-2021
|-
| 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||12-April-2021
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010|| Extreme Cloud iQ ||[[Media:i63_interop_extreme_cloud_10_8_3_0.pdf|AP 10.8.3.0, Cloud 25.4.3-40]]||August-2025
|-
| 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||03-Jun-2021
|-
| Huawei||AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E||AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus||V200R022C10SPC100||10-May-2023
|-
| Juniper Mist||AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63||Mist Cloud||0.12.26354 0.12.27139||10-Feb-2024
|-
| Ruckus||SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ100/300||5.2.0.0.699||27-April-2024
|-
| Ruckus||SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ144/300||6.1.2.0.404||29-April-2024
|}

as of March 2026.

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T08:11:17Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Certified WLAN Platforms
! Vendor !! AP Model(s) !! Controller Model(s) !! latest tested SW Version !! Test date
|-
| Aruba ||AP 207, 214, 215, 224, 225, 275||7000/7200/9000/MX-VA-xxx||8.6.0.5||22-Dez-2020
|-
| Aruba ||AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655||7000/7200/9000/MX-VA-xxx||8.10.0.13 LSR||09-Sept-2024
|-
| Aruba ||AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655||Networking Central||10.4.1.3_90100||12-Aug-2024
|-
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130||WLC 3504, 5520, 8540, vWLC, Mobility Express Solution||8.10.162||04-Feb-2022
|-
| Cisco||AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852||WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC||8.5.182||14-Feb-2022
|-
| Cisco||AP 1702, 2702, 3702||Catalyst 9800||17.3.3||01-June-2021
|-
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136||Catalyst 9800||17.9.3||2022-06-20
|-
| 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||29-Sept-2021
|-
| Cisco Meraki||MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax); CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)||-||MR 30.7||Nov-2024
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 3801, 3805, 3825, 3865, 3935|| Extreme Wireless C25, C35, C2110, C5110, C5210, v2110||10.51.10||03-Feb-2020
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 122, 130, 230, 250, 550, 650|| Extreme Cloud ||AP 10.0r8, Cloud 20.1.1.3||19-March-2020
|-
| 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||10-Dec-2020
|-
| 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||20-Jan-2021
|-
| 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||12-April-2021
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010|| Extreme Cloud iQ ||[[File:i63_interop_extreme_cloud_10_8_3_0.pdf|AP 10.8.3.0, Cloud 25.4.3-40]]||August-2025
|-
| 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||03-Jun-2021
|-
| Huawei||AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E||AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus||V200R022C10SPC100||10-May-2023
|-
| Juniper Mist||AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63||Mist Cloud||0.12.26354 0.12.27139||10-Feb-2024
|-
| Ruckus||SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ100/300||5.2.0.0.699||27-April-2024
|-
| Ruckus||SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ144/300||6.1.2.0.404||29-April-2024
|}

as of March 2026.

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

File:I63 interop extreme cloud 10 8 3 0.pdf

2026-03-31T08:11:00Z

Vsc:

Reference:IP73 WLAN WiFi Wireless IP-Phone

2026-03-31T08:06:44Z

Vsc: /* WLAN Infrastructure Compatibility */

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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Handset Features Matrix
! 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 ||
|}

As of firmware version 4.0.0, the connection of a central telephone book via LDAP is supported. For configuration to be carried out refer to the [[#Central Phonebook Access|corresponding section below]].

==WLAN Infrastructure Compatibility==

'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com 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.

{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+ Certified WLAN Platforms
! Vendor !! AP Model(s) !! Controller Model(s) !! latest tested SW Version !! Test date
|-
| Aruba ||AP 207, 214, 215, 224, 225, 275||7000/7200/9000/MX-VA-xxx||8.6.0.5||22-Dez-2020
|-
| Aruba ||AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655||7000/7200/9000/MX-VA-xxx||8.10.0.13 LSR||09-Sept-2024
|-
| Aruba ||AP 303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 535, 554, 555, 635, 655||Networking Central||10.4.1.3_90100||12-Aug-2024
|-
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130||WLC 3504, 5520, 8540, vWLC, Mobility Express Solution||8.10.162||04-Feb-2022
|-
| Cisco||AP 1602, 2602, 3502, 3602, 1702, 2702, 3700, 2802, 3802, 1832, 1852||WLC 2504, 3504, 5508, 5520, 7510, 8510, 8540, vWLC||8.5.182||14-Feb-2022
|-
| Cisco||AP 1702, 2702, 3702||Catalyst 9800||17.3.3||01-June-2021
|-
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136||Catalyst 9800||17.9.3||2022-06-20
|-
| 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||29-Sept-2021
|-
| Cisco Meraki||MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax); CW9162/CW9163E/CW9164/CW9166/CW9166D1 (Wifi 6E)||-||MR 30.7||Nov-2024
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 3801, 3805, 3825, 3865, 3935|| Extreme Wireless C25, C35, C2110, C5110, C5210, v2110||10.51.10||03-Feb-2020
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 122, 130, 230, 250, 550, 650|| Extreme Cloud ||AP 10.0r8, Cloud 20.1.1.3||19-March-2020
|-
| 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||10-Dec-2020
|-
| 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||20-Jan-2021
|-
| 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||12-April-2021
|-
| Extreme Networks (Enterasys/IdentiFi) ||AP 305c/305cx, 410c, 460c, 510c/510cx, 650/650x, 4000, 5010|| Extreme Cloud iQ ||[[:File:i63_interop_extreme_cloud_10_8_3_0.pdf|AP 10.8.3.0, Cloud 25.4.3-40]]||August-2025
|-
| 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||03-Jun-2021
|-
| Huawei||AirEngine5760-51/5760-22W/6760-X1/6760-X1E/6760R-51/6760R-51E/8760-X1-PRO/8760R-X1/8760R-X1E||AirEngine 9700-M1, AC6508/6805/6800V, iMaster NCE-Campus||V200R022C10SPC100||10-May-2023
|-
| Juniper Mist||AP34, AP45 AP12, AP32, AP33, AP41, AP 43, AP61, AP 63||Mist Cloud||0.12.26354 0.12.27139||10-Feb-2024
|-
| Ruckus||SmartZone ZoneFlex R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ100/300||5.2.0.0.699||27-April-2024
|-
| Ruckus||SmartZone ZoneFlex R350, R350e, T350, R550, R650, R750, T750, R850, R500, R510, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ144/300||6.1.2.0.404||29-April-2024
|}

as of March 2026.

=== DAS Compatibility ===
[http://en.wikipedia.org/wiki/Distributed_antenna_system 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 [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output 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.

=== U-APSD Required ===
U-APSD is a power saving function that is always enabled on the IP73. It must also be enabled/supported on the AP to avoid packet loss/voice problems.

==Configuration==
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.

=== Security ===
From version 7.x onwards, the IP73 firmware includes several changes to achieve compliance with the EU Radio Equipment Directive (RED) and the Cybersecurity Delegated Act.

This requires some additional configuration changes to get the handset operational:

====New handset initial configuration====
{{IP73_703_WinPDM_Auth}}

Resolution is to enter the [[#Shortcuts|default admin access code]] and afterwards to either disable WinPDM Authentication or change the Admin access code:

[[Image:IP73 703 WinPDMAuth.png]]

====Configuration changes for PBX connection====
For handsets running firmware 7.x, the following settings must be configured via WinPDM in order to enable a PBX connection:
* Unite connection mode must be set to another value than ‘Automatic’ at [Device/Unite/Connection mode].
* Admin access code must be set at [Device/General/Admin access code]. 5 - 10 characters required.
* Phone lock code must be set at [Device/Settings/Force phone lock]. 4 - 8 characters required. By setting the phone lock code the phone lock will be applied for every subsequent bootup. Phone lock is enforced on by default but can be turned off by parameter [Device/Settings/Force phone lock] or by admin menu in handset GUI. Note that handset does not comply with RED by turning off forced phone lock!
* Security has also been strengthen by disabling some outdated security protocols by default. If a service is no longer working after upgrade try to use more modern cryptographic protocol or set parameter “<service>/Allow outdated security protocols” to ‘Yes’.

===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> or <DNS-name of 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.

=== MWI for IP73===
The IP73 can be configured to display a message waiting indication / MWI.
You need a programming shell and the WinPDM software (available for download in our [https://store.innovaphone.com/release/141A000/download.htm Store] under the Software tab).
*Connect programming cradle to the administration PC
*Install WinPDM and start the application
*Place IP73 into the programming cradle
*If the IP73 is recognized in WinPDM, the parameter settings can be opened by switching to the Numbers tab (1)
*select the respective device type (2 -> WH2 = IP73) and double-clicking the device line (3).
*Select menu Device (4) and step to Message Centre (5)
*Insert the number of the voicemail object for the Message Centre Number (6)
*Insert the user number for the voice mail number (7)
Confirm settings with OK and ensure correct synchronisation of config changes to the handset. Reset of handset is recommended.

[[Image:WIFIMwi.PNG]]

===Central Phonebook Access===
The device offers access to a central LDAP-based directory. Following configuration steps have to be carried out by the administrator:

'''Device Configuration via the WinPDM application'''
* Device has to be plugged into programming cradle and edited via WinPDM
* Device has to be operated with at least firmware '''6.1.13''' available at the [https://store.innovaphone.com innovaphone store].
* Open section Device and step to Central phonebook. Change the central phonebook mode to LDAP and enter the appropriate parameters for the ldap directory to be queried.

For innovaphone PBX query, the following settings and attributes can be used and adapted to the PBX setup.

[[image:IP73_PBX_query.png]]

In case of using LDAP-secure-queries, upload of the LDAP-server-'''ROOT''' certificate to the IP73 trust list is required:

[[image:IP73_Certificate.png]]

==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 some hidden tools for information and analysis, which can be accessed via specific menus and codes:

;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==

===Packet loss and voice quality issues with non-tested WLAN AP and IP73===

'''Issuer: Ascom'''

'''Published: 2022-12-07'''

'''Background''' 
It has come to our (Ascom) knowledge that in later Aruba software versions than Ascom-certified v.8.7.1.1 there is a critical issue affecting clients using power save (U-APSD). 
Data packets will not be transmitted properly to clients in power save.

'''Affected Ascom Certified Aruba Access Points:''' 
7000/7200/9000/MX-VA-xxx Controllers 
AP-303, 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 
504, 505, 514, 515, 534, 535, 554, 555, 635 

'''Typical symptoms are:''' 
Poor voice quality issues. 

'''Workaround''' 
Currently none available. Disabling U-APSD on the SSID isn’t a viable workaround as this is a requirement for Ascom i63 handsets in enterprise-grade VoWi-Fi deployments. 
Thus it is strongly recommended to avoid upgrades to v. 8.9.x and higher at this point. 

'''Solution''' 
The root cause is still under investigation (case no. 5361636812), and Aruba is working on a fix. We (Ascom) will update this news regarding an ETA when communicated by Aruba. 
Should you have any further questions, feel free to reach out to interop@ascom.com. 

===Bluetooth automatically disabled===

'''Issuer: Ascom''' 

'''Version''' 
Handset Firmware 4.0.6

'''Detailed Information''' 
If you have enabled Bluetooth over WinPDM and you want to configure (establish connection to the headset), you get the message "Bluetooth automatically disabled".

'''Background''' 
The chip responsible for handling wireless radio communication, WLAN and BT, has a bug in its current firmware. Thus, using WLAN and BT on similar frequency bands does not work well.

'''Solution/Workaround''' 
Bluetooth is prohibited to be used when WLAN band 2.4 is in use by being automatically disabled. Bluetooth can only be used when WLAN on the 2.4 GHz band is inactive. 
You can disable WLAN 2.4 band over the WinPDM tool.

==Related Articles==
*[[IP73 Technical Data EN]]
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]

Howto:REDCOM-Conference - GESAT - 3rd Party Product

2026-03-30T13:09:59Z

Vsc:

[[Image:GesatLogo.png|200px|right|/GesatLogo.png|/GesatLogo.png]]

==Product Name==
Gesat [https://www.gesat.com/satellite-communication/eutelsat_oneweb/?lang=en REDCOM Conference] as an add-on to the GESAT REDCOM Server
==Certification Status==

{{Template:Compat_Status_referral_product_new}}

Testing of this product was completed in March 2026.

==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Conferencing_/_Video_Systems}}
[[Category:3rdParty_Conferencing_/_Video_Systems|{{PAGENAME}}]]

==Vendor==
[[Image:GesatLogo.png|150px|/GesatLogo.png|/GesatLogo.png]]

[https://www.gesat.com/?lang=en GESAT GmbH], the specialist for satellite communication solutions since 1989, has been a long-standing partner of authorities and agencies at federal, state and local level,
as well as of emergency services, CRITIS companies and companies that want or need to maintain their business continuity.

As one of the leading providers of satellite communication, we offer you manufacturer-independent hardware as well as services, installation and billing – all from a single source: complete turnkey solutions, in-house developments, remote maintenance, emergency communication, backup solutions, telematics systems and much more.

Our solutions offer, among other things, secure 1:1, 1:n and n:n communication in crises and emergency situations. Whether within an organisation or across the board with authorities and all participating companies. Either via satellite communication or via functioning internet connections.

==Description==
REDCOM-Conference is a powerful software extension for the GESAT REDCOM server, developed specifically for use in mobile and high-availability communication environments. The solution builds on the innovaphone suite and specifically extends existing terrestrial radio connections with a satellite-based link.

Through the integration of Eutelsat OneWeb, REDCOM-Conference enables a significant increase in the reliability and redundancy of the communications infrastructure. Even in remote operational areas or in the event of a failure of conventional networks, communications remain stable and available.

The solution allows a remote PBX to be operated directly in the field. This enables users not only to ensure basic voice communication but also to conduct telephone and video conferences with external participants in real time. This is of particular benefit to emergency services, crisis management teams or temporary infrastructure projects.

==Functions==
* Extension of terrestrial radio links via satellite-based communication
* Integration of Eutelsat OneWeb for global connectivity
* Increased reliability and redundancy
* Use of a mobile telecommunications system in the field
* Support for telephone and video conferencing
* Seamless integration as an add-on to the GESAT REDCOM server

==Version==




Product versions used for interop testing:

* Version 1.0

* innovaphone V15r1sr8

==Summary==
REDCOM-Conference extends the GESAT REDCOM server with a LEO satellite-based IP connection via Eutelsat OneWeb. The solution supplements terrestrial radio and IP links with a redundant, independent transmission path and enables the operation of a remote telecommunications infrastructure, including SIP telephony and audio/video conferencing in the field. It is designed for high-availability, mobile and safety-critical communication environments.

==Contact==
{|
| GESAT GmbH
|-
| Sales
|-
| Hanauer Landstrasse 220
|-
| 60314 Frankfurt am Main - Germany
|-
| Tel: +49(0)69962180-10
|-
| Fax: +49(0)69962180-99
|-
| Mail: sat@gesat.com
|}

Howto:REDCOM-Conference - GESAT - 3rd Party Product

2026-03-30T12:22:32Z

Vsc: /* Category */

[[Image:GesatLogo.png|200px|right|/GesatLogo.png|/GesatLogo.png]]

==Product Name==
[https://www.gesat.com/?lang=en Gesat] REDCOM Conference

REDCOM Conference as an add-on to the GESAT REDCOM Server

==Certification Status==




==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Conferencing_/_Video_Systems}}
[[Category:3rdParty_Conferencing_/_Video_Systems|{{PAGENAME}}]]

==Vendor==
[[Image:GesatLogo.png|150px|/GesatLogo.png|/GesatLogo.png]]

GESAT GmbH, the specialist for satellite communication solutions since 1989, has been a long-standing partner of authorities and agencies at federal, state and local level,
as well as of emergency services, CRITIS companies and companies that want or need to maintain their business continuity.

As one of the leading providers of satellite communication, we offer you manufacturer-independent hardware as well as services, installation and billing – all from a single source: complete turnkey solutions, in-house developments, remote maintenance, emergency communication, backup solutions, telematics systems and much more.

Our solutions offer, among other things, secure 1:1, 1:n and n:n communication in crises and emergency situations. Whether within an organisation or across the board with authorities and all participating companies. Either via satellite communication or via functioning internet connections.

==Description==
REDCOM-Conference is a powerful software extension for the GESAT REDCOM server, developed specifically for use in mobile and high-availability communication environments. The solution builds on the innovaphone suite and specifically extends existing terrestrial radio connections with a satellite-based link.

Through the integration of Eutelsat OneWeb, REDCOM-Conference enables a significant increase in the reliability and redundancy of the communications infrastructure. Even in remote operational areas or in the event of a failure of conventional networks, communications remain stable and available.

The solution allows a remote PBX to be operated directly in the field. This enables users not only to ensure basic voice communication but also to conduct telephone and video conferences with external participants in real time. This is of particular benefit to emergency services, crisis management teams or temporary infrastructure projects.

==Functions==
* Extension of terrestrial radio links via satellite-based communication
* Integration of Eutelsat OneWeb for global connectivity
* Increased reliability and redundancy
* Use of a mobile telecommunications system in the field
* Support for telephone and video conferencing
* Seamless integration as an add-on to the GESAT REDCOM server

==Version==




Product versions used for interop testing:

* Version 1.0

* innovaphone V12r2sr24

==Configuration==






==Summary==
REDCOM-Conference extends the GESAT REDCOM server with a LEO satellite-based IP connection via Eutelsat OneWeb. The solution supplements terrestrial radio and IP links with a redundant, independent transmission path and enables the operation of a remote telecommunications infrastructure, including SIP telephony and audio/video conferencing in the field. It is designed for high-availability, mobile and safety-critical communication environments.

==Contact==
{|
| GESAT GmbH
|-
| Sales
|-
| Hanauer Landstrasse 220
|-
| 60314 Frankfurt am Main - Germany
|-
| Tel: +49(0)69962180-10
|-
| Fax: +49(0)69962180-99
|-
| Mail: sat@gesat.com
|}

Howto:REDCOM-Conference - GESAT - 3rd Party Product

2026-03-30T12:15:09Z

Vsc: Created page with " /GesatLogo.png ==Product Name== [https://www.gesat.com/?lang=en Gesat] REDCOM Conference REDCOM Conference as an add-on to the GESAT REDCOM Server ==Certification Status==  <!-- {{Template:Compat_Status_referral_product_new}} -..."

[[Image:GesatLogo.png|200px|right|/GesatLogo.png|/GesatLogo.png]]

==Product Name==
[https://www.gesat.com/?lang=en Gesat] REDCOM Conference

REDCOM Conference as an add-on to the GESAT REDCOM Server

==Certification Status==




==Category==
{{Category:3rdParty Conferencing / Video Systems}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:Category:3rdParty Conferencing / Video Systems|{{PAGENAME}}]]

==Vendor==
[[Image:GesatLogo.png|150px|/GesatLogo.png|/GesatLogo.png]]

GESAT GmbH, the specialist for satellite communication solutions since 1989, has been a long-standing partner of authorities and agencies at federal, state and local level,
as well as of emergency services, CRITIS companies and companies that want or need to maintain their business continuity.

As one of the leading providers of satellite communication, we offer you manufacturer-independent hardware as well as services, installation and billing – all from a single source: complete turnkey solutions, in-house developments, remote maintenance, emergency communication, backup solutions, telematics systems and much more.

Our solutions offer, among other things, secure 1:1, 1:n and n:n communication in crises and emergency situations. Whether within an organisation or across the board with authorities and all participating companies. Either via satellite communication or via functioning internet connections.

==Description==
REDCOM-Conference is a powerful software extension for the GESAT REDCOM server, developed specifically for use in mobile and high-availability communication environments. The solution builds on the innovaphone suite and specifically extends existing terrestrial radio connections with a satellite-based link.

Through the integration of Eutelsat OneWeb, REDCOM-Conference enables a significant increase in the reliability and redundancy of the communications infrastructure. Even in remote operational areas or in the event of a failure of conventional networks, communications remain stable and available.

The solution allows a remote PBX to be operated directly in the field. This enables users not only to ensure basic voice communication but also to conduct telephone and video conferences with external participants in real time. This is of particular benefit to emergency services, crisis management teams or temporary infrastructure projects.

==Functions==
* Extension of terrestrial radio links via satellite-based communication
* Integration of Eutelsat OneWeb for global connectivity
* Increased reliability and redundancy
* Use of a mobile telecommunications system in the field
* Support for telephone and video conferencing
* Seamless integration as an add-on to the GESAT REDCOM server

==Version==




Product versions used for interop testing:

* Version 1.0

* innovaphone V12r2sr24

==Configuration==






==Summary==
REDCOM-Conference extends the GESAT REDCOM server with a LEO satellite-based IP connection via Eutelsat OneWeb. The solution supplements terrestrial radio and IP links with a redundant, independent transmission path and enables the operation of a remote telecommunications infrastructure, including SIP telephony and audio/video conferencing in the field. It is designed for high-availability, mobile and safety-critical communication environments.

==Contact==
{|
| GESAT GmbH
|-
| Sales
|-
| Hanauer Landstrasse 220
|-
| 60314 Frankfurt am Main - Germany
|-
| Tel: +49(0)69962180-10
|-
| Fax: +49(0)69962180-99
|-
| Mail: sat@gesat.com
|}

File:GesatLogo.png

2026-03-30T12:14:23Z

Vsc:

Datasheet App IP

2026-03-25T14:06:34Z

Vsc: Created page with "{{datasheet_header|innovaphone APPIP|Virtual communication platform}} <div class="datasheets-mehrspaltig"> Image:appip.png ===Firmware=== * Appliance operated with firmware version 16r1 or higher * Requires innovaphone myApps Application Platform version 140011 or higher ===Interfaces=== * Uses network connectivity of innovaphone myApps Application Platform * optional ISDN-connectivity with ISDN-capable innovaphone gateway ===Hardware=== Hardware independent; operate..."

{{datasheet_header|innovaphone APPIP|Virtual communication platform}}
<div class="datasheets-mehrspaltig">
[[Image:appip.png]]
===Firmware===
* Appliance operated with firmware version 16r1 or higher
* Requires innovaphone myApps Application Platform version 140011 or higher
===Interfaces===
* Uses network connectivity of innovaphone myApps Application Platform
* optional ISDN-connectivity with ISDN-capable innovaphone gateway
===Hardware===
Hardware independent; operated on top of innovaphone Application Platform

System requirements innovaphone Application Platform depend on used hardware

Soft Conferencing (without DSP) for up to 100 voice / conference channels G.711a/u-law

Channels for the innovaphone faxserver using T.38.

===virtual innovaphone PBX===
Executed as application in innovaphone Application Platform

===Use cases===
Hosting platform – several PBX using the same HW, customer separation

Seamless scalable – ranges from entry level platform for SMEs to large enterprises

Managed services

===Voice Codecs===
G.711 A-law / µ-law

{{Gateway_Firmware_Technische_Daten_EN|appip=false}}

{{Template:Leistungsmerkmale EN - Lizenzen Gateways}}

{{Template:CE-Decl_Gateways|Conformities|see separate information sheet}}
===Order Number IPAP license (for each port license used): 02-00043-003===
</div>
{{Template:Datasheet_footer|EN}}

[[Category:Technical Data Gateways EN|{{PAGENAME}}]]

Howto:File Transfer - MediaRunway - Partner App

2026-03-24T10:38:54Z

Vsc: /* Description */

[[Image:Mediarunway_company_logo_200.png|200px|right|/Mediarunway_company_logo_200.png]]

==Product Name==



MediaRunway [https://mediarunway.com/myapps/ File Tranfser]

==Certification Status==


==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:Mediarunway_company_logo_150_2.png|150px|/Mediarunway_company_logo_150_2.png]]




MediaRunway is an ITC enterprise that provides its customers with contemporary IT services in all areas - Your business, our solution.


[https://www.mediarunway.com/ MediaRunway - About us]

==Description==




[[Image:MediaRunway-filetransfer-icon.png|/MediaRunway-filetransfer-icon.png]]





'''File Transfer''' myApps App:

Allows to exchange files that are too large for email! There are also many other good reasons to share files better with this file transfer app. Encrypted, password-protected and limitable file transfer via your OWN system.


[https://mediarunway.com/myapps/ MediaRunway - About this application]





==Functions==



'''User App'''
Each user can upload file(s) and share a link to users for downloading this files. Also the user can send a link, that another user can upload files.

'''Admin App'''
Use the Admin App to configure email server settings, set the pbx name for a multi pbx scenario, etc.

===Multi-PBX ready===




There are no known restrictions.

===Cloud ready===




There are no known restrictions.

==Licensing==


Licensing: innovaphone licensing, each user who get the user app needs a license. [https://www.innovaphone.com/en/services/licenses/partner-apps.html?app=FileTransfer&type=license#filetransfer More infos]

==Prerequisites==





* An innovaphone PBX and Application Platform
* Valid licences

==Versions==



===Compatible innovaphone firmware versions===


* MediaRunway File Transfer 1.x (151xxxx)
** innovaphone V15r1

===Application versions used for interop testing===



* MediaRunway File Transfer 1.x (151xxxx)

** innovaphone IPVA V15r1 sr6

==Configuration==








In the admin app can be configured:
* pbx name for a multipbx scenario
* email server

==Installation==
After installing the app, adding the app instance and the app object for the users and the admin, one can start using "Call Info Plus". The steps of the installation process are the same as described in this article [https://wiki.innovaphone.com/index.php?title=Howto:Callback_-_mediarunway_-_3rd_Party_Product#Install_app_from_App_Store "Callback - Install App from App Store"] only with different names.

==Contact==




{|
| MediaRunway GmbH & Co. KG
|-
| Venloer Str. 8
|-
| D-41569 Rommerskirchen
|-
| Tel: +49 2183 80628-0
|-
| Mail: [mailto:myApps-sales@mediarunway.com myApps-sales@mediarunway.com]
|-
| Support: [mailto:myApps-support@mediarunway.com myApps-support@mediarunway.com]
|-
| Website: [https://www.mediarunway.com/ MediaRunway.com]
|}

For any questions please refer to [https://mediarunway.com/contact/ our contact page].

Howto:Call Forward - MediaRunway - Partner App

2026-03-24T10:38:51Z

Vsc: /* Description */

[[Image:Mediarunway_company_logo_200.png||200px|right]]

==Product Name==



MediaRunway [https://mediarunway.com/myapps/ Call Forward]

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

This App was listed July 2024.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:Mediarunway_company_logo_150_2.png|150px]]




MediaRunway is an ITC enterprise that provides its customers with contemporary IT services in all areas - Your business, our solution.


[https://www.mediarunway.com/ MediaRunway - About us]

==Description==




[[Image:mediarunway-callforward.png]]





'''Call Forward''' myApps App:

Allows one or more users to configure call forwarding for other users and PBX objects.


[https://mediarunway.com/myapps/ MediaRunway - About this application]





==Functions==



'''Personal App'''
* configure own call forwards
** internal incoming calls: set the destination to forward the call
** external incoming calls: set the destination to forward the call
* lookup last entries in a list
* activate/deactivate call forwards
[[Image:mediarunway-callforward-personal.png]]

'''User App'''
* search for pbx object
* add, change or delete call forward config of the selected pbx object
* configuration options:
** cfu (direct), cfnr (not reachable), cfb (busy)
** number or object where to forward the call with autocomplete
** set a timeperiod restriction by configured boolean object(s)
[[File:Mediarunway-callforward-user.png|alt=User GUI]]

'''Admin App'''
* set the pbx name (for master/slave scenarios)
* set trunk and region prefix to allow number conversion
[[Image:mediarunway-callforward-admin-configuration.png]]
* set permissions (all, blacklist, whitelist) and select specific pbx objects for the user app
[[File:Mediarunway-callforward-admin-permissions.png|alt=Admin GUI permissions]]
* set fixed favorites for the user app
[[Image:mediarunway-callforward-admin-favorites.png]]
* set prefix for personal call forwards
[[Image:mediarunway-callforward-admin-personal-configuration.png]]

===Multi-PBX ready===




There are no known restrictions, but have a look here to configuration to set the pbx name.

===Cloud ready===




There are no known restrictions.

==Licensing==


Licensing: innovaphone licensing, each user who gets the user/personal app needs a license. The user and personal apps have different licenses. [https://www.innovaphone.com/en/services/licenses/partner-apps.html?app=Analytics&type=license#callforward More infos]

==Prerequisites==





* an innovaphone PBX and Application Platform
* valid licences
* knowledge of the pbx name of the pbx where to synchronize with

==Versions==



===Compatible innovaphone firmware versions===


* MediaRunway Call Forward 1.0 (133xxx)
** innovaphone V13r3, V14r1

===Application versions used for interop testing===



* MediaRunway Call Forward 1.0 (133xxx)

** innovaphone IPVA V13r3 sr15

==Configuration==







In a Master/Slave scenario set the PBX name of the pbx where to synchronize with in the Call Forward Admin App under "Configuration" in the hamburger menu
[[File:MediaRunway-callforward-admin-configuration.png|alt=Admin GUI Configuration]]

Maybe set permissions that a user who has access to the call forward user app could only change the call forward settings of the configured pbx objects.
* if "all" is selected, the selected objects under the select box are ignored, because all possible pbx objects could be choosen in the call forward user app
* if "whitelist" is selected, only these objects where the switch is green could be searched and configured in the call forward user app
* if "blacklist" is selected, all the objects where the switch isn´t green could be searched and configured in the call forward user app
[[File:Mediarunway-callforward-admin-permissions.png|alt=Admin GUI permissions]]

==Installation==
After installing the app, adding the app instance and the app object for the users and the admin, someone can start using "Call Forward". The steps of the installation process are the same as described in this article [https://wiki.innovaphone.com/index.php?title=Howto:Callback_-_mediarunway_-_3rd_Party_Product#Install_app_from_App_Store "Callback - Install App from App Store"] only with different names.

===Brief summary of the installation===
* Install the app from app store
* Create an instance of the app
** Values needed: Name (e.g. "callforward", no blanks here please) - Domain (your platform domain) - App Password (generate one, e.g. with 15 characters) - DB Password (generate one, e.g. with 15 characters) - other values will be filled up automatically
* Add the user and the admin object with PbxManager app (when selecting the name, please do not use spaces)
* [https://wiki.innovaphone.com/index.php?title=Howto:Call_Forward_-_MediaRunway_-_Partner_App#Configuration]

==Contact==




{|
| MediaRunway GmbH & Co. KG
|-
| Venloer Str. 8
|-
| D-41569 Rommerskirchen
|-
| Tel: +49 2183 80628-0
|-
| Mail: [mailto:myApps-sales@mediarunway.com myApps-sales@mediarunway.com]
|-
| Support: [mailto:myApps-support@mediarunway.com myApps-support@mediarunway.com]
|-
| Website: [https://www.mediarunway.com/ MediaRunway.com]
|}

For any questions please refer to [https://mediarunway.com/contact/ our contact page].

Howto:File Transfer - MediaRunway - Partner App

2026-03-24T10:36:41Z

Vsc: /* Category */

[[Image:Mediarunway_company_logo_200.png|200px|right|/Mediarunway_company_logo_200.png]]

==Product Name==



MediaRunway [https://mediarunway.com/myapps/ File Tranfser]

==Certification Status==


==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:Mediarunway_company_logo_150_2.png|150px|/Mediarunway_company_logo_150_2.png]]




MediaRunway is an ITC enterprise that provides its customers with contemporary IT services in all areas - Your business, our solution.


[https://www.mediarunway.com/ MediaRunway - About us]

==Description==




[[Image:MediaRunway-filetransfer-icon.png|/MediaRunway-filetransfer-icon.png]]





'''File Transfer''' myApps App:
Allows you to exchange files that are too large for email! There are also many other good reasons to share files better with this file transfer app. Encrypted, password-protected and limitable file transfer via your OWN system.


[https://mediarunway.com/myapps/ MediaRunway - About this application]





==Functions==



'''User App'''
Each user can upload file(s) and share a link to users for downloading this files. Also the user can send a link, that another user can upload files.

'''Admin App'''
Use the Admin App to configure email server settings, set the pbx name for a multi pbx scenario, etc.

===Multi-PBX ready===




There are no known restrictions.

===Cloud ready===




There are no known restrictions.

==Licensing==


Licensing: innovaphone licensing, each user who get the user app needs a license. [https://www.innovaphone.com/en/services/licenses/partner-apps.html?app=FileTransfer&type=license#filetransfer More infos]

==Prerequisites==





* An innovaphone PBX and Application Platform
* Valid licences

==Versions==



===Compatible innovaphone firmware versions===


* MediaRunway File Transfer 1.x (151xxxx)
** innovaphone V15r1

===Application versions used for interop testing===



* MediaRunway File Transfer 1.x (151xxxx)

** innovaphone IPVA V15r1 sr6

==Configuration==








In the admin app can be configured:
* pbx name for a multipbx scenario
* email server

==Installation==
After installing the app, adding the app instance and the app object for the users and the admin, one can start using "Call Info Plus". The steps of the installation process are the same as described in this article [https://wiki.innovaphone.com/index.php?title=Howto:Callback_-_mediarunway_-_3rd_Party_Product#Install_app_from_App_Store "Callback - Install App from App Store"] only with different names.

==Contact==




{|
| MediaRunway GmbH & Co. KG
|-
| Venloer Str. 8
|-
| D-41569 Rommerskirchen
|-
| Tel: +49 2183 80628-0
|-
| Mail: [mailto:myApps-sales@mediarunway.com myApps-sales@mediarunway.com]
|-
| Support: [mailto:myApps-support@mediarunway.com myApps-support@mediarunway.com]
|-
| Website: [https://www.mediarunway.com/ MediaRunway.com]
|}

For any questions please refer to [https://mediarunway.com/contact/ our contact page].