Getting Started; Overview - Unify OpenStage Developer's Manual

Provisioning interface
Table of Contents

Advertisement

Nur für den internen Gebrauch
1

Getting Started

1.1

Overview

OpenStage SIP phones and OpenScape Desk Phones IP support the SIP protocol according
to RFC 3261 and therefore can operate at any standard-compliant SIP server.
Moreover, a multitude of interfaces for control, configuration, and provisioning is available:
Local user interface, graphical or text based: Allows for control and configuration both by
the user and the administrator.
Web-based interface: The phone has a built-in web server enabling both the user and the
administrator to control and configure the phone via a standard web browser.
Phone manager: A phone management tool for the user which allows for e. g. editing the
local phonebook and synchronizing it with MS Outlook contact data. The software, which
communicates over IP, is installed on the user's PC (Windows 2000, Windows XP, or Win-
dows 7/8)
Provisioning interface: The phone is controlled and configured by messages in XML for-
mat which are transmitted by HTTPS. In turn, the phone provides configuration and status
information over the same interface. Moreover, when local changes have been executed
on the phone, it informs the provisioning service automatically. Any kind of administration
task is supported, such as updating the firmware on a selection of phones. Hence, mass
deployment can be accomplished conveniently. Unlike many other VoIP phones, which are
limited to prefabricated configuration files to be downloaded at startup, OpenStage phones
can be deployed and provisioned by an interactive service at virtually any time.
The interface supports two different Security Modes:
Default Mode: The devices cannot directly validate the authenticity of the provisioning
server, but must rely on appropriate IP address / DHCP configuration only.
Secure Mode: Mutual authentication based on individual digital signatures is enforced,
in accordance with the TLS standard. This allows the devices to check the server's au-
thenticity directly. The required certificates and private keys are generated, managed
and distributed by provisioning service.
This document contains information about the required infrastructure and describes the
provisioning interface in detail.
A31003-S2000-R102-16-7620, 02/2016
Provisioning Service, Developer's Guide
c01.fm
Getting Started
Overview
7

Advertisement

Table of Contents
loading

This manual is also suitable for:

Openscape

Table of Contents