innovaphone wiki - User contributions [en]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:45:01Z

Swh: /* Applies To */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
**[[Howto:Gigaset-DeskPhone-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-DeskPhone-App - Gigaset - Partner App'']]
 
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central Cloud-Reverse-Proxy. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 (''= realm'00' '')
 
*'''Optional:'''
If you require additional realms for multiple customer master locations, e.g., for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIP 50601 
- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIP 506'''NN'''
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-DeskPhone-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-DeskPhone-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:38:34Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central Cloud-Reverse-Proxy. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 (''= realm'00' '')
 
*'''Optional:'''
If you require additional realms for multiple customer master locations, e.g., for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIP 50601 
- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIP 506'''NN'''
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-DeskPhone-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-DeskPhone-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:34:25Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central Cloud-Reverse-Proxy. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 (''= realm'00' '')
 
*'''Optional:'''
If you require additional realms for multiple customer master locations, e.g., for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’

- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIPS 506'''NN''' with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-DeskPhone-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-DeskPhone-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:17:31Z

Swh: /* Related Articles */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
*'''Optional:'''
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’

- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIPS 506'''NN''' with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-DeskPhone-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-DeskPhone-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:08:39Z

Swh: /* Applies To */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
*'''Optional:'''
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’

- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIPS 506'''NN''' with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:07:27Z

Swh: /* Related Articles */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
*'''Optional:'''
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’

- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIPS 506'''NN''' with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T09:02:24Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
*'''Optional:'''
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’

- Please enter the number '''NN''' of Gigaset masters required 
- up to maximum 50
*musterschuster-a.realm'''NN''' -> SIPS 506'''NN''' with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T08:46:26Z

Swh: /* Applies To */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’
- up to max. -
*musterschuster-a.realm50 -> SIPS 50650 with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T08:43:12Z

Swh: /* Related Articles */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’
- up to max. -
*musterschuster-a.realm50 -> SIPS 50650 with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]
*[[Howto:Gigaset-Feature-Control-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Feature-Control-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T08:37:19Z

Swh: /* Known Issues */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’
- up to max. -
*musterschuster-a.realm50 -> SIPS 50650 with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=

*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App - Gigaset - Partner App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2025-08-25T08:31:51Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP with Gigaset in your central RP. 
*musterschuster-p.innovaphone.com -> SIPS 5061 with 'Check Certificate'
*musterschuster-a.innovaphone.com -> SIP 5060 with ‘Check Certificate’
 
If you need more realms for multiple customer master locations, e.g. for multiple Gigaset apps or instances, the following must also be requested:
 
*musterschuster-a.realm01 -> SIPS 50601 with ‘Check Certificate’
- up to max. -
*musterschuster-a.realm50 -> SIPS 50650 with ‘Check Certificate’

 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '' Set auto update intervall''
| '' <param name="Provisioning.global.Period" value="time in seconds" />''
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

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

2025-08-25T08:19:35Z

Swh: /* Prerequisites */ ... entfernen des SIPS 5062 für musterschuster-a.innovaphone.com ... gemäß Mail zwischen Sven mit Dennis (14.8.2025)

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

==Product Name==

[[File:DECT ProvAPP logo.png|100x100px|dect_provapp_logo.png/|dect_provapp_logo.png/]] [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|gigaset-logo.png/|gigaset-logo.png/]]



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|n870.png/|n870.png/]]</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|n670_mini_multicell_en.png/|n670_mini_multicell_en.png/]]</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.

===Multi-PBX ready===




YES

===Cloud ready===




YES

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

''Wenn die Instanz in der innovaphone myApps Cloud betrieben wird, beantragt bitte via Ticket unter Angabe „Instanz-Nr|Domain-Name“ bei cloud@innovaphone.com die folgenden Freigaben am Cloud-RP:"''

''musterschuster-p.innovaphone.com -> SIPS 5061 mit ‘Check Certificate’''

''musterschuster-a.innovaphone.com -> SIP 5060 mit ‘Check Certificate’''

''Braucht ihr für euren Kunde mehr Realm's für mehrere Kunden-Master-Lokationen, für z.B. mehrere Gigaset APPs oder Instanzen, muss zusätzlich folgendes beantragt werden:''

''musterschuster-a.realm01 -> SIPS 50601 mit ‘Check Certificate’''

''- bis max. -''

''musterschuster-a.realm50 -> SIPS 50650 mit ‘Check Certificate’''

==Versions==


===Compatible innovaphone firmware versions===

* innovaphone V13r3
* innovaphone V14r2
* innovaphone V15r1

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


* Gigaset Provisioning-App - 136100 sr3

* innovaphone V15r1 final
* Gigaset Nx70 V2.61.2

==Configuration==




===Install the App===

===Gigaset - Provisoning - App===

==== innovaphone settings ====
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. If you want to show VoiceMail Messages into Phone Display enter the VoiceMail Number. Also define if reverse proxy should be activated or not. 

