innovaphone wiki - User contributions [en]

Reference16r1:Apps/PbxManager/App Projects

2026-04-21T08:57:06Z

Elievens: Created page with "= Add an app= ;Name :The ''name'' displayed for the App Object, which must be unique. ;SIP :The ''sip'' for the app object, which must be unique. ;Connect App :Select the ''Connect''-App (all available Connect-Apps will be listed). <ref>When selecting/changing the ''Connect App'', the ''Connect Admin Service'' will change accordingly.</ref> ;Connect Admin Service :Select the '''mandatory''' ''Connect Admin Service'' (all available Connect-Apps will be listed which..."

= Add an app=

;Name
:The ''name'' displayed for the App Object, which must be unique.

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

;Connect App
:Select the ''Connect''-App (all available Connect-Apps will be listed). <ref>When selecting/changing the ''Connect App'', the ''Connect Admin Service'' will change accordingly.</ref>

;Connect Admin Service
:Select the '''mandatory''' ''Connect Admin Service'' (all available Connect-Apps will be listed which have the 'admin-service'-mode) <ref>When selecting/changing the ''Connect Admin Service'', the ''Connect App'' will change accordingly (if empty: please add the ''admin-service''-mode to the selected Connect-App). </ref> This field may not be empty (if so: check/correct the modes of the 'Connect'-app).

;Config Templates
If Config Templates exist: these will be listed with a checkbox. The App Object will be assigned to the checked config templates.

;Administrators
If Config Templates exist: these will be listed with a checkbox. The App Object with ''''admin'-mode''' will be assigned to the checked config templates.

Reference16r1:Concept App Service Projects

2026-04-14T13:21:48Z

Elievens: /* Upgrade */

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


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

= 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 V16r1 features ==

= 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 140029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= 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 =
== 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T13:20:59Z

Elievens: /* Upgrade */

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


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

= 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 V16r1 features ==

= 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 140029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= 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 =
== 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T13:20:10Z

Elievens: /* Upgrade */

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


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

= 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 V16r1 features ==

= 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 140029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= 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 =
== 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T13:19:53Z

Elievens: /* Upgrade */

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


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

= 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 V16r1 features ==

= 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 140029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= 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 ==
=== 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).

== 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 =
== 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T13:19:24Z

Elievens: /* Upgrade */

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


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

= 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 V16r1 features ==

= 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 140029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= 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 =
== 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T13:06:57Z

Elievens: /* Requirements */

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


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

= 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 V16r1 features ==

= 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 140029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T12:54:58Z

Elievens: /* Requirements */

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


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

= 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 V16r1 features ==

