<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.innovaphone.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Viktor.gruenauer</id>
	<title>innovaphone wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.innovaphone.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Viktor.gruenauer"/>
	<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Special:Contributions/Viktor.gruenauer"/>
	<updated>2026-11-22T12:54:44Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider&amp;diff=80784</id>
		<title>Reference8:TAPI Service Provider</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider&amp;diff=80784"/>
		<updated>2026-11-04T12:25:56Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Known Problems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The &#039;&#039;innovaphone PBX V8.0 based TAPI Service Provider&#039;&#039; (TSP) is an enhanced version of the [[ Reference7:Unified Win32 and x64 TAPI Service Provider | previous TSP version ]] that takes advantage of the [[ Reference8:SOAP API | new SOAP features ]] provided with version 8 PBX firmware. It implements - like the previous versions - TAPI Version 3.0 without MSP (Media Service Provider).&lt;br /&gt;
&lt;br /&gt;
The [[Reference7:Unified Win32 and x64 TAPI Service Provider| previous TSP ]] still must be used for V7 PBX systems. &lt;br /&gt;
&lt;br /&gt;
This article describes how to install and use it as well how to configure the PBX in order for the TSP to work properly.&lt;br /&gt;
&lt;br /&gt;
==Applies To==&lt;br /&gt;
This information applies to&lt;br /&gt;
* innovaphone PBX V8.0 based TAPI Service Provider, Build 8001 and later&lt;br /&gt;
* innovaphone PBX V8 and later (that is, this Service Provider runs with PBX Firmware V8 and later)&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Enhancements ===&lt;br /&gt;
; Support for V8 firmware [[Reference8:Administration/PBX/Objects#Devices | devices]] : Each user object device is represented as a TAPI line (all sharing an identical address, the objects extension a.k.a. &#039;&#039;Number&#039;&#039; property).  This now allows to select individual registration devices when multiple devices are registered with the same PBX.  Please note that in V8, [[ Reference8:Administration/PBX/Objects/Edit_Forks | mobility devices ]] are not shown and thus not represented by  TAPI line device.  This was introduced in V9 only.&lt;br /&gt;
; Support for presence based lines :  These are TAPI lines shown which reflect the users presence state.  Presence state &#039;&#039;open&#039;&#039; is mapped to a TAPI device status &#039;&#039;in service&#039;&#039;.  Presence activity &#039;&#039;on-the-phone&#039;&#039; is mapped to a virtual call in state &#039;&#039;connected&#039;&#039;.&lt;br /&gt;
: &#039;&#039;&#039;NB&#039;&#039;&#039;: V8 PBX Firmware did set presence activity &#039;&#039;on-the-phone&#039;&#039; for each user object having a call.  Unfortunately, as this does create performance issues, this behaviour has been removed from V9 PBX Firmware.  The &#039;&#039;presence line&#039;&#039; feature may be useless with V9 PBX when the application did rely on this particular V8 PBX behaviour.&lt;br /&gt;
&lt;br /&gt;
===System Requirements===&lt;br /&gt;
The TSP will install on any Windows 32bit and x64 platform down to Windows XP/Server 2003.  For older systems, you must use a deprecated [[Reference7:TAPI_Service_Provider | previous TSP version]].  For systems running PBX firmware version 6 or earlier, you must use the even older [[Reference:TAPI_Service_Provider | version 5 based TSP]].  Note that there is no x64 version of the version 5 TSP!&lt;br /&gt;
&lt;br /&gt;
The TSP needs to maintain parallel connections to each individual PBX in the system.  For larger systems (i.e. systems with a huge number of PBXs), this may create substantial load to the underlying windows machine.  The number of parallel activities scheduled by the TSP is thus limited as a function of the available main memory and number of processors.  In particular, a maximum of 20 activities per available processor is allowed (up to build 8088, the limit is 60/processor for later builds).  If this limit is exceeded, the TSP will issue performance warnings of class WARNINGS in the TSP log file and system TAPI performance will be poor.  Use a more capable machine then.&lt;br /&gt;
&lt;br /&gt;
Microsoft Windows operating system version for desktop clients (as opposed to server systems) limit the number and performance of TCP/IP connections.  This may lead to bad performance or occasional request failures.  We generally recommend to use server operating systems for 3rd party TAPI installations thus.&lt;br /&gt;
&lt;br /&gt;
No special PBX licenses are required to use the innovaphone TSP.&lt;br /&gt;
&lt;br /&gt;
=== Download === &lt;br /&gt;
The TSP will be available on the tab &#039;&#039;Software&#039;&#039; in the [https://store.innovaphone.com/ Store].&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Windows cannot run a Win32 TSP on an x64 platform (although it can run Win32 applications on such platforms).  This is why there are 2 versions of the setup, the x64 installer (&amp;lt;code&amp;gt;setup64-release.msi&amp;lt;/code&amp;gt;) and the Win32 installer (&amp;lt;code&amp;gt;setup32-release.msi&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;release&#039;&#039; setup packages provided will install the retail version.  This is recommended for production purposes but provides no debug options whatsoever.  To track down possible problems, support may instruct you to install the debug version.  &lt;br /&gt;
&lt;br /&gt;
The TSP may be installed on each machine where a desired TAPI based&lt;br /&gt;
application is to be run.  If for example, Outlook is to be used, then&lt;br /&gt;
each client PC running Outlook may have the TSP installed.  Although&lt;br /&gt;
this is typical for a 1st party configuration, all clients may have full&lt;br /&gt;
3rd party functionality, that is, they may control all existing lines.&lt;br /&gt;
&lt;br /&gt;
As an alternative, the TSP can be installed on a single machine and a&lt;br /&gt;
3rd party TAPI server product (such as the IXI-Call Server available as&lt;br /&gt;
a separate product) may be used to provide the network clients with a&lt;br /&gt;
TAPI interface.  Also, Microsoft’s Remote TAPI Server should work but is not being tested, so you use it on your own risk.&lt;br /&gt;
&lt;br /&gt;
To install, &lt;br /&gt;
* select and download the &amp;lt;code&amp;gt;setup32-release.msi&amp;lt;/code&amp;gt; install packages on 32bit platforms or the &amp;lt;code&amp;gt;setup64-release.msi&amp;lt;/code&amp;gt; install package on 64bit platforms.&lt;br /&gt;
* double-click the install package to launch the installer&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - zipcontent.png]]&lt;br /&gt;
* accept the license agreement&lt;br /&gt;
* select the target folder&lt;br /&gt;
* complete the installer&lt;br /&gt;
&lt;br /&gt;
When the installer has copied all files to the target machine, you need to add the TSP to the machine&#039;s TAPI system&lt;br /&gt;
* open the &#039;&#039;Telephone and Modem&#039;&#039; control panel&lt;br /&gt;
* Switch to the rightmost tab (&#039;&#039;Extras&#039;&#039;)&lt;br /&gt;
* Click on the &#039;&#039;Add...&#039;&#039; button&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - Control Panel Add.png]]&lt;br /&gt;
* Select the innovaphone TAPI provider driver&lt;br /&gt;
* Fill out the configuration dialogue&lt;br /&gt;
* Install the provider by clicking &#039;&#039;OK&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==== File Organization ====&lt;br /&gt;
Windows forces all TAPI service provider files to reside in Windows&#039; &#039;&#039;System Folder&#039;&#039;.  This is the &amp;lt;code&amp;gt;system32&amp;lt;/code&amp;gt; folder in your windows install directory (usually &amp;lt;code&amp;gt;C:\windows\system32&amp;lt;/code&amp;gt;), even if you are running an x64 platform!  The installer will thus copy these files (&amp;lt;code&amp;gt;tsp8.tsp&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;tsp8UI.dll&amp;lt;/code&amp;gt;) in to this directory.  All other files however will be copied to the &amp;lt;code&amp;gt;innovaphone AG\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt; folder underneath your systems &#039;&#039;Program Files Folder&#039;&#039;.  &lt;br /&gt;
&lt;br /&gt;
The subdirectories &amp;lt;code&amp;gt;Debug&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;Logs&amp;lt;/code&amp;gt; are created.  &amp;lt;code&amp;gt;Debug&amp;lt;/code&amp;gt; contains the driver&#039;s debug version, &amp;lt;code&amp;gt;Logs&amp;lt;/code&amp;gt; will receive the log files when a debug version is used.&lt;br /&gt;
&lt;br /&gt;
On x64 platform systems, the Win32 version of the configuration DLL (&amp;lt;code&amp;gt;tsp8UI.dll&amp;lt;/code&amp;gt;) will be installed to the windows &#039;&#039;Windows on Windows64 System Folder&#039;&#039; (&amp;lt;code&amp;gt;SysWOW64&amp;lt;/code&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
====Upgrading to a newer Version====&lt;br /&gt;
When you attempt to upgrade the TSP from a previous version, the Windows&lt;br /&gt;
installer will first remove any previous installation.  When the new&lt;br /&gt;
software is installed then, the TSP will be installed again into the&lt;br /&gt;
TAPI system.  &lt;br /&gt;
&lt;br /&gt;
There is no need to remove the driver from the &#039;&#039;Telephone and Modem Control Panel&#039;&#039;, as this would make you loose your driver configuration.&lt;br /&gt;
&lt;br /&gt;
====Upgrading from the old Win32-only Version====&lt;br /&gt;
If you upgrade from the older Win32-only versions of the TSP (soap-appl/tapi/7.00 or soap-appl/tapi/5.00), you must first remove the old TSP from &#039;&#039;telephone and modem&#039;&#039; control panel and uninstall the old product from the &#039;&#039;Software&#039;&#039; (or &#039;&#039;Programs and Functions&#039;&#039;) control panel.&lt;br /&gt;
&lt;br /&gt;
When you upgrade from the old V7 64-bit TSP (soap-appl/tapi/7.00-64), you should first update this older version to the latest build available.&lt;br /&gt;
&lt;br /&gt;
This procedure ensures that during the upgrade your TAPI lines retain their internal identifiers and thus their meaning in your TAPI application&#039;s configuration.&lt;br /&gt;
&lt;br /&gt;
==== Uninstalling the TSP ====&lt;br /&gt;
To uninstall the TSP proceed as follows&lt;br /&gt;
* Remove the TAPI driver from the TAPI system using &#039;&#039;Telephony and Modem Control Panel&#039;&#039;&lt;br /&gt;
* close &#039;&#039;Telephony and Modem Control Panel&#039;&#039;&lt;br /&gt;
* shut down windows telephony service. This can be done from the Windows &#039;&#039;Service Control Panel&#039;&#039; or by invoking &amp;lt;code&amp;gt;net stop tapisrv&amp;lt;/code&amp;gt; from a command prompt&lt;br /&gt;
* remove the installation using windows &#039;&#039;Programs Control Panel&#039;&#039; or by invoking the original .msi again&lt;br /&gt;
&lt;br /&gt;
You will notice that Windows may fail to remove the driver files from the &#039;&#039;Windows System Directory&#039;&#039;.  To clean up remove &amp;lt;code&amp;gt;tsp8.tsp&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;tsp8UI.dll&amp;lt;/code&amp;gt; from the &amp;lt;code&amp;gt;system32&amp;lt;/code&amp;gt; folder as well as - on x64 systems - from the &amp;lt;code&amp;gt;SysWOW64&amp;lt;/code&amp;gt; folder.&lt;br /&gt;
&lt;br /&gt;
Also, if you did file tracing, any remaining debug files in the &amp;lt;code&amp;gt;Logs&amp;lt;/code&amp;gt; folder are left over and need to be removed manually.&lt;br /&gt;
&lt;br /&gt;
The TSP will create some entries in the windows registry which will not be removed on uninstall.  It is recommended to leave these entries as is.  Only if you are sure you will never install the TSP again on this system or you are sure you will never use it with the PBX installation you used so far, you may want to delete them from the registry.&lt;br /&gt;
&lt;br /&gt;
==== Rolling out First Party TSPs to multiple PCs ====&lt;br /&gt;
Normally, when multiple users require CTI and hence TAPI functionality, the best way is to use a server based, multi-client 3rd party CTI application.  This will share all functions among all client PCs.  If this is not an option, e.g. because the TAPI application in use does not support it, you may want to consider using Microsoft&#039;s TAPI Server and remote TSP.  See Microsoft&#039;s [http://technet.microsoft.com/en-us/library/cc786297%28v=ws.10%29.aspx Telephony service providers overview] and [http://technet.microsoft.com/en-us/library/cc770373.aspx Manage Telephony Servers] documents.  &lt;br /&gt;
&lt;br /&gt;
If you still want to use the native innovaphone TSP on a number of PCs (instead of once on a server), you can roll out the TSP using some of the [http://support.microsoft.com/kb/816102/EN-US software deployment schemes Microsoft Server provide].  In such a case, you will likely want to deploy identical configurations to all these PCs. While this theoretically can be done by distributing registry settings, there will be a problem with the PBX access credentials.  These are stored in encrypted format in the registry and can only be decrypted on the PC on which they have been set.  That is, deploying such registry settings to other PCs will result in a non-functional setup.&lt;br /&gt;
&lt;br /&gt;
To work around this problem, you may store the credentials in clear text in the registry.  To do so, you would put the &#039;&#039;Password&#039;&#039; in a REG_SZ value named &amp;lt;code&amp;gt;admin1-free&amp;lt;/code&amp;gt; and the &#039;&#039;Account&#039;&#039; into a REG_SZ value named &amp;lt;code&amp;gt;admin2-free&amp;lt;/code&amp;gt;.  If such a value is found in the proper place in the registry, the values configured using the telephony control panel are ignored.  &lt;br /&gt;
&lt;br /&gt;
[[Image:TAPI Service Provider-tsp8-nocrypt.png]]&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;Keep in mind that having credentials in clear in the registry presents a security risk!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This feature is available in build 8079 and later.&lt;br /&gt;
&lt;br /&gt;
=== Upgrade from Build 8164 or earlier ===&lt;br /&gt;
From build 8165, the TAPI configuration has been moved to a different registry location.  This has been done because latest windows versions (namely, Windows 10) do not allow the TSP to access registry information in the location used so far (&amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;).   To work around this issue, it is now stored in &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The TSP configuration dialogue however runs with user privileges (as opposed to the TSP which runs with limited service privileges). It can therefore read the old configuration information and copy it to the new location.  From build 8165, the configuration dialogue will thus copy any old configuration information to the new location when it is opened.  When you upgrade an existing installation and open the configuration dialogue, you will see no change.  However, when the configuration is saved, it is then present in the new location.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;To upgrade an installation from build 8164 or earlier (that is TAPI &#039;V8 TAPI Service Provider (32 and 64bit) - hotfix14&#039;&#039; available in the &#039;&#039;V8 applications hotfix20&#039;&#039; package or earlier), proceed as follows:&#039;&#039;&#039;&lt;br /&gt;
* stop the telephony service (e.g. &amp;lt;code&amp;gt;net stop tapisrv&amp;lt;/code&amp;gt;)&lt;br /&gt;
* install the new TSP&lt;br /&gt;
* open the TSP configuration dialogue&lt;br /&gt;
* verify the configuration data&lt;br /&gt;
* save the configuration&lt;br /&gt;
* (re) start your TAPI application&lt;br /&gt;
&lt;br /&gt;
If you fail to migrate the configuration as described, the TSP will start, but not work!&lt;br /&gt;
&lt;br /&gt;
===Configuration===&lt;br /&gt;
The TSP configuration dialogue looks like this:&lt;br /&gt;
&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - Config UI.png]]&lt;br /&gt;
&lt;br /&gt;
* The &#039;&#039;VERIFY&#039;&#039; button will verify the configuration.  Note that the &#039;&#039;Username&#039;&#039; drop down list will only be populated after a successful verify. &lt;br /&gt;
* The &#039;&#039;OK&#039;&#039; button will save the configuration.&lt;br /&gt;
* The &#039;&#039;CANCEL&#039;&#039; button will quit the configuration without saving any changes.  If it is the initial configuration while you add the TSP via the telephone and modem control panel, the TSP will not be added &lt;br /&gt;
&lt;br /&gt;
TAPI talks to the PBX using [[Reference7:SOAP_API | SOAP ]] which in turn uses HTTP for communication.  Both secure (https) and non-secure (http) communication is supported.  In any case, HTTP basic authentication is used.  &lt;br /&gt;
To be able to connect to the PBX, the TSP needs to know proper credentials to use during HTTP authentication. These are referred to as &#039;&#039;PBX Account&#039;&#039; and &#039;&#039;PBX Password&#039;&#039;.  Also, a suitable &#039;&#039;TAPI User&#039;&#039; must be selected.&lt;br /&gt;
&lt;br /&gt;
==== Controlling the Line Devices handled by TAPI ====&lt;br /&gt;
&lt;br /&gt;
TAPI connects to your PBX as a PBX user referred to as &#039;&#039;TAPI User&#039;&#039;.  It will see all PBX objects that are members of groups in which the &#039;&#039;TAPI User&#039;&#039; is an active member.  If the &#039;&#039;TAPI User&#039;&#039; is not an active member in any group, TAPI will see the &#039;&#039;TAPI User&#039;&#039; object only. This may be useful in a [http://en.wikipedia.org/wiki/Telephony_Application_Programming_Interface 1st party TAPI scenario].  PBX objects are represented as TAPI lines.  &lt;br /&gt;
&lt;br /&gt;
The PBX object you use as &#039;&#039;TAPI User&#039;&#039; needs to have at least &#039;&#039;Viewing only&#039;&#039; [[Reference:Administration/PBX/Objects/Edit Rights | PBX user rights]].  Its &#039;&#039;Long Name&#039;&#039; property is used as &#039;&#039;TAPI User Username&#039;&#039;, its &#039;&#039;Name&#039;&#039; property as &#039;&#039;PBX Account&#039;&#039; and the password as &#039;&#039;PBX Password&#039;&#039;.  This is why the PBX object used as &#039;&#039;TAPI User&#039;&#039; must have a password configured. &lt;br /&gt;
&lt;br /&gt;
===== 1st Party Configuration =====&lt;br /&gt;
In a 1st party scenario, the TSP will only work on a single PBX object.  This will typically be a user&#039;s phone and thus the user itself will be used as the &#039;&#039;TAPI User&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - FirstParty.png ]]&lt;br /&gt;
&lt;br /&gt;
In such a configuration the TSP is typically installed on the users PC and the CTI software is accessing TAPI directly (such as e.g. Microsoft Outlook does).   &lt;br /&gt;
&lt;br /&gt;
The TSP configuration dialogue will check for the number of lines seen.  If it is only one, then it will issue a warning message:&lt;br /&gt;
&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - OnlyOne.png]]&lt;br /&gt;
&lt;br /&gt;
This is because 3rd party configurations are much more common and this situation often indicates a configuration problem.  In a first party configuration, you can safely ignore this message. &lt;br /&gt;
&lt;br /&gt;
===== 3rd Party Configuration =====&lt;br /&gt;
In a 3rd party configuration, the TSP will work with multiple PBX objects.  &lt;br /&gt;
&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - ThirdParty.png]]&lt;br /&gt;
&lt;br /&gt;
Typically, you will share a single TSP instance on a server system for use by several users on their desktop PCs.  This is done by virtue of a &#039;&#039;TAPI Server&#039;&#039;.  There are various TAPI server products available on the market, including but not limit to the Estos ProCall product and the remote TAPI server included in Microsoft Windows server operating systems.  &lt;br /&gt;
&lt;br /&gt;
In this scenario, it is recommended to create a pseudo PBX user object for use as the &#039;&#039;TAPI User&#039;&#039;.  This pseudo user is often called &amp;lt;code&amp;gt;_TAPI_&amp;lt;/code&amp;gt;.  You would create a dedicated group to control the list of PBX objects the TSP creates a line device for.  This group is often called &amp;lt;code&amp;gt;tapi&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==== Selective Call Forwards ====&lt;br /&gt;
Many CTI applications support distinct call forwards for internal and/or external calls.  The TSP will translate such requests to a call forward on the PBX which has the [[Reference7:Administration/PBX/Objects/Edit_CFs | &#039;&#039;Only&#039;&#039; or &#039;&#039;Only not&#039;&#039; property]] set to the number of the trunk line.  For this to work, it needs to know this number.  To know the number, the trunk line PBX object must be seen by the TSP (see above).  If this is not the case, the TSP configuration dialogue will issue a warning:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - NoTrunk.png]]&lt;br /&gt;
&lt;br /&gt;
In a vanilla first party scenario, this is obviously not the case.  If you don&#039;t care, you can safely ignore this issue.  Attempts to set such call forward will be rejected then as &#039;&#039;operation unavailable&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
In a Master/Slave PBX scenario where there is no Trunk Line object on the Master PBX, but only on the Slave PBXs, a workaround is required to suppress the warning and enable selective call forwarding on the Slave PBXs. In this case, create a dummy &amp;quot;Trunk Line&amp;quot; object on the Master PBX with the same extension number used by the &amp;quot;Trunk Line&amp;quot; objects on the Slave PBXs (usually 0).&lt;br /&gt;
&lt;br /&gt;
==== Multi Site Configuration ====&lt;br /&gt;
In a system with multiple PBXs, the TSP needs to connect to each of the individual PBXs.  &lt;br /&gt;
&lt;br /&gt;
[[Image:Unified Win32 and x64 TAPI Service Provider - MultiSite.png]]&lt;br /&gt;
&lt;br /&gt;
In this case, you would specify your master PBX as &#039;&#039;PBX Master&#039;&#039;.  There is no need to configure the complete PBX tree to the TSP as it is determined dynamically on runtime by analysing the PBX/Node objects in the master PBX and their registration status.  If a registered PBX is found, this PBX is added to the list of active PBXs and a new connection is established.  The PBX tree is built and maintained dynamically.  A reconfiguration or restart of the TSP is not required on changes thus.&lt;br /&gt;
For this to work&lt;br /&gt;
&lt;br /&gt;
* the PBX object used as &#039;&#039;TAPI User&#039;&#039; must exist in each PBX with same properties (including name and the password). You may want to use &amp;lt;code&amp;gt;_TAPI_&amp;lt;/code&amp;gt; as &#039;&#039;Name&#039;&#039;/&#039;&#039;Long Name&#039;&#039;.  This object must be &#039;&#039;active&#039;&#039; member in a group (which you may want to call &amp;lt;code&amp;gt;tapi&amp;lt;/code&amp;gt;).  A password must be set.  The object must have at least &#039;&#039;Viewing only&#039;&#039; rights&lt;br /&gt;
* the slave PBX-objects (or in older firmware versions the slave PBX Node-objects)  must be visible to the TSP (that is, must be non-active member of the group the &#039;&#039;TAPI User&#039;&#039; object is an active member of, e.g. &amp;lt;code&amp;gt;tapi&amp;lt;/code&amp;gt;) so that the slaves are made known to the TSP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In a replicated scenario, you would create a &#039;&#039;TAPI user&#039;&#039; as recommended above and [[Reference8:Administration/PBX/Objects#Objects_with_empty_node_or_PBX | leave the &#039;&#039;PBX&#039;&#039; and &#039;&#039;Node&#039;&#039; properties empty ]].  This user should then be used as both &#039;&#039;PBX Account&#039;&#039; and &#039;&#039;TAPI User Username&#039;&#039; in the TAPI configuration dialog.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Further relevant settings&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
You can disable slave detection by checking &#039;&#039;Do not monitor slaves&#039;&#039; property in the TSP configuration dialogue. &lt;br /&gt;
&lt;br /&gt;
TAPI maintains an &#039;&#039;address&#039;&#039; property per line device.  This usually is the lines extension.  In a multi site configuration, the address property will be set to the &#039;&#039;Number&#039;&#039; property of the node the respective PBX object is configured in, plus the &#039;&#039;Number&#039;&#039; property of the object itself.  So if an object has &#039;&#039;Number&#039;&#039; &amp;lt;code&amp;gt;42&amp;lt;/code&amp;gt; and lives in node &amp;lt;code&amp;gt;801&amp;lt;/code&amp;gt;, then its correspondence line device will have address &amp;lt;code&amp;gt;80142&amp;lt;/code&amp;gt;.  By checking the &#039;&#039;Use pure node extensions&#039;&#039; property in the TSP configuration dialogue, you change the algorithm so that only the objects own &#039;&#039;Number&#039;&#039; is used (&amp;lt;code&amp;gt;42&amp;lt;/code&amp;gt; in our example).&lt;br /&gt;
&lt;br /&gt;
==== Standby Configurations ====&lt;br /&gt;
In a system with standby PBX for the master PBX, you need to specify the &#039;&#039;PBX Standby&#039;&#039; IP address.  This will be connected if the master is unavailable.  Note that there is no need to explicitly configure slave-standby PBXs.&lt;br /&gt;
&lt;br /&gt;
==== Working with multiple, unrelated PBXs ====&lt;br /&gt;
When working with multiple, unrelated PBXs (that is, PBXs that do &#039;&#039;not&#039;&#039; form a PBX tree as slaves and masters do), the TSP cannot derive the list of PBXs to track from the registration status.  To support such a configuration, you will need to configure the extraneous master PBXs manually using regedit.  Please note that using regedit may harm your system and may even cause inability to boot!&lt;br /&gt;
&lt;br /&gt;
To find and edit the right registry entries, proceed as follows:&lt;br /&gt;
&lt;br /&gt;
* open the key &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt;&lt;br /&gt;
* open its subkey &amp;lt;code&amp;gt;Device&amp;lt;/code&amp;gt;&#039;&#039;n&#039;&#039; where &#039;&#039;n&#039;&#039; is the provider id of the installed innovaphone TSP (for builds before 8164 only)&lt;br /&gt;
* Open the &amp;lt;code&amp;gt;FQDN&amp;lt;/code&amp;gt; key and add all extra PBXs&lt;br /&gt;
* For those PBXs that have a standby PBX, add a value to the &amp;lt;code&amp;gt;StandbyFQDN&amp;lt;/code&amp;gt; key (please note: these are parallel lists.  So master and standby need to have the same respective index in the &amp;lt;code&amp;gt;FQDN&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;StandbyFQDN&amp;lt;/code&amp;gt; value lists)&lt;br /&gt;
&lt;br /&gt;
The standard configuration UI will not show these extra values.  However, it will also not touch them.  So even if you use the standard UI to edit, only the first value in the lists will be changed and the remainder left unchanged. You can thus safely use the standard UI to edit all other values.   As with multi site configurations, all PBXs need to be accessible using the same &#039;&#039;TAPI User&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Please note that this method is deprecated and will likely be removed from future versions of the TSP.  &lt;br /&gt;
&lt;br /&gt;
==== Setting the Line Device Name ====&lt;br /&gt;
The TSP will derive the line device&#039;s name from the properties of the respective PBX object.  By default the name will be the objects &#039;&#039;Long Name&#039;&#039; followed by the name of the PBX the user ought to register with in parentheses.  So if the users &#039;&#039;Long Name&#039;&#039; is &amp;lt;code&amp;gt;Foo Bar&amp;lt;/code&amp;gt; and the registration PBX is &amp;lt;code&amp;gt;branch1&amp;lt;/code&amp;gt;, the line device will be called &amp;lt;code&amp;gt;Foo Bar [branch1]&amp;lt;/code&amp;gt;.  You can specify a different pattern by changing the &#039;&#039;TAPI Line Names&#039;&#039; property of the TSP configuration dialogue.  The following replacement characters are available:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|+&lt;br /&gt;
| Meta || Replacement&lt;br /&gt;
|+&lt;br /&gt;
| %c || The objects &#039;&#039;Long Name&#039;&#039; (cn)&lt;br /&gt;
|+&lt;br /&gt;
| %C || The objects &#039;&#039;Long Name&#039;&#039; (cn) followed by the &#039;&#039;Name&#039;&#039; of the &#039;&#039;Device&#039;&#039; the line represents in braces &amp;lt;code&amp;gt;[name]&amp;lt;/code&amp;gt; if it differs from the &#039;&#039;Long Name&#039;&#039;&lt;br /&gt;
|+&lt;br /&gt;
| %d || The objects &#039;&#039;Display Name&#039;&#039; (dn)&lt;br /&gt;
|+&lt;br /&gt;
| %D || The objects &#039;&#039;Display Name&#039;&#039; (dn) followed by the &#039;&#039;Name&#039;&#039; of the &#039;&#039;Device&#039;&#039; the line represents in braces &amp;lt;code&amp;gt;[name]&amp;lt;/code&amp;gt; if it differs from the &#039;&#039;Display Name&#039;&#039;&lt;br /&gt;
|+&lt;br /&gt;
| %h || The objects &#039;&#039;Name&#039;&#039; (h323 alias)&lt;br /&gt;
|+&lt;br /&gt;
| %H || The objects &#039;&#039;Name&#039;&#039; (h323 alias) followed by the &#039;&#039;Name&#039;&#039; of the &#039;&#039;Device&#039;&#039; the line represents in braces &amp;lt;code&amp;gt;[name]&amp;lt;/code&amp;gt; if it differs from the &#039;&#039;Name&#039;&#039;&lt;br /&gt;
|+&lt;br /&gt;
| %t || The &#039;&#039;Name&#039;&#039; of the &#039;&#039;Device&#039;&#039; the line represents&lt;br /&gt;
|+&lt;br /&gt;
| %T || The &#039;&#039;Hardware Id&#039;&#039; of the &#039;&#039;Device&#039;&#039; the line represents (from build 8181)&lt;br /&gt;
|+&lt;br /&gt;
| %e || The objects extension (e164)&lt;br /&gt;
|+&lt;br /&gt;
| %E || The objects extension (e164) prefixed with the objects node number&lt;br /&gt;
|+&lt;br /&gt;
| %N || The line address as reported to TAPI&lt;br /&gt;
|+&lt;br /&gt;
| %n || host name (of master pbx)&lt;br /&gt;
|+&lt;br /&gt;
| %p || &#039;&#039;&#039;:&#039;&#039;&#039;&#039;&#039;port-number&#039;&#039; (of master pbx&#039;s http access, empty if 80)&lt;br /&gt;
|+&lt;br /&gt;
| %P || raw port number of master pbx&lt;br /&gt;
|+&lt;br /&gt;
| %u || url-like user name (&#039;&#039;&#039;&#039;&#039;user&#039;&#039;@&#039;&#039;host&#039;&#039;&#039;&#039;&#039;)&lt;br /&gt;
|+&lt;br /&gt;
| %U || user url as per draft-levin-iptel-h323-url-scheme-04 (&#039;&#039;&#039;h323:://&#039;&#039;user&#039;&#039;@&#039;&#039;host&#039;&#039;:&#039;&#039;port&#039;&#039;&#039;&#039;&#039;)&lt;br /&gt;
|+&lt;br /&gt;
| %X || the PBX name the user is registered with (note that using this pattern may result in a change of the name when a standby situation occurs)&lt;br /&gt;
|+&lt;br /&gt;
| %x || the PBX name the user is reported by (note that using this pattern may result in a change of the name when the users &#039;&#039;PBX&#039;&#039; attribute changes)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The default pattern is &amp;lt;code&amp;gt;%C (%x)&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- rufumleitung, extern, intern, amtsleitung, vom amt, zum amt --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous Flags ====&lt;br /&gt;
; Show full E164 Numbers : when set, the TSP will announce the full calling number from the root when indicated by the PBX in the TAPI &#039;&#039;calling party name&#039;&#039; attribute.  The number will be appended to the calling name with a &amp;lt;code&amp;gt;@&amp;lt;/code&amp;gt;.&lt;br /&gt;
; Do not show parked Calls : will hide parked calls from the TAPI application (as some get confused and don&#039;t know how to handle them)&lt;br /&gt;
; Map PBX Devices to Lines : if set, the TSP will create one TAPI line for each individual [[Reference9:PBX/Objects#Devices|PBX device]] configured in a user object.  See [[#Enhancements]] above.  If you do not set this flag, see [[Support:How should TAPI line device be registered?]]&lt;br /&gt;
; Map Presence Status to TAPI Lines : if set, the TSP will create one extra TAPI line for each PBX device object.  See [[#Enhancements]] above.&lt;br /&gt;
; No special Disconnect Behaviour : normally, lines monitored by TAPI will behave slightly different when a call is terminated.  With no TAPI on the line, the call will be disconnected immediately (from a PBX point of view).  In cases where the phone would play some tones after termination of the call (e.g. a busy tone when the call has never been connected to the far end), this state is simulated by the phone and not visible to TAPI.  Therefore, it is not possible to use TAPI functions on this call any more (as it in reality does not exist any more).  When this flag is set, monitored lines will not be treated specially.  Available from hotfix 6. To prevent the IP-Phone to play any tones after the call is disconnected, the phone preferences option &#039;&#039;&#039;Go onhook if final call is released by remote side even if handset is lifted&#039;&#039;&#039; can be activated. This is the feature of the IP-Phone is useful in a e.g. call center at agent phones and can be configured here [[Reference11r1:Phone/Preferences]].&lt;br /&gt;
: To prevent an innovaphone IP-Phone from playing any tones after a call is disconnected, the phone preferences option &#039;&#039;&#039;Go onhook if final call is released by remote side even if handset is lifted&#039;&#039;&#039; can be activated. This feature is useful for agent phones in a call center for example and can be configured in [[Reference11r1:Phone/Preferences]]&lt;br /&gt;
&lt;br /&gt;
===Trouble Shooting===&lt;br /&gt;
The TSP will (from build 8095) write messages of type INFO (&#039;&#039;informational messages&#039;&#039;) or WARNING (&#039;&#039;Warnings/Errors&#039;&#039;) to the windows event log. Such events are always logged to the application log and event source is the provider name (&#039;&#039;innovaphone® PBX V8 TAPI Service Provider&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
==== Turning on Debugging ====&lt;br /&gt;
There are 2 versions of the TSP, debug and retail, which are both copied to the machine during setup.  The retail version is installed into the system directories, whereas the debug version is stored in a separate directory.  This is available through a short cut in the Start menu.&lt;br /&gt;
&lt;br /&gt;
The TSP can produce a number of debugging messages which can be helpful to debug issues (in both &#039;&#039;retail&#039;&#039; and &#039;&#039;debug&#039;&#039; builds).  By default, debug messages are written to the systems debug buffer mechanism (using OutputDebugString()).  Such messages can be examined using standard debugging tools, such as for example &amp;lt;code&amp;gt;dbgview&amp;lt;/code&amp;gt; which is [http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx available from Microsoft]. &lt;br /&gt;
&lt;br /&gt;
Debug messages have a class associated with it and the amount of messages written can be controlled by enabling or disabling specific classes.  This is done by setting a bitmask in the registry value &amp;lt;code&amp;gt;TraceLevel&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt; key. &lt;br /&gt;
&lt;br /&gt;
The easiest way to set the TSP&#039;s debug level is with the &#039;&#039;TSP Control&#039;&#039; utility (&#039;&#039;tsptray.exe&#039;&#039;) which is installed with the TSP.&lt;br /&gt;
&lt;br /&gt;
The available classes include&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| Bit in &amp;lt;code&amp;gt;TraceLevel&amp;lt;/code&amp;gt; || Class &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000001 || Minimum tracing &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000002 || TAPI api traces &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000020 || Basic telephony object creation/destruction  &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000040 || Thread creation/destruction &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000080 || Request creation/destruction &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000100 || call related messages &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000200 || Call id map &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000400 || Warnings/Errors &lt;br /&gt;
|-&lt;br /&gt;
| 0x00000800 || Worker thread execution &lt;br /&gt;
|-&lt;br /&gt;
| 0x00001000 || Full lock/unlock notifications &lt;br /&gt;
|-&lt;br /&gt;
| 0x00002000 || Win32 Critical section create/destroy &lt;br /&gt;
|-&lt;br /&gt;
| 0x00004000 || Agent proxy support &lt;br /&gt;
|-&lt;br /&gt;
| 0x00008000 || constructor/destructor debug &lt;br /&gt;
|-&lt;br /&gt;
| 0x00010000 || development debugs &lt;br /&gt;
|-&lt;br /&gt;
| 0x00100000 || verbose debugging  &lt;br /&gt;
|-&lt;br /&gt;
| 0x00200000 || SOAP trace &lt;br /&gt;
|-&lt;br /&gt;
| 0x00400000 || SOAP message dumps &lt;br /&gt;
|-&lt;br /&gt;
| 0x01000000 || ATL debug &lt;br /&gt;
|-&lt;br /&gt;
| 0x02000000 || line related messages &lt;br /&gt;
|-&lt;br /&gt;
| 0x04000000 || informational messages &lt;br /&gt;
|-&lt;br /&gt;
| 0x10000000 || dump call infos &lt;br /&gt;
|-&lt;br /&gt;
| 0x20000000 || dump PBX infos &lt;br /&gt;
|-&lt;br /&gt;
| 0x80000000 || output log messages to file &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If &amp;lt;code&amp;gt;TraceLevel&amp;lt;/code&amp;gt; is not set, it defaults to (hex) &amp;lt;code&amp;gt;04000400&amp;lt;/code&amp;gt; in retail builds and to (hex) FFFFFFFF in debug builds.  A nice value to use is (hex) &amp;lt;code&amp;gt;92200580&amp;lt;/code&amp;gt;.  The &amp;lt;code&amp;gt;TraceLevel&amp;lt;/code&amp;gt; can be changed during runtime of the provider (it may take up to 10 seconds though for the setting to take effect).  In normal scenarios there is no need to install the debug version.&lt;br /&gt;
&lt;br /&gt;
Both &#039;&#039;informational messages&#039;&#039; and &#039;&#039;Warnings/Errors&#039;&#039; are always turned on (from build 8095).&lt;br /&gt;
&lt;br /&gt;
: A problem has been reported on Server 2008 x64 systems which may also apply to others.  On such systems, the value of &amp;lt;code&amp;gt;TraceLevel&amp;lt;/code&amp;gt; may be reset to its default every 10 seconds.  A workaround is to change the account the Telephony service is running in from its default (usually &#039;&#039;Network Service&#039;&#039;) to e.g. &#039;&#039;Local System&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===== Crash Dumps =====&lt;br /&gt;
From build 8063 the TSP will write crash dumps to the log directory (usually something like &amp;lt;code&amp;gt;C:\Program Files\innovaphone AG\innovaphone® PBX V8 TSP\Logs&amp;lt;/code&amp;gt;) in case of a trap.  In release installs, these are not very useful. For debug builds though, they include helfpul information.  Please provide these files (the can be zipped to a great extent) to support if requested. A crash dump file will be called something like &amp;lt;code&amp;gt;TSP8&amp;lt;i&amp;gt;build&amp;lt;/i&amp;gt;-&amp;lt;i&amp;gt;hour&amp;lt;/i&amp;gt;#&amp;lt;i&amp;gt;minute&amp;lt;/i&amp;gt;-&amp;lt;i&amp;gt;day&amp;lt;/i&amp;gt;.&amp;lt;i&amp;gt;month&amp;lt;/i&amp;gt;#&amp;lt;i&amp;gt;seqnr&amp;lt;/i&amp;gt;.dmp&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===== Forcing a Crash Dump =====&lt;br /&gt;
In rare cases, it may be useful to force a TAPI crash for debug reasons.  This can be done by issueing a &amp;lt;code&amp;gt;lineMakeCall&amp;lt;/code&amp;gt; with called number &amp;lt;code&amp;gt;0815&amp;lt;/code&amp;gt;, called-subaddress &amp;lt;code&amp;gt;4711&amp;lt;/code&amp;gt; and called-name &amp;lt;code&amp;gt;!crash!&amp;lt;/code&amp;gt; or simply calling &amp;lt;code&amp;gt;0815|4711^!crash!&amp;lt;/code&amp;gt; from phone.exe.&lt;br /&gt;
&lt;br /&gt;
==== Saving Log Messages to a File ====&lt;br /&gt;
The &amp;lt;code&amp;gt;0x80000000&amp;lt;/code&amp;gt; value is special, as it does not denote a message class.  Instead, it turns on log file writing, both in retail and debug versions.  For this to work, the registry value &amp;lt;code&amp;gt;DoTraceFile&amp;lt;/code&amp;gt; must be set to &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt; when the TSP starts.  If this value is not present, it defaults to &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; in both retail and debug builds.  Setting it to 0 disables log file writing regardless of any other setting.  This may save some CPU cycles for installations with a real large number of lines.&lt;br /&gt;
&lt;br /&gt;
The TSP will keep 24 log files (a days worth) by default.   This value can be changed using the &amp;lt;code&amp;gt;NumLogFiles&amp;lt;/code&amp;gt; value in &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt;.  Older log files will be removed.  Also, when the TSP shuts down, it by default will remove all log files it created so far.  However, any TSP will only remove log files created by itself.  This ensures that if the TSP or the system terminates prematurely, the log files will be kept even if a new instance is started and terminated later on.  Form TSP V8 hotfix 8 on, this behaviour can be tweaked by setting the DWORD registry value &amp;lt;code&amp;gt;KeepLogFiles&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt;:&lt;br /&gt;
{|&lt;br /&gt;
| 0 || default || remove all log files on termination&lt;br /&gt;
|-&lt;br /&gt;
| 1 || || keep the last &#039;&#039;n&#039;&#039; log files (depending on &amp;lt;code&amp;gt;NumLogFiles&amp;lt;/code&amp;gt;) on termination&lt;br /&gt;
|-&lt;br /&gt;
| 2 || || keep all log files&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Larger systems (500 monitored lines and more) can slow down considerably when writing extensive logs.&lt;br /&gt;
&lt;br /&gt;
==== Installing the Debug Version ====&lt;br /&gt;
To install the debug version, you first install the retail version as outlined above.  You then copy the debug driver files from the &amp;lt;code&amp;gt;Debug&amp;lt;/code&amp;gt; directory to your windows system directory &amp;lt;code&amp;gt;system32&amp;lt;/code&amp;gt;.  You may want to use the shortcut to the &amp;lt;code&amp;gt;Debug&amp;lt;/code&amp;gt; folder which has been installed to the start menu for convenience.  &lt;br /&gt;
&lt;br /&gt;
For the copy to work, proceed as follows&lt;br /&gt;
* close &#039;&#039;Telephony and Modem Control Panel&#039;&#039; if you have it open&lt;br /&gt;
* shut down windows telephony service. This can be done from the Windows &#039;&#039;Service Control Panel&#039;&#039; or by invoking &amp;lt;code&amp;gt;net stop tapisrv&amp;lt;/code&amp;gt; from a command prompt&lt;br /&gt;
* copy the debug driver files to your system directory.  On x64 systems, be sure to use a 64bit application such as &#039;&#039;Windows File Explorer for&#039;&#039; (&amp;lt;code&amp;gt;explorer.exe&amp;lt;/code&amp;gt;) for this.  Windows will silently redirect any 32bit application to the &amp;lt;code&amp;gt;SysWOW64&amp;lt;/code&amp;gt; directory when accessing &amp;lt;code&amp;gt;system32&amp;lt;/code&amp;gt;.(if the copying fails, we recommend to deactivate the telephony service. But don’t forget to reset it to automatically if you are done copying). Overwrite the existing files: &amp;lt;code&amp;gt;installer.dll, installer.pdb, TSP8.pdb, TSP8.tsp&amp;lt;/code&amp;gt;&lt;br /&gt;
* if the copy does not succeed or the debug driver is not shown n the modem control panel after, it might be that a TAPI application re-starts the windows telephony before you actually to the copy.  If so, you can set the &#039;&#039;Startup type&#039;&#039; of the Windows &#039;&#039;Telephony&#039;&#039; service to &amp;lt;code&amp;gt;Disabled&amp;lt;/code&amp;gt; instead of &#039;&#039;Manual&#039;&#039; in the services control panel (&#039;&#039;services.msc&#039;&#039;). You can then &#039;&#039;Stop&#039;&#039; the services, copy the file and finally set the services mode back to &amp;lt;code&amp;gt;Manual&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you open &#039;&#039;Telephony and Modem Control Panel&#039;&#039; again, you should notice that the TSP driver name has changed to the debug version.&lt;br /&gt;
&lt;br /&gt;
==== Switching back to the Retail Version ====&lt;br /&gt;
To go back from the debug to the release version, proceed as follows:&lt;br /&gt;
* close &#039;&#039;Telephony and Modem Control Panel&#039;&#039; if you have it open&lt;br /&gt;
* shut down windows telephony service. This can be done from the Windows &#039;&#039;Service Control Panel&#039;&#039; or by invoking &amp;lt;code&amp;gt;net stop tapisrv&amp;lt;/code&amp;gt; from a command prompt&lt;br /&gt;
* delete the debug driver files from your system directory.  On x64 systems, be sure to use a 64bit application such as &#039;&#039;Windows File Explorer for&#039;&#039; (&amp;lt;code&amp;gt;explorer.exe&amp;lt;/code&amp;gt;) for this.  Windows will silently redirect any 32bit application to the &amp;lt;code&amp;gt;SysWOW64&amp;lt;/code&amp;gt; directory when accessing &amp;lt;code&amp;gt;system32&amp;lt;/code&amp;gt;&lt;br /&gt;
* repair the installation using windows &#039;&#039;Programs Control Panel&#039;&#039; or by invoking the original .msi again&lt;br /&gt;
&lt;br /&gt;
There is no need to remove the driver from the &#039;&#039;Telephone and Modem Control Panel&#039;&#039;, as this would make you loose your driver configuration.&lt;br /&gt;
&lt;br /&gt;
Please note that simply re-installing the driver from the original .msi without removing it from the system directory will not work.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===References===&lt;br /&gt;
The test applications provided with this setup comes from [http://www.julmar.com Julmar Technology Inc].&lt;br /&gt;
&lt;br /&gt;
=== Limitations ===&lt;br /&gt;
&lt;br /&gt;
Please note that there currently is a limitation to 2000 users being in&lt;br /&gt;
all active groups of a particular user.  Thus, you cannot configure more&lt;br /&gt;
than 2000 users to be handled by TAPI on a single PBX.  This is a PBX&lt;br /&gt;
limitation (and applies for all PBX groups).&lt;br /&gt;
&lt;br /&gt;
TAPI has a flat line model.  That is, all line numbers (aka&lt;br /&gt;
&#039;&#039;extensions&#039;&#039;) are considered to live in a single name space.  As a&lt;br /&gt;
result, lines with identical numbers cannot be distinguished in TAPI&lt;br /&gt;
(although they can exist).   All extensions in all nodes of a PBX&lt;br /&gt;
numbering tree are represented as TAPI lines.  When the TSP works with a&lt;br /&gt;
PBX that implements a hierarchical numbering tree, then some lines may&lt;br /&gt;
receive identical numbers (their node-local extension which may overlap&lt;br /&gt;
between nodes depending on the setting of the &#039;&#039;Use pure node extensions&#039;&#039; property).  When a TAPI application uses these numbers to initiate&lt;br /&gt;
calls to such lines, the call will work or not work depending on the&lt;br /&gt;
calling lines position in the numbering tree (that is, lines within the&lt;br /&gt;
same node as the called line will be fine, others may fail).&lt;br /&gt;
&lt;br /&gt;
The PBX&#039;s SOAP interface (on top of which the TSP is built) has no primitives to initiate a directed call pick-up based on a target number.  The TSP will reject such requests with &#039;&#039;Operation not available&#039;&#039;.  Pickup by name (which is understood as a group name) or unspecific is supported though.&lt;br /&gt;
&lt;br /&gt;
==== Citrix Environments ====&lt;br /&gt;
What happens is that all Citrix sessions share the same TAPI driver. This allows all users in the Citrix sessions to select &amp;quot;their&amp;quot; line from the set of all TAPI lines. Then everything works as desired. It is important to note that theoretically one user can select the line of another user.&lt;br /&gt;
You can use the &amp;quot;Microsoft Remote TAPI Server&amp;quot;, to implement access rights for lines for separate Citrix sessions.&lt;br /&gt;
&lt;br /&gt;
===Known Problems===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* The TSP is not tested with Microsoft’s Remote Tapi Server.  While some installation have reported this to work fine, others have encountered problems.  This scenario is not supported by innovaphone&lt;br /&gt;
* The TSP will read its configuration when it is loaded by the system.  Thus, configuration changes require a re-load of the TSP.  Unfortunately, there is no reliable way to force the system to unload the TSP, so you may have to reboot the system for changes to take effect.  See the [[ Howto:Troubleshooting_the_TAPI_service_provider | TAPI trouble shooting article ]] for details&lt;br /&gt;
* The TSP will use HTTP basic authentication to talk the PBX.  So if you disable basic authentication in the PBX&#039;s configuration, the TSP will not work.  It is recommended to use HTTPS&lt;br /&gt;
* TAPI requires the TSP to assign a unique id to each line device.  This ID must not change between re-boots of the system or between upgrades of the TSP.  This is done by keeping a persistent table in the windows registry (in the &amp;lt;code&amp;gt;lineGUIDs&amp;lt;/code&amp;gt; subkey of &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt;) that maps the PBX&#039;s line GUID to a fixed integer value (known as &#039;&#039;permanent line id&#039;&#039; in TAPI speak).  This key is retained even on uninstall.  To get rid of it, you must remove it manually&lt;br /&gt;
* Microsoft installer fails to remove driver files installed to the windows system folder.  This is why the TSP driver files are still present after an uninstall of the software.  To get rid of them, remove &amp;lt;code&amp;gt;TSP8.tsp&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;TSP8UI.dll&amp;lt;/code&amp;gt; from both &#039;&#039;%windir%&#039;&#039;&amp;lt;code&amp;gt;\system32&amp;lt;/code&amp;gt; and &#039;&#039;%windir%&#039;&#039;&amp;lt;code&amp;gt;\sysWOW64&amp;lt;/code&amp;gt;&lt;br /&gt;
* From Version 9, hotfix 1, the PBX firmware will not list objects tagged as [[Reference9:PBX/Objects#General_Object_Properties | &#039;&#039;hide from LDAP&#039;&#039; ]] in the result of a [[Reference9:Concept_SOAP_API#UserInfo.5B.5D_FindUser.28string_v501.2C_string_v700.2C_string_v800.2C_string_cn.2C_string_h323.2C_string_e164.2C_integer_count.2C_integer_next.29 | FindUser() ]] call.  As a result, such objects will not be shown in the TAPI configuration dialogue &#039;&#039;Username&#039;&#039; drop-down.  If you want to use such an object as &#039;&#039;TAPI User&#039;&#039; you can simply type in the name without selecting it from the drop down.&lt;br /&gt;
* Sometimes, setting configuration with &#039;&#039;TSP Control&#039;&#039; (not the telephone control panel dialogue) does not work due to windows&#039; &#039;&#039;User Access Control (UAC)&#039;&#039;, see [[Howto:TAPI_TSP_Control_Windows7]] for Details&lt;br /&gt;
* Various users have reported that first party TSP installations do not work reliably with Microsoft Outlook.  Symptoms reported are spurious error pop-ups from Outlook although there was no real problem.  We do not recommend first party installations anyway (see [[#Rolling_out_First_Party_TSPs_to_multiple_PCs]] for a reasoning), but these issues are related to Microsoft Outlook only.  No such problems have been reported with other first party TAPI applications. Consider using solutions like Estos ProCall instead.&lt;br /&gt;
* The number of parallel threads used within the TSP is limited to max. 60 per CPU.  As each connected PBX (amongst other things) is handled by a separate thread, if you have a large number of PBXs connected and only have a single CPU, you may run out of threads, resulting in a WARNING messages &#039;&#039;about to spawn new workerthread (n requests, m threads) -- but limit l exceeded&#039;&#039;.  This usually happens when you run the TSP on a virtualized platform such as vmWare and only dedicate a single CPU.  Ignoring this warning results in sluggish behaviour.  &lt;br /&gt;
* The TSP can work with dynamic PBXs too.  However, the TSP needs to determine the slave PBXs IP addresses from the master. If the slave is a dynamic PBX and it is hosted on the same device as the master and it is registered to the master using 127.0.0.1, the TSP will only learn the 127.0.0.1 as the slave&#039;s IP address.  Of course, connection to the slave PBX will fail then. &lt;br /&gt;
*The option System Wide Groups under PBX/Config/General is not compatible with the TSP. If it is enabled, LineMakeCall() may be sent to the wrong PBX. Do not enable this option in installations that use TAPI.&lt;br /&gt;
==== TAPI Operation with 3rd party Phones or innovaphone Phones registered with SIP ====&lt;br /&gt;
Various TAPI functions rely on use of the [[Reference:Remote Control Facility|Remote Control Facility]] message.  This message is not supported in 3rd party phones and also not fully supported in innovaphone Phones when they are registered to the PBX using SIP.  Full TAPI functionality is thus only available for innovaphone phones registered to the PBX using H.323.&lt;br /&gt;
&lt;br /&gt;
Known Limitations:&lt;br /&gt;
* Accepting an incoming call (lineAnswer)&lt;br /&gt;
* Automatic initiation of an outgoing call in handsfree mode (instead, the calling phone first rings and starts the outgoing call upon of-hook)&lt;br /&gt;
* toggle between 2 calls active on a phone (lineSwapHold)&lt;br /&gt;
* initiation and termination of a 3PTY (lineCompleteTransfer with mode LINETRANSFERMODE_CONFERENCE, lineDrop on a conference call)&lt;br /&gt;
&lt;br /&gt;
==== TAPI on Windows8 / Server 2012 ====&lt;br /&gt;
&lt;br /&gt;
Windows8 doesn&#039;t let you disable &#039;&#039;User Access Control&#039;&#039; (UAC) completely.  This has the disadvantage that &#039;&#039;TSP Control&#039;&#039; (tsptray.exe) cannot change system registry entries, which it needs to do to e.g. change debug settings for the TSP.&lt;br /&gt;
&lt;br /&gt;
There are 2 ways around it: &lt;br /&gt;
# use the hidden &#039;&#039;Administrator&#039;&#039; account on Windows 8&lt;br /&gt;
# elevate the tsptray.exe application&lt;br /&gt;
&lt;br /&gt;
To use the elevated &#039;&#039;Administrator&#039;&#039; account on Windows 8 you first need to un-hide it:&lt;br /&gt;
* log in to an account with administrator rights  &lt;br /&gt;
* use the &#039;&#039;Windows-Key+X&#039;&#039; shortcut and select &#039;&#039;Command Prompt (Administrator)&#039;&#039; (&#039;&#039;Eingabeaufforderung (Administrator)&#039;&#039;). An elevated cmd prompt appears&lt;br /&gt;
* type &amp;lt;code&amp;gt;net user administrator /active:yes&amp;lt;/code&amp;gt;&lt;br /&gt;
* the fully elevated &#039;&#039;Administrator&#039;&#039; account is now available and you can log-in to this account as usual&lt;br /&gt;
* &#039;&#039;&#039;Please make sure the account has a password set - by default, it does not!!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
To elevate the tsptray.exe application;&lt;br /&gt;
* log in to an account with administrator rights  &lt;br /&gt;
* start a windows explorer&lt;br /&gt;
* change directory to &amp;lt;code&amp;gt;C:\Program Files\innovaphone AG\innovaphone® PBX V8-x64 TSP&amp;lt;/code&amp;gt;&lt;br /&gt;
* right click on &amp;lt;code&amp;gt;tsptray.exe&amp;lt;/code&amp;gt; and open the &#039;&#039;properties&#039;&#039; (&#039;&#039;Eigenschaften&#039;&#039;) menu&lt;br /&gt;
* switch to the &#039;&#039;Compatibility&#039;&#039; (&#039;&#039;Kompatibilität&#039;&#039;) tab&lt;br /&gt;
* tick the &#039;&#039;Run as administrator&#039;&#039; (&#039;&#039;Program als Administrator ausführen&#039;&#039;) check mark&lt;br /&gt;
* save the settings&lt;br /&gt;
&lt;br /&gt;
Please note that Windows 8 will not let you run any &amp;quot;Metro App&amp;quot; in elevated mode!&lt;br /&gt;
&lt;br /&gt;
===== HTTPS ===== &lt;br /&gt;
The TSP will not be able to talk to the PBX using HTTPS with Windows8 or Server2012.  This [[ReleaseNotes8:TAPI#3722_-_HTTPS_SOAP_connections_did_not_work_on_Windows8_.2F_Server_2012|has been fixed]] with V8 TAPI Service Provider (32 and 64bit) - hotfix10.&lt;br /&gt;
===== .Net 3.5 missing on Server 2012 =====&lt;br /&gt;
Server 2012 has no support for .Net 3.5 by default.  Even more, it cannot be installed just by downloading it.  Instead, the &#039;&#039;NetFX3 Feature&#039;&#039; needs to be enabled.  Here is how:&lt;br /&gt;
&lt;br /&gt;
 Microsoft Windows [Version 6.2.9200]&lt;br /&gt;
 (c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.&lt;br /&gt;
 &lt;br /&gt;
 C:\Users\Administrator&amp;gt;dism /online /enable-feature /featurename:NetFX3 /all /Source:&#039;&#039;&amp;lt;path to windows setup, e.g. d:&amp;gt;&#039;&#039;\sources\sxs /LimitAccess&lt;br /&gt;
&lt;br /&gt;
See also&lt;br /&gt;
* [http://blogs.technet.com/b/aviraj/archive/2012/08/04/windows-8-enable-net-framework-3-5-includes-net-2-0-and-3-0-i-e-netfx3-feature-in-online-amp-offline-mode.aspx?PageIndex=2 Windows 8: Enable .NET Framework 3.5]&lt;br /&gt;
* [http://msdn.microsoft.com/en-us/library/hh506443.aspx Installing the .NET Framework 3.5 on Windows 8]&lt;br /&gt;
&lt;br /&gt;
==== TAPI dialer fails from Outlook when Lync client was/is installed ====&lt;br /&gt;
We have received reports that 1st-party TAPI dial-out from Outlook does not work anymore when a Lync client was installed.  Some users report that this phenomenon occurred only after an upgrade to Windows 8.  Reportedly, this can be [http://support.microsoft.com/kb/959625/en-us fixed by setting a registry key as outlined in Microsoft&#039;s knowledge-base].  You may want to give this a try.  However, we have not seen this issue ourselves and thus can&#039;t comment on it further.&lt;br /&gt;
&lt;br /&gt;
==== Slow Network Performance ====&lt;br /&gt;
TAPI is pretty sensitive to slow network performance.  While the TSP is multi-threaded, some internal locking must be done so that slow requests to a PBX my block other pending requests, resulting in unpleasant performance.  The TSP will create &#039;&#039;Windows Event Log&#039;&#039; entries of type &#039;&#039;slow SOAP call performance&#039;&#039; if this is detected.  You should inspect your event log regularly and resolve the reason for such network performance.&lt;br /&gt;
&lt;br /&gt;
Long PBX request round-trips may have a number of reasons:&lt;br /&gt;
&lt;br /&gt;
; slow WAN performance : of course, if the WAN is slow or unstable, bad performance is the result&lt;br /&gt;
; inappropriate QoS : SOAP is using HTTP/HTTPS.  In a QoS enabled network, call signalling and RTP may work fine, whereas HTTP/HTTPS is considered to be of no importance.  You need to keep in mind that such QoS policy may lead to bad TAPI performance, as the SOAP traffic used by the TSP (being based on HTTP/HTTPS) may be delayed.  You should assign SOAP traffic a similar priority as you do for VoIP signalling&lt;br /&gt;
; overloaded PBX : HTTP traffic is treated on a low priority level in the PBX.  If the PBX runs near to 100% CPU load, while all RTP and VoIP signalling will work well still, HTTP traffic may get severely delayed.  You should make sure your PBX runs well under 100% CPU load to get good TAPI performance.  See [[Reference:Device Health Check]] for more details&lt;br /&gt;
&lt;br /&gt;
==== TAPI on Windows 10 ====&lt;br /&gt;
In Windows 10, the TSP is not allowed any longer to read/write its own registry tree.  For this reason, it is not possible to store or read the configuration.  As a result, the TSP will not work.  To fix this, you need to modify the registry access rights so that the TSP has read/write access to &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note on windows registry paths&amp;lt;ref name=&amp;quot;regkey&amp;quot;&amp;gt;&lt;br /&gt;
Due to a change in &#039;&#039;Windows Registry Access Rights&#039;&#039; in Windows 10, from Build 8165, the configuration is stored in &lt;br /&gt;
: &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&lt;br /&gt;
(a place that is suitable for Windows 10 too). Before, the configuration was stored in &lt;br /&gt;
: &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
See [[#Upgrade_from_Build_8164_or_earlier| Upgrade from Build 8164 or_earlier ]] above for more details.&lt;br /&gt;
&amp;lt;/ref&amp;gt;:&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tweaks ===&lt;br /&gt;
There are a few configuration options which should be used rarely.  They can be enabled by setting an appropriate registry key.&lt;br /&gt;
&lt;br /&gt;
Since Hotfix 15 the location to set the interop tweaks has been changed to &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
; ProcessorMask : REG_DWORD. If set, the TSP will use &amp;lt;code&amp;gt;SetProcessAffinityMask(GetCurrentProcess(), set)&amp;lt;/code&amp;gt; to limit TSP execution to one or more of the existing processors.  Set to &amp;lt;code&amp;gt;0xff&amp;lt;/code&amp;gt; by default.&lt;br /&gt;
&lt;br /&gt;
; LineTimeOut : REG_DWORD. Can be set to a number of seconds the TSP should wait for the determination of lines to finish (default 90). On a large PBX, or a PBX with slow slaves, the determination might not finish in the default time frame.  If this happens, TAPI applications may show &#039;&#039;Line unnamed&#039;&#039; line entries in their line list.  If this is a problem, set it to a larger value (e.g. &amp;lt;code&amp;gt;120&amp;lt;/code&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
; IgnoreDevStatus : REG_DWORD. Some applications get confused if TAPI reports line to be disconnected or out-of-service dynamically.  Setting this to a non-zero value will disable any such notification.&lt;br /&gt;
&lt;br /&gt;
; ClearFwdOnSet : REG_DWORD.  If set to a non-zero value, the TSP will clear all current call forward settings before a lineForward request is executed.  This implies that all call forward settings are &#039;&#039;replaced&#039;&#039; by the new settings.  Standard behaviour is to only modify the settings, that is, replace all current settings of the same type with the settings found in the lineForward request (for example, if there is only one setting in the request that defines a CFU, then the current CFU settings are replaced by the new one provided. All others, such as e.g. CFNR settings, are left untouched).&lt;br /&gt;
&lt;br /&gt;
: Tapi spec is pretty clear on how this should work: &#039;&#039;The provider should &amp;quot;unforward everything&amp;quot; prior to setting the new forwarding instructions&#039;&#039;.  Even though, for historical reasons, ClearFwdOnSet=0 has been the default in all TAPI versions prior to V8 hotfix 6, from hotfix 6 on, the default changes to 1, as this has turned out to be the widely accepted interpretation.&lt;br /&gt;
&lt;br /&gt;
; No3PTY : REG_DWORD. See [[Reference8:TAPI_Service_Provider#Notes_on_3PTY_Conferences | Notes_on_3PTY_Conferences]] below.&lt;br /&gt;
&lt;br /&gt;
; HiddenRecordingNumber: REG_SZ. Active recording in an innovaphone PBX is implemented as an implicit 3PTY conference with the recording sink as one of the parties.  These will be shown as usual in the TAPI callstate.  However, some applications get confused as this results in a situation, where a normal endpoint (read: phone) has more than one active (i.e. &#039;&#039;not on hold&#039;&#039;) call.  To suppress such calls in the TAPI call states, you can set this tweak to the number of the recording sink as configured in the phone&#039;s recording configuration tab.  If so, any outgoing call from an endpoint that is registered with a PBX user object with a called number that equals the setting of this tweak, will be suppressed.  So if your recording sink has the number &amp;lt;code&amp;gt;44&amp;lt;/code&amp;gt;, you would set this registry value to &amp;lt;code&amp;gt;44&amp;lt;/code&amp;gt; (this is available from TAPI V8 hotfix 8). Please note that this feature actually suppresses any call info for such calls, however, it does not revert previously announced call infos.  So if the call is initiated using &#039;&#039;overlapped dialling&#039;&#039;, all call states will be shown until the called number matches the value of &amp;lt;code&amp;gt;HiddenRecordingNumber&amp;lt;/code&amp;gt; and all subsequent call states will be suppressed.  This will probably leave the call shown in &#039;&#039;dialling&#039;&#039; state.  The feature should be used for destinations which are called using &#039;&#039;block dialling&#039;&#039; only thus.  &lt;br /&gt;
&lt;br /&gt;
; SilentHold : REG_DWORD. When a call is put on hold using &amp;lt;code&amp;gt;lineHold&amp;lt;/code&amp;gt;, the held party will hear &#039;&#039;music on hold&#039;&#039; emitted by the PBX. The hold-initiator will hear a dialling tone (PBX firmware v11r2 and up, with older versions the initiator would hear &#039;&#039;music on hold&#039;&#039;).  When &amp;lt;code&amp;gt;SilentHold&amp;lt;/code&amp;gt; is set to a non-zero value, the initiating party will hear silence - i.e. no dialling tone (this is available from TAPI V8 hotfix 8).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- There are some more values in a key underneath &amp;lt;code&amp;gt;HKEY_LOCAL_MACHINE\SOFTWARE\innovaphone\innovaphone® PBX V8 TAPI Service Provider&amp;lt;/code&amp;gt;&amp;lt;ref name=&amp;quot;regkey&amp;quot;/&amp;gt; called &amp;lt;code&amp;gt;Device&amp;lt;/code&amp;gt;&#039;&#039;XX&#039;&#039;: --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; NoDuplicateConnectedCalls : REG_DWORD. If set to 1, the TSP will never show more than one call per line to be active.  Extra active calls will be shown as &#039;&#039;on-hold&#039;&#039;. The situation occurs e.g. when a user initiates a 3PTY conference on the phone.  This essentially is a bug fix for Microsoft&#039;s OCS client which forces any extra active call on-hold, thereby disturbing the 3PTY function.  If your are using [http://www.estos.de/download/software/eccg.htm ESTOS&#039; Call Control Gateway]: from version &#039;&#039;2.0.1.1474 - 05.11.2008&#039;&#039; there is a fix for this same problem available.  This option thus is deprecated.&lt;br /&gt;
&lt;br /&gt;
; UseFirstLeg2 : REG_DWORD. TAPI allows only for a single leg-2 info (redirection information in case of a call forward).  If a call is forwarded mutliple times, by default the last redirection is shown in TAPI. If &amp;lt;code&amp;gt;UseFirstLeg2&amp;lt;/code&amp;gt; is set to 1 however, the first redirection is shown.&lt;br /&gt;
&lt;br /&gt;
; UseNameForDeviceGuid : REG_DWORD. The TSP will create a TAPI line for each &#039;&#039;Device&#039;&#039; of each PBX object (if &#039;&#039;MapDevices&#039;&#039; is set).  The internal unique identifier includes the &#039;&#039;Hardware Id&#039;&#039; found in the &#039;&#039;Device&#039;&#039;.  If this changes, the TAPI line representing the &#039;&#039;Device&#039;&#039; is considered new and a new TAPI &#039;&#039;permanent line id&#039;&#039; is allocated.  This may be annoying cause when a device serial number (e.g. for a telephone) is used as &#039;&#039;Hardware Id&#039;&#039;, replacing the device creates a new TAPI line.  If &#039;&#039;UseNameForDeviceGuid&#039;&#039; is set to 1, the TSP will use the &#039;&#039;Device&#039;&#039;s &#039;&#039;Name&#039;&#039; instead (which usually not changes).  While this might be more convenient, be aware that you &#039;&#039;must&#039;&#039; make sure that no PBX object has duplicate &#039;&#039;Name&#039;&#039;s!  Otherwise, TAPI will get confused.   Available from build 8178&lt;br /&gt;
&lt;br /&gt;
; ShowConfGUID : REG_DWORD.  If set and not 0, the TSP will implicitly set each call&#039;s CallData to a string such as &amp;quot;&amp;lt;code&amp;gt;conf-guid:&amp;lt;/code&amp;gt;&#039;&#039;call-guid&#039;&#039;&amp;quot;.   &#039;&#039;call-guid&#039;&#039; is a 66-byte Unicode16 string (32 hex characters plus terminating 0). Note that this will interfere with an application&#039;s use of the lineSetCallData function (tapi.h) and is therefore disabled by default. Available from build 8190&lt;br /&gt;
&lt;br /&gt;
; NoFix : REG_DWORD. If set and not 0, the TSP will not trigger a full re-synchronization if it receives implausible state messages. Available from build 8197.&lt;br /&gt;
&lt;br /&gt;
===List of supported TSPI functions===&lt;br /&gt;
&lt;br /&gt;
The TSP supports the following TAPI Service Provider Interface Functions.  Note that these do not map one to one with TAPI user functions. For more information, see the Microsoft TAPI documentation.&lt;br /&gt;
&lt;br /&gt;
*TSPI_lineAnswer&lt;br /&gt;
*TSPI_lineBlindTransfer&lt;br /&gt;
*TSPI_lineClose                      &lt;br /&gt;
*TSPI_lineCloseCall                  &lt;br /&gt;
*TSPI_lineCompleteTransfer&lt;br /&gt;
*TSPI_lineDevSpecific&lt;br /&gt;
*TSPI_lineDevSpecificFeature&lt;br /&gt;
*TSPI_lineDial&lt;br /&gt;
*TSPI_lineDrop  &lt;br /&gt;
*TSPI_lineForward&lt;br /&gt;
*TSPI_lineGenerateDigits                     &lt;br /&gt;
*TSPI_lineGetAddressCaps             &lt;br /&gt;
*TSPI_lineGetAddressID               &lt;br /&gt;
*TSPI_lineGetAddressStatus           &lt;br /&gt;
*TSPI_lineGetCallAddressID           &lt;br /&gt;
*TSPI_lineGetCallHubTracking&lt;br /&gt;
*TSPI_lineGetCallIDs&lt;br /&gt;
*TSPI_lineGetCallInfo                &lt;br /&gt;
*TSPI_lineGetCallStatus              &lt;br /&gt;
*TSPI_lineGetDevCaps                 &lt;br /&gt;
*TSPI_lineGetExtensionID&lt;br /&gt;
*TSPI_lineGetID                      &lt;br /&gt;
*TSPI_lineGetLineDevStatus           &lt;br /&gt;
*TSPI_lineGetNumAddressIDs&lt;br /&gt;
*TSPI_lineHold&lt;br /&gt;
*TSPI_lineMakeCall      &lt;br /&gt;
*TSPI_lineNegotiateExtVersion&lt;br /&gt;
*TSPI_lineNegotiateTSPIVersion       &lt;br /&gt;
*TSPI_lineOpen    &lt;br /&gt;
*TSPI_linePark&lt;br /&gt;
*TSPI_linePickup&lt;br /&gt;
*TSPI_lineRedirect&lt;br /&gt;
*TSPI_lineSelectExtVersion&lt;br /&gt;
*TSPI_lineSendUserUserInfo&lt;br /&gt;
*TSPI_lineSetAppSpecific             &lt;br /&gt;
*TSPI_lineSetCallData&lt;br /&gt;
*TSPI_lineSetCallHubTracking&lt;br /&gt;
*TSPI_lineSetCallParams                 &lt;br /&gt;
*TSPI_lineSetCurrentLocation         &lt;br /&gt;
*TSPI_lineSetDefaultMediaDetection   &lt;br /&gt;
*TSPI_lineSetMediaMode               &lt;br /&gt;
*TSPI_lineSetStatusMessages          &lt;br /&gt;
*TSPI_lineSetupTransfer&lt;br /&gt;
*TSPI_lineSwapHold&lt;br /&gt;
*TSPI_lineUnhold&lt;br /&gt;
*TSPI_lineUnpark&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*TSPI_providerConfig                 &lt;br /&gt;
*TSPI_providerCreateLineDevice&lt;br /&gt;
*TSPI_providerEnumDevices            &lt;br /&gt;
*TSPI_providerGenericDialogData&lt;br /&gt;
*TSPI_providerInit                   &lt;br /&gt;
*TSPI_providerInstall                &lt;br /&gt;
*TSPI_providerRemove                 &lt;br /&gt;
*TSPI_providerShutdown               &lt;br /&gt;
*TSPI_providerUIIdentify     &lt;br /&gt;
=====Notes on Consultation Calls=====        &lt;br /&gt;
This TSP supports the &amp;lt;code&amp;gt;lineSetupTransfer&amp;lt;/code&amp;gt; function.  However, strictly speaking, this function is not needed and should not be used.  It is merely intended for applications which do not offer a consultation call interface to the user when this function is not available.  Instead, &amp;lt;code&amp;gt;TSPI_lineMakeCall&amp;lt;/code&amp;gt; can be used where &amp;lt;code&amp;gt;lineSetupTransfer&amp;lt;/code&amp;gt; would be otherwise.  The notion of a special &#039;&#039;consultation call&#039;&#039; is an idiosyncrasy forced by legacy PBX technologies which were not able to transfer two arbitrary calls.   In these scenarios, a potentially to-be-transferred call needed to be linked to the primary call.  The PBX can transfer two arbitrary calls and thus there is no need for &amp;lt;code&amp;gt;lineSetupTransfer&amp;lt;/code&amp;gt;.  This ability is indicated by the &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_TRANSFERMAKE&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_CONFERENCEMAKE &amp;lt;/code&amp;gt; flags.   The transfer is then requested by using &amp;lt;code&amp;gt;TSPI_lineCompleteTransfer&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=====Notes on 3PTY Conferences=====&lt;br /&gt;
The TSP supports the management of 3PTY conferences.  These can be initiated by using &amp;lt;code&amp;gt;TSPI_lineCompleteTransfer&amp;lt;/code&amp;gt; with &amp;lt;code&amp;gt;LINETRANSFERMODE_CONFERENCE&amp;lt;/code&amp;gt; instead of &amp;lt;code&amp;gt;LINETRANSFERMODE_TRANSFER&amp;lt;/code&amp;gt;.  This is indicated by the flags &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_CONFERENCEHELD&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_CONFERENCEMAKE&amp;lt;/code&amp;gt;.  The 3PTY function is actually implemented by the innovaphone IP phones (such as IP2xx).  Therefore, these capabilities are only advertised if the line is based on a PBX user object.  Still, some lines where the capabilities are advertised cannot do 3PTY (such as e.g. DECT lines, analogue lines, 3rd party devices, ...). So the call to &amp;lt;code&amp;gt;TSPI_lineCompleteTransfer&amp;lt;/code&amp;gt; will succeed but the conference will not be initiated and the subsequent call states will not indicate a conference (as there is no).  &lt;br /&gt;
&lt;br /&gt;
Also, if non-telephone devices are registered with a PBX user object and these device have multiple concurrent calls (e.g. a call center connected with a multi-channel XCapi), these will be viewed as 3PTY calls (as this is the way such calls appear to the TAPI: a line with more than one non-held call).  If these calls are in fact no 3PTY, this may lead to confusing call indications from TAPI.  It is better to register such objects as a PBX gateway object.  Special treatment of 3PTY calls can be disabled by setting the registry flag &amp;lt;code&amp;gt;No3PTY&amp;lt;/code&amp;gt; (from build 8087 onwards).&lt;br /&gt;
&lt;br /&gt;
A 3PTY conference will create a new call handle for the conference.  The only operation available for such a handle is &amp;lt;code&amp;gt;TSPI_lineDrop&amp;lt;/code&amp;gt;. This will terminate the conference and restore the state active before the conference was initiated (that is, the phone that implemented the conference will now have 2 calls, one active and one on hold).  This is indicated by not setting &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_CONFDROP&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
A &amp;lt;code&amp;gt;lineDrop()&amp;lt;/code&amp;gt; on one of the 2 &#039;&#039;real&#039;&#039; calls involved will of course cancel this call and thus remove the 3PTY.&lt;br /&gt;
&lt;br /&gt;
======Notes on Intrusion Calls======&lt;br /&gt;
A special case of 3PTY is an intrusion call initiated by a [[Reference9:Phone/User/Function-Keys/Partner | partner function key]].  To TAPI, this looks like a 3PTY (which it in fact is).  However, phones before firmware version 9 hotfix 19 will not be able to release this 3PTY upon request.  Thus, you will see a 3PTY in TAPI which cannot be dropped.  From phone firmware 9 hotfix 19 on, the request to drop this 3PTY will cancel the intrusion call.  Note that TAPI will nevertheless &#039;&#039;not&#039;&#039; set &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_CONFDROP&amp;lt;/code&amp;gt; on such conferences (as TAPI does not know that this is an intrusion call).&lt;br /&gt;
&lt;br /&gt;
======Notes on Recording Calls======&lt;br /&gt;
A special case of 3PTY is a recording call.  This effectively creates an user-invisible 3PTY on the phone.  To TAPI, this looks like a 3PTY (which it in fact is).  However, phones before firmware version 9 hotfix 19 will not be able to release this 3PTY upon request.  Thus, you will see a 3PTY in TAPI which cannot be dropped.  From phone firmware 9 hotfix 19 on, the request to drop this 3PTY will cancel the recording call.   Note that TAPI will nevertheless &#039;&#039;not&#039;&#039; set &amp;lt;code&amp;gt;LINEADDRCAPFLAGS_CONFDROP&amp;lt;/code&amp;gt; on such conferences (as TAPI does not know that this is a recording call).&lt;br /&gt;
&lt;br /&gt;
Recording calls are shown as normal conferences (unless &amp;lt;code&amp;gt;No3PTY&amp;lt;/code&amp;gt; is set).  This might be confusing to applications and/or users.  See the &amp;lt;code&amp;gt;HiddenRecordingNumber&amp;lt;/code&amp;gt; tweak above for a method to hide such calls.&lt;br /&gt;
&lt;br /&gt;
=====Notes on parked Calls=====&lt;br /&gt;
The PBX can park calls from and to any existing PBX object, e.g. by virtue of [[Reference8:Configuration/Registration/Function-Keys/Park | specific feature keys]].  They are parked to/from a numeric &#039;&#039;park position&#039;&#039;.  In SOAP however, calls are parked to an object by providing the objects &#039;&#039;&#039;UserInitialize()&#039;&#039;&#039; handle and a park position.  Parked calls are then reported as straight calls with a distinct signalling state (8).  The park position is not conveyed as part of the &#039;&#039;&#039;CallInfo&#039;&#039;&#039; record.  To unpark, &#039;&#039;&#039;[[Reference8:SOAP_API#integer_UserPickup.28int_user.2C_string_cn.2C_integer_call.2C_string_group.2C_int_reg.2C_InfoArray_info.29 | UserPickup]]&#039;&#039;&#039; can be used providing the parked calls call handle as &#039;&#039;&#039;call&#039;&#039;&#039; argument.  &lt;br /&gt;
&lt;br /&gt;
The TAPI specification is unclear on how the address information required to &#039;&#039;&#039;lineUnpark()&#039;&#039;&#039; a call can be obtained by an application (except that it is returned from &#039;&#039;&#039;linePark()&#039;&#039;&#039; if the call was parked using TAPI).    The TSP thus indicates parked calls on a line with a call reason &amp;lt;code&amp;gt;LINECALLREASON_PARKED&amp;lt;/code&amp;gt;.  The caller id information is set to the parked calls call handle.  This way, the application can take the caller id information and provide it to &#039;&#039;&#039;lineUnpark()&#039;&#039;&#039; to unpark a call.  If the appication does not support this mode of operation but supports &#039;&#039;&#039;lineUnpark()&#039;&#039;&#039; and lets the user input the park identifier, the user can just provide the caller id information.&lt;br /&gt;
&lt;br /&gt;
Some applications do not care for parked calls (by examining the call reason) and just blindly report these calls like ordinary connected calls (thereby confusing the user).  To work around this problem, reporting parked calls can be turned off in the TSP configuration dialogue.&lt;br /&gt;
&lt;br /&gt;
=====Notes on sending User to User Information =====&lt;br /&gt;
The TAPI specification for sending UserUserInfo closely resembles the way ISDN defines this service.  Although the innovaphone PBX supports this service both with H.323 and SIP, it is &#039;&#039;not&#039;&#039; supported in this TSP.  Instead, sending user to user information is implemented using H.323/SIP messaging.  However, there are some important deviations and limitations caused hereby:&lt;br /&gt;
* data is &#039;&#039;not transparent&#039;&#039;.  That is, the TSP only allows for null-terminated unicode to be sent.  The data must be of even length and the last two bytes must be null. &lt;br /&gt;
* data is &#039;&#039;not sent within the call&#039;&#039;, but by initiating a separate call.  This implies that the target number used to send the message carrying the data to is &#039;guessed&#039; from the available call data.  For example, if the call is in a connected state and a connected number is known, the message is sent to the connected number.  If the call is in the ringback state, then either the called number or - if available - the redirection number is used and so forth.&lt;br /&gt;
* message calls are not indicated by the SOAP CallInfo records.  As a result, messages sent with lineSendUserUserInfo cannot be received with TAPI&lt;br /&gt;
=====Notes on receiving User to User Information =====&lt;br /&gt;
From build 8200, the TSP will deliver incoming UUI on a call. Although lineSendUserUserInfo will still send H.323/SIP messages instead of native UUI, you can now receive incoming UUI (for example from ISDN) in a LINE_CALLINFO  message.&lt;br /&gt;
&lt;br /&gt;
=====Notes on sending proprietary innovaphone Remote Control Facilities  =====&lt;br /&gt;
The SOAP  [[Reference10:SOAP_API#UserRc.28integer_call.2C_integer_rc.29|UserRc]] function allows to send various [[Reference:Remote Control Facility|facility messages]] to an innovaphone phone device.  In some cases, it is useful to be able to invoke this function through a standard TAPI mechanism.  This can be achieved by using the TAPI &#039;&#039;&#039;lineBlindTransfer&#039;&#039;&#039; function.  If the &#039;&#039;called party name&#039;&#039; provided as destination for the &#039;&#039;lineBlindTransfer&#039;&#039; (in &#039;&#039;lpszDestAddress&#039;&#039;) has the magic value &amp;lt;code&amp;gt;USERRC&amp;lt;/code&amp;gt;, then the &#039;&#039;called subaddress&#039;&#039; is converted to an integer and the result is sent as remote control facility to the call the blind transfer is applied for.  For details on how to code the &#039;&#039;called party name&#039;&#039; and the &#039;&#039;called subaddress&#039;&#039; into &#039;&#039;lpszDestAddress&#039;&#039; see [http://msdn.microsoft.com/en-us/library/windows/desktop/ms726017%28v=vs.85%29.aspx Microsoft&#039;s &#039;&#039;Canonical Address&#039;&#039; specification].     This works from TAPI8 hotfix 4.&lt;br /&gt;
&lt;br /&gt;
For example, initiating a blind transfer to &amp;lt;code&amp;gt;|16^USERRC&amp;lt;/code&amp;gt; (empty address, subaddress 16 (that is, [[Reference:Remote Control Facility|&#039;&#039;change to handset mode&#039;&#039;]]), called name &amp;lt;code&amp;gt;USERRC&amp;lt;/code&amp;gt;) will switch the phone having the call to be transferred into handset mode (and &amp;lt;code&amp;gt;|18^USERRC&amp;lt;/code&amp;gt; will switch it back to handsfree mode).  Of course, no actual transfer will happen in these cases (&#039;&#039;lineBlindTransfer&#039;&#039; is merely used as a vehicle to send the facility to the proper call).&lt;br /&gt;
&lt;br /&gt;
Such proprietary facility message can also be sent with &#039;&#039;lineMakeCall&#039;&#039; (that is, in SOAP&#039;s [[Reference10:SOAP_API#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]] function).  For example, setting up a call to &amp;lt;code&amp;gt;123|21^USERRC&amp;lt;/code&amp;gt; will send an intrusion call to extension 123 and intrude any call that might be active there. This works from TAPI8 hotfix 6. Please note that the innovaphone TAPI service provider does not support TAPI&#039;s &#039;&#039;lineCompleteCall&#039;&#039; function with &amp;lt;code&amp;gt;LINECALLCOMPLMODE_INTRUDE&amp;lt;/code&amp;gt; though (as TAPI&#039;s call model here does not fit with the PBX&#039;s call model).  Please also note that intrusion calls look like 3PTY calls to TAPI (see [[#Notes_on_Intrusion_Calls|notes on intrusion calls]] above).&lt;br /&gt;
&lt;br /&gt;
Remote control facilities are implemented by the telephone devices, so these functions are subject to the phone firmware in use.&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
[[Category:Concept|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
* [[Howto:Troubleshooting the TAPI service provider]]&lt;br /&gt;
* [[ReleaseNotes8:TAPI]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:IXI-UMS_sometimes_delivers_faxes_as_voicemails&amp;diff=80701</id>
		<title>Howto:IXI-UMS sometimes delivers faxes as voicemails</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:IXI-UMS_sometimes_delivers_faxes_as_voicemails&amp;diff=80701"/>
		<updated>2026-10-14T07:26:58Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Applies To==&lt;br /&gt;
This information applies to&lt;br /&gt;
&lt;br /&gt;
* IXI-UMS (innovaphone edition) with VOIP-CAPI or [[Howto:XCAPI|XCAPI]] up to Kernel version 5.51 (newer versions are available but not tested yet - we will test them asap and let you know if there are any changes)&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
Sometimes faxes are received as voicemails by IXI-UMS where you only hear the &amp;quot;beep&amp;quot; of the caller. This is mainly because of a timing problem. Some older faxes (analog faxes) do wait until the called party sends the fax tone and then sends it&#039;s fax tone itself. IXI waits for the calling party to send the fax tone for the first few seconds - when it the sends the tone, the callong fax answers but will be rejected, because the tone came to late.&lt;br /&gt;
&lt;br /&gt;
You have an easy possibility to overcome this issue: Simply go into the IXI Kernel Configuration, then again IXI-UMS Kernel Configuration, then &amp;quot;DDI Mapping&amp;quot; - there press &amp;quot;add&amp;quot; and type in the extension which should receive faxes only and select &amp;quot;fax&amp;quot; as service.&lt;br /&gt;
&lt;br /&gt;
This is a good way to receive all faxes, but has the drawback that now a combined number for Voicemail and Fax is not possible anymore! (So you better use that &amp;quot;hack&amp;quot; only if you have a global fax box, which you want to make sure will receive faxes sent to it.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
&lt;br /&gt;
[[Howto:IXI-UMS_Unified_Messaging_Server_-_Servonic_-_3rd_Party_Product]]&lt;br /&gt;
&lt;br /&gt;
[[Howto:Requirements_for_a_Server_to_install_and_run_IXI_UMS | IXI-UMS Server Requirements]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
[[Category:Problem-Archive|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:IXI-UMS_sometimes_delivers_faxes_as_voicemails&amp;diff=80700</id>
		<title>Howto:IXI-UMS sometimes delivers faxes as voicemails</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:IXI-UMS_sometimes_delivers_faxes_as_voicemails&amp;diff=80700"/>
		<updated>2026-10-14T07:26:36Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Applies To==&lt;br /&gt;
This information applies to&lt;br /&gt;
&lt;br /&gt;
* IXI-UMS (innovaphone edition) with VOIP-CAPI or [[Howto:XCAPI|XCAPI]] up to Kernel version 5.51 (newer versions are available but not tested yet - we will test them asap and let you know if there are any changes)&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
Sometimes faxes are received as voicemails by IXI-UMS where you only hear the &amp;quot;beep&amp;quot; of the caller. This is mainly because of a timing problem. Some older faxes (analog faxes) do wait until the called party sends the fax tone and then sends it&#039;s fax tone itself. IXI waits for the calling party to send the fax tone for the first few seconds - when it the sends the tone, the callong fax answers but will be rejected, because the tone came to late.&lt;br /&gt;
&lt;br /&gt;
You have an easy possibility to overcome this issue: Simply go into the IXI Kernel Configuration, then again IXI-UMS Kernel Configuration, then &amp;quot;DDI Mapping&amp;quot; - there press &amp;quot;add&amp;quot; and type in the extension which should receive faxes only and select &amp;quot;fax&amp;quot; as service.&lt;br /&gt;
&lt;br /&gt;
This is a good way to receive all faxes, but has the drawback that now a combined number for Voicemail and Fax is not possible anymore! (So you better use that &amp;quot;hack&amp;quot; only if you have a global fax box, which you want to make sure will receive faxes sent to it.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
&lt;br /&gt;
[[Howto:IXI-UMS_Unified_Messaging_Server_-_Servonic_-_3rd_Party_Product)]]&lt;br /&gt;
&lt;br /&gt;
[[Howto:Requirements_for_a_Server_to_install_and_run_IXI_UMS | IXI-UMS Server Requirements]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
[[Category:Problem-Archive|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Swisscom_Business_Connect_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test&amp;diff=80699</id>
		<title>Howto:Swisscom Business Connect - SIP Trunk - SIP Provider Compatibility Test</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Swisscom_Business_Connect_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test&amp;diff=80699"/>
		<updated>2026-10-14T07:24:10Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Test Results */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Innovaphone Compatibility Test Report&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;SIP Provider: swisscom Business Connect&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The provider supports all mandatory innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]].&lt;br /&gt;
&lt;br /&gt;
That being said, the provider has achieved 86,34% of all possible test points (139 of 161). For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description|Test Description V11 and later]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note, that some features are restricted or not supported by swisscom&#039;&#039;&#039;&lt;br /&gt;
* Fax over IP is on principle not supported by swisscom&lt;br /&gt;
** The T.38 feature is not available&lt;br /&gt;
** Fax via G.711 (T.38 to G.711 / Audio Fax support) is not supported by swisscom but should work in most scenarios. This Feature is not guaranteed!&lt;br /&gt;
* Only G.711a is supported, no other codecs are supported&lt;br /&gt;
* Overlapped Sending is not supported&lt;br /&gt;
* NAT Detection is not supported&lt;br /&gt;
* Redundancy Mechanism are not supported&lt;br /&gt;
* SIP over TCP is not supported&lt;br /&gt;
&lt;br /&gt;
* Incoming Early Media Channel is not supported by default and must be requestet to swisscom.&lt;br /&gt;
* CLIP no screening does not work for &amp;quot;Trunk loop Connections&amp;quot;. This means, if you dial out to the PSTN and back to your own Trunk Number, CLNS does not work.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;swisscom doesn&#039;t support &amp;quot;Reverse Media negotiation&amp;quot;. Because of this, &amp;quot;Media-Relay&amp;quot; and an &amp;quot;Exclusive Coder Setting&amp;quot; must be configured.&#039;&#039;&#039; In contrast to a SIP trunk which does not need Media-Relay, the transport of all RTP packets across the gateway will result in a higher CPU load.&lt;br /&gt;
&lt;br /&gt;
In order to use some Features like[[Howto:How_does_CLIP_no_screening_work | Clip no screening]], some [[Howto:Swisscom_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test#Configuration|configuration]] must be done.&lt;br /&gt;
&lt;br /&gt;
Supported Features:&lt;br /&gt;
* Direct Dial In&lt;br /&gt;
* DTMF&lt;br /&gt;
* CGPN can be suppressed&lt;br /&gt;
* CLIP No Screening&lt;br /&gt;
* Reverse Media Negotiation&lt;br /&gt;
* Hold/Retrieve&lt;br /&gt;
* Blind Transfer &lt;br /&gt;
&lt;br /&gt;
Supported Codecs:&lt;br /&gt;
* G.711a only&lt;br /&gt;
&lt;br /&gt;
== Current test state ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;in progress&amp;quot;}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;planned&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;referral_prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;engineered_prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;rec._prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;tested&amp;quot;(sip provider)}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;rejected&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;referral_prod.&amp;quot;-no-certificate}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Compat Status &amp;quot;certified&amp;quot;|certificate=Swisscom_Business_Connect_-_SIP_Provider_-_product-cert.pdf}}&lt;br /&gt;
&lt;br /&gt;
Testing of this product has been finalized February 2015.&lt;br /&gt;
&lt;br /&gt;
== Testing Enviroment ==&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestTopology1.png]]&lt;br /&gt;
&lt;br /&gt;
This scenario describes a setup where the PBX and phones are in a private network.&lt;br /&gt;
&lt;br /&gt;
The swisscom is providing an own Gateway (&amp;quot;Connect Box&amp;quot; or &amp;quot;Patton Smart Node&amp;quot;) which must be located in the customers private network. This Gateway has two connections:&lt;br /&gt;
* One connection to swisscom&lt;br /&gt;
* One connection to the PBX &lt;br /&gt;
Because of this, the SIP Trunk does not connect directly to the internet, but to the swisscom Gateway (&amp;quot;Connect Box&amp;quot; or &amp;quot;Patton Smart Node&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The SIP trunk must be configured with &amp;quot;Media Relay&amp;quot;, &amp;quot;exclusive G.711a&amp;quot; and &amp;quot;NO T.38&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
[[Howto:Swisscom_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test#Configuration|See configuration]]&lt;br /&gt;
&lt;br /&gt;
== Test Results ==&lt;br /&gt;
&lt;br /&gt;
For more information on the test procedure, please read the following wiki article: [[Howto:SIP_Interop_Test_Description|Test Description V11 and later]]. Bold lines in the test results indicate a KO-criteria.&lt;br /&gt;
&lt;br /&gt;
(*1) To use Incoming Early Media Channel, this feature must be requested to swisscom. Per default, it&#039;s not possible.&lt;br /&gt;
&lt;br /&gt;
(*2) Fax via G.711 (T.38 to G.711 / Audio Fax support) is not supported by swisscom but should work in most scenarios. This Feature is not guaranteed!&lt;br /&gt;
&lt;br /&gt;
(*3) CLIP no screening does not work for &amp;quot;Trunk loop Connections&amp;quot;. This means, if you dial out to the PSTN and back to your own Trunk Number, CLNS does not work in this case. &lt;br /&gt;
&lt;br /&gt;
=== Basic Call ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;call using g711a&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;call using g711u&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;NOK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|call using g723&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|call using g729&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|call using g722&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|Overlapped sending&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;early media channel outgoing&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|early media channel incoming&lt;br /&gt;
|OK/NOK (*1)&lt;br /&gt;
|----&lt;br /&gt;
|Fax using T.38&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|T.38 Transcoding by the provider&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|Fax using G.711&lt;br /&gt;
|OK (*2)&lt;br /&gt;
|----&lt;br /&gt;
|Reverse Media Negotiation&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|CGPN can be suppressed&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|CLIP no screening&lt;br /&gt;
|OK (*3)&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Long time call possible(&amp;gt;30 min)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;External Transfer&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|NAT Detection&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|Redundancy&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|SIP over TCP&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Voice Quality OK?&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Direct Dial In ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Inbound(Provider -&amp;gt; Innovaphone)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Outbound(Innovaphone -&amp;gt; Provider)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Loop In call(Innovaphone -&amp;gt; Provider -&amp;gt; Innovaphone)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK (*3)&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== DTMF ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;DTMF tones sent correctly via RTP-events(RFC 2833)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|DTMF tones sent correctly via SIP-Info&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;DTMF tones received correctly via RTP-events(RFC 2833)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hold/Retrieve ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be put on hold&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold / announcement from PBX&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Transfer with consultation ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be transferred&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
!MoH Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Transfer with consultation (alerting only) ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be transferred&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold or dialling tone&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call returns to transferring device if the third&#039;&#039;&#039; &lt;br /&gt;
&#039;&#039;&#039;Endpoint is not available&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
!MoH Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Blind Transfer ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Call can be transferred&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears dialling tone&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== CFU / CFB Transfer ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be forward&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Held end hears dialling tone&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== CFNR / Blind Transfer (alerting only)===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be transferred or forward&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Held end hears dialling tone&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Broadcast Group &amp;amp; Waiting Queue ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Caller can make a call to a Broadcast Group&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Caller can make a call to a Waiting Queue&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Announcement if nobody picks up the call&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
===Firmware version===&lt;br /&gt;
&lt;br /&gt;
All innovaphone devices use V11 build 11.0828 as firmware during test.&lt;br /&gt;
&lt;br /&gt;
=== SIP - Trunk ===&lt;br /&gt;
Following configuration needs to be done in the SIP Gateway Interface settings:&lt;br /&gt;
&lt;br /&gt;
* 1: Enter your phonenumber and private IP address of swisscom Gateway (&amp;quot;Connect Box&amp;quot; or &amp;quot;Patton Smart Node&amp;quot;) with port 5062!&lt;br /&gt;
* 2: Enter credendtials&lt;br /&gt;
* 3: Select G.711a exclusive&lt;br /&gt;
* 4: Disable T.38 and Enable Media Relay&lt;br /&gt;
* 5: Disable encryption&lt;br /&gt;
* 6: Use &amp;quot;CGPN in user part of URI&amp;quot; in &amp;quot;From Header&amp;quot; and &amp;quot;Fixed AOR&amp;quot; in &amp;quot;Identity Header&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig1.png]]&lt;br /&gt;
&lt;br /&gt;
=== Number Mapping ===&lt;br /&gt;
Following configuration needs to be done in the SIP Gateway Number Mappings:&lt;br /&gt;
&lt;br /&gt;
* 1: Add &amp;quot;00&amp;quot; to incoming CGPNs without a leading &amp;quot;0&amp;quot; because international numbers are coming in like &amp;quot;49703173009&amp;quot;.&lt;br /&gt;
* 2: Because swisscom is using the full national number for incoming calls, you need to cut off the digits before an extension. In example, 04333693xx will be translated to xx.&lt;br /&gt;
* 3: In case of call forwardings, you need to cut off the single leading &amp;quot;0&amp;quot; (national calls) and translate a leading &amp;quot;000&amp;quot; (international calls) to &amp;quot;+&amp;quot; in the CGPN Out map.&lt;br /&gt;
* 4: In the CGPN Out map, you also need to translate the extensions to the national number format. In example, xx will be translated to 04333693xx.&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig2.png]]&lt;br /&gt;
&lt;br /&gt;
=== Route Settings ===&lt;br /&gt;
A default Route Setup is used:&lt;br /&gt;
&lt;br /&gt;
* 1: Force Enblock Setting is required for outgoing calls.&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig3.png]]&lt;br /&gt;
&lt;br /&gt;
=== Fax ===&lt;br /&gt;
&#039;&#039;&#039;swisscom does not support any Fax communications.&#039;&#039;&#039; Because of this, T.38 can not be used.&lt;br /&gt;
&lt;br /&gt;
If you want to use Fax even so, you need to set T.38 to G.711 translation (Audio Fax support, available from V11). This works in a lot of cases where you have no problems with QoS. &#039;&#039;&#039;But it&#039;s not guaranteed and swisscom gives no support in case of problems!&#039;&#039;&#039;  &lt;br /&gt;
&lt;br /&gt;
Example to set T.38 to G.711 translation (Audio Fax support) on the Faxserver interface:&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig4.png]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Compat|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Mobile_Extension&amp;diff=80698</id>
		<title>Howto:Mobile Extension</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Mobile_Extension&amp;diff=80698"/>
		<updated>2026-10-14T07:23:02Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some customers like to have their employees cellular phones integrated as pseudo extensions into the PBX. &lt;br /&gt;
&lt;br /&gt;
While there are sophisticated solutions (a.k.a “mobile extensions”) available on the market, basic requirements can be fulfilled using standard innovaphone PBX features.  &lt;br /&gt;
&lt;br /&gt;
Here is how.&lt;br /&gt;
&lt;br /&gt;
==Applies To==&lt;br /&gt;
This information applies to&lt;br /&gt;
&lt;br /&gt;
* innovaphone Pbx&lt;br /&gt;
Build 05-5903 and later (note that this is obsolete from V8, use mobility and/or fork instead)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: mobile integration, poor mans mobility --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
===Problem Details===&lt;br /&gt;
While PBX extensions enjoy a number of supported features, employees with cellular phones in addition to their normal extension often want to integrate their cell phone like just normal extensions.  &lt;br /&gt;
&lt;br /&gt;
Basic requirements include&lt;br /&gt;
&lt;br /&gt;
·         Cellular phones can be called via short dial (for example using a prefix like 67, if the users extension is 72, then her cellular can be called via 6772)&lt;br /&gt;
&lt;br /&gt;
·         The cellular phone’s busy status is seen by the CTI application&lt;br /&gt;
&lt;br /&gt;
·         The cellular number is hidden to external callers&lt;br /&gt;
&lt;br /&gt;
·         Cellular phones can place calls through the main PBX (2 stage dialing), allowing outgoing and incoming calls to be tracked be the PBX’s billing and monitoring system.&lt;br /&gt;
&lt;br /&gt;
Also, cost reductions may be achieved by using only the PBX’s mobile service number for outgoing calls.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===System Requirements===&lt;br /&gt;
The basic solution described here requires&lt;br /&gt;
&lt;br /&gt;
·         To define each cellular as a separate user in the PBX, thus consuming a PBX registration license&lt;br /&gt;
&lt;br /&gt;
·         A waiting queue for the 2 stage dialing function. &lt;br /&gt;
&lt;br /&gt;
·         A web server (or via the Compact Flash Slot)and an appropriate announcement for the waiting queue.  &lt;br /&gt;
&lt;br /&gt;
Access to this will require a GWxx entry.  &lt;br /&gt;
&lt;br /&gt;
However, this does not need to be dedicated, so you can share asingle access for all applications using web announcements.&lt;br /&gt;
&lt;br /&gt;
·         2 GWxx entries in the gateway implementing the trunk access.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Except for the web server (or via the Compact Flash Slot) for the announcement, no special soft- or firmware needs to be installed&lt;br /&gt;
===Configuration===&lt;br /&gt;
&lt;br /&gt;
===Numbering plan===&lt;br /&gt;
&lt;br /&gt;
Although there is not strict requirement to allocate a certain numbering space for cellular phones, users usually find it more easy to understand and memorize if all cell related functions are in a common numbering space.  &lt;br /&gt;
&lt;br /&gt;
In this example, we have allocated the numbering space starting with “67” for the cellular system.&lt;br /&gt;
&lt;br /&gt;
Also, in our example, the numbering plan for “normal” extensions has 2 digits.  As a convention, for cellular phone of a user with extension “xx”, we use extension “67xx”. &lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile2.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Waiting queue===&lt;br /&gt;
The waiting queue has extension 670.   &lt;br /&gt;
&lt;br /&gt;
Long name and name are set to “cell-dial”. &lt;br /&gt;
&lt;br /&gt;
The queue will accept calls after a short alerting period (we have chosen 1 second).  &lt;br /&gt;
&lt;br /&gt;
Only the 1st announcement needs to be configured, the exact settings here depend on your announcement source configuration.  &lt;br /&gt;
&lt;br /&gt;
If you already have a path to your web server through a gateway’s HTTP interface, use this.  &lt;br /&gt;
&lt;br /&gt;
If not, you will need to configure such path (see below).  &lt;br /&gt;
&lt;br /&gt;
It is important to enable the DTMF 2-stage dialing in the 3rd page.  &lt;br /&gt;
&lt;br /&gt;
For this, you simply need to map each digit to itself.&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_Extension_Mobile1.PNG ]]&lt;br /&gt;
&lt;br /&gt;
===HTTP Interface===&lt;br /&gt;
&lt;br /&gt;
If you already have a path to your web server configured, use this.  &lt;br /&gt;
&lt;br /&gt;
If not, you will need to configure one as follows. &lt;br /&gt;
&lt;br /&gt;
Create a standard user entry with name “announce”. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile3.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Create a GWxx entry that registers at the PBX user “announce”.&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile4.PNG ]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Create a route from the PBX user GWxx to the HTTP interface.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile5.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Registration of cellular phones to the PBX===&lt;br /&gt;
&lt;br /&gt;
Create a GWxx entry to register all cellular phones with the PBX.  &lt;br /&gt;
&lt;br /&gt;
The key point to understand here is that all phones are registered using a single PBX entry.  &lt;br /&gt;
&lt;br /&gt;
That is, a single registration from the GWxx configured will result in many registrations on the PBX.  &lt;br /&gt;
&lt;br /&gt;
Use a registration as client mode.&lt;br /&gt;
&lt;br /&gt;
Add an alias to this GWxx for each cellular phone, use its extension (“67xx”) as E164 and an appropriate name as H.323 name.&lt;br /&gt;
&lt;br /&gt;
In the PBX, add each cellular phone as standard user object.  &lt;br /&gt;
&lt;br /&gt;
Use an appropriate long name, use the H.323 name you have used as an alias above as name and use the E164 number you have used above as number.&lt;br /&gt;
&lt;br /&gt;
This user object is an ordinary user object and behaves like that.  &lt;br /&gt;
&lt;br /&gt;
You may do whatever you feel to it, e.g. add it to groups etc.&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile6.PNG]]&lt;br /&gt;
&lt;br /&gt;
===Defining Routes from and to the cellular Phones===&lt;br /&gt;
&lt;br /&gt;
As your cellular phones are now registered with the PBX, calls to them will be routed the gateway level.  &lt;br /&gt;
&lt;br /&gt;
The purpose here is to map the extension numbers to “real” cellular numbers and to route the call back then to the PBX.  &lt;br /&gt;
&lt;br /&gt;
While the mapping could be achieved using a PBX MAP object too, this would not allow the cellular to be seen by the SOAP system and thus your CTI application.  &lt;br /&gt;
&lt;br /&gt;
To route the calls back to the PBX, you will need a routing entry into the PBX.  &lt;br /&gt;
&lt;br /&gt;
If you already have an “EXTERN” registration, you can use this.  If not, you will need to configure a separate GWxx for this as follows.&lt;br /&gt;
&lt;br /&gt;
In the PBX, create a user object with name like the H.323 name you used for the GWxx.  &lt;br /&gt;
&lt;br /&gt;
Be sure to set the “gateway” option.  &lt;br /&gt;
&lt;br /&gt;
In our scenario, this user does not need a number as it is never used for outgoing calls.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Create a GWxx which registers with the PBX as gateway.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile7.PNG]]&lt;br /&gt;
&lt;br /&gt;
To configure calls to cellular phones, add a route from the gateway that registers your cellular phones as defined above (GW4 in our example) to the routing entry of the PBX.  &lt;br /&gt;
&lt;br /&gt;
In this route, map each phones short-dial extension (as defined above in the PBX) to the “real” phone-number.  &lt;br /&gt;
&lt;br /&gt;
Make sure you define the appropriate trunk access code if required.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extensionMobile8.PNG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To configure calls from cellular phones  through the PBX, create a route from your trunk line to the GWxx entry that registers your cell phones with the PBX.  &lt;br /&gt;
&lt;br /&gt;
Add a map that routes all calls unchanged (that is, no called number in and no called number out).  &lt;br /&gt;
&lt;br /&gt;
Make sure both the “final route” and “verify cgpn” flags are set.  &lt;br /&gt;
&lt;br /&gt;
Then add CGPN maps to this route, one for each cellular phone.  &lt;br /&gt;
&lt;br /&gt;
In these maps, map the cellular phones real number (as it is seen in the gateways routing, usually without trunk access code) to the cell phones pseudo extension.&lt;br /&gt;
&lt;br /&gt;
Then, add a last map which routes calls to the 2-stage dialing waiting queue to TEST.  &lt;br /&gt;
&lt;br /&gt;
This map is crucial as it prevents external callers to use your PBX for outgoing calls on you cost.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[image:Mobile_extension_Mobile9.PNG]]&lt;br /&gt;
&lt;br /&gt;
===Known Problems===&lt;br /&gt;
&lt;br /&gt;
As with all mobile solutions, cell phone users will effectively loose their local phone book (as they must not dial out directly any more but go through 2-stage dialing).  &lt;br /&gt;
&lt;br /&gt;
One solution to that is a cellular that supports “calling card operation”.  &lt;br /&gt;
&lt;br /&gt;
In this mode, the cellular will for each call first call the calling card number, then the desired target using DTMF.  &lt;br /&gt;
&lt;br /&gt;
If your cells do support this, configure the number of your 2-stage dialing waiting queue as calling card number.&lt;br /&gt;
&lt;br /&gt;
Professional mobile extension solutions will address this problem by providing a dialable phone book in the 2-stage dialing phase.  &lt;br /&gt;
&lt;br /&gt;
Also, such solutions will support a lot more features on the cellular phone, like putting calls on hold, transferring calls or setting up 3PTY conferences.&lt;br /&gt;
&lt;br /&gt;
When calling out to a cell phone, it is desriable to send the calling line id of the original caller to the cell.   &lt;br /&gt;
&lt;br /&gt;
The innovaphone PBX will do this in fact, however, under normal circumstances this calling line id is rejected by the carrier and replaced by the trunk lines base number.  &lt;br /&gt;
&lt;br /&gt;
This is because the number sent is not associated to the trunk line (that is, to the carrier it looks like spoofing invalid calling party numbers).  &lt;br /&gt;
&lt;br /&gt;
The only solution here is to enable &amp;quot;clip no screening&amp;quot; on the trunk line (there is a separate wiki [[Howto:How does &amp;quot;CLIP no screening&amp;quot; work?]] article about this topic).&lt;br /&gt;
&lt;br /&gt;
There may be an issue when external users are calling mobile extension and the &amp;quot;if an incomplete number is dialed&amp;quot; diversion in the trunk object is used.  &lt;br /&gt;
&lt;br /&gt;
The timeout to detect incomplete numbers is 4 seconds and the cellular network (where the call to the mobile extensions actually is routed to) may be too slow to respond within this time.&lt;br /&gt;
  &lt;br /&gt;
To work around, either do not use this diversion type or upgrade your pbx to build 05-5917 or later.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For professional 3rd party mobile integration soloution please refer to the related articels&lt;br /&gt;
&lt;br /&gt;
== Related Articles == &lt;br /&gt;
&lt;br /&gt;
[[Howto:Quescom Mobility Services Pack - SIP Testreport]]&lt;br /&gt;
&lt;br /&gt;
[[Howto:Teleserver_Mobile_Pro_-_Speech_Design_-_3rd_Party_Product]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto7:2N_VoiceBlue_Lite_-_2N_-_3rd_Party_Product&amp;diff=80697</id>
		<title>Howto7:2N VoiceBlue Lite - 2N - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto7:2N_VoiceBlue_Lite_-_2N_-_3rd_Party_Product&amp;diff=80697"/>
		<updated>2026-10-14T07:14:38Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- this text is a comment that is not visible on normal view at the article. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- to create a new entry here,&lt;br /&gt;
   - fill in all sections marked as &amp;quot;by vendor&amp;quot;&lt;br /&gt;
   - innovaphone will then complete the remaining sections (marked as &amp;quot;by inno&amp;quot;)&lt;br /&gt;
  &lt;br /&gt;
  Please note that this article is in English only!&lt;br /&gt;
  feel free to ask presales in case you have any difficulties on editing wiki articles &lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   - upload your company and product logo (if any) in a suitable size (.pgn preferred)&lt;br /&gt;
   - replace images below with your logo&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
[[Image:2N logo new.png||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
[http://www.2n.cz/products/gsm_gateways/voip_gsm_gateway/voiceblue_voip_gsm_gateway.html &#039;&#039;&#039;2N VoiceBlue Lite&#039;&#039;&#039; VoIP GSM Gateway]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&lt;br /&gt;
{{Template:Compat Status &amp;quot;tested&amp;quot;}}&lt;br /&gt;
&amp;lt;!--{{Template:Compat Status &amp;quot;in progress&amp;quot;}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;certified&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;tested&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;rejected&amp;quot;}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Testing of this product has been finalized October 6th, 2009.&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- by inno:&lt;br /&gt;
   - select one or more of the available recommended product categories &lt;br /&gt;
     a list of valid Categories can be found in &lt;br /&gt;
     Special Pages / Prefix Index / Display pages with prefix = RecProd, Display pages with prefix = Category &lt;br /&gt;
     (you need to apply it twice, first as template {{..}}, seconds as category [[..]])&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty Network Equipment}}&lt;br /&gt;
[[Category:3rdParty Network Equipment]]&lt;br /&gt;
&lt;br /&gt;
{{Category:3rdParty Mobility Solutions}}&lt;br /&gt;
[[Category:3rdParty Mobility Solutions|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
Gateway between VoIP environment and GSM network with additional features.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- by inno:&lt;br /&gt;
   - version of software that was tested, as declared by the vendor, please not if patches have been applied&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
*Firmware Version 2.00n&lt;br /&gt;
*innovaphone PBX Firmware Version 7.00 hotfix5&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- by vendor&lt;br /&gt;
   - Official name of your company, at best linked to your companies web site url, Official name of the vendors web site &lt;br /&gt;
   - you may also add a logo&lt;br /&gt;
     - upload your company logo (.png preferred, suitable size)&lt;br /&gt;
     - replace logo below with yours &lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:2N logo new.png|150px]] &lt;br /&gt;
&lt;br /&gt;
[http://www.2n.cz 2N TELEKOMUNIKACE a.s. ]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
2N® VoiceBlue Lite is an ideal complementary product to any SIP-based IP PBX. It allows the user to get from the IP to a GSM network and vice versa in the smartest and cheapest way. Target users are small, medium and large companies using IP telephony, traffic terminating companies or companies with international affiliates.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What are the biggest beneffits ?&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Saving your money&#039;&#039;&#039; || 2N VoiceBlue Lite provides connection between VoIP enviroment and GSM network, this kind of interconnection allows you to reduce your GSM call costs. In case you are using VPN SIM cards you can make &#039;&#039;&#039;free GSM calls&#039;&#039;&#039; from your company to appropriate GSM operator. 2N VoiceBlue Lite uses a powerful Least Cost Route automat so you can be sure that you are using the chepest way everytime.&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Mobility Extension support&#039;&#039;&#039; || Try to imagine that you can&#039;t miss any call in case that you are not in the office. This is the basic idea of this feature. All calls to your desk phone are automaticly tranfered to your mobile phone as well. But we went more further. You can also hold the call on mobile phone and make tranfer to another extension. You can also use all services of your IP PBX on mobile phone. To make it more easier we developed special Simbian application for mobile phones. &lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;SMS sending/receiving&#039;&#039;&#039; || When you implement 2N VoiceBlue Lite into your VoIP environment you receive possibility to send/receive SMSes from all computers in your company. You just need to install the SMS client to all of them.&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Sound Quality&#039;&#039;&#039; || 2N VoicBlue Lite contains high quality Siemens (Cinterion) GSM modules or SierraWireless UMTS modules. You can set transmitting/receiving volume for all of them and also more detailed settings is available by AT commands.&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Additional Services&#039;&#039;&#039; || Call Data Records, Callback, SMS at now answer etc. You can use many of our services what can make your communication easier, faster and more comfortable.&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Competitive Analysis==&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   - add short competitive analysis.  Maximum 250 words.  This text should enable the innovaphone reseller to select &lt;br /&gt;
     your product for scenarios where it is especially useful&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2N VoiceBlue Lite is solution for modern companies using VoIP network. It can be used like a complementary product for any IP PBX system.&lt;br /&gt;
&lt;br /&gt;
Unique selling points:&lt;br /&gt;
&lt;br /&gt;
* Reduce your GSM call costs up to 90%&lt;br /&gt;
* Mobility Extension feature&lt;br /&gt;
* SMS sending/receiving&lt;br /&gt;
* Lest Cost Routing according to free minutes, time, prefix&lt;br /&gt;
* Possibility to trace communication for technicians  &lt;br /&gt;
* Reliable product&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- by inno:&lt;br /&gt;
   - add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, &lt;br /&gt;
     parts of the product that has not been tested or limitations discovered.  very short and concise (everything else is in &lt;br /&gt;
     the test report) &lt;br /&gt;
   - add link to product test report here&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the first place 2N VoiceBlue Lite is a GSM to SIP Gateway with a support up to 4 SIM cards. There are also basic Mobility Extension features implemented, that may be used in addition to the main functions. A software for mobile phones to assist the Mobile Extension features is also available.&lt;br /&gt;
&lt;br /&gt;
However there are still [[Howto7:2N_-_VoiceBlue_Lite_-_Testreport#Minor_Bugs|minor bugs]], a bug-fix from vendor is still pending.&lt;br /&gt;
&lt;br /&gt;
For a detailed analysis of the product, please have a look at the [[Howto7:2N_-_VoiceBlue_Lite_-_Testreport|2N - VoiceBlue_Lite - Testreport]].&lt;br /&gt;
&lt;br /&gt;
==Pricing==&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   - describe ballpark pricing, e.g. &amp;quot;500€ per seat&amp;quot; or &amp;quot;starting at 25.000€ depending on the number of trunk lines&amp;quot;   &lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Starting at 2000 EUR for end users.&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   - add name, address, phone, fax, email, web of primary recommended sales contact&lt;br /&gt;
     if suitable, you may consider specifying several contacs, depending on your sales structure &lt;br /&gt;
     (e.g. by country or vertical market)&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| Name: || &lt;br /&gt;
|-&lt;br /&gt;
| Position: || Account and Product Manager&lt;br /&gt;
|-&lt;br /&gt;
| Company: || 2N Telekomunikace a.s. &lt;br /&gt;
|-&lt;br /&gt;
| Street: || Modranska 621 &lt;br /&gt;
|-&lt;br /&gt;
| Country/ZIP/City || CZ-14301 Praha 4&lt;br /&gt;
|-&lt;br /&gt;
| Tel: || +420 2613015...&lt;br /&gt;
|-&lt;br /&gt;
| Fax: || +420 2613015...&lt;br /&gt;
|-&lt;br /&gt;
| Mail: ||sales@2n.cz &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:Compat|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto7:2N_-_VoiceBlue_Lite_-_Testreport&amp;diff=80696</id>
		<title>Howto7:2N - VoiceBlue Lite - Testreport</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto7:2N_-_VoiceBlue_Lite_-_Testreport&amp;diff=80696"/>
		<updated>2026-10-14T07:14:14Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Summary==&lt;br /&gt;
In the first place 2N VoiceBlue Lite is a GSM to SIP Gateway with a support up to 4 SIM cards. There also basic Mobility Extension features implemented and may in addition to main functions are used in parallel. A software for mobile phones to assist Mobile Extension features is also available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A fix for the [[Howto7:2N_-_VoiceBlue_Lite_-_Testreport#Minor_Bugs|minor bug]] from vendor is pending.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==General Information==&lt;br /&gt;
&lt;br /&gt;
* Product name: Mobility Extension&lt;br /&gt;
* Vendor: 2N&lt;br /&gt;
* Version: 2.00n&lt;br /&gt;
* Firmware: 02.07.35i19 (first test done with older Firmware 02.07.35b02)&lt;br /&gt;
* innovaphone Firmware: V7 hotfix5&lt;br /&gt;
&lt;br /&gt;
==Current test state==&lt;br /&gt;
{{Template:Compat Status &amp;quot;tested&amp;quot;}}&lt;br /&gt;
&amp;lt;!--{{Template:Compat Status &amp;quot;in progress&amp;quot;}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;certified&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;tested&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;rejected&amp;quot;}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Testing of this product has been finalized October 6th, 2009.&lt;br /&gt;
&lt;br /&gt;
==Configured Scenario==&lt;br /&gt;
&amp;lt;!--insert here a graphical description(png - format) of the test scenario--&amp;gt;&lt;br /&gt;
&amp;lt;!--also try to describe the purpose of the implemented network setup--&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N Mobility Extenson Testing Scenario.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Description ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Mobile Extension Features ===&lt;br /&gt;
In addition to the SIP registration at the PBX as a GSM Gateway, it is possible to define Mobile Extensions registered via SIP separately to the particular user object on the PBX. In this way the calls to the user object on the PBX also signalled to ther mobile phone and the calls from the users mobile phone, dialed via 2 stage dialing, are placed to the PBX via this SIP registration.&lt;br /&gt;
&lt;br /&gt;
Access to the fixed-phone-like functions from any registered mobile phone(in addition to the PBX DTMF-Features) via DTMF Features of the GSM GW:&lt;br /&gt;
&lt;br /&gt;
*call hold/resume&lt;br /&gt;
*swap between the calls&lt;br /&gt;
*transfer&lt;br /&gt;
*blind transfer&lt;br /&gt;
&lt;br /&gt;
=== Tested Call Flows ===&lt;br /&gt;
; Normal user outbound to GSM : A call from a PBX user routed via LCR to the GSM network via GSM GW&lt;br /&gt;
; Inbound to normal user : A call from GSM network to an internal PBX user&lt;br /&gt;
; Inbound to Mobility Extension user : A call from any PBX user or from outside the PBX to the Mobility Extension user(One Number)&lt;br /&gt;
; Mobility Extension to normal user : A call from mobile phone of the Mobility Extension user via GSM GW into the PBX to an internal PBX user&lt;br /&gt;
&lt;br /&gt;
==Important Components==&lt;br /&gt;
&amp;lt;!--describe here the components used in the previous picture--&amp;gt;&lt;br /&gt;
&amp;lt;!--the description should contain information about the &#039;name&#039;, &#039;role&#039;(e.g. Master,Slave,etc.) and FW-version--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Server Requirements===&lt;br /&gt;
*no server components required&lt;br /&gt;
&lt;br /&gt;
==Product Setup==&lt;br /&gt;
&lt;br /&gt;
===Installation &amp;amp; Configuration of the vendor hardware===&lt;br /&gt;
; System parameters : Set IP address, SIM PIN Number and DTMF codes. Use &amp;quot;+&amp;quot; for the &amp;quot;End of dialing&amp;quot; if you intend to use PBX based DTMF features.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 01.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; SIP parameters : &amp;quot;SIP registration expires&amp;quot; must be set to 120s(see minor bugs). Set DTMF RFC2833.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 02.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; GSM outgouing groups : Set CLIR to &amp;quot;Disable (CLIP - on)&amp;quot;. Our experience is that in Norway Delay for alerting has to be set to 2 seconds. With only one second there is no ringtone.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 03.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; GSM incoming groups : Set &amp;quot;Accept incoming calls + dialtone&amp;quot;.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 04.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; Network list : Set prefixes according your GSM provider.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 05.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; LCR table : Configuration example for straightforward LCR.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 06.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; GSM basic parameters : Set &amp;quot;Generate busy tone to GSM&amp;quot;.&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 07.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; Mobile Extension : Define PBX User Name under &#039;&#039;Name&#039;&#039;, PBX User Number under &#039;&#039;User&#039;&#039; and PBX User Password under &#039;&#039;Password&#039;&#039;. The parameter &#039;&#039;Name&#039;&#039; must be one word without spaces. &#039;&#039;Password&#039;&#039; must be configured. Set users mobile phone number under &#039;&#039;CLIP&#039;&#039;. &lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 08.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Installation &amp;amp; Configuration of the innovaphone components===&lt;br /&gt;
The GSM GW is registered on the gatekeeper GW3:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 09.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LCR Routing from and into the PBX:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:2N VoiceBlue Lite Configuration 10.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
No special configuration in the PBX is required, mobile extension user is registered directly to the user object.&lt;br /&gt;
&lt;br /&gt;
==Product Test==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===SIP Interop Test Results===&lt;br /&gt;
&lt;br /&gt;
For more information on the test procedure, please read the following wiki article: [[Howto:SIP_Interop_Test_Description|SIP Interop Test Description]].&lt;br /&gt;
&lt;br /&gt;
==== Basic Call ====&lt;br /&gt;
&lt;br /&gt;
calls between mobile phone via GSM GW and innovaphone phones (both directions).&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|call using g711a&lt;br /&gt;
|&#039;&#039;&#039;Yes&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|call using g711u&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|call using g723&lt;br /&gt;
|Nok&lt;br /&gt;
|----&lt;br /&gt;
|call using g729&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Overlapped sending&lt;br /&gt;
|Not supported&lt;br /&gt;
|----&lt;br /&gt;
|Early media channel&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Fax using T.38&lt;br /&gt;
|Not supported&lt;br /&gt;
|----&lt;br /&gt;
|CGPN can be supressed&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Reverse Media Negotiaton&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Codec Renegotiaton&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Long time call possible(&amp;gt;30 min)&lt;br /&gt;
|Not tested, should work(no sessions expired timer)&lt;br /&gt;
|----&lt;br /&gt;
|Voice Quality OK?&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Direct Dial In ====&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Inbound(GSM GW-&amp;gt; innovaphone)&lt;br /&gt;
|Not supported&lt;br /&gt;
|----&lt;br /&gt;
|Outbound(innovaphone -&amp;gt; GSM GW)&lt;br /&gt;
|Not supported&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== DTMF ====&lt;br /&gt;
DTMF via RFC2833 is supported and must be activated on the GSM GW. Tested from mobile phone via GSM GW to innovaphone pbx and vice versa.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|DTMF tones sent to GSM correctly&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|DTMF tones received from GSM correctly&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Hold/Retrieve ====&lt;br /&gt;
&lt;br /&gt;
Tested between mobile phone via GSM GW and innovaphone phones. &lt;br /&gt;
Tested in both directions.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Call can be put on hold &lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold / announcement from PBX&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold &lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Transfer with consultation ====&lt;br /&gt;
&lt;br /&gt;
innovaphone phone transfers mobile call (via GSM GW) and vice versa.&lt;br /&gt;
Call returns works only when innovaphone phones transfers call (pbx feature).&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Call can be transferred&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold&lt;br /&gt;
|Yes&lt;br /&gt;
|---&lt;br /&gt;
|Call returns to transferring device if the third &lt;br /&gt;
Endpoint is not available&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Transfer with consultation (alerting only) ====&lt;br /&gt;
&lt;br /&gt;
innovaphone phone transfers mobile call (via GSM GW) and vice versa.&lt;br /&gt;
Call returns works only when innovaphone phones transfers call (pbx feature).&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Call can be transferred&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold or dialing tone&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Call returns to transferring device if the third &lt;br /&gt;
Endpoint is not available&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Blind Transfer ====&lt;br /&gt;
&lt;br /&gt;
Tested between mobile phone via GSM GW and innovaphone phones in both directions.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Call can be transferred&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears dialing tone&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Broadcast Group &amp;amp; Waiting Queue ====&lt;br /&gt;
&lt;br /&gt;
Calls from mobile phone (via GSM GW) to innovaphone pbx.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Mobile phone  can make a call to a Broadcast Group&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Mobile phone  can get a call from a Broadcast Group&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Mobile phone can make a call to a Waiting Queue &lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Mobile phone can get a call from a Waiting Queue &lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Announcement if nobody picks up the call&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Mobility Features available via DTMF on ViceBlue Lite===&lt;br /&gt;
&lt;br /&gt;
====Call Hold====&lt;br /&gt;
Default DTMF code 7*.&lt;br /&gt;
&lt;br /&gt;
Put on hold with *7, retrieve with 9#.&lt;br /&gt;
&lt;br /&gt;
====Transfer====&lt;br /&gt;
Default DTMF Code &amp;lt;Number&amp;gt;#&lt;br /&gt;
&lt;br /&gt;
*Call form mobile to GSM GW&lt;br /&gt;
*Dial 101#&lt;br /&gt;
*101 accepts the call&lt;br /&gt;
*Dial 7*&lt;br /&gt;
*Dial 102#&lt;br /&gt;
*102 accepts the call&lt;br /&gt;
*Hang up&lt;br /&gt;
*101 and 102 are connected&lt;br /&gt;
&lt;br /&gt;
====Blind Transfer====&lt;br /&gt;
Default DTMF Code #&amp;lt;Number&amp;gt;#&lt;br /&gt;
&lt;br /&gt;
*Call form mobile to GSM GW&lt;br /&gt;
*Dial 101#&lt;br /&gt;
*101 accepts the call&lt;br /&gt;
*Dial 7*&lt;br /&gt;
*Dial #102#&lt;br /&gt;
*102 alerting&lt;br /&gt;
*Hang up manually (9# doesnt work)&lt;br /&gt;
&lt;br /&gt;
====Folow Me====&lt;br /&gt;
Enable/disable calls on user object from PBX to GSM.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== SMS at No Answer====&lt;br /&gt;
Enable/disable SMS via GSM to the number of mobile phone.&lt;br /&gt;
&lt;br /&gt;
===Mobility Features available via PBX DTMF Features===&lt;br /&gt;
A DTMF Digit # is used on the GSM GW to provide the end of dialing as default seting, but it also used in the PBX DTMF Feature Object.&lt;br /&gt;
&lt;br /&gt;
; Solution 1 (used for tests): Change or disable &amp;quot;End of dialing&amp;quot; Digit to &amp;quot;+&amp;quot; and reduce the &amp;quot;Timeout for entering DTMF&amp;quot; on GSW GW.&lt;br /&gt;
; Solution 2 : Change PBX DTMF Features to use * instead of #.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Enable/Disable CFs&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Pickup Group&lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Park/Unpark &lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Call Completion Busy &lt;br /&gt;
|Yes&lt;br /&gt;
|----&lt;br /&gt;
|Join Group&lt;br /&gt;
|Yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Minor Bugs==&lt;br /&gt;
&amp;lt;!--all major bugs should be fixed when the product is certified. However if there are some minor problems(that will be fixed in a upcoming release), this is the place to mention them--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; No spaces in the username of Mobile Extension allowed: PBX User Object field &#039;&#039;Name&#039;&#039; must be without spaces, in order to be able to register the Mobile Extesion from 2n VoiceBlue Lite. The space is not escaped according RFC 3261 (19.1.4 URI Comparison) : should be &amp;lt;code&amp;gt;One%20Number&amp;lt;/code&amp;gt;, but is &amp;lt;code&amp;gt;One Number&amp;lt;/code&amp;gt;. Therefore registration is possible, but further SIP interop is broken(e.g. calls to busy subscribers, see the next Bug).&lt;br /&gt;
; No busy tone to Mobile Extension : if the PBX user is busy and is called by the Mobile Extension user, the call is just terminated without busy tone. If the username of Mobile Extension include a space, the call is terminated with &amp;lt;code&amp;gt;403 Forbidden&amp;lt;/code&amp;gt; by the PBX, instead to be terminated with &amp;lt;code&amp;gt;486 Busy Here&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Fixed in Version 02.07.35i19===&lt;br /&gt;
; Wrong SIP To-tag after 407: The SIP tag in &amp;quot;To:&amp;quot; Header is broken after &amp;lt;code&amp;gt;407 Proxy Authentication Required&amp;lt;/code&amp;gt; was sent from the PBX. Affects call transfer from Mobile Extension to internal user. Workaround: remove password on PBX User Object.&lt;br /&gt;
&lt;br /&gt;
===Solved by workaround===&lt;br /&gt;
; SIP Registeration Timeout : The default Registration Timeout of 600 sec. for the SIP Registration is not updated when the PBX defines another timeout in 200 OK after REGISTER. Workaround in the configuration of 2n VoiceBlue Lite: set register timeout to 120 manually.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Compat|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Switzerland_-_Swisscom_Business_Connect_-_SIP_Provider(2015)&amp;diff=80695</id>
		<title>Howto:Switzerland - Swisscom Business Connect - SIP Provider(2015)</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Switzerland_-_Swisscom_Business_Connect_-_SIP_Provider(2015)&amp;diff=80695"/>
		<updated>2026-10-14T07:12:52Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- {{FIXME|reason=in progress}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- this text is a comment that is not visible on normal view at the article. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- to create a new entry here,&lt;br /&gt;
   - fill in all sections marked as &amp;quot;by vendor&amp;quot;&lt;br /&gt;
   - innovaphone will then complete the remaining sections (marked as &amp;quot;by inno&amp;quot;)&lt;br /&gt;
  &lt;br /&gt;
  Please note that this article is in English only!&lt;br /&gt;
  feel free to ask presales in case you have any difficulties on editing wiki articles &lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   - upload your company and product logo (if any) in a suitable size (.pgn preferred)&lt;br /&gt;
   - replace images below with your logo&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
[[Image:3rdPartyGoldfischglas 03.png|right]]&lt;br /&gt;
[[Image:swisscom_logo.png|100px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   Place here Official Product Name, as used in vendors product collateral &lt;br /&gt;
   If you have a dedicated product page (not a generic vendor page) in English, also put the link below&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
[https://www.swisscom.ch/de/business/kmu/festnetz/erweiterte-telefonie/business-connect.html &#039;&#039;&#039;Business Connect&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
== Current test state ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important note:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The SIP provider test described in this article covers the product Swisscom Business Connect and was valid till 2015.&lt;br /&gt;
&lt;br /&gt;
Currently (2016), Swisscom offers a new product called Swisscom Smart Business Connect.&lt;br /&gt;
&lt;br /&gt;
In spite of the similar product name, prerequsities in terms of used hardware provided by Swisscom have changed.&lt;br /&gt;
&lt;br /&gt;
innovaphone currently is in certification process for the new product.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--{{Template:Compat Status &amp;quot;planned&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;in progress&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;engineered_prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!--{{Template:Compat_Status_&amp;quot;rec._prod.&amp;quot;|certificate=EFON_ADAPT_SIP_Provider_-_product-cert.pdf}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;tested&amp;quot;(sip provider)}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;rejected&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;referral_prod.&amp;quot;-no-certificate}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Compat Status &amp;quot;certified&amp;quot;|certificate=Swisscom_Business_Connect_-_SIP_Provider_-_product-cert.pdf}}&lt;br /&gt;
&lt;br /&gt;
Testing of this product has been finalized February, 2015.&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- by inno:&lt;br /&gt;
   - select one or more of the available recommended product categories &lt;br /&gt;
     a list of valid Categories can be found in &lt;br /&gt;
     Special Pages / Prefix Index / Display pages with prefix = RecProd, Display pages with prefix = Category &lt;br /&gt;
     (you need to apply it twice, first as template {{..}}, seconds as category [[..]])&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
{{Category:3rdParty SIP Provider}}&lt;br /&gt;
[[Category:3rdParty SIP Provider|CH - Swisscom Business Connect - SIP Provider(2015)]]&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- by inno:&lt;br /&gt;
   - version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
V11&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&lt;br /&gt;
[https://www.swisscom.ch &#039;&#039;swisscom&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://www.swisscom.ch/de/business/kmu/festnetz/erweiterte-telefonie/business-connect.html &#039;&#039;&#039;SIP Provider: swisscom Business Connect&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
The provider supports all mandatory innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]].&lt;br /&gt;
&lt;br /&gt;
That being said, the provider has achieved 86,34% of all possible test points (139 of 161). For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description|Test Description V11 and later]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note, that some features are restricted or not supported by swisscom&#039;&#039;&#039;&lt;br /&gt;
* Fax over IP is on principle not supported by swisscom&lt;br /&gt;
** The T.38 feature is not available&lt;br /&gt;
** Fax via G.711 (T.38 to G.711 / Audio Fax support) is not supported by swisscom but should work in most scenarios. This Feature is not guaranteed!&lt;br /&gt;
* Only G.711a is supported, no other codecs are supported&lt;br /&gt;
* Overlapped Sending is not supported&lt;br /&gt;
* NAT Detection is not supported&lt;br /&gt;
* Redundancy Mechanism are not supported&lt;br /&gt;
* SIP over TCP is not supported&lt;br /&gt;
&lt;br /&gt;
* Incoming Early Media Channel is not supported by default and must be requestet to swisscom.&lt;br /&gt;
* CLIP no screening does not work for &amp;quot;Trunk loop Connections&amp;quot;. This means, if you dial out to the PSTN and back to your own Trunk Number, CLNS does not work.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;swisscom doesn&#039;t support &amp;quot;Reverse Media negotiation&amp;quot;. Because of this, &amp;quot;Media-Relay&amp;quot; and an &amp;quot;Exclusive Coder Setting&amp;quot; must be configured.&#039;&#039;&#039; In contrast to a SIP trunk which does not need Media-Relay, the transport of all RTP packets across the gateway will result in a higher CPU load.&lt;br /&gt;
&lt;br /&gt;
In order to use some Features like[[Howto:How_does_CLIP_no_screening_work | Clip no screening]], some [[Howto:Swisscom_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test#Configuration|configuration]] must be done.&lt;br /&gt;
&lt;br /&gt;
Supported Features:&lt;br /&gt;
* Direct Dial In&lt;br /&gt;
* DTMF&lt;br /&gt;
* CGPN can be suppressed&lt;br /&gt;
* CLIP No Screening&lt;br /&gt;
* Reverse Media Negotiation&lt;br /&gt;
* Hold/Retrieve&lt;br /&gt;
* Blind Transfer &lt;br /&gt;
&lt;br /&gt;
Supported Codecs:&lt;br /&gt;
* G.711a only&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Howto:Swisscom_Business_Connect_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test | swisscom Test-report]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- by vendor:&lt;br /&gt;
   - add name, address, phone, fax, email, web of primary recommended sales contact&lt;br /&gt;
     if suitable, you may consider specifying several contacs, depending on your sales structure &lt;br /&gt;
     (e.g. by country or vertical market)&lt;br /&gt;
  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For further informations on this test, please contact [https://www.swisscom.ch swisscom].&lt;br /&gt;
&lt;br /&gt;
[[Category:Compat|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Swisscom_Business_Connect_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test&amp;diff=80694</id>
		<title>Howto:Swisscom Business Connect - SIP Trunk - SIP Provider Compatibility Test</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Swisscom_Business_Connect_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test&amp;diff=80694"/>
		<updated>2026-10-14T07:12:26Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Innovaphone Compatibility Test Report&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;SIP Provider: swisscom Business Connect&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The provider supports all mandatory innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F#SIP_Provider|recommended SIP Provider]].&lt;br /&gt;
&lt;br /&gt;
That being said, the provider has achieved 86,34% of all possible test points (139 of 161). For more information on the test rating, please refer to [[Howto:SIP_Interop_Test_Description|Test Description V11 and later]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note, that some features are restricted or not supported by swisscom&#039;&#039;&#039;&lt;br /&gt;
* Fax over IP is on principle not supported by swisscom&lt;br /&gt;
** The T.38 feature is not available&lt;br /&gt;
** Fax via G.711 (T.38 to G.711 / Audio Fax support) is not supported by swisscom but should work in most scenarios. This Feature is not guaranteed!&lt;br /&gt;
* Only G.711a is supported, no other codecs are supported&lt;br /&gt;
* Overlapped Sending is not supported&lt;br /&gt;
* NAT Detection is not supported&lt;br /&gt;
* Redundancy Mechanism are not supported&lt;br /&gt;
* SIP over TCP is not supported&lt;br /&gt;
&lt;br /&gt;
* Incoming Early Media Channel is not supported by default and must be requestet to swisscom.&lt;br /&gt;
* CLIP no screening does not work for &amp;quot;Trunk loop Connections&amp;quot;. This means, if you dial out to the PSTN and back to your own Trunk Number, CLNS does not work.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;swisscom doesn&#039;t support &amp;quot;Reverse Media negotiation&amp;quot;. Because of this, &amp;quot;Media-Relay&amp;quot; and an &amp;quot;Exclusive Coder Setting&amp;quot; must be configured.&#039;&#039;&#039; In contrast to a SIP trunk which does not need Media-Relay, the transport of all RTP packets across the gateway will result in a higher CPU load.&lt;br /&gt;
&lt;br /&gt;
In order to use some Features like[[Howto:How_does_CLIP_no_screening_work | Clip no screening]], some [[Howto:Swisscom_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test#Configuration|configuration]] must be done.&lt;br /&gt;
&lt;br /&gt;
Supported Features:&lt;br /&gt;
* Direct Dial In&lt;br /&gt;
* DTMF&lt;br /&gt;
* CGPN can be suppressed&lt;br /&gt;
* CLIP No Screening&lt;br /&gt;
* Reverse Media Negotiation&lt;br /&gt;
* Hold/Retrieve&lt;br /&gt;
* Blind Transfer &lt;br /&gt;
&lt;br /&gt;
Supported Codecs:&lt;br /&gt;
* G.711a only&lt;br /&gt;
&lt;br /&gt;
== Current test state ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;in progress&amp;quot;}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;planned&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;referral_prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;engineered_prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;rec._prod.&amp;quot;|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;tested&amp;quot;(sip provider)}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat Status &amp;quot;rejected&amp;quot;}} --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Template:Compat_Status_&amp;quot;referral_prod.&amp;quot;-no-certificate}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Compat Status &amp;quot;certified&amp;quot;|certificate=Swisscom_Business_Connect_-_SIP_Provider_-_product-cert.pdf}}&lt;br /&gt;
&lt;br /&gt;
Testing of this product has been finalized February 2015.&lt;br /&gt;
&lt;br /&gt;
== Testing Enviroment ==&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestTopology1.png]]&lt;br /&gt;
&lt;br /&gt;
This scenario describes a setup where the PBX and phones are in a private network.&lt;br /&gt;
&lt;br /&gt;
The swisscom is providing an own Gateway (&amp;quot;Connect Box&amp;quot; or &amp;quot;Patton Smart Node&amp;quot;) which must be located in the customers private network. This Gateway has two connections:&lt;br /&gt;
* One connection to swisscom&lt;br /&gt;
* One connection to the PBX &lt;br /&gt;
Because of this, the SIP Trunk does not connect directly to the internet, but to the swisscom Gateway (&amp;quot;Connect Box&amp;quot; or &amp;quot;Patton Smart Node&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The SIP trunk must be configured with &amp;quot;Media Relay&amp;quot;, &amp;quot;exclusive G.711a&amp;quot; and &amp;quot;NO T.38&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
[[Howto:Swisscom_-_SIP_Trunk_-_SIP_Provider_Compatibility_Test#Configuration|See configuration]]&lt;br /&gt;
&lt;br /&gt;
== Test Results ==&lt;br /&gt;
&lt;br /&gt;
For more information on the test procedure, please read the following wiki article: [[Howto:SIP_Interop_Test_Description_v11#|Test Description V11 and later]]. Bold lines in the test results indicate a KO-criteria.&lt;br /&gt;
&lt;br /&gt;
(*1) To use Incoming Early Media Channel, this feature must be requested to swisscom. Per default, it&#039;s not possible.&lt;br /&gt;
&lt;br /&gt;
(*2) Fax via G.711 (T.38 to G.711 / Audio Fax support) is not supported by swisscom but should work in most scenarios. This Feature is not guaranteed!&lt;br /&gt;
&lt;br /&gt;
(*3) CLIP no screening does not work for &amp;quot;Trunk loop Connections&amp;quot;. This means, if you dial out to the PSTN and back to your own Trunk Number, CLNS does not work in this case. &lt;br /&gt;
&lt;br /&gt;
=== Basic Call ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;call using g711a&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;call using g711u&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;NOK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|call using g723&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|call using g729&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|call using g722&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|Overlapped sending&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;early media channel outgoing&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|early media channel incoming&lt;br /&gt;
|OK/NOK (*1)&lt;br /&gt;
|----&lt;br /&gt;
|Fax using T.38&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|T.38 Transcoding by the provider&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|Fax using G.711&lt;br /&gt;
|OK (*2)&lt;br /&gt;
|----&lt;br /&gt;
|Reverse Media Negotiation&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|CGPN can be suppressed&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|CLIP no screening&lt;br /&gt;
|OK (*3)&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Long time call possible(&amp;gt;30 min)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;External Transfer&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|NAT Detection&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|Redundancy&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|SIP over TCP&lt;br /&gt;
|NA&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Voice Quality OK?&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Direct Dial In ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Inbound(Provider -&amp;gt; Innovaphone)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Outbound(Innovaphone -&amp;gt; Provider)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Loop In call(Innovaphone -&amp;gt; Provider -&amp;gt; Innovaphone)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK (*3)&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== DTMF ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;DTMF tones sent correctly via RTP-events(RFC 2833)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|DTMF tones sent correctly via SIP-Info&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;DTMF tones received correctly via RTP-events(RFC 2833)&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hold/Retrieve ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be put on hold&#039;&#039;&#039; &lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold / announcement from PBX&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Transfer with consultation ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be transferred&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
!MoH Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Transfer with consultation (alerting only) ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be transferred&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears music on hold or dialling tone&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call returns to transferring device if the third&#039;&#039;&#039; &lt;br /&gt;
&#039;&#039;&#039;Endpoint is not available&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
!MoH Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Blind Transfer ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|Call can be transferred&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|Held end hears dialling tone&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== CFU / CFB Transfer ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be forward&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Held end hears dialling tone&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== CFNR / Blind Transfer (alerting only)===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Call can be transferred or forward&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Held end hears dialling tone&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following tests are made to test if call transfer is working.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Voice Ok?&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls inno2. inno2 transfers to PSTN-phone.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|inno1 calls PSTN-phone. PSTN-phone transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to inno2.&lt;br /&gt;
|OK&lt;br /&gt;
|----&lt;br /&gt;
|PSTN-phone calls inno1. inno1 transfers to other PSTN-phone-2.&lt;br /&gt;
|OK&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Broadcast Group &amp;amp; Waiting Queue ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; &lt;br /&gt;
!Tested feature&lt;br /&gt;
!Result &lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Caller can make a call to a Broadcast Group&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Caller can make a call to a Waiting Queue&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|----&lt;br /&gt;
|&#039;&#039;&#039;Announcement if nobody picks up the call&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;OK&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
===Firmware version===&lt;br /&gt;
&lt;br /&gt;
All innovaphone devices use V11 build 11.0828 as firmware during test.&lt;br /&gt;
&lt;br /&gt;
=== SIP - Trunk ===&lt;br /&gt;
Following configuration needs to be done in the SIP Gateway Interface settings:&lt;br /&gt;
&lt;br /&gt;
* 1: Enter your phonenumber and private IP address of swisscom Gateway (&amp;quot;Connect Box&amp;quot; or &amp;quot;Patton Smart Node&amp;quot;) with port 5062!&lt;br /&gt;
* 2: Enter credendtials&lt;br /&gt;
* 3: Select G.711a exclusive&lt;br /&gt;
* 4: Disable T.38 and Enable Media Relay&lt;br /&gt;
* 5: Disable encryption&lt;br /&gt;
* 6: Use &amp;quot;CGPN in user part of URI&amp;quot; in &amp;quot;From Header&amp;quot; and &amp;quot;Fixed AOR&amp;quot; in &amp;quot;Identity Header&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig1.png]]&lt;br /&gt;
&lt;br /&gt;
=== Number Mapping ===&lt;br /&gt;
Following configuration needs to be done in the SIP Gateway Number Mappings:&lt;br /&gt;
&lt;br /&gt;
* 1: Add &amp;quot;00&amp;quot; to incoming CGPNs without a leading &amp;quot;0&amp;quot; because international numbers are coming in like &amp;quot;49703173009&amp;quot;.&lt;br /&gt;
* 2: Because swisscom is using the full national number for incoming calls, you need to cut off the digits before an extension. In example, 04333693xx will be translated to xx.&lt;br /&gt;
* 3: In case of call forwardings, you need to cut off the single leading &amp;quot;0&amp;quot; (national calls) and translate a leading &amp;quot;000&amp;quot; (international calls) to &amp;quot;+&amp;quot; in the CGPN Out map.&lt;br /&gt;
* 4: In the CGPN Out map, you also need to translate the extensions to the national number format. In example, xx will be translated to 04333693xx.&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig2.png]]&lt;br /&gt;
&lt;br /&gt;
=== Route Settings ===&lt;br /&gt;
A default Route Setup is used:&lt;br /&gt;
&lt;br /&gt;
* 1: Force Enblock Setting is required for outgoing calls.&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig3.png]]&lt;br /&gt;
&lt;br /&gt;
=== Fax ===&lt;br /&gt;
&#039;&#039;&#039;swisscom does not support any Fax communications.&#039;&#039;&#039; Because of this, T.38 can not be used.&lt;br /&gt;
&lt;br /&gt;
If you want to use Fax even so, you need to set T.38 to G.711 translation (Audio Fax support, available from V11). This works in a lot of cases where you have no problems with QoS. &#039;&#039;&#039;But it&#039;s not guaranteed and swisscom gives no support in case of problems!&#039;&#039;&#039;  &lt;br /&gt;
&lt;br /&gt;
Example to set T.38 to G.711 translation (Audio Fax support) on the Faxserver interface:&lt;br /&gt;
&lt;br /&gt;
[[Image:swisscomSIPProviderTestConfig4.png]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Compat|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Configure_Mobility_for_use_with_Opticaller&amp;diff=80691</id>
		<title>Howto:Configure Mobility for use with Opticaller</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Configure_Mobility_for_use_with_Opticaller&amp;diff=80691"/>
		<updated>2026-10-14T07:09:11Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Note: The third-party product mentioned here is no longer available and the content of the article may be outdated.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;OptiCaller&#039;&#039; software is used for easy access to the mobility functions of V9 PBX from Mobile phones.&lt;br /&gt;
&lt;br /&gt;
==Applies To==&lt;br /&gt;
This information applies to&lt;br /&gt;
&lt;br /&gt;
*innovaphone PBX V9 hotfix2 or later&lt;br /&gt;
*OptiCaller Version 2.0.6&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
===Requirements===&lt;br /&gt;
&lt;br /&gt;
==== On the PBX ====&lt;br /&gt;
* [http://download.innovaphone.com/ice/9.00/#firmware Firmware V9 hotfix2 or later]&lt;br /&gt;
* &#039;&#039;Mobility-9&#039;&#039; Licenses installed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== PBX Configuration  ===&lt;br /&gt;
&lt;br /&gt;
The following configurations must be done on the PBX&lt;br /&gt;
* Creation of the [[Reference9:PBX/Objects/Mobility |mobility objects]]&lt;br /&gt;
* Creation of the [[Reference9:PBX/Objects/DTMF Features | DTMF features objects ]]&lt;br /&gt;
* Installation of proper Mobility9 licenses&lt;br /&gt;
* Attribution of the respective [[Reference9:PBX/Objects/Edit Forks | user forking entries ]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Numbering Plan ====&lt;br /&gt;
Mobility is based on a number of feature codes which are used by the mobile phone to access the features.  These codes are in fact objects in the PBX (Mobility and DTMF-Feature) which need to be called.  As a result, these feature codes each require individual extensions in the PBX&#039;s numbering plan.  To make things worse, the GSM network does not carry * or # digits in a called number, so the extensions to be used&lt;br /&gt;
must be plain numbers.&lt;br /&gt;
&lt;br /&gt;
You will need to reserve a number of extensions with a common prefix thus in your PBX&#039;s numbering plan.  If this is not possible (e.g. because you reside in a country with a fixed numbering plan and you&lt;br /&gt;
don&#039;t have a block large enough to allocate the numbers), you may revert to use a single extension in your numbering plan.&lt;br /&gt;
&lt;br /&gt;
Be aware though that this will result in&lt;br /&gt;
* cost charged by your mobile operator for invoking features (some of the features are normally invoked by calling an extension without accepting the call, which should be free.  When using a single extension, all features are invoked by calling this number, accepting the call and then dialling the desired feature using in-band DTMF tones)&lt;br /&gt;
* longer execution time for most of the features invoked&lt;br /&gt;
&lt;br /&gt;
You need thus determine an available prefix for the feature codes within you PBX&#039;s numbering plan (say &amp;lt;code&amp;gt;54&amp;lt;/code&amp;gt;).  &lt;br /&gt;
For the remainder of this article, we will refer to this prefix as &#039;&#039;mobility-prefix&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==== Mobility Object ====&lt;br /&gt;
There must be a mobility object on each PBX system with a mobility enabled user (that is, a user with an integrated mobile phone).  The easiest way to achieve this is to create a mobility object with &#039;&#039;Node&#039;&#039;&lt;br /&gt;
and &#039;&#039;PBX&#039;&#039; left empty.&lt;br /&gt;
&lt;br /&gt;
However, if there is only a single PBX that hosts mobility enabled users, you simply put the (single) mobility object into the &amp;lt;code&amp;gt;root&amp;lt;/code&amp;gt; node.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;Number&#039;&#039; property of the mobility object must be set to the &#039;&#039;mobility-prefix&#039;&#039; chosen plus literal &amp;lt;code&amp;gt;9&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
This will result in one mobility object per PBX which has the PBX&#039;s node number as a prefix. Assuming the PBX&#039;s node number is &amp;lt;code&amp;gt;81&amp;lt;/code&amp;gt;, the full number of the mobility object in our example would be &amp;lt;code&amp;gt;81549&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
[[Image:Mobility Prefix 01.png]]&lt;br /&gt;
&lt;br /&gt;
==== DTMF-Features Object ====&lt;br /&gt;
Again, there must be a DTMF-Features object on each PBX system with a mobility enabled user (that is, a user with an integrated mobile phone).  The easiest way to achieve this is to create a DTMF-Features object with &#039;&#039;Node&#039;&#039; and &#039;&#039;PBX&#039;&#039; left empty.&lt;br /&gt;
&lt;br /&gt;
The DTMF-Features object itself does not have a &#039;&#039;Number&#039;&#039; property.  Instead, the individual features have one.  The features must have fixed numbers according to the following table:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| CFU Activate || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;10$#&amp;lt;/code&amp;gt; || Deactivate || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;11&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| CFB Activate || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;12$#&amp;lt;/code&amp;gt; || Deactivate || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;13&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| CFNR Activate || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;14$#&amp;lt;/code&amp;gt; || Deactivate || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;15&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Pickup Group || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;16&amp;lt;/code&amp;gt; || Directed || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;17$#&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Park || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;18$&amp;lt;/code&amp;gt; || Unpark || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;19$&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Park To || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;20$(1)$#&amp;lt;/code&amp;gt; || Unpark From || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;21$(1)$#&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Call Completion Busy || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;22$#&amp;lt;/code&amp;gt; || Cancel || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;23$#&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Join Group || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;24$#&amp;lt;/code&amp;gt; || Leave    || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;25$#&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Join All Groups || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;26&amp;lt;/code&amp;gt; || Leave || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;27&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Enable mobility || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;28&amp;lt;/code&amp;gt; || Disable mobility || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;29&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Enable mobility cw || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;30&amp;lt;/code&amp;gt; || Disable mobility cw || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;31&amp;lt;/code&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Set presence || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;32$(1)$(1)&amp;lt;/code&amp;gt; || Unset presence || &#039;&#039;mobility-prefix&#039;&#039;&amp;lt;code&amp;gt;33$(1)&amp;lt;/code&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In our example, the list of mobility related objects should look like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DTMF-Features#call_completion     81.5422&lt;br /&gt;
DTMF-Features#cancel_cc           81.5423&lt;br /&gt;
DTMF-Features#cfb_activate        81.5412&lt;br /&gt;
DTMF-Features#cfb_deactivate      81.5413&lt;br /&gt;
DTMF-Features#cfnr_activate       81.5414&lt;br /&gt;
DTMF-Features#cfnr_deactivate     81.5415&lt;br /&gt;
DTMF-Features#cfu_activate        81.5410&lt;br /&gt;
DTMF-Features#cfu_deactivate      81.5411&lt;br /&gt;
DTMF-Features#disable_mobility    81.5429&lt;br /&gt;
DTMF-Features#disable_mobility_cw 81.5431&lt;br /&gt;
DTMF-Features#enable_mobility     81.5428&lt;br /&gt;
DTMF-Features#enable_mobility_cw  81.5430&lt;br /&gt;
DTMF-Features#join_all_groups     81.5426&lt;br /&gt;
DTMF-Features#join_group          81.5424&lt;br /&gt;
DTMF-Features#leave_all_groups    81.5427&lt;br /&gt;
DTMF-Features#leave_group         81.5425&lt;br /&gt;
DTMF-Features#park                81.5418&lt;br /&gt;
DTMF-Features#park_to             81.5420&lt;br /&gt;
DTMF-Features#pickup_directed     81.5417&lt;br /&gt;
DTMF-Features#pickup_group        81.5416&lt;br /&gt;
DTMF-Features#set_presence        81.5432&lt;br /&gt;
DTMF-Features#unpark              81.5419&lt;br /&gt;
DTMF-Features#unpark_from         81.5421&lt;br /&gt;
DTMF-Features#unset_presence      81.5433&lt;br /&gt;
Mobility                          81.549&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Users ====&lt;br /&gt;
To enable mobility for a user, you need to &lt;br /&gt;
* make sure you have &#039;&#039;Mobility-9&#039;&#039;  license available.  As usual, test licenses are available from within [http://my.innovaphone.com  my.innovaphone]&lt;br /&gt;
* add a forking destination for each mobile phone the user wants to use with mobility&lt;br /&gt;
* make the users mobile phone numbers known to the system&lt;br /&gt;
&lt;br /&gt;
Put the phone&#039;s number into the &#039;&#039;No&#039;&#039; property.  This number must be specified exactly as it would be received by the PBX when this phone calls in.  That is, it is the number including GSM carrier prefix and  trunk prefix, no country code, no &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt;.  Assuming the users mobile number is &amp;lt;code&amp;gt;017247110815&amp;lt;/code&amp;gt; and the trunk line prefix in your PBX is &amp;lt;code&amp;gt;0&amp;lt;/code&amp;gt;, you would specify &amp;lt;code&amp;gt;0017247110815&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
[[Image:Mobility Fork Configuration 1.png]]&lt;br /&gt;
&lt;br /&gt;
=== Configuration in the Opticaller Mobile Provisioning Portal ===&lt;br /&gt;
&lt;br /&gt;
The the &#039;&#039;mobility-prefix&#039;&#039; (if any used) must be provided under &#039;&#039;MEX Functions&#039;&#039;, &#039;&#039;Function 2&#039;&#039;. In our example it will be &amp;lt;code&amp;gt;54&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The number of VoiceMail Object must be provided under &#039;&#039;MEX Functions&#039;&#039;, &#039;&#039;Function 1&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Functions Configuration:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Opticaller Mobile Provisioning Mex Configuration 1.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mex Buttons List:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Opticaller Mobile Provisioning Mex Configuration 0.png]]&lt;br /&gt;
&lt;br /&gt;
=== Phone Installation ===&lt;br /&gt;
&lt;br /&gt;
Refer to OptiCaller UserManual.&lt;br /&gt;
&lt;br /&gt;
==== Setting CLIR on the Mobile Phone ====&lt;br /&gt;
The phone must identify itself to the PBX as a legible mobile device by providing the proper calling line ID.  As a result, the phone &#039;&#039;must not be set into a CLIR (calling line identification restriction) mode&#039;&#039; as it will be rejected by the PBX then and no outgoing call through the PBX will thus be possible.  &lt;br /&gt;
&lt;br /&gt;
==== Disabling mobile Carrier based Absence Message ====&lt;br /&gt;
Many mobile carriers will terminate calls to your mobile phone even though it is not reachable, for example because it is busy, not registered with the provider, switched off etc.  This will happen for example if you have set a call forward (e.g. towards your mobile voice mail).  But even if you have not set such a call forward, your carrier may terminate the call and play a message such as &amp;quot;The user is currently unavailable, do you want to be notified ...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
With mobility, this behaviour is evil.  When your extension is called and the PBX forks the call to your mobile and the mobile is unavailable, the mobile carrier will take the call right away.  To the PBX, the call is connected then and it will assume it was delivered to you successfully.  In other words, you have no chance to take the call on your fixed phone.  Also, if the PBX is configured to handle calls which cannot be delivered (e.g. by forwarding them to the switchboard operator or your PBX mailbox), this handling will not happen as the PBX assumes the call to be taken by you.   For these reasons it is mandatory that you &#039;&#039;disable these mobile carrier features all together&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
Unfortunately, there is no standard procedure to do so.  You need to inquire with your mobile carrier.  As an example, vodafone in Germany requires you to [http://www.vodafone.de/business/firmenkunden/anruf-info.html#ID130607 call a hotline number] in order to disable what they call the &#039;&#039;Vodafone Anruf-Info&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=== OptiCaller UI Language ===&lt;br /&gt;
You can provide your own language.  This is down by providing the different configuration templates in the OptiCaller Mobile Provisioning Portal. E.g. to use German Lanuage on the OptiCaller assign &#039;&#039;innovaphone CDPN DE&#039;&#039; config tempalte to the user.&lt;br /&gt;
&lt;br /&gt;
=== Working with fixed Numbering Plans ===&lt;br /&gt;
The dial plan used for the mobility and DTMF features objects assumes that you have an open numbering plan, that is, that you are able to call in to your PBX from the mobile to extensions of different length.  For example, in our example these all share the common prefix &amp;lt;code&amp;gt;54&amp;lt;/code&amp;gt;.  The mobility object&#039;s extension thus is &amp;lt;code&amp;gt;549&amp;lt;/code&amp;gt;, the extension of the &#039;&#039;join all groups&#039;&#039; DTMF feature is &amp;lt;code&amp;gt;5426&amp;lt;/code&amp;gt;.  &lt;br /&gt;
&lt;br /&gt;
In some countries however, the numbering plan is fixed, that is, it is not possible to call extensions of different length.  If this is the case, you can create a configuration that only uses a single extension in your numbering plan for all mobility functions (see [[Howto:Configure_Mobility_for_use_with_Opticaller#Numbering_Plan | &#039;&#039;Numbering Plan&#039;&#039; ]] above).&lt;br /&gt;
&lt;br /&gt;
==== Additional Configuration in the PBX ====&lt;br /&gt;
In this case, you would configure the PBX objects as described.  In addition, you would create a PBX [[Reference8:Administration/Relay/Routes/Map | MAP object ]] which maps the externally visible extension you choose for mobility to the number configured for the mobility object.  In our example, where the mobility object has extension &amp;lt;code&amp;gt;549&amp;lt;/code&amp;gt;, assuming your numbering plan is 2-digit (-00 to -99) and you have chosen extension &amp;lt;code&amp;gt;99&amp;lt;/code&amp;gt;, you would create a MAP which maps &amp;lt;code&amp;gt;99&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;549&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
In case of multiple PBXes, you have also multiple Mobility objects with numbers containing PBX prefix, like 80.549 and 81.549 etc. Therefore multiple MAP objects must be created for every combination of externally visible extension and PBX prefix + Mobility object.&lt;br /&gt;
&lt;br /&gt;
==== Additional Configuration in the OptiCaller Mobile Provisioning Portal====&lt;br /&gt;
On the OptiCaller Provisioning Portal you have to use &#039;&#039;innovaphone DTMF&#039;&#039; configuration templates instead of &#039;&#039;innovaphone CDPN&#039;&#039; templates, to use all PBX Features via DTMF.&lt;br /&gt;
&lt;br /&gt;
===CallTrough initiation via Data/HTTP Request===&lt;br /&gt;
With CallThrough feature of the OptiCaller it is possible to initiate a CallThrough from PBX to Mobility Device via simple GET or POST request, in order to speed up call setup, since the dialed number is transmitted from OptiCaller to the PBX via a HTTP request, and not via DTMF.&lt;br /&gt;
&lt;br /&gt;
In case CallTrough via Data is used, following must be considered:&lt;br /&gt;
&lt;br /&gt;
*IP connection from OptiCaller to PBX for HTTP Requests&lt;br /&gt;
*Additional configuration in Provisioning Portal required&lt;br /&gt;
*Introduced in innovaphone V9 hotfix21 Firmware&lt;br /&gt;
&lt;br /&gt;
==== Direct HTTP CallTrough request to the innovaphone PBX ====&lt;br /&gt;
&lt;br /&gt;
We need to set:&lt;br /&gt;
&lt;br /&gt;
* Public IP address with NAT configured to the HTTPS port of the PBX (i.e: 145.x.x.x:35000 mapped to 192.168.x.x:443 TCP)&lt;br /&gt;
* At OptiCaller Calltrough DATA Settings we must configure: &lt;br /&gt;
** Public IP address and port configured before.&lt;br /&gt;
** HTTP GET Method&lt;br /&gt;
** User Data with Name of the user object and password too.&lt;br /&gt;
** Server URL : &amp;lt;code&amp;gt;http://x.x.x.x:80&amp;lt;/code&amp;gt;&lt;br /&gt;
** Data Handler: &amp;lt;code&amp;gt;PBX0/ADMIN/mod_cmd_login.xml?&amp;lt;/code&amp;gt;&lt;br /&gt;
** Data Format: &amp;lt;code&amp;gt;cmd=makecall&amp;amp;req=callthru&amp;amp;name=/*u*/&amp;amp;e164=/*b*/&amp;amp;hw=opticaller(Mobility device)&amp;lt;/code&amp;gt; (see here [[Howto:Initiate_a_Mobility_CallBack_via_simple_HTTP_GET_or_POST_request#Method_1:_HTTP_GET_Request|more about URL parameters]])&lt;br /&gt;
* Device name at Call Fork configuration should be &amp;quot;opticaller&amp;quot; (equal to the &amp;lt;code&amp;gt;hw&amp;lt;/code&amp;gt;). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: The option &amp;quot;name&amp;quot; refers to the Name on User Object and not the Long Name. If you want to use an HTTPS connection use the Server URL: https://x.x.x.x:443 instead, if you have problems regarding the use of HTTPs with Opticaller it&#039;s recommended to use Certificates with 5-10 Years period and not more (the default Gateways Certificates have more than 30 years period so you should create a new one or buy one to use it).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For HTTP Authentication following must be configured:&lt;br /&gt;
&lt;br /&gt;
* At OptiCaller User Phone Settings, under PRO Details&lt;br /&gt;
** define User Name - this is a Name (short, not Long Name) of the PBX User Object with [[Reference9:PBX/Objects/Edit Rights|Access Rights for PBX Administration]]. Usually &#039;&#039;Groups/Call Forwards only&#039;&#039; will be OK.&lt;br /&gt;
** define password of this PBX User Object. At innovaphone PBX user object should have password defined.&lt;br /&gt;
** Make sure the option &amp;quot;Disable HTTP basic authentication&amp;quot; at Services-&amp;gt;HTTP it&#039;s not enable!&lt;br /&gt;
&lt;br /&gt;
===CallBack via DATA===&lt;br /&gt;
With CallBack feature of the OptiCaller it is possible to initiate a CallBack from PBX to Mobility Device via simple GET or POST request.&lt;br /&gt;
&lt;br /&gt;
In case CallBack is used, following must be considered:&lt;br /&gt;
&lt;br /&gt;
*External HTTP connection to PBX or HTTP to SOAP converter needed ( more secure solution )&lt;br /&gt;
*Additional configuration in Provisioning Portal required&lt;br /&gt;
*OptiCaller PRO License is required (no CallBack support in MEX)&lt;br /&gt;
&lt;br /&gt;
==== Direct HTTP Callback request to the Innovaphone PBX ====&lt;br /&gt;
&lt;br /&gt;
We need to set:&lt;br /&gt;
&lt;br /&gt;
* Public IP address with NAT configured to the HTTPS port of the PBX (i.e: 145.x.x.x:35000 mapped to 192.168.x.x:443 TCP)&lt;br /&gt;
* At OptiCaller Callback Settings we must configure: &lt;br /&gt;
** Public IP address and port configured before.&lt;br /&gt;
** HTTP GET Method&lt;br /&gt;
** SSL option&lt;br /&gt;
** User Data with Long Name of the user object and password too.&lt;br /&gt;
** Data Handler: &amp;lt;code&amp;gt;PBX0/ADMIN/pbx_makecall.txt?&amp;lt;/code&amp;gt;&lt;br /&gt;
** Data Format: &amp;lt;code&amp;gt;cn=/*u*/&amp;amp;e164=/*b*/&amp;amp;hw=opticaller&amp;lt;/code&amp;gt;  (see here [[Howto:Initiate_a_Mobility_CallBack_via_simple_HTTP_GET_or_POST_request#Method_1:_HTTP_GET_Request|more about URL parameters]])&lt;br /&gt;
* Device name at Call Fork configuration should be &amp;quot;opticaller&amp;quot; (equal to the &amp;lt;code&amp;gt;hw&amp;lt;/code&amp;gt;). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: The option &amp;quot;name&amp;quot; refers to the Name on User Object and not the Long Name. If you have problems regarding the use of HTTPs with Opticaller it&#039;s recommended to use Certificates with 5-10 Years period and not more (the default Gateways Certificates have more than 30 years period so you should create a new one or buy one to use it).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For HTTP Authentication following must be configured:&lt;br /&gt;
&lt;br /&gt;
* At OptiCaller User Phone Settings, under PRO Details&lt;br /&gt;
** define User Name - this is a Name (short, not Long Name) of the PBX User Object with [[Reference9:PBX/Objects/Edit Rights|Access Rights for PBX Administration]]. Usually &#039;&#039;Groups/Call Forwards only&#039;&#039; will be OK.&lt;br /&gt;
** define password of this PBX User Object. At innovaphone PBX user object should have password defined.&lt;br /&gt;
** Make sure the option &amp;quot;Disable HTTP basic authentication&amp;quot; at Services-&amp;gt;HTTP it&#039;s not enable!&lt;br /&gt;
&lt;br /&gt;
==== HTTP to SOAP converter(Optional)====&lt;br /&gt;
A middleware could be used to convert HTTP CallBack requests from OptiCaller to the SOAP requests for PBX. A [[Howto:Initiate_a_Mobility_CallBack_via_simple_HTTP_GET_or_POST_request|sample PHP script is available]] on the innovaphone download page.&lt;br /&gt;
&lt;br /&gt;
Note: This is a good solution to install in the webserver and prevent direct HTTP External access to the PBX for security reasons. However, if no HTTP Server with PHP is available,&lt;br /&gt;
Direct HTTP Callback request to the Innovaphone PBXis also supported (see above).&lt;br /&gt;
&lt;br /&gt;
====Additional configuration in Provisioning Portal====&lt;br /&gt;
Following must be configured in the OptiCaller Mobile Provisioning Portal:&lt;br /&gt;
&lt;br /&gt;
*Configuration, Pro Features&lt;br /&gt;
**&#039;&#039;&#039;IP Address&#039;&#039;&#039; and &#039;&#039;&#039;Port&#039;&#039;&#039; of the PBX HTTP interface&lt;br /&gt;
**&#039;&#039;&#039;Data Method&#039;&#039;&#039; POST&lt;br /&gt;
**&#039;&#039;&#039;Data Handler&#039;&#039;&#039; &amp;lt;code&amp;gt;mobility.php&amp;lt;/code&amp;gt;&lt;br /&gt;
**&#039;&#039;&#039;Data Format&#039;&#039;&#039; &amp;lt;code&amp;gt;cn=/*u*/&amp;amp;e164=/*b*/&amp;amp;hw=opticaller&amp;lt;/code&amp;gt; where &amp;lt;code&amp;gt;opticaller&amp;lt;/code&amp;gt; is Device name used in the PBX on Mobility Fork destination&lt;br /&gt;
*for each User and Phone under &#039;&#039;&#039;PRO Details&#039;&#039;&#039;&lt;br /&gt;
**&#039;&#039;&#039;User Name&#039;&#039;&#039; must be configured. You may use this User Name (and Password) to authenticate against PBX (sample PHP script changes required).&lt;br /&gt;
&lt;br /&gt;
=== Debugging ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Known Problems===&lt;br /&gt;
&lt;br /&gt;
* Mobile phone always gets &#039;&#039;busy&#039;&#039; for outgoing calls through the PBX&lt;br /&gt;
&lt;br /&gt;
The phone most likely fails to identify itself properly.  This happens if the phone&#039;s number in the users &#039;&#039;Fork&#039;&#039; entry is incorrect (e.g. trunk prefix missing) or the phone is set to hide its own number (CLIR) on outgoing calls.&lt;br /&gt;
&lt;br /&gt;
* Setting Call Forward on iPhone is not possible&lt;br /&gt;
&lt;br /&gt;
This should be fixed in the next version of OptiCaller for iPhone.&lt;br /&gt;
&lt;br /&gt;
* Wrong DTMF sequences received by PBX while Call Through on iPhone with radio reception&lt;br /&gt;
&lt;br /&gt;
An update to iOS 4.3 could improve the DTMF transmission, but only CallBack is a reliable option.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
*[[Howto:Initiate a Mobility CallBack via simple HTTP GET or POST request]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Integration_of_CTI_in_Novell_Groupwise&amp;diff=80688</id>
		<title>Howto:Integration of CTI in Novell Groupwise</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Integration_of_CTI_in_Novell_Groupwise&amp;diff=80688"/>
		<updated>2026-10-14T07:07:06Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;FAQ:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At a new project, we have to guarantee the Integration of CTI in Novell Groupwise 7.0 (or higher). Netware 6.5 is used as operating system. The customer also demands that the user administration is done by using Novell&#039;s E-Directory. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Answer:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This can be realised with &amp;quot;caesar® unified messaging&amp;quot; from CAE Elektronik GmbH. The contact person at CAE is Klaus Tophoven. For more information use the link below.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
&lt;br /&gt;
* [[Howto:CAESAR_Unified_Communication_-_CASERISGmbH_-_3rd_Party_Product |Caesar® unified messaging]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Faq|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:SIPS_will_work_with_V7&amp;diff=80686</id>
		<title>Howto:SIPS will work with V7</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:SIPS_will_work_with_V7&amp;diff=80686"/>
		<updated>2026-10-14T07:03:44Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Related Articles */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Applies To==&lt;br /&gt;
&lt;br /&gt;
This information applies to&lt;br /&gt;
&lt;br /&gt;
* all innovaphone devices with V7&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: secure sip, sip-s,srtp,aes, tls--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
This information is for future release and describes baisicly how we will implement secure sip.&lt;br /&gt;
&lt;br /&gt;
This information is not confirmed now it is an basic overview how we will implement SIPS.&lt;br /&gt;
&lt;br /&gt;
Secure SIP is a security mechanism defined by SIP RFC 3261 for sending SIP messages over a Transport Layer Security-encrypted channel. &lt;br /&gt;
&lt;br /&gt;
Originally used for securing HTTP sessions, TLS can be repurposed to protect SIP session communications from eavesdropping or tampering. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Key exchange===&lt;br /&gt;
&lt;br /&gt;
In an SDP message we will send an attribute like this&lt;br /&gt;
&lt;br /&gt;
 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:fcUai9fK58dEKsmEQp4b5nylUROLpze0jLVyaE5i&lt;br /&gt;
&lt;br /&gt;
This menas that SRTP will be used with AES-128 using a 32 Bit hash and the key fcUai9fK58dEKsmEQp4b5nylUROLpze0jLVyaE5i. &lt;br /&gt;
&lt;br /&gt;
The whole SDP message will be sent encryped via TLS to protect the key.&lt;br /&gt;
&lt;br /&gt;
===SRTP===&lt;br /&gt;
&lt;br /&gt;
innovaphone will support&lt;br /&gt;
&lt;br /&gt;
AES-128&lt;br /&gt;
&lt;br /&gt;
AES-192&lt;br /&gt;
&lt;br /&gt;
AES-256 &lt;br /&gt;
&lt;br /&gt;
all with 32 or 80 bit SHA1 hashed message authentication codes (HMAC).&lt;br /&gt;
&lt;br /&gt;
===SIPS===&lt;br /&gt;
&lt;br /&gt;
Sips means SIP via TLS - we will implement SIP via TCP and TLS&lt;br /&gt;
&lt;br /&gt;
===TLS===&lt;br /&gt;
&lt;br /&gt;
innovaphone will support&lt;br /&gt;
&lt;br /&gt;
RSA with 3DES&lt;br /&gt;
&lt;br /&gt;
RSA with AES-128&lt;br /&gt;
&lt;br /&gt;
RSA with AES-256&lt;br /&gt;
&lt;br /&gt;
all with SHA1 hashes.&lt;br /&gt;
&lt;br /&gt;
===Certificates===&lt;br /&gt;
&lt;br /&gt;
We support X.509 certificates with RSA keys and SHA1/MD5 signatures.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
[[Reference16r1:Certificate_management]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:Feature_List_in_English&amp;diff=80685</id>
		<title>Howto:Feature List in English</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:Feature_List_in_English&amp;diff=80685"/>
		<updated>2026-10-14T07:02:54Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;innovaphone feature list&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- featurelist --&amp;gt;&lt;br /&gt;
==Applies to==&lt;br /&gt;
&lt;br /&gt;
This information applies to&lt;br /&gt;
&lt;br /&gt;
- All innovaphone products based on V7, V8, V9 and V10&lt;br /&gt;
&lt;br /&gt;
Starting with V11, this list is discontinued. Firmware-dependent functions and improvements can be found in the respective [[:Category:Release Notes|release notes]].&lt;br /&gt;
&lt;br /&gt;
Functions of earlier firmware versions are also included in newer versions (subject to change and discontinuation).&lt;br /&gt;
&lt;br /&gt;
==More information==&lt;br /&gt;
&lt;br /&gt;
=== PBX System Features ===&lt;br /&gt;
&lt;br /&gt;
* Access to exchange via group number &lt;br /&gt;
* Access to separate exchange via individual number &lt;br /&gt;
* ACD groups &lt;br /&gt;
* Active Directory Replication &lt;br /&gt;
* Administration via uniform interface &lt;br /&gt;
* Alarm and error events &lt;br /&gt;
* Alternate route selection &lt;br /&gt;
* Announcement before pickup (*) &lt;br /&gt;
* Announcements (*) &lt;br /&gt;
* Authorisation groups (class of service) &lt;br /&gt;
* Automatic break through for call protection for preferred numbers &lt;br /&gt;
* Automatic call distribution (ACD) &lt;br /&gt;
* Automatic night switching with week clock &lt;br /&gt;
* Automatic route selection (ARS) &lt;br /&gt;
* Bootcode with minifirmware (not supported with IP3000) &lt;br /&gt;
* Branches (virtual central PBX) &lt;br /&gt;
* Bunched circuit &lt;br /&gt;
* Call back &lt;br /&gt;
* Call back also if internal call &lt;br /&gt;
* Call detail records (CDR) &lt;br /&gt;
* Calling line identification restriction (CLIR) &lt;br /&gt;
* Calling party identification (CLIP) &lt;br /&gt;
* Calling to E.164 &lt;br /&gt;
* Calling via ENUM (H.323 and SIP) &lt;br /&gt;
* centralized backup /firmware/config upload&lt;br /&gt;
* Circle call with circle call query (#) &lt;br /&gt;
* Clock synchronization via IP &lt;br /&gt;
* Config templates for PBX User &lt;br /&gt;
* Configurable tones &lt;br /&gt;
* Configure / change / delete call diversion via web &lt;br /&gt;
* Conversation return to operator &lt;br /&gt;
* Cross connection via IP &lt;br /&gt;
* Cross connection via ISDN &lt;br /&gt;
* Different call (external, internal) &lt;br /&gt;
* Direct dial (with and without number reassessment) &lt;br /&gt;
* Door bell interface with door opener function (#) &lt;br /&gt;
* DTMF detection disabling &lt;br /&gt;
* DTMF-post dial/direct dial &lt;br /&gt;
* Emigration of endpoint &lt;br /&gt;
* Enhanced error reporting (SIP, QOS parameter, router error reporting)&lt;br /&gt;
* Enhanced H.323 features according to H.450.x &lt;br /&gt;
* Extended DTMF Object (feature set via DTMF dial) &lt;br /&gt;
* External communication &lt;br /&gt;
* Firmware upload in DRAM (not supported with IP3000) &lt;br /&gt;
* Floating license model &lt;br /&gt;
* Flexible dial plan &lt;br /&gt;
* General night switching &lt;br /&gt;
* Group call (all, circular)&lt;br /&gt;
* Hide Objects from LDAP&lt;br /&gt;
* Home office integration &lt;br /&gt;
* HTTP/ HTTPS allowed stations&lt;br /&gt;
* Incoming direct call to subscriber or group &lt;br /&gt;
* Interactive call acceptance (*) &lt;br /&gt;
* Interface for external announcement construction (#) &lt;br /&gt;
* Internal communication &lt;br /&gt;
* Internal music on hold &lt;br /&gt;
* Least cost routing (LCR) &lt;br /&gt;
* Log forwarding&lt;br /&gt;
* LDAP replication&lt;br /&gt;
* Message center (H.450.7 or DTMF) &lt;br /&gt;
* Message Waiting Indication (MWI) &lt;br /&gt;
* Messaging (SIP and H.323) &lt;br /&gt;
* Mixed dial method (overlap and en-block dialing) &lt;br /&gt;
* MS-chap V1/V2 &lt;br /&gt;
* Multi conferencing (IP800, IP6000, IP0010, IP1060, IP3010, IP6010) &lt;br /&gt;
* Multi protocol (H.323, SIP) &lt;br /&gt;
* Multilevel admin access (detailed multilevel user rights for the PBX configuration) &lt;br /&gt;
* Multiple system admin (multiple admin and viewer rights possible for the whole system) &lt;br /&gt;
* Multistage login (multi-user) &lt;br /&gt;
* Music / announcement in standby from analogue resource (#) &lt;br /&gt;
* Music / announcement in standby from HTTP resource (*) &lt;br /&gt;
* Network wide features (Master/slave with virtual PBX) &lt;br /&gt;
* Only calling to registered subscribers (passive control) &lt;br /&gt;
* Overflow of subscribers and cross connection &lt;br /&gt;
* Overlapped sending &lt;br /&gt;
* PBX directory search (LDAP search via DTMF) &lt;br /&gt;
* Phonebook either from internal or from external source (LDAP) &lt;br /&gt;
* QSIG &lt;br /&gt;
* QSIG inter-working &lt;br /&gt;
* QSIG trunking (point to point and point to multipoint) &lt;br /&gt;
* Redundancy of the ISDN-lines &lt;br /&gt;
* Redundancy of the PBX &lt;br /&gt;
* Remote monitoring and remote diagnostics &lt;br /&gt;
* Remote software upgrade &lt;br /&gt;
* RTP Proxy &lt;br /&gt;
* SDP Transit (for video and other codecs) &lt;br /&gt;
* Short dial (individual, group, system wide) &lt;br /&gt;
* Silent intrusion &lt;br /&gt;
* SIP/H.323 Media Relay (RTP stream routing via gateway) &lt;br /&gt;
* SIP trunking &lt;br /&gt;
* SIP via TCP&lt;br /&gt;
* SIPS (SIP-Secure) – SIP via TCP/TLS (not supported with IP3000) &lt;br /&gt;
* SNMP Traps (alarm events) &lt;br /&gt;
* SOAP-API &lt;br /&gt;
* SRTP (Voice encryption) for H.323 and SIP (not supported with IP3000) &lt;br /&gt;
* Subscriber authorisation&lt;br /&gt;
* Standard protocols to the endpoint &lt;br /&gt;
* Subscriber groups with progressive call (parallel, circular, sequential)&lt;br /&gt;
* Switch between day/night with code digit from subscribers &lt;br /&gt;
* System time/date via timeserver (LAN or web) &lt;br /&gt;
* TAPI / Multi line TAPI (via several PBX’s / locations)&lt;br /&gt;
* Telephone number assignment &lt;br /&gt;
* Time based subscriber authorisation&lt;br /&gt;
* Twin Phones &lt;br /&gt;
* US standard (T1 and CAS) &lt;br /&gt;
* VoIP-CAPI&lt;br /&gt;
* Waiting queue – call busy operators / CFU disable operators &lt;br /&gt;
* 802.1x&lt;br /&gt;
* Active Directory Replication/More detail information in error situations&lt;br /&gt;
&lt;br /&gt;
==== New in V8 ====&lt;br /&gt;
* Announcing the queue position in a waiting queue &lt;br /&gt;
* Call completion on busy/free to ISDN &lt;br /&gt;
* Customized Visual Appearance (individually designable user interface)&lt;br /&gt;
* Dual Forking (OCS compatible)&lt;br /&gt;
* Dynamic PBX (more PBXs on one Device ) PBX hosting / PBX virtualization &lt;br /&gt;
* Kerberos based authentication and Cross Realm authentication&lt;br /&gt;
* Mobility (GSM integration) &lt;br /&gt;
** Call-waiting &lt;br /&gt;
** hold &lt;br /&gt;
** transfer &lt;br /&gt;
** park &lt;br /&gt;
** group login/logout &lt;br /&gt;
** mobility on/off &lt;br /&gt;
** setting presence status &lt;br /&gt;
&lt;br /&gt;
* Off load Dialtone (external gateway)&lt;br /&gt;
* Off load Media Relay (external gateway) &lt;br /&gt;
* Off load MOH (external gateway)&lt;br /&gt;
* Presence &lt;br /&gt;
* Recording at the ISDN and analogue interfaces &lt;br /&gt;
* Roaming Phone Profiles &lt;br /&gt;
* RSTP (Rapid Spanning Tree) &lt;br /&gt;
* Send Message to group &lt;br /&gt;
* SIP error detection (alarm/event updated) &lt;br /&gt;
* SIP Federation &lt;br /&gt;
* SIP video multisite support&lt;br /&gt;
&lt;br /&gt;
====New in V9====&lt;br /&gt;
* Executive/secretary enhancements&lt;br /&gt;
** Secretary can initiate calls with the CLIP from the executive. &lt;br /&gt;
** Executive can see if the secretary is joined or unjoined in the primary secretary group. &lt;br /&gt;
** Executive sees if a call diversion is set at the secretary.&lt;br /&gt;
** Breakthrough disabled call waiting at secretary.&lt;br /&gt;
&lt;br /&gt;
* Reporting &lt;br /&gt;
** Based on internal or external Linux Application Platform&lt;br /&gt;
** Based on PBX CDR´s&lt;br /&gt;
** Predefined filter&lt;br /&gt;
** Reports (export as PDF, XML) from filter, combined filter, date and time&lt;br /&gt;
&lt;br /&gt;
* Emergency calls priority&lt;br /&gt;
* Import/Export PBX user database (CSV/XML)&lt;br /&gt;
* Individual MOH (context sensitive based on object, node or PBX)&lt;br /&gt;
* IP filter for registrations with or without password &lt;br /&gt;
* IPv6 support (IPv6 routing, 6to4 routing and http access, telnet)&lt;br /&gt;
* LDAP via TLS&lt;br /&gt;
* MTLS &lt;br /&gt;
* NTP redundancy&lt;br /&gt;
* Partnerkeys via separate Pbx´s&lt;br /&gt;
* Wideband audio&lt;br /&gt;
* Enhanced Boolean (call forward, filter and diversion filter) based also on date &lt;br /&gt;
* Maximum call duration&lt;br /&gt;
&lt;br /&gt;
==== New in V10 ====&lt;br /&gt;
* Show video calls on page PBX/Calls&lt;br /&gt;
* Show video capability of registrations on page PBX/Registrations&lt;br /&gt;
* Tone type for PBX generated tones (e.g. for Mobility) configurable&lt;br /&gt;
* Explicit assignement of licenses to users&lt;br /&gt;
* Server based myPBX call lists included with myPBX licenses at no extra charge&lt;br /&gt;
* per user Voicemail license scheme&lt;br /&gt;
* Support for cloud setup&lt;br /&gt;
* Ability to correct calendar-driven presence information manually&lt;br /&gt;
* &#039;do-not-disturb&#039; presence&lt;br /&gt;
* Support for Mobility client using data for call-control features (hold, retrieve etc.)&lt;br /&gt;
* configurable default visibility (presence/dialog) for group members &lt;br /&gt;
* Disconnect other ringing endpoints if call is rejected on one in a twin-phone configuration&lt;br /&gt;
* Broadcast Conference object supports chat conferences&lt;br /&gt;
* Offload-able media interface for voicemail (Hosting)&lt;br /&gt;
* Waiting Queue supports mobile operators &lt;br /&gt;
* Conditional Mobility/Forking (via &#039;&#039;Boolean&#039;&#039; object)&lt;br /&gt;
* Kerberos with AES (Windows 2008R2 compatibility)&lt;br /&gt;
&lt;br /&gt;
===Features IP Phones – IP110 / IP200 / IP230 / IP240 / IP240-1000 / IP241 / IP222 / IP232===&lt;br /&gt;
* Adjustable loudness &lt;br /&gt;
* Adjustable ringing tones also possible, import RTTTL and midi files &lt;br /&gt;
* Alphanumeric phonebook &lt;br /&gt;
* Announcement via loudspeaker &lt;br /&gt;
* Automatic callback on busy and free &lt;br /&gt;
* Automatic redialing &lt;br /&gt;
* Automatic redialing to busy bunched circuit &lt;br /&gt;
* Blind transfer &lt;br /&gt;
* Call diversion to internal phone number &lt;br /&gt;
* Call hold / retrieve call diversion to external phone number &lt;br /&gt;
* Call intrusion &lt;br /&gt;
* Call list (outgoing, incoming, combined, not reached, not answered)&lt;br /&gt;
* Call park and enquiry from other subscribers &lt;br /&gt;
* Call prevention &lt;br /&gt;
* Call transfer / pickup (selective and from a group)&lt;br /&gt;
* Call waiting (acoustical and optical signaling of waiting calls)&lt;br /&gt;
* Caller identification (name/number) &lt;br /&gt;
* Changeover of the assigned partners &lt;br /&gt;
* Conference (3 way) &lt;br /&gt;
* Configuration of the voice recording via HTTP&lt;br /&gt;
* Connect to busy and free subscribers without notification &lt;br /&gt;
* Counter and list of missed calls &lt;br /&gt;
* Date and time display (automatic summer/winter time adjustment) &lt;br /&gt;
* Delete call back &lt;br /&gt;
* Delete variable call diversion &lt;br /&gt;
* Dialing an IP address (with and without RAS) &lt;br /&gt;
* Dialing with code key from an unauthorized phone &lt;br /&gt;
* Direct dialing (immediate, internal/external)&lt;br /&gt;
* Display duration of call &lt;br /&gt;
* Display calling number &lt;br /&gt;
* Emigration of subscriber/endpoint &lt;br /&gt;
* Fixed call diversion (unconditional, no answer (time adjustable) on busy)&lt;br /&gt;
* Forced announcement (priority call) &lt;br /&gt;
* Function keys – multitude possible – exact list can be found in the technical specification of each IP phone &lt;br /&gt;
* Hands free &lt;br /&gt;
* Headset &lt;br /&gt;
* Individual configuration &lt;br /&gt;
* Individual phonebook &lt;br /&gt;
* Intercom with automatic call pick up &lt;br /&gt;
* Interlinked and limitless multiple conference &lt;br /&gt;
* Manager/assistant feature &lt;br /&gt;
* Message waiting indication (MWI) &lt;br /&gt;
* Messaging &lt;br /&gt;
* Multi language &lt;br /&gt;
* Multi-protocol and multi-registration (SIP and H.323 concurrent)&lt;br /&gt;
* Multiple registrations with selective de-registration &lt;br /&gt;
* Mute (switch off the microphone) &lt;br /&gt;
* Name dialing &lt;br /&gt;
* Open listening &lt;br /&gt;
* Over plugging (connect call to a busy subscriber) &lt;br /&gt;
* Phone lock &lt;br /&gt;
* Preferred subscribers &lt;br /&gt;
* Project code &lt;br /&gt;
* Redialing of the last 100 dialed numbers &lt;br /&gt;
* Silent Intrusion &lt;br /&gt;
* SIP via TCP &lt;br /&gt;
* SIPS (Secure SIP via TCP/TLS) &lt;br /&gt;
* SRTP (SIP and H.323) &lt;br /&gt;
* Status indication of the subscriber (free/busy/call) &lt;br /&gt;
* Subscriber with several lines &lt;br /&gt;
* Subscriber with several numbers &lt;br /&gt;
* Transfer with consultation &lt;br /&gt;
* Variable call diversion &lt;br /&gt;
* 802.1x&lt;br /&gt;
&lt;br /&gt;
==== Phone Menu Languages ====&lt;br /&gt;
* ger - Deutsch&lt;br /&gt;
* eng - English&lt;br /&gt;
* frn - Français&lt;br /&gt;
* dut - Nederlands&lt;br /&gt;
* ita - Italiano&lt;br /&gt;
* esp - Español&lt;br /&gt;
* swe - Svenska&lt;br /&gt;
* dan - Dansk&lt;br /&gt;
* nor - Norsk&lt;br /&gt;
* fin - Suomi&lt;br /&gt;
* cze - Cestina&lt;br /&gt;
* est - Eesti&lt;br /&gt;
* por - Português&lt;br /&gt;
* lat - Latviešu&lt;br /&gt;
* cro - Hrvatski&lt;br /&gt;
* pol - Polski&lt;br /&gt;
* rus - Русский&lt;br /&gt;
* slo - Slovenija&lt;br /&gt;
* hun - Magyar&lt;br /&gt;
* tha - ภาษาไทย&lt;br /&gt;
&lt;br /&gt;
==== New in V9 ====&lt;br /&gt;
* Colour display (IP241 / IP222 / IP232)&lt;br /&gt;
* Individual background picture (IP241 / IP222 / IP232)&lt;br /&gt;
* Individual audible signal for announcement calls /multicast announcements and messaging&lt;br /&gt;
* 802.3az (IP222 / IP232)&lt;br /&gt;
* Wideband audio (IP222 / IP232)&lt;br /&gt;
&lt;br /&gt;
==== New in V10 ====&lt;br /&gt;
* Russian and Slovenian languages&lt;br /&gt;
&lt;br /&gt;
===Features 3rd party Phones connected to analogue (POTS) port, DECT Phones IP52 / IP54 / IP55 / IP61 / IP63 / IP65 ===&lt;br /&gt;
* Call completion on busy &lt;br /&gt;
* Call completion on free &lt;br /&gt;
* Call diversion to internal/external number &lt;br /&gt;
* Call hold/retrieve &lt;br /&gt;
* Call park and enquiry from other subscribers &lt;br /&gt;
* Call protection &lt;br /&gt;
* Call transfer/pickup (selective and from a group)&lt;br /&gt;
* Call waiting (acoustic signalling of the waiting call)&lt;br /&gt;
* Clip to an analogue phone &lt;br /&gt;
* Confirmation tone (positive and negative) &lt;br /&gt;
* Connect to a free and busy subscriber without notification &lt;br /&gt;
* Delete variable call diversion &lt;br /&gt;
* Dial with code key from an unauthorized phone &lt;br /&gt;
* Direct dial immediate (internal, external)&lt;br /&gt;
* Do not disturb (internal and external calls)&lt;br /&gt;
* Fixed call diversion; unconditional, no answer (time adjustable), on busy &lt;br /&gt;
* Lock phone &lt;br /&gt;
* Message Waiting Indication (MWI) on DECT Phones&lt;br /&gt;
* Preferred subscriber &lt;br /&gt;
* Project code &lt;br /&gt;
* Special tone when active feature &lt;br /&gt;
* Transfer with consultation&lt;br /&gt;
&lt;br /&gt;
==== New in V10 ====&lt;br /&gt;
* DECT: pass the DECT Security certification&lt;br /&gt;
&lt;br /&gt;
===Features innovaphone Voice mail (*)===&lt;br /&gt;
* &#039;&#039;Languages supported: German / English / Italian / French / Dutch / Spanish / Norwegian / Danish / Polish /Swedish / Czech  – additional languages on demand.&#039;&#039;&lt;br /&gt;
* &#039;&#039;Voicemail runs on Compact Flash (CF slot in IP800, IP305, IP302, IP2000, IP6000, IP1060, IP3010, IP6010) or on external Web Server&#039;&#039;&lt;br /&gt;
* Email notification (with or without attachment) &lt;br /&gt;
* Listen to/delete /store voice mails by means of DTMF input &lt;br /&gt;
* MWI (according to H.450.7) &lt;br /&gt;
* Personal greeting message &lt;br /&gt;
* Voice recording &lt;br /&gt;
&lt;br /&gt;
==== New in V9 ====&lt;br /&gt;
* Voicemail support SRTP&lt;br /&gt;
&lt;br /&gt;
=== Features myPBX ===&lt;br /&gt;
UC client (myPBX) web-based and Windows launcher&lt;br /&gt;
* &#039;&#039;Languages supported: Danish / English / Estonian / Finnish / French / Italian / Latvian / Dutch /  Norwegian / Polish /  Portuguese / Spanish / Swedish / Czech – additional languages on demand.&#039;&#039;&lt;br /&gt;
** CTI (initiate call, accept call, terminate call, hold call, retrieve call, transfer call, park call, 3PTY conference)&lt;br /&gt;
** Manage own call diversions&lt;br /&gt;
** Call list&lt;br /&gt;
** Presence (manage own presence state)&lt;br /&gt;
** Buddylist (including partners presence and call status)&lt;br /&gt;
** Chat (multiparty chat)&lt;br /&gt;
** Audioconference (via innovaphone audio conference Interface)&lt;br /&gt;
** Videoconferece (via integration of  Webex or Microsoft Livemeeting)&lt;br /&gt;
** Application sharing (via integration of Webex or Microsoft Livemeeting)&lt;br /&gt;
&lt;br /&gt;
==== New in V10 ====&lt;br /&gt;
* Improved usability, new look, single-window design&lt;br /&gt;
* Intuitive LDAP search (arbitrary search string input, results from different sources are merged)&lt;br /&gt;
* Possibility to display additional info from the directory in the LDAP search&lt;br /&gt;
* Support for LDAPS (LDAP over TLS)&lt;br /&gt;
* Improved instant messaging (subject, list of participants, messages are received before the chat is accepted, window can be closed and opened again without terminating the session)&lt;br /&gt;
* Simplified call diversion configuration (synchonized with the favourite call diversions on the phone)&lt;br /&gt;
* Simplified visibility settings&lt;br /&gt;
* Do not disturb (new presence activity, chats are rejected if DND is set)&lt;br /&gt;
* Pickup calls from favourites&lt;br /&gt;
* Unpark calls from favourites&lt;br /&gt;
* Unlimited length of call list (using a paging mechanism).&lt;br /&gt;
* Configure language in launcher&lt;br /&gt;
* Translated launcher user interface&lt;br /&gt;
* Auto appear offline, after an idle timeout that can be configured in the launcher&lt;br /&gt;
* MSI-Parameters for deployment of the launcher&lt;br /&gt;
* Launcher can dock to the left or right screen border&lt;br /&gt;
* Launcher can write trace files for debugging purposes and support&lt;br /&gt;
* Audio conferencing from the chat window has been removed&lt;br /&gt;
* Desktop notifications and notification sounds for calls and instant messaging. Accept and reject calls directly from the notification window. Visibility requests using desktop notifications.&lt;br /&gt;
* Configure mobility&lt;br /&gt;
* Tool that dials or starts chats in myPBX. This tool is registered in windows as an handler for tel: sip: and im: URIs.&lt;br /&gt;
* Display diverting info at incoming alerting calls&lt;br /&gt;
* Display causes at disconnecting calls&lt;br /&gt;
*Video calls between two myPBX Launchers is now possible (runs on Windows 7 and Windows 8, see [[Reference10:Concept myPBX Video]] for details)&lt;br /&gt;
*3 party Video conference&lt;br /&gt;
*Webcam selection if several webcams present&lt;br /&gt;
*Webcam preview of the selected webcam&lt;br /&gt;
*Webcam menu to control settings like brightness or contrast. Adjustable at webcam preview or even during the video call&lt;br /&gt;
*Webcam is configured to deliver 352x288 or 320x240 resolutions and the maximun frame rate available, usually 30 fps&lt;br /&gt;
*H264 encoder configured to deliver an average rate of 250 kbps&lt;br /&gt;
*H264 video stream compatible with other vendors like LifeSize or Polycom&lt;br /&gt;
&lt;br /&gt;
=== Microsoft Office 2010/2013 integration (introduced in V10) ===&lt;br /&gt;
allows to see the presence of a user inside a Microsoft Office 2010 application&lt;br /&gt;
* Presence visibility inside an Office application&lt;br /&gt;
* Start of a chat from inside an Office application&lt;br /&gt;
* Start of a call from inside an Office application&lt;br /&gt;
&lt;br /&gt;
=== Exchange Calender Connector (introduced in V10) ===&lt;br /&gt;
Replicates Exchange Calendar information to PBX user presence &lt;br /&gt;
(Linux Application Platform)&lt;br /&gt;
* Presence is set to busy during calendar appointments&lt;br /&gt;
* The appointment subject is provided as presence note&lt;br /&gt;
* later appointments the same day are indicated as presence note, if presence is &#039;available&#039;&lt;br /&gt;
&lt;br /&gt;
=== Fax Server (introduced in V10)===&lt;br /&gt;
(Linux Application Platform)&lt;br /&gt;
* email-to-fax and fax-to-email gateway&lt;br /&gt;
* Each PBX user has an own fax number: personal fax&lt;br /&gt;
* Fax source formats&lt;br /&gt;
** plain text&lt;br /&gt;
** HTML&lt;br /&gt;
** PDF files &lt;br /&gt;
** all other file formats which can be converted by OpenOffice&lt;br /&gt;
* Cover page &lt;br /&gt;
* e-mail delivery/non-delivery report&lt;br /&gt;
* Incoming fax documents delivered as PDF&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Features Operator (V8) software based===&lt;br /&gt;
* &#039;&#039;Localized versions: German / English / Italian / Dutch – additional languages on demand&#039;&#039;&lt;br /&gt;
* Busylampfield (divided into groups) &lt;br /&gt;
* Call journal &lt;br /&gt;
* Call transfer (with/without consultation (blind)) &lt;br /&gt;
* Drag&amp;amp;Drop or with keypad use &lt;br /&gt;
* Integrated help &lt;br /&gt;
* Monitor blind transferred calls &lt;br /&gt;
* Monitor of waiting queue &lt;br /&gt;
* Name display for incoming calls in LDAP directory &lt;br /&gt;
* Park/unpark &lt;br /&gt;
* Send messages to PBX users &lt;br /&gt;
* Searching within a LDAP directory &lt;br /&gt;
* Searching for PBX users in all PBX´s &lt;br /&gt;
* Set/change call forward for all PBX users &lt;br /&gt;
* Set/change presence status for all PBX users &lt;br /&gt;
* Show busy state &lt;br /&gt;
* Show call forward &lt;br /&gt;
* Show current call&lt;br /&gt;
* Show presence status &lt;br /&gt;
* State-of-the-art user interface &lt;br /&gt;
* Support of Master/Slave scenarios&lt;br /&gt;
&lt;br /&gt;
===Features Interactive Voice Response (IVR) (*)===&lt;br /&gt;
* Call handling according to lines and/or calling number (CLI)&lt;br /&gt;
* Listen to the menu also from internal subscribers &lt;br /&gt;
* Multi level menu &lt;br /&gt;
* Overflow from the operator to an automatic operator &lt;br /&gt;
* Voice menu at extension (if no answer, busy, unconditional) &lt;br /&gt;
* Voice menu with information and automatic dialing &lt;br /&gt;
* Voice menu with predefined destinations &lt;br /&gt;
* Voice menu with manual dialing of the destination (DTMF) &lt;br /&gt;
&lt;br /&gt;
==== New in V8====&lt;br /&gt;
* Announcing the queue position in a waiting queue &lt;br /&gt;
&lt;br /&gt;
* Note: &lt;br /&gt;
* (*) 	External or internal (CF-card) web server required&lt;br /&gt;
* (#) 	innovaphone IP21 required &lt;br /&gt;
&lt;br /&gt;
== Related Information ==&lt;br /&gt;
[[Reference10:Concept_Phone_Firmware_10]]&lt;br /&gt;
&lt;br /&gt;
See the [http://www.innovaphone.com/en/services/downloads.html &#039;&#039;Downloads&#039;&#039; section on www.innovaphone.com] for further information&lt;br /&gt;
&lt;br /&gt;
[[Category:News|{{PAGENAME}}]]&lt;br /&gt;
[[Category:Technical Data EN|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference14r1:Apps/PbxManager/Conference&amp;diff=80684</id>
		<title>Reference14r1:Apps/PbxManager/Conference</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference14r1:Apps/PbxManager/Conference&amp;diff=80684"/>
		<updated>2026-10-14T07:00:13Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Configure your Conferences&lt;br /&gt;
&lt;br /&gt;
== Add a conference==&lt;br /&gt;
; Name&lt;br /&gt;
: Long Name of the PBX object&lt;br /&gt;
&lt;br /&gt;
; SIP&lt;br /&gt;
: Name of the PBX object&lt;br /&gt;
&lt;br /&gt;
; Number&lt;br /&gt;
: Number of the PBX object&lt;br /&gt;
&lt;br /&gt;
; Allow Web Access&lt;br /&gt;
: If it is set, the web access of a room can be enabled in the conference app by users.&lt;br /&gt;
&lt;br /&gt;
; International number&lt;br /&gt;
: External phone number of the PBX. This number is used for the construction of dial-in numbers within meeting invitations.&lt;br /&gt;
&lt;br /&gt;
; Announcements&lt;br /&gt;
: Select the announcements to be played. &lt;br /&gt;
: Use [[{{NAMESPACE}}:PBX/Objects/Conference/Announcement_types|predefined annoucement packages]] depending on language and place them in the local files app.&lt;br /&gt;
:&lt;br /&gt;
: For example: create a folder conference with a subfolder for the languages that you want to use, eg. de for German, en for English, nl for Dutch etc. Be aware, that the (sub)folders should not contain capital characters!&lt;br /&gt;
: Upload the language audio files in the respective subfolder.&lt;br /&gt;
: Share the folder conference with the fileskey and the language audio files are enabled for selection. &lt;br /&gt;
&lt;br /&gt;
; Conference interface&lt;br /&gt;
: Search for available conference devices and select appropriate one for use.&lt;br /&gt;
: Possibility to &lt;br /&gt;
:* set used amount for seats at dedicated conference device and&lt;br /&gt;
:* choose use of PBX-channels-license to operate interface with.&lt;br /&gt;
&lt;br /&gt;
; Channels app&lt;br /&gt;
: To be implemented.&lt;br /&gt;
&lt;br /&gt;
; Rooms&lt;br /&gt;
: Add room(s) to be used for conferences&lt;br /&gt;
: Display name: Room name displayed as endpoint and as the conference app name.&lt;br /&gt;
: Number: Room number. Appended to the conference number for a direct dial-in.&lt;br /&gt;
: Reserved channels: Amount of conference room participants.&lt;br /&gt;
: PIN: Access authentication to enter the room.&lt;br /&gt;
: Meetings: Creating meetings by users can be allowed or not. It is also possible to use a room only with meetings.&lt;br /&gt;
: Video coder: Supported video codec for video conference.&lt;br /&gt;
: Delete room: Erase the room from the conference.&lt;br /&gt;
&lt;br /&gt;
; Configuration templates&lt;br /&gt;
: Each app which is provided by the conference object can be enabled for users with configuration templates.&lt;br /&gt;
&lt;br /&gt;
= Related Articles = &lt;br /&gt;
* [[Courseware:IT_Connect_-_08.1_Conferencing]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Concept Conference]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=80683</id>
		<title>Howto14r1:Firmware Upgrade V13r3 V14r1</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=80683"/>
		<updated>2026-10-14T06:59:50Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 14r1 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 14r1, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
&lt;br /&gt;
: If possible after you finish upgrading to v14r1 you should proceed the update to next version v14r2 according the [[Howto14r2:Firmware_Upgrade_V14r1_V14r2]]&lt;br /&gt;
&lt;br /&gt;
== Licenses ==&lt;br /&gt;
If the system is licensed on premise, you&#039;ll need to regenerate the license file for V14 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).&lt;br /&gt;
&lt;br /&gt;
In case of cloud or rental model, don&#039;t worry about licenses.&lt;br /&gt;
&lt;br /&gt;
An existing myPBX license is counted by the PBX as one PhoneApp license and one SoftphoneApp license. See also [[Howto14r1:Firmware_Upgrade_V13r3_V14r1#myPBX | section on mypbx]].&lt;br /&gt;
&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 14r1.&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 14r1 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend upgrading the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# &#039;&#039;&#039;update the Apps to the last 13r3 SR&#039;&#039;&#039;&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps to the last 14r1 SR&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend reviewing all the configuration changes described below &#039;&#039;&#039;before&#039;&#039;&#039; you begin the update.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note: If you upgrade the App Platform image before updating the ManagerAPP to the latest version of v13r3 you can run into issues.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Changes visible to the end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 14r1 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
=== Softphone/Phone App UI changes === &lt;br /&gt;
* Dial-pad is now a new tab in the navigation.&lt;br /&gt;
* On Smartphones, the Navigation is in the bottom.&lt;br /&gt;
* Call button is removed from the searchbar. Calling only via the search results.&lt;br /&gt;
=== IP-Phone Call-Screen ===&lt;br /&gt;
* [[ReleaseNotes14r1:Firmware#154045 - New symbols unencrypted, encrypted and verified calls| New symbols for unencrypted, encrypted and verified calls]]&lt;br /&gt;
&amp;lt;abbr title=&amp;quot;Select active call on phone, check displayed keys with connected party and confirm with green key symbol&amp;quot;&amp;gt;Possibility&amp;lt;/abbr&amp;gt; to verify and confirm secured end-to-end media encryption through mutual key matching.&lt;br /&gt;
&lt;br /&gt;
=== Configuration of Logo URI ===&lt;br /&gt;
* In 13r3 this configuration was done in the advanced UI on the page PBX / Config / myPBX / Logo URI.&lt;br /&gt;
* But in 14r1 it can be found on the page PBX / Config / General / Logo URL.&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
Extra features for the users:&lt;br /&gt;
* Call the voicemailbox directly from the app.&lt;br /&gt;
* PIN-code can be checked (hidden by default; visible with a click) and changed/set back to default.&lt;br /&gt;
* Call Forwards to the Voicemailbox can be activated/removed (CFU/CFB/CFNR).&lt;br /&gt;
* Number Resolution via the Search Provider.&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
* While sending an outgoing fax via the fax app, you now can select and configure a fax cover page before sending.&lt;br /&gt;
* While configuring a fax app or groupfax via the PBX Manager plugin, you can customize the header line of fax pages and select a language.&lt;br /&gt;
* After updating from 13r3 or setting up your device with 14r1, the Fax object has 4 new options, which are enabled by default:&lt;br /&gt;
** Modem capability: the supported modem class can be changed if necessary.&lt;br /&gt;
** Append user number: if checked, the user number will be appended to the object number.&lt;br /&gt;
** ECM: that allows the T.30 connection to use error correction mode.&lt;br /&gt;
** Receiving with 400dpi allowed: which allows you to receive 400*400dpi documents.&lt;br /&gt;
===AP Manager===&lt;br /&gt;
* The AP Manager UI has been reworked. It is now responsive design, improved view of all app services and instance. Rework of statistic of CPU/RAM/used disk. This change is for the IT administrator, not relevant for end users&lt;br /&gt;
&lt;br /&gt;
== Changed Apps ==&lt;br /&gt;
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Devices App ===&lt;br /&gt;
New Device Configurations option to roll out certificates to the trust list of your devices. [[Reference14r1:Concept_App_Service_Devices#Certificates_configuration]]&lt;br /&gt;
&lt;br /&gt;
=== Recordings App ===&lt;br /&gt;
New option to add WebDav credentials in RecordingsAdmin. [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]&lt;br /&gt;
&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
* New Setting to configure the automatic deletion of old(er) voicemail-messages per app. [[Reference14r1:Concept_App_Service_Voicemail#Settings]]&lt;br /&gt;
* New Option to configure the default PIN per voicemail system. [[Reference14r1:Concept_App_Service_Voicemail#add_voicemail]]&lt;br /&gt;
: By configuring a PIN code from a different length, you also configure the length of the PIN code used by the system.&lt;br /&gt;
&lt;br /&gt;
=== Conference App ===&lt;br /&gt;
* A new settings is now available under [[Reference14r1:Apps/PbxManager/Conference]] to allow the users within his Conference App to access to the Meetings panel or not. By default Conference room set the Meeting option to &#039;&#039;&#039;not allowed&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
== New Apps ==&lt;br /&gt;
New Apps will not be installed automatically by the 13r3 to 14r1 upgrade. The installation description of new 14r1 apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.&lt;br /&gt;
&lt;br /&gt;
=== Calculator ===&lt;br /&gt;
*Although already released in 13r3 sr11, this app is now part of the 14r1 install. This app is explained in [[Reference13r3:Concept App Service Calculator App| the concept article]] and [[Howto14r1:Set up the calculator app| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connect ===&lt;br /&gt;
* A microblogging tool. This app is explained in [[Reference14r1:Concept App Service Messages| the concept article]] and [[Howto14r1:Set up Connect| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connector for Let&#039;s Encrypt ===&lt;br /&gt;
* Automatically creates &amp;amp; renews Let&#039;s Encrypt certificates, the App is included in the Install process - however when doing an upgrade it needs to be [[Reference14r1:Concept Let&#039;s Encrypt#Configuration| setup manually]].&lt;br /&gt;
&lt;br /&gt;
=== Contact Widgets App ===&lt;br /&gt;
* A Contact Widget (or Website Widget) is an element that can be added to a website. It offers to website visitors a way to get in contact with agents (e.g. help-desk). Website visitors can start chat sessions (asking questions, getting answers) or can start voice or even video calls. &lt;br /&gt;
&lt;br /&gt;
For more details have a look at [[Reference14r1:Concept Contact Widgets| the concept article]].&lt;br /&gt;
&lt;br /&gt;
Customers using the previous Widgets, should change to the new [[#Widgets| Contact Widgets App]]&lt;br /&gt;
&lt;br /&gt;
===Notes===&lt;br /&gt;
*Digital notes can be managed with the innovaphone app Notes. The app has a minimalistic feature set and is easy to use. The notes are saved on the server and available on all devices of the users. More infos available in the [[Reference14r1:Concept App Service Notes App| Reference article]]&lt;br /&gt;
&lt;br /&gt;
===PBX Manager - AP app installer===&lt;br /&gt;
*in the PBX manager you will find a new coloured plugin. this new plugin give access to the App store in order to ease the installation of an App service and its instance. You basically do not need to go to the AP platform when you want to install a new application. Idea is to have the further installed app done by this plugin, this also ease the way to discover new applications. More infos available in the [[Reference14r1:Concept App Platform#App Installer PBX Manager Plugin| Reference article]]&lt;br /&gt;
&lt;br /&gt;
=== Search App ===&lt;br /&gt;
* The app is immediately available on the PBX (no configuration is needed). In a new V14r1 configuration the Install provides all Users with this Search App via the &amp;quot;Config User&amp;quot;-Template. If the same configuration is required on an upgraded config, the Search App (&amp;quot;search&amp;quot;) can be ticked in the &amp;quot;Config User&amp;quot; template. For details refer to [[Reference14r1:Concept App Search| the concept article]].&lt;br /&gt;
&lt;br /&gt;
=== TechAssist ===&lt;br /&gt;
* Application for quality assurance and improvement of systems by collecting static and runtime information. For details refer to [[Reference14r1:Concept App Service TechAssist| the concept article]].&lt;br /&gt;
&lt;br /&gt;
== Needed configuration changes ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== EchoCanceller of myApps Client for Windows ===&lt;br /&gt;
In 14r1 the Windows client uses by default a Windows provided EchoCanceller. To switch back to the default Echocanceller used in 13r3, create a Windows registry entry in Computer\HKEY_CURRENT_USER\Software\innovaphone\myApps with the following values:&lt;br /&gt;
 Type: DWORD (REG_DWORD)&lt;br /&gt;
 Name: webrtcEchoCanceller&lt;br /&gt;
 Value: 1&lt;br /&gt;
&lt;br /&gt;
If the 13r3 echo-canceller is used, the myApps trace of a call will contain a line &#039;&#039;[AC] echo canceller is WebRTC aec3&#039;&#039;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Virtual Appliance on VMWare ===&lt;br /&gt;
After deploying the new firmware modify the guest configuration file (stemming from ipva.vmx) for all network cards as such:&lt;br /&gt;
Modify e.g. &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vlance&amp;quot;&amp;lt;/code&amp;gt; to become &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vmxnet3&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== IPVA certificates ==&lt;br /&gt;
IPVA certificates are no longer signed by &#039;&#039;&#039;innovaphone Device Certification Authority 2&#039;&#039;&#039;.&lt;br /&gt;
Instead they will be now signed by &#039;&#039;&#039;innovaphone Unverified Device CA&#039;&#039;&#039;, as innovaphone cannot control the serial numbers and thus the certificate creation of IPVAs.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In a 14r1 install you&#039;ll be asked whether you want to always trust this new CA or not. If you decide not to trust this CA, you have to manually trust newly created IPVA certificates.&amp;lt;br/&amp;gt;&lt;br /&gt;
Note that this is not neccessary for local registrations inside the IPVA itself and doesn&#039;t affect hardware phone registrations.&lt;br /&gt;
&lt;br /&gt;
You can download the innovaphone Unverified Device CA here: https://download.innovaphone.com/certificates/ca-unverified.pem &amp;lt;br/&amp;gt;&lt;br /&gt;
If you want to trust this new CA or your own IPVA certificates, you can use the Devices App to roll out certificates to the trust list of your devices.&lt;br /&gt;
&lt;br /&gt;
== Removed in 14r1 ==&lt;br /&gt;
The following software is no longer included in 14r1.&lt;br /&gt;
=== myPBX ===&lt;br /&gt;
This includes the following components&lt;br /&gt;
* myPBX webclient&lt;br /&gt;
* myPBX for Windows&lt;br /&gt;
* myPBX for iOS&lt;br /&gt;
* myPBX for Android&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Widgets===&lt;br /&gt;
The Widgets were based on the myPBX interfaces that have been removed. Please migrate to the [[Reference14r1:Concept Contact Widgets| the Contacts Widget App]].&lt;br /&gt;
&lt;br /&gt;
===WebRTC toolkit===&lt;br /&gt;
The WebRTC toolkit was based on the myPBX interfaces that have been removed.&lt;br /&gt;
Please use the current interfaces and libraries described in the &#039;&#039;&#039;[https://sdk.innovaphone.com innovaphone SDK]&#039;&#039;&#039;.&lt;br /&gt;
=== Windows Softwarephone ===&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps for Windows&#039;&#039;&#039; and the &#039;&#039;&#039;Softphone App&#039;&#039;&#039;.&lt;br /&gt;
===PBX Object Settings ===&lt;br /&gt;
The object provided the PBX Settings App that was used to configure dynamic group memberships in myPBX.&lt;br /&gt;
Please use the &#039;&#039;&#039;Profile App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===PBX Object ICP ===&lt;br /&gt;
Please use the integrated presence features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
 The ICP object will be restored since 14r1 SR5 and can be then used again!&lt;br /&gt;
&lt;br /&gt;
===Service Call-Lists ===&lt;br /&gt;
This service implemented call lists for myPBX on the local CF card.&lt;br /&gt;
Please use the &#039;&#039;&#039;Reports App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
== Deprecated in 14r1 ==&lt;br /&gt;
The following software is based on legacy technology with no further development and limited maintenance and support.&lt;br /&gt;
We strongly recommend migrating to our successor products that are fully compatible with 14r1 and myApps technology.&lt;br /&gt;
&lt;br /&gt;
=== Linux Application Platform (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;innovaphone App Platform&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
&lt;br /&gt;
=== innovaphone Faxserver (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Fax App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Reporting (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Reports App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Exchange (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Calendar App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== Operator (v9) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Switchboard App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Voice Recording 2014 ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Recordings App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== PBX Object External UC ===&lt;br /&gt;
Existing configurations still work. But new configurations can&#039;t be done using the advanced UI anymore.&lt;br /&gt;
&lt;br /&gt;
Please use the integrated &#039;&#039;&#039;UC&#039;&#039;&#039; and &#039;&#039;&#039;federation&#039;&#039;&#039; features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For presence synchronization with other systems we recommend using&lt;br /&gt;
* &#039;&#039;&#039;innovaphone myApps Connector for Microsoft 365&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Connector for kuando®&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Calendar App&#039;&#039;&#039;&lt;br /&gt;
==Known Problems==&lt;br /&gt;
===Long Update-duration===&lt;br /&gt;
When you update, it can be up to 10 minutes before you have access to your app platform again.&lt;br /&gt;
===Fax from 14r1 to 13r3 App===&lt;br /&gt;
14r1 faxes are sent with 400dpi by default, which the 13r3 app doesn&#039;t support and you will see a [[Reference14r1:Concept App Service Fax#Known Issues|non working incoming fax]]. The second try with lower resolution will work.&lt;br /&gt;
===new Connect App shows false Badgecount===&lt;br /&gt;
If you&#039;ve upgraded from a V13 Installation and Install Connect, it could be, that there is a high Badgecount even if Connect is empty.&amp;lt;br /&amp;gt;&lt;br /&gt;
This Badgecount comes from old chats stored in the Messages App. To get rid of it, the user have to open connect, click on the tree dots in the personal feed and click on &amp;quot;complete all messages&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 14r1 release will consume the same amount of RAM compared to a v13r3 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory  ===&lt;br /&gt;
As a rough rule of thumb, a v14r1 release will consume ~ 1.8 MB more flash memory compared to a v13r3 firmware.&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v14r1.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
*[[Howto:Firmware_Upgrade]]&lt;br /&gt;
* [[Howto:V13 Firmware Upgrade V13r2 V13r3]]&lt;br /&gt;
* [[Howto14r2:Firmware_Upgrade_V14r1_V14r2]]&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 13r3 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 13r3, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 13r2.  For hints on upgrading a system to 13r2 see [[Howto:V13_Firmware_Upgrade_V13r1_V13r2]].&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 13r3 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend to upgrade the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend to review all the configuration changes described below before you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Configuration Changes ==&lt;br /&gt;
In 13r3 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r3 from scratch. If you upgrade an existing installation, you have to configure the following settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Default SRTP key exchange value in device configuration of Phones/Interfaces ===&lt;br /&gt;
Before v13r3, the default value for SRTP key exchange was SDES-DTLS - with v13r3 it changes to the more secure DTLS-SDES. Therefore innovaphone devices now use DTLS instead - if the called endpoint has this preference. To make sure the more secure key exchange is used, we recommend adjusting the &#039;&#039;SRTP key exchange setting&#039;&#039; in the Devices App, &#039;&#039;Device Configuration&#039;&#039; for &#039;&#039;[Phone]&#039;&#039; and &#039;&#039;[Analog phone/fax]&#039;&#039;. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) or gateway models (IP24, IP22) in your setup - as these may have CPU performance issues in the connection setup phase. In that case, use &#039;&#039;&#039;SDES-DTLS&#039;&#039;&#039; as value for the &#039;&#039;SRTP key exchange&#039;&#039; for all devices, not only for the old phone models.&lt;br /&gt;
&lt;br /&gt;
===Group Fax===&lt;br /&gt;
The fax object has to be configured as external resource of a group fax object in 13r3. It is therefore &#039;&#039;&#039;mandatory&#039;&#039;&#039; to assign the fax object as an external resource to all group fax objects after the upgrade - via PBX Manager .&lt;br /&gt;
&lt;br /&gt;
In the Advanced UI, you have to enter the h323/sip name of the fax object in the field &#039;&#039;&#039;External Resource Destination&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Also, with 13r3, group faxes can have their own international fax number and company name, so you should fill in these fields, or else the fax header will be empty.&lt;br /&gt;
&lt;br /&gt;
===Contacts App | User drop-down menu for sharing address books===&lt;br /&gt;
With 13r3, personal address books can be created and shared with users/groups. To have a search and drop-down menu in the sharing step, you have to activate the &amp;quot;Admin&amp;quot; option at the &amp;quot;ContactsApi&amp;quot; app object (tab &amp;quot;App&amp;quot;) over the Advanced UI. Otherwise, no results will be shown, and you have to enter the correct h323 name of a user.&lt;br /&gt;
&lt;br /&gt;
===Improved Conference Rooms===&lt;br /&gt;
* The &#039;&#039;Web Access allowed&#039;&#039; checkbox in the conference app has to be set in order to access the Conference Web Access UI.&lt;br /&gt;
: To be able create HTTP links for external participants, the conferencing App is required.&lt;br /&gt;
* Update the [[Reference13r3:PBX/Objects/Conference/Announcement_types#Sample_Announcement_Files | announcements]] for your conference rooms, to include also the &#039;&#039;Web Access announcements&#039;&#039;. &lt;br /&gt;
* it is recommended to use a second Turn-Server listening on TCP port 443 as a fallback option for external conference participants, with local firewalls not allowing access to your standard Turn-server. Configure this second Turn-Server in [[Reference13r3:IP4/General/STUN#TURN_Extern | IP4/General/STUN -&amp;gt; Turn Extern]] [[User:Sga|Sga]] TBD: info zu inno Turn Fallback server&lt;br /&gt;
* 13r3 adds a search-API for the Conference Rooms, allowing users to search for Conference room names from their Phone, Softphone or RCC App. Each conference object provides its own search API which is named like &#039;&#039;&amp;lt;Name-of-conference-object&amp;gt;.search&#039;&#039; and access to it can be granted using the App-Section of a PBX-object. The PBX-Manager Plugin for Conferences offers also an option to add the rights for all conference rooms and their search-APIs to the Config-User and/or Config-Admin template.&lt;br /&gt;
&lt;br /&gt;
=== NTLM/OAuth===&lt;br /&gt;
13r3 introduces OAuth2 Windows Authentication for myApps. If your are currently using NTLM/Netlogon for authentication, you might want to consider upgrading it OAuth2, since this authentication mechanisms is more secure. See [[Reference13r3:Concept OAuth2 Windows Authentication]] for details. &lt;br /&gt;
In 13r3 only Microsoft AD FS is supported as OpenID Server.&lt;br /&gt;
&lt;br /&gt;
===HTTP-Proxy===&lt;br /&gt;
13r3 introduces [[Reference13r3:Concept_myApps_platform_services#HTTP_proxy_support | HTTP-Proxy]] support for myApps. Now, myApps follows by default the OS-settings regarding HTTP-Proxy. This might affect existing setups when updating from 13r2 to 13r3. We recommend to check before a 13r3 update if an HTTP-Proxy is used and if so, test before the update for interop problems between myApps and the used HTTP-Proxy.&lt;br /&gt;
&lt;br /&gt;
===Physical Location===&lt;br /&gt;
The Softphone App supports in 13r3 the determination of the Physical Location. Similar to an IP-Phone, this is determined automatically based on HTTP-Redirects of the myApps PBX-login process. If you use PBX-objects with activated &amp;quot;Local&amp;quot; option (often this is a Trunk Line object), the determined physical location might lead to a different behavior when calling these objects. If this leads to unwanted call flows, you can either adjust the initial myApps registration PBX or configure the Physical location manually at the Softphone.&lt;br /&gt;
&lt;br /&gt;
== Application Platform and its applications ==&lt;br /&gt;
===App Platform image===&lt;br /&gt;
&lt;br /&gt;
It is not mandatory but recommended to [[Reference13r3:Concept_App_Platform#Update_of_the_App_Platform_itself | update the App Platform image]] to the latest version to receive a newer kernel and updated Linux packages.&lt;br /&gt;
&lt;br /&gt;
===Recordings App===&lt;br /&gt;
Please follow the procedure described in the [[Reference13r3:Concept_App_Service_Recordings#Upgrade_from_V13r2_to_V13r3_Recordings_App | Recordings App concept article]].&lt;br /&gt;
&lt;br /&gt;
===Reports App===&lt;br /&gt;
The Reports App will improve missed calls queries by adding a new database index during the first start after an update. Depending on the size of the reporting database, this database adjustment can take some minutes and results also in high CPU-load and missed CDRs during that time.&lt;br /&gt;
&lt;br /&gt;
=== App Service Queues, Switchboard App ===&lt;br /&gt;
To allow monitoring of all queues by all switchboard users, configure a group (e.g. with the name &#039;&#039;queues&#039;&#039;) in the PBX and assign it as &#039;&#039;&#039;Static&#039;&#039;&#039; to all Waiting Queues used by the Switchboard App and assign it also as &#039;&#039;&#039;Static&#039;&#039;&#039; and &#039;&#039;&#039;Active&#039;&#039;&#039; to all Switchboard Users.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apps new in 13r3===&lt;br /&gt;
New Apps will not be installed automatically by the 13r2 to 13r3 upgrade. The installation description of new 13r3 apps is usually in the concept article. New apps are:&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_kuando®#Configuration | Connector for kuando®]]&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_Microsoft_365 | innovaphone myApps Connector for Microsoft 365]]&lt;br /&gt;
&lt;br /&gt;
== Changes visible to end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 13r3 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
===Rework of Phone &amp;amp; Softphone UI===&lt;br /&gt;
Several feature and UI improvements, see &#039;Features&#039; in [[Reference13r3:Concept_App_SoftphoneApp#Features | Reference13r3:Concept App SoftphoneApp ]] and [[Reference13r3:Concept Multi-Video-Conference]].&lt;br /&gt;
&lt;br /&gt;
===CallForwarding in Profile App===&lt;br /&gt;
Added configuration option on call diversions: call forwardings depending on &#039;&#039;myApps online&#039;&#039; and &#039;&#039;Presence&#039;&#039; state. This can be switched on or off by the user in the Profile App.&lt;br /&gt;
&lt;br /&gt;
===Focus App===&lt;br /&gt;
The &amp;quot;App focus&amp;quot; can be used to define a default app for the user. It is started and shown automatically when myApps is loaded. When closing other apps, the app is shown instead of the home screen. Users can activate (default) or deactivate the Focus function in their myApps Client settings (hamburger menu). See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
===Pin Apps===&lt;br /&gt;
Apps can be pinned to the main window. Pinned apps are always running and can&#039;t be closed. They are also started automatically when the myApps client is loaded. This setting is locally stored per-client. So you can pin different apps on your computer and your smartphone.  See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
The [[Reference13r3:Concept_App_Service_Fax#Mail_Configuration | Mail Configuration]] section of the Fax App offers in 13r3 additional options:&lt;br /&gt;
* Transmission confirmations&lt;br /&gt;
* Transmission reports for outgoing fax jobs as PDF&lt;br /&gt;
* Error notifications for outgoing fax jobs&lt;br /&gt;
&lt;br /&gt;
==Hardware Restrictions==&lt;br /&gt;
For a list of devices with no/restricted support in 13r3, see the [[Howto:Firmware_Upgrade#Version_13r3 | Firmware Upgrade article]].&lt;br /&gt;
&lt;br /&gt;
==Known Problems==&lt;br /&gt;
&lt;br /&gt;
===Boolean App===&lt;br /&gt;
Following the update to 13r3, it is not possible to edit Boolean Apps using the myApps client (except when using the myApps client in a web browser). To resolve this issue, you will need to delete the approxy folder for all users who use the boolean app. You can locate this folder in the following directory: %USERPROFILE%\AppData\Local\innovaphone\myApps.&lt;br /&gt;
Reload or restart myApps afterwards.&lt;br /&gt;
&lt;br /&gt;
This behavior can also occur under Mac OS. Here the problem can be solved by uninstalling the app and then reinstalling it again.&lt;br /&gt;
&lt;br /&gt;
===Current major issues that will be fixed with upcoming 13r3SR1 release===&lt;br /&gt;
* [[Support:PBX_13r3_final_trap_with_Unknown_Registrations | PBX 13r3 Final trap with Unknown Registrations]]&lt;br /&gt;
* [[Support:13r3final_App_Platform_-_SMTP_delivery_may_fail_due_to_IPv6_DNS_results | 13r3final App Platform - SMTP delivery may fail due to IPv6 DNS results]]&lt;br /&gt;
* [[Support:13r3final PBX randomly does not execute CFU | 13r3final PBX randomly does not execute CFU]]&lt;br /&gt;
&lt;br /&gt;
More info on other 13r3 SR1 changes can be found in the [[Reference13r3:Release_Notes_Firmware#13r3_Service_Release_1 | Release Notes]].&lt;br /&gt;
&lt;br /&gt;
===Regex Expression===&lt;br /&gt;
We updated the regular expression syntax which is used for the AD replication. A &#039;\&#039; followed by a non-special character is no longer allowed.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Technical_data_and_recommended_number_of_users_supported | the specs ]] will run on all supported hardware.  However, unusual configurations may not.  It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade.  Please find details in [[Reference:Device Health Check]].&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 13r3 release will consume the same amount of RAM compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory ===&lt;br /&gt;
As a rough rule of thumb, a v13r3 release will consume ~ 0.5 MB flash more compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r3.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
=== Conferences ===&lt;br /&gt;
Since Conferences now use [[Reference13r3:Concept_Multi-Video-Conference | multiple video streams]] to display each conference participant (in 13r1 &amp;amp; 13r2 only the video stream of the speaker was shown), the number of concurrent video streams used in a single conference increased. Please review this [[Reference13r3:Concept_Multi-Video-Conference#Bandwidth_Consideration | bandwidth considerations]]. As a result, a device hosting a multivideo conference on its CONF or SCNF interface has a higher CPU load in 13r3 than in 13r2.&lt;br /&gt;
&lt;br /&gt;
[[Image:13r3_conference_bandwidth.png|700px|Estimated Conference bandwidth requirements]]&lt;br /&gt;
&lt;br /&gt;
The graph shows the bandwidth needed for a device running the CONF interface to participate in a conference. The values shown are for when all participants are in gallery mode (which is the worst case scenario) and in fullscreen presentation mode (which is the best case scenario). In general, the actual bandwidth needed will fall somewhere between these two extremes. &lt;br /&gt;
&lt;br /&gt;
To calculate the CPU requirements for the device, you can use the following formula: &amp;lt;code&amp;gt;CPU% = Bandwidth (in Mbps) / x&amp;lt;/code&amp;gt;, where x is&lt;br /&gt;
* 0.42 for a xx10 device &lt;br /&gt;
* 0.18 for IP311 and IP411 devices&lt;br /&gt;
* 0.56 for a xx11 device&lt;br /&gt;
* 3.6 for a xx13 device &lt;br /&gt;
&lt;br /&gt;
For example, if you are hosting a conference with 10 participants on a xx11 device in gallery mode, the upstream and downstream bandwidth would be 25 Mbps. Using the formula, you can calculate the CPU requirements as follows: CPU% = 25 Mbps / 0.56 = 44.64%. This means that the device should have at least 45% free CPU capacity to handle the conference.&lt;br /&gt;
&lt;br /&gt;
From the client&#039;s perspective, the worst case values for upstream bandwidth (when presenting) would be 1 Mbps, and for downstream bandwidth (when in a gallery mode conference with 20 participants) would be 5 Mbps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Courseware:Advanced_-_Distributed_PBX&amp;diff=80682</id>
		<title>Courseware:Advanced - Distributed PBX</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Courseware:Advanced_-_Distributed_PBX&amp;diff=80682"/>
		<updated>2026-10-14T06:51:55Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#moodlebook: Master Templates / V12 Templates / Advanced | Distributed PBX | 121 }}&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Courseware:IT_Connect_-_10.3_How_to_create_a_support_ticket&amp;diff=80681</id>
		<title>Courseware:IT Connect - 10.3 How to create a support ticket</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Courseware:IT_Connect_-_10.3_How_to_create_a_support_ticket&amp;diff=80681"/>
		<updated>2026-10-14T06:50:19Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#moodlebook: Master Templates / V16 Templates / Connect|  How to create a support ticket | 161 }}&lt;br /&gt;
[[Category:IT_Connect|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Courseware:IT_Connect_-_06.0_Managing_Devices&amp;diff=80548</id>
		<title>Courseware:IT Connect - 06.0 Managing Devices</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Courseware:IT_Connect_-_06.0_Managing_Devices&amp;diff=80548"/>
		<updated>2026-09-23T10:05:44Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#moodlebook: Master Templates / V16 Templates / Connect| Managing Devices | 161 }}&lt;br /&gt;
[[Category:IT_Connect|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Courseware:IT_Connect_-_06.0_Managing_Devices&amp;diff=80547</id>
		<title>Courseware:IT Connect - 06.0 Managing Devices</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Courseware:IT_Connect_-_06.0_Managing_Devices&amp;diff=80547"/>
		<updated>2026-09-23T10:04:29Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#moodlebook: Master Templates / V15 Templates / Connect| Managing Devices | 161 }}&lt;br /&gt;
[[Category:IT_Connect|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79702</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79702"/>
		<updated>2026-04-28T13:37:00Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Steps to setup up the Connector for Whatsapp */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Steps to set up the Connector for Whatsapp ==&lt;br /&gt;
=== Install ===&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
=== Set up===&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform. It is crucial that the App Objekt exists on the PBX before you start the Onboarding process&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding. To add a phone id, your WhatsApp Business Display name as to be included in the Profile Name.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (&#039;&#039;&#039;MANDATORY&#039;&#039;&#039;). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79701</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79701"/>
		<updated>2026-04-28T13:35:22Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* App (innovaphone-whatsapp) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Steps to setup up the Connector for Whatsapp ==&lt;br /&gt;
=== Install ===&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
=== Set up===&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform. It is crucial that the App Objekt exists on the PBX before you start the Onboarding process&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding. To add a phone id, your WhatsApp Business Display name as to be included in the Profile Name.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (&#039;&#039;&#039;MANDATORY&#039;&#039;&#039;). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79601</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79601"/>
		<updated>2026-04-27T09:06:16Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Steps to setup up the Connector for Whatsapp */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
== Steps to setup up the Connector for Whatsapp ==&lt;br /&gt;
=== Install ===&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
=== Set up===&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform. It is crucial that the App Objekt exists on the PBX before you start the Onboarding process&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding. To add a phone id, your WhatsApp Business Display name as to be included in the Profile Name.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (&#039;&#039;&#039;MANDATORY&#039;&#039;&#039;). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79600</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79600"/>
		<updated>2026-04-27T09:03:09Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
== Steps to setup up the Connector for Whatsapp ==&lt;br /&gt;
=== Install ===&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
=== Set up===&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform. It is crucial that the App Objekt exists on the PBX before you start the Onboarding process&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (&#039;&#039;&#039;MANDATORY&#039;&#039;&#039;). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79599</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79599"/>
		<updated>2026-04-27T08:57:21Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform. It is crucial that the App Objekt exists on the PBX before you start the Onboarding process&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (&#039;&#039;&#039;MANDATORY&#039;&#039;&#039;). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79598</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79598"/>
		<updated>2026-04-27T08:56:42Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Set up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform. It is crucial that the App Objekt exists on the PBX before you start the Onboarding process&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (mandatory). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Apps/PbxManager/App_Connector_for_WhatsApp&amp;diff=79555</id>
		<title>Reference16r1:Apps/PbxManager/App Connector for WhatsApp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Apps/PbxManager/App_Connector_for_WhatsApp&amp;diff=79555"/>
		<updated>2026-04-22T12:50:05Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Settings plugin for the Connector for WhatsApp allows you to create and configure the corresponding app object. In addition, the app object can be assigned to specific configuration templates (if available).&lt;br /&gt;
&lt;br /&gt;
== Add Connector for WhatsApp ==&lt;br /&gt;
Create a new PBX object for the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Type &#039;&#039;whatsApp&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Name&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Long Name of the PBX object&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;SIP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Name of the object&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect App&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect app that is associated with the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect Moderator&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Moderator mode of the Connect app. If this mode is not available, open the Connect object in the Advanced UI and add &#039;&#039;moderator&#039;&#039; as a mode.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Licenses&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Add your license amount&lt;br /&gt;
&lt;br /&gt;
== Set up ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Phone PIN&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The user must enter a 6-digit PIN. This PIN is not generated by the system. After creation, it is linked to your Phone Number ID. Afterwards you can start your onboarding as described in the [[{{NAMESPACE}}:Concept App Service Connector for Whatsapp|Concept article.]]&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&#039;&#039;&#039;User Token&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The user token generated by Meta is automatically stored in your configuration.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mobile Number ID&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The mobile phone number ID is assigned to you by Meta during the onboarding process. You can have up to 20 phone IDs, but verification by Meta is required.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;App&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect app to process input/output from the connector. The selected app will receive incoming messages for the registered mobile number and be able to send messages from that number.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zone&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect zone to which WhatsApp messages should be posted. The zone should correspond to the SIP ID of the Connector for WhatsApp object.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect Tags&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Configure hashtags to be applied to messages posted via the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Licensed&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Mobile Number ID to be licensed. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Message on closed answer timeframe&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This message will be transmitted as soon as the 24 hours time frame elapsed.&lt;br /&gt;
&lt;br /&gt;
== Whatsapp account information ==&lt;br /&gt;
&lt;br /&gt;
Displays all relevant data used by the Connector for WhatsApp app.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
&lt;br /&gt;
[[Courseware:IT_Plus_-_Connect_App]]&amp;lt;/br&amp;gt;&lt;br /&gt;
[[{{NAMESPACE}}:Concept App Service Connector for Whatsapp]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79554</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79554"/>
		<updated>2026-04-22T12:47:29Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Known issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (mandatory). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
=== Sticker ===&lt;br /&gt;
Stickers are currently not supported. These messages will not be transmitted.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79553</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79553"/>
		<updated>2026-04-22T12:46:18Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. To add only a new phone number, select &#039;&#039;Register new phone number&#039;&#039; instead of completing the full onboarding.&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed in the Configuration menu.&lt;br /&gt;
&lt;br /&gt;
Now you have to assign a Connect instance and zone to each phone ID (mandatory). Hashtags are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
A custom message can be defined that will be sent once the 24-hour timeframe has elapsed.&lt;br /&gt;
&lt;br /&gt;
Enable the license option for each phone ID that needs to be licensed.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Business account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Set-up-whatsapp3.png&amp;diff=79552</id>
		<title>File:Set-up-whatsapp3.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Set-up-whatsapp3.png&amp;diff=79552"/>
		<updated>2026-04-22T12:17:37Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: Viktor.gruenauer uploaded a new version of File:Set-up-whatsapp3.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79531</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79531"/>
		<updated>2026-04-22T07:11:24Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Set up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the Connector for Whatsapp to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to &amp;lt;code&amp;gt;https://whatsapp.innovaphone.com/whatsappsharedservice&amp;lt;/code&amp;gt;. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here.&lt;br /&gt;
&lt;br /&gt;
You have to assign a Connect instance, zone to each phone ID. Hashtag are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79497</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79497"/>
		<updated>2026-04-17T08:34:26Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Install */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
** Configure the license amount&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to whatsapp.innovahone.com. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here.&lt;br /&gt;
&lt;br /&gt;
You have to assign a Connect instance, zone to each phone ID. Hashtag are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79496</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79496"/>
		<updated>2026-04-17T08:04:17Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to whatsapp.innovahone.com. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here.&lt;br /&gt;
&lt;br /&gt;
You have to assign a Connect instance, zone to each phone ID. Hashtag are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79495</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79495"/>
		<updated>2026-04-17T08:02:47Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to whatsapp.innovahone.com. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here.&lt;br /&gt;
You have to assign a Connect instance, zone to each phone ID. Hashtag are optional. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79493</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79493"/>
		<updated>2026-04-17T07:34:06Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* WhatsApp Account Information */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to whatsapp.innovahone.com. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
*License count&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Apps/PbxManager/App_Connector_for_WhatsApp&amp;diff=79492</id>
		<title>Reference16r1:Apps/PbxManager/App Connector for WhatsApp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Apps/PbxManager/App_Connector_for_WhatsApp&amp;diff=79492"/>
		<updated>2026-04-17T07:33:08Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Settings plugin for the Connector for WhatsApp allows you to create and configure the corresponding app object. In addition, the app object can be assigned to specific configuration templates (if available).&lt;br /&gt;
&lt;br /&gt;
== Add Connector for WhatsApp ==&lt;br /&gt;
Create a new PBX object for the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Type &#039;&#039;whatsApp&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Name&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Long Name of the PBX object&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;SIP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Name of the object&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect App&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect app that is associated with the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect Moderator&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Moderator mode of the Connect app. If this mode is not available, open the Connect object in the Advanced UI and add &#039;&#039;moderator&#039;&#039; as a mode.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;Service license&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Add your license amount&lt;br /&gt;
&lt;br /&gt;
== Set up ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Phone PIN&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The user must enter a 6-digit PIN. This PIN is not generated by the system. After creation, it is linked to your Phone Number ID. Afterwards you can start your onboarding as described in the [[{{NAMESPACE}}:Concept App Service Connector for Whatsapp|Concept article.]]&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&#039;&#039;&#039;User Token&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The user token generated by Meta is automatically stored in your configuration.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mobile Number ID&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The mobile phone number ID is assigned to you by Meta during the onboarding process. You can have up to 20 phone IDs, but verification by Meta is required.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;App&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect app to process input/output from the connector. The selected app will receive incoming messages for the registered mobile number and be able to send messages from that number.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zone&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect zone to which WhatsApp messages should be posted. The zone should correspond to the SIP ID of the Connector for WhatsApp object.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect Tags&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Configure hashtags to be applied to messages posted via the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Licensed&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Mobile Number ID to be licensed. &lt;br /&gt;
&lt;br /&gt;
== Whatsapp account information ==&lt;br /&gt;
&lt;br /&gt;
Displays all relevant data used by the Connector for WhatsApp app.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
&lt;br /&gt;
[[Courseware:IT_Plus_-_Connect_App]]&amp;lt;/br&amp;gt;&lt;br /&gt;
[[{{NAMESPACE}}:Concept App Service Connector for Whatsapp]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Apps/PbxManager/App_Connector_for_WhatsApp&amp;diff=79491</id>
		<title>Reference16r1:Apps/PbxManager/App Connector for WhatsApp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Apps/PbxManager/App_Connector_for_WhatsApp&amp;diff=79491"/>
		<updated>2026-04-17T07:32:45Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Settings plugin for the Connector for WhatsApp allows you to create and configure the corresponding app object. In addition, the app object can be assigned to specific configuration templates (if available).&lt;br /&gt;
&lt;br /&gt;
== Add Connector for WhatsApp ==&lt;br /&gt;
Create a new PBX object for the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Type &#039;&#039;whatsApp&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Name&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Long Name of the PBX object&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;SIP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Name of the object&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect App&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect app that is associated with the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect Moderator&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Moderator mode of the Connect app. If this mode is not available, open the Connect object in the Advanced UI and add &#039;&#039;moderator&#039;&#039; as a mode.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;Service license&#039;&#039;&#039;&lt;br /&gt;
Add your license amount&lt;br /&gt;
&lt;br /&gt;
== Set up ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Phone PIN&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The user must enter a 6-digit PIN. This PIN is not generated by the system. After creation, it is linked to your Phone Number ID. Afterwards you can start your onboarding as described in the [[{{NAMESPACE}}:Concept App Service Connector for Whatsapp|Concept article.]]&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&#039;&#039;&#039;User Token&#039;&#039;&#039;&lt;br /&gt;
The user token generated by Meta is automatically stored in your configuration.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mobile Number ID&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The mobile phone number ID is assigned to you by Meta during the onboarding process. You can have up to 20 phone IDs, but verification by Meta is required.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;App&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect app to process input/output from the connector. The selected app will receive incoming messages for the registered mobile number and be able to send messages from that number.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zone&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Connect zone to which WhatsApp messages should be posted. The zone should correspond to the SIP ID of the Connector for WhatsApp object.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Connect Tags&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Configure hashtags to be applied to messages posted via the Connector for WhatsApp.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Licensed&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Select the Mobile Number ID to be licensed. &lt;br /&gt;
&lt;br /&gt;
== Whatsapp account information ==&lt;br /&gt;
&lt;br /&gt;
Displays all relevant data used by the Connector for WhatsApp app.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
&lt;br /&gt;
[[Courseware:IT_Plus_-_Connect_App]]&amp;lt;/br&amp;gt;&lt;br /&gt;
[[{{NAMESPACE}}:Concept App Service Connector for Whatsapp]]&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79386</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79386"/>
		<updated>2026-04-02T06:52:01Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
Please note that only one app object can be created per instance. To create another, a separate app service instance is required.&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to whatsapp.innovahone.com. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79295</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79295"/>
		<updated>2026-03-30T07:10:48Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:whatsapp-oboarding.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone. This will open a new tab in your browser which will connect to whatsapp.innovahone.com. &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta (www.facebook.com/platform) and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin. In order to transmit the data, Meta must be able to connect to the Connector for WhatsApp on your Application Platform (webhook address). The reverse proxy must therefore allow connections to &amp;lt;dns-name of AP&amp;gt;/&amp;lt;domain-name&amp;gt;/whatsapp.&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Whatsapp-oboarding.png&amp;diff=79287</id>
		<title>File:Whatsapp-oboarding.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Whatsapp-oboarding.png&amp;diff=79287"/>
		<updated>2026-03-30T06:47:42Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79265</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79265"/>
		<updated>2026-03-27T09:21:35Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Troubleshooting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic &lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Websocket client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79251</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79251"/>
		<updated>2026-03-25T10:21:43Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Hidden: This app has no user interface and should be hidden for users&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
Please note that that Connect needs to have access to the Connector for Whatsapp as well. As a result, please make sure to enable the checkbox for the Connector for Whatsapp inside the Apps tab of the Connect app.&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79228</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79228"/>
		<updated>2026-03-23T10:14:36Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Known issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
=== Phone Calls ===&lt;br /&gt;
You cannot make phone calls between WhatsApp and Connect users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79225</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79225"/>
		<updated>2026-03-23T08:44:35Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Set up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;Text message&#039;&#039; to verify your number. You’ll receive a verification PIN via SMS. Enter it to complete the process.&amp;lt;br/&amp;gt;&lt;br /&gt;
If you use a MSN that is not capable of receiving a text message, choose  &#039;&#039;Phone call&#039;&#039; instead. An automated system will call you and provide the verification code.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79157</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79157"/>
		<updated>2026-03-16T13:12:25Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Within a discussion in Connect, all messages are forwarded to the sender of the WhatsApp message, not only those posted as direct replies to the incoming message. Private messages are excluded from this behavior and can only be viewed by the author and the recipient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Choose &#039;&#039;Text message&#039;&#039; to verify your number.&lt;br /&gt;
Afterwards, you will receive a verification PIN via text message, which must be entered.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
After completing the onboarding process, the user token and phone ID from Meta are displayed here. You can assign a Connect instance, zone, and hashtags to each phone ID. Messages received via a specific mobile number ID will be posted and tagged based on this configuration.&lt;br /&gt;
&lt;br /&gt;
To delete Phone numbers for a WhatsApp Business account, or the WhatsApp Business account itself, go to the Meta Business Suite:&lt;br /&gt;
[https://www.facebook.com/business/help/1592865014304024/] Note: Numbers are not removed from the Connector for WhatsApp settings when you delete the number in the Whatsapp Buiseness account.&lt;br /&gt;
To remove the numbers open the Configuration section of the plugin and remove the affected number using the delete icon.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79154</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79154"/>
		<updated>2026-03-16T12:40:34Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Set up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. This is a security mechanism to prevent spam for WhatsApp users. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Choose &#039;&#039;Text message&#039;&#039; to verify your number.&lt;br /&gt;
Afterwards, you will receive a verification PIN via text message, which must be entered.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
During the onboarding process, a user token and a phone ID are created for each MSN number and stored in the Connector for WhatsApp app service. They are automatically added to the Configuration section of the plugin.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
Add the mobile number IDs you received from Meta. Messages received via a specific mobile number ID can be assigned to a Connect zone and tagged with hashtags.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79138</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79138"/>
		<updated>2026-03-13T12:54:53Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform. This number cannot be associated with the free version of whatsapp already.&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. This is a security mechanism to prevent spam for WhatsApp users. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Choose &#039;&#039;Text message&#039;&#039; to verify your number.&lt;br /&gt;
Afterwards, you will receive a verification PIN via text message, which must be entered.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
Add the mobile number IDs you received from Meta. Messages received via a specific mobile number ID can be assigned to a Connect zone and tagged with hashtags.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79137</id>
		<title>Reference16r1:Concept App Service Connector for Whatsapp</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Reference16r1:Concept_App_Service_Connector_for_Whatsapp&amp;diff=79137"/>
		<updated>2026-03-13T12:50:59Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: /* Set up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{FIXME|reason=This product is in the beta phase and is not yet finished}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Keywords: Whatsapp, Meta, Connect, --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Applies To ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;innovaphone System (PBX/AP) from version 16r1 upwards&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt; innovaphone PBX&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone AppPlatform&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; innovaphone myApps&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; Messages App service and Connect app&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; A Facebook account&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt; At least one valid phone number (MSN) required for the registration with the WhatsApp Business platform (no private account allowed)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
This product requires licensing. You will need the following license.&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;Name: innovaphone Connector für WhatsApp&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;ID: Service(innovaphone-whatsapp)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Order number: 02-00050-017&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Concept ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The Connector for WhatsApp establishes a connection to the WhatsApp Business Platform and to a Connect instance. Messages can be exchanged between Connect users and WhatsApp users. Supported message types include text messages, locations, contacts, reactions, and media files ( e.g png, .jpg, .pdf, .mp4, .txt). You can find a full list here [https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/media#supported-media-types here]]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:Concept-connector-whatsapp.png]]&lt;br /&gt;
&lt;br /&gt;
== How it works ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Messages written by WhatsApp users will be displayed in Connect alsongside with the Name of the Sender. By answering within the feed, the message is sent to the whatsapp-account of the initiator of the conversation.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Please note that a discussion can only be initiated by the WhatsApp user. This is a security mechanism to prevent spam for WhatsApp users. A Connect user can reply to a message from WhatsApp within a 24-hour time window. If there was no response within the time frame, a new discussion will be created in Connect when a new message from the same number is received.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Apps ==&lt;br /&gt;
=== App (innovaphone-whatsapp) ===&lt;br /&gt;
[[image:whatsapp-connector.png]]The Settings plugin enable the following parameters:&lt;br /&gt;
&lt;br /&gt;
;Websocket: Connection between the PBX and the App Platform.&lt;br /&gt;
;Services: API which is used to get access to APIs provided by other App Services&lt;br /&gt;
;connect: The connector for Whatspp needs access to connect to the Connect App&lt;br /&gt;
;connect~moderator: The Connector for Whatsapp needs &#039;&#039;moderator&#039;&#039; rights to access the Connect App. &lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
*Install the WhatsApp Connector via the &#039;&#039;app Installer&#039;&#039; Settings plugin.&lt;br /&gt;
* Create a new PBX Object for the WhatsApp Connector with the Settings Plugin of the Connector for Whatsapp.&lt;br /&gt;
** Configure a name and SIPid&lt;br /&gt;
** Select your Connect app &lt;br /&gt;
** Select the moderator mode of the Connect app.&lt;br /&gt;
** Select a config template. Users inheriting from this template will have access to the Connect zone where WhatsApp posts are sent.&lt;br /&gt;
&lt;br /&gt;
== Set up==&lt;br /&gt;
After the initial installation of the Connector for WhatsApp, you need to onboard the connector to the WhatsApp Business Platform.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Go to the &#039;&#039;Whatsapp Settings&#039;&#039; Plugin in your Settings app and open &#039;&#039;Set Up&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:Set-up-whatsapp1.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, configure any 6-digit PIN. Please store the PIN in a safe place, as it is required for the administration of your Phone IDs if they need to be deleted.&amp;lt;br/&amp;gt;&lt;br /&gt;
[[image:set-up-whatsapp2.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Set Up&#039;&#039; to connect to a shared service operated by Innovaphone.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp3.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;Onboard&#039;&#039; to start an authenticated session with Meta and log in using your Facebook account. If you do not have one, you must create one.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp4.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you already have a WhatsApp Business Account or a Business Portfolio, you can select it here. If not, one will be created for you. Click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp5.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the details for your Business account, such as name, email address, and country, then click &#039;&#039;Next&#039;&#039;.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp6.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Next, select Use a new or existing WhatsApp number and enter the number you want to link as your WhatsApp Business number. Important: This number must not already be linked to another WhatsApp account, either WhatsApp Business or a regular WhatsApp account.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Choose &#039;&#039;Text message&#039;&#039; to verify your number.&lt;br /&gt;
Afterwards, you will receive a verification PIN via text message, which must be entered.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp7.png]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once completed, a success message will be displayed.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[image:set-up-whatsapp8.png]]&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
Add the mobile number IDs you received from Meta. Messages received via a specific mobile number ID can be assigned to a Connect zone and tagged with hashtags.&lt;br /&gt;
&lt;br /&gt;
== WhatsApp Account Information ==&lt;br /&gt;
After the Onboarding Process the plugin will show you the following Parameter:&lt;br /&gt;
*WhatsApp Business Account ID&lt;br /&gt;
*Webhook-address (This address has to be reachable from the Internet, so make sure your reverse proxy forwards the traffic to the AP)&lt;br /&gt;
*Phone IDs associated with Whatsapp Business (max 20 MSN numbers)&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;If problems occur, please send us a log of the app service. Before reproducing the issue, delete the current contents of the log. The following trace flags should be enabled:&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&amp;lt;li&amp;gt;HTTP client&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;App Websocket&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;li&amp;gt;Webserver traffic (only in case of media transmission problems)&lt;br /&gt;
&amp;lt;/li&amp;gt;&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
=== Whatsapp zone not visible in Connect===&lt;br /&gt;
The user must have access to the &#039;&#039;Connector for WhatsApp&#039;&#039; app (Users → Apps tab). Config Templates can be used to distribute the app to users.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Set-up-whatsapp8.png&amp;diff=79136</id>
		<title>File:Set-up-whatsapp8.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Set-up-whatsapp8.png&amp;diff=79136"/>
		<updated>2026-03-13T12:50:35Z</updated>

		<summary type="html">&lt;p&gt;Viktor.gruenauer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Viktor.gruenauer</name></author>
	</entry>
</feed>