innovaphone wiki - User contributions [en]

Reference16r1:Concept Buttons App

2026-03-18T14:32:57Z

Pst: /* Webhook Get Parameters */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" or "chat" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post (only for connect)
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigger.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button will trigger a call. Release the button will end the existing call.

===== Connect App=====
If the Connect App is assigend to the buttons AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish=====
''(only available in buttons-admin)''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|none|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:16:35Z

Pst: /* Working App */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigger.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button will trigger a call. Release the button will end the existing call.

===== Connect App=====
If the Connect App is assigend to the buttons AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish=====
''(only available in buttons-admin)''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|none|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:14:28Z

Pst: /* Phonecall - Toggle */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigger.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button will trigger a call. Release the button will end the existing call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish=====
''(only available in buttons-admin)''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|none|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:14:03Z

Pst: /* Phonecall - Toggle */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigger.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button will trigger a call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish=====
''(only available in buttons-admin)''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|none|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:13:41Z

Pst: /* Phonecall - Toggle */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigger.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish=====
''(only available in buttons-admin)''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|none|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:11:55Z

Pst: /* MQTT-Publish - (only in buttons-admin) */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish=====
''(only available in buttons-admin)''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|none|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:11:22Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

=====MQTT-Publish - (only in buttons-admin)=====

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|/Buttons-mqtt-publish.png|none|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:10:23Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

'''MQTT-Publish - (only in buttons-admin).'''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|/Buttons-mqtt-publish.png|none|/Buttons-mqtt-publish.png]]
== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:10:08Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

'''MQTT-Publish - (only in buttons-admin).'''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|thumb|/Buttons-mqtt-publish.png|/Buttons-mqtt-publish.png|none]] 

== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:09:32Z

Pst: /* Buttons App - Overview */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

'''MQTT-Publish - (only in buttons-admin).'''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|left|thumb|/Buttons-mqtt-publish.png]] 

== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:09:02Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

'''MQTT-Publish - (only in buttons-admin).'''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|left|thumb|/Buttons-mqtt-publish.png]] 

== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:08:29Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

'''MQTT-Publish - (only in buttons-admin).'''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|left|thumb|/Buttons-mqtt-publish.png]]

== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept Buttons App

2026-03-11T14:07:57Z

Pst: /* Output actions */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==
* innovaphone from version 16r1

== Overview ==
The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Phonecall - Toggle =====
Same as '''Phonecall''', but you can end the existing call with the same input trigge.

* Also it is possible to use this with ButtonDown and ButtonUp
* Press and hold a button we trigger the call. Release the button will end the existring call.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

'''MQTT-Publish - (only in buttons-admin).'''

In the Settings plugin it is now possible to connect the Buttons app to an existing MQTT broker. Once connected, you can simply add the TOPIC and CMD.

For example, if you want to toggle all "tasmota" devices connected to the MQTT broker, you can use it as follows.
[[File:Buttons-mqtt-publish.png|left|thumb]]

== Buttons App - Configuration ==
We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

File:Buttons-mqtt-publish.png

2026-03-11T14:05:22Z

Pst:

buttons-mqtt-publish

Reference15r1:Concept Buttons App

2026-03-11T13:03:39Z

Pst: /* Overview */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference16r1:Concept App Service Working

2026-03-09T12:58:47Z

Pst: /* Working */

The Working App is used to record working hours and manage absences. The Working User app can be used to start/stop time tracking and create vacation requests. There is also an admin app (Working Manager) which allows users to view working hours and approve vacation requests.

== Applies To ==

* innovaphone PBX from version 16r1

==Requirements==
* innovaphone PBX
* innovaphone Application Platform
* innovaphone myApps
* Firmware V16r1 beta1 or higher
* License “App(innovaphone-working)” (order no. 02-00050-010) per application-user

==Concept==

The innovaphone Service Working App is an application for digital time and absence management.

It consists of two parts:

* '''Working User App''' – used by employees to track their working hours (via clock-in/clock-out or manual entries) and to manage absence requests such as vacation or leave. Time entries and vacation requests must be confirmed (=submitted) before they appear in the admin app. Once confirmed, they can no longer be edited.
* '''Working Manager App''' – used by administrators or managers to view and manage working time and absence information for all users. It also allows approval or rejection of vacation requests and provides access to configuration settings.

==How it works==

The first time a user starts the Working App on myApps a new entry is created in the database for this user, based on the "Name" of this user, which will be used to store all the working hours entries, vacation days, sick days and national holidays. Entering the working hours is a two step task, because after defining the start/stop time it is also necessary to "confirm/submit" these hours as correct, after the confirmation is done the user can't change them anymore and they will be displayed on the admin app.

In the Working manager App the list of the users' names is based on the "Display Name", if no DN is set then the "Name" will be used. Once the users have opened the working app at least once, they will appear in the list of all users in the Working Manager App. The app adds a red mark when an user does not fulfill the working hours regulation.

== Features ==
=== Working ===
===== Working time tracking and costume work types =====

