innovaphone wiki - Recent changes [en]

Reference16r1:Concept App Platform

Hawk — Fri, 30 Oct 2026 16:47:49 GMT

Change IP Addresses / DNS Names / System Name

← Older revision		Revision as of 17:47, 30 October 2026
Line 786:		Line 786:
	If you want to change the System Name or the DNS Name of the PBX and/or App Platform Platform you must change records manually '''in the described order'''!		If you want to change the System Name or the DNS Name of the PBX and/or App Platform Platform you must change records manually '''in the described order'''!
	You have to know the Admin password to directly Login to the App Platform .		You have to know the Admin password to directly Login to the App Platform .

			Reverse Proxy

			General / Deviceregistration

			''- Devices app URL and domainname''

	=== App Platform ===		=== App Platform ===
	; Settings - General		; Settings - General
	* ''Devices app URL''		* ''Devices app URL and domainname''
	* ''App platform DNS name''		* ''App platform DNS name''

Reference14r2:PBX/Objects/Conference

Jbi — Fri, 30 Oct 2026 15:52:56 GMT

← Older revision		Revision as of 16:52, 30 October 2026
Line 82:		Line 82:

	'''Note:''' Overlap dialing to the operator number is not supported. You must dial the complete number (Conference Object Number + Operator Number) in one step (en-bloc dialing).		'''Note:''' Overlap dialing to the operator number is not supported. You must dial the complete number (Conference Object Number + Operator Number) in one step (en-bloc dialing).
			== Apps ==
			In the App tab, the Virtual Background app is ticked automatically when the Virtual Background service is installed and a Conference object exists.

			'''Note:''' You can check here whether the Virtual Background app is enabled.

	== Announcements ==		== Announcements ==

Reference14r2:PBX/Objects/Conference

Jbi — Fri, 30 Oct 2026 15:44:07 GMT

Created page with "The PBX conference object manages conference rooms, including announcements and PIN protection. Conference calls are handled by one or more ''conference servers (MCUs)'' registered as devices to this object. If multiple conference servers are used, different media types can be handled by different servers. innovaphone conference interfaces (CONF/SCNF) can also be registered to this object to provide audio, video and application sharing conferences. == General Configura..."

New page

The PBX conference object manages conference rooms, including announcements and PIN protection.

Conference calls are handled by one or more ''conference servers (MCUs)'' registered as devices to this object. If multiple conference servers are used, different media types can be handled by different servers.
innovaphone conference interfaces (CONF/SCNF) can also be registered to this object to provide audio, video and application sharing conferences.

== General Configuration ==
Information about general configuration options shared by all PBX objects can be found at [[{{NAMESPACE}}:PBX/Objects]].
== Devices ==
; Hardware Id
: The hardware ID must correspond to the hardware ID of a device listed on the object's General page (not the Gateway). The device is registered to this object and provides the conference service.
; innovaphone device
: Tick this option if the MCU is an innovaphone device.
; Media Types
: When a media type is selected, calls to the registration include that media type.
; Channels Licenses
: Use the PBX Channel Licenses to enable conference functionality. This option can be enabled via the Conference Plugin in the Settings App.
; Number of channels
: Specifies the number of channels available on the MCU device or the maximum number of channels to be used. If left empty, the value is 0 (no channels).
; MCU Room Numbers
: If the device is not an innovaphone device and has multiple rooms, the room numbers to dial can be configured here.
; Registration
: If a registration exists for this hardware ID, the registrar's IP address is displayed here.

== Options ==
; Announcement URL
: The URL used to store the announcements. In this URL, <code>$type</code> is automatically replaced with the announcement type. For example: ''<code>http://127.0.0.1/webdav/conference/$type.$coder?coder=g722,g711u,g711a,g723,g729,opus-nb,opus-wb</code>''. The available announcement types are listed in the [https://wiki.innovaphone.com/index.php?title=Reference13r1:PBX/Objects/Conference#Announcements Announcements section].
; Extern Announcement Name/No
: By default, the conference object uses its internal HTTP interface for announcements. You can also use an external destination. Enter its name or number here.
; Room number length
: If the room number length is set to zero, only one room is available. Otherwise, static rooms can be configured and temporary rooms can be created by the operator.
; PIN
: If the room number length is set to zero, you can set the PIN for the conference room here. The PIN can be empty or defined with four digits.
; Operator enabled
: If ticked, the operator is enabled and can be reached when no room number is dialed.
; International Number
: If an international number is configured, the conference invitation generated by the Conference App includes the international number, followed by the conference object number and the conference room number. It also includes the internal SIP dialing information. If no international number is configured, no dialing information is shown in the invitation.
; Trace
:If ticked, tracing is enabled for this PBX object.

