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/]]

Reference12r1:Interfaces/FXS/Advanced

Vsc — Thu, 22 Oct 2026 12:16:18 GMT

← Older revision		Revision as of 13:16, 22 October 2026
Line 24:		Line 24:
	\|-		\|-
	\|valign=top nowrap=true\|'''Loop length'''		\|valign=top nowrap=true\|'''Loop length'''
	\|~~present on ip29~~/~~311~~/~~411~~ gateways ~~only<br>~~		\|'''IP29-x adapters and IP311/411/511-gateways''': '500m' or '2500m'<br>
	~~Loop length can be set to~~ '500m' or '2500m'.		'''IP22/24/28 adapters''': 'low' = 500ft/155m or 'high' = 5000ft/1550m<br>
	~~Checking this topic to '2500m' decreases ring-trip threshold by 20% so that off-hook detection becomes more sensitive.~~		Use of '2500m' or 'high' decreases ring-trip threshold by 20% so that off-hook detection becomes more sensitive.
	\|-
	~~\|valign=top nowrap=true\|~~'''~~Loop length~~'''
	~~\|present on ip28/29/311/411 gateways only<br>~~
	~~Loop length can be set to~~ 'low' ~~for~~ 500ft/155m or 'high' ~~for~~ 5000ft/1550m.
	~~Checking this topic to~~ 'high' decreases ring-trip threshold by 20% so that off-hook detection becomes more sensitive.
	\|-		\|-
	\|valign=top nowrap=true\|'''RingTrip Threshold'''		\|valign=top nowrap=true\|'''RingTrip Threshold'''
Line 42:		Line 37:
	For possible line lengths, see [[Howto:Maximum_wire_length\|Maximum wire length]].		For possible line lengths, see [[Howto:Maximum_wire_length\|Maximum wire length]].

	==== Recommendation for ~~Use~~ with long ~~Wire Length~~ ====		==== Recommendation for use with long wire length on IP22/24/28 ====
	For best performance with long wires, use the following settings:		For best performance with long wires, use the following settings:
	* '''Optimization grade''' low		* '''Optimization grade''' low

Howto:Snom-DeskPhone-App - Snom - Partner App

Michal.boltz — Thu, 22 Oct 2026 11:38:35 GMT

Michal.boltz moved page Howto:Snom-DeskPhone-App - Snom - Partner App to Howto:Snom - DeskPhone provisioning - App Misspelled title

New page

{{FIXME|reason=This article is currently under work. As long, as this disclaimer is displayed, information may change.}}
[[File:Snom logo gray 60.jpg|right|200x200px|snom_logo_gray_60.jpg/|snom_logo_gray_60.jpg/]]

==Product Name==