= 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 120029''' '''[new in V16r1]'''
* The Application Platform must have the '''correct time''' and a '''Timezone''' set '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T12:53:37Z

Elievens: /* Auto Cleanup or automatic Task Status Updates do not work */

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


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

= 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 V16r1 features ==

= 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 120029 '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 =
* [[Reference15r1:Apps/PbxManager/App Projects]]
* [[Reference15r1:Concept App Connect]]

Reference16r1:Concept App Service Projects

2026-04-14T12:52:34Z

Elievens: /* Troubleshooting */

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


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

= 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 V16r1 features ==

= 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 120029 '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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 Setting of the '''App Platform''' (AP Manager/Settings/General) if the AP '''has the correct time and has a Timezone''' configured.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:49:44Z

Elievens: /* Troubleshooting */

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


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

= 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 V16r1 features ==

= 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 120029 '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:47:25Z

Elievens: /* Projects cannot be upgraded */

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


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

= 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 V16r1 features ==

= 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 120029 '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an '''App Platform of at least version 140029'''. 
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']].

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

Reference16r1:Concept App Service Projects

2026-04-14T12:39:02Z

Elievens: /* "App"-tab */

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


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

= 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 V16r1 features ==

= 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 120029 '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:38:51Z

Elievens: /* Requirements */

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


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

= 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 V16r1 features ==

= 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 120029 '''[new in V16r1]'''
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:37:24Z

Elievens: /* "App"-tab */

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


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

= 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 V16r1 features ==

= 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 120029
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[new in V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:36:14Z

Elievens: /* Configuration */

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


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

= 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 V16r1 features ==

= 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 120029
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= Upgrade =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:35:27Z

Elievens: /* Apps */

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


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

= 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 V16r1 features ==

= 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 120029
* 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 well-configured PBX App Object needed is needed for the Projects-App. 
This App Object is best created/adjusted via that projects-plugin of the Settings App.

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

=== "App"-tab ===
;Modes: admin ''(to allow an extra Admin-mode)'' '''[V16r1]'''
;WebSocket: needed ''(to allow Connect-postings)''
;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)''

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:26:58Z

Elievens: /* Requirements */

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


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

= 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 V16r1 features ==

= 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 120029
* 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:26:12Z

Elievens: /* New V16r1 features */

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


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

= 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 V16r1 features ==

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:25:54Z

Elievens: /* Overview */

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


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

= 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 V16r1 features =

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:25:22Z

Elievens: /* Troubleshooting */

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


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

= 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.

== Projects cannot be upgraded ==
The V16r1-version of Projects requires an App Platform of at least version 140029.

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

Reference16r1:Concept App Service Projects

2026-04-14T12:22:43Z

Elievens:

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


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

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

Reference16r1:Concept App Service Projects

2026-04-14T12:22:33Z

Elievens:

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


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

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

Reference16r1:Concept App Service Projects

2026-04-14T12:21:48Z

Elievens: 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...."

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

Howto15r1:Firmware Upgrade V14r2 V15r1

2026-04-10T12:30:02Z

Elievens: /* Connect */

== Applies To ==
This information applies to:

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

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

== Migration Policy ==
Here is how you upgrade a system from 14r2 to 15r1.

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

=== AP Upgrade to Image 130006+ ===
* Please Upgrade as first your Application Platform to at least Image Version 130006. After that you can go ahead.
* Before you begin, be sure that your Upgrade as first your Application Platform to Image Version 130006. After that you can go ahead.. 

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

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

=== App Platform on CF card (IPxx10) ===
Make sure that no App Platform is installed on a CF card, as this function is removed with the update.
Migrate the App Platform to a gateway with SSD or as a virtual machine before the update.

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

* '''myApps''': New UI design. In new installations users will see an intro video when logging in the first time.
* '''myApps iOS/Android''': You will find a new Version without the Major Version in the icon. Starting with V15, the client no longer needs to be replaced in the future.
* '''Phone App and Softphone App''': [[ReleaseNotes15r1:Firmware#192745 - Phone App and Softphone App: New UI design|New UI design]]
* '''Switchboard App''': See list of improvements in the [[Reference15r1:Concept App Service Queues#V15 Improvements|Concept App Service Queues Article]]
* '''Connect App''': New version with many new features. See list of improvements in the [[Reference15r1:Concept App Connect|connect article]].
* '''Chat App''': The chat app for persistent chat is now integrated in the connect app. More information in the [[Reference15r1:Concept App Connect#Chat|connect article]].
* '''Fax App settings plugin''': The admin can now set [[Reference15r1:Apps/PbxManager/App Fax#Default settings for mail notifications|default settings for mail notifications]] for the user specific/group fax app.
* '''Contacts App''': Contacts now has a new start screen, vCard Files can now be imported and exported, as well as there were made some User-Interface improvements. For more information, see [[Reference15r1:Concept App Service Contacts#15r1 Features|here]].
* '''Devices App''':OTA (Over the Air) Features for dect systems can now be [[Reference15r1:IP1202/IP1203 DECT System#OTA (Over the Air) Features|configured]].

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== myApps ===
* To configure an optional intro that is shown when user login the first time, see: [[Reference15r1:Concept_myApps#Onboarding]]

=== Techassist App ===
* You have to enable the API "PbxSignal" in the APP Objects "App" Tab

=== myApps iOS/Android ===
* You must install the new app without the major version in the icon. (Starting with V15, the client no longer needs to be replaced in future).
** iOS: https://apps.apple.com/us/app/innovaphone-myapps/id6739562892
** Android: https://play.google.com/store/apps/details?id=com.innovaphone.myapps

=== IPVA VMWare Fault Tolerance ===
* With 15r1 you can use again the VMWare Fault Tolerance Feature. If you want to re-enable this feature you have to [[Howto15r1:Implement PBX with zero downtime using IPVA and VMWare Fault Tolerance|setup a new IPVA-SCSI]] and export/import your configuration to the new machine.

=== Working App ===

* With 15r1, it is necessary to specify the master PBX in the Settings plugin under "Configuration"

=== Connect ===

* 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 added in order to allow other apps (like Projects) to create posts in connect.

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

=== Projects App ===
* Concept Article: [[Reference15r1:Concept App Service Projects|Concept App Service Projects]]

=== Virtual Background App ===
* Concept Article: [[Reference15r1:Concept Virtual Background App|Concept Virtual Background App]]

=== Remote Control Client msi application for external participants ===
* Concept Article [[Reference15r1:Concept App Remote Control|Concept App Remote Control]]

=== Assistant App ===
* Concept Article [[Reference15r1:Concept App Service myApps Assistant#Assistant App|Concept Assistant App]]

‎<onlyinclude>

== Good2Know ==

=== PBXManager ===
“PBX Manager” is now called “Settings”

=== Exchange Online calendar integration — Calendar App / Connector for Microsoft 365 ===
In the past, Microsoft has announced the end of support for Exchange Online EWS support in 2026:

https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440

Since the Calendar App uses EWS to synchronize calendar events from Exchange Online to the PBX, this feature will stop working from then on.

Microsoft suggests switching to the Graph API for this functionality and since we already have an app that works with the Graph API, we have extended the feature set of the Connector for Microsoft 365.

In addition to the initial functionality of synchronizing line states and presences bi-directionally between the Azure Portal (Teams) and the PBX, the Connector for Microsoft 365 can now also retrieve calendar events and integrate them into the PBX.

The Connector for Microsoft 365 requires a valid licence for each user.

The Exchange Online functionality of the Calendar App will no longer be enhanced or improved, but the current functionality will be included for as long as Microsoft continues to support EWS for Exchange Online.

The on-premise functionality is not affected by this and will remain in the Calendar App.

''As both apps integrate Exchange Online calendar events in the same way, it is not recommended or supported to use both calendar integrations at the same time.''

''However, you can use the Connector for Microsoft 365 for presence and line state synchronization and the Calendar App for calendar event integration.''

=== Federation ===
Beginning with 15r1 the certificate or CA of the certificate of the client device '''must''' be in the trust list of the RP/gateway or else, federation doesn't work anymore.

=== Devices App: Evaluation of PBX User Rights ===
When a PBX user with [[Reference9:PBX/Objects/Edit Rights|administrative rights]] accesses the Devices App, their PBX rights are enforced. As a result, only the PBX-related pages permitted by the user's rights can be modified.
However, PBX rights do not apply to other modules (e.g. IP configuration). This means that users retain full administrative access to non-PBX-related functions within the Devices App, regardless of their PBX rights.
Additionally, in the syslog the administrative changes now also contain a user ID and the remote IP address if the Devices App is used.
‎</onlyinclude>

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

* running an App Platform on the CF card of an IPxx10 gateway (Removed, migrate to a gateway with an SSD or a Virtual Machine to run the App Platform)
* Audio codec software transcoding to G.729 removed on: IP11x, IP10x, myApps, DECT-Radios. Only the conversion to G.729 has been removed, not the playback of already converted g.729 audio files such as an MOH or voicemail announcements. These can still be played.

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

* ''Nothing''

== Previously deprecated and now no longer supported ==
The following software is based on legacy technology, with no further development and no more maintenance and support. 
See: [[Howto14r2:Firmware_Upgrade_V14r1_V14r2#Deprecated]] 
We strongly recommend migrating to our successor products.

* iQM (innovaphone Queue Monitor) - Migrate to the [[Howto:Queueboard - MediaRunway - Partner App|Queueboard App]]. For existing innovaphone QueueMonitor licences, the corresponding MediaRunway Queueboard licences can be downloaded via portal.innovaphone.

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

===App Platform doesn't boot after Upgrade===
If you didn't upgrade the AP Image before upgrading the apps like describe [[#AP Upgrade to Image 130006|here]] and the AP isn't reachable via http(s), but still via ssh, please follow these [[Reference14r2:Concept App Platform#It still doesn't start|instructions]] to get the AP work correct again.

===Downgrade of Devices App from 15r1 to 14r2===
The database schema for update jobs in the Devices App has changed between versions 14r2 and 15r1. If you need to downgrade from 15r1 back to 14r2, you must delete all 15r1 update jobs before.

Failing to do so will cause the 14r2 Devices App to crash on startup. In that case, you will need to restore a 14r2 backup of the Devices App.

===After update endpoint no longer registers to the PBX ===
An incoming registration to a PBX is incorrectly identified as coming from/over the reverse proxy when the certificate sent by the registering endpoint matches a certificate mentioned in the reverse proxy addresses of the PBX, regardless of the IP address associated with this certificate in the 'PBX/Config/General/Reverse Proxy Addresses' list. The registration then is rejected, if the device at the PBX-object has no ''Reverse Proxy'' Flag.

For example, this often occurs with slave/standby PBXs if a wildcard certificate is used for registration and this wildcard certificate is also mentioned in the 'PBX/Config/General/Reverse Proxy Addresses' list. 

'''Solution 1''': Remove the wildcard-certificate from the Reverse Proxy-list '''or''' 
'''Solution 2''': Configure a strong password on the PBX-object and change the endpoint registration from 'H323/TLS' to 'H323/TCP' (and so with password)
'''or''' 
'''Solution 3''': Activate the ''Reverse Proxy'' Flag at the PBX-object

== Resources Considerations ==
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.

Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.

=== RAM ===
As a rough rule of thumb, a 15r1 release will consume the same amount of RAM compared to a v14r2 firmware.

=== Flash Memory ===
As a rough rule of thumb, a v15r1 release will consume ~ 64KB flash memory compared to a v14r2 firmware.
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v15r1. Here is the recommended procedure for upgrade on such devices:

* save entire configuration
* reset to factory defaults
* load saved configuration (this will reorganize the flash memory usage)
* upgrade to new firmware

When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a ''Firmwareupdate failed:no space'' / Update client end in a ''Error 0x00130001 Major FLASHMAN0 no space'' event) please open a support case with your current configuration file.

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

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-10T08:49:56Z

Elievens: /* Project */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

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

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-10T08:47:36Z

Elievens: /* Manual steps needed after upgrade */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

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

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-09T15:53:44Z

Elievens: /* Project */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Project ===
* For some extra admin-functionalities, the Project App must have the '''admin''' mode configured (App-tab). Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.
* The '''App Platform''' must have the '''correct time''' and a '''Timezone''' set under AP Manager/Settings/General. This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-09T15:52:47Z

Elievens: /* Manual steps needed after upgrade */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Project ===
* For some extra admin-functionalities, the Project App must have the '''admin''' mode configured (App-tab). Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.
* The App Platform must have the '''correct time''' and a '''Timezone''' set under AP Manager/Settings/General.
This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-09T15:44:41Z

Elievens: /* Project */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Project ===
* For some extra admin-functionalities, the Project App must have the '''admin''' mode configured (App-tab). Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-09T15:40:30Z

Elievens: /* Manual steps needed after upgrade */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Project ===
* For some extra admin-functionalities, teh Project App must have the '''admin''' mode configured (App-tab). This can set via the Advanced UI of the PBX; an easier way is to open the Projects App Object in the Projects-plugin and to re-apply it by clicking the OK-button. This mode can be distrubuted also via the same Plugin.

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Reference15r1:Concept App Service Projects

2026-04-09T12:45:44Z

Elievens: /* Settings App/App Installer */

Reference15r1:Concept App Service Projects

2026-04-09T12:36:14Z

Elievens: /* Projects-plugin cannot see the Connect Admin Service */

[[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'')
#** (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]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-09T08:43:11Z

Elievens: /* Working */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-09T08:42:54Z

Elievens: /* Switchboard */

== Applies To ==
This information applies to:

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

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

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

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''Connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Reference16r1:Concept App Service Queues

2026-04-09T08:41:36Z

Elievens: /* Switchboard App (innovaphone-switchboard) */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 16r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V16r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V16 Improvements==
'''Show call diversions for the favorites section in the BLF.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Breakthrough of call diversions from BLF in favorites section.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Edit mobility destination for users.''' 
An improvement for changing the mobility destination of the users.

'''Enable numeric + key as shortcut for transfer option.''' 
The Switchboard App now supports the shortkey + as shortkey for the transfer functionality.

'''Focus on second call for easier transfer ''' 
When starting a second call in the Switchboard App, the focus will be in the call section on this second call, so that a transfer can be initiated immediately by pressing the configured short-cut, for example the numeric + key. In case the focus is in the search field, press the TAB key first.

'''Call state in outgoing call section.''' 
When having an outgoing call, the status of this call (ringing or connected) will be shown in this outgoing call for a more user-friendly and intuitive feedback.

'''Notes for in- and outgoing calls in connect.''' 
When having an in- or outgoing call, you can add a note for this call in the Connect App. When a new call arrives, the Note can be consulted as additional information about this caller or called number.

'''Callback request email during a call.''' 
When having a call, a callback request per email can be generated. The email will have available callinformation already preloaded, like name, number and email-address of the caller if available.

'''Show Notes button in the Call History.''' 
Action key in the call history items to jump to the corresponding Notes in the Connect App.

'''Show fold/ unfold view for adjusting WQ height in Config''' 
changed design for configuring the showed Waiting Queue call section height.

'''Show Blf slider in Icons only view''' 
when selected the Icons only view of the BLF a slider will be shown.

'''Improved search funcionality.''' 
The improved search functionality is in line with the (Soft)Phone App search showing the source of the search result.

'''Improved search details.''' 
Improved the shown details from a search result and showing more info in the BLF entry details.

'''Create a popup box for already existing shortcuts.''' 
In case you enter a short cut that already excist, it will give you a warning that this shortcut is already created.

'''Fixed breakthrough option/button was not updated.''' 
Fixed breakthrough option/button was not updated (added/removed) when eg a CFu is set/removed.

'''Fix: Issue added users not visible immediately in BLF.''' 
Show users immediately in the BLF after adding them to a group.

'''Fix: Issue missing call-leg2 Info.''' 
Missing Call-leg2 Info now showed after connecting a Call.

'''Fix: Issue to many calls when starting call forward breakthrough.''' 
Fixed call forward breakthrough that leaded to many calls.

'''Fix: Issue to less space between buttons in BLF Details.''' 
Fixed the space between buttons in BLF user details.

'''Fix: Issue with Queues-plugin Group Configuration.''' 
The Display Name was wrongly used as User Identifier/Common Name to assign the 'queue'-group.

'''Fix: Issue Display of mismatched number with name in outgoing calls.''' 
Fixed the display of mismatched number with name in outgoing calls section on pickup.

'''Fix: Issue with missing CFx on a user after a change by the Switchboard App.''' 
Fixed the forwardings stored in PBX after a change by the Switchboard App.

'''Fix: Issue Users displayed multiple times when we click on BLF duplication button.''' 
Fixed the behavior when we click on BLF duplication button.

'''Fix: Issue when Transfer-button clicked twice.''' 
Fixed when transfer-button clicked twice, the transfer button was not removed on second call.

'''Fix: Issue Missing call after selecting IVR option.''' 
Fixed when selecting IVR option, show the waiting Queue again in the call panel section.

'''Fix: Issue transfer button shown on active calls.''' 
Fixed don't show the transfer button on active calls.

'''Fix: Show CFx Icon on toggling from large to small Icon view''' 
Fixed to show the Call Forward Icon in the small view of the Busy Lamp Field.

'''Fix: Favorites did have less actions than other contacts in the BLF''' 
Fixed to show all possibile actions on the BLF entries in the favorites section

'''Fix Add option to fix WQ height in config''' 
Fixed added option to waiting queues height configuration

'''For further fixes to come with future service releases, please consult our release notes accordingly.''' 

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;Services: to be able to connect to extra apis (eg messages or connect (*))
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

;Apps->connect (or Apps->messages): to be able to see/post call notes (*)

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

'''Note''': Make sure to close the Switchboard App of the user when adjusting the config this user via the Switchboard Admin App. This ensure that changes are not overwritten again with the old values.

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

Before doing any changes for any switchboard user, make sure that this user has closed the Switchboard App. Perform the changes, and afterward the Switchboard App user can reopen the Switchboard App and the changes will be applied.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed. The Notes Field when beeing used, will be on top off the Waiting Queues and Calls History section.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

==== Notes Field ====
During an active call you have the option to add a Note for this call and caller-id. The first notes information like name and/or number is added by the App service. You can add a personal note as additional information related to the call or caller-id.

The notes are stored in the Connect App in the zone Switchboard. To be able to see the Switchboard Notes from the service and other Switchboard operators, the Switchboard user should have read access to the zone Switchboard. To add personal notes to the discussion, the Switchboard User should also have the Connect App license (included in the UCC license)

In the call history you are also able to create, read and add notes.

With a new incoming call and there is already a note available for this caller-id, the note will be shown immediately in the right section of the screen.

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If disabled: a long list of incoming calls will be shown.
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
** Fix WQ height optional with height setting between 0 and 50
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-08T13:14:23Z

Elievens: /* Switchboard */

== Applies To ==
This information applies to:

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

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

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. 

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''Connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' and '''messages-api''' (Apps-tab) enabled.

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-08T13:14:01Z

Elievens: /* Switchboard */

== Applies To ==
This information applies to:

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

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

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. 

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''Connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' and '''messages-api''' (Apps-tab).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-08T13:11:03Z

Elievens: /* Switchboard */

== Applies To ==
This information applies to:

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

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

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. 

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''Connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (the Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' and '''messages-api''' (Apps-tab).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-08T13:08:52Z

Elievens: /* Switchboard */

== Applies To ==
This information applies to:

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

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

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. 

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''Connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect integration (the Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' and '''messages-api''' (Apps-tab).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-04-08T13:08:16Z

Elievens: /* Manual steps needed after upgrade */

== Applies To ==
This information applies to:

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

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

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. 

=== 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

=== New TLS Profile ===
Please note that we have changed our TLS profiles ([[Reference16r1:IP4/General/TLS]]). The new ''Normal'' setting, which is the default value, now only allows TLS 1.3 and TLS 1.2.

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

* ''Nothing''

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''Connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect integration (the Call Notes) to work, the Switchboard App must have the '''Services''' and '''connect''' and '''messages-api''' (in the Apps tab).

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

* App Polls: [[Reference16r1:Concept App Polls]]
* App Service Conference Transcriptions [[Reference16r1:Concept_App_Service_myApps_Assistant]]
* App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
* App Conference Scaler: [[Reference16r1:Concept_Conference_Scaler_App]]
* App Service IP: [[Reference16r1:Concept App Service IP]]

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

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

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

* ''Nothing''

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

* ''Nothing''

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

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Reference16r1:Concept App Service Queues

2026-04-08T13:03:00Z

Elievens: /* Apps */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 16r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V16r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V16 Improvements==
'''Show call diversions for the favorites section in the BLF.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Breakthrough of call diversions from BLF in favorites section.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Edit mobility destination for users.''' 
An improvement for changing the mobility destination of the users.

'''Enable numeric + key as shortcut for transfer option.''' 
The Switchboard App now supports the shortkey + as shortkey for the transfer functionality.

'''Focus on second call for easier transfer ''' 
When starting a second call in the Switchboard App, the focus will be in the call section on this second call, so that a transfer can be initiated immediately by pressing the configured short-cut, for example the numeric + key. In case the focus is in the search field, press the TAB key first.

'''Call state in outgoing call section.''' 
When having an outgoing call, the status of this call (ringing or connected) will be shown in this outgoing call for a more user-friendly and intuitive feedback.

'''Notes for in- and outgoing calls in connect.''' 
When having an in- or outgoing call, you can add a note for this call in the Connect App. When a new call arrives, the Note can be consulted as additional information about this caller or called number.

'''Callback request email during a call.''' 
When having a call, a callback request per email can be generated. The email will have available callinformation already preloaded, like name, number and email-address of the caller if available.

'''Show Notes button in the Call History.''' 
Action key in the call history items to jump to the corresponding Notes in the Connect App.

'''Show fold/ unfold view for adjusting WQ height in Config''' 
changed design for configuring the showed Waiting Queue call section height.

'''Show Blf slider in Icons only view''' 
when selected the Icons only view of the BLF a slider will be shown.

'''Improved search funcionality.''' 
The improved search functionality is in line with the (Soft)Phone App search showing the source of the search result.

'''Improved search details.''' 
Improved the shown details from a search result and showing more info in the BLF entry details.

'''Create a popup box for already existing shortcuts.''' 
In case you enter a short cut that already excist, it will give you a warning that this shortcut is already created.

'''Fixed breakthrough option/button was not updated.''' 
Fixed breakthrough option/button was not updated (added/removed) when eg a CFu is set/removed.

'''Fix: Issue added users not visible immediately in BLF.''' 
Show users immediately in the BLF after adding them to a group.

'''Fix: Issue missing call-leg2 Info.''' 
Missing Call-leg2 Info now showed after connecting a Call.

'''Fix: Issue to many calls when starting call forward breakthrough.''' 
Fixed call forward breakthrough that leaded to many calls.

'''Fix: Issue to less space between buttons in BLF Details.''' 
Fixed the space between buttons in BLF user details.

'''Fix: Issue with Queues-plugin Group Configuration.''' 
The Display Name was wrongly used as User Identifier/Common Name to assign the 'queue'-group.

'''Fix: Issue Display of mismatched number with name in outgoing calls.''' 
Fixed the display of mismatched number with name in outgoing calls section on pickup.

'''Fix: Issue with missing CFx on a user after a change by the Switchboard App.''' 
Fixed the forwardings stored in PBX after a change by the Switchboard App.

'''Fix: Issue Users displayed multiple times when we click on BLF duplication button.''' 
Fixed the behavior when we click on BLF duplication button.

'''Fix: Issue when Transfer-button clicked twice.''' 
Fixed when transfer-button clicked twice, the transfer button was not removed on second call.

'''Fix: Issue Missing call after selecting IVR option.''' 
Fixed when selecting IVR option, show the waiting Queue again in the call panel section.

'''Fix: Issue transfer button shown on active calls.''' 
Fixed don't show the transfer button on active calls.

'''Fix: Show CFx Icon on toggling from large to small Icon view''' 
Fixed to show the Call Forward Icon in the small view of the Busy Lamp Field.

'''Fix: Favorites did have less actions than other contacts in the BLF''' 
Fixed to show all possibile actions on the BLF entries in the favorites section

'''Fix Add option to fix WQ height in config''' 
Fixed added option to waiting queues height configuration

'''For further fixes to come with future service releases, please consult our release notes accordingly.''' 

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;Services: to be able to connect to extra apis (eg connect/connect-api (*))
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

;Apps->messages-api: to be able to see/post call notes (*)

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

'''Note''': Make sure to close the Switchboard App of the user when adjusting the config this user via the Switchboard Admin App. This ensure that changes are not overwritten again with the old values.

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

Before doing any changes for any switchboard user, make sure that this user has closed the Switchboard App. Perform the changes, and afterward the Switchboard App user can reopen the Switchboard App and the changes will be applied.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If disabled: a long list of incoming calls will be shown.
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
** Fix WQ height optional with height setting between 0 and 50
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)

Reference13r2:Apps/PbxManager/FXS

2026-02-11T10:00:10Z

Elievens:

Selection of an fxs interface from an fxs gateway in the system.

Possibility to generate provisioning code for device registration.

For additional information refer to the [[Courseware:IT_Connect_-_04_Managing_Users#Initiated_by_the_User_-_FXS_Phone|training description]].

'''Note''': Older devices (IP22/IP24/IP28) are shown here, but the FXS-ports still need to be configured over the Advanced UI.

Reference13r2:Apps/PbxManager/FXS

2026-02-11T09:58:13Z

Elievens:

Reference15r1:PBX/Config/General

2026-01-22T14:54:33Z

Elievens: /* Configuration */

== Configuration ==

=== Common ===

;PBX Mode: The PBX operating mode
:* '''Off''' - The PBX is disabled. After enabling the PBX a browser refresh is needed to activate additional PBX webpages.
:* '''Master''' - The PBX on this device acts as Master. Within a multisite installation exactly one PBX must be configured as Master.
:* '''Slave''' - The PBX on this device acts as Slave. Within a multisite installation several PBXes can be configured as Slave.
:* '''Standby''' - The PBX on this device acts as Standby for the Master. As long as the master is available, this PBX is not active, but just monitors the Master. If the Master is not available this PBX is active.
:* '''Standby-Slave''' - The PBX on this device acts as Standby for a Slave. As long as the slave is available, this PBX is not active, but just monitors the slave. If the slave is not available this PBX is active.

;System Name: The system Name. On all PBX within a multisite installation the same System Name must be configured. For H.323 endpoints this name is the gatekeeper identifier, for SIP endpoints it is the server name.

;Use as Domain: Uses the ''System Name'' as domain name, together with the name field in the user object the PBX constructs the email address (used for sending emails out ox myPBX). This mechanism is also used for Federation, to federate with other domains.

;PBX Name: The name of the PBX on this device. With this name a PBX is associated to a node. The field 'Name' (not Long Name) of a PBX Node object relates to this name.

;DNS: DNS Name of the PBX. If configured this will be used for myPBX redirects if a client tries to register at a PBX on which the user is not configured.

;Unknown Registrations: If this checkmark is set, the PBX accepts 'unknown' registrations. This means registrations with no matching object configured. If from an endpoint registered in this way a number of an object is dialed, which has no registration active and no 'HW-ID' configured the name used for the registration is configured as 'HW-ID' of this object. This is an easy way to deploy large numbers of phones.

:'''With PBX Pwd only:''' If checked only registrations with a PBX authentication or a verified certificate in case of H.323/TLS are accepted. In this case either "PBX Pwd" or "TLS only" is set in a device generated.

;Reverse Proxy Addresses: Up to 8 IP-Addresses (Mixed IPv4 and IPv6 allowed, but no DNS names) can be entered in this field, separated by comma. Registrations from one of these addresses are assumed to be routed through a Reverse Proxy. To the address '/<certificate name>' can be added to also check the TLS certificate of the Reverse Proxy. If the reverse proxy certificate is to be verified, the certificate or the issuer of the reverse proxy certificate must be trusted in the PBX. (If you use a SAN certificate you have to enter the first SAN-Name)
:Checking only on the certificate is also possible, by omitting the IP-address, eg '/*.domain.de'. Registrations sent with this certificate are considered to be coming over the Reverse Proxy.
:If empty addresses are used, unauthenticated registrations from unknown or internal addresses are not allowed, but any registration must be authenticated, with a password or the certificate from the reverse proxy.
; Assume TLS: If the ''Assume TLS'' checkmark is set, it is assumed, that the reverse Proxy did a successful check of the TLS certificate against the registration name.

;Media relay endpoint/Firewall public IP: For media relay endpoints (e.g. third party SIP phones) the public address of the firewall of the PBX network can be configured. This address is signaled in the SDP to received RTP from the phone. The firewall should have configured a port forwarding to the PBX or the TURN, for the RTP range of the PBX or TURN.

;Media relay endpoint/TURN: If this checkmark is set, the PBX allocates TURN endpoints for calls to or from media relay endpoints, which registerd thru the reverse proxy (e.g. third party SIP phones)

;IP address for App Platform
: The ip address of an App Platform can be configured here, with a DNS name used for it. If myApps uses a host to access the PBX different from the configured DNS name of the PBX, the hostname in any App url, which matches the configured AP DNS, is replaced by the AP IP. This way it is possible to configure a PBX with DNS names and access it with myApps when the DNS is not yet set up. If the checkmark ''Operation without DNS'' is set as well any matching DNS name is replaced also when an App service requests the URL of another App service (Example: Users requesting the URL of Devices for provisioning) and in the URL sent to the App services itself (Example: Devices uses this URL to construct the URL set at devices for the Devices registration).

: Note that this mode is intended to be able to run the PBX using DNS names while the DNS is not yet in place. Once the DNS is up and running, neither the DNS name of the AP nor its IP address should be configured here.

;Music On Hold URL: A URL for the Music On Hold. This file is read by the PBX using HTTP and sent to a held endpoint via RTP. The format of this URL is

:'''<nowiki>http://<addr>/<file>.$coder?coder=g711a,g711u,g722,g723,g729,opus-nb,opus-wb&repeat=true</nowiki>'''. <addr> is the IP address of the http server, no dns name is allowed here. <file> is the filename. $coder will be replaced by the actual coder used.

