Mass Deployment - Revision history

Christian.kaehler: /* Updated mass deployment according to portfolio*/

2013-11-19T14:52:20Z

‎Updated mass deployment according to portfolio

2011-04-25T12:29:42Z

2009-02-09T15:41:17Z

2008-07-15T14:41:52Z

‎Scenarios

2008-06-13T12:12:03Z

Sorting out DLS, XML and TFPT deployment

2007-10-11T09:34:31Z

‎Scenarios

2007-10-11T09:34:18Z

‎Scenarios

2007-10-11T09:33:48Z

‎Scenarios

2007-10-11T09:32:25Z

2007-10-11T09:13:17Z

‎See also

@@ Line 22: / Line 22: @@
 == Scenarios ==
-* Using the [[Deployment Service]]<ref name="notDLSintegr">[[optiPoint 150 S]] is not integrated in this scenario.</ref>, see [[DLS Mass Deployment]].
+* The OpenScape [[Deployment Service]], see [[DLS Mass Deployment]].
-* Using [[Mass Deployment XML configuration files]]<ref name="notintegr"> [[optiPoint 410/420 S|optiPoint 410/420 S family]] only.</ref>
+* The [[OpenStage WPI|OpenStage Work Point Interface]] for mass deployment.
-In addition to this further scenarios for single deployment and administration are available (administrators only):
+For small size deployment and administration tasks additional administration interfaces are available:
-* Using the phone's [[WBM|Web Based Management]].
+* The phone's [[WBM|Web Based Management]], administrator pages with password protection
-* Locally using dialpad and phone menu.
+* 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.
-<references />
+* Via [[TFTP]]-Server using [[optiPoint 150 S Mass Deployment procedure]] to automate configuration parameters and firmware upload.

← Older revision		Revision as of 12:29, 25 April 2011
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 24: / Line 24: @@
 * Using [[Mass Deployment XML configuration files]]<ref name="notintegr"> [[optiPoint 410/420 S|optiPoint 410/420 S family]] only.</ref>
 * Via [[TFTP]]-Server using [[optiPoint 150 S Mass Deployment procedure]]<ref name="150S">[[optiPoint 150 S]] only.</ref> to automate configuration parameters and firmware upload.
 In addition to this further scenarios for single deployment and administration are available (administrators only):
 * Using the phone's [[WBM|Web Based Management]].
 * Locally using dialpad and phone menu.
 <references />

@@ Line 22: / Line 22: @@
 * Using the [[Deployment Service]]<ref name="notDLSintegr">[[optiPoint 150 S]] is not integrated in this scenario.</ref>, see [[DLS Mass Deployment]].
-* Using [[Mass Deployment XML configuration files]]<ref name="notintegr"> [[optiPoint 410/420 S|optiPoint 410/420 S family]] only </ref>
+* Using [[Mass Deployment XML configuration files]]<ref name="notintegr"> [[optiPoint 410/420 S|optiPoint 410/420 S family]] only.</ref>
 * Via [[TFTP]]-Server using [[optiPoint 150 S Mass Deployment procedure]]<ref name="150S">[[optiPoint 150 S]] only.</ref> to automate configuration parameters and firmware upload.
@@ Line 28: / Line 28: @@
 * Using the phone's [[WBM|Web Based Management]].
 * Locally using dialpad and phone menu.
 <references />

@@ Line 21: / Line 21: @@
 == Scenarios ==
-* Using the [[Deployment Service]]<ref name="notintegr">[[optiPoint 150 S]] is not integrated in this scenario.</ref>, see [[DLS Mass Deployment]].
+* Using the [[Deployment Service]]<ref name="notDLSintegr">[[optiPoint 150 S]] is not integrated in this scenario.</ref>, see [[DLS Mass Deployment]].
-* Using [[Mass Deployment XML configuration files]]<ref name="notintegr" /> ([[SIP]] only).
+* Using [[Mass Deployment XML configuration files]]<ref name="notintegr"> [[optiPoint 410/420 S|optiPoint 410/420 S family]] only </ref>
-* Via [[TFTP]]-Server using [[optiPoint 150 S Mass Deployment procedure]]<ref name="150S">optiPoint 150 S only.</ref> to automate configuration parameters and firmware upload.
+* Via [[TFTP]]-Server using [[optiPoint 150 S Mass Deployment procedure]]<ref name="150S">[[optiPoint 150 S]] only.</ref> to automate configuration parameters and firmware upload.
 In addition to this further scenarios for single deployment and administration are available (administrators only):

@@ Line 9: / Line 9: @@
 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.
-== How it works ==
+== Requirements ==
 IP terminals offer a range of functions and characteristics that were unknown or technically impossible
@@ Line 19: / Line 19: @@
 * No or minimum (one-off) user activities
-There are two main scenarios:
+== Scenarios ==
-* Using the [[Deployment Service]], see [[DLS Mass Deployment]] or
+* Using the [[Deployment Service]], see [[DLS Mass Deployment]]<ref name="notintegr">[[optiPoint 150 S]] is not integrated in this scenario.</ref>.
-* using [[Mass Deployment XML configuration files]] ([[SIP]] only).
+* Using [[Mass Deployment XML configuration files]] ([[SIP]] only)<ref name="notintegr" />.
-== See also ==
+In addition to this further scenarios for single deployment and administration are available (administrators only):
-* [[optiPoint 150 S Mass Deployment procedure]]

← Older revision		Revision as of 09:13, 11 October 2007
Line 25:		Line 25:

	== See also ==		== See also ==
		+
		+	* [[optiPoint 150 S Mass Deployment procedure]]