* Work time account: Overview of the current work time balance
* Add pre-defined labels to working times

===== Working time regulations =====

*Timeout to submit entries (days): max interval the user has to submit the working hours.
* Min break time after 6 hours: min break time if the user has worked more than 6 hours.
* Min break time after 9 hours: min break time if the user has worked more than 9 hours.
* Default working hours

===== Groups/Group rights =====

* Groups can be defined
* Only the managers of the groups can see the users on the group on the Working Manager App
* Working types only available for the users on the group can be configured
* Enable/disable restrictions to submit working hours for the users on the group
* Enable/Disable verification by manager before submission to Human Resources

===== Archiving working times of deleted employees =====

===== User replication: New users appear once assigned the Working User App =====
=== Absences ===

==== vacation management ====

* Creating and approving vacation requests
* Define vacation rules in general and user-specific terms

==== holidays and sick days ====

* Entering sick days and public holidays

== Apps ==
=== innovaphone-working ===
[[Image: Innovaphone-working.png|innovaphone-working.png/|/Innovaphone-working.png]]
This is an app (Working User), where the user can enter the working hours, holidays, sick and vacation days. This can be done by clicking on the start/stop button. The user have also a calendar view to add, edit or delete working hours.

=== innovaphone-working-api ===
[[Image: Innovaphone-working-api.png|innovaphone-working-api.png/|/Innovaphone-working-api.png]]
This is a hidden app (Working Api), where the myApps session is been monitorized when the autostart/stop of the working times is enabled on the Working User App.

Parameters:
;Websocket: to set a websocket connection.
;Hidden: to configure the app as hidden.
;Admin: to get the app object name where to send the notifications.
;PbxApi: to send the notifications.

=== innovaphone-working-client-api ===
[[Image: Innovaphone-working-api.png|innovaphone-working-api.png/|/Innovaphone-working-api.png]]
This is an app needed to provide the Working Service API, so that other apps can start/stop working times. The Working Service API app is also a hidden app. The Settings plugin also sets the hidden function. This app should be granted to apps that use it, not to users.

Parameters:
;Websocket: to set a websocket connection.

=== innovaphone-working-manager ===
[[Image: Innovaphone-working-admin.png‎|innovaphone-working-admin.png/|/Innovaphone-working-admin.png]]
This is an admin app (Working Manager), where an administrator (i.e. Human Resources) can see the users' working hours. Several settings like the working hours per day can be configured per user and they are set to 8 hours from monday to friday by default.

Now "hr" must be entered as Mode on the app object on the PBX. With that now there are 2 workingmanager apps for the user-objects avaiable: 
workingmanager and 
workingmanager~hr. 
The administrator needs both.
* workingmanager: the managers on the group can only see the users on the group (no hamburger menu avaiable)
* workingmanager~hr: all the users can be seen there and all the configurations are available

Also some config items can be edited on the hamburguer menu:

* General settings

* Default working hours: workings hours defined per day when a user opens the app for the first time, which can be modified per user on the Admin App (Working Manager).

* Rights
** Config groups 

=== Public Holidays API ===
[[Image: Innovaphone-working-api.png|innovaphone-working-api.png/|/Innovaphone-working-api.png]]
This API provides public holiday data for other apps. It allows them to check whether a specific date is a public holiday in a given country or region.

Parameters:
;Websocket: to set a websocket connection.
;Hidden: to configure the app as hidden.

== Import and export of existing tracked time and absences with the help of CSV ==
=== CSV export ===
The users' data can be exported and imported on CSV format. There are some fixed fields that are available for the import and the export. There are also some other fields that are only displayed on the export file just as extra information, which are marked with (*).

'''Users'''

The fields that come with the CSV are the SIP, GUID, domain, display name, the defined working hours per day and the personal number.
&sip;&guid;&domain;&dn;&monday;&tuesday;&wednesday;&thursday;&friday;&saturday;&sunday;&p_number 
atlantis;null;innovaphone.com;Atlantis;8;8;8;8;8;0;0;0

'''Absences'''

The fields that come with the CSV are the SIP, the start timestamp, the working hours, label ('''vacation''' for a vacation day, '''hvacation''' for a 1/2 day vacation, '''holiday''' for national holidays, '''sick''' for sick leave), confirmed (if the absence has been submitted), date, and the personal number.
&sip;&start;&duration;&label;&confirmed;&date;&p_number 
atlantis;1712181600000;8;hvacation;true;2024-04-04;0

'''Times'''

The fields that come with the CSV are the SIP, the start timestamp, the stop timestamp, confirmed (if has been submitted), the display name, the personal number, the start date, the start time, the stop date, the stop time, the amount of hours and the label (if a type has been selected).
&sip;&start;&stop;&confirmed;&dn;&p_number;&start_date;&start_time;&stop_date;&stop_time;&hours;&label 
atlantis;1712651520199;1712651700199;true;Atlantis;0;2024-04-09;10:32:00.199+00:00;2024-04-09;10:35:00.199+00:00;0,1;