[[File:Snom-DeskPhones.png|100x100px|snom-deskphones.png/|snom-deskphones.png/]]
[https://www.snom.com Snom] Snom-DeskPhone-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed October 2026.

==Category==

[[Category:Partner Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[File:Snom logo gray 60.jpg|150x150px|snom_logo_gray_60.jpg/|snom_logo_gray_60.jpg/]]



== Snom Hospitality devices ==

;
;

[https://service.snom.com/spaces/wiki/pages/401541241/Innovaphone+-+Snom+Hospitality+devices+provisioning+app. Snom Hospitality devices provisioning app.]

==Certification Status==

;

{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed September 2026.

==Category==

;
;
;

{{Category:3rdParty_Terminal_Devices}}

==Vendor==

[[Index.php?title=File:Snom logo gray 60.jpg&action=edit&redlink=1|link=https://wiki.innovaphone.comhttps//wiki.innovaphone.com/file://snom_logo_gray_60.jpg/|150x150px|snom_logo_gray_60.jpg/]]

Snom Technology GmbH is a leading provider of innovative telecommunication solutions, specializing in the design and manufacture of high-quality VoIP telephones and communication endpoints.

With a strong focus on reliability, versatility, and user-friendly features, Snom has earned a reputation for delivering cutting-edge products tailored to meet the diverse needs of businesses and organizations worldwide.

Committed to excellence and customer satisfaction, Snom continues to push the boundaries of communication technology, empowering businesses to connect, collaborate, and thrive in today's dynamic digital landscape.

For further information refer to vendor website via link

[https://www.snom.com/ Snom Technology GmbH]

==Description==

{| class="wikitable"
| colspan="5" |Snom-DeskPhone App supports:
!
!
!
|-
| colspan="5" |DeskPhone 7xx - Series
!
!
!
|-
!
!Snom D335
!Snom D140
!Snom D150
! colspan="2" |Snom D713
! colspan="2" |Snom D717
|-
!
![[File:Snom d335 264x300.png|frameless|snom_d335_264x300.png/|snom_d335_264x300.png/]]
! colspan="2" |[[File:Snom D140 D150 sm.png|frameless|snom_d140_d150_sm.png/|snom_d140_d150_sm.png/]]
! colspan="2" |[[File:Snom d713 180x160.png|frameless|360x360px|snom_d713_180x160.png/|snom_d713_180x160.png/]]
! colspan="2" |[[File:Snom d717 264x300.png|frameless|264x264px|snom_d717_264x300.png/|snom_d717_264x300.png/]]
|-
|
|
| colspan="2" |
| colspan="2" |
| colspan="2" |
|-
|Display
|2,8" TFT colour
| colspan="2" |3,36" TFT colour
| colspan="2" |5" TFT colour
| colspan="2" |5" TFT colour
|-
|Resolution (pixels)
|320 x 240
| colspan="2" |320 x 240
| colspan="2" |480 x 272
| colspan="2" |480 x 272
|-
|Tiltable display
| -
| colspan="2" | -
| -
|Yes
| -
|Yes
|-
|LAN switch
|2 ports, Gbit
|2 ports 10/100 Mbps
|2 ports Gbit
| colspan="2" |2 ports, Gbit
| colspan="2" |2 ports, Gbit
|-
|PoE
|IEEE 802.3af, class 2
| colspan="2" |IEEE 802.3af, class 2
| colspan="2" |IEEE 802.3af, class 3
| colspan="2" |IEEE 802.3af, class 3
|-
|IP
|IPv4 & IPv6
| colspan="2" |IPv4 & IPv6
| colspan="2" |IPv4 & IPv6
| colspan="2" |IPv4 & IPv6
|-
|WLAN IEEE 802.11n/ac
| -
| colspan="2" | -
| colspan="2" | -
| colspan="2" |Yes
|-
|Bluetooth
| -
| colspan="2" | -
| colspan="2" | -
| colspan="2" | -
|-
|Headset connection via
|EHS/DHSG/RJ9 interface
| colspan="2" |EHS/DHSG/RJ9 interface
| colspan="2" |EHS/DHSG/RJ9 interface
| colspan="2" |EHS/DHSG/RJ9 interface
|-
|Function keys
|8 SmartLabel keys (up to 32 functions)
| colspan="2" |4 (12) self labeling
| colspan="2" |8 (28) self labeling
| colspan="2" |10 (36) self labeling
|-
|G.711 A-law, µ-law

G.722 (wideband)

G.726, G.729AB, GSM 6.10 (FR)
|Yes
| colspan="2" |Yes
| colspan="2" |Yes
| colspan="2" |Yes
|-
|Soft-keys
|4
| colspan="2" |4
| colspan="2" |4
| colspan="2" |4
|-
|SIP accounts
|12
| colspan="2" |12
| colspan="2" |12
| colspan="2" |12
|-
|USB
|1
| colspan="2" |1
| colspan="2" |1
|2
|1
|-
|Expansion module support
|via USB
| colspan="2" | -
| colspan="2" | -
| colspan="2" |via USB
|-
|SRAPS (Redirect and Provisioning)
|Yes
| colspan="2" |Yes
| colspan="2" |Yes
| colspan="2" |Yes
|}


The Snom DeskPhone App integrates the Phones into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Snom Phones.

==Functions==




* Add / Remove Snom DeskPhones
* Configure the Phonebook, keys and PBX Menue on Snom DeskPhones

With the Snom DeskPhone App it is possible to automatically add and remove DeskPhones.
In addition, the Phonebook, keys and PBX Menu configuration can be provisioned.

===Multi-PBX ready===




n.a.

===Cloud ready===



YES

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi

==Licensing==


No license is required for this app

==Prerequisites==


For BLF key signaling and pick-up a Group is needed where all phones are member of and logged in.

a PBX Object DTMF Features must be configured, with activated "Autocomplete '#'"

The app must not be installed and set up via myApps, that must be done via browser!

Because the connection from myApps to the app platform is only recognised as an http connection by SDK, even if https is used.

at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager

''If the instance is operated in the innovaphone myApps Cloud, please request the following approvals on the Cloud RP via ticket at cloud@innovaphone.com, specifying the “instance number|domain name”:''

''musterschuster-p.innovaphone.com -> SIPS 5061 mit Check Certificate''

''musterschuster-a.innovaphone.com -> SIP 5060 (= Realm'00')''

''If you require additional realms for multiple customer master locations, e.g., for multiple Snom apps or instances, the following must also be requested:''

''musterschuster-a.realm01 -> SIP 50601''

''- bis max. -''

''musterschuster-a.realm50 -> SIP 50650''

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1 final

===Application versions used for interop testing===


* Snom DeskPhone-App - 1021 sr1

* innovaphone V15r1 final
* Snom Desktop D810W, D815WB, D865 software:10.1.226.13

==Configuration==


===Install the App===

===Snom- DeskPhone - App===

==== innovaphone settings ====
As an admin, create the environment settings in the Snom DeskPhone App.

For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Longname or E164 as an alternative, when DN is not set. If you want to show VoiceMail Messages into Phone Display enter the VoiceMail Number. Also define if reverse proxy and/or STUN Server should be activated or not and configure it accordingly. 

[[File:DeskPhone inno settings.png|frameless|600x600px|deskphone_inno_settings.png/|deskphone_inno_settings.png/]]

==== Snom settings ====
Enter the parameters for the phones to reach the App Platform. SIP realm and App Platform adress as an IP adress or FQDN. Also SIP port and protocol. if you need other SIP port then 5060/5061 via reverse Proxy. Port to Reverse Proxy still stays as 5060/5061.

'''Please note:''' If you want to use more then one Snom App instance or Snom DECT Provisioning in parallel, you need for each instance a SIP realm and a dedicated forwarding rule to the AP must be configured on the reverse proxy!

Username and password will be set for the phones web-ui. The phone connects via SIP with the App Platform, therefore the SIP-Password is needed. You can generate a random Password by using the button below.

If activating the additional admin mode, only basic settings will be shown in the web UI. After entering the administrator mode password, the complete admin web UI of the phone will be unlocked again.

[[File:Snom enviroment settings.png|frameless|504x504px|snom_enviroment_settings.png/|snom_enviroment_settings.png/]]

==== number formatting ====
access code, prefixes, country and area code will be automatically read from the system.

this settings are not used by the phone at the moment.

[[File:DeskPhone number formatting.png|frameless|600x600px|deskphone_number_formatting.png/|deskphone_number_formatting.png/]]

==== key settings ====
This DeskPhone app reads the user's key configuration in two places. 1. Configured keys of the type: Dial and Partner

and 2. The user's favorites.

You can choose the order in which these two are displayed on the phone:

* Favorites first, then keys
* Keys first, then favorites
* Do not provision any changes

[[File:DeskPhone key settings1.png|frameless|543x543px|deskphone_key_settings1.png/|deskphone_key_settings1.png/]]

and you can choose where these keys should start on the phone:

* Ocupy from first page
* Occupy from second page
* Assign to key module
* Do not provision any changes

[[File:DeskPhone key settings2.png|frameless|547x547px|deskphone_key_settings2.png/|deskphone_key_settings2.png/]]

==== PBX menu settings ====
DekPhone App will automatically provide a PBX menu to the phones.

* Directory: will provide the local innovaphone LDAP contacts for dialing
* Diversion: see actual call diversion, set/change/activate/deactivate Diversion targets for Always, Busy and on No response.
* Group: show, join and leave Groups
* Presence: see actual Presence, change Presence to Online/Away/Busy/DND
* Working: see actual status of working and Start/Stop working

[[File:DeskPhone pbxmenu settings.png|frameless|600x600px|deskphone_pbxmenu_settings.png/|deskphone_pbxmenu_settings.png/]]

* advanced call forwarding: extend the Diversion menu by Diversion Busy and on No response.
* static groups: static Groups are shown on buttom of the list.
* function key: F4 as default, but you can choose F1-F3 also, or deactivate. this are they keys below the display of the phone.
* context sensitivity of the function key: e.g. on F4 normally info button is displayed when info messages are present, and into info menu the PBX menu button will shown until all mssages ar read, which this switch you can deactivate this behavior.
* menu name: this name will be displayed on the previously selected key.

==== phone book settings ====
Under Phonebook settings you can activate sync for a phonebook.
{| class="wikitable"
|+
![[File:DeskPhone phonebook settings1.png|frameless|555x555px|deskphone_phonebook_settings1.png/|deskphone_phonebook_settings1.png/]]
![[File:DeskPhone phonebook settings2.png|frameless|542x542px|deskphone_phonebook_settings2.png/|deskphone_phonebook_settings2.png/]]
|}
there are three different phone books available, you can configure only one at a time. the same for all three, first thing to choose is phone book key and set a name that will be displayed on the key.

# the standard LDAP directory of the innovaphone PBX (PBX0), which is also integrated in PBX menu. Please enter the IP address, port and previously created access data for the innovaphone LDAP.
# LDAP server where you manuelly enter all parameters.
# Contacts APP, enter the neccessary parameters:
#* phone book key : F3 (default)
#* Phonebook key name: name that will be displayed on the key
#* Host : innoapp.domain.de (address of the AP)
#* Port : 636
#* TLS : yes
#* LDAP search base : dc=entries
#* Username : [from PBX-Manager / AP Contacts / Change Configuration / User (LDAP)]
#* Password : [from PBX-Manager / AP Contacts / Change Configuration / Password (LDAP)]
#* Name filter : (|(cn=%)(sn=%))
#* Number filter : (metaSearchNumber=%)
#* all other entries as shown in below screenshot are preconfigured

[[File:DeskPhone phonebook settings Contacts.png|frameless|762x762px|deskphone_phonebook_settings_contacts.png/|deskphone_phonebook_settings_contacts.png/]] 

==== 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: 
'''[https://service.snom.com/spaces/wiki/pages/234341081/D-Series+Settings Snom Desktop Phone Settings] '''

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

 
please have in mind, that you have to replace special signs with placeholders: & - &amp;

‘ - &apos;

< - &lt;

> - &gt;

” - &quot;

Ä - &#196;

Ö - &#214;

Ü - &#220;

ä - &#228;

ö - &#246;

ü - &#252;

ß - &#223;

 

==== Advanced settings ====

* "Reload Snom Devices" will be reload all Snom DeskPhones from Devices List. Keyword is the APP-Name, which is also inserted into the Devices. Wildcards are allowed.
* Execute Provisioning NOW will send a SIP-Notify to every connected Phone to force them to pull again the Provisioning File from Provisioning App.
* Firmware URLs: if you want to Update DeskPhone Firmware by the Provisioning App enter here a Web Url where the Phone can download it. e.g. path from Snom Wiki Firmware File. '''[https://service.snom.com/spaces/wiki/pages/234331169/Firmware+Update+Center Snom Desktop Phone update center] '''
* provisioning via HTTP instead of HTTPS: Snom DeskPhones does '''NOT support self signed certificates!''' if you have no official sigend certificates, force the App to provide a HTTP Link insted of HTTPS. The fact that the Copy Link button is not displayed is a restriction in the innovaphone SDK for unsecure connections.
* generate new secret: if needed you can generate a new secret. or if you have to reinstall the app, you can copy your previously used secret in.
* provisioning path: The app generates a provisioning path from its data. This path does not change as long as you do not regenerate a new secret. Copy this path and paste it on every new phone, you have to copy the Provisioning URL into the phone via Web-Ui. Setup --> Advanced --> Update --> Setting URL: copy it here and apply. Afterwards type on the phone: Settings --> Maintenance (5) --> Synchronize Settings (4) --> Ok

 

===Add Devices to User and start Provisioning===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Snom + ''APP-Name''" in the manufacturer selection field and then enter the MAC adress of the phone.
You can find the MAC of the phone on the box, under the phone or by pressing settings --> Information (6) --> System Info (2) on the phone.

After you have saved the new phone, you have to copy the Provisioning URL into the phone via Web-Ui.

Setup --> Advanced --> Update --> Setting URL: copy it here and apply.

Afterwards type on the phone: Settings --> Maintenance (5) --> Synchronize Settings (4) --> Ok

[[File:Users admin Desktop App how to.png|frameless|875x875px|users_admin_desktop_app_how_to.png/|users_admin_desktop_app_how_to.png/]]

[[File:DeskPhone Devices1.png|frameless|900x900px|deskphone_devices1.png/|deskphone_devices1.png/]]

[[File:Snom Desktop app Devices list.png|frameless|790x790px|snom_desktop_app_devices_list.png/|snom_desktop_app_devices_list.png/]]

[[File:Snom Phone Advanced settings.png|frameless|774x774px|snom_phone_advanced_settings.png/|snom_phone_advanced_settings.png/]]

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Snom application on the application platform so that a rollback of the configuration is possible.

=== 1021 sr1 ===
- Startversion 

==Known Problems==

=== URLs are shown as http instead of https ===
The app must not be installed and set up via myApps, that must be done via browser!

Because the connection from myApps to the app platform is only recognised as an http connection by SDK, even if https is used.

=== MOH not working ===
put this parameter in the custom phone settings part:

<user_hold_inactive idx="1" perm="">on</user_hold_inactive>

=== Same SIP Port/Protocol for PBX and APP-Plattform via Reverse Proxy ===
is not working, due to load optimizations of Reverse Proxy. choose 5061/TLS for PBX and 5060/TCP for App Plattform.

===Provisioning of devices via Users Admin not working===
Please note the following for environments that do not have Internet access. In this case, the assignment of devices via the Users Admin may be disrupted.
The Snom App works together with the provisioning service of the Devices App. The online provisioning server from innovpahone "config.innovaphone.com" is entered as the default in the Devices app. If the environment cannot reach the server, the process is aborted.
To avoid this, offline provisioning must be configured for the domain in the Devices app.
https://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_Offline_Provisioning

=== Provisioning option not available in Users Admin when giving Profile app a custom name ===
When the name or long name of your profile app PBX object differs from the default names "Profile" (long name) and "profile" (name), you won't have the option to select "Snom - Snom Provisioning" as the manufacturer of the phone if you try to create new phone registrations via Users Admin. 

=== no Audio / disconnect after 30 - Snom phone is connected through a Reverse Proxy ===
Media Relay works only in a LAN. For working through a Reverse Proxy a view more settings are needed. See here:
https://wiki.innovaphone.com/index.php?title=Howto13r3:Step-by-Step_Media_Relay_connection_for_third_party_phone

== Related Articles ==
*[[Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments| Howto:Using Gigaset-Provisioning-App in innovaphone myApps cloud environments]]

==Contact==
Contact Details
==Contact Details==
{|
| Company Name: || Snom Technology GmbH
|-
| Street: || Aroser Allee 66
|-
| ZIP/City: || 13407 Berlin Germany
|-
| Country: || Germany
|-
| Phone: || +49 30 39833-0
|-
| Fax: || +49 30 39833-111
|-
| Mail: || [mailto:officemanagement@snom.com officemanagement@snom.com]
|-
| Internet: || [https://www.snom.com Snom Technology GmbH]
|-
| Contact: || [https://www.snom.com/de/kontakt/ Snom contact]
|-
| Support: || [https://service.snom.com Snom Service Hub]
|}

ReleaseNotes:Hardware IP17x

Mma — Thu, 22 Oct 2026 11:24:27 GMT

Created page with "These release notes describe the IP17x Hardware Builds starting with build 400 Please see ''the disclaimer'' before using the information presented here! __NOEDITSECTION__ {{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=Hardware%20IP17x}} Hardware"

New page

These release notes describe the IP17x Hardware Builds starting with build 400 
 
Please see ''[[Reference:What_are_the_Release_Notes_Documents?|the disclaimer]]'' before using the information presented here!

__NOEDITSECTION__
{{#invoke-url: http://wiki.innovaphone.com/extensions/InvokeUrlFunction/projectListWebsocket.php?project=Hardware%20IP17x}}

[[Category:Release Notes|Hardware]]

Howto:Howto:Snom - Hospitality - Provisioning - App

Michal.boltz — Thu, 22 Oct 2026 10:38:17 GMT

Michal.boltz moved page Howto:Howto:Snom - Hospitality - Provisioning - App to Howto:Snom - Hospitality - Provisioning - App Misspelled title

New page

[[Image:Snom logo gray 60.jpg|350px|right|snom_logo_gray_60.jpg/|snom_logo_gray_60.jpg/]]

==Snom Hospitality devices==
;
;
[https://service.snom.com/spaces/wiki/pages/401541241/Innovaphone+-+Snom+Hospitality+devices+provisioning+app. Snom Hospitality devices provisioning app.]

==Certification Status==
;
{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed September 2026.

==Category==
;
;
;
[[Category:Partner Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==
;
;
[[Image:Snom logo gray 60.jpg|150px|snom_logo_gray_60.jpg/|snom_logo_gray_60.jpg/]]

;
;
Snom Technology GmbH is a leading provider of innovative telecommunication solutions, specializing in the design and manufacture of high-quality VoIP telephones and communication endpoints. 
With a strong focus on reliability, versatility, and user-friendly features, Snom has earned a reputation for delivering cutting-edge products tailored to meet the diverse needs of businesses and organizations worldwide. 
Committed to excellence and customer satisfaction, Snom continues to push the boundaries of communication technology, empowering businesses to connect, collaborate, and thrive in today's dynamic digital landscape. 
 
For further information refer to vendor website via link 
[https://www.snom.com Snom Technology GmbH]

==Description==
 
;
;

;
;
[[File:Snom Hospitality app main.png|thumb|snom_hospitality_app_main.png/|snom_hospitality_app_main.png/]]
 
'''Snom Hospitality provisioning app''' for '''innovaphone''' is an auto-provisioning application designed to streamline the integration of Snom Hospitality phones into innovaphone systems.

This intuitive app allows innovaphone administrators to seamlessly add Snom Hospitality phones using the familiar graphical interface of the innovaphone platform.

With a straightforward installation process, Snom phones can be effortlessly integrated by simply entering their MAC address in User / Object device section. 
 
Starting with PhoneLink app version 1337 we support multi SIP account generation on all Snom devices. 
All DECT devices no longer need manual configuration for all handsets.
==Functions==
;
;'''Snom Hospitality provisioning app''' for '''innovaphone'''<nowiki> supports the following devices:</nowiki>
; HD100 / HD101
; HD300 / HD30L
; E303
; HD331
; HD340 / HD341
; HD350W / HD351W
; HM201

;

===Multi-PBX ready===
Snom Hospitality app. can be used in Multi-PBX enviroment 
No special configuration, required 

===Cloud ready===
Snom Hospitality app. is fully tested and compliant with innovaphon cloud enviroment 

=== Required API’s ===
* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==
No license required

==Prerequisites==
;

innovaphone PBX firmware version 14r2 or higher must be installed. 
The app platform must be correctly installed and accessible via its IP address. 

;
[https://service.snom.com/spaces/wiki/pages/401541241/Innovaphone+-+Snom+Hospitality+devices+provisioning+app. Snom Hospitality]

==Versions==
Hospitality app version 142007 final or higher

===Compatible innovaphone firmware versions===
;
* innovaphone V15r1
* innovaphone V14r2
* innovaphone V14r1

===Application versions used for interop testing===
* Snom Hospitality app version 142007 final
* innovaphone V15r1
* innovaphone V14r1

==Configuration==
;

=== Install the App ===
[[File:Snom Hospitality app main.png|frameless|621x621px|deskphone_gigaset_settings.png/|snom_hospitality_app_main.png/]]

=== Innovaphone settings ===
As an administrator, configure the environment under '''innovaphone Environment > Settings'''.

From the innovaphone PBX, provide the following information:

* Domain
* PBX IP address or fully qualified domain name (FQDN)
* SIP or SIP-TLS port
* Master PBX name
* PBX password

You can also enable and configure the reverse proxy and STUN server as required.

==== [[File:Innovaphone enviroment.png|frameless|600x600px|deskphone_number_formatting.png/|innovaphone_enviroment.png/]] ====

=== Global Phone Hospitality phones settings ===
In this section, you can configure settings that will be applied to all Snom hospitality phones provisioned through this app.

==== Emergency Dialing Settings ====
Enable and configure automatic emergency dialing:

* '''Enable emergency dialing''' – Activates the emergency dialing function.
* '''Phone number''' – Specifies the number to be dialed automatically.
* '''Delay (sec)''' – Defines the delay, in seconds, before the call is initiated.

'''Custom Provisioning Settings'''

Use this field to add additional Snom provisioning parameters that are not available as standard options in the application.

Enter each parameter on a separate line using the following format:

<code>setting.parameter = value</code>

Ensure that the parameter names and values comply with the provisioning syntax supported by the relevant Snom phone model and firmware version.

==== Advanced Settings ====
The following advanced options are available:

* '''Reload Snom devices''' – Allows a reload request to be sent to provisioned Snom devices. Specify the relevant app or object name, enable the option, and select '''Reload''' when required.
* '''WebUI password''' – Defines the password used to access the phones’ web user interface.
* '''Provisioning interval (in minutes)''' – Specifies how frequently the phones check the provisioning server for configuration updates.
* '''Provisioning via HTTP instead of HTTPS''' – Enables unencrypted HTTP provisioning. For security reasons, HTTPS should be used whenever possible.
* '''Generate new secret''' – Generates a new secret used to secure the provisioning URL. After generating a new secret, the phones may need to receive the updated provisioning path.
* '''Provisioning path''' – Displays the generated provisioning URL which is used in Settings Server url on the phones. Use the copy button to copy the path to the clipboard. Example

Select the '''Save''' button to apply the configuration changes.

[[File:Global phone settings.png|frameless|641x641px|deskphone_number_formatting.png/|global_phone_settings.png/]]

=== Add Devices to User and start Provisioning ===
Now create new end devices as usual via UserAdmin or the Profile app. Select "Snom + ''APP-Name''" in the manufacturer selection field and then enter the MAC adress of the phone.

You can find the MAC of the phone on the box, under the phone or by logging into the WUI's main page.

Please remove ":", the MAC provided to innovaphone must be in this format: >> 000413000000

Users Admin:

[[File:Provisioning hospitality phone.png|frameless|543x543px|deskphone_key_settings1.png/|provisioning_hospitality_phone.png/]]

After you have saved the new phone, you have to copy the Provisioning URL into the phone via Web-Ui.

Servicing --> Provisioning --> Server URL: copy it here and apply by cliking SAVE.

Device will reboot and download new settings.

==== Manual Configuration ====
To configure a device manually, navigate to either:

* '''Users Admin > User''', or
* '''Devices > PBX > Object'''

Complete the '''Devices''' section as shown in the example below.

'''Snom_Hospitality''' is the application name specified during the installation process.

[[File:Users admin.png|frameless|547x547px|deskphone_key_settings2.png/|users_admin.png/]]

Correct name ensure that the information shown in Hospitality Devices tab is displayed correcty.

[[File:Hospitality devices list.png|frameless|547x547px|deskphone_key_settings2.png/|hospitality_devices_list.png/]]

==== Individual model settings: ====
Snom Hospitality provisioning app allow to configure model specific settings speed dial buttons and url for software update.

Software section by default show SNOM download server URL. It can be changed for URL by customer choice.

Example:
;[[File:Invidual model settings.png|frameless|547x547px|deskphone_key_settings2.png/|invidual_model_settings.png/]]


==Contact Details==
{|
| Company Name: || Snom Technology GmbH
|-
| Street: || Aroser Allee 66
|-
| ZIP/City: || 13407 Berlin Germany
|-
| Country: || Germany
|-
| Phone: || +49 30 39833-0
|-
| Fax: || +49 30 39833-111
|-
| Mail: || [mailto:officemanagement@snom.com officemanagement@snom.com]
|-
| Internet: || [https://www.snom.com Snom Technology GmbH]
|-
| Contact: || [https://www.snom.com/de/kontakt/ Snom contact]
|-
| Support: || [https://service.snom.com Snom Service Hub]
|}

Howto:Howto:Snom PhoneLink provisioning App

Michal.boltz — Thu, 22 Oct 2026 10:37:56 GMT

Michal.boltz moved page Howto:Howto:Snom PhoneLink provisioning App to Howto:Snom PhoneLink provisioning App

New page

[[Image:Snom logo gray 60.jpg|350px|right]]

==Product Name==
;
;
[https://service.snom.com/display/wiki/PhoneLink+for+innovaphone SNOM PhoneLink App]

==Certification Status==
;
{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed February 2024.

==Category==
;
;
;
[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==
;
;
[[Image:Snom logo gray 60.jpg|150px]]

;
;
Snom Technology GmbH is a leading provider of innovative telecommunication solutions, specializing in the design and manufacture of high-quality VoIP telephones and communication endpoints. 
With a strong focus on reliability, versatility, and user-friendly features, Snom has earned a reputation for delivering cutting-edge products tailored to meet the diverse needs of businesses and organizations worldwide. 
Committed to excellence and customer satisfaction, Snom continues to push the boundaries of communication technology, empowering businesses to connect, collaborate, and thrive in today's dynamic digital landscape. 
 
For further information refer to vendor website via link 
[https://www.snom.com Snom Technology GmbH]

==Description==
 
;
;

;
;
[[File:PhoneLink main screen.jpg|thumb]] 
PhoneLink for innovaphone, an auto-provisioning application designed to streamline the integration of Snom phones into innovaphone systems. 
This intuitive app allows innovaphone administrators to seamlessly add Snom phones using the familiar graphical interface of the innovaphone platform. 
With a straightforward installation process, Snom phones can be effortlessly integrated by simply entering their MAC address. 
 
 
Through seamless integration with the SRAPS REST API, adding the MAC address within the innovaphone PBX triggers the registration and provisioning configuration data for Snom devices. 
Upon booting up, each phone automatically retrieves its configuration from SRAPS, ensuring smooth setup and deployment. 
 
 
PhoneLink for innovaphone supports all compatible models from the D-Series, M-Series, MSC-Series, and C-Series, making it versatile for various device types that support auto-provisioning via SRAPS. 
This essential app is conveniently accessible through the innovaphone App Store, allowing for easy downloading and installation directly from the platform. 
 
 
Starting with PhoneLink app version 1337 we support multi SIP account generation on all Snom devices. 
All DECT devices no longer need manual configuration for all handsets.

==Functions==
;
;
;

;

===Multi-PBX ready===
Phone Link app can be used in Multi-PBX enviroment 
No special configuration, required 

===Cloud ready===
PhoneLink app is fully tested and compliant with innovaphon cloud enviroment 

=== Required API’s ===
;
;
;

* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==
No license required

==Prerequisites==
;
;
;

innovaphone PBX firmware version 13r2 or higher must be installed. 
The app platform must be correctly installed and accessible via its IP address. 
Users need an SRAPS user account and have created an API key to utilize the app's functionalities. 

;
[https://service.snom.com/display/wiki/PhoneLink+for+innovaphone Snom PhoneLink app.]

==Versions==
PhoneLink app version 1337 final or higher

===Compatible innovaphone firmware versions===
;
* innovaphone V14r1
* innovaphone V13r3
* innovaphone V13r2

===Application versions used for interop testing===
* PhoneLink app version 1337 final
* innovaphone V14r1
* innovaphone V13r3

==Configuration==
;
;
;

;
;

;

;
;
In the articles below we will present how to configure PhoneLink app and all types of Snom phones. 

===PhoneLink on innovaphone app store===
Step by step instruction describing how to configure PhoneLink app on innovaphone AP platform. 
[https://service.snom.com/display/wiki/How+to+install+PhoneLink+from+the+innovaphone+app+store How to install PhoneLink from the innovaphone app store]

'''Note''': After installing the PhoneLink app, the Profile app needs to get access to the PhoneLink app to offer Snom devices for provisioning. 
Specifically, respective Snom-application must be activated in the Profile app object on the PBX under the Apps tab.

===Desktop phone configuration with PhoneLink===
In this article we are showing how to provision Snom desk phones series: D140/150, D3xx, D7xx and D8xx. 
Howto covers phones with a single SIP account and multiple SIP accounts. 
[https://service.snom.com/display/wiki/Provisioning+Snom+desk+phones+with+innovaphone+pbx How to Provision a Snom deck phones on Innovaphone PBX]

===DECT systems configuration with PhoneLink===
In this article we are showing how to provision Snom DECT systems series: M110, M400, M900, M700 and M300. 
Howto covers multiple SIP accounts configuration required by DECT system. 
[https://service.snom.com/display/wiki/Provisioning+Snom+DECT+systems+with+innovaphone+pbx How to Provision a Snom DECT systems on Innovaphone PBX]

===Mass deployment with PhoneLink app.===
In this article we are showing how to use PhoneLink app. with Mass Deploymnet of the Snom phones 
Howto covers single and multiple SIP accounts mass deploymnet scenarios with all Snom devices. 
[https://service.snom.com/display/wiki/Mass+deployment+of+Snom+phones+with+innovaphone+pbx PhoneLink for innovaphone - Mass deployment PBX]

===LDAP directory configuration with PhoneLink app.===
In this article we are showing how to add extra features like LDAP configuration with PhoneLink app. 
[https://service.snom.com/display/wiki/LDAP+configuration+for+Snom+phones+with+innovaphone+pbx LDAP directory configuration using PhoneLink app.]

==Contact Details==
{|
| Company Name: || Snom Technology GmbH
|-
| Street: || Aroser Allee 66
|-
| ZIP/City: || 13407 Berlin Germany
|-
| Country: || Germany
|-
| Phone: || +49 30 39833-0
|-
| Fax: || +49 30 39833-111
|-
| Mail: || [mailto:officemanagement@snom.com officemanagement@snom.com]
|-
| Internet: || [https://www.snom.com Snom Technology GmbH]
|-
| Contact: || [https://www.snom.com/de/kontakt/ Snom contact]
|-
| Support: || [https://service.snom.com Snom Service Hub]
|}

Howto:Snom-Hospitality-Provisioning-App - Snom - Partner App

Michal.boltz — Thu, 22 Oct 2026 10:37:34 GMT

Michal.boltz moved page Howto:Snom-Hospitality-Provisioning-App - Snom - Partner App to Howto:Howto:Snom PhoneLink provisioning App Misspelled title: Wrong title

New page

Howto:Snom PhoneLink - Snom - Partner App

Michal.boltz — Thu, 22 Oct 2026 10:35:54 GMT

Michal.boltz moved page Howto:Snom PhoneLink - Snom - Partner App to Howto:Howto:Snom - Hospitality - Provisioning - App Misspelled title: Wrong title

New page

Reference16r1:Concept App Service Users

Cam — Wed, 21 Oct 2026 09:35:20 GMT

Import/Export with CSV/XML on Users Admin App

← Older revision		Revision as of 10:35, 21 October 2026
Line 118:		Line 118:
	\|-		\|-
	\| device/&trusted \|\| Reverse Proxy \|\| true \|\| Either "true" (checked), "false" (not checked) or "" (empty, same as false)		\| device/&trusted \|\| Reverse Proxy \|\| true \|\| Either "true" (checked), "false" (not checked) or "" (empty, same as false)
			\|-
			\| device/&sreg \|\| Single Reg. \|\| true \|\| Either "true" (checked), "false" (not checked) or "" (empty, same as false)
			\|-
			\| device/&mr \|\| Media Relay \|\| true \|\| Either "true" (checked), "false" (not checked) or "" (empty, same as false)
			\|-
			\| device/&nosrtp \|\| No SRTP \|\| true \|\| Either "true" (checked), "false" (not checked) or "" (empty, same as false)
	\|-		\|-
	\| gws/&name \|\| DECT system \|\| dect1 \|\|		\| gws/&name \|\| DECT system \|\| dect1 \|\|
Line 208:		Line 214:
	\|-		\|-
	\| trusted \|\| Reverse Proxy \|\| true \|\| Either "true" (checked) or not present (not checked)		\| trusted \|\| Reverse Proxy \|\| true \|\| Either "true" (checked) or not present (not checked)
			\|-
			\| sreg \|\| Single Reg. \|\| true \|\| Either "true" (checked) or not present (not checked)
			\|-
			\| mr \|\| Media Relay \|\| true \|\| Either "true" (checked) or not present (not checked)
			\|-
			\| nosrtp \|\| No SRTP \|\| true \|\| Either "true" (checked) or not present (not checked)
	\|}		\|}

User:CSammiller

CSammiller — Wed, 21 Oct 2026 09:17:32 GMT

User account CSammiller was created

Reference16r1:Concept App Service Conference Transcriptions

Hma — Wed, 21 Oct 2026 08:07:40 GMT

Conference Transcriptions - App Service: added Info that chats are stored too

← Older revision		Revision as of 09:07, 21 October 2026
Line 49:		Line 49:
	The App Service performs tasks in the following areas:		The App Service performs tasks in the following areas:
	* Transcribes the audio of a conference room		* Transcribes the audio of a conference room
	* Stores the transcript in the database		* Stores the transcript, including chat messages, in the database
	* Creates and stores the summary of the transcript in the database		* Creates and stores the summary of the transcript in the database

Howto:Snom-DeskPhone-App - Snom - Partner App

Michal.boltz — Tue, 20 Oct 2026 12:47:38 GMT

Last words "gigaset" replaced by snom

Howto:How to configure a nightly automatic phone restart via Devices app expert config

Vsc — Tue, 20 Oct 2026 06:12:03 GMT

← Older revision		Revision as of 07:12, 20 October 2026
Line 1:		Line 1:
	~~==Titel==~~		Nightly automatic phone restart via Devices [[Reference16r1:Concept_App_Service_Devices#Expert_configuration\|application expert configuration]].
	Nightly automatic phone restart via Devices ~~app~~ expert ~~config~~

	==Problem description==		==Problem description==
	Beeing able to restart a device automatically on a scheduled time		Beeing able to restart a device automatically on a scheduled time
Line 9:		Line 7:

	==Concept==		==Concept==

	The expert configuration of the Devices app only runs '''once''': after a device restart, or when the expert configuration is changed. That means it cannot schedule anything itself.		The expert configuration of the Devices app only runs '''once''': after a device restart, or when the expert configuration is changed. That means it cannot schedule anything itself.

	So the expert config only sets the phone’s '''update server URL (UP1)''' to a small script stored in the Files app. The phone downloads that script every 15 minutes. A ~~<~~code~~>~~times~~<~~/code~~>~~ command inside the script makes sure the reset only happens in the chosen night hour.		So the expert config only sets the phone’s '''update server URL (UP1)''' to a small script stored in the Files app. The phone downloads that script every 15 minutes. A <code>times</code> command inside the script makes sure the reset only happens in the chosen night hour.


	=== Step 1 – Create the script ~~<~~code~~>~~nightly.txt~~<~~/code~~>~~ ===		=== Step 1 – Create the script <code>nightly.txt</code> ===
	Upload this file to a shared folder in the Files app:		Upload this file to a shared folder in the Files app:
	mod cmd UP1 times /allow 0 /initial 61		mod cmd UP1 times /allow 0 /initial 61
Line 23:		Line 19:
	!Meaning		!Meaning
	\|-		\|-
	\|~~<~~code~~>~~times /allow 0~~<~~/code~~>~~		\|<code>times /allow 0</code>
	\|The script only runs between '''00:00 and 00:59'''. At any other time, processing stops right after this line.		\|The script only runs between '''00:00 and 00:59'''. At any other time, processing stops right after this line.
	\|-		\|-
	\|~~<~~code~~>~~/initial 61~~<~~/code~~>~~		\|<code>/initial 61</code>
	\|Nothing runs during the first 61 minutes after a boot. After the reset at 00:xx, the next allowed hour is already over, so the phone does not loop.		\|Nothing runs during the first 61 minutes after a boot. After the reset at 00:xx, the next allowed hour is already over, so the phone does not loop.
	\|-		\|-
	\|~~<~~code~~>~~reset~~<~~/code~~>~~		\|<code>reset</code>
	\|'''Immediate''' restart, even during an active call. Use ~~<~~code~~>~~ireset~~<~~/code~~>~~ instead to wait until the phone is idle.		\|'''Immediate''' restart, even during an active call. Use <code>ireset</code> instead to wait until the phone is idle.
	\|}		\|}
	Get the '''fileskey''' from the info (“i”) button of the shared folder in the Files app.		Get the '''fileskey''' from the info (“i”) button of the shared folder in the Files app.
Line 40:		Line 36:
	config activate		config activate

	* ~~<~~code~~>~~/poll 15~~<~~/code~~>~~: the phone polls the script every 15 minutes.		* <code>/poll 15</code>: the phone polls the script every 15 minutes.
	* ~~<~~code~~>~~/no-dhcp~~<~~/code~~>~~: a URL handed out by DHCP cannot overwrite this URL.		* <code>/no-dhcp</code>: a URL handed out by DHCP cannot overwrite this URL.
	* Do '''not''' add ~~<~~code~~>~~iresetn~~<~~/code~~>~~, ~~<~~code~~>~~vars create~~<~~/code~~>~~ or ~~<~~code~~>~~times~~<~~/code~~>~~ to the expert config. They can cause a reboot loop or stop the expert config from running.		* Do '''not''' add <code>iresetn</code>, <code>vars create</code> or <code>times</code> to the expert config. They can cause a reboot loop or stop the expert config from running.

	=== Step 3 – Prerequisites ===		=== Step 3 – Prerequisites ===

	* The phone has a valid time from NTP. Without it, ~~<~~code~~>~~times~~<~~/code~~>~~ cancels every execution.		* The phone has a valid time from NTP. Without it, <code>times</code> cancels every execution.
	* The phone trusts the HTTPS certificate of the apps host.		* The phone trusts the HTTPS certificate of the apps host.
	* The URL works in a browser and shows the two lines of the script.		* The URL works in a browser and shows the two lines of the script.
Line 52:		Line 48:
	=== Step 4 – Verify (optional) ===		=== Step 4 – Verify (optional) ===

	* Add ~~<~~code~~>~~/trace~~<~~/code~~>~~ to the ~~<~~code~~>~~config change UP1~~<~~/code~~>~~ line.		* Add <code>/trace</code> to the <code>config change UP1</code> line.
	* In the phone’s Advanced UI, go to '''Maintenance → Diagnostics → Tracing''', enable '''HTTP Client''' and open '''trace(continuous)'''. There you can see the script being fetched and the server’s answer.		* In the phone’s Advanced UI, go to '''Maintenance → Diagnostics → Tracing''', enable '''HTTP Client''' and open '''trace(continuous)'''. There you can see the script being fetched and the server’s answer.
	* To test during the day, temporarily use the current hour and a small ~~<~~code~~>~~/initial~~<~~/code~~>~~ value (e.g. ~~<~~code~~>~~/allow 16,17 /initial 1~~<~~/code~~>~~). The phone then restarts about every 15 minutes within those hours.		* To test during the day, temporarily use the current hour and a small <code>/initial</code> value (e.g. <code>/allow 16,17 /initial 1</code>). The phone then restarts about every 15 minutes within those hours.
	* After testing, set the script back to ~~<~~code~~>~~/allow 0 /initial 61~~<~~/code~~>~~ and remove ~~<~~code~~>~~/trace~~<~~/code~~>~~.		* After testing, set the script back to <code>/allow 0 /initial 61</code> and remove <code>/trace</code>.

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

User:Matthias Mandl

Matthias Mandl — Tue, 20 Oct 2026 06:00:37 GMT

User account Matthias Mandl was created

User:Thomas.vanGalen

Thomas.vanGalen — Tue, 20 Oct 2026 05:56:36 GMT

User account Thomas.vanGalen was created

User:Lista-Utic

Lista-Utic — Mon, 19 Oct 2026 16:20:41 GMT

User account Lista-Utic was created

Reference16r1:Concept App Service Users

Cam — Mon, 19 Oct 2026 14:37:36 GMT

Import/Export with CSV/XML on Users Admin App

Show changes

User:Aasanz

Aasanz — Mon, 19 Oct 2026 11:58:51 GMT

User account Aasanz was created

How to post a successful Mantis Request

Slu — Mon, 19 Oct 2026 09:34:00 GMT

Understanding the state "closed"

← Older revision		Revision as of 10:34, 19 October 2026
Line 49:		Line 49:

	'''This means: If a case was temporarily closed, this is not a disadvantage and we and we can continue to process the case at any time.'''		'''This means: If a case was temporarily closed, this is not a disadvantage and we and we can continue to process the case at any time.'''

			=== AI-assisted case analysis ===
			We use AI to analyze your request, logs and configuration files, and to support our engineers in working on your case. By default, only locally hosted AI models are used – no case data is transferred to external AI providers.

			'''You can additionally allow the use of external AI services''' (e.g. Anthropic Claude, OpenAI) for your case. This usually gives a faster response and better analysis quality: your request reaches the right expert sooner, and the web form can give you feedback and self-help hints before you submit. In return, the relevant case data is sent to that provider, which may be located outside the EU (e.g. in the USA). The transferred content is not used to train AI models. For details, check our privacy policy.

			One example: a case with a rare race condition had already taken about two weeks of manual analysis. As a test it was given to an external AI model, which correctly diagnosed the issue in about 4 minutes, and the case was closed within one day.

			'''How to enable it:'''
			* '''Web form:''' in the ''AI analysis'' section, tick ''"Yes, enable external AI analysis"'' when you open the case.
			* '''Existing case:''' you can still enable it on the upload page of your case (see [[#Access to Case History\|Access to Case History]]). It then applies to the whole case, including the information and files sent earlier.
			* '''E-Mail:''' add the tag <code>@aiglobal true</code> (see [[#Valid TAGS\|Valid TAGS]]).

			Without your consent, your case is handled by our local AI only, which means a longer processing time and lower analysis quality. Your consent is voluntary, a choice per case, and can be revoked at any time with effect for the future for this case. Details are in our privacy policy.

	==E-Mail Interface==		==E-Mail Interface==

User:Tvangoylen

Tvangoylen — Fri, 16 Oct 2026 14:26:09 GMT

User account Tvangoylen was created

Reference16r1:Concept App Service Connector for Microsoft 365

Sga — Fri, 16 Oct 2026 13:43:44 GMT

EWS retirement dates, link to support article - Co-Authored-By: AI

← Older revision		Revision as of 14:43, 16 October 2026
Line 126:		Line 126:
	==== Technical Overview ====		==== Technical Overview ====
	Introduced in 15r1 the Connector for Microsoft 365 will offer a possibility to sync Azure Portal calendar events (Teams, Exchange online) via the Graph API with the PBX presence.<br>		Introduced in 15r1 the Connector for Microsoft 365 will offer a possibility to sync Azure Portal calendar events (Teams, Exchange online) via the Graph API with the PBX presence.<br>
	For now the [https://wiki.innovaphone.com/index.php?title=Reference13r3:Concept_App_Service_Calendar Calendar App] is (along with other functions) also capable of syncing calendar events, but using the old EWS mechanism~~, which~~ Microsoft ~~announced as end of life~~ starting ~~from~~ 2026.<br>		For now the [https://wiki.innovaphone.com/index.php?title=Reference13r3:Concept_App_Service_Calendar Calendar App] is (along with other functions) also capable of syncing calendar events, but using the old EWS mechanism. Microsoft disables EWS in Exchange Online by default starting October 1, 2026 and shuts it down permanently on April 1, 2027, see [[Support:Calendar App - Exchange Online EWS Retirement]].<br>
	'''Warning:''' Please make sure to not use both apps for syncing calendar events in parallel, this is not supported and will most likely lead to conflicts and unexpected behaviours.<br>		'''Warning:''' Please make sure to not use both apps for syncing calendar events in parallel, this is not supported and will most likely lead to conflicts and unexpected behaviours.<br>
	<br>		<br>

Support:Calendar App - Exchange Online EWS Retirement

Sga — Fri, 16 Oct 2026 13:43:24 GMT

New article: Exchange Online EWS retirement and Calendar App - Co-Authored-By: AI

Support:Firmware V16r1 product/16r1/firmware 1611053 (sr 6) available

Tle — Fri, 16 Oct 2026 10:17:25 GMT

Created page with "Firmware 16r1 Service Release 6 is available at http://store.innovaphone.com/release/download.htm"

Main Page

Tle — Fri, 16 Oct 2026 10:15:53 GMT

Support:MyApps Windows crashes on incoming calls after Windows Update KB5124010

Sga — Fri, 16 Oct 2026 08:37:44 GMT

Resolution

Support:MyApps Windows crashes on incoming calls after Windows Update KB5124010

Aci — Fri, 16 Oct 2026 07:21:28 GMT

← Older revision		Revision as of 11:15, 16 October 2026
Line 22:		Line 22:

	== Latest News ==		== Latest News ==
			<p align="right">[[User:Tle\|Tle]] ([[User talk:Tle\|talk]]) 12:15, 16 October 2026 (CEST)</p> [[Support:Firmware V16r1 product/16r1/firmware 1611053 (sr 6) available \| Version 16r1 Service Release 6]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

	<p align="right">[[User:Cam\|Cam]] ([[User talk:Cam\|talk]]) 09:06, 14 October 2026 (CEST)</p> [[Support:Firmware V15r1 product/15r1/firmware 1510788 (sr18) available \| Version 15r1 Service Release 18]] is now available from the [http://store.innovaphone.com/release/download.htm download page].		<p align="right">[[User:Cam\|Cam]] ([[User talk:Cam\|talk]]) 09:06, 14 October 2026 (CEST)</p> [[Support:Firmware V15r1 product/15r1/firmware 1510788 (sr18) available \| Version 15r1 Service Release 18]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

← Older revision		Revision as of 13:47, 20 October 2026
Line 206:		Line 206:
	<!-- At max 3 sentences, no novels. -->		<!-- At max 3 sentences, no novels. -->

	The Snom DeskPhone App integrates the ~~Snom~~ Phones into the innovaphone PBX environment.		The Snom DeskPhone App integrates the Phones into the innovaphone PBX environment.
	After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,		After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
	so that no further activities need to be performed on the ~~Gigaset~~ Phones.		so that no further activities need to be performed on the Snom Phones.

	==Functions==		==Functions==
Line 215:		Line 215:
	<!-- Preferred format is a short list of functions/buzz words offered by the product -->		<!-- Preferred format is a short list of functions/buzz words offered by the product -->

	* Add / Remove ~~Gigaset~~ DeskPhones		* Add / Remove Snom DeskPhones
	* Configure the Phonebook, keys and PBX Menue on Snom DeskPhones		* Configure the Phonebook, keys and PBX Menue on Snom DeskPhones

Line 272:		Line 272:


	''If you require additional realms for multiple customer master locations, e.g., for multiple ~~Gigaset~~ apps or instances, the following must also be requested:''		''If you require additional realms for multiple customer master locations, e.g., for multiple Snom apps or instances, the following must also be requested:''

	''musterschuster-a.realm01 -> SIP 50601''		''musterschuster-a.realm01 -> SIP 50601''
Line 320:		Line 320:
	If activating the additional admin mode, only basic settings will be shown in the web UI. After entering the administrator mode password, the complete admin web UI of the phone will be unlocked again.		If activating the additional admin mode, only basic settings will be shown in the web UI. After entering the administrator mode password, the complete admin web UI of the phone will be unlocked again.

	[[File:Snom enviroment settings.png\|frameless\|504x504px\|~~deskphone_gigaset_settings~~.png/\|snom_enviroment_settings.png/]]		[[File:Snom enviroment settings.png\|frameless\|504x504px\|snom_enviroment_settings.png/\|snom_enviroment_settings.png/]]


Line 457:		Line 457:
	Afterwards type on the phone: Settings --> Maintenance (5) --> Synchronize Settings (4) --> Ok		Afterwards type on the phone: Settings --> Maintenance (5) --> Synchronize Settings (4) --> Ok

	[[File:Users admin Desktop App how to.png\|frameless\|875x875px\|~~deskphone_users_admin~~.png/\|users_admin_desktop_app_how_to.png/]]		[[File:Users admin Desktop App how to.png\|frameless\|875x875px\|users_admin_desktop_app_how_to.png/\|users_admin_desktop_app_how_to.png/]]

	[[File:DeskPhone Devices1.png\|frameless\|900x900px\|deskphone_devices1.png/\|deskphone_devices1.png/]]		[[File:DeskPhone Devices1.png\|frameless\|900x900px\|deskphone_devices1.png/\|deskphone_devices1.png/]]

	[[File:Snom Desktop app Devices list.png\|frameless\|790x790px\|~~deskphone_web-ui~~.png/\|snom_desktop_app_devices_list.png/]]		[[File:Snom Desktop app Devices list.png\|frameless\|790x790px\|snom_desktop_app_devices_list.png/\|snom_desktop_app_devices_list.png/]]

	[[File:Snom Phone Advanced settings.png\|frameless\|774x774px\|~~deskphone_devices2~~.png/\|snom_phone_advanced_settings.png/]]		[[File:Snom Phone Advanced settings.png\|frameless\|774x774px\|snom_phone_advanced_settings.png/\|snom_phone_advanced_settings.png/]]

	==Release Notes==		==Release Notes==