:Parameters: ''coder=g729,g711a,g711u,g723,opus-nb,opus-wb'' is the list of available coders. Only these coders must be specified for which a corresponding file exists. ''repeat=true'' should be specified in order to loop the file endlessly. ''random=true'' can be used to start the music on hold on a random point (this will work only if the URL is not local though).

:By default the built-in Music-On-Hold is played (Pseudo URL: "MOH?coder=g729,g711a,g723&repeat=true"). You can also play a dial tone (Pseudo URL "TONE") or a ring-back tone (Pseudo URL "TONE?tone=ringback").

:The maximum length of the URL is limited to 500 characters (bytes).

:If you configure a wrong (or invalid) URL then you will have silence as MOH. To prevent this situation when the MoH for some specific context/user(see below) is missing and silence is played instead of any MoH, an additional parameter ''fallback=true'' is available. If the file provided in the URL is missing (HTTP Error 404 Not Found is delivered by the HTTP Server) and the parameter ''fallback'' is provided, the default MoH will be played instead of silence. To use a custom file as fallback MoH, instead of default MoH, any file name can be provided with the ''fallback'' parameter: e.g. ''fallback=other_filename''. The file other_filename.g7xx must be placed in the same folder as a file provided with URL. A special filename ''fallback=ringback'' can be used to generate a ringback tone (equivalent to ''TONE?tone=ringback'') instead to play an alternative file.