== Rooms ==
Up to ''30'' static rooms can be configured.
When the first participant joins a room, the room is opened and the configured number of channels is reserved for it. These channels are then available for the other participants joining the room. All selected media types must also be available when the room is opened. Otherwise, the room cannot be opened. When the last participant leaves the room, the reserved channels are released.

A room is defined by:
; Room number
: The room number must be unique. Its length depends on the ''Room number length'' option.
; Number of channels
: This is the number of channels configured on the Device tab. When the first participant joins the room, the configured number of channels is reserved for the room, provided that enough channels are available on the MCU to open it.
: Each additional participant uses one of the reserved channels. If all reserved channels are in use, additional participants can still join as long as channels are available on the MCU.
: If no channels are available on the MCU, the room cannot be opened. If all available channels are reserved or in use across all rooms, no additional rooms or participants can use them.
; Media types
: The ticked media types are used for the calls. All selected media types must be available when the room is opened. Otherwise, the room cannot be opened.
: If the H.264 video codec is not selected, it is removed from the call. The same applies to the VP8 video codec. This filtering takes place before the call is forwarded to the MCU.
; Display Name
: The name of the conference room. This name can be used to search for and call the room. It is also used as the name of the corresponding Conference App.
; Meeting Feature
: Defines which meeting features are available in the Conference App:
:* ''Meeting allowed'': Displays the invitation information for the permanent conference room and allows users to create temporary conferences.
:* ''Meeting not allowed'': Displays only the invitation information for the permanent conference room.
:* ''Only Meetings'': Displays only the option to create temporary conferences.
; PIN
: The room PIN can be empty or must contain four digits. The PIN cannot be included in the dialed number.

== Operator ==
If the operator is enabled, users can dial the operator number to create temporary conference rooms (ad-hoc rooms). When a new room is created, the requested number of channels is reserved for this room. These channels remain reserved until the last participant leaves the room.

; Operator Number
: The number used to access the operator menu. It must be different from all permanent room numbers. The system also checks that new ad-hoc room numbers do not match this number.
: '''If no operator number is configured, calls to the conference object are routed directly to the operator.'''
; PIN
: The PIN required to access the operator. It can be empty or must contain four digits. The PIN cannot be part of the dialing number.
; Media Types for ad-hoc rooms
: Defines the media types used for ad-hoc rooms.
: A room can still be created if some of the selected media types are not available. However, audio channels must be available.
: If the H.264 video codec is not selected, it is removed from the call. The same applies to the VP8 video codec. This filtering takes place before the call is forwarded to the MCU.
; IVR Menu
: The operator menu guides the user through the following steps:
:* Enter the PIN to access the operator.
:* Enter the room number. The number of digits depends on the configured ''Room number length''.
:* Enter the number of channels to reserve, followed by #.
:* Enter a four-digit PIN for the room, followed by #. To create a room without a PIN, press # only.

'''Note:''' Overlap dialing to the operator number is not supported. You must dial the complete number (Conference Object Number + Operator Number) in one step (en-bloc dialing).

== Announcements ==
For a list of supported announcements, please refer to [[{{NAMESPACE}}:PBX/Objects/Conference/Announcement types|Reference15r1:PBX/Objects/Conference/Announcement_types]].

'''Note:''' The available announcements can be customized and recorded again if needed.

== Notifications ==
To notify participants when someone joins the room, you can play a simple DTMF tone instead of the standard announcement. This is configured in the routing table.
Use the configuration shown below:

[[image:conf_interface_notification.png|/Conf_interface_notification.png]]

'''Note:''' This does not apply to software conference interfaces (SCNF), as they do not support DTMF sequence generation.
[[Category:Concept Conference]]

Reference13r1:PBX/Objects/Conference

Muschelpuster — Fri, 30 Oct 2026 11:50:18 GMT

Rooms: The description of the Cahnnels topic weas confusing. Hopefully it's now more clear.