==== Gigaset settings ====
'''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. 

==== Directory settings ====
Under Phonebook settings you can activate sync for three different phonebooks. 1.st 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. You can also define Contacts APP ([[#Contacts APP|Howto:Gigaset-Provisioning-App - Gigaset - Partner App#Contacts APP]]) or any other LDAP Directory in paralell.
In addition, you can now select which phone book should be selected on the phonebook key and which on the INT key. You can also select which one should be used for reverse lookup. 

==== Phone number formatting ====
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. 

==== provisioning parameters in XML format ====
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 
 

==== Advanced settings ====
"Reload Gigaset Devices" will be reload all Gigaset Handsets from Devices List and generate a new Provisioning File. Keyword is the APP-Name, which is also inserted into the Devices. Wildcards are allowed. Don't press Save and Send Button, when after Reload "0 Devices" is shown, check the keyword carefully. otherwise it could happen that all your Handsets are deleted and you have to register them again.

if you have Gigaset Feature Control App installed and configured this settings are not longer greyed out. With Gigaset Feature Control App you can set your diversions and presence into PBX. You can also activate or deactivate your group memberships and start or stop your working time recording. Longname will be shown in Info Center and Settings. Shortname is shown on Feature Key if configured.

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|innovaphone_gigasetapp_admin2.0_http.png/|innovaphone_gigasetapp_admin2.0_http.png/
Innovaphone GigasetApp Admin2.0 SIP RVP TLS.png|innovaphone_gigasetapp_admin2.0_sip_rvp_tls.png/|innovaphone_gigasetapp_admin2.0_sip_rvp_tls.png/
</gallery>

{| class="wikitable" style="margin-top:auto;margin-top: 0px;"
|
[[File:Innovaphone gigasetapp http.png|alt=innovaphone_gigasetapp_http|innovaphone_gigasetapp_http.png/|innovaphone_gigasetapp_http.png/]]
|
[[File:Innovaphone gigasetapp sip tls rp.png|alt=innovaphone_gigasetapp_sip_rvp_tls|innovaphone_gigasetapp_sip_tls_rp.png/|innovaphone_gigasetapp_sip_tls_rp.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|innovaphone_gigasetapp_user.png/|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.

From 136097 onwards we added the possibilty to activate Reverse Proxy support for multiple instances directly in the settings. see chapter below.

[[Image:Gigaset-rvp-all.png|gigaset-rvp-all.png/|gigaset-rvp-all.png/]]

===Multiple Instances===
From 136097 onwards we added the possibilty to activate Reverse Proxy support for multiple instances directly in the settings.

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. 5062, but the reverse proxy can only be reached via port 5060/5061. An outbound proxy must also be distributed to the DECT Manager. Therefore you can now activate ''"Enable Reverse Proxy Support"'' and enter seperate Ports for Connecting to the Reverse Proxy and connecting from Reverse Proxy to the APP Platform. The Port must be unique and must not be assigned twice. Don't forget to forward the Port in Reverse Proxy from 5060/5061 to your configured Port.

[[File:Innovaphone gigasetapp rp-port example.png|innovaphone_gigasetapp_rp-port_example.png/|innovaphone_gigasetapp_rp-port_example.png/]]
 

=== Directory Settings ===
After activating directory synchronisation you have the possibility to activate and configure thre sources simultaneously: innovaphone LDAP directory, any other LDAP directory and innovaphone myContacts APP.

[[File:Innovaphone gigasetapp ldaplokal.png|frameless|580x580px|innovaphone_gigasetapp_ldaplokal.png/|innovaphone_gigasetapp_ldaplokal.png/]]

fill in the needed data like host, Port and Credentials.

After all phonebooks, and maybee Gigaset Feature Controll App, are configured you can choose which ones will be used for phonebook key, INT key and Reverse Lookup.

[[File:Innovaphone gigasetapp directory settings.png|frameless|580x580px|innovaphone_gigasetapp_directory_settings.png/|innovaphone_gigasetapp_directory_settings.png/]]

===Contacts APP===
Use innovaphone Contacts App for forward search and reverse lookup from Gigaset Handsets
====Requirements====
* Gigaset firmware V2.59 or higher (supports new provisioning parameter <param name="LDAPDir.0.BlankFilter" value="(metaSearchNumber=0*)"/> )
* for Reverse Lookup number formatting in Contacts has to be '''without''' +49 - for example 02871 91-0 instead of +49 2871 91-0 otherwise reverse lookup will not work. For search and dialing this doesn't matter..
====Configuration====
* Host : apps.company.tld (address of the AP)
* Port : 636
* TLS : yes/no
* LDAP : dc=entries
* Username : [from PBX-Manager / AP Contacts / Change Configuration / User (LDAP)]
* Password : [from PBX-Manager / AP Contacts / Change Configuration / Password (LDAP)]
* Name filter : (cn=%) or (|(cn=%)(sn=%))
* Number filter : (metaSearchNumber=%)
* number format : +* (default) or 0*
* all other entries as shown in below screenshot are preconfigured

[[File:Innovaphone gigasetapp mycontacts.png|1182x1182px|innovaphone_gigasetapp_mycontacts.png/|innovaphone_gigasetapp_mycontacts.png/]]

[[Image:PBX Manager Contacts Parameter.png|750px|pbx_manager_contacts_parameter.png/|pbx_manager_contacts_parameter.png/]] 

===Forward lookup on different Nodes===
In some cases internal PBX Users are in different Nodes. When searching on a Handset for internal PBX Users the Result won't show the Nodeprefix for the Users - therefore the Calls would get lost and not reach the right Destination. For this to work you can either use a Meta Directory or an innovaphone PBX for use as Phone Book only.

Use of an innovaphone PBX as Phone Book:
You can use an additional innovaphone PBX which replicates all the Users from the Master PBX with type "Active Directory Replication", this way you're able to define the nodes within the extension field.
It's important here to also define the guid for the Users, this Configuration will look like this then:

[[Image:gigaset-forward-lookup-nodes.png|750px|gigaset-forward-lookup-nodes.png/|gigaset-forward-lookup-nodes.png/]] 

At last: You have to set the phone book PBX as your target phone book at the phone book settings

=== Advanced settings ===

* Reload Gigaset devices : this can e.g. become necessary if the app has been uninstalled and is reinstalled, to collect all previously configured handsets from the system. Devices will be reloaded and provisioning file new generated. Keyword is the APP-Name, which is also inserted into the Devices. Wildcards are allowed. Don't press Save and Sending Button, when after Reload "0 Devices" is shown. check the keyword carefully. otherwise it could happen that all your Handsets are deleted and you have to register them again.

Gigaset Feature Control APP connection : with Gigaset Control App you can set your diversions and presence into PBX.\n You can also activate or deactivate your group memberships and start or stop your working time recording.\n Longname will be shown in Info Center and Settings. Shortname is shown on Feature Key if configured.

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

=== 136100 sr3 ===
'''Note: The app must be opened after migration, save configuration and closed, after that open again!'''

==== Innovaphone System Settings ====

* Mailbox configuration

==== Gigaset System Settings ====

* SIP LED status display
* ProxyPort for SIP connection via reverse proxy or multiple instances

==== Directory settings ====

* Change of "Required" definition in phonebook entry input fields
* Phonebook contacts App
* Multiple selection of phonebooks
* configuration of phonebook and INT key

==== Advanced settings ====

* Loading already provisioned phones into the app database
* Connection to the Gigaset Feature Control App

and bugfixing and feature enhancements

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

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

===136017 - final===
- Startversion 

==Known Problems==

=== Provisioning via http does not work since Gigaset Firmware V2.62.1 ===
use Provisioning via SIP instead.

=== no MWI for new VoiceMails ===
Provisioning Parameter is missing, add to own provisioning parameters:

<param name=" SipProvider.0.MWISubscription " value="1"/>

=== Same SIP Port/Protocol for PBX and APP-Plattform via Reverse Proxy ===
is not working, due to load optimizations of Reverse Proxy. choose 5061/TLS for PBX and 5060/TCP for App Plattform.

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

===Reverse Lookup is not Working for LDAP===
As an Workaround, delete international and national dialing location from number formatting parameters.

=== Provisioning option not available in Users Admin when giving Profile app a custom name ===
When the name or long name of your profile app PBX object differs from the default names "Profile" (long name) and "profile" (name), you won't have the option to select "Gigaset - Gigaset Provisioning" as the manufacturer of the phone if you try to create new phone registrations via Users Admin. 

== Related Articles ==
*[[Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments| Howto:Using Gigaset-Provisioning-App in innovaphone myApps cloud environments]]

==Contact==
Gigaset Technologies 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:MyApps Cloud - FAQ

2025-03-10T17:35:37Z

Swh: /* Is Let's Encrypt supported in the cloud? */ Federation need HTTP Challenge with Port 80

[[Category:MyApps Cloud|FAQ|{{PAGENAME}}]]

Frequently Asked Questions

{{HOWTOMOD13r3 Translation Info}}

__toc__

== Applies To ==
This information applies to
* innovaphone myApps Cloud from version 13r1 and higher
* innovaphone myApps Cloud STANDARD and PREMIUM

=== The purpose of the myApps Cloud ===
Virtualization via highly available and redundant cluster systems are creating a variety of new opportunities when providing efficient IT services.
Therefore innovaphone AG provides the myApps Cloud service, as a flexible UCaaS platform. Consequently, the innovaphone myApps Cloud allows certified partners to offer and integrate such services without investing in an own infrastructure.

The service is available in two different service variations - the STANDARD and the PREMIUM version. The following table reveals the differences:

{| class="wikitable" border="1" cellspacing="0" cellpadding="10" style="text-align:center; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
!
! innovaphone myApps Cloud STANDARD
! innovaphone myApps Cloud PREMIUM
|-
| style="text-align:left;" | '''Datacenter:'''
|
|
|-
| style="text-align:right;" | Geo-Redundancy:
| active-passive
| active-active
|-
| style="text-align:right;" | Recovery time:
| hours (manual interaction needed)
| minutes (fully-automated)
|-
| style="text-align:right;" | Autonomy time on power failure:
| 1 day
| 5 days
|-
| style="text-align:right;" | Service delivery:
| within 24 h
| within 24 h
|-
| style="text-align:right;" | Fixed contract term:
| none
| none
|-
| style="text-align:left;" | '''Infrastructure-Support-Service:'''    
|
|
|-
| style="text-align:right;" | Acceptance:
| during business hours (optional enhancements possible)
| 24x7
|-
| style="text-align:right;" | Reaction time:
| best effort
| 2h
|-
|}

== FAQs ==
=== System, Services and Features ===
==== What are the typical application scenarios for the above product versions?====
The myApps Cloud STANDARD was designed for customers with average requirements (typically between 5 and 100, max. 250 ports, up to approx. 5 SIP trunks per PBX and with a moderate IVR usage and call volume). The PREMIUM platform was designed for large systems with customized or explicitly high requirements (load sharing mechanisms, availavillity, recovery time, e.g. for contact center scenarios, or similar).

==== What exactly does the extended 24x7 service of the myApps Cloud PREMIUM include and how does it differ from standard cloud support?====
* in the frame of the myApps Cloud STANDARD a technician is available per email during normal business hours, Monday to Friday between 9:00 a.m. and 5:00 p.m.
* As part of the myApps Cloud PREMIUM, innovaphone offers the extended 24x7 infrastructure supporte hotline.
** This is an emergency service that can be used by certified innovaphone technicians.
** The hotline operates outside normal business hours, on weekends and on public holidays.
** The service is aimed exclusively for cloud instances in operation.
** This support is limited to problems in the areas of infrastructure and virtualization platform (i.e., no installation and configuration support in this time-frame).

==== In which languages is the cloud support and hotline available?====
This service is available in German and English.

==== Where (geographically) is the service being produced?====
Both product versions are implemented in different data centers in Germany. The two data centers used for the myApps Cloud PREMIUM are approximately 10 km apart from each other.

==== Are there any special requirements to access the myApps Cloud, e.g. from a standard home Internet connection or Home Office?====
There are no specific requirements. In most cases a standard Internet access will do fine. Specific considerations in regards to bandwidth consumption, please see below.

==== Is Let's Encrypt supported in the cloud?====
In the myApps Cloud we work with 'purchased' *.innovaphone.com certificates - therefore Let's Encrypt is not necessary there. In addition, no Let's Encrypt App should be started on the myApps Cloud instances. This would change the default values for the cloud and cause massive registration problems.

There will be an exception with '''15r1''' in the scope of the '''federation'''.

* This will require the Let' Encrypt app on the app platform (''more details soon in a separate wiki article'').
* However, it is already known that special entries will be required on the reverse proxy.
* In this case, please open a ticket with the cloud team.

==== How much bandwidth is being consumed through the different services?====
Bandwidth consumption always depends on a series of different factors. Below, we will provide some rough estimations, and a link to further readings.
* '''Voice''' - Mainly depending on the codec in use and packet size. The average data rate should not exceed 70kbps. Further readings [http://wiki.innovaphone.com/i.php?8228#Codecs here].Note: All innovaphone devices support the ICE protocol, which is a technique to find the most direct way for two devices to talk to each other. If properly applied, this technique allows to maintain network internal calls inside the LAN. Therefore, no external bandwidth must be considered, for such cases. Further readings [http://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_ICE here].
* '''Video''' - Mainly depending on resolution and frame rate. The average data rate should not exceed 350kbps. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps_platform_services#Video_capture here].
* '''Application Sharing''' - The maximum data rate should be 500kbps. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps_platform_services#Application_sharing here].
* '''Idle Bandwidth''' - The average data rate, including the synchronization of presence information should be below 1 kbps, and therefor negligible in most cases. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r2:Concept_myApps#Idle_Bandwidth here]

==== What protocols are used, to access the myApps Cloud, what ports are used?====
The myApps Cloud is relying on standard protocols. Phones and the myApps Client are using the following protocols to access the cloud (those should be usable through the local NAT router):
* '''http/https''' with ports 80, 443
* '''SIP/SIPS''' with ports 5060, 5061
* '''H.323 with''' ports 1720, 1300
* '''LDAP/LDAPS''' with ports 389, 636
* '''STUN/TURN/ICE''' Phones generally use this mechanism to discover its public IP address, when it is located behind a NAT/Firewall.

==== What is the max. upper limit of supported ports / amount of branch offices / number of SIP trunks for a myApps Cloud installation?====
The myApps Cloud concept is based on innovaphone’s highly modular technology. Therefore, it can easily be adapted to very large projects or highly specific requirements - especially when using the PREMIUM plattform. Thus, a “hard” upper limit does not exist. With default configurations on the STANDARD plattform, the myApps Cloud instance is set to serve installations with up to 100 users. For installations larger than this, the responsible reseller may discuss specific project requirements with our presales department.

==== Is it possible to use FAX on the myApps Cloud PBX?====
Yes, you can use FAX on the myApps Cloud platform, however it should be clearly understood to what degree the SIP provider does support T.38 (Suggestion: Clearly ask your SIP provider, if his network will convert an audio fax to T.38).In general, we distinguish between two cases:
* '''Audio Fax''': In case the SIP carrier does not convert faxes to T.38, an additional hardware DSP is needed to do this job. Therefore, the use of one of our hardware devices with fax interface and a DSPs must be physically available (meaning, purchase or rent the respective hardware device, e.g. IP29-x). Further, the necessary licenses shall be configured via the Devices App > Software Rental:
** Fax License (or UC License, which already contains Fax License), according to the number of users.
** PBX Port License is needed.
* '''T.38 through SIP provider''': In Case a FAX call is converted to T.38 through the SIP carrier. This method is supported by the FAX interface of the myApps Cloud PBX without additional hardware. In this case, the following licenses shall be configured via the Devices App > Software Rental:
** At least one PBX Port License is needed
** Fax License (or UC License, which already contains Fax License), according to the number of users.

==== Which SIP trunks do you support in the cloud?====
In principle, we support all certified SIP provider, for which a profile is available in the innovaphone PBX. For your reference, please check [http://wiki.innovaphone.com/index.php?title=Category:Automated_SIP_Tests here].Further, just verify:
* '''Termination''' - The SIP trunk is generally terminated directly on the Cloud PBX. Therefore, it must be ensured that the SIP provider is willing to terminate the trunk on the respective data center (at this moment locations in Germany only).
* '''Authentication''' - It must be ensured that the authentication to a SIP trunk is done with registration via username and password (not through IP address).
* '''Workaround''' - In case of issues with the above topics, a SIP trunk may be terminated locally, at the customers premises, through a gateway. In the simplest case, the termination might be done on a innovaphone FAX gateway, such as for example the IP29-2.
* '''Exceptions''' - Some SIP trunks have special behaviors in a hosted cloud environment, which we describe in the following, according to our knowledge:
** '''Deutschland-LAN''' - Due to security reasons, the provider Deutsche Telekom has limited the product to the use of a maximum of 5 simultaneous TCP sessions from a single IP address. Therefore this product is not suitable for hosting scenarios and consequently it is not supported by the myApps Cloud platform. Since the beginning of 2022, the Deutsche Telekom has discontinued this product. Alternative products are available from the same provider.

=== Order-Process and Pricing ===
==== Who can order a myApps Cloud Instance?====
Basically, cloud instances are only ordered and operated through certified partners. This means that an end customer should place an order through a certified partner. The partner then places the order at innovaphone. There are some special cases in which exceptions are made - with the partner's involvement.

==== Is there a minimum contract term required to operate a myApps Cloud Instance?====
No, none of our cloud products requires a fixed contract term.

==== How is the order process, specifically for myApps Cloud PREMIUM?====
The ordering process corresponds to the standard ordering process of the myApps Cloud service and is done through our contract portal. All you have to do is select the PREMIUM contract, when ordering. The installation link is usually provided Monday to Friday within 24 hours.

==== What is the price for the myApps Cloud Service?====
myApps Cloud installations are calculated according to price list.
* on the PREMIUM environment the 24x7 infrastructure support license must be included (mandatory) and SMB licenses are excluded.
* on the STANDARD plattform, the 24x7 infrastructure support is optional.

=== Install and Provisioning ===
==== How does the Installation of the myApps Cloud work?====
After innovaphone received an order for a cloud instance, the configuration will be generated and the partner receives an URL for the installation process. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:MyApps_Cloud:_Installation here].

==== How does the regular, day-to-day access to the myApps Cloud work?====
There are many ways to access and work with the myApps Cloud platform. Below a small selection of possibilities:
* '''Phones''' - after the installation, innovaphone desk phones will connect automatically through a corporate LAN and the internet to the myApps Cloud. No specific actions from the user are required.
* '''myApps Communication Client''' - This software does exist as a native client for various operating Systems, such as Windows, iOS, Android, etc. Once installed and under normal operation condition, the application opens and connects itself automatically to the cloud platform. The myApps Client might be started through standard browsers as well. In this case, the user has to identify himself through username and password (and Two-factor authentication by email). Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps here].

==== Can phones be connected (rollout) to the myApps Cloud PBX without using the innovaphone provisioning process?====
No, specifically in the Cloud, the provisioning of devices (phones, gateways) has to be realized trough the innovaphone provisioning process.

=== Operations ===
==== Is it possible to generate a backup of an entire myApps Cloud Instance?====
The configuration of a regular backup to an external storage is possible and can be configured easily, through the Devices App.
* It is highly recommendable, to generate such a regular backup on an external storage device. The innovaphone GTC refers to this issue as "Customers Obligation" in chapter 7.6. [https://www.innovaphone.com/en/general-terms-and-conditions.html#j here].
* Please do not store backups on the App Platform of the respective Cloud Instance, but on an external storage. Thus, in the unlikely case of an instance failure, the backup is most probably accessible.

==== As a partner, can I restart my App-Platform VM by myself after a shutdown? ====
No - cloud VMs must always be restarted by the innovaphone cloud team.

* If this becomes necessary outside our business hours (9 a.m. - 5 p.m.) or at the weekend (Sat + Sun)
** AND you have agreed appropriate SLAs with your end-customers
** you can order the innovaphone infrastructure service (24x7) optionally in our STANDARD Cloud product.
*** Simply add the licence under Devices > Rental > Configure licences > Cloud Infrastructure License - Start
*** The Cloud team will then contact you via a ticket regarding the modalities
* In the PREMIUM Cloud product, the innovaphone infrastructure service is already included by default .

==== Is there a Disaster-Recovery-Plan and what Recovery-Time is expected?====
Yes, we have a High-Availability-, Backup- and Disaster-Recovery-Concept, with the following specifics:
* High-Availability / Multi-Server redundancy trough ''' Operational-Datacenters''' in Germany - currently based on vSphere™ technology from VMware®.
* System backups to '''a remote Backup-Datacenter''' in Germany.
* The expected Recovery-time is depending on the used product version:
** In case if STANDARD, a Recovery-Time of 4-5 hours is expected.
** For PREMIUM, with a fully automated recovery, we are expecting a recovery within seconds.
** General information on this can also be found in our '''GT&C'''. [https://www.innovaphone.com/en/general-terms-and-conditions.html#j here]

=== External connection through standard interfaces ===
==== Can we use '''SOAP''' to connect to the myApps PBX platform in the Cloud?====
Yes, this is possible. As underlying transport mechanism SOAP is generally using HTTPS (further readings [http://wiki.innovaphone.com/index.php?title=Reference:SOAP_API here]). In case of the myApps Cloud service, '''HTTPS''' is the only option to access the PBX. We recommend to create a specific account to give the SOAP application (limited) access to the system (In most scenario’s a User Object / User account in the PBX with delegated rights - for security reasons as less as possible - is preferred and will fit, depending what will be done through the SOAP application).

==== Can we use '''TAPI''' to connect to the myApps PBX platform in the Cloud?====
Yes, same as with an on-premise system, the myApps Cloud PBX supports a TAPI interface. Call control via the TAPI interfaces is possible. Details, please check [http://wiki.innovaphone.com/index.php?title=Course12:Advanced_-_TAPI here]

=== Tracking and Tracing inside the myApps Cloud ===
==== Is it possible to write Wireshark / PCAP traces to an external URL?====
Yes, there are basically three options:
* you can write PCAP trace to a specified, external URL. Details, please check [http://wiki.innovaphone.com/index.php?title=Howto:Pcap here] and [http://wiki.innovaphone.com/index.php?title=Reference12r1:Maintenance/Diagnostics/Tracing here]. The URL is expected to be a folder on any standard WebDAV drive.
* it is possible to store the trace files on Files App, on the respective App Platform. Please keep in mind, that this App is not a file server. File size should be limited to the available storage.
* Please do not save traces on local Flash Disk of the PBX, as this can lead to a trap of the PBX, when the local Flash disk becomes full.

=== Regulations and compliance ===
*'''General Data Protection Regulation (EU GDPR) 2016/679''': Designed to harmonize data privacy laws across all the EU member countries as well as providing greater protection and rights to individuals. Details, please check [https://gdpr-info.eu/ here]
** innovaphone is taking great care for the privacy of your data. Details please find on our website [http://www.innovaphone.com/en/privacy.html here]. Further, please check [http://www.innovaphone.com/en/general-terms-and-conditions.html#k part K] of our general terms and conditions.

*'''Directive (EU) 2018/1972''': Adopted by the European Union in December 2018 to set-up a European Electronic Communications Code (EECC). Details, please check [http://www.europeansources.info/record/directive-eu-2018-1972-establishing-the-european-electronic-communications-code/ here]
** No phone lines or SIP Trunks are part of the myApps Cloud service. Thus, each innovaphone partner is obliged to verify jointly with the selected SIP provider, if this regulation fully applies.

Howto:MyApps Cloud - FAQ

2025-03-10T17:07:22Z

Swh: /* Operations */ order - better add of the infrastructure support license

[[Category:MyApps Cloud|FAQ|{{PAGENAME}}]]

Frequently Asked Questions

{{HOWTOMOD13r3 Translation Info}}

__toc__

== Applies To ==
This information applies to
* innovaphone myApps Cloud from version 13r1 and higher
* innovaphone myApps Cloud STANDARD and PREMIUM

=== The purpose of the myApps Cloud ===
Virtualization via highly available and redundant cluster systems are creating a variety of new opportunities when providing efficient IT services.
Therefore innovaphone AG provides the myApps Cloud service, as a flexible UCaaS platform. Consequently, the innovaphone myApps Cloud allows certified partners to offer and integrate such services without investing in an own infrastructure.

The service is available in two different service variations - the STANDARD and the PREMIUM version. The following table reveals the differences:

{| class="wikitable" border="1" cellspacing="0" cellpadding="10" style="text-align:center; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
!
! innovaphone myApps Cloud STANDARD
! innovaphone myApps Cloud PREMIUM
|-
| style="text-align:left;" | '''Datacenter:'''
|
|
|-
| style="text-align:right;" | Geo-Redundancy:
| active-passive
| active-active
|-
| style="text-align:right;" | Recovery time:
| hours (manual interaction needed)
| minutes (fully-automated)
|-
| style="text-align:right;" | Autonomy time on power failure:
| 1 day
| 5 days
|-
| style="text-align:right;" | Service delivery:
| within 24 h
| within 24 h
|-
| style="text-align:right;" | Fixed contract term:
| none
| none
|-
| style="text-align:left;" | '''Infrastructure-Support-Service:'''    
|
|
|-
| style="text-align:right;" | Acceptance:
| during business hours (optional enhancements possible)
| 24x7
|-
| style="text-align:right;" | Reaction time:
| best effort
| 2h
|-
|}

== FAQs ==
=== System, Services and Features ===
==== What are the typical application scenarios for the above product versions?====
The myApps Cloud STANDARD was designed for customers with average requirements (typically between 5 and 100, max. 250 ports, up to approx. 5 SIP trunks per PBX and with a moderate IVR usage and call volume). The PREMIUM platform was designed for large systems with customized or explicitly high requirements (load sharing mechanisms, availavillity, recovery time, e.g. for contact center scenarios, or similar).

==== What exactly does the extended 24x7 service of the myApps Cloud PREMIUM include and how does it differ from standard cloud support?====
* in the frame of the myApps Cloud STANDARD a technician is available per email during normal business hours, Monday to Friday between 9:00 a.m. and 5:00 p.m.
* As part of the myApps Cloud PREMIUM, innovaphone offers the extended 24x7 infrastructure supporte hotline.
** This is an emergency service that can be used by certified innovaphone technicians.
** The hotline operates outside normal business hours, on weekends and on public holidays.
** The service is aimed exclusively for cloud instances in operation.
** This support is limited to problems in the areas of infrastructure and virtualization platform (i.e., no installation and configuration support in this time-frame).

==== In which languages is the cloud support and hotline available?====
This service is available in German and English.

==== Where (geographically) is the service being produced?====
Both product versions are implemented in different data centers in Germany. The two data centers used for the myApps Cloud PREMIUM are approximately 10 km apart from each other.

==== Are there any special requirements to access the myApps Cloud, e.g. from a standard home Internet connection or Home Office?====
There are no specific requirements. In most cases a standard Internet access will do fine. Specific considerations in regards to bandwidth consumption, please see below.

==== Is Let's Encrypt supported in the cloud?====
In the myApps Cloud we work with 'purchased' *.innovaphone.com certificates - therefore Let's Encrypt is not necessary there. In addition, no Let's Encrypt App should be started on the myApps Cloud instances. This would change the default values for the cloud and cause massive registration problems.

==== How much bandwidth is being consumed through the different services?====
Bandwidth consumption always depends on a series of different factors. Below, we will provide some rough estimations, and a link to further readings.
* '''Voice''' - Mainly depending on the codec in use and packet size. The average data rate should not exceed 70kbps. Further readings [http://wiki.innovaphone.com/i.php?8228#Codecs here].Note: All innovaphone devices support the ICE protocol, which is a technique to find the most direct way for two devices to talk to each other. If properly applied, this technique allows to maintain network internal calls inside the LAN. Therefore, no external bandwidth must be considered, for such cases. Further readings [http://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_ICE here].
* '''Video''' - Mainly depending on resolution and frame rate. The average data rate should not exceed 350kbps. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps_platform_services#Video_capture here].
* '''Application Sharing''' - The maximum data rate should be 500kbps. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps_platform_services#Application_sharing here].
* '''Idle Bandwidth''' - The average data rate, including the synchronization of presence information should be below 1 kbps, and therefor negligible in most cases. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r2:Concept_myApps#Idle_Bandwidth here]

==== What protocols are used, to access the myApps Cloud, what ports are used?====
The myApps Cloud is relying on standard protocols. Phones and the myApps Client are using the following protocols to access the cloud (those should be usable through the local NAT router):
* '''http/https''' with ports 80, 443
* '''SIP/SIPS''' with ports 5060, 5061
* '''H.323 with''' ports 1720, 1300
* '''LDAP/LDAPS''' with ports 389, 636
* '''STUN/TURN/ICE''' Phones generally use this mechanism to discover its public IP address, when it is located behind a NAT/Firewall.

==== What is the max. upper limit of supported ports / amount of branch offices / number of SIP trunks for a myApps Cloud installation?====
The myApps Cloud concept is based on innovaphone’s highly modular technology. Therefore, it can easily be adapted to very large projects or highly specific requirements - especially when using the PREMIUM plattform. Thus, a “hard” upper limit does not exist. With default configurations on the STANDARD plattform, the myApps Cloud instance is set to serve installations with up to 100 users. For installations larger than this, the responsible reseller may discuss specific project requirements with our presales department.

==== Is it possible to use FAX on the myApps Cloud PBX?====
Yes, you can use FAX on the myApps Cloud platform, however it should be clearly understood to what degree the SIP provider does support T.38 (Suggestion: Clearly ask your SIP provider, if his network will convert an audio fax to T.38).In general, we distinguish between two cases:
* '''Audio Fax''': In case the SIP carrier does not convert faxes to T.38, an additional hardware DSP is needed to do this job. Therefore, the use of one of our hardware devices with fax interface and a DSPs must be physically available (meaning, purchase or rent the respective hardware device, e.g. IP29-x). Further, the necessary licenses shall be configured via the Devices App > Software Rental:
** Fax License (or UC License, which already contains Fax License), according to the number of users.
** PBX Port License is needed.
* '''T.38 through SIP provider''': In Case a FAX call is converted to T.38 through the SIP carrier. This method is supported by the FAX interface of the myApps Cloud PBX without additional hardware. In this case, the following licenses shall be configured via the Devices App > Software Rental:
** At least one PBX Port License is needed
** Fax License (or UC License, which already contains Fax License), according to the number of users.

==== Which SIP trunks do you support in the cloud?====
In principle, we support all certified SIP provider, for which a profile is available in the innovaphone PBX. For your reference, please check [http://wiki.innovaphone.com/index.php?title=Category:Automated_SIP_Tests here].Further, just verify:
* '''Termination''' - The SIP trunk is generally terminated directly on the Cloud PBX. Therefore, it must be ensured that the SIP provider is willing to terminate the trunk on the respective data center (at this moment locations in Germany only).
* '''Authentication''' - It must be ensured that the authentication to a SIP trunk is done with registration via username and password (not through IP address).
* '''Workaround''' - In case of issues with the above topics, a SIP trunk may be terminated locally, at the customers premises, through a gateway. In the simplest case, the termination might be done on a innovaphone FAX gateway, such as for example the IP29-2.
* '''Exceptions''' - Some SIP trunks have special behaviors in a hosted cloud environment, which we describe in the following, according to our knowledge:
** '''Deutschland-LAN''' - Due to security reasons, the provider Deutsche Telekom has limited the product to the use of a maximum of 5 simultaneous TCP sessions from a single IP address. Therefore this product is not suitable for hosting scenarios and consequently it is not supported by the myApps Cloud platform. Since the beginning of 2022, the Deutsche Telekom has discontinued this product. Alternative products are available from the same provider.

=== Order-Process and Pricing ===
==== Who can order a myApps Cloud Instance?====
Basically, cloud instances are only ordered and operated through certified partners. This means that an end customer should place an order through a certified partner. The partner then places the order at innovaphone. There are some special cases in which exceptions are made - with the partner's involvement.

==== Is there a minimum contract term required to operate a myApps Cloud Instance?====
No, none of our cloud products requires a fixed contract term.

==== How is the order process, specifically for myApps Cloud PREMIUM?====
The ordering process corresponds to the standard ordering process of the myApps Cloud service and is done through our contract portal. All you have to do is select the PREMIUM contract, when ordering. The installation link is usually provided Monday to Friday within 24 hours.

==== What is the price for the myApps Cloud Service?====
myApps Cloud installations are calculated according to price list.
* on the PREMIUM environment the 24x7 infrastructure support license must be included (mandatory) and SMB licenses are excluded.
* on the STANDARD plattform, the 24x7 infrastructure support is optional.

=== Install and Provisioning ===
==== How does the Installation of the myApps Cloud work?====
After innovaphone received an order for a cloud instance, the configuration will be generated and the partner receives an URL for the installation process. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:MyApps_Cloud:_Installation here].

==== How does the regular, day-to-day access to the myApps Cloud work?====
There are many ways to access and work with the myApps Cloud platform. Below a small selection of possibilities:
* '''Phones''' - after the installation, innovaphone desk phones will connect automatically through a corporate LAN and the internet to the myApps Cloud. No specific actions from the user are required.
* '''myApps Communication Client''' - This software does exist as a native client for various operating Systems, such as Windows, iOS, Android, etc. Once installed and under normal operation condition, the application opens and connects itself automatically to the cloud platform. The myApps Client might be started through standard browsers as well. In this case, the user has to identify himself through username and password (and Two-factor authentication by email). Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps here].

==== Can phones be connected (rollout) to the myApps Cloud PBX without using the innovaphone provisioning process?====
No, specifically in the Cloud, the provisioning of devices (phones, gateways) has to be realized trough the innovaphone provisioning process.

=== Operations ===
==== Is it possible to generate a backup of an entire myApps Cloud Instance?====
The configuration of a regular backup to an external storage is possible and can be configured easily, through the Devices App.
* It is highly recommendable, to generate such a regular backup on an external storage device. The innovaphone GTC refers to this issue as "Customers Obligation" in chapter 7.6. [https://www.innovaphone.com/en/general-terms-and-conditions.html#j here].
* Please do not store backups on the App Platform of the respective Cloud Instance, but on an external storage. Thus, in the unlikely case of an instance failure, the backup is most probably accessible.

==== As a partner, can I restart my App-Platform VM by myself after a shutdown? ====
No - cloud VMs must always be restarted by the innovaphone cloud team.

* If this becomes necessary outside our business hours (9 a.m. - 5 p.m.) or at the weekend (Sat + Sun)
** AND you have agreed appropriate SLAs with your end-customers
** you can order the innovaphone infrastructure service (24x7) optionally in our STANDARD Cloud product.
*** Simply add the licence under Devices > Rental > Configure licences > Cloud Infrastructure License - Start
*** The Cloud team will then contact you via a ticket regarding the modalities
* In the PREMIUM Cloud product, the innovaphone infrastructure service is already included by default .

==== Is there a Disaster-Recovery-Plan and what Recovery-Time is expected?====
Yes, we have a High-Availability-, Backup- and Disaster-Recovery-Concept, with the following specifics:
* High-Availability / Multi-Server redundancy trough ''' Operational-Datacenters''' in Germany - currently based on vSphere™ technology from VMware®.
* System backups to '''a remote Backup-Datacenter''' in Germany.
* The expected Recovery-time is depending on the used product version:
** In case if STANDARD, a Recovery-Time of 4-5 hours is expected.
** For PREMIUM, with a fully automated recovery, we are expecting a recovery within seconds.
** General information on this can also be found in our '''GT&C'''. [https://www.innovaphone.com/en/general-terms-and-conditions.html#j here]

=== External connection through standard interfaces ===
==== Can we use '''SOAP''' to connect to the myApps PBX platform in the Cloud?====
Yes, this is possible. As underlying transport mechanism SOAP is generally using HTTPS (further readings [http://wiki.innovaphone.com/index.php?title=Reference:SOAP_API here]). In case of the myApps Cloud service, '''HTTPS''' is the only option to access the PBX. We recommend to create a specific account to give the SOAP application (limited) access to the system (In most scenario’s a User Object / User account in the PBX with delegated rights - for security reasons as less as possible - is preferred and will fit, depending what will be done through the SOAP application).

==== Can we use '''TAPI''' to connect to the myApps PBX platform in the Cloud?====
Yes, same as with an on-premise system, the myApps Cloud PBX supports a TAPI interface. Call control via the TAPI interfaces is possible. Details, please check [http://wiki.innovaphone.com/index.php?title=Course12:Advanced_-_TAPI here]

=== Tracking and Tracing inside the myApps Cloud ===
==== Is it possible to write Wireshark / PCAP traces to an external URL?====
Yes, there are basically three options:
* you can write PCAP trace to a specified, external URL. Details, please check [http://wiki.innovaphone.com/index.php?title=Howto:Pcap here] and [http://wiki.innovaphone.com/index.php?title=Reference12r1:Maintenance/Diagnostics/Tracing here]. The URL is expected to be a folder on any standard WebDAV drive.
* it is possible to store the trace files on Files App, on the respective App Platform. Please keep in mind, that this App is not a file server. File size should be limited to the available storage.
* Please do not save traces on local Flash Disk of the PBX, as this can lead to a trap of the PBX, when the local Flash disk becomes full.

=== Regulations and compliance ===
*'''General Data Protection Regulation (EU GDPR) 2016/679''': Designed to harmonize data privacy laws across all the EU member countries as well as providing greater protection and rights to individuals. Details, please check [https://gdpr-info.eu/ here]
** innovaphone is taking great care for the privacy of your data. Details please find on our website [http://www.innovaphone.com/en/privacy.html here]. Further, please check [http://www.innovaphone.com/en/general-terms-and-conditions.html#k part K] of our general terms and conditions.

*'''Directive (EU) 2018/1972''': Adopted by the European Union in December 2018 to set-up a European Electronic Communications Code (EECC). Details, please check [http://www.europeansources.info/record/directive-eu-2018-1972-establishing-the-european-electronic-communications-code/ here]
** No phone lines or SIP Trunks are part of the myApps Cloud service. Thus, each innovaphone partner is obliged to verify jointly with the selected SIP provider, if this regulation fully applies.

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T15:20:29Z

Swh: /* Special thanks To */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port ... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']]) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:59:56Z

Swh: /* View on the Gigaset Provisioning App */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port ... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']]) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:59:22Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port ... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environments#Known_Issues | ''Known Issues'']]) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:55:35Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port ... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']]) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:11:39Z

Swh:

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:08:26Z

Swh: /* Collection of further possibly helpful screenshots */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:07:45Z

Swh: /* Related Articles */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
*[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:05:33Z

Swh: /* Collection of further possibly helpful screenshots */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T14:04:27Z

Swh: /* View on the Gigaset Provisioning App */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP Directory, config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|''http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...'' (if necessary change http: to http'''s''':)
| (... see below [[Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues | ''Known Issues'']])
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T13:55:20Z

Swh: /* Applies To */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App | ''Howto:Gigaset-Provisioning-App'']]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T13:48:45Z

Swh: /* How do I get the necessary SIP ports for my cloud instance forwarded? */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App Howto:Gigaset-Provisioning-App]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com Cloud-Support] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up our necessary host forwardings for SIP in your central RP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 
 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T13:39:17Z

Swh: /* Applies To */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App Howto:Gigaset-Provisioning-App]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com Cloud-Support].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up the necessary host forwarding for SIP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T13:36:46Z

Swh: /* Known Issues */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App Howto:Gigaset-Provisioning-App]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up the necessary host forwarding for SIP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary. [[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T13:33:59Z

Swh: /* Collection of further possibly helpful screenshots */

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App Howto:Gigaset-Provisioning-App]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up the necessary host forwarding for SIP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 

*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 

*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 

=Known Issues=
[[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary.
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

File:Gspapp pwd-rp-mrelay.png

2024-05-17T13:28:43Z

Swh:

File:Gspapp HandsetReg.png

2024-05-17T13:27:42Z

Swh:

File:Gspapp profile.png

2024-05-17T13:26:46Z

Swh:

File:Gspapp LDAP.png

2024-05-17T13:24:50Z

Swh:

File:Gspapp gigasetuser.png

2024-05-17T13:23:39Z

Swh:

File:Gspapp ProvPath.png

2024-05-17T13:22:18Z

Swh:

File:Gspapp config.png

2024-05-17T13:20:33Z

Swh:

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T13:19:14Z

Swh:

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App Howto:Gigaset-Provisioning-App]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.
 

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com] 
*'''Subject:'''
**''Instance-Number|Cloud-Instance-Domain-Name'' - Gigaset-Prov-App Port enabling on RP
*'''Text:
Dear Cloud-Team, 
Please set up the necessary host forwarding for SIP. 
Port 5061 TLS 
(''Port 5060 TCP'' ... only if you wish / you need this port) 
(see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']) ) 
- ''xxx-a(apps).innovaphone.com'' (address of the App Platform) 
- ''xxx-p(pbx).innovaphone.com'' (address of the PBX) 

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031 (your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use your main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username & Password
|
|
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
|https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}
 

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*Navigate to:
**Settings > System > Provisioning and configuration > Provisioning server
*Insert copied provisioning path:
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*Then click on
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!
 

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]
 
 
 