=== CSV import ===
'''Users'''

The fields that should come with the CSV are the SIP, GUID, domain, display name, the defined working hours per day and the personal number.
&sip;&guid;&domain;&dn;&monday;&tuesday;&wednesday;&thursday;&friday;&saturday;&sunday;&p_number 
atlantis;null;innovaphone.com;Atlantis;8;8;8;8;8;0;0;0

'''Absences'''

The fields that should come with the CSV are the SIP, the start timestamp, duration (the working hours), label ('''vacation''' for a vacation day, '''hvacation''' for a 1/2 day vacation, '''holiday''' for national holidays, '''sick''' for sick leave), confirmed (if the absence has been submitted) and date (if present timestamp will be ignored). The date must always have the english format, i.e. MM-DD-YYYY.
&sip;&start;&duration;&label;&confirmed;&date 
atlantis;1712181600000;8;hvacation;true;2024-04-04

'''Times'''

The fields that should come with the CSV are the SIP, the start timestamp, the stop timestamp, confirmed (if has been submitted).
&sip;&start;&stop;&confirmed 
atlantis;1712651520199;1712651700199;true

Parameters:
;workingmanager: the name of the working admin app.

== Settings Plugins ==

=== Working ===

With the Working plugin App Objects can be created, edited and deleted on the PBX.

=== Settings Plugin - Configuration ===
General settings for the app can be configured within this area.

* '''PBX Name:''' This refers to the name of the MasterPBX in the respective system environment. This setting must be set correctly for user replication and other functions to work.
* '''Connect Name:''' The H323 name of the Connect app must be configured here. This is usually “connect,” but it depends on the individual setup of the system.
* '''Connect Groups:''' Here you can define a comma-separated list of PBX group names to be used for Connect integration in private posts. This is necessary in order to be able to include separate PBX groups, such as the human resources department, in private posts in addition to department heads.
* '''Language for connectsposts''': Integration with the Connect app and thus the creation of “posts” is carried out from a central location. The language can be set for these posts. Currently, there is ‘de’ for German and “en” for English.

==Configuration==
* Install the Working App with the new AP app installer available in the Settings . ''Hint : after the installation done, close and open again the Settings to refresh the list of the installed app (the coloured plug-in)''
* Create a new PBX Object for the Working User, Working Manager and Working API Apps with the Settings Plugin.
* Assign the Working User (to normal users) and Working Manager App (to administration for example Human Resources) by selecting the config template that should include the App.
* Assign the Working API to all the users, so users can use the auto start/stop and push notifications.
* Assign license "App(innovaphone-working)" via config template or directly to all users using the APP.
* Open the object workingmanager / App / Modes: (insert here:) hr.
* Open the object Config Admin / Apps / workingmanager~hr (select).
* Set configuration settings on the "burger" menu of the Working Manager App (i.e. Reports Interval in weeks, groups and types configuration...).

==Troubleshooting==
Trace flags for App on App Platform:
*App
*App Database
*App Websocket

Trace flags for myApps Client:
*Browser Console

==Known issues==

