innovaphone wiki - User contributions [en]

Reference14r1:Apps/PbxManager/App Microsoft365

2025-10-02T08:58:16Z

The: /* Add an app object */

With the Connector for Microsoft 365 PBX-Manager plugin, the needed app object can be created and configured automatically.

== Add an app object ==

;name
:The ''name'' displayed for the app object which must be unique.

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

== Add an API object ==

;name
:The ''name'' from the API object, which must be named microsoft365-api.

;SIP
:The ''sip'' from the API object, which must be named microsoft365-api.

Reference16r1:Concept App Service Connector for Microsoft 365

2025-07-23T12:24:58Z

The: /* Technical Overview */

{{FIXME|reason=This article is still work in progress}}

[[Category:Concept|Apps]]
== Applies To ==

* Connector for Microsoft 365 from Version 16r1

= Overview =

Connector for Microsoft 365 synchronizes Microsoft Teams presences with the innovaphone PBX and back, and optionally additionally Calendar presence from Exchange Online (part of the Microsoft 365 Cloud Services).
It is also possible to search for your own contacts.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform (minimum version 120004)
* V16r1
* App(Connector for Microsoft 365)
* PBX-App(innovaphone-microsoft365) license per user - order no. 02-00050-009

== Concept ==

=== User Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure User Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph API.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made periodically.