*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 
*Checking the ''auto configuration'' on the Gigaset Integrator
*Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 
*Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 
 

=Known Issues=
[[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are often more stable with 5060.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/'''iPUI''' can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for ''PBX Pwd'', ''Reverse Proxy'' and ''Media Relay'' were automatically set in the user object when the phone was created for the user.
**Set manually if necessary.
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:MyApps Cloud - Using Gigaset-Provisioning-App in innovaphone cloud environments

2024-05-17T10:29:16Z

Swh: Created page with " {{PAGENAME}} __toc__ =DRAFT - this side is under construction= =Disclaimer= Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App. =Applies To= *This article is only intended as a supple..."

[[Category:myApps_Cloud|Gigaset|{{PAGENAME}}]]

__toc__

 
=DRAFT - this side is under construction=
 

=Disclaimer=
Gigaset is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the Gigaset firmware or Gigaset-Provisioning-App itself, or malfunction caused through or due to changes in the Gigaset firmware or Gigaset-Provisioning-App.

=Applies To=
*This article is only intended as a supplement to the detailed configuration description from our colleagues at Gigaset.
**[Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App Howto:Gigaset-Provisioning-App]
*It is often difficult to match the field names in the Gigaset Provisioning App with the names from the innovaphone myApps Cloud.
**We will therefore provide additional example screenshots of the configuration windows with terms from our cloud environment here.
*The Gigaset Provisioning App is a 3rd party product which is not permanently tested by innovaphone for functionality in our cloud environments.
**If you have any '''comments on changes''' or '''errors in this article''', you are welcome to send them in a Ticket to [Mailto:cloud@innovaphone.com].

==Special thanks To==
*The description of the implementation on our innovaphone myApps Cloud platforms was primarily created by our highly esteemed colleague Mr. Martin Pfeiffer from Mehrens.
*He tested this together with another reseller in our cloud on a Gigaset N870 and provided us with his results.

=Be aware of the following=

==How do I get the necessary SIP ports for my cloud instance forwarded?==
Open a Ticket via [Mailto:cloud@innovaphone.com] 
*'''Subject:'''
**Instance-Number|Cloud-Instance-Domain-Name - Gigaset-Prov-App Port enabling on RP 
*'''Text:
**Dear Cloud-Team,
**Please set up the necessary host forwarding for SIP.
**Port 5061 TLS:
***only if you wish/need
***also specify additional Port 5060 TCP
***... see below
****([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
**> xxx-a(apps).innovaphone.com (address of the App Platform)
**> xxx-p(pbx).innovaphone.com (address of the PBX)

==View on the Gigaset Provisioning App==
Recommended configuration
[[Image: gspapp_config.png|thumb|upright=1.0|right|Gigaset-Provisioning-App config]]

{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''innovaphone environment/settings'''
|-
| SIP domain
| cloud.muster.de
| (System Name of PBX)
|-
| SIP server
| cloudmuster-p.innovaphone.com
| (DNS of the PBX)
|-
| Port
| 5061
| (or if needed 5060)
|-
| TLS ''checkbox''
| check
| (or 'uncheck' if you need 5060)
|-
| MasterPBX Name
| master
| ('master' for PBX Name is our cloud default)
|-
| PBX password
| 123xxx78
| ('''NOT''' the admin or domain password)
|-
| Handset display name fallback
| Longname
|
|-
| Reverse-Proxy ''checkbox''
| Enabled
|
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Gigaset environment/settings'''
|-
| Connecting using ''checkbox''
| SIP
|
|-
| Gigaset Integrator MAC-ID
| 549EC2xxxx60'''-4xx7'''
| (from 'state' of the master antenna - possibly named iPUI)
|-
| SIP Realm in App Service
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Port
| 5061
|
|-
| TLS ''checkbox''
| check
|
|-
| Gigaset Integrator Password
| 12x4
| (Password of the Gigaset master antenna for the user 'admin')
|-
| SIP username
| gigasetuser
| (create a user in the PBX with this name)
|-
| SIP password
| 56x8
| (Password of the 'gigasetuser')
|-
| DECT frequency
| Europa
|
|-
| Registration window in seconds
| 300
| (is default)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Phone number formatting'''
|-
| Access code
| 0
|
|-
| Prefix for Int/Ntl/Subsciber
| 00
| 0
|-
| Dialing location
| 49
| 7031(your prefix)
|-
| internal number length
| e.g. 3
| (or '73009' your main phone number)
|-
| wildcarding ''checkbox''
| check
| (or uncheck if you use main phone number)
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Directory settings'''
|-
| Directory synchronisation ''checkbox''
| On
|
|-
| Source
| cloudmuster-p.innovaphone.com
| Port 636
|-
| TLS ''checkbox''
| check
|
|-
| App Platform FQDN
| cloudmuster-a.innovaphone.com
| (DNS of the App-Platform)
|-
| Username
| &
| Password
|-
|- colspan="12" style="font-weight:bold; background-color:#c0c0c0;"
| '''Append your own provisioning parameters in XML format'''
|-
| Copy the 'Provisioning path'
| https://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga... (if necessary change http: to http'''s''':)
| (... see below ([Howto:MyApps_Cloud_-_Using_Gigaset-Provisioning-App_in_innovaphone_cloud_environment#Known Issues ''Known Issues'']))
|-
| '''Save changes''' and start provisioning
| click on the ''floppy disk icon''
|
|-
|}

==View on the settings in the Gigaset Integrator==
Continue on the customer side with the master antenna
[[Image: gspapp_ProvPath.png|thumb|upright=1.0|right|provisioning path, start config]]

*''Navigate to:''
**Settings > System > Provisioning and configuration > Provisioning server
*''Insert copied provisioning path:''
**http'''s'''://cloudmuster-a.innovaphone.com/cloud.muster.de/Giga...
*''Then click on''
**'''Start auto configuration'''
**This must also be done after any changes in the Gigaset Provisioning App!

==Collection of further possibly helpful screenshots==
*Gigasetuser configuration on the PBX
[[Image: gspapp_gigasetuser.png|thumb|upright=1.0|right|gigasetuser, config]]

*LDAP configuration on the PBX
[[Image: gspapp_LDAP.png|thumb|upright=1.0|right|LDAP, config]]
 
 
 
*Checking the auto configuration on the Gigaset Integrator
**Provider profil 'innovaphone'
[[Image: gspapp_profile.png|thumb|upright=1.0|right|check, Gigaset profiles]]
 
 
 
**Handset registration
[[Image: gspapp_HandsetReg.png|thumb|upright=1.0|right|check, handset registration]]
 
 
 
 

=Known Issues=
[[Image: gspapp_pwd-rp-mrelay.png|thumb|upright=1.0|right|user devices, checkboxes]]
*It has been shown in field projects, that although the SIP registrations/connections generally work with TLS (5061) ...
**... but they are '''often more stable with 5060'''.
*The provisioning link from the Gigaset Provisioning App is possibly created as an http link ...
**... but it only works in the Gigaset Integrator as an http'''s''' link.
*When provisioning the handsets, the Gigaset MAC/iPUI can be read on the box (you require this with the UsersAdmin).
**If you have many handsets, it can also be done using a standard barcode scanner.
*Check whether the checkboxes for PBX Pwd, Reverse Proxy and Media Relay were automatically set in the user object when the phone was created for the user.
**Set manually if necessary.
 

== Related Articles ==
https://wiki.innovaphone.com/index.php?title=Howto:Gigaset-Provisioning-App_-_Gigaset_-_Partner_App

Howto:Deploy Yealink Devices on myApps

2024-04-19T11:02:24Z

Swh:

==Applies To==
This information applies to

* Yealink desk phone T3 series, T4 series, T5 series, VP59
* Yealink conference phone
* Yealink DECT phone



==How to deploy Yealink desk phone on Innovaphone?==
Step 1: Download the Yealink app in “App Store” 
[[Image:APP Store.png]]

Step 2: Create an instance for Yealink 
1. Go to the AP manager -> Installed apps, you can see the “Yealink” in the app list 
2. Click “Add” to create an instance for Yealink app 
3. Enter the name, Domain, Password, and Database password to create 
[[Image:Create instance.png]] 
4. Start the app and instance. 
[[Image:Start APP.png]] 

Step3: Create an object for yealinkphone 
1. Go to the PBX Manager, you can see the instance "yealinkphone" you just created 
2. Click AP "yealinkphone", then click “Add an app” to create an object for "yealinkphone" 
3. Enter the name, SIP and choose the template to create 
[[Image:Create object.png]] 
4. In all apps list, you will see the app object Yealinktest you just created. Add it to the Home screen 
[[Image:Add to home screen.png]] 

Step 4: Customize other device configurations 
1. Go to the Yealinktest, which is the Yealink object you just created 
2. Click the hamburger icon in the upper right corner 
[[Image:Hamburger icon.png]] 
3. Customize other device configurations here 
[[Image:APP configuration.png]] 

Step 5: Configure the desk Phone MAC and account 
1. Go to the “Users Admin”-> “Register Phones”, click “+ New phone registrations” 
[[Image:Register phone.png]] 
2. Select the Yealink 
[[Image:Select Yealink.png]] 
3. Select “master IP Phone” 
[[Image:Select master.png]] 
4. Choose the users you want to assign the phone and enter the MAC of the desk Phone. You can configure multiple phones at once. Then wait and click the "Finish" button 
[[Image:Enter mac.png]] 

Step 6: Factory reset the desk Phone, then the deployment is completed 

==How to deploy Yealink DECT Phone on Innovaphone?==
Step 1: Download the Yealink app in “App Store” 
[[Image:APP Store.png]]

Step 2: Create an instance for Provisioning DECT 
1. Go to the AP manager -> Installed apps, you can see the “Yealink” in the app list 
2. Click “Add” to create an instance for Provisioning DECT 
3. Enter the name, Domain, Password, and Database password to create 
[[Image:Create instance DECT.png]] 
4. Start the app and instance 
[[Image:Start APP DECT.png]] 

Step3: Create an object for Provisioning DECT 
1. Go to the PBX Manager, you can see the instance "provisioningdect" you just created 
2. Click AP "provisioningdect", then click “Add an app” to create an object for Provisioning DECT 
3. Enter the name, SIP, and choose the template to create 
[[Image:Create object DECT.png]] 
4. In all apps list, you will see the app object Yealinktest you just created. Add it to the Home screen 
[[Image:Add to home screen DECT.png]] 

Step 4: Customize other device configurations and MAC for the Provisioning DECT object 
1. Go to the "yltestdect", which is the Provisioning DECT object you just created 
[[Image:Yltestdect.png]] 
2. Click the hamburger icon in the upper right corner 
[[Image:Hamburger icon DECT.png]] 
3. Customize other device configurations and MAC here 
[[Image:APP configuration DECT.png]] 

Step 5: Configure the handset and account for your W90/W80/W70B 
1. Go to the “Users Admin”-> “Register Phones”, click “+ New phone registrations” 
[[Image:Register phone.png]] 
2. Select the YealinkProvisioningDect 
[[Image:Select Yealink DECT.png]] 
3. Select “master IP Phone” 
[[Image:Select master.png]] 
4. Choose the users you want to assign handsets to, and enter the IPUI of the handsets. Then wait and click the "Finish" button 
[[Image:Enter mac DECT.png]] 

Step 6: Factory reset W90/W80/W70B 

Step 7: Connect handset to the W70/W90, then the deployment is completed 
W70B: Go to W70B web portal, under “Handset & VOIP”->” Start Register Handset” 
W90: Go to W90DM web portal, under “Handset & VOIP”->” Register Handset”, click “Add Handset”, and click “Start Register Handset”. (Before this step, we have to ensure W90 base is connected with W90DM) 
Handset: Press OK -> Settings -> Registration -> Register handset and select one base slot to register the handset 
Refer to: 
1. https://support.yealink.com/en/portal/knowledge/show?id=6458b6dab1fa936c57b5674b 
2. https://support.yealink.com/en/portal/knowledge/show?id=6458b6dab1fa936c57b56761 

===Known Problems===
[https://support.yealink.com/en/portal/knowledge/show?id=616e8af9d02500669fc5003e I have DM configured, why can't register the handset to DM?]



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

Howto:MyApps Cloud - FAQ

2024-04-17T13:06:58Z

Swh: /* System, Services and Features */

[[Category:myApps_Cloud|FAQ|{{PAGENAME}}]]

Frequently Asked Questions

{{HOWTOMOD13r3 Translation Info}}

__toc__

== Applies To ==
This information applies to
* innovaphone myApps Cloud from version 13r1 and higher
* innovaphone myApps Cloud STANDARD and PREMIUM

=== The purpose of the myApps Cloud ===
Virtualization via highly available and redundant cluster systems are creating a variety of new opportunities when providing efficient IT services.
Therefore innovaphone AG provides the myApps Cloud service, as a flexible UCaaS platform. Consequently, the innovaphone myApps Cloud allows certified partners to offer and integrate such services without investing in an own infrastructure.

The service is available in two different service variations - the STANDARD and the PREMIUM version. The following table reveals the differences:

{| class="wikitable" border="1" cellspacing="0" cellpadding="10" style="text-align:center; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
!
! innovaphone myApps Cloud STANDARD
! innovaphone myApps Cloud PREMIUM
|-
| style="text-align:left;" | '''Datacenter:'''
|
|
|-
| style="text-align:right;" | Geo-Redundancy:
| active-passive
| active-active
|-
| style="text-align:right;" | Recovery time:
| hours (manual interaction needed)
| minutes (fully-automated)
|-
| style="text-align:right;" | Autonomy time on power failure:
| 1 day
| 5 days
|-
| style="text-align:right;" | Service delivery:
| within 24 h
| within 24 h
|-
| style="text-align:right;" | Fixed contract term:
| none
| none
|-
| style="text-align:left;" | '''Infrastructure-Support-Service:'''    
|
|
|-
| style="text-align:right;" | Acceptance:
| during business hours (optional enhancements possible)
| 24x7
|-
| style="text-align:right;" | Reaction time:
| best effort
| 2h
|-
|}

== FAQs ==

=== System, Services and Features ===
 
*'''Question''': What are the typical application scenarios for the above product versions? '''Answer''': The myApps Cloud STANDARD was designed for customers with average requirements (typically between 5 and 100, max. 250 ports, up to approx. 5 SIP trunks per PBX and with a moderate IVR usage and call volume). The PREMIUM platform was designed for large systems with customized or explicitly high requirements (load sharing mechanisms, availavillity, recovery time, e.g. for contact center scenarios, or similar). 

* '''Question''': What exactly does the extended 24x7 service of the myApps Cloud PREMIUM include and how does it differ from standard cloud support? '''Answer''':
** in the frame of the myApps Cloud STANDARD a technician is available per email during normal business hours, Monday to Friday between 9:00 a.m. and 5:00 p.m.
** As part of the myApps Cloud PREMIUM, innovaphone offers the extended 24x7 infrastructure supporte hotline.
*** This is an emergency service that can be used by certified innovaphone technicians.
*** The hotline operates outside normal business hours, on weekends and on public holidays.
*** The service is aimed exclusively for cloud instances in operation.
*** This support is limited to problems in the areas of infrastructure and virtualization platform (i.e., no installation and configuration support in this time-frame).

*'''Question''': In which languages is the cloud support and hotline available? '''Answer''': This service is available in German and English. 

*'''Question''': Where (geographically) is the service being produced? '''Answer''': Both product versions are implemented in different data centers in Germany. The two data centers used for the myApps Cloud PREMIUM are approximately 10 km apart from each other. 

*'''Question''': Are there any special requirements to access the myApps Cloud, e.g. from a standard home Internet connection or Home Office? '''Answer''': There are no specific requirements. In most cases a standard Internet access will do fine. Specific considerations in regards to bandwidth consumption, please see below. 

*'''Question''': Is Let's Encrypt supported in the cloud? '''Answer''': In the myApps Cloud we work with 'purchased' *.innovaphone.com certificates - therefore Let's Encrypt is not necessary there. In addition, no Let's Encrypt App should be started on the myApps Cloud instances. This would change the default values for the cloud and cause massive registration problems. 

*'''Question''': How much bandwidth is being consumed through the different services? '''Answer''': Bandwidth consumption always depends on a series of different factors. Below, we will provide some rough estimations, and a link to further readings.
** '''Voice''' - Mainly depending on the codec in use and packet size. The average data rate should not exceed 70kbps. Further readings [http://wiki.innovaphone.com/i.php?8228#Codecs here]. Note: All innovaphone devices support the ICE protocol, which is a technique to find the most direct way for two devices to talk to each other. If properly applied, this technique allows to maintain network internal calls inside the LAN. Therefore, no external bandwidth must be considered, for such cases. Further readings [http://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_ICE here].
** '''Video''' - Mainly depending on resolution and frame rate. The average data rate should not exceed 350kbps. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps_platform_services#Video_capture here].
** '''Application Sharing''' - The maximum data rate should be 500kbps. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps_platform_services#Application_sharing here].
** '''Idle Bandwidth''' - The average data rate, including the synchronization of presence information should be below 1 kbps, and therefor negligible in most cases. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r2:Concept_myApps#Idle_Bandwidth here] 

*'''Question''': What protocols are used, to access the myApps Cloud, what ports are used? '''Answer''': The myApps Cloud is relying on standard protocols. Phones and the myApps Client are using the following protocols to access the cloud (those should be usable through the local NAT router):
** '''http/https''' with ports 80, 443
** '''SIP/SIPS''' with ports 5060, 5061
** '''H.323 with''' ports 1720, 1300
** '''LDAP/LDAPS''' with ports 389, 636
** '''STUN/TURN/ICE''' Phones generally use this mechanism to discover its public IP address, when it is located behind a NAT/Firewall. 

*'''Question''': What is the max. upper limit of supported ports / amount of branch offices / number of SIP trunks for a myApps Cloud installation? '''Answer''': The myApps Cloud concept is based on innovaphone’s highly modular technology. Therefore, it can easily be adapted to very large projects or highly specific requirements - especially when using the PREMIUM plattform. Thus, a “hard” upper limit does not exist. With default configurations on the STANDARD plattform, the myApps Cloud instance is set to serve installations with up to 100 users. For installations larger than this, the responsible reseller may discuss specific project requirements with our presales department. 

*'''Question''': Is it possible to use FAX on the myApps Cloud PBX? '''Answer''': Yes, you can use FAX on the myApps Cloud platform, however it should be clearly understood to what degree the SIP provider does support T.38 (Suggestion: Clearly ask your SIP provider, if his network will convert an audio fax to T.38). In general, we distinguish between two cases:
** '''Audio Fax''': In case the SIP carrier does not convert faxes to T.38, an additional hardware DSP is needed to do this job. Therefore, the use of one of our hardware devices with fax interface and a DSPs must be physically available (meaning, purchase or rent the respective hardware device, e.g. IP29-x). Further, the necessary licenses shall be configured via the Devices App > Software Rental:
*** Fax License (or UC License, which already contains Fax License), according to the number of users.
*** PBX Port License is needed.
** '''T.38 through SIP provider''': In Case a FAX call is converted to T.38 through the SIP carrier. This method is supported by the FAX interface of the myApps Cloud PBX without additional hardware. In this case, the following licenses shall be configured via the Devices App > Software Rental:
*** At least one PBX Port License is needed
*** Fax License (or UC License, which already contains Fax License), according to the number of users. 

*'''Question''': Which SIP trunks do you support in the cloud? '''Answer''': In principle, we support all certified SIP provider, for which a profile is available in the innovaphone PBX. For your reference, please check [http://wiki.innovaphone.com/index.php?title=Category:Automated_SIP_Tests here]. Further, just verify: 
** '''Termination''' - The SIP trunk is generally terminated directly on the Cloud PBX. Therefore, it must be ensured that the SIP provider is willing to terminate the trunk on the respective data center (at this moment locations in Germany only). 
** '''Authentication''' - It must be ensured that the authentication to a SIP trunk is done with registration via username and password (not through IP address).
** '''Workaround''' - In case of issues with the above topics, a SIP trunk may be terminated locally, at the customers premises, through a gateway. In the simplest case, the termination might be done on a innovaphone FAX gateway, such as for example the IP29-2. 
** '''Exceptions''' - Some SIP trunks have special behaviors in a hosted cloud environment, which we describe in the following, according to our knowledge:
*** '''Deutschland-LAN''' - Due to security reasons, the provider has limited the product to the use of a maximum of 5 simultaneous TCP sessions from a single IP address, such as our cloud platform (see [https://geschaeftskunden.telekom.de/internet-dsl/tarife/festnetz-internet-dsl/deutschlandlan-sip-trunk/sip-trunk-technische-unterlage product description, section 11.3]). Therefore this product is not suitable for such kind of hosting scenarios and therefore is not supported by the myApps Cloud platform. Alternative products are available from the same provider. 

=== Order-Process and Pricing ===
 
*'''Question''': Who can order a myApps Cloud Instance? '''Answer''': Basically, cloud instances are only ordered and operated through certified partners. This means that an end customer should place an order through a certified partner. The partner then places the order at innovaphone. There are some special cases in which exceptions are made - with the partner's involvement. 

*'''Question''': Is there a minimum contract term required to operate a myApps Cloud Instance? '''Answer''': No, none of our cloud products requires a fixed contract term. 

*'''Question''': How is the order process, specifically for myApps Cloud PREMIUM? '''Answer''': The ordering process corresponds to the standard ordering process of the myApps Cloud service and is done through our contract portal. All you have to do is select the PREMIUM contract, when ordering. The installation link is usually provided Monday to Friday within 24 hours. 

*'''Question''': What is the price for the myApps Cloud Service? '''Answer''': myApps Cloud installations are calculated according to price list.
** on the PREMIUM environment the 24x7 infrastructure support license must be included (mandatory) and SMB licenses are excluded.
** on the STANDARD plattform, the 24x7 infrastructure support is optional. 

=== Install and Provisioning ===
 
*'''Question''': How does the Installation of the myApps Cloud work? '''Answer''': After innovaphone received an order for a cloud instance, the configuration will be generated and the partner receives an URL for the installation process. Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:MyApps_Cloud:_Installation here]. 

*'''Question''': How does the regular, day-to-day access to the myApps Cloud work? '''Answer''': There are many ways to access and work with the myApps Cloud platform. Below a small selection of possibilities:
** '''Phones''' - after the installation, innovaphone desk phones will connect automatically through a corporate LAN and the internet to the myApps Cloud. No specific actions from the user are required.
** '''myApps Communication Client''' - This software does exist as a native client for various operating Systems, such as Windows, iOS, Android, etc. Once installed and under normal operation condition, the application opens and connects itself automatically to the cloud platform. The myApps Client might be started through standard browsers as well. In this case, the user has to identify himself through username and password (and Two-factor authentication by email). Further readings [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_myApps here]. 

*'''Question''': Can phones be connected (rollout) to the myApps Cloud PBX without using the innovaphone provisioning process? '''Answer''': No, specifically in the Cloud, the provisioning of devices (phones, gateways) has to be realized trough the innovaphone provisioning process.
 

=== Operations ===
 
*'''Question''': Is it possible to generate a backup of an entire myApps Cloud Instance? '''Answer''': The configuration of a regular backup to an external storage is possible and can be configured easily, through the Devices App.
** It is highly recommendable, to generate such a regular backup on an external storage device. The innovaphone GTC refers to this issue as "Customers Obligation" in chapter 7.6. [https://www.innovaphone.com/en/general-terms-and-conditions.html#j here].
** Please do not store backups on the App Platform of the respective Cloud Instance, but on an external storage. Thus, in the unlikely case of an instance failure, the backup is most probably accessible.

 
*'''Question''': Is there a Disaster-Recovery-Plan and what Recovery-Time is expected? '''Answer''': Yes, we have a High-Availability-, Backup- and Disaster-Recovery-Concept, with the following specifics:
** High-Availability / Multi-Server redundancy trough ''' Operational-Datacenters''' in Germany - currently based on vSphere™ technology from VMware®. 
** System backups to '''a remote Backup-Datacenter''' in Germany. 
** The expected Recovery-time is depending on the used product version:
*** In case if STANDARD, a Recovery-Time of 4-5 hours is expected.
*** For PREMIUM, with a fully automated recovery, we are expecting a recovery within seconds.
*** General information on this can also be found in our '''GT&C'''. [https://www.innovaphone.com/en/general-terms-and-conditions.html#j here] 
 

=== External connection through standard interfaces ===
 
*'''Question''': Can we use '''SOAP''' to connect to the myApps PBX platform in the Cloud? '''Answer''': Yes, this is possible. As underlying transport mechanism SOAP is generally using HTTPS (further readings [http://wiki.innovaphone.com/index.php?title=Reference:SOAP_API here]). In case of the myApps Cloud service, '''HTTPS''' is the only option to access the PBX. We recommend to create a specific account to give the SOAP application (limited) access to the system (In most scenario’s a User Object / User account in the PBX with delegated rights - for security reasons as less as possible - is preferred and will fit, depending what will be done through the SOAP application). 
*'''Question''': Can we use '''TAPI''' to connect to the myApps PBX platform in the Cloud? '''Answer''': Yes, same as with an on-premise system, the myApps Cloud PBX supports a TAPI interface. Call control via the TAPI interfaces is possible. Details, please check [http://wiki.innovaphone.com/index.php?title=Course12:Advanced_-_TAPI here] 

=== Tracking and Tracing inside the myApps Cloud ===
 
*'''Question''': Is it possible to write Wireshark / PCAP traces to an external URL? '''Answer''': Yes, there are basically three options:
** you can write PCAP trace to a specified, external URL. Details, please check [http://wiki.innovaphone.com/index.php?title=Howto:Pcap here] and [http://wiki.innovaphone.com/index.php?title=Reference12r1:Maintenance/Diagnostics/Tracing here]. The URL is expected to be a folder on any standard WebDAV drive.
** it is possible to store the trace files on Files App, on the respective App Platform. Please keep in mind, that this App is not a file server. File size should be limited to the available storage.
** Please do not save traces on local Flash Disk of the PBX, as this can lead to a trap of the PBX, when the local Flash disk becomes full.

=== Regulations and compliance ===
 
*'''General Data Protection Regulation (EU GDPR) 2016/679''': Designed to harmonize data privacy laws across all the EU member countries as well as providing greater protection and rights to individuals. Details, please check [https://gdpr-info.eu/ here]
** innovaphone is taking great care for the privacy of your data. Details please find on our website [http://www.innovaphone.com/en/privacy.html here]. Further, please check [http://www.innovaphone.com/en/general-terms-and-conditions.html#k part K] of our general terms and conditions. 

*'''Directive (EU) 2018/1972''': Adopted by the European Union in December 2018 to set-up a European Electronic Communications Code (EECC). Details, please check [http://www.europeansources.info/record/directive-eu-2018-1972-establishing-the-european-electronic-communications-code/ here]
** No phone lines or SIP Trunks are part of the myApps Cloud service. Thus, each innovaphone partner is obliged to verify jointly with the selected SIP provider, if this regulation fully applies.

MyApps Cloud - Comparison table

2024-03-19T10:59:29Z

Swh: /* HA concept of both myApps Cloud variants in detail */

[[Category:myApps_Cloud|Comparison|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__

=Applies To=
This information applies to the innovaphone myApps Cloud versions:
*PREMIUM
*STANDARD

=Briefly the facts=

*The main advantages of '''PREMIUM''' over STANDARD environment are:
**the '''fully automated GEOredundancy''' between two '''High-Available Data-Centers'''
*** STANDARD has HA in one Data-Center with manual GEOredundancy
**the '''5-day power blackout protection''' is fully available.
*** STANDARD has one-day power protection
**the '''24x7 cloud infrastructure hotline''' as a default option.
*** STANDARD has this optional
 

{| class="wikitable" border="1" cellspacing="0" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
! style="text-align:center;" | Description
! style="text-align:center;" | Cloud-PREMIUM
! style="text-align:center;" | Cloud-STANDARD
|-
| style="vertical-align:top" | Cloud
| style="vertical-align:top" |
'''Contract partner:''' Partner or end customer 
* GEO redundancy at different locations
* HA server and HA '''DataCenter''' redundancy
** Both data centers active, ''=> active-active operating mode'' 
** Third data center for backup data
* '''Daily''' backup - instances & infrastructur
* Restart time for data center failure: in the range of '''seconds'''
* Blackout / Autonomy time: '''120h'''
* Storage availability: RAID + '''GEO-DataCenter-Mirror''' + Backup
* Minimum consumption: not defined iSC / month
* Infrastructure-Hotline-License ''' ''inclusive'' 24x7 hotline'''

 
[[Image:Cloud_Compare_PREM-DC.png|600px]]
| style="vertical-align:top" |
'''Contract partner:''' Partner or end customer 
* GEO redundancy at different locations
* HA server redundancy
** One active data center
** A Standby data center ''=> active-passive operating mode''
** Third data center for backup data
* '''Weekly''' backup of instances - infrastructure daily
* Restart time for data center failure: in the range of '''hours'''
* Blackout / Autonomy time: '''24h'''
* Storage availability: RAID + Backup
* Minimum consumption: 500 iSC / month
* Infrastructure-Hotline-License ''' ''for optional'' 24x7 hotline'''

 
[[Image:Cloud_Compare_STD-DC.png|600px]]
|-
| style="vertical-align:top;" rowspan="2"| Phone- Hotline 24x7
| style="border-bottom:hidden;" | Inclusive
| style="border-bottom:hidden;" | Optional
|-
| style="border-top:hidden;" colspan="2" |
'''Provision of services by:''' innovaphone 
* Emergency infrastructure hotline service
**Exclusively for certified partners
**For cloud instances in operation and completely licensed by Infrastructure-Hotline-License
* Qualified ticket opening by email before calling
**Authorization through confidential identification markers
|-
|}

=HA concept of both myApps Cloud variants in detail=
 
{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
!
! style="text-align: center;" | PREMIUM
! style="text-align: center;" | STANDARD
|-
| colspan="3" style="background-color:#f2f2f2;" |
*Both innovaphone myApps Cloud variants are currently based on a GEOredundant disaster recovery concept within Germany.
*Due to the different levels of technical complexity, different service availability requirements are covered in the event of a disaster.
|-
| - 1 -
'''Restart time for data center failure / Downtimes'''
|
*'''"Fully automated"''' failure detection and restart time for the Cloud-Services
*Failure symptoms in the range of '''''seconds / a few minutes'''''
|
*'''"Manual"''' failure detection and restore of the Cloud-Services
*Failure symptoms in the range of '''''some hours'''''
|-
| - 2 -
'''DataCenter Lokations'''
|
*"'''active - active'''"
**Two active DCs in Germany or EU (currently in Germany)
***Location for Backup-Data is the innovaphone headquater in Sindelfingen (Germany)
|
*"'''active''' - cold standby"
**One active DC in Germany or EU (currently in Germany)
***One other passive DC has server resources ready in the event of a disaster
***Location for Backup-Data is the innovaphone headquater in Sindelfingen (Germany)
|-
| - 3 -
'''Desaster-Recovery-Concept'''
|
'''''„stretched-VMware-HA-Cluster“''''' actual based on a Metrocluster Storage
*This is made possible by redundant "two-way" Darkfiber connected data centers in two cities.
**The operating LAN and an iSCSI SAN run over this, which keeps the VMware datastores mirrored at both data centers.
*If the darkfirber connection between the two data centers is interrupted (no more storage mirror), but the ESX servers in each data center are still in operation, a third additional connection via a separate "heartbeat network" was made available to avoid a "split brain" of the VMware database (lack of quorum accessibility of ALL ESX servers).
**This is then used to decide in which data center location the mirroring of the iSCSI SAN was interrupted (e.g. due to a component defect).
**Datastore operation is thus continued " unique" on the undamaged mirror datastore in a data center (automatic HA boot of the VMs from the damaged data center).
**Once the mirror connection is re-established, vSphere DRS redistributes the VMs across both data center locations.
*The route-redundant Internet breakout is routed via HSRP technology and, if necessary, relocated from one city to the other within a few seconds.
*In addition, we move nightly backups/replicas to the company headquarters in Sindelfingen.
[[Image:Cloud_Compare_PREM-DC_detail.png|600px]]
|
'''''„simple VMware-HA-Cluster“''''' with ''Backup-Instances'' in the innovaphone headquater
*The simple disaster recovery concept requires a backup/restore or replication process in addition to VMware vSphere and vCenter.
**vSphere Replication" and "Site Recovery Manager" are VMware terms.
**For our STANDARD cloud, we use the backup variant, which offers us a more diverse range of possible use cases.
***both via the cloud instances
***as well as for all services from our company headquarters in Sindelfingen.
*In the event of a disaster, operations are only restarted on the resources provided in the standby data center after recovery/restore from the company headquarters in Sindelfingen.
**This requires a new Internet breakout under a new IP address
|-
| - 4 -
'''Blackout / Autonomy time'''
|
*Infrastructural protection of the two remote data centers by the provider
**Redundancies for Internet connection, air conditioning systems, UPS and emergency power generators as well as resulting autonomy time in the event of a regional power failure
***'''5 days'''
*!! In the event of a power failure in only one DataCenter, operation automatically switches to disaster mode at the latest after the autonomy time has expired, and thus to the remaining DataCenter location !!
|
*Infrastructural protection of the data center by the provider
**Redundancies for Internet connection, air conditioning systems, UPS and emergency power generators as well as resulting autonomy time in the event of a regional power failure
***'''1 day'''
*!! In the event of a power failure in the active DataCender that lasts longer than 24 hours, the disaster case Restore to standby location must be triggered, which means several hours of operational interruption !!
|-
| colspan="3" style="background-color:#f2f2f2;" | '''Both cloud variants use secondary services from the company headquarter in Sindelfingen'''
*Central services out of Sindelfingen are:
**Customer care by sales & support teams (central call acceptance & Mantis)
**my.innovapone portal (license management)
**App store (firmware and myApps updates)
**Push & provisioning server (smartphone synchronization & rollout of IP devices)
**Data center for the backup data of the STANDARD and PREMIUM cloud

*The Internet presence of our company headquarters required for this is protected against a regional power blackout via UPS.
**~1h battery power

|}

Howto:MyApps Cloud - Connecting 3rd-party SIP devices (general considerations)

2024-03-06T16:26:16Z

Swh: /* Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud */

__toc__

=Applies To=
This information applies to
* myApps Cloud v13
* General considerations on 3rd-party SIP devices

==Disclaimer==
This article is presenting a summary of our experience, connecting 3rd-party devices to the myApps Cloud Platform. As innovaphone is not able to track all changes in functionality or firmware of 3rd-party SIP devices, this document is meant to be an orientation to our certified partners. In any case, we recommended to our partners to verify the functionality of a 3rd-party product. As such innovaphone is not liable for any malfunction of, or caused through a 3rd-party product, even if the respective product is listed in this article.

==Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud ==

# By default, the myApps Cloud service relies on the '''ICE protocol''' (according [https://tools.ietf.org/html/rfc8445 RFC 8445]) to establish peer-to-peer media communication between connected 3rd-party SIP devices. Thus, the connecting SIP device has to support STUN, TURN and the ICE mechanism.
#* In case ICE and TURN are not supported by the SIP device, the absolute minimum requirement is '''STUN support''' (in such case, the respective PBX User Object has to enable Media-Relay). In this scenario the media stream is always routed through the PBX (instead of peer-to-peer routing, when using the default ICE mechanism as described above).
#* The following setting for '''Media relay endpoints''' is configured by default in the myApps Cloud PBX
#** Admin UI > PBX > Config > General
#*** '''Nothing''' may be entered in the field > Media relay endpoints > '''Firewall public IP''' !
#*** The '''TURN''' field must be '''checked''' !
#**** This ensures that the innovaphone Cloud Turn server is used for this
#**** Admin UI > IP4 > General > STUN > TURN Server 
# The innovaphone PBX uses the standardized '''SIP Digest Access Authentication''' (according [https://tools.ietf.org/html/rfc3261 RFC 3261] "The Digest Authentication Scheme") to verify the credentials of any connected 3rd-party SIP device.
#* If the selected 3rd-party device does not support this protocol, the Digest Authentication Reply Check can be disabled on the customer PBX, for all incoming SIP connections, with the following commands:
#** At the advanced PBX user interface > Maintenance > Diagnostics > Command
#** <code>!config add TSIP /disable-digest-replay-check </code>
#** <code>!config add SIPS /disable-digest-replay-check </code>
#** <code>!config write</code>
#** <code>!config activate</code> 
# Further the following features should be supported by the device
#* DTMF (according [https://tools.ietf.org/html/rfc2833 RFC 2833] "RTP payload for DTMF")
#* Hold/Retrieve (according [https://tools.ietf.org/html/rfc3264 RFC 3264] "Offer/Answer Model for SDP")
#* Transfer (according [https://tools.ietf.org/html/rfc3515 RFC 3515] "REFER Method", [https://tools.ietf.org/html/rfc3891 RFC 3891] "Replaces Header) 
# To ensure secure data connections, the myApps Cloud relies by default '''TLS''' encryption (e.g. SIPS or SIP/TLS). Thus, we recommend to select a 3rd-party SIP device supporting TLS. For this reason, the myApps Cloud platform already includes the root certificates of the following 3-rd party manufacturers:
#* Yealink
#* Gigaset
#* snom
#* Telecom Behnke (TFE in combination with specific 3rd-Party MediaRunway [https://wiki.innovaphone.com/index.php?title=Howto:Doorbell_-_MediaRunway_-_Partner_App "Doorbell-App"]) (this list will be extended, step-by-step)

 
Some more hints for evaluating 3rd party devices can be found in the ''Things to consider'' section of [[Howto:Guidelines_for_Testing_3rd_Party_SIP_Terminal_Devices#Things_to_consider | Howto:Guidelines for Testing 3rd Party SIP Terminal Devices]].

==Howto articles, for selected 3-rd party SIP devices==

For the following 3-rd party devices, a specific description is available, describing details of the respective configuration:
* [https://wiki.innovaphone.com/index.php?title=Howto:Yealink_IP_phones_-_Yealink_-_3rd_Party_Product Howto:Yealink_IP_phones_-_Yealink_-_3rd_Party_Product]

==Workaround: 3-rd party SIP devices without STUN support ==
If a 3rd-party SIP device (e.g. doorphone) does not meet the above defined minimum requirements, an additional local gateway (edge component) on the customers premises is needed, to connect the device to the myApps Cloud platform.

[[Image:3rd-party-SIP-device.png]]

[[Category:myApps_Cloud|Connecting|{{PAGENAME}}]]

Howto:MyApps Cloud - Connecting 3rd-party SIP devices (general considerations)

2024-03-06T16:19:59Z

Swh: /* Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud */

__toc__

=Applies To=
This information applies to
* myApps Cloud v13
* General considerations on 3rd-party SIP devices

==Disclaimer==
This article is presenting a summary of our experience, connecting 3rd-party devices to the myApps Cloud Platform. As innovaphone is not able to track all changes in functionality or firmware of 3rd-party SIP devices, this document is meant to be an orientation to our certified partners. In any case, we recommended to our partners to verify the functionality of a 3rd-party product. As such innovaphone is not liable for any malfunction of, or caused through a 3rd-party product, even if the respective product is listed in this article.

==Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud ==

# By default, the myApps Cloud service relies on the '''ICE protocol''' (according [https://tools.ietf.org/html/rfc8445 RFC 8445]) to establish peer-to-peer media communication between connected 3rd-party SIP devices. Thus, the connecting SIP device has to support STUN, TURN and the ICE mechanism.
#* In case ICE and TURN are not supported by the SIP device, the absolute minimum requirement is '''STUN support''' (in such case, the respective PBX User Object has to enable Media-Relay). In this scenario the media stream is always routed through the PBX (instead of peer-to-peer routing, when using the default ICE mechanism as described above).
#* The following setting for '''Media relay endpoints''' is configured by default in the myApps Cloud PBX
#** Admin UI > PBX > Config > General
#*** '''Nothing''' may be entered in the field > Media relay endpoints > '''Firewall public IP''' !
#*** The '''TURN''' field must be '''checked''' ! 
# The innovaphone PBX uses the standardized '''SIP Digest Access Authentication''' (according [https://tools.ietf.org/html/rfc3261 RFC 3261] "The Digest Authentication Scheme") to verify the credentials of any connected 3rd-party SIP device.
#* If the selected 3rd-party device does not support this protocol, the Digest Authentication Reply Check can be disabled on the customer PBX, for all incoming SIP connections, with the following commands:
#** At the advanced PBX user interface > Maintenance > Diagnostics > Command
#** <code>!config add TSIP /disable-digest-replay-check </code>
#** <code>!config add SIPS /disable-digest-replay-check </code>
#** <code>!config write</code>
#** <code>!config activate</code> 
# Further the following features should be supported by the device
#* DTMF (according [https://tools.ietf.org/html/rfc2833 RFC 2833] "RTP payload for DTMF")
#* Hold/Retrieve (according [https://tools.ietf.org/html/rfc3264 RFC 3264] "Offer/Answer Model for SDP")
#* Transfer (according [https://tools.ietf.org/html/rfc3515 RFC 3515] "REFER Method", [https://tools.ietf.org/html/rfc3891 RFC 3891] "Replaces Header) 
# To ensure secure data connections, the myApps Cloud relies by default '''TLS''' encryption (e.g. SIPS or SIP/TLS). Thus, we recommend to select a 3rd-party SIP device supporting TLS. For this reason, the myApps Cloud platform already includes the root certificates of the following 3-rd party manufacturers:
#* Yealink
#* Gigaset
#* snom
#* Telecom Behnke (TFE in combination with specific 3rd-Party MediaRunway [https://wiki.innovaphone.com/index.php?title=Howto:Doorbell_-_MediaRunway_-_Partner_App "Doorbell-App"]) (this list will be extended, step-by-step)

 
Some more hints for evaluating 3rd party devices can be found in the ''Things to consider'' section of [[Howto:Guidelines_for_Testing_3rd_Party_SIP_Terminal_Devices#Things_to_consider | Howto:Guidelines for Testing 3rd Party SIP Terminal Devices]].

==Howto articles, for selected 3-rd party SIP devices==

For the following 3-rd party devices, a specific description is available, describing details of the respective configuration:
* [https://wiki.innovaphone.com/index.php?title=Howto:Yealink_IP_phones_-_Yealink_-_3rd_Party_Product Howto:Yealink_IP_phones_-_Yealink_-_3rd_Party_Product]

==Workaround: 3-rd party SIP devices without STUN support ==
If a 3rd-party SIP device (e.g. doorphone) does not meet the above defined minimum requirements, an additional local gateway (edge component) on the customers premises is needed, to connect the device to the myApps Cloud platform.

[[Image:3rd-party-SIP-device.png]]

[[Category:myApps_Cloud|Connecting|{{PAGENAME}}]]

Howto:MyApps Cloud - Connecting 3rd-party SIP devices (general considerations)

2024-03-06T13:35:21Z

Swh: /* Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud */

__toc__

=Applies To=
This information applies to
* myApps Cloud v13
* General considerations on 3rd-party SIP devices

==Disclaimer==
This article is presenting a summary of our experience, connecting 3rd-party devices to the myApps Cloud Platform. As innovaphone is not able to track all changes in functionality or firmware of 3rd-party SIP devices, this document is meant to be an orientation to our certified partners. In any case, we recommended to our partners to verify the functionality of a 3rd-party product. As such innovaphone is not liable for any malfunction of, or caused through a 3rd-party product, even if the respective product is listed in this article.

==Requirements to 3-rd party SIP devices, when connecting to the myApps Cloud ==

# By default, the myApps Cloud service relies on the '''ICE protocol''' (according [https://tools.ietf.org/html/rfc8445 RFC 8445]) to establish peer-to-peer media communication between connected 3rd-party SIP devices. Thus, the connecting SIP device has to support STUN, TURN and the ICE mechanism.
#* In case ICE and TURN are not supported by the SIP device, the absolute minimum requirement is '''STUN support''' (in such case, the respective PBX User Object has to enable Media-Relay). In this scenario the media stream is always routed through the PBX (instead of peer-to-peer routing, when using the default ICE mechanism as described above). 
# The innovaphone PBX uses the standardized '''SIP Digest Access Authentication''' (according [https://tools.ietf.org/html/rfc3261 RFC 3261] "The Digest Authentication Scheme") to verify the credentials of any connected 3rd-party SIP device.
#* If the selected 3rd-party device does not support this protocol, the Digest Authentication Reply Check can be disabled on the customer PBX, for all incoming SIP connections, with the following commands:
#** At the advanced PBX user interface > Maintenance > Diagnostics > Command
#** <code>!config add TSIP /disable-digest-replay-check </code>
#** <code>!config add SIPS /disable-digest-replay-check </code>
#** <code>!config write</code>
#** <code>!config activate</code> 
# Further the following features should be supported by the device
#* DTMF (according [https://tools.ietf.org/html/rfc2833 RFC 2833] "RTP payload for DTMF")
#* Hold/Retrieve (according [https://tools.ietf.org/html/rfc3264 RFC 3264] "Offer/Answer Model for SDP")
#* Transfer (according [https://tools.ietf.org/html/rfc3515 RFC 3515] "REFER Method", [https://tools.ietf.org/html/rfc3891 RFC 3891] "Replaces Header) 
# To ensure secure data connections, the myApps Cloud relies by default '''TLS''' encryption (e.g. SIPS or SIP/TLS). Thus, we recommend to select a 3rd-party SIP device supporting TLS. For this reason, the myApps Cloud platform already includes the root certificates of the following 3-rd party manufacturers:
#* Yealink
#* Gigaset
#* snom
#* Telecom Behnke (TFE in combination with specific 3rd-Party MediaRunway [https://wiki.innovaphone.com/index.php?title=Howto:Doorbell_-_MediaRunway_-_Partner_App "Doorbell-App"]) (this list will be extended, step-by-step)

 
Some more hints for evaluating 3rd party devices can be found in the ''Things to consider'' section of [[Howto:Guidelines_for_Testing_3rd_Party_SIP_Terminal_Devices#Things_to_consider | Howto:Guidelines for Testing 3rd Party SIP Terminal Devices]].

==Howto articles, for selected 3-rd party SIP devices==

For the following 3-rd party devices, a specific description is available, describing details of the respective configuration:
* [https://wiki.innovaphone.com/index.php?title=Howto:Yealink_IP_phones_-_Yealink_-_3rd_Party_Product Howto:Yealink_IP_phones_-_Yealink_-_3rd_Party_Product]

==Workaround: 3-rd party SIP devices without STUN support ==
If a 3rd-party SIP device (e.g. doorphone) does not meet the above defined minimum requirements, an additional local gateway (edge component) on the customers premises is needed, to connect the device to the myApps Cloud platform.

[[Image:3rd-party-SIP-device.png]]

[[Category:myApps_Cloud|Connecting|{{PAGENAME}}]]

MyApps Cloud - Comparison table

2023-11-27T17:05:33Z

Swh: /* HA concept of both myApps Cloud variants in detail */

[[Category:myApps_Cloud|Comparison|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__

=Applies To=
This information applies to the innovaphone myApps Cloud versions:
*PREMIUM
*STANDARD

=Briefly the facts=

*The main advantages of '''PREMIUM''' over STANDARD environment are:
**the '''fully automated GEOredundancy''' between two '''High-Available Data-Centers'''
*** STANDARD has HA in one Data-Center with manual GEOredundancy
**the '''5-day power blackout protection''' is fully available.
*** STANDARD has one-day power protection
**the '''24x7 cloud infrastructure hotline''' as a default option.
*** STANDARD has this optional
 

{| class="wikitable" border="1" cellspacing="0" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
! style="text-align:center;" | Description
! style="text-align:center;" | Cloud-PREMIUM
! style="text-align:center;" | Cloud-STANDARD
|-
| style="vertical-align:top" | Cloud
| style="vertical-align:top" |
'''Contract partner:''' Partner or end customer 
* GEO redundancy at different locations
* HA server and HA '''DataCenter''' redundancy
** Both data centers active, ''=> active-active operating mode'' 
** Third data center for backup data
* '''Daily''' backup - instances & infrastructur
* Restart time for data center failure: in the range of '''seconds'''
* Blackout / Autonomy time: '''120h'''
* Storage availability: RAID + '''GEO-DataCenter-Mirror''' + Backup
* Minimum consumption: not defined iSC / month
* Infrastructure-Hotline-License ''' ''inclusive'' 24x7 hotline'''
**''first User'': 1.000 iSC / month
**''each additional user'': 10 iSC / month 
 
[[Image:Cloud_Compare_PREM-DC.png|600px]]
| style="vertical-align:top" |
'''Contract partner:''' Partner or end customer 
* GEO redundancy at different locations
* HA server redundancy
** One active data center
** A Standby data center ''=> active-passive operating mode''
** Third data center for backup data
* '''Weekly''' backup of instances - infrastructure daily
* Restart time for data center failure: in the range of '''hours'''
* Blackout / Autonomy time: '''24h'''
* Storage availability: RAID + Backup
* Minimum consumption: 500 iSC / month
* Infrastructure-Hotline-License ''' ''for optional'' 24x7 hotline'''
**''first User'': 500 iSC / month (open a cloud ticket for activation)
**''each additional user'': 5 iSC / month 
 
[[Image:Cloud_Compare_STD-DC.png|600px]]
|-
| style="vertical-align:top;" rowspan="2"| Phone- Hotline 24x7
| style="border-bottom:hidden;" | Inclusive
| style="border-bottom:hidden;" | Optional
|-
| style="border-top:hidden;" colspan="2" |
'''Provision of services by:''' innovaphone 
* Emergency infrastructure hotline service
**Exclusively for certified partners
**For cloud instances in operation and completely licensed by Infrastructure-Hotline-License
* Qualified ticket opening by email before calling
**Authorization through confidential identification markers
|-
|}

=HA concept of both myApps Cloud variants in detail=
 
{| class="wikitable" border="1" cellspacing="1" cellpadding="10" style="text-align:left; font-size:13px; font-family:Arial, Helvetica, sans-serif !important;;"
|- style="font-weight:bold; background-color:#c0c0c0;"
!
! style="text-align: center;" | PREMIUM
! style="text-align: center;" | STANDARD
|-
| colspan="3" style="background-color:#f2f2f2;" |
*Both innovaphone myApps Cloud variants are currently based on a GEOredundant disaster recovery concept within Germany.
*Due to the different levels of technical complexity, different service availability requirements are covered in the event of a disaster.
|-
| - 1 -
'''Restart time for data center failure / Downtimes'''
|
*'''"Fully automated"''' failure detection and restart time for the Cloud-Services
*Failure symptoms in the range of '''''seconds / a few minutes'''''
|
*'''"Manual"''' failure detection and restore of the Cloud-Services
*Failure symptoms in the range of '''''some hours'''''
|-
| - 2 -
'''DataCenter Lokations'''
|
*"'''active - active'''"
**Two active DCs in Germany or EU (currently in Germany)
***Location for Backup-Data is the innovaphone headquater in Sindelfingen (Germany)
|
*"'''active''' - cold standby"
**One active DC in Germany or EU (currently in Germany)
***One other passive DC has server resources ready in the event of a disaster
***Location for Backup-Data is the innovaphone headquater in Sindelfingen (Germany)
|-
| - 3 -
'''Desaster-Recovery-Concept'''
|
'''''„stretched-VMware-HA-Cluster“''''' actual based on a Metrocluster Storage
*This is made possible by redundant "two-way" Darkfiber connected data centers in two cities.
**The operating LAN and an iSCSI SAN run over this, which keeps the VMware datastores mirrored at both data centers.
*If the darkfirber connection between the two data centers is interrupted (no more storage mirror), but the ESX servers in each data center are still in operation, a third additional connection via a separate "heartbeat network" was made available to avoid a "split brain" of the VMware database (lack of quorum accessibility of ALL ESX servers).
**This is then used to decide in which data center location the mirroring of the iSCSI SAN was interrupted (e.g. due to a component defect).
**Datastore operation is thus continued " unique" on the undamaged mirror datastore in a data center (automatic HA boot of the VMs from the damaged data center).
**Once the mirror connection is re-established, vSphere DRS redistributes the VMs across both data center locations.
*The route-redundant Internet breakout is routed via HSRP technology and, if necessary, relocated from one city to the other within a few seconds.
*In addition, we move nightly backups/replicas to the company headquarters in Sindelfingen.
[[Image:Cloud_Compare_PREM-DC_detail.png|600px]]
|
'''''„simple VMware-HA-Cluster“''''' with ''Backup-Instances'' in the innovaphone headquater
*The simple disaster recovery concept requires a backup/restore or replication process in addition to VMware vSphere and vCenter.
**vSphere Replication" and "Site Recovery Manager" are VMware terms.
**For our STANDARD cloud, we use the backup variant, which offers us a more diverse range of possible use cases.
***both via the cloud instances
***as well as for all services from our company headquarters in Sindelfingen.
*In the event of a disaster, operations are only restarted on the resources provided in the standby data center after recovery/restore from the company headquarters in Sindelfingen.
**This requires a new Internet breakout under a new IP address
|-
| - 4 -
'''Blackout / Autonomy time'''
|
*Infrastructural protection of the two remote data centers by the provider
**Redundancies for Internet connection, air conditioning systems, UPS and emergency power generators as well as resulting autonomy time in the event of a regional power failure
***'''5 days'''
*!! In the event of a power failure in only one DataCenter, operation automatically switches to disaster mode at the latest after the autonomy time has expired, and thus to the remaining DataCenter location !!
|
*Infrastructural protection of the data center by the provider
**Redundancies for Internet connection, air conditioning systems, UPS and emergency power generators as well as resulting autonomy time in the event of a regional power failure
***'''1 day'''
*!! In the event of a power failure in the active DataCender that lasts longer than 24 hours, the disaster case Restore to standby location must be triggered, which means several hours of operational interruption !!
|-
| colspan="3" style="background-color:#f2f2f2;" | '''Both cloud variants use secondary services from the company headquarter in Sindelfingen'''
*Central services out of Sindelfingen are:
**Customer care by sales & support teams (central call acceptance & Mantis)
**my.innovapone portal (license management)
**App store (firmware and myApps updates)
**Push & provisioning server (smartphone synchronization & rollout of IP devices)
**Data center for the backup data of the STANDARD and PREMIUM cloud

*The Internet presence of our company headquarters required for this is protected against a regional power blackout via UPS.
**~6h battery power

|}

MyApps Cloud - STANDARD Concept

2023-11-24T14:51:11Z

Swh: /* Future tickets for cloud instances */

[[Category:myApps_Cloud|Concept|STANDARD|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__
 

=Applies To=
This information applies to the innovaphone myApps Cloud variant:
*STANDARD
 

=Reasons for the myApps Cloud STANDARD=
*Customers with low to normal demands on ...
**Infrastructure redundancies and autonomy times (''blackout scenarios'')
*In the most unlikely event of a data center failure a temporary interruption to operations of a few hours is acceptable
*The planned project requires only one Master PBX and high load requirements are not expected
*A maximum of 200 users are operated in the instance
 

=The characteristics of the myApps Cloud STANDARD=
*The technical structure of the [[MyApps_Cloud_-_Comparison_table |Cloud STANDARD version (in comparison to the Cloud PREMIUM version) is explained < here]]
*Further questions about the innovaphone myApps Cloud are answered in our HowTo category ''myApps Cloud''
**e.g. in the [[Howto:MyApps_Cloud_-_FAQ |FAQ < here]]
**e.g. a [[Howto:MyApps_Cloud_-_Installation |Cloud Installation < here]]
*The [[Howto:MyApps_Cloud_-_Order_Process |Order-Process wird < here]]
*A description of the optional 24x7 infrastructure support hotline service (must be can be found as a PDF download here
**Download page with '' 'Handling_innovaphone_myApps_Cloud-Infrastructure-Support.pdf' '' (currently only in German)
*Instructions for licensing the ''Infrastructure Support License'' can be found [https://www.innovaphone.com/de/services/lizenzen/lizenzen-cloud.html > here in the license guide]
**The services for the 24x7 hotline must be activated for every instance via support ticket to the Cloud-Team (cloud@innovaphone.com)
 

=Support in the myApps Cloud environment=
==Every new myApps Cloud instance starts with an "installation support ticket"==
*This includes, among things:
**Basic data (instance number / system name)
**The contract data
**Notes on the installation
**Instructions on how to open future tickets for the instance
**A PDF for support in discussions with firewall administrators
**The individually prepared installation link for your ordered Cloud instance

*This first cloud ticket assists you and the instance until the time of the first operational handover to your end customer
**Installation process
**Loading of iSC or/and conclusion of an auto-iSC contract
**Configuring licenses

==Subsequent tickets for cloud instances==
*All issues relating to cloud instances are handled by the cloud team via the cloud hotline during normal business hours.
**Open a qualified ticket via cloud@innovaphone.com
***[[Course13:IT_Connect_-_11.1_How_to_create_a_support_ticket|How to create a support ticket is explained in general < here]]
****e.g. attach the config file of the PBX
**Subject should always start with
***Instance no.|system name
****e.g. 12345|holzschuh.com - problem description

*Most cases are also resolved directly by the cloud team
*For cases that are not primarily cloud-specific, the ticket may be forwarded to the specialized support colleagues at innovaphone Support.

MyApps Cloud - PREMIUM Concept

2023-11-24T14:49:24Z

Swh: /* Future tickets for cloud instances */

[[Category:myApps_Cloud|Concept|PREMIUM|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__

 

=Applies To=
This information applies to the innovaphone myApps Cloud variant:
*PREMIUM
 

=Reasons for the myApps Cloud PREMIUM=
*Customers with high demands on ...
**Infrastructure redundancies and autonomy times (''blackout scenarios'')
**Fastest restart of operations in the event of a data center failure
*The planned project requires one or more slave PBXs to meet the administrative requirements or call load
*A large instance with many users/ports (> 200) is anticipated
 

=The characteristics of the myApps Cloud PREMIUM=
*The technical structure of the [[MyApps_Cloud_-_Comparison_table |Cloud PREMIUM version (in comparison to the Cloud STANDARD version) is explained < here]]
*Further questions about the innovaphone myApps Cloud are answered in our HowTo category ''myApps Cloud''
**e.g. in the [[Howto:MyApps_Cloud_-_FAQ |FAQ < here]]
**e.g. a [[Howto:MyApps_Cloud_-_Installation |Cloud Installation < here]]
*The [[Howto:MyApps_Cloud_-_Order_Process |Order-Process is explained < here]]
*A description of the 24x7 infrastructure support hotline service included as standard in the PREMIUM version can be found as a PDF download here
**Download page with '' 'Handhabung_innovaphone_myApps_Cloud-Infrastruktur-Support.pdf' '' (currently only in German)
*Instructions for licensing the ''Infrastructure Support License'' can be found [https://www.innovaphone.com/de/services/lizenzen/lizenzen-cloud.html > here in the license guide]
 

=Support in the myApps Cloud environment=
==Every new myApps Cloud instance starts with an "installation support ticket"==
*This includes, among things:
**Basic data (instance number / system name)
**The contract data
**Notes on the installation
**Instructions on how to open future tickets for the instance
**A PDF for support in discussions with firewall administrators
**The individually prepared installation link for your ordered Cloud instance

*This first cloud ticket assists you and the instance until the time of the first operational handover to your end customer
**Installation process
**Loading of iSC or/and conclusion of an auto-iSC contract
**Configuring licenses

==Subsequent tickets for cloud instances==
*All issues relating to cloud instances are handled by the cloud team via the cloud hotline during normal business hours.
**Open a qualified ticket via cloud@innovaphone.com
***[[Course13:IT_Connect_-_11.1_How_to_create_a_support_ticket|How to create a support ticket is explained in general < here]]
****e.g. attach the config file of the PBX
**Subject should always start with
***Instance no.|system name
****e.g. 12345|holzschuh.com - problem description

*Most cases are also resolved directly by the cloud team
*For cases that are not primarily cloud-specific, the ticket may be forwarded to the specialized support colleagues at innovaphone Support.
 

==Special 24x7 infrastructure hotline service for myApps Cloud PREMIUM==
*An additional process starts with the regular operation of the PREMIUM instance
*At this time you will receive an additional ticket with
**Instructions for using the 24x7 infrastructure support
**Individual identification data to access the 24x7 hotline

MyApps Cloud - STANDARD Concept

2023-11-24T13:40:57Z

Swh:

[[Category:myApps_Cloud|Concept|STANDARD|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__
 

=Applies To=
This information applies to the innovaphone myApps Cloud variant:
*STANDARD
 

=Reasons for the myApps Cloud STANDARD=
*Customers with low to normal demands on ...
**Infrastructure redundancies and autonomy times (''blackout scenarios'')
*In the most unlikely event of a data center failure a temporary interruption to operations of a few hours is acceptable
*The planned project requires only one Master PBX and high load requirements are not expected
*A maximum of 200 users are operated in the instance
 

=The characteristics of the myApps Cloud STANDARD=
*The technical structure of the [[MyApps_Cloud_-_Comparison_table |Cloud STANDARD version (in comparison to the Cloud PREMIUM version) is explained < here]]
*Further questions about the innovaphone myApps Cloud are answered in our HowTo category ''myApps Cloud''
**e.g. in the [[Howto:MyApps_Cloud_-_FAQ |FAQ < here]]
**e.g. a [[Howto:MyApps_Cloud_-_Installation |Cloud Installation < here]]
*The [[Howto:MyApps_Cloud_-_Order_Process |Order-Process wird < here]]
*A description of the optional 24x7 infrastructure support hotline service (must be can be found as a PDF download here
**Download page with '' 'Handling_innovaphone_myApps_Cloud-Infrastructure-Support.pdf' '' (currently only in German)
*Instructions for licensing the ''Infrastructure Support License'' can be found [https://www.innovaphone.com/de/services/lizenzen/lizenzen-cloud.html > here in the license guide]
**The services for the 24x7 hotline must be activated for every instance via support ticket to the Cloud-Team (cloud@innovaphone.com)
 

=Support in the myApps Cloud environment=
==Every new myApps Cloud instance starts with an "installation support ticket"==
*This includes, among things:
**Basic data (instance number / system name)
**The contract data
**Notes on the installation
**Instructions on how to open future tickets for the instance
**A PDF for support in discussions with firewall administrators
**The individually prepared installation link for your ordered Cloud instance

*This first cloud ticket assists you and the instance until the time of the first operational handover to your end customer
**Installation process
**Loading of iSC or/and conclusion of an auto-iSC contract
**Configuring licenses

==Future tickets for cloud instances==
*All issues relating to cloud instances are handled by the cloud team via the cloud hotline during normal business hours.
**Open a qualified ticket via cloud@innovaphone.com (e.g. attach config)
**Subject should always start with
***Instance no.|system name
***e.g. 12345|holzschuh.com - problem description

*Most cases are also resolved directly by the cloud team
*For cases that are not primarily cloud-specific, the ticket may be forwarded to the specialized support colleagues at innovaphone Support.

MyApps Cloud - PREMIUM Concept

2023-11-24T13:38:38Z

Swh: /* Special 24x7 infrastructure hotline service for myApps Cloud PREMIUM */

[[Category:myApps_Cloud|Concept|PREMIUM|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__

 

=Applies To=
This information applies to the innovaphone myApps Cloud variant:
*PREMIUM
 

=Reasons for the myApps Cloud PREMIUM=
*Customers with high demands on ...
**Infrastructure redundancies and autonomy times (''blackout scenarios'')
**Fastest restart of operations in the event of a data center failure
*The planned project requires one or more slave PBXs to meet the administrative requirements or call load
*A large instance with many users/ports (> 200) is anticipated
 

=The characteristics of the myApps Cloud PREMIUM=
*The technical structure of the [[MyApps_Cloud_-_Comparison_table |Cloud PREMIUM version (in comparison to the Cloud STANDARD version) is explained < here]]
*Further questions about the innovaphone myApps Cloud are answered in our HowTo category ''myApps Cloud''
**e.g. in the [[Howto:MyApps_Cloud_-_FAQ |FAQ < here]]
**e.g. a [[Howto:MyApps_Cloud_-_Installation |Cloud Installation < here]]
*The [[Howto:MyApps_Cloud_-_Order_Process |Order-Process is explained < here]]
*A description of the 24x7 infrastructure support hotline service included as standard in the PREMIUM version can be found as a PDF download here
**Download page with '' 'Handhabung_innovaphone_myApps_Cloud-Infrastruktur-Support.pdf' '' (currently only in German)
*Instructions for licensing the ''Infrastructure Support License'' can be found [https://www.innovaphone.com/de/services/lizenzen/lizenzen-cloud.html > here in the license guide]
 

=Support in the myApps Cloud environment=
==Every new myApps Cloud instance starts with an "installation support ticket"==
*This includes, among things:
**Basic data (instance number / system name)
**The contract data
**Notes on the installation
**Instructions on how to open future tickets for the instance
**A PDF for support in discussions with firewall administrators
**The individually prepared installation link for your ordered Cloud instance

*This first cloud ticket assists you and the instance until the time of the first operational handover to your end customer
**Installation process
**Loading of iSC or/and conclusion of an auto-iSC contract
**Configuring licenses

==Future tickets for cloud instances==
*All issues relating to cloud instances are handled by the cloud team via the cloud hotline during normal business hours.
**Open a qualified ticket via cloud@innovaphone.com (e.g. attach config)
**Subject should always start with
***Instance no.|system name
***e.g. 12345|holzschuh.com - problem description

*Most cases are also resolved directly by the cloud team
*For cases that are not primarily cloud-specific, the ticket may be forwarded to the specialized support colleagues at innovaphone Support.
 

==Special 24x7 infrastructure hotline service for myApps Cloud PREMIUM==
*An additional process starts with the regular operation of the PREMIUM instance
*At this time you will receive an additional ticket with
**Instructions for using the 24x7 infrastructure support
**Individual identification data to access the 24x7 hotline

MyApps Cloud - PREMIUM Concept

2023-11-24T13:00:08Z

Swh:

[[Category:myApps_Cloud|Concept|PREMIUM|{{PAGENAME}}]]

{{HOWTOMOD13r3 Translation Info}}
__toc__

 

=Applies To=
This information applies to the innovaphone myApps Cloud variant:
*PREMIUM
 

=Reasons for the myApps Cloud PREMIUM=
*Customers with high demands on ...
**Infrastructure redundancies and autonomy times (''blackout scenarios'')
**Fastest restart of operations in the event of a data center failure
*The planned project requires one or more slave PBXs to meet the administrative requirements or call load
*A large instance with many users/ports (> 200) is anticipated
 

=The characteristics of the myApps Cloud PREMIUM=
*The technical structure of the [[MyApps_Cloud_-_Comparison_table |Cloud PREMIUM version (in comparison to the Cloud STANDARD version) is explained < here]]
*Further questions about the innovaphone myApps Cloud are answered in our HowTo category ''myApps Cloud''
**e.g. in the [[Howto:MyApps_Cloud_-_FAQ |FAQ < here]]
**e.g. a [[Howto:MyApps_Cloud_-_Installation |Cloud Installation < here]]
*The [[Howto:MyApps_Cloud_-_Order_Process |Order-Process is explained < here]]
*A description of the 24x7 infrastructure support hotline service included as standard in the PREMIUM version can be found as a PDF download here
**Download page with '' 'Handhabung_innovaphone_myApps_Cloud-Infrastruktur-Support.pdf' '' (currently only in German)
*Instructions for licensing the ''Infrastructure Support License'' can be found [https://www.innovaphone.com/de/services/lizenzen/lizenzen-cloud.html > here in the license guide]
 

=Support in the myApps Cloud environment=
==Every new myApps Cloud instance starts with an "installation support ticket"==
*This includes, among things:
**Basic data (instance number / system name)
**The contract data
**Notes on the installation
**Instructions on how to open future tickets for the instance
**A PDF for support in discussions with firewall administrators
**The individually prepared installation link for your ordered Cloud instance

*This first cloud ticket assists you and the instance until the time of the first operational handover to your end customer
**Installation process
**Loading of iSC or/and conclusion of an auto-iSC contract
**Configuring licenses

==Future tickets for cloud instances==
*All issues relating to cloud instances are handled by the cloud team via the cloud hotline during normal business hours.
**Open a qualified ticket via cloud@innovaphone.com (e.g. attach config)
**Subject should always start with
***Instance no.|system name
***e.g. 12345|holzschuh.com - problem description

*Most cases are also resolved directly by the cloud team
*For cases that are not primarily cloud-specific, the ticket may be forwarded to the specialized support colleagues at innovaphone Support.
 

==Special 24x7 infrastructure hotline service for myApps Cloud PREMIUM==
*An additional process starts with the regular operation of the PREMIUM instance

File:Cloud Compare STD-DC.png

2023-11-23T17:47:03Z

Swh: