Siemens 410 S, 420 S User Manual

optiPoint 410 S V6.0
optiPoint 420 S V6.0

XML Configuration Management

Administrator Manual

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Procedure and Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.2 File Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2.1 Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2.1.1 System Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2.1.2 Device Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.3 Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.3.1 Downloading Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.3.2 Periodically Checking Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.3.3 Automatic Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.3.4 Defining Configuration File Parameters in the Phone . . . . . . . . . . . . . . . . . . . . . 2-4

2.3.5 Description of Download Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.1 Config Update FTP IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.2 Config Update FTP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.3 Config Update Pathname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.4 Config Update Account ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.5 Config Update User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.6 Config Update Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.7 Config Update Filename. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.8 Config Update File Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3.5.9 Config Update Periodic Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.3.5.10 Config Update Unregistration Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.3.5.11 Config Update Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.4.1 DHCP is Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.4.1.1 Further Information on Option 43 (DHCP Support) . . . . . . . . . . . . . . . . . . . . 2-8

2.4.2 DHCP is Not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.4.2.1 DNS Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.4.2.2 Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

3 XML Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Tag Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2 Structure of an XML File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2.1 General and Phone-Specific XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.2.1.1 File names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.2.1.2 XML Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.2.1.3 Implementation in the Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

0-1

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

3.3.2 Network and IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.3.2.1 DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.3.2.2 Terminal IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.3.2.3 Terminal Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.3.2.4 Primary DNS IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

3.3.2.5 Secondary DSN IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

3.3.2.6 Default Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

3.3.2.7 Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3.2.8 Terminal Host name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3.2.9 Route 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3.2.10 Gateway 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3.2.11 Mask 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.3.2.12 Route 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.3.2.13 Gateway 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.3.2.14 Mask 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.3.3 SIP Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.3.3.1 Phone number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.3.3.2 Phone name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.3.3.3 Register by name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.3.3.4 Display ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

3.3.3.5 SIP routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

3.3.3.6 Registrar IP address or DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

3.3.3.7 Registrar IP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

3.3.3.8 Server IP address or DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.3.3.9 Server IP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.3.3.10 Gateway IP address or DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.3.3.11 Gateway IP Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.3.3.12 SIP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.3.13 RTP Base Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.3.14 Outbound proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.3.15 Default ODP domain name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.3.16 SIP transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

3.3.3.17 SIP server type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

3.3.3.18 SIP session timer enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

3.3.3.19 SIP session timer value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

3.3.3.20 Registration timer value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

3.3.3.21 SIP realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

3.3.3.22 SIP user ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

A31003-J4260-M101-2-76A9, 03-2007

0-2 XML Configuration Management, Administrator Manual

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

3.3.3.27 System description Branding/Identity name . . . . . . . . . . . . . . . . . . . . . . . . 3-17

3.3.4 SIP features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

3.3.4.1 Auto answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

3.3.4.2 Beep on auto answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

3.3.4.3 Auto reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

3.3.4.4 Beep on auto reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

3.3.4.5 Refuse call feature enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

3.3.4.6 Allow Transfer on ringing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

3.3.4.7 Allow Join in conference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

3.3.4.8 Group pickup URI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

3.3.4.9 Hot line/warm line – phone type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

3.3.4.10 Hot line/warm line – Default dial string . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

3.3.4.11 initial-digit-timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

3.3.4.12 Conference server URI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

3.3.4.13 Callback – busy URI (only HiPath 8000) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

3.3.4.14 Callback – no reply URI (only HiPath 8000) . . . . . . . . . . . . . . . . . . . . . . . . 3-21

3.3.4.15 Cancel callbacks URI (only HiPath 8000). . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

3.3.4.16 Call park URI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

3.3.4.17 Call pickup URI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

3.3.5 Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

3.3.5.1 Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

3.3.5.2 Layer 2 voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.3.5.3 Layer 2 signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.3.5.4 Layer 2 default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.3.5.5 Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.3.5.6 Layer 3 voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

3.3.5.7 Layer 3 signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

3.3.5.8 VLAN Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

3.3.5.9 Manual VLAN id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

3.3.6 File transfer and phone Download settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.3.6.1 FTP Server Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.3.6.2 FTP account name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.3.6.3 FTP Username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.3.6.4 New FTP password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

