Unify CP200, CP400, CP600 Administrator Documentation

Download

Page 1

OpenScape Desk Phone CP200/400/600  Phone Administration

Administrator Documentation

A31003-C1000-M101-1-76A9

Page 2

Our Quality and Environmental Management Systems are implemented according to the requirements of the ISO9001 and ISO14001 standards and are certified by an external certification company.



Reference No.: A31003-C1000-M101-1-76A9

The information provided in this document contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products. An obligation to provi de the respective characteristics shall only exist if expressly agreed in the terms of contract.

Availability and technical specifications are subject to change without notice.

Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and Solutions GmbH & Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.



unify.com

Page 3

TOC.fm

Nur für den internen Gebrauch Content

Content 0

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

1.1 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

1.2 Maintenance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.3 Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.4 About the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.5 Conventions for this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

1.6 The OpenScape Desk Phone CP Family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

1.6.1 OpenScape Desk Phone CP600. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

1.6.2 OpenScape Desk Phone CP400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

1.6.3 OpenScape Desk Phone CP200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

1.7 Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

1.7.1 Web-based Management (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

1.7.2 DLS (OpenScape Deployment Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

1.7.3 Local Phone Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

1.7.4 OpenStage Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

2 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

2.2 Assembling and Installing the Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

2.2.1 Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

2.2.2 Connectors at the bottom side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

2.2.3 Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

2.2.4 How to Connect the Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

2.2.5 How to Better Use LAN Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

2.2.6 Key Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

2.3 Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

2.3.1 How to Access the Web Interface (WBM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

2.3.2 How to Set the Terminal Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

2.3.3 Basic Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

2.3.4 DHCP Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

2.3.5 Date and Time / SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

2.3.6 SIP Server Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

2.3.7 Extended Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

2.3.8 Vendor Specific: VLAN Discovery and DLS Address . . . . . . . . . . . . . . . . . . . . . 2-27

2.3.8.1 How to Use a Vendor Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

2.3.8.2 How to Use Option #43 "Vendor Specific" . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

2.3.9 DLS Server Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

2.3.9.1 Using Vendor Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

2.3.9.2 Using Option #43 "Vendor Specific" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

2.3.10 Using the Web Interface (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

2.3.11 Using the Local Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 4

TOC.fm

Content Nur für den internen Gebrauch

3 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

3.1 Access via Local Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

3.2 Bluetooth Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3.3 LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3.3.1 LAN Port Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3.3.2 VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

3.3.2.1 Automatic VLAN discovery using LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . 3-50

3.3.2.2 Automatic VLAN discovery using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

3.3.2.3 Manual configuration of a VLAN ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

3.4 IP Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.4.1 Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.4.1.1 Layer 2 / 802.1p. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.4.1.2 Layer 3 / Diffserv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

3.4.2 Protocol Mode IPv4/IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

3.4.3 Use DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59

3.4.4 IP Address - Manual Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62

3.4.5 Default Route/Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64

3.4.6 Specific IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.4.7 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.4.7.1 DNS Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.4.7.2 DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

3.4.7.3 Terminal Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.4.8 Configuration & Update Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

3.4.9 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

3.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

3.5.1 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

3.5.2 SRTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78

3.5.3 Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

3.5.4 Security Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81

3.5.5 Security-Related Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82

3.5.6 Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83

3.5.6.1 General Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83

3.5.6.2 Admin Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84

3.5.6.3 Character Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

3.5.6.4 Change Admin and User password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

3.5.7 Certificate Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86

3.5.7.1 Online Certificate Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86

3.5.7.2 Server Authentication Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

3.6 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88

3.6.1 Terminal and User Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88

3.6.1.1 Terminal Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88

3.6.1.2 Display Identity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88

3.6.2 Emergency and Voice Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89

3.6.3 Energy Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90

A31003-C1000-M101-1-76A9, 03/2016

4 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 5

TOC.fm

Nur für den internen Gebrauch Content

3.6.3.1 Backlight Time Setting (OpenScape Desk Phone CP600 only) . . . . . . . . . . 3-90

3.6.3.2 Energy Efficient Ethernet (OpenScape Desk Phone CP200 only) . . . . . . . . 3-91

3.6.4 Call logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

3.6.4.1 Logging of Missed Calls (via User menu). . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93

3.6.5 Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94

3.6.5.1 SNTP is Available, but no Automatic Configuration by DHCP Server . . . . . 3-95

3.6.5.2 No SNTP Server Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96

3.6.6 SIP Addresses and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97

3.6.6.1 SIP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97

3.6.6.2 SIP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99

3.6.7 SIP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

3.6.8 SIP Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103

3.6.8.1 Outbound Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103

3.6.8.2 SIP Transport Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104

3.6.8.3 SIP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104

3.6.8.4 Media/SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106

3.6.8.5 Early 183 response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107

3.6.9 SIP Session Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108

3.6.10 Resilience and Survivability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110

3.6.10.1 Connectivity Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111

3.6.10.2 Response Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112

3.6.10.3 Non-INVITE Transaction Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114

3.6.10.4 Maximum Registration Backoff Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115

3.6.10.5 Backup SIP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116

3.6.11 Interactive Connectivity Establishment (ICE) . . . . . . . . . . . . . . . . . . . . . . . . . 3-118

3.6.11.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118

3.6.11.2 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118

3.6.11.3 Candidates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120

3.6.11.4 Technical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120

3.7 Feature access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

-121

3.8 Feature Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124

3.8.1 Allow Refuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124

3.8.2 Hot/Warm Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125

3.8.3 Initial Digit Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126

3.8.4 Group Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

3.8.4.1 Feature Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

3.8.4.2 Pickup alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

3.8.5 Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130

3.8.5.1 Transfer on Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130

3.8.5.2 Transfer on Hangup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130

3.8.6 Callback URIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132

3.8.6.1 Call Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133

3.8.7 Message Waiting Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134

3.8.8 Indicate Messages . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 6

TOC.fm

Content Nur für den internen Gebrauch

3.8.9 System Based Conference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136

3.8.10 Server Based Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137

3.8.11 uaCSTA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139

3.8.12 Local Menu Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140

3.8.13 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141

3.9 Free Programmable Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-144

3.9.1 How to Configure Free Programmable Keys (FPKs) . . . . . . . . . . . . . . . . . . . . . 3-144

3.9.2 How to Enable "Long Press" for Free Programmable Keys . . . . . . . . . . . . . . . . 3-144

3.9.3 Clear (no feature assigned) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146

3.9.4 Selected Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146

3.9.5 Repeat Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147

3.9.6 Call Forwarding (Standard) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147

3.9.7 Call Forwarding by Call Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-148

3.9.8 Ringer Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-150

3.9.9 Hold . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-150

3.9.10 Alternate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151

3.9.11 Blind Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151

3.9.12 Transfer Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152

3.9.13 Deflect a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153

3.9.14 Shift Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153

3.9.15 Phone-Based Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154

3.9.16 Accept Call via Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154

3.9.17 Do Not Disturb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

3.9.18 Group Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

3.9.19 Repertory Dial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156

3.9.20 Feature Toggle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157

3.9.21 Mobility / Mobile User Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157

3.9.22 Directed Pickup . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158

3.9.23 Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158

3.9.23.1 Cancel Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-159

3.9.24 Pause Callbacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-159

3.9.25 Resume Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160

3.9.26 Consultation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160

3.9.27 Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-161

3.9.28 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-161

3.9.28.1 Auto Answer With Zip Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-162

3.9.29 Server Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-162

3.9.30 BLF Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-163

3.9.31 Send Request via HTTP/HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-163

3.9.32 Built-in Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-166

3.9.33 2nd Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-166

3.9.34 Start Phonebooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-167

3.9.35 Show phone screen (OpenScape Desk Phone CP200 only) . . . . . . . . . . . . . . 3-167

3.9.36 Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-168

A31003-C1000-M101-1-76A9, 03/2016

6 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 7

TOC.fm

Nur für den internen Gebrauch Content

3.10 Fixed Function Keys on OpenScape Desk Phone CP200. . . . . . . . . . . . . . . . . . . 3-168

3.11 Multiline Appearance/Keyset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-169

3.11.1 Line Key Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-169

3.11.2 How to Configure Line Keys for Keyset Operation . . . . . . . . . . . . . . . . . . . . . 3-172

3.11.3 Configure Keyset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-174

3.11.4 Line Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-179

3.11.4.1 Preview and Preselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-180

3.11.5 Immediate Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-181

3.11.6 Direct Station Select (DSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-181

3.11.6.1 General DSS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-182

3.11.6.2 Settings for a DSS key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-183

3.11.7 Distinctive Ringers per Keyset Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-185

3.12 Key Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-188

3.13 Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-188

3.13.1 Canonical Dialing Configuration . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . 3-188

3.13.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193

3.13.3 Phone location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-195

3.13.4 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-196

3.14 Ringer Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-197

3.14.1 Distinctive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-197

3.14.2 Map to Specials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-200

3.14.3 Special Ringers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-200

3.15 Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-203

3.16 Transferring Phone Software, Application, and Media Files . . . . . . . . . . . . . . . . . 3-205

3.16.1 FTP/HTTPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-205

3.16.2 Common FTP/HTTPS Settings (Defaults). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-205

3.16.3 Phone Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-207

3.16.3.1 Upgrade using File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-207

3.16.3.2 Upgrade using FTP/HTTPS . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . 3-208

3.16.3.3 Download/Update Phone Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-210

3.16.4 Picture Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-211

3.16.4.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-211

3.16.4.2 Download Picture Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-213

3.16.5 LDAP Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-214

3.16.5.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-214

3.16.5.2 Download LDAP Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-216

3.16.6 Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-217

3.16.6.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-217

3.16.6.2 Download Logo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-219

3.16.7 Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-220

3.16.7.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-220

3.16.7.2 Download Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-222

3.16.8 Ringer File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-223

3.16.8.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-224

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 8

TOC.fm

Content Nur für den internen Gebrauch

3.16.8.2 Download Ringer File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-226

3.16.9 Dongle Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-227

3.16.9.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-227

3.16.9.2 Download Dongle Key File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-229

3.17 Corporate Phonebook: Directory Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-230

3.17.1 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-230

3.18 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-232

3.18.1 RTP Base Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-232

3.18.2 Codec Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233

3.18.3 Audio Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-235

3.19 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-235

3.19.1 Troubleshooting: Lost Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-236

3.20 Restart Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-237

3.21 Factory Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-237

3.22 SSH – Secure Shell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-237

3.23 Display License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-238

3.24 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-239

3.24.1 Display General Phone Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-239

3.24.2 View Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-240

3.24.3 User Access to Diagnostic Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-240

3.24.4 Diagnostic Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-241

3.24.5 LAN Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-243

3.24.6 LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-244

3.24.7 IP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-246

3.24.8 Process and Memory Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-247

3.24.9 Fault Trace Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-249

3.24.10 EasyTrace Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-255

3.24.10.1 Bluetooth handsfree profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-255

3.24.10.2 Bluetooth headset profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-255

3.24.10.3 Call Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-256

3.24.10.4 Call Log Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-257

3.24.10.5 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-257

3.24.10.6 DAS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-258

3.24.10.7 DLS Data Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-258

3.24.10.8 Help Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-259

3.24.10.9 Key Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-259

3.24.10.10 LAN Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-260

3.24.10.11 Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-260

3.24.10.12 Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261

3.24.10.13 Phone administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261

3.24.10.14 Local Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-262

3.24.10.15 LDAP Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-262

3.24.10.16 Server based applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-263

3.24.10.17 Sidecar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-263

A31003-C1000-M101-1-76A9, 03/2016

8 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 9

TOC.fm

Nur für den internen Gebrauch Content

3.24.10.18 SIP standard multiline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-263

3.24.10.19 SIP standard singleline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-264

3.24.10.20 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-264

3.24.10.21 Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-265

3.24.10.22 Voice Dialling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-266

3.24.10.23 Web Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-266

3.24.10.24 802.1x problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-267

3.24.10.25 No Tracing for All Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-267

3.24.11 Bluetooth Advanced Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-267

3.24.12 M5T Advanced Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-267

3.24.13 QoS Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-269

3.24.13.1 Conditions and Thresholds for Report Generation . . . . . . . . . . . . . . . . . 3-269

3.24.13.2 View Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-272

3.24.14 Core dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-276

3.24.15 Remote Tracing – Syslog . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . 3-277

3.24.16 HPT Interface (For Service Staff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-278

3.25 MWI LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-279

3.26 Missed Call LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-279

3.27 Impact Level Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-281

4 Technical Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284

4.1 Default Port List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284

4.2 Troubleshooting: Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-286

5 Examples and HowTos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-288

5.1 Canonical Dialing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-288

5.1.1 Canonical Dialing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-288

5.1.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-289

5.1.2.1 Conversion examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-290

5.2 How to Create Logo Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-292

5.2.1 For OpenScape Desk Phone CP600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-292

5.3 How to Set Up the Corporate Phonebook (LDAP). . . . . . . . . . . . . . . . . . . . . . . . . . 5-295

5.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-295

5.3.2 Create an LDAP Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-296

5.3.3 Load the LDAP Template onto the Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-300

5.3.4 Configure LDAP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-301

5.3.5 Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-301

5.4 An LLDP-Med Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-304

5.5 Example Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-306

5.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-306

5.5.2 Dial Plan Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-306

5.5.3 How To Set Up And Deploy A Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-308

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-311

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

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 10

uebersicht.fm

Overview

Important Notes

1Overview

1.1 Important Notes

Do not operate the equipment in environments where there is a danger of explosions.

If Power over Ethernet (PoE) is not available: For safety reasons the phone should only be operating using the supplied plug-in power unit.

Use only original accessories. Using other accessories may be dangerous and will invalidate the warranty, extended manufacturer’s liability and the CE mark.

Never open the telephone or add-on equipment. If you encounter any problems, contact System Support.

Installation requirement for USA, Canada, Norway, Finland, and Sweden: Connection to networks which use outside cables is prohibited. Only in-house networks are permitted.

For USA and Canada only:

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician for help.

This product is a UL Listed Accessory, I.T.E., in U.S.A. and Canada.

This equipment also complies with the Part 68 of the FCC Rules and the Industrie Canada CS-03.

A31003-C1000-M101-1-76A9, 03/2016

10 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 11

1.2 Maintenance Notes

Do not perform maintenance work or servicing of the telephone in environments where there is a danger of explosions.

Use only original accessories. Using other accessories may be dangerous and will invalidate the warranty and the CE mark.

Never open the telephone or a key module. If you encounter any problems, contact System Support.

1.3 Labeling

The compliance of the equipment according to EU directives is confirmed by the CE mark. This Declaration of Conformity and, where applicable, other existing declarations of conformity as well as further information on regulations that restrict the usage of substances or affect the declaration of substances used in products can be found in the Unify Expert WIKI at http://wiki.unify.com under the section “Declarations of Conformity”.

uebersicht.fm

Overview

Maintenance Notes

1.4 About the Manual

The instructions within this manual will help you in administering and maintaining OpenScape Desk Phone CP telephones. The instructions contain important information for safe and proper operation of the phones. Follow them carefully to avoid improper operation and get the most out of your multi-function telephone in a network environment.

This guide is intended for service providers and network administrators who administer VoIP services using the OpenScape Desk Phone CP and who have a fundamental understanding of VoIP, SIP, IP networking, and telephony. The tasks described in this guide are not intended for end users.

These instructions are laid out in a user-oriented manner, which means that you are led through the functions of the OpenScape Desk Phone CP step by step, wherever expedient. For the users, a separate manual is provided.

You can find further information on the official Unify website (http://www.unify.com/) and on the Unify Wiki (http://wiki.unify.com/).

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 12

uebersicht.fm

Overview

Conventions for this Document

1.5 Conventions for this Document

The terms for parameters and functions used in this document are derived from the web interface (WBM). In some cases, the phone’s local menu uses shorter, less specific terms and abbreviations. In a few cases the terminologies differ in wording. If so, the local menu term is added with a preceding "/".

For the parameters described in this document, a WBM screenshot and the path in the local phone menu is provided.

This document describes the software version V3R4.

A31003-C1000-M101-1-76A9, 03/2016

12 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 13

The OpenScape Desk Phone CP Family

1.6 The OpenScape Desk Phone CP Family

The OpenScape Desk Phone CP phone family comprises the following devices.

• Section 1.6.1, “OpenScape Desk Phone CP600”

• Section 1.6.2, “OpenScape Desk Phone CP400”

• Section 1.6.3, “OpenScape Desk Phone CP200”

uebersicht.fm

Overview

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 14

uebersicht.fm

Overview

The OpenScape Desk Phone CP Family

1.6.1 OpenScape Desk Phone CP600

1 With the Handset, the user can pick up and conduct calls in the usual manner.

2 The Microphone is used in the speakerphone mode.

3 The Display provides intuitive support for telephone operation.

4 With the Menu Key, the user/administrator has access to the user/administrator menu.

5 With the Navigation Keys, the user/administrator can navigate through the various phone functions.

6 With the Soft Keys, the user/administrator can operate the phone´s functions.

7 Audio Keys:

+ and -: Increases/decreases the speaker/headset and handset volume. Mute: Turns off/on the microphone during conversations. Speaker: Turns on/off the hands-free mode (speakerphone). Headset: Switches the audio between handset/speakerphone and headset

8 The Notification LED visually signals incoming calls and new voice messages.

9 The Keypad is used for entering phone numbers and text.

10 The Out-of-Office Key provides an easy way to set up Call Deflection and DND.

Tabelle 1-1

14 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 15

1.6.2 OpenScape Desk Phone CP400

uebersicht.fm

Overview

The OpenScape Desk Phone CP Family

1 With the Handset, the user can pick up and conduct calls in the usual manner.

2 The Microphone is used in the speakerphone mode.

3 The Display provides intuitive support for telephone operation.

4 With the Menu Key, the user/administrator has access to the user/administrator menu.

5 With the Navigation Keys, the user/administrator can navigate through the various phone functions.

6 With the Context Keys, the user/administrator can operate the phone´s functions.

7 Audio Keys:

8 The Notification LED visually signals incoming calls and new voice messages.

9 The Keypad is used for entering phone numbers and text.

10 The Out-of-Office Key provides an easy way to set up Call Deflection and DND.

11 The Free programmable Keys can be set up with various functions defined by user.

Tabelle 1-2

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 16

uebersicht.fm

Overview

The OpenScape Desk Phone CP Family

1.6.3 OpenScape Desk Phone CP200

1 With the Handset, the user can pick up and conduct calls in the usual manner.

2 The Microphone is used in the speakerphone mode.

3 The Display provides intuitive support for telephone operation.

4 Conversation Keys:

Hold: Places a call in hold. Transfer: Transfers a current call to another party. Conference: Initiates a conference call.

5 With the Menu Key, the user has access to the user menu.

6 With the Messages Key, the user has access to the voicemail and the call log.

7 With the Navigation Keys, the user/administrator can navigate through the various phone functions.

8 With the Function Keys, the user can comfortably operate the phone´s functions like Conversations,

Phonebook, Call Deflection and Redial.

9 The Keypad is used for entering phone numbers and text.

10 Audio Keys:

11 The Notification LED visually signals incoming calls and new voice messages.

Tabelle 1-3

A31003-C1000-M101-1-76A9, 03/2016

16 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 17

uebersicht.fm

Overview

Administration Interfaces

1.7 Administration Interfaces

You can configure the OpenScape Desk Phone CP by using any of the methods described in this chapter.

1.7.1 Web-based Management (WBM)

This method employs a web browser for communication with the phone via HTTPS. It is applicable for remote configuration of individual IP phones in your network. Direct access to the phone is not required.

To use this method, the phone must first obtain IP connectivity.

1.7.2 DLS (OpenScape Deployment Service)

The OpenScape Deployment Service (DLS) is an OpenScape Management application for administering phones and soft clients in both OpenScape and non-OpenScape networks. It has a Java-supported, web-based user interface, which runs on an internet browser. For further information, please refer to the OpenScape Deployment Service Administration Guide.

1.7.3 Local Phone Menu

This method provides direct configuration of the OpenScape Desk Phone CP via the local phone menu. Direct access to the phone is required.

As long as the IP connection is not properly configured, you have to use this method

to set up the phone.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 18

uebersicht.fm

Overview

Administration Interfaces

1.7.4 OpenStage Manager

This program offers you an additional option for tailoring your OpenScape Desk Phone CP to your personal needs. Further information please find under:

http://wiki.unify.com/wiki/OpenStage_Manager.

Features

• Phonebook management

• Synchronisation of contacts

• Save and restore

• Key programming

• Ringtones

• Assignment of images to contacts (OpenScape Desk Phone CP600)

• Screensaver (OpenScape Desk Phone CP600)

Contact your administrator for the latest version of OpenStage Manager. The feature availablity depends on phonetype.

A31003-C1000-M101-1-76A9, 03/2016

18 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 19

inbetriebnahme.fm

Startup

Prerequisites

2Startup

2.1 Prerequisites

The OpenScape Desk Phone CP acts as an endpoint client on an IP telephony network, and has the following network requirements:

• An Ethernet connection to a network with SIP clients and servers.

Only use switches in the LAN to which the OpenScape Desk Phone CP phone

• OpenScape Voice server.

• An FTP Server for file transfer, e. g. firmware, configuration data, application software

• A DHCP (Dynamic Host Configuration Protocol) server (recommended).

• DLS (OpenScape Deployment Service) for advanced configuration and software deployment (recommended).

is connected. An operation at hubs can cause serious malfunctions in the hub and in the whole network.

For additional information see: http://wiki.unify.com/wiki/IEEE_802.1x.

2.2 Assembling and Installing the Phone

2.2.1 Shipment

• Phone

• Handset

• Handset cable

• Subpackage: – Document "Information and Important Operating Procedures" – Emergency number sticker

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 20

inbetriebnahme.fm

Headset

Handset

Network Switch

PC (eg. Phone Manager)

Key Module (max. 4)

Power supply (if required)

Service Interface

Startup

Assembling and Installing the Phone

2.2.2 Connectors at the bottom side

OpenScape Desk Phone CP600

A31003-C1000-M101-1-76A9, 03/2016

20 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 21

OpenScape Desk Phone CP400

Headset

Handset

Network Switch

PC (eg. Phone Manager)

Key Module (max. 2)

Service Interface

Power supply (if required)

inbetriebnahme.fm

Startup

Assembling and Installing the Phone

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 22

inbetriebnahme.fm

Headset

Handset

Network Switch

PC (eg. Phone Manager)

Service Interface

Power supply (if required)

Startup

Assembling and Installing the Phone

OpenScape Desk Phone CP200

2.2.3 Assembly

1. Handset

Insert the plug on the long end of the handset cable into the jack on the base of the telephone and press the cable into the groove provided for it. Next, insert the plug on the short end of the handset cable into the jack on the handset.

2. Emergency Number Sticker

Write your telephone number and the emergency numbers for the fire and police departments on the included label and attach it to the telephone housing underneath the handset.

2.2.4 How to Connect the Phone

1. Plug the LAN cable into the connector at the bottom of the telephone and connect the cable to the LAN resp. switch. If PoE (Power over Ethernet) is to be used, the PSE (Power Sourcing Equipment) must meet the IEEE 802.3af specification.

For details about the required power supply, see the following table:

A31003-C1000-M101-1-76A9, 03/2016

22 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 23

inbetriebnahme.fm

Network switch

OpenScape Desk Phone CP400/600

Startup

Assembling and Installing the Phone

Model Power Consumption

OpenScape Desk Phone CP200 PoE (Power Class 1)

OpenScape Desk Phone CP400 PoE (Power Class 2)

OpenScape Desk Phone CP600

1 If more than one Key Module is connected, a Plug-in Power Supply is required (see below).

2. If Power over Ethernet (PoE) is NOT supported or an OpenScape Desk Phone CP600

phone has more than one Key Module connected: Plug the power supply unit into the mains. Connect the plug-in power supply unit to the

jack at the bottom of the phone.

The order no. for the plug-in power supply is region specific:

• EU: C39280-Z4-C510

• UK: C39280-Z4-C512

• USA: C39280-Z4-C511

PoE (Power Class 2)

3. If applicable, connect the following optional jacks:

• LAN connection to PC

• Headset (accessory)

2.2.5 How to Better Use LAN Network Connections

The OpenScape Desk Phone CP400 and OpenScape Desk Phone CP600 phones provide a 1000 Mbps Ethernet-Switch. This allows you to connect one additional network device (e. g. a PC) directly via the telephone to the LAN. The direct connection functionality from phone to PC needs to be activated by administrator first. This type of connection allows you to save one network connection per switch,with the advantage of less network cables and shorter connection distances.

Do not use this connection for further OpenScape Desk Phone CP,

OpenScape Desk Phone IP or OpenStage phones!

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 24

inbetriebnahme.fm

Startup

Quick Start

2.2.6 Key Module

A key module provides additional program keys. The following table shows which key modules can be connected to the particular phone types.

Phone Type Key Modules additional keys per module

OpenScape Desk Phone CP200 - -

OpenScape Desk Phone CP400 2 16

OpenScape Desk Phone CP600 4 12

The configuration of a key on the key module is just the same as the configuration of a phone key.

2.3 Quick Start

This section describes a typical case: the setup of an OpenScape Desk Phone CP endpoint in an environment using a DHCP server and the web interface. For different scenarios, cross-references to the corresponding section of the administration chapter are given.

Alternatively, the DLS (Deployment Service) administration tool can be used. Its

Plug & Play functionality allows to provide the phone with configuration data by assigning an existing data profile to the phone’s MAC address or E.164 number. For further information, see the Deployment Service Administration Manual.

Any settings made by a DHCP server are not configurable by other configuration tools.

2.3.1 How to Access the Web Interface (WBM)

Prerequisites

• The phone´s IP address or URL is required for accessing the phone´s web interface via a web browser. By default, the phone will automatically search for a DHCP server on startup and try to obtain IP data and further configuration parameters from that central server.

• If no DHCP server is available in the IP network or if the DHCP parameter is disabled, the IP address, subnet mask and default gateway/route must be defined manually.

• To obtain the phone´s IP address, proceed as follows:

1. Access the local phone´s Admin menu as described in Access via Local Phone.

• If DHCP is enabled (default): In the Admin menu, navigate to Network > IPv4 config-

uration > IP address. The IP address is displayed.

A31003-C1000-M101-1-76A9, 03/2016

24 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 25

inbetriebnahme.fm

Startup

Quick Start

• If DHCP is disabled or if no DHCP server is available in the IP network, the IP address, Subnet Mask and Default Route/Gateway must be defined manually as described in How to Manually Configure the Phone´s IP address.

2. Open your web browser (MS Internet Explorer or Mozilla Firefox) and enter the appropriate URL. Example: https://192.168.1.15 or https://myphone.phones.

For configuring the phone’s DNS name, please refer to Section 3.4.7.3, “Terminal Hostname”.

If the browser displays a certificate notification, accept it. The start page of the web interface appears. In the upper right corner, the phone number, the phone’s IP address, as well as the DNS name assigned to the phone are displayed. The left corner contains the user menu tree.

3. Click on the tab "Administrator Pages". In the dialog box, enter the admin password. The default password is 123456.

4. The administration main page opens. The left column contains the menu tree. If you click on an item which is printed in normal style, the corresponding dialog opens in the center of the page. If you click on an item printed in bold letters, a sub-menu opens to the right of the main menu.

2.3.2 How to Set the Terminal Number

Prerequisites

• If the user and administrator menus are needed in the course of setup, the terminal number,

which by default is identical with the phone number, must be configured first. When the phone is in delivery status, the terminal number input form is presented to the user/administrator right after booting, unless the Plug&Play facility of the DLS is used. For further information about this setting, please refer to Terminal Identity. With the WBM, the terminal number is configured as follows:

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 26

inbetriebnahme.fm

Startup

Quick Start

1) Log on as administrator to the WBM by entering the access data for your phone.

2) In the Administrator menu (left column), select System > System Identity to open the "System Identity" dialog. Enter the terminal number, i. e. the SIP name / phone number. For further information, please refer to Terminal Identity.

2.3.3 Basic Network Configuration

For basic functionality, DHCP must provide the following parameters:

• IP Address: IP Address for the phone.

• Subnet Mask (option #1): Subnet mask of the phone.

• Default Route (option #3 "Router"): IP Address of the default gateway which is used for connections beyond the subnet.

• DNS IP Addresses (option #6 "Domain Server"): IP Addresses of the primary and secondary DNS servers.

If no DHCP server is present, see Section 3.4.4, “IP Address - Manual Configuration” for IP address and subnet mask, and Section 3.4.5, “Default Route/Gateway” for the default route.

2.3.4 DHCP Resilience

Prerequisites

It is possible to sustain network connectivity in case of DHCP server failure. If DHCP lease reuse is activated, the phone will keep its DHCP-based IP address even if the lease expires. To prevent address conflicts, the phone will send ARP requests in 5 second intervals. Additionally, it will send discovery messages periodically to obtain a new DHCP lease.

Step by Step

In the left column, select Network > IPv4 configuration. Select the check box to enable DHCP lease reuse.

A31003-C1000-M101-1-76A9, 03/2016

26 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 27

inbetriebnahme.fm

Startup

Quick Start

2.3.5 Date and Time / SNTP

An SNTP (Simple Network Time Protocol) server provides the current date and time for network clients. The IP address of an SNTP server can be given by DHCP.

In order to provide the correct time, it is required to give the time zone offset, i.e. the shift in hours to be added to the UTC time provided by the SNTP server.

The following DHCP options are required:

• SNTP IP Address (option #42 "NTP Servers"): IP Address or hostname of the SNTP server to be used by the phone.

• Time zone offset (option #2 "Time Offset"): Offset in seconds in relationship to the UTC time provided by the SNTP server. For manual configuration of date and time see 3.5.5 Date and Time.

2.3.6 SIP Server Address

The IP Address or hostname of the SIP server can be provided by DHCP.

The option’s name and code are as follows:

• option #120 "SIP Servers DHCP Option". For manual configuration of the SIP server address see SIP Addresses.

2.3.7 Extended Network Configuration

To have constant access to other subnets, you can enter a total of two more network destinations. For each further domain/subnet you wish to use, first the IP address for the destination, and then that of the router must be given. The option’s name and code are as follows:

• option #33 "Static Routing Table"

For manual configuration of specific/static routing see Section 3.4.6, “Specific IP Routing”.

Also the DNS domain wherein the phone is located can be specified by DHCP. The option’s name and code are as follows:

• option #15 "Domain Name"

For manual configuration of the DNS domain name see Section 3.4.7.1, “DNS Domain Name”.

2.3.8 Vendor Specific: VLAN Discovery and DLS Address

The VLAN ID can also be configured by LLDP-MED (see Automatic VLAN discovery

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

using LLDP-MED).

Page 28

inbetriebnahme.fm

Startup

Quick Start

If the phone is to be located in a VLAN (Virtual LAN), a VLAN ID must be assigned. If the VLAN shall be provided by DHCP, VLAN Discovery must be set to "DHCP" (see Section 3.3.2.1, “Automatic VLAN discovery using LLDP-MED”). The corresponding DHCP option is vendor-specific, thus a specific procedure is necessary.

If a DLS (Deployment Service) server is in use, its IP address must be provided. It is recommended to configure the DLS server address by DCHP, as this method enables full Plug & Play: having received the DLS address from DHCP, the phone will contact the DLS during start-up. Provided that the DLS is configured appropriately, it will send all necessary configuration data to the phone. Additionally, this method is relevant to security, as it ensures the authenticity of the DLS server.

For manual configuration of the DLS server address see Configuration & Update Service.

For the configuration of vendor-specific settings by DHCP, there are two alternative methods:

• the use of a vendor class - see How to Use a Vendor Class,

• the use of DHCP option 43 - see How to Use Option #43 "Vendor Specific".

2.3.8.1 How to Use a Vendor Class

It is recommended to define a vendor class on the DHCP server, thus enabling server and phone to exchange vendor-specific data exclusively. The data is disclosed from other clients. The following steps are required for the configuration of the Windows DHCP server and for Unix/Linux.

Example: Configuration of the Window DHCP Server

Setting up a new vendor class using the Windows DHCP Server

1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.

2. In the DHCP console menu, right-click the DHCP server in question and select Define Vendor Classes... in the context menu.

3. A dialog window opens with a list of the classes that are already available.

A31003-C1000-M101-1-76A9, 03/2016

28 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 29

inbetriebnahme.fm

Startup

Quick Start

4. Define a new vendor class with the name OptiIpPhone and enter a description of this class.

Click OK to apply the changes. The new vendor class now appears in the list.

5. Exit the window with Close.

Add Options to the New Vendor Class

Next, two options resp. tags will be added to the vendor class. Two passes are needed for this: in the first pass, tag #1 with the required value "Siemens" is entered, and in the second pass, the VLAN ID is entered as tag #2.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 30

inbetriebnahme.fm

Startup

Quick Start

For DHCP servers on a Windows 2003 Server (pre-SP2):

6. In the DHCP console menu, right-click the DHCP server in question and select Set Predefined Options from the context menu.

Windows 2003 Server contains a bug that prevents you from using the DHCP console to create an option with the ID 1 for a user-defined vendor class. Instead, this entry must be created with the netsh tool in the command line (DOS shell).

You can use the following command to configure the required option (without error message) so that it is also appears later in the DHCP console:

netsh dhcp server add optiondef 1 "Optipoint element 001" STRING 0 vendor=OptiIpPhone comment="Tag 001 for Optipoint"

The value SIEMENS for optiPoint Element 1 can then be re-assigned over the DHCP console.

This error was corrected in Windows 2003 Server SP2.

7. In the dialog, select the previously defined OptiIpPhone class and click on Add... to add a new option.

A31003-C1000-M101-1-76A9, 03/2016

30 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 31

8. Enter the following data for the new option:

1. First Pass: Option 1

• Name: Free text, e. g. "OptiIpPhone element 01"

• Data type: "String"

• Code: "1"

• Description: Free text.

2. Second Pass: Option 2

• Name: Free text, e. g. "OptiIpPhone element 02"

• Data type: "Long"

• Code: "2"

inbetriebnahme.fm

Startup

Quick Start

• Description: Free text.

9. Enter the value for this option.

1. First Pass: "Siemens"

2. Second Pass: VLAN ID

10. Press OK, repeat steps 7 to 9 for the second pass, and press OK again.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 32

inbetriebnahme.fm

Startup

Quick Start

Defining the scope for the new vendor class

11. Select the DHCP server in question and the Scope and right-click Scope Options. Select Configure Options... in the context menu.

12. Select the Advanced tab. Under Vendor class, select the class that you previously defined (OptiIpPhone) and, under User class, select Default User Class.

Activate the check boxes for the options that you want to assign to the scope (in the example, 001, 002, and 003). Click OK.

13. The DHCP console now shows the information that will be transmitted for the corresponding workpoints. Information from the Standard vendor is transmitted to all clients, whereas information from the OptiIpPhone vendor is transmitted only to the clients (workpoints) in this vendor class.

A31003-C1000-M101-1-76A9, 03/2016

32 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 33

inbetriebnahme.fm

Startup

Quick Start

Setup using a DHCP server on Unix/Linux

The following snippet from a DHCP configuration file (usually dhcpd.conf) shows how to set up a configuration using a vendor class and the "vendor-encapsulated-options" option.

class "OptiIpPhone" {

option vendor-encapsulated-options

# The vendor encapsulated options consist of hexadecimal values for the option number (for instance, 01), the length of the value (for instance, 07), and the value (for instance, 53:69:65:6D:65:6E:73). The options can be written in separate lines; the last option must be followed by a ’;’ instead of a ’:’.

# Tag/Option #1: Vendor "Siemens"

#1 7 S i e m e n s

01:07:53:69:65:6D:65:6E:73: # Tag/Option #2: VLAN ID #2 4 0 0 1 0

02:04:00:00:00:0A; match if substring (option vendor-class-identifier, 0, 11) = "OptiIpPhone";

}

2.3.8.2 How to Use Option #43 "Vendor Specific"

Alternatively, option #43 can be used for setting up the VLAN ID. Two tags are required:

• Tag 001: Vendor name

• Tag 002: VLAN ID

• Tag 003: DLS address

Optionally, the DLS address can be given in an alternative way:

• Tag 4: DLS hostname

The Vendor name tag is coded as follows (the first line indicates the ASCII values, the second line contains the hexadecimal values):

Code Length Vendor name

1 7 Si emens

01 07 53 69 65 6D 65 6E 73

The following example shows a VLAN ID with the decimal value "10":

Code Length VLAN ID

240010

02 04 00 00 00 0A

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 34

inbetriebnahme.fm

Startup

Quick Start

For manual configuration of the VLAN ID see Section 3.3.2.3, “Manual configuration of a VLAN ID”.

The DLS IP address tag consists of the protocol prefix "sdlp://", the IP address of the DLS server, and the DLS port number, which is "18443" by default. The following example illustrates the syntax:

Code Length DLS IP address

3 25 sdl p: / / 192. 168. 3. 30: 18443

03 19 73646C703A2F2F3139322E3136382E332E33303A313834343

Setup Using the Windows DHCP Server

1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.

2. Select the DHCP server and the scope. Choose "Configure Options" in the context menu using the right mouse button.

3. Enter the VLAN ID. Providing the length is not required here, as the VLAN ID is always 4 Bytes long.

A31003-C1000-M101-1-76A9, 03/2016

34 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 35

inbetriebnahme.fm

Startup

Quick Start

2.3.9 DLS Server Address

This setting only applies if a DLS (Deployment Service) server is in use.

It is recommended to configure the DLS server address by DCHP, as this method enables full Plug & Play and ensures the authenticity of the DLS server.

For manual configuration of the DLS server address see Section 3.4.8, “Configuration & Update Service”.

For the configuration of vendor-specific settings by DHCP, there are two alternative methods:

1) the use of a vendor class, or 2) the use of DHCP option 43.

2.3.9.1 Using Vendor Class

It is recommended to define a vendor class on the DHCP server, thus enabling server and phone to exchange vendor-specific data exclusively. The data is disclosed from other clients. If not done already, create a vendor class by the name of "OptiIpPhone".

The following steps are required for the configuration of the Windows DHCP server.

Setting up a new vendor class using the Windows DHCP Server

1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 36

inbetriebnahme.fm

Startup

Quick Start

2. In the DHCP console menu, right-click the DHCP server in question and select Define Vendor Classes... in the context menu.

3. A dialog window opens with a list of the classes that are already available.

4. Define a new vendor class with the name OptiIpPhone and enter a description of this class.

Click OK to apply the changes. The new vendor class now appears in the list.

5. Exit the window with Close.

A31003-C1000-M101-1-76A9, 03/2016

36 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 37

inbetriebnahme.fm

Startup

Quick Start

Add Options to the New Vendor Class

For DHCP servers on a Windows 2003 Server (pre-SP2):

6. In the DHCP console menu, right-click the DHCP server in question and select Set Predefined Options from the context menu.

You can use the following command to configure the required option (without error message) so that it is also appears later in the DHCP console:

netsh dhcp server add optiondef 1 "Optipoint element 001" STRING 0 vendor=OptiIpPhone comment="Tag 001 for Optipoint"

The value SIEMENS for optiPoint Element 1 can then be re-assigned over the DHCP console.

This error was corrected in Windows 2003 Server SP2.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 38

inbetriebnahme.fm

Startup

Quick Start

7. In the dialog, select the previously defined OptiIpPhone class and click on Add... to add a new option.

8. Enter the following data for the new option:

1. First Pass: Option 1

• Name: Free text, e. g. "OptiIpPhone element 01"

• Data type: "String"

• Code: "1"

• Description: Free text.

2. Second Pass: Option 3

• Name: Free text, e. g. "OptiIpPhone element 03"

• Data type: "String"

• Code: "3"

• Description: Free text.

A31003-C1000-M101-1-76A9, 03/2016

38 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 39

9. Enter the value for this option.

1. First Pass: "Siemens"

2. Second Pass: DLS address The DLS address has the following format: <PROTOCOL>:://<IP ADDRESS OF DLS SERVER>:<PORT NUMBER> Example: sdlp://192.168.3.30:18443

inbetriebnahme.fm

Startup

Quick Start

10. Press OK, repeat steps 7 to 9 for the second pass, and press OK again.

Defining the scope for the new vendor class

11. Select the DHCP server in question and the Scope and right-click Scope Options. Select Configure Options... in the context menu.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 40

inbetriebnahme.fm

Startup

Quick Start

12. Select the Advanced tab. Under Vendor class, select the class that you previously defined (OptiIpPhone) and, under User class, select Default User Class.

Activate the check boxes for the options that you want to assign to the scope (in the example, 001 and 003)

A31003-C1000-M101-1-76A9, 03/2016

40 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 41

inbetriebnahme.fm

Startup

Quick Start

Setup using a DHCP server on Unix/Linux

The following snippet from a DHCP configuration file (usually dhcpd.conf) shows how to set up a configuration using a vendor class and the "vendor-encapsulated-options" option.

class "OptiIpPhone" {

option vendor-encapsulated-options

# Tag/Option #1: Vendor "Siemens"

#1 7 S i e m e n s

01:07:53:69:65:6D:65:6E:73: # Tag/Option #3: DLS IP Address (here: sdlp://192.168.3.30:18443)

#3 25sdlp://1 92.168.3. ...etc.

03:19:73:64:6C:70:3A:2F:2F:31:39:32:2E:31:36:38:2E:33:2E:33:30:

3A:31:38:34:34:33;

match if substring (option vendor-class-identifier, 0, 11) = "OptiIpPhone";

}

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 42

inbetriebnahme.fm

Startup

Quick Start

2.3.9.2 Using Option #43 "Vendor Specific"

Alternatively, option #43 can be used for setting up the DLS address. Two tags are required:

• Tag 001: Vendor name

• Tag 003: DLS IP address

Additionally, you can enter a host name for the DLS server:

• Tag 004: DLS hostname

The data is entered in hexadecimal values. Note that the length of the information contained in a tag must be given.

The Vendor name tag is coded as follows (the first line indicates the ASCII values, the second line contains the hexadecimal values):

Code Length Vendor name

17Siemens

01 07 53 69 65 6D 65 6E 73

The DLS IP address tag consists of the protocol prefix "sdlp://", the IP address of the DLS server, and the DLS port number, which is "18443" by default. The following example illustrates the syntax:

Code Length DLS IP address

3 25 sdl p: / / 192. 168. 2. 19: 18443

03 19

73646C703A2F2F3139322E3136382E322E31393A3138343433

A31003-C1000-M101-1-76A9, 03/2016

42 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 43

inbetriebnahme.fm

Startup

Quick Start

Setup using the Windows DHCP Server

1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.

2. Select the DHCP server and the scope. Choose "Configure Options" in the context menu using the right mouse button. [Engl. Screenshot]

3. Enter the IP address and port number of the DLS server.

2.3.10 Using the Web Interface (WBM)

1. Log in to the Administrator Pages of the WBM. For details about accessing the WBM, see Section 2.3.1, “How to Access the Web Interface (WBM)”.

2. In the menu at the lefthand side, go to System > Gateway.

3. Enter the IP address of the OpenScape Voice Communication System in the IP address field.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 44

inbetriebnahme.fm

Startup

Quick Start

4. In the Subscriber number field, enter the internal extension number of the phone. It can be 1 to 24 characters long.

5. Enter the subscriber password in the Password field.

2.3.11 Using the Local Menu

Take the following steps to configure the access to an HFA gateway (for further information see Section 3.1, “Access via Local Phone”):

1. Press the mode key v once or twice to activate the administration menu (the key toggles

between the user’s configuration menu and the administration menu).

2. When the Admin menu is active, you will be prompted to enter the administrator password. The default admin password is "123456". It is recommended to change the password (see Section 3.11, "Password”) after your first login.

3. In the administration menu, go to System > Gateway. For further instructions on entering data using the Local menu see Section 3.1, “Navigate within the Administration Menu.”. The path is as follows:

--- Administration

--- System

--- Gateway

|--- System type |--- IP address |--- Gateway ID |--- Subscriber number

--- Password

4. Enter the IP address of the HFA gateway provided by your OpenScape Communication System.

5. Enter the phone’s Gateway Id, which will also serve as internal phone number.

6. Enter the password associated with the Gateway Id.

7. After the data has been entered, select Save & exit and press .

A31003-C1000-M101-1-76A9, 03/2016

44 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 45

administration.fm

Scroll upwards Hold down: Jump to top of list

Confirm input or perform action

Navigate tab or move right

Cancel function, delete character left of cursor, navigate tab or go back one menu level

€

Scroll downwards Hold down: Jump to bottom of list

Administration

Access via Local Phone

3 Administration

This chapter describes the configuration of every parameter available on the OpenScape Desk Phone CP phones. For access via the local phone menu, see the following; for access using the web interface (WBM), please refer to Section 2.3.1, “How to Access the Web Interface (WBM)”.

3.1 Access via Local Phone

The data entered in input fields is parsed and controlled by the phone. Thus, data is

1. Access the Administration Menu

accepted only if it complies to the value range.

Press the @ or À key and use the Up Arrow, Down Arrow and OK keys consecutively

to select the Admin menu.

2. When the Admin menu is active, you will be prompted to enter the administrator password. The default admin password is "123456". It is highly recommended to change the password (see Section 3.19, “Password”) after your first login.

For entering passwords with non-numeric characters, please consider the following: By default, password entry is in numeric mode and a minimum length of 6 characters. For

changing the mode, press the # key once or repeatedly, depending on the desired character. The # key cycles around the input modes as follows:

(Abc) -> (abc) -> (123) -> (ABC) -> back to start. Usable characters are 0-9 A-Z a-z .*#,?!’"+-()@/:_

3. Navigate within the Administration Menu.

4. Select a parameter

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 46

administration.fm

Administration

Access via Local Phone

If a parameter is set by choosing a value from a selective list, an arrow symbol appears in the parameter field that has the focus. Press the OK key to enter the selective list. Use the Up Arrow and Down Arrow keys to scroll up and down in the selection list. To select a list entry, press the OK key.

A31003-C1000-M101-1-76A9, 03/2016

46 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 47

administration.fm

Bluetooth

Enable Bluetooth interface

;

Administration

Bluetooth Interface

5. Enter the parameter value For selecting numbers and characters, you can use special keys. See the following table:

Key Key Function during text input Key function when held down

Enter special characters. Ringer on/off when pressed short,

ringer set to alerting with longpress.

Toggle between lowercase characters, up-

Phonelock on/off. percase characters, and digits in the following order: (Abc) -> (abc) -> (123) -> (ABC) -> back to start.

With the OpenScape Desk Phone CP200/400/600 use the keypad for entering parameter values. Use the Navigation Keys or Navigation Block to navigate and execute administrative actions in the Administration Menu.

6. Save and exit When you are done, select Save & exit and press OK key.

3.2 Bluetooth Interface

You can activate and deactivate the Bluetooth interface. If the Bluetooth interface is deactivated no Bluetooth services are available.

Administration via WBM

Bluetooth

Administration via Local Phone

--- Bluetooth

3.3 LAN Settings

3.3.1 LAN Port Settings

The OpenScape Desk Phone CP200/400/600 phone provides an integrated switch which connects the LAN, the phone itself and a PC port. By default, the switch will auto negotiate transfer rate (10/100/1000 Mb/s autosensing, configurable, Gigabit not available on

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 48

administration.fm

Administration

LAN Settings

OpenScape Desk Phone CP200) and duplex method (full or half duplex) with whatever equipment is connected. Optionally, the required transfer rate and duplex mode can be specified manually using the LAN Port Speed parameter.

In the default configuration, the LAN port supports automatic detection of cable con-

The PC Ethernet port (default setting: Disabled) is controlled by the PC port mode parameter. If set to "Disabled", the PC port is inactive; if set to "Enabled", it is active. If set to "Mirror", the data traffic at the LAN port is mirrored at the PC port. This setting is for diagnostic purposes. If, for instance, a PC running Ethereal/Wireshark is connected to the PC port, all network activities at the phone’s LAN port can be captured.

figuration (pass through or crossover cable) and will reconfigure itself as needed to connect to the network. If the phone is set up to manually configure the switch port settings, the cable detection mechanism is disabled. In this case care must be taken to use the correct cable type.

Do not use this connection for further phones!

Removing the power from the phone or a phone reset/reboot will result in the tem-

When PC port autoMDIX is enabled, the switch determines automatically whether a regular MDI connector or a MDI-X (crossover) connector is needed, and configures the connector accordingly.

Data required

• LAN port speed / LAN port type: Settings for the ethernet port connected to a LAN

• PC port speed / PC port type: Settings for the ethernet port connected to a PC.

• PC port mode / PC port status: Controls the PC port.

porary loss of the network connection to the PC port.

switch. Value range: "Automatic," "10 Mbps half duplex", "10 Mbps full duplex", "100 Mbps half duplex", "100 Mbps full duplex", "Gigabit/s full duplex" (OpenScape Desk Phone CP400 and OpenScape Desk Phone CP600 only) . Default: "Automatic"

Value range: "Automatic," "10 Mbps half duplex", "10 Mbps full duplex", "100 Mbps half duplex", "100 Mbps full duplex", "Gigabit/s full duplex" (OpenScape Desk Phone CP400 and OpenScape Desk Phone CP600 only). Default: "Automatic"

Value range: "disabled", "enabled", "mirror". Default: "disabled"

A31003-C1000-M101-1-76A9, 03/2016

48 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 49

• PC port autoMDIX: Switches between MDI and MDI-X automatically.

SIP local

Backup proxy

RTP base

Download server (default)

LDAP server

Port configuration

5060

SIP gateway

5060

5010

SIP server

SIP registrar

5060

LAN port speed

Automatic

Submit

Reset

Automatic

PC port speed

PC port autoMDIX

disabled

389

PC port mode

HTTP proxy

Value range: "On", "Off" Default: "Off"

Administration via WBM

Network > Port configuration

administration.fm

Administration

LAN Settings

Administration via Local Phone

--- Admin

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

--- Network

--- Port Configuration

--- Number

|--- LAN port type |--- PC port status |--- PC port type

--- PC port autoMDIX

Page 50

administration.fm

Administration

LAN Settings

3.3.2 VLAN

VLAN (Virtual Local Area Network) is a technology that allows network administrators to partition one physical network into a set of virtual networks (or broadcast domains).

Partitioning a physical network into separate VLANs allows a network administrator to build a more robust network infrastructure. A good example is a separation of the data and voice networks into data and voice VLANs. This isolates the two networks and helps shield the endpoints within the voice network from disturbances in the data network and vice versa.

The implementation of a voice network based on VLANs requires the network infra-

In a layer 1 VLAN, the ports of a VLAN-aware switch are assigned to a VLAN statically. The switch only forwards traffic to a particular port if that port is a member of the VLAN that the traffic is allocated to. Any device connected to a VLAN-assigned port is automatically a member of this VLAN, without being a VLAN aware device itself. If two or more network clients are connected to one port, they cannot be assigned to different VLANs. When a network client is moving from one switch to another, the switches’ ports have to be updated accordingly by hand.

structure (the switch fabric) to support VLANs.

With a layer 2 VLAN, the assignment of VLANs to network clients is realized by the MAC addresses of the network devices. In some environments, the mapping of VLANs and MAC addresses can be stored and managed by a central database. Alternatively, the VLAN ID, which defines the VLAN whereof the device is a member, can be assigned directly to the device, e. g. by DHCP. The task of determining the VLAN for which an Ethernet packet is destined is carried out by VLAN tags within each Ethernet frame. As the MAC addresses are (more or less) wired to the devices, mobility does not require any administrator action, as opposed to layer 1 VLAN.

The phone must be configured as a VLAN aware endpoint if the phone itself is a member of the voice VLAN, and the PC connected to the phone’s PC port is a member of the data VLAN.

There are 3 ways for configuring the VLAN ID:

• By LLDP-MED

• By DHCP

• Manually

3.3.2.1 Automatic VLAN discovery using LLDP-MED

This is the default setting. The VLAN ID is configured by the network switch using LLDP-MED (Link Layer Discovery Protocol-Media Endpoint Discovery). If the switch provides an appropriate TLV (Type-Length-Value) element containing the VLAN ID, this VLAN ID will be used. If no appropriate TLV is received, DHCP will be used for VLAN discovery.

A31003-C1000-M101-1-76A9, 03/2016

50 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 51

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

LLDP-MED

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

IPv4_IPv6

Protocol Mode

Administration

LAN Settings

Administration via WBM

Network > General IP configuration

First, click on change mode. Afterwards, the IP configuration mode dialog opens.

Administration via Local Phone

To enable VLAN discovery via LLDP-MED, set the Use LLDP-MED option to Yes and select LLDP-MED in the VLAN discovery option.

--- Administration

--- Network

--- General IP configuration

--- VLAN ID

3.3.2.2 Automatic VLAN discovery using DHCP

To automatically discover a VLAN ID using DHCP, the phone must be configured as DHCP enabled, and VLAN discovery mode must be set to "DHCP". LLDPMED should be disabled. The DHCP server must be configured to supply the Vendor Unique Option in the correct VLAN over DHCP format. If a phone configured for VLAN discovery by DHCP fails to discover its VLAN, it will proceed to configure itself from the DHCP within the non-tagged LAN. Under these circumstances, network routing may probably not be correct.

Administration via WBM

Network > General IP configuration

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 52

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

LLDP-MED

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

IPv4_IPv6

Protocol Mode

Administration

LAN Settings

To enable VLAN discovery via LLDP-MED, activate the LLDP-MED Enabledcheckbox and select LLDP-MED in the VLAN discovery option. Afterwards, click Submit.

Administration via Local Phone

To enable VLAN discovery via DHCP, activate the DHCPv6 Enabled checkbox and select DHCP in the VLAN discovery option.

--- Administration

--- Network

--- General IP configuration

--- VLAN ID

3.3.2.3 Manual configuration of a VLAN ID

To configure layer 2 VLAN manually, first make sure that VLAN discovery is set to "Manual" (see Section 3.3.2.1, “Automatic VLAN discovery using LLDP-MED”). Then, the phone must be provided with a VLAN ID between 1 and 4095. If you misconfigure a phone to an incorrect VLAN, the phone will possibly not connect to the network. In DHCP mode it will behave as though the DHCP server cannot be found, in fixed IP mode no server connections will be possible.

52 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 53

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

Manual

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

IPv4_IPv6

Protocol Mode

Administration

LAN Settings

Administration via WBM

The phone must be provided with a VLAN Id between 1 and 4095. Set the VLAN discovery to Manual. Afterwards, click Submit.

Network > General IP configuration

Administration via Local Phone

--- Administration

--- Network

--- General IP configuration

--- VLAN ID

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 54

administration.fm

Administration

IP Network Parameters

3.4 IP Network Parameters

3.4.1 Quality of Service (QoS)

The QoS technology based on layer 2 and the two QoS technologies Diffserv and TOS/IP Precedence based on layer 3 are allowing the VoIP application to request and receive predictable service levels in terms of data throughput capacity (bandwidth), latency variations (jitter), and delay.

Layer 2 and 3 QoS for voice transmission can be set via LLDP-MED (see LLDP-

3.4.1.1 Layer 2 / 802.1p

QoS on layer 2 is using 3 Bits in the 802.1q/p 4-Byte VLAN tag which has to be added in the Ethernet header.

MED). If so, the value can not be changed by any other interface.

The CoS (class of service) value can be set from 0 to 7. 7 is describing the highest priority and is reserved for network management. 5 is used for voice (RTP-streams) by default. 3 is used for signaling by default.

PREAM. SFD DA SA

TAG

4 Bytes

Three Bits Used for CoS

PT DATA FCS

(User Priority)

Data required

• Layer 2: Activates or deactivates QoS on layer 2. Value range: "Yes", "No" Default: "Yes"

• Layer 2 voice: Sets the CoS (Class of Service) value for voice data (RTP streams). Value range: 0-7 Default: 5

• Layer 2 signalling: Sets the CoS (Class of Service) value for signaling. Value range: 0-7 Default: 3

• Layer 2 default: Sets the default CoS (Class of Service) value. Value range: 0-7 Default: 0

A31003-C1000-M101-1-76A9, 03/2016

54 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 55

Administration via WBM

Layer 2 signalling

Layer 3 voice

Layer 2 voice

Layer 2

QoS

Layer 3

;

Service

MLPP

Priority

Immediate

Flash

Flash override

Submit

Reset

Layer 2 default

Layer 3 signalling

AF31

Network > QoS > Service >

administration.fm

Administration

IP Network Parameters

Administration via Local Phone

--- Admin

--- Network

--- QoS

--- Service

|--- Layer 2 |--- Layer 2 voice |--- Layer 2 signalling

--- Layer 2 default

3.4.1.2 Layer 3 / Diffserv

Diffserv assigns a class of service to an IP packet by adding an entry in the IP header.

Traffic flows are classified into 3 per-hop behavior groups:

1. Default Any traffic that does not meet the requirements of any of the other defined classes is placed

in the default per-hop behaviour group. Typically, the forwarding has best-effort forwarding characteristics. The DSCP (Diffserv Codepoint) value for Default is "000000".

2. Expedited Forwarding (EF referred to RFC 3246) Expedited Forwarding is used for voice (RTP streams) by default. It effectively creates a

special low-latency path in the network. The DSCP (Diffserv Codepoint) value for EF is "101110".

3. Assured Forwarding (AF referred to RFC 2597)

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 56

administration.fm

Layer 2 signalling

Layer 3 voice

Layer 2 voice

Layer 2

QoS

Layer 3

;

Service

MLPP

Priority

Immediate

Flash

Flash override

Submit

Reset

Layer 2 default

Layer 3 signalling

AF31

Administration

IP Network Parameters

Assured forwarding is used for signaling messages by default (AF31). It is less stringent than EF in a multiple dropping system. The AF values are containing two digits X and Y (AFXY), where X is describing the priority class and Y the drop level.

Four classes X are reserved for AFXY: AF1Y (low priority), AF2Y, AF3Y and AF4Y (high priority).

Three drop levels Y are reserved for AFXY: AFX1 (low drop probability), AFX2 and AFX3 (High drop probability). In the case of low drop level, packets are buffered over an extended period in the case of high drop level, packets are promptly rejected if they cannot be forwarded.

Data required

• Layer 3: Activates or deactivates QoS on layer 3. Value range: "Yes", "No" Default: "Yes"

• Layer 3 voice: Sets the CoS (Class of Service) value for voice data (RTP streams). Value range: "BE", "AF11", "AF12", "AF13", "AF21", "AF22", "AF23", "AF31", "AF32", "AF33", "AF41", "AF42", "AF43", "EF", "CS7", "CS3", "CS4", "CS5", 0, 1, 2 ... through 63. Default: "EF"

• Layer 3 signalling: Sets the CoS (Class of Service) value for signaling. Value range: "BE", "AF11", "AF12", "AF13", "AF21", "AF22", "AF23", "AF31", "AF32", "AF33", "AF41", "AF42", "AF43", "EF", "CS7", "CS3", "CS4", "CS5", 0, 1, 2 ... through 63. Default: "AF31"

Administration via WBM

Network > QoS > Service

A31003-C1000-M101-1-76A9, 03/2016

56 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 57

Administration via Local Phone

--- Admin

--- Network

--- QoS

--- Service

|--- Layer 3 |--- Layer 3 voice

--- Layer 3 signalling

administration.fm

Administration

IP Network Parameters

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 58

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

Manual

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

485

IPv4_IPv6

Protocol Mode

Administration

IP Network Parameters

3.4.2 Protocol Mode IPv4/IPv6

An IPv4 address consists of 4 number blocks, each between 0 and 255, separated by ".". Example:

Example: 1.222.44.123

An IPv6 address consists of 8 hexadecimal number blocks, separated by ":".

Example:

2001:0db8:85a3:08d3:1319:8a2e:0370:7347 or, if not all blocks are used:

2000:1::3

Administration via WBM

Network > General IP configuration

Set the Protocol Mode to IPv4 or IPv6 or both (the default setting is IPv4_IPv6).

Afterwards, click Submit.

Administration via Local Phone

--- Admin

--- Network

--- General IP Configuration

--- Protocol Mode

58 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 59

administration.fm

Administration

IP Network Parameters

3.4.3 Use DHCP

If this parameter is set to "Yes" (default), the phone will search for a DHCP server on startup and try to obtain IP data and further configuration parameters from that central server.

If no DHCP server is available in the IP network, please deactivate this option. In this case, the IP address, subnet mask and default gateway/route must be defined manually.

The change will only have effect if you restart the phone.

The following parameters can be obtained by DHCP:

Basic Configuration

The phone is able to maintain its IP connection even in case of DHCP server failure. For further information, please refer to DHCP Resilience.

• IP Address

• Subnet Mask

Optional Configuration

• Default Route (Routers option 3)

• IP Routing/Route 1 & 2 (Static Routes option 33), Classless static route option 121, Provate/Classless Static Rout (Microsoft) option 249)

• SNTP IP Address (NTP Server option 42)

• Timezone offset (Time Server Offset option 2)

• Primary/Secondary DNS (DNS Server option 6)

• DNS Domain Name (DNS Domain option 15)

• SIP Addresses/ SIP Server & Registrar (SIP Server option 120)

• VLAN ID, DLS address (Vendor specific Information option 43)

The following parameters can be obtained by DHCPv6:

Basic Configuration

• Global Address

Global Address Prefix Length

Optional Configuration

• Primary/Secondary DNS (DNS recursive name server option 23)

• SNTP IP Address (Simple Network Time Protocol Server option 31)

• SIP Addresses / SIP Server & Registrar (SIP Server Domain Name List option 21, SIP Server IPv6 Address List option 22)

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 60

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

DHCP

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

485

IPv4_IPv6

Protocol Mode

;

Administration

IP Network Parameters

• VLAN ID, DLS address (Vendor specific Information option 17)

DHCPv6 options are preferred in Dual Stack Mode if a parameter is configured both via DHCP and via DHCPv6, for instance DNS or SNTP server addresses.

Administration via WBM - IPv4

Network > General IP configuration

Set DHCP Enabled to "selected". Afterwards, click Submit.

Administration via Local Phone

--- Admin

--- Network

--- IPv4 configuration

or / and

Administration via WBM - IPv6

Network > General IP configuration

Set DHCPv6 Enabled to "selected" (default setting is Enabled). Afterwards, click Submit.

60 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 61

Administration via Local Phone

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

DHCP

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

485

IPv4_IPv6

Protocol Mode

;

administration.fm

Administration

IP Network Parameters

--- Admin

--- Network

--- IPv6 configuration

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 62

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

LLDP-MED

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

IPv4_IPv6

Protocol Mode

Administration

IP Network Parameters

3.4.4 IP Address - Manual Configuration

If not provided by DHCP dynamically, you must specify the phone’s IP address and subnet mask manually.

IP addresses can be entered in the following formats:

– Decimal format. Example: 11.22.33.44 or 255.255.255.0 (no leading zeroes).

– Octal format. Example: 011.022.033.044 (leading zeroes must be used with every

address block)

– Hexadecimal format. Example: 0x11.0x22.0x33.0x44 (prefix 0x must be used with

every address block)

By default, IP configuration by DHCP and LLDP-MED is enabled. For manual IP configuration, please proceed as follows:

Data required

• IP address: used for addressing the phone.

• Subnet mask: subnet mask that is needed for the subnet in use.

Administration via WBM

1. Navigate to Network > General IP Configuration. Set DHCP Enabled, DHCPv6 Enabled and LLDP-MED Enabled to "not selected". Afterwards, click Submit.

Network > General IP configuration

2. Navigate to Network > IPv4 configuration or IPv6 configuration, depending on the settings in Protocol Mode IPv4/IPv6. Set DHCP Enabled , resp. DHCPv6 Enabled and LLDP-MED Enabled to "not selected". Enter the IP address and the Subnet mask. If applicable, enter the Default route. Afterwards, click Submit.

62 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 63

Network > IPv4 configuration

LLDP-MED Enabled

IP address

Subnet mask

Default route

Route 1 IP address

IPv4 configuration

255.255.255.0

DHCP Enabled

Submit

Reset

192.168.1.105

Route 2 mask

Route 1 gateway

Route 1 mask

Route 2 IP address

Route 2 gateway

192.168.1.2

DHCP lease reuse

LLDP-MED Enabled

Global address

Address Prefix Len

Global Gateway

Link Local Address

Route 1 Dest.

IPv6 configuration

255.255.255.0

DHCPv6 Enabled

Submit

Reset

192.168.1.105

Route 2 Gateway

Route 1 Prefix Len

Route 1 Gateway

Route 2 Dest.

Route 2 Prefix Len

192.168.1.2

DHCPv6 lease reuse

Network > IPv6 configuration

administration.fm

Administration

IP Network Parameters

Administration via Local Phone

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

--- Admin

--- Network

--- Admin

--- Network

--- Admin

--- General IP Configuration

|--- Use LLDP-MED |--- Use DHCP

--- Use DHCPv6

--- IPv4 Configuration

|--- IP address

--- Subnet mask

Page 64

administration.fm

LLDP-MED Enabled

IP address

Subnet mask

Default route

Route 1 IP address

IPv4 configuration

255.255.255.0

DHCP Enabled

Submit

Reset

192.168.1.105

Route 2 mask

Route 1 gateway

Route 1 mask

Route 2 IP address

Route 2 gateway

192.168.1.2

DHCP lease reuse

Administration

IP Network Parameters

--- Network

--- IPv6 Configuration

|--- Global address

--- Global Prefix Len

3.4.5 Default Route/Gateway

If not provided by DHCP dynamically (see Section 3.4.3, “Use DHCP”), enter the IP address of the router that links your IP network to other networks. If the value was assigned by DHCP, it can only be read.

The change will only have effect if you restart the phone.

Administration via WBM - IPv4 Configuration

Enter the Default route, i.e. the IP address of the router that links your IP network to other networks. Afterwards, click Submit.

Network > IPv4 configuration

Administration via Local Phone - IPv4 Configuration

--- Admin

--- Network

--- IPv4 configuration

--- Route (Default)

Administration via WBM - IPv6 Configuration

Enter the IP address of the Global Gateway that links your IP network to other networks. Afterwards, click Submit.

64 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 65

Network > IPv6 configuration

LLDP-MED Enabled

Global address

Address Prefix Len

Global Gateway

Link Local Address

Route 1 Dest.

IPv6 configuration

DHCPv6 Enabled

Submit

Reset

Route 2 Gateway

Route 1 Prefix Len

Route 1 Gateway

Route 2 Dest.

Route 2 Prefix Len

DHCPv6 lease reuse

fe80::21a:e8ff:fe09:31e2

administration.fm

Administration

IP Network Parameters

Administration via Local Phone - IPv6 Configuration

--- Admin

--- Network

--- IPv6 configuration

--- Global Gateway

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 66

administration.fm

LLDP-MED Enabled

IP address

Subnet mask

Default route

Route 1 IP address

IPv4 configuration

255.255.255.0

DHCP Enabled

Submit

Reset

192.168.1.105

Route 2 mask

Route 1 gateway

Route 1 mask

Route 2 IP address

Route 2 gateway

192.168.1.2

DHCP lease reuse

Administration

IP Network Parameters

3.4.6 Specific IP Routing

To have constant access to network subscribers of other domains, you can enter a total of two more network destinations, in addition to the default route/gateway. This is useful if the LAN has more than one router or if the LAN is divided into subnets.

IPv4 Route Configuration

Data required

• Route 1/2 IP address: IP address of the selected route.

• Route 1/2 gateway: IP address of the gateway for the selected route.

• Route 1/2 mask: Network mask for the selected route.

Administration via WBM - IPv4 Configuration

Enter the required data:

• For Route 1: Route 1 IP address, Route 1 Gateway, and Route 1 mask.

• For Route 2: Route 2 IP address, Route 2 Gateway, and Route 2 mask.

Click Submit.

Network > IPv4 configuration

Administration via Local Phone

--- Admin

--- Network

--- IPv4 Configuration

|--- Route 1 IP

66 OpenScape Desk Phone CP200/400/600, Administrator Documentation

|--- Route 1 gateway |--- Route 1 mask

--- Route 2 IP

A31003-C1000-M101-1-76A9, 03/2016

Page 67

IP Network Parameters

LLDP-MED Enabled

Global address

Address Prefix Len

Global Gateway

Link Local Address

Route 1 Dest.

IPv6 configuration

DHCPv6 Enabled

Submit

Reset

Route 2 Gateway

Route 1 Prefix Len

Route 1 Gateway

Route 2 Dest.

Route 2 Prefix Len

DHCPv6 lease reuse

fe80::21a:e8ff:fe09:31e2

|--- Route 2 gateway

--- Route 2 mask

IPv6 Route Configuration

Data required

• Route 1/2 destination: IPv6 address of the selected route.

• Route 1/2 prefix len: Prefix length for the selected route.

• Route 1/2 gateway: IPv6 address of the gateway for the selected route.

Administration via WBM - IPv6 Configuration

Enter the required data:

• For Route 1: Route 1 Dest., Route 1 Prefix Len, and Route 1 Gateway.

• For Route 2: Route 2 Dest., Route 2 Prefix Len, and Route 2 Gateway.

administration.fm

Administration

Click Submit.

Network > IPv6 configuration

Administration via Local Phone

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

--- Admin

--- Network

--- IPv6 Configuration

--- Route 2 gateway

Page 68

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

Manual

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

485

IPv4_IPv6

Protocol Mode

;

Administration

IP Network Parameters

3.4.7 DNS

The main task of the domain name system (DNS) is to translate domain names to IP addresses. For some features and functions of the OpenScape Desk Phone CP phone, it is necessary to configure the DNS domain the phone belongs to, as well as the name servers needed for DNS resolving.

3.4.7.1 DNS Domain Name

This is the name of the phone’s local domain.

Administration via WBM

Enter the DNS domain the phone belongs to. Afterwards, click Submit.

Network > General IP configuration

Administration via Local Phone

--- Admin

--- Network

--- General IP configuration

--- DNS domain

68 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 69

administration.fm

LLDP-MED Enabled

DHCPv6 Enabled

VLAN discovery

VLAN ID

DNS domain

Primary DNS

Secondary DNS

HTTP proxy

General IP configuration

Manual

workgroup

DHCP Enabled

Submit

Reset

192.168.1.105

485

IPv4_IPv6

Protocol Mode

;

Administration

IP Network Parameters

3.4.7.2 DNS Servers

If not provided by DHCP automatically, a primary and a secondary DNS server can be configured.

Depending on the configuration chosen for survivability, DNS SRV is required. For

details, please refer to Resilience and Survivability.

Data required

• Primary DNS: IP address of the primary DNS server.

• Secondary DNS: IP address of the secondary DNS server.

Administration via WBM

Network > IP configuration

Enter the IP addresses of the Primary DNS and the Secondary DNS server. Afterwards, click

Submit.

Administration via Local Phone

--- Admin

--- Network

--- General IP configuration

|--- Primary DNS

--- Secondary DNS

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 70

administration.fm

System Identity

Terminal number

Terminal name

Submit

Reset

3338

Display identity

312

Enabled ID

;

Web name

DNS name construction

Only number

Administration

IP Network Parameters

3.4.7.3 Terminal Hostname

The phone’s hostname can be customised.

DHCP and DNS must be appropriately connected and configured at the customer

site.

The corresponding DNS domain is configured in Network > General IP configuration > DNS domain (see Section 3.4.7.1, “DNS Domain Name”).

The current DNS name of the phone is displayed at the right-hand side of the banner of the admin and user web pages, under DNS name. To see configuration changes, the web page must be reloaded.

It is recommended to inform the user about the DNS name of the phone. The

complete WBM address can be found under User menu > Network information > Web address.

The DNS name can be constructed from pre-defined parameters and free text. Its composition is defined by the DNS name construction parameter Administration > System > System Identity > DNS name construction. The following options are available:

• None: No hostname is send to the DHCP server during DHCP configuration.

• MAC based: The DNS name is built from the prefix "OIP" followed by the phone’s MAC address.

• Web name: The DNS name is set to the the string entered in Web name.

• Only number: The DNS name is set to the Terminal number, that is, the phone’s call number (E.164).

• Prefix number: The DNS name is constructed from the the string entered in Web name, followed by the Terminal number.

Administration via WBM

System > System Identity

70 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 71

administration.fm

Administration

IP Network Parameters

Administration via Local Phone

--- Administration

--- System

--- Identity

|--- Web name

--- DNS name construction

3.4.8 Configuration & Update Service

The OpenScape Deployment Service (DLS) is a OpenScape Management Application for administering workpoints in both HiPath and non-HiPath networks. Amongst the most important features are: security (e.g. PSS generation and distribution within an SRTP security domain), mobility for OpenScape SIP phones, software deployment, plug&play support, as well as error and activity logging.

DLS address, i.e. the IP address or hostname of the DLS server, and Default mode port, i.e. the port on which the DLS server is listening, are required to enable proper communication between phone and DLS. The Contact gap parameter is not used. Set Revert to default security to disable mutual authentication and return to DEFAULT mode. SECURE mode related settings are reset and certificates are removed.

The Mode (labeled Mode in the local phone´s Admin menu) determines the security level for the communication between the phone and the DLS. Mutual authentication establishes a higher security level of the connection by mutually exchanging credentials between the DLS and the phone. After this, the communication is encrypted, and a different port is used, thus ensuring that the phone is unambiguously connected to the correct DLS server.

It is possible to operate the DLS server behind a firewall or NAT (Network Address

Translation), which prevents the DLS from sending Contact-Me messages directly to the phone. Only outbound connections from the phone are allowed. To overcome this restriction, a DLS Contact-Me proxy (DCMP) can be deployed. The phone periodically polls the DCMP (DLS Contact- Me Proxy), which is placed outside of the phone’s network, for pending contact requests from the DLS. If there are contact requests, the phone will send a request to the DLS in order to obtain the update, just as with a regular DLS connection.

The URI of the DCMP, as well as the polling interval, are configured by the DLS. For

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

this purpose, it is necessary that the phone establishes a first contact to the DLS, e. g. by phone restart or local configuration change.

Page 72

administration.fm

Update Service

DLS address

Default mode port

Submit

Reset

Mode

Default

Contact gap

300

18443

Security PIN

Revert to default security

;

Administration

IP Network Parameters

A Security PIN can be provided which is used for decrypting data provided by the DLS during bootstrap. For further information, please refer to the DLS documentation.

Data required

• DLS address: IP address or hostname of the server on which the Deployment Service is running.

• Default mode port: Port on which the DLS Deployment Service is listening. Default: 18443.

• Contact gap: Minimum time interval in seconds that must elapse between responses to a ContactMe request from the DLS, in order to prevent DoS attacks. Default: 300.

• Revert to default security: When set, security mode will be set to default. When using local phone administration, this will be set by selection option ’Default security’ after pressing Save&exit.

• Mode: Determines whether the communication between the phone and the DLS is secure. Value range: "Default", "Secure", "Secure PIN". This parameter is read-only. Default: "Default".

• Security PIN: Used for enhanced security.

Administration via WBM

Network > Update Service

72 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 73

Administration via Local Phone

--- Admin

--- Network

--- Update Service

--- Security PIN

administration.fm

Administration

IP Network Parameters

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 74

administration.fm

Administration

IP Network Parameters

3.4.9 SNMP

The Simple Network Management Protocol is used by network management systems for monitoring network-attached devices for conditions that warrant administrative attention. An SNMP manager surveys and, if needed, configures several SNMP elements, e.g. VoIP phones.

OpenScape Desk Phone CP phones support SNMPv1.

There are currently 4 trap categories that can be sent by the phones:

Standard SNMP traps

OpenScape Desk Phone CP phones support the following types of standard SNMP traps, as defined in RFC 1157:

• coldStart: sent if the phone does a full restart.

• warmStart: sent if only the phone software is restarted.

• linkUp: sent when IP connectivity is restored.

QoS Related traps

These traps are designed specifically for receipt and interpretation by the QDC collection system. The traps are common to SIP phones, HFA phones, Gateways, etc.

Traps for important high level SIP related problems

Currently, these traps are related to problems in registering with a SIP Server and to a failure in remotely logging off a mobile user. These traps are aimed at a nonexpert user (e.g. a standard Network Management System) to highlight important telephony related problems.

Traps specific to OpenScape Desk Phone CP

Currently, the following traps are defined:

TraceEventFatal: sent if severe trace events occur; aimed at expert users.

TraceEventError: sent if severe trace events occur; aimed at expert users.

Data required

• Trap sending enabled: Enables or disables the sending of a TRAP message to the SNMP manager. Value range: "Yes", "No" Default: "No"

• Trap destination: IP address or hostname of the SNMP manager that receives traps.

• Trap destination port: Port on which the SNMP manager is receiving TRAP messages. Default: 162

A31003-C1000-M101-1-76A9, 03/2016

74 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 75

administration.fm

Administration

IP Network Parameters

• Trap community: SNMP community string for the SNMP manager receiving TRAP messages. Default: "snmp"

• Queries allowed: Allows or disallows queries by the SNMP manager.

• Query password: Password for the execution of a query by the SNMP manager.

• Diagnostic sending enabled: Enables or disables the sending of diagnostic data to the SNMP manager. Value range: "Yes", "No" Default: "No"

• Diagnostic destination: IP address or hostname of the SNMP manager receiving diagnostic data.

• Diagnostic destination port: Port on which the SNMP manager is receiving diagnostic data.

• Diagnostic community: SNMP community string for the SNMP manager receiving diagnostic data.

• Diagnostic to generic destination: Enables or disables the sending of diagnostic data to a generic destination. Value range: "Yes", "No" Default: "No"

• QoS traps to QCU: Enables or disables the sending of TRAP messages to the QCU server. Value range: "Yes", "No" Default: "No"

• QCU address: IP address or hostname of the QCU server.

• QCU port: Port on which the QCU server is listening for messages. Default: 12010.

• QCU community: QCU community string. Default: "QOSCD".

• QoS to generic destination: Enables or disables the sending of QoS traps to a generic destination. Value range: "Yes", "No" Default: "No"

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 76

administration.fm

Traping sending enabled

Trap destination

Trap destination port

Trap community

Queries allowed

Query password

SNMP

QoS report traps

Diagnostic traps

Generic traps

****

Diagnostic sending enabled

Diagnostic destination

Diagnostic destination port

Diagnostic community

Diagnostic to generic destination

Submit

Reset

162

QoS traps to QCU

QCU address

QCU port

12010

QCU community

QoS to generic destination

*****

Administration

IP Network Parameters

Administration via WBM

System > SNMP

Administration via Local Phone

--- Admin

--- System

--- SNMP

76 OpenScape Desk Phone CP200/400/600, Administrator Documentation

--- QoS to generic dest.

A31003-C1000-M101-1-76A9, 03/2016

Page 77

administration.fm

Administration

Security

3.5 Security

3.5.1 System

OpenScape Desk Phone CP phones support secure (i.e. encrypted) speech transmission via SRTP. For enabling secure (encrypted) calls, a TLS connection to the OpenScape Voice server is required.

If Use secure calls is activated, the encryption of outgoing calls is enabled, and the phone is capable of receiving encrypted calls. When the phone is connected to an OpenScape Voice system, call security is communicated to the user as follows:

• An icon in the call view tells the user whether a call is secure (encrypted) or not.

• If an active call changes from secure to insecure, e. g. after a transfer, a popup window and an alert tone will notify the user.

For secure (encrypted) calls, it is required that both endpoints support SRTP. The

secure call indication tells the user that the other endpoint has acknowledged the secure connection.

In order to use SRTP, the phone must be configured for NTP (for further information

If SIP server certificate validation resp. Backup SIP server certificate validation is activated, the phone will validate the server certificate sent by the OpenScape Voice server in order to establish a TLS connection. The server certificate is validated against the root certificate from the trusted certificate authority (CA), which must be stored on the phone first. For delivering the root certificate, a DLS (OpenScape Deployment Service) server is required.

The SRTP type sets the key exchange method for SRTP.

MIKEY (Multimedia Internet KEYing) is a key management protocol that is intended for use with real-time applications. It can specifically be used to set up encryption keys for multimedia sessions that are secured using SRTP.

Use secure calls activates the encryption of outgoing calls, i.e. the phone iscapable of receiving encrypted calls.

please see Date and Time). The reason is that the key generation (MIKEY) uses the system time of the particular device as a basis. Thus, encryption will only work correctly if all devices have the same UTC time.

For secure (encrypted) calls, it is required that both endpoints support SRTP. The secure call indication tells the user that the other endpoint has acknowledged the secure connection

The SRTP type sets the key exchange method (negotiation method) for secure calls via SRTP. The following encryption key exchange methods are available:

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 78

administration.fm

SIP server certificate validation

System

Submit

Reset

Validate SW upgrade

Administration

Security

•MIKEY

• SDES (see SDES Configuration)

The SRTP Type and Use SRTCP options are only available for secure (encrypted) calls, i.e. these parameters are only enabled if Use secure calls is activated.

When Use SRTCP is activated (together with Use secure calls), the phone will use SRTCP (Se- cure RTCP) to transmit and receive RTP control packets.

If SRTP is enabled, ANAT interworking (see Media/SDP) is only possible if SDES is

configured as the key exchange protocol for SRTP.

Administration via WBM

System > Security > System

Administration via Local Phone

--- Administration

--- System

--- Security

--- System

|--- SIP server certificate validation

--- Validate SW upgrade

3.5.2 SRTP Configuration

The SDP negotiation parameter specifies whether the use of SRTP will be forced by the phone. The following choices are available:

• RTP + SRTP - Both non-encrypted (non-secure) and encrypted (secure) media connections are offered. Non-encrypted connections are preferred over encrypted connections, i.e. the phone uses the non-encrypted RTP connection if the remote party accepts it and only switches to SRTP if RTP is not accepted.

• With SRTP only, only an encrypted (secure) media connection is allowed; if the remote party should not support SRTP, no connection will be established.

• With SRTP + RTP, the phone will try to establish an SRTP connection, but fall back to RTP if this should fail. This is the recommended option.

A31003-C1000-M101-1-76A9, 03/2016

78 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 79

administration.fm

SRTP config

Submit

Reset

SHA1-80 ranking

SHA1-32 ranking

SRTP key mode

RTP + SRTP (2mline)

SDP mode

MIKEY

Use secure calls

Use SRTCP

;

Administration

Security

With SHA1-80 ranking and SHA1-32 ranking, the ranking for each crypto-suite for negotiation is defined. Additionally, each crypto-suite can be enabled or disabled.

Administration via WBM

System > Security > SRTP config

Administration via Local Phone

--- Administration

--- System

--- Security

--- SRTP config

--- SHA1-32 ranking

3.5.3 Access control

The CCE access parameter controls TCP and UDP access for the CCE (CommsChannel Extender). This affects the operation of the OpenStage Manager, local CTI access, and HPT access. When Disable is selected, both TCP and UDP are disabled. With Enable, there are no restrictions. With Factory reset claw, the ’hooded claw’ keypad mechanism to initiate a factory reset without requiring an authenticated access can be enabled or disabled.

The Serial port parameter controls access to the serial port. When set to No password, a ter-

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

minal connected to the port can interact with the phone’s operating system without restrictions. When Passwd reqd is selected, the serial port requires a password for access (root user is not available). When Unavailable is chosen, the serial port is not accessible. As a prerequisite, the root user needs to create a user and to define a password via Serial Access, so that access can be granted when the Password required prompt is issued.

Page 80

administration.fm

Access control

Submit

Reset

Factory reset claw

CCE access

No Password

Serial port

Enable

;

Administration

Security

Administration via WBM

System > Security > Access control

Administration via Local Phone

--- Administration

--- System

--- Security

--- Access control

|--- CCE access |--- Factory reset claw

--- Serial port

A31003-C1000-M101-1-76A9, 03/2016

80 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 81

administration.fm

Logging

Submit

Reset

Archive to DLS

Max. lines

50%

Archive when at

500

20101105-0010

Last archived

Administration

Security

3.5.4 Security Log

A circular security log is used to capture important security specific events. It can be exported as CSV data to an external application for analysis.

The security log cannot be disabled.

• The Max. lines parameter defines the maximum number of entry lines that can be kept in the security log before old entries are overwritten by new entries.

• Archive to DLS controls whether the log is sent to the DLS. When activated, the DLS is used to automatically archive the security log so that no log entries will be lost.

• Archive when at: This value sets the trigger for log archiving. Automatic archiving of new security log entries will occur when the percentage of unarchived entries in the log is as specified or more. When set to disabled, every new entry will trigger a save (only possible via DLS). The possible values are "10%”, ”20%”, ”30%”, ”35%”, ”40%”, ”45%”, ”50%”, ”55%”, ”60%”, ”65%”, ”70%”, ”80%”, ”90%”.

The security log upload may be accomplished in two ways: – If "Archive to DLS" is enabled, if the security log reaches the threshold % for un-

achieved entries, the phone will initiate an upload.

– If "Archive to DLS" is NOT enabled and the security log reaches the threshold % for

unachieved entries, the phone only sets the "archive-me" flag, it does not initiate the archive.

It is up to the DLS to recognize the flag and initiate an upload.

• Last archived shows the date when the security log was last archived to the DLS.

Administration via WBM

System > Security > Logging

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 82

administration.fm

Security log entry

OCSR Failure

User access

Cancel faults

Faults

20111009-2206

Admin access

All

Submit Reset

Administration

Security

Administration via Local Phone

--- Administration

--- System

--- Security

--- Logging

|--- Max. lines |--- Archive to DLS |--- Archive when at

--- Last archived

3.5.5 Security-Related Faults

• Security log entry shows the date and time of a loss of security log entries.

The entries in this list are only displayed until they are reported to the DLS, which

usually happens very fast. After that, the entries are automatically deleted from the phone. If the entries are not deleted automatically, they can be deleted manually by using the Cancel faults parameter.

• OCSR failure: Shows the date and time when the phone was unable to connect to any certificate checking server for revoked certificates.

• Admin access: Shows the date and time when the phone encountered multiple consecutive failures to enter the admin password.

• User access: Shows the date and time when the phone encountered multiple consecutive failures to enter the user password.

Administration via WBM

System > Security > Faults

A31003-C1000-M101-1-76A9, 03/2016

82 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 83

administration.fm

Administration

Security

Administration via Local Phone

--- Administration

--- System

--- Security

--- Faults

|--- Security log entry |--- OCSR failure |--- Admin access

--- User access

3.5.6 Password Policy

3.5.6.1 General Policy

• Expires after (days): Sets the maximum validity period of a password.

• Warn before (days): Specifies when the user/admin is notified that his password will ex- pire.

• Force changed: Only affects the User password. When Force changed is activated, the user will be forced to change his/her password at next login. This only applies to users, not to administrators.

• Tries allowed: Specifies the maximum number of password entry trials before the password is suspended. Values: 0 (no limits), 2, 3, 4, 5

• No change for (hours): Specifies a period before a password is allowed to be changed again. Value range: 0 to 99

• Suspended for (mins): Defines how long a password will be suspended after the number of failed retries has exceeded. Value range: 0 to 99

• History valid for (days): Defines a period in days during which the history is valid. Passwords no longer used are kept in history lists for the user and admin passwords to prevent reuse of past passwords. This list is organised as FIFO (First In, First Out) so that it always contains the latest passwords.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 84

administration.fm

Warn before (days)

Force changed

Tries allowed

No change for (hours)

History valid for (days)

Generic policy

Expires after (days)

Submit

Reset

Suspended for (mins)

Expiry date

Minimum length

Password history

Current status

Admin policy

Submit

Reset

2038-01-19T03:14:07+00:00

Active

Administration

Security

Administration via WBM

Security and Policies > Password > Generic Policy

3.5.6.2 Admin Policy

• Expiry date: Shows the date and time when the admin password will expire.

• Minimum length: Defines the minimum number of characters for the admin password.

• Password history: Specifies the number of entries to be kept in the admin password history. New passwords must not match any password in the history.

• Current status: Determines the status for the admin password. When set to "Active", the admin password is available for use. With "Suspended", the admin password is not available for a period or until reset. When set to "Disabled", all access via the admin password is disabled. The status of the admin password can only be set via DLS/WPI. It is changed internally to "suspended" when the password has been entered incorrectly more times than allowed.

Administration via WBM

Security and Policies > Password > Admin Policy

84 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 85

administration.fm

Special chars reqd

Bar repeat length

Min char difference

Character set

Digits required

Submit

Reset

Ucase chars reqd.

Lcase chars reqd.

Change Admin password

Old password

New password

Confirm password

Submit

Reset

Administration

Security

3.5.6.3 Character Set

The composition of the password can be configured in detail.

• Ucase chars reqd.: Defines the minimum number of uppercase characters. Value range: 0 to 24

• Lcase chars reqd.: Defines the minimum number of lowercase characters. Value range: 0 to 24

• Digits required: Defines the minimum number of digits. 0 to 24

• Special chars reqd: Defines the minimum number of special characters. The set of possible characters is ` - = [ ] ; ’ # \ , . / ¬ ! ” £ $ % ^ & * ( ) _ + { } : @ ~ | < > ? Value range: 0 to 24

• Bar repeat length: Specifies the maximum number of consecutive uses of a character. Value range: 0 to 24, but not 1 (with 1 set as value, no password would be valid, because it would be forbidden to use any character once).

• Min char difference: Specifies the minimum number of characters by which a new password must differ from the previous password. Value range: 0 to 24

Administration via WBM

Security and Policies > Password > Character set

3.5.6.4 Change Admin and User password

The passwords for user and administrator can be set here. They have to be confirmed after entering. The factory setting for the Admin password is "123456"; it should be changed after the first login (Password handling in previous versions see Section 3.19, “Password”).

Administration via WBM

Security and Policies > Password > Change Admin password

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 86

administration.fm

Change User password

Admin password

New password

Confirm password

Submit

Reset

Generic

Submit

Reset

OCSP check

OCSR 1 address

OCSR 2 address

Administration

Security

Security and Policies > Password > Change User password

Administration via Local Phone

--- Admin

--- Security & policies

--- Password

|--- Change Admin password ||--- Current password ||--- New password ||--- Confirm password

--- Change User password

--- Admin password

--- New password

--- Confirm password

3.5.7 Certificate Policy

3.5.7.1 Online Certificate Check

The Online Certificate Status Protocol (OCSP) is used to check if a certificate to be used has been revoked. This protocol is used to query an Online Certificate Status Responder (OCSR) at the point when the certificate is being validated. The address of an OCSR can be configured on the phone and can also be obtained from the certificate to be checked (which will have the priority).

• OCSP check: If activated, the configured OCSR is requested to check if the certificate has been revoked.

• OCSR 1 address: Specifies the IP address (or FQDN) of a primary OCSP responder.

• OCSR 2 address: Specifies the IP address (or FQDN) of a secondary OCSP responder.

Administration via WBM

Security and Policies > Certificates > Generic

86 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 87

administration.fm

Secure 802.1x

Authentication policy

Secure SIP server

Submit

Reset

None

Secure file transfer

Secure send URL

None

LDAP via TLS

None

Administration

Security

3.5.7.2 Server Authentication Policy

For individual certificates provided by specific servers, the level of authentication can be configured. When "None" is selected, no certificate check is performed. With "Trusted", the certificate is only checked against the signature credentials provided by the remote entity for signature, and the expiry date is checked. When "Full" is selected, the certificate is fully checked against the credentials provided by the remote entity for signature, the fields must match the requested subject/usage, and the expiry date is checked.

• Secure file transfer sets the authentication level for the HTTPS server to be used (see Section 3.16.2, “Common FTP/HTTPS Settings (Defaults)”).

• Secure send URL sets the authentication level for the server to which special HTTP requests are sent on key press ("Send URL" function, see Section 3.9.31, “Send Request via HTTP/HTTPS”).

• Secure SIP server sets the authentication level for the SIP server connected to the phone (see Section 3.6.7, “SIP Registration”).

• Secure 802.1x sets the authentication level for the 802.1x authentication server.

• LDAP via TLS sets the authentication level for LDAP access.

Administration via WBM

Security and Policies > Certificates > Authentication policy

Administration via Local Phone

--- Admin

--- Security & policies

--- Certificates

--- Authentication policy

|--- Secure file transfer |--- Secure send URL |--- Secure SIP server |--- Secure file transfer

--- LDAP via TLS

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 88

administration.fm

Terminal name

Display identity

Enable ID

Web name

DNS name construction

System Identity

4711

Terminal number

4711

Submit

Reset

OPDPIPCP

Only number

;

Administration

System Settings

3.6 System Settings

3.6.1 Terminal and User Identity

3.6.1.1 Terminal Identity

Within a SIP environment, both Terminal Number and Terminal Name may serve as a phone number. The values are used in the userinfo part of SIP URIs.

In order to register with a SIP registrar, the phone sends REGISTER messages to the registrar containing the contents of Terminal number.

Data required

• Terminal number: Number to be registered at the SIP registrar.

• Terminal name: Name to be registered at the SIP registrar.

Administration via WBM

System > System Identity

Administration via Local Phone

--- Admin

--- System

--- Identity

|--- Terminal number

--- Terminal name

3.6.1.2 Display Identity

If an individual name or number is entered as Display identity and Enable ID is activated, it is displayed in the phone’s status bar instead of the Terminal number.

A31003-C1000-M101-1-76A9, 03/2016

88 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 89

Administration via WBM

Terminal name

Display identity

Enable ID

Web name

DNS name construction

System Identity

4711

Terminal number

4711

Submit

Reset

openstage

Only number

;

System > System Identity

Administration via Local Phone

--- Admin

--- System

--- Identity

|--- Display identity

--- Enable ID

administration.fm

Administration

System Settings

3.6.2 Emergency and Voice Mail

It is important to have an Emergency number configured. If the phone is locked, a clickable area for making an emergency call is created.

If more than one emergency number is needed, additional numbers can be configu-

If a mailbox located at a remote server shall be used, its Voice mail number must be entered.

red in the canonical dial settings (Section 3.13.1, “Canonical Dialing Configuration”).

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 90

administration.fm

Voice Mail number

Allow refuse

Hot/warm phone

Hot/warm destination

Initial digit timer (seconds)

Emergency number

Allow uaCSTA

Server features

Not used timeout (minutes)

Transfer on hangup

3335

General

Bridging enabled

Dial plan enabled

FPK program timer

No action

;

; ;

;

MWI LED

Key & AlertBar

Missed call LED

Key only

Administration

System Settings

Administration via WBM

System > Features > Configuration

Administration via Local Phone

--- Admin

--- System

--- Features

--- Configuration

--- General

|--- Emergency number

--- Voicemail number

3.6.3 Energy Saving

3.6.3.1 Backlight Time Setting (OpenScape Desk Phone CP600 only)

After the phone has been inactive within the timespan specified in Backlight time, the display backlight is switched off to save energy.

The possible values are: 1 minute, 5 minutes, 30 minutes, 60 minutes, 2 hours, 4 hours, or 8 hours. Moreover, with OpenScape Desk Phone CP600 this parameter can also be configured by the user. The default value is 1 minute.

Administration via WBM

Local functions > Energy saving

90 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016

Page 91

administration.fm

Backlight time

Energy saving

2 hours

Submit

Reset

Administration

System Settings

Administration via Local Phone

--- Admin

--- Local Functions

--- Energy saving

--- Backlight time

3.6.3.2 Energy Efficient Ethernet (OpenScape Desk Phone CP200 only)

The OpenScape Desk Phone CP200 phone supports the standard IEEE 802.3az (Energy Efficient Ethernet).

The energy saving benefit provided by this standard can only be received when the phone is connected to a network component which also is able to support the IEEE 802.3az standard.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 92

administration.fm

FAC prefixes

Call logging

Submit

Reset

Administration

System Settings

3.6.4 Call logging

This configuration item allows the phone to detect if a number dialled by the User is likely to be a Feature Access Code (FAC) by comparing the start of the dialled number with the configured FAC prefixes. If the dialled number does match a FAC prefix and the SIP server has provided a different number for the called party then the number shown in the Dialled tab list of Call Log is changed from the dialled number to the server provided number. If the new configuration item is left empty then the Dialled tab list display will remain as currently populated (i.e. the dialled number is shown in the list).

A further enhancement for an entry matched to a FAC in the Dialled tab list of Call Log is that the context menu for the list entry now provides both numbers from the last call associated with the entry as Dial options in the context menu for the list entry (similar to that already provided by the context menu for the Details form of such an entry). Note that the Call Log display on OpenScape Desk Phone CP200 has been simplified so that an entry only displays a name or a number (not both) and there is no access to entry details. However, this only limits the display and the default dialling number for an OpenScape Desk Phone CP200 entry is determined as above.

Call Log entry grouping rules for the Dialled tab list remain unchanged, if multiple FACs all map to numbers associated with one contact then they are grouped together.

Data required

• FAC prefixes: A comma separated list of feature prefixes considered to represent feature codes configured at the SIP server for abbreviated dialling.

Administration via WBM

Local functions > Call logging

A31003-C1000-M101-1-76A9, 03/2016

92 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 93

administration.fm

Enable call log

General

Submit

Reset

Administration

System Settings

3.6.4.1 Logging of Missed Calls (via User menu)

This feature allows the user to

• distinguish logged calls based on the device on which the calls were completed, and

• decide whether missed calls that were answered elsewhere shall be – included into the call log, or – excluded from the call log, i.e. not logged at all

• decide whether a number which also exists in missed calls tab of call log is to be deleted from call log when this number is called

– manually – when called

In the Call Lists, missed calls that were completed elsewhere are marked with a check mark. For details, please refer to the User manual.

Forwarded calls are not logged under "Missed calls", but under "Forwarded" in the call log.

Administration via WBM (User menu)

User > Configuration > Call logging > General

User > Configuration > Call logging > Missed calls

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 94

administration.fm

Administration

System Settings

Administration via Local Phone (User menu)

--- User

--- Configuration

--- Call logging

|--- General ||--- FAC prefixes

--- Missed calls

|--- Answered elsewhere ||--- Include ||--- Exclude

--- Delete entry

|--- Manually

--- When called

Answered elsewhere > Include: Calls completed elsewhere will be logged as missed calls. In the call log these calls are marked with a check mark.

Answered elsewhere > Exclude: Calls completed elsewhere will not be visible on phone; they will not be logged at all.

Delete entry > Manually: Call numbers remain in call log until they are deleted manually.

Delete entry > When called: Call numbers existing in missed call list are deleted automatically

when they are called again.

3.6.5 Date and Time

TIf the DHCP server in your network provides the IP address of the SNTP server, no manual configuration is necessary. If not, you have to set the SNTP IP address parameter manually.

For correct display of the current time, the Timezone offset must be set appropriately. This is the time offset from UTC (Universal Time Coordinated). If, for instance, the phone is located in Munich, Germany, the offset is +1 (or simply 1); if it is located in Los Angeles, USA, the offset is -8. For countries or areas with half-our time zones, like South Australia or India, non-integer values can be used, for example 10.5 for South Australia (UTC +10:30).

If the phone is located in a country with DST (Daylight Saving Time), you can choose whether DST is toggled manually or automatically. For manual toggling, disable Auto time change and enable or disable Daylight saving; the change will be in effect immediately. For automatical toggling, enable Auto time change; now, daylight saving is controlled by the DST zone / Time zone parameter. This parameter determines when DST starts or ends, and must be set according to the location of the phone.

The Difference (minutes) parameter defines how many minutes the clock is put forward for DST. In Germany, for instance, the value is +60.

A31003-C1000-M101-1-76A9, 03/2016

94 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 95

administration.fm

SNTP IP address

Timezone offset (hours)

Date and time

Daylight saving

Time source

192.43.244.18

Daylight saving

Difference (minutes)

Auto time change

;

DST zone

Europe (Rest)

Submit

Reset

Administration

System Settings

Please note that Difference (minutes) must be specified both for manual and auto-

matic DST toggling.

3.6.5.1 SNTP is Available, but no Automatic Configuration by DHCP Server

Data required

• SNTP IP address: IP address or hostname of the SNTP server.

• Timezone offset (hours): Shift in hours corresponding to UTC.

• Daylight saving: Enables or disables daylight saving time in conjunction with Auto time change. Value range: "Yes", "No".

• Difference (minutes): Time difference when daylight saving time is in effect.

• Auto time change / Auto DST: Enables or disables automatic control of daylight saving time according to the DST zone. Value range: "Yes", "No". Default setting is Yes. After a factory reset, the system will be reset to this value.

• Time zone/DST zone: Area with common start and end date for daylight saving time. Value range: "Australia 2007 (ACT, South Australia, Tasmania, Victoria)", "Australia 2007 (New South Wales)", "Australia (Western Australia)", "Australia 2008+ (ACT, New South Wales, South Australia, Tasmania, Victoria)", "Brazil", "Canada", "Canada (Newfoundland)", "Europe (Portugal, United Kingdom)", "Europe (Finland)", "Europe (Rest)", "Mexico", "United States", "New Zealand", "New Zealand (Chatham)". Default setting for US is "United States". After a factory reset, the system will be reset to this value.

Administration via WBM

Date and Time

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 96

administration.fm

Local time (hh:mm):

Local date (day,month,year):

Use daylight saving:

Date and Time

Submit

Reset

November

87678

Difference (minutes):

200630

Auto time change

Administration

System Settings

Administration via Local Phone

--- Administration

--- Date and Time

--- Time source

|--- SNTP IP address

--- Timezone offset

3.6.5.2 No SNTP Server Available

If no SNTP server is available, date and time must be set manually.

The manual setting of time and date is located in the user menu, not in the

administrator menu.

Data required

• Local time (hh:mm): Local time.

• Local date (day, month, year): Local date.

• Allow daylight saving: Defines whether there is daylight is set.

• Difference (minutes): Timezone offset in minutes.

• Auto time change / Auto DST: Enables or disables automatic control of daylight saving time according to the Time zone. Value range: "Yes", "No"

Default setting is "Yes". After a factory reset, the system will be reset to this value.

Administration via WBM (User menu)

User > Date and Time

Administration via Local Phone

--- Menu

--- Date and Time

A31003-C1000-M101-1-76A9, 03/2016

96 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 97

administration.fm

Administration

System Settings

|--- Time |--- Date |--- Daylight saving |--- Difference (mins)

--- Auto DST

3.6.6 SIP Addresses and Ports

3.6.6.1 SIP Addresses

In this group of parameters, the IP addresses or host names for the SIP server, the SIP registrar, and the SIP gateway are defined.

SIP server address provides the IP address or host name of the SIP proxy server (OpenScape Voice). This is necessary for outgoing calls. SIP registrar address contains the IP address or host name of the registration server, to which the phone will send REGISTER messages. When registered, the phone is ready to receive incoming calls. SIP gateway ad- dress gives the IP address or host name of the SIP gateway. If configured, the SIP gateway is used for outgoing calls; otherwise the server specified in SIP server address is used. A SIP gateway is able to perform a conversion of SIP to TDM, which enables to send calls directly into the public network.

Enhanced survivability using DNS SRV is available. To make use of it, a special con-

Data required

• SIP server address: IP address or host name of the SIP proxy server.

• SIP registrar address: IP address or host name of the registration server.

• SIP gateway address: IP address or host name of the SIP gateway.

figuration is required. For details, please refer to Section 3.6.10, “Resilience and Survivability”.

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 98

administration.fm

SIP server address

SIP registar address

SIP gateway address

Registration

SIP Survivability

SIP Session

SIP Addresses

192.168.1.165

Session timer enabled

Session duration (seconds)

Registration timer (seconds)

3600

Server type

OS Voice

Submit

Reset

192.168.1.165

Backup registration allowed

Backup proxy address

Backup registration timer (seconds)

3600

;

Backup transport

Backup OBP flag

UDP

Realm

User ID

Password

MLPP base

Local

dsn+uc

MLPP Domain

Other Domain

Backup connection

Persistent (SB)

Administration

System Settings

Administration via WBM

System > Registration

Administration via Local Phone

--- Admin

98 OpenScape Desk Phone CP200/400/600, Administrator Documentation

--- System

--- Registration

--- SIP Addresses

|--- SIP server |--- SIP registrar

--- SIP gateway

A31003-C1000-M101-1-76A9, 03/2016

Page 99

administration.fm

SIP local

Backup proxy

RTP base

Download server (default)

LDAP server

HTTP proxy

LAN port speed

PC port speed

389

Port configuration

5060

Automatic

SIP gateway

5060

Submit

Reset

Automatic

5060

5010

SIP Server

SIP registrar

5060

PC port mode

PC port autoMDIX

disabled

Administration

System Settings

3.6.6.2 SIP Ports

In this group of parameters, the ports for the SIP server, the SIP registrar, and the SIP gateway are defined (for further information see Section 3.6.6.1, “SIP Addresses”), as well as the SIP port used by the phone (SIP local).

Data required

• SIP server: Port of the SIP proxy server. Default: 5060.

• SIP registrar: Port of the server at which the phone registers. Default: 5060.

• SIP gateway: Port of the SIP gateway. Default: 5060.

• SIP local: Port used by the phone for sending and receiving SIP messages. Default: 5060.

When changing the SIP Transport protocol from UDP/TCP to TLS, the SIP port now

also have to be changed correspondingly (e.g. SIP port from 5060 to 5061) and on changing vice versa.

Administration via WBM

Network > Port configuration

A31003-C1000-M101-1-76A9, 03/2016 OpenScape Desk Phone CP200/400/600, Administrator Documentation

Page 100

administration.fm

Administration

System Settings

Administration via Local Phone

--- Admin

--- Network

--- Port Configuration

|--- SIP server |--- SIP registrar |--- SIP gateway

--- SIP local

3.6.7 SIP Registration

Registration is the process by which centralized SIP Server/Registrars become aware of the existence and readiness of an endpoint to make and receive calls. The phone supports a number of configuration parameters to allow this to happen. Registration can be authenticated or un-authenticated depending on how the server and phone is configured.

For operation with an OpenScape Voice server, set Server type to "OS Voice". When HiQ8000 is to be used, set it to "HiQ8000". The expiry time of a registration can be specified by Regis-

tration timer.

Unauthenticated Registration

For unauthenticated registration, the following parameters must be set on the phone: Terminal number or Terminal name (see Section 3.6.1.1, “Terminal Identity”), SIP server and SIP registrar address (see Section 3.6.6.1, “SIP Addresses”).

In unauthenticated mode, the server must pre-authenticate the user. This procedure is server specific and is not described here.

Authenticated Registration

The phone supports the digest authentication scheme and requires some parameters to be configured in addition to those for unauthenticated registration. By providing a User ID and a Password which match with a corresponding account on the SIP registrar, the phone authenticates itself. Optionally, a Realm can be added. This parameter specifies the protection domain wherein the SIP authentication is meaningful. The protection domain is globally unique, so that each protection domain has its own arbitrary usernames and passwords.

A challenge from the server for authentication information is not only restricted to the

100 OpenScape Desk Phone CP200/400/600, Administrator Documentation

A31003-C1000-M101-1-76A9, 03/2016