:Within the URL %<id> can be used to put in some context information of the call. The information refers to the party which has put the receiving party on hold. For information about the receiving party itself, the id has to be preceded by '.' (e.g. '''.l''').

:'''l''' Long Name
:'''h''' Name (H.323 id)
:'''n''' Number
:'''N''' Node
:'''P''' PBX
:'''d''' Diverting Name
:'''#d''' Diverting Number

: See [[Howto:Dynamic_MOH]] for more details on how to use dynamic music on hold.

;External Music On Hold: To offload the device from playing the Music on hold, the Music On Hold can be played by a separate device. This device can register with a name configured here. To retrieve the Music On Hold a call is sent to this device. For each held endpoint a call is sent.

;Response Timeout: Global timeout (in seconds) after which any action for no response is taken (e.g. Call Forward on No Response). A timeout configured at any object overrides this value.

;Dial Complete Timeout: Global timeout (in seconds) after which any action for incomplete dialed number is taken (e.g. incomplete destination at trunk object).

;No. of Regs w/o Pwd: Number of registration without password authentication which are allowed per user. If 0 is configured no registration without password is possible.
Pls. note that registrations from 127.0.0.1 w/o password will be accepted anyway

;Security block time(s): Time for which a registration to a user is blocked after attempt with wrong password. Default is 20s. With a value of 0 this features is turned off.