← Older revision		Revision as of 12:50, 30 October 2026
Line 42:		Line 42:
	: The room number must be unique; it length depends on the room number length option.		: The room number must be unique; it length depends on the room number length option.
	; Number of channels		; Number of channels
	: The number of channels which must be available to open a room at dial-in. If this count ~~of member~~ is reached, the room is full and no ~~further caller~~ can ~~take part~~.		: The number of configured channels on the Device topic, which must be available to open a room at dial-in. If this channel count is reached across all rooms, the room is full, and nobody can use it. If not, the 1st caller in the room occupies all configured channels to reserve channels for the configured number of channels for the room. Every additional caller uses one of the occupied channels. If no channels are free, the next callers can still enter the room if channels are free overall.
	; Media types		; Media types
	: If a media type is ticked, it is used for the call. If not all ticked media types are available at dial-in, the room can't be opened.		: If a media type is ticked, it is used for the call. If not all ticked media types are available at dial-in, the room can't be opened.

User:Jksrt

Jksrt — Fri, 30 Oct 2026 09:23:39 GMT

User account Jksrt was created

Reference13r1:PBX/Objects/Conference

Jbi — Thu, 29 Oct 2026 14:52:50 GMT

Announcements

← Older revision		Revision as of 15:52, 29 October 2026
Line 68:		Line 68:

	== Announcements ==		== Announcements ==
	For the supported announcements, please refer to [[{{NAMESPACE}}:PBX/Objects/Conference/Announcement types\|~~Reference13r1~~:PBX/Objects/Conference/~~Announcement types~~]].		For the supported announcements, please refer to [[{{NAMESPACE}}:PBX/Objects/Conference/Announcement types\|Reference15r1:PBX/Objects/Conference/Announcement_types]].

	== Notifications ==		== Notifications ==

User:CatfishKeith

CatfishKeith — Thu, 29 Oct 2026 12:39:47 GMT

User account CatfishKeith was created

Support:IP270 fix mac address memory

Lmi — Thu, 29 Oct 2026 10:54:51 GMT

Reference9:Concept USB Headset

Vsc — Thu, 29 Oct 2026 08:46:01 GMT

EPOS IMPACT 1060T ANC - BT Headset with EPOS BTD 800 III Dongle (Art. No. 1001163, Headset ID=0186 | Dongle ID=0189)

← Older revision		Revision as of 09:46, 29 October 2026
Line 2,833:		Line 2,833:
	<br/>		<br/>

			====='''EPOS IMPACT 500 MS UC ANC WL - BT Headset with EPOS BTD 900c Dongle (Art. No. 1001490, Headset ID=0190\| Dongle ID=0881)'''=====
			Call Control operational in wireless connection mode (IP270 since PhonePlatform Build 2231)
	====='''EPOS IMPACT 1060T ANC - BT Headset with EPOS BTD 800 III Dongle (Art. No. 1001163, Headset ID=0186 \| Dongle ID=0189)'''=====		====='''EPOS IMPACT 1060T ANC - BT Headset with EPOS BTD 800 III Dongle (Art. No. 1001163, Headset ID=0186 \| Dongle ID=0189)'''=====
	(since v13r2sr24, v14r1sr11, v14r2sr7) <br/>		(since v13r2sr24, v14r1sr11, v14r2sr7) <br/>

User:Wyatt James

Wyatt James — Wed, 28 Oct 2026 13:41:23 GMT

User account Wyatt James was created

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

Gigaset Dennis — Wed, 28 Oct 2026 10:33:10 GMT

provisioning parameters in XML format

