ページ1に含まれる内容の要旨
optiPoint 410 S V6.0
optiPoint 420 S V6.0
XML Configuration Management
Administrator Manual
ページ2に含まれる内容の要旨
xmlTOC.fm Nur für den internen Gebrauch Contents Contents 0 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.1 Overview and Areas of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.2 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 2 XML Configuration Management. . . . . . . .
ページ3に含まれる内容の要旨
xmlTOC.fm Contents Nur für den internen Gebrauch 3.3 Administration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 3.3.1 System Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 3.3.1.1 System config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 3.3.1.2 Device config . . . . . . . . . . . . . . . . . . . . .
ページ4に含まれる内容の要旨
xmlTOC.fm Nur für den internen Gebrauch Contents 3.3.3.23 New SIP password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 3.3.3.24 Message Waiting IP address or DNS name . . . . . . . . . . . . . . . . . . . . . . . . 3-16 3.3.3.25 Emergency number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 3.3.3.26 Voicemail number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ページ5に含まれる内容の要旨
xmlTOC.fm Contents Nur für den internen Gebrauch 3.3.6.9 Logo filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28 3.3.6.10 Java Program filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29 3.3.6.11 LDAP template filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29 3.3.6.12 DSM firmware filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ページ6に含まれる内容の要旨
xmlTOC.fm Nur für den internen Gebrauch Contents 3.3.13.3 Key label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43 3.3.13.4 Select dialling Dial string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43 3.3.13.5 Repertory dial Dial string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44 3.3.13.6 Phone lock Dial string . . . . . . . . . . . . . . . . . . . . . . . . .
ページ7に含まれる内容の要旨
xmlTOC.fm Contents Nur für den internen Gebrauch 3.3.17 Configuration management settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61 3.3.17.1 Deployment Service (DLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61 3.3.17.2 HTTPS IP address or DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62 3.3.17.3 HTTPS Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ページ8に含まれる内容の要旨
xmlTOC.fm Nur für den internen Gebrauch Contents 3.3.21 QoS Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74 3.3.21.1 Send QDC Traps to QCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74 3.3.21.2 QDC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74 3.3.21.3 QDC Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ページ9に含まれる内容の要旨
xmlTOC.fm Contents Nur für den internen Gebrauch 4.3.13 Dial plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 4.3.14 Dialling Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22 4.3.15 Feature Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23 4.3.16 User Mobility. . . . . . . . . . . . . . . . . . . . . .
ページ10に含まれる内容の要旨
xml_01.fm Introduction Overview and Areas of Use 1 Introduction 1.1 Overview and Areas of Use Apart from the standard features users already expect from phones, what functions are impor- tant for the successful operation of a communication solution? The most important functions are mostly not implemented by the end users themselves. During installation and configuration, however, they form a basis that enables phones to be tailored to user requirements. This is the decisive factor that shows w
ページ11に含まれる内容の要旨
xml_01.fm Introduction Overview and Areas of Use ● Simultaneous access for up to five administrators ● Client/server architecture ● Database ● Job management ● Provision of parameters and software for terminals For detailed information on this tool, see the HiPath Deployment Service Administrator Man- ual. Scenario 2: Hosted Office solutions in a carrier/Internet Service Provider (ISP) environ- ment ● Small to medium-size businesses connected to central systems via a WAN or the Internet. ● LAN/
ページ12に含まれる内容の要旨
xml_01.fm Introduction About this Manual 1.2 About this Manual This manual is designed to help you get to know and correctly use XML configuration files. Fol- low these instructions carefully to use the tool as effectively as possible and avoid operating errors. The following chapters contain information on how to use XML configuration management as well as detailed descriptions on how to configure and control terminals. ● XML Configuration Management: This chapter presents the concept and con
ページ13に含まれる内容の要旨
xml_01.fm Introduction About this Manual A31003-J4260-M101-2-76A9, 03-2007 1-4 XML Configuration Management, Administrator Manual
ページ14に含まれる内容の要旨
xml_02.fm XML Configuration Management Procedure and Workflow 2 XML Configuration Management 2.1 Procedure and Workflow optiPoint SIP phones not only provide a direct interface to a management system (Deployment Service), they also permit configuration tasks that are both system-independent and central- ized. In the course of these tasks, configuration parameters are stored as XML files on a server where they can be retrieved independently by each phone. This results in a "loose" connection b
ページ15に含まれる内容の要旨
xml_02.fm XML Configuration Management File Formats If the configuration download setup program is not available, for example, if a configuration up- date server has not been installed, the phone does not initiate a download. In this case, an al- ternative procedure must be used for the configuration update. 2.2 File Formats 2.2.1 Configuration Files Configuration files are stored on the configuration server. There are two kinds of configuration files. 2.2.1.1 System Configuration File The syst
ページ16に含まれる内容の要旨
xml_02.fm XML Configuration Management Download When downloading configuration files, the phone first downloads the system configuration file and then the device configuration file. Each parameter value in the system configuration file overwrites an existing value. Each parameter value in the device configuration file overwrites existing values and values from the system configuration file. 2.3.2 Periodically Checking Configuration Files To ensure that it always retrieves modifiable configura
ページ17に含まれる内容の要旨
xml_02.fm XML Configuration Management Download 2.3.4 Defining Configuration File Parameters in the Phone Parameter WEB settings for Configuration Management (menu ! page 4-25) FTP IP FTP server IP address or DNS name Description: ! page 2-5 FTP Port FTP server port Description: ! page 2-5 Pathname FTP path Description: ! page 2-5 Account ID FTP account name Description: ! page 2-5 User Name FTP username Description: ! page 2-5 Password New FTP password Description: ! page 2-5 Https DL Par
ページ18に含まれる内容の要旨
xml_02.fm XML Configuration Management Download 2.3.5 Description of Download Parameters 2.3.5.1 Config Update FTP IP This parameter contains the IP address of the FTP server used for configuration download. The address and port are normally obtained at startup via DHCP (as a "Vendor Specific" extension), or if this fails, via DNS (as a text record linked to the phones domain name). When it is obtained in this way, the address automatically updates this menu item. If the DHCP or DNS procedu
ページ19に含まれる内容の要旨
xml_02.fm XML Configuration Management Download 2.3.5.9 Config Update Periodic Timer The interval at which the SIP phone automatically checks for configuration file downloads after registration (usually the primary line of a multiline phone). The value "0" deactivates this check. 2.3.5.10 Config Update Unregistration Timer The interval at which the SIP phone checks for configuration file downloads if it cannot perform registration (any line of a multiline phone). 2.3.5.11 Config Update Authent
ページ20に含まれる内容の要旨
xml_02.fm XML Configuration Management Installation 2.4 Installation 2.4.1 DHCP is Available Step 1 In order for it to reach the phone, the FTP, DLS or HTTPS server address must be entered in DHCP option 43. Tag 03 is used to configure the following: ● the FTP server: "FTP://[|][:port"]" ● the HTTPS server "https://[base URL of link on Download Web Server] Option 43 on the DHCP server in the customer LAN must be modified accordingly before any phone is configured. Thi
