Page 1
Siemens Enterprise Communications
www.siemens-enterprise.com
Documentation
OpenScape Desk Phone IP, Phone Administration
P31003D3000M1000176A9
02-2013
Siemens Enterprise Communications GmbH & Co. KG.
2013
OpenScape Desk Phone IP
Phone Administration
Administrator Documentation
A31003-D3000-M100-01-76A9
Page 2
Siemens Enterprise Communications
www.siemens-enterprise.com
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.
Copyright © Siemens Enterprise
Communications GmbH & Co. KG 02-2013
Hofmannstr. 51, D-80200 München
Siemens Enterprise Communications GmbH & Co. KG
is a Trademark Licensee of Siemens AG
Reference No.: A31003-D3000-M100-01-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
provide the respective characteristics shall only exist if
expressly agreed in the terms of contract. Availability
and technical specifications are subject to change
without notice.
OpenScape, OpenStage and HiPath are registered
trademarks of Siemens Enterprise
Communications GmbH & Co. KG.
All other company, brand, product and service names
are trademarks or registered trademarks of their
respective holders.
Page 3
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 3
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Maintenance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 About the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Conventions for this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 The OpenScape Desk Phone Family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5.1 OpenScape Desk Phone IP 35G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6 Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6.1 Web-based Management (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6.2 DLS (OpenScape Deployment Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6.3 Local Phone Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 Assembling and Installing the Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.1 Shipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.2 Connectors at the Bottom Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.3 Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.4 How to Connect the Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1 How to Access the Web Interface (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2 How to Set the Terminal Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.3 Basic Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.4 DHCP Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.5 Date and Time / SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3.6 SIP Server Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3.7 Extended Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.8 Vendor Specific: VLAN Discovery and DLS Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.8.1 How to Use a Vendor Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.8.2 Setup using a DHCP Server on Unix/Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.8.3 How to Use Option #43 "Vendor Specific" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.9 How to Register at OpenScape Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4 Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.5 Cloud Deployment (V3 R1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.5.1 Process of Cloud Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.5.2 Aborting Cloud Deployment Process by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.5.3 Re-trigger Cloud Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.5.4 Deployment errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1 Access via Local Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2 LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2.1 LAN Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2.2 VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2.2.1 Automatic VLAN discovery using LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.2.2.2 Automatic VLAN discovery using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.2.2.3 Manual Configuration of a VLAN ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.3 LLDP-MED Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Contents
Page 4
Contents
A31003-D3000-M100-01-76A9, 02-2013
4 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
3.3 IP Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.1 Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.1.1 Layer 2 / IEEE 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.1.2 Layer 3 / Diffserv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.3.2 Protocol Mode IPv4/IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3.3 Use DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.3.4 IP Address - Manual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.3.4.1 How to Manually Configure the Phone´s IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.3.5 Default Route/Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.3.6 Specific IP Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.3.7 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.3.7.1 DNS Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.3.7.2 DNS Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.3.7.3 Terminal Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.3.8 Configuration & Update Service (DLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.3.9 SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.4.1 Speech Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.4.1.1 Security - General Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.4.1.2 MIKEY Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.4.1.3 SDES Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.4.2 Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.4.3 Security Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.4.4 Security-Related Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.4.5 Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.4.5.1 General Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.4.5.2 Admin Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.4.5.3 User Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.4.5.4 Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.4.5.5 Change Admin and User password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.4.6 Certificate Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.4.6.1 Online Certificate Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.4.6.2 Server Authentication Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.5 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.1 Terminal and User Identity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.1.1 Terminal Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.5.1.2 Display Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.5.2 Emergency and Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.5.3 Call logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.5.3.1 Logging of Missed Calls Answered Elsewhere (via User menu) . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.5.4 Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.5.4.1 SNTP is Available, but No Automatic Configuration by DHCP Server . . . . . . . . . . . . . . . . . . . . . . 83
3.5.4.2 No SNTP Server Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.5.5 SIP Addresses and Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.5.5.1 SIP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.5.5.2 SIP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.5.6 SIP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.5.7 SIP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 90
3.5.7.1 Outbound Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.5.7.2 SIP Transport Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
3.5.7.3 Media/SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
3.5.8 SIP Session Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Page 5
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 5
Contents
3.5.9 Resilience and Survivability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.5.9.1 Connectivity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.5.9.2 Response Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.5.9.3 Non-INVITE Transaction Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.5.9.4 Maximum Registration Backoff Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.5.9.5 Backup SIP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.6 Feature Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.7 Feature Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.7.1 Allow Refuse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.7.2 Hot/Warm Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.7.3 Initial Digit Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.7.4 Group Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.7.4.1 Addressing - via Group Pickup URI Feature Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.7.4.2 Pickup Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.7.5 Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.7.5.1 Transfer on Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.7.5.2 Transfer on Hangup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.7.6 Callback URIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.7.6.1 Call Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.7.7 Message Waiting Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.7.8 Indicate Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.7.9 System-Based Conference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.7.10 Server Based Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.7.11 uaCSTA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
3.7.12 Local Menu Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
3.7.13 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.8 Free Programmable Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
3.8.1 How to Configure Free Programmable Keys (FPKs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
3.8.2 How to Enable "Long Press" for Free Programmable Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
3.8.3 Clear (no feature assigned) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
3.8.4 Selected Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
3.8.5 Repeat Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
3.8.6 Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
3.8.7 Ringer Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.8.8 Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.8.9 Alternate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.8.10 Blind Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.8.11 Join Two Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.8.12 Deflect a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.8.13 Shift Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.8.14 Phone-Based Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.8.15 Accept Call via Headset (OpenScape Desk Phones). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
3.8.16 Do Not Disturb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
3.8.17 Group Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.8.18 Repertory Dial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.8.19 Hunt Group: Send Busy Status Using Feature Toggle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
3.8.20 Mobile User Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
3.8.21 Directed Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.8.22 Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.8.23 Cancel Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3.8.24 Pause Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3.8.25 Resume Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Page 6
Contents
A31003-D3000-M100-01-76A9, 02-2013
6 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
3.8.26 Consultation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
3.8.27 Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.8.28 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.8.29 Auto Answer With Zip Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.8.30 Server Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
3.8.31 BLF Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
3.8.32 Send URL Request via HTTP/HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
3.8.33 Built-in Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
3.8.34 2nd Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.8.35 Show phone screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.9 Preset Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.10 Fixed Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.11 Multiline Appearance/Keyset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.11.1 Line Key Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
3.11.2 How to Configure Line Keys for Keyset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
3.11.3 Configure Keyset Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
3.11.4 Line Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
3.11.4.1 Preview and Preselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
3.11.5 Immediate Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
3.11.6 Direct Station Select (DSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
3.11.6.1 General DSS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
3.11.6.2 Settings for a DSS key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
3.12 Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
3.12.1 Canonical Dialing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
3.12.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
3.12.3 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
3.13 Distinctive Ringing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
3.13.1 Special Ringers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
3.14 Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
3.15 Transferring Phone Software, Application and Media Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
3.15.1 FTP/HTTPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
3.15.2 Common FTP/HTTPS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
3.15.3 Phone Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
3.15.3.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
3.15.3.2 Download/Update Phone Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
3.15.4 Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
3.15.4.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
3.15.4.2 Download Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
3.15.5 Ringer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
3.15.5.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
3.15.5.2 Download Ringer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
3.15.6 Dongle Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
3.15.6.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
3.15.6.2 Download Dongle Key File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
3.16 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
3.16.1 RTP Base Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
3.16.2 Codec Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 188
3.16.3 Audio Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
3.17 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
3.18 Troubleshooting: Lost Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
3.19 Restart Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
3.20 Factory Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Page 7
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 7
Contents
3.21 SSH – Secure Shell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
3.22 Display License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
3.23 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
3.23.1 Display General Phone Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
3.23.2 View Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
3.23.3 User Access to Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
3.23.4 Diagnostic Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
3.23.5 LAN Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
3.23.6 LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
3.23.7 IP Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
3.23.8 Process and Memory Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
3.23.9 Fault Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
3.23.10 Easy Trace Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
3.23.10.1 Call Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
3.23.10.2 Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
3.23.10.3 Call Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
3.23.10.4 DAS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
3.23.10.5 DLS Data Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
3.23.10.6 802.1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
3.23.10.7 Key Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
3.23.10.8 LAN Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
3.23.10.9 Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
3.23.10.10 Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
3.23.10.11 Phone administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
3.23.10.12 Sidecar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
3.23.10.13 SIP Standard Multiline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
3.23.10.14 SIP Standard Single Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
3.23.10.15 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
3.23.10.16 Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
3.23.10.17 Web Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
3.23.10.18 Clear All Profiles (No Tracing for All Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
3.23.11 QoS Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
3.23.11.1 Conditions and Thresholds for Report Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
3.23.11.2 View Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
3.23.12 Core dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
3.23.13 Remote Tracing – Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
3.23.14 HPT Interface (For Service Staff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
3.24 MWI LED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
3.25 Missed Call LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
3.26 Impact Level Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
4 Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.1 Default Port List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.2 Troubleshooting: Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
5 Examples and HowTos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
5.1 Canonical Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
5.1.1 Canonical Dialing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 232
5.1.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
5.1.2.1 Conversion examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
5.2 An LLDP-Med Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
5.3 Example Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Page 8
Contents
A31003-D3000-M100-01-76A9, 02-2013
8 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
5.3.2 Dial Plan Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.3.3 How To Set Up And Deploy A Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
6 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Page 9
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 9
Overview
Important Notes
1 Overview
Related Topics
1.1 Important Notes
Related Topics
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 be operated using the supplied plug-in power unit.
Use only original accessories from Siemens Enterprise Communications GmbH &
Co. KG!
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.
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.
Page 10
Overview
A31003-D3000-M100-01-76A9, 02-2013
10 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Maintenance Notes
1.2 Maintenance Notes
Related Topics
1.3 About the Manual
The instructions within this manual will help you in administering and maintaining
the OpenScape Desk Phone. 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 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 step by step,
wherever expedient. For the users, a separate manual is provided.
You can find further information on the official Siemens Enterprise
Communications website (http://www.siemens-enterprise.com) and on the
Siemens Enterprise Wiki (http://wiki.siemens-enterprise.com).
Related Topics
1.4 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 V3R2.
Related Topics
1.5 The OpenScape Desk Phone Family
Related Topics
Do not perform maintenance work or servicing of the telephone in environments
where there is a danger of explosions.
Use only original accessories from Siemens Enterprise Communications GmbH
& Co. KG. Using other accessories may be dangerous, and will invalidate the
warranty and the CE mark.
Never open the telephone or add-on equipment, e.g. a key module.
Page 11
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 11
Overview
The OpenScape Desk Phone Family
1.5.1 OpenScape Desk Phone IP 35G
1
2
3
4
5
3
6
7
5
8
Page 12
Overview
A31003-D3000-M100-01-76A9, 02-2013
12 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
The OpenScape Desk Phone Family
Related Topics
1With the Handset, the user can pick up and conduct calls in the usual
manner.
2 The Display provides intuitive support for telephone operation and allows
the user to control the phone settings via the local User and Admin menu.
3 The Fixed Function Keys (NOT re-programmable) provide access to
frequently used telephony functions, as follows:
Messages: Provides access to the Call Log, allowing the user to view and
manage the lists of Missed Calls, Dialed Calls, Received Calls, Forwarded Calls and to access and manage the Voice Mail.
Settings: Provides access to the User and Admin menus for locally con-
trolling the phone settings
Speaker: Turns on/off the hands-free mode (speakerphone).
Headset: Switches the audio sound to the headset or back from the head-
set to the handset speaker/speakerphone.
Vol. + and Vol. -: Increases/decreases the speaker/headset and handset
volume.
Mute: Turns off/on the microphone during conversations. This feature is
used to prevent the listening party from hearing what is being said at the
calling party´s location or to prevent noise from being transmitted to all
participants in conference calls.
4With the Navigation Keys, the user/administrator can navigate through
the various phone functions, applications, and configuration menus.
5 The Fixed Function Keys (re-programmable via WBM or DLS) pro-
vide access to frequently used telephony functions, as follows:
Transfer: Transfers calls to other destinations.
Conference: Provides access to the conferencing features. By default,
pressing this key automatically seizes an outgoing line and turns on the
hands-free mode.
Hold: Places an ongoing call on hold or reconnects a held call.
6 The Keypad is used for entering phone numbers and text.
7 The Free Programmable Keys enable the user to customize the tele-
phone in line with his/her personal needs by assigning individual phone
numbers and functions.
Preset default values:
•Forward
• Pick up
• Do Not Disturb (DND)
8 Inbound calls are visually signaled via the Alert Bar.
Waiting Voice Mail messages and Missed Calls are also signaled via the
alert bar LED if the MWI LED and Missed call LED features are configured
accordingly.
Page 13
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 13
Overview
Administration Interfaces
1.6 Administration Interfaces
You can configure the OpenScape Desk Phone by using any of the methods
described in this chapter:
• via the Web Based Management (WBM) (see 1.6.1 Web-based Management
(WBM);
OR
• via the DSL (OpenScape Deployment Service) (see 1.6.2 DLS (OpenScape
Deployment Service);
OR
• via the Local Phone (see Local Phone Menu).
Related Topics
1.6.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.
INFO: To use this method, the phone must first obtain IP connectivity.
Related Topics
1.6.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 nonOpenScape 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.
Related Topics
1.6.3 Local Phone Menu
This method provides direct configuration of the OpenScape Desk Phone via the
local phone menu. Direct access to the phone is required.
INFO: As long as the IP connection is not properly configured,
you have to use this method to set up the phone.
Related Topics
Page 14
Startup
A31003-D3000-M100-01-76A9, 02-2013
14 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Prerequisites
2 Startup
Related Topics
2.1 Prerequisites
The OpenScape Desk Phone 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.
INFO: Only use switches in the LAN to which the OpenScape
phone is connected. An operation at hubs can cause serious
malfunctions in the hub and in the whole network.
• 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).
For additional information see the Wiki page http://wiki.siemens-enterprise.com/
wiki/IEEE_802.1x
Related Topics
2.2 Assembling and Installing the Phone
Related Topics
2.2.1 Shipment
• Phone
• Handset
• Handset cable
• Subpackage:
– Document "Information and Important Operating Procedures"
– Emergency number sticker
Related Topics
Page 15
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 15
Startup
Assembling and Installing the Phone
2.2.2 Connectors at the Bottom Side
OpenScape Desk Phone IP 35G
Related Topics
2.2.3 Assembly
Step by Step
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
Network
PC
Headset
Power
Handset
Page 16
Startup
A31003-D3000-M100-01-76A9, 02-2013
16 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
Write your phone number and the emergency numbers for the fire and police
departments on the included label and attach it to the telephone housing
where applicable, e.g. underneath the handset.
Related Topics
2.2.4 How to Connect the Phone
Step by Step
1) Plug the LAN cable into the connector at the bottom side of the telephone
and connect the cable to the LAN resp. switch.
a) If PoE (Power over Ethernet) is to be used, the PSE (Power Sourcing
Equipment) must meet the IEEE 802.3af specification.
INFO: The required power supply for the OpenScape Desk
Phone IP 35G must comply with the Power Consumption/Supply
Class 2.
b) Only if Power over Ethernet (PoE) is NOT supported, you have to use the
optional plug-in power supply:
INFO: The order no. for the plug-in power supply is regionspecific:
- EU: C39280-Z4-C510
- UK: C39280-Z4-C512
- USA: C39280-Z4-C511
Plug the power supply unit into the mains. Connect the plug-in power
supply unit to the jack at the bottom side of the phone.
2) If applicable, connect the following optional jacks:
• LAN connection to PC
• Headset (accessory)
Related Topics
2.3 Quick Start
This section describes a typical case: the setup of an OpenScape Desk Phone
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.
INFO: Alternatively, the DLS (OpenScape Deployment Service)
administration tool can be used. Its Plug & Play functionality
allows to provide the phone with configuration data by assigning
Page 17
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 17
Startup
Quick Start
an existing data profile to the phone’s MAC address or E.164
number. For further information, see the Deployment Service
Administration Manual.
INFO: Any settings made by a DHCP server are not configurable
by other configuration tools.
Related Topics
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:
Step by Step
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 configuration > IP address. The IP address is displayed.
• If DHCP is disabled or if no DHCP server is available in the IP network,
the IP address, subnet mask and default gateway/route 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 IP address or URL.
Example: https://192.168.1.15 or https://myphone.phones
Page 18
Startup
A31003-D3000-M100-01-76A9, 02-2013
18 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
For configuring the phone’s DNS name, please refer to 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 column contains the menu tree.
3) Click on the "Administrator Pages" tab. 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.
Related Topics
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:
Page 19
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 19
Startup
Quick Start
Step by Step
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 Term i na l
Identity.
Related Topics
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 IP Address - Manual Configuration for IP
address and subnet mask, and Default Route/Gateway for the default route.
Related Topics
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.
Page 20
Startup
A31003-D3000-M100-01-76A9, 02-2013
20 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
Step by Step
› In the left column, select Network > IPv4 configuration to open the "System
Identity" dialog. Select the check box to enable DHCP lease reuse.
Related Topics
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.4 Date and Time.
Related Topics
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.
Related Topics
Page 21
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 21
Startup
Quick Start
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 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 DNS Domain Name.
Related Topics
2.3.8 Vendor Specific: VLAN Discovery and DLS Address
INFO: The VLAN ID can also be configured by LLDP-MED (see
Automatic VLAN discovery using LLDP-MED).
If the phone is to be located in a VLAN (Virtual LAN), a VLAN ID must be
assigned. In case the VLAN shall be provided by DHCP, VLAN Discovery must
be set to "DHCP" (see Automatic VLAN discovery using DHCP).
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 (DLS).
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,
or
• the use of DHCP option 43 - see How to Use Option #43 "Vendor Specific".
Related Topics
Page 22
Startup
A31003-D3000-M100-01-76A9, 02-2013
22 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
2.3.8.1 How to Use a Vendor Class
Prerequisites
• 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.
• In the following, the configuration of vendor classes is explained both for a
Windows DHCP Server and for Unix/Linux.
Example: Configuration of the Windows DHCP Server
INFO: For DHCP servers on a pre-SP2 Windows 2003 Server.
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 set the required option
(without error message), so that it will appear in the DHCP
console afterwards:
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 reassigned using the DHCP console.
This error was corrected in Windows 2003 Server SP2.
Page 23
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 23
Startup
Quick Start
Step by Step
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.
A dialog opens with a list of the classes that are already available.
3) Press Add... to define a new vendor class.
4) Enter "OptiIpPhone" as Display name and give a description of this class.
Provide the class name proper by setting the cursor underneath ASCII and
typing "OptiIpPhone". The binary value is displayed simultaneously.
Page 24
Startup
A31003-D3000-M100-01-76A9, 02-2013
24 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
5) Click OK to apply the changes. The new vendor class now appears in the list:
6) Exit the window with Close.
7) In the DHCP console menu, right-click the DHCP server in question and
select Set Predefined Options from the context menu.
8) In the dialog, select the previously defined OptiIpPhone class and click on
Add... to add a new option. (If the workaround for a pre-SP2 Windows 2003
Server has been applied, the first option will be there already.)
9) In the following dialog, specify the option type as follows. (If the workaround
for a pre-SP2 Windows 2003 Server has been applied, the option type dialog
will be skipped for the first option.)
•Name: Free text, e. g. "OptiIpPhone element 01".
• Data type: "String".
Page 25
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 25
Startup
Quick Start
•Code: "1".
• Description: Free text, e. g. "tag 1 for OptiIpPhone class".
Click OK to return to the previous window.
10) The newly created option is displayed now. Enter "Siemens" in the Value
field.
11) If the VLAN is to be provided by DHCP: Repeat step 7 and 8, and then specify
the option type as follows. If you want to proceed to the configuration of the
DLS address, continue with step 13.
•Name: Free text, e. g. "OptiIpPhone element 02"
•Data type: "Long"
•Code: "2"
• Description: Free text, e. g. "tag 2 for OptiIpPhone class".
Click OK to return to the previous window.
Page 26
Startup
A31003-D3000-M100-01-76A9, 02-2013
26 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
12) The newly created option is displayed now. Enter the VLAN ID as a
hexadecimal number in the Value field. In the example, the VLAN ID is 42
(Hex: 0x2A).
If you do not intend to configure the DLS address, click OK and continue with
step 15.
13) If the DLS address is to be provided by DHCP: Repeat step 7 and 8, and then
specify the option type as follows.
•Name: Free text, e. g. "OptiIpPhone element 03".
• Data type: "String".
• Code: "3"
• Description: Free text, e. g. "tag 3 for OptiIpPhone class".
Click OK to return to the previous window.
Page 27
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 27
Startup
Quick Start
14) The newly created option is displayed now. Enter the DLS address in the
Value field, using the following format:
<PROTOCOL>:://<IP ADDRESS OF DLS SERVER>:<PORT NUMBER> In
the example, the DLS address is "sdlp://192.168.3.30:18443".
Click OK.
15) To define a scope, select the DHCP server in question, and then Scope, and
right-click Scope Options. Select Configure Options... in the context menu.
Page 28
Startup
A31003-D3000-M100-01-76A9, 02-2013
28 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
16) 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.
17) The DHCP console now shows the information that will be transmitted to 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.
Related Topics
Page 29
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 29
Startup
Quick Start
2.3.8.2 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-encapsulatedoptions" 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 in-stance, 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 must be "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 0 10
02:04:00:00:00:0A;
# Tag/Option #3: DLS IP Address (here: sdlp://
192.168.3.30:18443)
# 3 25 s d l p : / / 1 9 2 . 1 6 8 . 3 .
(...etc.)
03:19:73:64:6C:70:3A:2F:2F:31:39:32:2E:31:36:38:2E:33:2E:33:3
0: 3A:31:38:34:34:33;
match if substring (option vendor-class-identifier, 0, 11) =
"OptiIpPhone";
}
Related Topics
2.3.8.3 How to Use Option #43 "Vendor Specific"
Alternatively, option #43 can be used for setting up the VLAN ID and DLS
address. The following tags are used:
• Tag 1: Vendor name
• Tag 2: VLAN ID
• Tag 3: DLS address
Optionally, the DLS address can be given in an alternative way:
• Tag 4: DLS host name
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
Page 30
Startup
A31003-D3000-M100-01-76A9, 02-2013
30 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
The following example shows a VLAN ID with the decimal value "10". Providing:
For manual configuration of the VLAN ID see 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:
Example: Setup Using the Windows DHCP Server
Step by Step
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 tag 1, that is the vendor tag. The value has to be "Siemens".
Code Length VLAN ID
2 4 0010
02 04 00 00 00 0A
Code Length DLS IP address
3 25 sdl p: / / 192. 168. 3. 30: 18443
03 19 73646C703A2F2F3139322E3136382E332E33303A313834343
3
Page 31
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 31
Startup
Quick Start
4) If the VLAN ID is to be provided by DHCP: Enter the hexadecimal value in
Data entry. In the example, the VLAN ID is 10 (Hex: 0A).
5) If the DLS address is to be provided by DHCP: Enter the DLS address in the
Value field, using the following format: <PROTOCOL>:://<IP ADDRESS OF
DLS SERVER>:<PORT NUMBER>
INFO: For ensuring proper functionality, the port number should
not be followed by any character.
In the example, the DLS address is "sdlp://192.168.3.30:18443". Note that the
screenshot also shows the VLAN ID described in step 4.
Click OK.
Page 32
Startup
A31003-D3000-M100-01-76A9, 02-2013
32 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Quick Start
6) The DHCP console now shows the information that will be transmitted to the
corresponding workpoints.
Related Topics
2.3.9 How to Register at OpenScape Voice
Prerequisites
• For registration at the OpenScape Voice server, a SIP user ID (and password,
if required, depending on the SIP Server configuration) must be provided by
the phone. The following procedure describes the configuration using the web
interface (see 2.3.1 How to Access the Web Interface (WBM); if the web
interface is not accessible, please refer to 3.5.6 SIP Registration) for configuration via the local menu.
Page 33
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 33
Startup
Quick Start
Step by Step
1) In the administration menu, select System > Registration. The Registration
dialog opens.
2) Make sure that SIP server address and SIP registrar address contain the
IP address of your OpenScape Voice server. If not provided by DHCP or DLS,
enter the appropriate values. If the phone is to register with a gateway, enter
the appropriate SIP Gateway address.
3) In the Server type field, select "OS Voice".
4) In Realm, enter the SIP realm the targeted user/password combination refers
to. This setting depends on the configuration of the OpenScape Voice server.
5) In the User ID and Password fields, enter the user name/password combi-
nation for the phone. This setting depends on the configuration of the
OpenScape Voice server.
Related Topics
Page 34
Startup
A31003-D3000-M100-01-76A9, 02-2013
34 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Startup Procedure
2.4 Startup Procedure
The following flowchart shows the startup process for OpenScape phones:
Related Topics
Page 35
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 35
Startup
Cloud Deployment (V3 R1)
2.5 Cloud Deployment (V3 R1)
This chapter describes how a phone progresses through the cloud deployment
process from factory start-up until the cloud service provider considers it to be
ready for use by its user.
The phone determines that a cloud deployment process is to be used based on
the IP settings it receives from the DHCP at the customer site. The SEN Redirect
server
1
requires a code to determine which cloud service provider is responsible
for the phone. The code is provided as part of a pin supplied from the cloud organisation to the user. When the user enters the pin at the phone the SEN Redirect
server redirects the phone to a DLS-WPI based management system operated by
the cloud service provider. This management system completes the configuration
of the phone with all the information required for it to be usable and may also
customise the phone for the cloud service provider's 'house' style.
Related Topics
2.5.1 Process of Cloud Deployment
The following flow chart shows the way from a factory start-up to a user prepared
OpenScape Desk Phone, deployed by a relevant DLS-WPI based management
system.
Preconditions:
• Phone is not running
• Phone is set to factory default values
• The phone has a LAN connection
1. The address for the SEN Redirect server is hardcoded as "cloud-setup.com"
Page 36
Startup
A31003-D3000-M100-01-76A9, 02-2013
36 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Cloud Deployment (V3 R1)
• The LAN connection provides access to the public internet
Start
Phone broadcasts a DHCP request
A DHCP server responds with IP
addresses
The phone detects that a cloud
deployment is required
The phone has all the information that it needs to contact a DNS server.
A DLS address is not provided.
DHCP is available; IP address allocated to the phone;
DNS address is available; Subnet mask is available;
Router address is available; No DLS address available;
No SIP addresses available
The phone starts the cloud
deployment process
The phone is locked so that the mode keys & FPKs etc. cannot be used.
The phone obtains the IP address
of the SEN Redirect server
("cloud-setup.com") from the DNS
Phone displays the Progress
prompt
The phone gets the pin from the
user
The user enters the pin and presses OK.
The phone verifies that the pin is valid.
The user has the option to cancel the process (see chapter 2, “Aborting
Cloud Deployment process by User”.
Page 37
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 37
Startup
Cloud Deployment (V3 R1)
Phone contacts the SEN Redirect
server using DLS-WPI
Phone receives configuration
items from the SEN Redirect
server
• DLS address (set to the name of the Deployment server)
• Language optional)
• DLS port (optional)
Phone updates, and displays, the
Progress prompt
Phone saves the configuration data
If the language is changed, then the display is updated
The phone obtains the IP address
of the Deployment server from the
DNS by looking up the DLS
address if appropriate
The stored DLS address is not changed by the result of the DNS lookup
Phone contacts the Deployment
server using DLS-WPI
The hash of the pin is provided as an Inventory item to the Deployment
server
Deployment server configures the
phone and the phone saves the
changes
Deployment server terminates the
DLS-WPI session
Page 38
Startup
A31003-D3000-M100-01-76A9, 02-2013
38 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Cloud Deployment (V3 R1)
Related Topics
2.5.2 Aborting Cloud Deployment Process by User
The phone detects that a cloud deployment is required and starts the cloud
deployment process. The phone expects the input of the PIN by the user. At this
point the user has the option to cancel the process with Cancel. If the user
confirms his decision, the deployment process is aborted.
Related Topics
2.5.3 Re-trigger Cloud Deployment
Cloud deployment may be restarted by triggering a Factory reset:
The DLS-WPI requests a restart to factory defaults of the phone. The phone
restart should then trigger the cloud deployment process if the conditions in Cloud
Deployment are still met.
Related Topics
2.5.4 Deployment errors
During deployment the display will always show deployment specific information.
A persistent warning popup displays the information that will be shown in an idle
screen error after deployment failed.
The phone exits the cloud
deployment process and enables
the mode keys & FPKs etc. to act
as normal
Phone removes the Progress
prompt and displays a timed
success pop-up, indicating that the
cloud deployment is done
The phone verifies that it now has
an E.164 address
Registered
Page 39
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 39
Startup
Cloud Deployment (V3 R1)
Related Topics
Code Priority Cause
AU 1 Abandoned by user. Occurs when the pin prompt is dismissed.
RS 1 Unable to get the address for the SEN Redirect server. DNS lookup
failed.
RN 3 Unable to establish contact with SEN Redirect server – no reply.
RR 2 Unable to establish contact with SEN Redirect server – refused.
DS 1 Unable to get the address for the Deployment server. DNS lookup
failed.
DN 3 Unable to establish contact with Deployment server – no reply.
DR 2 Unable to establish contact with Deployment server – refused.
Page 40
Administration
A31003-D3000-M100-01-76A9, 02-2013
40 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Access via Local Phone
3 Administration
This chapter describes the configuration of every parameter available on the
OpenScape Desk Phones. For access via the local phone menu, see the subsequent description; for access via the web interface (WBM), please refer to How to
Access the Web Interface (WBM).
Related Topics
3.1 Access via Local Phone
Prerequisites
• The data entered in input fields is parsed and controlled by the phone.
Step by Step
1) Access the Administration Menu
Press the Settings, Up Arrow or 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 adminis-
trator password.
The default admin password is 123456. It is highly recommended to change
the password (see Password) after your first login.
For entering passwords with non-numeric characters, please consider the
following:
By default, password entry is in numeric mode. For changing the mode, press
the # key once or repeatedly, depending on the desired character. The # key
cycles through the input modes as follows:
(Abc) > (abc) > (123) > (HEX) > (ABC) > back to start.
Usable characters are 0-9 A-Z a-z .*#,?!’+-()@/:_
Page 41
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 41
Administration
Access via Local Phone
3) Navigate within the Administration Menu
Use the navigation keys to navigate and execute administrative actions in the
administration menu.
4) Select a parameter.
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.
5) Enter the parameter value.
For selecting numbers and characters, you can use special keys. See the
following table:
With the OpenScape Desk Phone IP 35G, use the keypad for entering
parameter values. Use the navigation keys to navigate and execute administrative actions in the Administration menu.
6) Save and exit the menu.
When you are done, select Save & exit and press the OK key.
Related Topics
Key Function
Switch to punctuation and special characters.
Toggle between lowercase characters, uppercase characters, and digits in the following order:
(Abc) > (abc) > (123) > (HEX) > (ABC) > back to start.
Press the OK key:
- Confirm entries
- Perform an action
Press the key
briefly:
- Scroll up
Press the key:
In Idle mode:
- Open idle menu
In lists and menus:
- Scroll down
Press the key:
- Scroll down
Hold down the key:
- Scroll to end of list
Page 42
Administration
A31003-D3000-M100-01-76A9, 02-2013
42 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
LAN Settings
3.2 LAN Settings
Related Topics
3.2.1 LAN Port Settings
The OpenScape Desk Phone IP 35G 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 Mb/s, 1000 Mb/s with OpenScape Desk Phone IP
35G) 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.
INFO: In the default configuration, the LAN port supports
automatic detection of cable configuration (pass through or
crossover cable) and will reconfigure itself as needed to connect
to the network.
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.
INFO: Removing the power from the phone, or a phone reset/
reboot will result in the temporary loss of the network connection
to the PC port.
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 switch. Value range: "Automatic," "10 Mbps half duplex", "10 Mbps full
duplex", "100 Mbps half duplex", "100 Mbps full duplex". Default: "Automatic"
• PC port speed / PC port type: Settings for the ethernet port connected to a
PC. Value range: "Automatic," "10 Mbps half duplex", "10 Mbps full duplex",
"100 Mbps half duplex", "100 Mbps full duplex". Default: "Automatic"
• PC port mode / PC port status: Controls the PC port. Value range: "disabled",
"enabled", "mirror". Default: "disabled"
• PC port autoMDIX: Switches between MDI and MDI-X automatically. Value
range: "On", "Off" Default: "Off"
Page 43
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 43
Administration
LAN Settings
Administration via WBM
Network > Port configuration
Administration via Local Phone
Related Topics
3.2.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.
INFO: The implementation of a voice network based on VLANs
requires the network infrastructure (the switch fabric) to support
VLANs.
|--- Admin
|--- Network
|--- Port Configuration
|--- LAN port type
|--- PC port status
|--- PC port type
|--- PC port autoMDIX
Page 44
Administration
A31003-D3000-M100-01-76A9, 02-2013
44 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
LAN Settings
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 VLANassigned 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.
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.
It is important that every switch connected to a PC is VLAN-capable. This is also
true for the integrated switch of the OpenScape Desk Phone. 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 of the phone port:
• By LLDP-MED
• By DHCP
• Manually
Related Topics
3.2.2.1 Automatic VLAN discovery using LLDP-MED
The VLAN ID can be configured by the network switch using LLDP-MED (Link
Layer Discovery Protocol-Media Endpoint Discovery). If this option is selected
then the switch has to provide an appropriate TLV (Type-Length-Value) element
containing the VLAN ID. If no appropriate TLV is received, DHCP will be used for
VLAN discovery.
Administration via WBM
Network > General IP configuration
Page 45
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 45
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 LLDP-MED, set the Use LLDP-MED option to Yes
and select LLDP-MED in the VLAN discovery option.
Related Topics
3.2.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
|--- Admin
|--- Network
|--- General IP configuration
|--- Protocol mode
|--- Use LLDP-MED
|--- Use DHCP
|--- Use DHCPv6
|--- VLAN discovery
|--- VLAN ID
Page 46
Administration
A31003-D3000-M100-01-76A9, 02-2013
46 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
LAN Settings
To enable VLAN discovery via DHCP, activate the DHCPv6 Enabled checkbox
and select DHCP 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.
Related Topics
3.2.2.3 Manual Configuration of a VLAN ID
To configure layer 2 VLAN manually, make sure that VLAN discovery is set to
Manual and LLDP-MED is disabled. Then, the phone must be provided with a
VLAN ID between 1 and 4095. If you mis-configure 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.
Administration via WBM
Network > General IP configuration
|--- Admin
|--- Network
|--- General IP configuration
|--- Protocol mode
|--- Use LLDP-MED
|--- Use DHCP
|--- Use DHCPv6
|--- VLAN discovery
|--- VLAN ID
Page 47
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 47
Administration
LAN Settings
The phone must be provided with a VLAN ID between 1 and 4095. Set the VLAN
discovery to Manual. Afterwards, click Submit.
Administration via Local Phone
To enable VLAN discovery via Manual operation, select Manual in the VLAN
discovery option.
Related Topics
3.2.3 LLDP-MED Operation
OpenScape Desk Phones support LLDP-MED (Link Layer Discovery ProtocolMedia Endpoint Discovery) for auto-configuration and network management. The
auto-configurable parameters are VLAN ID (see VLAN and Quality of Service
parameters (see Quality of Service (QoS)).
The data sent by a network device is stored in neighboring network devices in MIB
(Management Information Base) format. In order to keep this information up-todate, a specific TTL (Time To Live) is specified in LLDP. This value tells a device
how long the received information is valid. For OpenScape Desk Phones, the
value range is 40, 60, 80, 100, 110, 120, 140, 180, 240, 320, 400.
An example for LLDP-MED operation on OpenScape Desk Phones can be found
in An LLDP-Med Example.
|--- Admin
|--- Network
|--- General IP configuration
|--- Protocol mode
|--- Use LLDP-MED
|--- Use DHCP
|--- Use DHCPv6
|--- VLAN discovery
|--- VLAN ID
Page 48
Administration
A31003-D3000-M100-01-76A9, 02-2013
48 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
Administration via WBM
Network > LLDP-MED operation
Administration via Local Phone
Related Topics
3.3 IP Network Parameters
Related Topics
3.3.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.
INFO: Layer 2 and 3 QoS for voice transmission can be set via
LLDP-MED (see LLDP-MED). If so, the value can not be changed
by any other interface.
Related Topics
3.3.1.1 Layer 2 / IEEE 802.1p
QoS on layer 2 is using 3 Bits in the IEEE 802.1q/p 4-Byte VLAN tag which has
to be added in the Ethernet header.
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 (RTPstreams) by default. 3 is used for signaling by default.
|--- Admin
|--- Network
|--- LLDP-MED operation
|--- TTL
|--- TTL
Three Bits Used for CoS (User Priority)
PREAM. SFD DA SA TAG 4
Bytes
PT DATA FCS
Page 49
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 49
Administration
IP Network Parameters
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
Administration via WBM
Network > QoS
Administration via Local Phone
Related Topics
3.3.1.2 Layer 3 / Diffserv
Diffserv assigns a class of service to an IP packet by adding an entry in the IP
header.
|--- Admin
|--- Network
|--- QoS
|--- Service
|--- Layer 2
|--- Layer 2 voice
|--- Layer 2 signalling
|--- Layer 2 default
Page 50
Administration
A31003-D3000-M100-01-76A9, 02-2013
50 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
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 "0 0 0 0 0 0".
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 "1 0 1 1 1 0".
3. Assured Forwarding (AF referred to RFC 2597)
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"
Page 51
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 51
Administration
IP Network Parameters
Administration via WBM
Network > QoS
Administration via Local Phone
Related Topics
3.3.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
|--- Admin
|--- Network
|--- QoS
|--- Service
|--- Layer 3
|--- Layer 3 voice
|--- Layer 3 signalling
Page 52
Administration
A31003-D3000-M100-01-76A9, 02-2013
52 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
Set the Protocol Mode to IPv4 or IPv6 or both (the default setting is IPv4_IPv6).
Afterwards, click Submit.
Administration via Local Phone
Related Topics
3.3.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.
INFO: The phone is able to maintain its IP connection even in
case of DHCP server failure. For further information, please refer
to DHCP Resilience.
The following parameters can be obtained by DHCP:
Basic Configuration
• 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, Private/Classless Static Route (Microsoft) option 249)
• SNTP IP Address (NTP Server option 42)
|--- Admin
|--- Network
|--- General IP Configuration
|--- Protocol Mode
Page 53
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 53
Administration
IP Network Parameters
• 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)
• 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 - IPv4
or/and
Administration via WBM - IPv6
Network > General IP configuration
|--- Admin
|--- Network
|--- IPv4 configuration
Page 54
Administration
A31003-D3000-M100-01-76A9, 02-2013
54 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
Set DHCPv6 Enabled to selected (the default setting is Enabled). Afterwards,
click Submit.
Administration via Local Phone - IPv6
Related Topics
3.3.4 IP Address - Manual Configuration
Related Topics
3.3.4.1 How to Manually Configure the Phone´s IP Address
Prerequisites
• If not provided by DHCP dynamically, the phone’s IP address and subnet
mask must be specified manually.
INFO: 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:
Administration via WBM
|--- Admin
|--- Network
|--- IPv6 configuration
Page 55
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 55
Administration
IP Network Parameters
Step by Step
1) Navigate to Network > General IP Configuration. Set DHCP Enabled,
DHCPv6 Enabled and LLDP-MED Enabled to "not selected". Afterwards,
click Submit.
Page 56
Administration
A31003-D3000-M100-01-76A9, 02-2013
56 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
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.
3) After the phone’s network service has restarted, the other IP parameters can
be configured.
Administration via Local Phone
|--- Admin
|--- Network
General IP configuration
|--- Use LLDP-MED
|--- Use DHCP
|--- Use DHCPv6
Page 57
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 57
Administration
IP Network Parameters
Related Topics
3.3.5 Default Route/Gateway
If not provided by DHCP dynamically (see 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.
Administration via WBM - IPv4 Configuration
Network > 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.
|--- Admin
|--- Network
IPv4 configuration
|--- IP address
|--- Subnet mask
|--- Admin
|--- Network
IPv6 configuration
|--- Global address
|--- Global Prefix Len
Page 58
Administration
A31003-D3000-M100-01-76A9, 02-2013
58 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
Administration via Local Phone - IPv4 Configuration
Administration via WBM - IPv6 Configuration
Network > IPv6 configuration
Enter the IP address of the Global Gateway that links your IP network to other
networks. Afterwards, click Submit.
Administration via Local Phone - IPv6 Configuration
Related Topics
3.3.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.
|--- Admin
|--- Network
|--- IPv4 configuration
|--- Route (Default)
|
--- Admin
|--- Network
|--- IPv6 configuration
|--- Global Gateway
Page 59
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 59
Administration
IP Network Parameters
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
Network > 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 2Gateway, and Route 2 mask.
Click Submit.
Administration via Local Phone
IPv6 Route Configuration
Data required
• Route 1/2 destination: IPv6 address of the selected route.
|--- Admin
|--- Network
|--- IPv4 configuration
|--- Route 1 IP
|--- Route 1 gateway
|--- Route 1 mask
|--- Route 2 IP
|--- Route 2 gateway
|--- Route 2 mask
Page 60
Administration
A31003-D3000-M100-01-76A9, 02-2013
60 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
• 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
Network > 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.
Click Submit.
Administration via Local Phone
Related Topics
3.3.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,
it is necessary to configure the DNS domain the phone belongs to, as well as the
name servers needed for DNS resolving.
|--- Admin
|--- Network
|--- IPv6 configuration
|--- Route 1 dest
|--- Route 1 prefix len
|--- Route 1 gateway
|--- Route 2 dest
|--- Route 2 prefix len
|--- Route 2 gateway
Page 61
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 61
Administration
IP Network Parameters
Related Topics
3.3.7.1 DNS Domain Name
This is the name of the phone’s local domain.
Administration via WBM
Network > General IP configuration
Enter the DNS domain the phone belongs to. Afterwards, click Submit.
Administration via Local Phone
Related Topics
3.3.7.2 DNS Servers
If not provided by DHCP automatically, a primary and a secondary DNS server
can be configured.
INFO: 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 > General IP configuration
|--- Admin
|--- Network
|--- General IP configuration
|--- DNS domain
Page 62
Administration
A31003-D3000-M100-01-76A9, 02-2013
62 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
Enter the Primary DNS and Secondary DNS IP addresses for the primary and
the secondary DNS server. Afterwards, click Submit.
Administration via Local Phone
Related Topics
3.3.7.3 Terminal Hostname
INFO: DHCP and DNS must be appropriately connected and
configured at the customer site.
The phone’s hostname can be customised.
The corresponding DNS domain is configured in Network > General IP configuration > DNS domain (see 3.3.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.
INFO: It is recommended to inform the user about the DNS name
of his/her phone. If the corresponding infrastructure is available at
the customer site, 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 under the
WBM path Administration > System > System Identity > DNS name
construction. The following options are available:
• None.
|--- Admin
|--- Network
|--- General IP configuration
|--- Primary DNS
|--- Secondary DNS
Page 63
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 63
Administration
IP Network Parameters
• 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 string entered in Web name.
• Only number: The DNS name is set to the Terminal number, that is, the
phone’s call number (see Terminal and User Identity).
• Prefix number: The DNS name is constructed from the string entered in Web
name, followed by the Terminal number.
Administration via WBM
System > System Identity
Administration via Local Phone
Related Topics
3.3.8 Configuration & Update Service (DLS)
The Deployment Service (DLS) is an OpenScape Management application for
administering workpoints in communication 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 host name of the DLS server, and DLS 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.
The Security mode 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
|--- Admin
|--- System
|--- Identity
|--- Web name
|--- DDNS hostname
Page 64
Administration
A31003-D3000-M100-01-76A9, 02-2013
64 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
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.
INFO: 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 ContactMe 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.
INFO: The URI of the DCMP, as well as the polling interval, are
configured by the DLS. For this purpose, it is necessary that the
phone establishes a first contact to the DLS, e. g. by phone restart
or local configuration change.
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 documen-
tation.
Data required
• DLS address: IP address or host name of the server on which the
Deployment Service is running.
• DLS port: Port on which the DLS Deployment Service is listening. Default:
18443
• Contact gap: The parameter is not used.
• Security status: Shows whether the communication between the phone and
the DLS is secure. Value range: "Default", "Secure", "Secure PIN" This
parameter is read-only.
•Security PIN: Used for enhanced security.
Administration via WBM
Network > Update Service (DLS)
Page 65
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 65
Administration
IP Network Parameters
Administration via Local Phone
Related Topics
3.3.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 Phones support SNMPv1.
There are currently 4 trap categories that can be sent by the phones:
Standard SNMP Traps
OpenScape Desk 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
Customer Data Collection system (OpenScape Customer Data Collection (CDC)
or HiPath QoS Data Collection). 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 Phones
Currently, the following traps are defined:
TraceEventFatal: sent if severe trace events occur; aimed at expert users.
|--- Admin
|--- Network
|--- Update Service (DLS)
|--- DLS address
|--- DLS port
|--- Contact gap
|--- Security status
|--- Security PIN
Page 66
Administration
A31003-D3000-M100-01-76A9, 02-2013
66 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
IP Network Parameters
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 host name of the SNMP manager that
receives traps.
• Trap destination port: Port on which the SNMP manager is receiving TRAP
messages.
Default: 162
• 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 host name 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 / Diagnostic to generic device: 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"
Page 67
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 67
Administration
IP Network Parameters
Administration via WBM
System > SNMP
Administration via Local Phone
|--- Admin
|--- System
|--- SNMP
|--- Queries allowed
|--- Query password
|--- Trap sending enabled
|--- Trap destination
|--- Trap destination port
|--- Trap community
|--- Diag sending enabled
|--- Diag destination
|--- Diag destination port
|--- Diag community
|--- QoS traps to QCU
|--- QCU address
Page 68
Administration
A31003-D3000-M100-01-76A9, 02-2013
68 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Security
Related Topics
3.4 Security
Related Topics
3.4.1 Speech Encryption
Related Topics
3.4.1.1 Security - General Configuration
OpenScape Desk 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.
INFO: 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.
INFO: In order to use SRTP, the phone must be configured for
NTP (for further information 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.
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.
|--- QCU port
|--- QCU community
|--- QoS to generic dest.
Page 69
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 69
Administration
Security
When Use SRTCP is activated (together with Use secure calls), the phone will
use SRTCP (Secure RTCP) to transmit and receive RTP control packets.
INFO: 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
Related Topics
3.4.1.2 MIKEY Configuration
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 is
capable of receiving encrypted calls.
INFO: 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:
•MIKEY
• SDES (see SDES Configuration)
|--- Admin
|--- System
|--- Security
|--- Server cerfificate
|--- Use secure calls
|--- SRTP type
|--- Use SRTCP
Page 70
Administration
A31003-D3000-M100-01-76A9, 02-2013
70 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Security
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 (Secure RTCP) to transmit and receive RTP control packets.
INFO: 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
Related Topics
3.4.1.3 SDES Configuration
When SDES is selected as SRTP negotiation method (see Security - General
Configuration), it can be configured further.
The SDES status parameter enables or disables SDES, just like SRTP type in
System > Security > System (see Security - General Configuration). When SDES
is disabled, MIKEY will be used.
The SDP negotiation parameter specifies whether the use of SRTP will be forced
by the phone. The following choices are available:
|--- Admin
|--- System
|--- Security
|--- Server cerfificate
|--- Use secure calls
|--- SRTP type
|--- Use SRTCP
Page 71
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 71
Administration
Security
• 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.
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 > SDES config
Related Topics
3.4.2 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 terminal 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 72
Administration
A31003-D3000-M100-01-76A9, 02-2013
72 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Security
Administration via WBM
System > Security > Access control
Related Topics
3.4.3 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.
INFO: 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.
With Archive when at, the trigger for log archiving is set. 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 0%, every new entry will trigger a
save. The possible values are ”0%", "10%”, ”20%”, ”30%”, ”35%”, ”40%”, ”45%”,
”50%”, ”55%”, ”60%”, ”65%”, ”70%”, ”80%”, ”90%”.
Last archived shows the date when the security log was last archived to the DLS.
Administration via WBM
System > Security > Logging
Related Topics
Page 73
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 73
Administration
Security
3.4.4 Security-Related Faults
INFO: 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.
Security log entry shows the date and time of a loss of security log entries.
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
Related Topics
3.4.5 Password Policy
Related Topics
3.4.5.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 expire.
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.
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
Page 74
Administration
A31003-D3000-M100-01-76A9, 02-2013
74 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Security
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.
Administration via WBM
Security and Policies > Password > Generic Policy
Related Topics
3.4.5.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.
The Current status parameter 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
Related Topics
3.4.5.3 User Policy
Expiry date shows the date and time when the user password will expire.
Page 75
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 75
Administration
Security
Minimum length defines the minimum number of characters for the user
password.
Password history specifies the number of entries to be kept in the user
password history.
The Current status parameter determines the status for the user password.
When set to Active, the user password is available for use. With Suspended, the
user password is not available for a period or until reset. When set to Disabled,
all access via the user password is disabled.
Administration via WBM
Security and Policies > Password > User Policy
Related Topics
3.4.5.4 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. Value range: 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
Page 76
Administration
A31003-D3000-M100-01-76A9, 02-2013
76 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Security
Administration via WBM
Security and Policies > Password > Character set
Related Topics
3.4.5.5 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 Password).
Administration via WBM
Security and Policies > Password > Change Admin password
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
Page 77
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 77
Administration
Security
Related Topics
3.4.6 Certificate Policy
Related Topics
3.4.6.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).
When OCSP check is 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
Related Topics
3.4.6.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 Common FTP/HTTPS Settings).
|--- Admin password
|--- New password
| |--- Confirm password
Page 78
Administration
A31003-D3000-M100-01-76A9, 02-2013
78 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Secure send URL sets the authentication level for the server to which special
HTTP requests are sent on key press ("Send URL" function, see Send URL
Request via HTTP/HTTPS).
Secure SIP server sets the authentication level for the SIP server connected to
the phone (see SIP Registration).
Secure 802.1x server sets the authentication level for the 802.1x authentication
server.
Administration via WBM
Security and Policies > Certificates > Authentication policy
Administration via Local Phone
Related Topics
3.5 System Settings
Related Topics
3.5.1 Terminal and User Identity
Related Topics
3.5.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.
|--- Admin
|--- Security & policies
|--- Certificates
|--- Authentication policy
|--- Secure file transfer
|--- Secure send URL
Page 79
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 79
Administration
System Settings
Administration via WBM
System > System Identity
Administration via Local Phone
Related Topics
3.5.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.
Administration via WBM
System > System Identity
Administration via Local Phone
|--- Admin
|--- System
|--- Identity
|--- Terminal number
|--- Terminal name
|
--- Admin
|--- System
|--- Identity
|--- Display identity
|--- Enable ID
Page 80
Administration
A31003-D3000-M100-01-76A9, 02-2013
80 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Related Topics
3.5.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.
INFO: If more than one emergency number is needed, additional
numbers can be configured in the canonical dial settings
(Canonical Dialing Configuration).
If a mailbox located at a remote server shall be used, its Voice mail number must
be entered.
Administration via WBM
System > Features > Configuration
Page 81
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 81
Administration
System Settings
Administration via Local Phone
Related Topics
3.5.3 Call logging
This configuration item allows the phone to detect if a number dialed by the user
is likely to be a Feature Access Code (FAC) by comparing the start of the dialed
number with the configured FAC prefixes. If the dialed 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 dialed
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 dialed
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 the OpenScape Desk Phone IP
35G 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 dialing number for an OpenScape Desk Phone IP 35G 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.
Administration via WBM
Local functions > Call logging
Related Topics
3.5.3.1 Logging of Missed Calls Answered Elsewhere (via User menu)
This feature allows the user to
|--- Admin
|--- System
|--- Features
|--- Configuration
|--- General
|--- Emergency number
|--- Voicemail number
Page 82
Administration
A31003-D3000-M100-01-76A9, 02-2013
82 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
• 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 in the call log, OR
– excluded from the call log, i.e. not logged at all.
In the Call Lists, missed calls that were completed elsewhere are marked with a
check mark. For details, please refer to the User manual.
Administration via WBM (User menu)
User > Configuration > Call logging
Administration via Local Phone (User menu)
Include answered elsewhere: Calls completed elsewhere will be logged as
missed calls. In the call log these calls are marked with a check mark.
Exclude answered elsewhere: Calls completed elsewhere will not be visible on
phone; they will not be logged at all.
Related Topics
3.5.4 Date and Time
If 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 difference between the local time and 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, noninteger 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 automatic toggling, enable Auto time change;
|--- User
|--- Configuration
|--- Missed
|--- Include answered elsewhere
|--- Exclude answered elsewhere
Page 83
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 83
Administration
System Settings
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.
INFO: Please note that Difference (minutes) must be specified
both for manual and automatic DST toggling.
Related Topics
3.5.4.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"
Default setting is Yes . After a factory reset, the system will be reset to this
value.
• Difference (minutes): Time difference when daylight saving time is in effect.
Default setting is 60 (mins). After a factory reset, the system will be reset to
this value.
• 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.
• 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.
Page 84
Administration
A31003-D3000-M100-01-76A9, 02-2013
84 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Administration via WBM
Date and Time
Administration via Local Phone
Related Topics
3.5.4.2 No SNTP Server Available
If no SNTP server is available, date and time must be set manually.
INFO: The parameters for the manual setting of time and date are
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.
Administration via WBM
(User pages >) Date and time
|--- Admin
|--- Date and Time
|--- SNTP IP address
|--- Timezone offset
Page 85
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 85
Administration
System Settings
Administration via Local Phone
Related Topics
3.5.5 SIP Addresses and Ports
Related Topics
3.5.5.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 address 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.
INFO: Enhanced survivability using DNS SRV is available. To
make use of it, a special configuration is required. For details,
please refer to Resilience and Survivability.
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.
|--- User
|--- Date and Time
|--- Time
|--- Date
|--- Daylight saving
|--- Difference (mins)
Page 86
Administration
A31003-D3000-M100-01-76A9, 02-2013
86 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Administration via WBM
System > Registration
Administration via Local Phone
Related Topics
3.5.5.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 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.
|--- Admin
|--- System
|--- Registration
|--- SIP Addresses
|--- SIP server
|--- SIP registrar
|--- SIP gateway
Page 87
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 87
Administration
System Settings
• 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.
INFO: When changing the SIP Transport protocol from UDP/TCP
to TLS, the SIP ports 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
Administration via Local Phone
Related Topics
|--- Admin
|--- Network
|--- Port Configuration
|--- SIP server
|--- SIP registrar
|--- SIP gateway
|--- SIP local
Page 88
Administration
A31003-D3000-M100-01-76A9, 02-2013
88 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
3.5.6 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 Registration timer.
Unauthenticated Registration
For unauthenticated registration, the following parameters must be set on the
phone: Terminal number or Terminal name (see Terminal Identity), SIP server and
SIP registrar address (see 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 user names and passwords.
INFO: A challenge from the server for authentication information
is not only restricted to the REGISTER message, but can also
occur in response to other SIP messages, e. g. INVITE.
INFO: If registration has not succeeded at startup or registration
fails after having been previously successfully registered the
phone will try to re-register every 30 seconds. This is not configurable.
If the registration is not answered at all, the phone will try to reregister every 60 seconds by default. This is configurable (see
Maximum Registration Backoff Timer).
Data required
• Registration timer (seconds): Expiry time of the registration in seconds.
Default value: 3600.
•Server type: Type of server the phone will register to.
Value range: "Other", "OS Voice", "HiQ8000", "Genesys"
Default value: "OS Voice"
Page 89
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 89
Administration
System Settings
•Realm: Protection domain for authentication.
•User ID: User name required for an authenticated registration.
• Password: Password required for an authenticated registration.
Administration via WBM
System > Registration
Administration via Local Phone
Related Topics
|--- Admin
|--- System
|--- Registration
|--- SIP Session
|--- Registration timer
|--- Server type
|--- Realm
|--- User ID
|--- Password
Page 90
Administration
A31003-D3000-M100-01-76A9, 02-2013
90 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
3.5.7 SIP Communication
Related Topics
3.5.7.1 Outbound Proxy
If this option is set to "Yes", the phone routes outbound requests to the configured
proxy. The outbound proxy will fulfill the task of resolving the domain contained in
the SIP request. If "No" is set, the phone will attempt to resolve the domain by
itself.
If a Default OBP domain (Outbound Proxy checkbox) is set and the number or
name dialed by the user does not provide a domain, this value will be appended
to the name or number. Otherwise, the domain of the outbound proxy will be
appended.
Data required
• Outbound proxy: Determines whether an outbound proxy is used or not.
Value range: "Yes", "No"
Default: "Yes"; when System > Registration > Server type is set to "HiQ8000"
(firmware version V3 onwards): "Yes"
• Default OBP domain: Alternative value for the domain that is given in the
outbound request.
Administration via WBM
System > SIP interface
Administration via Local Phone
Related Topics
|--- Admin
|--- System
|--- SIP Interface
|--- Outbound proxy
|--- Default OBP domain
Page 91
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 91
Administration
System Settings
3.5.7.2 SIP Transport Protocol
Selects the transport protocol to be used for SIP messages. The values "UDP",
"TCP", and "TLS" are available. The default is "UDP"; Default when System >
Registration > Server type is set to "HiQ8000" (firmware version V3 onwards):
"TLS".
Administration via WBM
System > SIP interface
Administration via Local Phone
Related Topics
3.5.7.3 Media/SDP
OpenScape Desk Phones support IPv4/IPv6 media address negotiation in SDP
using ANAT (Alternative Network Address Types). ANAT allows for for the
expression of alternative network addresses (e. g., different IP versions) for a
particular media stream.
When Media negotation is set to "ANAT", ANAT is supported; the phone will reregister with the SIP server and advertise ANAT support in the SIP header. When
set to "Single IP", ANAT support is disabled.
INFO: If SRTP is enabled, ANAT interworking is only possible if
SDES is configured as the key exchange protocol for SRTP (see
Security - General Configuration).
|--- Admin
|--- System
|--- SIP Interface
|--- SIP transport
Page 92
Administration
A31003-D3000-M100-01-76A9, 02-2013
92 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Media IP mode defines which IP version is to be used for voice transmission.
With "IPv4", only IPv4 is used; with "IPv6", only IPv6 is used; with "IPv4_IPv6",
both IPv4 and IPv6 can be used, but IPv4 is preferred; with "IPv6_IPv4", both IPv6
and IPv4 can be used, but IPv6 is preferred.
Administration via WBM
System > SIP interface
Administration via Local Phone
Related Topics
3.5.8 SIP Session Timer
Session timers provide a basic keep-alive mechanism between 2 user agents or
phones. This mechanism can be useful to the endpoints concerned or for stateful
proxies to determine that a session is still alive. This is achieved by the phone
sending periodic re-INVITEs to keep the session alive. If no re-INVITE is received
before the interval passes, the session is considered terminated. Both phones are
supposed to terminate the call, and stateful proxies can remove any state for the
call.
This feature is sufficiently backward compatible such that only one end of a call
needs to implement the SIP extension for it to work.
|--- Admin
|--- System
|--- SIP Interface
|--- Media negotiation
|--- Media IP mode
Page 93
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 93
Administration
System Settings
The parameter Session timer enabled determines whether the mechanism shall
be used, and Session duration (seconds) sets the expiration time, and thus the
interval between refresh re-INVITEs.
INFO: Some server environments support their own mechanism
for auditing the health of a session. In these cases, the Session
timer must be deactivated. For OpenScape Voice, the Session
timer should be deactivated.
Data required
• Session timer enabled: Activates or deactivates the session timer
mechanism. Value range: "Yes", "No" Default value: "No"
• Session duration (seconds): Sets the expiration time for a SIP session.
Default: 3600
Administration via WBM
System > Registration
Page 94
Administration
A31003-D3000-M100-01-76A9, 02-2013
94 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Administration via Local Phone
Related Topics
3.5.9 Resilience and Survivability
To allow for stable operation even in case of network or server failure, OpenScape
Desk Phones have the capability of switching to a fallback system. The switchover is controlled by various configurable check and timeout intervals.
Survivability is achieved in two different ways:
1. DNS SRV can be used for enhanced survivability, either in a scenario with a
survivability proxy, or in a scenario with multiple primary SIP servers. The
DNS -server provides the phone with a prioritized list of SIP servers via DNS
SRV. The phone fetches this list periodically from the server, depending on
the TTL (time to live) specified for the DNS SRV records.
To enable DNS SRV requests from the phone, please make the following
settings:
• Specify the IP address of the DNS server that provides the server list via
DNS SRV. The web interface path is Network > IP configuration > Primary
DNS. For details, see DNS Servers.
• Enable the use of an outbound proxy for routing outbound requests. The
web interface path is System > SIP interface > Outbound proxy. For
details, see Outbound Proxy.
• Set the SIP gateway port to 0. The web interface path is Network > Port
configuration > SIP gateway.
If the SIP server is to be configured by DNS SRV, set the SIP server port
to 0. The web interface path is Network > Port configuration > SIP server.
The SIP server address is specified in System > Registration > SIP server
address. For details, see SIP Ports.
• As SIP gateway address, enter the DNS domain name for which the DNS
SRV records are valid. The web interface path is System > Registration >
SIP gateway address.
If the SIP server is to be configured by DNS SRV, set the mentioned
parameter to the DNS domain name for which the DNS SRV records are
valid. The SIP server address is specified in System > Registration > SIP
server address. For details, see SIP Addresses.
A survivability proxy acts as a relay between the phone and the primary SIP
server. Thus, the address of the survivability proxy is specified as gateway or
SIP server at the phone (see SIP Registration). When the TLS connection
|--- Admin
|--- System
|--- Registration
|--- SIP session
|--- Session timer
|--- Session duration
Page 95
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 95
Administration
System Settings
between the survivability proxy and the SIP server breaks down, e. g.
because of server failure, the survivable proxy itself acts as a replacement for
the primary SIP server. Vice versa, in case the phone can not reach the
survivability proxy itself, it will register directly with the primary SIP server,
provided that it is specified in the DNS SRV server list.
The survivability proxy notifies the phone whenever the survivability changes,
so it can indicate possible feature limitations to the user. Furthermore, to
enhance survivability, the phone will be kept up-to-date about the current
survivability state even after a restart.
Another way to realize survivability is the use of multiple, geographically
separated SIP servers. Normally, the phone is registered with that server that
has the highest priority in the DNS SRV server list. If the highest priority server
fails to respond to the TLS connectivity check (see Connectivity Check), the
phone will register with the server that has the second highest priority.
2. Use of a Backup SIP Server. Along with the registration at the primary SIP
server, the phone is registered with a backup SIP server. In normal operation,
the phone uses the primary server for outgoing calls. If the phone detects that
the connection to the primary SIP server is lost, it uses the backup server for
outgoing calls. This connection check is realized by 2 timers; for details, see
Response Timer and Non-INVITE Transaction Timer. For configuring the
backup server, please refer to Backup SIP Server.
INFO: In survivability mode, some features will presumably not
be available. The user will be informed by a message in the Call
View display.
Related Topics
3.5.9.1 Connectivity Check
A regular check ensures that the TLS link to the main SIP server is active. When
the Connectivity check timer is set to a non-zero value, test messages will be
sent at the defined interval. If the link is found to be dead, the phone uses DNS
SRV to find another SIP server. Certainly, the DNS SRV records must be properly
configured in the DNS server.
Value range: 0 (off), and 10 to 3600 sec.
If no other primary SIP server is found via DNS SRV, the phone will switch over
to a backup server for making receiving calls. For configuring the backup server,
please refer to Backup SIP Server.
Page 96
Administration
A31003-D3000-M100-01-76A9, 02-2013
96 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
Administration via WBM
System > SIP interface
Related Topics
3.5.9.2 Response Timer
The Response Timer resp. Call trans. timer is started whenever the phone
sends a new INVITE message to the SIP server.
If the call transaction timer expires before the phone gets a response from the SIP
server, the phone assumes that the server had died and then attempts to contact
the backup server, if configured. If there is no backup server configured, the
phone just tidies up internally.
The data is given in milliseconds. The default value is 32 000; for OpenScape
Voice, the recommended setting is 3.7 seconds (3700 ms).
Administration via WBM
System > SIP interface
Page 97
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 97
Administration
System Settings
Administration via Local Phone
Related Topics
3.5.9.3 Non-INVITE Transaction Timer
The NonCall trans. timer is started whenever the phone sends a non-INVITE
message to the SIP server. If the timer expires before the phone gets a response
from the SIP server, the phone assumes that the server had died and then
attempts to contact the backup server, if configured. If no backup server is
configured, the phone will just tidy up internally.
The data is given in milliseconds. The default value is 32000; for OpenScape
Voice, the recommended setting is 6 seconds (6000 ms).
Administration via WBM
System > SIP interface
Administration via Local Phone
Related Topics
|--- Admin
|--- System
|--- SIP Interface
|--- Call trans. (ms)
|
--- Admin
|--- System
|--- SIP Interface
|--- NonCall transactions (ms)
Page 98
Administration
A31003-D3000-M100-01-76A9, 02-2013
98 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
System Settings
3.5.9.4 Maximum Registration Backoff Timer
If a registration attempt should result in a timeout, the phone waits a random time
before sending another REGISTER message. The Reg. backoff (seconds)
parameter determines the maximum waiting time.
Administration via WBM
System > SIP interface
Administration via Local Phone
Related Topics
3.5.9.5 Backup SIP Server
The Backup registration allowed flag indicates whether or not the phone treats
the backup proxy server as a SIP registrar. If set to "Yes", the phone tries to
register its SIP address with the server whose IP address or hostname is
specified by Backup proxy address. Once an IP address has been entered, the
SIP-UDP Port is opened, even if SIP-TLS is used for the OS Voice connection.
The Backup registration timer determines the duration of a registration with the
backup SIP server.
The Backup transport option displays the current transport protocol used to
carry SIP messages to the Backup proxy server.
The Backup OBP flag indicates whether or not the Backup proxy server is used
as an outbound proxy.
|--- Admin
|--- System
|--- SIP Interface
|--- Reg. backoff
Page 99
A31003-D3000-M100-01-76A9, 02-2013
OpenScape Desk Phone IP, Phone Administration, Administrator Documentation 99
Administration
System Settings
Data required
• Backup registration allowed / Backup registration flag: Determines
whether or not the backup proxy is used as a SIP Registrar.
Value Range: "Yes", "No"
Default: "Yes"
• Backup proxy address: IP address or hostname of the backup proxy server.
• Backup registration timer: Expiry time of the registration in seconds.
Default: 3600
• Backup transport: Transport protocol to be used for messages to the backup
proxy.
Value range: "TCP", "UDP"
Default: "UDP"
• Backup OBP flag: Determines whether or not the backup proxy is used as
an outbound proxy.
Value range: "Yes", "No"
Default: "No"
• Network > Port Configuration > Backup proxy: Port of the backup proxy
server.
Default: 5060
Administration via WBM
System > Registration
Page 100
Administration
A31003-D3000-M100-01-76A9, 02-2013
100 OpenScape Desk Phone IP, Phone Administration, Administrator Documentation
Feature Access
Network > Port configuration
Administration via Local Phone
Related Topics
3.6 Feature Access
Certain OpenScape Desk Phone features and interfaces can be enabled or
disabled:
• Blind Transfer (see Blind Call Transfer)
• 3rd Call Leg (consultation from a second call; see User Manual)
• Callback Busy (see Callback and Callback URIs)
• Callback on No Reply (see Callback and Callback URIs)
|--- Admin
|--- System
|--- Registration
|--- SIP Session
|--- SIP Survivability
|--- Backup registration flag
|--- Backup proxy address
|--- Backup transport
|--- OBP flag
|
--- Admin
|--- Network
|--- Port Configuration
|--- Backup proxy
Loading...