==Related Articles==
* [https://sdk.innovaphone.com/14r2/web1/com.innovaphone.working/com.innovaphone.working.htm SDK Documentation - Working API]
* [https://sdk.innovaphone.com/14r2/doc/service/Working.htm SDK Documentation - Working Client API]

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2026-02-18T08:35:49Z

Pst: Added sample configuration files for Datafox Studio

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==

{{Template:Compat_Status_referral_terminals|manufacturername=Datafox GmbH|certificationdate=in September 2025}}

==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the [[Reference15r1:Concept App Service Working|innovaphone App Service Working]] via the the [[Reference15r1:Concept Buttons App|innovaphone Buttons App]].

The configured identities (RFID, PIN, Fingerprint) can be assigned to a PBX user via the Application buttons.

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==
This only applies to the connection to Innovaphone, not the complete configuration of a Datafox terminal.

The configuration of terminals is carried out via Datafox Studio. This is available from https://www.datafox.de/unternehmen/downloads/software

=== Settings for Buttons App ===
* The innovaphone buttons app has a reachable webpath for datafox terminals
* The app receives all communication from the terminal via http-get
** The Buttons app has opened a web path ‘datafox’ below the app path for this purpose.
*** For example => <nowiki>http://ap.domain.de/domain.de/buttons/</nowiki>'''datafox'''
**** ap.domain.de => FQDN of the AppPlattform
**** /domain.de/buttons/ => the webpath for the buttons app
**** datafox => the subpath as destination for GET-Variables
* The needed settings for the terminal can be edited via Datafox Studio.

=== Settings in Datafox Studio ===

* You have to setup the Configuration for Devicecommunication (in view on the example above)
** com.http = 1
** com.http_mode[0].host = '''''ap.domain.de'''''
** com.http_mode[0].port = 80
** com.http_mode[0].send = GET '''''/domain.de/buttons/datafox'''''?
* There are still some fieldnames, you have to choose in the input chain of your setup. All other configuration depends on your setup.
** Create a Dataset Table "working".
*** df_name
*** df_serial
*** action
*** mac
*** Date or Datum
*** maybe other fields you need
** Assign the Table to your controlpanel
*** for the operating menu you have to assingn "working" as dataset table
*** for your Chip/RFID assign "mac" as datafield
*** for come or leave assign constant values
**** come => assign 1 to field action
**** leave => assign 2 to field action

===== Example Configuration Files =====
[[File:Datafox - Example.zip|left|thumb]]

=== Assign IDs to Users ===

* After you have done the steps before, the Datafax Terminal will send your data to the Buttons in OnlineMode
* You can assign actions to your ID (RFID Token)
** working-start
** working-stop
** ...also all other actions, which can be triggered via buttons App are available.

[[File:Datafox Studio 001.png|thumb|/Datafox_Studio_001.png|none|/Datafox_Studio_001.png]]

==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

File:Datafox - Example.zip

2026-02-18T08:33:04Z

Pst: Here you can find some default configuration and display design for usage with innovpahone Buttons and innovaphone Working App

== Summary ==
Here you can find some default configuration and display design for usage with innovpahone Buttons and innovaphone Working App

File:Innovaphone Working - Datafox Example.zip

2026-02-18T08:30:56Z

Pst:

Here you can find an example of display design and some default configuration with innovaphone buttons and working app

Reference16r1:Configure OpenLDAP Directory Replication

2025-10-29T10:17:51Z

Pst: /* Applies To */

==Applies To==

* This information applies to V16r1 ''(since Beta2)''
* Tested with OpenLDAP slapd-Version: 2.4.57

=More Information=
With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well.

Unlike Active Directory, OpenLDAP does not have an <code>objectGuid</code> attribute; therefore, we use the <code>entryUUID</code> attribute as the source for our internal guid.

All other attribute mappings can be applied in the same way as they are for Active Directory replication.

See also: https://wiki.innovaphone.com/index.php?title=Reference15r1:Configure_Active_Directory_Replication#Attribute_Mapping

Reference16r1:Configure OpenLDAP Directory Replication

2025-10-29T10:16:35Z

Pst: /* Applies To */

==Applies To==

* This information applies to V16r1 Beta2.
* Tested with OpenLDAP slapd-Version: 2.4.57.

=More Information=
With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well.

Unlike Active Directory, OpenLDAP does not have an <code>objectGuid</code> attribute; therefore, we use the <code>entryUUID</code> attribute as the source for our internal guid.

All other attribute mappings can be applied in the same way as they are for Active Directory replication.

See also: https://wiki.innovaphone.com/index.php?title=Reference15r1:Configure_Active_Directory_Replication#Attribute_Mapping

Reference16r1:Configure OpenLDAP Directory Replication

2025-10-29T10:13:55Z

Pst: Created page with "==Applies To== This information applies to V16r1 Beta2. Tested with OpenLDAP slapd-Version: 2.4.57. =More Information= With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well. Unlike Active Directory, OpenLDAP does not have an <code>objectGuid</code> attribute; therefore, we use the <code>entryUUID</code> attribute as the source for our internal guid. All other attribute mappings..."

==Applies To==
This information applies to V16r1 Beta2. 
Tested with OpenLDAP slapd-Version: 2.4.57.

=More Information=
With version 16, we have enhanced the LDAP replication functionality for Active Directory, allowing OpenLDAP to be used as a source as well.

Unlike Active Directory, OpenLDAP does not have an <code>objectGuid</code> attribute; therefore, we use the <code>entryUUID</code> attribute as the source for our internal guid.

All other attribute mappings can be applied in the same way as they are for Active Directory replication.

See also: https://wiki.innovaphone.com/index.php?title=Reference15r1:Configure_Active_Directory_Replication#Attribute_Mapping

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2025-09-11T09:38:14Z

Pst: /* Assign IDs to Users */

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==



==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the Working App via the the Buttons App.

The configured identities (RFID, PIN, Fingerprint) can be assigned to a PBX user via the Application buttons..

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==
This only applies to the connection to Innovaphone, not the complete configuration of a Datafox terminal.

The configuration of terminals is carried out via Datafox Studio. This is available from https://www.datafox.de/unternehmen/downloads/software

=== Settings for Buttons App ===
* The innovaphone buttons app has a reachable webpath for datafox terminals
* The app receives all communication from the terminal via http-get
** The Buttons app has opened a web path ‘datafox’ below the app path for this purpose.
*** For example => <nowiki>http://ap.domain.de/domain.de/buttons/</nowiki>'''datafox'''
**** ap.domain.de => FQDN of the AppPlattform
**** /domain.de/buttons/ => the webpath for the buttons app
**** datafox => the subpath as destination for GET-Variables
* The needed settings for the terminal can be edited via Datafox Studio.

=== Settings in Datafox Studio ===

* You have to setup the Configuration for Devicecommunication (in view on the example above)
** com.http = 1
** com.http_mode[0].host = '''''ap.domain.de'''''
** com.http_mode[0].port = 80
** com.http_mode[0].send = GET '''''/domain.de/buttons/datafox'''''?
* There are still some fieldnames, you have to choose in the input chain of your setup. All other configuration depends on your setup.
** Create a Dataset Table "working".
*** df_name
*** df_serial
*** action
*** mac
*** Date or Datum
*** maybe other fields you need
** Assign the Table to your controlpanel
*** for the operating menu you have to assingn "working" as dataset table
*** for your Chip/RFID assign "mac" as datafield
*** for come or leave assign constant values
**** come => assign 1 to field action
**** leave => assign 2 to field action

=== Assign IDs to Users ===

* After you have done the steps before, the Datafax Terminal will send your data to the Buttons in OnlineMode
* You can assign actions to your ID (RFID Token)
** working-start
** working-stop
** ...also all other actions, which can be triggered via buttons App are available.

[[File:Datafox Studio 001.png|thumb|/Datafox_Studio_001.png|/Datafox_Studio_001.png|none]]

==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2025-09-09T07:46:29Z

Pst:

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==



==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the Working App via the the Buttons App.

The configured identities (RFID, PIN, Fingerprint) can be assigned to a PBX user via the Application buttons..

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==
This only applies to the connection to Innovaphone, not the complete configuration of a Datafox terminal.

The configuration of terminals is carried out via Datafox Studio. This is available from https://www.datafox.de/unternehmen/downloads/software

=== Settings for Buttons App ===
* The innovaphone buttons app has a reachable webpath for datafox terminals
* The app receives all communication from the terminal via http-get
** The Buttons app has opened a web path ‘datafox’ below the app path for this purpose.
*** For example => <nowiki>http://ap.domain.de/domain.de/buttons/</nowiki>'''datafox'''
**** ap.domain.de => FQDN of the AppPlattform
**** /domain.de/buttons/ => the webpath for the buttons app
**** datafox => the subpath as destination for GET-Variables
* The needed settings for the terminal can be edited via Datafox Studio.

=== Settings in Datafox Studio ===

* You have to setup the Configuration for Devicecommunication (in view on the example above)
** com.http = 1
** com.http_mode[0].host = '''''ap.domain.de'''''
** com.http_mode[0].port = 80
** com.http_mode[0].send = GET '''''/domain.de/buttons/datafox'''''?
* There are still some fieldnames, you have to choose in the input chain of your setup. All other configuration depends on your setup.
** Create a Dataset Table "working".
*** df_name
*** df_serial
*** action
*** mac
*** Date or Datum
*** maybe other fields you need
** Assign the Table to your controlpanel
*** for the operating menu you have to assingn "working" as dataset table
*** for your Chip/RFID assign "mac" as datafield
*** for come or leave assign constant values
**** come => assign 1 to field action
**** leave => assign 2 to field action

=== Assign IDs to Users ===

* After you have done the steps before, the Datafax Terminal will send your data to the Buttons in OnlineMode
* You can assign actions to your ID (RFID Token)
** working-start
** working-stop
** ...also all other actions, which can be triggered via buttons App are available.

[[File:Datafox Studio 001.png|thumb|/Datafox_Studio_001.png]]

==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:10:31Z

Pst: /* Userobject */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|thumb|508x508px|/Medai-vmuser_01.png|none|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|thumb|1308x1308px|/Medai-vmuser_02.png|none|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:08:36Z

Pst: /* Userobject */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|thumb|508x508px|/Medai-vmuser_01.png|/Medai-vmuser_01.png|none]]

[[File:Medai-vmuser 02.png|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png|none]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:07:44Z

Pst: Undo revision 77706 by Pst (talk)

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|508x508px|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:06:16Z

Pst: /* Contact us: */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|508x508px|/Medai-vmuser_01.png|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:05:51Z

Pst: /* Configuration */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|508x508px|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:05:14Z

Pst: /* Configuration */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|/Medai-vmuser_01.png|508x508px]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

 
 
=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:04:49Z

Pst: /* Configuration */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|/Medai-vmuser_01.png|508x508px]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

 
=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:03:57Z

Pst: /* Configuration */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|/Medai-vmuser_01.png|508x508px]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:03:13Z

Pst: /* Configuration */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:01:36Z

Pst: /* Userobject */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:01:15Z

Pst: /* Userobject */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb|/Medai-vmuser_01.png]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px|/Medai-vmuser_02.png]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

Howto:VisualMailbox - mAIsolutions - 3rd Party Product

2025-09-08T06:01:05Z

Pst: /* Compatible innovaphone firmware versions */

{{FIXME|reason=Work in progress, still incomplete}}

[[Image:mAIsolutions.png|200px|right|/MAIsolutions.png|/MAIsolutions.png]]

==Product Name==


[[Image:mAIVisualMailbox.png|100px]]

