Category:Auto Provisioning

From Snom User Wiki

(Difference between revisions)
Jump to: navigation, search
(Scenarios)
Line 22: Line 22:
|[[Image:md_scenarios.png|350px]]
|[[Image:md_scenarios.png|350px]]
|
|
-
#Scenario: [[/DHCP|The '''DHCP Server in the LAN''' may be configured to send the provisioning URL via '''DHCP Option 66/67'''.]]
+
#Scenario: [[Features/Mass Deployment/DHCP|The '''DHCP Server in the LAN''' may be configured to send the provisioning URL via '''DHCP Option 66/67'''.]]
-
#Scenario: [[/PnP|The '''SIP Server in the LAN''' is able to send the provisioning URL by replying to '''SIP SUBSCRIBE Broadcast''' messages]]  
+
#Scenario: [[Features/Mass Deployment/PnP|The '''SIP Server in the LAN''' is able to send the provisioning URL by replying to '''SIP SUBSCRIBE Broadcast''' messages]]  
-
#Scenario: [[/Manual Redirection|Scenario 1/2/4 cannot be used, the provisioning URL must be configured '''manually'''.]]
+
#Scenario: [[Features/Mass Deployment/Manual Redirection|Scenario 1/2/4 cannot be used, the provisioning URL must be configured '''manually'''.]]
-
#Scenario: [[/Automatic Redirection|If scenario 1/2/3 is not used the phones will contact snom's public provisioning server which is preconfigured to redirect the request automatically to another customer provisioning server where the configuration is hosted]]
+
#Scenario: [[Features/Mass Deployment/Automatic Redirection|If scenario 1/2/3 is not used the phones will contact snom's public provisioning server which is preconfigured to redirect the request automatically to another customer provisioning server where the configuration is hosted]]
#Scenario: '''Reserved for OEM partners''': The provisioning URL is '''hardcoded''' in the OEM firmware.
#Scenario: '''Reserved for OEM partners''': The provisioning URL is '''hardcoded''' in the OEM firmware.
|-
|-

Revision as of 11:50, 28 May 2010

Author: Alexander Feldt

Overview

Prerequisites

Scenarios

Depending on the phone installation environment the following scenarios to provide the setting (provisioning) URL to the phones can be distinguished:

  1. Scenario: The DHCP Server in the LAN may be configured to send the provisioning URL via DHCP Option 66/67.
  2. Scenario: The SIP Server in the LAN is able to send the provisioning URL by replying to SIP SUBSCRIBE Broadcast messages
  3. Scenario: Scenario 1/2/4 cannot be used, the provisioning URL must be configured manually.
  4. Scenario: If scenario 1/2/3 is not used the phones will contact snom's public provisioning server which is preconfigured to redirect the request automatically to another customer provisioning server where the configuration is hosted
  5. Scenario: Reserved for OEM partners: The provisioning URL is hardcoded in the OEM firmware.

Further Documentation

Firmware Release Phone Type Document Type Document Link
Version 2 Image:pdf.gif (not maintained) Description
Version 3 Image:pdf.gif (not maintained) Description
Versions 4, 5, 6, 7, 8 Image:pdf.gif (maintained) Description & Example
Version 1 maintained Description
Version 9 maintained Description & Example

FAQ Links

Can I provide license files via mass deployment?
Can I provide encrypted user passwords via mass deployment?
What does 'Subscribe Config' mean ?
How to trigger the phone to synchronize its settings via mass deployment?

Pages in category "Auto Provisioning"

The following 2 pages are in this category, out of 2 total.

R

Personal tools
Interoperability