← Older revision		Revision as of 11:33, 28 October 2026
Line 1:		Line 1:
	[[Image:Gigaset-logo.png\|200px\|right\|~~/Gigaset~~-logo.png\|gigaset-logo.png/]]		[[Image:Gigaset-logo.png\|200px\|right\|gigaset-logo.png/\|gigaset-logo.png/]]

	==Product Name==		==Product Name==
	<!-- Mandatory topic. -->		<!-- Mandatory topic. -->
	<!-- replace CompanyName & ProductName by real names and add URL to productpage -->[[File:DECT ProvAPP logo.png\|100x100px\|~~/DECT_ProvAPP_logo~~.png\|dect_provapp_logo.png/]] [https://www.gigaset.com Gigaset] Gigaset-Provisioning-App		<!-- replace CompanyName & ProductName by real names and add URL to productpage -->[[File:DECT ProvAPP logo.png\|100x100px\|dect_provapp_logo.png/\|dect_provapp_logo.png/]] [https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

	==Certification Status==		==Certification Status==
Line 23:		Line 23:

	<!-- Place optional company logo. Don't change logo size. -->		<!-- Place optional company logo. Don't change logo size. -->
	[[Image:Gigaset-LOGO.png\|150px\|~~/Gigaset~~-~~LOGO~~.png\|gigaset-logo.png/]]		[[Image:Gigaset-LOGO.png\|150px\|gigaset-logo.png/\|gigaset-logo.png/]]

	<!-- Give some introducting words about the vendor itself. -->		<!-- Give some introducting words about the vendor itself. -->
Line 45:		Line 45:
	</tr>		</tr>
	<tr>		<tr>
	<td><b><font size=3px>N870</font></b><br>[[Image:N870.png‎\|250px\|~~/N870~~.png\|n870.png/]]</td>		<td><b><font size=3px>N870</font></b><br>[[Image:N870.png‎\|250px\|n870.png/\|n870.png/]]</td>
	<td>		<td>
	- IP DECT Multicell System<br>		- IP DECT Multicell System<br>
Line 55:		Line 55:
	<p></p><br>		<p></p><br>
	<td></td>		<td></td>
	<td><b><font size=3px>N670</font></b><br>[[Image:N670_Mini_Multicell_EN.png‎\|250px\|~~/N670_Mini_Multicell_EN~~.png\|n670_mini_multicell_en.png/]]</td>		<td><b><font size=3px>N670</font></b><br>[[Image:N670_Mini_Multicell_EN.png‎\|250px\|n670_mini_multicell_en.png/\|n670_mini_multicell_en.png/]]</td>
	<td>		<td>
	- IP DECT Singlecell and Mini-Multicell System<br>		- IP DECT Singlecell and Mini-Multicell System<br>
Line 240:		Line 240:

	<gallery>		<gallery>
	Innovaphone GigasetApp Admin2.0 HTTP.png\|~~/Innovaphone_GigasetApp_Admin2~~.~~0_HTTP~~.png\|innovaphone_gigasetapp_admin2.0_http.png/		Innovaphone GigasetApp Admin2.0 HTTP.png\|innovaphone_gigasetapp_admin2.0_http.png/\|innovaphone_gigasetapp_admin2.0_http.png/
	Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png\|~~/Innovaphone_GigasetApp_Admin2~~.~~0_SIP_RVP_TLS~~.png\|innovaphone_gigasetapp_admin2.0_sip_rvp_tls.png/		Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png\|innovaphone_gigasetapp_admin2.0_sip_rvp_tls.png/\|innovaphone_gigasetapp_admin2.0_sip_rvp_tls.png/
	</gallery>		</gallery>

	{\| class="wikitable" style="margin-top:auto;margin-top: 0px;"		{\| class="wikitable" style="margin-top:auto;margin-top: 0px;"
	\|		\|
	[[File:Innovaphone gigasetapp http.png\|alt=innovaphone_gigasetapp_http\|~~/Innovaphone_gigasetapp_http~~.png\|innovaphone_gigasetapp_http.png/]]		[[File:Innovaphone gigasetapp http.png\|alt=innovaphone_gigasetapp_http\|innovaphone_gigasetapp_http.png/\|innovaphone_gigasetapp_http.png/]]
	\|		\|
	[[File:Innovaphone gigasetapp sip tls rp.png\|alt=innovaphone_gigasetapp_sip_rvp_tls\|~~/Innovaphone_gigasetapp_sip_tls_rp~~.png\|innovaphone_gigasetapp_sip_tls_rp.png/]]		[[File:Innovaphone gigasetapp sip tls rp.png\|alt=innovaphone_gigasetapp_sip_rvp_tls\|innovaphone_gigasetapp_sip_tls_rp.png/\|innovaphone_gigasetapp_sip_tls_rp.png/]]
	\|}		\|}
	<br>		<br>
Line 267:		Line 267:
	or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.		or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

	[[Image:innovaphone_GigasetApp_User.png\|~~/Innovaphone_GigasetApp_User~~.png\|innovaphone_gigasetapp_user.png/]]		[[Image:innovaphone_GigasetApp_User.png\|innovaphone_gigasetapp_user.png/\|innovaphone_gigasetapp_user.png/]]


Line 276:		Line 276:
	From 136097 onwards we added the possibilty to activate Reverse Proxy support for multiple instances directly in the settings. see chapter below.		From 136097 onwards we added the possibilty to activate Reverse Proxy support for multiple instances directly in the settings. see chapter below.

	[[Image:Gigaset-rvp-all.png\|~~/Gigaset~~-rvp-all.png\|gigaset-rvp-all.png/]]		[[Image:Gigaset-rvp-all.png\|gigaset-rvp-all.png/\|gigaset-rvp-all.png/]]

	===Multiple Instances===		===Multiple Instances===
Line 284:		Line 284:
	If the local SIP port of the app is e.g. 5062, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. Therefore you can now activate ''"Enable Reverse Proxy Support"'' and enter seperate Ports for Connecting to the Reverse Proxy and connecting from Reverse Proxy to the APP Platform.<br>The Port must be unique and must not be assigned twice. Don't forget to forward the Port in Reverse Proxy from 5060/5061 to your configured Port.		If the local SIP port of the app is e.g. 5062, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. Therefore you can now activate ''"Enable Reverse Proxy Support"'' and enter seperate Ports for Connecting to the Reverse Proxy and connecting from Reverse Proxy to the APP Platform.<br>The Port must be unique and must not be assigned twice. Don't forget to forward the Port in Reverse Proxy from 5060/5061 to your configured Port.

	[[File:Innovaphone gigasetapp rp-port example.png\|~~/Innovaphone_gigasetapp_rp~~-port_example.png\|innovaphone_gigasetapp_rp-port_example.png/]]		[[File:Innovaphone gigasetapp rp-port example.png\|innovaphone_gigasetapp_rp-port_example.png/\|innovaphone_gigasetapp_rp-port_example.png/]]
	<br><br>		<br><br>

Line 290:		Line 290:
	After activating directory synchronisation you have the possibility to activate and configure thre sources simultaneously: innovaphone LDAP directory, any other LDAP directory and innovaphone myContacts APP.		After activating directory synchronisation you have the possibility to activate and configure thre sources simultaneously: innovaphone LDAP directory, any other LDAP directory and innovaphone myContacts APP.

	[[File:Innovaphone gigasetapp ldaplokal.png\|frameless\|580x580px\|~~/Innovaphone_gigasetapp_ldaplokal~~.png\|innovaphone_gigasetapp_ldaplokal.png/]]		[[File:Innovaphone gigasetapp ldaplokal.png\|frameless\|580x580px\|innovaphone_gigasetapp_ldaplokal.png/\|innovaphone_gigasetapp_ldaplokal.png/]]

	fill in the needed data like host, Port and Credentials.		fill in the needed data like host, Port and Credentials.
Line 296:		Line 296:
	After all phonebooks, and maybee Gigaset Feature Controll App, are configured you can choose which ones will be used for phonebook key, INT key and Reverse Lookup.		After all phonebooks, and maybee Gigaset Feature Controll App, are configured you can choose which ones will be used for phonebook key, INT key and Reverse Lookup.

	[[File:Innovaphone gigasetapp directory settings.png\|frameless\|580x580px\|~~/Innovaphone_gigasetapp_directory_settings~~.png\|innovaphone_gigasetapp_directory_settings.png/]]		[[File:Innovaphone gigasetapp directory settings.png\|frameless\|580x580px\|innovaphone_gigasetapp_directory_settings.png/\|innovaphone_gigasetapp_directory_settings.png/]]

	===Contacts APP===		===Contacts APP===
Line 315:		Line 315:
	* all other entries as shown in below screenshot are preconfigured		* all other entries as shown in below screenshot are preconfigured

	[[File:Innovaphone gigasetapp mycontacts.png\|1182x1182px\|~~/Innovaphone_gigasetapp_mycontacts~~.png\|innovaphone_gigasetapp_mycontacts.png/]]		[[File:Innovaphone gigasetapp mycontacts.png\|1182x1182px\|innovaphone_gigasetapp_mycontacts.png/\|innovaphone_gigasetapp_mycontacts.png/]]

	[[Image:PBX Manager Contacts Parameter.png\|750px\|~~/PBX_Manager_Contacts_Parameter~~.png\|pbx_manager_contacts_parameter.png/]]<br>		[[Image:PBX Manager Contacts Parameter.png\|750px\|pbx_manager_contacts_parameter.png/\|pbx_manager_contacts_parameter.png/]]<br>

	===Forward lookup on different Nodes===		===Forward lookup on different Nodes===
Line 326:		Line 326:
	It's important here to also define the guid for the Users, this Configuration will look like this then:		It's important here to also define the guid for the Users, this Configuration will look like this then:

	[[Image:gigaset-forward-lookup-nodes.png\|750px\|~~/Gigaset~~-forward-lookup-nodes.png\|gigaset-forward-lookup-nodes.png/]]<br>		[[Image:gigaset-forward-lookup-nodes.png\|750px\|gigaset-forward-lookup-nodes.png/\|gigaset-forward-lookup-nodes.png/]]<br>

	At last: You have to set the phone book PBX as your target phone book at the phone book settings		At last: You have to set the phone book PBX as your target phone book at the phone book settings

Howto:Gigaset-DeskPhone-App - Gigaset - Partner App

Gigaset Dennis — Wed, 28 Oct 2026 10:30:18 GMT

phone book settings

← Older revision		Revision as of 11:30, 28 October 2026
Line 372:		Line 372:
	==== custom provisioning settings ====		==== custom provisioning settings ====
	You have the possibility to add provisioning parameters by your own in xml strings. You can find an overview of provisioning parameters here:<br>		You have the possibility to add provisioning parameters by your own in xml strings. You can find an overview of provisioning parameters here:<br>
	'''[https://~~teamwork~~.gigaset.com/~~gigawiki~~/~~display~~/GPPPO/FAQ+-~~+Auto+provisioning~~%~~3A+Parameters~~ Gigaset Desktop Phone Settings] <br>'''		'''[https://pro-wiki.gigaset.com/bin/view/GPPPO/Products/Desktop%20IP%20PRO/FAQ%20Desktop%20-%20Settings/ Gigaset Desktop Phone Settings] <br>'''

	[[File:DeskPhone custom settings.png\|frameless\|545x545px\|deskphone_custom_settings.png/\|deskphone_custom_settings.png/]]		[[File:DeskPhone custom settings.png\|frameless\|545x545px\|deskphone_custom_settings.png/\|deskphone_custom_settings.png/]]

Reference13r3:Concept Softphone Redundancy

Vsc — Wed, 28 Oct 2026 10:26:45 GMT

← Older revision		Revision as of 11:26, 28 October 2026
Line 14:		Line 14:
	;phys: Explicit physical location, if configured.		;phys: Explicit physical location, if configured.

	See [[~~Reference13r3~~:Concept_myApps_Redundancy#Published_information_for_the_softphone_app]] ~~for details~~.		See generic article about myApps-Redundancy for [[Reference16r1:Concept_myApps_Redundancy#Published_information_for_the_softphone_app\|for details on softphone redundancy]].

	=== Explicit physical location ===		=== Explicit physical location ===
	* For configuration in the myApps launcher, see [[~~Reference13r3~~:Concept_myApps_platform_services#Server_configuration]].		* For configuration in the myApps launcher, see [[Reference16r1:Concept_myApps_platform_services#Server_configuration]].
	* For configuration in the browser using a URL parameters, see [[~~Reference13r3~~:Concept_myApps#Supported_URL_Parameters]].		* For configuration in the browser using a URL parameters, see [[Reference16r1:Concept_myApps#Supported_URL_Parameters]].

	== Registration ==		== Registration ==

User:Afoeldi

Afoeldi — Wed, 28 Oct 2026 08:26:14 GMT

User account Afoeldi was created

Reference14r2:MyApps Plugin for Virtual Desktops

Smayoral — Tue, 27 Oct 2026 17:25:55 GMT

Applies To

← Older revision		Revision as of 18:25, 27 October 2026
Line 9:		Line 9:
	== Applies To ==		== Applies To ==
	* innovaphone PBX from version 14r2		* innovaphone PBX from version 14r2
	* Client OS: Windows, Linux<ref>VDI Plugin for Linux only connects to Citrix or VMWare Horizon, RDP ~~still not supported~~</ref>(Ubuntu 22 or 23, RangeeOS<ref>RangeeOS is listed due to a customer testimonial. No tests have been conducted by innovaphone. Tests were done using myapps 14r2sr3, RangeeOS Firmware 12.00 build 203 ff and Citrix Workspace 2311. (Workspace version 2402 & 2405 have a bug with USB redirection and 2408 is not starting reliably)</ref>, IGEL OS<ref>IGEL OS: available at [https://app.igel.com/myAppsPlugin/15.1.455+1 IGEL App Portal]</ref>) or MacOS operating systems		* Client OS: Windows, Linux<ref>VDI Plugin for Linux only connects to Citrix, VMWare Horizon or RDP </ref>(Ubuntu 22 or 23, RangeeOS<ref>RangeeOS is listed due to a customer testimonial. No tests have been conducted by innovaphone. Tests were done using myapps 14r2sr3, RangeeOS Firmware 12.00 build 203 ff and Citrix Workspace 2311. (Workspace version 2402 & 2405 have a bug with USB redirection and 2408 is not starting reliably)</ref>, IGEL OS<ref>IGEL OS: available at [https://app.igel.com/myAppsPlugin/15.1.455+1 IGEL App Portal]</ref>) or MacOS operating systems
	* Hypervisor OS: Citrix, Windows Terminal Server environments and VMWare Horizon<ref>VMWare Horizon OS is listed due to a customer testimonial. No tests have been conducted by innovaphone.</ref><br />		* Hypervisor OS: Citrix, Windows Terminal Server environments and VMWare Horizon<ref>VMWare Horizon OS is listed due to a customer testimonial. No tests have been conducted by innovaphone.</ref><br />
	<references/>		<references/>
Line 40:		Line 40:

	=== Audio transmission ===		=== Audio transmission ===
	The plugin connects Audio, ICE and DTLS directly to the other endpoint.<br>Since Audio itself does not use virtual channels, the plugin on the client must be able [[Howto:~~What_Ports_are_used_for_Signaling_and_Voice_Traffic_in_SIP_and_H~~.323~~%3F~~#~~ICE_STUN_TURN~~\|to reach the TURN/STUN server via port 3478]].		The plugin connects Audio, ICE and DTLS directly to the other endpoint.<br>Since Audio itself does not use virtual channels, the plugin on the client must be able [[Howto:What Ports are used for Signaling and Voice Traffic in SIP and H.323?#ICE STUN TURN\|to reach the TURN/STUN server via port 3478]].

	== Configuration ==		== Configuration ==

Reference15r1:Concept App Service Recordings

She — Tue, 27 Oct 2026 11:18:49 GMT

← Older revision		Revision as of 12:18, 27 October 2026
(One intermediate revision by the same user not shown)
Line 201:		Line 201:
	When using newer versions of WinSCP, authentication to the WebDAV directory of recordings fails.		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.		Workaround: An older version of WinSCP must be used. The last working version is WinSCP V6.3.7.

			=== Wrong owner for recordings made via DECT ===
			A DECT base station (e.g. IP1202) puts its own RFPI into the recording file name instead of the handset’s H.323 name. Reporting therefore can’t match the recording to the DECT user and uses the first connected user instead, which is often the internal caller. If that user has no recording license (e.g. an analog extension), the recording is marked unlicensed and can’t be played back. If all participants are licensed, the recording plays back but may still be assigned to the wrong user.

Reference15r1:Concept App Service Recordings

Jbi — Tue, 27 Oct 2026 09:34:39 GMT

Call Recording Storage

← Older revision		Revision as of 10:34, 27 October 2026
Line 140:		Line 140:

	=== Call Recording Storage ===		=== Call Recording Storage ===
	~~If a~~ 60 second ~~Call with Codec~~ G.711 ~~is recorded, it will take approx.~~ 1.5 ~~MegaByte memory~~.		A 60-second call recorded using the G.711 codec requires approximately 1.5 MB of storage.

	=== Licensing ===		=== Licensing ===

Reference16r1:Concept App Service IP

Dde — Tue, 27 Oct 2026 07:38:44 GMT

Functional Distinction from a Gateway or an IPVA

← Older revision		Revision as of 08:38, 27 October 2026
Line 74:		Line 74:
	The following features are not available:		The following features are not available:
	* Additional Administrator Accounts under General/Admin		* Additional Administrator Accounts under General/Admin
			** with the release of the new advanced UI, additional accounts will be available inside the App IP too (also merged into 16r1 at some time)
	* PBX users with "additional user rights" and an associated login to the advanced UI		* PBX users with "additional user rights" and an associated login to the advanced UI
	* SOAP (currently)		* SOAP (currently)
			** SOAP is now available with the main admin user (and later for additional administrator accounts too)

	==Troubleshooting==		==Troubleshooting==

User:Timowieczorek

Timowieczorek — Mon, 26 Oct 2026 14:45:39 GMT

User account Timowieczorek was created

User:Anonymus wiki

Anonymus wiki — Mon, 26 Oct 2026 14:41:29 GMT

User account Anonymus wiki was created

Reference15r1:Concept App Service Connector for Microsoft 365

Tfu — Mon, 26 Oct 2026 11:03:42 GMT

Calendar Presence

← Older revision		Revision as of 12:03, 26 October 2026
Line 139:		Line 139:
	* Event subscriptions are renewed every day.		* Event subscriptions are renewed every day.
	* License Check is made every hour.		* License Check is made every hour.
			* Synchronization is limited to events within the next 72 hours. The calendar data is refreshed once every 24 hours, so events further in the future are only synchronized with the first daily refresh after they fall into this 72-hour window.

	== Related Articles ==		== Related Articles ==

Reference16r1:Concept App Service Connector for Microsoft 365

Tfu — Mon, 26 Oct 2026 11:03:11 GMT

Technical Overview

← Older revision		Revision as of 12:03, 26 October 2026
Line 142:		Line 142:
	* Event subscriptions are renewed every day.		* Event subscriptions are renewed every day.
	* License Check is made every hour.		* License Check is made every hour.
			* Synchronization is limited to events within the next 72 hours. The calendar data is refreshed once every 24 hours, so events further in the future are only synchronized with the first daily refresh after they fall into this 72-hour window.

	=== Contact Search ===		=== Contact Search ===

Reference15r1:Concept IP29-20

Vsc — Mon, 26 Oct 2026 07:07:34 GMT

Direct terminal connection

← Older revision		Revision as of 08:07, 26 October 2026
Line 86:		Line 86:


	Next to own assembling, below listed ~~are some~~ 3rd-party-~~products~~ (information is subject ot change):		Next to own assembling, below listed is a 3rd-party-product (information is subject ot change):
	* [~~http~~://~~www~~.logilink.~~org~~/~~Produkte_LogiLink~~/~~Passive_Netzwerkkomponenten/Telefonzubehoer/Modular_Adapter~~-4-~~Port.htm?seticlanguage=en LogiLink~~-~~Adapter]~~		* [https://shop.logilink.com/products/logilink-modular-adapter-4-port-telefonsplitter-rj45-rj11?variant=50507797561670 LogiLink-Adapter]
	* [https://www.l-~~com.com/ethernet~~-~~tia568b~~-~~splitter~~-~~8x8-plug-4-6x2-jacks L-Com~~-Adapter]

	[[Image:ll_adapter_8p8c_6p2c.png\|300px\|ll_adapter_8p8c_6p2c.png/]]		[[Image:ll_adapter_8p8c_6p2c.png\|300px\|ll_adapter_8p8c_6p2c.png/]]

Reference13r1:Concept IP29-20

Vsc — Mon, 26 Oct 2026 07:03:36 GMT

Direct terminal connection

← Older revision		Revision as of 08:03, 26 October 2026
Line 85:		Line 85:


	Next to own assembling, below listed ~~are some~~ 3rd-party-~~products~~ (information is subject ot change):		Next to own assembling, below listed is a 3rd-party-product (information is subject ot change):
	* [~~http~~://~~www~~.logilink.~~org~~/~~Produkte_LogiLink~~/~~Passive_Netzwerkkomponenten/Telefonzubehoer/Modular_Adapter~~-4-~~Port.htm?seticlanguage=en LogiLink~~-~~Adapter]~~		* [https://shop.logilink.com/products/logilink-modular-adapter-4-port-telefonsplitter-rj45-rj11?variant=50507797561670 LogiLink-Adapter]
	* [https://www.l-~~com.com/ethernet~~-~~tia568b~~-~~splitter~~-~~8x8-plug-4-6x2-jacks L-Com~~-Adapter]

	[[Image:ll_adapter_8p8c_6p2c.png\|300px\|ll_adapter_8p8c_6p2c.png/]]		[[Image:ll_adapter_8p8c_6p2c.png\|300px\|ll_adapter_8p8c_6p2c.png/]]