The app synchronises the PBX presence with Teams through the Graph Api. The on-the-phone presence will be renewed every 5 minutes. The other presences have a lifetime of 1 day but the away has a lifetime of 7 days.
The lifetimes are described [https://learn.microsoft.com/en-us/graph/api/presence-setuserpreferredpresence?view=graph-rest-1.0&tabs=http here]

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

===== User Matching =====
You now can choose the fields used for user matching on either side from the following options:
* PBX
** CN (Long Name property from the PBX user object)
** h323 (Name property from the PBX user object)
* Azure Portal
** displayName
** mail
** mailNickname
** onPremisesDistinguishedName
** onPremisesSamAccountName
** onPremisesUserPrincipalName
** userPrincipalName

Additionally, you have the possibility to remove a possibly contained domain from the Azure fields content. 
Example: 'user@domain.tld' is transformed to 'user', if this option is checked.

===== Mapping Table =====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

===== Master/Slave =====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

=== Calendar Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure_Calendar_Presence_Sync_by_Connector_for_Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 15r1 the Connector for Microsoft 365 will offer a possibility to sync Azure Portal calendar events (Teams, Exchange online) via the Graph API with the PXB presence. 
For now the [https://wiki.innovaphone.com/index.php?title=Reference13r3:Concept_App_Service_Calendar Calendar App] is (along with other functions) also capable of syncing calendar events, but using the old EWS mechanism, which Microsoft announced as end of life starting from 2026. 
'''Warning:''' Please make sure to not use both apps for syncing calendar events in parallel, this is not supported and will most likely lead to conflicts and unexpected behaviours. 
 
When the configuration of the connector for Microsoft 365 Calendar Presence Sync is complete, the app connects to Microsoft to receive a token with the calendar app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, a subscription for calendar events is created at Microsoft to receive event changes in Microsoft Calendar for these users. 
 
A user subscription is also started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 
If a calendar event has been started or ended, it is forwarded to the PBX. 

* User subscriptions are renewed every 60 minutes.
* Event subscriptions are renewed every day.
* License Check is made every hour.

=== Contact Search ===

==== Configuration ====
Please have a look into our [[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 16r1 the Connector for Microsoft 365 will offer a possibility to search for your own contacts (Teams, Exchange online) via the Graph API.

When the configuration of the connector for Microsoft 365 Contact Search is complete, the app connects to Microsoft to receive a token with the contact search app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, the user can search with the Phone App, for example. The search string is made available to the Connector for Microsoft 365 via the microsoft365-api. The results are sent to the consumer, e.g. the Phone App and presented there. 
 
A user subscription is started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 

* User subscriptions are renewed every 60 minutes.
* License Check is made every hour.

== Related Articles ==

=Known Limitation=

== General ==
''Applies to the User Presence and the Calendar Presence''

=== Synchronization Delay ===
In the official Graph-API documentation, Microsoft is providing an overview about expected latencies for change notifications. 
You can find a whole overview table here: 
https://learn.microsoft.com/en-us/graph/change-notifications-overview#latency 
 
For the user presences the resource "presence" is used and an average latency of 10 seconds but a maximum up to 1 minute is provided. 
Such a delay in syncing changed presences from Teams down to the PBX are considered normal and are caused by the Microsoft Graph-API. 
 
In case of calendar events the average is provided as "less than 1 minute" and the maximum to 3 minutes. 

== User Presence ==
=== Line states set by the PBX does not block calls in Teams ===
Line states set by a 3rd party application (like the Connector for Microsoft 365) through the graph API are currently '''only for display purpose and do not block new calls''' in Teams. 
 
https://techcommunity.microsoft.com/t5/teams-developer/ms-graph-setpresence-problems/m-p/2798805/highlight/true#M3957 
As you can see in the above linked discussion, there once existed a feature request on Microsoft Voice, which is no longer available since it was not voted.
=== Maximum number of supported users ===
The connector now supports multiple Microsoft Teams communication users, which is the prerequisite to subscribe for more than 650 users. There is a new ribbon (Manage Teams Accounts) that allows you to configure as many communication users as you need. Every configured communication user can be used to subscribe 650 users, for example:

*3 configured communication users x 650 licensed users = 1950 users can be subscribed
'''Please be aware''': Each communication user must have a Teams license applied.

This limitation is caused by Microsoft. 
In the documentation of the Graph-API you will find a hint to this limitation: 
https://learn.microsoft.com/en-us/graph/changenotifications-for-presence#subscribe-to-multiple-users-presence 
Trying to subscribe more than 650 users (with one communication user) by using the presence subscription API will be declined by the graph API with an error message, that too many users are requested. 

=== Communication User (UserSynctoPbx) ===
Users with MFA (multi-factor-authentication) are not supported as technical communication user for the Connector.

=== Multiple sites / instances require multiple communication users ===
Each instance or each site must have separate communication users, as Microsoft only allows one concurrent subscription per communication user. (otherwise an HTTP 409 conflict will occur)

This means that if you want to subscribe to the same Azure Portal backend from two different sites (or instances), you will need to have multiple communication users (each with an applied Teams licence) in order to be able to subscribe from all endpoints.

=== Subscription Timeout ===

==== Situation ====
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

==== Impact ====
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=
== General ==

===Creating an app trace===
For further analysis and creating a support ticket it will be useful to have a suitable app trace. 
Before creating the trace please make sure the following trace flags are activated for the app instance:
* App
* Database
* HTTP client
* TLS
* TCP
* App WebSocket
* Config
* Webserver

After setting the config flags, please make sure to
* stop the instance
* deleting the current instance log
* start the instance
'''Now please wait at least 5 Minutes before you save the log''', otherwise we could not have the whole picture in the trace.

The restart and deletion of the the old log is useful the see the complete initialization process right away.

===SSL Certificate for notification URL===
It also is useful to make sure the notification URL has a valid and public signed certificate. 
You can do that, using an SSL-Checker, for example: https://www.sslshopper.com/ssl-checker.html 
Without a valid, public signed certificate, Microsoft will decline the connection since it will not be possible to establish a trust relationship for the SSL/TLS secure channel.

===Correctness of notification URL===
You can try to open the notification URL in your Browser 
Most likely you will see a HTTP 404 (Not Found) error message, which is the expected behavior since we are not providing an HTML website, the HTTP GET request from the browser will not be answered with content. 
This is perfectly fine since Microsoft will send presence updates with HTTP POST and will not try to request content from our app. 
 
What you can find out by trying to open the URL in your browser are the two following things: 
* If you receive a HTTP 404 error message you are most likely connected to an App Platform, if not you need to check your DNS (and maybe also reverse proxy) settings.
* If the URL is modified and the used build number is added, an app has answered your request
** Example: <code>https://public.dns/your.domain/microsoft365/subscriptions</code> is modified to <code>https://public.dns/your.domain/microsoft365/1510411/subscriptions</code>
** If this is not the case, your URL is wrong. (Be aware: The URL depends on the settings of the web server path of your app instance)

'''Be aware:''' The URL-Recognition in the Application Platform is '''case sensitive'''.

== User Presence ==
===GUI Feedback===
The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. 
Sometimes it needs a little bit time until the states are changed. 
If the states remain, it is mandatory to enable logs on the app platform and check for more information. 
([[Howto13r3:Configure Connector for Microsoft365#Creating an app trace|Concept App Service Connector for Microsoft 365: Creating an app trace]])

====No connection to Master PBX====
Check the MasterPBX name. 
The field must only contain the name [pbx], '''not the full domain''' [pbx.domain.tld]. ([[Howto13r3:Configure Connector for Microsoft365#Synchronization from Teams to the PBX|Synchronization from Teams to the PBX - Master PBX field]])

====Presence subscription failed====
There are many reasons why the "Presence subscription failed" message could be displayed. 
We try to list the most common reasons:
* The permission for the registered app in the Azure portal are not correctly set ([[Howto13r3:Configure Connector for Microsoft365#Create an App for syncing Teams to PBX|Howto: Create an App for syncing Teams to PBX]])
* The Notification URL is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The App service is not reachable from the internet ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The certificate for the public endpoint (e.g. reverse proxy) is not valid, or not publicly signed ([[Reference13r3:Concept App Service Connector for Microsoft 365#SSL Certificate for notification URL|Concept App Service Connector for Microsoft 365: SSL Certificate for notification URL]])
* The user from PBX and the Azure Portal cannot be matched ([[Reference13r3:Concept App Service Connector for Microsoft 365#User Matching|Concept App Service Connector for Microsoft 365: User Matching]])
* The App Platforms clock time is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#App Platform clock time is wrong|Concept App Service Connector for Microsoft 365: App Platform clock time is wrong]])
* No user has a valid Connector for Microsoft 365 App license ([[Reference13r3:Concept App Service Connector for Microsoft 365#Requirements|Concept App Service Connector for Microsoft 365: Requirements]])

===Teams License for communication user===
If presence subscription does not work, please check if all of the configured communication users have a Microsoft Teams license applied and no multifactor authentication is in use for this particular user. 
Also please make sure you can login with the configured credentials. (If you have set a password as an Administration, the user needs to change the password during the first login, therefore the given password will be invalid for API access). 
''Sometimes, after changing setting or after the instance has restarted it can take up to 12 minutes until the presence subscription is working correctly. (Due to the subscription timeout)''

= Known Issues =
== Special Characters In Password ==
If you are using special characters (*, &, (, ), etc.) in you password you could possibly run into a problem with the authentication of the communication user. 
The authentication failed status is beeing displayed. 
For the moment the only workaround is to eliminate special characters from you password.

==App Platform clock time is wrong==
If the clock time at the App Platform is not correct, this will lead to an unstable behaviour of the Connector for Microsoft 365. 
Since the Connector for Microsoft 365 is using the Microsoft Graph APIs presence subscription function, it needs to provide in its request a precise time until the subscription validity will be expired. 
The app service is handling subscription and will automatically recreate a new subscription each time the previous one has expired. 

A wrong clock time will lead to false expiration times and thus
* the subscription will be expired earlier than expected (synchronisation is not working because there is no valid subscription)
* the subscription will be valid longer than expected (the app service is trying to create a new subscription because it is expecting the previous one to be expired - will lead to a 409 conflict error, because only one subscription can be valid at a time)

If you are not sure about the current time of the App Platform, you can login via SSH into the App Platform and execute the <code>date</code> command to check the current time. 
You will receive an output like:
Tue Mar 12 13:38:57 UTC 2024
Please be aware: The time is displayed in UTC, so please make sure to convert to your local time zone.

==Geoblocking==
Since there might be no reliable country assignment for Microsoft addresses, all Microsoft addresses must be enabled on the upstream firewall in the event of geoblocking in order to ensure functionality of the Office365 Connector. 
As an alternative you might be able to configure your firewall to bypass the geoblocking for the configured notification URL.

= Related Articles =
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Contact Search by Connector for Microsoft365]]

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

Reference16r1:Concept App Service Connector for Microsoft 365

2025-07-23T12:22:58Z

The:

{{FIXME|reason=This article is still work in progress}}

[[Category:Concept|Apps]]
== Applies To ==

* Connector for Microsoft 365 from Version 16r1

= Overview =

Connector for Microsoft 365 synchronizes Microsoft Teams presences with the innovaphone PBX and back, and optionally additionally Calendar presence from Exchange Online (part of the Microsoft 365 Cloud Services).
It is also possible to search for your own contacts.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform (minimum version 120004)
* V16r1
* App(Connector for Microsoft 365)
* PBX-App(innovaphone-microsoft365) license per user - order no. 02-00050-009

== Concept ==

=== User Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure User Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph API.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made periodically.

The app synchronises the PBX presence with Teams through the Graph Api. The on-the-phone presence will be renewed every 5 minutes. The other presences have a lifetime of 1 day but the away has a lifetime of 7 days.
The lifetimes are described [https://learn.microsoft.com/en-us/graph/api/presence-setuserpreferredpresence?view=graph-rest-1.0&tabs=http here]

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

===== User Matching =====
You now can choose the fields used for user matching on either side from the following options:
* PBX
** CN (Long Name property from the PBX user object)
** h323 (Name property from the PBX user object)
* Azure Portal
** displayName
** mail
** mailNickname
** onPremisesDistinguishedName
** onPremisesSamAccountName
** onPremisesUserPrincipalName
** userPrincipalName

Additionally, you have the possibility to remove a possibly contained domain from the Azure fields content. 
Example: 'user@domain.tld' is transformed to 'user', if this option is checked.

===== Mapping Table =====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

===== Master/Slave =====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

=== Calendar Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure_Calendar_Presence_Sync_by_Connector_for_Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 15r1 the Connector for Microsoft 365 will offer a possibility to sync Azure Portal calendar events (Teams, Exchange online) via the Graph API with the PXB presence. 
For now the [https://wiki.innovaphone.com/index.php?title=Reference13r3:Concept_App_Service_Calendar Calendar App] is (along with other functions) also capable of syncing calendar events, but using the old EWS mechanism, which Microsoft announced as end of life starting from 2026. 
'''Warning:''' Please make sure to not use both apps for syncing calendar events in parallel, this is not supported and will most likely lead to conflicts and unexpected behaviours. 
 
When the configuration of the connector for Microsoft 365 Calendar Presence Sync is complete, the app connects to Microsoft to receive a token with the calendar app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, a subscription for calendar events is created at Microsoft to receive event changes in Microsoft Calendar for these users. 
 
A user subscription is also started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 
If a calendar event has been started or ended, it is forwarded to the PBX. 

* User subscriptions are renewed every 60 minutes.
* Event subscriptions are renewed every day.
* License Check is made every hour.

=== Contact Search ===

==== Configuration ====
Please have a look into our [[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 16r1 the Connector for Microsoft 365 will offer a possibility to search for your own contacts (Teams, Exchange online) via the Graph API.

When the configuration of the connector for Microsoft 365 Contact Search is complete, the app connects to Microsoft to receive a token with the contact search app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, the user can search with the Phone App for example. The search string is provided to the Connector for Microsoft 365 via the microsoft365-api. The results are send to the consumer, for example the Phone App and were presented there. 
 
A user subscription is started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 

* User subscriptions are renewed every 60 minutes.
* License Check is made every hour.

== Related Articles ==

=Known Limitation=

== General ==
''Applies to the User Presence and the Calendar Presence''

=== Synchronization Delay ===
In the official Graph-API documentation, Microsoft is providing an overview about expected latencies for change notifications. 
You can find a whole overview table here: 
https://learn.microsoft.com/en-us/graph/change-notifications-overview#latency 
 
For the user presences the resource "presence" is used and an average latency of 10 seconds but a maximum up to 1 minute is provided. 
Such a delay in syncing changed presences from Teams down to the PBX are considered normal and are caused by the Microsoft Graph-API. 
 
In case of calendar events the average is provided as "less than 1 minute" and the maximum to 3 minutes. 

== User Presence ==
=== Line states set by the PBX does not block calls in Teams ===
Line states set by a 3rd party application (like the Connector for Microsoft 365) through the graph API are currently '''only for display purpose and do not block new calls''' in Teams. 
 
https://techcommunity.microsoft.com/t5/teams-developer/ms-graph-setpresence-problems/m-p/2798805/highlight/true#M3957 
As you can see in the above linked discussion, there once existed a feature request on Microsoft Voice, which is no longer available since it was not voted.
=== Maximum number of supported users ===
The connector now supports multiple Microsoft Teams communication users, which is the prerequisite to subscribe for more than 650 users. There is a new ribbon (Manage Teams Accounts) that allows you to configure as many communication users as you need. Every configured communication user can be used to subscribe 650 users, for example:

*3 configured communication users x 650 licensed users = 1950 users can be subscribed
'''Please be aware''': Each communication user must have a Teams license applied.

This limitation is caused by Microsoft. 
In the documentation of the Graph-API you will find a hint to this limitation: 
https://learn.microsoft.com/en-us/graph/changenotifications-for-presence#subscribe-to-multiple-users-presence 
Trying to subscribe more than 650 users (with one communication user) by using the presence subscription API will be declined by the graph API with an error message, that too many users are requested. 

=== Communication User (UserSynctoPbx) ===
Users with MFA (multi-factor-authentication) are not supported as technical communication user for the Connector.

=== Multiple sites / instances require multiple communication users ===
Each instance or each site must have separate communication users, as Microsoft only allows one concurrent subscription per communication user. (otherwise an HTTP 409 conflict will occur)

This means that if you want to subscribe to the same Azure Portal backend from two different sites (or instances), you will need to have multiple communication users (each with an applied Teams licence) in order to be able to subscribe from all endpoints.

=== Subscription Timeout ===

==== Situation ====
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

==== Impact ====
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=
== General ==

===Creating an app trace===
For further analysis and creating a support ticket it will be useful to have a suitable app trace. 
Before creating the trace please make sure the following trace flags are activated for the app instance:
* App
* Database
* HTTP client
* TLS
* TCP
* App WebSocket
* Config
* Webserver

After setting the config flags, please make sure to
* stop the instance
* deleting the current instance log
* start the instance
'''Now please wait at least 5 Minutes before you save the log''', otherwise we could not have the whole picture in the trace.

The restart and deletion of the the old log is useful the see the complete initialization process right away.

===SSL Certificate for notification URL===
It also is useful to make sure the notification URL has a valid and public signed certificate. 
You can do that, using an SSL-Checker, for example: https://www.sslshopper.com/ssl-checker.html 
Without a valid, public signed certificate, Microsoft will decline the connection since it will not be possible to establish a trust relationship for the SSL/TLS secure channel.

===Correctness of notification URL===
You can try to open the notification URL in your Browser 
Most likely you will see a HTTP 404 (Not Found) error message, which is the expected behavior since we are not providing an HTML website, the HTTP GET request from the browser will not be answered with content. 
This is perfectly fine since Microsoft will send presence updates with HTTP POST and will not try to request content from our app. 
 
What you can find out by trying to open the URL in your browser are the two following things: 
* If you receive a HTTP 404 error message you are most likely connected to an App Platform, if not you need to check your DNS (and maybe also reverse proxy) settings.
* If the URL is modified and the used build number is added, an app has answered your request
** Example: <code>https://public.dns/your.domain/microsoft365/subscriptions</code> is modified to <code>https://public.dns/your.domain/microsoft365/1510411/subscriptions</code>
** If this is not the case, your URL is wrong. (Be aware: The URL depends on the settings of the web server path of your app instance)

'''Be aware:''' The URL-Recognition in the Application Platform is '''case sensitive'''.

== User Presence ==
===GUI Feedback===
The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. 
Sometimes it needs a little bit time until the states are changed. 
If the states remain, it is mandatory to enable logs on the app platform and check for more information. 
([[Howto13r3:Configure Connector for Microsoft365#Creating an app trace|Concept App Service Connector for Microsoft 365: Creating an app trace]])

====No connection to Master PBX====
Check the MasterPBX name. 
The field must only contain the name [pbx], '''not the full domain''' [pbx.domain.tld]. ([[Howto13r3:Configure Connector for Microsoft365#Synchronization from Teams to the PBX|Synchronization from Teams to the PBX - Master PBX field]])

====Presence subscription failed====
There are many reasons why the "Presence subscription failed" message could be displayed. 
We try to list the most common reasons:
* The permission for the registered app in the Azure portal are not correctly set ([[Howto13r3:Configure Connector for Microsoft365#Create an App for syncing Teams to PBX|Howto: Create an App for syncing Teams to PBX]])
* The Notification URL is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The App service is not reachable from the internet ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The certificate for the public endpoint (e.g. reverse proxy) is not valid, or not publicly signed ([[Reference13r3:Concept App Service Connector for Microsoft 365#SSL Certificate for notification URL|Concept App Service Connector for Microsoft 365: SSL Certificate for notification URL]])
* The user from PBX and the Azure Portal cannot be matched ([[Reference13r3:Concept App Service Connector for Microsoft 365#User Matching|Concept App Service Connector for Microsoft 365: User Matching]])
* The App Platforms clock time is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#App Platform clock time is wrong|Concept App Service Connector for Microsoft 365: App Platform clock time is wrong]])
* No user has a valid Connector for Microsoft 365 App license ([[Reference13r3:Concept App Service Connector for Microsoft 365#Requirements|Concept App Service Connector for Microsoft 365: Requirements]])

===Teams License for communication user===
If presence subscription does not work, please check if all of the configured communication users have a Microsoft Teams license applied and no multifactor authentication is in use for this particular user. 
Also please make sure you can login with the configured credentials. (If you have set a password as an Administration, the user needs to change the password during the first login, therefore the given password will be invalid for API access). 
''Sometimes, after changing setting or after the instance has restarted it can take up to 12 minutes until the presence subscription is working correctly. (Due to the subscription timeout)''

= Known Issues =
== Special Characters In Password ==
If you are using special characters (*, &, (, ), etc.) in you password you could possibly run into a problem with the authentication of the communication user. 
The authentication failed status is beeing displayed. 
For the moment the only workaround is to eliminate special characters from you password.

==App Platform clock time is wrong==
If the clock time at the App Platform is not correct, this will lead to an unstable behaviour of the Connector for Microsoft 365. 
Since the Connector for Microsoft 365 is using the Microsoft Graph APIs presence subscription function, it needs to provide in its request a precise time until the subscription validity will be expired. 
The app service is handling subscription and will automatically recreate a new subscription each time the previous one has expired. 

A wrong clock time will lead to false expiration times and thus
* the subscription will be expired earlier than expected (synchronisation is not working because there is no valid subscription)
* the subscription will be valid longer than expected (the app service is trying to create a new subscription because it is expecting the previous one to be expired - will lead to a 409 conflict error, because only one subscription can be valid at a time)

If you are not sure about the current time of the App Platform, you can login via SSH into the App Platform and execute the <code>date</code> command to check the current time. 
You will receive an output like:
Tue Mar 12 13:38:57 UTC 2024
Please be aware: The time is displayed in UTC, so please make sure to convert to your local time zone.

==Geoblocking==
Since there might be no reliable country assignment for Microsoft addresses, all Microsoft addresses must be enabled on the upstream firewall in the event of geoblocking in order to ensure functionality of the Office365 Connector. 
As an alternative you might be able to configure your firewall to bypass the geoblocking for the configured notification URL.

= Related Articles =
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Contact Search by Connector for Microsoft365]]

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

Howto16r1:Configure Contact Search by Connector for Microsoft365

2025-07-23T11:33:34Z

The:

{{FIXME|reason=This article is still work in progress}}

==Applies To==
This information applies to
Connector for Microsoft 365 from version 16r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App to search for contacts====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration|app_registration_connector_for_microsoft365.png/]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|authentication_connector_for_microsoft365_calendar.png/]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Contacts.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px|azure_select_api-permission.png/]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px|azure_select_api-permission_application.png/]]
[[Image:APIPermission Connector for Microsoft365 ContactSearch.png|thumb|none|600px|APIPermission Connector for Microsoft365 ContactSearch/]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px|microsoft365_install_app_1.png/]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px|microsoft365_install_app_2.png/]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px|microsoft365_create_instance_1.png/]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px|microsoft365_create_instance_2.png/]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 App'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Creating the API object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 API'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* The '''Name''' and '''SIP''' has to be '''<code>microsoft365-api</code>'''
[[Image:Microsoft_365_Settings_API.png|thumb|none|600px|microsoft_365_Settings_API.png/]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px|microsoft365_template_1.png/]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px|microsoft365_template_2.png/]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px|microsoft365_admin_app_1.png/]]

=====Configuration of the Contact Search=====
* For the contact search you select '''Configuration for Contact Search''' in the admin app
# '''ClientIDContactSearch''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Contact Search app
# '''TenantContactSearch''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Contact Search app
# '''ClientSecretContactSearch''' - Please insert the shared secret from the in preparation created Contact Search app
# '''NotificationURL''' - You need to specify the address Microsoft can send presence updates to
## You need to make sure that you define a URL where you can reach your App Platform from the public internet <code>public.dns</code>
## Next you need the domain you have configured in the app instance before (3.2.2) <code>your.domain</code>
## Next you need the name of the instance you have configured before (3.2.2) <code>microsoft365</code>
## The URL will always be terminated by <code>subscriptions</code>
##* <code>https://public.dns/your.domain/microsoft365/subscriptions</code>

==Related Articles==
[[Reference16r1:Concept App Service Connector for Microsoft 365|Concept App Service Connector for Microsoft 365]] 
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 

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

Howto16r1:Configure Contact Search by Connector for Microsoft365

2025-07-23T11:33:00Z

The: /* Synchronization from the Teams to PBX */

{{FIXME|reason=This article is still work in progress}}

'''WARNING:''' Der Artikel ist derzeit noch eine Kopie der Calendar Presence Integration und muss noch überarbeitet werden.

==Applies To==
This information applies to
Connector for Microsoft 365 from version 16r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App to search for contacts====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration|app_registration_connector_for_microsoft365.png/]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|authentication_connector_for_microsoft365_calendar.png/]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Contacts.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px|azure_select_api-permission.png/]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px|azure_select_api-permission_application.png/]]
[[Image:APIPermission Connector for Microsoft365 ContactSearch.png|thumb|none|600px|APIPermission Connector for Microsoft365 ContactSearch/]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px|microsoft365_install_app_1.png/]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px|microsoft365_install_app_2.png/]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px|microsoft365_create_instance_1.png/]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px|microsoft365_create_instance_2.png/]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 App'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Creating the API object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 API'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* The '''Name''' and '''SIP''' has to be '''<code>microsoft365-api</code>'''
[[Image:Microsoft_365_Settings_API.png|thumb|none|600px|microsoft_365_Settings_API.png/]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px|microsoft365_template_1.png/]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px|microsoft365_template_2.png/]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px|microsoft365_admin_app_1.png/]]

=====Configuration of the Contact Search=====
* For the contact search you select '''Configuration for Contact Search''' in the admin app
# '''ClientIDContactSearch''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Contact Search app
# '''TenantContactSearch''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Contact Search app
# '''ClientSecretContactSearch''' - Please insert the shared secret from the in preparation created Contact Search app
# '''NotificationURL''' - You need to specify the address Microsoft can send presence updates to
## You need to make sure that you define a URL where you can reach your App Platform from the public internet <code>public.dns</code>
## Next you need the domain you have configured in the app instance before (3.2.2) <code>your.domain</code>
## Next you need the name of the instance you have configured before (3.2.2) <code>microsoft365</code>
## The URL will always be terminated by <code>subscriptions</code>
##* <code>https://public.dns/your.domain/microsoft365/subscriptions</code>

==Related Articles==
[[Reference16r1:Concept App Service Connector for Microsoft 365|Concept App Service Connector for Microsoft 365]] 
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 

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

Howto16r1:Configure Contact Search by Connector for Microsoft365

2025-07-23T11:28:55Z

The:

{{FIXME|reason=This article is still work in progress}}

'''WARNING:''' Der Artikel ist derzeit noch eine Kopie der Calendar Presence Integration und muss noch überarbeitet werden.

==Applies To==
This information applies to
Connector for Microsoft 365 from version 16r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App to search for contacts====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration|app_registration_connector_for_microsoft365.png/]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|authentication_connector_for_microsoft365_calendar.png/]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Contacts.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px|azure_select_api-permission.png/]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px|azure_select_api-permission_application.png/]]
[[Image:APIPermission Connector for Microsoft365 ContactSearch.png|thumb|none|600px|APIPermission Connector for Microsoft365 ContactSearch/]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px|microsoft365_install_app_1.png/]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px|microsoft365_install_app_2.png/]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px|microsoft365_create_instance_1.png/]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px|microsoft365_create_instance_2.png/]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 App'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Creating the API object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 API'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* The '''Name''' and '''SIP''' has to be '''<code>microsoft365-api</code>'''
[[Image:Microsoft_365_Settings_API.png|thumb|none|600px|microsoft_365_Settings_API.png/]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px|microsoft365_template_1.png/]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px|microsoft365_template_2.png/]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px|microsoft365_admin_app_1.png/]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - You need to specify the address Microsoft can send presence updates to
## You need to make sure that you define a URL where you can reach your App Platform from the public internet <code>public.dns</code>
## Next you need the domain you have configured in the app instance before (3.2.2) <code>your.domain</code>
## Next you need the name of the instance you have configured before (3.2.2) <code>microsoft365</code>
## The URL will always be terminated by <code>subscriptions</code>
##* <code>https://public.dns/your.domain/microsoft365/subscriptions</code>

==Related Articles==
[[Reference16r1:Concept App Service Connector for Microsoft 365|Concept App Service Connector for Microsoft 365]] 
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 

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

File:Microsoft 365 Settings API.png

2025-07-23T11:14:24Z

The:

Howto16r1:Configure Contact Search by Connector for Microsoft365

2025-07-23T08:06:01Z

The:

{{FIXME|reason=This article is still work in progress}}

'''WARNING:''' Der Artikel ist derzeit noch eine Kopie der Calendar Presence Integration und muss noch überarbeitet werden.

==Applies To==
This information applies to
Connector for Microsoft 365 from version 16r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App to search for contacts====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration|app_registration_connector_for_microsoft365.png/]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|authentication_connector_for_microsoft365_calendar.png/]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Contacts.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px|azure_select_api-permission.png/]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px|azure_select_api-permission_application.png/]]
[[Image:APIPermission Connector for Microsoft365 ContactSearch.png|thumb|none|600px|APIPermission Connector for Microsoft365 ContactSearch/]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px|microsoft365_install_app_1.png/]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px|microsoft365_install_app_2.png/]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px|microsoft365_create_instance_1.png/]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px|microsoft365_create_instance_2.png/]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 App'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Creating the API object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
# Click '''Microsoft365 API'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* The '''Name''' and '''SIP''' has to be '''<code>microsoft365-api</code>'''
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px|microsoft365_template_1.png/]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px|microsoft365_template_2.png/]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px|microsoft365_admin_app_1.png/]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - You need to specify the address Microsoft can send presence updates to
## You need to make sure that you define a URL where you can reach your App Platform from the public internet <code>public.dns</code>
## Next you need the domain you have configured in the app instance before (3.2.2) <code>your.domain</code>
## Next you need the name of the instance you have configured before (3.2.2) <code>microsoft365</code>
## The URL will always be terminated by <code>subscriptions</code>
##* <code>https://public.dns/your.domain/microsoft365/subscriptions</code>

==Related Articles==
[[Reference16r1:Concept App Service Connector for Microsoft 365|Concept App Service Connector for Microsoft 365]] 
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 

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

Howto16r1:Configure Contact Search by Connector for Microsoft365

2025-07-23T07:05:17Z

The:

{{FIXME|reason=This article is still work in progress}}

'''WARNING:''' Der Artikel ist derzeit noch eine Kopie der Calendar Presence Integration und muss noch überarbeitet werden.

==Applies To==
This information applies to
Connector for Microsoft 365 from version 16r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App to search for contacts====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration|app_registration_connector_for_microsoft365.png/]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|authentication_connector_for_microsoft365_calendar.png/]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Contacts.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px|azure_select_api-permission.png/]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px|azure_select_api-permission_application.png/]]
[[Image:APIPermission Connector for Microsoft365 ContactSearch.png|thumb|none|600px|APIPermission Connector for Microsoft365 ContactSearch/]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px|microsoft365_install_app_1.png/]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px|microsoft365_install_app_2.png/]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px|microsoft365_create_instance_1.png/]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px|microsoft365_create_instance_2.png/]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px|microsoft365_template_1.png/]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px|microsoft365_template_2.png/]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px|microsoft365_admin_app_1.png/]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - You need to specify the address Microsoft can send presence updates to
## You need to make sure that you define a URL where you can reach your App Platform from the public internet <code>public.dns</code>
## Next you need the domain you have configured in the app instance before (3.2.2) <code>your.domain</code>
## Next you need the name of the instance you have configured before (3.2.2) <code>microsoft365</code>
## The URL will always be terminated by <code>subscriptions</code>
##* <code>https://public.dns/your.domain/microsoft365/subscriptions</code>

==Related Articles==
[[Reference16r1:Concept App Service Connector for Microsoft 365|Concept App Service Connector for Microsoft 365]] 
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 

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

File:APIPermission Connector for Microsoft365 ContactSearch.png

2025-07-23T07:00:47Z

The:

APIPermission Connector for Microsoft365 ContactSearch

Howto16r1:Configure Contact Search by Connector for Microsoft365

2025-07-23T06:59:41Z

