Difference between revisions of "Mass Deployment"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
(→Scenarios) |
m (→Updated mass deployment according to portfolio) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Breadcrumb|0|0|Glossary}} | ||
| + | |||
This article descibes '''Mass Deployment''' in general for [[OpenStage]] and [[optiPoint]] phones in serveral environments. | This article descibes '''Mass Deployment''' in general for [[OpenStage]] and [[optiPoint]] phones in serveral environments. | ||
| Line 20: | Line 22: | ||
== Scenarios == | == Scenarios == | ||
| + | For OpenStage and Desk Phone IP SIP phones it is recommended using: | ||
| − | * | + | * The OpenScape [[Deployment Service]], see [[DLS Mass Deployment]]. |
| − | * | + | * The [[OpenStage WPI|OpenStage Work Point Interface]] for mass deployment. |
| − | |||
| − | + | For small size deployment and administration tasks additional administration interfaces are available: | |
| − | * | + | * The phone's [[WBM|Web Based Management]], administrator pages with password protection |
| − | * | + | * The phone's local menu and keypad, administrator section with password protection |
| − | + | Notes on older products: | |
| + | * Using [[Mass Deployment XML configuration files]] supported by [[optiPoint 410/420 S|optiPoint 410/420 S family]] only. | ||
| + | * Via [[TFTP]]-Server using [[optiPoint 150 S Mass Deployment procedure]] to automate configuration parameters and firmware upload. | ||
Latest revision as of 14:52, 19 November 2013
This article descibes Mass Deployment in general for OpenStage and optiPoint phones in serveral environments.
Deployment
The installation of an IP phone in general requires integrating the phone into an IP infrastructure specific to the customer's or user's needs. This integration normally requires some activities on all components involved, i.e. on the IP phone and on other components like application servers and routers.
Additionally to the hardware related tasks like providing LAN cables and setting up the necessary power supply, this integration also covers adapting the IP phone to the individual customer configuration by setting various parameters to appropriate values. In this article we will use the term "deployment" for this task, including the provisioning of new software to the IP phone. Sometimes the term "provisioning" is used instead of "deployment”.
Individual phones can be easily set up using the local menue and the keypad or - more comfortable and even remotely - the phone's web administration. Larger companies or voice service providers have to install and maintain hundreds or thousands of phones, requiring mass deployment capabilities.
Requirements
IP terminals offer a range of functions and characteristics that were unknown or technically impossible in analog or early digital system environments (for example, ISDN). But increased product flexibility requires more complex technology. For this reason, it is essential that VoIP devices be optimally configured for users while at the same time expenditure (costs, time, training) must be kept to a minimum for service providers.
Different scenarios have different requirements. However the following factors are critical for all solutions:
- Minimum network intervention or modification
- No inflexible or costly preconfiguration at the terminal
- No or minimum (one-off) user activities
Scenarios
For OpenStage and Desk Phone IP SIP phones it is recommended using:
- The OpenScape Deployment Service, see DLS Mass Deployment.
- The OpenStage Work Point Interface for mass deployment.
For small size deployment and administration tasks additional administration interfaces are available:
- The phone's Web Based Management, administrator pages with password protection
- The phone's local menu and keypad, administrator section with password protection
Notes on older products:
- Using Mass Deployment XML configuration files supported by optiPoint 410/420 S family only.
- Via TFTP-Server using optiPoint 150 S Mass Deployment procedure to automate configuration parameters and firmware upload.