mAIsolutions [https://www.dm2s.de/maisolutions/ VisualMailbox]

==Certification Status==


==Category==

[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty CTI and integrations|{{PAGENAME}}]]
{{Category:3rdParty CTI and integrations}}

==Vendor==



[[Image:mAIsolutions.png|150px|/MAIsolutions.png|/MAIsolutions.png]]



DM² AI Solutions is a technology provider based in Walldorf, Germany, 
offering a Conversational AI & Workflow Suite designed to help organizations simplify processes, optimize communication flows, and reduce workload efficiently.


[https://www.dm2s.de/ About us]

==Description==






mAIsolutions Visual Mailbox is a smart voice assistant.

It ensures availability by automatically answering incoming calls, asking predefined questions, and documenting all inquiries in a structured way.

Callers receive a structured and professional experience while teams save time and stay focused on their core tasks.

This method helps your team to stay focused and maximizes operational efficiency.

==Functions==




* Secure Web Portal
* Set-up of VisualMailbox consists of the conversation and questions

Example process:
* Greeting: e.g., "Welcome to your practice – how can we help you?"
* Prompt: Type of request, name, date of birth, callback number – all automated and structured
* Closing message: e.g., "Thank you – we will take care of your request as soon as possible."

Further settings are: call categories, voice, or specific transcript details that you can set-up individually.

[[Image:mAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png|/MAI_VisualMailbox_Screenshot.png]]

===Multi-PBX ready===





===Cloud ready===





==Licensing==



* Standard VisualMailbox with Innovaphone integration starting at EUR 89,- per month

==Prerequisites==



* Only Call forwarding to a German phone number
* No further infrastructure needed.
* innovaphone myApps as Web- or native client
* accessible environment via the reverse proxy via SIP TCP
* 1x Port for each VisualMailbox number is used for the registration in the PBX.

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V14r2
* innovaphone V15r1

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


* mAIsolutions VisualMailbox V12345

* innovaphone V15r1sr1

==Configuration==









===   Userobject ===
You Create a useraccount in the PBX via UserAdmin or the advanced UI.

* Username / H323 Name
* Password
* Number
* HardwareID (for registering, with special options)
** Reverse Proxy
** Media Relay

[[File:Medai-vmuser 01.png|left|thumb]]

[[File:Medai-vmuser 02.png|center|thumb|1308x1308px]]

=== Contact us: ===
For the technical setup on our site, we need the environment data:

* PBX Server Adress
* SIP Domain (Systemname)
* The useraccount from above

==Contact==




{|
| DM² AI Solutions GmbH
|-
| Schloßweg 4
|-
| 69190 Walldorf
|-
| Tel: [tel:+496227899299 +496227899299]
|-
| Mail: [mailto:info@dm2s.de info@dm2s.de]
|}

For any questions please refer to [https://www.dm2s.de/kontakt/ our contact page].

File:Medai-vmuser 02.png

2025-09-08T06:00:29Z

Pst:

Hardwaredevice

File:Medai-vmuser 01.png

2025-09-08T05:58:02Z

Pst:

Create Userobject

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2025-09-02T11:59:41Z

Pst: /* Configuration */

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==



==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the Working App via the the Buttons App.

The configured identities (RFID, PIN, Fingerprint) can be assigned to a PBX user via the Application buttons..

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==
This only applies to the connection to Innovaphone, not the complete configuration of a Datafox terminal.

The configuration of terminals is carried out via Datafox Studio. This is available from https://www.datafox.de/unternehmen/downloads/software

'''Settings for Buttons App'''

* The innovaphone buttons app has a reachable webpath for datafox terminals
* The app receives all communication from the terminal via http-get
* The needed settings for the terminal can be edited via Datafox Studio.

[[File:Datafox Studio 001.png|thumb]]

==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

File:Datafox Studio 001.png

2025-09-02T11:58:59Z

Pst:

Datafox Studio Settings

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2025-09-02T11:40:05Z

Pst: /* Configuration */

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==



==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the Working App via the the Buttons App.

The configured identities (RFID, PIN, Fingerprint) can be assigned to a PBX user via the Application buttons..

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==






==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2025-09-02T11:34:57Z

Pst: /* innovaphone Working Integration */

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==



==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the Working App via the the Buttons App.

The configured identities (RFID, PIN, Fingerprint) can be assigned to a PBX user via the Application buttons..

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==






==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

Howto:EVO TimeTrackingTerminals - Datafox - 3rd Party Product

2025-09-02T11:34:19Z

Pst:

[[Image:Datafox Logo CI7 2025.png|200px|right|/Datafox_Logo_CI7_2025.png]]

==Product Name==


Datafox GmbH [https://www.datafox.de/en/products-solutions/time-recording EVO Time tracking terminals]

==Certification Status==



==Category==
[[Category:Referral Product|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty Terminal Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Datafox Logo CI7 2025.png|150px|/Datafox_Logo_CI7_2025.png]]

Datafox is a German manufacturer of devices for time recording, access control, and operational data collection. Established in 1998, we design and produce all products in Thuringia – 100% Made in Germany.
[[File:Datafox Siegel Made in Germany.jpg|100px|right|/Datafox_Siegel_Made_in_Germany.jpg]]
As one of the leading suppliers in Central Europe, we offer a broad portfolio of terminals, self-service PCs, access readers, and controllers – complemented by accessories for convenient identification and flexible installation.
Thanks to our collaboration with a wide network of system integrators, our devices can be seamlessly integrated into diverse IT environments – including communication platforms such as innovaphone.

==Description==



This section presents a curated selection of Datafox terminals for time and access management. These represent a subset of our portfolio and are selected for their proven suitability in UC-related projects – such as integration into communication environments like innovaphone.
All terminals are custom-configured and manufactured based on individual project requirements. Depending on the site and functional needs, different models can be selected and deployed in combination – enabling scalable, tailored solutions.
{|

! Datafox EVO 3.5 Pure !! Datafox EVO 5.0 Pure!! Datafox EVO 5.0 Flex
|-
| [[File:Datafox EVO 3.5 Pure.png|150px|center|/Datafox_EVO_3.5_Pure.png]]

The EVO 3.5 Pure is our most compact and cost-efficient terminal – ideal for projects that require a small display and straightforward interaction. It is particularly suitable for budget-sensitive environments, installations with limited space, or where individual design is not a priority.
Despite its price advantage, it offers full functionality for time and job tracking.

|| [[File:Datafox EVO 5.0 Pure White.png|160px|center|/Datafox_EVO_5.0_Pure_White.png]]

The EVO 5.0 Pure shares its housing and base features with the EVO 3.5 Pure, but offers enhanced usability through a larger 5.0” display.
This allows for a more comfortable user experience, especially where extended keypad layouts or visual feedback are required.
The device can be equipped with either a capacitive or resistive touch interface, making it adaptable to various environments and usage scenarios.
It is available in both anthracite (RAL 7016) and signal white (RAL 9003).

|| [[File:Datafox EVO 5.0 Flex.png|170px|center|/Datafox_EVO_5.0_Flex.png]]

The EVO 5.0 Flex combines the compact size of the EVO Pure series with the premium build quality of the Flex line. It features a solid aluminium frame with a durable real-glass front, offering an elevated look and feel, as well as IP65 front protection.

For companies seeking a visually branded setup, this terminal supports custom printing on the housing – beyond just logo display on screen.

|-
|'''Key specifications:'''
* 3.5” capacitive touch display (480 × 320 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016), custom colours from 500 units
|| '''Key specifications:'''
* 5.0” capacitive or resistive touch display (800 × 480 px)
* Plastic housing (PC-ABS), IP54 front protection
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Anthracite (RAL 7016) and Signal white (RAL 9003)
||'''Key specifications:'''
* 5.0” capacitive touch display (800 × 480 px)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 109 × 200 × 85 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
|-
|

|-
| '''Example configuration:'''
EVO 3.5 Pure base unit (Art. 114051) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Pure base unit signal white (Art. 114061-WS) with
* Mifare RFID reader – Classic & DESFire (Art. 114304MB)
* LAN module (Art. 114104)
* PoE module (Art. 114117)
|| '''Example configuration:'''
EVO 5.0 Flex base unit (Art. 135001) with
* Mifare RFID reader – Classic & DESFire (Art. 135304MB)
* LAN module (Art. 135104)
* PoE module (Art. 135117)

|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-pure/ EVO 3.5 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-pure EVO 5.0 Pure] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-50-flex EVO 5.0 Flex]
|}

{|
|-
! Datafox EVO 7.0 Flex !! Datafox EVO 3.5 Universal IP66 und IP69K
|-
|
[[File:Datafox EVO 7.0 Flex.png|150px|center|/Datafox_EVO_7.0_Flex.png]] Our largest and most advanced terminal – perfect where space allows and premium usability is expected.
||
[[File:Datafox EVO 3.5 Universal IP66,69K.png|120px|center|/Datafox_EVO_3.5_Universal_IP66,69K.png]] The EVO 3.5 Universal IP66/IP69K is built for high-hygiene and extreme industrial conditions – such as food processing spray zones, wash bays, or marine terminals.

|-
| '''Key specifications:'''
* 7.0” color TFT (480 × 800 pixels)
* Housing: anodised aluminium, hardened real-glass front (≥6H)
* Front protection class: IP65
* Dimensions: 140 x 266 x 95 mm
* Operating temperature: -20 to +60 °C
* USB interface (Micro-USB), typically used for setup
* Communication via HTTP/HTTPS
* Supplied with wall mount plate and proximity sensor
* Standard colour: Black, customized design possible
|| It comes standard with integrated access control capabilities, including multiple I/Os and RS485 interfaces for direct connection of door modules and readers – making it a fully equipped access control terminal right out of the box.
Its anodised aluminium frame, real-glass front and V4A stainless steel backplate ensure exceptional resistance to water, dust, impact, and cleaning processes.

'''Key specifications:'''
* 3.5” color TFT (320 × 480 pixels)
* IP66/IP69K: full protection against dust, water, pressure cleaning
* Aluminum frame (hard-anodized), real glass (hardness ≥6H), V4A stainless steel base
* Dimensions: 96 × 243 × 55 mm (W×H×D)
* Operating temperature: –20 to +50 °C (PoE: –20 to +40 °C)
* Integrated I/Os, RS485, PoE, LAN
* Includes distance spacers for hygiene-compliant wall mounting

|-
| '''Example configuration:'''
EVO 7.0 Flex base unit (Art. 126001) with
* Mifare RFID reader – Classic & DESFire (Art. 126304MB)
* LAN module (Art. 126104)
* PoE module (Art. 126117)

|| ''pre-configured''
|-
| [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-70 EVO 7.0 Flex] || [https://www.datafox.de/en/products-solutions/alle-geraete/datafox-evo-35-universal-ip66-and-ip69k EVO 3.5 Universal IP66/IP69K]
|}




==Use Cases==
* Employee time tracking
* Project and job time logging
* Volunteer time tracking at events
* Access control with rights management
* Visitor and supplier access
* Cost center allocation
* Machine unlocking / machine control
* Driver’s license validation before vehicle use

==Functions==


'''Mounting & Accessories'''
* Wall mounting (standard configuration)
* Weather protection roof, desktop stand, pedestal
* Front panel mounting kit for flush integration (1–3 mm front plates)
* Shatter protection film for glass front
* Braille overlay
* SD card slot for memory expansion
'''Reading Technologies & Authentication'''
* Supported RFID technologies: MIFARE Classic, MIFARE DESFire, MIFARE Plus, NFC, LEGIC Prime, LEGIC Advant, HITAG, EM4200, ISO 14443, ISO 15693
* Barcode & QR code reader
* Fingerprint sensor
* iButton or PIN input
* Multi-factor authentication (e.g. card + PIN)
* Signature capture via touch display (image file)
'''Communication & Power'''
* Ethernet (LAN), Wi-Fi, mobile network (LTE)
* Power supply via PoE or external power adapter
* Configuration via free Datafox Studio software
* Central device management tool (upcoming)
'''Special Features & Expansion Modules'''
* Access control modules incl. "Data on Card"
* Machine data collection modules
* GPS module
* Integrated speaker
* Wrist temperature measurement
* Relay and I/O control (e.g. for machines or doors)
* Continuous activation when RFID card remains detected

==innovaphone Working Integration==
Datafox terminals can operate the Working App via the the Buttons App.

The configured identities (RFID, PIN, fingerprint) can be assigned to a PBX user via the Application buttons..

==Version==




Product versions used for interop testing:

* Datafox EVO Version XYZ

* innovaphone PBX V15r1
* innovaphone Buttons App 15r1
* innovaphone Working App 15r1

==Configuration==






==Summary==


The Datafox EVO terminal series offers highly flexible, scalable solutions for digital identification and data capture – from compact entry-level terminals to rugged industrial devices for hygiene-critical environments. Featuring modular hardware, various design options, and seamless system integration, these terminals are ideal for professional IT projects across industries.
Each terminal is designed to be configured to the customer’s exact requirements – functionally and visually. With fast support, in-house development, and quality “Made in Germany,” Datafox ensures reliability and future-proof implementation in any project.

==Contact==



{|
| '''Datafox GmbH'''
|-
| Andy Burghart
|-
| Dermbacher Str. 12-14
|-
| 36419 Geisa
|-
| Tel: +49 36967 595 0
|-
| Fax: +49 36967 595 50
|-
| Mail: [mailto:sales@datafox.de sales@datafox.de]
|}

Reference15r1:Concept Buttons App

2025-07-09T10:49:18Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

Reference15r1:Concept Buttons App

2025-07-03T07:51:49Z

Pst: /* Buttons App - Overview */

Reference15r1:Concept Buttons App

2025-07-03T07:45:43Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======= Webhook Get Parameters =======

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

== Troubleshooting ==

== Related Articles ==

Reference15r1:Concept Buttons App

2025-07-03T07:44:31Z

Pst: /* Webhook (RestApi) */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======= Webhook - Get Variables =======

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

== Troubleshooting ==

== Related Articles ==

Reference15r1:Concept Buttons App

2025-07-03T07:42:13Z

Pst: /* Buttons App - Overview */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

== Troubleshooting ==

== Related Articles ==

Reference15r1:Concept Buttons App

2025-07-03T07:37:31Z

Pst: /* Input trigger */

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

== Troubleshooting ==

== Related Articles ==

Reference15r1:Concept Buttons App

2025-06-30T07:46:12Z

Pst:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|/Buttons-mwi-working.png|none|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|/Buttosapp_user_chat.png|none|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''Alert Timout = 0''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

== Troubleshooting ==

== Related Articles ==