The:

{{FIXME|reason=This article is still work in progress}}

'''WARNING:''' Der Artikel ist derzeit noch eine Kopie der Calendar Presence Integration und muss noch überarbeitet werden.

==Applies To==
This information applies to
Connector for Microsoft 365 from version 16r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App to search for contacts====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration|app_registration_connector_for_microsoft365.png/]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|authentication_connector_for_microsoft365_calendar.png/]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Contacts.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px|azure_select_api-permission.png/]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px|azure_select_api-permission_application.png/]]
[[Image:APIPermission_Connector_for_Microsoft365_Calendar.png|thumb|none|600px|apipermission_connector_for_microsoft365_calendar.png/]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px|microsoft365_install_app_1.png/]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px|microsoft365_install_app_2.png/]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px|microsoft365_create_instance_1.png/]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px|microsoft365_create_instance_2.png/]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px|microsoft365_pbx_manager_1.png/]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px|microsoft365_pbx_manager_2.png/]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px|microsoft365_template_1.png/]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px|microsoft365_template_2.png/]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px|microsoft365_admin_app_1.png/]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - You need to specify the address Microsoft can send presence updates to
## You need to make sure that you define a URL where you can reach your App Platform from the public internet <code>public.dns</code>
## Next you need the domain you have configured in the app instance before (3.2.2) <code>your.domain</code>
## Next you need the name of the instance you have configured before (3.2.2) <code>microsoft365</code>
## The URL will always be terminated by <code>subscriptions</code>
##* <code>https://public.dns/your.domain/microsoft365/subscriptions</code>

==Related Articles==
[[Reference16r1:Concept App Service Connector for Microsoft 365|Concept App Service Connector for Microsoft 365]] 
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 

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

Reference14r1:Concept App Service Voicemail

2025-06-30T16:40:57Z

The: /* Features */

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

The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to manage voicemail-messages (store, play, download and (auto-)delete) and configure the voicemail-box per user (change PIN-code, activate the voicemail-box, ...).

=Features=
* Database for voicemails
* Voicemail App on all myApps capable devices with visual Voicemail Notification
* Play, Download and Delete Voicemails
* Automatic Deletion of old voicemail-messages
* MWI on IP phones
* Email notification with a .wav attachment of the voicemail file
* Available languages German, Danish, Dutch, English, Finnish, French, Italian, Norwegian, Polish, Portuguese, from 15r1:Romanian, Swedish, Spanish, and Czech
* Custom XML voicemail scripts can be enabled
* Group Voicemail
* Automatically delete old voicemails (read/stored and unread) after x days
* Configure default pin / length of the PIN-codes
* Call own voice box
* Edit own pin (set back to default)
* Activate/deactivate call forwarding (CFU/CFB/CFNR)
* Number resolution with search provider (com.innovaphone.phonelookup) -> at the moment only usable with myApps and OutlookSearch

=Requirements=
* innovaphone PBX and App Platform from version 14r1 on.
* A UC- or Voicemail-license per user having a voicemail-box.
* Each voicemail-user needs to have a number assigned.
* Group Voicemail-boxes need a Voicemail license (PBX-VoicemailUser<version>) too (set automatically via the PBX Manager).

= Apps =

== Voicemail App (innovaphone-voicemail) ==
Main app to manage the voicemail-messages and personal settings.

=Details=

=== Group Voicemail ===
After configuration with the PBX Manager, it offers the same familiar features. Delete/Move affects all users of this app (MWI for all users is deleted). For its configuration, see the [[Howto:Group_Voicemail#Configuration_App_Platform| Group Voicemail article]].

== PBX Manager ==

=== Settings ===
Here you can configure all global Voicemail-settings:
* User and Password for all
* (From V14r1 on) Number of days for auto deletion of old voicemail-messages. If not set (default), there is no auto-deletion.

=== add voicemail ===
Input-field to create a new Voicemail-system. Besides the normal input-fields, you can:
* Activate the email notifications
* Activate a custom voicemail-script
* (From V14r1 Final on) Configure the default PIN. If not set (default), the 8765 is assumed.
: By configuring a default PIN, you can also change the PIN length:
: Using 876543 as default PIN not only changes the default PIN, but defines also the PIN-length used to 6.
* Used URL-parameters:
** '$app': indicates that it's an App
** $_defaultpin: defines the default PIN and the length of the PIN used by the system

=== add group voicemail ===
Input-field to create a new VoicemailGroup-box. Besides the normal input-fields (see 'add voicemail'), you can:
* Configure the list of users who want to receive an MWI. This is a comma-separated list of SIP names (no numbers allowed).
* Extra Used URL-parameters:
** '$m': comma-separated list of SIP names for MWI
** '$group': indicates that it's a Group Voicemail

== MWI on Phone ==
http://wiki.innovaphone.com/index.php?title=Howto:Group_Voicemail

=Troubleshooting=
==Voicemail XML Script==
The PBX should be able to load the <code>vm.xml</code> file from the Voicemail App Service. Therefore the credentials(''User'', ''Password'') under Tab ''Voicemail'', must match with the credentials configured in the ''AP voicemail_xx''-plugin of the PBX-Manager (Settings-section).
Changing these credentials can be done best via the ''AP voicemail_xx''-plugin of the PBX-Manager, as this plugin will adjust all the necessary things (Voicemail-object and database-record of the Voicemail-instance).

To trace, if PBX can read the Voicemail XML from App Platform, activate the Trace flag on the Voicemail Object, PBX Trace in the Maintenance/Tracing, and make a call to the Voicemail to see if the vm.xml is transmitted correctly.

==App WebSocket==
The PBX should maintain a permanent WebSocket connection to the Voicemail App Service. On the Voicemail Object, under Tab ''Voicemail'', check if ''Script URL'' show ''connected'' state. The Voicemail-objects password in the 'General'-tab is being used for this and checked against the Voicemail-instances password.

If not, check if the URL is correct and points to the service instance. The PBX should be able to resolve the DNS name and be able to connect to the Voicemail App Service on the App Platform.
If all OK: re-configure the password on the instance and voicemail-object.

=Known Problems=

= Related Articles =
* [[Howto:Group_Voicemail| Group Voicemail]]
* [[Howto:Getting_started_with_your_own_PBX_voicemail_script| Getting started with your own PBX voicemail script]]
* [[Howto:V13_Access_Voicemail_Files#Use_your_own_voicemail_files_with_the_voicemail-App_in_custom_mode| Use your own voicemail files with the voicemail APP in custom mode]]

Reference14r1:Concept App Service Voicemail

2025-06-30T16:39:38Z

The: /* Features */

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

The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to manage voicemail-messages (store, play, download and (auto-)delete) and configure the voicemail-box per user (change PIN-code, activate the voicemail-box, ...).

=Features=
* Database for voicemails
* Voicemail App on all myApps capable devices with visual Voicemail Notification
* Play, Download and Delete Voicemails
* Automatic Deletion of old voicemail-messages
* MWI on IP phones
* Email notification with a .wav attachment of the voicemail file
* Available languages German, Danish, Dutch, English, Finnish, French, Italian, Norwegian, Polish, Portuguese, Romanian, Swedish, Spanish, and Czech
* Custom XML voicemail scripts can be enabled
* Group Voicemail
* Automatically delete old voicemails (read/stored and unread) after x days
* Configure default pin / length of the PIN-codes
* Call own voice box
* Edit own pin (set back to default)
* Activate/deactivate call forwarding (CFU/CFB/CFNR)
* Number resolution with search provider (com.innovaphone.phonelookup) -> at the moment only usable with myApps and OutlookSearch

=Requirements=
* innovaphone PBX and App Platform from version 14r1 on.
* A UC- or Voicemail-license per user having a voicemail-box.
* Each voicemail-user needs to have a number assigned.
* Group Voicemail-boxes need a Voicemail license (PBX-VoicemailUser<version>) too (set automatically via the PBX Manager).

= Apps =

== Voicemail App (innovaphone-voicemail) ==
Main app to manage the voicemail-messages and personal settings.

=Details=

=== Group Voicemail ===
After configuration with the PBX Manager, it offers the same familiar features. Delete/Move affects all users of this app (MWI for all users is deleted). For its configuration, see the [[Howto:Group_Voicemail#Configuration_App_Platform| Group Voicemail article]].

== PBX Manager ==

=== Settings ===
Here you can configure all global Voicemail-settings:
* User and Password for all
* (From V14r1 on) Number of days for auto deletion of old voicemail-messages. If not set (default), there is no auto-deletion.

=== add voicemail ===
Input-field to create a new Voicemail-system. Besides the normal input-fields, you can:
* Activate the email notifications
* Activate a custom voicemail-script
* (From V14r1 Final on) Configure the default PIN. If not set (default), the 8765 is assumed.
: By configuring a default PIN, you can also change the PIN length:
: Using 876543 as default PIN not only changes the default PIN, but defines also the PIN-length used to 6.
* Used URL-parameters:
** '$app': indicates that it's an App
** $_defaultpin: defines the default PIN and the length of the PIN used by the system

=== add group voicemail ===
Input-field to create a new VoicemailGroup-box. Besides the normal input-fields (see 'add voicemail'), you can:
* Configure the list of users who want to receive an MWI. This is a comma-separated list of SIP names (no numbers allowed).
* Extra Used URL-parameters:
** '$m': comma-separated list of SIP names for MWI
** '$group': indicates that it's a Group Voicemail

== MWI on Phone ==
http://wiki.innovaphone.com/index.php?title=Howto:Group_Voicemail

=Troubleshooting=
==Voicemail XML Script==
The PBX should be able to load the <code>vm.xml</code> file from the Voicemail App Service. Therefore the credentials(''User'', ''Password'') under Tab ''Voicemail'', must match with the credentials configured in the ''AP voicemail_xx''-plugin of the PBX-Manager (Settings-section).
Changing these credentials can be done best via the ''AP voicemail_xx''-plugin of the PBX-Manager, as this plugin will adjust all the necessary things (Voicemail-object and database-record of the Voicemail-instance).

To trace, if PBX can read the Voicemail XML from App Platform, activate the Trace flag on the Voicemail Object, PBX Trace in the Maintenance/Tracing, and make a call to the Voicemail to see if the vm.xml is transmitted correctly.

==App WebSocket==
The PBX should maintain a permanent WebSocket connection to the Voicemail App Service. On the Voicemail Object, under Tab ''Voicemail'', check if ''Script URL'' show ''connected'' state. The Voicemail-objects password in the 'General'-tab is being used for this and checked against the Voicemail-instances password.

If not, check if the URL is correct and points to the service instance. The PBX should be able to resolve the DNS name and be able to connect to the Voicemail App Service on the App Platform.
If all OK: re-configure the password on the instance and voicemail-object.

=Known Problems=

= Related Articles =
* [[Howto:Group_Voicemail| Group Voicemail]]
* [[Howto:Getting_started_with_your_own_PBX_voicemail_script| Getting started with your own PBX voicemail script]]
* [[Howto:V13_Access_Voicemail_Files#Use_your_own_voicemail_files_with_the_voicemail-App_in_custom_mode| Use your own voicemail files with the voicemail APP in custom mode]]

Howto15r1:Configure Calendar Presence Sync by Connector for Microsoft365

2025-02-27T11:56:43Z

The: /* Configuration in Azure Portal */

==Applies To==
This information applies to
Connector for Microsoft 365 from version 15r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App for syncing Calendar Events from Teams to PBX====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Calendars.Read) and (User.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px]]
[[Image:APIPermission_Connector_for_Microsoft365_Calendar.png|thumb|none|600px]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - Please insert the Notification URL to your App Platform to get notifications
[[Category:Howto|{{PAGENAME}}]]

Howto15r1:Configure Calendar Presence Sync by Connector for Microsoft365

2025-02-27T11:55:30Z

The:

==Applies To==
This information applies to
Connector for Microsoft 365 from version 15r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App for syncing Calendar Events from Teams to PBX====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Calendar.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px]]
[[Image:APIPermission_Connector_for_Microsoft365_Calendar.png|thumb|none|600px]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - Please insert the Notification URL to your App Platform to get notifications
[[Category:Howto|{{PAGENAME}}]]

File:Authentication Connector for Microsoft365 Calendar.png

2025-02-27T11:53:54Z

The:

File:APIPermission Connector for Microsoft365 Calendar.png

2025-02-27T11:53:30Z

The:

Howto15r1:Configure Calendar Presence Sync by Connector for Microsoft365

2025-02-27T11:43:23Z

The: /* Configuration in Azure Portal */

==Applies To==
This information applies to
Connector for Microsoft 365 from version 15r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App for syncing Calendar Events from Teams to PBX====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px]]
[[Image:Azure_Select_Api-Permission_Application.png|thumb|none|600px]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - Please insert the Notification URL to your App Platform to get notifications
[[Category:Howto|{{PAGENAME}}]]

Howto15r1:Configure Calendar Presence Sync by Connector for Microsoft365

2025-02-27T11:42:30Z

The: /* Configuration in Azure Portal */

==Applies To==
This information applies to
Connector for Microsoft 365 from version 15r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App for syncing Calendar Events from Teams to PBX====
* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:Azure_Select_Api-Permission.png|thumb|none|600px]]

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - Please insert the Notification URL to your App Platform to get notifications
[[Category:Howto|{{PAGENAME}}]]

Howto15r1:Configure Calendar Presence Sync by Connector for Microsoft365

2025-02-27T11:38:35Z

The: /* Synchronization from the Teams to PBX */

==Applies To==
This information applies to
Connector for Microsoft 365 from version 15r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App for syncing Calendar Events from Teams to PBX====

* '''In the Azure Portal of Microsoft you have to add a new app registration'''
* '''In the picture you can see that we have 2 values after that which we can use for the configuration of the app'''

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app
# '''NotificationURLCalendar''' - Please insert the Notification URL to your App Platform to get notifications
[[Category:Howto|{{PAGENAME}}]]

Howto15r1:Configure Calendar Presence Sync by Connector for Microsoft365

2025-02-26T18:35:19Z

The: Created page with "==Applies To== This information applies to Connector for Microsoft 365 from version 15r1 ==More Information== This article outlines a configuration scheme for Connector for Microsoft365 functionality. In preparation, you first will need to configure one Application in your Azure Portal. After that, you will install the App in your Application Platform, and configure everything. ===System Requirements=== * Licenses '''innovaphone Connector for Microsoft 365'..."

==Applies To==
This information applies to
Connector for Microsoft 365 from version 15r1

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality. 
In preparation, you first will need to configure one Application in your Azure Portal. 
After that, you will install the App in your Application Platform, and configure everything.

===System Requirements===

* Licenses '''innovaphone Connector for Microsoft 365''' per user who wants to use the innovaphone myApps Connector for Microsoft 365.
* '''account in Azure Portal of Microsoft''' (for each of the technical communication users, no permission role needed) 
* Must have access from the internet to your App Platform
** This can be done by using a reverse proxy or other firewall
* The public endpoint '''must have ''' a '''valid, public signed certificate''' (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)

==Installation==

===Configuration in Azure Portal===

====Create an App for syncing Calendar Events from Teams to PBX====

* '''In the Azure Portal of Microsoft you have to add a new app registration'''
* '''In the picture you can see that we have 2 values after that which we can use for the configuration of the app'''

* '''Switch to Certificates & Secrets on the left'''
* '''You only have to configure a client secret and save the value for the configuration of the app'''

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

===Installing and configuring App Platform and PBX===
====Installing the connector app====
* First you need to install the connector app from the App Store:
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]
* Install the app by selecting
# All apps
# innovaphone AG
# innovaphone myApps Connector for Microsoft 365
# select the current Version
# Click install
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]
====Creating an instance for the connector app====
* For creating an Instance, in the AP Manager you need to
# select '''innovaphone myApps Connector for Microsoft 365'''
# click '''add'''
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]
* Insert the following information and save
# The technical Instance Name (we suggest microsoft365)
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)
# define a password for the communication between the PBX and the app instance
# define a password for the communication between the app instance and the database
''All other fields should be filled automatically''
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]