;Recall Timeout: A value configured here enables recall after transfer. If a call is transferred and not answered within this time, the call is sent back to the transferring endpoint.

;Chat no Attachments: If checked, no file attachments are allowed in chats for any user

;Retries on busy (14s): Number of retries (Each attempt runs for 14 seconds) of blind transfer to a busy endpoint, before a recall back to the initiator is executed. During an attempt, the PBX waits to see if the target is free, and then delivers the call. The default value are 4-retries if the field is empty. If there is a 0 configured no further (in addition to the initial) will be executed. (This function depends on the ''Recall Timeout'' so the ''Recall Timeout'' must not be empty)

;Max Call Duration (h): Number of hours until a call with media is disconnected automatically. Affects all calls with initialized media channels signalled via PBX.

;Group Default Visibility: Defines additional visibility for active group members. These are added to the visibility rights derived from the [[{{NAMESPACE}}:PBX/Objects/Visibility | Visibility settings]] in user or template definitions. Note that changes made here only take effect after a re-registration.

;Presence with Alert: Enable presentation of presence on phone upon alert. Setting applies for all PBX users.

;Enable External Transfer: Unless this checkbox is set any attempt to transfer an external call back to an external destination will result in disconnection of the call.

;No CLIR on Internal calls: If checked numbers are displayed even if received with presentation restricted. When sending a call presentation restricted can still be set and should be honored by a public network.

;Media Relay:
:;Off: No Media Relay is done in the PBX
:;On: All media traffic is routed through the PBX. With the '''No Media Relay if Addresses are identical or private''' checkmark, this is not done if the two call endpoints registration addresses are either private or equal (i.e. external endpoints behind the same NAT router). To identify an address as private the "Private Networks" configuration from ''IP4/General/Settings'' is used.
:;Auto: Media traffic is routed through the PBX if calls are between private and public registration addresses but not for calls between private and private or public and public registration addresses. To identify an address as private the "Private Networks" configuration from ''IP4/General/Settings'' is used. In v11 this was the behaviour if ''RTP Proxy'' was ''on''.
: Please note that when media relay is in effect for a call, '''video is not working'''. With ICE (available from v12r1), media relay in the PBX should be obsolete except for special applications. Check ''On'' or ''Auto'' only if you need to have this, since it creates CPU load on the PBX.

;Generate CDRs: If this checkbox is set, the PBX generates CDRs for all calls. For details, refer to the [[{{NAMESPACE}}:Concept_Call_Detail_Record_CDR_PBX|CDR description article]].

;Reverse Lookup URL
: A String in the LDAP URL Format according [https://tools.ietf.org/html/rfc2255 RFC2255] which will be used by the PBX to make a lookup for all external numbers.
: Number resolutions will be forwarded to internal applications like generated CDRs, Phone App etc..
: Example: ''ldaps://ap.innovaphone.com/dc=entries?givenname,sn,company?sub?(metaSearchNumber=+%n)?bindname=innovaphone.com\contacts''
:* dn: ''dc=entries''
:* attributes: ''givenname,sn,company''
:* scope: ''sub''
:* filter: ''(metaSearchNumber=+%n)''
:** %n is a placeholder for the given cgpn
:* extension: ''bindname=innovaphone.com\contacts''
:** The username for the authentication.
:'''Variables'''
:* %n - cgpn
:* %u - h323 name of the current object
: Also there is an additional field for the LDAP password
: Examples are listed in the [[{{NAMESPACE}}:Concept_Number_Resolution_and_LDAP#PBX_Configuration|Concept Article]]

;Logo URL
:The URL to a customized logo image that will be displayed on the phones. Leave empty to keep the standard logo. The image size should be 220x150px or less with 24Bit color deep or less and an RGB range. The file format should be PNG or JPEG.

;Route Root-Node External Calls to: Destination object (Long Name) of Root-Node external calls. This configuration option is available on the Master or Standby PBX only. Any call which cannot be terminated inside the PBX is sent to this destination as long as neither the source nor the destination of the call can be associated with a node with a PBX configured. This object must be assigned to this PBX.
:'''For calls from local PBX only''': If set on a master, calls from a slave are not sent to this destination but sent back to the slave where the call came from. On the slave the call is then sent to a destination configured with 'Route Root-Node External Calls to'.

;Route PBX-Node External Calls to: Destination object (Long Name) of PBX-Node external calls. Any call which cannot be terminated inside the PBX is sent to this destination as long as the source nor the destination of the call can be associated with the node of this PBX. If a call is sent from or to an object defined inside the node of this PBX or in a node hierarchically below the node of this PBX the call is associated to the node of this PBX. This object must be assigned to this PBX, that is, it has to register to this PBX.

;Route Internal Calls to: Destination object (Long Name) to which any call is sent for which a PBX internal destination was found, except for those calls that originated from that object. This can be used to apply special routing on PBX internal calls.

;Escape Dialtone from: The PBX object (Long Name) to which a call is made to get a dialtone if a dialtone is configured for the escape of a node. As above, this object must be assigned to this PBX.

;Prefix for Intl/Ntl/Subscriber/Area-Code/Country-Code: Prefixes to be used to map International, National and Subscriber numbers.
:* '''International Prefix''' (<code>000</code> in Germany).
:* '''National Prefix''' (<code>00</code> in Germany).
:* '''Subscriber''' (in Germany, <code>0</code> is a commonly used trunk line access code).
::The SubscriberID is used for hotkey-actions within myAPPs-launcher. By use of node-objects, adjust the Subscriber Prefix in the respective [[{{NAMESPACE}}:PBX/Objects/Node#Number_Mapping_.28International.2C_National.2C_Subscriber_Prefix.29|node object number mapping]].
::For myPBX-launcher hotkeys, refer to the [[{{NAMESPACE}}:Phone/User/Directories#Dialing_location|dialing location settings]].

:* '''Area-Code''' (in Germany for example, the town Mannheim has area code <code>621</code>).
:* '''Country-Code''' (for Germany, <code>49</code> would be used)

: These settings resemble the same settings found in the [[{{NAMESPACE}}:PBX/Objects/Node | Node]] and [[{{NAMESPACE}}:PBX/Objects/PBX | PBX]] object. However, they apply to the ''root'' node instead (and should be consistent through all PBXs in a multi-PBX system).
'''Max. length internal number'''

In the phone and softphone App: If the number, witch is dialed is 7 digits or longer, the subscriber prefix is added. (A reset of the pbx and the myApps is needet after changes.)
;Adjust LDAP results for e.164: Add a "+" prefix to an PBX-internal LDAP-contact-search result. This is used for 3rd-party- and DECT-phones which are not able to benefit from the Dialing Location settings in case of LDAP-search in an E.164-setup. See also [[{{NAMESPACE}}:Concept_Number_Adjustments_%28Dialing_Location%29#PBX_database_used_as_LDAP_database|concept description]].

;Tones: The tones scheme to be used for PBX generated dialtones. This applies to dialtones generated for node prefixes, ringback on transfer and some more.

=== Slave PBX ===

If the PBX is operated in Slave mode, then the Slave PBX section is displayed

;Registration: The VOIP protocol used for the registration to the master. Possible choices are H.323, H.323/TCP or H.323/TLS.

;Master: The IP address of the PBX master

;License Only: If set, the PBX obtains license from master, but acts as master in all other respects.

;Alternate Master: The IP address of an alternative PBX master (standby, if available)

;Password: The password to be used for registration at the Master as configured in the corresponding PBX Object (The length of the password is limited to 16 characters)

;Master GK-ID: The System Name/Gatekeeper ID of the PBX Master were will register (Optional, usually used for DynPBX).

;Replication: This parameter allows you to select the replication style for the slave PBX: either ''All'' or ''Local'' (only users that need to be known in this PBX). For the replication process the [[Reference9:PBX/Config/Security|PBX Password]] is used which have to be the same password on all PBXes in the system.

;dyn PBX ID: This parameter allows to set replication from a specific DynPBX configured on the Master Device.

;Use local static User DB: A dynPBX has also this checkmark. The database of the main PBX is used, but be careful due to the increased memory usage. The dynPBX will create its own PBX datastructure which allocates memory.

;Route Master calls if no Master to: If the master is not available, master calls are sent to this destination. Destination has to be an object with active registration.

;Max Calls to Master/No Reroute: This parameter can be used to limit the calls to the master. If a call is sent to the master and there are already calls to/from the master equal to or exceeding this value, the call is rejected if '''No Reroute''' is set or is handled as if the master was not available otherwise.

;License Limits: Here we can set limit of licensing for this Slave PBX for Port, Mobility, Operator and Softwarephone.

For complete replication from master to slave, check also password in [[Reference9:Administration/PBX/Security&action=edit&redlink=1|Reference9:Administration/PBX/Security]]

=== Standby PBX ===

If the PBX is operated in Standby mode, then the Standby PBX section is displayed

;Master: The IP address of the PBX master

;Replicate from Master: Turns on full replication from the master PBX

;use TLS: Use LDAPS (TLS) instead of LDAP (TCP).

For complete replication from master to slave or standby, check also password in [[Reference9:Administration/PBX/Security&action=edit&redlink=1|Reference9:Administration/PBX/Security]]

Reference16r1:Concept App Service Queues

2025-12-16T16:01:54Z

Elievens: /* Configuration */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 16r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V16r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V16 Improvements==
'''Show call diversions for the favorites section in the BLF.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Breakthrough of call diversions from BLF in favorites section.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Edit mobility destination for users.''' 
An improvement for changing the mobility destination of the users.

'''Enable numeric + key as shortcut for transfer option.''' 
The Switchboard App now supports the shortkey + as shortkey for the transfer functionality.

'''Focus on second call for easier transfer ''' 
When starting a second call in the Switchboard App, the focus will be in the call section on this second call, so that a transfer can be initiated immediately by pressing the configured short-cut, for example the numeric + key. In case the focus is in the search field, press the TAB key first.

'''Call state in outgoing call section.''' 
When having an outgoing call, the status of this call (ringing or connected) will be shown in this outgoing call for a more user-friendly and intuitive feedback.

'''Notes for in- and outgoing calls in connect.''' 
When having an in- or outgoing call, you can add a note for this call in the Connect App. When a new call arrives, the Note can be consulted as additional information about this caller or called number.

'''Fix: Issue breakthrough option/button not updated.''' 
Fixed breakthrough option/button was not updated (added/removed) when eg a CFu is set/removed.

'''Fix: Issue added users not visible immediately in BLF.''' 
Show users immediately in the BLF after adding them to a group.

'''Fix: Issue missing call-leg2 Info.''' 
Missing Call-leg2 Info now showed after connecting a Call.

'''Fix: Issue to many calls when starting call forward breakthrough.''' 
Fixed call forward breakthrough that leaded to many calls.

'''Fix: Issue to less space between buttons in BLF Details.''' 
Fixed the space between buttons in BLF user details.

'''Fix: Issue with Queues-plugin Group Configuration.''' 
The Display Name was wrongly used as User Identifier/Common Name to assign the 'queue'-group.

'''Fix: Issue Display of mismatched number with name in outgoing calls.''' 
Fixed the display of mismatched number with name in outgoing calls section on pickup.

'''Fix: Issue with missing CFx on a user after a change by the Switchboard App.''' 
Fixed the forwardings stored in PBX after a change by the Switchboard App.

'''Fix: Issue Users displayed multiple times when we click on BLF duplication button.''' 
Fixed the behavior when we click on BLF duplication button.

'''Fix: Issue when Transfer-button clicked twice.''' 
Fixed when transfer-button clicked twice, the transfer button was not removed on second call.

'''Fix: Issue Missing call after selecting IVR option.''' 
Fixed when selecting IVR option, show the waiting Queue again in the call panel section.

'''Fix: Issue transfer button shown on active calls.''' 
Fixed don't show the transfer button on active calls.

'''Further fixes will come with future service releases. Please consult our release notes accordingly.''' 

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

'''Note''': Make sure to close the Switchboard App of the user when adjusting the config this user via the Switchboard Admin App. This ensure that changes are not overwritten again with the old values.

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
* If disabled: a long list of incoming calls will be shown.
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)

Reference15r1:Concept App Service Queues

2025-12-16T16:01:39Z

Elievens: /* Configuration */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 15r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V15r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V15 Improvements==
'''Show call diversions for BLF entries.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Break-through of call diversions from BLF and Search details.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Fix for handling connections from multiple PBXs.''' 
An overall improvement of the handling when multiple calls are ringing.

'''Hotkeys for accepting and releasing calls.''' 
The myApps provide hotkeys functionality to start an App from anywhere within windows with this hotkey.
The Switchboard App now supports this hotkey functionality.

'''Focus call panel when starting switchboard''' 
When starting the Switchboard App, the focus will be in the call section, so that an incoming call can be answered immediately by pressing the enter-key.

'''Transfer button on the second call for intuitive transfer handling.''' 
When having an incoming call, a click on the Transfer button, did already show multiple transfer icons on the BLF entries. When having also an outgoing call, this icons now also appears on the outgoing call for a more user-friendly and intuitive transfer of the call. By clicking this icon on the outgoing call, the incoming call will be transferred to the outgoing call.

'''Pickup in BLF Favorites.''' 
The Phone and Softphone favorites are shown in the BLF field from the Switchboard App. New in this version, when a call is ringing at one of the favorites, a pickup symbol will be shown. By clicking on the pickup symbol, the call will start ringing on your phone and can be answered by the Switchboard App User.

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

'''Note''': Make sure to close the Switchboard App of the user when adjusting the config this user via the Switchboard Admin App. This ensure that changes are not overwritten again with the old values.

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
* If disabled: a long list of incoming calls will be shown.
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)

Reference15r1:Concept App Service Queues

2025-12-16T16:01:01Z

Elievens: /* Configuration */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 15r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V15r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V15 Improvements==
'''Show call diversions for BLF entries.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Break-through of call diversions from BLF and Search details.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Fix for handling connections from multiple PBXs.''' 
An overall improvement of the handling when multiple calls are ringing.

'''Hotkeys for accepting and releasing calls.''' 
The myApps provide hotkeys functionality to start an App from anywhere within windows with this hotkey.
The Switchboard App now supports this hotkey functionality.

'''Focus call panel when starting switchboard''' 
When starting the Switchboard App, the focus will be in the call section, so that an incoming call can be answered immediately by pressing the enter-key.

'''Transfer button on the second call for intuitive transfer handling.''' 
When having an incoming call, a click on the Transfer button, did already show multiple transfer icons on the BLF entries. When having also an outgoing call, this icons now also appears on the outgoing call for a more user-friendly and intuitive transfer of the call. By clicking this icon on the outgoing call, the incoming call will be transferred to the outgoing call.

'''Pickup in BLF Favorites.''' 
The Phone and Softphone favorites are shown in the BLF field from the Switchboard App. New in this version, when a call is ringing at one of the favorites, a pickup symbol will be shown. By clicking on the pickup symbol, the call will start ringing on your phone and can be answered by the Switchboard App User.

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

'''Note''': Make sure to close the Switchboard App of the user when adjusting the config this ser via the Switchboard Admin App. This ensure that changes are not overwritten again wiht the old values.

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
* If disabled: a long list of incoming calls will be shown.
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)

Reference15r1:Concept App Service Queues

2025-12-11T11:51:27Z

Elievens: /* Configuration */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 15r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V15r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V15 Improvements==
'''Show call diversions for BLF entries.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Break-through of call diversions from BLF and Search details.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Fix for handling connections from multiple PBXs.''' 
An overall improvement of the handling when multiple calls are ringing.

'''Hotkeys for accepting and releasing calls.''' 
The myApps provide hotkeys functionality to start an App from anywhere within windows with this hotkey.
The Switchboard App now supports this hotkey functionality.

'''Focus call panel when starting switchboard''' 
When starting the Switchboard App, the focus will be in the call section, so that an incoming call can be answered immediately by pressing the enter-key.

'''Transfer button on the second call for intuitive transfer handling.''' 
When having an incoming call, a click on the Transfer button, did already show multiple transfer icons on the BLF entries. When having also an outgoing call, this icons now also appears on the outgoing call for a more user-friendly and intuitive transfer of the call. By clicking this icon on the outgoing call, the incoming call will be transferred to the outgoing call.

'''Pickup in BLF Favorites.''' 
The Phone and Softphone favorites are shown in the BLF field from the Switchboard App. New in this version, when a call is ringing at one of the favorites, a pickup symbol will be shown. By clicking on the pickup symbol, the call will start ringing on your phone and can be answered by the Switchboard App User.

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
* If disabled: a long list of incoming calls will be shown.
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)

Reference16r1:Concept App Service Queues

2025-12-11T11:46:43Z

Elievens: /* Configuration */

[[Category:Concept|Apps]]
The Queues App Service can be installed on an innovaphone App Platform and will provide services for several Apps that can be used to manage calls and waiting queues with myApps. For example the Switchboard App.

== Applies To ==

* innovaphone PBX from version 16r1final

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* Firmware V16r1xx
* UsersAdminApp
* (Soft)PhoneApp
* ProfileApp
* CalllistApp
* Calllist-API
* RCC-API
* configured Waiting Queues in the PBX
* configured group(s) in the PBX assigned as "Static" and "Active" to the Waiting Queue
* License “App(innovaphone-switchboard)13” (order no. 02-00050-007) per application-user
* A dedicated group(queues) in the PBX assigned as "Static" to all Waiting Queues used by the Switchboard App and assigned as "Static and Active" to all Switchboard Users

==V16 Improvements==
'''Show call diversions for the favorites section in the BLF.''' 
This feature shows, with a colored label in the BLF entry, the configured call forwarding from the respective User. The color of the label depends on the type of configured forwarding, CFNR (orange/yellow), CFB (red) or CFU (purple). A click on the label, shows the configured forwarding destination.

'''Breakthrough of call diversions from BLF in favorites section.''' 
With a new icon (handset with arrow) it is possible to call to the User with a Call forward and breakthrough this call forward. This applies for CFB and CFU. In case of a CFNR the CFx-breakthrough does not apply because the call rings first at the user and after the configured timer the CFNR will be executed.

'''Edit mobility destination for users.''' 
An improvement for changing the mobility destination of the users.

'''Enable numeric + key as shortcut for transfer option.''' 
The Switchboard App now supports the shortkey + as shortkey for the transfer functionality.

'''Focus on second call for easier transfer ''' 
When starting a second call in the Switchboard App, the focus will be in the call section on this second call, so that a transfer can be initiated immediately by pressing the configured short-cut, for example the numeric + key. In case the focus is in the search field, press the TAB key first.

'''Call state in outgoing call section.''' 
When having an outgoing call, the status of this call (ringing or connected) will be shown in this outgoing call for a more user-friendly and intuitive feedback.

'''Notes for in- and outgoing calls in connect.''' 
When having an in- or outgoing call, you can add a note for this call in the Connect App. When a new call arrives, the Note can be consulted as additional information about this caller or called number.

'''Fix: Issue breakthrough option/button not updated.''' 
Fixed breakthrough option/button was not updated (added/removed) when eg a CFu is set/removed.

'''Fix: Issue added users not visible immediately in BLF.''' 
Show users immediately in the BLF after adding them to a group.

'''Fix: Issue missing call-leg2 Info.''' 
Missing Call-leg2 Info now showed after connecting a Call.

'''Fix: Issue to many calls when starting call forward breakthrough.''' 
Fixed call forward breakthrough that leaded to many calls.

'''Fix: Issue to less space between buttons in BLF Details.''' 
Fixed the space between buttons in BLF user details.

'''Fix: Issue with Queues-plugin Group Configuration.''' 
The Display Name was wrongly used as User Identifier/Common Name to assign the 'queue'-group.

'''Fix: Issue Display of mismatched number with name in outgoing calls.''' 
Fixed the display of mismatched number with name in outgoing calls section on pickup.

'''Fix: Issue with missing CFx on a user after a change by the Switchboard App.''' 
Fixed the forwardings stored in PBX after a change by the Switchboard App.

'''Fix: Issue Users displayed multiple times when we click on BLF duplication button.''' 
Fixed the behavior when we click on BLF duplication button.

'''Fix: Issue when Transfer-button clicked twice.''' 
Fixed when transfer-button clicked twice, the transfer button was not removed on second call.

'''Fix: Issue Missing call after selecting IVR option.''' 
Fixed when selecting IVR option, show the waiting Queue again in the call panel section.

'''Fix: Issue transfer button shown on active calls.''' 
Fixed don't show the transfer button on active calls.

'''Further fixes will come with future service releases. Please consult our release notes accordingly.''' 

== Apps ==
=== Switchboard App (innovaphone-switchboard) ===
[[Image: Switchboard-App.png|50px|switchboard-app.png/|switchboard-app.png/]]

The Switchboard App is an attendant workstation integrated into the myApps user interface. At a switchboard workstation, an employee of a company or a telephone network operator can process incoming calls and connection requests from external or internal callers. An employee can accept connections, request information, put calls on hold, transfer them to the desired destination, or reject the connection. The calls displayed are the ones from the monitorized phone device and they are managed using the RCC-API. The Switchboard App needs a license per Switchboard user, called the Switchboard App.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard</pre>
;Websocket
;TableUsers: to be able to replicate the users for the BLF
;Admin: to be able to edit the User object to monitor or un-monitor a waiting queue
;PbxApi: to edit the presence information
;RCC: to use the RCC API to manage the calls
;Impersonation: to get the Phone App favorites

=== Switchboard Admin App (innovaphone-switchboard-admin) ===
[[Image: Innovaphone-switchboard-admin.png|50px|innovaphone-switchboard-admin.png/|innovaphone-switchboard-admin.png/]]

With the Switchboard Admin App an administrator can manage the user(s) rights, can assign waiting queues to users and can pre-configure the Busy Lamp Field BLF.

Parameters:
;URL: <pre>http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-switchboard-admin</pre>
;Websocket
;TableUsers: to be able to replicate the users from the PBX
;Admin: to be able to assign the waiting queue groups to the user

== PBX Manager Plugins ==

=== Queues ===

With the Queues plugin the Switchboard App and Switchboard Admin App Objects can be created, edited and deleted on the PBX.

==Configuration==
# Install the Queues App
#* Option 1: Settings Apps/App Installer plugin - Search and Install the Queues App or
#* Option 2: AP Manager/App Store:
#** Search and Install the Queues App
#** Create an Instance of the Queues App
#** Start the created instance
# Settings App/Queues Plugin - Create the necessary App Objects:
#* Switchboard App: e.g. 'Switchboard'/'switchboard'
#* Switchboard Admin App: e.g. 'Switchboard Admin'/'switchboard-admin'
# Assign the Switchboard App and License to the correct users (can be done User- or Config Template-based)
# Assign the Switchboard Admin App to the correct Admin-users (can be done User- or Config Template-based)
# Configure Master PBX via the Switchboard Admin App Settings (optional with a single PBX):
#* PBX Name: PBX Name (PBX/Config/General/PBX Name) of the Master PBX
#* DNS (optional): DNS Name (PBX/Config/General/PBX Name) of the Master PBX Restart the Queues Instance after changing (so the App Objects can re-connect).
# Configure Waiting Queues via the Settings App/Waiting Queues Plugin or check existing Waiting Queues:
#* Waiting Queues monitored by the Switchboard App must have a '''Primary Group''' (used by the Switchboard Admin App to assign groups to Users)
#* Waiting Queues monitored by the Switchboard App must '''not''' have the ''''Operator connect for SOAP''''-checkbox ticked (needed to release calls correctly when taken/accepted by another Switchboard User)
# Create a Monitoring Group '''queues''' for the Switchboard (Admin) App. This can be done easily via the Queues Plugin of the Settings App (Groups configuration) or via the Advanced UI of the PBX:
#* '''Waiting Queues''' to be seen by the Switchboard App must have this group assigned '''Static only'''
#* '''Switchboard Users''' must have this group assigned '''Static and Active'''
# Configure the Switchboard Users via Switchboard Admin App:
#* Assign the correct rights / Waiting Queues to be monitored
#* (Optional) Create or Assign an already created Busy Lamp Field
# Adjust the Switchboard User Object and Phone Config (can also be done via a Config Template (desk phones only)):
#* Object: '''Untick 'Twin Phones'''' => Picking alerting calls (BLF or Waiting Queue-section) is possible
#* (Soft)Phone: '''Enable 'Call Waiting'''' => handling of multiple calls is possible (e.g. pickup call while there is an already alerting call)
# (Optional) Adjust the PBX/Phone/myApps/UsersAdmin App Config for better usage:
#* PBX: Configure the Recall Timeout of the PBX (PBX/Config/General/Recall Timeout) => Blind Transferred calls can be taken back
#* Phone: Configure a Park-key on the phone(s) of the Switchboard User(s) => visual/audio reminder of Parked Calls after X seconds
#* myApps: Deselect the default (Soft)Phone App + Untick the "Bring AppSharing/Video always to front" in your (Soft)Phone App => prevention of the (Soft)Phone App to popup.
#* UsersAdmin App: Tick the 'Privacy/Display e-mail address' in the Settings of the Users Admin, so that a callback-button is shown for User-search results.
# Open the Switchboard App and Select a (Soft)Phone to be controlled in the Settings/Hamburger Menu

==Switchboard Admin App - User interface==
When opening the Switchboard Admin App the Switchboard Admin App shows only a search field at start (since release V14r1).
It will not list all users anymore, which speeds up the start of the App in big environments with many users.
At this point, closing the Switchboard Admin App, doesn't make any changes to the Switchboard App database.

===Search field===
Search for the user of your choice by typing its name.
The users details include their configured CFx since V15r1 and up.
When multiple user are shown, select the correct user.
The more detailed information (Rights / Busy lamp field) shown is retrieved from the Switchboard App database, while the existing user's group membership of the configured waiting queues, is retrieved from the PBX.

===Rights===
Here, you can define the rights of the Switchboard App user:
* Edit waiting queues: the user is allowed to add or delete waiting queues in the Switchboard App, to receive calls from.
* Edit presence: the user is allowed to change the presence state and presence note from other users in the system.
* Edit call diversions and mobility: the user is allowed to change other user's call forwards, mobility and its destinations.

===Waiting Queues===
This section shows the membership of primary group activity from the respective waiting queue.
This information is retrieved from the PBX. Changes will be saved into the PBX and the Switchboard App database.
Be aware that when making any changes to the selected user, it will be saved in the PBX and the Switchboard App database as well.
It might overwrite the latest group membership change done by the Switchboard App user itself. 
To make sure that your Administrative group membership settings will apply, make sure that the user's Switchboard App is closed before doing any changes. 
You might want to verify the user's preferred settings before, to apply them respectively with your changes.

The, in the PBX manager, pre-configured waiting queues will be shown to select the possible group membership. The possible choices are:
* Off: this waiting queue will not be shown in the user's Switchboard App for login.
* Dynamic-In: this waiting queue will be shown in the user's Switchboard App and the user is automatically logged-in the group with the start of the App (the user logs off from the group when closing the Switchboard App).
* Dynamic-Out: this waiting queue will be shown in the user's Switchboard App and the user is logged-off at start of the App (the user logs off from the group when closing the Switchboard App).
* Static: this waiting queue will be shown in the user's Switchboard App and the user is static in the group without the option to log-off (the user stays active in the group after closing the Switchboard App).

===Busy Lamp Field===

The Busy Lamp Field (BLF) section in the Switchboard Admin App, allows you, as admin, to pre-define the BLF groups and the PBX Users in the groups.
There is also the option to copy an already configured BLF from another user and edit it to your preferences.

==Switchboard App - User interface==
[[File:Switchboard app user interface.png|thumb|switchboard_app_user_interface.png/|switchboard_app_user_interface.png/]]
The user interface is divided in 3 panels:
* Left panel : Busy Lamp Field and users search
* Central panel: Calls
* Right panel: Waiting queues and calls history

There is also a hamburger menu, where some configuration settings can be edited.

=== Left panel ===
==== Busy Lamp Field ====
[[File:Switchboard app BLF contact.png|thumb|switchboard_app_blf_contact.png/|switchboard_app_blf_contact.png/]]
The '''BLF''' is displayed on the left panel. There all the users replicated from the PBX are displayed and it can be undocked and displayed on another window.
Information displayed by user:
* Profile picture
* Presence
* Common name
* Phone number
* CFx label if a CFx is configured (destination of the CFx is visible with a click on the label)

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a call by using the phone button
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display users detailed contact information
* Create BLF groups
* Re-arrange BLF groups by moving one entry '''on top of''' another entry in order to place it '''before it'''.
* Add a user to a BLF group
* Delete a user from a BLF group by long press left mouse
* Call Breaktrough on configured CFB or CFU

The BLF contacts is limited to PBX users and Contacts from the Contacts App with the proper detailed information. A Name, sip-name and number must be available as minimum information

==== Users search ====
[[File:Switchboard app contact information search result.png|thumb|switchboard_app_contact_information_search_result.png/|switchboard_app_contact_information_search_result.png/]]
The '''users search''' (Search-API) can be done with the input field. This input field can also be used to directly dial using the phone button.
Information displayed by user:
* Profile picture
* Presence
* Common name
* CFx if configured

Actions allowed:
* Select a user to Transfer a call by clicking on it
* Start a chat
* Start a call
* Start a Breakthrough call on CFB or CFU
* Send an email
[[File:Switchboard app BLF contact information detailed.png|thumb|switchboard_app_blf_contact_information_detailed.png/|switchboard_app_blf_contact_information_detailed.png/]]
The user '''details''' can also be expanded by clicking on the arrow icon.
Data displayed (read only) for the user:
* Profile picture
* Common name
* SIP
* Phone number
* Email
* PBX
* Node

Data displayed that can also be edited for the user (if the user has the appropriate rights):
* Presence note
* Presence
* Call diversions
* Mobility

Actions allowed:
* Start a chat
* Start a call (by SIP and phone number)
* Send an email
* Send a "Call me back" notification by email
* Add the user to a BLF group

=== Center panel ===
On the center panel the calls are displayed.

==== Calls ====
The calls are divided in 5 sections: in the waiting queue, incoming, outgoing, parked and transferred.

Depending on the call state, different '''actions''' are allowed to manage the calls:
* Connect/Disconnect a call
* Mute/Unmute a call
* Hold/Release a call
* Park/Unpark a call
* Transfer a call to a user or connect 2 calls
* Pick up a transferred call or a call from the waiting queue

=== Right panel ===
On the right panel the waiting queues and the calls history are displayed.

==== Waiting Queues ====
On the right panel the '''waiting queues''' are displayed. They can be added by clicking on "Add waiting queue" (only displayed if the user has the appropriate right), which will automatically add the user to the given group. The calls will be displayed on the calls section and from there they can be picked up or transferred to an user.

==== Calls history ====
On this panel also the '''calls history''' is displayed, which is received from the Call List-API.

Information displayed on entry:
* Call flow
* Call information (source/destination, date and duration)

Actions allowed:
* Start a call
* Start a chat
* Send an email
* Send a "Call me back" notification by email
* Display contact information
* Add the user to a BLF group

=== Hamburger menu ===
On the hamburger menu the '''shortcuts''' can be edited and the size of the users items from the BLF can be customized.
==== Edit shortcuts ====
To edit a shortcut, the shortcut must be selected and then the desired key pressed. Afterwards it has to be clicked again to finish the editing. To remove a shorcut, select the shortcut and press the "Del" key on your keyboard.

==== Size of the user items (BLF) ====
There are 2 different size:
* Icons only: only the profile picture, presence and common name will be displayed.
* Detailed large: the phone number and the call button are displayed too.

==== Limit displayed calls in waiting queues section ====
Different view of incoming calls in the waiting queues section
* If enabled: a short list of incoming calls will be shown and a scrollbar will appear in this section
* If disabled: a long list of incoming calls will be shown.
The amount of showed calls in both scenarios depends on the used display size and resolution configuration (adaptive design)

==== Select monitored device ====
If a device is selected, all the calls from/to that device will be monitored by the app.

==Additional information==
===Licensing===
* When using the OperatorV13 license in a pre V13r2 release, and you want to use the Switchboard App instead in a > V13r2, you need to download a new license file from my.innovaphone
* Upgrade from Operator, the Operator13 license will result in 3 times App(innovaphone-switchboard)13 in addition.

===Reverse Lookup from Contacts===
For Reverse Lookup to work both for Queue-calls as Operator-calls, the Directory must have the correct Access Rules:
* if the directory has no ACL-rules => will work for Queue- and Operator Calls
* if the directory has ACL-rules => a rule for each object (WQ and Operator) must apply:
** the name of the WQ/Operator-object
** an active group of the WQ/Operator

===Info field for BLF contact details, Operator Note===
The Switchboard Operator can use the Contacts App to add or edit the contact details with the Info field, to show additional information like an "Operator Note".

The information added to the Info field, will be shown in the detailed view of a BLF Contact or in the detailed view of a searched contact at the bottom as additional information aka "Operator Note"

==Known issues==
* When closing the Switchboard App, the user will be logout of all the waiting queues groups. When opening the app again, the user will be automatically logged-in on this groups again. (This is by design)
* Shortcuts may not be triggered on the Switchboard App if the app is not on focus. For this just click on the UI of the app.
* If a softphone is being monitored, the Softphone App must be opened on background. Otherwise the RCC-API will not sent calls information to the Switchboard App. Since >= V13r3 this will be done automatically.
* If no (soft)phone device has been selected on the hamburger menu of the Switboard App, the calls may be displayed duplicated because that means that the app is monitoring all the devices. To avoid this please select your default (Soft)Phone App on the phone devices section.
* When using the Softphone App with the same name and hardware-id on multiple devices (PC and Smartphone) an incoming call will be shown more than once, depending on the amount of used devices. You can add a Softphone with different naming and hardware-ID for the Switchboard User to use with the Switchboard App only.
* As Switchboard App "Operator" you will work mainly with the Switchboard App. To have video from internal callers, you need to have a (Soft)Phone App open in the background. Deselect your Default Phone device in the myApps otherwise this App will get focus during the incoming call and on connect after answering a call. Best Practice to undock the Video from your (Soft)Phone App in the background and deselect the option "Bring AppSharing/Video always to front" as this would bring your (Soft)Phone App to the front as well.
* When using Softphone App on X multiple devices, incoming calls will be displayed X multiple times. In scenarios where the Switchboard App user has multiple devices with myApps(Smartphone, tabblet, PC) it might make sense to create a Softphone with different name for each device or at least for the device where you want to use the Switchboard App with the Softphone App. Using different names for the Softphones, creates respectively different hardware-ID's. This assures that only the selected specific Softphone App and device will be monitored by the Switchboard App based on this specific name and HW-ID.
* If LDAP contacts are not displayed on the search results, please check if the rights for the LDAP object have been given to the Switchboard App.
* It is possible that the app instance needs to be restarted if the PBX name has changed on the hamburger menu of the Switchboard Admin App.
* Use unique group name per waiting queue. The Group and group name, assigned to your waiting queue, should not be (re)used for other Waiting Queues or other groups.

==Trouble shooting==
* If any issue can be reproduced, open the console output of your browser or right-click and inspect in the native client version of the Switchboard App. Clear the console output and reproduce the issue and copy past the output as a textfile and send this attached in your support ticket.

==Related Articles==
* SDK Integration (if the content is available)