innovaphone wiki - User contributions [en]

Howto:Callback Manager App - effexx - Partner App

2024-03-11T07:31:55Z

Peter.stock: /* Release Notes */

__NOCACHE__
[[File:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[File:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[File:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[File:Effexx-cbm-install-01.png]]
 
[[File:Effexx-cbm-install-02.png]]
 
[[File:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Reverse Lookup - Shared Contacts ===
If the phone numbers are stored in the Contacts app and have only been shared there with certain users or groups, the contacts must also be shared for the "Waiting Queue" itself, as the reverse lookup is carried out with the user name of the Waiting Queue.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR6''' 
- fix in UI, if the App was started in small windowscale 
- show a legend of colormeaning in callbacklist 
'''130049 - SR7''' 
- sometimes the end of call was not clearly recognized 
- fix for some scenarios, where reverselookup was not updated in Database 
'''130050 - SR8''' 
- fix for Displayname / Reverselookup - Wait for Database INSERT before Database UPDATE if Displayname comes very fast from Reverselookup

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2024-02-15T10:48:50Z

Peter.stock: /* Release Notes */

__NOCACHE__
[[File:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[File:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[File:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[File:Effexx-cbm-install-01.png]]
 
[[File:Effexx-cbm-install-02.png]]
 
[[File:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Reverse Lookup - Shared Contacts ===
If the phone numbers are stored in the Contacts app and have only been shared there with certain users or groups, the contacts must also be shared for the "Waiting Queue" itself, as the reverse lookup is carried out with the user name of the Waiting Queue.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR6''' 
- fix in UI, if the App was started in small windowscale 
- show a legend of colormeaning in callbacklist 
'''130049 - SR7''' 
- sometimes the end of call was not clearly recognized 
- fix for some scenarios, where reverselookup was not updated in Database

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2024-02-15T10:47:22Z

Peter.stock: /* Release Notes */

__NOCACHE__
[[File:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[File:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[File:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[File:Effexx-cbm-install-01.png]]
 
[[File:Effexx-cbm-install-02.png]]
 
[[File:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Reverse Lookup - Shared Contacts ===
If the phone numbers are stored in the Contacts app and have only been shared there with certain users or groups, the contacts must also be shared for the "Waiting Queue" itself, as the reverse lookup is carried out with the user name of the Waiting Queue.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR6''' 
- fix in UI, if the App was started in small windowscale 
- show a legend of colormeaning in callbacklist
'''130049 - SR7''' 
- sometimes the end of call was not clearly recognized 
- fix for some scenarios, where reverselookup was not updated in Database

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2024-02-08T11:02:21Z

Peter.stock:

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.

===136017 - final===
- Startversion 

===136035 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

===136036 - SR2===
- Increase paketsize for receiving SIP Request in App Service

==Known Problems==
===Provisioning of devices via Users Admin not working===
Please note the following for environments that do not have Internet access. In this case, the assignment of devices via the Users Admin may be disrupted.
The Gigaset App works together with the provisioning service of the Devices App. The online provisioning server from innovpahone "config.innovaphone.com" is entered as the default in the Devices app. If the environment cannot reach the server, the process is aborted.
To avoid this, offline provisioning must be configured for the domain in the Devices app.
https://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_Offline_Provisioning

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Sendnumber App - effexx - Partner App

2024-02-02T09:50:28Z

Peter.stock: /* Known Issues */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] SendNumber-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

This App was listed April 11th, 2022.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==






The Sendnumber app allows users to choose which phone number they want to use to make outgoing calls. All extensions of existing waiting queue objects are automatically available for configuration.

The Sendnumber admin app allows admins to assign and remove phone numbers to users.

==Functions==




* Set the outgoing number
* Reset to own number
* Permission management

=== Provided APIs ===




* Websocket
* PbxAdminApi

==Licensing==


No license is required for this app

==Prerequisites==


* Edited trunk object with "Name as Number" option via Advanced UI
* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2sr9

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


* effexx SendNumber-App 130001

* innovaphone V13r2sr9
* innovaphone AP Platform 100013

==Configuration==




===Edit the trunk object ===
 
The SendNumber app edits user objects on the "External" attribute, which has been available since software version V13R2. In order for this option to be taken into account for outgoing telephony, the trunk object must be adjusted via the Advanced UI. It is also important to note that after this adjustment, it should first be checked whether this will result in restrictions on outgoing telephony with regard to call number display or call diversions.
 
''In rare PBX constellations, errors can occur at this point. Innovaphone support should be contacted first. This function has nothing to do with the SendNumber app, but is just a feature of the innovaphone PBX that is required.'' '' 

[[Image:Effexx-sendnumber-AdvancedUI-01.PNG]] 
-------------------------------------------------------------- 
[[Image:Effexx-sendnumber-AdvancedUI-02.PNG]] 

===Install the App===
 
The following series of images shows the installation sequence of the SendNumber app from the AppStore. 

[[Image:Effexx-sendnumber-01.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-02.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-03.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-04.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-05.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-06.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-07.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-08.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-09.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-10.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-11.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-12.PNG]] 

===SendNumber - Admin App===
With Sendnumber Admin App, the outgoing phone numbers of the existing waiting queues can be assigned to individual or all users. 
[[Image:Effexx-sendnumber-admin-01.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-admin-02.PNG]] 
------------------------------------------ 

===SendNumber - User App ===
With the SendNumber user app, users can select their outgoing phone number. 
[[Image:Effexx-sendnumber-user-01.PNG]] 
------------------------------------------ 

==Known Issues==
- There was an error in the app file name. When updating from 13R2 SR10 to a higher version, the old App Service must be uninstalled.
 
- The User needs a configured Number in PBX. Otherwise the Userapp don't show anything. Users without number are not supported.

==Release Notes==
'''130001 - SR10''' 
- Startversion 
'''130002 - SR11''' 
- fixed an issue with AvatarApi in small pbx sceanrios. 
- changed appname in binary with companyname as prefix 
'''130003 - SR12''' 
- fixed an issue with untrusted or self signed webserver certificates on pbx 
'''130004 - SR13''' 
- compatibility with 13R3 PbxAdminApi Security 
'''130006 - SR14''' 
- compatibility with 13R3 - Sendnumber-User fills external attribut with Waiting Queue or own user extension. Before that a null value was presented to own number 
'''130007 - SR15''' 
- Add new Option for using the "External" Field of Waiting Queues 
- Add new Option for Node Support 
- Add new field for individual prefix 
'''130008 - SR16''' 
- New Settings Checkmark did not work sometimes 

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Sendnumber App - effexx - Partner App

2024-02-02T09:50:09Z

Peter.stock: /* Known Issues */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] SendNumber-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

This App was listed April 11th, 2022.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==






The Sendnumber app allows users to choose which phone number they want to use to make outgoing calls. All extensions of existing waiting queue objects are automatically available for configuration.

The Sendnumber admin app allows admins to assign and remove phone numbers to users.

==Functions==




* Set the outgoing number
* Reset to own number
* Permission management

=== Provided APIs ===




* Websocket
* PbxAdminApi

==Licensing==


No license is required for this app

==Prerequisites==


* Edited trunk object with "Name as Number" option via Advanced UI
* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2sr9

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


* effexx SendNumber-App 130001

* innovaphone V13r2sr9
* innovaphone AP Platform 100013

==Configuration==




===Edit the trunk object ===
 
The SendNumber app edits user objects on the "External" attribute, which has been available since software version V13R2. In order for this option to be taken into account for outgoing telephony, the trunk object must be adjusted via the Advanced UI. It is also important to note that after this adjustment, it should first be checked whether this will result in restrictions on outgoing telephony with regard to call number display or call diversions.
 
''In rare PBX constellations, errors can occur at this point. Innovaphone support should be contacted first. This function has nothing to do with the SendNumber app, but is just a feature of the innovaphone PBX that is required.'' '' 

[[Image:Effexx-sendnumber-AdvancedUI-01.PNG]] 
-------------------------------------------------------------- 
[[Image:Effexx-sendnumber-AdvancedUI-02.PNG]] 

===Install the App===
 
The following series of images shows the installation sequence of the SendNumber app from the AppStore. 

[[Image:Effexx-sendnumber-01.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-02.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-03.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-04.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-05.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-06.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-07.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-08.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-09.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-10.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-11.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-12.PNG]] 

===SendNumber - Admin App===
With Sendnumber Admin App, the outgoing phone numbers of the existing waiting queues can be assigned to individual or all users. 
[[Image:Effexx-sendnumber-admin-01.PNG]] 
------------------------------------------ 
[[Image:Effexx-sendnumber-admin-02.PNG]] 
------------------------------------------ 

===SendNumber - User App ===
With the SendNumber user app, users can select their outgoing phone number. 
[[Image:Effexx-sendnumber-user-01.PNG]] 
------------------------------------------ 

==Known Issues==
- There was an error in the app file name. When updating from 13R2 SR10 to a higher version, the old App Service must be uninstalled.
- The User needs a configured Number in PBX. Otherwise the Userapp don't show anything. Users without number are not supported.

==Release Notes==
'''130001 - SR10''' 
- Startversion 
'''130002 - SR11''' 
- fixed an issue with AvatarApi in small pbx sceanrios. 
- changed appname in binary with companyname as prefix 
'''130003 - SR12''' 
- fixed an issue with untrusted or self signed webserver certificates on pbx 
'''130004 - SR13''' 
- compatibility with 13R3 PbxAdminApi Security 
'''130006 - SR14''' 
- compatibility with 13R3 - Sendnumber-User fills external attribut with Waiting Queue or own user extension. Before that a null value was presented to own number 
'''130007 - SR15''' 
- Add new Option for using the "External" Field of Waiting Queues 
- Add new Option for Node Support 
- Add new field for individual prefix 
'''130008 - SR16''' 
- New Settings Checkmark did not work sometimes 

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-11-06T15:43:43Z

Peter.stock: /* Configuration */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Reverse Lookup - Shared Contacts ===
If the phone numbers are stored in the Contacts app and have only been shared there with certain users or groups, the contacts must also be shared for the "Waiting Queue" itself, as the reverse lookup is carried out with the user name of the Waiting Queue.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR6''' 
- fix in UI, if the App was started in small windowscale 
- show a legend of colormeaning in callbacklist

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-10-27T08:56:26Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR6''' 
- fix in UI, if the App was started in small windowscale 
- show a legend of colormeaning in callbacklist

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-10-27T08:55:28Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR6''' 
- fix in UI, if the App was started in small windowscale 
- show a legend of for colors in callbacklist

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-10-27T08:54:58Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR8''' 
- fix in UI, if the App was started in small windowscale
- show a legend of for colors in callbacklist

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-10-27T08:54:28Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount 
'''130048 - SR8''' 
- fix in UI, if the App was started in small windowscale
- show a legend of for colors in callbacklist

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-09-08T07:54:14Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality -> Instead of an update, you have to set the PbxSignal API in the Callback Manager User App for using the batchcount <7b>

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-09-08T06:11:08Z

Peter.stock: /* Provided APIs */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi
* PbxSignal

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-09-08T06:00:31Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 
'''130047 - SR5''' 
- add batchcount functionality

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-09-01T10:41:53Z

Peter.stock: /* 136036 - SR2 */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.

===136017 - final===
- Startversion 

===136035 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

===136036 - SR2===
- Increase paketsize for receiving SIP Request in App Service

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-09-01T10:41:27Z

Peter.stock: /* Release Notes */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.

===136017 - final===
- Startversion 

===136035 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

===136036 - SR2===
- Increase paketsize for receiving SIP Request

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-09-01T10:40:11Z

Peter.stock: /* 136032 - SR1 */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.

===136017 - final===
- Startversion 

===136035 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T13:02:52Z

Peter.stock: /* 130037 - final */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.

===136017 - final===
- Startversion 

===136032 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T13:02:00Z

Peter.stock: /* Update Notice */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing an update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.

===130037 - final===
- Startversion 

===136032 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T13:01:06Z

Peter.stock: /* Release Notes */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
<param name="DmGlobal.0.SuotaEnable" value="1" /> --> Enable Software Update over the Air for Gigaset Handsets 
<param name="hs.@.DirectAccessDir" value="1"/> --> change Directory Access Key to Local Directory 
<param name="hs.@.IntKeyDir" value="10"/> --> change Int Key to LDAP Directory 
<param name="hs.@.ShowMissedCalls" value="0" /> --> deactivates LED signaling for Missed Calls 
<param name="hs.@.ShowMissedAlarms" value="0" /> --> deactivates LED signaling for Missed Alarms 
<param name="hs.@.ShowMissedNetAM" value="0" /> --> deactivates LED signaling for Missed Voicemails 
 

Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===Update Notice===

Even though this should be the standard procedure, we would still like to point this out. 
Before installing the update, we recommend backing up the PBX and the Gigaset application on the application platform so that a rollback of the configuration is possible.
===130037 - final===
- Startversion 

===136032 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T08:10:45Z

Peter.stock: /* Multiple Instances */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 
In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===130037 - final===
- Startversion 

===136032 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T08:09:26Z

Peter.stock: /* 136030 - SR1 */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 

In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===130037 - final===
- Startversion 

===136032 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T08:05:25Z

Peter.stock: /* Multiple Instances */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.PNG]]
 

In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T08:04:24Z

Peter.stock: /* Configuration */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.png]]
 

In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T08:02:43Z

Peter.stock: /* Configuration */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

[[Image:Gigaset-rvp-special.png]] 

In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

File:Gigaset-rvp-special.PNG

2023-08-15T08:01:40Z

Peter.stock:

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T07:58:30Z

Peter.stock: /* Multiple Instances */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/> 
<param name="SipProvider.19.OutboundProxyMode" value="0"/> 
<param name="SipProvider.19.OutboundProxyPort" value="5061"/> 

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T07:58:03Z

Peter.stock: /* Multiple Instances */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used. 
If the local SIP port of the app is e.g. 5065, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. This is done via the area for own provisioning parameters. 

In view on the example above: 
<param name="SipProvider.19.OutboundProxyAddress" value="app.example.com"/>
<param name="SipProvider.19.OutboundProxyMode" value="0"/>
<param name="SipProvider.19.OutboundProxyPort" value="5061"/>

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T07:53:02Z

Peter.stock: /* Configuration */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

===Multiple Instances===
If you want to run multiple instances of the app on one AppPlatform, the local SIP ports of the app service must not overlap. This means that different ports must be used for SIP provisioning in each app service. The distinction can be made in the reverse proxy on the basis of the SIP realm used.

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T07:48:27Z

Peter.stock: /* Configuration */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service. 

[[Image:Gigaset-rvp-all.png]]

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

File:Gigaset-rvp-all.png

2023-08-15T07:44:57Z

Peter.stock:

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-15T06:27:20Z

Peter.stock: /* Usage over ReverseProxy */

[[Image:Gigaset-logo.png||200px|right]]

==Product Name==


[https://www.gigaset.com Gigaset] Gigaset-Provisioning-App

==Certification Status==



{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed December 2022.

==Category==

[[Category:Partner_Apps|{{PAGENAME}}]]
{{Category:3rdParty_Terminal_Devices}}
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]

==Vendor==



[[Image:Gigaset-LOGO.png|150px]]



With innovative communication solutions from Gigaset professional, your organisation can unlock its true potential and stay ahead of the competition.
Our cutting-edge telephony technology is delivered by a community of dedicated partners that can help you create a complete communications solution rather than a multitude of products.
With Gigaset professional, you gain access to an open platform designed for its user-friendliness, flexibility and outstanding performance, while offering seamless compatibility with leading on-premise telephony systems and cloud-based service providers.

[https://www.gigaset.com/pro/en_en/ Gigaset - Pro]

==Description==



<table>
<tr>
<tr>
<td colspan="5">Gigaset-Provisioning App supports:</td>
</tr>
<td colspan="5">DECT IP PRO</td>
</tr>
<tr>
<td>N870 [[Image:N870.png‎|250px]]</td>
<td>
- IP DECT Multicell System 
- max. number basestations: 6000 
- max. number handsets: 20000 
- max. number parallel Calls: 6000 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N870 N870]
 
<td></td>
<td>N670 [[Image:N670_Mini_Multicell_EN.png‎|250px]]</td>
<td>
- IP DECT Singlecell and Mini-Multicell System 
- max. number basestations: 3 
- max. number handsets: 20 
- max. number parallel Calls: 8 
for further information see: 
[https://teamwork.gigaset.com/gigawiki/display/GPPPO/N670 N670]
 
</tr>
</table>



The Gigaset Provisioning App integrates the Gigaset Single-, MiniMulti and Multicell Systems into the innovaphone PBX environment.
After the initial setup, user and phonebook management can be done from the innovaphone myApps environment,
so that no further activities need to be performed on the Gigaset system.

==Functions==




* Add / Remove Gigaset handset
* Configure the Phonebook on Gigaset Environment

With the Gigaset Provisioning App it is possible to automatically add and remove DECT devices via IPUI provisioning on the Gigaset Nx70 IP DECT.
In addition, the LDAP configuration can be provisioned.

== Provided APIs ==




* Websocket
* AdminApi
* TableUsers
* Services
* PbxApi (since SR1)

==Licensing==


No license is required for this app

==Prerequisites==


None (at least knowledge about installing an App on the AP Platform and adding the App Object via PBX Manager)

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5

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


* Gigaset Provisioning-App - 13R3 136017
* Gigaset Provisioning-App - 13R2 132017

* innovaphone V13r2 SR19
* innovaphone V13r3 Beta5
* Gigaset Nx70 V2.49.1

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

As an admin, create the environment settings in the Gigaset Provisioning App.
For the innovaphone PBX, enter the domain, the IP address of the PBX or the FQDN, the SIP- or SIP-TLS Port, the MasterPBX-Name and the PBX password. You can also set Logname or E164 as an alternative, when DN is not set. Also define if reverse proxy should be activated or not. 

'''There are two different ways to configure provisioing from this app to the gigaset integrator. '''

The '''simple way is http'''. Therefore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the IP address of the integrator, the admin password and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Provisioning via http is quit simple to configure, but has a few disadvantages: you can't be logged in on WebUi at the same time and the App Platform must reachable by IP-Address from Gigaset Integrator, and vise versa. 

That's why we implemented the '''second connection method via SIP'''. 
Therfore you have to enter the MAC ID (MAC address plus 4-digit code, can be found on the web UI under Status or on the integrator's box),
the SIP Realm of the App Platfrom, the App Platfrom FQDN, App Platform SIP- or SIP-TLS Port and additionally a sip username and password of your choice!
of course also the admin password from the integrator and select the DECT frequency. You can also define an alternative open dect registration time window (default 300s).
Advantages of the provisioning via SIP is that you can be logged in into the WebUi in paralell and this will also work e.g. for cloud environments and other scenarios where PBX and Gigaset Integrator are not into the same routed network. 

If the Admin Password does not match the one assigned, it would be overwritten in the next step, during the 1st provisioning with the one entered here. 

Under Phonebook settings you can activate the sync of the standard LDAP directory of the innovaphone PBX (PBX0).
or alternatively enter all parameters manually according to the LDAP server used.
Please enter the IP address, port and previously created access data for the innovaphone LDAP. 

Call number formatting reads access code and prefixes from the pbx or you can define it manually. 
This is used for reverse lookup and call settings. you can change more call settings manually or via own provisioning parameters. 
If you activate wild carding and enter your internal number length and Emergencey Numbers, the Gigaset DECT System will wildcarding your phone number search into the phonebook.
for example: the access code will be stripped and then *4989123 is searched for instead of 004989123, or *89123 is searched instead of 089123. 

You have the possibility to add provisioning parameters by your own in xml strings. You can find all provisioning parameters here: 
'''[https://teamwork.gigaset.com/gigawiki/display/GPPPO/FAQ+-+Auto+provisioning%3A+Parameters Gigaset Provisioing Parameters] '''
 
please have in mind, that you have to replace special signs with placeholders: 
& – '&amp'; 
‘ – '&apos'; 
< – '&lt'; 
> – '&gt'; 
” – '&quot'; 
Ä - '&#196'; 
Ö - '&#214'; 
Ü - '&#220'; 
ä - '&#228'; 
ö - '&#246'; 
ü - '&#252'; 
ß - '&#223'; 
 
here are a few examples for popular provisioning parameters: 
Click on the Save icon to save the entered configuration. The app generates a provisioning path from the data.
This path does not change as long as you do not change the MAC-ID.
Copy this path and paste it on the Gigaset Integrator under Settings --> System --> Provisioning and configuration.
Execute the first provisioning via the button "Start Auto Configuration" and log out of the web interface,
because as long as you are logged in, no provisioning can be performed by the app! 

<gallery>
Innovaphone GigasetApp Admin2.0 HTTP.png|Caption1
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|Caption2
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[Image:Innovaphone GigasetApp Admin2.0 HTTP.png]]
|
[[Image:Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png]]
|}
 

===Add Devices to User===

Now create new end devices as usual via UserAdmin or the Profile app. Select "Gigaset" in the manufacturer selection field and then enter the IPUI of the handset instead of the MAC address.
You can find the IPUI of the handset on the box, in the battery compartment or by switching to the menu on the handset with the right button and typing "*#06#".
Now the IPUI is displayed in the top line.

After you have saved the new handset, Gigaset Provisioning will automatically transfer the account to the integrator and start the login window for 5 minutes.
Now you can register the new handset with the default PIN "0000".

If you want to trigger provisioning again, e.g. to open the login window again, press the Save button in the Admin area of the Gigaset Provisioning app again.
The successful transfer is indicated by a message.
If the provisioning was not successful, this is also displayed.
This can have 2 reasons, either you are still logged in on the integrator in the background
or you have changed the admin password on the integrator in the meantime and have not stored the new one in the settings of the app.

[[Image:innovaphone_GigasetApp_User.png]]

===Usage over ReverseProxy===
As you can see, the app provides a small SIP server. For this SIP server, a SIP realm should be used that is not used in any other system in the environment.
As an example: If the SIP realm / system domain of the environment is "example.com", "gigaset.example.com" could be used as the SIP realm for the App Service. The advantage now is that we can enter this domain on the reverse proxy and direct it from there to the SIP port of the App Service.

==Release Notes==
===130037 - final===
- Startversion 

===136030 - SR1===
====GUI and App====
- Change App Icon and Logo 
- Support more languages 

====Innovaphone System Settings====
- Add Configuration for SIP Port of PBX 
- Add Checkmark for TLS 
- Add Configuration for PBX Name of Master PBX (required after Update) 
- Add Configuration for Usage of Longname or Number instead no Displayname is availabe. 
- Add Checkmark "ReverseProxy" for authorization of DECT Devices over ReverseProxy 

====Gigaset System Settings====
With the update, you have the option to run the Gigaset app as a small SIP server. This is necessary to register the transmitter with the app via a special SIP profile. The registration is done with a separate SIP domain directly on the AppPlatform without registering via the PBX. This makes it possible to run the app via the reverse proxy on Cloud PBX environments. 
- Add Registration time for DECT Device Register 
- Add New Option "Connect via SIP" instead of http 
- implementation of small SIP server methods "Register" , "Check Sync" 
- Add Configuration for Provisiong SIP Domain (different from PBX Domain) 
- Add Configuration for SIP Port of App Platform 
- Add Checkmark for TLS 
- Add Username for SIP Authentication on App Platform 
- Add Password for SIP Authentication on App Platform 
- Add the possibility of specifying the prefixes and internal number length, for phone number formatting, based on the innovapone configuration 
- Add Checkmark for wildcarding, so that reverse lookup in Phonebooks works independent of the saved format 
- Add the possibility of specifying emergency numbers 
- Add a field for adding individual provisioning parameters as an xml string 

==Contact==
Gigaset Communications GmbH 
Frankenstraße 2 
46395 Bocholt

Tel: +49 2871 91-0 
E-Mail: de.pro@gigaset.com

'''Support''' 
+49 (89) 8780 6575 + PIN Code 
support@gigaset.com

'''Become a partner''' 
https://gigasetportal.force.com/Partner

'''App Feature Request''' 
Dennis Zimmermann 
Technical Sales Manager 
dennis.zimmermann@gigaset.com

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-11T11:37:07Z

Peter.stock: /* Configuration */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-10T14:27:20Z

Peter.stock: /* GUI and App */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-10T10:48:57Z

Peter.stock: /* Provided APIs */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-10T10:48:21Z

Peter.stock: /* Provided APIs */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T12:04:19Z

Peter.stock: /* Gigaset System Settings */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T12:00:08Z

Peter.stock: /* Gigaset System Settings */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:59:51Z

Peter.stock: /* 136030 - SR1 */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:53:19Z

Peter.stock: /* 136030 - SR1 */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:52:49Z

Peter.stock: /* 130037 - final */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:52:33Z

Peter.stock: /* Release Notes */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:52:10Z

Peter.stock: /* Release Notes */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:51:40Z

Peter.stock: /* Release Notes */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:51:23Z

Peter.stock: /* Release Notes */

Howto:Gigaset-Provisioning-App - Gigaset - Partner App

2023-08-09T11:43:23Z

Peter.stock:

Howto:Callback Manager App - effexx - Partner App

2023-08-07T10:07:28Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service 
- clear all active calls when app service starts 

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-08-07T10:06:58Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist. 
'''130042 - SR4''' 
- sometimes the end of a call was not recognized by the app service
- clear all active calls when app service starts

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-08-02T09:07:22Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''130041 - SR3''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist.

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com

Howto:Callback Manager App - effexx - Partner App

2023-07-28T08:06:18Z

Peter.stock: /* Release Notes */

[[Image:Effexx-logo01.png||150px|right]]

==Product Name==


[https://www.effexx.com effexx] CallbackManager-App

==Certification Status==

{{Template:Compat_Status_referral_product_new|type=App}}

Testing of this product has been finalized May 2023.

==Category==

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

==Vendor==



[[Image:Effexx-logo01.png|150px]]



In order to make your business infrastructure and your communication processes efficient and secure, you not only need innovative technologies, but also solutions that are precisely tailored to your specific goals and requirements. The areas of telecommunications, information technology, security and software technology are constantly changing. Optimizing your technology flow requires selecting products and technologies that bring measurable benefits to your business. effexx advises you reliably, competently and individually on this.


[https://www.effexx.com/ueber-effexx effexx - Über uns]

==Description==


Sometimes there are callflows with multiple nested waiting queues. The app works differently than a queue monitor. It adapts to the existing waiting queues and their interconnection. 
You can define if the queue should only be counted or missed calls should also be recorded in the callback queue. 
With the Callback Manager app, the calls of waiting queues are recorded and displayed in a daily history. Missed calls can be commented and processed from a list. 
The app can monitor multiple waiting queues at the same time and summarize them in one overview.
Agents can start the call directly on the app. The default device of myApps is used here. Calls from the same caller within a group are totaled and combined. For contact identification, the app uses the reverse lookup of the PBX.
 
[[Image:Effexx-cbm-user01.PNG]]



* Callmanagement
* Callback list

==Functions==




* Manage missed Calls of Waiting Queues
* Create a Daily Dashboard of callcounters

=== Provided APIs ===




* Websocket
* Admin
* RccApi

==Licensing==


* one service license per callback list regardless of the number of users. Several waiting queues can be combined per callback list.
* with activated testmode you can test the function of this app.
* each callback list needs an separate app Instance and service lincense in environment.

Example
You have a few Waiting Queues, like "IT Hotline" - 10 , "Telephone Hotline" - 11, "Network Hotline" - 12, "CRM - Hotline" - 13

* If you want to sumarize all callbacks of Waiting Queues mentioned above in one single callback list, you only need one service license and only need one app instance of Callback Manager App in AP Platform.
--> 1 Service License, 1 App Instance

* If you want separate callback lists for each Waiting Queue mentioned above, you need 4 service licenses and 4 Instances of Callback Manager App in AP Platform.
--> 4 Service License, 4 App Instances

Since it is a service license, no user license is required. Therefore, any number of users can be authorized to the callback list and use it.

==Prerequisites==


* '''If you use myApps via browser, https is required'''


==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3 SR4

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


* effexx CallbackManager-App 13r3 130035 final

* innovaphone V13r3 SR4
* innovaphone AP Platform 100013

==Configuration==




===Install the App===
[[Image:Effexx-cbm-install-01.png]]
 
[[Image:Effexx-cbm-install-02.png]]
 
[[Image:Effexx-cbm-install-03.png]]

==== Add "Operator Connect for SOAP - Important for all Waiting Queues you want to monitor ====

[[File:Effexx-cbm-queue-config.png]]

====Add a Waiting Queue with Callback list to configuration====
To define a waiting queue with callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the upper list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-rr-01.png]]

====Add a Waiting Queue without Callback list to configuration====
To define a waiting queue without callback list, you must define the PBX name (1) , the Longname of the waiting queue (2) and the display name (3) in the bottom list. 
The display name is independent of the PBX and freely definable within the app. 
=> (1) In Master-Slave Scenario you have to define the name of the pbx where the waiting queue is assigned.

[[File:Effexx-cbm-admin-nr-01.png]]

====Option - Show the origin of the Call - In case of a forwarded call====
In some scenarios, the call may have been routed first to an employee or through another object and then enter the waiting queue. With this option, the source of the call detour can be displayed.

[[File:Effexx-cbm-admin-option-01.png]]

====Option - Reset Database====
For testing purposes or other configurational activities we have added a "Remove all data" button in the admin area. This will reset the current counters and the callback lists. Normally you don't need this button in active mode. However, should there be an error, the user app view can be reset via this button. Administrative settings remain unchanged.

[[File:Effexx-cbm-admin-option-02.png]]

===License Configuration - Add Service License to App===
The app is licensed via a service license as described. For this purpose, the service license must be set to "1" via the Advanced UI on the app object of the user app. This works if a license has been purchased or the test mode is used.
 
 Currently, it might be necessary to restart the app service in the AP after this adjustment. Otherwise, the app may not notice the change. 

[[File:Effexx-cbm-license-01.png]]

===Callback Manager - User App ===
====Callback Manager - User App - Client GUI ====
 
[[File:Effexx-cbm-user-02.png]]

* (1) - Total sum of all calls
* (2) - Total sum of all active calls
* (3) - Total sum of all connected calls | Incoming calls to a monitored waiting queue that were successfully connected to an agent.
* (4) - Total sum of all not connected calls | In case the call was on a monitored waiting queue without callback list.
* (5) - Total sum of all not connected calls | In case the call was on a monitored waiting queue with callback list.
-------------------------------- 
* (6) - The displayname (given in Admin App) from the called waiting queue
* (7) - The caller name | In case the number get resolved over the pbx reverse lookup, the name is displayed here.
* (8) - The caller number | In case the number called multiple, the call count will be displayed in brackets beside the number.
* (9) - Timestamp of the last call from this number
* (10) - In case an Agent starts a callback from the app, the call is highlighted and the agentname is placed here.
* (11) - In case a callback could not be close the case or the caller was not reachable, a comment to the call cloud be placed here.
* (12) - Actions: (Telephone Handset) -> starts the call with your choosen phone application in myApps. (Delete Button) -> Removes the calls from the callback list.

===Database - automatic cleanup ===
Due to possible extensions in the area of evaluation, the call data is kept in the database. 
The History of calls in Database will be deleted after 90 Days.

==Release Notes==
'''130037 - final''' 
- Startversion 
'''130038 - SR1''' 
- fixed an style issue for iniated callbacks in darkmode 
'''130040 - SR2''' 
- fixed callhandling in the backend service 
- some fixes because of missing callcounters in some scenarios 
- sometimes a call was not pushed in the callbacklist 
- send notify to clients was not performed in some scenarios at the end of a call 
- if no displayname is available, the cgpn is used for it 
'''1300xx - SR3 - not released yet''' 
- sometimes the displayname is presented in a update message from reverselookup. In this case the name was not updated in Callbacklist.

==Contact==
effexx its GmbH 
Obere Industriestraße 8 
57250 Netphen

Peter Stock 
Tel: +49 271 7095-220 
Fax: +49 271 7095-4200 
E-Mail: apps@effexx.com