innovaphone wiki - User contributions [en]

Reference16r1:Concept innovaphone App Platform Container

2026-07-07T15:13:01Z

Afi: /* Requirements */ add ARM64 support and multi arch

The innovaphone App Platform Container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

== Applies To ==

* innovaphone App Platform Container

==Requirements==
* A container runtime supporting the OCI (Open Container Initiative) image format — e.g. Docker, Kubernetes, containerd, or CRI-O
* A host on a x86_64 (amd64) or arm64 (aarch64) platform
* innovaphone App Platform Container

The container image is built and published as a standard OCI-compliant, multi-architecture image. It can be run directly with Docker or deployed on Kubernetes (or any other OCI-compatible platform). The runtime automatically selects the correct image variant (amd64 or arm64) matching the host platform — no additional configuration or platform flags are required.

==Image Tags==
Each released build is published under a numeric version tag (e.g. <code>140048</code>), pointing to a multi-architecture manifest covering both amd64 and arm64. Architecture-specific tags are also published for each build, using the suffix <code>-amd64</code> or <code>-arm64</code> (e.g. <code>140048-amd64</code>, <code>140048-arm64</code>), for cases where a specific platform variant needs to be pulled explicitly.

The <code>latest</code> tag always points to the most recent stable build and, like the numeric version tags, is published as a multi-architecture manifest. Corresponding <code>latest-amd64</code> and <code>latest-arm64</code> tags are also available.

==Concept==

The innovaphone App Platform Container provides the innovaphone App Platform for container environments (Open Container Initiative (OCI) format).

* The App Platform Manager and Webserver Apps are already integrated in the container and provide the already known functionality.
* Apps are installed, updated and managed as usual.
* The mount point will be used for the database, the App binaries and log files.

==Image Information==

This chapter provides details about the Docker image used for the innovaphone App Platform.

===Repository Details===

;Repository Host : registry.innovaphone.com
;Image Name : cloud/kubernetes/innovaphone-platform-instance

registry.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

===Tagging and Versioning===
The image is usually tagged with the build number according to innovaphone software releases:

;Latest Tag : Use the latest tag for pulling the most recent service release.

;Release Build Number : For production or version-specific deployments, use a specific build number as the tag (e.g., 130006).

Example:
docker pull registry.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

===Supported Architecture===
This Docker image supports the <code>linux/amd64</code> architecture.

===Image Reference===
An example of a full image reference using a specific release build number would be:
registry.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

==Ports==
This chapter outlines the various ports exposed by the container. The webserver ports are available immediately upon container startup, after start of the AP Manager and the Webserver, while the additional application ports become active after the app installation. In most cases, a one-to-one mapping is used, meaning the container port is mapped directly to the same host port unless otherwise specified.

===Ports < 1024===
On most docker hosts, a container won't be able to use ports below 1024, unless the container is started with higher privileges.
This shouldn't be neccessary anyways as all ports can be configured to higher ports.

===Webserver Ports===
;HTTP:
Container Port: 8080
Description: Used for accessing the built-in webserver immediately upon container startup.

;HTTPS:
Container Port: 8082
Description: Used for accessing the built-in webserver immediately upon container startup.

=== Additional Application Ports===
Following additional container ports are avilable depending on installed and configured applications:
;H323/TLS : 1300
;SIP : 5060
;SIPS : 5061
;LDAPS : 1636
;SMTP : 8025
;SMTPS : 8587
;STUN/TURN : 3478 UDP/TCP
'''Additional hint for Portmapping'''<syntaxhighlight lang="yaml" line="1">
docker run -d \
--name=innovaphone \
--restart unless-stopped \
-p 9090:8080 \ #Container Host Port (external) 9090:8080 Container Port
-p 9091:8082 \
-p 5060:5060 \
-p 5061:5061 \
-p 1300:1300 \
-p 1636:1636 \
-p 8025:8025 \
-p 8587:8587 \
-p 3478:3478 \
-p 3478:3478/udp \
-v /path/of/data/innovaphone:/mnt/data \ #in this path you will find Apps, DBs & Logs
#this path musst be used for backups!!
-e WEBSERVERPORTHTTP=8080 \
-e WEBSERVERPORTHTTPS=8082 \
-e LOG_FLAGS=7 \
-e LOG_SIZE=1048576 \
-e DNSIPV4=8.8.8.8 \
-e LIMIT_RAM=512 \ #Ram limit in MB
-e LIMIT_DISK=10 \ #disk size in GB
-e TZ=Europe/Berlin \
registry.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

</syntaxhighlight>

==Environment Variables (ENVs)==
This chapter outlines the key environment variables used to configure the behavior of the innovaphone App Platform Container. These variables allow you to customize logging, port settings, resource limits, and more during startup and runtime.

;LOG_FLAGS : Defines the integer representation for the trace flags of the AP Manager, according flags activated under the AP Manager / Diagnostics. See browser console message on Save button press (e.g. "logFlags":1 , if the "App" flag is activated).
LOG_FLAGS=7
;LOG_SIZE : Specifies the maximum size in bytes for logs before rotation or management actions occur. Default: 5242880.
LOG_SIZE=1048576
;WEBSERVERPORTHTTP : Sets the in-container HTTP port for the webserver. Default: 8080.
WEBSERVERPORTHTTP=8080
;WEBSERVERPORTHTTPS : Sets the in-container HTTPS port for the webserver. Default: 8082.
WEBSERVERPORTHTTPS=8443
;DNSIPV4 : Specifies the in-container DNS server IPv4 address for DNS resolution. Overrides the default container runtime DNS server.
DNSIPV4=8.8.8.8
;DNS_DOMAIN : The FQDN of the App Platform that can be used to access the app services. This optional parameter is used as a static DNS entry added to /etc/hosts. The destination IP address is the resolved IP address behind INTERNAL_DNS_DOMAIN or NAMESPACE.
DNS_DOMAIN=ap.example.com
;INTERNAL_DNS_DOMAIN : The internal FQDN of the App Platform. This FQDN is used to resolve the internal IP address of the App Platform, to be mapped from DNS_DOMAIN in /etc/hosts.
INTERNAL_DNS_DOMAIN=my-apps-deployment.my-namespace.svc.cluster.local
;NAMESPACE : The Kubernetes namespace used to build internal FQDN of the App Platform. Used with DNS_DOMAIN to map it to the IP address of ap.my-namespace.svc.cluster.local.
NAMESPACE=my-namespace
;LIMIT_RAM : Sets the RAM limit for the container, in MB, controlling how much memory it may consume. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_RAM=512
;LIMIT_DISK : Defines the disk space limit in GB for the container to manage storage consumption. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_DISK=10

==File limits==
Containers may have a default file limit per process, e.g. 1024 files. Depending on your installation and usage, this value is too small and you need to allow more, e.g. handing this in the docker run command:
--ulimit nofile=500000:500000

==Volumes and Mounts==
This container uses a dedicated internal mount path for the persistent data management across container restarts and updates.

===Internal Data Volume===
;Mount Path : <code>/mnt/data</code>
;Contents:
*Apps: Installed application binaries.
*Databases: PostgreSQL files.
*Logging: Log files for system and application events.

===Mounting===
To ensure that your data is preserved, map a host directory or Docker named volume to the container's /mnt/data path when running the container.
For example:
docker run -d -v /path/on/host:/mnt/data registry.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

This setup guarantees that your apps, associated data, databases, and logs persist independently of the container lifecycle.

==Entrypoint==
The container uses a fixed entrypoint:
ENTRYPOINT ["/entrypoint.sh"]

This script prepares the container and starts the AP Manager executable.

==Logging and Monitoring==
The log of the entrypoint.sh and of the AP manager is avilable as conatiner output. The installed applications store the ir log files under <code>/mnt/data/var/log/apps/</code>.

=== Unexpected high system load ===
If you encounter a high load, you need to verify whether the load is actually coming from your container. Docker containers always display the load of the physical host system.

It may be that the Docker host itself is also virtualized as an LXC container, and your Docker instances are running within it. In such a setup, the system load of the physical host is displayed because <code>/proc/loadavg</code> is not isolated per logical layer.

An increased load in the container therefore does not automatically mean that the container itself is the cause or that you have a problem at all. In short: To assess the load, you always need information (e.g., number of CPU cores or I/O information) from the physical host.

==Usage Example==
sudo docker run -d --ulimit nofile=500000:500000 --restart unless-stopped --name innovaphoneAP -p 9090:8080 -p 9091:8082 -e WEBSERVERPORTHTTP=8080 -e WEBSERVERPORTHTTPS=8082 -v $(pwd)/myapps/:/mnt/data registry.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

This command runs the container in detached mode with automatic restart. It names the container innovaphoneAP, maps host ports 9090 and 9091 to the container's HTTP and HTTPS ports, sets the webserver port environment variables, mounts a host directory to /mnt/data, and starts the AP Manager. After container start up the AP manager web UI is accessible via <code>http://localhost:9090</code> or <code>https://localhost:9091</code>.

== Related Articles ==
[https://wiki.innovaphone.com/index.php?title=Howto16r1:Step-by-Step_Docker_Compose_Container_Deployment Step-by-Step Docker Compose Container Deployment]

User:Afi

2025-12-02T09:41:15Z

Afi:

Andreas Fink
Development

innovaphone AG
Umberto-Nobile-Straße 15
71063 Sindelfingen
Germany
Fon: +49 (7031) 73009 23
Fax: +49 (7031) 73009 523

Reference16r1:Concept innovaphone App Platform Container

2025-11-10T12:29:31Z

Afi: /* Environment Variables (ENVs) */ added DNS_DOMAIN, INTERNAL_DNS_DOMAIN and NAMESPACE

{{FIXME|reason=Below described feature is experimental and not officially supported for use in productive environments.}}
The innovaphone App Platform Docker container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

==Image Information==

This chapter provides details about the Docker image used for the innovaphone App Platform.

===Repository Details===

;Repository Host : docker.innovaphone.com
;Image Name : cloud/kubernetes/innovaphone-platform-instance

docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

===Tagging and Versioning===
The image is usually tagged with the build number according to innovaphone software releases:

;Latest Tag : Use the latest tag for pulling the most recent service release.

;Release Build Number : For production or version-specific deployments, use a specific build number as the tag (e.g., 130006).

Example:
docker pull docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

===Supported Architecture===
This Docker image supports the <code>linux/amd64</code> architecture.

===Image Reference===
An example of a full image reference using a specific release build number would be:
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

==Ports==
This chapter outlines the various ports exposed by the Docker container. The webserver ports are available immediately upon container startup, after start of the AP Manager and the Webserver, while the additional application ports become active after the app installation. In most cases, a one-to-one mapping is used, meaning the container port is mapped directly to the same host port unless otherwise specified.

===Webserver Ports===
;HTTP:
Container Port: 8080
Description: Used for accessing the built-in webserver immediately upon container startup.

;HTTPS:
Container Port: 8082
Description: Used for accessing the built-in webserver immediately upon container startup.

=== Additional Application Ports===
Following additional container ports are avilable depending on installed and configured applications:
;H323/TLS : 1300
;SIP : 5060
;SIPS : 5061
;LDAPS : 1636
;SMTP : 8025
;SMTPS : 8587
'''Additional hint for Portmapping'''<syntaxhighlight lang="yaml" line="1">
docker run -d \
--name=innovaphone \
--restart unless-stopped \
-p 9090:8080 \ #Container Host Port (external) 9090:8080 Container Port
-p 9091:8082 \
-p 5060:5060 \
-p 5061:5061 \
-p 1300:1300 \
-p 1636:1636 \
-p 8025:8025 \
-p 8587:8587 \
-v /path/of/data/innovaphone:/mnt/data \ #in this path you will find Apps, DBs & Logs
#this path musst be used for backups!!
-e WEBSERVERPORTHTTP=8080 \
-e WEBSERVERPORTHTTPS=8082 \
-e LOG_FLAGS=7 \
-e LOG_SIZE=1048576 \
-e DNSIPV4=8.8.8.8 \
-e LIMIT_RAM=512 \ #Ram limit in MB
-e LIMIT_DISK=10 \ #disk size in GB
-e TZ=Europe/Berlin \
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

</syntaxhighlight>

==Environment Variables (ENVs)==
This chapter outlines the key environment variables used to configure the behavior of the innovaphone App Platform Docker container. These variables allow you to customize logging, port settings, resource limits, and more during startup and runtime.

;LOG_FLAGS : Defines the integer representation for the trace flags of the AP Manager, according flags activated under the AP Manager / Diagnostics. See browser console message on Save button press (e.g. "logFlags":1 , if the "App" flag is activated).
LOG_FLAGS=7
;LOG_SIZE : Specifies the maximum size in bytes for logs before rotation or management actions occur. Default: 5242880.
LOG_SIZE=1048576
;WEBSERVERPORTHTTP : Sets the in-container HTTP port for the webserver. Default: 8080.
WEBSERVERPORTHTTP=8080
;WEBSERVERPORTHTTPS : Sets the in-container HTTPS port for the webserver. Default: 8082.
WEBSERVERPORTHTTPS=8443
;DNSIPV4 : Specifies the in-container DNS server IPv4 address for DNS resolution. Overrides the default container runtime DNS server.
DNSIPV4=8.8.8.8
;DNS_DOMAIN : The FQDN of the App Platform that can be used to access the app services. This optional parameter is used as a static DNS entry added to /etc/hosts. The destination IP address is the resolved IP address behind INTERNAL_DNS_DOMAIN or NAMESPACE.
DNS_DOMAIN=ap.example.com
;INTERNAL_DNS_DOMAIN : The internal FQDN of the App Platform. This FQDN is used to resolve the internal IP address of the App Platform, to be mapped from DNS_DOMAIN in /etc/hosts.
INTERNAL_DNS_DOMAIN=my-apps-deployment.my-namespace.svc.cluster.local
;NAMESPACE : The Kubernetes namespace used to build internal FQDN of the App Platform. Used with DNS_DOMAIN to map it to the IP address of ap.my-namespace.svc.cluster.local.
NAMESPACE=my-namespace
;LIMIT_RAM : Sets the RAM limit for the container, in MB, controlling how much memory it may consume. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_RAM=512
;LIMIT_DISK : Defines the disk space limit in GB for the container to manage storage consumption. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_DISK=10
;MANAGER_DB_HOST : defines an external database host for the database of the App Platform Manager
If you hand database settings, the container will work without the local database server and doesn't need any storage at all (under development).
MANAGER_DB_HOST=172.16.14.35:5432 (port is optional)
;MANAGER_DB_NAME : the external database name
MANAGER_DB_NAME=databasename
;MANAGER_DB_USER : the external database user who has access
MANAGER_DB_USER=databaseuser
;MANAGER_DB_PASSWORD : the password of the user
MANAGER_DB_PASSWORD=o1kk2hj312k3
;DB_PROVISIONER_URL : a websocket URL to an external DBProvisioner App which is used to provide databases
DB_PROVISIONER_URL=wss://domain.com/domain.com/dbprovisioner

==Volumes and Mounts==
This container uses a dedicated internal mount path for the persistent data management across container restarts and updates.

===Internal Data Volume===
;Mount Path : <code>/mnt/data</code>
;Contents:
*Apps: Installed application binaries.
*Databases: PostgreSQL files.
*Logging: Log files for system and application events.

===Mounting===
To ensure that your data is preserved, map a host directory or Docker named volume to the container's /mnt/data path when running the container.
For example:
docker run -d -v /path/on/host:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

This setup guarantees that your apps, associated data, databases, and logs persist independently of the container lifecycle.

==Entrypoint==
The container uses a fixed entrypoint:
ENTRYPOINT ["/entrypoint.sh"]

This script prepares the container and starts the AP Manager executable.

==Logging and Monitoring==
The log of the entrypoint.sh and of the AP manager is avilable as conatiner output. The installed applications store the ir log files under <code>/mnt/data/var/log/apps/</code>.

==Usage Example==
sudo docker run -d --restart unless-stopped --name innovaphoneAP -p 9090:8080 -p 9091:8082 -e WEBSERVERPORTHTTP=8080 -e WEBSERVERPORTHTTPS=8082 -v $(pwd)/myapps/:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

This command runs the container in detached mode with automatic restart. It names the container innovaphoneAP, maps host ports 9090 and 9091 to the container's HTTP and HTTPS ports, sets the webserver port environment variables, mounts a host directory to /mnt/data, and starts the AP Manager. After container start up the AP manager web UI is accessible via <code>http://localhost:9090</code> or <code>https://localhost:9091</code>.

Datasheet AP container

2025-08-12T09:09:06Z

Afi: Created page with "{{datasheet_header|innovaphone App Platform|Containerized Application Platform}} <div class="datasheets-mehrspaltig"> '''Technical Preview:''' This container is intended for evaluation and testing purposes only. It is not supported for production use. ===Core Components=== * innovaphone App Plattform * AP Manager * Webserver * PostgreSQL Database ===System Requirements=== Host OS: Linux with Kernel 5.10 or newer Host Environment: Container Runtime CPU: 2 Cores (minimum..."

{{datasheet_header|innovaphone App Platform|Containerized Application Platform}}
<div class="datasheets-mehrspaltig">
'''Technical Preview:''' This container is intended for evaluation and testing purposes only. It is not supported for production use.

===Core Components===
* innovaphone App Plattform
* AP Manager
* Webserver
* PostgreSQL Database

===System Requirements===
Host OS: Linux with Kernel 5.10 or newer
Host Environment: Container Runtime
CPU: 2 Cores (minimum)
RAM: 256 MB (minimum)
Disk Space: 20 GB (recommended)

===Performance===
Platform for up to 8000 registrations

===Image Details===
Repository Host: docker.innovaphone.com
Image Name: cloud/kubernetes/innovaphone-platform-instance
Supported Architecture: linux/amd64
Approx. Image Size: 197 MB

===Network Ports===
Webserver Ports (available on startup):
* HTTP: 8080/tcp
* HTTPS: 8082/tcp

Additional Application Ports (available after app installation):
* H323/TLS: 1300/tcp
* SIP: 5060/tcp/udp
* SIPS: 5061/tcp
* LDAPS: 1636/tcp
* SMTP: 8025/tcp
* SMTPS: 8587/tcp

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

===Persistent Storage===
Persistent storage volume for use by installed Apps and their databases

</div>
{{Template:Datasheet_footer|EN}}

[[Category:Technical Data App Platform EN|{{PAGENAME}}]]

Reference:Opensource

2025-05-08T10:06:33Z

Afi: Link to sdk.innovaphone.com 14r2 => 15r1

This article lists the opensource software that is used in innovaphone products.

Please note that there is a separate article for the innovaphone App Platform and the innovaphone SDK that can be found here: [https://sdk.innovaphone.com/15r1/doc/copyright.htm https://sdk.innovaphone.com/15r1/doc/copyright.htm]

== AES ==
Our AES implementation in software is derived from:
* Official name: AES implementation by Brian Gladman
* Version number: Issue 09/09/2006
* URL for source: http://brgladman.org/oldsite/cryptography_technology/rijndael/aessrc.zip
* URL for license: http://brgladman.org/oldsite/cryptography_technology/rijndael/
* License type: BSD style

License and Copyright available in documentation:

Copyright (c) 1998-2006, Brian Gladman, Worcester, UK. All rights reserved.
LICENSE TERMS
The free distribution and use of this software in both source and binary
form is allowed (with or without changes) provided that:
1. distributions of this source code include the above copyright
notice, this list of conditions and the following disclaimer;
2. distributions in binary form include the above copyright
notice, this list of conditions and the following disclaimer
in the documentation and/or other associated materials;
3. the copyright holder's name is not used to endorse products
built using this software without specific written permission.
ALTERNATIVELY, provided that this notice is retained in full, this product
may be distributed under the terms of the GNU General Public License (GPL),
in which case the provisions of the GPL apply INSTEAD OF those given above.
DISCLAIMER
This software is provided 'as is' with no explicit or implied warranties
in respect of its properties, including, but not limited to, correctness
and/or fitness for purpose.

== AES-GCM ==
Our AES-GCM implementation in software is derived from:
* Official name: SharedAES-GCM
* Version number: v1.0
* URL for source: https://github.com/mko-x/SharedAES-GCM
* URL for license: https://github.com/mko-x/SharedAES-GCM
* License type: Public domain

/******************************************************************************
* THIS SOURCE CODE IS HEREBY PLACED INTO THE PUBLIC DOMAIN FOR THE GOOD OF ALL
*
* This is a simple and straightforward implementation of AES-GCM authenticated
* encryption. The focus of this work was correctness & accuracy. It is written
* in straight 'C' without any particular focus upon optimization or speed. It
* should be endian (memory byte order) neutral since the few places that care
* are handled explicitly.
*
* This implementation of AES-GCM was created by Steven M. Gibson of GRC.com.
*
* It is intended for general purpose use, but was written in support of GRC's
* reference implementation of the SQRL (Secure Quick Reliable Login) client.
*
* See: http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf
* http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/proposedmodes/
* gcm/gcm-revised-spec.pdf
*
* NO COPYRIGHT IS CLAIMED IN THIS WORK, HOWEVER, NEITHER IS ANY WARRANTY MADE
* REGARDING ITS FITNESS FOR ANY PARTICULAR PURPOSE. USE IT AT YOUR OWN RISK.
*******************************************************************************/

== Big Number Library ==
* Official name: tropicssl multi-precision integer library
* Version number: tropicssl 0.10.1 with commits up to Friday January 18 2013
* URL for source: https://gitorious.org/tropicssl/tropicssl
* URL for license: https://gitorious.org/tropicssl/tropicssl/source/92bb3462dfbdb4568c92be19e8904129a17b1eed:library/bignum.c
* License type: BSD style

/*
* Multi-precision integer library
*
* Based on XySSL: Copyright (C) 2006-2008 Christophe Devine
*
* Copyright (C) 2009 Paul Bakker <polarssl_maintainer at polarssl dot org>
* Copyright (C) 2010 StackFoundry LLC <yann@stackfoundry.com>
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* * Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* * Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* * Neither the names of Tropic SSL,
* PolarSSL or XySSL nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
* FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
* OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
* TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
* PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
* LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
* NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

== ECDHE ==
* Official name: micro-ecc
* Version number: v1.1.
* URL for source: https://github.com/kmackay/micro-ecc
* URL for license: https://github.com/kmackay/micro-ecc/blob/master/LICENSE.txt
* License type: BSD 2-clause license

Copyright (c) 2014, Kenneth MacKay
All rights reserved.

Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Download link: https://github.com/kmackay/micro-ecc

== OpenSSL (SHA, SHA2, DES, RC2, RC4) ==
Some functions from the OpenSSL library are used for the encryption and hash functions SHA, SHA2, DES, RC2, RC4.

* Official name: OpenSSL
* Version: v3.3.2
* URL for source: http://www.openssl.org/source/
* URL for license: http://www.openssl.org/source/license.html
* License type: BSD style

LICENSE ISSUES
==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of
the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts. Actually both licenses are BSD-style
Open Source licenses. In case of any license issues related to OpenSSL
please contact openssl-core@openssl.org.

OpenSSL License
---------------

/* ====================================================================
* Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
*
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* openssl-core@openssl.org.
*
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
*
* 6. Redistributions of any form whatsoever must retain the following
* acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
*
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================
*
* This product includes cryptographic software written by Eric Young
* (eay@cryptsoft.com). This product includes software written by Tim
* Hudson (tjh@cryptsoft.com).
*
*/

Original SSLeay License
-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young (eay@cryptsoft.com).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson (tjh@cryptsoft.com).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young (eay@cryptsoft.com)"
* The word 'cryptographic' can be left out if the rouines from the library
* being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence.]
*/

== MD4 ==
* Official name: RSA Data Security, Inc. MD4 Message-Digest Algorithm
* Version: 1.5 2012/03/20
* URL for source: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/sys/
* URL for license: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/sys/md4.h

/*
* This file is derived from the RSA Data Security, Inc. MD4 Message-Digest
* Algorithm and has been modified by Jason R. Thorpe <thorpej@NetBSD.ORG>
* for portability and formatting.
*/

/*
* Copyright (C) 1990-2, RSA Data Security, Inc. All rights reserved.
*
* License to copy and use this software is granted provided that it
* is identified as the "RSA Data Security, Inc. MD4 Message-Digest
* Algorithm" in all material mentioning or referencing this software
* or this function.
*
* License is also granted to make and use derivative works provided
* that such works are identified as "derived from the RSA Data
* Security, Inc. MD4 Message-Digest Algorithm" in all material
* mentioning or referencing the derived work.
*
* RSA Data Security, Inc. makes no representations concerning either
* the merchantability of this software or the suitability of this
* software for any particular purpose. It is provided "as is"
* without express or implied warranty of any kind.
*
* These notices must be retained in any copies of any part of this
* documentation and/or software.
*/

== MD5 ==
* Official name: RSA Data Security, Inc. MD5 Message-Digest Algorithm
* Version: 1.5 2012/03/20
* URL for source: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/sys/
* URL for license: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/sys/md5.h

/*
* This file is derived from the RSA Data Security, Inc. MD5 Message-Digest
* Algorithm and has been modifed by Jason R. Thorpe <thorpej@NetBSD.ORG>
* for portability and formatting.
*/

/*
* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All
* rights reserved.
*
* License to copy and use this software is granted provided that it
* is identified as the "RSA Data Security, Inc. MD5 Message-Digest
* Algorithm" in all material mentioning or referencing this software
* or this function.
*
* License is also granted to make and use derivative works provided
* that such works are identified as "derived from the RSA Data
* Security, Inc. MD5 Message-Digest Algorithm" in all material
* mentioning or referencing the derived work.
*
* RSA Data Security, Inc. makes no representations concerning either
* the merchantability of this software or the suitability of this
* software for any particular purpose. It is provided "as is"
* without express or implied warranty of any kind.
*
* These notices must be retained in any copies of any part of this
* documentation and/or software.
*/

== CHAP-MS ==
* Official name: Microsoft MS-CHAP compatible implementation
* URL for source: http://ftp.netbsd.org/pub/NetBSD/NetBSD-release-6/src/dist/pppd/pppd/
* URL for license: http://ftp.netbsd.org/pub/NetBSD/NetBSD-release-6/src/dist/pppd/pppd/chap_ms.h
* License type: BSD style

/*
* chap_ms.c - Microsoft MS-CHAP compatible implementation.
*
* Copyright (c) 1995 Eric Rosenquist. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. The name(s) of the authors of this software must not be used to
* endorse or promote products derived from this software without
* prior written permission.
*
* THE AUTHORS OF THIS SOFTWARE DISCLAIM ALL WARRANTIES WITH REGARD TO
* THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
* AND FITNESS, IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY
* SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
* AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
* OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*/

/*
* Modifications by Lauri Pesonen / lpesonen@clinet.fi, april 1997
*
* Implemented LANManager type password response to MS-CHAP challenges.
* Now pppd provides both NT style and LANMan style blocks, and the
* prefered is set by option "ms-lanman". Default is to use NT.
* The hash text (StdText) was taken from Win95 RASAPI32.DLL.
*
* You should also use DOMAIN\\USERNAME as described in README.MSCHAP80
*/

/*
* Modifications by Frank Cusack, frank@google.com, March 2002.
*
* Implemented MS-CHAPv2 functionality, heavily based on sample
* implementation in RFC 2759. Implemented MPPE functionality,
* heavily based on sample implementation in RFC 3079.
*
* Copyright (c) 2002 Google, Inc. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. The name(s) of the authors of this software must not be used to
* endorse or promote products derived from this software without
* prior written permission.
*
* THE AUTHORS OF THIS SOFTWARE DISCLAIM ALL WARRANTIES WITH REGARD TO
* THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
* AND FITNESS, IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY
* SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
* AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
* OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
*/

== slcompress ==
* Official name: SL compression
* Version: v1.6
* URL for source: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/net/
* URL for license: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/net/slcompress.h
* License type: BSD style

/*
* Copyright (c) 1989, 1993
* The Regents of the University of California. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This product includes software developed by the University of
* California, Berkeley and its contributors.
* 4. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* @(#)slcompress.h 8.1 (Berkeley) 6/10/93
*/

/*
* Definitions for tcp compression routines.
*
* Van Jacobson (van@helios.ee.lbl.gov), Dec 31, 1989:
* - Initial distribution.
*/

== ZLIB ==
* Official name: zlib
* Version number: 1.3.1
* URL for source: http://www.zlib.net/
* URL for license: http://www.zlib.net/manual.html
* License and Copyright available in documentation:

Copyright (C) 1995-2002 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
The origin of this software must not be misrepresented ; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
This notice may not be removed or altered from any source distribution.

== CRC32 ==
* Official name: CRC32
* URL for source: http://www.opensource.apple.com/source/xnu/xnu-1456.1.26/bsd/libkern/crc32.c
* URL for license: http://www.opensource.apple.com/source/xnu/xnu-1456.1.26/bsd/libkern/crc32.c
* License and Copyright available in documentation:

COPYRIGHT (C) 1986 Gary S. Brown. You may use this program, or
code or tables extracted from it, as desired without restriction.

CRC32 code derived from work by Gary S. Brown.

== Regex ==
* Official name: regular-expression library
* Version: 1.5
* URL for source: ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/lib/libc/regex
* URL for license: ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/lib/libc/regex/COPYRIGHT
* License type: BSD Style

$NetBSD: COPYRIGHT,v 1.5 2003/08/07 16:43:19 agc Exp $

Copyright 1992, 1993, 1994 Henry Spencer. All rights reserved.
This software is not subject to any license of the American Telephone
and Telegraph Company or of the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on
any computer system, and to alter it and redistribute it, subject
to the following restrictions:

1. The author is not responsible for the consequences of use of this
software, no matter how awful, even if they arise from flaws in it.

2. The origin of this software must not be misrepresented, either by
explicit claim or by omission. Since few users ever read sources,
credits must appear in the documentation.

3. Altered versions must be plainly marked as such, and must not be
misrepresented as being the original software. Since few users
ever read sources, credits must appear in the documentation.

4. This notice may not be removed or altered.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
/*-
* Copyright (c) 1994
* The Regents of the University of California. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* @(#)COPYRIGHT 8.1 (Berkeley) 3/16/94
*/

== Opus audio codec ==
* Official name: Opus audio codec
* Version number: 1.1.1-beta 15 October, 2014
* URL for source: http://downloads.xiph.org/releases/opus/opus-1.1.1-beta.tar.gz
* URL for license: https://www.opus-codec.org/license/
* License type: BSD style

License and Copyright available in documentation:

* Copyright 2001-2011 Xiph.Org, Skype Limited, Octasic,
* Jean-Marc Valin, Timothy B. Terriberry,
* CSIRO, Gregory Maxwell, Mark Borgerding,
* Erik de Castro Lopo
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* - Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* - Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* - Neither the name of Internet Society, IETF or IETF Trust, nor the
* names of specific contributors, may be used to endorse or promote
* products derived from this software without specific prior written
* permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
* OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
* PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
* LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
* NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
* Opus is subject to the royalty-free patent licenses which are
* specified at:
*
* Xiph.Org Foundation:
* https://datatracker.ietf.org/ipr/1524/
*
* Microsoft Corporation:
* https://datatracker.ietf.org/ipr/1914/
*
* Broadcom Corporation:
* https://datatracker.ietf.org/ipr/1526/

== Libfdt ==
* Official name: Flat Device Tree manipulation
* Version number: 1.4.1
* URL for source: https://git.kernel.org/cgit/utils/dtc/dtc.git
* URL for license: https://git.kernel.org/cgit/utils/dtc/dtc.git/tree/libfdt/libfdt.h
* License type: BSD style

/*
* libfdt - Flat Device Tree manipulation
* Copyright (C) 2006 David Gibson, IBM Corporation.
*
* libfdt is dual licensed: you can use it either under the terms of
* the GPL, or the BSD license, at your option.
*
* a) This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public
* License along with this library; if not, write to the Free
* Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
* MA 02110-1301 USA
*
* Alternatively,
*
* b) Redistribution and use in source and binary forms, with or
* without modification, are permitted provided that the following
* conditions are met:
*
* 1. Redistributions of source code must retain the above
* copyright notice, this list of conditions and the following
* disclaimer.
* 2. Redistributions in binary form must reproduce the above
* copyright notice, this list of conditions and the following
* disclaimer in the documentation and/or other materials
* provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
* CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
* INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
* MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
* EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

== PLCrashReporter ==
* Official name: In-process CrashReporter framework for iOS and Mac OS X
* Version number: v1.11.0
* URL for source: https://www.plcrashreporter.org/static/downloads/PLCrashReporter-1.11.0.zip
* URL for license: https://www.plcrashreporter.org/, https://opensource.org/licenses/mit-license.php, http://www.apache.org/licenses/LICENSE-2.0.html
* License type: MIT style, components have Apache license

License and Copyright available in documentation:

Except as noted below, PLCrashReporter is provided under the
following license:

Copyright (c) Microsoft Corporation.
Copyright (c) 2008 - 2014 Plausible Labs Cooperative, Inc.
All rights reserved.

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following
conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

Additional contributions have been made under the same license terms
as above, with copyright held by their respective authors:

Damian Morris <damian@moso.com.au>
Copyright (c) 2010 MOSO Corporation, Pty Ltd.
All rights reserved.

HockeyApp/Bitstadium
Copyright (c) 2012 HockeyApp, Bit Stadium GmbH.
All rights reserved.

The protobuf-c library, as well as the PLCrashLogWriterEncoding.c
file are licensed as follows:

Copyright 2008, Dave Benson.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with
the License. You may obtain a copy of the License
at http://www.apache.org/licenses/LICENSE-2.0 Unless
required by applicable law or agreed to in writing,
software distributed under the License is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.

== Unicode Consortium (Timezone mapping Microsoft → tz database) ==
* Official name: Mapping Zone → Tzid (also windowsZones.xml)
* Version number: 2017a, 7e00600
* URL for source: http://www.unicode.org/cldr/charts/29/supplemental/zone_tzid.html
* URL for license: http://www.unicode.org/copyright.html
* License and Copyright available in documentation:

UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE

Unicode Data Files include all data files under the directories
http://www.unicode.org/Public/, http://www.unicode.org/reports/,
http://www.unicode.org/cldr/data/, http://source.icu-project.org/repos/icu/, and
http://www.unicode.org/utility/trac/browser/.

Unicode Data Files do not include PDF online code charts under the
directory http://www.unicode.org/Public/.

Software includes any source code published in the Unicode Standard
or under the directories
http://www.unicode.org/Public/, http://www.unicode.org/reports/,
http://www.unicode.org/cldr/data/, http://source.icu-project.org/repos/icu/, and
http://www.unicode.org/utility/trac/browser/.

NOTICE TO USER: Carefully read the following legal agreement.
BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S
DATA FILES ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"),
YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE
TERMS AND CONDITIONS OF THIS AGREEMENT.
IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE
THE DATA FILES OR SOFTWARE.

COPYRIGHT AND PERMISSION NOTICE

Copyright © 1991-2017 Unicode, Inc. All rights reserved.
Distributed under the Terms of Use in http://www.unicode.org/copyright.html.

Permission is hereby granted, free of charge, to any person obtaining
a copy of the Unicode data files and any associated documentation
(the "Data Files") or Unicode software and any associated documentation
(the "Software") to deal in the Data Files or Software
without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, and/or sell copies of
the Data Files or Software, and to permit persons to whom the Data Files
or Software are furnished to do so, provided that either
(a) this copyright and permission notice appear with all copies of the Data Files or Software, or
(b) this copyright and permission notice appear in associated Documentation.

THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS.
IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THE DATA FILES OR SOFTWARE.

Except as contained in this notice, the name of a copyright holder
shall not be used in advertising or otherwise to promote the sale,
use or other dealings in these Data Files or Software without prior
written authorization of the copyright holder.

== The WebRTC project (Acoustic echo cancellation) ==
* Official name: The Android Open Source Project: The WebRTC project
* Version number: 5.0_r6
* URL for source: https://webrtc.googlesource.com/src/+/cd277b84dad534145445d3586145ff25aa5637ee
* URL for license: https://webrtc.googlesource.com/src/+/cd277b84dad534145445d3586145ff25aa5637ee
* License type: BSD Style
* License and Copyright available in documentation:

Copyright (c) 2011, The WebRTC project authors. All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.

* Neither the name of Google nor the names of its contributors may
be used to endorse or promote products derived from this software
without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

* Included patents text:

Additional IP Rights Grant (Patents)

"This implementation" means the copyrightable works distributed by
Google as part of the WebRTC code package.

Google hereby grants to you a perpetual, worldwide, non-exclusive,
no-charge, irrevocable (except as stated in this section) patent
license to make, have made, use, offer to sell, sell, import,
transfer, and otherwise run, modify and propagate the contents of this
implementation of the WebRTC code package, where such license applies
only to those patent claims, both currently owned by Google and
acquired in the future, licensable by Google that are necessarily
infringed by this implementation of the WebRTC code package. This
grant does not include claims that would be infringed only as a
consequence of further modification of this implementation. If you or
your agent or exclusive licensee institute or order or agree to the
institution of patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that this
implementation of the WebRTC code package or any code incorporated
within this implementation of the WebRTC code package constitutes
direct or contributory patent infringement, or inducement of patent
infringement, then any patent rights granted to you under this License
for this implementation of the WebRTC code package shall terminate as
of the date such litigation is filed.

== dTree ==
* Official name: dTree
* Version number: 2.05
* URL for source: https://destroydrop.com/javascripts/tree/dtree.zip
* URL for license: https://destroydrop.com/javascripts/tree/
* License type: non-standard (see below)
* License and Copyright available in documentation:

/*--------------------------------------------------|
| dTree 2.05 | www.destroydrop.com/javascript/tree/ |
|-------------------------------------------------- |
| Copyright (c) 2002-2003 Geir Landrö |
| |
| This script can be used freely as long as all |
| copyright messages are intact. |
| |
| Updated: 17.04.2003 |
|--------------------------------------------------*/

== STLport ==
* Official name: STLport
* Version number: 5.2.1
* URL for source: https://sourceforge.net/projects/stlport/files/STLport/STLport-5.2.1/STLport-5.2.1.tar.bz2
* URL for license: https://sourceforge.net/projects/stlport/files/STLport/STLport-5.2.1/STLport-5.2.1.tar.bz2
* License type: non-standard (see below)
* License and Copyright available in documentation:

This software is being distributed under the following terms:
*
*
* Copyright (c) 1994
* Hewlett-Packard Company
*
* Copyright (c) 1996-1999
* Silicon Graphics Computer Systems, Inc.
*
* Copyright (c) 1997
* Moscow Center for SPARC Technology
*
* Copyright (c) 1999-2003
* Boris Fomitchev
*
* This material is provided "as is", with absolutely no warranty expressed
* or implied. Any use is at your own risk.
*
* Permission to use or copy this software for any purpose is hereby granted
* without fee, provided the above notices are retained on all copies.
* Permission to modify the code and to distribute modified code is granted,
* provided the above notices are retained, and a notice that the code was
* modified is included with the above copyright notice.
*
**********************************************************************

== VPX video codec ==
* Official name: webmproject
* Version number: v1.10.0
* URL for source: https://www.webmproject.org/code/
* URL for license: https://www.webmproject.org/license/
* License type: BSD license

== YUV ==
* Official name: libyuv
* Version number: 1787
* URL for source: https://chromium.googlesource.com/libyuv/libyuv/
* URL for license: https://chromium.googlesource.com/libyuv/libyuv/+/HEAD/LICENSE
* License type: BSD license

== Chromium ==
* Official name: Chromium Embedded Framework
* Version number: 127.0.6533.100
* URL for source: https://bitbucket.org/chromiumembedded/cef/src
* URL for license: https://bitbucket.org/chromiumembedded/cef/src/master/LICENSE.txt
* License type: BSD license

== fromXML ==
* Official name: fromXML - Pure JavaScript XML Parser
* Version number: 0.1.11
* URL for source: https://github.com/kawanet/from-xml
* URL for license: https://github.com/kawanet/from-xml/blob/master/LICENSE
* License type: MIT License (MIT)
* Copyright: 2016-2023 Yusuke Kawasaki
* Used in Apps: TechAssist, myPhoneKeys

== CodeMirror ==
* Official name: CodeMirror
* Version number: 0.16.0
* URL for source: https://github.com/codemirror/dev
* URL for license: https://github.com/codemirror/dev/blob/main/LICENSE
* License type: MIT License (MIT)
* Copyright: 2018 by Marijn Haverbeke <marijn@haverbeke.berlin>, Adrian Heine <mail@adrianheine.de>, and others
* Used in Apps: TechAssist

== jQuery ==
* Official name: jQuery - New Wave JavaScript
* Version number: 3.6.1
* URL for source: https://github.com/jquery/jquery
* URL for license: https://github.com/jquery/jquery/blob/main/LICENSE.txt
* License type: MIT License (MIT)
* Copyright: OpenJS Foundation and other contributors, https://openjsf.org/
* Used in Apps: TechAssist

== jQuery Datatables ==
* Official name: DataTables
* Version number: 1.13.6
* URL for source: https://datatables.net/download/
* URL for license: https://datatables.net/license/
* License type: MIT License (MIT)
* Copyright: 2008-2024, SpryMedia Ltd.
* Used in Apps: TechAssist

== Bootstrap 5 ==
* Official name: Bootstrap 5
* Version number: 5.2.2
* URL for source: https://github.com/twbs/bootstrap
* URL for license: https://github.com/twbs/bootstrap/blob/main/LICENSE
* License type: MIT License (MIT)
* Copyright: 2011-2024 The Bootstrap Authors
* Used in Apps: TechAssist

== QR Code svg generator ==
* Official name: QR Code svg generator
* Version number: Download as of 2024-12-19
* URL for source: https://github.com/datalog/qrcode-svg
* URL for license: https://github.com/datalog/qrcode-svg/blob/master/LICENSE
* License type: MIT License (MIT)
* Used in Apps: myApps

Reference16r1:Concept innovaphone App Platform Container

2025-04-15T09:11:33Z

Afi: /* Mounting */ new build number format

The innovaphone App Platform Docker container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

==Image Information==

This chapter provides details about the Docker image used for the innovaphone App Platform.

===Repository Details===

;Repository Host : docker.innovaphone.com
;Image Name : cloud/kubernetes/innovaphone-platform-instance

docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

===Tagging and Versioning===
The image is usually tagged with the build number according to innovaphone software releases:

;Latest Tag : Use the latest tag for pulling the most recent service release.

;Release Build Number : For production or version-specific deployments, use a specific build number as the tag (e.g., 130006).

Example:
docker pull docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

===Supported Architecture===
This Docker image supports the <code>linux/amd64</code> architecture.

===Image Reference===
An example of a full image reference using a specific release build number would be:
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

==Ports==
This chapter outlines the various ports exposed by the Docker container. The webserver ports are available immediately upon container startup, after start of the AP Manager and the Webserver, while the additional application ports become active after the app installation. In most cases, a one-to-one mapping is used, meaning the container port is mapped directly to the same host port unless otherwise specified.

===Webserver Ports===
;HTTP:
Container Port: 8080
Description: Used for accessing the built-in webserver immediately upon container startup.

;HTTPS:
Container Port: 8082
Description: Used for accessing the built-in webserver immediately upon container startup.

=== Additional Application Ports===
Following additional container ports are avilable depending on installed and configured applications:
;H323/TLS : 1300
;SIP : 5060
;SIPS : 5061
;LDAPS : 1636
;SMTP : 8025
;SMTPS : 8587
'''Additional hint for Portmapping'''<syntaxhighlight lang="yaml" line="1">
docker run -d \
--name=innovaphone \
--restart unless-stopped \
-p 9090:8080 \ #Container Host Port (external) 9090:8080 Container Port
-p 9091:8082 \
-p 5060:5060 \
-p 5061:5061 \
-p 1300:1300 \
-p 1636:1636 \
-p 8025:8025 \
-p 8587:8587 \
-v /path/of/data/innovaphone:/mnt/data \ #in this path you will find Apps, DBs & Logs
#this path musst be used for backups!!
-e WEBSERVERPORTHTTP=8080 \
-e WEBSERVERPORTHTTPS=8082 \
-e LOG_FLAGS=7 \
-e LOG_SIZE=1048576 \
-e DNSIPV4=8.8.8.8 \
-e LIMIT_RAM=512 \ #Ram limit in MB
-e LIMIT_DISK=10 \ #disk size in GB
-e TZ=Europe/Berlin \
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

</syntaxhighlight>

==Environment Variables (ENVs)==
This chapter outlines the key environment variables used to configure the behavior of the innovaphone App Platform Docker container. These variables allow you to customize logging, port settings, resource limits, and more during startup and runtime.

;LOG_FLAGS : Defines the integer representation for the trace flags of the AP Manager, according flags activated under the AP Manager / Diagnostics. See browser console message on Save button press (e.g. "logFlags":1 , if the "App" flag is activated).
LOG_FLAGS=7
;LOG_SIZE : Specifies the maximum size in bytes for logs before rotation or management actions occur. Default: 5242880.
LOG_SIZE=1048576
;WEBSERVERPORTHTTP : Sets the in-container HTTP port for the webserver. Default: 8080.
WEBSERVERPORTHTTP=8080
;WEBSERVERPORTHTTPS : Sets the in-container HTTPS port for the webserver. Default: 8082.
WEBSERVERPORTHTTPS=8443
;DNSIPV4 : Specifies the in-container IPv4 address for DNS resolution. Overrides the deafult container runtime DNS server.
DNSIPV4=8.8.8.8
;LIMIT_RAM : Sets the RAM limit for the container, in MB, controlling how much memory it may consume. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_RAM=512
;LIMIT_DISK : Defines the disk space limit in GB for the container to manage storage consumption. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_DISK=10
==Volumes and Mounts==
This container uses a dedicated internal mount path for the persistent data management across container restarts and updates.

===Internal Data Volume===
;Mount Path : <code>/mnt/data</code>
;Contents:
*Apps: Installed application binaries.
*Databases: PostgreSQL files.
*Logging: Log files for system and application events.

===Mounting===
To ensure that your data is preserved, map a host directory or Docker named volume to the container's /mnt/data path when running the container.
For example:
docker run -d -v /path/on/host:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

This setup guarantees that your apps, associated data, databases, and logs persist independently of the container lifecycle.

==Entrypoint==
The container uses a fixed entrypoint:
ENTRYPOINT ["/entrypoint.sh"]

This script prepares the container and starts the AP Manager executable.

==Logging and Monitoring==
The log of the entrypoint.sh and of the AP manager is avilable as conatiner output. The installed applications store the ir log files under <code>/mnt/data/var/log/apps/</code>.

==Usage Example==
sudo docker run -d --restart unless-stopped --name innovaphoneAP -p 9090:8080 -p 9091:8082 -e WEBSERVERPORTHTTP=8080 -e WEBSERVERPORTHTTPS=8082 -v $(pwd)/myapps/:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

This command runs the container in detached mode with automatic restart. It names the container innovaphoneAP, maps host ports 9090 and 9091 to the container's HTTP and HTTPS ports, sets the webserver port environment variables, mounts a host directory to /mnt/data, and starts the AP Manager. After container start up the AP manager web UI is accessible via <code>http://localhost:9090</code> or <code>https://localhost:9091</code>.

Reference16r1:Concept innovaphone App Platform Container

2025-04-15T09:10:59Z

Afi: /* Image Reference */ new build number format

The innovaphone App Platform Docker container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

==Image Information==

This chapter provides details about the Docker image used for the innovaphone App Platform.

===Repository Details===

;Repository Host : docker.innovaphone.com
;Image Name : cloud/kubernetes/innovaphone-platform-instance

docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

===Tagging and Versioning===
The image is usually tagged with the build number according to innovaphone software releases:

;Latest Tag : Use the latest tag for pulling the most recent service release.

;Release Build Number : For production or version-specific deployments, use a specific build number as the tag (e.g., 130006).

Example:
docker pull docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

===Supported Architecture===
This Docker image supports the <code>linux/amd64</code> architecture.

===Image Reference===
An example of a full image reference using a specific release build number would be:
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

==Ports==
This chapter outlines the various ports exposed by the Docker container. The webserver ports are available immediately upon container startup, after start of the AP Manager and the Webserver, while the additional application ports become active after the app installation. In most cases, a one-to-one mapping is used, meaning the container port is mapped directly to the same host port unless otherwise specified.

===Webserver Ports===
;HTTP:
Container Port: 8080
Description: Used for accessing the built-in webserver immediately upon container startup.

;HTTPS:
Container Port: 8082
Description: Used for accessing the built-in webserver immediately upon container startup.

=== Additional Application Ports===
Following additional container ports are avilable depending on installed and configured applications:
;H323/TLS : 1300
;SIP : 5060
;SIPS : 5061
;LDAPS : 1636
;SMTP : 8025
;SMTPS : 8587
'''Additional hint for Portmapping'''<syntaxhighlight lang="yaml" line="1">
docker run -d \
--name=innovaphone \
--restart unless-stopped \
-p 9090:8080 \ #Container Host Port (external) 9090:8080 Container Port
-p 9091:8082 \
-p 5060:5060 \
-p 5061:5061 \
-p 1300:1300 \
-p 1636:1636 \
-p 8025:8025 \
-p 8587:8587 \
-v /path/of/data/innovaphone:/mnt/data \ #in this path you will find Apps, DBs & Logs
#this path musst be used for backups!!
-e WEBSERVERPORTHTTP=8080 \
-e WEBSERVERPORTHTTPS=8082 \
-e LOG_FLAGS=7 \
-e LOG_SIZE=1048576 \
-e DNSIPV4=8.8.8.8 \
-e LIMIT_RAM=512 \ #Ram limit in MB
-e LIMIT_DISK=10 \ #disk size in GB
-e TZ=Europe/Berlin \
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

</syntaxhighlight>

==Environment Variables (ENVs)==
This chapter outlines the key environment variables used to configure the behavior of the innovaphone App Platform Docker container. These variables allow you to customize logging, port settings, resource limits, and more during startup and runtime.

;LOG_FLAGS : Defines the integer representation for the trace flags of the AP Manager, according flags activated under the AP Manager / Diagnostics. See browser console message on Save button press (e.g. "logFlags":1 , if the "App" flag is activated).
LOG_FLAGS=7
;LOG_SIZE : Specifies the maximum size in bytes for logs before rotation or management actions occur. Default: 5242880.
LOG_SIZE=1048576
;WEBSERVERPORTHTTP : Sets the in-container HTTP port for the webserver. Default: 8080.
WEBSERVERPORTHTTP=8080
;WEBSERVERPORTHTTPS : Sets the in-container HTTPS port for the webserver. Default: 8082.
WEBSERVERPORTHTTPS=8443
;DNSIPV4 : Specifies the in-container IPv4 address for DNS resolution. Overrides the deafult container runtime DNS server.
DNSIPV4=8.8.8.8
;LIMIT_RAM : Sets the RAM limit for the container, in MB, controlling how much memory it may consume. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_RAM=512
;LIMIT_DISK : Defines the disk space limit in GB for the container to manage storage consumption. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_DISK=10
==Volumes and Mounts==
This container uses a dedicated internal mount path for the persistent data management across container restarts and updates.

===Internal Data Volume===
;Mount Path : <code>/mnt/data</code>
;Contents:
*Apps: Installed application binaries.
*Databases: PostgreSQL files.
*Logging: Log files for system and application events.

===Mounting===
To ensure that your data is preserved, map a host directory or Docker named volume to the container's /mnt/data path when running the container.
For example:
docker run -d -v /path/on/host:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:1510987

This setup guarantees that your apps, associated data, databases, and logs persist independently of the container lifecycle.

==Entrypoint==
The container uses a fixed entrypoint:
ENTRYPOINT ["/entrypoint.sh"]

This script prepares the container and starts the AP Manager executable.

==Logging and Monitoring==
The log of the entrypoint.sh and of the AP manager is avilable as conatiner output. The installed applications store the ir log files under <code>/mnt/data/var/log/apps/</code>.

==Usage Example==
sudo docker run -d --restart unless-stopped --name innovaphoneAP -p 9090:8080 -p 9091:8082 -e WEBSERVERPORTHTTP=8080 -e WEBSERVERPORTHTTPS=8082 -v $(pwd)/myapps/:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

This command runs the container in detached mode with automatic restart. It names the container innovaphoneAP, maps host ports 9090 and 9091 to the container's HTTP and HTTPS ports, sets the webserver port environment variables, mounts a host directory to /mnt/data, and starts the AP Manager. After container start up the AP manager web UI is accessible via <code>http://localhost:9090</code> or <code>https://localhost:9091</code>.

Reference16r1:Concept innovaphone App Platform Container

2025-04-15T09:10:40Z

Afi: /* Tagging and Versioning */ new build number format

The innovaphone App Platform Docker container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

==Image Information==

This chapter provides details about the Docker image used for the innovaphone App Platform.

===Repository Details===

;Repository Host : docker.innovaphone.com
;Image Name : cloud/kubernetes/innovaphone-platform-instance

docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

===Tagging and Versioning===
The image is usually tagged with the build number according to innovaphone software releases:

;Latest Tag : Use the latest tag for pulling the most recent service release.

;Release Build Number : For production or version-specific deployments, use a specific build number as the tag (e.g., 130006).

Example:
docker pull docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:130006

===Supported Architecture===
This Docker image supports the <code>linux/amd64</code> architecture.

===Image Reference===
An example of a full image reference using a specific release build number would be:
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:1510987

==Ports==
This chapter outlines the various ports exposed by the Docker container. The webserver ports are available immediately upon container startup, after start of the AP Manager and the Webserver, while the additional application ports become active after the app installation. In most cases, a one-to-one mapping is used, meaning the container port is mapped directly to the same host port unless otherwise specified.

===Webserver Ports===
;HTTP:
Container Port: 8080
Description: Used for accessing the built-in webserver immediately upon container startup.

;HTTPS:
Container Port: 8082
Description: Used for accessing the built-in webserver immediately upon container startup.

=== Additional Application Ports===
Following additional container ports are avilable depending on installed and configured applications:
;H323/TLS : 1300
;SIP : 5060
;SIPS : 5061
;LDAPS : 1636
;SMTP : 8025
;SMTPS : 8587
'''Additional hint for Portmapping'''<syntaxhighlight lang="yaml" line="1">
docker run -d \
--name=innovaphone \
--restart unless-stopped \
-p 9090:8080 \ #Container Host Port (external) 9090:8080 Container Port
-p 9091:8082 \
-p 5060:5060 \
-p 5061:5061 \
-p 1300:1300 \
-p 1636:1636 \
-p 8025:8025 \
-p 8587:8587 \
-v /path/of/data/innovaphone:/mnt/data \ #in this path you will find Apps, DBs & Logs
#this path musst be used for backups!!
-e WEBSERVERPORTHTTP=8080 \
-e WEBSERVERPORTHTTPS=8082 \
-e LOG_FLAGS=7 \
-e LOG_SIZE=1048576 \
-e DNSIPV4=8.8.8.8 \
-e LIMIT_RAM=512 \ #Ram limit in MB
-e LIMIT_DISK=10 \ #disk size in GB
-e TZ=Europe/Berlin \
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

</syntaxhighlight>

==Environment Variables (ENVs)==
This chapter outlines the key environment variables used to configure the behavior of the innovaphone App Platform Docker container. These variables allow you to customize logging, port settings, resource limits, and more during startup and runtime.

;LOG_FLAGS : Defines the integer representation for the trace flags of the AP Manager, according flags activated under the AP Manager / Diagnostics. See browser console message on Save button press (e.g. "logFlags":1 , if the "App" flag is activated).
LOG_FLAGS=7
;LOG_SIZE : Specifies the maximum size in bytes for logs before rotation or management actions occur. Default: 5242880.
LOG_SIZE=1048576
;WEBSERVERPORTHTTP : Sets the in-container HTTP port for the webserver. Default: 8080.
WEBSERVERPORTHTTP=8080
;WEBSERVERPORTHTTPS : Sets the in-container HTTPS port for the webserver. Default: 8082.
WEBSERVERPORTHTTPS=8443
;DNSIPV4 : Specifies the in-container IPv4 address for DNS resolution. Overrides the deafult container runtime DNS server.
DNSIPV4=8.8.8.8
;LIMIT_RAM : Sets the RAM limit for the container, in MB, controlling how much memory it may consume. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_RAM=512
;LIMIT_DISK : Defines the disk space limit in GB for the container to manage storage consumption. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_DISK=10
==Volumes and Mounts==
This container uses a dedicated internal mount path for the persistent data management across container restarts and updates.

===Internal Data Volume===
;Mount Path : <code>/mnt/data</code>
;Contents:
*Apps: Installed application binaries.
*Databases: PostgreSQL files.
*Logging: Log files for system and application events.

===Mounting===
To ensure that your data is preserved, map a host directory or Docker named volume to the container's /mnt/data path when running the container.
For example:
docker run -d -v /path/on/host:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:1510987

This setup guarantees that your apps, associated data, databases, and logs persist independently of the container lifecycle.

==Entrypoint==
The container uses a fixed entrypoint:
ENTRYPOINT ["/entrypoint.sh"]

This script prepares the container and starts the AP Manager executable.

==Logging and Monitoring==
The log of the entrypoint.sh and of the AP manager is avilable as conatiner output. The installed applications store the ir log files under <code>/mnt/data/var/log/apps/</code>.

==Usage Example==
sudo docker run -d --restart unless-stopped --name innovaphoneAP -p 9090:8080 -p 9091:8082 -e WEBSERVERPORTHTTP=8080 -e WEBSERVERPORTHTTPS=8082 -v $(pwd)/myapps/:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

This command runs the container in detached mode with automatic restart. It names the container innovaphoneAP, maps host ports 9090 and 9091 to the container's HTTP and HTTPS ports, sets the webserver port environment variables, mounts a host directory to /mnt/data, and starts the AP Manager. After container start up the AP manager web UI is accessible via <code>http://localhost:9090</code> or <code>https://localhost:9091</code>.

Reference16r1:Concept innovaphone App Platform Container

2025-02-14T16:52:05Z

Afi: Created page with "The innovaphone App Platform Docker container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX. ==Image Information== This chapter provides details about the Docker image used for the innovaphone App Platform. ===Repository Details=== ;Repository Host : docker.innovaphone.com ;Image Name : cloud/kubernetes/innovaphone-platfor..."

The innovaphone App Platform Docker container provides a myApps App Platform instance that includes the AP Manager, Webserver and PostgreSQL. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

==Image Information==

This chapter provides details about the Docker image used for the innovaphone App Platform.

===Repository Details===

;Repository Host : docker.innovaphone.com
;Image Name : cloud/kubernetes/innovaphone-platform-instance

docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

===Tagging and Versioning===
The image is usually tagged with the build number according to innovaphone software releases:

;Latest Tag : Use the latest tag for pulling the most recent service release.

;Release Build Number : For production or version-specific deployments, use a specific build number as the tag (e.g., 1510987).

Example:
docker pull docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:1510987

===Supported Architecture===
This Docker image supports the <code>linux/amd64</code> architecture.

===Image Reference===
An example of a full image reference using a specific release build number would be:
docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:1510987

==Ports==
This chapter outlines the various ports exposed by the Docker container. The webserver ports are available immediately upon container startup, after start of the AP Manager and the Webserver, while the additional application ports become active after the app installation. In most cases, a one-to-one mapping is used, meaning the container port is mapped directly to the same host port unless otherwise specified.

===Webserver Ports===
;HTTP:
Container Port: 8080
Description: Used for accessing the built-in webserver immediately upon container startup.

;HTTPS:
Container Port: 8082
Description: Used for accessing the built-in webserver immediately upon container startup.

=== Additional Application Ports===
Following additional container ports are avilable depending on installed and configured applications:
;H323/TLS : 1300
;SIP : 5060
;SIPS : 5061
;LDAPS : 1636
;SMTP : 8025
;SMTPS : 8587

==Environment Variables (ENVs)==
This chapter outlines the key environment variables used to configure the behavior of the innovaphone App Platform Docker container. These variables allow you to customize logging, port settings, resource limits, and more during startup and runtime.

;LOG_FLAGS : Defines the integer representation for the trace flags of the AP Manager, according flags activated under the AP Manager / Diagnostics. See browser console message on Save button press (e.g. "logFlags":1 , if the "App" flag is activated).
LOG_FLAGS=7
;LOG_SIZE : Specifies the maximum size in bytes for logs before rotation or management actions occur. Default: 5242880.
LOG_SIZE=1048576
;WEBSERVERPORTHTTP : Sets the in-container HTTP port for the webserver. Default: 8080.
WEBSERVERPORTHTTP=8080
;WEBSERVERPORTHTTPS : Sets the in-container HTTPS port for the webserver. Default: 8082.
WEBSERVERPORTHTTPS=8443
;DNSIPV4 : Specifies the in-container IPv4 address for DNS resolution. Overrides the deafult container runtime DNS server.
DNSIPV4=8.8.8.8
;LIMIT_RAM : Sets the RAM limit for the container, in MB, controlling how much memory it may consume. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_RAM=512
;LIMIT_DISK : Defines the disk space limit in GB for the container to manage storage consumption. Used by AP Manager to stop the app instances on overconsumption.
LIMIT_DISK=10
==Volumes and Mounts==
This container uses a dedicated internal mount path for the persistent data management across container restarts and updates.

===Internal Data Volume===
;Mount Path : <code>/mnt/data</code>
;Contents:
*Apps: Installed application binaries.
*Databases: PostgreSQL files.
*Logging: Log files for system and application events.

===Mounting===
To ensure that your data is preserved, map a host directory or Docker named volume to the container's /mnt/data path when running the container.
For example:
docker run -d -v /path/on/host:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:1510987

This setup guarantees that your apps, associated data, databases, and logs persist independently of the container lifecycle.

==Entrypoint==
The container uses a fixed entrypoint:
ENTRYPOINT ["/entrypoint.sh"]

This script prepares the container and starts the AP Manager executable.

==Logging and Monitoring==
The log of the entrypoint.sh and of the AP manager is avilable as conatiner output. The installed applications store the ir log files under <code>/mnt/data/var/log/apps/</code>.

==Usage Example==
sudo docker run -d --restart unless-stopped --name innovaphoneAP -p 9090:8080 -p 9091:8082 -e WEBSERVERPORTHTTP=8080 -e WEBSERVERPORTHTTPS=8082 -v $(pwd)/myapps/:/mnt/data docker.innovaphone.com/cloud/kubernetes/innovaphone-platform-instance:latest

This command runs the container in detached mode with automatic restart. It names the container innovaphoneAP, maps host ports 9090 and 9091 to the container's HTTP and HTTPS ports, sets the webserver port environment variables, mounts a host directory to /mnt/data, and starts the AP Manager. After container start up the AP manager web UI is accessible via <code>http://localhost:9090</code> or <code>https://localhost:9091</code>.

Main Page

2024-11-13T14:22:37Z

Afi:

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">
== Remote Support ==
innovaphone only carries out scheduled remote maintenance via our ticket system by prior consultation. 
Please do not accept AnyDesk requests without prior appointment via ticket.

Please ensure that you download the [https://anydesk.com/en/downloads/windows latest AnyDesk version].

Please note: We cannot accept any liability for the external content of AnyDesk. AnyDesk is responsible for the content of its own software.
We are not liable for any damages resulting from the use of a non-updated or non-conforming version of AnyDesk.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have Google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales@innovaphone.com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] ([[User talk:Afi|talk]]) 15:22, 13 November 2024 (CET)
[[Support:Firmware V14r2 product/14r2/firmware 1420399 (sr4) available | Version 14r2 Service Release 4]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] ([[User talk:Afi|talk]]) 15:22, 13 November 2024 (CET)
[[Support:Firmware V14r1 product/14r1/firmware 1410578 (sr9) available | Version 14r1 Service Release 9]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] ([[User talk:Afi|talk]]) 15:22, 13 November 2024 (CET)
[[Support:Firmware V13r3 product/13r3/firmware 137999 (sr21) available | Version 13r3 Service Release 21]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] ([[User talk:Afi|talk]]) 15:22, 13 November 2024 (CET)
[[Support:Firmware V12r2 product/12r2/firmware 125885 (sr71) available | Version 12r2 Service Release 71]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Cam|Cam]] 16:22, 18 September 2023 (CEST)
[[App Calculator beta1 available]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Sga|Sga]] ([[User talk:Sga|talk]]) 17:43, 15 September 2023 (CEST)
[[Support:Wireless Handset Firmware IP73 1011 (5.0.1) released | Wireless Handset Firmware IP73 1011 (5.0.1)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Gal|Gal]] ([[User talk:Gal|talk]]) 13:39, 31 July 2023 (CEST)
[[Support:Wireless Handset Firmware IP64 10314 (3.0.13)/IP65 10119 (3.0.13) released | Wireless Handset Firmware IP64 10314 (3.0.13)/IP65 10119 (3.0.13)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Cam|Cam]] 12:03, 31 July 2023 (CEST)
[[App Working final available]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] 15:38, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040621_(6.2.7)_released | Wireless Handset Firmware IP62 3040621 (6.2.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM_Software_3130113_%284.1.8%29_released | WinPDM Software 3130113 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">

== New Articles ==

{{Special:Newestpages/all/20}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">
== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
</div>

Reference15r1:Concept innovaphone Cloud Instance

2024-09-27T10:26:25Z

Afi: Undo revision 73606 by Afi (talk)

= Applies To =

* innovaphone Cloud Instance on the <code>*.innovaphone.cloud</code> Kubernetes cluster

== Requirements ==

* Browser (Chrome, Firefox, ...)
* Access to the [https://www.innovaphone.com/en/services/partner-login.html my.innovaphone Partner Portal]

== Default credentials ==

'''During INSTALL, the default passwords are replaced with the global Admin PW!'''
* manager App (web login) '''pwd'''
* App IP (PBX advanced web UI) '''admin:pwd'''

== Concept ==
The innovaphone Cloud Instance is an [[Reference14r2:Concept App Platform |innovaphone App Platform]] running inside a container, orchestrated by a Kubernetes cluster hosted under the <code>*.innovaphone.cloud</code> domain.

The instance of an App IP installed on the App Platform instance delivers the PBX and myApps functionality.

The initial configuration of the Cloud Instance is done via the Install

== Instance Life-cycle ==

The innovaphone Cloud Instances can be created on the the [https://www.innovaphone.com/en/services/partner-login.html my.innovaphone Partner Portal].

After a successful login to the my.innovaphone Partner portal navigate to the tab "Cloud instances" to access the instance management view.

The Cloud Instances are shared between the accounts of the same company.

=== Create ===

* Unique name - the name of the instance. Could be a customer ID or customer name.
* External domain - the third-level domain name in the <code>*.innovaphone.cloud</code> domain

The creation of the instance may take few minutes. After the instance is created the

=== Delete ===

Make sure to create backups of the app instances in case any relevant data is stored there.

==Install==
The individual Install URL for each Cloud Instance is available on the instance entry and can be used to configure the App Platform and the PBX to a state with a fully functional myApps installation.

===Install type===
The only supported type of the installation for the innovaphone Cloud Instance is <code>Master PBX to start a new system with local App Platform</code>. The resulting installation contains an innovaphone App Platform and a PBX running as an App IP instance on it.

===Update URL===
The Update Server URL points to the App Store that will be used during the installation process. The default value should not be changed, unless you know exactly which version should be used instead.

===innovaphone PBX options===

*First user account with administrator rights - will be used for instance administration.
*Identification of the PBX - this should match the domain name of the Cloud Instance used in the Instance creation phase.
*PBX location name - the name of the PBX.
*Voicemail App - the version of the Voice Mail App (optional).
*Dialing prefixes - the dialing location information for the SIP trunk (optional).

===Emergency administration password===
It is recommended to save the emergency administration password for the case the user account with the administration rights is not functional.

===Email account===
The optional email account can be configured for the email delivery from the instance.

===Device certificates===
* Trust unverified IPVA certificates - this option will allow to connect additional IPVAs to this instance.

===Installation progress===
The set up progress screen lists the Apps that are being installed and redirects to the myApps login screen, when the installation is finished.

==Administration==
For the administration of the Cloud Instance following Apps are available:

*AP Manager - the App installation and the App Platform management.
*PBX Manager - the App instance setting in the PBX.
*Devices App - the advanced web UI of the PBX/App IP which is available via the PBX-UI button.

==Available Resources==
Each Cloud Instance is limited by the following constraints in therms of CPU, memory and storage:

*CPU: 0.25 CPU
*Memory: 384MiB
*Storage: 20 GB

==Current Limitations==
For the time of the public preview of the Cloud Instance the provided functionality is limited by the current state of the development.

===PBX functionality===
Following functions are not available or limited:
*PBX and telephony (H.323/SIP/Softphone) - the PBX functionality provided by the App IP is limited to the functions required for the myApps client.
*LDAP connectivity - connecting to the PBX/Contacts App via LDAP is not supported.
*Firmware/App Updates via Devices - no automatic app updates are available.
*myApps Launcher - the myApps launcher can not handle the URL used by the cloud instance - only usage from a web browser is supported.
*Licenses - no licenses are available, please use Test-Mode.

===Custom DNS Domains===
The Cloud Instances are solely available under the <code>*.innovaphone.cloud</code> domain.

===Distributed PBX Scenarios===
Each Cloud Instance represents one Master PBX. No Master PBX/Slave PBX scenarios are supported.

==Support==
Limited Support for the cloud instances is available via the Channel CloudSupport on the Community Connect (use tag <code>#CloudSupport</code>).

Reference15r1:Concept innovaphone Cloud Instance

2024-09-26T15:52:25Z

Afi:

= Applies To =

* innovaphone Cloud Instance on the <code>*.innovaphone.cloud</code> Kubernetes cluster

== Requirements ==

* Browser (Chrome, Firefox, ...)
* Access to the [https://www.innovaphone.com/en/services/partner-login.html my.innovaphone Partner Portal]

== Default credentials ==

'''During INSTALL, the default passwords are replaced with the global Admin PW!'''
* manager App (web login) '''pwd'''
* App IP (PBX advanced web UI) '''admin:pwd'''

== Concept ==
The innovaphone Cloud Instance is an [[Reference14r2:Concept App Platform |innovaphone App Platform]] running inside a container, orchestrated by a Kubernetes cluster hosted under the <code>*.innovaphone.cloud</code> domain.

The instance of an App IP installed on the App Platform instance delivers the PBX and myApps functionality.

The initial configuration of the Cloud Instance is done via the Install

== Instance Life-cycle ==

The innovaphone Cloud Instances can be created on the the [https://www.innovaphone.com/en/services/partner-login.html my.innovaphone Partner Portal].

After a successful login to the my.innovaphone Partner portal navigate to the tab "Cloud instances" to access the instance management view.

The Cloud Instances are shared between the accounts of the same company.

=== Create ===

* Unique name - the name of the instance. Could be a customer ID or customer name.
* External domain - the third-level domain name in the <code>*.innovaphone.cloud</code> domain

The creation of the instance may take few minutes. After the instance is created the

=== Delete ===

Make sure to create backups of the app instances in case any relevant data is stored there.

==Install==
The individual Install URL for each Cloud Instance is available on the instance entry and can be used to configure the App Platform and the PBX to a state with a fully functional myApps installation.

===Install type===
The only supported type of the installation for the innovaphone Cloud Instance is <code>Master PBX to start a new system with local App Platform</code>. The resulting installation contains an innovaphone App Platform and a PBX running as an App IP instance on it.

===Update URL===
The Update Server URL points to the App Store that will be used during the installation process. The default value should not be changed, unless you know exactly which version should be used instead.

===innovaphone PBX options===

*First user account with administrator rights - will be used for instance administration.
*Identification of the PBX - this should match the domain name of the Cloud Instance used in the Instance creation phase.
*PBX location name - the name of the PBX.
*Voicemail App - the version of the Voice Mail App (optional).
*Dialing prefixes - the dialing location information for the SIP trunk (optional).

===Emergency administration password===
It is recommended to save the emergency administration password for the case the user account with the administration rights is not functional.

===Email account===
The email account can not be configured yet - disable it.

===Device certificates===
* Trust unverified IPVA certificates - this option will allow to connect additional IPVAs to this instance.

===Installation progress===
The set up progress screen lists the Apps that are being installed and redirects to the myApps login screen, when the installation is finished.

==Administration==
For the administration of the Cloud Instance following Apps are available:

*AP Manager - the App installation and the App Platform management.
*PBX Manager - the App instance setting in the PBX.
*Devices App - the advanced web UI of the PBX/App IP which is available via the PBX-UI button.

==Available Resources==
Each Cloud Instance is limited by the following constraints in therms of CPU, memory and storage:

*CPU: 0.25 CPU
*Memory: 384MiB
*Storage: 20 GB

==Current Limitations==
For the time of the public preview of the Cloud Instance the provided functionality is limited by the current state of the development.

===PBX functionality===
Following functions are not available or limited:
*PBX and telephony (H.323/SIP/Softphone) - the PBX functionality provided by the App IP is limited to the functions required for the myApps client.
*LDAP connectivity - connecting to the PBX/Contacts App via LDAP is not supported.
*Firmware/App Updates via Devices - no automatic app updates are available.
*myApps Launcher - the myApps launcher can not handle the URL used by the cloud instance - only usage from a web browser is supported.
*Licenses - no licenses are available, please use Test-Mode.

===Custom DNS Domains===
The Cloud Instances are solely available under the <code>*.innovaphone.cloud</code> domain.

===Distributed PBX Scenarios===
Each Cloud Instance represents one Master PBX. No Master PBX/Slave PBX scenarios are supported.

==Support==
Limited Support for the cloud instances is available via the Channel CloudSupport on the Community Connect (use tag <code>#CloudSupport</code>).

Reference15r1:Concept innovaphone Cloud Instance

2024-09-26T14:30:19Z

Afi: Created page with "= Applies To = * innovaphone Cloud Instance on the <code>*.innovaphone.cloud</code> Kubernetes cluster == Requirements == * Browser (Chrome, Firefox, ...) * Access to the [https://www.innovaphone.com/en/services/partner-login.html my.innovaphone Partner Portal] == Default credentials == '''During INSTALL, the default passwords are replaced with the global Admin PW!''' * manager App (web login) '''pwd''' * App IP (PBX advanced web UI) '''admin:pwd''' == Concept == T..."

ReleaseNotes14r2:SDK

2024-05-13T09:56:56Z

Afi: Created page with "This is the SDK 14r2 Release Notes Document. Service Releases are planned for the second monday each month. Please see ''the disclaimer'' before using the information presented here! __NOEDITSECTION__ {{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=SDK%2014r2}} SDK"

This is the SDK 14r2 Release Notes Document. 
 
Service Releases are planned for the second monday each month. 
 
Please see ''[[Reference:What_are_the_Release_Notes_Documents?|the disclaimer]]'' before using the information presented here!

__NOEDITSECTION__
{{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=SDK%2014r2}}

[[Category:Release Notes|SDK]]

Howto:Guideline for Documenting Partner Apps

2024-03-13T12:45:38Z

Afi: /* Content template */

__TOC__
==Scope==

innovaphone supports execution of Partner Applications at the innovaphone myApps Application Platform.

Apps are developed using the [http://sdk.innovaphone.com innovaphone SDK] and may be published via the innovaphone App Store.

To achieve a higher level of awareness, App development Partners (App Partners) may be listed as technology partner on the innovaphone website and they can describe their App here in the innovaphone wiki in addition to the presentation in the innovaphone App Store.

This requires the documentation of the product by a respective wiki article.

In the following you can find a guideline on how to create this kind of article:

==Main rules==

The App development partner or any appropriate partner are '''exclusively responsible''' for
* creation of this document
* updating this document in case of any product changes
* inital and regression testing of the product and updates in conjunction with current innvaphone firmware
* support of the product

Test results and other informational data concerning the Partner App product have to be put into the innovaphone wiki according to following standardized format.

==Creation of a Partner App article==

* Login to innovaphone wiki
* Open this instruction in the first browser tab
* Open the following URL in a second window

http://wiki.innovaphone.com/index.php?title=Howto:productname_-_companyname_-_Partner_App&action=edit

* Replace the terms "productname" and "companyname" by your data
* Confirm your input by pressing Enter
* A new empty wiki page titled with the given URL is generated and opened in editor mode
* Copy the text content from the content template below and paste it completely into the empty wiki-page
* Start editing according to the comments given
* '''we request to describe the product in English only'''. No language mix.
* DON'T forget to SAVE!
* Upload appropriate files/images indicated by a red link
* Inform your innovaphone contact when finished
* innovaphone will set the correct product category and grant status upon successful document check

===Content template===
<syntaxhighlight lang="text">

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

==Product Name==


CompanyName [https://www.linktoproductpage.com ProductName]

==Certification Status==


==Category==




==Vendor==



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




BlaBlaBla (not: we are the best)


[https://www.vendor.tld/ VendorName - About us]

==Description==






xyz application is used to manage call flows within innovaphone PBX (not: this application is the best)


[https://www.vendor.tld/productpage VendorName - About this application]







==Functions==






===Multi-PBX ready===





===Cloud ready===





=== Provided APIs ===






==Licensing==



App(manufacturer-appname)
Service(manufacturer-appname)

==Prerequisites==



==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r?
===Application versions used for interop testing===


* vendorname productname versionno

* innovaphone V13r?sr?

==Configuration==













==Contact==




{|
| CompanyName
|-
| ContactName
|-
| Street
|-
| ZIP City Country
|-
| Tel:
|-
| Fax:
|-
| Mail: [mailto:contactname@companyname contactname@companyname]
|}

For any questions please refer to [https://www.vendor.tld/contact our contact page].
</syntaxhighlight>

Howto:Guideline for Documenting Partner Apps

2024-03-13T12:41:10Z

Afi: /* Content template */ fixed XML comments

__TOC__
==Scope==

innovaphone supports execution of Partner Applications at the innovaphone myApps Application Platform.

Apps are developed using the [http://sdk.innovaphone.com innovaphone SDK] and may be published via the innovaphone App Store.

To achieve a higher level of awareness, App development Partners (App Partners) may be listed as technology partner on the innovaphone website and they can describe their App here in the innovaphone wiki in addition to the presentation in the innovaphone App Store.

This requires the documentation of the product by a respective wiki article.

In the following you can find a guideline on how to create this kind of article:

==Main rules==

The App development partner or any appropriate partner are '''exclusively responsible''' for
* creation of this document
* updating this document in case of any product changes
* inital and regression testing of the product and updates in conjunction with current innvaphone firmware
* support of the product

Test results and other informational data concerning the Partner App product have to be put into the innovaphone wiki according to following standardized format.

==Creation of a Partner App article==

* Login to innovaphone wiki
* Open this instruction in the first browser tab
* Open the following URL in a second window

http://wiki.innovaphone.com/index.php?title=Howto:productname_-_companyname_-_Partner_App&action=edit

* Replace the terms "productname" and "companyname" by your data
* Confirm your input by pressing Enter
* A new empty wiki page titled with the given URL is generated and opened in editor mode
* Copy the text content from the content template below and paste it completely into the empty wiki-page
* Start editing according to the comments given
* '''we request to describe the product in English only'''. No language mix.
* DON'T forget to SAVE!
* Upload appropriate files/images indicated by a red link
* Inform your innovaphone contact when finished
* innovaphone will set the correct product category and grant status upon successful document check

===Content template===
<syntaxhighlight lang="text">

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

==Product Name==


CompanyName [https://www.linktoproductpage.com ProductName]

==Certification Status==


==Category==




==Vendor==



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




BlaBlaBla (not: we are the best)


[https://www.vendor.tld/ VendorName - About us]

==Description==






xyz application is used to manage call flows within innovaphone PBX (not: this application is the best)


[https://www.vendor.tld/productpage VendorName - About this application]







==Functions==






===Multi-PBX ready===





===Cloud ready===





=== Provided APIs ===






==Licensing==



App(manufacturer-appname)
Service(manufacturer-appname)

==Prerequisites==



==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r?
===Application versions used for interop testing===


* vendorname productname versionno

* innovaphone V13r?sr?

==Configuration==












==Contact==




{|
| CompanyName
|-
| ContactName
|-
| Street
|-
| ZIP City Country
|-
| Tel:
|-
| Fax:
|-
| Mail: [mailto:contactname@companyname contactname@companyname]
|}

For any questions please refer to [https://www.vendor.tld/contact our contact page].
</syntaxhighlight>

Howto:Guideline for Documenting Partner Apps

2024-03-13T12:23:33Z

Afi: /* Content template */ removed leading whitespace

__TOC__
==Scope==

innovaphone supports execution of Partner Applications at the innovaphone myApps Application Platform.

Apps are developed using the [http://sdk.innovaphone.com innovaphone SDK] and may be published via the innovaphone App Store.

To achieve a higher level of awareness, App development Partners (App Partners) may be listed as technology partner on the innovaphone website and they can describe their App here in the innovaphone wiki in addition to the presentation in the innovaphone App Store.

This requires the documentation of the product by a respective wiki article.

In the following you can find a guideline on how to create this kind of article:

==Main rules==

The App development partner or any appropriate partner are '''exclusively responsible''' for
* creation of this document
* updating this document in case of any product changes
* inital and regression testing of the product and updates in conjunction with current innvaphone firmware
* support of the product

Test results and other informational data concerning the Partner App product have to be put into the innovaphone wiki according to following standardized format.

==Creation of a Partner App article==

* Login to innovaphone wiki
* Open this instruction in the first browser tab
* Open the following URL in a second window

http://wiki.innovaphone.com/index.php?title=Howto:productname_-_companyname_-_Partner_App&action=edit

* Replace the terms "productname" and "companyname" by your data
* Confirm your input by pressing Enter
* A new empty wiki page titled with the given URL is generated and opened in editor mode
* Copy the text content from the content template below and paste it completely into the empty wiki-page
* Start editing according to the comments given
* '''we request to describe the product in English only'''. No language mix.
* DON'T forget to SAVE!
* Upload appropriate files/images indicated by a red link
* Inform your innovaphone contact when finished
* innovaphone will set the correct product category and grant status upon successful document check

===Content template===
<syntaxhighlight lang="text">

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

==Product Name==


CompanyName [https://www.linktoproductpage.com ProductName]

==Certification Status==


==Category==




==Vendor==



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




BlaBlaBla (not: we are the best)


[https://www.vendor.tld/ VendorName - About us]

==Description==






xyz application is used to manage call flows within innovaphone PBX (not: this application is the best)


[https://www.vendor.tld/productpage VendorName - About this application]







==Functions==






===Multi-PBX ready===





===Cloud ready===





=== Provided APIs ===






==Licensing==



App(manufacturer-appname)
Service(manufacturer-appname)

==Prerequisites==



==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r?
===Application versions used for interop testing===


* vendorname productname versionno

* innovaphone V13r?sr?

==Configuration==












==Contact==




{|
| CompanyName
|-
| ContactName
|-
| Street
|-
| ZIP City Country
|-
| Tel:
|-
| Fax:
|-
| Mail: [mailto:contactname@companyname contactname@companyname]
|}

For any questions please refer to [https://www.vendor.tld/contact our contact page].
</syntaxhighlight>

Howto:Guideline for Documenting Partner Apps

2024-03-13T12:15:23Z

Afi: /* Content template */

__TOC__
==Scope==

innovaphone supports execution of Partner Applications at the innovaphone myApps Application Platform.

Apps are developed using the [http://sdk.innovaphone.com innovaphone SDK] and may be published via the innovaphone App Store.

To achieve a higher level of awareness, App development Partners (App Partners) may be listed as technology partner on the innovaphone website and they can describe their App here in the innovaphone wiki in addition to the presentation in the innovaphone App Store.

This requires the documentation of the product by a respective wiki article.

In the following you can find a guideline on how to create this kind of article:

==Main rules==

The App development partner or any appropriate partner are '''exclusively responsible''' for
* creation of this document
* updating this document in case of any product changes
* inital and regression testing of the product and updates in conjunction with current innvaphone firmware
* support of the product

Test results and other informational data concerning the Partner App product have to be put into the innovaphone wiki according to following standardized format.

==Creation of a Partner App article==

* Login to innovaphone wiki
* Open this instruction in the first browser tab
* Open the following URL in a second window

http://wiki.innovaphone.com/index.php?title=Howto:productname_-_companyname_-_Partner_App&action=edit

* Replace the terms "productname" and "companyname" by your data
* Confirm your input by pressing Enter
* A new empty wiki page titled with the given URL is generated and opened in editor mode
* Copy the text content from the content template below and paste it completely into the empty wiki-page
* Start editing according to the comments given
* '''we request to describe the product in English only'''. No language mix.
* DON'T forget to SAVE!
* Upload appropriate files/images indicated by a red link
* Inform your innovaphone contact when finished
* innovaphone will set the correct product category and grant status upon successful document check

===Content template===
<syntaxhighlight lang="text">

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

==Product Name==


CompanyName [https://www.linktoproductpage.com ProductName]

==Certification Status==


==Category==




==Vendor==



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




BlaBlaBla (not: we are the best)


[https://www.vendor.tld/ VendorName - About us]

==Description==






xyz application is used to manage call flows within innovaphone PBX (not: this application is the best)


[https://www.vendor.tld/productpage VendorName - About this application]







==Functions==






===Multi-PBX ready===





===Cloud ready===





=== Provided APIs ===






==Licensing==



App(manufacturer-appname)
Service(manufacturer-appname)

==Prerequisites==



==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r?
===Application versions used for interop testing===


* vendorname productname versionno

* innovaphone V13r?sr?

==Configuration==












==Contact==




{|
| CompanyName
|-
| ContactName
|-
| Street
|-
| ZIP City Country
|-
| Tel:
|-
| Fax:
|-
| Mail: [mailto:contactname@companyname contactname@companyname]
|}

For any questions please refer to [https://www.vendor.tld/contact our contact page].
</syntaxhighlight>

ReleaseNotes13r2:Firmware

2023-11-07T13:10:17Z

Afi:

This is the Firmware 13r2 Release Notes Document.

Service Releases are planned for the second monday each month. For each of the service release the complete set of tests is executed. If problems show up during the tests, the problems are fixed. This may cause a delay. The tests are started early, so that some delay is covered, but it still may happen that the patchday has to be moved. In this case it is hard to predict when the service release is good. It may be any day, so it would not be good to move the patchday by a fixed number of days, it still should be released as early as possible.

Please see ''[[Reference:What_are_the_Release_Notes_Documents?|the disclaimer]]'' before using the information presented here!

__NOEDITSECTION__
{{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=Firmware%2013r2}}

[[Category:Release Notes|Firmware]]

Howto7:ACD with Voicemail XML Script and external Database or Application

2023-11-03T09:41:45Z

Afi: fixed syntaxhighlight

This article describes how to setup a simple automated call distribution by using custom voicemail XML script and an external database or a CRM application.

==Applies To==
This information applies to

* innovaphone PBX, V7

==More Information==
A frequently asked feature for incoming call centers is ability to connect incoming customer calls to their respective personal point of contact(an agent or agent group). The relationship of customer calling number and responsible agent is stored in the external database or CRM application. For this purpose a custom XML voicemail script can be used to perform a query from innovaphone PBX to an external application via HTTP.

The voicemail command <code>exec url</code> executes an HTTP GET CGI-request. The URL is supposed to contain arbitrary script variables. The remote CGI script shall return a short voicemail script comprising <code>assign</code> elements.

The call distribution is intentional designed so that the first free agent gets the most calls.

Please note, that the scripts are exemplary and free and can be modified to fulfil your special requirements.

===Configuration===
The outline for the following configuration scenario shall be as follows:
*Create a file with XML script listed below and named "acd.xml".
*Additionally place the text files with numbers of agents and voicemail box in this folder.
*Create a new voicemail object in the PBX with URL <code>http://127.0.0.1/drive/CF0/acd.xml?$_pbxfwd=true</code>.

Contents of acd.xml:
<syntaxhighlight lang="html5">
<?xml version="1.0" encoding="utf-8" ?>
<voicemail xmlns="http://www.innovaphone.com/xsd/voicemail6.xsd">
<function define="Main">

<pbx-getcallinfo out-cgpn="$cgpn" out-cdpn="$cdpn" out-leg2="$leg2" />


<assign out="$forward" value="999"/>


<exec url="http://172.16.0.17/query.php?cgpn=$cgpn"/>


<pbx-fwd e164="$forward" out-cause="$cause" barge-in="false" />


<store-get root="" name="silence.$coder" out-url="$ctrl" />
<pbx-prompt url="$ctrl" sec="1" repeat="true"/>
<pbx-disc/>

</function>
</voicemail>
</syntaxhighlight>

A very simple server side code example based on PHP:
<syntaxhighlight lang="php">
<?php
//just for test: if CGPN is 235, forward to 103
//implement your db query etc. here instead
if ($_GET['cgpn'] == "235") $forward = "103";

echo "<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n";
echo "<voicemail xmlns=\"http://www.innovaphone.com/xsd/voicemail6.xsd\">\r\n";
echo " <assign out=\"\$forward\" value=\"$forward\"/>\r\n";
echo "</voicemail>\r\n";
?>
</syntaxhighlight>

The response of the PHP script should be as follows(if CGPN is 235):
<syntaxhighlight lang="html5">
<?xml version="1.0" encoding="utf-8"?>
<voicemail xmlns="http://www.innovaphone.com/xsd/voicemail6.xsd">
<assign out="$forward" value="103"/>
</voicemail>
</syntaxhighlight>

===Known Problems===

*Don't forget to provide additional option to the script URL, since it is required for the executing of call forwards: <code>?$_pbxfwd=true</code>

== Related Articles ==
[[Howto:How_to_Configure_the_innovaphone_Voicemail|How to Configure the innovaphone Voicemail]]

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

Reference10:Concept SOAP API

2023-09-21T09:28:08Z

Afi: Updated SOAP API general description, added WebSocket RCC API hint

innovaphone®'s PBX web services, also known as SOAP API, while no longer actively extended, remains available and functional. A transition to WebSocket API, specifically the RCC API (https://sdk.innovaphone.com/13r3/doc/appwebsocket/RCC.htm), was introduced with version 13 firmware.

For ongoing development, we recommend utilizing [http://www.innovaphone.com/wsdl/pbx10_00.wsdl WSDL version 10 ''pbx10_00.wsdl''] (also available on the gateway <code>http://xx.xx.xx.xx/pbx10_00.wsdl</code>) in conjunction with this Wiki article. It's advisable to disregard the higher versions of WSDL for your development.

For upcoming developments the WebSocket API should be used, as it represents the current and future direction of our API development.

==Overview==

For an overview of the basic architecture, see the [[Reference:SOAP_API_%28pbx501.wsdl%29#Overview|corresponding chapter in the pbx501.wsdl related article]].

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

== Definition of PBX object (WSDL) ==
Within the SOAP framework there is a mechanism to formally decribe the definition of remote objects. This is done by so called WSDL (Web Service Description Language) files. This [[http://www.innovaphone.com/wsdl/pbx10_00.wsdl wsdl file]] defines the PBX web services described in this document.

NB: while you can access and retrieve the WSDL file through this URL on runtime of your application, we'd rather recommend to install a local copy with your application and use this on runtime. This way, your application will be immune against failures of www.innovaphone.com.

There is also an [[http://www.innovaphone.com/wsdl/pbx900.wsdl old version of the wsdl]] available which has less interface functions. This interface can still be accessed by legacy applications and is activated on the PBX by calling the '''Initialize''' Function with fewer arguments ('''Integer Initialize(string user, string appl, out key)'''). It should not be used for new develoments though.

=== SOAP URL ===
The SOAP service URI is '''/PBX0/user.soap''' for the standard PBX and '''/PBX-''id''/user.soap''' for a dynamic PBX (where ''id'' corresponds to the ''Id'' field in the [[Reference10:PBX/Dyn-PBXs]] configuration dialog). SOAP is accessible via plain HTTP or HTTPS, so valid URLs might be <code>http://172.16.0.1/PBX0/user.soap</code> or <code>https://172.16.0.1/PBX0-mydynpbxid/user.soap</code>.

==PBX Objects and Methods==

This section contains a language agnostic description of the PBX API’s object model. Despite of the fact that we are discussing an object model, the PBX API is in fact not an object oriented API. This is because SOAP itself is not really object oriented. In particular, there is no object creation, activation or lifetime concept. This is left up to the service designer. SOAP is more a message exchange mechanism than an object method invocation mechanism. This is reflected in the API structure.

Specifically, objects are represented through handles, which are integers. Objects are created and destroyed using dedicated methods and it’s the users responsibility to manage the lifetime of all objects.

The syntax shown here actually is no valid syntax in any existing language. Please refer to the various sample codes for working syntax.

===Session===

All PBX API methods are executed in the context of a session. A session is created using the '''initialize''' method and is identified by a handle. This handle must be provided to all subsequent method calls.

A session is owned by the PBX API user, i.e. there is no way to have access to a session of another application. Each session has a scope, which defines the view of the PBX the session user has. The scope determines the set of PBX registrations seen by the session.

Scopes are defined and configured in the PBX and are bound to particular PBX users. Thus, a session has a user attribute, which defines the scope. It includes all users which are members of groups '''user''' is active member of. If '''user''' is not an active member of any group, the scope is the user itself.

====Initialize(string user, string appl, bool $v, bool $v501, bool v700, bool v800, bool vx1000, out int key)====

To access the current web services implementation, '''v''', '''v501''', '''v700''', '''v800''' and '''vx10000''' must be present and set to '''true'''.
These parameters actually convey the wsdl version used by the client. Different versions of the interface use different parameter sets for the Initialize call. Applications should always use the wsdl version current at the time of writing the application.

The method creates a session. The session will have the user '''user'''’s scope ('''user''' is the ''Long Name'' of a PBX user). The session handle is returned and is 0 for failure and positive for a valid session handle. '''appl''' specifies the name of the calling application and is used for administrative purposes. The output parameter '''key''' is a random number associated to the session. It may be used in subsequent '''Echo''' operations.

When a session is created, '''UserInfo''' events for all PBX registrations in the scope can be received by the '''Poll''' function. Initially, one '''UserInfo''' per registration within the session’s scope is received (the list is terminated by a '''UserInfo''' with empty '''cn''' and may require multiple '''Poll''' calls to retrieve). Subsequently, '''UserInfo''' events are received when a registrations state changes.

The underlying transport session (HTTP) must authenticate itself either as '''user''' (using the users long name and PBX password) or as the admin user (using the gateway administrator account name and password) to perform an '''Initialize''' and any session related function. Note that if you use a PBX user account, the user needs to have at least ''Group/Call Forwards'' rights.

Note that the method to force the SOAP system you are using to authenticate to the PBX is entirely up to the system itself. Some systems even do not support authentication at all. If your SOAP implementation does not support digest authentication, make sure the gateway accepts basic authentication by setting the “''allow HTTP basic authentication''” in the “''General settings''”.

Note that although many HTTP connections may be used in a single session, at least one HTTP connection must remain open during the lifetime of the session. When the last connection disappears, the logical session is terminated after a short timeout. Some SOAP libraries may per default always close the HTTP connection and reconnect on subsequent SOAP calls, which will not work. The SOAP library should either be configured to keep at least one HTTP connection alive or, if this is not an option, the application should take care to always have a an active request pending (such as '''Poll''').

====Echo(integer session, integer key)====

Verifies a session. You need to supply the ''session'' identifier and ''key'' returned by a previous call to '''Initialize'''. Returns nonzero if successful.

====End(integer session)====

Terminates the session referenced by ''session''. No further events will be received.

====Integer Version(out string gkId, out string location, out string firmware, out string serial)====

Returns the version number of the WSDL file the PBX supports. The first released WSDL file had version number 500. The version described by this document has version number 501. Also delivers information about the connected PBX (in ''gkId'', ''location'', ''firmware'' and ''serial'').

====AnyInfo Poll(integer session)====

Returns pending events for the session referenced by ''session''. ''AnyInfo'' is a struct with four arrays as members: ''user'', ''call'', ''reg'' and ''info''. ''user'' is an array of type ''UserInfo'' and call is an array of type CallInfo. The other two arrays ''reg'' and ''info'' are currently not used.

After a successful '''Initialize()'' there will be a ''UserInfo'' event for each defined and visible user in the system. This allows the application to synchronize on the state of all visible users. The list will be terminated by an ''UserInfo'' event for a user with an empty ''cn'' which normally cannot happen since a user entry must have a cn.

===User===

A user represents a configured object within the PBX (a “PBX user”). The PBX API provides the '''UserInitialize''' method to obtain a handle to the user.

====UserInfo====
The user’s properties are stored in a ''UserInfo'' structure, which has the following elements:

*'''boolean active'''

true if the user exists. The only case where active can be false is when a user is moved out of the session context. This may happen if the users group assignment is changed or the user is deleted. A single UserInfo event will be posted with active set to false then.

*'''integer state'''

1 if the user is registered, 0 otherwise.

*'''integer channel'''

number of current calls.

*'''integer alert'''

number of alerting calls

*'''string type'''

the type of the users device. Currently defined are “'''ep'''” (it is an endpoint), “'''gw'''” (it is a gateway, for example a trunk line), “'''waiting'''” (a call queue) or “'''broadcast'''” (a group). Others may be defined over time.

*'''string guid'''

the users GUID. This is a globally unique identifier for the user.

*'''string cn'''

the common name of the user. This is what the PBX’s LDAP server recognizes as the CN of this user. The user’s name in the PBX configuration applet.

*'''string e164'''

the extension number the user is registered with.

*'''string h323'''

the alias the user is registered with.

*'''string dn'''

the users display name.

*'''string domain'''

the PBX domain if the Gatekeeper ID is used as domain

*'''boolean h323email'''

If true, the h323 name shall be used as primary email address when sending emails to this user.

*'''string email[]'''

email addresses of the user. If 'h323email' is not set, the first address in this list shall be used as primary email address when sending emails to this user.

*'''Group groups'''

An array of '''Group''' records (see below).

*'''Presence presence'''

An array of '''Presence''' records (see below).

*'''boolean cfg'''

If set to true indicates that the config of the user has changed

*'''string object'''

The type of the user object

*'''string loc'''

If the object described is not local to the PBX the '''UserInfo''' is sent from, the name of the location the object is homed in is given in this element. See '''LocationUrl''' to find out how to proceed further.

*'''string node'''

The node of the object.

*'''string nodenum'''

The object nodes node number (prefix).

*'''Info'''
An '''Info''' record describing various aspects of the user. The type of the information described in an individual '''Info''' record is determined by the value of its ''type'' member. Currently defined values for ''type'' are:

:*'''fake'''
: The value configured as 'Send Number'

*'''groups'''

The users group memberships are stored in a '''Group''' record which has the following elements:

:*'''string group'''

: the name of the group the user is a member of

:*'''bool active'''

: true if the user is an active member of the group

*'''presence'''

The users presence status is stored in a '''Presence''' record which has the following elements:

:*'''string status'''

: either '''open''' or '''closed'''

:*'''string activity'''

: The users current activity (optional)

:*'''string note'''

: The user provided additional note (optional)

====integer UserInitialize(integer session, string user, bool xfer, bool disc, string hw)====

Returns a handle to the named ''user'' (0 on failure). String <code>user</code> must be a Long Name(cn). Phone number(e164) is not supported. Use FindUser instead, to retrieve cn to specified e164 number.

Once a user handle is obtained with '''UserInitialize''', '''CallInfo''' events will be posted and retrieved via '''Poll''' for all calls related to the user. If '''xfer''' is set to '''true''', '''CallInfo''' events will also be posted for calls which are transferred away from '''user'''. Otherwise, such events will be posted only for the user handle which the call has been transferred to. Thus, without setting follow to true, an application will generally not be able to track calls after a transfer unless it has called '''UserInitialize''' for any PBX object a call may be transferred to and matches the new call on the transferred-to user via the '''conf''' information in the '''Info''' record of the new call (which will be identical to the '''conf''' information for the transferred call).

When '''xfer''' is set to '''true''', transferred calls will show up in the '''CallInfo''' records with a '''No''' element of type '''xfer''' that indicates the number the call has been transferred to.

When '''disc''' is set to '''true''', calls to phones of the monitored user are cleared only after the user hangs up the phone. This way it can be avoided that the SOAP application assumes the phone is free but is still off-hook. This only works with innovaphone H.323 endpoints since the Disconnect message used to do this is not defined in the SIP standard.

When a '''hw''' argument is provided only the device identified by this is monitored. Please note that a valid handle will be returned even if there is no matching device for '''user'''.

Also, the user handle can be used to create and control calls on behalf of the user.

====void UserEnd(integer user)====

Frees the handle ''user'' obtained with '''UserInitialize'''. No events will be posted for this user anymore.

====int SetPresence(inno:Presence presence, bool im, string contact, string guid, string h323)====

Sets the presence of a PBX user.

* '''presence''':
:* '''inno:PresenceStatus''': the status '''closed'''/'''open''' or empty
:* '''inno:PresenceActivity''': the activity like '''busy'''
:* string '''note''': the presence note
* '''im''': from im client?
* '''contact''': the presence contact like '''tel:''', '''calendar:'''...
* '''guid''': the user guid
* '''h323''': the h323 name of the user

You can use '''guid''' or '''h323''' to identify the user! If no guid is known, use '''*''' as guid value.
 
If the setting of the presence was ok, the method returns '''1'''. Otherwise '''0'''.

===Device===

For each User object multiple devices can be configured within the PBX. A device reprersents the physical endpoint used for calls (e.g. phones). Any registration to the PBX is associated to a configured device by the name/number used for the registration. Even thou it is possible that one configured device in the PBX accepts multiple registrations, it is recommened to configure the PBX in a way that there is one registration to a device. This way an application can control which physical endpoint is used for a call.

====Device[] Devices(int session, string user)====

This function returns an array of devices configured for a user identified by its cn (long name). The '''cfg''' flag in '''UserInfo''' is set when this information is changed. The structure 'Device' contains the following members:

{|
|valign=top nowrap=true|'''hw'''
|The Hardware Id used to identify the device. This string is used to associate any calls to devices.
|-
|valign=top nowrap=true|'''text'''
|A text configured as a description of the device. It can be used to be presented to the user for the user to select a device.
|}

===Call===
A call represents one leg of an existing call in the PBX.

====CallInfo====
The calls attributes are stored in a '''CallInfo''' structure, which has the following elements:

*'''int user'''

the user handle the call belongs to

*'''int call'''
the call handle

*'''int reg'''

currently unused

*'''bool active'''

'''true''' if the call exists, '''false''' if not. The only case where ''active'' can be '''false''' is when a call is terminated. A single '''CallInfo''' event will be posted with ''active'' set to '''false''' then

*'''integer state'''

A calls state. A bit field made up as follows:
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"
|+
| Value
| Mask
| Meaning
|-
| 1
| 0xF
| setup
|-
| 2 || 0xF || setup-ack
|-
| 3 || 0xF || call-proc
|-
| 4 || 0xF || Alert
|-
| 5 || 0xF || Connect
|-
| 6 || 0xF || disconnect sent
|-
| 7 || 0xF || disconnect received
|-
| 8 || 0xF || parked
|-
| 0 || 0x80 || inbound call
|-
| 128 || 0x80 || outbound call
|-
| 0 || 0x100 || active call
|-
| 256 || 0x100 || call on hold
|-
| 0 || 0x200 || active call
|-
| 512 || 0x200 || active call put on hold by peer
|}

Note that the PBX API is PBX-centric, not terminal centric. As such, it considers a call ''from'' the PBX ''to'' the terminal as ''outbound''.

Refer to the [[Howto:SOAP API PHP5 Sample Code#Working with Call States from CallInfo]] Article to learn how to work with the call state values.

*'''string msg'''
A textual representation of the signalling message causing this event. E.g. “'''x-setup'''”.

*'''No No'''

An array of '''No''' records (see below). This can include information about various peers related to the call itself. The type of the peer described in an individual '''No''' record is determined by the value of its '''type''' member. Currently defined values for '''type''' are:

:*'''peer'''

: The current remote end of the call (the local end is determined by the UserInfo identified through the user handle above)

:*'''leg2'''

: The last diverting user (if any)

:*'''leg2orig'''

: The 1st diverting user (if any, from on v9hf1)

:* '''leg1'''

: Indicates a call-forward/blind-xfer(?) to the calling end

:*'''ct'''

: The last user having transferred the call (if any)

:*'''parked-to'''

: The call was parked to the indicated endpoint. This is sent with the 'r-rel' message indicating the clearing of this call.

:*'''picking'''

: The call was picked by the indicated endpoint. Usually empty because sent with the new call which is created at the picking endpoint, but the fact that it is present indicates that this is a picked up call. The endpoint where this call is picked from is indicated with a ''ct'' No within the same call_info.
*'''Info info'''

An '''Info''' record describing various aspects of the call. The type of the information described in an individual '''Info''' record is determined by the value of its ''type'' member. Currently defined values for ''type'' are:

:*'''conf'''

: A string holding the ''conference id'' (a GUID) of the call the reported call leg (all legs of a certain call share the same ''conference id''). Also, CDRs for a call show this ''conference id'' (''ref'' for [[Reference:Call_Detail_Record_CDR|gateway CDRs]], ''conf'' in the ''<event>'' tag for [[Reference10:Concept_Call_Detail_Record_CDR_PBX|PBX CDRs]]).
:*'''cause'''

: The latest [[Reference:ISDN_Cause_Codes | cause code ]] which has been notified on the call

===== CallInfo for Boolean Objects =====
A ''Boolean'' will send a CallInfo event when it's status changes. From the indicated number, you can derive the status as follows:

00 - Auto-Off
01 - Auto-On
10 - Manual-Off
11 - Manual-On

====No Record====

Peer information is stored in a '''No''' record with the following elements:

*'''string type'''

the type of the peer described by the record

*'''string cn'''

the peer’s PBX’s objects common name (if any)

*'''string e164'''

the peer’s phone number

*'''string h323'''

the peer’s h323 alias

*'''string dn'''

the peer’s display name

====Info record====
Various information is stored in '''Info''' records with the following elements:

*'''string type'''

the type of the information described by the record

*'''string vals'''

a string value associated with this information (if any, the ''type'' of the element determines if an '''Info''' element has a string or an integer value)

*'''integer vali'''

an integer value associated with this information (if any)

Note that the call related functions do not return a meaningful value. This is because the operations success is reflected in the subsequent CallInfo events.

====integer UserCall(integer user, string cn, string e164, string h323, int reg, InfoArray info, int rc, string srce164)====

Creates an outgoing call from the '''user''' (which is a handle obtained by a call to '''UserInitialize''') to the destination described by ''cn'', ''e164'' and ''h323''. The argument '''srce164''' may be used to override the calling party number (note that this overrides the callers extension, not the full calling party number). Arguments ''reg'' and ''info'' are currently ignored. The argument ''rc'' is usually 0, unless special behavior is required by using other [[Reference8:SOAP_API#Remote_Control_Facilities|Remote Control Facilities]]. Returns a handle to the call (0 on failure).

The called number (''e164'') is interpreted in the context of the user object the call is placed for (''user'').

From V8HF3 on, if the srce164 argument of UserCall starts with 'r' or 'R', the call is sent with CLIR (calling line identification restricted).

Depending on the nature of the device the user is registered with, the device may actually place the call or the PBX may place a call and once it is accepted, it places another call to the destination.

====UserConnect(integer call)====
Connects an existing ''call''. This forces the device the user is registered with to accept the call. It may then go into hands-free mode. Incapable (i.e. non-innovaphone) devices may simply ignore this call.

====UserTransfer (int acall, integer bcall)====
''acall'' and ''bcall'' are both calls a single user currently has active. This method will connect ''acall'' with ''bcall'', leaving the user without both calls.

====UserMediaTransfer (integer acall, integer bcall, boolean user, boolean peer)====

This function establishes a media connection between two parties currently active in a call independent of the signalling connection. ''acall'' and ''bcall'' are both active (connected) calls. If ''user'' is true, the user sides of the calls are connected together, if ''peer'' is set to true the peer sides of the calls are connected together. If neither ''user'' nor ''peer'' is set the calls are connected to their respective signalling peers.

====bool UserRedirect(integer call, string cn, string e164, string h323, InfoArray info)====
Places a call to the destination described by ''cn'', ''e164'' and ''h323'' and connects ''call'' to this destination. Argument ''info'' is currently ignored.

Any call forwarding configured for the destination will be ignored. See [[Reference8:SOAP_API#bool_UserReroute.28integer_call.2C_string_cn.2C_string_e164.2C_string_h323.29|UserReroute()]] below.

====bool UserReroute(integer call, string cn, string e164, string h323)====
Performs a rerouting of the call. Call forwardings set for the destination will be obeyed.

====integer UserPickup(int user, string cn, integer call, string group, int reg, InfoArray info)====
Redirects a call such that it appears as a new call at ''user''. The call to be redirected can be specified by its ''call'' handle. Alternatively, calls can be picked up by a users ''cn'' or by a ''group'' name. If all parameters are null, an implicit pickup is done. The new call handle is returned. Arguments ''reg'' and ''info'' are currently ignored.

====UserClear(integer call, integer cause, InfoArray info)====
Disconnects the ''call'' providing ''cause'' as disconnect reason. For example the cause code ''26 non-selected user clearing'' could be used to disconnect the call immediately on local phone, so no disconnect tone is played.

Cause is coded as a 7bit integer according to the table found in [[Reference:ISDN Cause Codes]].
Argument ''info'' is currently ignored.

====UserCtComplete(integer call, string e164, string h323)====

Sends a notification to the device ''call'' is active on that the remote peer has changed to ''e164'' and ''h323''. This resembles the notification a device may receive if its remote peer transfers the call to the new destination. The device may update its display and/or call data accordingly. This call is often used to force the devices (i.e. telephones) display to show application specific data.

====UserHold(integer call, bool remote)====
Sets the call on hold. The device may or may not display the hold status. In any case, the media channel is disconnected until a UserRetrieve is called.

In ''V8 hotfix23'' an additional parameter '''remote''' was added. If set to '''true''', '''remote''' will force to play MOH only to remote user (who is being held), set to '''false''' maintains the default behaviour (MOH played on remote user and a dialing tone to local user (depending on the pbx firmware, versions prior to v11r2 will play music on hold)). To use this parameter the recent WSDL 8.00 file must be retrieved.

====UserRetrieve(integer call)====
Retrieves the ''call'' on hold. The device may or may not display the new status. In any case, the media channel is reconnected.

====integer UserPark(integer call, string cn, integer position)====
Parks the call at the PBX object '''cn''' and local user on postion '''position'''. A position of -1 means any position is allowed. The return value is the handle of the new call.

To unpark calls, use the returned call handle with the '''UserPickup()''' function.

The '''cn''' argument can be used to identify another object, where the call shall be parked to.

====UserDTMF(integer call, bool recv, string dtmf)====
Sends DTMF digits on behalf of the user. If '''recv''' is set to ''true'' the DTMF is sent to the local user.

====UserUUI(integer call, bool recv, string uui)====
Sends User-User_information on behalf of the user. If '''recv''' is set to ''true'' the uui is sent to the local user.

====UserInfo(integer call, bool recv, string cdpn, string key, string dsp)====
Sends INFO message on behalf of the user. If '''recv''' is set to ''true'' the INFO message is sent to the local user. This function can be used to send overlap dialing information.

====UserRc(integer call, integer rc)====
Sends remote control facility to an innovaphone IP phone. It will be ignored by 3rd-party endpoints.

A remote control facility can be sent to an innovaphone IP phone to activate additional call handling on the device.

The current set of remote control facility function codes actually depends on the firmware used on the telephone, not the WSDL version used for SOAP. The current set is documented in [[Reference:Remote Control Facility]].

This function can be used for example to establish a three-party conference on an innovaphone IP phone. For this use the function UserRc on an active call using the '''rc''' value 4, while a second call is on hold. See also the ''rc'' argument to [[#integer_UserCall.28integer_user.2C_string_cn.2C_string_e164.2C_string_h323.2C_int_reg.2C_InfoArray_info.2C_int_rc.2C_string_srce164.29|UserCall()]].

===Messaging===

====integer UserMessage(integer user, string e164, string h323, string msg, string src_e164, string src_h323 )====
Sends an message from the '''user''' (which is a handle obtained by a call to '''UserInitialize''') to the destination described by ''e164'' and ''h323''. The parameters ''src_e164'' and ''src_h323'' may be used to override the calling party's information, in order to present a different callback information to the recipient of the message. Returns a handle to the call (0 on failure), which can be used to track the delivery of the message. A event of type 'msg-sent' indicates the delivery of the message.

===Status Retrieval===

Instead of monitoring calls using the ''Poll'' mechanics, there are some functions to retrieve the current at a certain point in time.

====CallInfo[] Calls(integer session, string user)====
Returns an array of '''CallInfo''' records for the calls currently active at the registration defined by ''user''. Please note that this function may be called without having called '''UserInitialize ()''' before. Thus, the call handle information in the '''CallInfo''' records returned is meaningless.

====UserInfo[] FindUser(string v501, string v700, string v800, string vx1000, string cn, string h323, string e164, integer count, integer next, boolean nohide)====
Returns an array of at most ''count'' '''UserInfo''' records for the users matching ''cn'', ''h323'' or ''e164''. Only one of ''cn'', ''h323'' and ''e164'' may be specified, except that ''e164'' and ''cn'' may be specified. In this case the number in ''e164'' is interpreted in the Node of the user specified with ''cn''. The search string will be used as a starting point into the alphabetically sorted list of objects, that is, a search for “'''A'''” will yield entries starting with “'''A'''” but also – depending on ''count'' – the following entries. Neither search string may be empty. ''v501'', ''v700'', ''v800'' and ''vx1000'' must be set to a non-empty value. In case ''cn'' is set to the empty value, '''FindUser''' returns results starting from the first object in the PBX.

To call '''FindUser''', no session is required, however, you need a valid HTTP authentication.

Be aware that large values for ''count'' may fail and even crash the PBX. If you need to retrieve the whole user list, you should be using 20 as ''count'', provide the last ''cn'' retrieved as new start cn and loop until '''FindUser''' returns no more results, passing '''true''' as value for ''next'' for all but the first calls.

If the parameter ''nohide'' is true, all objects regardless if marked as ''Hide from LDAP'' or not are returned by the '''FindUser''' function.

====bool UserFindDestination(integer user, string e164, string h323, out UserInfo user)====
This function checks if a destination can be reached from a given user by either a given number or a given name. ''user'' is the user handle from which PBX user the searching is started through all PBX nodes up and down. ''e164'' is the number, ''h323'' is a name.

The function returns '''true''', if the number or name is incomplete, otherwise '''false'''. If a destination is found, a '''UserInfo''' ''user'' is delivered.

No session is required to call '''UserFindDestination''', however, you need a valid HTTP authentication.

====string License(integer session, string name)====
This function is for internal use only.

====string LocationUrl(string v501, string v700, string v800, string vx1000, string location, bool tls)====
Returns a string with the HTTP URL for the PBX named location to which a SOAP session can be created. Typically, ''location'' is retrieved from the ''vals'' element of an '''Info''' record with ''type'' '''loc''' in an '''UserInfo''' record.

''location'' needs to be specified as the '''h323''' attributes value of the PBX node '''UserInfo''' data you are interested in.

If ''tls'' is set to '''true''', a HTTPS URL is returned.

====string UserLocalNum(int user, string num)====
Converts a given number '''num''' into a number diallable from the location of a specific '''user'''. Useful in inter-node scenarios where a destination node number and -extension are known, but the required escape prefix digits are unknown.
;user:The id of the specified user
;num:The number to be localized into the spefified user's location
;result:The localized number, including escape prefixes

===Administration===
The SOAP interface can be used for administrational purposes also. This is done via the Admin call. All kinds of PBX objects can be created, read or modified.

====string Admin(string xml)====

Sends the administrational command ''xml'' to the PBX. The command is executed and any result is returned.

This command allows you to query and modify the PBX object configuration (e.g. to query and set a users call forwarding). The scope and format of the commands valid for ''xml'' is beyond the scope of this document, however, there is a [[Howto:Using the SOAP Admin Function | separate article on that ]].

To call '''Admin''', no session is required. However, you must be authenticated as an admin user on the underlying HTTP layer.

[[Howto:Using the SOAP Admin Function]]

==Typical design of a PBX SOAP Application==
Please refer to the [[Reference:SOAP_API_%28pbx501.wsdl%29#Typical_design_of_a_PBX_SOAP_Application|pbx501.wsdl]] article for a discussion of the typical design of a SOAP application.

==References==
* [http://www.innovaphone.com/wsdl/pbx10_00.wsdl Version10-wsdl].

Applications based on this wsdl will work with V10 PBX firmware (and up) only.

Applications written to the previous pbx501.wsdl, pbx700.wsdl and pbx900.wsdl will continue to work with V10 firmware.

For your reference the old version files are still available:
* [http://www.innovaphone.com/wsdl/pbx501.wsdl Version5-wsdl]
* [http://www.innovaphone.com/wsdl/pbx700.wsdl Version7-wsdl]
* [http://www.innovaphone.com/wsdl/pbx900.wsdl Version9-wsdl]

==Known Problems==
Please read [[Howto:Authentication in the SOAP interface]] in case you have problems to authenticate SOAP access.

==System Requirements==
The PBX SOAP API requires a working PBX.

To work with the PBX API in this version, you must run at least version 7.00 software on your PBX. Also, you must run at least version 5 software on the phones.

==Installation==
There is no specific installation required, as the PBX API is integral part of the PBX (although licenses are required to operate the PBX).

==Configuration==
To prepare an PBX for PBX API testing
*setup a separate PBX
*install current firmware (at least 8.00)
*configure the PBX as usually
*add an user object called '''API''' , define a ''password'' for this object
*create a new group (e.g. called '''all users'''), by adding a group tag to '''API''', make it ''active''
*add a similar group tag to all other test users
*call '''Initialize()''' and use '''API''' as user and '''API''' and its ''password'' as http credentials

==Known Issues==
We have reports that the PBX wsdl is incompatible to some of the contemporary SOAP platforms available in the market. Most notably, Silverlight and Java seem to be affected. These problems are fixed in the v11 implementation of the PBX SOAP interface ''pbx11_00.wsdl'' (available at [http://www.innovaphone.com/wsdl/pbx11_00.wsdl www.innovaphone.com/wsdl/pbx11_00.wsdl ]).

Note: This wdsl file is not available directly from the PBX (e.g. at <code>http://xx.xx.xx.xx/pbx11_00.wsdl</code>)

However, we have had indications that for Java, solutions are possible based on Apache Axis 1.4, Netbeans 6.8 or JAX-RPC.

The PBX does not expect the SOAP client to disconnect the session right after a UserCall. If this is the case (e.g. in a script which merely creates a call on behalf of a user and then terminates), it might happen that the outgoing call from the device will not be created correctly (a matter of timing). In this case, just wait for one second.

==Related Articles==
:[[Howto:Authentication in the SOAP interface]]
:[[Howto:Clear a call completely with SOAP using UserClear]]
:[[Howto:PBX SOAP Api C sample code]]
:[[Howto:SOAP Api VisualBasic.Net Sample Code]]
:[[Support:TAPI or other SOAP Application fails to function properly if PBX users have special characters in their long or short user name]]
:[[Howto:How to monitor configuration changes in the SOAP interface ]]
:[[Howto:SOAP with PHP5 ]]
:[[Howto:SOAP API Java Sample Code ]]
:[[Howto:Using the SOAP Admin Function]]

[http://wiki.innovaphone.com/index.php?search=soap Search for more articles about SOAP]

Howto:SOAP API PHP5 Sample Code

2023-08-23T13:42:48Z

Afi: fix link to SOAPClient PHP Lib

==Applies To==
This information applies to

* V9 and later innovaphone PBX platform
* web server running PHP 5

innovaphone PBX web services can be used from PHP easily. Here is how



==More Information==
===Configuration===
You will need php with the SoapClient class available.

The innovaphone PBX wsdl file is required. See [[Reference8:SOAP API]] for information how to obtain this file.
To access older WSDL versions, you will need to change the WSDL URL setting (in <code>const ___wsdl</code>) and adapt to the required number of version booleans in the call to <code>Initialize()</code> in the pbx wrapper class.

If you have access to the internet, you can try out the sample code given below right away. Of course you may also adapt the sample script configuration and try with your own innovaphone PBX.

===Running the Sample Code===
To demonstrate SOAP usage with PHP, a simple script is presented that will allow you to initiate a call using a web page.

The following class '''innoPBX''' is used to wrap the (somewhat clumsy) PHP SOAP access mechanism:

<code php>
<?php

// innovaphone PBX SOAP API PHP wrapper class
//

class innoPBX extends SOAPClient {

protected $___key; // the session key
protected $___session; // the session id

protected $___options = array(
// default SOAPClient::__construct options used by the class
"connection_timeout" => 10,
"exceptions" => true,
);

const ___wsdl = 'http://www.innovaphone.com/wsdl/pbx900.wsdl';

// class constructor
public function __construct(
$server, // the PBX IP
$httpu, // the HTTP user id (e.g. "admin")
$httpp, // the HTTP password (e.g. "ip800")
$user = null, // the PBX user CN to work with
$options = null,
// extra or overriding options for SOAPClient::__construct
$wsdl = null // the wsdl file location
) {
$wsdl = ($wsdl === null) ? self::___wsdl : $wsdl;
$usedoptions = array( // forced options
'login' => $httpu,
'password' => $httpp,
'location' => "http://$server/PBX0/user.soap",
);
if (is_array($options)) $usedoptions += $options;
// merge in user options
$usedoptions += $this->___options; // merged in class global options

// construct parent class
parent::__construct($wsdl, $usedoptions);

// get the connection (using and activating v9 wsdl)
$init = $this->Initialize($user, "PHP SOAP Wrapper", true, true, true, true, true);
$this->___key = $init['key'];
$this->___session = $init['return'];
}

public function key() { return $this->___key; }
public function session() { return $this->___session; }
}

?>

</code>
Save this code into a file named '''innopbx.class.php''' on your web server. This class is of course not required to use PHP SOAP with the innovaphone PBX API. However, it comes handy and should be generic enough to be useful in most cases.

The SOAP client uses the following code:

<code php>
<?php

// get the innoPBX wrapper class
require_once('innopbx.class.php');

// dummy classes to map SOAP results to (really would love to use namespaces here...)
// you can add methods and variables to these classes as needed
class innoUserInfo { };
class innoCallInfo { };
class innoAnyInfo { };
class innoGroup { };
class innoNo { };
class innoInfo { };

// config, adapt to your need
// this data below will work with innovaphones demo PBX. Just register 2 phones as user-3 and user-4 and hve fun!
$server = "demo.innovaphone.com";
$user = "SOAP";
$httpu = "demo";
$httpp = "demo";
$caller = "PBX User Four";
$destination = "130";

print "<pre>";

// create connector to PBX
// class mapping is optional
$inno = new innoPBX($server, $httpu, $httpp, $user,
array('classmap' => array("UserInfo" => "innoUserInfo",
"CallInfo" => "innoCallInfo",
"AnyInfo" => "innoAnyInfo",
"Group" => "innoGroup",
"No" => "innoNo",
"Info" => "innoInfo",
)));
if ($inno->key() == 0) die("failed to login to PBX");

// show all methods supported by this object
print "All the functions provided by class innoPBX:\n";
print_r($inno->__getFunctions());
print "\n\n";

// get version info
$v = $inno->Version();

// show both types of infos list
function showInfos(&$poll, $head, $cn = "", $user = "", $call = "") {
print $head . "\n";
if ($cn !== null) {
print count($poll->user) . " UserInfos\n";
foreach($poll->user as $ui) {
if (($cn === "") || ($cn == $ui->cn)) {
print " {$ui->cn} ({$ui->h323} #{$ui->e164}) state {$ui->state}\n";
}
}
}
if ($call !== null) {
print count($poll->call) . " CallInfos\n";
foreach($poll->call as $ci) {
if ((($user === "") || ($user == $ci->user)) &&
(($call === "") || ($call == $ci->call))) {
print " {$ci->user}/{$ci->call} {$ci->No[1]->h323} #{$ci->No[1]->e164} (remote {$ci->No[0]->h323} #{$ci->No[0]->e164}) msg {$ci->msg}\n";
}
}
}
}

// retrieve the full user list. Foreach object in the PBX, one userinfo is posted, terminated by an empty one
// You cannot assume that you will receive this list within a certain number of Poll results, so please iterate
print "Retrieving User list for "; foreach ($v as $name => $value) print "\n $name=$value "; print "...\n\n";
$seen = false;
$i = 1;
while (!$seen) {
$p = $inno->Poll($inno->session());
showInfos($p, "Poll() result #$i", "", null, null); $i++;
if ($p->user[count($p->user)-1]->cn == "") {
// we have seen all entries
print " --- END OF LIST ---\n\n";
$seen = true;
break;
}
}

// create a call on behalf of some user
// first we need a user handle
print "\nObtaining a user handle for $caller...";
$uhandle = $inno->UserInitialize($inno->session(), $caller);
print " $uhandle\n";
if ($uhandle == 0) {
die("cant get user handle for $caller");
}

// then we create a call
print "Creating call from $caller to $destination...";
$call = $inno->UserCall($uhandle, null, $destination, null, 0, array());
print " $call\n";
if ($call == 0) {
die("cant call on behalf of user $caller ($uhandle)");
}

// get call state(s) until call disappears
// note: you must at least poll for one call info related to this call, if you end
// the session right after UserCall, the call will not succeed!
$done = false;
while (!$done) {
ob_flush(); // this is just to see the progress on the call states
$p = $inno->Poll($inno->session());
showInfos($p, "Call States #$i for #{$call}", $caller, $uhandle, $call); $i++;
// see if there was a del event (there is ALWAYS a del event)
// we could as well look for an event with active = false
foreach ($p->call as $ci) {
if (($ci->user == $uhandle) &&
($ci->call == $call) &&
($ci->msg == "del")) {
print "\nCall terminated!\n";
$done = true;
}
}
}

// terminate the session
$e = $inno->End($inno->session());

?>
</code>
Save this into a file named '''innopbx.sample.php''' in the same directory of your web server.
To run the code, you need to examine and possibly adapt the configuration parameters in '''innopbx.sample.php''':
<code php>
// config, adapt to your need
// this data below will work with innovaphones demo PBX. Just register 2 phones as user-3 and user-4 and hve fun!
$server = "demo.innovaphone.com";
$user = "SOAP";
$httpu = "demo";
$httpp = "demo";
$caller = "PBX User Four";
$destination = "130";
</code>

This configuration will work right away with our publicly available [http://demo.innovaphone.com demo PBX]. You simply need to register 2 phones with the '''user-3''' and '''user-4''' users.

Of course you can also use your own PBX. Set the configuration parameters as follow:
{|
|$server || IP address of your innovaphone PBX
|-
| $user || CN (aka ''Long name'') of a PBX user that is active group member of a group where all others are (active or passive) members of
|-
| $httpu || the admin account of the box running the innovaphone PBX (e.g.'''admin''')
|-
| $httpp || the admin password of this box (e.g. '''ip''xxx''''')
|-
| $caller || CN (aka ''Long name'') of a PBX user you will have the script make a call for
|-
| $destination || the number to be called
|}

When the configuration parameters are set, you can point your browser to '''http:'''<nowiki>//</nowiki>''your-web-server-ip''/''path-to-folder''/'''innopbx.sample.php''' which should create a call on '''$callers''' phone.

Please note that you need internet access to retrieve the wsdl from innovaphone's web site.

===How the code works===
====The innovaphone PBX API wrapper class====

This class is derived from (''extends'' in PHP speak) the standard SOAPClient class. It basically simplifies the use of the standard class and performs the required call to '''Initialize''' within its constructor.

The constructor takes the following arguments:

<code php>
public function __construct($server, $httpu, $httpp, $user, $options = null, $wsdl = null);
</code>

{|
|$server, $httpu, $httpp, $user || see table above
|-
| $options
| an optional array of further options to SOAPClient::__construct. Normally not required. See [https://www.php.net/manual/en/class.soapclient.php the PHP SOAPClient class documentation] for details.
|-
| $wsdl
| the optional URI of the pbx wsdl file. Please note that you should use '''pbx10_00.wsdl''' instead of '''pbx.wsdl''', as this is the more recent version of the wsdl. By default, the wsdl is received from the innovaphone web and (subject to PHP configuration options) cached in PHP's wsdl cache. If you intend to supply it locally (which is recommended, as you otherwise depend on www.innovaphone.com being available each time your program runs), use a '''file://''' URI.
|}

Calls to PBX API functions defined in the wsdl can be done directly through an instance of '''class innoPBX'''. These member functions - which are neither defined in '''class innoPBX''' nor in '''class SOAPClient''' - are created automagically by reading the wsdl:
<code php>
$v = $inno->Version();
</code>

To see the functions available and their PHP signatures, you may call
<code php>
$inno = new innoPBX(...);
print_r($inno->$inno->__getFunctions());
</code>

Many PBX SOAP API functions required either the ''session-key'' or ''session-handle''. These are available from the class instance for convenience:
<code php>
$p = $inno->Poll($inno->session());
</code>

==== How to use the innovaphone PBX API wrapper class with SSL ====
{{3rd Party Input}}
In order to make a secure connection to the PBX, you have to change the '''inno.class.php''' as follows:

<code php>'location' => "https://$server/PBX0/user.soap"</code>

''Note'': in '''PHP 5.6''' all encrypted client streams now '''enable peer verification by default'''. By default, this will use OpenSSL's default CA bundle to verify the peer certificate.
See: [http://php.net/manual/en/soapclient.getfunctions.php OpenSSL changes in PHP 5.6.x]

To disable peer verification for the soap connection, you have to pass this as an option to the constructor:

<code php>
$context = stream_context_create(array(
'ssl' => array(
'verify_peer' => false,
'verify_peer_name' => false,
'allow_self_signed' => false
)
));

$options = array('stream_context' => $context);

$inno = new innoPBX($server, $httpu, $httpp, $user, $options, $wsdl);
</code>

More information on stream_context_create and ssl options:
[http://php.net/stream_context_create stream_context_create] and
[http://php.net/manual/en/context.ssl.php SSL context options]

====How PHP maps SOAP parameters to method parameters and results====
The mapping of parameters is pretty straight forward. Arguments passed in to a SOAP method are passed as a value parameters to the class methods. The thing to understand is that return values are always passed as return values, never as ''by-reference'' method arguments.

If a SOAP method returns a single item, then it is returned by the function directly with appropriate type:
<code php>
int UserInitialize(int $session, string $user);
</code>
The single return value from the '''UserInitialize''' SOAP method is returned as '''int''' by the '''UserInitialize''' '''innoPBX'''-method.

If the SOAP methods returns multiple items, then the corresponding class method will return an array:
<code php>
array Initialize(string $user, string $appl);
</code>
will return an array such as
<code php>
array(
['return'] => value
['key'] => value
)
</code>
In the method signature printed out by '''__getFunctions()''' this looks like
<code php>
list(int $return, int $key) Initialize(string $user, string $appl)
</code>

====The sample class user====
This section will discuss the sample code. It is not a decent description of the PBX SOAP API. For this, see the related articles.

A new '''innoPBX''' class instance object '''$inno''' is created using the values from the configuration variables discussed above.

<code php>
$inno = new innoPBX($server, $httpu, $httpp, $user,
array('classmap' => array("UserInfo" => "innoUserInfo",
"CallInfo" => "innoCallInfo",
"AnyInfo" => "innoAnyInfo",
"Group" => "innoGroup",
"No" => "innoNo",
"Info" => "innoInfo",
)));
</code>

The option fifth argument will add a '''classmap''' entry to the options passed to '''SOAPClient::__construct'''. If this is done, the SOAP class will use your defined classes when returning values to the caller. Otherwise, structured return values will be indexed arrays (using the element names as array indexes). This is neat, but not required for the class to function.

When '''Initialize''' (which is done implicitly in the '''innoPBX''' constructor) was successfull, one '''UserInfo''' class object per PBX object is posted to the caller. This list is terminated by an empty entry (more precisely, an entry with an empty '''cn''' member).

The
<code php>
while (!$seen) {
$p = $inno->Poll($inno->session());
...
</code>

loop will retrieve and show all these entries.

To be able to perform calls, a user session must be opened by
<code php>
$uhandle = $inno->UserInitialize($inno->session(), $caller);
</code>

The '''$uhandle''' retrieved will identify the user to be worked with on subsequent calls.

A call on behalf of '''$caller''' is then initiated:
<code php>
$call = $inno->UserCall($uhandle, null, $destination, null, 0, array());
</code>

When '''UserCall''' returns a non-zero call handle, the call is initiated and can be monitored by examining '''CallInfo''' events returned by subsequent '''Poll()''' calls:

<code php>
while (!$done) {
$p = $inno->Poll($inno->session());
</code>

this will retrieve events from the PBX

<code php>
if (($ci->user == $uhandle) &&
($ci->call == $call) &&
($ci->msg == "del")) {
print "\nCall terminated!\n";
$done = true;
</code>

until a '''del''' event is seen for the call previously created by UserCall. Please note that any number of call events may occur, e.g. because someone else called $caller. You cannot assume that all events retrieved are related to the call you created. Also, any number of '''UserInfo''' events may be retrieved.

Please note that there is no need to consume all of the events related to the call for it to work. However, you must not terminate the session before the call is actually proceeding. If you do so, strange things will happen. To be sure the call proceeds, it is ok to wait for ''just any'' '''CallInfo''' event related to the call. You can then safely terminate your session and exit the web page.

==Working with Call States from CallInfo==
The ''state'' field of the [[Reference10:Concept_SOAP_API#CallInfo|''CallInfo'']] contains a bit field encoded information about direction of the call, hold information and an actual call state.

Here is an example how to get relevant states:

<code php>
<?php

// decimal state value from CallInfo
// $callstate = 2;

// call state?
switch ($callstate & 0xF) {
case 1:
echo ("setup\r\n");
break;
case 2:
echo ("setup-ack\r\n");
break;
case 3:
echo ("call-proc\r\n");
break;
case 4:
echo ("Alert\r\n");
break;
case 5:
echo ("Connect\r\n");
break;
case 6:
echo ("disconnect sent\r\n");
break;
case 7:
echo ("disconnect received\r\n");
break;
case 8:
echo ("parked\r\n");
break;
default:
echo ("UNKNOWN STATE: " . ($callstate & 0xF) . "\r\n");
break;
}

// call direction?
switch ($callstate & 0x80) {
case 0:
echo ("inbound call\r\n");
break;
case 128:
echo ("outbound call\r\n");
break;
default:
echo ("UNKNOWN STATE: " . ($callstate & 0x80) . "\r\n");
break;
}

// is call on hold?
switch ($callstate & 0x100) {
case 0:
echo ("active call\r\n");
break;
case 256:
echo ("call on hold\r\n");
break;
default:
echo ("UNKNOWN STATE: " . ($callstate & 0x100) . "\r\n");
break;
}

// is call being held by peer?
switch ($callstate & 0x200) {
case 0:
echo ("active call\r\n");
break;
case 512:
echo ("active call put on hold by peer\r\n");
break;
default:
echo ("UNKNOWN STATE: " . ($callstate & 0x200) . "\r\n");
break;
}

?>

</code>

==More Sample Code==
Much more elaborate SOAP sample code is available for download from [http://wiki.innovaphone.com/index.php?title=Howto:Wiki_Sources#soapphp5 the samples section] on http://download.innovaphone.com.

Note that if you want to use [[Howto:Use_the_innovaphone_Demo_PBX | innovaphone's demo PBX ]] to test the code, you need to change the PBX IP address from 145.253.157.200 to <code>demo.innovaphone.com</code> in the downloaded code.

This code shows how to deal with call control on master/slave scenarios as well as how to perform PBX configuration updates or PBX object creation using the [[Howto:Using the SOAP Admin Function|SOAP Admin function]]. Currently, there are the following sample functions available:

* create a SOAP session to the master PBX
* create a user session on a device
* initiate a call via SOAP and terminate it once connected
* List all available SOAP functions
* Show an object's configuration using the Admin() function
* clone of adminshow which forces config=1
* Modify a user object using the Admin() function
* Clone a PBX object using the Admin() function
* Add call forwarding using Admin() function
* Delete call forwarding using Admin() function
* Get the PBX key
* Generate an encrypted PBX user password
* Set a new password for user
* Get the password of a PBX object in clear
* Decrypt a password from VARs (only works for boxes with default admin password!)
* Encrypt a password for use in VARs (only works for boxes with default admin password!)
* Find matching users

Although this code is written in PHP5, it is also good reading if you do not intend to use PHP as it exemplifies the principles of using SOAP and the SOAP Admin() function.

==Download ==
*[http://wiki.innovaphone.com/index.php?title=Howto:Wiki_Sources#soapphp5 Download] the complete file package of scripts and files described in this article.

==Related Articles==
* [[Reference:SOAP API]]
* [[Reference7:SOAP API]]
* [[Reference8:SOAP API]]
* [[Reference9:Concept SOAP API]]
* [[Reference10:Concept SOAP API]]
* [[Howto:Use the innovaphone Demo PBX]]

* [[Howto:Using the SOAP Admin Function]]

[http://wiki.innovaphone.com/index.php?search=soap+sample&go=Go Search all SOAP sample code in the wiki]



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

ReleaseNotes13r3:SDK

2023-07-20T14:25:04Z

Afi:

This is the SDK 13r3 Release Notes Document. 
 
Service Releases are planned for the second monday each month. 
 
Please see ''[[Reference:What_are_the_Release_Notes_Documents?|the disclaimer]]'' before using the information presented here!

__NOEDITSECTION__
{{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=SDK%2013r3}}

[[Category:Release Notes|SDK]]

Reference13r3:Concept Conference Meeting Invitations

2023-05-27T15:52:46Z

Afi:

[[Category:Concept_Conference]]


= Applies To =

* innovaphone PBX from version 13r3

= Overview =
Conference meeting invitations is a new feature of the [[Reference13r1:PBX/Objects/Conference | Conference Object]]. Meeting invitations are used to create temporary conference rooms.

= Requirements =
* CONF or SCNF interface with [[Howto:Conferences%2C_Resources_and_Licenses | appropriate channel licensing]]
* Conference App license (App(innovaphone-pbx-conference)13), necessary to create meeting links and invitations.
* If announcements should be played, announcement files must be available. The file names are listed [[Reference13r3:PBX/Objects/Conference/Announcement_types | here]].

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

In addition, two new options have been introduced:

;Web Access allowed: Needs to be enabled to use the temporary meeting links
;International Number: Needs to be set to add a phone number in the meeting invitations.

= Features =
The conference web access features are available.

* Dial-in with web access link
* Dial-in with a SIP uri.
* Dial-in with a number and an additional meeting id if this id is not used several times and the meeting room is created.

= Usage =
The conference doesn't save meeting links and so, it doesn't reserve any conference channel for them. The conference reserves channels if a meeting link is used and a meeting room is created.

== Creating Meetings ==
A meeting is defined by a meeting id, the start and end of the date and time and the number of participants. The number of participants specifies how many channels will be allocated for this meeting.

A meeting HTTP link and a SIP uri can be generated in the conference app by clicking the invitation button, ''create link'', which can be directly sent to participants via email. If the ''mail link'' button is used, a mail-to link is generated and opened, so the operation system opens an email client with a prefilled message subject and body.

In addition, a meeting can be scheduled. A calendar file (ICS) is created by clicking the ''open calendar'' button. It depends on the current browser configuration if the calendar file is saved to the client system or opened with a supported application.

The generated HTTP link can be used to take part in the meeting with a browser, the generated SIP uri can be used with a phone app, internal or with federation.

It is also possible to take part in the meeting with a dial-in number. The room number must be dialed followed by the meeting id with DTMF. This is possible not before someone else has used the HTTP link or the SIP uri.

== Joining Meetings ==
A meeting link can be used between one hour before the defined starting time and the defined end time, or if the meeting is being on.
If you call the meeting room one hour till five minutes before the meeting starts, a predefined announcement is played. No room is created and no conference channels are reserved at this time.

If you call or have a call to the meeting room five minutes or less before the meeting starts, a room is created, channels are reserved and the meeting room is listed in the conference app. The conference reserves as many channels as previously defined as number of participants. If not enough channels are available, the caller is announced and the call is disconnected.

== Moderating Meetings ==
All current meetings of a room can be listed in the corresponding conference room app. If a meeting is chosen, the participants of this meeting room are shown. A meeting room only appears five minutes before the meeting starts.

= Data Content =
The base64-encoded data of the HTTP link or SIP URI includes following content:

# the version number, currently 0, 1 byte (hex: 00)
# flags for optional content, currently 0, 1 byte (hex: 00)
# the room number length, 1 byte (e.g. 2 digits, hex: 02)
# the room number, 4 bytes (e.g. room number 1, hex: 00 00 00 01)
# meeting id, 4 bytes (random unique 6-digit id e.g. hex: 00 00 00 01)
# start timestamp, 4 bytes (e.g. 20-03-2023 12:00 unix-timestamp: 1679310000, hex: 64 18 3c b0)
# end timestamp, 4 bytes (e.g. 20-03-2024 17:00 unix-timestamp: 1710950400, hex: 65 fb 08 00)
# number of reserved channels, 2 bytes (e.g. 5, hex: 00 05)
# m-key from the conference object, read in the config-show from the PBX, the m-key value from the used conference object and convert in hex, 4e5344534f537153
# creation timestamp, not used for the hash calculation, 4 bytes (e.g. 20-03-2023 12:00 unix-timestamp: 1679310000, hex: 64 18 3c b0)
# MD5 hash, 16 bytes The MD5 hash is calculated with the content above from point 1 until 8, followed by point 9, the meeting password ("m-key") from the conference object in your configuration.

Example for the link creation:
* The data for the MD5 hash calculation contain the Bytes from points 1 to 9: 00 00 02 00000001 00000001 64183cb0 65fb0800 0005 4e5344534f537153
* Calculated MD5 hash from above data, bytes: b42f6e2c0f130900f6b62c51e74dc2aa
* The data for the Base64 encoded link contain the point 1 to 8, 10 and 11, the above MD5 hash value: 00 00 02 00000001 00000001 64183cb0 65fb0800 0005 64183cb0 b42f6e2c0f130900f6b62c51e74dc2aa
* Base64 encoded: AAACAAAAAQAAAAFkGDywZfsIAAAFZBg8sLQvbiwPEwkA9rYsUedNwqo=
* Link to the temporary conference room: https://pbx.domain.com/PBX0/APPS/conference-en/webaccess.htm?m=AAACAAAAAQAAAAFkGDywZfsIAAAFZBg8sLQvbiwPEwkA9rYsUedNwqo

Note that from the base64-encoded result, some character needs to be replaced to be URL-compatible. Replace the '+' with a '-' and the '/' with a '_' .

Online converters that can be used:

* https://www.unixtimestamp.com/
* https://cryptii.com/pipes/md5-hash
* https://cryptii.com/pipes/binary-to-base64
* https://cryptii.com/pipes/base64-to-binary

Example implementation for innovaphone JavaScript Runtime can be found here:
https://github.com/innovaphone/confinvite

= Troubleshooting =
The same as for conference web access.

Reference13r3:Concept Conference Meeting Invitations

2023-05-26T13:46:57Z

Afi: /* Data Content */

[[Category:Concept_Conference]]


= Applies To =

* innovaphone PBX from version 13r3

= Overview =
Conference meeting invitations is a new feature of the [[Reference13r1:PBX/Objects/Conference | Conference Object]]. Meeting invitations are used to create temporary conference rooms.

= Requirements =
* CONF or SCNF interface with [[Howto:Conferences%2C_Resources_and_Licenses | appropriate channel licensing]]
* Conference App license (App(innovaphone-pbx-conference)13), necessary to create meeting links and invitations.
* If announcements should be played, announcement files must be available. The file names are listed [[Reference13r3:PBX/Objects/Conference/Announcement_types | here]].

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

In addition, two new options have been introduced:

;Web Access allowed: Needs to be enabled to use the temporary meeting links
;International Number: Needs to be set to add a phone number in the meeting invitations.

= Features =
The conference web access features are available.

* Dial-in with web access link
* Dial-in with a SIP uri.
* Dial-in with a number and an additional meeting id if this id is not used several times and the meeting room is created.

= Usage =
The conference doesn't save meeting links and so, it doesn't reserve any conference channel for them. The conference reserves channels if a meeting link is used and a meeting room is created.

== Creating Meetings ==
A meeting is defined by a meeting id, the start and end of the date and time and the number of participants. The number of participants specifies how many channels will be allocated for this meeting.

A meeting HTTP link and a SIP uri can be generated in the conference app by clicking the invitation button, ''create link'', which can be directly sent to participants via email. If the ''mail link'' button is used, a mail-to link is generated and opened, so the operation system opens an email client with a prefilled message subject and body.

In addition, a meeting can be scheduled. A calendar file (ICS) is created by clicking the ''open calendar'' button. It depends on the current browser configuration if the calendar file is saved to the client system or opened with a supported application.

The generated HTTP link can be used to take part in the meeting with a browser, the generated SIP uri can be used with a phone app, internal or with federation.

It is also possible to take part in the meeting with a dial-in number. The room number must be dialed followed by the meeting id with DTMF. This is possible not before someone else has used the HTTP link or the SIP uri.

== Joining Meetings ==
A meeting link can be used between one hour before the defined starting time and the defined end time, or if the meeting is being on.
If you call the meeting room one hour till five minutes before the meeting starts, a predefined announcement is played. No room is created and no conference channels are reserved at this time.

If you call or have a call to the meeting room five minutes or less before the meeting starts, a room is created, channels are reserved and the meeting room is listed in the conference app. The conference reserves as many channels as previously defined as number of participants. If not enough channels are available, the caller is announced and the call is disconnected.

== Moderating Meetings ==
All current meetings of a room can be listed in the corresponding conference room app. If a meeting is chosen, the participants of this meeting room are shown. A meeting room only appears five minutes before the meeting starts.

= Data Content =
The base64-encoded data of the HTTP link or SIP URI includes following content:

# the version number, currently 0, 1 byte (hex: 00)
# flags for optional content, currently 0, 1 byte (hex: 00)
# the room number length, 1 byte (e.g. 2 digits, hex: 02)
# the room number, 4 bytes (e.g. room number 1, hex: 00 00 00 01)
# meeting id, 4 bytes (random unique 6-digit id e.g. hex: 00 00 00 01)
# start timestamp, 4 bytes (e.g. 20-03-2023 12:00 unix-timestamp: 1679310000, hex: 64 18 3c b0)
# end timestamp, 4 bytes (e.g. 20-03-2024 17:00 unix-timestamp: 1710950400, hex: 65 fb 08 00)
# number of reserved channels, 2 bytes (e.g. 5, hex: 00 05)
# creation timestamp, not used for the hash calculation, 4 bytes (e.g. 20-03-2023 12:00 unix-timestamp: 1679310000, hex: 64 18 3c b0)
# MD5 hash, 16 bytes

Note that from the base64-encoded result, the '+' are replaced with '-' and the '/' with '_' afterward to be URL-compatible.
The MD5 hash is calculated with the content above from point 1 until 8, followed by the meeting password ("m-key") of the conference object configuration.

Example for the link creation:
* Bytes for MD5 hash calculation: 00 00 02 00000001 00000001 64183cb0 65fb0800 0005 4e5344534f537153 (m-key in hex)
* Calculated MD5 hash from string above: b42f6e2c0f130900f6b62c51e74dc2aa
* Data for the link hash value: 00 00 02 00000001 00000001 64183cb0 65fb0800 0005 64183cb0 b42f6e2c0f130900f6b62c51e74dc2aa
* Base64 encoded: AAACAAAAAQAAAAFkGDywZfsIAAAFZBg8sLQvbiwPEwkA9rYsUedNwqo=
* Link to the temporary conference room: https://pbx.domain.com/PBX0/APPS/conference-en/webaccess.htm?m=AAACAAAAAQAAAAFkGDywZfsIAAAFZBg8sLQvbiwPEwkA9rYsUedNwqo

= Troubleshooting =
The same as for conference web access.

Main Page

2023-05-02T09:11:40Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] ([[User talk:Afi|talk]]) 11:11, 2 May 2023 (CEST)
[[Support:Wireless_Handset_Firmware_IP73_1008_(4.0.2)_released | Wireless Handset Firmware IP73 1008 (4.0.2)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Smayoral|sma]] 10:29, 27 April 2023 (CEST)
[[Support:Firmware V13r3 product/13r3/firmware 137818 (sr 4) available | Version 13r3 Service Release 4]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Smayoral|sma]] 10:29, 27 April 2023 (CEST)
[[Support:Firmware V13r2 product/13r2/firmware 136416 (sr 22) available | Version 13r2 Service Release 22]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Smayoral|sma]] 10:29, 27 April 2023 (CEST)
[[Support:Firmware V12r2 product/12r2/firmware 125871 (sr 62) available | Version 12r2 Service Release 62]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Smayoral|sma]] 10:29, 27 April 2023 (CEST)
[[Support:Firmware V11r2 product/11r2/firmware 113809 (sr 66) available | Version 11r2 Service Release 66]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Cam|Cam]] 16:43, 25 April 2023 (CEST)
[[App Working Beta beta1 available]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] 15:38, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040621_(6.2.7)_released | Wireless Handset Firmware IP62 3040621 (6.2.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM_Software_3130113_%284.1.8%29_released | WinPDM Software 3130113 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Inno-mst|Inno-mst]] 17:40, 14 February 2022 (CET)
[[Support:Firmware V12r1 product/12r1/firmware 121355(sr 46) available | Version 12r1 Service Release 46]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

Howto:ComteloGROUPS - comteloGbR - Partner App

2023-03-02T12:12:33Z

Afi: New page:  <!-- to create a new entry here, - fill in all sections marked as "by vendor" - innovaphone will th...

[[Image:Logo-jpg.jpg||200px|right]]
[[Image:Comtelo-groups.jpg||200px|right]]

==Product Name==

[https://www.comtelo.com comtelo] GROUPS-App
==Certification Status==


{{Template:Compat Status "in progress"}}






<internal>
Zertifikatsvorlagen liegen unter \\inno-sifi\dfs\Techserv\Testlab
Beim Abschluss des Tests (egal ob gut, schlecht oder abgebrochen) bitte Nachricht an ptr!
 Bitte darauf achten, dass das Zertifizierungsdatum angegeben ist, also "Testing of this product has been finalized January 1st, 1970"
</internal>
==Category==

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

==Functions==

Short summary of the most important features:
*Display waiting queues and their members
*Display waiting queue status
*Display user status of members
*Display call forwarding
*Change your own waiting queue status
*Call and chat with members
[[Image:Comtelo-GROUPS-ov.png||quick start Guide]]

==Version==

comtelo GROUPS APP Build 1001 Beta1
===Compatible innovaphone firmware versions===

*comtelo GROUPS APP Build 1001 Beta1
** innovaphone V13r2
** innovaphone V13r3
===Application versions used for interop testing===
*comtelo GROUPS APP Build 1001 Beta1
** innovaphone IPVA V13r2sr19
** innovaphone IPVA V13r3sr1

==Configuration==

===Install app from App Store===
To get the steps done, log in to your PBX as admin.

'''Open "AP Manager"''':
After you have logged in to your PBX as admin, click on "AP Manager"

[[Image:comtelo_Ap_manager.png]]

'''Go to the "App Store"''':
Inside the "AP Manager", next we click on "App Store"

[[Image:comtelo_ap_Manager_button_App_Store.png]]

[[Image:comtelo_install_groups_app.png|800px|]]

[[Image:comtelo_bedingungen_groups_app.png|800px|]]

[[Image:Comtelo_add_groups_app.png|800px|]]

[[Image:Comtelo_add_instance_groups_app.png|800px|]]

'''Go to the "PBX Manager"''':

[[Image:Comtelo_start_groups_app.png|800px|]]

[[Image:Comtelo_pbx_manager_groups_app.png|800px|]]

=== User configuration ===

Give the desired users permission for the app.

Without further settings, users can now see all waiting queues in which they are members.

'''Via Visibility you can fade in and fade out the waiting queues.'''

[[Image:Comtelo_devices_objects_visibility_groups_app.png]]

'''In the example below, waiting queue "WQ_91" is visible and "WQ_EK" is not visible.'''

[[Image:Comtelo_devices_visibility_groups_app.png]]

==Vendor==
[http://www.comtelo.de www.comtelo.de ]
[[Image:Logo-jpg.jpg||200px||left]]

==Description==

comteloGROUPS brings structure to your call groups. If you want to work together efficiently, this app has many advantages. Thanks to the user-friendly interface, Waiting Queues are clearly summarized and provide information on the status of the groups and their participants.
What is the current availability of my group participants? Who is available or who has an appointment at the moment? Are there any people in my group who are available permanently?
These are just a few examples, of what the comteloGROUPS app makes visible. The practicality of the app is supplemented with additional functions, such as a direct call from the app or the chat button for short messages in between.
Take efficient collaboration to a new level with comteloGROUPS!

==Summary==









==Pricing==


==Contact==


{|
| colspan=99 | comtelo GbR | Dipl.-Ing. (FH) Torge Knop und Olaf Tomaski
|-
| colspan=99 | Berliner Allee 51
|-
| colspan=99 | 30855 Langenhagen
|-
| Tel: || +49 511 676 676 6-0
|-
| Fax: || +49 511 676 676 6-77
|-
| Mail: || [mailto:info@comtelo.de info@comtelo.de]
|-
| Support: || [https://comtelo.de/kontakt/#kontakt/ comtelo Team ]

|}

[[Category:Partner Apps]]

Main Page

2023-02-06T15:42:43Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] 15:38, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040621_(6.2.7)_released | Wireless Handset Firmware IP62 3040621 (6.2.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM_Software_3130113_%284.1.8%29_released | WinPDM Software 3130113 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 12:49, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP73_1006_(3.1.7)_released | Wireless Handset Firmware IP73 1006 (3.1.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r3 product/13r3/firmware 137766 (sr 1) available | Version 13r3 Service Release 1]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r2 product/13r2/firmware 136395 (sr 19) available | Version 13r2 Service Release 19]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r1 product/13r1/firmware 133139 (sr 45) available | Version 13r1 Service Release 45]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V12r2 product/12r2/firmware 125863 (sr 59) available | Version 12r2 Service Release 59]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V11r2 product/11r2/firmware 113806 (sr 65) available | Version 11r2 Service Release 65]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 17:40, 14 February 2022 (CET)
[[Support:Firmware V12r1 product/12r1/firmware 121355(sr 46) available | Version 12r1 Service Release 46]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

Main Page

2023-02-06T14:38:46Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] 15:38, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040621_(6.2.7)_released | Wireless Handset Firmware IP62 3040621 (6.2.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM_Software_3130112_%284.1.8%29_released | WinPDM Software 3130112 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 12:49, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP73_1006_(3.1.7)_released | Wireless Handset Firmware IP73 1006 (3.1.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r3 product/13r3/firmware 137766 (sr 1) available | Version 13r3 Service Release 1]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r2 product/13r2/firmware 136395 (sr 19) available | Version 13r2 Service Release 19]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r1 product/13r1/firmware 133139 (sr 45) available | Version 13r1 Service Release 45]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V12r2 product/12r2/firmware 125863 (sr 59) available | Version 12r2 Service Release 59]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V11r2 product/11r2/firmware 113806 (sr 65) available | Version 11r2 Service Release 65]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 17:40, 14 February 2022 (CET)
[[Support:Firmware V12r1 product/12r1/firmware 121355(sr 46) available | Version 12r1 Service Release 46]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

Main Page

2023-02-06T12:13:52Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM_Software_3130112_%284.1.8%29_released | WinPDM Software 3130112 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 12:49, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP73_1006_(3.1.7)_released | Wireless Handset Firmware IP73 1006 (3.1.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r3 product/13r3/firmware 137766 (sr 1) available | Version 13r3 Service Release 1]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r2 product/13r2/firmware 136395 (sr 19) available | Version 13r2 Service Release 19]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r1 product/13r1/firmware 133139 (sr 45) available | Version 13r1 Service Release 45]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V12r2 product/12r2/firmware 125863 (sr 59) available | Version 12r2 Service Release 59]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V11r2 product/11r2/firmware 113806 (sr 65) available | Version 11r2 Service Release 65]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 17:40, 14 February 2022 (CET)
[[Support:Firmware V12r1 product/12r1/firmware 121355(sr 46) available | Version 12r1 Service Release 46]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 17:38, 21 January 2021 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040620_(6.2.3)_released | Wireless Handset Firmware IP62 3040620 (6.2.3)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

Main Page

2023-02-06T11:49:26Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] 12:49, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP73_1006_(3.1.7)_released | Wireless Handset Firmware IP73 1006 (3.1.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r3 product/13r3/firmware 137766 (sr 1) available | Version 13r3 Service Release 1]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r2 product/13r2/firmware 136395 (sr 19) available | Version 13r2 Service Release 19]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V13r1 product/13r1/firmware 133139 (sr 45) available | Version 13r1 Service Release 45]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V12r2 product/12r2/firmware 125863 (sr 59) available | Version 12r2 Service Release 59]] is now available from the [http://store.innovaphone.com/release/download.htm download page].
[[User:Cam|Cam]] 16:39, 10 January 2023 (CET)
[[Support:Firmware V11r2 product/11r2/firmware 113806 (sr 65) available | Version 11r2 Service Release 65]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 17:40, 14 February 2022 (CET)
[[Support:Firmware V12r1 product/12r1/firmware 121355(sr 46) available | Version 12r1 Service Release 46]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 17:38, 21 January 2021 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040620_(6.2.3)_released | Wireless Handset Firmware IP62 3040620 (6.2.3)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 17:27, 21 January 2021 (CET)
[[Support:WinPDM_Software_3130111_%284.0.0%29_released | WinPDM Software 3130111 (4.0.0)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

Reference13r3:Concept OAuth2 Windows Authentication

2022-12-16T16:12:28Z

Afi: /* OpenID server */

[[Category:Concept|OAuth2 and myApps Windows Authentication]]
[[Category:Concept_OAuth2]]
[[Category:Concept_myApps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

Users can login-in to myApps using their windows password. The PBX uses OAuth2 with an OpenID configuration to verify the login information.

== Applies to ==
* innovaphone devices with a PBX from version 13r3
* innovaphone myApps (all platforms)

== How it works ==
=== Connection to the OpenID server ===
The OAuth2 service of the PBX retrieves the OpenID configuration from the configured OpenID server. 
This configuration is used to generate an authorization URL and to verify the login information which is retrieved after the login.

[[Image:MyApps OAuth2 flow config.png]]

=== Login with windows password in myApps ===
The login process using windows credentials:

* myApps starts the login and learns that OpenID is configured
* If the user selects OpenID for authentication, myApps opens the authorization URL of your OpenID server inside a popup window.
* after a successfull login with the windows credentials, the OpenID server redirects back to the '''Redirect URI''' of the PBX
* the redirect contains an id_token which itself contains the login information
* the signature of the id_token is verified against the OpenID configuration to ensure that the login is from the correct OpenID server
* the myApps login is completed

[[Image:MyApps OAuth2 flow login.png]]

;Shared secret:
OAuth2 doesn't offer a shared secret and the user's password is unknown by the PBX and myApps.
So we do an ECDHE key agreement to create a shared secret that is used for digest calculations and encryption of session parameters.

;Session credentials:
The PBX creates session credentials for future connections and stores them at the user object. After that it encrypts the credentials using the shared secret and sends them to the web application.

;Login:
For the initial login, the username from the id_token and the shared secret is used.
For subsequent connections, the session credentials are used.

Note: If the user is already logged-in at the OpenID provider, the redirect to the Redirect URL is done without asking for credentials and the login is completed automatically.

;Logout:
If the user actively logs out, the session credentials are deleted in the PBX and on the myApps client.
So for the next authentication, the login screen is displayed again.

Note: Logging out from myApps does not mean a logging out from the OpenID provider.

=== Characteristics ===
* The windows password is just used inside the OpenID authorization page. It is unknown by the PBX and the myApps client and it is never stored or transmitted over the network.
* During the login, a shared secret is negotiated using an ECDHE handshake. Session credentials are created and stored in the PBX at the user object and the DOM storage of the browser. So the user doesn't have to authenticate again, if the PBX or the browser is restarted.
* On logout the session credentials are deleted in the DOM Storage of the browser and in the PBX. So the next time the user is asked again for authentication.

== Requirements ==
=== OpenID server ===
We have developed and tested the functionality based on Microsoft Active Directory Federation Service (AD FS):
* Windows Server 2019 has been successfully tested
* Windows Server 2016 is currently being tested
* Windows Server 2012 is not supported

In principle, any server that meets the following conditions should work
* OpenID compliant server
* It has a well-known configuration URI, e.g. <code>https://adfs.domain.com/adfs/.well-known/openid-configuration</code>
* The OpenID configuration must deliver:
** Authorization endpoint
** JWKS URI
** support for id_token response type
** support for id_token signing algorithm RS256
** support for response mode form_post
** support for upn claim
** support for unique-name claim
** support for nonce claim
** at least one key which is used for token signing

However, as we have not carried out tests with other OpenID server variants, use with such servers is not supported.

=== PBX ===
* Firmware from version 13r3 or later.
* Working DNS configuration.
* The usernames (Name) of the user objects in the PBX must match the Windows usernames (samAccountName).
* OAuth2 authentication must be enabled on the PBX/Config/Authentication page in the advanced UI.

=== RP/Firewalls ===

* all communication is done via HTTPs
* RPs/Firewalls must allow access to the AD FS authorization URL (with can be retrieved by looking at the response of the openid configuration URL)
* RPs/Firewalls must allow access to the OAuth2 module on the PBX which is accessed by the myApps clients, e.g. <code>https://pbx.domain.com/OAUTH2/oauth2_login.htm</code>
* the PBX must be able to access the OpenID configuration URL

== Configuration ==
This just describes the configuration on a Windows 2019 server, but every OpenID server meeting the above mentioned requirements should be possible to use.

=== Activate AD FS server role ===
* make sure the AD FS server role is activated in your Windows Server

=== Server application with Client-ID ===
* open your AD FS management
* go to ''Application groups''
* add a new ''Application group''
* select ''Server application''
* give it a name of your choice and proceed
* note down the Client-ID
* add the Redirect URI of your PBX, e.g. <code>https://pbx.domain.com:443/OAUTH2/oauth2_login.htm</code>
** here you can also add multiple Redirect URIs for all your slaves and standbys too
* generate a secret key (this key isn't used inside the PBX, so you don't need to note it)

=== Token signature certificate ===
* open your AD FS management
* go to ''Service''
* go to ''Certificates''
* ensure you have a ''Token-signing'' certificate

There are also Powershell commands to add server applications etc., but they are out of scope of this article.

=== PBX ===
On all PBXes in the system:
* Configure the OAuth2 service on the innovaphone device on page [[{{NAMESPACE}}:Services/OAuth2/Config | Services/OAuth2/Config]].
* Activate OAuth2 authentication on page [[{{NAMESPACE}}:PBX/Config/Authentication | PBX/Config/Authentication ]]

== Usage ==
Depending on the configuration on page[[{{NAMESPACE}}:PBX/Config/Authentication | PBX/Config/Authentication ]] users can use their PBX user password, their Windows password or both for the myApps login.
;OAuth2 only: Shows a button redirecting to the OpenID provider.
;PBX only: Shows a login form with fields for username and password.
;PBX and OAuth2: Shows both and lets the user decide.

== Tracing and logging ==
The following trace flags can be activated at [[{{NAMESPACE}}:Maintenance/Diagnostics/Tracing | Maintenance/Diagnostics/Tracing]].

;OAuth2
: fetching the OpenID configuration
: processing of incoming id_tokens
: communication between the OAuth2 module and the PBX

;PBX: communication between the PBX and the myApps client

;HTTP Client
: the HTTPS communication for fetching the OpenID configuration

Additionally, you can enable the following trace flags at the myApps client.
;Browser Console
: login-flow and possible errors from the client perspective

== Alarms and Events ==
* an event is generated on every id_token which cannot be parsed or verified
* an alarm is generated if the Open ID configuration cannot be fetched or is invalid

== Test page ==

You can also use the test page at ''Services/OAuth2/Test''.

== id_token ==
The OpenID server redirects to the PBX after a successfull login. This redirect contains two form variables:
* id_token
* state: this is just echoed from the initial authorization URL to be able to link the login in myApps to the id_token

An id_token is a JSON Web Token in the following format:

base64url(JSON header).base64url(JSON payload).base64url(binary signature)

=== decoded header example ===
<code javascript>
{
"typ": "JWT",
"alg": "RS256",
"x5t": "VtIJQ2e2n7_Nmui0Bk7veW5IUPQ",
"kid": "VtIJQ2e2n7_Nmui0Bk7veW5IUPQ"
}
</code>

=== decoded payload example ===
<code javascript>
{
"aud": "8e4e2791-8583-4141-ce5b-a16f048758d9",
"iss": "https://adfs.domain.com/adfs",
"iat": 1663142781,
"nbf": 1663142781,
"exp": 1663146381,
"auth_time": 1663138217,
"nonce": "123456",
"sub": "wtj0QFR+Y2vsjTJXCclEZ4vtQKIEZKIOSpPRvxxLIxY=",
"upn": "username@domain.com",
"unique_name": "DOMAIN\\username",
"sid": "S-1-5-11-864245398-616249376-725345543-3105"
}
</code>

=== signature ===
The signature is binary. The signature is verified by calculating the SHA256 hash of "base64url(header).base64url(payload)" and generation of an RSA public key of the '''n''' and '''e''' properties of the OpenID key with the '''kid''' retrieved inside the header JSON. With this rsa key and the hash the binary signature is verified.

Reference13r3:PBX/Config/Authentication

2022-11-18T14:36:53Z

Afi:

[[Category:Concept_OAuth2]]
[[Category:Concept_myApps]]
The authentication for myApps and myPBX is configured on this page.

= Configuration =
== Authentication ==
* '''Two-factor authentication''' Requires users to additionally approve their logins using an existing session or by clicking a link sent via email. (myApps only)
* '''Authentication type''' (myApps and myPBX)
** '''PBX only''' Login is allowed with PBX user password only.
** '''Netlogon only''' Login is allowed with Windows password only.
** '''PBX and Netlogon''' Login is allowed with both PBX user password and Windows password.
** '''OAuth2 only''' Login is allowed with OpenID/OAuth2 only. (myApps only)
** '''PBX and OAuth2''' Login is allowed with both PBX user password and OpenId/OAuth2. (myApps only)
* '''OAuth2 provider name''' A user friendly name of the OAuth2 provider that shall be displayed on the login form, e.g. "Windows" or "Active Directory". (myApps only)
* '''OAuth2 domain''' This configuration is needed, if the OAuth2 user domain does not match the PBX domain. If a domain is configured, users of that domain will be treated like members of the PBX domain.
** Example: No domain configured. user@example.com -> user@example.com
** Example: example.com configured. user@example.com -> user

== Email verification ==
An email account that is used by the PBX for sending mails. It is used for:
* Sending verification emails for two-factor authentication.
* Emails from the voicemail object.
Configuration:
* '''SMTP server''' The IP address or DNS name of the SMTP server.
* '''Client host name''' The hostname or IP address for the EHLO message. Optional, defaulting to 127.0.0.1.
* '''Sender name''' A readable name that is used as the sender of the emails.
* '''Email address''' The email address for sending mails.
* '''Username''' The username of the email account.
* '''Password''' The password of the email account.
* '''Verification link''' The link that is used for accepting or rejecting sessions. Configure <code>https://PBX-IP-or-DNS-name/PBX0/session.xml</code>

* '''Test''' Here you can send a test mail using the configured account.
==Related Articles==
[[Reference13r3:Concept OAuth2 Windows Authentication]]

Howto:Callback - mediarunway - 3rd Party Product

2022-06-01T09:16:04Z

Afi: Howto:Callback - mediarunway - 3rd Party Product moved to Howto:Callback - MediaRunway - 3rd Party Product

#REDIRECT [[Howto:Callback - MediaRunway - 3rd Party Product]]

Howto:Callback - MediaRunway - Partner App

2022-06-01T09:16:04Z

Afi: Howto:Callback - mediarunway - 3rd Party Product moved to Howto:Callback - MediaRunway - 3rd Party Product

{{FIXME|reason=Work in progress, still incomplete}}

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

==Product Name==


MediaRunway Callback

==Certification Status==

{{Template:Compat_Status_referral_product_new}}


App not yet available in innovaphone-appstore

==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-callback.png]]



With Callback you have the possibility to organize your callbacks in this app instead of email, paper, etc. You can send callback requests or forward one of your callbacks to other licensed users. Tracking the status of a callback will help you gain the customer experience.



==Functions==



[[Image:Callback_main_2.png|977px]]

* Create, forward and edit callbacks according to your needs
** For yourself or other users
* Track which callbacks you have created and which you have forwarded
** Track a callbacks state or add additional information to a callback
* View your Callist and immediately create Callbacks from here
* Explore your history of callbacks
* Manage the backend of the app

[[Image:Callback_main_functions_1.png|1236px]]

[[Image:Callback_main_functions_2.png|903px]]







==Licensing==


Licensing: One license per user with any number of devices. No floating licensing, only the users who got a configured license have access. For licensing and test licensing please contact [mailto:myApps-sales@mediarunway.com myApps-sales@mediarunway.com].

* Example: "Hello MediaRunway, we would like to purchase the Callback app. Here is our authentication key 1113335557. A one year license for 10 users would fullfill our needs. Please send us the license key as fast as possible. Best reagards"

'''Enter license key and activate user license''': Simply enter the license key that you received from us and press "Confirm". After that, you should see the valid date of your license and the number of available user licenses. Next to the desired user name, activate or deactivate the user's license.

[[Image:Callback_admin.png|507px]]

==Prerequisites==


What you need is this Wiki article and a valid license. For a valid license please install the app and in the admin area of the app you will find the authentication key. Please send us this authentication key, together with the number of users and the desired license period to [mailto:myApps-sales@mediarunway.com myApps-sales@mediarunway.com].

Installation and configuration of the app will be described in the next sections.

==Versions==


* MediaRunway Callback 1.0

===Compatible innovaphone firmware versions===

* MediaRunway Callback 1.0
** innovaphone V13r2

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


* MediaRunway Callback 1.0

** innovaphone IPVA V13r2sr12
** innovaphone IPVA V13r2sr11
** innovaphone IPVA V13r2sr10

==Configuration==








===Configure Callback object rights===

Here we will describe all necessary configuration steps to get the app running. After successfully installing the app, adding the app instance, and the app objects (see next sections for a HowTo), we still need 1st to assign the necessary permissions to the app object and 2nd enter our license information and assign licenses to the users.

'''Open "Devices" app''': The app object must be assigned a few permissions in order for the app to work correctly.

[[Image:Callback_devices.png|173px]]

'''Navigate to the "PBX Objects" list''': The Callback app object must be assigned a few permissions in order for the app to work correctly. Do get that done, we will open the "PBX Objects" with the "Admin UI" interface of our "Devices" app.
* "Devices" App -> Devices Tab -> click your PBX -> click "Admin UI" -> click "PBX" Tab -> click "Objects" Tab

[[Image:Callback_devices_nav_object.png|1100px]]

'''Search for our "Callback" object''': Enter "callback" into the search mask and press "show". If pressing "show" without entering a text, you will get the hole list of objects from your PBX.

[[Image:Callback_devices_search_object.png|1175px]]

'''Open "Callback" object settings window''': Click on your "Callback" Object.

[[Image:Callback_devices_click_object.png|1179px]]

'''Open "App" tab in "Callback" object settings window''': Click on "App" tab.

[[Image:Callback_devices_objects_window.png|1255px]]

'''Set the rights for "Callback"''': Check mark as shown in the picture (Websocket, PbxSignal, TableUsers) and press "Apply" (more than once).

[[Image:Callback_devices_objects_set_rights.png|741px]]

'''Close "Callback" object settings window''': After pressing "Apply" you will see a "connected" next to the URL.

[[Image:Callback_devices_objects_confirm_rights.png|779px]]

===Enter licence key and activate user rights===

As mentioned in the "License" and "Prerequisites" section you need a license key and set the users rights in the "Callback Admin" app. Simply enter the license key that you received from us and press "Confirm". After that, you should see the valid date of your license and the number of available user licenses. Next to the desired user name, activate or deacvtivate the user's license.

[[Image:Callback_admin_set_key_and_user.png|779px]]

===Install app from App Store===
To get the steps done, log in to your PBX as admin.

'''Open "AP Manager"''':
After you have logged in to your PBX as admin, click on "AP Manager"

[[Image:Ap_manager.png|175px]]

'''Go to the "App Store"''':
Inside the "AP Manager", next we click on "App Store"

[[Image:Ap_app_store_button_mark.png|1246px]]

'''Select Callback App''':
In the list of apps, one will find the Callback App

[[Image:Callback_store_selection.png|886px]]

'''Select Callback Version''':
Usually, we always select the latest version of the app and after that press the "Install" button

[[Image:Callback_store_selection_mark.png|1246px]]

'''Confirm "Terms and Conditions"''':
Before installation starts, confirm the terms and conditions

[[Image:Callback_terms_conditions.png|1246px]]

'''Wait for installation to finish''':
Wait until installation has finished, and go back to main "AP Manager" view

[[Image:Callback_selection_installed.png|885px]]

===Add an app instance===
We have installed the app properly, now we will add an app instance.

'''Callback in "AP Manager"''':
In the list of "Installed apps" on the left side of the "AP Manager" manager, click on "Callback". Indicated by a "Play Sign" you can see that the app is installed and running.

[[Image:Callback_ap_app_installed.png|1228px]]

'''What is your domain?''': We see that our app is installed and runnning, but yet we have no instance of the app.
So in the next step we will add an app instance. To achieve this we need the Domain of your system which one can see for example in the "Contacts" app.

[[Image:Callback_contacts_system_domain.png|1223px]]

'''Add an instance''': Now we know the domain and can go back to Callbacks view, in the list of apps click again on Callback.
To add an app instance click the "Add" button, what will open the "Add instance" dialog

[[Image:Callback_install_instance_mark.png|1228px]]

'''Add instance dialog''': Inside the "Add instance" dialog, name your app instance "Callback", enter your domain and set the password for the app and the database user. The other input options will be filled automatically. We recommend to use different passwords here that you store inside your password management solution. After everything is filled up properly, press the "Save" button

[[Image:Callback_add_instance.png|728px]]

'''Mark added Callback instance''': After pressing the "Save" button, we can see in the Callbacks "AP Manager" view, that our app instance was added but is not yet running, indicated by a "Stop Sign". With a click on our freshly installed app instance we can mark it.

[[Image:Callback_highlight_installed.png|1224px]]

'''Start the app''': To start our app instance, click on "Start" next

[[Image:Callback_start_installed.png|1224px]]

'''App running''': Now you will see that your app instance is running, indicated by a "Play Sign"

[[Image:Callback_installed_startet.png|1225px]]

We have successfully added a Callback app instance.

Next, we create the user and admin object that will allow access to the Callback instance we just created and assign the necessary permissions.

===Add user object===
The user object is the interface between the user - PBX - and the app platform. For this purpose, we switch to the "PBX Manager".

'''Open "PBX Manager"''': Go back to your home screen and click on "PBX Manager"

[[Image:Callback_pbx_manager.png|174px]]

'''Go to app object area''': With a click on "AP Callback" the "Add an App" button will appear on the right screen, click on it

[[Image:Callback_user_object_mark.png|935px]]

'''Callback user object''': Now you can see "Callback" and "Callbackadmin", first we will add a "Callback" user object and after that we add a "Callbackadmin" admin object. The steps are the same, with different names for the object.

[[Image:Callback_user_object_add_mark.png|945px]]

'''Callback user object configuration''': For our Callback user object we need a unique name that will be "Callback", and a unique SIP "callback". We are adding a user object so we check mark "Config User"

[[Image:Callback_object_conf_mark.png|1100px]]

'''Confirm object configuration''': With a click on "OK" we confirm our settings

[[Image:Callback_user_object_save_mark.png|980px]]

'''Object connected''': Our Callback user object was added successfully

[[Image:Callback_user_object_success_mark.png|1165px]]

===Add admin object===
We need the "Callbackadmin" object too.

[[Image:Mediarunway-callbackadmin.png]]

'''Callback admin object''': Repeat steps from "Add user object" with the "Callbackadmin" object. For our Callbackadmin object we need a unique name that will be "Callback Admin", and a unique SIP "callback-admin". We are adding an admin object so we check mark "Config Admin" inside "Callbackadmin" object configuration.

[[Image:Callback_admin_object.png|1100px]]

'''Admin object connected''': After succesfully done, our "AP Callback" looks like this:

[[Image:Callback_admin_object_success_mark.png|917px]]

We have successfully added a "Callback" user object and a "Callbackadmin" object.

===After Installation===
After successful installation of the app, the app instance and the user and admin object, we have to perform some configuration steps. Please see the [https://wiki.innovaphone.com/index.php?title=Howto:Callback_-_mediarunway_-_3rd_Party_Product#Configuration Configuration] section in this article

==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]
|-
|Website: [https://www.mediarunway.com/ MediaRunway.com]
|}

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

Main Page

2022-05-11T16:42:43Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] 18:42, 11 May 2022 (CEST)
[[Support:Wireless_Handset_Firmware_IP73_1005_(3.1.6)_released | Wireless Handset Firmware IP73 1005 (3.1.6)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Teh|teh]] 07:40, 9 May 2022 (CEST)
[[Support:Firmware V13r2 product/13r2/firmware 136349 (sr 12) available | Version 13r2 Service Release 12]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Teh|teh]] 07:40, 9 May 2022 (CEST)
[[Support:Firmware V13r1 product/13r1/firmware 133114(sr 39) available | Version 13r1 Service Release 39]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Teh|teh]] 07:40, 9 May 2022 (CEST)
[[Support:Firmware V12r2 product/12r2/firmware 125850(sr 55) available | Version 12r2 Service Release 55]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Inno-mst|Inno-mst]] 17:40, 14 February 2022 (CET)
[[Support:Firmware V12r1 product/12r1/firmware 121355(sr 46) available | Version 12r1 Service Release 46]] is now available from the [https://store.innovaphone.com/release/download.htm download page].

[[User:Lmi|Lmi]] 12:34, 13 April 2022 (CEST)
[[Support:Firmware V11r2 product/11r2/firmware 113800 (sr 60) available | Version 11r2 Service Release 60]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 17:38, 21 January 2021 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040620_(6.2.3)_released | Wireless Handset Firmware IP62 3040620 (6.2.3)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 17:27, 21 January 2021 (CET)
[[Support:WinPDM_Software_3130111_%284.0.0%29_released | WinPDM Software 3130111 (4.0.0)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

ReleaseNotes13r1:Firmware

2022-05-11T09:02:20Z

Afi: Protected "Reference13r1:Release Notes Firmware" [edit=sysop:move=sysop]

This is the Firmware 13r1 Release Notes Document.

Service Releases are planned for the second monday each month. For each of the service release the complete set of tests is executed. If problems show up during the tests, the problems are fixed. This may cause a delay. The tests are started early, so that some delay is covered, but it still may happen that the patchday has to be moved. In this case it is hard to predict when the service release is good. It may be any day, so it would not be good to move the patchday by a fixed number of days, it still should be released as early as possible.

Please see ''[[Reference:What_are_the_Release_Notes_Documents?|the disclaimer]]'' before using the information presented here!

__NOEDITSECTION__
{{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=Firmware%2013r1}}

[[Category:Release Notes|Firmware]]

ReleaseNotes13r1:Firmware

2022-05-11T09:01:40Z

Afi: Protected "Reference13r1:Release Notes Firmware" [edit=autoconfirmed:move=autoconfirmed]

Main Page

2022-02-11T14:05:20Z

Afi: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Before you try to use this wiki ==
To get access '''[[Account_Creation|READ THIS FIRST]]''', make sure you [[Special:Userlogin|log in]] and have [[Account_Creation|your account authorized]].

You may then modify most of the articles and even add new ones. We hope for a rich and useful platform for professional innovaphone users to emerge this way.

To make sure you understand the terms of use, have a quick look at the [[innovaphone-wiki:About | legal stuff]]. But do not waste too much time there! Instead, rather browse through the information provided. There are various hopefully useful links in the sidebar on the left.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales-at-innovaphone-dot-com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==
[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP73_1004_(3.0.10)_released | Wireless Handset Firmware IP73 1004 (3.0.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 15:30, 17 January 2022 (CET)
[[Support:Firmware V12r2 product/12r2/firmware 125847 (sr 52) available | Version 12r2 Service Release 52]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Dde|Dde]] 15:30, 17 January 2022 (CET)
[[Support:Firmware V13r1 product/13r1/firmware 133100 (sr 35) available | Version 13r1 Service Release 35]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Dde|Dde]] 15:30, 17 January 2022 (CET)
[[Support:Firmware V13r2 product/13r2/firmware 136268 (sr 8) available | Version 13r2 Service Release 8]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Lbu|Lbu]] 17:03, 20 December 2021 (CET)
[[Support:Firmware V11r2 product/11r2/firmware 113796 (sr 58) available | Version 11r2 Service Release 58]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Inno-mst|Inno-mst]] 10:35, 18 February 2021 (CET)
[[Support:Operator9 90244 (hotfix23) available | Operator9 hotfix23]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 17:38, 21 January 2021 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040620_(6.2.3)_released | Wireless Handset Firmware IP62 3040620 (6.2.3)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 17:27, 21 January 2021 (CET)
[[Support:WinPDM_Software_3130111_%284.0.0%29_released | WinPDM Software 3130111 (4.0.0)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 17:04, 21 January 2021 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10311_(2.11.4)/IP65_10117_(2.11.4)_released | Wireless Handset Firmware IP64 10311 (2.11.4)/IP65 10117 (2.11.4)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 09 December 2020 (CEST)
[[Support:IQM_Build_8028700_available | IQM Build 8028700 Hotfix33]] is now available from the [http://download.innovaphone.com/ice/8.00/#iqm V8 download area].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==
{{Special:Newpages/8,namespace=Howto,namespace=Support,namespace=Reference,namespace=Reference7,namespace=Reference8}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">

== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>