Nur für den internen Gebrauch. Inhalt. Inhalt. 0. 1 Overview. These settings will be used for a specific file type if its Use defaults parameter is set to „Yes“. Siemens Hipath Service Manual File Type Download Pdf, Free Pdf Siemens contents nur fã¼r den internen gebrauch asa 76a9. and Log-on Nur für den internen Gebrauch AHM File type For a description of the various file types, see Section
|Published (Last):||25 June 2004|
|PDF File Size:||4.71 Mb|
|ePub File Size:||9.72 Mb|
|Price:||Free* [*Free Regsitration Required]|
Our Quality and Environmental Management Systems are implemented according to the requirements of the ISO and ISO standards and are certified by an external certification company.
Availability and technical specifications are subject to change without notice. All other company, brand, product and service names are trademarks or registered trademarks of their respective holders. Item is Unknown at Phone.
Configuration Items Failed to be Set at Phone. Item is Read Only. PIN entry exceeds max. Moreover, a multitude of interfaces for control, configuration, and provisioning is available: Allows for control and imternen both by the user and the administrator.
Interface to Open Communications – PDF
The phone has inrernen built-in web server enabling both the user and the administrator to control and configure the phone via a standard web browser. A phone management tool for the user which allows for e.
In turn, the phone provides configuration and status information over the fildtyp 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.
Interface to Open Communications
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: Mutual authentication based on individual digital signatures is enforced, in accordance with the TLS standard.
This allows the devices to check the server’s authenticity 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. Further configuration is done via the provisioning service. To enable telephony, the phones are registered at a SIP server. In this case, provisioning service driven interactions may not be possible for details about provisioning service driven interactions, please refer to Section 1.
To enable a solution for this problem, the phone can be configured to periodically poll the provisioning service, or a special proxy, for new messages.
Thus, provisioning service driven interactions are possible even when the provisioning service is located behind a firewall, or in a DMZ. For further information, please refer to Section 1. For a high-level description of the possible interactions, please refer to Section 3, “Basic Communication Procedures”.
This problem is solved with firmware version V3. Protocols When the provisioning service wants to start communicating with a phone, it has to send a special contact-me message. This message, as well as the response from the phone, is transmitted via HTTP clear text, not encrypted.
All further communication between the provisioning service and the phone consists of messages in XML format, which are transmitted using HTTP v1. All further requests of this device are performed on port For information on importing or creating a suitable TLS web server certificate, please refer the relevant documentation for your web server.
Ports On the phone side, the destination port for messages to the provisioning server can be freely chosen. For sending contact-me messages to the phone in order to initiate an interaction, the provisioning service must use port as destination port.
To end a session, the provisioning server sends a special clean-up message to the phone. In some error cases, e. XML messages for phone control and data exchange, and HTML messages for initiating an interaction by the provisioning service.
This is the structure of a URI for a request sent by the phone to the provisioning server: Initial contact-me messages from the provisioning service are transmitted via non-encrypted HTTP.
The POST method is used.
Set to true if a response from the phone is expected. Target IP address for the response from the phone. The parameters described above enable the provisioning service to scan a certain range of IP gebrach for phones simply by sending contact-me requests to each address consecutively.
The complete URI for contact-me messages has the following structure: The HTTP status is no content. To enable provisioning service driven interactions despite this limitation, the phone can be configured to periodically poll the provisioning service, or a special proxy, for new messages.
This configuration is done by the provisioning service, for instance, at phone startup; for the relevant data items, see Section 6. The structure is as follows: To enable an OpenStage phone or OpenScape Desk Phone IP to contact the provisioning service immediately on startup, the appropriate contact address must be provided beforehand.
This can be done by DHCP. Fioetyp, this method prevents faking a gebrajch service with malicious intentions, as the phone will only contact the provisioning service whose address it has learned from the DHCP server. IP address for the phone. Gebfauch mask of the phone.
IP address of the default gateway which is used for connections beyond the subnet. IP addresses of the primary and secondary DNS servers. The SIP server to be used by the phone. The name of the DNS domain wherein the phone is residing. This parameter can be provided by means of a “vendor-encapsulated-options” option.
Enables the phone to contact the provisioning service immediately on startup. This parameter can be provided by means of a vendor-encapsulated-options option. The fixed value is OptiIpPhone. The vendor-encapsulated-options option allows for defining custom-made options in either a single series of bytes or a sequence of parameters which is constructed from: To assign the specific vendor-encapsulated-options to the appropriate devices, the use of classes is recommended.
In the example, the vendor-classes class is divided into subclasses automatically for each vendor-class-identifier option that is received from the clients. Depending on the situation and the intended task, the interaction will be started by the phone or by the provisioning service. First, we will explain the basic message flow.
In order to prevent overflow problems, longer messages can be split into fragments. For details, see Section 3. The message flow might proceed as follows: In an initial HTTPS request, the phone tells the provisioning service that it is ready for operation. In its response, the provisioning service asks for all current settings data items. Hence, the phone sends a complete list of settings, allowing the provisioning service to update its database. If not, the provisioning service should send a CleanUp message, telling the phone not to expect any further messages.
In an initial HTTP request, the provisioning service sends a contact-me message to the phone. The phone responds to this request, and afterwards transmits a basic set of data items containing configuration settings to the provisioning service.
Now, the provisioning service sends a list of data items that have to be changed. If the phone is ready, it will confirm the action and execute the commands or configuration changes. If the phone is busy, it will send an appropriate message to the provisioning service see Section 3.
The phones reaction will imternen to schedule an automatic solicited connection to the provisioning service when the busy condition is cleared. If the phone is downgraded then gebrauvh receipt of a Send-solicited item in a CleanUp action from the provisioning service will result in the pre-existing behaviour.
OpenStage Provisioning Interface Developer’s Guide |
In order to make sure that the desired changes have been made, the provisioning service should send a read request for the modified data. Hereupon, the phone sends back the modified items. Finally, the provisioning service terminates the interaction with a CleanUp message. To enable provisioning service driven interactions despite this limitation, the phone can be configured so that it periodically polls the provisioning service, or a special proxy, for new messages.
The procedure is as follows: On startup, the phone receives the address and port of the provisioning service from the DHCP server. During the startup procedure, the phone contacts the provisioning service see Section 3.
The provisioning service instructs the phone to poll the provisioning service, or a proxy, along with the target URL for the polling messages, and the polling interval see Section 6. From now on, the phone will periodically poll the provisioning service, or proxy, according to the configured polling interval.
In the following message flow, the phone polls the provisioning service or proxy, and the provisioning service resp. Most of the simpler items are defined by the name attribute and the content of the element.
The attributes name and index are used in messages sent by the phone, and in messages sent by the provisioning service. The status attribute only exists in responses from the phone. The item element can have the following attributes: Attribute Value Description name mandatory Enumerated: Tag name Identifier for the item. However, more than one item element may appear within one message See index underneath.