Reference13r1:Concept Offline Provisioning: Difference between revisions
No edit summary |
|||
(8 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
=Overview= | =Overview= | ||
In some cases or environments, PBXs, Gateways and phones do not have Internet access. In this case '' | In some cases or environments, PBXs, Gateways and phones do not have Internet access. In this case ''config.innovaphone.com'' will not be reachable and a provisioning of new devices is not possible. | ||
In order to be able to provision devices without Internet access, there is an option to provide the service itself in the local environment. | In order to be able to provision devices without Internet access, there is an option to provide the service itself in the local environment. | ||
Line 7: | Line 7: | ||
* Version 13r1 (Phone and PBX) | * Version 13r1 (Phone and PBX) | ||
* | * a running App Platform | ||
= How it works = | = How it works = | ||
Line 13: | Line 13: | ||
* As soon as the user adds a new device via the ''User App'', a new code is fetched from the local provisioning system. | * As soon as the user adds a new device via the ''User App'', a new code is fetched from the local provisioning system. | ||
* When the code is entered on the phone, the client sends the code to the local provisioning system. | * When the code is entered on the phone, the client sends the code to the local provisioning system. | ||
** If the code is valid, the client will receive | ** If the code is valid, the client will receive the [[{{NAMESPACE}}:General/Sysclient|Sysclient URL]] and store it in the local configuration. Then the client connect via websocket to the ''Devices App''. All further Processing depends on your devices configuration. | ||
This is the same flow like we use it on the regular provisioning with Internet access. | This is the same flow like we use it on the regular provisioning with Internet access. | ||
Line 22: | Line 22: | ||
There is no need to activate the Provisioning System on a Gateway. | There is no need to activate the Provisioning System on a Gateway. | ||
It | It's already available and you can use it on every Gateway. | ||
== Devices APP == | == Devices APP == | ||
Line 34: | Line 34: | ||
==Client Setup== | ==Client Setup== | ||
You need to tell the Client, that he should not try to connect to the | You need to tell the Client, that he should not try to connect to the vendor Provisioning System. Instead he must connect to your local System. | ||
The goal is to set the [[{{NAMESPACE}}:Services/Update|Update URL]] in the Client to: <code>https://<span style="background-color: yellow">pbx.domain.tld</span>/INSTALL/provisioning.htm?mac=#m&provisioning-code=#p&localip=#i</code> | |||
In | In most cases you want to distribute the Update URL to multiple Clients. Then you can use the following methods: | ||
* Use a local [[{{NAMESPACE}}:DHCP_client#Supported_Options | DHCP Server]] with vendor options | * Use a local [[{{NAMESPACE}}:DHCP_client#Supported_Options | DHCP Server]] with vendor options | ||
* Use [[Reference:My_Innovaphone#Properties | my.innovaphone.com redirection]] (works only if the client is able to connect to ''https://config.innovaphone.com'') | * Use [[Reference:My_Innovaphone#Properties | my.innovaphone.com redirection]] (works only if the client is able to connect to ''https://config.innovaphone.com'') | ||
=Related Articles= | =Related Articles= | ||
* [[{{NAMESPACE}}:Concept_Provisioning]] | |||
* [[{{NAMESPACE}}:Services/Provisioning]] | * [[{{NAMESPACE}}:Services/Provisioning]] | ||
* [[{{NAMESPACE}}:Services/Update]] | * [[{{NAMESPACE}}:Services/Update]] |
Latest revision as of 15:55, 25 March 2020
Overview
In some cases or environments, PBXs, Gateways and phones do not have Internet access. In this case config.innovaphone.com will not be reachable and a provisioning of new devices is not possible.
In order to be able to provision devices without Internet access, there is an option to provide the service itself in the local environment.
Requirements
- Version 13r1 (Phone and PBX)
- a running App Platform
How it works
- The client (e.g. Phone) which is waiting for a provisioning, logs into the local provisioning service which is located on a gateway.
- As soon as the user adds a new device via the User App, a new code is fetched from the local provisioning system.
- When the code is entered on the phone, the client sends the code to the local provisioning system.
- If the code is valid, the client will receive the Sysclient URL and store it in the local configuration. Then the client connect via websocket to the Devices App. All further Processing depends on your devices configuration.
This is the same flow like we use it on the regular provisioning with Internet access.
Configuration
Provisioning System
There is no need to activate the Provisioning System on a Gateway. It's already available and you can use it on every Gateway.
Devices APP
You need to configure your own Provisioning Service in the Devices App
- Open the Devices APP from your myApps Launcher
- Select the desired domain from the list and use the tab edit
- Here you can insert you own Provisioning URL:
https://pbx.domain.tld/INSTALL/get-provisioning-code.htm
- Here you can insert you own Provisioning URL:
Client Setup
You need to tell the Client, that he should not try to connect to the vendor Provisioning System. Instead he must connect to your local System.
The goal is to set the Update URL in the Client to: https://pbx.domain.tld/INSTALL/provisioning.htm?mac=#m&provisioning-code=#p&localip=#i
In most cases you want to distribute the Update URL to multiple Clients. Then you can use the following methods:
- Use a local DHCP Server with vendor options
- Use my.innovaphone.com redirection (works only if the client is able to connect to https://config.innovaphone.com)