innovaphone wiki - Recent changes [en]

Howto:Productname - companyname - 3rd Party Product

Algo — Tue, 14 Apr 2026 20:20:57 GMT

Created page with "Creating Howto: Algo 8301 IP Paging Adapter & Scheduler - Algo - 3rd Party Product ==Product Name== Algo [https://www.algosolutions.com/product/8301-ip-paging-adapter-scheduler/ 8301 IP Paging Adapter & Scheduler] ==Certification Status==  ==Category==  ==Vendor== Algo Communication Products Ltd. is a manufacturer of network-based IP endpoints for voi..."

New page

Creating Howto: Algo 8301 IP Paging Adapter & Scheduler - Algo - 3rd Party Product

==Product Name==
Algo [https://www.algosolutions.com/product/8301-ip-paging-adapter-scheduler/ 8301 IP Paging Adapter & Scheduler]

==Certification Status==


==Category==


==Vendor==
Algo Communication Products Ltd. is a manufacturer of network-based IP endpoints for voice paging, emergency alerting, visual notification, intercom, and secure door entry applications. Algo products are designed for integration with unified communications, collaboration, and mass notification platforms. The company’s portfolio includes IP speakers, paging adapters, intercoms, visual alerters, display speakers, and endpoint management tools for commercial, education, healthcare, transportation, and industrial environments.

==Description==
The Algo 8301 IP Paging Adapter & Scheduler is a wideband SIP paging adapter designed to connect traditional analog amplifiers and legacy paging infrastructure to modern IP-based communication environments.

The 8301 emulates a page port similar to what is found on a legacy PBX or key system, allowing a traditional amplifier to be integrated into a VoIP or unified communications environment. This enables organizations to retain existing analog speaker infrastructure while adding SIP paging, multicast distribution, scheduled bells, automated announcements, emergency notifications, and other IP-based communication capabilities.

The device includes a balanced and isolated line output to reduce hum and noise when connected to an amplifier, and it also supports multicast audio transmission to additional Algo IP endpoints and compatible multicast-enabled phones. The 8301 is appropriate for education, retail, manufacturing, transportation, healthcare, and other environments where hybrid analog and IP paging is required.

==Functions==
The Algo 8301 IP Paging Adapter & Scheduler supports a range of functions for paging, alerting, scheduling, and hybrid analog/IP deployments.

Core functions include:
* SIP-based voice paging through registration as a 3rd-party SIP endpoint
* Integration of traditional analog amplifiers into IP and UC environments
* Scheduled bells, tones, and automated announcements synchronized to NTP
* Emergency, safety, security, and customer service audio notifications
* Multicast transmission to Algo IP speakers, paging adapters, display speakers, and compatible multicast-enabled phones
* Ring, page, and alert extension support
* Relay input and relay output support for connected accessories and external triggers
* Music input and background audio distribution
* Web interface configuration and centralized provisioning support

The 8301 can be deployed either as a SIP extension or as a multicast endpoint, depending on the communication design. In hybrid systems, it can provide local analog paging output while simultaneously distributing audio to IP endpoints over the network.

==Version==
Product versions used for interop testing:
* Algo 8301 IP Paging Adapter & Scheduler: version to be confirmed
* innovaphone firmware / software version: to be confirmed

==Configuration==
Configuration details will be completed based on the validated test setup.

The planned configuration section will include:
* innovaphone-side SIP configuration
* Algo 8301 SIP registration settings
* paging behavior and extension mapping
* multicast settings, if used
* audio output connection to amplifier
* relay input / output use, if applicable
* any deployment notes, limitations, or prerequisites identified during testing

==Summary==
The Algo 8301 IP Paging Adapter & Scheduler provides a practical bridge between legacy analog paging infrastructure and modern IP-based communication systems. It enables organizations to preserve existing amplifier and speaker investments while adding SIP paging, scheduling, multicast distribution, and emergency notification capabilities. Final interoperability details with innovaphone will be updated after test validation and configuration review.

==Contact==
{|
| Algo Communication Products Ltd.
|-
| Contact Name: to be confirmed
|-
| Burnaby, BC, Canada
|-
| Tel: +1 604-454-3790
|-
| Support: +1 604-454-3792
|-
| Mail: [mailto:info@algosolutions.com info@algosolutions.com]
|}

For additional information please refer to [https://www.algosolutions.com/contact-us/ our contact page].

User:Algo

Algo — Tue, 14 Apr 2026 15:42:19 GMT

User account Algo was created

Howto:DE - htp - SIP Trunk pure SIP-Provider (2026)

Twh — Tue, 14 Apr 2026 13:44:55 GMT

Created page with "== Summary == {{Template:SIP_TEST_STATUS_ongoing|update=April 1st, 2026|url=|productname=SIP_Trunk_pure|providername=htp}} === {{SIP_TEST_ISSUES_NO_MR_TITLE}} === {{SIP_TEST_ISSUES_NO_MR_INTRO}} ; EARLY MEDIA INBOUND : {{SIP_TEST_FACT_EARLY MEDIA INBOUND}} ; FAX T38 : {{SIP_TEST_FACT_FAX T38}} ; FAX T38ANDAUDIO : {{SIP_TEST_FACT_FAX T38ANDAUDIO}} ; MOBILITY : {{SIP_TEST_FACT_MOBILITY}} ; REDIR DIVHDR : {{SIP_TEST_FACT_REDIR DIVHDR}} ; REDIR HISTHDR : {{SIP_TEST_FACT_R..."

New page

== Summary ==
{{Template:SIP_TEST_STATUS_ongoing|update=April 1st, 2026|url=|productname=SIP_Trunk_pure|providername=htp}}

=== {{SIP_TEST_ISSUES_NO_MR_TITLE}} ===
{{SIP_TEST_ISSUES_NO_MR_INTRO}}
; EARLY MEDIA INBOUND : {{SIP_TEST_FACT_EARLY MEDIA INBOUND}}
; FAX T38 : {{SIP_TEST_FACT_FAX T38}}
; FAX T38ANDAUDIO : {{SIP_TEST_FACT_FAX T38ANDAUDIO}}
; MOBILITY : {{SIP_TEST_FACT_MOBILITY}}
; REDIR DIVHDR : {{SIP_TEST_FACT_REDIR DIVHDR}}
; REDIR HISTHDR : {{SIP_TEST_FACT_REDIR HISTHDR}}
; SDP RTCP MUX : {{SIP_TEST_FACT_SDP RTCP MUX}}
: {{SIP_TEST_FACT__unreliable}}
; SIP INFO : {{SIP_TEST_FACT_SIP INFO}}
; XFER CONS ALERT : {{SIP_TEST_FACT_XFER CONS ALERT}}
; XFER CONS : {{SIP_TEST_FACT_XFER CONS}}

{{SIP_TEST_FACTS_LIST}} [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_180_RINGING_FAILS|180_RINGING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_BASIC_CALL_FAILS|BASIC_CALL]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLIR_FAILS|CLIR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLNS_ONNET_FAILS|CLNS_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLNS_FAILS|CLNS]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_DIFF_FAILS|CONN_NR_DIFF]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_INCOMING_FAILS|CONN_NR_INCOMING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_FAILS|CONN_NR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_DTMF_FAILS|DTMF]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_EARLY_MEDIA_INBOUND_FAILS|EARLY_MEDIA_INBOUND]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_AUDIO_FAILS|FAX_AUDIO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38_ONNET_FAILS|FAX_T38_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38_FAILS|FAX_T38]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38ANDAUDIO_FAILS|FAX_T38ANDAUDIO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711A_ONNET_FAILS|G711A_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711A_FAILS|G711A]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711U_ONNET_FAILS|G711U_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711U_FAILS|G711U]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G722_ONNET_FAILS|G722_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G722_FAILS|G722]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G729_ONNET_FAILS|G729_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G729_FAILS|G729]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_HOLD_RETRIEVE_FAILS|HOLD_RETRIEVE]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_IP_FRAGMENTATION_FAILS|IP_FRAGMENTATION]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_LARGE_SIP_MESSAGES_FAILS|LARGE_SIP_MESSAGES]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_MOBILITY_FAILS|MOBILITY]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_OPUS_NB_FAILS|OPUS_NB]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_OPUS_WB_FAILS|OPUS_WB]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_RALERT_DISC_FAILS|RALERT_DISC]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_302_FAILS|REDIR_302]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_DIVHDR_FAILS|REDIR_DIVHDR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_HISTHDR_FAILS|REDIR_HISTHDR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REVERSE_MEDIA_FAILS|REVERSE_MEDIA]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_ICE_FAILS|SDP_ICE]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_RTCP_MUX_FAILS|SDP_RTCP_MUX]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_VIDEO_FAILS|SDP_VIDEO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SIP_INFO_FAILS|SIP_INFO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_INCOMING_FAILS|SRTP_INCOMING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_INTERNAL_FAILS|SRTP_INTERNAL]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_OUTGOING_FAILS|SRTP_OUTGOING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SUBSCRIBER_NR_FAILS|SUBSCRIBER_NR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_BLIND_FAILS|XFER_BLIND]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_ALERT_FAILS|XFER_CONS_ALERT]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_EXT_FAILS|XFER_CONS_EXT]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_FAILS|XFER_CONS]]

=== {{SIP_TEST_ISSUES_MR_TITLE}} ===
{{SIP_TEST_ISSUES_ALTERNATE_INTRO}}
{{SIP_TEST_ISSUES_MR_INTRO}}
{{SIP_TEST_ISSUES_NO_ALTERNATE_ISSUES}}

== Test Results ==
{{SIP_TEST_TESTRESULT_BOTH_INTRO}}
=== {{SIP_TEST_RESULTS_NO_MR_TITLE}} ===
; Registration : {{Template:SIP_Profile_Test_Registration_UDP_TCP_TLS}}

; NAT Traversal : {{Template:SIP_Profile_Test_NAT_a_no_c}}

; DTMF (RFC2833) : {{Template:SIP_Profile_Test_DTMF_RFC2833_yes}}

; Session Timer : {{Template:SIP_Profile_Test_EXPIRES_yes}}

; Redundancy : {{Template:SIP_Profile_Test_REDUNDANCY_yes_FAILOVER_no|timeout=2 minutes}}

; Correct signalling of Ringing-state : {{Template:SIP_Profile_Test_RINGING_yes}}

; CLIR : {{Template:SIP_Profile_Test_CLIR_yes}}

; Clip No Screening (CLNS) : {{Template:SIP_Profile_Test_CLNS_yes}} {{Template:SIP_Profile_Test_CLNS_clns_302_not_recommended}}

; COLP : {{Template:SIP_Profile_Test_COLP_out_yes_in_yes}} {{Template:SIP_Profile_Test_COLP_diff_no}}

; Early-Media : {{Template:SIP_Profile_Test_EARLY_MEDIA_INBOUND_no}}

; Fax : {{Template:SIP_Profile_Test_AUDIOFAX_PSTN_yes}} {{Template:SIP_Profile_Test_AUDIOFAX_PSTN_REQUIRES_EXCLUSIVE_CODEC|codec="G711A"}}
: {{Template:SIP_Profile_Test_T38_PSTN_no_onnet_yes_fallback_no}}

; Codecs : supported to/from PSTN: G711A
: supported onnet (VoIP to VoIP): G711A and G711U

; IP-Fragmentation : {{Template:SIP_Profile_Test_FRAGMENTATION_yes}}

; Large SIP messages : {{Template:SIP_Profile_Test_LARGE_MESSAGES_yes}}

; Reverse Media Negotiation : {{Template:SIP_Profile_Test_REV_MEDIA_NEG_yes}}

; Mobility Calls : {{Template:SIP_Profile_Test_MobilityCall_no_with_MediaRelay}}

; SRTP : {{Template:SIP_Profile_Test_SRTP_yes}}

; Dialing of Subscriber Numbers : {{Template:SIP_Profile_Test_SUBSCRIBER_NR_yes}}

; Call Transfer :
: {{Template:SIP_Profile_Test_CALL_TRANSFER_consconn}}
: {{Template:SIP_Profile_Test_CALL_TRANSFER_consalert}}

=== {{SIP_TEST_RESULTS_MR_TITLE}} ===
; Registration : {{Template:SIP_Profile_Test_Registration_UDP_TCP_TLS}}

; NAT Traversal : {{Template:SIP_Profile_Test_NAT_a_no_c}}

; DTMF (RFC2833) : {{Template:SIP_Profile_Test_DTMF_RFC2833_yes}}

; Session Timer : {{Template:SIP_Profile_Test_EXPIRES_yes}}

; Redundancy : {{Template:SIP_Profile_Test_REDUNDANCY_yes_FAILOVER_no|timeout=2 minutes}}

; Correct signalling of Ringing-state : {{Template:SIP_Profile_Test_RINGING_yes}}

; CLIR : {{Template:SIP_Profile_Test_CLIR_yes}}

; Clip No Screening (CLNS) : {{Template:SIP_Profile_Test_CLNS_yes}} {{Template:SIP_Profile_Test_CLNS_clns_302_not_recommended}}

; COLP : {{Template:SIP_Profile_Test_COLP_out_yes_in_yes}} {{Template:SIP_Profile_Test_COLP_diff_no}}

; Early-Media : {{Template:SIP_Profile_Test_EARLY_MEDIA_INBOUND_no}}

; Fax : {{Template:SIP_Profile_Test_AUDIOFAX_PSTN_yes}} {{Template:SIP_Profile_Test_AUDIOFAX_PSTN_REQUIRES_EXCLUSIVE_CODEC|codec="G711A"}}
: {{Template:SIP_Profile_Test_T38_PSTN_no_onnet_yes_fallback_no}}

; Codecs : supported to/from PSTN: G711A
: supported onnet (VoIP to VoIP): G711A and G711U

; IP-Fragmentation : {{Template:SIP_Profile_Test_FRAGMENTATION_yes}}

; Large SIP messages : {{Template:SIP_Profile_Test_LARGE_MESSAGES_yes}}

; Reverse Media Negotiation : {{Template:SIP_Profile_Test_REV_MEDIA_NEG_yes}}

; Mobility Calls : {{Template:SIP_Profile_Test_MobilityCall_no_with_MediaRelay}}

; SRTP : {{Template:SIP_Profile_Test_SRTP_yes}}

; Dialing of Subscriber Numbers : {{Template:SIP_Profile_Test_SUBSCRIBER_NR_yes}}

; Call Transfer :
: {{Template:SIP_Profile_Test_CALL_TRANSFER_consconn}}
: {{Template:SIP_Profile_Test_CALL_TRANSFER_consalert}}

==Configuration==
Use profile ''DE-htp-SIP_Trunk_pure'' in ''Gateway/Interfaces/SIP'' to configure this SIP provider.

Please note the following configuration hints:
* <nowiki>FAX requires exclusive G711A codec</nowiki>
* <nowiki>STUN required on all endpoints if media-relay is not used</nowiki>
* <nowiki>If you intend to use SIPS (SIP/TLS) registration, you need to add the ' DigiCert Global Root G2' certificate to the trust list of your SBC</nowiki>

: {{SIP_TEST_V12_HINT}}

== Disclaimer ==
{{SIP_TEST_PREFACE}}

[[Category:Compat|{{PAGENAME}}]]
[[Category:3rdParty SIP Provider|{{PAGENAME}}]]

Reference16r1:Concept App Service Projects

Elievens — Tue, 14 Apr 2026 13:21:48 GMT

Upgrade

← Older revision		Revision as of 15:21, 14 April 2026
Line 157:		Line 157:

	= Upgrade =		= Upgrade =
	== Prerequisites ==		===Prerequisites ===
	The App Platform must have at least version 140029. So make sure the AP has been upgraded before trying to upgrade Projects, otherwise an upgrade of Projects will not be possible.==		The App Platform must have at least version 140029. So make sure the AP has been upgraded before trying to upgrade Projects, otherwise an upgrade of Projects will not be possible.==

	== Upgrade ==		=== Upgrade ===
	An upgrade of the Projects App can be done via an '''Update via the App Store''' or via an '''Update Job of the Devices App'''.		An upgrade of the Projects App can be done via an '''Update via the App Store''' or via an '''Update Job of the Devices App'''.

	== Manual adjustments ==		=== Manual adjustments ===
	* Add the admin-mode to the Projects App Object. This can be done manual via the Advanced UI of the PBX or easier via the Projects Plugin of the Settings App (open the Projects App Object + click OK).		* Add the admin-mode to the Projects App Object. This can be done manual via the Advanced UI of the PBX or easier via the Projects Plugin of the Settings App (open the Projects App Object + click OK).
	* Add (if necesseary) a correct Timezone to the Application Platform. This can be done via the AP Manager (Settings/General/Timezone).		* Add (if necesseary) a correct Timezone to the Application Platform. This can be done via the AP Manager (Settings/General/Timezone).

Howto:DE - Firstcomeurope - Universe SIP Trunk SIP-Provider (2026)

Twh — Tue, 14 Apr 2026 13:21:22 GMT

Provider renamed and changed number mapping

← Older revision		Revision as of 15:21, 14 April 2026
Line 1:		Line 1:
	== Summary ==		== Summary ==
	{{Template:~~SIP_TEST_STATUS_complete~~\|update=~~December 28th~~, ~~2017~~\|url=https:\|productname=Universe_SIP_Trunk\|providername=~~CITEC_AG~~}}		{{Template:SIP_TEST_STATUS_ongoing\|update=April 14th, 2026\|url=https:\|productname=Universe_SIP_Trunk\|providername=Firstcomeurope}}
	=== Remarks ===		=== Remarks ===
	* CLNS only works if CGPN number sent has 12 digits (the 00 does not count), if shorter the call will be displayed as anonymous		* CLNS only works if CGPN number sent has 12 digits(the 00 does not count), if shorter the call will be displayed as anonymous

	* Alert not signalled, 'Carrier w/o Alerting' required in all PBX 'Mobility' objects		* Alert not signalled, 'Carrier w/o Alerting' required in all PBX 'Mobility' objects
Line 10:		Line 10:
	* Dialling of subscriber numbers not possible, 'Dialing Location' must be configured without 'Area Code'		* Dialling of subscriber numbers not possible, 'Dialing Location' must be configured without 'Area Code'

	~~<internal>Provider SBC: User-Agent: Universe 1.0</internal>~~


Line 44:		Line 43:
	; CLIR : {{Template:SIP_Profile_Test_CLIR_yes}}		; CLIR : {{Template:SIP_Profile_Test_CLIR_yes}}

	; COLP : {{Template:SIP_Profile_Test_COLP_out_yes_in_yes}}{{Template:SIP_Profile_Test_COLP_diff_no}}		; COLP : {{Template:SIP_Profile_Test_COLP_out_yes_in_yes}} {{Template:SIP_Profile_Test_COLP_diff_no}}

	; Early-Media : {{Template:SIP_Profile_Test_EARLY_MEDIA_INBOUND_yes}}		; Early-Media : {{Template:SIP_Profile_Test_EARLY_MEDIA_INBOUND_yes}}
Line 73:		Line 72:

	==Configuration==		==Configuration==
	Use profile ''DE-~~CITEC_AG~~-Universe_SIP_Trunk'' in ''Gateway/Interfaces/SIP'' to configure this SIP provider.		Use profile ''DE-Firstcomeurope-Universe_SIP_Trunk'' in ''Gateway/Interfaces/SIP'' to configure this SIP provider.

	Please note the following configuration hints:		Please note the following configuration hints:

Reference16r1:Concept App Service Projects

Elievens — Tue, 14 Apr 2026 13:20:59 GMT

Upgrade

← Older revision		Revision as of 15:20, 14 April 2026
(3 intermediate revisions by the same user not shown)
Line 157:		Line 157:

	= Upgrade =		= Upgrade =
			== Prerequisites ==
			The App Platform must have at least version 140029. So make sure the AP has been upgraded before trying to upgrade Projects, otherwise an upgrade of Projects will not be possible.==

			== Upgrade ==
			An upgrade of the Projects App can be done via an '''Update via the App Store''' or via an '''Update Job of the Devices App'''.

			== Manual adjustments ==
			* Add the admin-mode to the Projects App Object. This can be done manual via the Advanced UI of the PBX or easier via the Projects Plugin of the Settings App (open the Projects App Object + click OK).
			* Add (if necesseary) a correct Timezone to the Application Platform. This can be done via the AP Manager (Settings/General/Timezone).

	= Troubleshooting =		= Troubleshooting =

Howto:DE - CITEC AG - Universe SIP Trunk SIP-Provider (2017)

Twh — Tue, 14 Apr 2026 13:11:22 GMT

Twh moved page Howto:DE - CITEC AG - Universe SIP Trunk SIP-Provider (2017) to Howto:DE - Firstcomeurope - Universe SIP Trunk SIP-Provider (2026)

New page

== Summary ==
{{Template:SIP_TEST_STATUS_complete|update=December 28th, 2017|url=https:|productname=Universe_SIP_Trunk|providername=CITEC_AG}}
=== Remarks ===
* CLNS only works if CGPN number sent has 12 digits (the 00 does not count), if shorter the call will be displayed as anonymous

* Alert not signalled, 'Carrier w/o Alerting' required in all PBX 'Mobility' objects

* 'Set Calling = Diverting No' recommended in PBX 'Trunk' objects

* Dialling of subscriber numbers not possible, 'Dialing Location' must be configured without 'Area Code'

<internal>Provider SBC: User-Agent: Universe 1.0</internal>

=== {{SIP_TEST_ISSUES_MR_TITLE}} ===
{{SIP_TEST_ISSUES_MR_INTRO}}
; 180 RINGING : {{SIP_TEST_FACT_180 RINGING}}
; FAX T38 ONNET : {{SIP_TEST_FACT_FAX T38 ONNET}}
; FAX T38 : {{SIP_TEST_FACT_FAX T38}}
; FAX T38ANDAUDIO : {{SIP_TEST_FACT_FAX T38ANDAUDIO}}
; REDIR 302 : {{SIP_TEST_FACT_REDIR 302}}
; REDIR DIVHDR : {{SIP_TEST_FACT_REDIR DIVHDR}}
; REDIR HISTHDR : {{SIP_TEST_FACT_REDIR HISTHDR}}
; REVERSE MEDIA : {{SIP_TEST_FACT_REVERSE MEDIA}}

{{SIP_TEST_FACTS_LIST}} [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_180_RINGING_FAILS|180_RINGING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_BASIC_CALL_FAILS|BASIC_CALL]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLIR_FAILS|CLIR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_DIFF_FAILS|CONN_NR_DIFF]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_INCOMING_FAILS|CONN_NR_INCOMING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_FAILS|CONN_NR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_DTMF_FAILS|DTMF]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_EARLY_MEDIA_INBOUND_FAILS|EARLY_MEDIA_INBOUND]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_AUDIO_FAILS|FAX_AUDIO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38_ONNET_FAILS|FAX_T38_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38_FAILS|FAX_T38]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38ANDAUDIO_FAILS|FAX_T38ANDAUDIO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711A_ONNET_FAILS|G711A_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711A_FAILS|G711A]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711U_ONNET_FAILS|G711U_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711U_FAILS|G711U]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G722_ONNET_FAILS|G722_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G722_FAILS|G722]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_HOLD_RETRIEVE_FAILS|HOLD_RETRIEVE]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_IP_FRAGMENTATION_FAILS|IP_FRAGMENTATION]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_LARGE_SIP_MESSAGES_FAILS|LARGE_SIP_MESSAGES]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_MOBILITY_FAILS|MOBILITY]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_RALERT_DISC_FAILS|RALERT_DISC]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_302_FAILS|REDIR_302]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_DIVHDR_FAILS|REDIR_DIVHDR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_HISTHDR_FAILS|REDIR_HISTHDR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REVERSE_MEDIA_FAILS|REVERSE_MEDIA]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_ICE_FAILS|SDP_ICE]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_RTCP_MUX_FAILS|SDP_RTCP_MUX]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_VIDEO_FAILS|SDP_VIDEO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SIP_INFO_FAILS|SIP_INFO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_INCOMING_FAILS|SRTP_INCOMING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_INTERNAL_FAILS|SRTP_INTERNAL]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_OUTGOING_FAILS|SRTP_OUTGOING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SUBSCRIBER_NR_FAILS|SUBSCRIBER_NR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_BLIND_FAILS|XFER_BLIND]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_ALERT_FAILS|XFER_CONS_ALERT]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_EXT_FAILS|XFER_CONS_EXT]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_FAILS|XFER_CONS]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G729_FAILS|G729]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G729_ONNET_FAILS|G729_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_OPUS_WB_FAILS|OPUS_WB]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_OPUS_NB_FAILS|OPUS_NB]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLNS_FAILS|CLNS]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLNS_ONNET_FAILS|CLNS_ONNET]]

== Test Results ==
{{SIP_TEST_TESTRESULT_ONLYMR_INTRO}}
=== {{SIP_TEST_RESULTS_MR_TITLE}} ===
; Registration : {{Template:SIP_Profile_Test_Registration_UDP}}

; NAT Traversal : {{Template:SIP_Profile_Test_NAT_a_no_c}}

; DTMF (RFC2833) : {{Template:SIP_Profile_Test_DTMF_RFC2833_yes}}

; Session Timer : {{Template:SIP_Profile_Test_EXPIRES_yes}}

; Redundancy : {{Template:SIP_Profile_Test_REDUNDANCY_yes_FAILOVER_no|timeout=2 minutes}}

; Correct signalling of Ringing-state : {{Template:SIP_Profile_Test_RINGING_no}}

; CLIR : {{Template:SIP_Profile_Test_CLIR_yes}}

; COLP : {{Template:SIP_Profile_Test_COLP_out_yes_in_yes}}{{Template:SIP_Profile_Test_COLP_diff_no}}

; Early-Media : {{Template:SIP_Profile_Test_EARLY_MEDIA_INBOUND_yes}}

; Fax : {{Template:SIP_Profile_Test_AUDIOFAX_PSTN_yes}}
: {{Template:SIP_Profile_Test_T38_PSTN_no_onnet_no_fallback_no}}

; Codecs : supported to/from PSTN: G711A, G711U and G722
: supported onnet (VoIP to VoIP): G711A, G711U and G722

; IP-Fragmentation : {{Template:SIP_Profile_Test_FRAGMENTATION_yes}}

; Large SIP messages : {{Template:SIP_Profile_Test_LARGE_MESSAGES_yes}}

; Reverse Media Negotiation : {{Template:SIP_Profile_Test_REV_MEDIA_NEG_no}}

; Mobility Calls : {{Template:SIP_Profile_Test_MobilityCall_yes}} {{Template:SIP_Profile_Test_MobilityCall_no_ringing}}

; SRTP : {{Template:SIP_Profile_Test_SRTP_no}}

; Dialing of Subscriber Numbers : {{Template:SIP_Profile_Test_SUBSCRIBER_NR_no}}

; Call Transfer : {{Template:SIP_Profile_Test_CALL_TRANSFER_ok}}

; Clip No Screening (CLNS) : {{Template:SIP_Profile_Test_CLNS_yes}}

==Configuration==
Use profile ''DE-CITEC_AG-Universe_SIP_Trunk'' in ''Gateway/Interfaces/SIP'' to configure this SIP provider.

Please note the following configuration hints:
* <nowiki>Alert not signalled, 'Carrier w/o Alerting' required in all PBX 'Mobility' objects</nowiki>
* <nowiki>Dialling of subscriber numbers not possible, 'Dialing Location' must be configured without 'Area Code'</nowiki>

: {{SIP_TEST_V12_HINT}}

== Disclaimer ==
{{SIP_TEST_PREFACE}}

[[Category:Compat|{{PAGENAME}}]]
[[Category:3rdParty SIP Provider|{{PAGENAME}}]]

Reference16r1:Concept App Service Projects

Elievens — Tue, 14 Apr 2026 13:06:57 GMT

Requirements

← Older revision		Revision as of 15:06, 14 April 2026
(16 intermediate revisions by the same user not shown)
Line 2:		Line 2:
	[[Category:Concept App Service Projects]]		[[Category:Concept App Service Projects]]
	<!-- Project Management Sprints Backlog Tasks Templates -->		<!-- Project Management Sprints Backlog Tasks Templates -->

			{{FIXME\|reason=This product is in the beta phase and is not yet finished}}


	= Overview =		= Overview =
	The App Service Projects provides useful functionality to manage projects. It is built-on an hierarchical structure of areas, projects, backlog, sprints and tasks.		The App Service Projects provides useful functionality to manage projects. It is built-on an hierarchical structure of areas, projects, backlog, sprints and tasks.
	Projects uses the Connect Api to post messages automatically at specified events, e.g. task status updates, and integrates the Connect App window to allow user posts.		Projects uses the Connect Api to post messages automatically at specified events, e.g. task status updates, and integrates the Connect App window to allow user posts.

			== New V16r1 features ==

	= General Information =		= General Information =
Line 72:		Line 78:
	= Requirements =		= Requirements =
	* Connect App		* Connect App
	* The Application Platform must be at least version ~~120004~~		* The Application Platform must be at least '''version 140029''' <small>'''[new in V16r1]'''</small>
			* The Application Platform must have the '''correct time''' and a '''Timezone''' set <small>'''[new in V16r1]'''</small>
	* License “App(innovaphone-projects)xx” (order no. 02-00050-014). </br> '''Free version available'''.		* License “App(innovaphone-projects)xx” (order no. 02-00050-014). </br> '''Free version available'''.

Line 134:		Line 141:

	== Apps ==		== Apps ==
	Only one PBX App ~~object~~ is ~~used and~~ needed.		Only one well-configured PBX App Object needed is needed for the Projects-App. <br />
			This App Object is best created/adjusted via that projects-plugin of the Settings App.

	Parameters of the PBX App object:		Parameters of the PBX App object:
	<pre>URL: https://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-projects</pre>		<pre>URL: https://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-projects</pre>

	=== ~~Under tab~~ "App" ===		=== "App"-tab ===
	To allow ~~posting to Connect App:~~		;Modes: admin ''(to allow an extra Admin-mode)'' <small>'''[new in V16r1]'''</small>
	;WebSocket: needed		;WebSocket: needed ''(to allow Connect-postings)''
	;Services: needed		;Services: needed ''(to allow Connect-postings)''

			=== "Apps"-tab ===
			;connect: ticked ''(to allow Projects to maintain Projects zones in Connect)''
			;connect~admin-service: ''ticked (to allow Projects to maintain Projects zones in Connect)''

	==~~= Under tab "Apps" ===~~		= Upgrade =
	~~To allow Projects to maintain Projects zones in Connect:~~
	~~;connect: ticked~~
	~~;connect~admin-service: ticked~~

	= Troubleshooting =		= Troubleshooting =
