innovaphone wiki - User contributions [en]

Reference16r1:Concept Innovaphone Virtual Appliance (IPVA)

2026-08-24T13:51:53Z

Slu: /* Applies To */

==Applies To==
This information applies to:
*V16r1
*innovaphone Virtual Appliance
*Intel/AMD CPUs
* Virtualization platforms
**VMware
*** Workstation
*** Player
*** vSphere 4 - 8
*** ESXi 6 - 8
**Microsoft Hyper-V ([[{{NAMESPACE}}:Concept IPVA On Hyper-V|Concept IPVA On Hyper-V]])
*** Windows 8.1
*** Windows 10
*** Windows Server 2012 R2
*** Windows Server 2016 CTP4
**Linux based Hypervisors with [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM] and [https://en.wikipedia.org/wiki/QEMU QEMU] support
*** Proxmox VE 8.0 / 8.1 / 9.1 / 9.2

''Disclaimer: Manufacturers/versions of VM platforms other than those specified here have not been tested, so use at your own risk.''

''Disclaimer 2: We occasionally encounter customers experiencing unusual issues related to OpenStack. OpenStack is not officially supported, and such issues are not analyzed.''

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.

The IPVA is a software-only solution. It appears and behaves like an innovaphone "hard-box" without physical resources such as hardware DSP or ISDN interface.

==Package Overview==
We supply an OVF ('''O'''pen '''V'''irtualization '''F'''ormat) import or - depending on the virtualization platform - a suitable variant.
OVF is an open standard that contains several files in one package. The .ovf file is therefore an archive that contains all the necessary files.

=== Sample VMware ===
;ipva-ovf.zip:
The compressed archive ''ipva-ovf.zip'' contains the file ipva.ova. A deployment of ipva.ova will result in a set of 5 files - the file names may differ from the following list:
*ipva.vmx: The virtual machine configuration file
*hd-boot.vmdk: The virtual boot disk on IDE 0:0
*hd-cf.vmdk: The disk for emulation of a Compact Flash card on IDE 0:1
*hd-flash.vmdk: The disk for emulation of flash memory on IDE 1:0
*hd-dump.vmdk: The disk serving as a store for a crash dump on IDE 1:1

;ipva.bin:
The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

== Virtualization platforms ==

===VMware Player / VMware Workstation===
==== Import new Machine ====
*Copy the file ipva.ova to e.g. your desktop and Double-click on ipva.ova.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===VMware vSphere===
==== Import new Machine ====
*Import ipva.ova by means of '''File/Deploy OVF-Template...''' (de: '''Datei/OFV-Vorlage bereitstellen...''') and follow instructions.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===Microsoft Hyper-V===
==== Import new Machine ====
* Use the UI Wizard to Import a new machine
* Browse to the directory where the downloaded package was extracted to. Browse to the subdirectory Virtual Machines and click Ok
* Select ''Copy the Virtual Machine'' as ''Import Type''

===Proxmox VE===
==== Settings ====
Here, we list the VM settings that allowed us to successfully test the system and that ensure VMs run stably in production. These settings should be considered best practices.

===== PVE Version =====
* Version: 9.2.4
* Repositories: Enterprise repositories

===== Hardware =====
* Processors: 1 socket, 1 core, Type "Host" preferred, fallback "x86-64-v2-AES"
* Bios: SeaBIOS
* Machine: i440fx
* SCSI Controller: VirtIO SCSI single
* Hard Disks
** Datastore: Ceph (19.2.3) or local LVM
** Cache: No Cache
** Discard: Enable
** SSD emulation: Yes
** Async IO: io_uring
* Network Devices
** Model: VirtIO (paravirtualized)

===== Options =====
* OS Type: Other
* Boot Order: ide0, ide1, ide2, ide3
* QEMU Gust Agent: Disabled

==== Import new Machine ====
Import the "ova" file to your storage which is enabled for the type "import". After that you can select the created template an create new machines from it with the button "Import"

* Before you start up the VM in the UI you have to adjust the following configuration options:
** Hardware -> Processors: Adjust "Extra Cpu Flags" -> "aes" if required
** Hardware -> SCSI Controller: Change Model to "VirtIO SCSI Single"
** Hardware -> Network Device (net0 / net1): Change Model to "VirtIO (paravirtualized)"

==Configuration==

===Network Configuration===
The IPVA is preconfigured a DHCP client. You will see the current IP-Address in the console-screen of the VM. If there's in no case a DHCP server available for the 1st-time configuration, you can set your IP-Configuration in the console.

config change IP0 ETH0 /addr 192.168.0.10 /mask 255.255.255.0
config change IP0 RT0 /gateway 192.168.0.1
config change DHCP0 /mode off
config write
reset

====MAC/serial number====
Take care that you use a MAC address which is supported by my.innovaphone, see [[Reference:My_Innovaphone#IPVA_MAC_exists]].

===AES Hardware Acceleration===
It may be beneficial to activate hardware acceleration for AES operations.
Whether hardware acceleration is activated can be checked with the command <code>!mod cmd CPU cpu-info</code>.

* The "flags" attribute must contain "aesni"
* The "act-features" attribute must contain "has_aesni"

Example:
<info>
<cpu
vendor="GenuineIntel"
signature="0x906e9"
brand="Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz"
...
flags="sse3 pclmulqdq ssse3 sse4_1 sse4_2 aesni xsave xsaveopt osxsave avx f16c rdrand fpu mmx fxsr sse sse2 avx2"
act-features="has_aesni has_avx has_vaesni has_vpclmulqdq" srtp-mips="5"/>
</info>

==Large IPVA with 512 MiB Flash==
In some scenarios the standard 64 MiB flash memory is not enough to store all user data. It is possible to manually enlarge the flash memory of an IPVA up to 512 MiB.

You have to change the settings of the virtual machine and format the flash. You cannot do it with an already configured machine, because you will lose all your configuration!

# shutdown the IPVA
# increase the RAM to 3.072 MiB
# increase the size of '''IDE1:0''' to 512 MiB or recreate it
# power up the IPVA
# format the flash: <code>!mod cmd FLASHMAN0 reset all</code>
# reboot the IPVA: <code>!reset</code>

You can check the free space with the command <code>!mod cmd FLASHMAN0 info</code>. You will see a big amount of available segments

segments=675, segment-size=0x10000 (64k)
LDAP - used 1k avail 63k owned 64k (segments 1) maximum 517056k (segments 8079, configured 8079)
VARS - used 23k avail 16k owned 192k (segments 3) maximum 640k (segments 10, configured 10)

But please keep in mind, the more data is saved, the longer it takes to reboot and load the UI in the [[{{NAMESPACE}}:PBX/Objects|PBX/Objects]] area.

==Troubleshooting==
Support procedures are commonly identical to the ones known from innovaphones' physical appliances. Except for:
*'''Post-Mortem Logs''' A post-mortem log must be retrieved by clicking on ''Maintenance/Diagnostics/Tracing/'''trace(crash-dump)''''' (alternatively: http://a.b.c.d/crash_dump.txt).

==Known Issues==

=== Maximal 3.072 MiB RAM ===
Because the IPVA has no [https://en.wikipedia.org/wiki/Virtual_memory virtual memory management], it will use only the first linear 3 GiB of RAM. But please keep in mind, that the flash content will be stored 3-times (Flashmanager, Flashdirectory, PBX) in RAM at startup.
=== Restored IPVA may not run ===
We have seen issues where an IPVA which had been backed up using one of the available backup tools for VMWare do not start up properly when they have been restored.

We strongly suggest to not rely on VMWare backup mechanism but instead to use the standard innovaphone backup scheme (that is, save the configuration on a regular basis).

==== How to run a restored backup that fails to start ====
Here is the procedure to run an IPVA from an IPVA if the restored virtual machine does not boot up properly:

* restore the backed up V10 IPVA
* create a new, empty V11r1 IPVA (you will need this merely to copy the boot disk from)
*replace the boot disk of the failing V10 IPVA by the boot disk of the fresh V11r1 IPVA (see [[#How To Replace The Boot Disk On vSphere.3F| How To Replace The Boot Disk On vSphere]] for details)
* start the restored and fixed V10 IPVA (it should run fine now)
* downgrade this V10 IPVA to desired V10 firmware
* remove the fresh V11r1 IPVA

Some Customer who are running Fw v12r1 (up to sr6) with ESXi 6.0 and VEEAM 9 reported that after a backup with VEEAM 9, the restored IPVA was not starting.
At this point, there is no possibility to solve this problem. The only workaround in that case is to delete the machine, reinstall a new one, and restore a configuration saved before.

If you did not run into the problem yet, for prevention, we recommend to replace the Boot disk of your working IPVA.vmx with one of the IPVA.ova. Please follow the steps below (be aware that this will upgrade the firmware on the IPVA to 12r2, due to the fact that actually, IPVA.ova is only available from version 12r2):

1. Remove the Boot disk of the virtual machine (vmx)(is normaly the first one). 
* Power off the VM
* Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Remove''.
* Click ''OK'' to save your changes.

2. Add the Boot disk of the ova virtual machine to the vmx one.
* Identify the size of the boot disk of the ova virtual machine (will be needed on the step when navigating to boot disk)
* On the powered off VM, Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Add''.
* Select Use “an existing virtual disk” then click ''Next''.
* Navigate to the boot disk of the ova Virtual machine then click ''next''.
* Click ''Finish''.
Now the vmx virtual machine should have the Fw version 12r2.

The .ova version will be available also in V12r1 sr7

=== IPVA does not run on Citrix Cloud Platform ===
Reportedly, the Citrix cloud platform - although based on VMware - cannot run the IPVA. Amongst other issues, the platform does not allow 4 virtual disks, which are required for the IPVA.

=== IPVA does not run on VCloud Air ===
VCloud Air apparently does not support the timekeeping mechanism required by the IPVA.

[[User:Ckl|ckl]] 15:50, 30 November 2016 (CET) We have seen the IPVA v12r2 running on vCloud Air. Use the ova import.

=== IPVA on ESX 6.5 ===
We have reports that the IPVA does not run properly on ESX 6.5. The IPVA boots up properly but the clock does not run. Running the .ova based variation available in v12r2 fixed the issue or edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

=== Administration: Avoid 'reboot' Command. Use 'reset' Command ===
Alwas use the 'reset' command to restart an IPVA.
The 'reboot' command makes sense only on physical applicances, where its purpose is to deploy a new bootcode by means of a forced watchdog trap. The resulting post-reboot state will be as if an unsolicited trap/crash had occurred.

=== Voice Quality Issues ===
When dealing with media streams (e.g. for announcements), the IPVA needs to fulfil real-time processing requirements, for example to process RTP packets in a timely fashion. To do so, the IPVA relies on the capabilities of the virtualization platform it runs on.

It is therefore important to configure the platform so that it supports real-time applications best. If you experience voice quality or latency issues, consider
* to make sure that all of the IPVAs memory is ''reserved'' to the IPVA (''Latency Sensitivity'' set to ''High'')
* to guarantee exclusive PCPU access
This helps to reduce CPU halt/wake-up states.

===Additional vCPUs may cause problems===
The Multi-Core functionality of version 13r2 is a beta functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==FAQ==
===Can The emulated compact-flash disk size be increased?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated compact-flash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given. Please note: The compact-flash disk is not the flash which store LDAP and VARS.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)
===What Is the minimum size of the emulated flash storage?===
The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===What Is The Size Of the Flash Directory on the IPVA?===
As noted above, the virtual flash memory on the IPVA is defaulted to a size of 64MB. Most of the flash is used by the ''flash directory'' (FLASHDIR0) which amongst other things provides storage for PBX objects.

The size of the flash directory depends on the available RAM. The maximum of 900 segments á 64KB, i.e. ~56MB, is available if 192MB or more RAM is available. If less RAM is available, the size of the flash directory is decreased accordingly. For this reason, it is unsafe to reduce RAM size in a given IPVA, as the flash directory size may be decreased so that objects from the flash directory get lost.

The easiest method to see how much flash directory space is available is to investigate the boot trace. For the standard configuration of 64MB the respective trace output is going to look as follows and informs about a size of 14MB:

0:0000:081:4 - start flashdir FLASHDIR0
0:0000:081:4 - fdir: segments=901->224(14.0MB)

{{Limit_Virtual_IPVA_Flash}}

===How much RAM is required per IPVA instance?===
Since 12r2sr27/13r1sr5 the downloadable virtual appliance comes preconfigured with 256 MiB RAM. This amount is seen as a good trade-off for the majority of all installations. The IPVA need the amount of used flash 3-times at startup. The RAM-size can be administrated by VMware-means.

===What is the maximum amount of RAM?===
The maximum meaningful RAM setting is 3GB. Memory space beyond that limit will be left unused. Assigning more than 3GB to an IPVA instance doesn't provide any benefit.

===Why does ''General/Info/DRAM'' show less than the configured memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===What about Open VM Tools / VMware Tools?===
Tools like this are not supported / integrated because it is not needed. The Virtual Appliance provides his own operating system, and we don't need any of the VM-Tools features in our guest.

===What Can I Do In Case Of A Checksum Boot Error?===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
checksum wrong! Loading failed for image=IPVA BIN
</pre>
[[Image:ipva-crc-wrong.jpg|center|thumb|200px|ipva-crc-wrong.jpg/|/Ipva-crc-wrong.jpg]]

'''Solution'''
*Power-off the IPVA
*Replace the boot harddisk by a fresh one. The boot harddisk is the 1st hd(originally named ''hd-boot.vmdk'').

'''Remarks'''

This problem may occur on a system crash while a firmware update is taking place.

===What Can I Do In Case Of Boot-Problem: ''NIC unavailable!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
NIC unavailable!
</pre>
[[Image:ipva-nic-unavailable.jpg|center|thumb|200px|ipva-nic-unavailable.jpg/|/Ipva-nic-unavailable.jpg]]

'''Solution'''
*Power-off the IPVA
*Administrate by VMware means: Ensure the correct/expected type of network interface controller(NIC) is going to be offered by the hypervisor.

The IPVA offers driver support for:
*AMD NIC: Am79C970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller
**a.k.a ''PCNet32''
**a.k.a ''Vlance''

The AMD-NIC is kind of default. However, the NIC type may be overriden manually and accordingly within the configuration file ipva.vmx as follows
<pre>
ethernet0.virtualDev = "vlance"
</pre>

'''Remarks'''

This problem may occur after a VMware re-configuration of the network settings.

===What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
perfcounter-not enabled!!!
</pre>
[[Image:screenshot-ipva-perfcounter-nok.jpg|center|thumb|200px|screenshot-ipva-perfcounter-nok.jpg/|/Screenshot-ipva-perfcounter-nok.jpg]]

'''Solution''' 
This problem is likely caused by an OVA-import of the IPVA. The appliance's configuration file ''ipva.vmx'' requires a VMware proprietary configuration line that's not specifiable within an OVA-file.

The IPVA utilizes a VMware proprietary mechanism for its internal timekeeping<ref>Timekeeping in Virtual Machines http://www.vmware.com/pdf/vmware_timekeeping.pdf</ref>. That mechanism is only available after adding the following line to the configuration file ''ipva.vmx'':
<pre>
monitor_control.pseudo_perfctr = TRUE
</pre>
If that line is not present, the hypervisor is going to throw a CPU exception. Hint: In vSphere a VMX-file can be edited under '''Edit Settings/Options/Advanced/General/Configuration Parameters'''<ref>vmware Labs - How to edit vmx file in ESXi vSphere: https://www.youtube.com/watch?v=ICICoq-maB0</ref>

'''Remarks'''
*The vmx file should be edited after the installation of the IPVA.
*The vmx file should NOT be edited with Text editor (use vSphere as shown above)
*To our knowledge, a converter is always necessary for the installation with vmx.

===What Can I Do In Case Of Boot-Problem: ''Loading failed for image=IPVA BIN''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
Loading failed for image=IPVA BIN
</pre>
[[Image:Ipva-fw-load-failed.png|center|thumb|200px|ipva-fw-load-failed.png/|/Ipva-fw-load-failed.png]]

'''Solution''' 
This problem is likely caused by a calculation fault within the boot-code.
*The solution requires a replacement of the boot disk hd-boot.vmdk.
**Download an IPVA package from on 11r2 sr22.
**Replace the 1st disk with the one from the downloaded package

===Are Additional vCPUs useful?===
The Multi-Core functionality is an experimental functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==Notes==
<references/>

==Related Articles==
* [[{{NAMESPACE}}:Licenses|Reference15r1:Licenses]]
* [[Howto15r1:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance]]
* [[Howto:A_rough_estimate_of_IPVA_Performance]]

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

Reference16r1:Concept Innovaphone Virtual Appliance (IPVA)

2026-08-24T13:51:28Z

Slu: /* Settings */

==Applies To==
This information applies to:
*V16r1
*innovaphone Virtual Appliance
*Intel/AMD CPUs
* Virtualization platforms
**VMware
*** Workstation
*** Player
*** vSphere 4 - 8
*** ESXi 6 - 8
**Microsoft Hyper-V ([[{{NAMESPACE}}:Concept IPVA On Hyper-V|Concept IPVA On Hyper-V]])
*** Windows 8.1
*** Windows 10
*** Windows Server 2012 R2
*** Windows Server 2016 CTP4
**Linux based Hypervisors with [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM] and [https://en.wikipedia.org/wiki/QEMU QEMU] support
*** Proxmox VE 8.0 / 8.1 / 9.1

''Disclaimer: Manufacturers/versions of VM platforms other than those specified here have not been tested, so use at your own risk.''

''Disclaimer 2: We occasionally encounter customers experiencing unusual issues related to OpenStack. OpenStack is not officially supported, and such issues are not analyzed.''

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.

The IPVA is a software-only solution. It appears and behaves like an innovaphone "hard-box" without physical resources such as hardware DSP or ISDN interface.

==Package Overview==
We supply an OVF ('''O'''pen '''V'''irtualization '''F'''ormat) import or - depending on the virtualization platform - a suitable variant.
OVF is an open standard that contains several files in one package. The .ovf file is therefore an archive that contains all the necessary files.

=== Sample VMware ===
;ipva-ovf.zip:
The compressed archive ''ipva-ovf.zip'' contains the file ipva.ova. A deployment of ipva.ova will result in a set of 5 files - the file names may differ from the following list:
*ipva.vmx: The virtual machine configuration file
*hd-boot.vmdk: The virtual boot disk on IDE 0:0
*hd-cf.vmdk: The disk for emulation of a Compact Flash card on IDE 0:1
*hd-flash.vmdk: The disk for emulation of flash memory on IDE 1:0
*hd-dump.vmdk: The disk serving as a store for a crash dump on IDE 1:1

;ipva.bin:
The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

== Virtualization platforms ==

===VMware Player / VMware Workstation===
==== Import new Machine ====
*Copy the file ipva.ova to e.g. your desktop and Double-click on ipva.ova.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===VMware vSphere===
==== Import new Machine ====
*Import ipva.ova by means of '''File/Deploy OVF-Template...''' (de: '''Datei/OFV-Vorlage bereitstellen...''') and follow instructions.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===Microsoft Hyper-V===
==== Import new Machine ====
* Use the UI Wizard to Import a new machine
* Browse to the directory where the downloaded package was extracted to. Browse to the subdirectory Virtual Machines and click Ok
* Select ''Copy the Virtual Machine'' as ''Import Type''

===Proxmox VE===
==== Settings ====
Here, we list the VM settings that allowed us to successfully test the system and that ensure VMs run stably in production. These settings should be considered best practices.

===== PVE Version =====
* Version: 9.2.4
* Repositories: Enterprise repositories

===== Hardware =====
* Processors: 1 socket, 1 core, Type "Host" preferred, fallback "x86-64-v2-AES"
* Bios: SeaBIOS
* Machine: i440fx
* SCSI Controller: VirtIO SCSI single
* Hard Disks
** Datastore: Ceph (19.2.3) or local LVM
** Cache: No Cache
** Discard: Enable
** SSD emulation: Yes
** Async IO: io_uring
* Network Devices
** Model: VirtIO (paravirtualized)

===== Options =====
* OS Type: Other
* Boot Order: ide0, ide1, ide2, ide3
* QEMU Gust Agent: Disabled

==== Import new Machine ====
Import the "ova" file to your storage which is enabled for the type "import". After that you can select the created template an create new machines from it with the button "Import"

* Before you start up the VM in the UI you have to adjust the following configuration options:
** Hardware -> Processors: Adjust "Extra Cpu Flags" -> "aes" if required
** Hardware -> SCSI Controller: Change Model to "VirtIO SCSI Single"
** Hardware -> Network Device (net0 / net1): Change Model to "VirtIO (paravirtualized)"

==Configuration==

===Network Configuration===
The IPVA is preconfigured a DHCP client. You will see the current IP-Address in the console-screen of the VM. If there's in no case a DHCP server available for the 1st-time configuration, you can set your IP-Configuration in the console.

config change IP0 ETH0 /addr 192.168.0.10 /mask 255.255.255.0
config change IP0 RT0 /gateway 192.168.0.1
config change DHCP0 /mode off
config write
reset

====MAC/serial number====
Take care that you use a MAC address which is supported by my.innovaphone, see [[Reference:My_Innovaphone#IPVA_MAC_exists]].

===AES Hardware Acceleration===
It may be beneficial to activate hardware acceleration for AES operations.
Whether hardware acceleration is activated can be checked with the command <code>!mod cmd CPU cpu-info</code>.

* The "flags" attribute must contain "aesni"
* The "act-features" attribute must contain "has_aesni"

Example:
<info>
<cpu
vendor="GenuineIntel"
signature="0x906e9"
brand="Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz"
...
flags="sse3 pclmulqdq ssse3 sse4_1 sse4_2 aesni xsave xsaveopt osxsave avx f16c rdrand fpu mmx fxsr sse sse2 avx2"
act-features="has_aesni has_avx has_vaesni has_vpclmulqdq" srtp-mips="5"/>
</info>

==Large IPVA with 512 MiB Flash==
In some scenarios the standard 64 MiB flash memory is not enough to store all user data. It is possible to manually enlarge the flash memory of an IPVA up to 512 MiB.

You have to change the settings of the virtual machine and format the flash. You cannot do it with an already configured machine, because you will lose all your configuration!

# shutdown the IPVA
# increase the RAM to 3.072 MiB
# increase the size of '''IDE1:0''' to 512 MiB or recreate it
# power up the IPVA
# format the flash: <code>!mod cmd FLASHMAN0 reset all</code>
# reboot the IPVA: <code>!reset</code>

You can check the free space with the command <code>!mod cmd FLASHMAN0 info</code>. You will see a big amount of available segments

segments=675, segment-size=0x10000 (64k)
LDAP - used 1k avail 63k owned 64k (segments 1) maximum 517056k (segments 8079, configured 8079)
VARS - used 23k avail 16k owned 192k (segments 3) maximum 640k (segments 10, configured 10)

But please keep in mind, the more data is saved, the longer it takes to reboot and load the UI in the [[{{NAMESPACE}}:PBX/Objects|PBX/Objects]] area.

==Troubleshooting==
Support procedures are commonly identical to the ones known from innovaphones' physical appliances. Except for:
*'''Post-Mortem Logs''' A post-mortem log must be retrieved by clicking on ''Maintenance/Diagnostics/Tracing/'''trace(crash-dump)''''' (alternatively: http://a.b.c.d/crash_dump.txt).

==Known Issues==

=== Maximal 3.072 MiB RAM ===
Because the IPVA has no [https://en.wikipedia.org/wiki/Virtual_memory virtual memory management], it will use only the first linear 3 GiB of RAM. But please keep in mind, that the flash content will be stored 3-times (Flashmanager, Flashdirectory, PBX) in RAM at startup.
=== Restored IPVA may not run ===
We have seen issues where an IPVA which had been backed up using one of the available backup tools for VMWare do not start up properly when they have been restored.

We strongly suggest to not rely on VMWare backup mechanism but instead to use the standard innovaphone backup scheme (that is, save the configuration on a regular basis).

==== How to run a restored backup that fails to start ====
Here is the procedure to run an IPVA from an IPVA if the restored virtual machine does not boot up properly:

* restore the backed up V10 IPVA
* create a new, empty V11r1 IPVA (you will need this merely to copy the boot disk from)
*replace the boot disk of the failing V10 IPVA by the boot disk of the fresh V11r1 IPVA (see [[#How To Replace The Boot Disk On vSphere.3F| How To Replace The Boot Disk On vSphere]] for details)
* start the restored and fixed V10 IPVA (it should run fine now)
* downgrade this V10 IPVA to desired V10 firmware
* remove the fresh V11r1 IPVA

Some Customer who are running Fw v12r1 (up to sr6) with ESXi 6.0 and VEEAM 9 reported that after a backup with VEEAM 9, the restored IPVA was not starting.
At this point, there is no possibility to solve this problem. The only workaround in that case is to delete the machine, reinstall a new one, and restore a configuration saved before.

If you did not run into the problem yet, for prevention, we recommend to replace the Boot disk of your working IPVA.vmx with one of the IPVA.ova. Please follow the steps below (be aware that this will upgrade the firmware on the IPVA to 12r2, due to the fact that actually, IPVA.ova is only available from version 12r2):

1. Remove the Boot disk of the virtual machine (vmx)(is normaly the first one). 
* Power off the VM
* Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Remove''.
* Click ''OK'' to save your changes.

2. Add the Boot disk of the ova virtual machine to the vmx one.
* Identify the size of the boot disk of the ova virtual machine (will be needed on the step when navigating to boot disk)
* On the powered off VM, Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Add''.
* Select Use “an existing virtual disk” then click ''Next''.
* Navigate to the boot disk of the ova Virtual machine then click ''next''.
* Click ''Finish''.
Now the vmx virtual machine should have the Fw version 12r2.

The .ova version will be available also in V12r1 sr7

=== IPVA does not run on Citrix Cloud Platform ===
Reportedly, the Citrix cloud platform - although based on VMware - cannot run the IPVA. Amongst other issues, the platform does not allow 4 virtual disks, which are required for the IPVA.

=== IPVA does not run on VCloud Air ===
VCloud Air apparently does not support the timekeeping mechanism required by the IPVA.

[[User:Ckl|ckl]] 15:50, 30 November 2016 (CET) We have seen the IPVA v12r2 running on vCloud Air. Use the ova import.

=== IPVA on ESX 6.5 ===
We have reports that the IPVA does not run properly on ESX 6.5. The IPVA boots up properly but the clock does not run. Running the .ova based variation available in v12r2 fixed the issue or edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

=== Administration: Avoid 'reboot' Command. Use 'reset' Command ===
Alwas use the 'reset' command to restart an IPVA.
The 'reboot' command makes sense only on physical applicances, where its purpose is to deploy a new bootcode by means of a forced watchdog trap. The resulting post-reboot state will be as if an unsolicited trap/crash had occurred.

=== Voice Quality Issues ===
When dealing with media streams (e.g. for announcements), the IPVA needs to fulfil real-time processing requirements, for example to process RTP packets in a timely fashion. To do so, the IPVA relies on the capabilities of the virtualization platform it runs on.

It is therefore important to configure the platform so that it supports real-time applications best. If you experience voice quality or latency issues, consider
* to make sure that all of the IPVAs memory is ''reserved'' to the IPVA (''Latency Sensitivity'' set to ''High'')
* to guarantee exclusive PCPU access
This helps to reduce CPU halt/wake-up states.

===Additional vCPUs may cause problems===
The Multi-Core functionality of version 13r2 is a beta functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==FAQ==
===Can The emulated compact-flash disk size be increased?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated compact-flash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given. Please note: The compact-flash disk is not the flash which store LDAP and VARS.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)
===What Is the minimum size of the emulated flash storage?===
The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===What Is The Size Of the Flash Directory on the IPVA?===
As noted above, the virtual flash memory on the IPVA is defaulted to a size of 64MB. Most of the flash is used by the ''flash directory'' (FLASHDIR0) which amongst other things provides storage for PBX objects.

The size of the flash directory depends on the available RAM. The maximum of 900 segments á 64KB, i.e. ~56MB, is available if 192MB or more RAM is available. If less RAM is available, the size of the flash directory is decreased accordingly. For this reason, it is unsafe to reduce RAM size in a given IPVA, as the flash directory size may be decreased so that objects from the flash directory get lost.

The easiest method to see how much flash directory space is available is to investigate the boot trace. For the standard configuration of 64MB the respective trace output is going to look as follows and informs about a size of 14MB:

0:0000:081:4 - start flashdir FLASHDIR0
0:0000:081:4 - fdir: segments=901->224(14.0MB)

{{Limit_Virtual_IPVA_Flash}}

===How much RAM is required per IPVA instance?===
Since 12r2sr27/13r1sr5 the downloadable virtual appliance comes preconfigured with 256 MiB RAM. This amount is seen as a good trade-off for the majority of all installations. The IPVA need the amount of used flash 3-times at startup. The RAM-size can be administrated by VMware-means.

===What is the maximum amount of RAM?===
The maximum meaningful RAM setting is 3GB. Memory space beyond that limit will be left unused. Assigning more than 3GB to an IPVA instance doesn't provide any benefit.

===Why does ''General/Info/DRAM'' show less than the configured memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===What about Open VM Tools / VMware Tools?===
Tools like this are not supported / integrated because it is not needed. The Virtual Appliance provides his own operating system, and we don't need any of the VM-Tools features in our guest.

===What Can I Do In Case Of A Checksum Boot Error?===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
checksum wrong! Loading failed for image=IPVA BIN
</pre>
[[Image:ipva-crc-wrong.jpg|center|thumb|200px|ipva-crc-wrong.jpg/|/Ipva-crc-wrong.jpg]]

'''Solution'''
*Power-off the IPVA
*Replace the boot harddisk by a fresh one. The boot harddisk is the 1st hd(originally named ''hd-boot.vmdk'').

'''Remarks'''

This problem may occur on a system crash while a firmware update is taking place.

===What Can I Do In Case Of Boot-Problem: ''NIC unavailable!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
NIC unavailable!
</pre>
[[Image:ipva-nic-unavailable.jpg|center|thumb|200px|ipva-nic-unavailable.jpg/|/Ipva-nic-unavailable.jpg]]

'''Solution'''
*Power-off the IPVA
*Administrate by VMware means: Ensure the correct/expected type of network interface controller(NIC) is going to be offered by the hypervisor.

The IPVA offers driver support for:
*AMD NIC: Am79C970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller
**a.k.a ''PCNet32''
**a.k.a ''Vlance''

The AMD-NIC is kind of default. However, the NIC type may be overriden manually and accordingly within the configuration file ipva.vmx as follows
<pre>
ethernet0.virtualDev = "vlance"
</pre>

'''Remarks'''

This problem may occur after a VMware re-configuration of the network settings.

===What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
perfcounter-not enabled!!!
</pre>
[[Image:screenshot-ipva-perfcounter-nok.jpg|center|thumb|200px|screenshot-ipva-perfcounter-nok.jpg/|/Screenshot-ipva-perfcounter-nok.jpg]]

'''Solution''' 
This problem is likely caused by an OVA-import of the IPVA. The appliance's configuration file ''ipva.vmx'' requires a VMware proprietary configuration line that's not specifiable within an OVA-file.

The IPVA utilizes a VMware proprietary mechanism for its internal timekeeping<ref>Timekeeping in Virtual Machines http://www.vmware.com/pdf/vmware_timekeeping.pdf</ref>. That mechanism is only available after adding the following line to the configuration file ''ipva.vmx'':
<pre>
monitor_control.pseudo_perfctr = TRUE
</pre>
If that line is not present, the hypervisor is going to throw a CPU exception. Hint: In vSphere a VMX-file can be edited under '''Edit Settings/Options/Advanced/General/Configuration Parameters'''<ref>vmware Labs - How to edit vmx file in ESXi vSphere: https://www.youtube.com/watch?v=ICICoq-maB0</ref>

'''Remarks'''
*The vmx file should be edited after the installation of the IPVA.
*The vmx file should NOT be edited with Text editor (use vSphere as shown above)
*To our knowledge, a converter is always necessary for the installation with vmx.

===What Can I Do In Case Of Boot-Problem: ''Loading failed for image=IPVA BIN''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
Loading failed for image=IPVA BIN
</pre>
[[Image:Ipva-fw-load-failed.png|center|thumb|200px|ipva-fw-load-failed.png/|/Ipva-fw-load-failed.png]]

'''Solution''' 
This problem is likely caused by a calculation fault within the boot-code.
*The solution requires a replacement of the boot disk hd-boot.vmdk.
**Download an IPVA package from on 11r2 sr22.
**Replace the 1st disk with the one from the downloaded package

===Are Additional vCPUs useful?===
The Multi-Core functionality is an experimental functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==Notes==
<references/>

==Related Articles==
* [[{{NAMESPACE}}:Licenses|Reference15r1:Licenses]]
* [[Howto15r1:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance]]
* [[Howto:A_rough_estimate_of_IPVA_Performance]]

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

Reference16r1:Concept Innovaphone Virtual Appliance (IPVA)

2026-08-24T13:47:34Z

Slu: /* Settings */

==Applies To==
This information applies to:
*V16r1
*innovaphone Virtual Appliance
*Intel/AMD CPUs
* Virtualization platforms
**VMware
*** Workstation
*** Player
*** vSphere 4 - 8
*** ESXi 6 - 8
**Microsoft Hyper-V ([[{{NAMESPACE}}:Concept IPVA On Hyper-V|Concept IPVA On Hyper-V]])
*** Windows 8.1
*** Windows 10
*** Windows Server 2012 R2
*** Windows Server 2016 CTP4
**Linux based Hypervisors with [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM] and [https://en.wikipedia.org/wiki/QEMU QEMU] support
*** Proxmox VE 8.0 / 8.1 / 9.1

''Disclaimer: Manufacturers/versions of VM platforms other than those specified here have not been tested, so use at your own risk.''

''Disclaimer 2: We occasionally encounter customers experiencing unusual issues related to OpenStack. OpenStack is not officially supported, and such issues are not analyzed.''

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.

The IPVA is a software-only solution. It appears and behaves like an innovaphone "hard-box" without physical resources such as hardware DSP or ISDN interface.

==Package Overview==
We supply an OVF ('''O'''pen '''V'''irtualization '''F'''ormat) import or - depending on the virtualization platform - a suitable variant.
OVF is an open standard that contains several files in one package. The .ovf file is therefore an archive that contains all the necessary files.

=== Sample VMware ===
;ipva-ovf.zip:
The compressed archive ''ipva-ovf.zip'' contains the file ipva.ova. A deployment of ipva.ova will result in a set of 5 files - the file names may differ from the following list:
*ipva.vmx: The virtual machine configuration file
*hd-boot.vmdk: The virtual boot disk on IDE 0:0
*hd-cf.vmdk: The disk for emulation of a Compact Flash card on IDE 0:1
*hd-flash.vmdk: The disk for emulation of flash memory on IDE 1:0
*hd-dump.vmdk: The disk serving as a store for a crash dump on IDE 1:1

;ipva.bin:
The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

== Virtualization platforms ==

===VMware Player / VMware Workstation===
==== Import new Machine ====
*Copy the file ipva.ova to e.g. your desktop and Double-click on ipva.ova.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===VMware vSphere===
==== Import new Machine ====
*Import ipva.ova by means of '''File/Deploy OVF-Template...''' (de: '''Datei/OFV-Vorlage bereitstellen...''') and follow instructions.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===Microsoft Hyper-V===
==== Import new Machine ====
* Use the UI Wizard to Import a new machine
* Browse to the directory where the downloaded package was extracted to. Browse to the subdirectory Virtual Machines and click Ok
* Select ''Copy the Virtual Machine'' as ''Import Type''

===Proxmox VE===
==== Settings ====
Here, we list the VM settings that allowed us to successfully test the system and that ensure VMs run stably in production. These settings should be considered best practices.

===== Hardware =====
* Processors: 1 socket, 1 core, Type "Host" preferred, fallback "x86-64-v2-AES"
* Bios: SeaBIOS
* Machine: i440fx
* SCSI Controller: VirtIO SCSI single
* Hard Disks
** Datastore: Ceph (19.2.3) or local LVM
** Cache: No Cache
** Discard: Enable
** SSD emulation: Yes
** Async IO: io_uring
* Network Devices
** Model: VirtIO (paravirtualized)

===== Options =====
* OS Type: Other
* Boot Order: ide0, ide1, ide2, ide3
* QEMU Gust Agent: Disabled

==== Import new Machine ====
Import the "ova" file to your storage which is enabled for the type "import". After that you can select the created template an create new machines from it with the button "Import"

* Before you start up the VM in the UI you have to adjust the following configuration options:
** Hardware -> Processors: Adjust "Extra Cpu Flags" -> "aes" if required
** Hardware -> SCSI Controller: Change Model to "VirtIO SCSI Single"
** Hardware -> Network Device (net0 / net1): Change Model to "VirtIO (paravirtualized)"

==Configuration==

===Network Configuration===
The IPVA is preconfigured a DHCP client. You will see the current IP-Address in the console-screen of the VM. If there's in no case a DHCP server available for the 1st-time configuration, you can set your IP-Configuration in the console.

config change IP0 ETH0 /addr 192.168.0.10 /mask 255.255.255.0
config change IP0 RT0 /gateway 192.168.0.1
config change DHCP0 /mode off
config write
reset

====MAC/serial number====
Take care that you use a MAC address which is supported by my.innovaphone, see [[Reference:My_Innovaphone#IPVA_MAC_exists]].

===AES Hardware Acceleration===
It may be beneficial to activate hardware acceleration for AES operations.
Whether hardware acceleration is activated can be checked with the command <code>!mod cmd CPU cpu-info</code>.

* The "flags" attribute must contain "aesni"
* The "act-features" attribute must contain "has_aesni"

Example:
<info>
<cpu
vendor="GenuineIntel"
signature="0x906e9"
brand="Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz"
...
flags="sse3 pclmulqdq ssse3 sse4_1 sse4_2 aesni xsave xsaveopt osxsave avx f16c rdrand fpu mmx fxsr sse sse2 avx2"
act-features="has_aesni has_avx has_vaesni has_vpclmulqdq" srtp-mips="5"/>
</info>

==Large IPVA with 512 MiB Flash==
In some scenarios the standard 64 MiB flash memory is not enough to store all user data. It is possible to manually enlarge the flash memory of an IPVA up to 512 MiB.

You have to change the settings of the virtual machine and format the flash. You cannot do it with an already configured machine, because you will lose all your configuration!

# shutdown the IPVA
# increase the RAM to 3.072 MiB
# increase the size of '''IDE1:0''' to 512 MiB or recreate it
# power up the IPVA
# format the flash: <code>!mod cmd FLASHMAN0 reset all</code>
# reboot the IPVA: <code>!reset</code>

You can check the free space with the command <code>!mod cmd FLASHMAN0 info</code>. You will see a big amount of available segments

segments=675, segment-size=0x10000 (64k)
LDAP - used 1k avail 63k owned 64k (segments 1) maximum 517056k (segments 8079, configured 8079)
VARS - used 23k avail 16k owned 192k (segments 3) maximum 640k (segments 10, configured 10)

But please keep in mind, the more data is saved, the longer it takes to reboot and load the UI in the [[{{NAMESPACE}}:PBX/Objects|PBX/Objects]] area.

==Troubleshooting==
Support procedures are commonly identical to the ones known from innovaphones' physical appliances. Except for:
*'''Post-Mortem Logs''' A post-mortem log must be retrieved by clicking on ''Maintenance/Diagnostics/Tracing/'''trace(crash-dump)''''' (alternatively: http://a.b.c.d/crash_dump.txt).

==Known Issues==

=== Maximal 3.072 MiB RAM ===
Because the IPVA has no [https://en.wikipedia.org/wiki/Virtual_memory virtual memory management], it will use only the first linear 3 GiB of RAM. But please keep in mind, that the flash content will be stored 3-times (Flashmanager, Flashdirectory, PBX) in RAM at startup.
=== Restored IPVA may not run ===
We have seen issues where an IPVA which had been backed up using one of the available backup tools for VMWare do not start up properly when they have been restored.

We strongly suggest to not rely on VMWare backup mechanism but instead to use the standard innovaphone backup scheme (that is, save the configuration on a regular basis).

==== How to run a restored backup that fails to start ====
Here is the procedure to run an IPVA from an IPVA if the restored virtual machine does not boot up properly:

* restore the backed up V10 IPVA
* create a new, empty V11r1 IPVA (you will need this merely to copy the boot disk from)
*replace the boot disk of the failing V10 IPVA by the boot disk of the fresh V11r1 IPVA (see [[#How To Replace The Boot Disk On vSphere.3F| How To Replace The Boot Disk On vSphere]] for details)
* start the restored and fixed V10 IPVA (it should run fine now)
* downgrade this V10 IPVA to desired V10 firmware
* remove the fresh V11r1 IPVA

Some Customer who are running Fw v12r1 (up to sr6) with ESXi 6.0 and VEEAM 9 reported that after a backup with VEEAM 9, the restored IPVA was not starting.
At this point, there is no possibility to solve this problem. The only workaround in that case is to delete the machine, reinstall a new one, and restore a configuration saved before.

If you did not run into the problem yet, for prevention, we recommend to replace the Boot disk of your working IPVA.vmx with one of the IPVA.ova. Please follow the steps below (be aware that this will upgrade the firmware on the IPVA to 12r2, due to the fact that actually, IPVA.ova is only available from version 12r2):

1. Remove the Boot disk of the virtual machine (vmx)(is normaly the first one). 
* Power off the VM
* Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Remove''.
* Click ''OK'' to save your changes.

2. Add the Boot disk of the ova virtual machine to the vmx one.
* Identify the size of the boot disk of the ova virtual machine (will be needed on the step when navigating to boot disk)
* On the powered off VM, Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Add''.
* Select Use “an existing virtual disk” then click ''Next''.
* Navigate to the boot disk of the ova Virtual machine then click ''next''.
* Click ''Finish''.
Now the vmx virtual machine should have the Fw version 12r2.

The .ova version will be available also in V12r1 sr7

=== IPVA does not run on Citrix Cloud Platform ===
Reportedly, the Citrix cloud platform - although based on VMware - cannot run the IPVA. Amongst other issues, the platform does not allow 4 virtual disks, which are required for the IPVA.

=== IPVA does not run on VCloud Air ===
VCloud Air apparently does not support the timekeeping mechanism required by the IPVA.

[[User:Ckl|ckl]] 15:50, 30 November 2016 (CET) We have seen the IPVA v12r2 running on vCloud Air. Use the ova import.

=== IPVA on ESX 6.5 ===
We have reports that the IPVA does not run properly on ESX 6.5. The IPVA boots up properly but the clock does not run. Running the .ova based variation available in v12r2 fixed the issue or edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

=== Administration: Avoid 'reboot' Command. Use 'reset' Command ===
Alwas use the 'reset' command to restart an IPVA.
The 'reboot' command makes sense only on physical applicances, where its purpose is to deploy a new bootcode by means of a forced watchdog trap. The resulting post-reboot state will be as if an unsolicited trap/crash had occurred.

=== Voice Quality Issues ===
When dealing with media streams (e.g. for announcements), the IPVA needs to fulfil real-time processing requirements, for example to process RTP packets in a timely fashion. To do so, the IPVA relies on the capabilities of the virtualization platform it runs on.

It is therefore important to configure the platform so that it supports real-time applications best. If you experience voice quality or latency issues, consider
* to make sure that all of the IPVAs memory is ''reserved'' to the IPVA (''Latency Sensitivity'' set to ''High'')
* to guarantee exclusive PCPU access
This helps to reduce CPU halt/wake-up states.

===Additional vCPUs may cause problems===
The Multi-Core functionality of version 13r2 is a beta functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==FAQ==
===Can The emulated compact-flash disk size be increased?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated compact-flash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given. Please note: The compact-flash disk is not the flash which store LDAP and VARS.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)
===What Is the minimum size of the emulated flash storage?===
The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===What Is The Size Of the Flash Directory on the IPVA?===
As noted above, the virtual flash memory on the IPVA is defaulted to a size of 64MB. Most of the flash is used by the ''flash directory'' (FLASHDIR0) which amongst other things provides storage for PBX objects.

The size of the flash directory depends on the available RAM. The maximum of 900 segments á 64KB, i.e. ~56MB, is available if 192MB or more RAM is available. If less RAM is available, the size of the flash directory is decreased accordingly. For this reason, it is unsafe to reduce RAM size in a given IPVA, as the flash directory size may be decreased so that objects from the flash directory get lost.

The easiest method to see how much flash directory space is available is to investigate the boot trace. For the standard configuration of 64MB the respective trace output is going to look as follows and informs about a size of 14MB:

0:0000:081:4 - start flashdir FLASHDIR0
0:0000:081:4 - fdir: segments=901->224(14.0MB)

{{Limit_Virtual_IPVA_Flash}}

===How much RAM is required per IPVA instance?===
Since 12r2sr27/13r1sr5 the downloadable virtual appliance comes preconfigured with 256 MiB RAM. This amount is seen as a good trade-off for the majority of all installations. The IPVA need the amount of used flash 3-times at startup. The RAM-size can be administrated by VMware-means.

===What is the maximum amount of RAM?===
The maximum meaningful RAM setting is 3GB. Memory space beyond that limit will be left unused. Assigning more than 3GB to an IPVA instance doesn't provide any benefit.

===Why does ''General/Info/DRAM'' show less than the configured memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===What about Open VM Tools / VMware Tools?===
Tools like this are not supported / integrated because it is not needed. The Virtual Appliance provides his own operating system, and we don't need any of the VM-Tools features in our guest.

===What Can I Do In Case Of A Checksum Boot Error?===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
checksum wrong! Loading failed for image=IPVA BIN
</pre>
[[Image:ipva-crc-wrong.jpg|center|thumb|200px|ipva-crc-wrong.jpg/|/Ipva-crc-wrong.jpg]]

'''Solution'''
*Power-off the IPVA
*Replace the boot harddisk by a fresh one. The boot harddisk is the 1st hd(originally named ''hd-boot.vmdk'').

'''Remarks'''

This problem may occur on a system crash while a firmware update is taking place.

===What Can I Do In Case Of Boot-Problem: ''NIC unavailable!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
NIC unavailable!
</pre>
[[Image:ipva-nic-unavailable.jpg|center|thumb|200px|ipva-nic-unavailable.jpg/|/Ipva-nic-unavailable.jpg]]

'''Solution'''
*Power-off the IPVA
*Administrate by VMware means: Ensure the correct/expected type of network interface controller(NIC) is going to be offered by the hypervisor.

The IPVA offers driver support for:
*AMD NIC: Am79C970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller
**a.k.a ''PCNet32''
**a.k.a ''Vlance''

The AMD-NIC is kind of default. However, the NIC type may be overriden manually and accordingly within the configuration file ipva.vmx as follows
<pre>
ethernet0.virtualDev = "vlance"
</pre>

'''Remarks'''

This problem may occur after a VMware re-configuration of the network settings.

===What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
perfcounter-not enabled!!!
</pre>
[[Image:screenshot-ipva-perfcounter-nok.jpg|center|thumb|200px|screenshot-ipva-perfcounter-nok.jpg/|/Screenshot-ipva-perfcounter-nok.jpg]]

'''Solution''' 
This problem is likely caused by an OVA-import of the IPVA. The appliance's configuration file ''ipva.vmx'' requires a VMware proprietary configuration line that's not specifiable within an OVA-file.

The IPVA utilizes a VMware proprietary mechanism for its internal timekeeping<ref>Timekeeping in Virtual Machines http://www.vmware.com/pdf/vmware_timekeeping.pdf</ref>. That mechanism is only available after adding the following line to the configuration file ''ipva.vmx'':
<pre>
monitor_control.pseudo_perfctr = TRUE
</pre>
If that line is not present, the hypervisor is going to throw a CPU exception. Hint: In vSphere a VMX-file can be edited under '''Edit Settings/Options/Advanced/General/Configuration Parameters'''<ref>vmware Labs - How to edit vmx file in ESXi vSphere: https://www.youtube.com/watch?v=ICICoq-maB0</ref>

'''Remarks'''
*The vmx file should be edited after the installation of the IPVA.
*The vmx file should NOT be edited with Text editor (use vSphere as shown above)
*To our knowledge, a converter is always necessary for the installation with vmx.

===What Can I Do In Case Of Boot-Problem: ''Loading failed for image=IPVA BIN''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
Loading failed for image=IPVA BIN
</pre>
[[Image:Ipva-fw-load-failed.png|center|thumb|200px|ipva-fw-load-failed.png/|/Ipva-fw-load-failed.png]]

'''Solution''' 
This problem is likely caused by a calculation fault within the boot-code.
*The solution requires a replacement of the boot disk hd-boot.vmdk.
**Download an IPVA package from on 11r2 sr22.
**Replace the 1st disk with the one from the downloaded package

===Are Additional vCPUs useful?===
The Multi-Core functionality is an experimental functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==Notes==
<references/>

==Related Articles==
* [[{{NAMESPACE}}:Licenses|Reference15r1:Licenses]]
* [[Howto15r1:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance]]
* [[Howto:A_rough_estimate_of_IPVA_Performance]]

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

Reference16r1:Concept Innovaphone Virtual Appliance (IPVA)

2026-08-24T11:24:48Z

Slu: /* Hardware */

==Applies To==
This information applies to:
*V16r1
*innovaphone Virtual Appliance
*Intel/AMD CPUs
* Virtualization platforms
**VMware
*** Workstation
*** Player
*** vSphere 4 - 8
*** ESXi 6 - 8
**Microsoft Hyper-V ([[{{NAMESPACE}}:Concept IPVA On Hyper-V|Concept IPVA On Hyper-V]])
*** Windows 8.1
*** Windows 10
*** Windows Server 2012 R2
*** Windows Server 2016 CTP4
**Linux based Hypervisors with [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM] and [https://en.wikipedia.org/wiki/QEMU QEMU] support
*** Proxmox VE 8.0 / 8.1 / 9.1

''Disclaimer: Manufacturers/versions of VM platforms other than those specified here have not been tested, so use at your own risk.''

''Disclaimer 2: We occasionally encounter customers experiencing unusual issues related to OpenStack. OpenStack is not officially supported, and such issues are not analyzed.''

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.

The IPVA is a software-only solution. It appears and behaves like an innovaphone "hard-box" without physical resources such as hardware DSP or ISDN interface.

==Package Overview==
We supply an OVF ('''O'''pen '''V'''irtualization '''F'''ormat) import or - depending on the virtualization platform - a suitable variant.
OVF is an open standard that contains several files in one package. The .ovf file is therefore an archive that contains all the necessary files.

=== Sample VMware ===
;ipva-ovf.zip:
The compressed archive ''ipva-ovf.zip'' contains the file ipva.ova. A deployment of ipva.ova will result in a set of 5 files - the file names may differ from the following list:
*ipva.vmx: The virtual machine configuration file
*hd-boot.vmdk: The virtual boot disk on IDE 0:0
*hd-cf.vmdk: The disk for emulation of a Compact Flash card on IDE 0:1
*hd-flash.vmdk: The disk for emulation of flash memory on IDE 1:0
*hd-dump.vmdk: The disk serving as a store for a crash dump on IDE 1:1

;ipva.bin:
The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

== Virtualization platforms ==

===VMware Player / VMware Workstation===
==== Import new Machine ====
*Copy the file ipva.ova to e.g. your desktop and Double-click on ipva.ova.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===VMware vSphere===
==== Import new Machine ====
*Import ipva.ova by means of '''File/Deploy OVF-Template...''' (de: '''Datei/OFV-Vorlage bereitstellen...''') and follow instructions.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===Microsoft Hyper-V===
==== Import new Machine ====
* Use the UI Wizard to Import a new machine
* Browse to the directory where the downloaded package was extracted to. Browse to the subdirectory Virtual Machines and click Ok
* Select ''Copy the Virtual Machine'' as ''Import Type''

===Proxmox VE===
==== Settings ====
===== Hardware =====
* Processors: 1 socket, 1 core, Type "Host" preferred, fallback "x86-64-v2-AES"
* Bios: SeaBIOS
* Machine: i440fx
* SCSI Controller: VirtIO SCSI single
* Hard Disks
** Dadstore: Ceph (19.2.3) or local LVM
** Cache: No Cache
** Discard: Enable
** SSD emulation: Yes
** Async IO: io_uring
* Network Devices
** Model: VirtIO (paravirtualized)

===== Options =====
* OS Type: Other
* Boot Order: ide0, ide1, ide2, ide3
* QEMU Gust Agent: Disabled

==== Import new Machine ====
Import the "ova" file to your storage which is enabled for the type "import". After that you can select the created template an create new machines from it with the button "Import"

* Before you start up the VM in the UI you have to adjust the following configuration options:
** Hardware -> Processors: Adjust "Extra Cpu Flags" -> "aes" if required
** Hardware -> SCSI Controller: Change Model to "VirtIO SCSI Single"
** Hardware -> Network Device (net0 / net1): Change Model to "VirtIO (paravirtualized)"

==Configuration==

===Network Configuration===
The IPVA is preconfigured a DHCP client. You will see the current IP-Address in the console-screen of the VM. If there's in no case a DHCP server available for the 1st-time configuration, you can set your IP-Configuration in the console.

config change IP0 ETH0 /addr 192.168.0.10 /mask 255.255.255.0
config change IP0 RT0 /gateway 192.168.0.1
config change DHCP0 /mode off
config write
reset

====MAC/serial number====
Take care that you use a MAC address which is supported by my.innovaphone, see [[Reference:My_Innovaphone#IPVA_MAC_exists]].

===AES Hardware Acceleration===
It may be beneficial to activate hardware acceleration for AES operations.
Whether hardware acceleration is activated can be checked with the command <code>!mod cmd CPU cpu-info</code>.

* The "flags" attribute must contain "aesni"
* The "act-features" attribute must contain "has_aesni"

Example:
<info>
<cpu
vendor="GenuineIntel"
signature="0x906e9"
brand="Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz"
...
flags="sse3 pclmulqdq ssse3 sse4_1 sse4_2 aesni xsave xsaveopt osxsave avx f16c rdrand fpu mmx fxsr sse sse2 avx2"
act-features="has_aesni has_avx has_vaesni has_vpclmulqdq" srtp-mips="5"/>
</info>

==Large IPVA with 512 MiB Flash==
In some scenarios the standard 64 MiB flash memory is not enough to store all user data. It is possible to manually enlarge the flash memory of an IPVA up to 512 MiB.

You have to change the settings of the virtual machine and format the flash. You cannot do it with an already configured machine, because you will lose all your configuration!

# shutdown the IPVA
# increase the RAM to 3.072 MiB
# increase the size of '''IDE1:0''' to 512 MiB or recreate it
# power up the IPVA
# format the flash: <code>!mod cmd FLASHMAN0 reset all</code>
# reboot the IPVA: <code>!reset</code>

You can check the free space with the command <code>!mod cmd FLASHMAN0 info</code>. You will see a big amount of available segments

segments=675, segment-size=0x10000 (64k)
LDAP - used 1k avail 63k owned 64k (segments 1) maximum 517056k (segments 8079, configured 8079)
VARS - used 23k avail 16k owned 192k (segments 3) maximum 640k (segments 10, configured 10)

But please keep in mind, the more data is saved, the longer it takes to reboot and load the UI in the [[{{NAMESPACE}}:PBX/Objects|PBX/Objects]] area.

==Troubleshooting==
Support procedures are commonly identical to the ones known from innovaphones' physical appliances. Except for:
*'''Post-Mortem Logs''' A post-mortem log must be retrieved by clicking on ''Maintenance/Diagnostics/Tracing/'''trace(crash-dump)''''' (alternatively: http://a.b.c.d/crash_dump.txt).

==Known Issues==

=== Maximal 3.072 MiB RAM ===
Because the IPVA has no [https://en.wikipedia.org/wiki/Virtual_memory virtual memory management], it will use only the first linear 3 GiB of RAM. But please keep in mind, that the flash content will be stored 3-times (Flashmanager, Flashdirectory, PBX) in RAM at startup.
=== Restored IPVA may not run ===
We have seen issues where an IPVA which had been backed up using one of the available backup tools for VMWare do not start up properly when they have been restored.

We strongly suggest to not rely on VMWare backup mechanism but instead to use the standard innovaphone backup scheme (that is, save the configuration on a regular basis).

==== How to run a restored backup that fails to start ====
Here is the procedure to run an IPVA from an IPVA if the restored virtual machine does not boot up properly:

* restore the backed up V10 IPVA
* create a new, empty V11r1 IPVA (you will need this merely to copy the boot disk from)
*replace the boot disk of the failing V10 IPVA by the boot disk of the fresh V11r1 IPVA (see [[#How To Replace The Boot Disk On vSphere.3F| How To Replace The Boot Disk On vSphere]] for details)
* start the restored and fixed V10 IPVA (it should run fine now)
* downgrade this V10 IPVA to desired V10 firmware
* remove the fresh V11r1 IPVA

Some Customer who are running Fw v12r1 (up to sr6) with ESXi 6.0 and VEEAM 9 reported that after a backup with VEEAM 9, the restored IPVA was not starting.
At this point, there is no possibility to solve this problem. The only workaround in that case is to delete the machine, reinstall a new one, and restore a configuration saved before.

If you did not run into the problem yet, for prevention, we recommend to replace the Boot disk of your working IPVA.vmx with one of the IPVA.ova. Please follow the steps below (be aware that this will upgrade the firmware on the IPVA to 12r2, due to the fact that actually, IPVA.ova is only available from version 12r2):

1. Remove the Boot disk of the virtual machine (vmx)(is normaly the first one). 
* Power off the VM
* Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Remove''.
* Click ''OK'' to save your changes.

2. Add the Boot disk of the ova virtual machine to the vmx one.
* Identify the size of the boot disk of the ova virtual machine (will be needed on the step when navigating to boot disk)
* On the powered off VM, Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Add''.
* Select Use “an existing virtual disk” then click ''Next''.
* Navigate to the boot disk of the ova Virtual machine then click ''next''.
* Click ''Finish''.
Now the vmx virtual machine should have the Fw version 12r2.

The .ova version will be available also in V12r1 sr7

=== IPVA does not run on Citrix Cloud Platform ===
Reportedly, the Citrix cloud platform - although based on VMware - cannot run the IPVA. Amongst other issues, the platform does not allow 4 virtual disks, which are required for the IPVA.

=== IPVA does not run on VCloud Air ===
VCloud Air apparently does not support the timekeeping mechanism required by the IPVA.

[[User:Ckl|ckl]] 15:50, 30 November 2016 (CET) We have seen the IPVA v12r2 running on vCloud Air. Use the ova import.

=== IPVA on ESX 6.5 ===
We have reports that the IPVA does not run properly on ESX 6.5. The IPVA boots up properly but the clock does not run. Running the .ova based variation available in v12r2 fixed the issue or edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

=== Administration: Avoid 'reboot' Command. Use 'reset' Command ===
Alwas use the 'reset' command to restart an IPVA.
The 'reboot' command makes sense only on physical applicances, where its purpose is to deploy a new bootcode by means of a forced watchdog trap. The resulting post-reboot state will be as if an unsolicited trap/crash had occurred.

=== Voice Quality Issues ===
When dealing with media streams (e.g. for announcements), the IPVA needs to fulfil real-time processing requirements, for example to process RTP packets in a timely fashion. To do so, the IPVA relies on the capabilities of the virtualization platform it runs on.

It is therefore important to configure the platform so that it supports real-time applications best. If you experience voice quality or latency issues, consider
* to make sure that all of the IPVAs memory is ''reserved'' to the IPVA (''Latency Sensitivity'' set to ''High'')
* to guarantee exclusive PCPU access
This helps to reduce CPU halt/wake-up states.

===Additional vCPUs may cause problems===
The Multi-Core functionality of version 13r2 is a beta functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==FAQ==
===Can The emulated compact-flash disk size be increased?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated compact-flash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given. Please note: The compact-flash disk is not the flash which store LDAP and VARS.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)
===What Is the minimum size of the emulated flash storage?===
The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===What Is The Size Of the Flash Directory on the IPVA?===
As noted above, the virtual flash memory on the IPVA is defaulted to a size of 64MB. Most of the flash is used by the ''flash directory'' (FLASHDIR0) which amongst other things provides storage for PBX objects.

The size of the flash directory depends on the available RAM. The maximum of 900 segments á 64KB, i.e. ~56MB, is available if 192MB or more RAM is available. If less RAM is available, the size of the flash directory is decreased accordingly. For this reason, it is unsafe to reduce RAM size in a given IPVA, as the flash directory size may be decreased so that objects from the flash directory get lost.

The easiest method to see how much flash directory space is available is to investigate the boot trace. For the standard configuration of 64MB the respective trace output is going to look as follows and informs about a size of 14MB:

0:0000:081:4 - start flashdir FLASHDIR0
0:0000:081:4 - fdir: segments=901->224(14.0MB)

{{Limit_Virtual_IPVA_Flash}}

===How much RAM is required per IPVA instance?===
Since 12r2sr27/13r1sr5 the downloadable virtual appliance comes preconfigured with 256 MiB RAM. This amount is seen as a good trade-off for the majority of all installations. The IPVA need the amount of used flash 3-times at startup. The RAM-size can be administrated by VMware-means.

===What is the maximum amount of RAM?===
The maximum meaningful RAM setting is 3GB. Memory space beyond that limit will be left unused. Assigning more than 3GB to an IPVA instance doesn't provide any benefit.

===Why does ''General/Info/DRAM'' show less than the configured memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===What about Open VM Tools / VMware Tools?===
Tools like this are not supported / integrated because it is not needed. The Virtual Appliance provides his own operating system, and we don't need any of the VM-Tools features in our guest.

===What Can I Do In Case Of A Checksum Boot Error?===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
checksum wrong! Loading failed for image=IPVA BIN
</pre>
[[Image:ipva-crc-wrong.jpg|center|thumb|200px|ipva-crc-wrong.jpg/|ipva-crc-wrong.jpg/]]

'''Solution'''
*Power-off the IPVA
*Replace the boot harddisk by a fresh one. The boot harddisk is the 1st hd(originally named ''hd-boot.vmdk'').

'''Remarks'''

This problem may occur on a system crash while a firmware update is taking place.

===What Can I Do In Case Of Boot-Problem: ''NIC unavailable!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
NIC unavailable!
</pre>
[[Image:ipva-nic-unavailable.jpg|center|thumb|200px|ipva-nic-unavailable.jpg/|ipva-nic-unavailable.jpg/]]

'''Solution'''
*Power-off the IPVA
*Administrate by VMware means: Ensure the correct/expected type of network interface controller(NIC) is going to be offered by the hypervisor.

The IPVA offers driver support for:
*AMD NIC: Am79C970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller
**a.k.a ''PCNet32''
**a.k.a ''Vlance''

The AMD-NIC is kind of default. However, the NIC type may be overriden manually and accordingly within the configuration file ipva.vmx as follows
<pre>
ethernet0.virtualDev = "vlance"
</pre>

'''Remarks'''

This problem may occur after a VMware re-configuration of the network settings.

===What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
perfcounter-not enabled!!!
</pre>
[[Image:screenshot-ipva-perfcounter-nok.jpg|center|thumb|200px|screenshot-ipva-perfcounter-nok.jpg/|screenshot-ipva-perfcounter-nok.jpg/]]

'''Solution''' 
This problem is likely caused by an OVA-import of the IPVA. The appliance's configuration file ''ipva.vmx'' requires a VMware proprietary configuration line that's not specifiable within an OVA-file.

The IPVA utilizes a VMware proprietary mechanism for its internal timekeeping<ref>Timekeeping in Virtual Machines http://www.vmware.com/pdf/vmware_timekeeping.pdf</ref>. That mechanism is only available after adding the following line to the configuration file ''ipva.vmx'':
<pre>
monitor_control.pseudo_perfctr = TRUE
</pre>
If that line is not present, the hypervisor is going to throw a CPU exception. Hint: In vSphere a VMX-file can be edited under '''Edit Settings/Options/Advanced/General/Configuration Parameters'''<ref>vmware Labs - How to edit vmx file in ESXi vSphere: https://www.youtube.com/watch?v=ICICoq-maB0</ref>

'''Remarks'''
*The vmx file should be edited after the installation of the IPVA.
*The vmx file should NOT be edited with Text editor (use vSphere as shown above)
*To our knowledge, a converter is always necessary for the installation with vmx.

===What Can I Do In Case Of Boot-Problem: ''Loading failed for image=IPVA BIN''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
Loading failed for image=IPVA BIN
</pre>
[[Image:Ipva-fw-load-failed.png|center|thumb|200px|ipva-fw-load-failed.png/|ipva-fw-load-failed.png/]]

'''Solution''' 
This problem is likely caused by a calculation fault within the boot-code.
*The solution requires a replacement of the boot disk hd-boot.vmdk.
**Download an IPVA package from on 11r2 sr22.
**Replace the 1st disk with the one from the downloaded package

===Are Additional vCPUs useful?===
The Multi-Core functionality is an experimental functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==Notes==
<references/>

==Related Articles==
* [[{{NAMESPACE}}:Licenses|Reference15r1:Licenses]]
* [[Howto15r1:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance]]
* [[Howto:A_rough_estimate_of_IPVA_Performance]]

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

Reference16r1:Concept Innovaphone Virtual Appliance (IPVA)

2026-08-24T11:14:39Z

Slu: /* Hardware */

==Applies To==
This information applies to:
*V16r1
*innovaphone Virtual Appliance
*Intel/AMD CPUs
* Virtualization platforms
**VMware
*** Workstation
*** Player
*** vSphere 4 - 8
*** ESXi 6 - 8
**Microsoft Hyper-V ([[{{NAMESPACE}}:Concept IPVA On Hyper-V|Concept IPVA On Hyper-V]])
*** Windows 8.1
*** Windows 10
*** Windows Server 2012 R2
*** Windows Server 2016 CTP4
**Linux based Hypervisors with [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM] and [https://en.wikipedia.org/wiki/QEMU QEMU] support
*** Proxmox VE 8.0 / 8.1 / 9.1

''Disclaimer: Manufacturers/versions of VM platforms other than those specified here have not been tested, so use at your own risk.''

''Disclaimer 2: We occasionally encounter customers experiencing unusual issues related to OpenStack. OpenStack is not officially supported, and such issues are not analyzed.''

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.

The IPVA is a software-only solution. It appears and behaves like an innovaphone "hard-box" without physical resources such as hardware DSP or ISDN interface.

==Package Overview==
We supply an OVF ('''O'''pen '''V'''irtualization '''F'''ormat) import or - depending on the virtualization platform - a suitable variant.
OVF is an open standard that contains several files in one package. The .ovf file is therefore an archive that contains all the necessary files.

=== Sample VMware ===
;ipva-ovf.zip:
The compressed archive ''ipva-ovf.zip'' contains the file ipva.ova. A deployment of ipva.ova will result in a set of 5 files - the file names may differ from the following list:
*ipva.vmx: The virtual machine configuration file
*hd-boot.vmdk: The virtual boot disk on IDE 0:0
*hd-cf.vmdk: The disk for emulation of a Compact Flash card on IDE 0:1
*hd-flash.vmdk: The disk for emulation of flash memory on IDE 1:0
*hd-dump.vmdk: The disk serving as a store for a crash dump on IDE 1:1

;ipva.bin:
The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

== Virtualization platforms ==

===VMware Player / VMware Workstation===
==== Import new Machine ====
*Copy the file ipva.ova to e.g. your desktop and Double-click on ipva.ova.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===VMware vSphere===
==== Import new Machine ====
*Import ipva.ova by means of '''File/Deploy OVF-Template...''' (de: '''Datei/OFV-Vorlage bereitstellen...''') and follow instructions.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===Microsoft Hyper-V===
==== Import new Machine ====
* Use the UI Wizard to Import a new machine
* Browse to the directory where the downloaded package was extracted to. Browse to the subdirectory Virtual Machines and click Ok
* Select ''Copy the Virtual Machine'' as ''Import Type''

===Proxmox VE===
==== Settings ====
===== Hardware =====
* Processors: 1 socket, 1 core, Type "Host" preferred, fallback "x86-64-v2-AES"
* Bios: SeaBIOS
* Machine: i440fx
* SCSI Controller: VirtIO SCSI single
* Hard Disks
** Cache: No Cache
** Discard: Enable
** SSD emulation: Yes
** Async IO: io_uring
* Network Devices
** Model: VirtIO (paravirtualized)
===== Options =====
* OS Type: Other
* Boot Order: ide0, ide1, ide2, ide3
* QEMU Gust Agent: Disabled

==== Import new Machine ====
Import the "ova" file to your storage which is enabled for the type "import". After that you can select the created template an create new machines from it with the button "Import"

* Before you start up the VM in the UI you have to adjust the following configuration options:
** Hardware -> Processors: Adjust "Extra Cpu Flags" -> "aes" if required
** Hardware -> SCSI Controller: Change Model to "VirtIO SCSI Single"
** Hardware -> Network Device (net0 / net1): Change Model to "VirtIO (paravirtualized)"

==Configuration==

===Network Configuration===
The IPVA is preconfigured a DHCP client. You will see the current IP-Address in the console-screen of the VM. If there's in no case a DHCP server available for the 1st-time configuration, you can set your IP-Configuration in the console.

config change IP0 ETH0 /addr 192.168.0.10 /mask 255.255.255.0
config change IP0 RT0 /gateway 192.168.0.1
config change DHCP0 /mode off
config write
reset

====MAC/serial number====
Take care that you use a MAC address which is supported by my.innovaphone, see [[Reference:My_Innovaphone#IPVA_MAC_exists]].

===AES Hardware Acceleration===
It may be beneficial to activate hardware acceleration for AES operations.
Whether hardware acceleration is activated can be checked with the command <code>!mod cmd CPU cpu-info</code>.

* The "flags" attribute must contain "aesni"
* The "act-features" attribute must contain "has_aesni"

Example:
<info>
<cpu
vendor="GenuineIntel"
signature="0x906e9"
brand="Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz"
...
flags="sse3 pclmulqdq ssse3 sse4_1 sse4_2 aesni xsave xsaveopt osxsave avx f16c rdrand fpu mmx fxsr sse sse2 avx2"
act-features="has_aesni has_avx has_vaesni has_vpclmulqdq" srtp-mips="5"/>
</info>

==Large IPVA with 512 MiB Flash==
In some scenarios the standard 64 MiB flash memory is not enough to store all user data. It is possible to manually enlarge the flash memory of an IPVA up to 512 MiB.

You have to change the settings of the virtual machine and format the flash. You cannot do it with an already configured machine, because you will lose all your configuration!

# shutdown the IPVA
# increase the RAM to 3.072 MiB
# increase the size of '''IDE1:0''' to 512 MiB or recreate it
# power up the IPVA
# format the flash: <code>!mod cmd FLASHMAN0 reset all</code>
# reboot the IPVA: <code>!reset</code>

You can check the free space with the command <code>!mod cmd FLASHMAN0 info</code>. You will see a big amount of available segments

segments=675, segment-size=0x10000 (64k)
LDAP - used 1k avail 63k owned 64k (segments 1) maximum 517056k (segments 8079, configured 8079)
VARS - used 23k avail 16k owned 192k (segments 3) maximum 640k (segments 10, configured 10)

But please keep in mind, the more data is saved, the longer it takes to reboot and load the UI in the [[{{NAMESPACE}}:PBX/Objects|PBX/Objects]] area.

==Troubleshooting==
Support procedures are commonly identical to the ones known from innovaphones' physical appliances. Except for:
*'''Post-Mortem Logs''' A post-mortem log must be retrieved by clicking on ''Maintenance/Diagnostics/Tracing/'''trace(crash-dump)''''' (alternatively: http://a.b.c.d/crash_dump.txt).

==Known Issues==

=== Maximal 3.072 MiB RAM ===
Because the IPVA has no [https://en.wikipedia.org/wiki/Virtual_memory virtual memory management], it will use only the first linear 3 GiB of RAM. But please keep in mind, that the flash content will be stored 3-times (Flashmanager, Flashdirectory, PBX) in RAM at startup.
=== Restored IPVA may not run ===
We have seen issues where an IPVA which had been backed up using one of the available backup tools for VMWare do not start up properly when they have been restored.

We strongly suggest to not rely on VMWare backup mechanism but instead to use the standard innovaphone backup scheme (that is, save the configuration on a regular basis).

==== How to run a restored backup that fails to start ====
Here is the procedure to run an IPVA from an IPVA if the restored virtual machine does not boot up properly:

* restore the backed up V10 IPVA
* create a new, empty V11r1 IPVA (you will need this merely to copy the boot disk from)
*replace the boot disk of the failing V10 IPVA by the boot disk of the fresh V11r1 IPVA (see [[#How To Replace The Boot Disk On vSphere.3F| How To Replace The Boot Disk On vSphere]] for details)
* start the restored and fixed V10 IPVA (it should run fine now)
* downgrade this V10 IPVA to desired V10 firmware
* remove the fresh V11r1 IPVA

Some Customer who are running Fw v12r1 (up to sr6) with ESXi 6.0 and VEEAM 9 reported that after a backup with VEEAM 9, the restored IPVA was not starting.
At this point, there is no possibility to solve this problem. The only workaround in that case is to delete the machine, reinstall a new one, and restore a configuration saved before.

If you did not run into the problem yet, for prevention, we recommend to replace the Boot disk of your working IPVA.vmx with one of the IPVA.ova. Please follow the steps below (be aware that this will upgrade the firmware on the IPVA to 12r2, due to the fact that actually, IPVA.ova is only available from version 12r2):

1. Remove the Boot disk of the virtual machine (vmx)(is normaly the first one). 
* Power off the VM
* Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Remove''.
* Click ''OK'' to save your changes.

2. Add the Boot disk of the ova virtual machine to the vmx one.
* Identify the size of the boot disk of the ova virtual machine (will be needed on the step when navigating to boot disk)
* On the powered off VM, Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Add''.
* Select Use “an existing virtual disk” then click ''Next''.
* Navigate to the boot disk of the ova Virtual machine then click ''next''.
* Click ''Finish''.
Now the vmx virtual machine should have the Fw version 12r2.

The .ova version will be available also in V12r1 sr7

=== IPVA does not run on Citrix Cloud Platform ===
Reportedly, the Citrix cloud platform - although based on VMware - cannot run the IPVA. Amongst other issues, the platform does not allow 4 virtual disks, which are required for the IPVA.

=== IPVA does not run on VCloud Air ===
VCloud Air apparently does not support the timekeeping mechanism required by the IPVA.

[[User:Ckl|ckl]] 15:50, 30 November 2016 (CET) We have seen the IPVA v12r2 running on vCloud Air. Use the ova import.

=== IPVA on ESX 6.5 ===
We have reports that the IPVA does not run properly on ESX 6.5. The IPVA boots up properly but the clock does not run. Running the .ova based variation available in v12r2 fixed the issue or edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

=== Administration: Avoid 'reboot' Command. Use 'reset' Command ===
Alwas use the 'reset' command to restart an IPVA.
The 'reboot' command makes sense only on physical applicances, where its purpose is to deploy a new bootcode by means of a forced watchdog trap. The resulting post-reboot state will be as if an unsolicited trap/crash had occurred.

=== Voice Quality Issues ===
When dealing with media streams (e.g. for announcements), the IPVA needs to fulfil real-time processing requirements, for example to process RTP packets in a timely fashion. To do so, the IPVA relies on the capabilities of the virtualization platform it runs on.

It is therefore important to configure the platform so that it supports real-time applications best. If you experience voice quality or latency issues, consider
* to make sure that all of the IPVAs memory is ''reserved'' to the IPVA (''Latency Sensitivity'' set to ''High'')
* to guarantee exclusive PCPU access
This helps to reduce CPU halt/wake-up states.

===Additional vCPUs may cause problems===
The Multi-Core functionality of version 13r2 is a beta functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==FAQ==
===Can The emulated compact-flash disk size be increased?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated compact-flash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given. Please note: The compact-flash disk is not the flash which store LDAP and VARS.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)
===What Is the minimum size of the emulated flash storage?===
The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===What Is The Size Of the Flash Directory on the IPVA?===
As noted above, the virtual flash memory on the IPVA is defaulted to a size of 64MB. Most of the flash is used by the ''flash directory'' (FLASHDIR0) which amongst other things provides storage for PBX objects.

The size of the flash directory depends on the available RAM. The maximum of 900 segments á 64KB, i.e. ~56MB, is available if 192MB or more RAM is available. If less RAM is available, the size of the flash directory is decreased accordingly. For this reason, it is unsafe to reduce RAM size in a given IPVA, as the flash directory size may be decreased so that objects from the flash directory get lost.

The easiest method to see how much flash directory space is available is to investigate the boot trace. For the standard configuration of 64MB the respective trace output is going to look as follows and informs about a size of 14MB:

0:0000:081:4 - start flashdir FLASHDIR0
0:0000:081:4 - fdir: segments=901->224(14.0MB)

{{Limit_Virtual_IPVA_Flash}}

===How much RAM is required per IPVA instance?===
Since 12r2sr27/13r1sr5 the downloadable virtual appliance comes preconfigured with 256 MiB RAM. This amount is seen as a good trade-off for the majority of all installations. The IPVA need the amount of used flash 3-times at startup. The RAM-size can be administrated by VMware-means.

===What is the maximum amount of RAM?===
The maximum meaningful RAM setting is 3GB. Memory space beyond that limit will be left unused. Assigning more than 3GB to an IPVA instance doesn't provide any benefit.

===Why does ''General/Info/DRAM'' show less than the configured memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===What about Open VM Tools / VMware Tools?===
Tools like this are not supported / integrated because it is not needed. The Virtual Appliance provides his own operating system, and we don't need any of the VM-Tools features in our guest.

===What Can I Do In Case Of A Checksum Boot Error?===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
checksum wrong! Loading failed for image=IPVA BIN
</pre>
[[Image:ipva-crc-wrong.jpg|center|thumb|200px|ipva-crc-wrong.jpg/|ipva-crc-wrong.jpg/]]

'''Solution'''
*Power-off the IPVA
*Replace the boot harddisk by a fresh one. The boot harddisk is the 1st hd(originally named ''hd-boot.vmdk'').

'''Remarks'''

This problem may occur on a system crash while a firmware update is taking place.

===What Can I Do In Case Of Boot-Problem: ''NIC unavailable!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
NIC unavailable!
</pre>
[[Image:ipva-nic-unavailable.jpg|center|thumb|200px|ipva-nic-unavailable.jpg/|ipva-nic-unavailable.jpg/]]

'''Solution'''
*Power-off the IPVA
*Administrate by VMware means: Ensure the correct/expected type of network interface controller(NIC) is going to be offered by the hypervisor.

The IPVA offers driver support for:
*AMD NIC: Am79C970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller
**a.k.a ''PCNet32''
**a.k.a ''Vlance''

The AMD-NIC is kind of default. However, the NIC type may be overriden manually and accordingly within the configuration file ipva.vmx as follows
<pre>
ethernet0.virtualDev = "vlance"
</pre>

'''Remarks'''

This problem may occur after a VMware re-configuration of the network settings.

===What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
perfcounter-not enabled!!!
</pre>
[[Image:screenshot-ipva-perfcounter-nok.jpg|center|thumb|200px|screenshot-ipva-perfcounter-nok.jpg/|screenshot-ipva-perfcounter-nok.jpg/]]

'''Solution''' 
This problem is likely caused by an OVA-import of the IPVA. The appliance's configuration file ''ipva.vmx'' requires a VMware proprietary configuration line that's not specifiable within an OVA-file.

The IPVA utilizes a VMware proprietary mechanism for its internal timekeeping<ref>Timekeeping in Virtual Machines http://www.vmware.com/pdf/vmware_timekeeping.pdf</ref>. That mechanism is only available after adding the following line to the configuration file ''ipva.vmx'':
<pre>
monitor_control.pseudo_perfctr = TRUE
</pre>
If that line is not present, the hypervisor is going to throw a CPU exception. Hint: In vSphere a VMX-file can be edited under '''Edit Settings/Options/Advanced/General/Configuration Parameters'''<ref>vmware Labs - How to edit vmx file in ESXi vSphere: https://www.youtube.com/watch?v=ICICoq-maB0</ref>

'''Remarks'''
*The vmx file should be edited after the installation of the IPVA.
*The vmx file should NOT be edited with Text editor (use vSphere as shown above)
*To our knowledge, a converter is always necessary for the installation with vmx.

===What Can I Do In Case Of Boot-Problem: ''Loading failed for image=IPVA BIN''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
Loading failed for image=IPVA BIN
</pre>
[[Image:Ipva-fw-load-failed.png|center|thumb|200px|ipva-fw-load-failed.png/|ipva-fw-load-failed.png/]]

'''Solution''' 
This problem is likely caused by a calculation fault within the boot-code.
*The solution requires a replacement of the boot disk hd-boot.vmdk.
**Download an IPVA package from on 11r2 sr22.
**Replace the 1st disk with the one from the downloaded package

===Are Additional vCPUs useful?===
The Multi-Core functionality is an experimental functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==Notes==
<references/>

==Related Articles==
* [[{{NAMESPACE}}:Licenses|Reference15r1:Licenses]]
* [[Howto15r1:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance]]
* [[Howto:A_rough_estimate_of_IPVA_Performance]]

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

Reference16r1:Concept Innovaphone Virtual Appliance (IPVA)

2026-08-24T11:13:05Z

Slu: /* Settings */

==Applies To==
This information applies to:
*V16r1
*innovaphone Virtual Appliance
*Intel/AMD CPUs
* Virtualization platforms
**VMware
*** Workstation
*** Player
*** vSphere 4 - 8
*** ESXi 6 - 8
**Microsoft Hyper-V ([[{{NAMESPACE}}:Concept IPVA On Hyper-V|Concept IPVA On Hyper-V]])
*** Windows 8.1
*** Windows 10
*** Windows Server 2012 R2
*** Windows Server 2016 CTP4
**Linux based Hypervisors with [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM] and [https://en.wikipedia.org/wiki/QEMU QEMU] support
*** Proxmox VE 8.0 / 8.1 / 9.1

''Disclaimer: Manufacturers/versions of VM platforms other than those specified here have not been tested, so use at your own risk.''

''Disclaimer 2: We occasionally encounter customers experiencing unusual issues related to OpenStack. OpenStack is not officially supported, and such issues are not analyzed.''

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.

The IPVA is a software-only solution. It appears and behaves like an innovaphone "hard-box" without physical resources such as hardware DSP or ISDN interface.

==Package Overview==
We supply an OVF ('''O'''pen '''V'''irtualization '''F'''ormat) import or - depending on the virtualization platform - a suitable variant.
OVF is an open standard that contains several files in one package. The .ovf file is therefore an archive that contains all the necessary files.

=== Sample VMware ===
;ipva-ovf.zip:
The compressed archive ''ipva-ovf.zip'' contains the file ipva.ova. A deployment of ipva.ova will result in a set of 5 files - the file names may differ from the following list:
*ipva.vmx: The virtual machine configuration file
*hd-boot.vmdk: The virtual boot disk on IDE 0:0
*hd-cf.vmdk: The disk for emulation of a Compact Flash card on IDE 0:1
*hd-flash.vmdk: The disk for emulation of flash memory on IDE 1:0
*hd-dump.vmdk: The disk serving as a store for a crash dump on IDE 1:1

;ipva.bin:
The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

== Virtualization platforms ==

===VMware Player / VMware Workstation===
==== Import new Machine ====
*Copy the file ipva.ova to e.g. your desktop and Double-click on ipva.ova.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===VMware vSphere===
==== Import new Machine ====
*Import ipva.ova by means of '''File/Deploy OVF-Template...''' (de: '''Datei/OFV-Vorlage bereitstellen...''') and follow instructions.
*Edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

===Microsoft Hyper-V===
==== Import new Machine ====
* Use the UI Wizard to Import a new machine
* Browse to the directory where the downloaded package was extracted to. Browse to the subdirectory Virtual Machines and click Ok
* Select ''Copy the Virtual Machine'' as ''Import Type''

===Proxmox VE===
==== Settings ====
===== Hardware =====
* Processors: 1 socket, 1 core, Type "Host" preferred, fallback "x86-64-v2-AES"
* Bios: SeaBIOS
* Machine: i440fx
* SCSI Controller: VirtIO SCSI single
* Hard Disks
** Cache: No Cache
** Discard: Enable
** SSD emulation: Yes
** Async IO: io_uring
* Network Devices
** Model: VirtIO (paravirtualized)

==== Import new Machine ====
Import the "ova" file to your storage which is enabled for the type "import". After that you can select the created template an create new machines from it with the button "Import"

* Before you start up the VM in the UI you have to adjust the following configuration options:
** Hardware -> Processors: Adjust "Extra Cpu Flags" -> "aes" if required
** Hardware -> SCSI Controller: Change Model to "VirtIO SCSI Single"
** Hardware -> Network Device (net0 / net1): Change Model to "VirtIO (paravirtualized)"

==Configuration==

===Network Configuration===
The IPVA is preconfigured a DHCP client. You will see the current IP-Address in the console-screen of the VM. If there's in no case a DHCP server available for the 1st-time configuration, you can set your IP-Configuration in the console.

config change IP0 ETH0 /addr 192.168.0.10 /mask 255.255.255.0
config change IP0 RT0 /gateway 192.168.0.1
config change DHCP0 /mode off
config write
reset

====MAC/serial number====
Take care that you use a MAC address which is supported by my.innovaphone, see [[Reference:My_Innovaphone#IPVA_MAC_exists]].

===AES Hardware Acceleration===
It may be beneficial to activate hardware acceleration for AES operations.
Whether hardware acceleration is activated can be checked with the command <code>!mod cmd CPU cpu-info</code>.

* The "flags" attribute must contain "aesni"
* The "act-features" attribute must contain "has_aesni"

Example:
<info>
<cpu
vendor="GenuineIntel"
signature="0x906e9"
brand="Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz"
...
flags="sse3 pclmulqdq ssse3 sse4_1 sse4_2 aesni xsave xsaveopt osxsave avx f16c rdrand fpu mmx fxsr sse sse2 avx2"
act-features="has_aesni has_avx has_vaesni has_vpclmulqdq" srtp-mips="5"/>
</info>

==Large IPVA with 512 MiB Flash==
In some scenarios the standard 64 MiB flash memory is not enough to store all user data. It is possible to manually enlarge the flash memory of an IPVA up to 512 MiB.

You have to change the settings of the virtual machine and format the flash. You cannot do it with an already configured machine, because you will lose all your configuration!

# shutdown the IPVA
# increase the RAM to 3.072 MiB
# increase the size of '''IDE1:0''' to 512 MiB or recreate it
# power up the IPVA
# format the flash: <code>!mod cmd FLASHMAN0 reset all</code>
# reboot the IPVA: <code>!reset</code>

You can check the free space with the command <code>!mod cmd FLASHMAN0 info</code>. You will see a big amount of available segments

segments=675, segment-size=0x10000 (64k)
LDAP - used 1k avail 63k owned 64k (segments 1) maximum 517056k (segments 8079, configured 8079)
VARS - used 23k avail 16k owned 192k (segments 3) maximum 640k (segments 10, configured 10)

But please keep in mind, the more data is saved, the longer it takes to reboot and load the UI in the [[{{NAMESPACE}}:PBX/Objects|PBX/Objects]] area.

==Troubleshooting==
Support procedures are commonly identical to the ones known from innovaphones' physical appliances. Except for:
*'''Post-Mortem Logs''' A post-mortem log must be retrieved by clicking on ''Maintenance/Diagnostics/Tracing/'''trace(crash-dump)''''' (alternatively: http://a.b.c.d/crash_dump.txt).

==Known Issues==

=== Maximal 3.072 MiB RAM ===
Because the IPVA has no [https://en.wikipedia.org/wiki/Virtual_memory virtual memory management], it will use only the first linear 3 GiB of RAM. But please keep in mind, that the flash content will be stored 3-times (Flashmanager, Flashdirectory, PBX) in RAM at startup.
=== Restored IPVA may not run ===
We have seen issues where an IPVA which had been backed up using one of the available backup tools for VMWare do not start up properly when they have been restored.

We strongly suggest to not rely on VMWare backup mechanism but instead to use the standard innovaphone backup scheme (that is, save the configuration on a regular basis).

==== How to run a restored backup that fails to start ====
Here is the procedure to run an IPVA from an IPVA if the restored virtual machine does not boot up properly:

* restore the backed up V10 IPVA
* create a new, empty V11r1 IPVA (you will need this merely to copy the boot disk from)
*replace the boot disk of the failing V10 IPVA by the boot disk of the fresh V11r1 IPVA (see [[#How To Replace The Boot Disk On vSphere.3F| How To Replace The Boot Disk On vSphere]] for details)
* start the restored and fixed V10 IPVA (it should run fine now)
* downgrade this V10 IPVA to desired V10 firmware
* remove the fresh V11r1 IPVA

Some Customer who are running Fw v12r1 (up to sr6) with ESXi 6.0 and VEEAM 9 reported that after a backup with VEEAM 9, the restored IPVA was not starting.
At this point, there is no possibility to solve this problem. The only workaround in that case is to delete the machine, reinstall a new one, and restore a configuration saved before.

If you did not run into the problem yet, for prevention, we recommend to replace the Boot disk of your working IPVA.vmx with one of the IPVA.ova. Please follow the steps below (be aware that this will upgrade the firmware on the IPVA to 12r2, due to the fact that actually, IPVA.ova is only available from version 12r2):

1. Remove the Boot disk of the virtual machine (vmx)(is normaly the first one). 
* Power off the VM
* Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Remove''.
* Click ''OK'' to save your changes.

2. Add the Boot disk of the ova virtual machine to the vmx one.
* Identify the size of the boot disk of the ova virtual machine (will be needed on the step when navigating to boot disk)
* On the powered off VM, Select the Virtual Machine > Settings.
* On the Hardware tab, select the virtual hard disk and click ''Add''.
* Select Use “an existing virtual disk” then click ''Next''.
* Navigate to the boot disk of the ova Virtual machine then click ''next''.
* Click ''Finish''.
Now the vmx virtual machine should have the Fw version 12r2.

The .ova version will be available also in V12r1 sr7

=== IPVA does not run on Citrix Cloud Platform ===
Reportedly, the Citrix cloud platform - although based on VMware - cannot run the IPVA. Amongst other issues, the platform does not allow 4 virtual disks, which are required for the IPVA.

=== IPVA does not run on VCloud Air ===
VCloud Air apparently does not support the timekeeping mechanism required by the IPVA.

[[User:Ckl|ckl]] 15:50, 30 November 2016 (CET) We have seen the IPVA v12r2 running on vCloud Air. Use the ova import.

=== IPVA on ESX 6.5 ===
We have reports that the IPVA does not run properly on ESX 6.5. The IPVA boots up properly but the clock does not run. Running the .ova based variation available in v12r2 fixed the issue or edit the file ipva.vmx according to [[#What Can I Do In Case Of Boot-Problem: perf-counter not enabled.21| What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!'']]

=== Administration: Avoid 'reboot' Command. Use 'reset' Command ===
Alwas use the 'reset' command to restart an IPVA.
The 'reboot' command makes sense only on physical applicances, where its purpose is to deploy a new bootcode by means of a forced watchdog trap. The resulting post-reboot state will be as if an unsolicited trap/crash had occurred.

=== Voice Quality Issues ===
When dealing with media streams (e.g. for announcements), the IPVA needs to fulfil real-time processing requirements, for example to process RTP packets in a timely fashion. To do so, the IPVA relies on the capabilities of the virtualization platform it runs on.

It is therefore important to configure the platform so that it supports real-time applications best. If you experience voice quality or latency issues, consider
* to make sure that all of the IPVAs memory is ''reserved'' to the IPVA (''Latency Sensitivity'' set to ''High'')
* to guarantee exclusive PCPU access
This helps to reduce CPU halt/wake-up states.

===Additional vCPUs may cause problems===
The Multi-Core functionality of version 13r2 is a beta functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==FAQ==
===Can The emulated compact-flash disk size be increased?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated compact-flash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given. Please note: The compact-flash disk is not the flash which store LDAP and VARS.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)
===What Is the minimum size of the emulated flash storage?===
The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===What Is The Size Of the Flash Directory on the IPVA?===
As noted above, the virtual flash memory on the IPVA is defaulted to a size of 64MB. Most of the flash is used by the ''flash directory'' (FLASHDIR0) which amongst other things provides storage for PBX objects.

The size of the flash directory depends on the available RAM. The maximum of 900 segments á 64KB, i.e. ~56MB, is available if 192MB or more RAM is available. If less RAM is available, the size of the flash directory is decreased accordingly. For this reason, it is unsafe to reduce RAM size in a given IPVA, as the flash directory size may be decreased so that objects from the flash directory get lost.

The easiest method to see how much flash directory space is available is to investigate the boot trace. For the standard configuration of 64MB the respective trace output is going to look as follows and informs about a size of 14MB:

0:0000:081:4 - start flashdir FLASHDIR0
0:0000:081:4 - fdir: segments=901->224(14.0MB)

{{Limit_Virtual_IPVA_Flash}}

===How much RAM is required per IPVA instance?===
Since 12r2sr27/13r1sr5 the downloadable virtual appliance comes preconfigured with 256 MiB RAM. This amount is seen as a good trade-off for the majority of all installations. The IPVA need the amount of used flash 3-times at startup. The RAM-size can be administrated by VMware-means.

===What is the maximum amount of RAM?===
The maximum meaningful RAM setting is 3GB. Memory space beyond that limit will be left unused. Assigning more than 3GB to an IPVA instance doesn't provide any benefit.

===Why does ''General/Info/DRAM'' show less than the configured memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===What about Open VM Tools / VMware Tools?===
Tools like this are not supported / integrated because it is not needed. The Virtual Appliance provides his own operating system, and we don't need any of the VM-Tools features in our guest.

===What Can I Do In Case Of A Checksum Boot Error?===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
checksum wrong! Loading failed for image=IPVA BIN
</pre>
[[Image:ipva-crc-wrong.jpg|center|thumb|200px|ipva-crc-wrong.jpg/|ipva-crc-wrong.jpg/]]

'''Solution'''
*Power-off the IPVA
*Replace the boot harddisk by a fresh one. The boot harddisk is the 1st hd(originally named ''hd-boot.vmdk'').

'''Remarks'''

This problem may occur on a system crash while a firmware update is taking place.

===What Can I Do In Case Of Boot-Problem: ''NIC unavailable!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
NIC unavailable!
</pre>
[[Image:ipva-nic-unavailable.jpg|center|thumb|200px|ipva-nic-unavailable.jpg/|ipva-nic-unavailable.jpg/]]

'''Solution'''
*Power-off the IPVA
*Administrate by VMware means: Ensure the correct/expected type of network interface controller(NIC) is going to be offered by the hypervisor.

The IPVA offers driver support for:
*AMD NIC: Am79C970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller
**a.k.a ''PCNet32''
**a.k.a ''Vlance''

The AMD-NIC is kind of default. However, the NIC type may be overriden manually and accordingly within the configuration file ipva.vmx as follows
<pre>
ethernet0.virtualDev = "vlance"
</pre>

'''Remarks'''

This problem may occur after a VMware re-configuration of the network settings.

===What Can I Do In Case Of Boot-Problem: ''perf-counter not enabled!''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
perfcounter-not enabled!!!
</pre>
[[Image:screenshot-ipva-perfcounter-nok.jpg|center|thumb|200px|screenshot-ipva-perfcounter-nok.jpg/|screenshot-ipva-perfcounter-nok.jpg/]]

'''Solution''' 
This problem is likely caused by an OVA-import of the IPVA. The appliance's configuration file ''ipva.vmx'' requires a VMware proprietary configuration line that's not specifiable within an OVA-file.

The IPVA utilizes a VMware proprietary mechanism for its internal timekeeping<ref>Timekeeping in Virtual Machines http://www.vmware.com/pdf/vmware_timekeeping.pdf</ref>. That mechanism is only available after adding the following line to the configuration file ''ipva.vmx'':
<pre>
monitor_control.pseudo_perfctr = TRUE
</pre>
If that line is not present, the hypervisor is going to throw a CPU exception. Hint: In vSphere a VMX-file can be edited under '''Edit Settings/Options/Advanced/General/Configuration Parameters'''<ref>vmware Labs - How to edit vmx file in ESXi vSphere: https://www.youtube.com/watch?v=ICICoq-maB0</ref>

'''Remarks'''
*The vmx file should be edited after the installation of the IPVA.
*The vmx file should NOT be edited with Text editor (use vSphere as shown above)
*To our knowledge, a converter is always necessary for the installation with vmx.

===What Can I Do In Case Of Boot-Problem: ''Loading failed for image=IPVA BIN''===
This paragraph applies, if you experience the following start-up problem.

'''Symptom'''
*the IPVA doesn't start properly
*the console displays
<pre>
Loading failed for image=IPVA BIN
</pre>
[[Image:Ipva-fw-load-failed.png|center|thumb|200px|ipva-fw-load-failed.png/|ipva-fw-load-failed.png/]]

'''Solution''' 
This problem is likely caused by a calculation fault within the boot-code.
*The solution requires a replacement of the boot disk hd-boot.vmdk.
**Download an IPVA package from on 11r2 sr22.
**Replace the 1st disk with the one from the downloaded package

===Are Additional vCPUs useful?===
The Multi-Core functionality is an experimental functionality. Additional virtual CPUs(vCPUs) should not be utilized in production environments.

==Notes==
<references/>

==Related Articles==
* [[{{NAMESPACE}}:Licenses|Reference15r1:Licenses]]
* [[Howto15r1:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance]]
* [[Howto:A_rough_estimate_of_IPVA_Performance]]

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

Reference16r1:Services/NTP

2026-08-14T12:03:37Z

Slu: /* Configuration */

The device can synchronize its internal date/time to an NTP server using the SNTP protocol. Without synchronization to an NTP server the internal date/time is reset to Januar 1st, 1970 0:00 after each restart.

== Configuration ==

{|
|valign=top nowrap=true|'''Server'''
| The IP-Address or DNS-Name of the time server
|-
|valign=top nowrap=true|'''Interval [min]:'''
|The time interval (in minutes) at which the device tries to synchronise with the time server
|-
|valign=top nowrap=true|'''Timezone'''
|Select the time zone in which the device is located.
|-
|valign=top nowrap=true|'''String'''
|If the timezone to be used is not one of the predefined timezones, it can be confugured with a string in accordance with the IEEE POSIX standard
|-
|valign=top nowrap=true|'''Current Server'''
|Displays the current used NTP Server.
|-
|valign=top nowrap=true|'''Last sync'''
|Displays the data and time of the last synchronisation.
|-
|valign=top nowrap=true|'''Default Time'''
|Default time in UTC on startup that shall be used if no NTP Server is available. The Format is ''dd.mm.yyyy-hh:mm''
|}

== Timezone Configuration String ==

Time services always provide the coordinated world time UTC (Universal Time Coordinated), which corresponds to GMT (Greenwich Mean Time), not however the correct time zone and summer time. It is therefore possible to specify the time difference between the time zone and the world time in the String field. The difference from the time zone GMT+1 (Central European time zone) is 60 minutes. A further 60 minutes has to be added with summer time, adding up to a total difference of 120 minutes. In this case, however, you must adjust the time difference manually when switching from winter to summer time and vice versa.

If a so-called timezone string was entered in the String field, the device can make the switch from summer to winter time automatically. The name of the time zone, the name of the summer time zone, their respective differences in time compared to the UTC and the time switch points are encoded in this field.

There are various formats for the specification of this string. These formats are defined by the IEEE POSIX standard.
POSIX timezone strings have the following format (optional parts in square brackets):

'''StdOffset[Dst[Offset], Date/Time, Date/Time]'''

'''Std''' stands for the time zone (for example, CET for Central European Time or MET for Middle European Time).

'''Offset''' specifies the time difference between the time zone and UTC, for example, -1 for Central European Time. The difference is negative if the time zone is ahead of UTC. If the time difference does not comprise full hours, the number of minutes can be added, for example, -1:30.
The TZ string ends here if you are not using a summer time.

'''Dst''' stands for the summer time zone (for example, CEST for Central European Summer Time or MES for Middle European Summer Time).

The optional, '''second Offset''' parameter gives the offset of the summer time in respect of UTC. An hour before normal time is assumed if no entry is made.

'''Date/Time''' define the start and end of summer time. The format for a time entry is Mm.n.d, signifying the d-th day of the n-th week of the m-th month. Day 0 is Sunday. If the fifth week is entered, the last day (with respect to d) of the month is meant. The format for a time entry is hh[:mm[:ss]], in the 24-hour format.

=== Example ===

The Central European time zone is specified '''CET-1CEST-2,M3.5.0/2,M10.5.0/3''':

CET (Central European Time) - offset -1

CEST (Central European Summer Time) - offset -2

Switch to Summer Time at 3(March), 5(last week of the month), 0(Sunday)/at 2:00

Switch to Standard Time at 10(October), 5(last week of the month), 0(Sunday)/at 3:00

= Related Articles =
* [[Howto:Setting time and date without using an NTP]]

Reference16r1:Services/NTP

2026-08-14T12:03:05Z

Slu: Created page with "The device can synchronize its internal date/time to an NTP server using the SNTP protocol. Without synchronization to an NTP server the internal date/time is reset to Januar 1st, 1970 0:00 after each restart. == Configuration == {| |valign=top nowrap=true|'''Server''' |The IP-Adresse of the time server |- |valign=top nowrap=true|'''Interval [min]:''' |The time interval (in minutes) at which the device tries to synchronise with the time server |- |valign=top nowrap=tru..."

The device can synchronize its internal date/time to an NTP server using the SNTP protocol. Without synchronization to an NTP server the internal date/time is reset to Januar 1st, 1970 0:00 after each restart.

== Configuration ==

{|
|valign=top nowrap=true|'''Server'''
|The IP-Adresse of the time server
|-
|valign=top nowrap=true|'''Interval [min]:'''
|The time interval (in minutes) at which the device tries to synchronise with the time server
|-
|valign=top nowrap=true|'''Timezone'''
|Select the time zone in which the device is located.
|-
|valign=top nowrap=true|'''String'''
|If the timezone to be used is not one of the predefined timezones, it can be confugured with a string in accordance with the IEEE POSIX standard
|-
|valign=top nowrap=true|'''Current Server'''
|Displays the current used NTP Server.
|-
|valign=top nowrap=true|'''Last sync'''
|Displays the data and time of the last synchronisation.
|-
|valign=top nowrap=true|'''Default Time'''
|Default time in UTC on startup that shall be used if no NTP Server is available. The Format is ''dd.mm.yyyy-hh:mm''
|}

== Timezone Configuration String ==

Time services always provide the coordinated world time UTC (Universal Time Coordinated), which corresponds to GMT (Greenwich Mean Time), not however the correct time zone and summer time. It is therefore possible to specify the time difference between the time zone and the world time in the String field. The difference from the time zone GMT+1 (Central European time zone) is 60 minutes. A further 60 minutes has to be added with summer time, adding up to a total difference of 120 minutes. In this case, however, you must adjust the time difference manually when switching from winter to summer time and vice versa.

If a so-called timezone string was entered in the String field, the device can make the switch from summer to winter time automatically. The name of the time zone, the name of the summer time zone, their respective differences in time compared to the UTC and the time switch points are encoded in this field.

There are various formats for the specification of this string. These formats are defined by the IEEE POSIX standard.
POSIX timezone strings have the following format (optional parts in square brackets):

'''StdOffset[Dst[Offset], Date/Time, Date/Time]'''

'''Std''' stands for the time zone (for example, CET for Central European Time or MET for Middle European Time).

'''Offset''' specifies the time difference between the time zone and UTC, for example, -1 for Central European Time. The difference is negative if the time zone is ahead of UTC. If the time difference does not comprise full hours, the number of minutes can be added, for example, -1:30.
The TZ string ends here if you are not using a summer time.

'''Dst''' stands for the summer time zone (for example, CEST for Central European Summer Time or MES for Middle European Summer Time).

The optional, '''second Offset''' parameter gives the offset of the summer time in respect of UTC. An hour before normal time is assumed if no entry is made.

'''Date/Time''' define the start and end of summer time. The format for a time entry is Mm.n.d, signifying the d-th day of the n-th week of the m-th month. Day 0 is Sunday. If the fifth week is entered, the last day (with respect to d) of the month is meant. The format for a time entry is hh[:mm[:ss]], in the 24-hour format.

=== Example ===

The Central European time zone is specified '''CET-1CEST-2,M3.5.0/2,M10.5.0/3''':

CET (Central European Time) - offset -1

CEST (Central European Summer Time) - offset -2

Switch to Summer Time at 3(March), 5(last week of the month), 0(Sunday)/at 2:00

Switch to Standard Time at 10(October), 5(last week of the month), 0(Sunday)/at 3:00

= Related Articles =
* [[Howto:Setting time and date without using an NTP]]

Howto17:Firmware Upgrade V16r1 V17

2026-08-14T08:33:12Z

Slu: /* Upgrade AP Image */

== Applies To ==
This information applies to:

* All 17 capable innovaphone devices
: For a general overview of the upgrade process and a list of supported devices with 17, see [[Howto:Firmware Upgrade]]
== Licenses ==
In case of cloud or rental model, don't worry about licenses.

If the system is licensed on premise, you'll need to regenerate the license file for v17 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 16r1 service release. Create backups before you start and store them on an external location

=== Upgrade AP Image ===
* First, upgrade your application platform to at least image version <code>140049</code>. After that you can go ahead.

=== Upgrade Sequence ===
In systems of multiple units, it is important to update the tree from top to bottom. In other words, update the master unit first, and then the machines at the lower levels. If you're using a DevicesApp update job that updates the entire system at once, you don't need to do anything here.

=== TechAssist Upgrade Helper ===
* Before you start, make sure that all TechAssist tests (you will receive the required tests in the last update in the previous major version) labelled <code>Pre Upgrade: xy</code> are positive, if available
* When you are finished, make sure that all TechAssist tests (you will receive new tests with the upgrade) are positive

== Changes visible to the end customers ==
Listed here are changes that should be communicated by resellers to end users prior to a upgrade, as the change will be visible/audible in the behaviour of the application/device.

* <code>tbd</code>

== Manual steps needed after upgrade ==
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.

=== Connector for kuando - MacOS ===
With V17, the Kuando HTTP server is no longer required. From version 2.0.7 onwards, the HTTP server is already integrated into KuandoHub and works in exactly the same way as the Windows version.
The HTTP server must be uninstalled and KuandoHub installed; once the default setting has been defined in the Platform Priorities, no further configuration is required.

== New Apps ==
New Apps will not be installed automatically by the upgrade. The installation description of new apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.

<code>tbd</code>
;
:

== Removed ==
The following software is no longer included.

* <code>tbd</code>

== Deprecated ==
The following software is based on legacy technology, with no further development and limited maintenance and support.

* <code>tbd</code>

== Previously deprecated and now no longer supported ==
The following software is based on legacy technology, with no further development and no more maintenance and support.

* <code>tbd</code>

==Known Problems==
===Long Update-duration===
When you update, it can be up to 10 minutes before you have access to your app platform again.

== Related Articles ==
* [[Howto:Firmware_Upgrade]]
* [[Howto16r1:Firmware_Upgrade_V15r1_V16r1]]
[[Category:Howto|{{PAGENAME}}]]

Reference16r1:Concept App Service IP

2026-07-23T13:13:52Z

Slu: /* Create instance */

[[Category:Concept|Apps]]
[[Category:Concept|IP]]

The App IP is an app which offers the PBX functionality and further functionalities as App service on our innovaphone App Platform.

== Applies To ==

* innovaphone firmware and apps V16

==Requirements==
* innovaphone Application Platform (image version 140011 or higher)

==Concept==

The App IP offers modules known from innovaphone gateways, like the PBX, TURN server functionality etc.

==How it works==

=== Single instance mode ===
Unlike other App Services, the App IP is a single instance App Service, so you can create '''just''' a single instance and not multiple instances.

== Licensing ==
Standard licensing mechanisms apply to the App IP as they apply to innovaphone gateways.

In addition, every port license requires a dedicated IPAP license (similar to the IPVA license for virtual machines).

== Apps ==

There is no App provided by this App Service.

== PBX Manager Plugins ==

There is no PBX Manager Plugin provided by this App Service.

== Configuration ==

The configuration is done as an innovaphone gateway is configured too.

=== Create instance ===
You have to create one instance for the App IP Service.

[[Courseware:IT Advanced - 04 Setting up the Application Platform#Adding an App Service instance|Here]] are more informations how to do this.

We recommend the following settings: 
'''Name''' = ip 
'''Domain''' = customer domain (system name of the PBX) 
'''Password''' = The password '''must be set to "pwd"''' for Install and will be changed during the process. '''Note:''' if you want to login with the Adv.GUI to the PBX prior to the Install proces, this is also the admin password! 
'''Webserver Path''' - Used for access to the UI. Adjustable, will be filled automatically with the value "$domain/ip", eg. <code>domain.com/ip</code>

=== Install Process ===
Install can be started under the webserver path of the App IP instance and /''install.htm'', e.g.: http://app.domain.com/domain.com/ip/install.htm

⚠️ Use standard ports for installation. If necessary, install via a reverse proxy

⚠️ Do not use the localhost (127.0.0.1) address

=== Advanced UI ===
The advanced UI is reachable under the webserver path of the App IP instance and /admin.xml?xsl=admin.xsl, e.g.:
https://app.domain.com/domain.com/ip/admin.xml?xsl=admin.xsl

==== Password ====
The password for the Advanced UI is the password of the App IP instance. 
If the Devices App rolls out passwords, the domain password is also used for the App IP admin login.

=== IP configuration ===
As the App IP is just an App on an App Platform, there are no IP4/IP6, NTP etc. settings as on other innovaphone devices.

==== Devices App ====
If your App Platform which runs the App IP is connected to a Devices App, you can access the Advanced UI with the '''PBX''' tab of your App Platform device.

== Functional Distinction from a Gateway or an IPVA ==
Due to the system architecture, not all existing software functions of a gateway or an IPVA can be made available in an "IP App".

The following features are not available:
* PBX users with "additional user rights" and an associated login to the advanced UI
* SOAP (currently)

==Troubleshooting==
The App IP offers standard tracing mechanism for App Services and in addition mechanisms known from innovaphone gateways. 
You can enable module related trace flags with config change commands or by setting trace flags under Maintenance -> Tracing in the Advanced UI of the App IP.

Trace files are not found under Maintenance -> Tracing but on the App IP service on your App Platform Manager.

==Known issues==
The installation process must be performed using a DNS name rather than an IP address. 
The URL must include the parameter ''?apdns="DNS from App Platform"'' in the path, for example: http://app.domain.com/domain.com/ip/install.htm?apdns=pbx.domain.com 
Starting with version 16r1 sr1, installation using an IP address is supported. 

However, it is generally recommended to use DNS for the installation.

==Related Articles==
* [[Reference16r1:Concept_innovaphone_App_Platform_Container]]

Reference16r1:Concept App Service IP

2026-07-23T13:12:55Z

Slu: /* Create instance */

[[Category:Concept|Apps]]
[[Category:Concept|IP]]

The App IP is an app which offers the PBX functionality and further functionalities as App service on our innovaphone App Platform.

== Applies To ==

* innovaphone firmware and apps V16

==Requirements==
* innovaphone Application Platform (image version 140011 or higher)

==Concept==

The App IP offers modules known from innovaphone gateways, like the PBX, TURN server functionality etc.

==How it works==

=== Single instance mode ===
Unlike other App Services, the App IP is a single instance App Service, so you can create '''just''' a single instance and not multiple instances.

== Licensing ==
Standard licensing mechanisms apply to the App IP as they apply to innovaphone gateways.

In addition, every port license requires a dedicated IPAP license (similar to the IPVA license for virtual machines).

== Apps ==

There is no App provided by this App Service.

== PBX Manager Plugins ==

There is no PBX Manager Plugin provided by this App Service.

== Configuration ==

The configuration is done as an innovaphone gateway is configured too.

=== Create instance ===
You have to create one instance for the App IP Service.

[[Courseware:IT Advanced - 04 Setting up the Application Platform#Adding an App Service instance|Here]] are more informations how to do this.

We recommend the following settings: 
'''Name''' = ip 
'''Domain''' = customer domain (system name of the PBX) 
'''Password''' = The password '''must be set to "pwd"''' for Install and will be changed during the process. '''Note:''' if you want to login with the Adv.GUI to the PBX prior to the Install proces, this is also the admin password! 
'''Webserver Path''' - Adustable, will be filled automatically with the value "$domain/ip", eg. <code>domain.com/ip</code>

=== Install Process ===
Install can be started under the webserver path of the App IP instance and /''install.htm'', e.g.: http://app.domain.com/domain.com/ip/install.htm

⚠️ Use standard ports for installation. If necessary, install via a reverse proxy

⚠️ Do not use the localhost (127.0.0.1) address

=== Advanced UI ===
The advanced UI is reachable under the webserver path of the App IP instance and /admin.xml?xsl=admin.xsl, e.g.:
https://app.domain.com/domain.com/ip/admin.xml?xsl=admin.xsl

==== Password ====
The password for the Advanced UI is the password of the App IP instance. 
If the Devices App rolls out passwords, the domain password is also used for the App IP admin login.

=== IP configuration ===
As the App IP is just an App on an App Platform, there are no IP4/IP6, NTP etc. settings as on other innovaphone devices.

==== Devices App ====
If your App Platform which runs the App IP is connected to a Devices App, you can access the Advanced UI with the '''PBX''' tab of your App Platform device.

== Functional Distinction from a Gateway or an IPVA ==
Due to the system architecture, not all existing software functions of a gateway or an IPVA can be made available in an "IP App".

The following features are not available:
* PBX users with "additional user rights" and an associated login to the advanced UI
* SOAP (currently)

==Troubleshooting==
The App IP offers standard tracing mechanism for App Services and in addition mechanisms known from innovaphone gateways. 
You can enable module related trace flags with config change commands or by setting trace flags under Maintenance -> Tracing in the Advanced UI of the App IP.

Trace files are not found under Maintenance -> Tracing but on the App IP service on your App Platform Manager.

==Known issues==
The installation process must be performed using a DNS name rather than an IP address. 
The URL must include the parameter ''?apdns="DNS from App Platform"'' in the path, for example: http://app.domain.com/domain.com/ip/install.htm?apdns=pbx.domain.com 
Starting with version 16r1 sr1, installation using an IP address is supported. 

However, it is generally recommended to use DNS for the installation.

==Related Articles==
* [[Reference16r1:Concept_innovaphone_App_Platform_Container]]

Reference16r1:Concept App Service IP

2026-07-21T07:12:29Z

Slu: /* Troubleshooting */

[[Category:Concept|Apps]]
[[Category:Concept|IP]]

The App IP is an app which offers the PBX functionality and further functionalities as App service on our innovaphone App Platform.

== Applies To ==

* innovaphone firmware and apps V16

==Requirements==
* innovaphone Application Platform (image version 140011 or higher)

==Concept==

The App IP offers modules known from innovaphone gateways, like the PBX, TURN server functionality etc.

==How it works==

=== Single instance mode ===
Unlike other App Services, the App IP is a single instance App Service, so you can create '''just''' a single instance and not multiple instances.

== Licensing ==
Standard licensing mechanisms apply to the App IP as they apply to innovaphone gateways.

In addition, every port license requires a dedicated IPAP license (similar to the IPVA license for virtual machines).

== Apps ==

There is no App provided by this App Service.

== PBX Manager Plugins ==

There is no PBX Manager Plugin provided by this App Service.

== Configuration ==

The configuration is done as an innovaphone gateway is configured too.

=== Create instance ===
You have to create one instance for the App IP Service.

[[Courseware:IT Advanced - 04 Setting up the Application Platform#Adding an App Service instance|Here]] are more informations how to do this.

We recommend the following settings: 
'''Name''' = ip 
'''Domain''' = customer domain (system name of the PBX) 
'''Password''' = The password '''must be set to "pwd"''' for Install and will be changed during the process. '''Note:''' if you want to login with the Adv.GUI to the PBX prior to the Install proces, this is also the admin password!

=== Install Process ===
Install can be started under the webserver path of the App IP instance and /''install.htm'', e.g.: http://app.domain.com/domain.com/ip/install.htm

⚠️ Use standard ports for installation. If necessary, install via a reverse proxy

⚠️ Do not use the localhost (127.0.0.1) address

=== Advanced UI ===
The advanced UI is reachable under the webserver path of the App IP instance and /admin.xml?xsl=admin.xsl, e.g.:
https://app.domain.com/domain.com/ip/admin.xml?xsl=admin.xsl

==== Password ====
The password for the Advanced UI is the password of the App IP instance. 
If the Devices App rolls out passwords, the domain password is also used for the App IP admin login.

=== IP configuration ===
As the App IP is just an App on an App Platform, there are no IP4/IP6, NTP etc. settings as on other innovaphone devices.

==== Devices App ====
If your App Platform which runs the App IP is connected to a Devices App, you can access the Advanced UI with the '''PBX''' tab of your App Platform device.

== Functional Distinction from a Gateway or an IPVA ==
Due to the system architecture, not all existing software functions of a gateway or an IPVA can be made available in an "IP App".

The following features are not available:
* PBX users with "additional user rights" and an associated login to the advanced UI
* SOAP (currently)

==Troubleshooting==
The App IP offers standard tracing mechanism for App Services and in addition mechanisms known from innovaphone gateways. 
You can enable module related trace flags with config change commands or by setting trace flags under Maintenance -> Tracing in the Advanced UI of the App IP.

Trace files are not found under Maintenance -> Tracing but on the App IP service on your App Platform Manager.

==Known issues==
The installation process must be performed using a DNS name rather than an IP address. 
The URL must include the parameter ''?apdns="DNS from App Platform"'' in the path, for example: http://app.domain.com/domain.com/ip/install.htm?apdns=pbx.domain.com 
Starting with version 16r1 sr1, installation using an IP address is supported. 

However, it is generally recommended to use DNS for the installation.

==Related Articles==
* [[Reference16r1:Concept_innovaphone_App_Platform_Container]]

Howto16r1:Reverse Proxy with HAProxy

2026-07-14T12:50:21Z

Slu: /* Configuration Example */

This article explains how to configure HAProxy to work with the innovaphone Reverse Proxy, specifically when using WebSockets.

== Problem Description ==

When HAProxy is deployed in front of an innovaphone Reverse Proxy, WebSocket connections may not function correctly by default. This can cause issues such as:

* myApps browser sessions reloading or disconnecting periodically (e.g. every 60 seconds)
* WebSocket-based services failing to establish stable connections
* Unexpected behavior with real-time communication features

This happens because HAProxy requires specific configuration to handle WebSocket upgrades properly. The most common issue is that the WebSocket Upgrade/Connection headers are not passed through correctly, or the HTTP keep-alive behavior interferes with the persistent WebSocket connection.

== Solution ==

HAProxy needs to be configured to pass through the WebSocket upgrade headers correctly. The following configuration changes are required:

* Enable HTTP keep-alive
* Pass through the Upgrade and Connection headers
* Configure proper timeouts for WebSocket connections

The key is to add the correct headers to the backend configuration so that HAProxy does not interfere with the WebSocket upgrade process.

== Configuration Example ==

The following is a working HAProxy configuration example for connecting to an innovaphone Reverse Proxy:

frontend https-frontend
bind *:443
mode http
option http-keep-alive
timeout client 30000
http-request set-var(txn.txnhost) hdr(host)
use_backend innovaphone if { var(txn.txnhost) -m sub innovaphone }

backend innovaphone
mode http
timeout connect 30000
timeout server 30000
http-request set-header X-Forwarded-Proto https
http-request set-header Host 192.168.26.11
http-request set-header X-Forwarded-Host innovaphone.example.com
http-request set-header Upgrade %[hdr(upgrade)]
http-request set-header Connection %[hdr(connection),lower]
server innovaphone 192.168.26.11:80 check

=== Key Parameters Explained ===

* ''option http-keep-alive'' (frontend): Ensures that the frontend connection is kept alive and can be reused for multiple requests, including WebSocket upgrades.
* ''timeout client/server 30000'': Sufficiently long timeouts to prevent premature disconnection of persistent WebSocket connections.
* ''http-request set-header X-Forwarded-Proto https'': Preserves the original protocol (HTTPS) so that the innovaphone Reverse Proxy can correctly identify the scheme.
* ''http-request set-header Host'': Sets the correct Host header for the backend, which is important for virtual host routing on the innovaphone Reverse Proxy.
* ''http-request set-header Upgrade'': Passes the ''Upgrade'' header (e.g. "websocket") to the backend, which is required for the WebSocket handshake.
* ''http-request set-header Connection'': Passes the ''Connection'' header (e.g. "Upgrade") to the backend, which is required for the WebSocket handshake.

== Troubleshooting ==

If you are experiencing issues with WebSocket connections through HAProxy:

* Review the HAProxy configuration for proper WebSocket handling (see parameters above)
* Check the HAProxy logs for any connection errors
* Ensure that timeout values are set appropriately for long-lived connections
* Verify that the Upgrade and Connection headers are being passed through correctly
* Test the WebSocket connection without HAProxy in the path to isolate the problem

For detailed HAProxy WebSocket configuration, please refer to the official HAProxy documentation:

[https://www.haproxy.com/blog/websockets-load-balancing-with-haproxy HAProxy WebSocket Blog]

== When to Open a Support Ticket ==

If problems persist after reviewing and adjusting the HAProxy configuration, please open a support ticket with:

* A pcap capture from the innovaphone Reverse Proxy (reverse proxy / all IPv4 TCP/UDP traffic / all IPv4 TLS traffic / enable RPCAP)
* The relevant Client ID
* Your HAProxy configuration (if available)

[[Category:Reverse_Proxy]]
[[Category:Concept_Reverse_Proxy]]

Howto16r1:Reverse Proxy with HAProxy

2026-07-13T14:12:26Z

Slu: /* Configuration Example */

This article explains how to configure HAProxy to work with the innovaphone Reverse Proxy, specifically when using WebSockets.

== Problem Description ==

When HAProxy is deployed in front of an innovaphone Reverse Proxy, WebSocket connections may not function correctly by default. This can cause issues such as:

* myApps browser sessions reloading or disconnecting periodically (e.g. every 60 seconds)
* WebSocket-based services failing to establish stable connections
* Unexpected behavior with real-time communication features

This happens because HAProxy requires specific configuration to handle WebSocket upgrades properly. The most common issue is that the WebSocket Upgrade/Connection headers are not passed through correctly, or the HTTP keep-alive behavior interferes with the persistent WebSocket connection.

== Solution ==

HAProxy needs to be configured to pass through the WebSocket upgrade headers correctly. The following configuration changes are required:

* Enable HTTP keep-alive
* Pass through the Upgrade and Connection headers
* Configure proper timeouts for WebSocket connections

The key is to add the correct headers to the backend configuration so that HAProxy does not interfere with the WebSocket upgrade process.

== Configuration Example ==

The following is a working HAProxy configuration example for connecting to an innovaphone Reverse Proxy:

frontend https-frontend
bind *:443
mode http
option http-keep-alive
timeout client 30000
http-request set-var(txn.txnhost) hdr(host)
use_backend innovaphone if { var(txn.txnhost) -m sub inovaphone }

backend innovaphone
mode http
timeout connect 30000
timeout server 30000
http-request set-header X-Forwarded-Proto https
http-request set-header Host 192.168.26.11
http-request set-header X-Forwarded-Host inovaphone.example.com
http-request set-header Upgrade %[hdr(upgrade)]
http-request set-header Connection %[hdr(connection),lower]
server innovaphone 192.168.26.11:80 check

=== Key Parameters Explained ===

* ''option http-keep-alive'' (frontend): Ensures that the frontend connection is kept alive and can be reused for multiple requests, including WebSocket upgrades.
* ''timeout client/server 30000'': Sufficiently long timeouts to prevent premature disconnection of persistent WebSocket connections.
* ''http-request set-header X-Forwarded-Proto https'': Preserves the original protocol (HTTPS) so that the innovaphone Reverse Proxy can correctly identify the scheme.
* ''http-request set-header Host'': Sets the correct Host header for the backend, which is important for virtual host routing on the innovaphone Reverse Proxy.
* ''http-request set-header Upgrade'': Passes the ''Upgrade'' header (e.g. "websocket") to the backend, which is required for the WebSocket handshake.
* ''http-request set-header Connection'': Passes the ''Connection'' header (e.g. "Upgrade") to the backend, which is required for the WebSocket handshake.

== Troubleshooting ==

If you are experiencing issues with WebSocket connections through HAProxy:

* Review the HAProxy configuration for proper WebSocket handling (see parameters above)
* Check the HAProxy logs for any connection errors
* Ensure that timeout values are set appropriately for long-lived connections
* Verify that the Upgrade and Connection headers are being passed through correctly
* Test the WebSocket connection without HAProxy in the path to isolate the problem

For detailed HAProxy WebSocket configuration, please refer to the official HAProxy documentation:

[https://www.haproxy.com/blog/websockets-load-balancing-with-haproxy HAProxy WebSocket Blog]

== When to Open a Support Ticket ==

If problems persist after reviewing and adjusting the HAProxy configuration, please open a support ticket with:

* A pcap capture from the innovaphone Reverse Proxy (reverse proxy / all IPv4 TCP/UDP traffic / all IPv4 TLS traffic / enable RPCAP)
* The relevant Client ID
* Your HAProxy configuration (if available)

[[Category:Reverse_Proxy]]
[[Category:Concept_Reverse_Proxy]]

Howto16r1:Reverse Proxy with HAProxy

2026-07-13T14:12:07Z

Slu:

This article explains how to configure HAProxy to work with the innovaphone Reverse Proxy, specifically when using WebSockets.

== Problem Description ==

When HAProxy is deployed in front of an innovaphone Reverse Proxy, WebSocket connections may not function correctly by default. This can cause issues such as:

* myApps browser sessions reloading or disconnecting periodically (e.g. every 60 seconds)
* WebSocket-based services failing to establish stable connections
* Unexpected behavior with real-time communication features

This happens because HAProxy requires specific configuration to handle WebSocket upgrades properly. The most common issue is that the WebSocket Upgrade/Connection headers are not passed through correctly, or the HTTP keep-alive behavior interferes with the persistent WebSocket connection.

== Solution ==

HAProxy needs to be configured to pass through the WebSocket upgrade headers correctly. The following configuration changes are required:

* Enable HTTP keep-alive
* Pass through the Upgrade and Connection headers
* Configure proper timeouts for WebSocket connections

The key is to add the correct headers to the backend configuration so that HAProxy does not interfere with the WebSocket upgrade process.

== Configuration Example ==

The following is a working HAProxy configuration example for connecting to an innovaphone Reverse Proxy:

<code>
frontend https-frontend
bind *:443
mode http
option http-keep-alive
timeout client 30000
http-request set-var(txn.txnhost) hdr(host)
use_backend innovaphone if { var(txn.txnhost) -m sub inovaphone }

backend innovaphone
mode http
timeout connect 30000
timeout server 30000
http-request set-header X-Forwarded-Proto https
http-request set-header Host 192.168.26.11
http-request set-header X-Forwarded-Host inovaphone.example.com
http-request set-header Upgrade %[hdr(upgrade)]
http-request set-header Connection %[hdr(connection),lower]
server innovaphone 192.168.26.11:80 check
</code>

=== Key Parameters Explained ===

* ''option http-keep-alive'' (frontend): Ensures that the frontend connection is kept alive and can be reused for multiple requests, including WebSocket upgrades.
* ''timeout client/server 30000'': Sufficiently long timeouts to prevent premature disconnection of persistent WebSocket connections.
* ''http-request set-header X-Forwarded-Proto https'': Preserves the original protocol (HTTPS) so that the innovaphone Reverse Proxy can correctly identify the scheme.
* ''http-request set-header Host'': Sets the correct Host header for the backend, which is important for virtual host routing on the innovaphone Reverse Proxy.
* ''http-request set-header Upgrade'': Passes the ''Upgrade'' header (e.g. "websocket") to the backend, which is required for the WebSocket handshake.
* ''http-request set-header Connection'': Passes the ''Connection'' header (e.g. "Upgrade") to the backend, which is required for the WebSocket handshake.

== Troubleshooting ==

If you are experiencing issues with WebSocket connections through HAProxy:

* Review the HAProxy configuration for proper WebSocket handling (see parameters above)
* Check the HAProxy logs for any connection errors
* Ensure that timeout values are set appropriately for long-lived connections
* Verify that the Upgrade and Connection headers are being passed through correctly
* Test the WebSocket connection without HAProxy in the path to isolate the problem

For detailed HAProxy WebSocket configuration, please refer to the official HAProxy documentation:

[https://www.haproxy.com/blog/websockets-load-balancing-with-haproxy HAProxy WebSocket Blog]

== When to Open a Support Ticket ==

If problems persist after reviewing and adjusting the HAProxy configuration, please open a support ticket with:

* A pcap capture from the innovaphone Reverse Proxy (reverse proxy / all IPv4 TCP/UDP traffic / all IPv4 TLS traffic / enable RPCAP)
* The relevant Client ID
* Your HAProxy configuration (if available)

[[Category:Reverse_Proxy]]
[[Category:Concept_Reverse_Proxy]]

Howto16r1:Reverse Proxy with HAProxy

2026-07-13T14:09:58Z

Slu: Fix list formatting and add HAProxy WebSocket config details - Co-Authored-By: Claude claude-opus-4-5-20251101

This article explains how to configure HAProxy to work with the innovaphone Reverse Proxy, specifically when using WebSockets.

== Problem Description ==

When HAProxy is deployed in front of an innovaphone Reverse Proxy, WebSocket connections may not function correctly by default. This can cause issues such as:

* myApps browser sessions reloading or disconnecting periodically (e.g. every 60 seconds)
* WebSocket-based services failing to establish stable connections
* Unexpected behavior with real-time communication features

This happens because HAProxy requires specific configuration to handle WebSocket upgrades properly. The most common issue is that the WebSocket Upgrade/Connection headers are not passed through correctly, or the HTTP keep-alive behavior interferes with the persistent WebSocket connection.

== Solution ==

HAProxy needs to be configured to pass through the WebSocket upgrade headers correctly. The following configuration changes are required:

* Enable HTTP keep-alive
* Pass through the Upgrade and Connection headers
* Configure proper timeouts for WebSocket connections

The key is to add the correct headers to the backend configuration so that HAProxy does not interfere with the WebSocket upgrade process.

== Configuration Example ==

The following is a working HAProxy configuration example for connecting to an innovaphone Reverse Proxy:

<source lang="haproxy">
frontend https-frontend
bind *:443
mode http
option http-keep-alive
timeout client 30000
http-request set-var(txn.txnhost) hdr(host)
use_backend innovaphone if { var(txn.txnhost) -m sub inovaphone }

backend innovaphone
mode http
timeout connect 30000
timeout server 30000
http-request set-header X-Forwarded-Proto https
http-request set-header Host 192.168.26.11
http-request set-header X-Forwarded-Host inovaphone.example.com
http-request set-header Upgrade %[hdr(upgrade)]
http-request set-header Connection %[hdr(connection),lower]
server innovaphone 192.168.26.11:80 check
</source>

=== Key Parameters Explained ===

* ''option http-keep-alive'' (frontend): Ensures that the frontend connection is kept alive and can be reused for multiple requests, including WebSocket upgrades.
* ''timeout client/server 30000'': Sufficiently long timeouts to prevent premature disconnection of persistent WebSocket connections.
* ''http-request set-header X-Forwarded-Proto https'': Preserves the original protocol (HTTPS) so that the innovaphone Reverse Proxy can correctly identify the scheme.
* ''http-request set-header Host'': Sets the correct Host header for the backend, which is important for virtual host routing on the innovaphone Reverse Proxy.
* ''http-request set-header Upgrade'': Passes the ''Upgrade'' header (e.g. "websocket") to the backend, which is required for the WebSocket handshake.
* ''http-request set-header Connection'': Passes the ''Connection'' header (e.g. "Upgrade") to the backend, which is required for the WebSocket handshake.

== Troubleshooting ==

If you are experiencing issues with WebSocket connections through HAProxy:

* Review the HAProxy configuration for proper WebSocket handling (see parameters above)
* Check the HAProxy logs for any connection errors
* Ensure that timeout values are set appropriately for long-lived connections
* Verify that the Upgrade and Connection headers are being passed through correctly
* Test the WebSocket connection without HAProxy in the path to isolate the problem

For detailed HAProxy WebSocket configuration, please refer to the official HAProxy documentation:

[https://www.haproxy.com/blog/websockets-load-balancing-with-haproxy HAProxy WebSocket Blog]

== When to Open a Support Ticket ==

If problems persist after reviewing and adjusting the HAProxy configuration, please open a support ticket with:

* A pcap capture from the innovaphone Reverse Proxy (reverse proxy / all IPv4 TCP/UDP traffic / all IPv4 TLS traffic / enable RPCAP)
* The relevant Client ID
* Your HAProxy configuration (if available)

[[Category:Reverse_Proxy]]
[[Category:Concept_Reverse_Proxy]]

Howto16r1:Reverse Proxy with HAProxy

2026-07-13T14:05:54Z

Slu: Create HAProxy WebSocket configuration guide - Co-Authored-By: Claude claude-opus-4-5-20251101

Reference16r1:IP6/ETH/IP6

2026-06-25T11:41:16Z

Slu: /* Addresses */

== Configuration ==
{|
|valign=top nowrap=true|'''Address Configuration:'''
| Automatic or static IP6 address configuration
|}

== Addresses ==
{|
|valign=top nowrap=true|'''IP6 Address:'''
| The IP address used by the network adapter.
|-
|valign=top nowrap=true|'''Prefix:'''
| Prefix in CIDR notation without slash
|}

== Gateway ==
{|
|valign=top nowrap=true|'''Default Gateway:'''
| The standard router used by the device.
|}

== Options==
{|
|valign=top nowrap=true|'''Router Interface:'''
| Interface is router. Replies Router Solicitations with Router Advertisments, publishes routes and forwards packets.
|-
|valign=top nowrap=true|'''Proxy ND:'''
| Enable replies to Neighbour Discovery requests if for queried IP6 address an active route exists
|-
| '''Disabled:'''
| Disable the interface
|}

== Static IP6 Routes ==
In the '''Static IP6 Routes''' section, additional network routes can be defined if other network areas apart from the local network are required.
{|
|valign=top nowrap=true|'''Destination:'''
| The network address of the destination route.
|-
|valign=top nowrap=true|'''Gateway:'''
| The gateway of the network being routed.
|}

== IP6-Filter==
Definition of global IP6 address filters to protect the device from unauthorized access.
{|
|valign=top nowrap=true|'''Enable:'''
| Consider defined filters
|-
|valign=top nowrap=true|'''IP6-Filter-Address:'''
| The network address to be filtered.
|-
|valign=top nowrap=true|'''IP6-Filter-Port:'''
| The port to be filtered out of the defined network address.
|-
|valign=top nowrap=true|'''Protocol:'''
| Protocol to which the filter is applied. UDP or TCP.
|}

Reference16r1:IP6/ETH/IP6

2026-06-25T11:39:35Z

Slu: Created page with "== Configuration == {| |valign=top nowrap=true|'''Address Configuration:''' | Automatic or static IP6 address configuration |} == Addresses == {| |valign=top nowrap=true|'''IP6 Address:''' | The IP6 address used by the network adapter. |- |valign=top nowrap=true|'''Prefix:''' | tbd |} == Gateway == {| |valign=top nowrap=true|'''Default Gateway:''' | The standard router used by the device. |} == Options== {| |valign=top nowrap=true|'''Router Interface:''' | tbd |- |val..."

== Configuration ==
{|
|valign=top nowrap=true|'''Address Configuration:'''
| Automatic or static IP6 address configuration
|}

== Addresses ==
{|
|valign=top nowrap=true|'''IP6 Address:'''
| The IP6 address used by the network adapter.
|-
|valign=top nowrap=true|'''Prefix:'''
| tbd
|}

== Gateway ==
{|
|valign=top nowrap=true|'''Default Gateway:'''
| The standard router used by the device.
|}

== Options==
{|
|valign=top nowrap=true|'''Router Interface:'''
| tbd
|-
|valign=top nowrap=true|'''Proxy ND:'''
| Enable replies to Neighbour Discovery requests if for queried IP6 address an active route exists
|-
| '''Disabled:'''
| Disable the interface
|}

== Static IP6 Routes ==
In the '''Static IP6 Routes''' section, additional network routes can be defined, if other network areas apart from the local network are required.
{|
|valign=top nowrap=true|'''Destination:'''
| The network address of the destination route.
|-
|valign=top nowrap=true|'''Gateway:'''
| The standard gateway of the network being routed.
|}

== IP6-Filter==
Definition of global IP6 address filters to protect the device from unauthorised access.
{|
|valign=top nowrap=true|'''Enable:'''
| Consider defined filters
|-
|valign=top nowrap=true|'''IP6-Filter-Address:'''
| The network address to be filtered.
|-
|valign=top nowrap=true|'''IP6-Filter-Port:'''
| The port to be filtered out of the defined network address.
|-
|valign=top nowrap=true|'''Protocol:'''
| Protocol to which the filter is applied. UDP or TCP.
|}

Reference16r1:IP6/General/Routing

2026-06-25T11:39:11Z

Slu: Created page with "The '''routing''' table of the current IP configuration of the device is displayed here. The table is used for fault analysis by the network administrator. The table is structured as follows: {| |valign=top nowrap=true|'''Destination:''' | The destination network. |- |valign=top nowrap=true|'''Gateway:''' | The IP address of the router. |- |valign=top nowrap=true|'''Interface:''' | Displays the interface on which the route was created. Possible interfaces are: ''ETH0, '..."

The '''routing''' table of the current IP configuration of the device is displayed here. The table is used for fault analysis by the network administrator. The table is structured as follows:

{|
|valign=top nowrap=true|'''Destination:'''
| The destination network.
|-
|valign=top nowrap=true|'''Gateway:'''
| The IP address of the router.
|-
|valign=top nowrap=true|'''Interface:'''
| Displays the interface on which the route was created. Possible interfaces are: ''ETH0, ''ETH1, ''PPP0-31'', ''Local'' and ''ISDN''.
|-
|valign=top nowrap=true|'''Flag:'''
| Address flag.
|}

Reference16r1:IP4/General/Routing

2026-06-25T11:36:49Z

Slu: Created page with "The '''routing''' table of the current IP configuration of the device is displayed here. The table is used for fault analysis by the network administrator. The table is structured as follows: {| |valign=top nowrap=true|'''Destination Network:''' | The destination network address. |- |valign=top nowrap=true|'''Network Mask:''' | The associated network mask. |- |valign=top nowrap=true|'''Gateway:''' | The IP-Adresse of the router. |- |valign=top nowrap=true|'''Interface:'..."

The '''routing''' table of the current IP configuration of the device is displayed here. The table is used for fault analysis by the network administrator. The table is structured as follows:

{|
|valign=top nowrap=true|'''Destination Network:'''
| The destination network address.
|-
|valign=top nowrap=true|'''Network Mask:'''
| The associated network mask.
|-
|valign=top nowrap=true|'''Gateway:'''
| The IP-Adresse of the router.
|-
|valign=top nowrap=true|'''Interface:'''
| Displays the interface on which the route was created. Possible interfaces are: ''ETH0, ''ETH1, ''PPP0-31'', ''Local'' and ''ISDN''.
|-
|valign=top nowrap=true|'''State:'''
| Possible states are: ''Up'' or ''Down''.
|}

Reference16r1:Gateway/GK/GW

2026-06-24T06:17:57Z

Slu: /* Interface (VoIP Interfaces) */

Below is an overview of all the gateway's configurable VoIP interfaces:
* '''Interface:''' The name of the interface. Clicking this name opens a popup page, on which all settings can be made. The settings are described in more detail in the following chapter "[[#Interface .28VoIP Interfaces.29|Administration/Gateway/VOIP/Interface (VoIP interfaces)]]".
* '''CGPN In, CDPN In, CGPN Out, CDPN Out:''' Precise details on CGPN In, CDPN In, CGPN Out and CDPN Out mappings are contained in the chapter entitled "[[#CGPN.2FCDPN Mappings|Administration/Gateway/Interfaces/CGPN-CDPN Mappings]]" further up in the text.
* '''Registration:''' If a terminal has successfully registered with a gateway, then this is indicated in this column through specification of the IP address <Name of the VoIP interface:Call number:IP address>.

== Interface (VoIP Interfaces) ==
Clicking the relevant VoIP interface (GW1-12 <Name of the VoIP interface>) in the Interface column opens a popup page, on which the VoIP interfaces can be individually configured. Like the PBX objects, this popup page also contains standard entry fields that occur, more or less, in all VoIP interfaces.

These standard fields are:
* '''Name:''' The descriptive name of the VoIP interface.
* '''Disable:''' A checked check box disables the relevant VoIP interface.
* '''Protocol:''' The protocol to be used, that is, H.323 or SIP. Depending on which protocol is used, the set-up of the entry fields changes.
* '''Mode:''' Describes the mode of registration. Possible registration modes are:
# Gateway without Registration - Logs the VoIP interface (gateway) on to the configured gatekeeper without a registration.
# Register as Endpoint - Registers a VoIP terminal with the configured gatekeeper.
# Register as Gateway - Registers a VoIP gateway with the configured gatekeeper.
# Gatekeeper/Registrar - Is required for managing all gatekeeper registrations on a gateway. (is only visible when running in test-mode or if a gatekeeper license is available)
# ENUM - Is used to register an ENUM connection with the relevant interface.
* '''Gatekeeper Address (primary):''' The primary Gatekeeper IP address at which the terminal or gateway is to register via the relevant interface. Only necessary for modes 2 and 3. (IPv6 addresses must be enclosed in square brackets)
* '''Gatekeeper Address (secondary):''' The alternative gatekeeper IP address at which the terminal or gateway is to register via the relevant interface, if registration with the primary gatekeeper fails. Only necessary for modes 2 and 3. (IPv6 addresses must be enclosed in square brackets)
* '''Local Domain:''' Replaces the existing system/domain name (for H323 federation only).
* '''Mask:''' By specifying a network mask, incoming calls can be filtered. Specification of the network mask 255.255.0.0 therefore allows incoming calls on the relevant interface for terminals from the IP address range 192.168.0.0 - 192.168.255.255 .
* '''Gatekeeper Identifier:''' It is also sufficient to specify only the gatekeeper ID. Every gatekeeper in a network can be identified by means of its own gatekeeper ID, so that several gatekeepers can be operated in a network, with each terminal nevertheless identifying the correct gatekeeper by means of Gatekeeper Discovery (uses the multicast address 224.0.1.41).
* '''STUN SERVER:''' The STUN server name or IP address must be configured if this device has no public IP address while the SIP server is accessible under a public IP address. The value is given by the SIP provider or administrator (for example, stun.xten.com or 64.69.76.23). You can choose any STUN server; it does not necessarily have to correspond to the one of the SIP provider.
* '''Local Signalling Port:''' Signalling Port used by the Interface.
* '''SIP - Register as Gateway/Endpoint:'''
** '''Remote Domain (SIP Only):''' SIP Domain of the remote SIP Server to register (often equal to the SIP Proxy).
** '''Proxy (SIP Only):''' DNS name or IP address of the SIP proxy where SIP messages (REGISTER,INVITE,etc) are to be sent to. Proxy can be omitted if domain part of AOR can be used as remote signaling destination and it's set at Remote Domain.
* '''SIP - Gateway without Registration:'''
** '''Remote Domain (SIP Only):''' Check the Domain/IP Address on the SIP URI "FROM" field and removes it if match.
** '''Local Domain (SIP Only):''' Check the Domain/IP Address on the SIP URI "TO" field and removes it if match.
** '''Proxy (SIP Only):''' DNS name or IP address of the SIP proxy where SIP messages (INVITE,etc) are to be sent to, this field it's mandatory.
** '''Filter Incoming Calls (SIP Only):''' Accept Incoming Call on this interface only if the domain part of the "To:" field SIP URI matches the ''Local Domain'' configured. If not accepted, the call may still be accepted by another interface
* '''H323/TLS - Gateway without Registration
** '''Federation:''' Turns on open federation, which means the domain part of a destination name is used to look up the remote gateway in the DNS
** '''Veriyfy Cert:''' If set, the remote ceritficate on an incoming call is verified against the domain part of the source name

=== Authorization section ===
In the '''Authorization''' section, you can store a password for the VoIP interface.
* '''Password / Retype:''' The security of the registration can be raised by specifying a password (Password). The password must be confirmed (Retype).

=== Alias List section ===
In the '''Alias List''' section, you specify the call name (H.323) and the call number (E.164) of the relevant registration. For VoIP end points, you should define the assigned direct dialling number or MSN as the E.164 address, and the name as the H.323 name. For VoIP gateways it is sufficient to define the name.
* '''Name:''' The H.323 name.
* '''Number:''' The E.164 call number.

=== Coder Preferences section ===
The standard entry fields in the '''Coder Preferences''' section were already described in chapter "[[Reference:Administration/Gateway/Interfaces#Interface .28ISDN.2C SIP .26 virtual interfaces.29|Administration/Gateway/Interfaces/Interface (physical and virtual interfaces)]]".

=== Media Properties ===
The standard entry fields in the '''Media Properties''' section were already described [[{{NAMESPACE}}:Gateway/Interfaces/Media_Properties | Media Properties]].

=== H.323 Interop Tweaks section ===
In addition to the standard fields, several advanced settings are available in the '''H.323 Interop Tweaks''' section. They are normally not necessary and are merely used to solve compatibility problems with some PBXs:
* '''No Faststart:''' The H.245 faststart procedure is enabled as standard. Outgoing calls are made with faststart, incoming calls with faststart are answered with faststart. A checked check box disables the H.245 faststart procedure. Outgoing calls are made without faststart, incoming calls with and without faststart are answered without faststart.
* '''No H.245 Tunneling:''' The H.245 tunneling procedure is enabled as standard. The voice data connection is negotiated in the TCP signalling connection*) already available. This can be advantageous in connection with NAT and firewalls.
A checked check box disables the H.245 tunneling procedure, meaning that a separate TCP connection is set up for this negotiation. This applies to the signalling connection leading out of the gatekeeper.
* '''Suppress HLC:''' A checked check box disables the transmission of HLC (High Layer Compatibility) information elements.
* '''Suppress FTY:''' A checked check box disables the transmission of FTY (Facility) information elements.
* '''Suppress Subaddress:''' A checked check box disables the transmission of Subaddress information elements.
*) From a technical viewpoint, the H.245 protocol does not establish its own TCP connection,
but shares the H.225 TCP connection.

=== SIP Interop Tweaks section ===
Miscellaneous interoperability options for SIP.
{|
|valign=top nowrap=true|'''Proposed Registration Interval'''
|Set in seconds, default is 120 seconds
|-
|valign=top nowrap=true|'''Accept INVITE's from Anywhere'''
|If disabled, registered interfaces will reject INVITE's not coming from the SIP server with "305 Use Proxy".
|-
|valign=top nowrap=true|'''Enforce Sending Complete'''
|Affects handling of "484 Address Incomplete" responses. If enabled and "484 Address Incomplete" is received, the call is cleared. If not enabled and "484 Address Incomplete" is received, the call is retained and re-initiated in case of new dialing digits.
|-
|valign=top nowrap=true|'''No Video'''
|Removes Video Capabilities from outgoing media offer.
|-
|valign=top nowrap=true|'''No Early Media'''
|Ignore any SDP answer received before final connect response. (Affects only outgoing SIP calls)
|-
|valign=top nowrap=true|'''No Inband Information on Error'''
|Controls interworking of Q.931 DISC message. If this option is set, DISC message is always interworked into BYE request.
|-
|valign=top nowrap=true|'''No Inband Disconnect'''
|TBD.
|-
|valign=top nowrap=true|'''No Remote Hold Signaling'''
|Disables interworking of "inactive" into RemoteHold (affects connected SIP calls only).
|-
|valign=top nowrap=true|'''Take Refer-To URI as Remote Target URI'''
|If enabled: When REFER is received and transfer is executed by the Gateway application and a new INVITE is sent, the Request-URI of this INVITE matches the URI that has been received in Refer-To header in REFER. 
If not enabled: The Request-URI of the outgoing INVITE is created by usual means. Userpart of the Request-URI usually contains the CDPN as provided by Gateway application.
|-
|valign=top nowrap=true|'''To Header when Sending INVITE'''
|Affects only outgoing diverted calls . '''Called Party''': If set we write CDPN into To header of outgoing INVITE (and DGPN into History-Info header). '''Original Called Party''': If set we write the DGPN into To header of outgoing INVITE (and CDPN into Request-URI).
|-
|valign=top nowrap=true|'''From Header when Sending INVITE'''
|Controls the local URI (From header) of outgoing calls. Applys to registered interfaces only. '''Fixed AOR''': Fixed AOR is used as From-URI regardless of the actual calling party number. '''AOR with CGPN as Display''': Fixed AOR is used as From-URI and calling party number is added as display string. '''CGPN in user part of URI''': Variable From-URI with actual calling party number.
|-
|valign=top nowrap=true|'''Identity Header when Sending INVITE'''
|Controls the identity header (P-Preferred-Identity, P-Asserted-Identity and Remote-Party-Id). '''CGPN in user part of URI''': Variable From-URI with actual calling party number. '''Fixed AOR''': Fixed AOR is used as Identity-URI regardless of the actual calling party number.
|-
|valign=top nowrap=true|'''Reliability of Provisional Responses'''
|Controls the support of PRACK (RFC-3262). '''Supported''': Supported as optional extension. '''Required''': Required as mandatory extension. '''Disabled''': Hide support for PRACK extension.
|-
|valign=top nowrap=true|'''Microsoft Presence Format'''
|Enables special Microsoft Presence format/scheme, only used for SIP Federation with Lync 2013.
|}

== CGPN/CDPN Mappings ==
A detailed description may be found in the chapter entitled "[[Reference:Administration/Gateway/Interfaces#CGPN.2FCDPN Mappings|Administration/Gateway/Interface/CGPN-CDPN Mappings]]".

Reference16r1:Gateway/GK/GW

2026-06-24T06:16:12Z

Slu: Created page with "Below is an overview of all the gateway's configurable VoIP interfaces: * '''Interface:''' The name of the interface. Clicking this name opens a popup page, on which all settings can be made. The settings are described in more detail in the following chapter "Administration/Gateway/VOIP/Interface (VoIP interfaces)". * '''CGPN In, CDPN In, CGPN Out, CDPN Out:''' Precise details on CGPN In, CDPN In, CGPN Out and CDPN Out mappings are co..."

Below is an overview of all the gateway's configurable VoIP interfaces:
* '''Interface:''' The name of the interface. Clicking this name opens a popup page, on which all settings can be made. The settings are described in more detail in the following chapter "[[#Interface_.28VoIP_Interfaces.29|Administration/Gateway/VOIP/Interface (VoIP interfaces)]]".
* '''CGPN In, CDPN In, CGPN Out, CDPN Out:''' Precise details on CGPN In, CDPN In, CGPN Out and CDPN Out mappings are contained in the chapter entitled "[[#CGPN.2FCDPN_Mappings|Administration/Gateway/Interfaces/CGPN-CDPN Mappings]]" further up in the text.
* '''Registration:''' If a terminal has successfully registered with a gateway, then this is indicated in this column through specification of the IP address <Name of the VoIP interface:Call number:IP address>.

== Interface (VoIP Interfaces) ==
Clicking the relevant VoIP interface (GW1-12 <Name of the VoIP interface>) in the Interface column opens a popup page, on which the VoIP interfaces can be individually configured. Like the PBX objects, this popup page also contains standard entry fields that occur, more or less, in all VoIP interfaces.

These standard fields are:
* '''Name:''' The descriptive name of the VoIP interface.
* '''Disable:''' A checked check box disables the relevant VoIP interface.
* '''Protocol:''' The protocol to be used, that is, H.323 or SIP. Depending on which protocol is used, the set-up of the entry fields changes.
* '''Mode:''' Describes the mode of registration. Possible registration modes are:
# Gateway without Registration - Logs the VoIP interface (gateway) on to the configured gatekeeper without a registration.
# Register as Endpoint - Registers a VoIP terminal with the configured gatekeeper.
# Register as Gateway - Registers a VoIP gateway with the configured gatekeeper.
# Gatekeeper/Registrar - Is required for managing all gatekeeper registrations on a gateway. (is only visible when running in test-mode or if a gatekeeper license is available)
# ENUM - Is used to register an ENUM connection with the relevant interface.
* '''Gatekeeper Address (primary):''' The primary Gatekeeper IP address at which the terminal or gateway is to register via the relevant interface. Only necessary for modes 2 and 3.
* '''Gatekeeper Address (secondary):''' The alternative gatekeeper IP address at which the terminal or gateway is to register via the relevant interface, if registration with the primary gatekeeper fails. Only necessary for modes 2 and 3 .
* '''Local Domain:''' Replaces the existing system/domain name (for H323 federation only).
* '''Mask:''' By specifying a network mask, incoming calls can be filtered. Specification of the network mask 255.255.0.0 therefore allows incoming calls on the relevant interface for terminals from the IP address range 192.168.0.0 - 192.168.255.255 .
* '''Gatekeeper Identifier:''' It is also sufficient to specify only the gatekeeper ID. Every gatekeeper in a network can be identified by means of its own gatekeeper ID, so that several gatekeepers can be operated in a network, with each terminal nevertheless identifying the correct gatekeeper by means of Gatekeeper Discovery (uses the multicast address 224.0.1.41).
* '''STUN SERVER:''' The STUN server name or IP address must be configured if this device has no public IP address while the SIP server is accessible under a public IP address. The value is given by the SIP provider or administrator (for example, stun.xten.com or 64.69.76.23). You can choose any STUN server; it does not necessarily have to correspond to the one of the SIP provider.
* '''Local Signalling Port:''' Signalling Port used by the Interface.
* '''SIP - Register as Gateway/Endpoint:'''
** '''Remote Domain (SIP Only):''' SIP Domain of the remote SIP Server to register (often equal to the SIP Proxy).
** '''Proxy (SIP Only):''' DNS name or IP address of the SIP proxy where SIP messages (REGISTER,INVITE,etc) are to be sent to. Proxy can be omitted if domain part of AOR can be used as remote signaling destination and it's set at Remote Domain.
* '''SIP - Gateway without Registration:'''
** '''Remote Domain (SIP Only):''' Check the Domain/IP Address on the SIP URI "FROM" field and removes it if match.
** '''Local Domain (SIP Only):''' Check the Domain/IP Address on the SIP URI "TO" field and removes it if match.
** '''Proxy (SIP Only):''' DNS name or IP address of the SIP proxy where SIP messages (INVITE,etc) are to be sent to, this field it's mandatory.
** '''Filter Incoming Calls (SIP Only):''' Accept Incoming Call on this interface only if the domain part of the "To:" field SIP URI matches the ''Local Domain'' configured. If not accepted, the call may still be accepted by another interface
* '''H323/TLS - Gateway without Registration
** '''Federation:''' Turns on open federation, which means the domain part of a destination name is used to look up the remote gateway in the DNS
** '''Veriyfy Cert:''' If set, the remote ceritficate on an incoming call is verified against the domain part of the source name

=== Authorization section ===
In the '''Authorization''' section, you can store a password for the VoIP interface.
* '''Password / Retype:''' The security of the registration can be raised by specifying a password (Password). The password must be confirmed (Retype).

=== Alias List section ===
In the '''Alias List''' section, you specify the call name (H.323) and the call number (E.164) of the relevant registration. For VoIP end points, you should define the assigned direct dialling number or MSN as the E.164 address, and the name as the H.323 name. For VoIP gateways it is sufficient to define the name.
* '''Name:''' The H.323 name.
* '''Number:''' The E.164 call number.

=== Coder Preferences section ===
The standard entry fields in the '''Coder Preferences''' section were already described in chapter "[[Reference:Administration/Gateway/Interfaces#Interface_.28ISDN.2C_SIP_.26_virtual_interfaces.29|Administration/Gateway/Interfaces/Interface (physical and virtual interfaces)]]".

=== Media Properties ===
The standard entry fields in the '''Media Properties''' section were already described [[{{NAMESPACE}}:Gateway/Interfaces/Media_Properties | Media Properties]].

=== H.323 Interop Tweaks section ===
In addition to the standard fields, several advanced settings are available in the '''H.323 Interop Tweaks''' section. They are normally not necessary and are merely used to solve compatibility problems with some PBXs:
* '''No Faststart:''' The H.245 faststart procedure is enabled as standard. Outgoing calls are made with faststart, incoming calls with faststart are answered with faststart. A checked check box disables the H.245 faststart procedure. Outgoing calls are made without faststart, incoming calls with and without faststart are answered without faststart.
* '''No H.245 Tunneling:''' The H.245 tunneling procedure is enabled as standard. The voice data connection is negotiated in the TCP signalling connection*) already available. This can be advantageous in connection with NAT and firewalls.
A checked check box disables the H.245 tunneling procedure, meaning that a separate TCP connection is set up for this negotiation. This applies to the signalling connection leading out of the gatekeeper.
* '''Suppress HLC:''' A checked check box disables the transmission of HLC (High Layer Compatibility) information elements.
* '''Suppress FTY:''' A checked check box disables the transmission of FTY (Facility) information elements.
* '''Suppress Subaddress:''' A checked check box disables the transmission of Subaddress information elements.
*) From a technical viewpoint, the H.245 protocol does not establish its own TCP connection,
but shares the H.225 TCP connection.

=== SIP Interop Tweaks section ===
Miscellaneous interoperability options for SIP.
{|
|valign=top nowrap=true|'''Proposed Registration Interval'''
|Set in seconds, default is 120 seconds
|-
|valign=top nowrap=true|'''Accept INVITE's from Anywhere'''
|If disabled, registered interfaces will reject INVITE's not coming from the SIP server with "305 Use Proxy".
|-
|valign=top nowrap=true|'''Enforce Sending Complete'''
|Affects handling of "484 Address Incomplete" responses. If enabled and "484 Address Incomplete" is received, the call is cleared. If not enabled and "484 Address Incomplete" is received, the call is retained and re-initiated in case of new dialing digits.
|-
|valign=top nowrap=true|'''No Video'''
|Removes Video Capabilities from outgoing media offer.
|-
|valign=top nowrap=true|'''No Early Media'''
|Ignore any SDP answer received before final connect response. (Affects only outgoing SIP calls)
|-
|valign=top nowrap=true|'''No Inband Information on Error'''
|Controls interworking of Q.931 DISC message. If this option is set, DISC message is always interworked into BYE request.
|-
|valign=top nowrap=true|'''No Inband Disconnect'''
|TBD.
|-
|valign=top nowrap=true|'''No Remote Hold Signaling'''
|Disables interworking of "inactive" into RemoteHold (affects connected SIP calls only).
|-
|valign=top nowrap=true|'''Take Refer-To URI as Remote Target URI'''
|If enabled: When REFER is received and transfer is executed by the Gateway application and a new INVITE is sent, the Request-URI of this INVITE matches the URI that has been received in Refer-To header in REFER. 
If not enabled: The Request-URI of the outgoing INVITE is created by usual means. Userpart of the Request-URI usually contains the CDPN as provided by Gateway application.
|-
|valign=top nowrap=true|'''To Header when Sending INVITE'''
|Affects only outgoing diverted calls . '''Called Party''': If set we write CDPN into To header of outgoing INVITE (and DGPN into History-Info header). '''Original Called Party''': If set we write the DGPN into To header of outgoing INVITE (and CDPN into Request-URI).
|-
|valign=top nowrap=true|'''From Header when Sending INVITE'''
|Controls the local URI (From header) of outgoing calls. Applys to registered interfaces only. '''Fixed AOR''': Fixed AOR is used as From-URI regardless of the actual calling party number. '''AOR with CGPN as Display''': Fixed AOR is used as From-URI and calling party number is added as display string. '''CGPN in user part of URI''': Variable From-URI with actual calling party number.
|-
|valign=top nowrap=true|'''Identity Header when Sending INVITE'''
|Controls the identity header (P-Preferred-Identity, P-Asserted-Identity and Remote-Party-Id). '''CGPN in user part of URI''': Variable From-URI with actual calling party number. '''Fixed AOR''': Fixed AOR is used as Identity-URI regardless of the actual calling party number.
|-
|valign=top nowrap=true|'''Reliability of Provisional Responses'''
|Controls the support of PRACK (RFC-3262). '''Supported''': Supported as optional extension. '''Required''': Required as mandatory extension. '''Disabled''': Hide support for PRACK extension.
|-
|valign=top nowrap=true|'''Microsoft Presence Format'''
|Enables special Microsoft Presence format/scheme, only used for SIP Federation with Lync 2013.
|}

== CGPN/CDPN Mappings ==
A detailed description may be found in the chapter entitled "[[Reference:Administration/Gateway/Interfaces#CGPN.2FCDPN_Mappings|Administration/Gateway/Interface/CGPN-CDPN Mappings]]".

Howto:Innovaphones public services

2026-06-16T13:42:51Z

Slu: /* Services */

==Applies To==
This information applies to

* All versions

==Services==
Some services or products use a data connection to the vendor system. Innovaphone will provide his services from the following IP-networks:

46.232.228.0/26
213.144.10.192/29
141.95.57.16/28
185.145.188.12/32 # push NRW-RZ1
2a06:d840::12/128 # push NRW-RZ1

To configure your firewall accordingly, allow those entire networks as shown above. We suggest allowing traffic on the target DNS resolution eg. push.innovaphone.com.

=== STUN ===
[[Reference12r2:IP4/General/STUN|STUN Service]] for all customers
stun.innovaphone.com (udp/3478)

''Note: [http://wiki.innovaphone.com/index.php?title=Course13:IT_Advanced_2_-_07_Public_access_to_PBX_resources_%28practice%29#Media_data It is not a good idea to use innovaphone's STUN server. Although this server would yield the same results, there is no guarantee of availability. Your ISP or SIP provider's STUN should do better]''

=== TURN ===
[[Reference13r3:IP4/General/STUN#TURN Extern|TURN fallback service]] on port 443 for all customers
turn-fallback.innovaphone.com (tcp/443)

''Note: This TURN server shall only be used as 443 fallback server. It is not intended to be used as your [[Reference13r3:IP4/General/STUN#TURN Servers| regular TURN server]] as it is not designed as a primary TURN server. Do not use turn.innovaphone.com either.''

=== Provisioning ===
[[Reference13r1:Concept Provisioning|Provisioning System]] for all devices
config.innovaphone.com (tcp/http/https)

=== Push ===
[[Reference13r2:Concept Push Notifications for iOS and Android|Push]] for iOS, Android, Huawei and Browser Clients
push.innovaphone.com (tcp/https/wss)

=== Store ===
store.innovaphone.com (tcp/http/https)

=== Devices/Rental ===
my-app.innovaphone.com (tcp/https)

=== NTP ===
[[Reference13r1:Services/NTP|NTP Service]] for all customers
ntp.innovaphone.com (udp/123)

=== Remote Control Central ID service ===
[[Reference16r1:Concept App Remote Control#Central ID service server| Central ID service server]]
remotecontrol.innovaphone.com (tcp/https/wss)

=== Connector for Whatsapp ===
[[Reference16r1:Concept App Service Connector for Whatsapp| App Connector for Whatsapp]]
whatsapp.innovaphone.com (tcp/https/wss)

==Certificates==
innovaphone provides a public certificate download for used public keys.

* https://download.innovaphone.com/certificates/innovaphone.pem (the current innovaphone public key which will used for example for our push service)
* https://download.innovaphone.com/certificates/ca.pem (all innovaphone Device Certification Authority public keys)
* https://download.innovaphone.com/certificates/ca-unverified.pem (all innovaphone Unverified Device Certification Authority public keys)
** The Unverified CA is used for non hardware devices, e.g. IPVAs, which are not shipped with an official innovaphone Device Certification Authority certificate, as innovaphone has no control over the serial number here.

If needed, you can trust them manually or distribute them via [[Reference14r1:Concept App Service Devices#Certificates configuration|device's configuration]].

== Related Articles ==
* [[Reference13r2:Concept_Push_Notifications_for_iOS_and_Android]]
* [[Concept Status innovaphone Services]]
* [[Reference13r1:Concept_Provisioning]]
* [[Howto:Update_innovaphone.com_Wildcard-Certificate_in_a_Device_Trustlist]]

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

Howto:Innovaphones public services

2026-06-16T13:31:39Z

Slu: /* Services */

==Applies To==
This information applies to

* All versions

==Services==
Some services or products use a data connection to the vendor system. Innovaphone will provide his services from the following IP-networks:

46.232.228.0/26
213.144.10.192/29
141.95.57.16/28
45.133.189.205/32 # will be removed soon, push NRW-RZ1
2a0f:ff00:2001:366::21/128 # will be removed soon, push NRW-RZ1
185.145.188.12/32 # upcoming, push NRW-RZ1
2a06:d840::12/128 # upcoming, push NRW-RZ1

To configure your firewall accordingly, allow those entire networks as shown above. We suggest allowing traffic on the target DNS resolution eg. push.innovaphone.com.

=== STUN ===
[[Reference12r2:IP4/General/STUN|STUN Service]] for all customers
stun.innovaphone.com (udp/3478)

''Note: [http://wiki.innovaphone.com/index.php?title=Course13:IT_Advanced_2_-_07_Public_access_to_PBX_resources_%28practice%29#Media_data It is not a good idea to use innovaphone's STUN server. Although this server would yield the same results, there is no guarantee of availability. Your ISP or SIP provider's STUN should do better]''

=== TURN ===
[[Reference13r3:IP4/General/STUN#TURN Extern|TURN fallback service]] on port 443 for all customers
turn-fallback.innovaphone.com (tcp/443)

''Note: This TURN server shall only be used as 443 fallback server. It is not intended to be used as your [[Reference13r3:IP4/General/STUN#TURN Servers| regular TURN server]] as it is not designed as a primary TURN server. Do not use turn.innovaphone.com either.''

=== Provisioning ===
[[Reference13r1:Concept Provisioning|Provisioning System]] for all devices
config.innovaphone.com (tcp/http/https)

=== Push ===
[[Reference13r2:Concept Push Notifications for iOS and Android|Push]] for iOS, Android, Huawei and Browser Clients
push.innovaphone.com (tcp/https/wss)

=== Store ===
store.innovaphone.com (tcp/http/https)

=== Devices/Rental ===
my-app.innovaphone.com (tcp/https)

=== NTP ===
[[Reference13r1:Services/NTP|NTP Service]] for all customers
ntp.innovaphone.com (udp/123)

=== Remote Control Central ID service ===
[[Reference16r1:Concept App Remote Control#Central ID service server| Central ID service server]]
remotecontrol.innovaphone.com (tcp/https/wss)

=== Connector for Whatsapp ===
[[Reference16r1:Concept App Service Connector for Whatsapp| App Connector for Whatsapp]]
whatsapp.innovaphone.com (tcp/https/wss)

==Certificates==
innovaphone provides a public certificate download for used public keys.

* https://download.innovaphone.com/certificates/innovaphone.pem (the current innovaphone public key which will used for example for our push service)
* https://download.innovaphone.com/certificates/ca.pem (all innovaphone Device Certification Authority public keys)
* https://download.innovaphone.com/certificates/ca-unverified.pem (all innovaphone Unverified Device Certification Authority public keys)
** The Unverified CA is used for non hardware devices, e.g. IPVAs, which are not shipped with an official innovaphone Device Certification Authority certificate, as innovaphone has no control over the serial number here.

If needed, you can trust them manually or distribute them via [[Reference14r1:Concept App Service Devices#Certificates configuration|device's configuration]].

== Related Articles ==
* [[Reference13r2:Concept_Push_Notifications_for_iOS_and_Android]]
* [[Concept Status innovaphone Services]]
* [[Reference13r1:Concept_Provisioning]]
* [[Howto:Update_innovaphone.com_Wildcard-Certificate_in_a_Device_Trustlist]]

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

Howto:Innovaphones public services

2026-06-16T12:36:19Z

Slu: /* Services */

==Applies To==
This information applies to

* All versions

==Services==
Some services or products use a data connection to the vendor system. Innovaphone will provide his services from the following IP-networks:

46.232.228.0/26
213.144.10.192/29
141.95.57.16/28
45.133.189.205/32 # will be removed soon, push NRW-RZ1
2a0f:ff00:2001:366::21/128 # will be removed soon, push NRW-RZ1
185.145.188.12/32 # upcoming, push NRW-RZ1
2a06:d840::12/128 # upcoming, push NRW-RZ1

To configure your firewall accordingly, allow those entire networks as shown above.

=== STUN ===
[[Reference12r2:IP4/General/STUN|STUN Service]] for all customers
stun.innovaphone.com (udp/3478)

''Note: [http://wiki.innovaphone.com/index.php?title=Course13:IT_Advanced_2_-_07_Public_access_to_PBX_resources_%28practice%29#Media_data It is not a good idea to use innovaphone's STUN server. Although this server would yield the same results, there is no guarantee of availability. Your ISP or SIP provider's STUN should do better]''

=== TURN ===
[[Reference13r3:IP4/General/STUN#TURN_Extern |TURN fallback service ]] on port 443 for all customers
turn-fallback.innovaphone.com (tcp/443)

''Note: This TURN server shall only be used as 443 fallback server. It is not intended to be used as your [[Reference13r3:IP4/General/STUN#TURN_Servers | regular TURN server ]] as it is not designed as a primary TURN server. Do not use turn.innovaphone.com either.''

=== Provisioning ===
[[Reference13r1:Concept Provisioning|Provisioning System]] for all devices
config.innovaphone.com (tcp/http/https)

=== Push ===
[[Reference13r2:Concept_Push_Notifications_for_iOS_and_Android|Push]] for iOS, Android, Huawei and Browser Clients
push.innovaphone.com (tcp/https/wss)

=== Store ===
store.innovaphone.com (tcp/http/https)

=== Devices/Rental ===
my-app.innovaphone.com (tcp/https)

=== NTP ===
[[Reference13r1:Services/NTP|NTP Service]] for all customers
ntp.innovaphone.com (udp/123)

=== Remote Control Central ID service ===
[[Reference16r1:Concept_App_Remote_Control#Central_ID_service_server| Central ID service server]]
remotecontrol.innovaphone.com (tcp/https/wss)

=== Connector for Whatsapp ===
[[Reference16r1:Concept_App_Service_Connector_for_Whatsapp| App Connector for Whatsapp]]
whatsapp.innovaphone.com (tcp/https/wss)

==Certificates==
innovaphone provides a public certificate download for used public keys.

* https://download.innovaphone.com/certificates/innovaphone.pem (the current innovaphone public key which will used for example for our push service)
* https://download.innovaphone.com/certificates/ca.pem (all innovaphone Device Certification Authority public keys)
* https://download.innovaphone.com/certificates/ca-unverified.pem (all innovaphone Unverified Device Certification Authority public keys)
** The Unverified CA is used for non hardware devices, e.g. IPVAs, which are not shipped with an official innovaphone Device Certification Authority certificate, as innovaphone has no control over the serial number here.

If needed, you can trust them manually or distribute them via [[Reference14r1:Concept_App_Service_Devices#Certificates_configuration|device's configuration]].

== Related Articles ==
* [[Reference13r2:Concept_Push_Notifications_for_iOS_and_Android]]
* [[Concept Status innovaphone Services]]
* [[Reference13r1:Concept_Provisioning]]
* [[Howto:Update_innovaphone.com_Wildcard-Certificate_in_a_Device_Trustlist]]

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

Reference16r1:Apps/PbxManager/App Translations

2026-06-15T12:24:28Z

Slu:

With the translations PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Add an app object ==

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

;Config Templates
:Enabled config templates where the App should be available.
:If config templates exist, they will be listed with a checkbox.
:The app object will be assigned to the config templates if a checkbox is checked. 
:'''Be Aware:''' Every user who should be able to use the translation service needs to have it assigned (by using a config template, for example).

=== Translations Service ===
Select the active translation backend.

=== DeepL ===
Specific https://www.deepl.com configuration

;URL
:The URL API Endpoint for the translation backend.
: If the field is empty, which is the default, the API endpoint will be selected automatically depending on the type of the key. If key ends with ":fx" the URL <code>https://api-free.deepl.com</code> is used, otherwise <code>https://api.deepl.com</code>

;API-Key
:The secret ''api-key''

=== eTranslation ===
Specific https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en configuration

;Application Name
:The secret ''Application Name''

;Password
:The secret ''Password''

=== Custom LLM ===
Connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, LM Studio, or a self-hosted model and interact with the endpoint <code>POST /v1/chat/completions</code>.

;Hostname
:The base URL of the server. The protocol prefix <code>https://</code> is assumed if omitted.
:Example: <code>https://ollama.example.com</code> or <code>ollama.example.com</code>
:Once a hostname is entered, the plugin automatically queries <code>{hostname}/v1/models</code> and populates the ''Model'' dropdown.

;Token
:Optional Bearer token sent as <code>Authorization: Bearer {token}</code> with every request to the inference server, including the model list query. Leave empty if the server does not require authentication.

;System Prompt
:The system prompt sent to the model with every translation request. Use <code>{LANG}</code> as a placeholder - it is replaced at runtime with the ISO target language code (e.g. <code>DE</code>, <code>EN-GB</code>).
:If left empty, the following default prompt is used:
You are a translation engine. Translate the user input into {LANG}.
Strictly follow all output rules:
- Return ONLY the translated content. No preamble, no explanations, no surrounding text of any kind.
- If the input contains HTML: preserve all tags, attributes, and structure unchanged; translate text nodes only.
- Never translate attribute values (href, src, class, id, style, data-*, etc.).
- Preserve proper nouns, brand names, and technical identifiers exactly as-is.
- Preserve whitespace, line breaks, and formatting exactly.
- Maintain the original tone and register (formal/informal).
- If the input is already in {LANG}, return it unchanged.

;Model
:Dropdown populated automatically from the models available on the configured host. Select the model to be used for translation requests.

;Temperature
:Define the parameter "temperature" in the LLM request. (Default 0.3)

;Max. Tokens
:Define the parameter "max_tokens" in the LLM request. (Default 65536)

;Enable Thinking
:Define the parameter "chat_template_kwargs.enable_thinking" in the LLM request. (Default false)

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Translations]]

[[Category:Concept App Service Translations]]

Reference16r1:Concept App Service Translations

2026-06-15T12:23:47Z

Slu:

[[Category:Concept|Apps]]
[[Category:Concept App Service Translations]]
== Overview ==
The idea of the translations app is to provide an interface for other apps to translate user content on-the-fly. So other apps can integrate the translation service via the [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm local JavaScript API] in the client and thus offer the user translated texts.

The service serves as a proxy and integrates a corresponding backend. For cloud services (DeepL, eTranslation) you need your own account and credentials. For Custom LLM, a self-hosted OpenAI API-compatible inference server is used instead.

== Supported translation services ==
You can configure multiple translation backends and switch between them.

=== DeepL ===
This interface uses the https:///www.deepl.com translation API.

This interface is used as the default interface. you dont must provide an ''API-URL'' in the [[Reference16r1:Apps/PbxManager/App Translations|Settings]]. A custom API-URL is only for a local version with the same API interface.

;Privacy
:API Free: https://www.deepl.com/de/privacy#section_12
:API Pro: https://www.deepl.com/de/privacy#section_5
;Cost model and Pricing
:Pay per character (To save costs, the app service offers a cache to avoid multiple translations)
:https://www.deepl.com/de/pro#developer

==== Technical Concept ====

* The DeepL API is a synchronous HTTP flow. This means that we request a translation and get an instant response with the translation.
* Outgoing HTTP(S) request to the DeepL API
* If you not override the URL, it is used HTTPS only

=== EU - eTranslation ===
This interface uses the EU service eTranslation.

European Commission’s free and secure AI language tools: https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en

Technical Documentation: https://language-tools.ec.europa.eu/dev-corner/etranslation/rest-v2/text

==== Technical Concept ====
* The EU-eTranslation uses an asynchronous HTTP flow with webhooks to deliver processed translations
* Translation flow
*# On every app startup
*## a dynamic user / password combination is created, which will be used for later secure incoming webhooks
*### Example: <code>23bcf2fd / 19ccf70b-028c-e7a8-94eb-1ad7db91d4c8</code>
*## the own app url is generated from the current environment
*### Example: <code><nowiki>https://23bcf2fd:19ccf70b-028c-e7a8-94eb-1ad7db91d4c8@apps.slu.de/slu.de/translations/webhook-basicauth</nowiki></code>
*# Outgoing HTTPS request to the eTranslation Service. The translation job will be queued. As additional information in the job, a callback webhook URL with a username and password will be placed.
*# If the processing is finished, a webhook to the app is delivered via HTTPS
*# The job result will be processed and delivered back to the user that has requested the translation
==== Limitations ====
* 50 concurrent translation requests
* 5.000 characters per translation

=== Custom LLM ===
This interface connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, or LM Studio.

;Privacy
:Depends on the operator of the server. No data is sent to third parties.
;Cost model
:Depends on the operator of the inference server.

==== Technical Concept ====
* Synchronous HTTP flow - a translation request is sent and the response is returned immediately
* Outgoing HTTPS request to the configured server
* The available models are queried via <code>GET /v1/models</code> in the [[Reference17:Apps/PbxManager/App Translations|settings plugin]]
* Optional performance options, authentication options, and the system prompt can be configured in the [[Reference17:Apps/PbxManager/App Translations|settings plugin]]
* Translation requests are sent as <code>POST /v1/chat/completions</code>
* The system prompt uses <code>{LANG}</code> as a placeholder for the ISO target language code

== Licensing ==
No license needed

== Installation ==
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown.
* In the search field located on the top right corner of the store, search for '''"Translations"''' and click on it
* Select the proper firmware version and click on install
* Close and open the PBX manager to refresh the list of the available colored AP plugin
* Click on the '''"AP Translations"''' and click on '''" + Add an App"'''
* Enter a '''"Name"''' that is used as the display name ''(all characters allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Translations, SIP: translations''
* Tick the appropriate template to distribute the App (the app is needed at every user object from any user who wants to use the translation API)
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

== Translation - Client ==
There is no view/app that the user can explicitly open. The service runs in the background and has no UI and can be integrated by other apps. In order for the user to have access to the translation service, their user object must have access to the app object of the translations app.

The client side of the app service receives requests from all other apps via the local JavaScript API and sends them to the service. The result of the request is returned to the original app via the local JavaScript API

== Translation - App Service ==
The App Service performs tasks in the following areas:
* Language recognition
* Caching
* Translations against the backend (deepl.com)

=== Language recognition ===
An offline API is offered to recognize the language used in a string. This recognition is also used for translations to avoid unnecessary translations (e.g. EN to EN translations are prevented). This payload will not be sent to any backend service, thus avoiding unnecessary costs. A few features exist which should make sure, a recognized language is only considered, if there is enough confidence:
* Strings shorter than 6 words are skipped, since the chance for false positives are relatively high
* Strings in which there are not enough word matches to be confident for any language will be skipped, also because of high chances for false positives
* Strings that are more than one language with a nearly similar amount of word matches will be skipped

Supported languages: cs, de, en-gb, es, fr, it, nl, pl, pt-pt, ro, ru, sl, tr

=== Caching ===
To save costs, all translations are cached in the App Services database. If a string is translated multiple times, only the first translation is carried out by the backend, and the translated version is saved in the cache. A second translation is therefore free of charge and performs better.

=== Translations against the backend ===
Translation requests that cannot be handled by the local cache are forwarded to the configured translation backend. After successful translation, the translated version is kept in the cache for future requests.

The list of supported languages depends on the supported languages of the used [https://developers.deepl.com/docs/resources/supported-languages#target-languages service provider]. It will be read from the service provider each time the Translations App Service starts.

=== Charts Statistics ===
The app service will provide telemetry data to the integrated Charts app service.

;requestTranslate
:Translation requests (default) to the App Service
;requestTranslateAll
:TranslationAll requests to the App Service
;requestWebhookBasic
:Webhooks from external translations backend with legacy BasicAuth to the App Service
;requestWebhook
:Webhooks from external translations backend to the App Service
;DetectLanguagePreventTranslation
:Amount of translation requests that are not processed because language detection detected same languages
;CacheAdd
:New translation payload is stored in the cache
;CacheHit
:Translation request is solved by existing cache entry
;DeepL
:External backend request
;eTranslation
:External backend request

== Troubleshooting ==

To troubleshoot this App Service, you need the traceflags ''App'', ''Database'', ''HTTP-Client'' in your App instance.

== Related Articles ==
* [https://sdk.innovaphone.com/15r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm SDK Documentation - Translation API]
* [[{{NAMESPACE}}:Apps/PbxManager/App_Translations]]

Reference17:Apps/PbxManager/App Translations

2026-06-09T08:08:52Z

Slu: /* Custom LLM */

Reference17:Concept App Service Translations

2026-06-09T07:57:45Z

Slu: /* Technical Concept */

Reference17:Apps/PbxManager/App Translations

2026-06-02T11:48:47Z

Slu: /* Custom LLM */

With the translations PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Add an app object ==

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

;Config Templates
:Enabled config templates where the App should be available.
:If config templates exist, they will be listed with a checkbox.
:The app object will be assigned to the config templates if a checkbox is checked. 
:'''Be Aware:''' Every user who should be able to use the translation service needs to have it assigned (by using a config template, for example).

=== Translations Service ===
Select the active translation backend.

=== DeepL ===
Specific https://www.deepl.com configuration

;URL
:The URL API Endpoint for the translation backend.
: If the field is empty, which is the default, the API endpoint will be selected automatically depending on the type of the key. If key ends with ":fx" the URL <code>https://api-free.deepl.com</code> is used, otherwise <code>https://api.deepl.com</code>

;API-Key
:The secret ''api-key''

=== eTranslation ===
Specific https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en configuration

;Application Name
:The secret ''Application Name''

;Password
:The secret ''Password''

=== Custom LLM ===
Connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, LM Studio, or a self-hosted model and interact with the endpoint <code>POST /v1/chat/completions</code>.

;Hostname
:The base URL of the server. The protocol prefix <code>https://</code> is assumed if omitted.
:Example: <code>https://ollama.example.com</code> or <code>ollama.example.com</code>
:Once a hostname is entered, the plugin automatically queries <code>{hostname}/v1/models</code> and populates the ''Model'' dropdown.

;Token
:Optional Bearer token sent as <code>Authorization: Bearer {token}</code> with every request to the inference server, including the model list query. Leave empty if the server does not require authentication.

;System Prompt
:The system prompt sent to the model with every translation request. Use <code>{LANG}</code> as a placeholder - it is replaced at runtime with the ISO target language code (e.g. <code>DE</code>, <code>EN-GB</code>).
:If left empty, the following default prompt is used:
You are a translation engine. Translate the user input into {LANG}.
Strictly follow all output rules:
- Return ONLY the translated content. No preamble, no explanations, no surrounding text of any kind.
- If the input contains HTML: preserve all tags, attributes, and structure unchanged; translate text nodes only.
- Never translate attribute values (href, src, class, id, style, data-*, etc.).
- Preserve proper nouns, brand names, and technical identifiers exactly as-is.
- Preserve whitespace, line breaks, and formatting exactly.
- Maintain the original tone and register (formal/informal).
- If the input is already in {LANG}, return it unchanged.

;Model
:Dropdown populated automatically from the models available on the configured host. Select the model to be used for translation requests.

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Translations]]

[[Category:Concept App Service Translations]]

Reference17:Concept App Service Translations

2026-06-02T10:23:12Z

Slu: /* EU - eTranslation */

[[Category:Concept|Apps]]
[[Category:Concept App Service Translations]]
== Overview ==
The idea of the translations app is to provide an interface for other apps to translate user content on-the-fly. So other apps can integrate the translation service via the [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm local JavaScript API] in the client and thus offer the user translated texts.

The service serves as a proxy and integrates a corresponding backend. For cloud services (DeepL, eTranslation) you need your own account and credentials. For Custom LLM, a self-hosted OpenAI API-compatible inference server is used instead.

== Supported translation services ==
You can configure multiple translation backends and switch between them.

=== DeepL ===
This interface uses the https:///www.deepl.com translation API.

This interface is used as the default interface. you dont must provide an ''API-URL'' in the [[Reference16r1:Apps/PbxManager/App Translations|Settings]]. A custom API-URL is only for a local version with the same API interface.

;Privacy
:API Free: https://www.deepl.com/de/privacy#section_12
:API Pro: https://www.deepl.com/de/privacy#section_5
;Cost model and Pricing
:Pay per character (To save costs, the app service offers a cache to avoid multiple translations)
:https://www.deepl.com/de/pro#developer

==== Technical Concept ====

* The DeepL API is a synchronous HTTP flow. This means that we request a translation and get an instant response with the translation.
* Outgoing HTTP(S) request to the DeepL API
* If you not override the URL, it is used HTTPS only

=== EU - eTranslation ===
This interface uses the EU service eTranslation.

European Commission’s free and secure AI language tools: https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en

Technical Documentation: https://language-tools.ec.europa.eu/dev-corner/etranslation/rest-v2/text

==== Technical Concept ====
* The EU-eTranslation uses an asynchronous HTTP flow with webhooks to deliver processed translations
* Translation flow
*# On every app startup
*## a dynamic user / password combination is created, which will be used for later secure incoming webhooks
*### Example: <code>23bcf2fd / 19ccf70b-028c-e7a8-94eb-1ad7db91d4c8</code>
*## the own app url is generated from the current environment
*### Example: <code><nowiki>https://23bcf2fd:19ccf70b-028c-e7a8-94eb-1ad7db91d4c8@apps.slu.de/slu.de/translations/webhook-basicauth</nowiki></code>
*# Outgoing HTTPS request to the eTranslation Service. The translation job will be queued. As additional information in the job, a callback webhook URL with a username and password will be placed.
*# If the processing is finished, a webhook to the app is delivered via HTTPS
*# The job result will be processed and delivered back to the user that has requested the translation
==== Limitations ====
* 50 concurrent translation requests
* 5.000 characters per translation

=== Custom LLM ===
This interface connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, or LM Studio.

;Privacy
:Depends on the operator of the server. No data is sent to third parties.
;Cost model
:Depends on the operator of the inference server.

==== Technical Concept ====
* Synchronous HTTP flow - a translation request is sent and the response is returned immediately
* Outgoing HTTPS request to the configured server
* The available models are queried via <code>GET /v1/models</code> in the settings plugin
* Translation requests are sent as <code>POST /v1/chat/completions</code> with an editable system prompt
* The system prompt uses <code>{LANG}</code> as a placeholder for the ISO target language code
* An optional Bearer token can be configured for servers that require authentication

== Licensing ==
No license needed

== Installation ==
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown.
* In the search field located on the top right corner of the store, search for '''"Translations"''' and click on it
* Select the proper firmware version and click on install
* Close and open the PBX manager to refresh the list of the available colored AP plugin
* Click on the '''"AP Translations"''' and click on '''" + Add an App"'''
* Enter a '''"Name"''' that is used as the display name ''(all characters allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Translations, SIP: translations''
* Tick the appropriate template to distribute the App (the app is needed at every user object from any user who wants to use the translation API)
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

== Translation - Client ==
There is no view/app that the user can explicitly open. The service runs in the background and has no UI and can be integrated by other apps. In order for the user to have access to the translation service, their user object must have access to the app object of the translations app.

The client side of the app service receives requests from all other apps via the local JavaScript API and sends them to the service. The result of the request is returned to the original app via the local JavaScript API

== Translation - App Service ==
The App Service performs tasks in the following areas:
* Language recognition
* Caching
* Translations against the backend (deepl.com)

=== Language recognition ===
An offline API is offered to recognize the language used in a string. This recognition is also used for translations to avoid unnecessary translations (e.g. EN to EN translations are prevented). This payload will not be sent to any backend service, thus avoiding unnecessary costs. A few features exist which should make sure, a recognized language is only considered, if there is enough confidence:
* Strings shorter than 6 words are skipped, since the chance for false positives are relatively high
* Strings in which there are not enough word matches to be confident for any language will be skipped, also because of high chances for false positives
* Strings that are more than one language with a nearly similar amount of word matches will be skipped

Supported languages: cs, de, en-gb, es, fr, it, nl, pl, pt-pt, ro, ru, sl, tr

=== Caching ===
To save costs, all translations are cached in the App Services database. If a string is translated multiple times, only the first translation is carried out by the backend, and the translated version is saved in the cache. A second translation is therefore free of charge and performs better.

=== Translations against the backend ===
Translation requests that cannot be handled by the local cache are forwarded to the configured translation backend. After successful translation, the translated version is kept in the cache for future requests.

The list of supported languages depends on the supported languages of the used [https://developers.deepl.com/docs/resources/supported-languages#target-languages service provider]. It will be read from the service provider each time the Translations App Service starts.

=== Charts Statistics ===
The app service will provide telemetry data to the integrated Charts app service.

;requestTranslate
:Translation requests (default) to the App Service
;requestTranslateAll
:TranslationAll requests to the App Service
;requestWebhookBasic
:Webhooks from external translations backend with legacy BasicAuth to the App Service
;requestWebhook
:Webhooks from external translations backend to the App Service
;DetectLanguagePreventTranslation
:Amount of translation requests that are not processed because language detection detected same languages
;CacheAdd
:New translation payload is stored in the cache
;CacheHit
:Translation request is solved by existing cache entry
;DeepL
:External backend request
;eTranslation
:External backend request

== Troubleshooting ==

To troubleshoot this App Service, you need the traceflags ''App'', ''Database'', ''HTTP-Client'' in your App instance.

== Related Articles ==
* [https://sdk.innovaphone.com/15r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm SDK Documentation - Translation API]
* [[{{NAMESPACE}}:Apps/PbxManager/App_Translations]]

Reference17:Concept App Service Translations

2026-06-02T10:11:41Z

Slu: /* Overview */

[[Category:Concept|Apps]]
[[Category:Concept App Service Translations]]
== Overview ==
The idea of the translations app is to provide an interface for other apps to translate user content on-the-fly. So other apps can integrate the translation service via the [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm local JavaScript API] in the client and thus offer the user translated texts.

The service serves as a proxy and integrates a corresponding backend. For cloud services (DeepL, eTranslation) you need your own account and credentials. For Custom LLM, a self-hosted OpenAI API-compatible inference server is used instead.

== Supported translation services ==
You can configure multiple translation backends and switch between them.

=== DeepL ===
This interface uses the https:///www.deepl.com translation API.

This interface is used as the default interface. you dont must provide an ''API-URL'' in the [[Reference16r1:Apps/PbxManager/App Translations|Settings]]. A custom API-URL is only for a local version with the same API interface.

;Privacy
:API Free: https://www.deepl.com/de/privacy#section_12
:API Pro: https://www.deepl.com/de/privacy#section_5
;Cost model and Pricing
:Pay per character (To save costs, the app service offers a cache to avoid multiple translations)
:https://www.deepl.com/de/pro#developer

==== Technical Concept ====

* The DeepL API is a synchronous HTTP flow. This means that we request a translation and get an instant response with the translation.
* Outgoing HTTP(S) request to the DeepL API
* If you not override the URL, it is used HTTPS only

=== EU - eTranslation ===
This interface uses the EU service eTranslation.

European Commission’s free and secure AI language tools: https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en

Technical Documentation: https://language-tools.ec.europa.eu/dev-corner/etranslation/rest-v2/text

==== Technical Concept ====
* The EU-eTranslation uses an asynchronous HTTP flow with webhooks to deliver processed translations
* Translation flow
*# On every app startup
*## a dynamic user / password combination is created, which will be used for later secure incoming webhooks
*### Example: <code>23bcf2fd / 19ccf70b-028c-e7a8-94eb-1ad7db91d4c8</code>
*## the own app url is generated from the current environment
*### Example: <code><nowiki>https://23bcf2fd:19ccf70b-028c-e7a8-94eb-1ad7db91d4c8@apps.slu.de/slu.de/translations/webhook-basicauth</nowiki></code>
*# Outgoing HTTPS request to the eTranslation Service. The translation job will be queued. As additional information in the job, a callback webhook URL with a username and password will be placed.
*# If the processing is finished, a webhook to the app is delivered via HTTPS
*# The job result will be processed and delivered back to the user that has requested the translation
==== Limitations ====
* 50 concurrent translation requests
* 5.000 characters per translation

== Licensing ==
No license needed

== Installation ==
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown.
* In the search field located on the top right corner of the store, search for '''"Translations"''' and click on it
* Select the proper firmware version and click on install
* Close and open the PBX manager to refresh the list of the available colored AP plugin
* Click on the '''"AP Translations"''' and click on '''" + Add an App"'''
* Enter a '''"Name"''' that is used as the display name ''(all characters allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Translations, SIP: translations''
* Tick the appropriate template to distribute the App (the app is needed at every user object from any user who wants to use the translation API)
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

== Translation - Client ==
There is no view/app that the user can explicitly open. The service runs in the background and has no UI and can be integrated by other apps. In order for the user to have access to the translation service, their user object must have access to the app object of the translations app.

The client side of the app service receives requests from all other apps via the local JavaScript API and sends them to the service. The result of the request is returned to the original app via the local JavaScript API

== Translation - App Service ==
The App Service performs tasks in the following areas:
* Language recognition
* Caching
* Translations against the backend (deepl.com)

=== Language recognition ===
An offline API is offered to recognize the language used in a string. This recognition is also used for translations to avoid unnecessary translations (e.g. EN to EN translations are prevented). This payload will not be sent to any backend service, thus avoiding unnecessary costs. A few features exist which should make sure, a recognized language is only considered, if there is enough confidence:
* Strings shorter than 6 words are skipped, since the chance for false positives are relatively high
* Strings in which there are not enough word matches to be confident for any language will be skipped, also because of high chances for false positives
* Strings that are more than one language with a nearly similar amount of word matches will be skipped

Supported languages: cs, de, en-gb, es, fr, it, nl, pl, pt-pt, ro, ru, sl, tr

=== Caching ===
To save costs, all translations are cached in the App Services database. If a string is translated multiple times, only the first translation is carried out by the backend, and the translated version is saved in the cache. A second translation is therefore free of charge and performs better.

=== Translations against the backend ===
Translation requests that cannot be handled by the local cache are forwarded to the configured translation backend. After successful translation, the translated version is kept in the cache for future requests.

The list of supported languages depends on the supported languages of the used [https://developers.deepl.com/docs/resources/supported-languages#target-languages service provider]. It will be read from the service provider each time the Translations App Service starts.

=== Charts Statistics ===
The app service will provide telemetry data to the integrated Charts app service.

;requestTranslate
:Translation requests (default) to the App Service
;requestTranslateAll
:TranslationAll requests to the App Service
;requestWebhookBasic
:Webhooks from external translations backend with legacy BasicAuth to the App Service
;requestWebhook
:Webhooks from external translations backend to the App Service
;DetectLanguagePreventTranslation
:Amount of translation requests that are not processed because language detection detected same languages
;CacheAdd
:New translation payload is stored in the cache
;CacheHit
:Translation request is solved by existing cache entry
;DeepL
:External backend request
;eTranslation
:External backend request

== Troubleshooting ==

To troubleshoot this App Service, you need the traceflags ''App'', ''Database'', ''HTTP-Client'' in your App instance.

== Related Articles ==
* [https://sdk.innovaphone.com/15r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm SDK Documentation - Translation API]
* [[{{NAMESPACE}}:Apps/PbxManager/App_Translations]]

Reference17:Apps/PbxManager/App Translations

2026-06-02T10:09:05Z

Slu: /* DeepL */

With the translations PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Add an app object ==

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

;Config Templates
:Enabled config templates where the App should be available.
:If config templates exist, they will be listed with a checkbox.
:The app object will be assigned to the config templates if a checkbox is checked. 
:'''Be Aware:''' Every user who should be able to use the translation service needs to have it assigned (by using a config template, for example).

=== Translations Service ===
Select the active translation backend.

=== DeepL ===
Specific https://www.deepl.com configuration

;URL
:The URL API Endpoint for the translation backend.
: If the field is empty, which is the default, the API endpoint will be selected automatically depending on the type of the key. If key ends with ":fx" the URL <code>https://api-free.deepl.com</code> is used, otherwise <code>https://api.deepl.com</code>

;API-Key
:The secret ''api-key''

=== eTranslation ===
Specific https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en configuration

;Application Name
:The secret ''Application Name''

;Password
:The secret ''Password''

=== Custom LLM ===
Connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, LM Studio, or a self-hosted model and interact with the endpoint <code>POST /v1/chat/completions</code>.

;Hostname
:The base URL of the server. The protocol prefix <code>https://</code> is assumed if omitted.
:Example: <code>https://ollama.example.com</code> or <code>ollama.example.com</code>
:Once a hostname is entered, the plugin automatically queries <code>{hostname}/v1/models</code> and populates the ''Model'' dropdown.

;Token
:Optional Bearer token sent as <code>Authorization: Bearer {token}</code> with every request to the inference server, including the model list query. Leave empty if the server does not require authentication.

;System Prompt
:The system prompt sent to the model with every translation request. Use <code>{LANG}</code> as a placeholder - it is replaced at runtime with the ISO target language code (e.g. <code>DE</code>, <code>EN-GB</code>).
:If left empty, the following default prompt is used: <code>You are a translation assistant. Translate the following text to {LANG}. Return only the translated text, with no explanations or additional content.</code>

;Model
:Dropdown populated automatically from the models available on the configured host. Select the model to be used for translation requests.

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Translations]]

[[Category:Concept App Service Translations]]

Reference17:Apps/PbxManager/App Translations

2026-06-02T09:50:50Z

Slu: /* Custom LLM */

With the translations PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Add an app object ==

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

;Config Templates
:Enabled config templates where the App should be available.
:If config templates exist, they will be listed with a checkbox.
:The app object will be assigned to the config templates if a checkbox is checked. 
:'''Be Aware:''' Every user who should be able to use the translation service needs to have it assigned (by using a config template, for example).

=== Translations Service ===
Select the active translation backend.

=== DeepL ===
Specific https://www.deepl.com configuration

;URL
:The URL API Endpoint for the translation backend.
: If the field is empty, which is the default, the API endpoint will be selected automatically depending on the type of the key. If key ends with ":fx" the URL <code>https://api-free.deepl.com</code> is used, otherwhise <code>https://api.deepl.com</code>

;API-Key
:The secret ''api-key''

=== eTranslation ===
Specific https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en configuration

;Application Name
:The secret ''Application Name''

;Password
:The secret ''Password''

=== Custom LLM ===
Connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, LM Studio, or a self-hosted model and interact with the endpoint <code>POST /v1/chat/completions</code>.

;Hostname
:The base URL of the server. The protocol prefix <code>https://</code> is assumed if omitted.
:Example: <code>https://ollama.example.com</code> or <code>ollama.example.com</code>
:Once a hostname is entered, the plugin automatically queries <code>{hostname}/v1/models</code> and populates the ''Model'' dropdown.

;Token
:Optional Bearer token sent as <code>Authorization: Bearer {token}</code> with every request to the inference server, including the model list query. Leave empty if the server does not require authentication.

;System Prompt
:The system prompt sent to the model with every translation request. Use <code>{LANG}</code> as a placeholder - it is replaced at runtime with the ISO target language code (e.g. <code>DE</code>, <code>EN-GB</code>).
:If left empty, the following default prompt is used: <code>You are a translation assistant. Translate the following text to {LANG}. Return only the translated text, with no explanations or additional content.</code>

;Model
:Dropdown populated automatically from the models available on the configured host. Select the model to be used for translation requests.

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Translations]]

[[Category:Concept App Service Translations]]

Reference17:Apps/PbxManager/App Translations

2026-06-02T09:49:13Z

Slu: /* Translations Service */

With the translations PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Add an app object ==

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

;Config Templates
:Enabled config templates where the App should be available.
:If config templates exist, they will be listed with a checkbox.
:The app object will be assigned to the config templates if a checkbox is checked. 
:'''Be Aware:''' Every user who should be able to use the translation service needs to have it assigned (by using a config template, for example).

=== Translations Service ===
Select the active translation backend.

=== DeepL ===
Specific https://www.deepl.com configuration

;URL
:The URL API Endpoint for the translation backend.
: If the field is empty, which is the default, the API endpoint will be selected automatically depending on the type of the key. If key ends with ":fx" the URL <code>https://api-free.deepl.com</code> is used, otherwhise <code>https://api.deepl.com</code>

;API-Key
:The secret ''api-key''

=== eTranslation ===
Specific https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en configuration

;Application Name
:The secret ''Application Name''

;Password
:The secret ''Password''

=== Custom LLM ===
Connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, LM Studio, or a self-hosted model.

;Hostname
:The base URL of the server. The protocol prefix <code>https://</code> is assumed if omitted.
:Example: <code>https://ollama.example.com</code> or <code>ollama.example.com</code>
:Once a hostname is entered, the plugin automatically queries <code>{hostname}/v1/models</code> and populates the ''Model'' dropdown.

;Token
:Optional Bearer token sent as <code>Authorization: Bearer {token}</code> with every request to the inference server, including the model list query. Leave empty if the server does not require authentication.

;System Prompt
:The system prompt sent to the model with every translation request. Use <code>{LANG}</code> as a placeholder - it is replaced at runtime with the ISO target language code (e.g. <code>DE</code>, <code>EN-GB</code>).
:If left empty, the following default prompt is used: <code>You are a translation assistant. Translate the following text to {LANG}. Return only the translated text, with no explanations or additional content.</code>

;Model
:Dropdown populated automatically from the models available on the configured host. Select the model to be used for translation requests.

:'''Note:''' Translation requests are sent as <code>POST /v1/chat/completions</code> to the configured host. The model receives a system prompt instructing it to translate the input text to the target language and return only the translated result.

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Translations]]

[[Category:Concept App Service Translations]]

Reference17:Apps/PbxManager/App Translations

2026-06-02T09:44:46Z

Slu: /* Custom LLM */

With the translations PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Add an app object ==

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

;Config Templates
:Enabled config templates where the App should be available.
:If config templates exist, they will be listed with a checkbox.
:The app object will be assigned to the config templates if a checkbox is checked. 
:'''Be Aware:''' Every user who should be able to use the translation service needs to have it assigned (by using a config template, for example).

=== Translations Service ===
You have to configure the current active translations service.

=== DeepL ===
Specific https://www.deepl.com configuration

;URL
:The URL API Endpoint for the translation backend.
: If the field is empty, which is the default, the API endpoint will be selected automatically depending on the type of the key. If key ends with ":fx" the URL <code>https://api-free.deepl.com</code> is used, otherwhise <code>https://api.deepl.com</code>

;API-Key
:The secret ''api-key''

=== eTranslation ===
Specific https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en configuration

;Application Name
:The secret ''Application Name''

;Password
:The secret ''Password''

=== Custom LLM ===
Connects to any OpenAI API-compatible server, such as [https://ollama.com Ollama], vLLM, LM Studio, or a self-hosted model.

;Hostname
:The base URL of the server. The protocol prefix <code>https://</code> is assumed if omitted.
:Example: <code>https://ollama.example.com</code> or <code>ollama.example.com</code>
:Once a hostname is entered, the plugin automatically queries <code>{hostname}/v1/models</code> and populates the ''Model'' dropdown.

;Token
:Optional Bearer token sent as <code>Authorization: Bearer {token}</code> with every request to the inference server, including the model list query. Leave empty if the server does not require authentication.

;System Prompt
:The system prompt sent to the model with every translation request. Use <code>{LANG}</code> as a placeholder - it is replaced at runtime with the ISO target language code (e.g. <code>DE</code>, <code>EN-GB</code>).
:If left empty, the following default prompt is used: <code>You are a translation assistant. Translate the following text to {LANG}. Return only the translated text, with no explanations or additional content.</code>

;Model
:Dropdown populated automatically from the models available on the configured host. Select the model to be used for translation requests.

:'''Note:''' Translation requests are sent as <code>POST /v1/chat/completions</code> to the configured host. The model receives a system prompt instructing it to translate the input text to the target language and return only the translated result.

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Translations]]

[[Category:Concept App Service Translations]]

Reference17:Apps/PbxManager/App Translations

2026-06-02T09:21:13Z

Slu: /* eTranslation */

Reference17:Apps/PbxManager/App Translations

2026-06-02T09:11:16Z

Slu: /* European eTranslation */

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-05-28T13:51:06Z

Slu: /* Changes visible to the end customers */

== Applies To ==
This information applies to:

* All 16r1 capable innovaphone devices
: For a general overview of the upgrade process and a list of supported devices with 16r1, see [[Howto:Firmware Upgrade]]
== Licenses ==
In case of cloud or rental model, don't worry about licenses.

If the system is licensed on premise, you'll need to regenerate the license file for v16 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location

=== AP Upgrade to Image 140037 or newer ===
* First, upgrade your application platform to at least image version 140037. After that you can go ahead.

=== Upgrade Sequence ===
In systems of multiple units, it is important to update the tree from top to bottom. In other words, update the master unit first, and then the machines at the lower levels. If you're using a DevicesApp update job that updates the entire system at once, you don't need to do anything here.

=== TechAssist Upgrade Helper ===
* Before you start, make sure that all TechAssist tests (you will receive the required tests in the last update in the previous major version) labelled <code>Pre Upgrade: xy</code> are positive, if available
* When you are finished, make sure that all TechAssist tests (you will receive new tests with the upgrade) are positive

== Changes visible to the end customers ==
Listed here are changes that should be communicated by resellers to end users prior to a upgrade, as the change will be visible/audible in the behaviour of the application/device.

* 16r1 introduces the feature of [[Reference16r1:Concept_Reconnect_Calls | Reconnect Calls for Seamless Handover & Roaming]]. As a result, calls will not be dropped on network interruptions or PBX reboots. Instead users receive visual (MyApps or phone display) and audio (in-band tone) feedback and the call is reconnected automatically.
* Chat App: The option for users to choose whether to send a chat message using ENTER or SHIFT+ENTER has been removed. Messages can now only be sent using CTRL+ENTER without pressing the send button.

== Manual steps needed after upgrade ==
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.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Projects ===
* Projects requires '''App platform version 140029''' or higher, so updating the App Platform before Projects is recommended. The Store will prohibit the update if the App Plattform does not have the minimum required version.
* For some extra admin-functionalities the '''Projects App Object needs to have an admin mode''' (App-tab). Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.
* The '''App Platform requires the correct Time and a Timezone''' set under AP Manager/Settings/General. This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).

=== For legacy support only: Change TLS Profile ===
The ''Normal'' profile has been updated to allow only TLS 1.3 and TLS 1.2. This setting is compatible with all supported firmware versions. So you don't need to do any changes.
However if you need older TLS versions for compatibility with legacy devices, consider changing the TLS profile to ''Legacy''. In that case please see [[Reference16r1:IP4/General/TLS]] for details.

== New Apps ==
New Apps will not be installed automatically by the upgrade. The installation description of new apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.

; App Charts: [[Reference16r1:Concept_App_Charts]]
; App Polls: [[Reference16r1:Concept App Polls]]
; App MQTT Broker: [[Reference16r1:Concept_App_MQTT_Broker]]
; App Service Conference Scaler: [[Reference16r1:Concept_App_Service_Conference_Scaler]]
; App Service Conference Transcriptions: [[Reference16r1:Concept_App_Service_Conference_Transcriptions]]
; App Service Transcriptions: [[Reference16r1:Concept_App_Service_Transcriptions]]
; App Service Documents: [[Reference16r1:Concept_App_Service_Documents]]
; App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
; App Service IP: [[Reference16r1:Concept App Service IP]]

== New environment for App Platform ==
The new [[Reference16r1:Concept_innovaphone_App_Platform_Container|App Platform Container]] provides an Docker container. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

== Removed ==
The following software is no longer included.

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

== Deprecated ==
The following software is based on legacy technology, with no further development and limited maintenance and support.

* ''Nothing''

== Previously deprecated and now no longer supported ==
The following software is based on legacy technology, with no further development and no more maintenance and support.

* ''Nothing''

==Known Problems==
===Long Update-duration===
When you update, it can be up to 10 minutes before you have access to your app platform again.

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-05-28T13:46:45Z

Slu: /* Changes visible to the end customers */

== Applies To ==
This information applies to:

* All 16r1 capable innovaphone devices
: For a general overview of the upgrade process and a list of supported devices with 16r1, see [[Howto:Firmware Upgrade]]
== Licenses ==
In case of cloud or rental model, don't worry about licenses.

If the system is licensed on premise, you'll need to regenerate the license file for v16 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location

=== AP Upgrade to Image 140037 or newer ===
* First, upgrade your application platform to at least image version 140037. After that you can go ahead.

=== Upgrade Sequence ===
In systems of multiple units, it is important to update the tree from top to bottom. In other words, update the master unit first, and then the machines at the lower levels. If you're using a DevicesApp update job that updates the entire system at once, you don't need to do anything here.

=== TechAssist Upgrade Helper ===
* Before you start, make sure that all TechAssist tests (you will receive the required tests in the last update in the previous major version) labelled <code>Pre Upgrade: xy</code> are positive, if available
* When you are finished, make sure that all TechAssist tests (you will receive new tests with the upgrade) are positive

== Changes visible to the end customers ==
Listed here are changes that should be communicated by resellers to end users prior to a upgrade, as the change will be visible/audible in the behaviour of the application/device.

* 16r1 introduces the feature of [[Reference16r1:Concept_Reconnect_Calls | Reconnect Calls for Seamless Handover & Roaming]]. As a result, calls will not be dropped on network interruptions or PBX reboots. Instead users receive visual (MyApps or phone display) and audio (in-band tone) feedback and the call is reconnected automatically.
* Chat App: The option in ChatApp that allowed users to choose whether to send a message using ENTER or SHIFT+ENTER has been removed. Messages can now only be sent using CTRL+ENTER without pressing the send button.

== Manual steps needed after upgrade ==
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.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Projects ===
* Projects requires '''App platform version 140029''' or higher, so updating the App Platform before Projects is recommended. The Store will prohibit the update if the App Plattform does not have the minimum required version.
* For some extra admin-functionalities the '''Projects App Object needs to have an admin mode''' (App-tab). Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.
* The '''App Platform requires the correct Time and a Timezone''' set under AP Manager/Settings/General. This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).

=== For legacy support only: Change TLS Profile ===
The ''Normal'' profile has been updated to allow only TLS 1.3 and TLS 1.2. This setting is compatible with all supported firmware versions. So you don't need to do any changes.
However if you need older TLS versions for compatibility with legacy devices, consider changing the TLS profile to ''Legacy''. In that case please see [[Reference16r1:IP4/General/TLS]] for details.

== New Apps ==
New Apps will not be installed automatically by the upgrade. The installation description of new apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.

; App Charts: [[Reference16r1:Concept_App_Charts]]
; App Polls: [[Reference16r1:Concept App Polls]]
; App MQTT Broker: [[Reference16r1:Concept_App_MQTT_Broker]]
; App Service Conference Scaler: [[Reference16r1:Concept_App_Service_Conference_Scaler]]
; App Service Conference Transcriptions: [[Reference16r1:Concept_App_Service_Conference_Transcriptions]]
; App Service Transcriptions: [[Reference16r1:Concept_App_Service_Transcriptions]]
; App Service Documents: [[Reference16r1:Concept_App_Service_Documents]]
; App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
; App Service IP: [[Reference16r1:Concept App Service IP]]

== New environment for App Platform ==
The new [[Reference16r1:Concept_innovaphone_App_Platform_Container|App Platform Container]] provides an Docker container. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.

== Removed ==
The following software is no longer included.

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

== Deprecated ==
The following software is based on legacy technology, with no further development and limited maintenance and support.

* ''Nothing''

== Previously deprecated and now no longer supported ==
The following software is based on legacy technology, with no further development and no more maintenance and support.

* ''Nothing''

==Known Problems==
===Long Update-duration===
When you update, it can be up to 10 minutes before you have access to your app platform again.

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Reference17:Concept App Service Translations

2026-05-27T11:20:17Z

Slu: /* Translations against the backend */

[[Category:Concept|Apps]]
[[Category:Concept App Service Translations]]
== Overview ==
The idea of the translations app is to provide an interface for other apps to translate user content on-the-fly. So other apps can integrate the translation service via the [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm local JavaScript API] in the client and thus offer the user translated texts.

The service serves as a proxy and integrates a corresponding backend. This means that you need your own account at the external translations service and can configure your credentials in the Settings App.

== Supported translation services ==
You can configure multiple translation backends and switch between them.

=== DeepL ===
This interface uses the https:///www.deepl.com translation API.

This interface is used as the default interface. you dont must provide an ''API-URL'' in the [[Reference16r1:Apps/PbxManager/App Translations|Settings]]. A custom API-URL is only for a local version with the same API interface.

;Privacy
:API Free: https://www.deepl.com/de/privacy#section_12
:API Pro: https://www.deepl.com/de/privacy#section_5
;Cost model and Pricing
:Pay per character (To save costs, the app service offers a cache to avoid multiple translations)
:https://www.deepl.com/de/pro#developer

==== Technical Concept ====

* The DeepL API is a synchronous HTTP flow. This means that we request a translation and get an instant response with the translation.
* Outgoing HTTP(S) request to the DeepL API
* If you not override the URL, it is used HTTPS only

=== EU - eTranslation ===
This interface uses the EU service eTranslation.

European Commission’s free and secure AI language tools: https://translation.ec.europa.eu/tools-and-resources/ai-translation-and-language-tools_en

Technical Documentation: https://language-tools.ec.europa.eu/dev-corner/etranslation/rest-v2/text

==== Technical Concept ====
* The EU-eTranslation uses an asynchronous HTTP flow with webhooks to deliver processed translations
* Translation flow
*# On every app startup
*## a dynamic user / password combination is created, which will be used for later secure incoming webhooks
*### Example: <code>23bcf2fd / 19ccf70b-028c-e7a8-94eb-1ad7db91d4c8</code>
*## the own app url is generated from the current environment
*### Example: <code><nowiki>https://23bcf2fd:19ccf70b-028c-e7a8-94eb-1ad7db91d4c8@apps.slu.de/slu.de/translations/webhook-basicauth</nowiki></code>
*# Outgoing HTTPS request to the eTranslation Service. The translation job will be queued. As additional information in the job, a callback webhook URL with a username and password will be placed.
*# If the processing is finished, a webhook to the app is delivered via HTTPS
*# The job result will be processed and delivered back to the user that has requested the translation
==== Limitations ====
* 50 concurrent translation requests
* 5.000 characters per translation

== Licensing ==
No license needed

== Installation ==
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown.
* In the search field located on the top right corner of the store, search for '''"Translations"''' and click on it
* Select the proper firmware version and click on install
* Close and open the PBX manager to refresh the list of the available colored AP plugin
* Click on the '''"AP Translations"''' and click on '''" + Add an App"'''
* Enter a '''"Name"''' that is used as the display name ''(all characters allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Translations, SIP: translations''
* Tick the appropriate template to distribute the App (the app is needed at every user object from any user who wants to use the translation API)
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

== Translation - Client ==
There is no view/app that the user can explicitly open. The service runs in the background and has no UI and can be integrated by other apps. In order for the user to have access to the translation service, their user object must have access to the app object of the translations app.

The client side of the app service receives requests from all other apps via the local JavaScript API and sends them to the service. The result of the request is returned to the original app via the local JavaScript API

== Translation - App Service ==
The App Service performs tasks in the following areas:
* Language recognition
* Caching
* Translations against the backend (deepl.com)

=== Language recognition ===
An offline API is offered to recognize the language used in a string. This recognition is also used for translations to avoid unnecessary translations (e.g. EN to EN translations are prevented). This payload will not be sent to any backend service, thus avoiding unnecessary costs. A few features exist which should make sure, a recognized language is only considered, if there is enough confidence:
* Strings shorter than 6 words are skipped, since the chance for false positives are relatively high
* Strings in which there are not enough word matches to be confident for any language will be skipped, also because of high chances for false positives
* Strings that are more than one language with a nearly similar amount of word matches will be skipped

Supported languages: cs, de, en-gb, es, fr, it, nl, pl, pt-pt, ro, ru, sl, tr

=== Caching ===
To save costs, all translations are cached in the App Services database. If a string is translated multiple times, only the first translation is carried out by the backend, and the translated version is saved in the cache. A second translation is therefore free of charge and performs better.

=== Translations against the backend ===
Translation requests that cannot be handled by the local cache are forwarded to the configured translation backend. After successful translation, the translated version is kept in the cache for future requests.

The list of supported languages depends on the supported languages of the used [https://developers.deepl.com/docs/resources/supported-languages#target-languages service provider]. It will be read from the service provider each time the Translations App Service starts.

=== Charts Statistics ===
The app service will provide telemetry data to the integrated Charts app service.

;requestTranslate
:Translation requests (default) to the App Service
;requestTranslateAll
:TranslationAll requests to the App Service
;requestWebhookBasic
:Webhooks from external translations backend with legacy BasicAuth to the App Service
;requestWebhook
:Webhooks from external translations backend to the App Service
;DetectLanguagePreventTranslation
:Amount of translation requests that are not processed because language detection detected same languages
;CacheAdd
:New translation payload is stored in the cache
;CacheHit
:Translation request is solved by existing cache entry
;DeepL
:External backend request
;eTranslation
:External backend request

== Troubleshooting ==

To troubleshoot this App Service, you need the traceflags ''App'', ''Database'', ''HTTP-Client'' in your App instance.

== Related Articles ==
* [https://sdk.innovaphone.com/15r1/web1/com.innovaphone.translation/com.innovaphone.translation.htm SDK Documentation - Translation API]
* [[{{NAMESPACE}}:Apps/PbxManager/App_Translations]]