innovaphone wiki - User contributions [en]

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.<br>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.<br/>
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.<br>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.<br/>
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.<br>
:'''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.<br>
:'''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.<br>
:'''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.<br>
:'''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.<br>
:'''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.<br>
:'''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 ==
<span style="color:red; font-weight: bold">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</span>

=== 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)
<br>
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. <br />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). <br />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. <br />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 ==
<span style="color:red; font-weight: bold">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</span>

=== 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)
<br>
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. <br />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). <br />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. <br />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]]

Howto:How to IPxx13

2026-05-27T09:42:12Z

Slu: /* SSD */

[[Category:Howto]]
[[Category:Concept IPxx13]]

== Applies to ==
* IP0013
* IP6013
* V13+

== Brief ==

=== IP0013 ===
* VoIP-PBX and routing gateway including reverse proxy and SBC functionalities
* Orderno.: 01-00013-001

=== IP6013 ===
* VoIP-PBX and routing gateway for four ISDN-S2M interfaces plus Reverse Proxy and SBC functionalities
* Orderno.: 01-06013-001

== SSD ==

IPxx13 owns two internal slots for '''M.2 SSD'''.

Slot interface is '''NVMe''' - [https://en.wikipedia.org/wiki/NVM_Express non volatile memory express].

Slot formfactor is M.2 2242 M-Key - dimensioning 22mm*42mm.

Maximum power consumption per M.2 SSD is 2.5W.

SSD has to be plugged in outer slot named '''SSD0''' on the PCB. <u>Use of secondary inner slot SSD1 is not supported.</u>

[[image:xx13_ssd.png]]

innovaphone offers and supports:
* M.2 SSD 1 TB with order no 03-00010-031
* M.2 SSD 512 GB with order no 03-00010-017

No technical support is provided for models other than those offered by innovaphone.

<span style="color:red">Note: '''These information <u>DO NOT APPLY</u> to IPxx11 and IP11xx based mSATA SSDs!''' For information to those devices, refer to [[Howto:Tested mSata modules|this article]].</span>

== Power supply ==

The devices mandatorily require Power over Ethernet+ supply according to IEEE 802.3at, Class 4 (PoE+) for operation.

Currently, innovaphone offers no POE+ injector.

According to customer feedback, the following PoE+ injectors that meet the performance requirements of IPxx13 are used in projects:
* [https://docs.rs-online.com/c557/A700000010094578.pdf Edimax GP-103IT]
* [https://ww1.microchip.com/downloads/aemDocuments/documents/POE/ProductDocuments/DataSheets/PD-9001GR-Data-Sheet.pdf Microchip PD-9001GR/AT]
* LANCOM POE++ injector (type unknown)
Please note that this information are subject to change and have not been verified by innovaphone.

== Firmware ==
Available in [https://store.innovaphone.com/release/download.htm official release store]

===IP0013===
Following firmware versions are available for the IP0013 gateway itself:
* V13r2: available via release store since V13r2sr10, build no 136337

===IP6013===
Following firmware versions are available for the IP6013 gateway itself:
* V13r1: available via release store since V13r1sr25, build no 132894
* V13r2: starting with 13r2final, build no 136094

=== Application Platform ===
The device hosts an 64-bit-ARM-processor which requires use of 64bit-architecture application platform.

Respective arm64-AP is available for 13r1 and 13r2 in offical release store.

== Use cases ==
IP0013 and IP6013 host 150 software conference channels for audio conferencing (since 13r3sr4, before 60).

IP6013 additionally hosts 60 hardware digital signal processors for support of PCM traffic via PRI interfaces, audio faxes and audio conferencing.

Cumulating hardware and software conference channels at IP6013 into a single room is not supported.

Use of features such as PBX-operation, PRI- and fax traffic, audio/video conferencing and Application Sharing influence the CPU load.

Exceeding the maximum CPU limit may lead to device outage.

innovaphone supports following use cases:

'''All-in-one-box'''
* operation of PBX-functionality
* IP0013: for conferencing use SCNF interface
* IP6013: use HW-DSPs for PCM-Audio and Fax only, for conferencing use CONF '''or''' SCNF interface only

'''Gateway only'''
* operation as gateway only '''without activated PBX functionality and no AP installed'''
* IP0013: use SCNF for conferencing
* IP6013: use PRI-interfaces and HW-DSPs for S2M-Audio and Fax and SCNF for conferencing, <br />'''or''' in case of no PRI/FAX traffic, both CONF and SCNF can be used for conferencing

[[Howto:How to implement large PBXs|Herefore mentioned basic conditions]] apply at any time for all kind of configurations and usecases.

==Known Issues==
* IP6013: FAX interface will provide audio-fax capabilities starting with 13r1sr26

Reference16r1:Services/Reverse-Proxy

2026-05-19T14:44:36Z

Slu: /* General Parameters */

[[Category:Concept|Reverse Proxy]]
[[Category:Concept Reverse Proxy]]
The reverse proxy is used to forward H.323, SIP, LDAP, HTTP and SMTP requests it receives to other hosts, based on system information like gatekeeper name host name, path or domain.
This way it can be controlled which services may be accessed thru the reverse proxy.
A reverse proxy may be located at the boundary of an private and a public network, or inside the private network, if the respective ports are forwarded to it by the NAT Router/Firewall.
It can be even configured on the same device as the PBX itself. In this case the other services on the device should use non-standard ports, so that the reverse proxy can receive the requests on the standard port and forward them locally to the non-standard ports.

== General Parameters ==

;No IPv4: Turn off IPv4 for the reverse proxy function
;No IPv6: Turn off IPv6 for the reverse proxy function
;H.323/TCP, H.323/TLS: Ports for incoming H.323 TCP or TLS Connections. Use 1720 and 1300 for the standard ports.
;SIP/TCP, SIP/TLS: Ports for incoming SIP TCP or TLS Connections. Use 5060 and 5061 for the standard ports.
;LDAP, LDAPs: Ports for incoming LDAP TCP or TLS Connections. Use 389 and 636 for the Standard ports.
;HTTP, HTTPS: Ports for incoming HTTP TCP or TLS Connections. Use 80 and 443 for the Standard ports.
;SMTP, SMTPS: Ports for incoming SMTP TCP or TLS Connections. Use 25 and 587 for the Standard ports.
;Log Forwarded Requests: activate protocol dependent logging for successfully forwarded / accepted requests
;Log Rejected Requests: activate protocol dependent logging for rejected / non-accepted requests
;Blacklist Expiration: Time in minutes after which an entry put in the blacklist automatically, will be removed from the blacklist.
;Suspicious Requests/min: Threshold to put an address into the blacklist
;Public NAT router address: Required for SIP if RP is behind NAT. External SIP clients will receive this value in Route header of SIP messages. You can configure DNS name or IP address and port here.<br>If not configured, RP writes it's own local IP address and port into Route header of SIP messages. This works only if RP has a public local IP address.

== Hosts ==

List of configured hosts. Click on the host Name to edit or delete. Use new to add new host

;Out
:Destination IP-Address (IPv4 or IPv6) for this rule, following by the plain text port
:Destination DNS name: must start with '''@''' and is limited to 15 chars. For longer names, you can use a DNS suffix (see below).
;TLS
:Port for encrypted traffic
;Check Certificate
:If the Check Certificate checkmark is set, for the internal connection TLS is used only if the received certificate matches the user name within the protocol. This way a host receiving a request through the Reverse Proxy using TLS can assume that the connection was authenticated using a valid certificate, which matches the user.
;App Login
:Experimental feature to allow access only if a myPBX session has been previously authenticated. Not supported for myApps.
;Default
:This rule will be used if only the Domain without a path or file in the URI was requested. The empty path is then replaced by the specified URL when the request is forwarded (e.g. an entry ''<nowiki>http://</nowiki><host>/web/index.htm'' with the ''Default'' check-mark ticked will match requests with no path and the request is forwarded with the path set to ''/web/index.htm''). Note that also, an implicit rule is created that forwards all requests for files in and beneath the folder where the default document is in (in the example rule, requests to all files under ''<nowiki>http://</nowiki><host>/web'' will be forwarded)
;MTLS:
:Request MTLS on incoming connections. The requesting client has to provide the TLS Server Name on the incoming TLS connection. The Server Name is used to match to the host. If the checkmark is set, MTLS is requested then. If no Server Name is provided or no valid client certificate a connection for this host is rejected. The name od the received and validated certificate is forwarded as X-Remote-Cert HTTP header.
;Network
:''adddr:network'' to restrict a configured protocol to certain networks

=== SMTP ===
The host is searched for using different criteria based on the incoming socket.

The criteria are searched in the order given and the first match wins.

;TLS: the SNI of the TLS handshake
;EHLO: the client hostname send inside the client EHLO SMTP protocol message
;AUTH: the username of an AUTH PLAIN login. The whole username is matched and if no match is found, the domain part after an @ sign if present.
;RCPT-TO: the recipient mail address. The whole mail address is matched and if no match is found, the domain part.

==== STARTTLS ====

* If the EHLO message is already suitable to detect the host, STARTTLS is handled by the server behind the RP and port forwarding must be done to the non TLS port in this case.
* Otherwise the RP itself handles the STARTTLS handshake. It then doesn't matter if you internally forward to the non TLS port or the TLS port but STARTTLS won't be done anymore in any case.

== DNS Suffixes ==

If you want to forward requests to internal DNS names instead of IP addresses and such an internal DNS name is longer than 15 chars, you must use DNS suffixes to reference it.<br/>

;Id: a unique id which is used as reference
;Suffix: a suffix which is used as replacement of #Id

If you want to use such a suffix inside '''Out''' of a host, you must write it like this:
'''@host1.#1''' -> this will be expanded to '''host1.example.com''', if the suffix with Id 1 has the value example.com

== Counter ==

Current top ten address with suspicious requests

== Addresses ==

Blacklist/Whitelist addresses

Reference16r1:Services/Reverse-Proxy

2026-05-19T13:24:51Z

Slu: /* General Parameters */

[[Category:Concept|Reverse Proxy]]
[[Category:Concept Reverse Proxy]]
The reverse proxy is used to forward H.323, SIP, LDAP, HTTP and SMTP requests it receives to other hosts, based on system information like gatekeeper name host name, path or domain.
This way it can be controlled which services may be accessed thru the reverse proxy.
A reverse proxy may be located at the boundary of an private and a public network, or inside the private network, if the respective ports are forwarded to it by the NAT Router/Firewall.
It can be even configured on the same device as the PBX itself. In this case the other services on the device should use non-standard ports, so that the reverse proxy can receive the requests on the standard port and forward them locally to the non-standard ports.

== General Parameters ==

;No IPv4: Turn off IPv4 for the reverse proxy function
;No IPv6: Turn off IPv6 for the reverse proxy function
;H.323/TCP, H.323/TLS: Ports for incoming H.323 TCP or TLS Connections. Use 1720 and 1300 for the standard ports.
;SIP/TCP, SIP/TLS: Ports for incoming SIP TCP or TLS Connections. Use 5060 and 5061 for the standard ports.
;LDAP, LDAPs: Ports for incoming LDAP TCP or TLS Connections. Use 389 and 636 for the Standard ports.
;HTTP, HTTPS: Ports for incoming HTTP TCP or TLS Connections. Use 80 and 443 for the Standard ports.
;SMTP, SMTPS: Ports for incoming SMTP TCP or TLS Connections. Use 25 and 587 for the Standard ports.
;Log Forwarded Requests: activate protocol dependent logging for successfully forwarded / accepted requests
;Log Rejected Requests: activate protocol dependent logging for rejected / non-accepted requests
;Blacklist Expiration: Time in minutes after which an entry put in the blacklist automatically, will be removed from the blacklist.
;Suspicious Requests/min: Threshold to put an address into the blacklist: Whether a request is flagged as suspicious depends on the following factors, all of them must be met.
:* System uptime > 300 seconds (prevents false positives immediately after boot)
:* Connection duration < 4 seconds (the connection was closed very quickly)
:* The destination closed the connection, not the client itself
:* HTTP version is not 1.0
:* HTTP-Content-Length is set to another value than -1 (a body was announced) Translated with DeepL.com (free version)
;Public NAT router address: Required for SIP if RP is behind NAT. External SIP clients will receive this value in Route header of SIP messages. You can configure DNS name or IP address and port here.<br>If not configured, RP writes it's own local IP address and port into Route header of SIP messages. This works only if RP has a public local IP address.

== Hosts ==

List of configured hosts. Click on the host Name to edit or delete. Use new to add new host

;Out
:Destination IP-Address (IPv4 or IPv6) for this rule, following by the plain text port
:Destination DNS name: must start with '''@''' and is limited to 15 chars. For longer names, you can use a DNS suffix (see below).
;TLS
:Port for encrypted traffic
;Check Certificate
:If the Check Certificate checkmark is set, for the internal connection TLS is used only if the received certificate matches the user name within the protocol. This way a host receiving a request through the Reverse Proxy using TLS can assume that the connection was authenticated using a valid certificate, which matches the user.
;App Login
:Experimental feature to allow access only if a myPBX session has been previously authenticated. Not supported for myApps.
;Default
:This rule will be used if only the Domain without a path or file in the URI was requested. The empty path is then replaced by the specified URL when the request is forwarded (e.g. an entry ''<nowiki>http://</nowiki><host>/web/index.htm'' with the ''Default'' check-mark ticked will match requests with no path and the request is forwarded with the path set to ''/web/index.htm''). Note that also, an implicit rule is created that forwards all requests for files in and beneath the folder where the default document is in (in the example rule, requests to all files under ''<nowiki>http://</nowiki><host>/web'' will be forwarded)
;MTLS:
:Request MTLS on incoming connections. The requesting client has to provide the TLS Server Name on the incoming TLS connection. The Server Name is used to match to the host. If the checkmark is set, MTLS is requested then. If no Server Name is provided or no valid client certificate a connection for this host is rejected. The name od the received and validated certificate is forwarded as X-Remote-Cert HTTP header.
;Network
:''adddr:network'' to restrict a configured protocol to certain networks

=== SMTP ===
The host is searched for using different criteria based on the incoming socket.

The criteria are searched in the order given and the first match wins.

;TLS: the SNI of the TLS handshake
;EHLO: the client hostname send inside the client EHLO SMTP protocol message
;AUTH: the username of an AUTH PLAIN login. The whole username is matched and if no match is found, the domain part after an @ sign if present.
;RCPT-TO: the recipient mail address. The whole mail address is matched and if no match is found, the domain part.

==== STARTTLS ====

* If the EHLO message is already suitable to detect the host, STARTTLS is handled by the server behind the RP and port forwarding must be done to the non TLS port in this case.
* Otherwise the RP itself handles the STARTTLS handshake. It then doesn't matter if you internally forward to the non TLS port or the TLS port but STARTTLS won't be done anymore in any case.

== DNS Suffixes ==

If you want to forward requests to internal DNS names instead of IP addresses and such an internal DNS name is longer than 15 chars, you must use DNS suffixes to reference it.<br/>

;Id: a unique id which is used as reference
;Suffix: a suffix which is used as replacement of #Id

If you want to use such a suffix inside '''Out''' of a host, you must write it like this:
'''@host1.#1''' -> this will be expanded to '''host1.example.com''', if the suffix with Id 1 has the value example.com

== Counter ==

Current top ten address with suspicious requests

== Addresses ==

Blacklist/Whitelist addresses

Reference16r1:Services/Reverse-Proxy

2026-05-19T13:17:22Z

Slu: Created page with "Reverse Proxy Category:Concept Reverse Proxy The reverse proxy is used to forward H.323, SIP, LDAP, HTTP and SMTP requests it receives to other hosts, based on system information like gatekeeper name host name, path or domain. This way it can be controlled which services may be accessed thru the reverse proxy. A reverse proxy may be located at the boundary of an private and a public network, or inside the private network, if the respective ports..."

Reference15r1:Concept App Service Recordings

2026-05-19T09:41:29Z

Slu: /* Scheduled deletion of old recordings */

[[Category:Concept App Service Recordings]]
[[Category:Concept|Apps]]

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V15r1
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* ReportsApp

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png|/Usrrecord.png|usrrecord.png/]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Search for user specific recordings
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information, the activity protocol and the notes
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png|/Adminrecord.png|adminrecord.png/]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Download the activity protocol
* Search for recordings
* Play, Listen or Download a recording as a .zip file which contains the .WAV file and a .PDF with the call information, the activity protocol and the notes
* Protect against deletion or delete a recording
* Filter records by name, by date
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX Recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX Recordings Admin APP-Object with the PBX Manager Plugin.
* Assign Recordings Admin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign Recordings App to users who will use the Recordings App.
* Start Recordings Admin App, open the menu (upright) and configure
** Delete recordings after (days) (mandatory - default is 30 days)
** PBX name (mandatory)
** CryptKey (optional)
** WebDav user & WebDav password (both optional)
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:on deskphones, softphones or gateway interfaces.
:On innovaphone deskphones, enable recording via Phone/User-X/Recording by setting Mode to transparent and Recorder to HTTP Server.
:On innovaphone softphones, recordings config is only visible, if the user has the appropriate app(innovaphone-recorder) license.

=== PBX Manager Plugin ===

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

==== Deletion of recordings ====
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied".<br>
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

==== Access List ====
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible.<br />
For the configuration, see : [[Howto15r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

== Functions / Features ==
=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. This is done in a .zip archive containing
* the wave audio file
* a .pdf file containing
** the call information
** the activity protocol
** the notes

=== Download Action log ===
After clicking on "Action log" in RecordingsAdmin, it can be downloaded. This is done in a .zip archive containing a .pdf file with the performed actions for all recordings
* action_play (recording has been played)
* action_download (recording has been downloaded)
* action_delete (recording has been deleted)
* action permanent (recording has been protected against deletion)
* action_volatile (protection against deletion has been deactivated)
* action_timeout (recording has been deleted due to the scheduled deletion config)

=== WebDav Access ===
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

In conjunction with the [[#Scheduled deletion of old recordings|scheduled deletion of old recordings]], this can control the size of the application database used.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto15r1:RecordingsApp#Configuring WebDav credentials in RecordingsAdmin|the respective documentation]].

=== Encrypted Recordings ===
Recordings can be stored encrypted when in the Recordings Admin App in the settings tab a crypt key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next recordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remembered to access previously stored recordings with that key.

=== 4 Eyes Access ===
This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbxmanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users Recordings App, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his Recordings App, all permissions given to the users are revoked

=== Notes ===
To each recording textual notes can be added. Pressing the "Note" button on the recording entry opens a window beneath the entry. Each user with access to a specific recording is also allowed to see the notes for this recording.

=== Watermark ===
In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existed in the database prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Information ==
=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion. The background deletion process will be triggered 24 hours after the initial app start-up.

''The deletion will remove the database entry as well as the audio file from the file system completely, so no recovery will be possible.''

=== Call Information ===
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

=== Call Recording Storage ===
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

=== Licensing ===
An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

=== Recording on Special Interfaces ===
* Trunk Interface/Gateway
The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.
* Waiting Queue
The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3, V14r1 or V14r2 to V15r1 Recordings App ==
=== Compatibility ===
A V15r1 Recordings App can not be used in the V13r3, V14r1 or V14r2 PBX and App Platform environment.
=== License Changes ===
Licensing is the same as version 14r2
=== Database Conversion ===
Databases from previous versions (13r3,14r1,14r2) will be converted automatically

== Troubleshooting ==
=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:
*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports"
** WebSocket connection from App Object Reports should show ''connected''
**In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto15r1:RecordingsApp|HowtoV15r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
<br>
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

=== WebDav Access to Recordings not possible with newer Versions of WinSCP ===
When using newer versions of WinSCP, authentication to the WebDAV directory of recordings fails.
Workaround: An older version of WinSCP must be used. The last working version is WinSCP V6.3.7.

Template:Click

2026-05-15T13:23:42Z

Slu: /* Problems */

<div style="position: relative; width: {{{width}}}; height: {{{height}}}; overflow: hidden;">
<div style="position: absolute; top: 0px; left: 0px; font-size: 100px; overflow: hidden; line-height: 100px; z-index: 3;">[[{{{link}}}|   ]]</div>
<div style="position: absolute; top: 0px; left: 0px; z-index: 2;">[[Image:{{{image}}}|{{{width}}}|{{{link}}}]]</div>
</div>
<noinclude>

'''Usage:''' <nowiki>{{Click | image=myimage.png | link=PageName | width=10px | height=10px}}</nowiki>

This template attempts to superimpose an invisible link on an image, such that clicking on the image does ''not'' take you to the image description page (normal behaviour).

It's useful for small icons/logos which are representative of an article, and which a user might click on expecting to be taken to that article. Here we are using it on the [[Main Page]] for example. It's use should minimised because of the following problems.

==== Problems ====

It doesn't work in text-only browsers, and in screen readers for the disabled, and possibly other situations. The technique of using CSS to change page content also completely breaks an article's web accessibility by contravening a WAI priority-one checkpoint.[http://www.w3.org/TR/WAI-WEBCONTENT/#tech-order-style-sheets]

==== See also ====
* [http://en.wikipedia.org/wiki/Template:Click Template:Click on wikipedia] where we got this from.

</noinclude>

Help:Navigation bar

2026-05-15T13:23:04Z

Slu:

The '''navigation bar''' provides links to the most important locations in the wiki and supplies site administrators with a place to add a persistent collection of links. For instance, most wikis will link to their main page and some useful tools.

Under the default skin, the navigation bar appears to the left along with the search bar and toolbox, but the placement varies between skins.

== Contents ==

The contents of the navigation bar can be edited using the <tt>'''[[MediaWiki:Sidebar]]'''</tt> message page. To access this page, enter "MediaWiki:Sidebar" into the "search" box and click ''Go''. As of MediaWiki 1.9.0, the default page will not appear to exist; this is normal. Click "create this page" to edit the navigation bar the first time.

The format of this message is as follows:

<pre>* navigation
** mainpage|mainpage
** Special:Recentchanges|Recent changes
** forums-url|Forums
** http://www.mediawiki.org|MediaWiki home</pre>

This snippet demonstrates the various formats available for use.

=== Headings ===

The navigation bar can be split into sections, each with a heading of its own. The heading for each section is taken from the first-level list element (in the example above, "navigation", for instance).

If this text corresponds to the name of a system message, i.e. a page with that title exists in the MediaWiki namespace, then the text of the message is used as a label, otherwise the title is used as-is.

Example: if you put <code><a href="somewhere">navigation</a></code> into your wiki's navigation you get a link to the page somewhere instead of just plain text. Of course, headings can be plain text if you prefer.

=== Links ===
The second-level list elements each correspond to a link on the navigation bar, where the format is:

<code>** ''target''|''label''</code>

The link target does not depend on the interface language set in the preferences, while the link label ''can'' be made to depend on that, and taken from the database or the language file:

*If the MediaWiki page with the name ''target'' exists then the contents of that MediaWiki page is taken as link target (internal, interwiki, or external).
*Else, if there is a default message in the site language with ID equal to ''target'', that message is taken as link target.
*Else, ''target'' itself is taken as link target (this does not work for some external links, notably those with "&" in it; use the first method instead: make a page in the MediaWiki namespace).

*In the case of existence of the MediaWiki page with the name ''label'' (followed by ''/interface_language_code'' if the interface language set in the preferences is not the default) then the contents of that MediaWiki page is taken as link label.
*Else, if there is a default message in the interface language with ID equal to ''label'', that message is taken as link label.
*Else, ''label'' itself is taken as link label.

In the example above, [[Main Page]] contains the name of the main page, e.g. [[Main Page]], and so both the target and caption are expanded to that text. However, [[Special:Recent changes]] does not exist, so in the case of the example, the label text for the second item is used as-is. This has the disadvantage that the preference setting of the interface language does not work for such a label.

The third element references Forums-url, which will contain the full external URL for the "forums", while using a plain label. Item four demonstrates direct linking to an external source.

=== Troubleshooting ===

==== Unable to edit ====

The usual cause for being unable to edit the page is having insufficient permissions to do so. Since the page is in the MediaWiki namespace, permission to edit the user interface text is required. By default, this is available to all sysops, but may be customised on your wiki installation.

==== Changes not showing up on all pages ====

MediaWiki performs aggressive caching at various levels, which often causes the navigation bar to persist after changes. [[Help:Purge|Purging the cache]] of affected pages should correct the situation. To perform a mass-purge of all caches at once, [http://www.mysql.org/doc/refman/5.0/en/truncate.html truncate] the <tt>'''objectcache'''</tt> table in your database or [http://www.freebsd.org/cgi/man.cgi?query=touch touch] the <tt>'''LocalSettings.php'''</tt> file (you may have to do both).

==== Lowercase links ====

If your links are not being capitalised as intended, trying adding spaces around the bar character, eg

<nowiki>* http://www.example.com/download.php?file=44555 | Download</nowiki>

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

Template:Click

2026-05-15T13:22:23Z

Slu:

<div style="position: relative; width: {{{width}}}; height: {{{height}}}; overflow: hidden;">
<div style="position: absolute; top: 0px; left: 0px; font-size: 100px; overflow: hidden; line-height: 100px; z-index: 3;">[[{{{link}}}|   ]]</div>
<div style="position: absolute; top: 0px; left: 0px; z-index: 2;">[[Image:{{{image}}}|{{{width}}}|{{{link}}}]]</div>
</div>
<noinclude>

'''Usage:''' <nowiki>{{Click | image=myimage.png | link=PageName | width=10px | height=10px}}</nowiki>

This template attempts to superimpose an invisible link on an image, such that clicking on the image does ''not'' take you to the image description page (normal behaviour).

It's useful for small icons/logos which are representative of an article, and which a user might click on expecting to be taken to that article. Here we are using it on the [[Main Page]] for example. It's use should minimised because of the following problems.

==== Problems ====

It doesn't work in text-only browsers, and in screen readers for the disabled, and possibly other situations. The technique of using [[w:CSS|CSS]] to change page content also completely breaks an article's [[w:web accessibility|web accessibility]] by contravening a [[w:WAI|WAI]] priority-one checkpoint.[http://www.w3.org/TR/WAI-WEBCONTENT/#tech-order-style-sheets]

==== See also ====
* [http://en.wikipedia.org/wiki/Template:Click Template:Click on wikipedia] where we got this from.

</noinclude>

Help:Copying

2026-05-15T13:20:59Z

Slu:

You can obtain a copy of the help system in this wiki for local use in your own wiki following these steps:

* Step one: In a separate browser window, navigate to [[Special:Export]].
* Step two: You will see an open textbox asking you for a list of pages to export.
* Step three: Copy the list below and paste it into that textbox. This is a generally useful set, making the resulting help structure in your wiki look almost identical to the one here.

[[Help:Contents]]
[[Help:Navigation]]
[[Help:Searching]]
[[Help:Tracking_changes]]
[[Help:Editing_pages]]
[[Help:Starting_a_new_page]]
[[Help:Formatting]]
[[Help:Links]]
[[Help:Categories]]
[[Help:Images]]
[[Help:Templates]]
[[Help:Tables]]
[[Help:Variables]]
[[Help:Managing_files]]
[[Help:Preferences]]
[[Help:Skins]]
[[Help:Namespaces]]
[[Help:Interwiki_linking]]
[[Category:Help]]
[[Template:Meta]]
[[Template:Admin_tip]]
[[Template:Prettytable]]
[[Template:Hl2]]
[[Template:Hl3]]
[[Template:Thankyou]]
[[:Image:Example.jpg]]
[[:Image:Geographylogo.png]]

Sysops only:
[[Template:Click]]
[[Template:Languages]]

* Step four: Make sure the box "Include only the current revision, not the full history" is CHECKED.
* Step five: Click the 'Export' button.
* Step six: Save the file to your desktop or other convenient location you'll remember.
* Step seven: Navigate to Special:Import on YOUR wiki. (You must be logged in as Admin/Sysop level to do this.)
* Step eight: Browse for the file you saved, and click 'Upload'.

For the images this only copies the image descriptions. You need also to upload them on your wiki. Although not complete, at least this gets you started on a decent help system.

==Automated copying==

If you use pywikipedia, there is a script to automate the copying at http://mediawiki-tools.cvs.sourceforge.net/mediawiki-tools/pywikipedia/mirrorhelp.py, which copies all pages in the help namespace along with templates and images directly referenced by those.

[[Category:Help|Copying]]

Help:Navigation

2026-05-15T13:20:40Z

Slu: /* Toolbox */

If you look at a page in MediaWiki, you'll find three main navigation elements: The sidebar on the left gives you access to important pages in the Wiki like recent changes or file upload. At the top of the page are the links which belong to the page currently displayed: its associated discussion page, the version history, and - most notably - the edit link. In the top right corner you'll find, as an anonymous user, the link to create an account and login (they are on the same page). As a logged-in user you have a collection of personal links, like the one to your user page or your preferences.

== Sidebar ==
[[Image:M-en-sidebar.png|framed|right|Example sidebar, shown on the left of the page]]
The sidebar is displayed on the left edge of the page below the site logo (if using the default MonoBook skin). This sidebar gives you access to important pages in the Wiki like recent changes or file upload.

=== Navigation ===
A click on the logo brings you back to the start page of the wiki. The links take you to important pages in the wiki, they can be configured by site administrators of the individual wikis

{{Admin tip|tip=You can customize the links in the navigation section via [[Special:Allmessages]]. Or create a menu on your own in [[MediaWiki:Sidebar]].}}

=== Toolbox ===
The toolbox contains a selection of links which change depending on what type of page you are viewing.

On all pages (except special pages):
* ''What links here'' takes you to a special page that lists the pages on this wiki which contain a link to the current page. This is helpful when you are looking for pages of related information. The ''What links here'' information can also be useful when you are refactoring wiki pages and need to check whether links to this page are still relevant after changes in the current page.
* The ''Related changes'' tool lists all recent changes in the pages linked to from the current page. Recent changes to all relevant template pages are included in the resulting page list. The "Hide minor edits" option that can be set in the user [[Help:Preferences|preferences]] applies, among other things, to ''Related Changes''.

On all pages (including special pages):
* ''Upload file'' displays a special page that allows logged-in users to upload images and other files to the wiki. Uploaded files can be linked-from or embedded-in wiki pages. Uploading files, viewing files on the server, including them in wiki pages and managing the uploaded files is discussed in the [[Help:Managing files|managing files]] section of this manual. This is not displayed if file uploading has been disabled or not enabled in the first place.
{{Admin tip|tip=To enable file uploading someone with access to the MediaWiki installation files needs to edit the <code>LocalSettings.php</code> file and uncomment or add the option <code>$wgEnableUploads = true;</code>. Uploaded files will be stored in the images folder specified by the <code>$wgUploadPath</code> variable in the <code>LocalSettings.php</code>. This directory must be writable if file uploads is enabled. The [http://www.mediawiki.org/wiki/Manual:LocalSettings.php#Upload_location upload location] and [http://www.mediawiki.org/wiki/Manual:LocalSettings.php#Image_uploads image uploads] settings are described in more detail on the MetaWiki [http://www.mediawiki.org/wiki/Manual:LocalSettings.php LocalSettings.php] page.}}
* The ''Special pages'' tool lists the MediaWiki special pages. In MediaWiki terminology, a special page is one that presents information about the Wiki and/or allows access to administration activities for the wiki. For example, a list of users registered with the wiki, statistics about the wiki such as the number of pages and number of page edits, system logs, a list of orphaned pages, and so on. These special pages are commonly generated when the special page is loaded rather than being stored in the wiki database.

:''The function and use of the default special pages can be found in the special pages section of this manual.''

== Page Tabs ==
[[Image:M-en-pagetabs.png|framed|right|Default page tabs at the top of the page]]
The page tabs are displayed at the top of the article to the right of the site logo (if using the default MonoBook skin). These tabs allow you to perform actions or view pages that are related to the current article. The available default actions include: viewing, editing, and discussing the current article. The specific tabs displayed on your pages depend on whether or not you are logged into the wiki and whether you have sysop (administrator) privileges on the wiki. On special pages only the namespace tab is displayed.

;Default for all users
: ''[[Help:Namespaces|namespace]]'' (article, help, special page, template, user page etc.)
: ''discussion''
: ''edit'' (may be view source if anonymous editing is enabled, the page is in the MediaWiki namespace or the page is protected)
: ''history''

;Extra tabs for logged in users:
: ''move''
: ''watch''

;Extra tabs for sysops:
: ''protect''
: ''delete''

Extra tabs may be added, or some taken away, by wiki administrators using JavaScript or adding extensions so these may be different depending on which wiki you are using.

== User Links ==
[[Image:M-en-userlinks.png|framed|right|Default user links at the top right of the page]]
The user links are displayed at the top far right of the article (if using the default MonoBook skin). These tabs allow the logged-in user to view and edit their user page and wiki preferences. Additionally, the user links allow the user to quickly access their contributions to the wiki and logout.

For anonymous users the user links is replaced by a link to the wiki login page or, if enabled, a link to your ip address and your ip address's talk page.

* ''<username>''
*: This links to your user page which is where you can put information about yourself, store bits of information you want to remember or whatever else you fancy.
* ''my talk''
*: This links to your discussion page, where people can leave messages for you.
* ''preferences''
*: Allows you to change your personal site preferences.
* ''my watchlist''
*: A list of all pages that you are watching. Pages can be added to this list by clicking 'watch' at the top of the page.
* ''my contributions''
*: A list of all contributions you have made to the wiki.
* ''log out''
*: Click this link to log out of the wiki.

[[Category:Help|Navigation]]

Help:Navigation

2026-05-15T13:20:11Z

Slu: /* Navigation */

If you look at a page in MediaWiki, you'll find three main navigation elements: The sidebar on the left gives you access to important pages in the Wiki like recent changes or file upload. At the top of the page are the links which belong to the page currently displayed: its associated discussion page, the version history, and - most notably - the edit link. In the top right corner you'll find, as an anonymous user, the link to create an account and login (they are on the same page). As a logged-in user you have a collection of personal links, like the one to your user page or your preferences.

== Sidebar ==
[[Image:M-en-sidebar.png|framed|right|Example sidebar, shown on the left of the page]]
The sidebar is displayed on the left edge of the page below the site logo (if using the default MonoBook skin). This sidebar gives you access to important pages in the Wiki like recent changes or file upload.

=== Navigation ===
A click on the logo brings you back to the start page of the wiki. The links take you to important pages in the wiki, they can be configured by site administrators of the individual wikis

{{Admin tip|tip=You can customize the links in the navigation section via [[Special:Allmessages]]. Or create a menu on your own in [[MediaWiki:Sidebar]].}}

=== Toolbox ===
The toolbox contains a selection of links which change depending on what type of page you are viewing.

On all pages (except special pages):
* ''What links here'' takes you to a special page that lists the pages on this wiki which contain a link to the current page. This is helpful when you are looking for pages of related information. The ''What links here'' information can also be useful when you are refactoring wiki pages and need to check whether links to this page are still relevant after changes in the current page.
* The ''Related changes'' tool lists all recent changes in the pages linked to from the current page. Recent changes to all relevant template pages are included in the resulting page list. The "Hide minor edits" option that can be set in the user [[Help:Preferences|preferences]] applies, among other things, to ''Related Changes''.

On all pages (including special pages):
* ''Upload file'' displays a special page that allows logged-in users to upload images and other files to the wiki. Uploaded files can be linked-from or embedded-in wiki pages. Uploading files, viewing files on the server, including them in wiki pages and managing the uploaded files is discussed in the [[Help:Managing files|managing files]] section of this manual. This is not displayed if file uploading has been disabled or not enabled in the first place.
{{Admin tip|tip=To enable file uploading someone with access to the MediaWiki installation files needs to edit the <code>LocalSettings.php</code> file and uncomment or add the option <code>$wgEnableUploads = true;</code>. Uploaded files will be stored in the images folder specified by the <code>$wgUploadPath</code> variable in the <code>LocalSettings.php</code>. This directory must be writable if file uploads is enabled. The [http://www.mediawiki.org/wiki/Manual:LocalSettings.php#Upload_location upload location] and [http://www.mediawiki.org/wiki/Manual:LocalSettings.php#Image_uploads image uploads] settings are described in more detail on the MetaWiki [http://www.mediawiki.org/wiki/Manual:LocalSettings.php LocalSettings.php] page.}}
* The ''Special pages'' tool lists the MediaWiki special pages. In MediaWiki terminology, a special page is one that presents information about the Wiki and/or allows access to administration activities for the wiki. For example, a list of users registered with the wiki, statistics about the wiki such as the number of pages and number of page edits, system logs, a list of orphaned pages, and so on. These special pages are commonly generated when the special page is loaded rather than being stored in the wiki database.

:''The function and use of the default special pages can be found in the [[Help:Special pages|special pages]] section of this manual.''

== Page Tabs ==
[[Image:M-en-pagetabs.png|framed|right|Default page tabs at the top of the page]]
The page tabs are displayed at the top of the article to the right of the site logo (if using the default MonoBook skin). These tabs allow you to perform actions or view pages that are related to the current article. The available default actions include: viewing, editing, and discussing the current article. The specific tabs displayed on your pages depend on whether or not you are logged into the wiki and whether you have sysop (administrator) privileges on the wiki. On special pages only the namespace tab is displayed.

;Default for all users
: ''[[Help:Namespaces|namespace]]'' (article, help, special page, template, user page etc.)
: ''discussion''
: ''edit'' (may be view source if anonymous editing is enabled, the page is in the MediaWiki namespace or the page is protected)
: ''history''

;Extra tabs for logged in users:
: ''move''
: ''watch''

;Extra tabs for sysops:
: ''protect''
: ''delete''

Extra tabs may be added, or some taken away, by wiki administrators using JavaScript or adding extensions so these may be different depending on which wiki you are using.

== User Links ==
[[Image:M-en-userlinks.png|framed|right|Default user links at the top right of the page]]
The user links are displayed at the top far right of the article (if using the default MonoBook skin). These tabs allow the logged-in user to view and edit their user page and wiki preferences. Additionally, the user links allow the user to quickly access their contributions to the wiki and logout.

For anonymous users the user links is replaced by a link to the wiki login page or, if enabled, a link to your ip address and your ip address's talk page.

* ''<username>''
*: This links to your user page which is where you can put information about yourself, store bits of information you want to remember or whatever else you fancy.
* ''my talk''
*: This links to your discussion page, where people can leave messages for you.
* ''preferences''
*: Allows you to change your personal site preferences.
* ''my watchlist''
*: A list of all pages that you are watching. Pages can be added to this list by clicking 'watch' at the top of the page.
* ''my contributions''
*: A list of all contributions you have made to the wiki.
* ''log out''
*: Click this link to log out of the wiki.

[[Category:Help|Navigation]]