3.3.6.5 FTP path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

3.3.6.6 Application filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

3.3.6.7 Configuration filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

3.3.6.8 Hold music filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

0-3

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

3.3.7 Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.3.7.1 SNTP server IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.3.7.2 SNTP server name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.3.7.3 Timezone offset (hours) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.3.7.4 Daylight saving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

3.3.7.5 Local Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

3.3.8 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

3.3.8.1 Management Center Address (IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

3.3.8.2 Management Center Address (name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

3.3.8.3 Management Center Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

3.3.8.4 Send Generic Traps to Management Center. . . . . . . . . . . . . . . . . . . . . . . . . 3-32

3.3.8.5 Send QDC Traps to Management Center . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

3.3.8.6 New Query password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

3.3.8.7 Queries Allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

3.3.9 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

3.3.9.1 Codec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

3.3.9.2 Audio mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3.3.9.3 RTP packet size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3.3.9.4 G.711 Silence Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3.3.9.5 G.711 Microphone Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3.3.10 Ringer Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3.3.11 LAN Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3.3.11.1 LAN port 1 (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

3.3.11.2 LAN port 2 (PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

3.3.12 Multiline Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

3.3.12.1 Originating line preference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

3.3.12.2 Terminating line preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

3.3.12.3 Line key operation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

3.3.12.4 Rollover type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

3.3.12.5 Rollover volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3.3.12.6 Registration LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3.3.12.7 Show focus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3.3.12.8 Use LED to indicate Remote Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3.3.12.9 Reservation timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

3.3.13 Phone function key assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

3.3.13.1 Assigning a Function to a Key (1st key level or normal function key) . . . . . 3-40

3.3.13.2 Assigning a Function to a Key (2nd key level or shifted function key). . . . . 3-42

A31003-J4260-M101-2-76A9, 03-2007

0-4 XML Configuration Management, Administrator Manual

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

3.3.13.7 Feature toggle – Feature Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

3.3.13.8 Feature toggle – description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

3.3.13.9 Line – Primary line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

3.3.13.10 Line – Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3.3.13.11 Line – Hunt ranking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3.3.13.12 Line – Address of record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48

3.3.13.13 Line – Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48

3.3.13.14 Line – User ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

3.3.13.15 Line – Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

3.3.13.16 Line – Shared type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

3.3.13.17 Line – Hot line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

3.3.13.18 Line – Hot line dial string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

3.3.13.19 Line – Intrusion allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

3.3.13.20 Line – Short description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

3.3.13.21 Line – Overview position on DSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

3.3.13.22 Line – Show on DSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3.3.13.23 DSS – Address of record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3.3.13.24 DSS – Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.3.13.25 DSS – User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.3.13.26 DSS – Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.3.13.27 Forwarding – Forward type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

3.3.13.28 Forwarding – Dial string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

3.3.14 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

3.3.14.1 Dial Plan – Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

3.3.14.2 Dial Plan – Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

3.3.14.3 Dial Plan – Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

3.3.14.4 Dial Plan – Digit string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

3.3.15 Dialling Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

3.3.15.1 External Access Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

3.3.15.2 International Dial Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

3.3.15.3 Local Country Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

3.3.15.4 National Dial Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59

3.3.15.5 Local Area Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59

3.3.15.6 Local District Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59

3.3.16 Feature Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60

3.3.16.1 Feature Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60

3.3.16.2 Callback – busy allow (only HiPath 8000) . . . . . . . . . . . . . . . . . . . . . . . . . 3-61

3.3.16.3 Callback – no reply allow (only HiPath 8000) . . . . . . . . . . . . . . . . . . . . . . . 3-61

3.3.16.4 Hot keypad dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

0-5

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62

3.3.17.4 HTTPS – File path for URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62

3.3.17.5 HTTPS – Use secure configuration Download . . . . . . . . . . . . . . . . . . . . . . 3-62

3.3.17.6 FTP – IP address or DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63

3.3.17.7 FTP - Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63

3.3.17.8 FTP – Use non-secure configuration Download . . . . . . . . . . . . . . . . . . . . . 3-63

3.3.17.9 FTP – FTP account name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63

3.3.17.10 FTP – FTP User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64

3.3.17.11 FTP – New FTP password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64

3.3.17.12 FTP – FTP path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64

3.3.17.13 HTTPS/FTP – Configuration Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

3.3.17.14 HTTPS/FTP – Configuration File Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

3.3.17.15 HTTPS/FTP – After registration, check for updates every. . . . . . . . . . . . . 3-65

3.3.17.16 HTTPS/FTP – If registration fails, check for updates every. . . . . . . . . . . . 3-65

3.3.17.17 HTTPS/FTP – Authentication enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.3.18 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.3.18.1 Directory – LDAP server address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.3.18.2 Directory – Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.3.18.3 Address Book – Phone Book server address . . . . . . . . . . . . . . . . . . . . . . . 3-67

3.3.18.4 Address Book – FTP account name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

3.3.18.5 Address Book – FTP User Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

3.3.18.6 Address Book – New FTP password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.3.18.7 Address Book – FTP path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.3.18.8 Address Book – Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.3.18.9 WAP Settings – WAP Server address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

3.3.18.10 WAP Settings – Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

3.3.18.11 WAP Settings – WAP mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

3.3.18.12 WAP Settings – WAP proxy User Name . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.3.18.13 WAP Settings – New WAP proxy password . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.3.18.14 WAP Settings – Help internet URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.3.18.15 WAP Settings – Home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.3.19 Change administrator password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

3.3.20 Survivabilty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

3.3.20.1 Survivabilty – Backup IP address or DNS name . . . . . . . . . . . . . . . . . . . . . 3-71

3.3.20.2 Survivabilty – Backup port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

3.3.20.3 Survivabilty – Backup Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

3.3.20.4 Survivabilty – Backup Registration timer value . . . . . . . . . . . . . . . . . . . . . . 3-72

3.3.20.5 Survivabilty – Backup Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

3.3.20.6 Survivabilty – Backup Outbound Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73

A31003-J4260-M101-2-76A9, 03-2007

0-6 XML Configuration Management, Administrator Manual

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

3.4 User Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.4.1 Change user password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.4.2 Country Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.4.3 Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76

3.4.4 Configuration menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76

3.4.4.1 Lock/unlock configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76

3.4.4.2 Lock/unlock functions in the configuration menu selectively . . . . . . . . . . . . 3-77

3.4.5 Local functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78

3.4.5.1 Lock/unlock local functions menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78

3.4.5.2 Lock/unlock functions in the local menu selectively . . . . . . . . . . . . . . . . . . . 3-78

3.4.6 Function keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

3.4.6.1 Lock/unlock function keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

3.4.6.2 Lock/unlock function keys selectively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80

4 Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Creating a Phone Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.2 Accessing the Administrator Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.2.1 The Administrator Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4.3 Configuration Menus for Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

4.3.1 Network IP Address and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

4.3.2 SIP Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4.3.3 SIP features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

4.3.4 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4.3.5 File transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

4.3.6 Time and Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

4.3.7 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

4.3.8 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

4.3.9 Ringer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

4.3.10 LAN port settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

4.3.11 Multiline operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

4.3.12 Function keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

4.3.12.1 "Selected dialing" Function Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

4.3.12.2 "Line" Function Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

4.3.12.3 "Phone lock" Function Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

4.3.12.4 "Feature toggle" Function Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

4.3.12.5 "Repertory dial" Function Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

4.3.12.6 Function key „DSS“ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

4.3.12.7 Function key "Forwarding" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

0-7

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

4.3.17 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

4.3.17.1 Configuration management settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

4.3.17.2 Error log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

4.3.18 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

4.3.18.1 Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

4.3.18.2 Address Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

4.3.18.3 WAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

4.3.19 Change administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

4.3.20 Survivability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

4.3.21 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

4.3.21.1 QoS Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

4.4 Configuration Menus for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

4.4.1 Change user password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

4.4.2 Country Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

4.4.3 Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32

5 Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1.1 Assignment for Function Key Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

5.2 Device Configuration for Multiline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

5.3 Device Configuration for Single Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

A31003-J4260-M101-2-76A9, 03-2007

0-8 XML Configuration Management, Administrator Manual

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 whether the advantages of IP-based voice services can
also be suitably integrated in the overall solution - from the user to the service provider.

IP terminals offer a range of functions and characteristics that were unknown or technically im­possible 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, train­ing) 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

There are two main scenarios:

Scenario 1: Communication solutions for medium-size and large businesses

This scenario has the following characteristics:

● A stronger focus on internal communication performance, in other words the company

runs key IT components itself. A typical example of this scenario is a Siemens HiPath 8000
real-time communication system installed in a company’s data center.

● Medium to large installations (1000 - 10,000 subscribers).

● Trained personnel available (IT, LAN and server operation), company-performed mainte-

nance or partial implementation of Managed Services.

The Deployment Service Tool (DLS) is best suited to this scenario. This tool enables optiPoint
terminals to be installed as plug-and-play devices and provides a range of high-performance
functions:

● Administration of up to 10,000 subscribers

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

1-1

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/WAN interfaces with NAT and firewalls.

● No company-performed maintenance, outsourcing of (voice) communication services.

● Administrative modifications from outside the customer LAN are either not possible (fire-

walls) or not desired - access to configuration information and software is only required
from the terminal.

A configuration procedure that is based on XML files is ideally suited to this scenario.

A31003-J4260-M101-2-76A9, 03-2007

1-2 XML Configuration Management, Administrator Manual

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 contents of

XML files and provides information on initial phone installation.

● XML Overview: This chapter describes the structure of an XML file and its elements. It lists

available tags and their parameters and provides an example for each case. Tags are sort­ed on the basis of the Web interface and refer to the entry in the corresponding dialog.

● WEB Interface: This chapter contains a graphical presentation of the Web interface with

the possible dialogs and corresponding jump labels for the relevant XML parameter de­scription.

● Sample Configurations: This chapter contains brief examples of system and device con-

figurations together with corresponding references to parameter descriptions.

● Index: This section provides a comprehensive directory for finding terms in the dialogs and

XML parameters.

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

1-3

xml_01.fm

Introduction

About this Manual

A31003-J4260-M101-2-76A9, 03-2007

1-4 XML Configuration Management, Administrator Manual

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
between the management system (which places the configuration files on the server) and the
phones (which may be located in different WANs or LANs). In other words, a phone usually re­trieves the information independently. Downloads are not initiated manually at the phone. Us­ers do not require any knowledge of the LAN structure which means it does not have be to in­cluded in technical considerations.

● The phone can access the server (via FTP or HTTPS)

● The phone can download files independently (after startup or periodically)

● Technicians can trigger a download via a menu option (local administration menu or admin

Web pages)

● Users can trigger a download indirectly via a restart (by entering the restart sequence on

the keypad (- + * 2))

● A management system can trigger a download (SIP NOTIFY message)

If the downloaded configuration files contain information on a new application software version
available, the phone automatically downloads the software from the FTP software server.

The two configuration files are as follows:

● the system configuration file which contains identical parameters (for example, the soft-

ware version or registrar address) for all phones of the same model (for example, optiPoint
410 standard S) and

● the device configuration file which contains parameters for each phone (for example,

phone number).

It is also possible to specify that only the device configuration is loaded. This ensures that only
phone-specific parameters are modified. System-wide parameters that may be have been
modified locally on the phone, for example, are not affected.

The configuration download setup is only designed to configure parameters administered by
technicians. User parameters are not changed during this procedure. For information on con­figuration changes, see ! page 2-4.

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

2-1

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 system configuration file has a unique name for every phone model (for example,
op410adv_conf.xml). This file does not contain any phone-specific parameters (see
3-2).

! page

2.2.1.2 Device Configuration File

Each device configuration file name contains the MAC address of the corresponding phone (for
example, op410adv_conf001E300A9F3.xml). This file only contains phone-specific parame­ters (see ! page 3-2).

2.3 Download

2.3.1 Downloading Configuration Files

Every phone expects a default account named "config" on the FTP server with the password
"config" (the plug-and-play settings are also located in the "Configuration management set­tings" dialog on the phone’s Web interface
been downloaded, the phone checks the file versions. To do this, it searches for a "system­config-version" tag in the system configuration file and a "device-config-version" tag in the de­vice configuration file.

The phone then compares the system configuration file version with the version in the last
download. If the version has changed, the phone executes the write instructions in the system
and device configuration files

If the system configuration file version has not changed but the device configuration file version
has, the phone only executes the write instructions from the device configuration file. If neither
version has changed, the action is terminated.

! page 4-25). Once the configuration files have

A31003-J4260-M101-2-76A9, 03-2007

2-2 XML Configuration Management, Administrator Manual

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 configuration parameters, the phone constantly
updates its configuration by activating a configuration server and periodically downloading con­figuration files (for example, once a day) while logged on to the SIP server.

This is useful in the following two scenarios:

● if the phone’s parameters are out of date because it was unable to download configuration

files (due to an FTP server overload, for instance), it still has the possibility of downloading
all modified new parameters.

● if the phone is in a state that does not support the notification mechanism, for example:

– the user is conducting a call
– the administration menu is currently activated
– the phone’s Web interface is currently in use

The periods between configuration file checks can be modified as required.

2.3.3 Automatic Software Download

The device configuration file contains a tag called "dl-ftp-firmware-filename" which contains the
file name of the current software version. The phone treats this tag differently to other tags. If
the file name in the element is the same as the file name of the current software, the phone
skips this tag and continues processing the other tags in the configuration file.

However, if the file names are different, only the FTP download parameters are configured. Af­ter this configuration, the phone loads the new software and restarts. The configuration files are
reloaded during the restart. The phone now detects that it has the correct software version and
continues processing the remaining tags in the configuration file.

>

Once the download is complete, the optiPoint 410/420 restarts.

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

2-3

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
Description: ! page 2-5

FTP Port
Description: ! page 2-5

Pathname
Description: ! page 2-5

Account ID
Description: ! page 2-5

User Name
Description: ! page 2-5

Password
Description: ! page 2-5

Https DL Params

! page 4-25

Filename
Description: ! page 2-5

FTP server IP address or DNS name

FTP server port

FTP path

FTP account name

FTP username

New FTP password

IP address
IP address port:
File path for URL:

Configuration file name

File Type
Description

: ! page 2-5

Periodic Timer

Configuration file type

After registration, check for updates every n seconds.

Description: ! page 2-6

Unregistration Timer
Description

: ! page 2-6

Authentication

If registration fails, check for updates every n seconds

Authentication enabled

Description: ! page 2-6

A31003-J4260-M101-2-76A9, 03-2007

2-4 XML Configuration Management, Administrator Manual

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 phone’s domain name). When it is obtained
in this way, the address automatically updates this menu item. If the DHCP or DNS procedures
do not provide a valid IP address, the menu item value is used, provided it contains an IP ad­dress (in other words, if it is not empty).

The IP address cannot be modified if it has been obtained via DHCP or DNS. For other sce­narios, the IP address editor can be accessed by clicking OK. The address can then be
changed in this editor. The updated address is used for the next configuration download. The
IP address is set during startup if a valid IP address is obtained via DHCP or DNS.

2.3.5.2 Config Update FTP Port

The FTP server port used for configuration download.

2.3.5.3 Config Update Pathname

The path from the FTP server root directory to the directory that contains the configuration files.

2.3.5.4 Config Update Account ID

The name of the FTP user account that contains the configuration files.

2.3.5.5 Config Update User Name

The name of the FTP user with configuration file authorization.

2.3.5.6 Config Update Password

The FTP password used to download configuration files.

2.3.5.7 Config Update Filename

The name of the system configuration file (also used as a template for the device configuration
file name).

2.3.5.8 Config Update File Type

File name extension for the system configuration file (also used for the device configuration
file).

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

2-5

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 Authentication

This parameter is only used in a BroadSoft environment. It indicates if digest authentication is
required for the check-sync notify message.

A31003-J4260-M101-2-76A9, 03-2007

2-6 XML Configuration Management, Administrator Manual

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://[<host-ip-addr>|<host-name>][: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. This must be done once so that no further intervention is required, no mat­ter how many phones need to be installed or require maintenance.

The following step only applies to FTP and HTTPS servers.

Step 2

Generate the XML files and save them to the FTP or HTTPS server. XML files can either be
generated manually (for example, if you only want to use the model-specific file and not the
phone-specific file) or are generated by the platform management system (for example, Broad­Soft).

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

2-7

xml_02.fm

XML Configuration Management

Installation

2.4.1.1 Further Information on Option 43 (DHCP Support)

As there is no DHCP option for exchanging VLAN information via DHCP, the "Vendor Specific
Information" option (43) is used to encapsulate VLAN and download information. 1The follow­ing diagram illustrates the format of the "Vendor Specific" option.

Byte # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Description

Code

Value 43 20 1 10 ’S’ ’i’ ’e’ ’m’ ’e’ ’n’ ’s’ 0 0 0 2 4 0 0

Length

Option 1 data - "Siemens" identifier

Code

Length

Option 2 data - to
be allocated VID

Code

Length

Padding

Padding

0 0 0 0 0 255

VID HI

VID LO

Padding

Padding

Padding

Code

Byte 1 contains tag "43", "Option 1 data" contains the "Siemens" identifier. The "VLAN ID" is
contained in "Option 2". Five padding bytes (starting at byte 20) and the "Terminate Option 255"
tag in byte 25 complete the option frame.

You must enter the server values if you have to specify a configuration download server for the
configuration update. You can enter the new option before or after the VLAN information but
the five padding bytes (value 0) and the "Terminate Option 255" tag must close the option
frame.

Example:

Code: 3

Length: 21

File: ftp://ftp.siemens.com (or https://www.siemens.com, for example)

20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48

Option 1 data - "ftp server address"

Code

Length

3 21 ’f’ ’t’ ’p’ ’:’ ’/’ ’/’ ’f’ ’t’ ’p’ ’.’ ’s’ ’i’ ’e’ ’m’ ’e’ ’n’ ’s’ ’.’ ’c’ ’o’ ’m’00000255

Padding

Padding

Padding

Padding

Padding

Code

The five padding bytes and the "Terminate Option 255" tag now complete the option frame in
byte 48.

1. Data is transferred from the application layer to the transport layer, where it is assigned a TPC or UDP header
and split into datagrams. The transport layer forwards the datagrams to the network layer which divides them
into packets and assigns them headers.

A31003-J4260-M101-2-76A9, 03-2007

2-8 XML Configuration Management, Administrator Manual

xml_02.fm

XML Configuration Management

Installation

2.4.2 DHCP is Not Available

You can use a DNS TXT record to transfer the FTP, DLS or HTTPS server address to the
phone or you can enter it manually at the terminal.

2.4.2.1 DNS Entry

Step 1

Generate a DNS TXT record with the following parameters:

● for the FTP server

"FTP://[<host-ip-addr>|<host-name>][:port"]"

● for the HTTPS server

"https://[base URL of link on Download Web Server]

The DNS TXT record is generated in the same domain as the phones. The domain name must
be configured in the phone.

The following step only applies to FTP and HTTPS servers.

Step 2

Generate the XML files and save them to the FTP or HTTPS server. XML files can either be
generated manually (for example, if you only want to use the model-specific file and not the
phone-specific file) or are generated by the platform management system (for example, Broad­Soft).

2.4.2.2 Manual

Step 1

Enter the IP address via Web admin or locally at the phone.

Step 2

Generate the XML files and save them to the FTP or HTTPS server. XML files can either be
generated manually (for example, if you only want to use the model-specific file and not the
phone-specific file) or are generated by the platform management system (for example, Broad­Soft).

Step 3

Enter the data required for the configuration download: FTP server, user and password, ac­count and path.

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

2-9

xml_02.fm

XML Configuration Management

Installation

The default user name and user password in the FTP server account data is "config". The set­ting is individual and can be modified.

The server, port, and path must be entered for the HTTPS server.

Step 4

The phone attempts to download the XML files either after manual initiation or a restart. A re­start may be activated after download, depending on the modified parameters the phone re­ceives.

A31003-J4260-M101-2-76A9, 03-2007

2-10 XML Configuration Management, Administrator Manual

xml_03.fm

XML Overview

Tag Structure

3 XML Overview

XML files for system and device configuration contain tags (command lines) which can be used
to configure one or more optiPoint phones.

3.1 Tag Structure

An XML file is a text file that contains "tags" (command lines) which can be edited using a text editor.
XML tags always have the same structure.
A parameter and a value is transferred for optiPoint phones. Each phone function is assigned a param­eter which in turn can have one or more values. Some parameters may be interdependent.
Example:
<Item name="admin-pwd">123456</item>
A tag consists of three parts.
The first part (<Item name="admin-pwd">) specifies which parameters are transferred.
The second part (123456) defines the parameter value, in this example the administration password
"123456". The third part (</Item>) completes the tag.
Indexed XML tags are the exception as they contain an index in an additional fourth part.
Example:
<Item name=“function-key-def“ Index=“5“>1</Item>

This additional index, for example, specifies the number on the keypad or the value in question (in­dex="5").

3.2 Structure of an XML File

An XML file always has the same structure. It starts with the following tags:

<?xml version=“1.0“ encoding=“utf-8“ ?>

This tag describes the text file language (XML version and encoding).

<Message>
<Action>WriteItems</Action>

This tag instructs the phone to process the following tags.

<ItemList>

This chapter contains a list of other configuration tags that form the main part of the XML
file.

</ItemList>
</Message>

These tags complete the XML file.

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

3-1

xml_03.fm

XML Overview

Structure of an XML File

3.2.1 General and Phone-Specific XML Files

Phones load the following two files during every XML upload:

● the general XML file for system-wide configuration.

● the device-specific XML file with settings that apply to specific phone models.

A phone uses the file name and XML header to differentiate between files.

3.2.1.1 File names

The MAC address of the phone is attached to the file name of the device-specific XML file. The
first part of the name is generated using the type and version of the phone and suffixed with
the attribute "_conf" (op410adv_conf). This procedure ensures that a unique name is generat­ed for every type of phone.

Example: op420adv_conf0001e321bb06.xml

The above example is a device-specific configuration file for an optiPoint 420 advance.

The following table contains a list of default file names:

Model System configuration Device configuration

optiPoint 420 advance op420adv_conf.xml op420adv_confyyyyyyyyyyyy.xml

optiPoint 420 default op420std_conf.xml op420std_confyyyyyyyyyy.xml

optiPoint 420 economy plus op420ecop_conf.xml op420ecop_confyyyyyyyyy.xml

optiPoint 420 economy op420eco_conf.xml op420eco_confyyyyyyyyyy.xml

optiPoint 410 advance op410adv_conf.xml op410adv_confyyyyyyyyyyyy.xml

optiPoint 410 default op410std_conf.xml op410std_confyyyyyyyyyyy.xml

optiPoint 410 economy plus op410ecop_conf.xml op410ecop_confyyyyyyyyyy.xml

optiPoint 410 economy op410eco_conf.xml op410eco_confyyyyyyyyyyy.xml

optiPoint 410 entry op410entry_conf.xml op410entry_confyyyyyyyyyy.xml

"yyyyyyyyyyyy" represents each phone’s MAC address.

A31003-J4260-M101-2-76A9, 03-2007

3-2 XML Configuration Management, Administrator Manual

xml_03.fm

XML Overview

Structure of an XML File

3.2.1.2 XML Header

At the start of the item list, you must specify whether the XML file contains a system-wide or
device-specific configuration. The header also contains the current file release.

Example of a system-wide configuration: 0001e321bb06

<Item name = "system-config-version">2005.09.20 09:54 GMT</Item>

Example of a device-specific configuration:

<Item name = "device-config-version">2005.09.20 09:54 GMT</Item>

Make sure you enter spaces before and after the "=" sign.

7

3.2.1.3 Implementation in the Phone

The XML file can be provided via an FTP server (non-secure connection) or via a HTTPS con­nection.

● When using FTP, the IP address, user, password and filename must be entered on the

phone.

● When using HTTPS, the IP address or DNS of the URL, port number and path must be

entered on the phone.

For both types of synchronization you also need to configure the interval time to resynchronize
with the XML file, as well the device filename and extension.

For both procedures, a time interval must be specified in which the synchronization with the
XML file as well as with the device file name and file extension should take place.

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

3-3

xml_03.fm

XML Overview

Administration Tags

3.3 Administration Tags

The sequence of tags described in this section is based on the sequence in WBM and its dia­logs.

3.3.1 System Tag

Determines whether there is a system-wide or device-specific configuration and whether the
file content was modified - in this case via the "Value" field. Every time the content of the "Val­ue" field does not match the previous entry, the phone will read all items in the file. If the content
is unchanged, no action is taken.

3.3.1.1 System config

Parameter system-config-version Start of system-wide configuration

file

Index –

Value 2005.09.20 09:54 GMT Date and time of modification

<Item name = "system-config-version">2005.09.20 09:54 GMT</Item>

Example

Notes Only applies to system-wide configuration - excludes device configuration

Make sure you enter spaces be-
fore and after the "=" sign.

3.3.1.2 Device config

Parameter device-config-version

Index –

Value 2005.09.20 09:54 GMT Date and time of modification

Example <Item name = "device-config-version">2005.09.20 09:54 GMT</Item>

Start of device-specific configura­tion file

Make sure you enter spaces be­fore and after the "=" sign.

Notes Only applies to device-specific configuration - excludes system configuration.

A31003-J4260-M101-2-76A9, 03-2007

3-4 XML Configuration Management, Administrator Manual

Administration Tags

3.3.2 Network and IP Routing

3.3.2.1 DHCP

Parameter dhcp WEB

Index –

Value true, false true = DHCP Discover

false = manual IP address

xml_03.fm

XML Overview

Example <Item name="dhcp">false</Item>

Notes "false": ipaddress, mask, gw-default.

DHCP is switched off

3.3.2.2 Terminal IP address

Parameter ipaddress

Index –

Value 192.168.0.1 IP address for the phone. 4 x 8 bit

Example <Item name="ipaddress">192.168.0.1

</Item>

Notes

dhcp requires: mask, gwdefault

WEB

dec. value separated by "."

Assigns the phone the IP ad­dress: 192.168.0.1.

3.3.2.3 Terminal Mask

Parameter mask WEB

Index –

Value 255.255.255.0 Network mask 4 x 8 bit dec. value

separated by "."

Example <Item name="mask">255.255.255.0</Item>

Notes dhcp, ipaddress, requires: gwdefault

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

Assigns the mask 255.255.255.0

3-5

xml_03.fm

XML Overview

Administration Tags

3.3.2.4 Primary DNS IP address

Parameter dns-server-addr WEB

Index –

Value 172.16.127.2 IP address of the default DNS serv-

er. 4 x 8 bit dec. value separated by
"."

Example <Item name="dns-server-addr">172.16.127.2</Item>

Notes DHCP=false

3.3.2.5 Secondary DSN IP address

Parameter dns-server-addr2

Index –

Value 172.16.127.3 IP address of the secondary DNS

Example <Item name="dns-server-addr2">172.16.127.3</Item>

Notes DHCP=false

WEB

server. 4 x 8 bit dec. value separat­ed by "."

3.3.2.6 Default Route

Parameter gw-default

Index –

Value 192.168.0.1 IP address

Example <Item name="gw-default">192.168.0.1</Item>

Notes DHCP=false, Ip-addr, mask

WEB

A31003-J4260-M101-2-76A9, 03-2007

3-6 XML Configuration Management, Administrator Manual

3.3.2.7 Domain Name

Parameter dns-domain-name WEB

Index –

Value Sample.net Domain name

Example <Item name="dns-domain-name">Sample.net</Item>

Notes DHCP=false

3.3.2.8 Terminal Host name

xml_03.fm

XML Overview

Administration Tags

Parameter host name

Index –

Value ABCabc123 Any name

Example <Item name="Host name">4989722123456</Item>

Notes Model and MAC address. Can also be freely assigned.

WEB

3.3.2.9 Route 1

Parameter route1

Index –

Value 192.168.0.1 IP addr. 4 x 8 bit dec. value sepa-

Example <Item name="route1">192.168.0.1</Item>

Notes

WEB

rated by ","

3.3.2.10 Gateway 1

Parameter gw1

Index –

Value 192.168.0.1 IP addr. 4 x 8 bit dec. value sepa-

Example <Item name="gw1">192.168.0.1</Item>

A31003-J4260-M101-2-76A9, 03-2007
XML Configuration Management, Administrator Manual

WEB

rated by ","

3-7