====Creating the PBX app object using the PBX Manager Plugin====
* Open the PBX Manager and
# select the '''AP <code>InstanceName</code>''' Tile
# Click '''Add an app'''
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]
* Specify the '''Name''' and the '''SIP''' (We suggest using '''<code>microsoft365</code>''' for this technical names)
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]

====Add the admin app to a user or a template====
To be able to configure the connector app, you need users to have access to the admin app. 
You can achieve this by adding the app to a user, or to a template. 
In this Howto - as an example - we will add the app to the <code>Config Admin</code> template. 
* In the PBX Manager
# select the <code>Templates</code> tile
# click on the <code>Config Admin</code> template
[[Image:Microsoft365_template_1.png|thumb|none|600px]]
* In the <code>Config Admin</code> template
# open Apps
# Check the <code>app name</code> checkbox
# Save the changes
[[Image:Microsoft365_template_2.png|thumb|none|600px]]

====Configure the connector with the admin app====
Now your admins (designated groups or configured user) should have access to the connector admin app. 
* A user with access to the app can now see a new tile in the '''All Apps''' area
* The name depends on the configured <code>app name</code> from the PBX Manager plugin
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]

=====Synchronization from the Teams to PBX=====
* For the calendar synchronization you select from Teams to PBX for '''Calendar Presence''' in the admin app
# '''ClientIDCalendar''' - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Calendar app
# '''TenantCalendar''' - Please insert the Directory ID (Tenant) from Azure Portal from the in preparation created Calendar app
# '''ClientSecretCalendar''' - Please insert the shared secret from the in preparation created Calendar app

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

Main Page

2025-02-13T15:51:57Z