Line 171:		Line 180:
	<br>		<br>
	By editing the area the connection establishment will be restarted.		By editing the area the connection establishment will be restarted.

			== Projects cannot be upgraded ==
			The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. <br/>
			See: [[Howto16r1:Firmware_Upgrade_V15r1_V16r1#AP_Upgrade_to_Image_140029_or_newer\|'Upgrade to Image 140029 or newer']] or [[Howto16r1:Firmware_Upgrade_V15r1_V16r1#Projects\|'Manual Steps needed after upgarde -> Projects']].

			== Extra Admin Features are not available ==
			Check if the Project App Object in the PBX does have an '''"admin"-mode''' and that the user does have the '''"projects~admin"-app''' selected.

			== Auto Cleanup or automatic Task Status Updates do not work ==
			Check the settings of the '''App Platform''' (AP Manager/Settings/General); the '''correct time''' together with a '''Timezone''' must be available.

	= Related Articles =		= Related Articles =
	* [[Reference15r1:Apps/PbxManager/App Projects]]		* [[Reference15r1:Apps/PbxManager/App Projects]]
	* [[Reference15r1:Concept App Connect]]		* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

Elievens — Tue, 14 Apr 2026 12:21:48 GMT

Created page with "Apps Category:Concept App Service Projects  = Overview = The App Service Projects provides useful functionality to manage projects. It is built-on an hierarchical structure of areas, projects, backlog, sprints and tasks. Projects uses the Connect Api to post messages automatically at specified events, e.g. task status updates, and integrates the Connect App window to allow user posts...."

New page

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

= Overview =
The App Service Projects provides useful functionality to manage projects. It is built-on an hierarchical structure of areas, projects, backlog, sprints and tasks.
Projects uses the Connect Api to post messages automatically at specified events, e.g. task status updates, and integrates the Connect App window to allow user posts.

= General Information =
== Projects items ==
Projects items consist of description, status and responsible person like project owner, sprint manager or task handler.

=== Areas ===
The highest level items on the hierarchical structure of projects. E.g. to combine all projects of a department.
 User access rights to the whole area including all lower level items are defined during area definition. Three access levels are provided: public, user group specific or private areas.
 User groups are defined in the PBX. Protected areas and all their lower level items are invisible for unauthorized users.
 Areas may be defined as zones in Connect.

=== Projects ===
A project consists of its description, status, the owner information and the area it belongs too. Projects may be filtered on area, project owner and/or attribute.
Projects typically contain several sprints and backlog entries.
Project tiles provides information about their sprints, backlog entries and tasks and a progress bar estimated on the story points of closed tasks / the story points of all tasks.

=== Backlog ===
Container for any tasks and ideas to a project which are not in work yet. Backlog entries may be filtered on area, project, backlog entry handler and/or attribute.

=== Sprints ===

Sprints specify closed units of work which are subdivided typically in several tasks.
Sprint tiles provides information about their tasks and a progress bar estimated on the story points of closed tasks / the story points of all tasks.
A sprint consists of its description, status, the manager information and the project it belongs too. Sprints may be filtered on area, project, sprint manager and/or attribute.

=== Tasks ===

Tasks are small units of work which are mostly handled by one person.
A task consists of its description, status, the handler information and the sprint it belongs too. Tasks may be filtered on area, project, sprint, task handler and/or attribute.

== Other items and Projects users ==

=== Attributes ===
Attributes are free defined, area independent flags. They may be assigned to all item types except areas. Attributes may be used as filter criteria.

=== Templates ===
To define sprint and task templates for specific workflows.

=== Projects users ===
Users are added automatically to projects as soon as they are logged in the first time. Only registered users can be assigned to Projects items.

== Projects App UI concepts ==
The App Projects UI is subdivided into tabs that provide a structure that helps to organize projects, reflecting the Project Items: '''[[#Areas|Areas]]''', '''[[#Projects|Projects]]''', '''[[#Sprints|Sprints]] / [[#Backlog|Backlog]]''' and '''[[#Tasks|Tasks]]'''.

Other extra tabs provide additional functionalities: '''[[#Attributes|Attributes]]''', '''[[#Templates|Templates]]''' and '''[[#Users|Users]]'''.

The '''Home'''-tab gives a quick and useful overview of all Current tasks and pinned Users/Areas/Projects and Sprints.

Projects, Sprints and Tabs each consist of a board organising the '''Backlog''' or '''Planned''', '''Current''' and '''Closed''' items.

=== Filters ===
When selecting an item, it works as filter on lower level items. E.g. if an area is selected, only projects of that area are provided. All active filter definitions are shown in the corresponding tabs and may be removed there.

=== Item search ===
Item title / ID search is provided for projects, sprints, backlog entries and tasks in the corresponding tabs. The item search does not consider user filters.

== Synchronisation ==
Updates on Projects items are synchronized immediately.

== Using Projects App in combination with Connect App ==
When using Projects combined with Connect App new items defined in Projects or updates on items e.g. status changes are posted to Connect App. 
The Zone has to be defined in Projects area definition and is used in all lower level items of the area. 
Users are notified about item assignments and will be able to add comments / own posts on items. 
[[#Project cannot see the Connect-discussion|Checks when having issues]]

= Requirements =
* Connect App
* The Application Platform must be at least version 120004
* License “App(innovaphone-projects)xx” (order no. 02-00050-014). '''Free version available'''.

= License =
* This is a user licence. This licence is debited if the function is configured on a user in the PBX - regardless of use.
* The Projects app licence version must be greater than or equal to the PBX software version and app software version in use (see: Licence version).
* The private area is available for every user and can also be used without a licence (free version).
* The Connect app (installation without licences) is required to use all the functions of Projects.
* Only a user licence is required for the Projects app. Further licences such as the port licence are not required!

== Free version ==
An unlicensed user can also use Projects, but is restricted to their own area and can only use Projects to manage their own tasks. 
However, an unlicensed user cannot see any cross-departmental areas, projects, sprints or tasks.

= Configuration =
== Settings App/App Installer ==
# Install the Projects App on the App Platform via the 'Settings App/App Installer'-plugin:
#* Open the Settings App
#* Open the app installer plugin
#* Read and accept the Terms and Conditions of the App Installer (if not done yet)
#* Search ''projects''
#* Select the Projects-App
#* Select the correct version and click Install
#* Read and accept the Terms and Conditions of the Projects App and click Install
# Add an App-Object via the Projects-plugin of the Settings App:
#* Close and Re-Open the Settings App
#* Open the Projects-plugin
#* Click on Add an app; Select 'Projects' and complete the form:
#** Name: ''Projects''
#** SIP: ''projects''
#** Connect App: select the correct Connect-App (default ''connect'')
#** Connect Admin App: should be updated automatically to the previous Connect App appended with ~admin-service (default ''connect~admin-service''). If nothing can be selected, see: [[#Projects-plugin_cannot_see_the_Connect_Admin_Service|Troubleshooting]].
#** (Optional) Assign the Projects-App to an existing Template
# Assign the Projects App to authorized users using a Config Template and/or directly on the User Object(s)
# Assign 'App(innovaphone-project)xx'-licenses to the authorized users (or try the free version)

== AP Manager/App Store ==
Installing the Project App via the 'Settings App/App Installer'-plugin is the preferred/easier method, but a complete manual install is also possible.
# Install the Projects App on the App Platform via the App Store:
#* Open the AP Manager
#* Open the App Store
#* Read and accept the Terms and Conditions of the App Installer (if not done yet)
#* Search ''projects''
#* Select the Projects-App
#* Select the correct version and click Install
#* Read and accept the Terms and Conditions of the Projects App and click Install
# Add an instance of the Projects App on the App Platform:
#* Close the App Store
#* Open the newly installed Projects App
#* Click on '+ Add' to add a new Projects Instances and complete the form:
#** Name: ''projects''
#** Domain: {System Name} (found under PBX/Config/General)
#** Password: {strong password}
#** Database password: {strong password}
# Select and Start the instance
# Create a PBX-object:
#* Via the Settings App Plugin (see above)
#* Via the PBX Advanced UI (see below for settings)
# Assign the Projects App to authorized users using a Config Template and/or directly on the User Object(s)
# Assign 'App(innovaphone-project)'-licenses to the authorized users (or try the free version)

== Apps ==
Only one PBX App object is used and needed.

Parameters of the PBX App object:
<pre>URL: https://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-projects</pre>

=== Under tab "App" ===
To allow posting to Connect App:
;WebSocket: needed
;Services: needed

=== Under tab "Apps" ===
To allow Projects to maintain Projects zones in Connect:
;connect: ticked
;connect~admin-service: ticked

= Troubleshooting =
== Projects-plugin cannot see the Connect Admin Service ==
* Check that the Connect App has an ''''admin-service''''-mode configured (modes-field can be found in the 'App'-tab of the object). See: https://wiki.innovaphone.com/index.php?title=Howto15r1:Firmware_Upgrade_V14r2_V15r1#Connect

== Project cannot see the Connect-discussion ==
Both the Project App and the User using the Project App must be checked for the necessary settings:

'''Project''' App object:
* Check that the Project App has ''''WebSocket'''' and ''''Services'''' ticked ('App'-tab).
* Check that the Project App has ''''connect'''' and ''''connect~admin-service'''' ticked ('Apps'-tab)
* Open the Project App/Areas + edit an Area. Check the 'Connect zone setup state':
** Green: connection OK
** Orange: connection not yet established
** Red: connection NOK

'''User''' Object using the Project App:
* Check if the User using Projects has ''''connect'''' ticked in the 'Apps'-tab (best deployed via a global Template; e.g. the default 'Config User').

== Area Not Connected (Orange/Red) ==
Check the previous Troubleshoot-item (''Project cannot see the Connect-discussion'') and edit the Area (via the Pencil-icon).
 
By editing the area the connection establishment will be restarted.

= Related Articles =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Howto:XQv Recording - XQTING - Partner App

JanVidts — Tue, 14 Apr 2026 09:22:32 GMT

Compatible innovaphone firmware versions

← Older revision		Revision as of 11:22, 14 April 2026
Line 5:		Line 5:
	<!-- Mandatory topic. -->		<!-- Mandatory topic. -->
	<!-- Place product logo. Use the application-tile-logo. Don't change logo size. -->		<!-- Place product logo. Use the application-tile-logo. Don't change logo size. -->
	[[Image:XQv_Recording.png\|100px\|xqv_recording.png/]]		[[Image:XQv_Recording.png\|100px\|xqv_recording.png/\|xqv_recording.png/]]
	<!-- replace CompanyName & ProductName by real names and add URL to productpage -->		<!-- replace CompanyName & ProductName by real names and add URL to productpage -->
	XQTING [https://www.xqting.com/products/XQv-Recording XQv Recording]		XQTING [https://www.xqting.com/products/XQv-Recording XQv Recording]
Line 52:		Line 52:
	Using transcripts provides valuable information without the need of listening to entire recordings.		Using transcripts provides valuable information without the need of listening to entire recordings.

	[[Image:App_logo_recording.png\|150px\|~~App_logo_recording~~.png/\|app_logo_recording.png/]]		[[Image:App_logo_recording.png\|150px\|app_logo_recording.png/\|app_logo_recording.png/]]


Line 80:		Line 80:
	The User Interface for the administrator and supervisor is launched as an app from within innovaphone, and interacts with the core module		The User Interface for the administrator and supervisor is launched as an app from within innovaphone, and interacts with the core module

	[[Image:Concept-Architecture_422x409.png\|150px\|~~Concept~~-~~Architecture_422x409~~.png/\|concept-architecture_422x409.png/]]		[[Image:Concept-Architecture_422x409.png\|150px\|concept-architecture_422x409.png/\|concept-architecture_422x409.png/]]

	Detailed functional documentation is available: [https://documentation.xqting.be/en/XQv_Recording here]		Detailed functional documentation is available: [https://documentation.xqting.be/en/XQv_Recording here]
Line 134:		Line 134:
	<!-- List compatible major innovaphone firmware versions. Several listings are valid -->		<!-- List compatible major innovaphone firmware versions. Several listings are valid -->
	* innovaphone V13r onwards		* innovaphone V13r onwards
			Supports the web-based version of MyApps, not myApps for Windows.

	===Application versions used for interop testing===		===Application versions used for interop testing===
	<!-- Give used versions for testing of both innovaphone and 3rd-pty product -->		<!-- Give used versions for testing of both innovaphone and 3rd-pty product -->

Howto:Contacts Manager - MediaRunway - Partner App

Vsc — Tue, 14 Apr 2026 08:23:04 GMT

Licensing

← Older revision		Revision as of 10:23, 14 April 2026
Line 123:		Line 123:
	Licensing: innovaphone licensing		Licensing: innovaphone licensing

	The number of Contacts Manager licenses to be purchased depends on the number of port licenses used. [https://www.innovaphone.com/de/services/~~lizenzen~~/partner-~~apps~~.html?app=~~Analytics&type=license#contactsmanager~~ Here you will find the list how many licenses are need].		The number of Contacts Manager licenses to be purchased depends on the number of port licenses used. [https://www.innovaphone.com/en/services/licenses/partner-app-licenses.html?app=contacts%20manager Here you will find the list how many licenses are need].


	==Prerequisites==		==Prerequisites==

Reference16r1:Concept App Service Devices

Vsc — Tue, 14 Apr 2026 07:08:37 GMT

Supported DECT handsets

← Older revision		Revision as of 09:08, 14 April 2026
(2 intermediate revisions by the same user not shown)
Line 510:		Line 510:

	=== Supported DECT handsets ===		=== Supported DECT handsets ===

	The following handsets are supported for update jobs and the DECT handsets configuration:		The following handsets are supported for update jobs and the DECT handsets configuration:
			* innovaphone IP64
	* IP64		* innovaphone IP65
	* IP65		* Ascom d81
	* ~~D81~~		* Ascom d83
	* ~~D83~~

	== Known issues ==		== Known issues ==

Reference16r1:Concept Reconnect Calls

Sga — Mon, 13 Apr 2026 14:51:41 GMT

Known Issues

← Older revision		Revision as of 16:51, 13 April 2026
Line 41:		Line 41:

	Once this call is transparently connected (user is not aware of the reconnect process) the old call is cleared up.		Once this call is transparently connected (user is not aware of the reconnect process) the old call is cleared up.

			==Limitations==
			* not supported for IP73 Wifi-endpoints and IP-DECT endpoints

	== Known Issues ==		== Known Issues ==
Line 49:		Line 52:
	* Calls in a conference are not reconnected at the moment.		* Calls in a conference are not reconnected at the moment.
	* Non successfully Reconnect Calls will be shown in the call list.		* Non successfully Reconnect Calls will be shown in the call list.
			* Reconnect calls don't work for calls to/from analog interfaces

Reference13r1:PBX/Objects/Edit Forks

Kpe — Mon, 13 Apr 2026 10:49:50 GMT

← Older revision		Revision as of 12:49, 13 April 2026
Line 1:		Line 1:
	With this page call forking can be configured for a user. This means a call for this user is not only sent to endpoints registered to the user object, but also to the forking destination. If a mobility object is configured for the forking, the phone identified by the forking destination can use the mobility functions. A delay can be configured for the call to the mobile endpoint. This delay is not supported for normal call forking without mobility functions. Operator calls from a waiting queue require a UC license to be sent to forking destinations.		With this page call forking can be configured for a user. This means a call for this user is not only sent to endpoints registered to the user object, but also to the forking destination. If a mobility object is configured for the forking, the phone identified by the forking destination can use the mobility functions. A delay can be configured for the call to the mobile endpoint. This delay is not supported for normal call forking without mobility functions. Operator calls from a waiting queue require a UC license to be sent to forking destinations.

	;No/Name: Forking destination		;No/Name: Forking destination, Mobility destination (the mobility destination must be a '''unique''' number, you cannot add the same number for different users)

	;Bool/Not: The forking can be turned on and off by a Boolean object. With the '''Not''' checkmark the state is inverted.		;Bool/Not: The forking can be turned on and off by a Boolean object. With the '''Not''' checkmark the state is inverted.
Line 9:		Line 9:
	For the function of the Mobility features a Mobility license must be installed.		For the function of the Mobility features a Mobility license must be installed.

	;Object: The [[Reference9:PBX/Objects/Mobility \| Mobility]] Object (Long Name) must be set, if the mobile endpoint (GSM Phone) needs to use the [[Reference8:Administration/PBX/Objects/Mobility \| mobility features]].		;Object: The [[Reference9:PBX/Objects/Mobility\| Mobility]] Object (Long Name) must be set, if the mobile endpoint (GSM Phone) needs to use the [[Reference8:Administration/PBX/Objects/Mobility\| mobility features]].
	: Mobility license is required		: Mobility license is required

Line 18:		Line 18:
	;Delay: A Delay in seconds can be configured to call the mobile endpoint.		;Delay: A Delay in seconds can be configured to call the mobile endpoint.

	;Disable: Disabling the Mobility features for the mobile device, this can also be en/disabled via [[Reference8:Administration/PBX/Objects/~~DTMF_Features~~#Enable.~~2Fdisable_mobility~~ \|DTMF featurecodes]]		;Disable: Disabling the Mobility features for the mobile device, this can also be en/disabled via [[Reference8:Administration/PBX/Objects/DTMF Features#Enable.2Fdisable mobility\|DTMF featurecodes]]

	;Call-Waiting: Enable or disable call-waiting for the mobile endpoint, if a mobile endpoint is in a call a call waiting tone will be played from the PBX to the mobile endpoint via the RTP stream. See [[Reference9:PBX/Objects/Mobility \| R-Key Functions]] for waiting calls handling options.		;Call-Waiting: Enable or disable call-waiting for the mobile endpoint, if a mobile endpoint is in a call a call waiting tone will be played from the PBX to the mobile endpoint via the RTP stream. See [[Reference9:PBX/Objects/Mobility\| R-Key Functions]] for waiting calls handling options.
	: Mobility features are required		: Mobility features are required

Line 31:		Line 31:
	: Mobility features are required		: Mobility features are required

	[[Category:~~Concept_App_RCC~~\|Related]]		[[Category:Concept App RCC\|Related]]

Reference13r2:Gateway/Interfaces/SIP

Nwe — Mon, 13 Apr 2026 10:48:45 GMT

← Older revision		Revision as of 12:48, 13 April 2026
Line 122:		Line 122:
	; /get-cdpn-from-to-uri : get CDPN of incoming provider-calls from To-URI instead of Request-URI		; /get-cdpn-from-to-uri : get CDPN of incoming provider-calls from To-URI instead of Request-URI
	; /prefer-pai : get CGPN from PAI/PPI/RPID if present		; /prefer-pai : get CGPN from PAI/PPI/RPID if present
			; /take-sendonly-as-inactive on : some endpoints use sendonly instead of inactive (Useful if no MOH is played when hold is used from a SIP-Endpoint)
	; /no-diverting-name: don't add display name to diverting party URI		; /no-diverting-name: don't add display name to diverting party URI
	; /installed-certificate: for SIP/TLS trunks where the installed certificate should be used instead of the build-in device certificate		; /installed-certificate: for SIP/TLS trunks where the installed certificate should be used instead of the build-in device certificate

Reference16r1:Apps/PbxManager/Email

Vsc — Mon, 13 Apr 2026 09:57:36 GMT

← Older revision		Revision as of 11:57, 13 April 2026
Line 1:		Line 1:
	{{FIXME\|reason=This product is in the beta phase and is not yet finished}}		{{FIXME\|reason=This product is in the beta phase and is not yet finished}}
	This PBX Manager Plugin configures the E-Mail Account of all PBXes in the system. The same configuration can be found in the advanced UI of the individual PBXes at [[~~Reference13r2~~:PBX/Config/Authentication\|PBX/Config/Authentication]].		This PBX Manager Plugin configures the E-Mail Account of all PBXes in the system. The same configuration can be found in the advanced UI of the individual PBXes at [[{{NAMESPACE}}:PBX/Config/Authentication\|PBX/Config/Authentication]].

	== Add Email Account ==		== Add Email Account ==

Reference15r1:Concept Conference

Vsc — Mon, 13 Apr 2026 08:47:59 GMT

← Older revision		Revision as of 10:47, 13 April 2026
(One intermediate revision by the same user not shown)
Line 8:		Line 8:

	= Overview =		= Overview =
	The innovaphone conference is provided by the [[~~Reference13r1~~:PBX/Objects/Conference\| PBX Conference Object]]. It is used to create conference rooms which allows audio, video, application sharing and chat between all participants. The conference rooms can be joined via phone, WebRTC using any browser or myApps.		The innovaphone conference is provided by the [[{{NAMESPACE}}:PBX/Objects/Conference\| PBX Conference Object]]. It is used to create conference rooms which allows audio, video, application sharing and chat between all participants. The conference rooms can be joined via phone, WebRTC using any browser or myApps.

	= Requirements =		= Requirements =
Line 20:		Line 20:
	= Features =		= Features =
	* Audio Conferencing		* Audio Conferencing
	* Multi Video as described in [[~~Reference13r3~~:Concept Multi-Video-Conference\| this wiki article]]		* Multi Video as described in [[{{NAMESPACE}}:Concept Multi-Video-Conference\| this wiki article]]
	* Application sharing		* Application sharing
	* Chat		* Chat
	* Apps		* Apps
	* Using an innovaphone conference interface according to [[~~Reference13r1~~:Gateway/Interfaces\| this wiki article]]		* Using an innovaphone conference interface according to [[{{NAMESPACE}}:Gateway/Interfaces\| this wiki article]]
	* Various voice prompts listed in [[~~Reference13r3~~:PBX/Objects/Conference/Announcement types\| this wiki article]]		* Various voice prompts listed in [[{{NAMESPACE}}:PBX/Objects/Conference/Announcement types\| this wiki article]]
	* PBX Manager Plugin as described in [[~~Reference13r3~~:Apps/PbxManager/Conference\| this wiki article]]		* PBX Manager Plugin as described in [[{{NAMESPACE}}:Apps/PbxManager/Conference\| this wiki article]]
	* Web Access as described in [[~~Reference13r3~~:Concept Conference Web Access\| this wiki article]]		* Web Access as described in [[{{NAMESPACE}}:Concept Conference Web Access\| this wiki article]]
	* Meeting scheduling as described in [[~~Reference13r3~~:Concept Conference Meeting Invitations\| this wiki article]]		* Meeting scheduling as described in [[{{NAMESPACE}}:Concept Conference Meeting Invitations\| this wiki article]]

	== Codec-Filtering ==		== Codec-Filtering ==
Line 53:		Line 53:
	The apps show all participants of the conference room. Participants can be muted or thrown out. The room PIN can be changed.		The apps show all participants of the conference room. Participants can be muted or thrown out. The room PIN can be changed.

	The web access of the room can be configured, this link shown or mailed, as described in [[~~Reference13r3~~:Concept Conference Web Access\| this wiki article]].		The web access of the room can be configured, this link shown or mailed, as described in [[{{NAMESPACE}}:Concept Conference Web Access\| this wiki article]].
	In addition, meeting links can be created, as described in [[~~Reference13r3~~:Concept Conference Meeting Invitations\| this wiki article]].		In addition, meeting links can be created, as described in [[{{NAMESPACE}}:Concept Conference Meeting Invitations\| this wiki article]].

	== Conference App (innovaphone-pbx-conferencing-access) ==		== Conference App (innovaphone-pbx-conferencing-access) ==

Howto15r1:Firmware Upgrade V14r2 V15r1

Elievens — Fri, 10 Apr 2026 12:30:02 GMT

Connect

← Older revision		Revision as of 14:30, 10 April 2026
Line 66:		Line 66:

	* You need to enable "impersonation" at all Connect app objects in order to make chat work correctly. Otherwise, chat messages will not be received from the target user.		* You need to enable "impersonation" at all Connect app objects in order to make chat work correctly. Otherwise, chat messages will not be received from the target user.
	* A new mode "admin-service" needs to be ~~add~~ in order to allow other apps (like Projects) to create posts in connect.		* A new mode "admin-service" needs to be added in order to allow other apps (like Projects) to create posts in connect.

	== New Apps ==		== New Apps ==

Howto16r1:Firmware Upgrade V15r1 V16r1

Slu — Fri, 10 Apr 2026 11:01:06 GMT

AP Upgrade to Image 140029 or newer

← Older revision		Revision as of 13:01, 10 April 2026
(One intermediate revision by the same user not shown)
Line 11:		Line 11:
	== Migration Policy ==		== Migration Policy ==
	<span style="color:red; font-weight: bold">Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location</span>		<span style="color:red; font-weight: bold">Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location</span>

			=== AP Upgrade to Image 140029 or newer ===
			* First, upgrade your application platform to at least image version 140029. After that you can go ahead.

	=== Upgrade Sequence ===		=== Upgrade Sequence ===

Reference16r1:Concept LDAP Replication

Slu — Fri, 10 Apr 2026 10:04:13 GMT

Glossary

← Older revision		Revision as of 12:04, 10 April 2026
Line 6:		Line 6:
	;Flashdir, Flashman: Flash Directory, Flash Manager with Flashdir sitting on-top of Flashman. The Flashdir exchanges API messages with the Flashman to persistently add, replace, and delete LDAP objects.		;Flashdir, Flashman: Flash Directory, Flash Manager with Flashdir sitting on-top of Flashman. The Flashdir exchanges API messages with the Flashman to persistently add, replace, and delete LDAP objects.
	;Full Replication: Every object is going to be queried by replication partners.		;Full Replication: Every object is going to be queried by replication partners.
	;~~GUID~~: A unique 16-byte value. Every object contains an attribute ''GUID''.		;guid: A unique 16-byte value. Every object contains an attribute ''GUID''.
	;Incremental Replication: Only objects written since a last-known point in time will be queried.		;Incremental Replication: Only objects written since a last-known point in time will be queried.
	;Master: The replication partner acting as an LDAP server.		;Master: The replication partner acting as an LDAP server.
Line 16:		Line 16:
	;Slave: The replication partner acting as an LDAP client.		;Slave: The replication partner acting as an LDAP client.
	;Tombstones, isDeleted: Deleted objects aren't deleted immediately from storage. Instead, such objects are marked with an attribute ''isDeleted''.		;Tombstones, isDeleted: Deleted objects aren't deleted immediately from storage. Instead, such objects are marked with an attribute ''isDeleted''.
	;~~USN~~ (Update sequence number)		;usn (Update sequence number)
	: Unique value incremented by 1 on every write. It is unique within every local LDAP DB.		: Unique value incremented by 1 on every write. It is unique within every local LDAP-DB.
	;~~RUSN~~ (Remote update sequence number)		;rusn (Remote update sequence number)
	: Unique value over the whole system over all LDAP DBs.		: Unique value over the whole system over all LDAP-DBs.
	; ~~RWR~~ (Replication Write)		; rwr (Replication Write)
	: Optional attribute on an object that is incremented by 1 on every update on a slave locally. Indicator that these changes have to be committed to the upper ~~ldap master~~.		: Optional attribute on an object that is incremented by 1 on every update on a slave locally. Indicator that these changes have to be committed to the upper LDAP-Master.

	= Technical concept of replication as client =		= Technical concept of replication as client =
Line 77:		Line 77:
	**Variable: '''LDAPI/epoc-r/cn=PBX0'''		**Variable: '''LDAPI/epoc-r/cn=PBX0'''

	==~~USN Processing~~==		==usn processing==
	Every object features the attribute '''~~USN~~'''. A slave keeps track of the highest USN seen within all objects rx'ed from a master.		Every object features the attribute '''usn'''. A slave keeps track of the highest USN seen within all objects rx'ed from a master.
	*Slave checks USN for objects rx'ed from master		*Slave checks USN for objects rx'ed from master
	**No local record of a highest ~~USN~~		**No local record of a highest usn
	***=> Store current ~~USN~~ as highest ~~USN~~		***=> Store current usn as highest usn
	**Local copy of highest ~~USN~~ existing		**Local copy of highest usn existing
	***RX'ed USN greater than local ~~USN~~ copy		***RX'ed USN greater than local usn copy
	****=> Store current USN as highest ~~USN~~		****=> Store current USN as highest usn
	***RX'ed USN less or equal than local ~~USN~~ copy		***RX'ed USN less or equal than local usn copy
	****=> NOP, nothing to be done		****=> NOP, nothing to be done

	*Slave, persistent ~~USN~~ storage		*Slave, persistent usn storage
	**Replication completed - at the end of a full or incremental replication. Also, when rx'ing notify search results from a master.		**Replication completed - at the end of a full or incremental replication. Also, when rx'ing notify search results from a master.
	***=> Persistently storing the volatile memorized highest ~~USN~~		***=> Persistently storing the volatile memorized highest usn
	**Variable: '''LDAPI/r-usn/cn=PBX0'''		**Variable: '''LDAPI/r-usn/cn=PBX0'''

	==Paging==		==Paging==
	Incremental paging requires an additional filter term ~~spedifying~~ a ~~USN~~ value.		Incremental paging requires an additional filter term specifying a usn value.
	*1st Search		*1st Search
	**Slave		**Slave
	**Filter (&(objectclass=)'''(usn>=103)''') The ~~USN~~-Term contains the highest ~~USN~~ rx'ed during last replication run, plus 1.		**Filter (&(objectclass=)'''(usn>=103)''') The usn-Term contains the highest usn rx'ed during last replication run, plus 1.
	***Cookie <empty>		***Cookie <empty>
	**Server		**Server
Line 103:		Line 103:
	***Replies with entries and non-empty(more) or empty(final) cookie		***Replies with entries and non-empty(more) or empty(final) cookie

	*2nd Search~~,..~~		*2nd Search
	**Slave		**Slave
	**Filter (objectclass=)		**Filter (objectclass=)
Line 123:		Line 123:
	==VARs==		==VARs==
	Noteable variables for persistent storage of some replication control data within a slave's VARs section.		Noteable variables for persistent storage of some replication control data within a slave's VARs section.
	;Remote highest rusn:		;Remote highest rusn
	vars create LDAPI/r-rusn/cn=PBX0 p 102		vars create LDAPI/r-rusn/cn=PBX0 p 102

	;Remote highest usn:		;Remote highest usn
	vars create LDAPI/r-usn/cn=PBX0 p 548		vars create LDAPI/r-usn/cn=PBX0 p 548

	;Remote last seen epoch, saved per view:		;Remote last seen epoch, saved per view
	vars create LDAPI/epoc-r/cn=KPBX0 pb 5238705224c067016fd10090334117be		vars create LDAPI/epoc-r/cn=KPBX0 pb 5238705224c067016fd10090334117be
	vars create LDAPI/epoc-r/cn=PBX0 pb 5238705224c067016fd10090334117be		vars create LDAPI/epoc-r/cn=PBX0 pb 5238705224c067016fd10090334117be
Line 143:		Line 143:

	==Detecting Obsolete Objects==		==Detecting Obsolete Objects==
	Objects with the isDeleted attribute, a.k.a. tombstones, shall persist ~~ideally~~ forever. In practice tombstones get erased after a timeout. Only the most recent tombstone (tombstone with highest ~~USN~~) remains.		Objects with the isDeleted attribute, a.k.a. tombstones, shall ideally persist forever. In practice, tombstones get erased after a timeout. Only the most recent tombstone (tombstone with the highest usn) remains.
	;Current tombstone timeout: 48 hours		;Current tombstone timeout: 48 hours
	===Behaviour during Full Replication===		===Behaviour during Full Replication===
	The local phase takes place in full. The replicator pages over all local objects and compares them with the master to see if they are still present.		The local phase takes place in full. The replicator pages over all local objects and compares them with the master to see if they are still present.
	===Behaviour during Incremental Replication===		===Behaviour during Incremental Replication===
	The local phase is completely eliminated, respectively ~~skipped~~.		The local phase is completely eliminated or skipped, respectively.

Howto16r1:Firmware Upgrade V15r1 V16r1

Slu — Fri, 10 Apr 2026 09:59:25 GMT

Migration Policy

← Older revision		Revision as of 11:59, 10 April 2026
Line 10:		Line 10:

	== Migration Policy ==		== Migration Policy ==
	<span style="color:red; font-weight: bold">Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location</span>~~<br>~~		<span style="color:red; font-weight: bold">Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location</span>

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

	=== TechAssist Upgrade Helper ===		=== TechAssist Upgrade Helper ===

Howto15r1:Firmware Upgrade V14r2 V15r1

Slu — Fri, 10 Apr 2026 09:59:02 GMT

Migration Policy

Howto14r2:Firmware Upgrade V14r1 V14r2

Slu — Fri, 10 Apr 2026 09:59:01 GMT

Migration Policy

← Older revision		Revision as of 11:59, 10 April 2026
Line 12:		Line 12:
	Here is how you upgrade a system from 14r1 to 14r2.		Here is how you upgrade a system from 14r1 to 14r2.

	<span style="color:red; font-weight: bold">Before you begin, be sure that your whole installation is running the latest 14r1 service release. If you are still running 13r3 or earlier, be sure to update to [[Howto14r1:Firmware Upgrade V13r3 V14r1\|14r1 latest service release]] before.</span><br>		<span style="color:red; font-weight: bold">Before you begin, be sure that your whole installation is running the latest 14r1 service release. Create backups before you start and store them on an external location. If you are still running 13r3 or earlier, be sure to update to [[Howto14r1:Firmware Upgrade V13r3 V14r1\|14r1 latest service release]] before.</span><br>

	=== IPVA - Flash preparations ===		=== IPVA - Flash preparations ===
Line 58:		Line 58:

	Alternatively you can install the standbys from scratch.		Alternatively you can install the standbys from scratch.

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

	== Changes visible to the end customers ==		== Changes visible to the end customers ==

Howto:Firmware Upgrade

Slu — Fri, 10 Apr 2026 09:52:19 GMT

Firmware upgrade policy

← Older revision		Revision as of 11:52, 10 April 2026
(2 intermediate revisions by the same user not shown)
Line 3:		Line 3:
	* All innovaphone devices and software		* All innovaphone devices and software

	== ~~Firmware support policy~~ ==		== General policies for firmware updates ==

			=== Firmware support policy ===
	For currently supported firmware versions, please [[Support:Supported innovaphone versions\|refer to this overview]].		For currently supported firmware versions, please [[Support:Supported innovaphone versions\|refer to this overview]].

	== Firmware upgrade policy ==		=== Firmware upgrade policy ===
			The upgrade policies may vary for each major upgrade. Therefore, please refer to the "Migration Policy" in the relevant upgrade article.
	~~When upgrading from a previous major version to a service release within a higher major version, it is '''mandatory to upgrade in stages'''.~~

	~~For example, if you want to do an~~ upgrade ~~from '''13r3''' to 16r1, you must first upgrade from 13r3 to 14r1, then from 14r1 to 14r2, then from 14r2 to 15r1, and the from 15r1 to 16r1 following the instructions listed~~ for each major ~~upgrade wiki article.~~

	~~You will find a separate wiki article for each major step, which describes all the necessary adjustments required for the~~ upgrade.

	~~When coming from V12r2 or a V13r1 and up installation without any myApps App platform and no Apps installed~~, ~~(no Install procedure has been performed previously) you only need~~ to ~~perform the firmware upgrade of~~ the ~~hardware or virtual machine~~ in ~~use.~~
	~~Once you are at~~ the ~~level of the desired firmware version, you can perform the Install.~~
	~~Doing the install in the latest firmware, will assure an install including all new Apps from this Version~~.

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

	== Version 16r1 ==		== Version 16r1 ==

Howto16r1:Firmware Upgrade V15r1 V16r1

Dde — Fri, 10 Apr 2026 09:11:34 GMT

Projects

← Older revision		Revision as of 11:11, 10 April 2026
Line 45:		Line 45:

	=== Projects ===		=== Projects ===
	* Projects requires '''App platform version ~~140003~~''' or higher, so updating the App Platform before Projects is recommended. <br />The Store will prohibit the update if the App Plattform does not have the minimum required version.		* Projects requires '''App platform version 140029''' or higher, so updating the App Platform before Projects is recommended. <br />The Store will prohibit the update if the App Plattform does not have the minimum required version.
	* For some extra admin-functionalities the '''Projects App Object needs to have an admin mode''' (App-tab). <br />Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.		* For some extra admin-functionalities the '''Projects App Object needs to have an admin mode''' (App-tab). <br />Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.
	* The '''App Platform requires the correct Time and a Timezone''' set under AP Manager/Settings/General. <br />This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).		* The '''App Platform requires the correct Time and a Timezone''' set under AP Manager/Settings/General. <br />This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).