Howto:PresenceHeartbeat - MediaRunway - Partner App: Difference between revisions
Mediarunway (talk | contribs) |
Mediarunway (talk | contribs) m (→Functions) |
||
| Line 63: | Line 63: | ||
<!-- Preferred format is a short list of functions/buzz words offered by the product --> | <!-- Preferred format is a short list of functions/buzz words offered by the product --> | ||
The Presence Heartbeat App has three parts and needs an external trigger. | The Presence Heartbeat App has three parts and needs an external trigger. | ||
1. App service, which listen on a specific URL for HTTPS POST input | 1. App service, which listen on a specific URL for HTTPS POST input | ||
2. Admin app where you could configure how to react to a specific for example Windows State (Login/Logoff). In the Admin App you could also do the licensing | 2. Admin app where you could configure how to react to a specific for example Windows State (Login/Logoff). In the Admin App you could also do the licensing | ||
3. User app, where a user could manually click on a button to set his/her presence state to the configured one in the admin app. If the user didn´t need the app, you could decide to don´t deliver this app to the users | 3. User app, where a user could manually click on a button to set his/her presence state to the configured one in the admin app. If the user didn´t need the app, you could decide to don´t deliver this app to the users | ||
Because the myApps client has no knowledge of the actual MS Windows state of a user, an external trigger is needed. Here are two examples to do a trigger. | Because the myApps client has no knowledge of the actual MS Windows state of a user, an external trigger is needed. Here are two examples to do a trigger. | ||
1. With curl you could do a group policy in the MS Windows Active Directory which send the specific curl command to the listening app service url (1) for Login / Shutdown | 1. With curl you could do a group policy in the MS Windows Active Directory which send the specific curl command to the listening app service url (1) for Login / Shutdown | ||
2. To react to the MS Windows lock screen states you can get a mini .exe file from MediaRunway | 2. To react to the MS Windows lock screen states you can get a mini .exe file from MediaRunway | ||
Revision as of 14:05, 28 January 2023
Product Name
MediaRunway Presence Heartbeat
Certification Status
Category
Vendor
MediaRunway is an ITC enterprise that provides its customers with contemporary IT services in all areas - Your business, our solution.
Description
Presence Heartbeat could change the presence state depending on the MS Windows login status. So the app could automatically change the presence color and the presence text with a preset when the Windows screen lock is activated and unlocked again, as well as when Windows logs on and logs off/ shutdown. This works on the local Windows PC as well as in a Windows Terminal session. But also other triggers for example other Systems like macOS are possible.
MediaRunway - About this application
Functions
The Presence Heartbeat App has three parts and needs an external trigger. 1. App service, which listen on a specific URL for HTTPS POST input 2. Admin app where you could configure how to react to a specific for example Windows State (Login/Logoff). In the Admin App you could also do the licensing 3. User app, where a user could manually click on a button to set his/her presence state to the configured one in the admin app. If the user didn´t need the app, you could decide to don´t deliver this app to the users
Because the myApps client has no knowledge of the actual MS Windows state of a user, an external trigger is needed. Here are two examples to do a trigger. 1. With curl you could do a group policy in the MS Windows Active Directory which send the specific curl command to the listening app service url (1) for Login / Shutdown 2. To react to the MS Windows lock screen states you can get a mini .exe file from MediaRunway
Licensing
Licensing: One license per user with any number of devices for one instance of the app. No floating licensing, only the users who got a configured license have access. For licensing and test licensing please contact myApps-sales@mediarunway.com.
- Example: "Hello MediaRunway, we would like to purchase the Presence Heartbeat app. Here is our authentication key 1113335557, we have only one app instance. A one year license for 10 users would fullfill our needs. Please send us the license key as fast as possible. Best reagards"
Enter license key and activate user license: Simply enter the license key that you received from us and press "Confirm". After that, you should see the valid date of your license and the number of available user licenses. Next to the desired user name, activate or deactivate the user's license.
Prerequisites
My prerequisites text here ...
Versions
Compatible innovaphone firmware versions
- MediaRunway PresenceHeartbeat 1.0 (132xxx sr18, 133xxx final)
- innovaphone V13r2
- innovaphone V13r3
Application versions used for interop testing
- MediaRunway PresenceHeartbeat 1.0 (132xxx sr18, 133xxx final)
- innovaphone IPVA V13r2sr18
- innovaphone IPVA V13r3final
Configuration
My configuration text ...
Installation
After installing the App, adding the App instance and the App Object for the users, one can start using "Presence Favorites". The steps of the installation process are the same as described in this article "Callback - Install App from App Store" only with different names.
AP manager settings
File:Presenceheartbeat ap manager.png
PBX manager settings
Checkmark your users config while adding the object.
File:Presenceheartbeat pbx manager.png
Contact
| MediaRunway GmbH & Co. KG |
| Venloer Str. 8 |
| D-41569 Rommerskirchen |
| Tel: +49 2183 80628-0 |
| Mail: myApps-sales@mediarunway.com |
| Support: myApps-support@mediarunway.com |
| Website: MediaRunway.com |
For any questions please refer to our contact page.