The: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">
== Remote Support ==
As Remote Support Tool, we use our own product [https://www.innovaphone.com/en/all-apps/apps-to-work-with/remote-control-app.html Remote Control]. innovaphone only carries out scheduled remote maintenance via our ticket system by prior consultation.

You will receive a support link from our support team, which you can use to download and install the necessary client.

After you have opened the client, you can enter the support link and then join the session.

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have Google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales@innovaphone.com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==

[[User:The|The]] ([[User talk:The|talk]]) 16:51, 13 February 2025 (CET) [[Support:Firmware V14r2 product/14r2/firmware 1420458 (sr 7) available | Version 14r2 Service Release 7]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:The|The]] ([[User talk:The|talk]]) 16:51, 13 February 2025 (CET) [[Support:Firmware V14r1 product/14r1/firmware 1410589 (sr 12) available | Version 14r1 Service Release 12]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:The|The]] ([[User talk:The|talk]]) 16:51, 13 February 2025 (CET) [[Support:Firmware V13r3 product/13r3/firmware 138014 (sr 24) available | Version 13r3 Service Release 24]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:The|The]] ([[User talk:The|talk]]) 16:51, 13 February 2025 (CET) [[Support:Firmware V12r2 product/12r2/firmware 125887 (sr 73) available | Version 12r2 Service Release 73]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Msc|Msc]] ([[User talk:Msc|talk]]) 13:01, 7 February 2025 (CET)
[[Support:Firmware V15r1 product/15r1/firmware 1510335 (beta3) available| Version 15r1 Beta3]] is now available from the [https://store.innovaphone.com/beta/download.htm Beta Store].

[[User:Cam&action=edit&redlink=1|Cam]] 16:22, 18 September 2023 (CEST)
[[App Calculator beta1 available]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Sga|Sga]] ([[User talk:Sga|talk]]) 17:43, 15 September 2023 (CEST)
[[Support:Wireless Handset Firmware IP73 1011 (5.0.1) released| Wireless Handset Firmware IP73 1011 (5.0.1)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Gal&action=edit&redlink=1|Gal]] ([[User talk:Gal&action=edit&redlink=1|talk]]) 13:39, 31 July 2023 (CEST)
[[Support:Wireless Handset Firmware IP64 10314 (3.0.13)/IP65 10119 (3.0.13) released| Wireless Handset Firmware IP64 10314 (3.0.13)/IP65 10119 (3.0.13)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Cam&action=edit&redlink=1|Cam]] 12:03, 31 July 2023 (CEST)
[[App Working final available]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] 15:38, 6 February 2023 (CET)
[[Support:Wireless Handset Firmware IP62 3040621 (6.2.7) released| Wireless Handset Firmware IP62 3040621 (6.2.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM Software 3130113 (4.1.8) released| WinPDM Software 3130113 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10) released| Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Kwa&action=edit&redlink=1|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:IQM Build 8029100 available| IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Dde&action=edit&redlink=1|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux Application Platform 100271 (sr64) available| Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde&action=edit&redlink=1|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone Reporting 100271 (sr64) available| innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde&action=edit&redlink=1|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone Fax 100271 (sr64) available| innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde&action=edit&redlink=1|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone Exchange Calendar Connector 100271 (sr64) available| innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8) released| Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless Handset Firmware and Management Software product/9.00/wireless 100037 (hotfix19) available| Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde&action=edit&redlink=1|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App Platform build 90007 available| App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Kwa&action=edit&redlink=1|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording Build 121100 available| innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">

== New Articles ==

{{Special:Newestpages/all/20}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">
== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
</div>

Reference14r1:Concept App Service Voicemail

2024-01-02T13:35:49Z

The:

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

The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to manage voicemail-messages (store, play, download and (auto-)delete) and configure the voicemail-box per user (change PIN-code, activate the voicemail-box, ...).

=Features=
* Database for voicemails
* Voicemail App on all myApps capable devices with visual Voicemail Notification
* Play, Download and Delete Voicemails
* Automatic Deletion of old voicemail-messages
* MWI on IP phones
* Email notification with a .wav attachment of the voicemail file
* Available languages German, Danish, Dutch, English, Finnish, French, Italian, Norwegian, Polish, Portuguese, Swedish, Spanish, and Czech
* Custom XML voicemail scripts can be enabled
* Group Voicemail
* Automatically delete old voicemails (read/stored and unread) after x days
* Configure default pin / length of the PIN-codes
* Call own voice box
* Edit own pin (set back to default)
* Activate/deactivate call forwarding (CFU/CFB/CFNR)
* Number resolution with search provider (com.innovaphone.phonelookup) -> at the moment only usable with myApps and OutlookSearch

=Requirements=
* innovaphone PBX and App Platform from version 14r1 on.
* A UC- or Voicemail-license per user having a voicemail-box.
* Each voicemail-user needs to have a number assigned.
* Group Voicemail-boxes need a Voicemail license too (set automatically via the PBX Manager).

= Apps =

== Voicemail App (innovaphone-voicemail) ==
Main app to manage the voicemail-messages and personal settings.

=Details=

=== Group Voicemail ===
After configuration with the PBX Manager, it offers the same familiar features. Delete/Move affects all users of this app (MWI for all users is deleted). For its configuration, see the [[Howto:Group_Voicemail#Configuration_App_Platform| Group Voicemail article]].

== PBX Manager ==

=== Settings ===
Here you can configure all global Voicemail-settings:
* User and Password for all
* (From V14r1 on) Number of days for auto deletion of old voicemail-messages. If not set (default), there is no auto-deletion.

=== add voicemail ===
Input-field to create a new Voicemail-system. Besides the normal input-fields, you can:
* Activate the email notifications
* Activate a custom voicemail-script
* (From V14r1 Final on) Configure the default PIN. If not set (default), the 8765 is assumed.
: By configuring a default PIN, you can also change the PIN length:
: Using 876543 as default PIN not only changes the default PIN, but defines also the PIN-length used to 6.
* Used URL-parameters:
** '$app': indicates that it's an App
** $_defaultpin: defines the default PIN and the length of the PIN used by the system

=== add group voicemail ===
Input-field to create a new VoicemailGroup-box. Besides the normal input-fields (see 'add voicemail'), you can:
* Configure the list of users who want to receive an MWI. This is a comma-separated list of SIP names (no numbers allowed).
* Extra Used URL-parameters:
** '$m': comma-separated list of SIP names for MWI
** '$group': indicates that it's a Group Voicemail

== MWI on Phone ==
http://wiki.innovaphone.com/index.php?title=Howto:Group_Voicemail

=Troubleshooting=
==Voicemail XML Script==
The PBX should be able to load the <code>vm.xml</code> file from the Voicemail App Service. Therefore the credentials(''User'', ''Password'') under Tab ''Voicemail'', must match with the credentials configured in the ''AP voicemail_xx''-plugin of the PBX-Manager (Settings-section).
Changing these credentials can be done best via the ''AP voicemail_xx''-plugin of the PBX-Manager, as this plugin will adjust all the necessary things (Voicemail-object and database-record of the Voicemail-instance).

To trace, if PBX can read the Voicemail XML from App Platform, activate the Trace flag on the Voicemail Object, PBX Trace in the Maintenance/Tracing, and make a call to the Voicemail to see if the vm.xml is transmitted correctly.

==App WebSocket==
The PBX should maintain a permanent WebSocket connection to the Voicemail App Service. On the Voicemail Object, under Tab ''Voicemail'', check if ''Script URL'' show ''connected'' state. The Voicemail-objects password in the 'General'-tab is being used for this and checked against the Voicemail-instances password.

If not, check if the URL is correct and points to the service instance. The PBX should be able to resolve the DNS name and be able to connect to the Voicemail App Service on the App Platform.
If all OK: re-configure the password on the instance and voicemail-object.

=Known Problems=

= Related Articles =
* [[Howto:Group_Voicemail| Group Voicemail]]
* [[Howto:Getting_started_with_your_own_PBX_voicemail_script| Getting started with your own PBX voicemail script]]
* [[Howto:V13_Access_Voicemail_Files#Use_your_own_voicemail_files_with_the_voicemail-App_in_custom_mode| Use your own voicemail files with the voicemail APP in custom mode]]

Reference14r1:Concept App Service Voicemail

2023-12-01T11:55:59Z

The:

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

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

The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to manage voicemail-messages (store, play, download and (auto-)delete) and configure the voicemail-box per user (change PIN-code, activate the voicemail-box, ...).

=Features=
* Database for voicemails
* Voicemail App on all myApps capable devices with visual Voicemail Notification
* Play, Download and Delete Voicemails
* Automatic Deletion of old voicemail-messages
* MWI on IP phones
* Email notification with a .wav attachment of the voicemail file
* Available languages German, Danish, Dutch, English, Finnish, French, Italian, Norwegian, Polish, Portuguese, Swedish, Spanish, and Czech
* Custom XML voicemail scripts can be enabled
* Group Voicemail
* Automatically delete old voicemails after x days
* Configure default pin
* Call own voice box
* Edit own pin (set back to default)
* Activate/deactivate call forwarding (CFU/CFB/CFNR)
* Number resolution with search provider

=Requirements=
* innovaphone PBX and App Platform from version 14r1 on.
* A UC- or Voicemail-license per user having a voicemail-box.
* Group Voicemail-boxes need a Voicemail license too (set automatically via the PBX Manager).

= Apps =

== Voicemail App (innovaphone-voicemail) ==
Main app to manage the voicemail-messages and personal settings.

=Details=

=== Group Voicemail ===
After configuration with the PBX Manager, it offers the same familiar features. Delete/Move affects all users of this app (MWI for all users is deleted). For its configuration, see the [[Howto:Group_Voicemail#Configuration_App_Platform| Group Voicemail article]].

== PBX Manager ==

=== Settings ===
Here you can configure all global Voicemail-settings:
* User and Password for all
* (From V14r1 on) Number of days for auto deletion of old voicemail-messages. If not set (default), there is no auto-deletion.

=== add voicemail ===
Input-field to create a new Voicemail-system. Besides the normal input-fields, you can:
* Activate the email notifications
* Activate a custom voicemail-script
* (From V14r1 on) Configure the default PIN. If not set (default), 8765 is assumed.
* Used URL-parameters:
** '$app': indicates that it's an App

=== add group voicemail ===
Input-field to create a new VoicemailGroup-box. Besides the normal input-fields (see 'add voicemail'), you can:
* Configure the list of users who want to receive an MWI. This is a comma-separated list of SIP names (no numbers allowed).
* Extra Used URL-parameters:
** '$m': comma-separated list of SIP names for MWI
** '$group': indicates that it's a Group Voicemail

== MWI on Phone ==
http://wiki.innovaphone.com/index.php?title=Howto:Group_Voicemail

=Troubleshooting=
==Voicemail XML Script==
The PBX should be able to load the <code>vm.xml</code> file from the Voicemail App Service. Therefore the credentials(''User'', ''Password'') under Tab ''Voicemail'', must match with the credentials configured in the ''AP voicemail_xx''-plugin of the PBX-Manager (Settings-section).
Changing these credentials can be done best via the ''AP voicemail_xx''-plugin of the PBX-Manager, as this plugin will adjust all the necessary things (Voicemail-object and database-record of the Voicemail-instance).

To trace, if PBX can read the Voicemail XML from App Platform, activate the Trace flag on the Voicemail Object, PBX Trace in the Maintenance/Tracing, and make a call to the Voicemail to see if the vm.xml is transmitted correctly.

==App WebSocket==
The PBX should maintain a permanent WebSocket connection to the Voicemail App Service. On the Voicemail Object, under Tab ''Voicemail'', check if ''Script URL'' show ''connected'' state. The Voicemail-objects password in the 'General'-tab is being used for this and checked against the Voicemail-instances password.

If not, check if the URL is correct and points to the service instance. The PBX should be able to resolve the DNS name and be able to connect to the Voicemail App Service on the App Platform.
If all OK: re-configure the password on the instance and voicemail-object.

=Known Problems=

= Related Articles =
* [[Howto:Howto:Group_Voicemail| Group Voicemail]]
* [[Howto:Howto:Getting_started_with_your_own_PBX_voicemail_script| Getting started with your own PBX voicemail script]]
* [[Howto:V13_Access_Voicemail_Files#Use_your_own_voicemail_files_with_the_voicemail-App_in_custom_mode| Use your own voicemail files with the voicemail APP in custom mode]]

Reference14r1:Concept App Service Voicemail

2023-12-01T11:54:33Z

The: Created page with "{{FIXME|reason=This article is still work in progress}} Apps The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to manage voicemail-messages (store, play, download and (auto-)delete) and configure the voicemail-box per user (change PIN-code, activate the voicemail-box, ...). =Features= * Database for voicemails * Voicemail App on all myApps capable devices with visual Voicemail Notificatio..."

{{FIXME|reason=This article is still work in progress}}
[[Category:Concept|Apps]]

The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to manage voicemail-messages (store, play, download and (auto-)delete) and configure the voicemail-box per user (change PIN-code, activate the voicemail-box, ...).

=Features=
* Database for voicemails
* Voicemail App on all myApps capable devices with visual Voicemail Notification
* Play, Download and Delete Voicemails
* Automatic Deletion of old voicemail-messages
* MWI on IP phones
* Email notification with a .wav attachment of the voicemail file
* Available languages German, Danish, Dutch, English, Finnish, French, Italian, Norwegian, Polish, Portuguese, Swedish, Spanish, and Czech
* Custom XML voicemail scripts can be enabled
* Group Voicemail
* Automatically delete old voicemails after x days
* Configure default pin
* Call own voice box
* Edit own pin (set back to default)
* Activate/deactivate call forwarding (CFU/CFB/CFNR)
* Number resolution with search provider

=Requirements=
* innovaphone PBX and App Platform from version 14r1 on.
* A UC- or Voicemail-license per user having a voicemail-box.
* Group Voicemail-boxes need a Voicemail license too (set automatically via the PBX Manager).

= Apps =

== Voicemail App (innovaphone-voicemail) ==
Main app to manage the voicemail-messages and personal settings.

=Details=

=== Group Voicemail ===
After configuration with the PBX Manager, it offers the same familiar features. Delete/Move affects all users of this app (MWI for all users is deleted). For its configuration, see the [[Howto:Group_Voicemail#Configuration_App_Platform| Group Voicemail article]].

== PBX Manager ==

=== Settings ===
Here you can configure all global Voicemail-settings:
* User and Password for all
* (From V14r1 on) Number of days for auto deletion of old voicemail-messages. If not set (default), there is no auto-deletion.

=== add voicemail ===
Input-field to create a new Voicemail-system. Besides the normal input-fields, you can:
* Activate the email notifications
* Activate a custom voicemail-script
* (From V14r1 on) Configure the default PIN. If not set (default), 8765 is assumed.
* Used URL-parameters:
** '$app': indicates that it's an App

=== add group voicemail ===
Input-field to create a new VoicemailGroup-box. Besides the normal input-fields (see 'add voicemail'), you can:
* Configure the list of users who want to receive an MWI. This is a comma-separated list of SIP names (no numbers allowed).
* Extra Used URL-parameters:
** '$m': comma-separated list of SIP names for MWI
** '$group': indicates that it's a Group Voicemail

== MWI on Phone ==
http://wiki.innovaphone.com/index.php?title=Howto:Group_Voicemail

=Troubleshooting=
==Voicemail XML Script==
The PBX should be able to load the <code>vm.xml</code> file from the Voicemail App Service. Therefore the credentials(''User'', ''Password'') under Tab ''Voicemail'', must match with the credentials configured in the ''AP voicemail_xx''-plugin of the PBX-Manager (Settings-section).
Changing these credentials can be done best via the ''AP voicemail_xx''-plugin of the PBX-Manager, as this plugin will adjust all the necessary things (Voicemail-object and database-record of the Voicemail-instance).

To trace, if PBX can read the Voicemail XML from App Platform, activate the Trace flag on the Voicemail Object, PBX Trace in the Maintenance/Tracing, and make a call to the Voicemail to see if the vm.xml is transmitted correctly.

==App WebSocket==
The PBX should maintain a permanent WebSocket connection to the Voicemail App Service. On the Voicemail Object, under Tab ''Voicemail'', check if ''Script URL'' show ''connected'' state. The Voicemail-objects password in the 'General'-tab is being used for this and checked against the Voicemail-instances password.

If not, check if the URL is correct and points to the service instance. The PBX should be able to resolve the DNS name and be able to connect to the Voicemail App Service on the App Platform.
If all OK: re-configure the password on the instance and voicemail-object.

=Known Problems=

= Related Articles =
* [[Howto:Howto:Group_Voicemail| Group Voicemail]]
* [[Howto:Howto:Getting_started_with_your_own_PBX_voicemail_script| Getting started with your own PBX voicemail script]]
* [[Howto:V13_Access_Voicemail_Files#Use_your_own_voicemail_files_with_the_voicemail-App_in_custom_mode| Use your own voicemail files with the voicemail APP in custom mode]]

Main Page

2023-07-25T09:27:26Z

The: /* Latest News */

__NOTOC__

<div style="margin:0px; margin-right:10px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0em 1em;">

== Remote Support ==

[https://get.anydesk.com/PK8coqHH/AnyDesk.exe Download Anydesk]

== Searching ==
Searching in wiki works, but is sometimes cumbersome. However, you can have Google do the job for you. Try [https://www.google.de/search?q=site%3Ainnovaphone.com+xml+documentation <code>site:innovaphone.com your search terms</code>] to search the innovaphone sites for matches!

If you still don't find what you are looking for, [mailto:presales@innovaphone.com drop us a message]
</div>


<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em;">



== Latest News ==

[[User:The|The]] ([[User talk:The|talk]]) 11:27, 25 July 2023 (CEST)
[[Support:Firmware V13r3 product/13r3/firmware 137863 (sr 7) available | Version 13r3 Service Release 7]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:The|The]] ([[User talk:The|talk]]) 11:27, 25 July 2023 (CEST)
[[Support:Firmware V13r2 product/13r2/firmware 136429 (sr 25) available | Version 13r2 Service Release 25]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:The|The]] ([[User talk:The|talk]]) 11:27, 25 July 2023 (CEST)
[[Support:Firmware V12r2 product/12r2/firmware 125872 (sr 63) available | Version 12r2 Service Release 63]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] ([[User talk:Afi|talk]]) 11:11, 2 May 2023 (CEST)
[[Support:Wireless_Handset_Firmware_IP73_1008_(4.0.2)_released | Wireless Handset Firmware IP73 1008 (4.0.2)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Smayoral|sma]] 10:29, 27 April 2023 (CEST)
[[Support:Firmware V11r2 product/11r2/firmware 113809 (sr 66) available | Version 11r2 Service Release 66]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Cam|Cam]] 16:43, 25 April 2023 (CEST)
[[App Working Beta beta1 available]] is now available from the [http://store.innovaphone.com/release/download.htm download page].

[[User:Afi|Afi]] 15:38, 6 February 2023 (CET)
[[Support:Wireless_Handset_Firmware_IP62_3040621_(6.2.7)_released | Wireless Handset Firmware IP62 3040621 (6.2.7)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 13:13, 6 February 2023 (CET)
[[Support:WinPDM_Software_3130113_%284.1.8%29_released | WinPDM Software 3130113 (4.1.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Inno-mst|Inno-mst]] 11:22, 14 April 2022 (CEST)
[[Support:Operator9 90246 (hotfix24) available | Operator9 hotfix24]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 15:05, 11 February 2022 (CET)
[[Support:Wireless_Handset_Firmware_IP64_10313_(2.12.10)/IP65_10118_(2.12.10)_released | Wireless Handset Firmware IP64 10313 (2.12.10)/IP65 10118 (2.12.10)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 16 June 2021 (CEST)
[[Support:iQM_Build_8029100_available | IQM Build 8029100 Hotfix34]] is now available from the [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Afi|Afi]] 12:46, 16 June 2021 (CEST))
[[Support:TAPI Service Provider 8188 (hotfix21) available|TAPI Service Provider 8188 (hotfix21)]] is now available from [https://store.innovaphone.com/release/download.htm the Software download area].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Linux_Application_Platform_100271_(sr64)_available | Linux Application Platform V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Reporting_100271_(sr64)_available | innovaphone Reporting V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Fax_100271_(sr64)_available | innovaphone Fax V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Dde|Dde]] 13:17, 2 November 2020 (CET)
[[Support:Innovaphone_Exchange_Calendar_Connector_100271_(sr64)_available | innovaphone Exchange Calendar Connector V10 100271 sr64]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 18:21, 12 October 2020 (CEST)
[[Support:Wireless_Handset_Firmware_IP61_3022811_(4.7.8)/IP63_3022912_(4.7.8)_released | Wireless Handset Firmware IP61 3022811 (4.7.8)/IP63 3022912 (4.7.8)]] is now available from the [https://store.innovaphone.com/release/download.htm App store].

[[User:Afi|Afi]] 21:30, 27 March 2020 (CET)
[[Support:Wireless_Handset_Firmware_and_Management_Software_product/9.00/wireless_100037_%28hotfix19%29_available | Wireless Package hotfix 19]] is now available from the [http://download.innovaphone.com/ice/9.00#wireless V9 download area].

[[User:Dde|Dde]] 07:56, 9 March 2020 (CET)
[[Support:App_Platform_build_90007_available | App Platform build 90007]] is now available from the [http://store.innovaphone.com/release/download.htm App store].

[[User:kwa|kwa]] 14:00, 02 March 2020 (CET)
[[Support:Recording_Build_121100_available | innovaphone Recording SR29 build 121100]] is now available from the [http://download.innovaphone.com/ice/10.00/#recording V10 download area].

== New Articles ==

{{Special:Newestpages/all/20}}
</div>

<div style="margin:0px; margin-right:10px; margin-top:15px; border:1px solid #58C4C3; background-color:#F4F4F4; padding:0em 1em 0.5em 1em; font-size:1">
== More innovaphone Ressources ==
* [http://www.innovaphone.com Home Page]
* [http://download.innovaphone.com Download Site ]
* [http://my.innovaphone.com my.innovaphone ]
* [http://mantis.innovaphone.com/ Ticketing System ]
* [[Support:What are the Roadmap Documents? | Roadmaps ]]
</div>

Reference13r1:PBX/Objects/Voicemail

2023-01-05T13:25:39Z

The:

The Voicemail object is is a script interpreter. It targets IVR solutions and offers a set of call control mechanisms by means of an innovaphone-proprietary script language.
The Voicemail object is capable of retrieving script files either from a remote WebDAV server or from the local CompactFlash card. The interpretation starts for calls destined for the configured '''Number''' of a Voicemail object.

Innovaphone offers a few localized script files as a separate product - the ''innovaphone Voicemail''. Those scripts implement an answering machine, including MWI, for every PBX user. See [[Howto:How_to_Configure_the_innovaphone_Voicemail|How to Configure the innovaphone Voicemail]] for further configuration information of that product.

The following specifications are made in the Voicemail section:
* '''Script URL:''' The HTTP URL of the script file that is to be interpreted. URLs towards a script file on the local CompactFlash card contain a box-local IP address and must be entered alike http://127.0.0.1/DRIVE/CF0/vm/de/vm.xml. '''Hint:''' Copy the URL into the clipboard by means of ''Diagnostics/CF/Browse CF content''. Afterwards paste the URL into this edit field. '''Note:''' URLs with box-local IP addresses will be processed internally without using the HTTP transport mechanism. I.e. HTTP passwords must not be considered.
**Since V13 the Voicemail Object also can connect via Websocket instead of HTTP-GET. If the Object should use Websocket you have to add the param <code>$app=on</code> to the URL.
* '''Backup URL''':A fallback- or backup script URL can be configured here. If the read operation for the first ''Script URL'' does not succeed within 5s, then the ''Backup URL'' will be tried. The ''Backup URL'' provides a means for an emergency script. Such an emergency script could be used to play an out-of-order announcement.
* '''User:''' authentication (refer to voicemail instance name) for the HTTP request of the v13 voicemail files
* '''Password:''' authentication (refer to the voicemail instance password) for the HTTP request authentication of the v13 voicemail files
* '''Encryption Key:''' encrypt the voicemails in database on app platform - Instance must be restarted for the change to take effect - older voice messages are no longer readable after the change
* '''Trace:''' Enables some trace output. See also the chapter entitled "[[Reference:Administration/Diagnostics/Tracing|Administration/Diagnostics/Tracing]]".

'''Note:''' Pressing on ''OK,Apply,Delete'' causes a disconnection of all voicemail calls being currently active at the affected voicemail object.

== Related Articles ==
[[Howto:How_to_Configure_the_innovaphone_Voicemail|How to Configure the innovaphone Voicemail]] 
[[Howto:Getting started with your own PBX voicemail script]]

Reference13r1:PBX/Objects/Voicemail

2023-01-05T13:24:40Z

The:

The Voicemail object is is a script interpreter. It targets IVR solutions and offers a set of call control mechanisms by means of an innovaphone-proprietary script language.
The Voicemail object is capable of retrieving script files either from a remote WebDAV server or from the local CompactFlash card. The interpretation starts for calls destined for the configured '''Number''' of a Voicemail object.

Innovaphone offers a few localized script files as a separate product - the ''innovaphone Voicemail''. Those scripts implement an answering machine, including MWI, for every PBX user. See [[Howto:How_to_Configure_the_innovaphone_Voicemail|How to Configure the innovaphone Voicemail]] for further configuration information of that product.

The following specifications are made in the Voicemail section:
* '''Script URL:''' The HTTP URL of the script file that is to be interpreted. URLs towards a script file on the local CompactFlash card contain a box-local IP address and must be entered alike http://127.0.0.1/DRIVE/CF0/vm/de/vm.xml. '''Hint:''' Copy the URL into the clipboard by means of ''Diagnostics/CF/Browse CF content''. Afterwards paste the URL into this edit field. '''Note:''' URLs with box-local IP addresses will be processed internally without using the HTTP transport mechanism. I.e. HTTP passwords must not be considered.
**Since V13 the Voicemail Object also can connect via Websocket instead of HTTP-GET. If the Object should use Websocket you have to add the param <code>$app=on</code> to the URL.
* '''Backup URL''':A fallback- or backup script URL can be configured here. If the read operation for the first ''Script URL'' does not succeed within 5s, then the ''Backup URL'' will be tried. The ''Backup URL'' provides a means for an emergency script. Such an emergency script could be used to play an out-of-order announcement.
* '''User:''' authentication (refer to voicemail instance name) for the HTTP request of the v13 voicemail files
* '''Password:''' authentication (refer to the voicemail instance password) for the HTTP request authentication of the v13 voicemail files
* '''Encryption Key:''' encrypt the voicemails in database on app platform - Instance must be restarted for the change to take effect - older voicemails are not readable after change
* '''Trace:''' Enables some trace output. See also the chapter entitled "[[Reference:Administration/Diagnostics/Tracing|Administration/Diagnostics/Tracing]]".

'''Note:''' Pressing on ''OK,Apply,Delete'' causes a disconnection of all voicemail calls being currently active at the affected voicemail object.

== Related Articles ==
[[Howto:How_to_Configure_the_innovaphone_Voicemail|How to Configure the innovaphone Voicemail]] 
[[Howto:Getting started with your own PBX voicemail script]]

Howto13r3:Configure User Presence Sync by Connector for Microsoft365

2022-12-21T13:32:50Z

The:

==Applies To==
This information applies to
V13r3

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality.

===System Requirements===

* '''admin account in Azure Portal of Microsoft'''

==Configuration in Azure Portal==

* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to the authentication in the left'''-
* '''You only have to configure allow public client flow'''

[[Image:Authentication_Connector_for_Microsoft365.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure delegated permissions (User.Read.All and Presence.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:APIPermission_Connector_for_Microsoft365.png|thumb|none|600px]]

With these configurations you can configure the Connector for Microsoft365

* '''Client ID as shown in the picture'''
* '''Tenant ID as shown in the picture'''
* '''User'''
* '''Password'''

[[Image:Overview_Connector_for_Microsoft365.png|thumb|none|600px]]

==Configuration in Azure Portal Sync to Teams==

* '''In the Azure Portal of Microsoft you have to add a new app registration'''
* '''In the picture you can see that we have 2 values after that which we can use for the configuration of the app'''

[[Image:Overview_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to the authentication in the left'''-
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:APIPermission_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

==Configuration in PBX Objects==
For the sync direction from PBX to Teams the app itself needs visibility permissions (presence, on-the-phone) for the users who are should be synced to Teams. The configuration tag is visibility for each user object.

==Configuration in PBX Manager==
For configuring the app you need the following parameter:

* Name of the master PBX (Not full DNS name, really just only the PBX name)
* Client ID of the registrated app from the azure portal
* Tenant ID of your organization, also from the azure portal
* Credentials for your Microsoft Azure Portal login (User needs a Teams license)
* Notification uri "https://{your_domain}/{your_tenant}/microsoft365/subscriptions"
** After successful configuration and subscription the Microsoft services will connect to the specified ''notification uri'' for presence and line state updates.
** For this to work it is important to make sure that the specified ''notification uri'' is reachable from the Microsoft services, meaning from the public internet.
** You need to be able to reach your app platform with the specified uri from the public internet.

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

Howto13r3:Configure User Presence Sync by Connector for Microsoft365

2022-12-13T09:39:25Z

The:

{{FIXME|reason=This article is still worked on}}

==Applies To==
This information applies to
V13r3

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality.

===System Requirements===

* '''admin account in Azure Portal of Microsoft'''

==Configuration in Azure Portal==

* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to the authentication in the left'''-
* '''You only have to configure allow public client flow'''

[[Image:Authentication_Connector_for_Microsoft365.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure delegated permissions (User.Read.All and Presence.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:APIPermission_Connector_for_Microsoft365.png|thumb|none|600px]]

With these configurations you can configure the Connector for Microsoft365

* '''Client ID as shown in the picture'''
* '''Tenant ID as shown in the picture'''
* '''User'''
* '''Password'''

[[Image:Overview_Connector_for_Microsoft365.png|thumb|none|600px]]

==Configuration in Azure Portal Sync to Teams==

* '''In the Azure Portal of Microsoft you have to add a new app registration'''
* '''In the picture you can see that we have 2 values after that which we can use for the configuration of the app'''

[[Image:Overview_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to the authentication in the left'''-
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:APIPermission_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

==Configuration in PBX Objects==
For the sync direction from PBX to Teams the app itself needs visibility permissions (presence, on-the-phone) for the users who are should be synced to Teams. The configuration tag is visibility for each user object.

==Configuration in PBX Manager==
For configuring the app you need the following parameter:

* Name of the master PBX (Not full DNS name, really just only the PBX name)
* Client ID of the registrated app from the azure portal
* Tenant ID of your organization, also from the azure portal
* Credentials for your Microsoft Azure Portal login (User needs a Teams license)
* Notification uri "https://{your_domain}/{your_tenant}/microsoft365/subscriptions"
** After successful configuration and subscription the Microsoft services will connect to the specified ''notification uri'' for presence and line state updates.
** For this to work it is important to make sure that the specified ''notification uri'' is reachable from the Microsoft services, meaning from the public internet.
** You need to be able to reach your app platform with the specified uri from the public internet.

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

Reference13r3:Concept App Service Connector for Microsoft 365

2022-12-13T09:34:48Z

The: /* Technical Overview */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is still in progress}}

== Applies To ==

* innovaphone PBX from version 13r3

= Overview =

Connector for Microsoft 365 synchronises Microsoft Teams presences with the innovaphone PBX and back.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* App(Connector for Microsoft 365)
* Connector for Microsoft 365 License per user

== Concept ==

=== Configuration ===
Please have a look into our Howto guide for basic configuration aid:
[[How_to:_Configure_Connector_for_Microsoft365| Howto13r3:Configure Connector for Microsooft365]]

=== Technical Overview ===
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph Api.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made before every presence subscription.

The app synchronises the PBX presence with Teams through the Graph Api. The on-the-phone presence will be renewed every 5 minutes. The other presences have a lifetime of 1 day but the away has a lifetime of 7 days.
The lifetimes are described [https://learn.microsoft.com/en-us/graph/api/presence-setuserpreferredpresence?view=graph-rest-1.0&tabs=http here]

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

==== Mapping Table ====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

==== Master/Slave ====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

== Related Articles ==

=Known Limitation=

Only 650 users can be subscribed for the presence subscription.

== Communication User (UserSynctoPbx) ==
Users with MFA (multi-factor-authentication) are not supported as user for the Connector.

== Subscription Timeout ==

=== Situation ===
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

=== Impact ===
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=

The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. Sometimes it needs a little bit time until the states are changed. If the states remain, it is mandatory to enable logs on the app platform and check for more information.

If presence subscription does not work, please check if the configured user has a Microsoft Teams license.

Reference13r3:Concept App Service Connector for Microsoft 365

2022-12-13T09:33:22Z

The: /* Overview */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is still in progress}}

== Applies To ==

* innovaphone PBX from version 13r3

= Overview =

Connector for Microsoft 365 synchronises Microsoft Teams presences with the innovaphone PBX and back.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* App(Connector for Microsoft 365)
* Connector for Microsoft 365 License per user

== Concept ==

=== Configuration ===
Please have a look into our Howto guide for basic configuration aid:
[[How_to:_Configure_Connector_for_Microsoft365| Howto13r3:Configure Connector for Microsooft365]]

=== Technical Overview ===
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph Api.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made before every presence subscription.

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

==== Mapping Table ====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

==== Master/Slave ====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

== Related Articles ==

=Known Limitation=

Only 650 users can be subscribed for the presence subscription.

== Communication User (UserSynctoPbx) ==
Users with MFA (multi-factor-authentication) are not supported as user for the Connector.

== Subscription Timeout ==

=== Situation ===
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

=== Impact ===
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=

The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. Sometimes it needs a little bit time until the states are changed. If the states remain, it is mandatory to enable logs on the app platform and check for more information.

If presence subscription does not work, please check if the configured user has a Microsoft Teams license.

File:Overview Connector for Microsoft365 Sync to Teams.png

2022-12-13T09:30:28Z

The:

File:Authentication Connector for Microsoft365 Sync to Teams.png

2022-12-13T09:30:10Z

The:

File:APIPermission Connector for Microsoft365 Sync to Teams.png

2022-12-13T09:29:48Z

The:

Howto13r3:Configure User Presence Sync by Connector for Microsoft365

2022-12-13T09:29:20Z

The:

{{FIXME|reason=This article is still worked on}}

==Applies To==
This information applies to
V13r3

==More Information==

This article outlines a configuration scheme for Connector for Microsoft365 functionality.

===System Requirements===

* '''admin account in Azure Portal of Microsoft'''

==Configuration in Azure Portal==

* '''In the Azure Portal of Microsoft you have to add an app registration'''
* '''You only have to give a name for the app'''

[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]

* '''Switch to the authentication in the left'''-
* '''You only have to configure allow public client flow'''

[[Image:Authentication_Connector_for_Microsoft365.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure delegated permissions (User.Read.All and Presence.Read.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:APIPermission_Connector_for_Microsoft365.png|thumb|none|600px]]

With these configurations you can configure the Connector for Microsoft365

* '''Client ID as shown in the picture'''
* '''Tenant ID as shown in the picture'''
* '''User'''
* '''Password'''

[[Image:Overview_Connector_for_Microsoft365.png|thumb|none|600px]]

==Configuration in Azure Portal Sync to Teams==

* '''In the Azure Portal of Microsoft you have to add a new app registration'''
* '''In the picture you can see that we have 2 values after that which we can use for the configuration of the app'''

[[Image:Overview_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to the authentication in the left'''-
* '''You only have to configure a client secret and save the value for the configuration of the app'''

[[Image:Authentication_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

* '''Switch to api permissions on the left'''
* '''You have to configure application permission (Presence.ReadWrite.All) as shown in the picture'''
* '''Grant access to the api permissions, if not possible you have to ask an admin'''

[[Image:APIPermission_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]

==Configuration in PBX Manager==
For configuring the app you need the following parameter:

* Name of the master PBX (Not full DNS name, really just only the PBX name)
* Client ID of the registrated app from the azure portal
* Tenant ID of your organization, also from the azure portal
* Credentials for your Microsoft Azure Portal login (User needs a Teams license)
* Notification uri "https://{your_domain}/{your_tenant}/microsoft365/subscriptions"
** After successful configuration and subscription the Microsoft services will connect to the specified ''notification uri'' for presence and line state updates.
** For this to work it is important to make sure that the specified ''notification uri'' is reachable from the Microsoft services, meaning from the public internet.
** You need to be able to reach your app platform with the specified uri from the public internet.

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

Reference13r3:Concept App Service Connector for Microsoft 365

2022-12-12T06:38:02Z

The: /* Known Limitation */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is still in progress}}

== Applies To ==

* innovaphone PBX from version 13r3

= Overview =

Connector for Microsoft 365 synchronises Microsoft Teams presences with the innovaphone PBX (unidirectional).

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* App(Connector for Microsoft 365)
* Connector for Microsoft 365 License per user

== Concept ==

=== Configuration ===
Please have a look into our Howto guide for basic configuration aid:
[[How_to:_Configure_Connector_for_Microsoft365| Howto13r3:Configure Connector for Microsooft365]]

=== Technical Overview ===
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph Api.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made before every presence subscription.

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

==== Mapping Table ====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

==== Master/Slave ====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

== Related Articles ==

=Known Limitation=

Only 650 users can be subscribed for the presence subscription.

== Communication User (UserSynctoPbx) ==
Users with MFA (multi-factor-authentication) are not supported as user for the Connector.

== Subscription Timeout ==

=== Situation ===
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

=== Impact ===
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=

The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. Sometimes it needs a little bit time until the states are changed. If the states remain, it is mandatory to enable logs on the app platform and check for more information.

If presence subscription does not work, please check if the configured user has a Microsoft Teams license.

Reference13r3:Concept App Service Connector for Microsoft 365

2022-11-08T17:52:45Z

The:

File:Overview Connector for Microsoft365.png

2022-09-27T08:57:14Z

The:

Howto13r3:Configure User Presence Sync by Connector for Microsoft365

2022-09-27T08:56:53Z

The: /* More Information */

File:Authentication Connector for Microsoft365.png

2022-09-27T08:51:27Z

The:

File:App Registration Connector for Microsoft365.png

2022-09-27T08:51:10Z

The:

File:APIPermission Connector for Microsoft365.png

2022-09-27T08:50:56Z

The: