Unify OpenStage 60, OpenStage 80, OpenStage 20, OpenStage 40, OpenStage 15 Administration Manual
Page 1
OpenStage SIP V3R3 for OpenScape Voice
Administration Manual
A31003-S2030-M100-11-76A9
Page 2
Our Quality and Environmental Management Systems are
implemented according to the requirements of the ISO9001 and
ISO14001 standards and are certified by an external certification
company.
Copyright © Unify GmbH & Co. KG 01/2015
Hofmannstr. 63, 81379 Muni ch/Germany
All rights reserved.
Reference No.: A31003-S2030-M100-11-7 6A9
The information provided in this document contains merely general descriptions or
characteristics of performance which in case of actual use do not always apply as
described or which may change as a result of further development of the products.
An obligation to provi de the respective chara cteristics shall onl y exist if expressly agreed in
the terms of contract.
Availability and technical specifications are subject to change without notice.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify GmbH & Co. KG.
All other company, brand, product and service names are trademarks or registered trademarks
of their respective holders.
unify.com
Page 3
bkTOC.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
3
Nur für den internen Gebrauch Content
Content 0
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.1 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.2 Maintenance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.3 About the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.4 Conventions for this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.5 The OpenStage Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
1.5.1 OpenStage 60/80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
1.5.2 OpenStage 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
1.5.3 OpenStage 40 US . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.5.4 OpenStage 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.5.5 OpenStage 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
1.6 Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.6.1 Web-based Management (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.6.2 DLS (Deployment Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.6.3 Local Phone Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
2 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
2.2 Assembling and Installing the Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
2.2.1 Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
2.2.2 Connectors at the bottom side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
2.2.3 Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
2.2.4 Connecting the Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
2.3 Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
2.3.1 Accessing the Web Interface (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
2.3.2 Set the Terminal Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
2.3.3 Basic Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
2.3.4 DHCP Resilience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
2.3.5 Date and Time / SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
2.3.6 SIP Server Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
2.3.7 Extended Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
2.3.8 Vendor Specific: VLAN Discovery And DLS Address . . . . . . . . . . . . . . . . . . . . . 1-28
2.3.8.1 Using a Vendor Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
2.3.8.2 Using Option #43 "Vendor Specific" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
2.3.9 Registering at Phone Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
2.4 Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Page 4
Content Nur für den internen Gebrauch
A31003-S2030-M100-11-76A9, 01/2015
4 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
bkTOC.fm
2.5 Cloud Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
2.5.1 Process of Cloud Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
2.5.2 Aborting cloud deployment process by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
2.5.3 Re-trigger cloud deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
2.5.4 Deployment errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
3 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
3.1 Access via Local Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
3.2 LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
3.2.1 LAN Port Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
3.2.2 VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55
3.2.2.1 Automatic VLAN discovery using LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . 1-56
3.2.2.2 Automatic VLAN discovery using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
3.2.2.3 Manual configuration of a VLAN ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
3.2.3 LLDP-MED Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
3.3 IP Network Parameters . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
3.3.1 Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
3.3.1.1 Layer 2 / 802.1p. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
3.3.1.2 Layer 3 / Diffserv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
3.3.2 Protocol Mode IPv4/IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
3.3.3 Use DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65
3.3.4 IP Address - Manual Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
3.3.4.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
3.3.5 Default Route/Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
3.3.6 Specific IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72
3.3.7 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74
3.3.7.1 DNS Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74
3.3.7.2 DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-75
3.3.7.3 Terminal Hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76
3.3.8 Configuration & Update Service (DLS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77
3.3.9 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-79
3.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
3.4.1 Speech Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
3.4.1.1 General Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
3.4.1.2 MIKEY Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83
3.4.1.3 SDES Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85
3.4.2 Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-86
3.4.3 Security Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87
3.4.4 Security-Related Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-88
3.4.5 Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
3.4.5.1 General Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
3.4.5.2 Admin Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-90
3.4.5.3 User Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91
Page 5
bkTOC.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
5
Nur für den internen Gebrauch Content
3.4.5.4 Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91
3.4.5.5 Change Admin and User password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-92
3.4.6 Certificate Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-93
3.4.6.1 Online Certificate Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-93
3.4.6.2 Server Authentication Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-94
3.5 System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-95
3.5.1 Terminal and User Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-95
3.5.1.1 Terminal Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-95
3.5.1.2 Display Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-95
3.5.2 Emergency and Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-97
3.5.3 Energy Saving (OpenStage 40/60/80) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-98
3.5.4 Call logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-99
3.5.4.1 Logging of Missed Calls Answered Elsewhere (via User menu) . . . . . . . . 1-100
3.5.5 Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-102
3.5.5.1 SNTP is Available, but no Automatic Configuration by DHCP server. . . . . 1-102
3.5.5.2 No SNTP Server Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-104
3.5.6 SIP Addresses and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-105
3.5.6.1 SIP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-105
3.5.6.2 SIP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-107
3.5.7 SIP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
3.5.8 SIP Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-110
3.5.8.1 Outbound Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-110
3.5.8.2 SIP Transport Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111
3.5.8.3 Media/SDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-112
3.5.9 SIP Session Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-113
3.5.10 Resilience and Survivability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-115
3.5.10.1 TLS Connectivity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-116
3.5.10.2 Response Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-117
3.5.10.3 Non-INVITE Transaction Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-118
3.5.10.4 Maximum Registration Backoff Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-119
3.5.10.5 Backup SIP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-120
3.6 Feature Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-123
3.7 Feature Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-126
3.7.1 Allow Refuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-126
3.7.2 Hot/Warm Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-128
3.7.3 Initial Digit Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-130
3.7.4 Group Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-131
3.7.4.1 Feature Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-131
3.7.4.2 Pickup alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-131
3.7.5 Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-135
3.7.5.1 Transfer on Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-135
3.7.5.2 Transfer on Hangup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-135
3.7.6 Callback URIs . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-137
3.7.6.1 Call Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-138
Page 6
Content Nur für den internen Gebrauch
A31003-S2030-M100-11-76A9, 01/2015
6 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
bkTOC.fm
3.7.7 Message Waiting Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-139
3.7.8 Indicate Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-140
3.7.9 System Based Conference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-142
3.7.10 Server Based Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-143
3.7.11 uaCSTA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-145
3.7.12 Local Menu Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-147
3.7.13 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-148
3.8 Free Programmable Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-150
3.8.1 Clear (no feature assigned) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-151
3.8.2 Selected Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-151
3.8.3 Repeat Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-152
3.8.4 Call Forwarding (Standard) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-152
3.8.5 Call Forwarding by Call Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-153
3.8.6 Ringer Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-155
3.8.7 Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-155
3.8.8 Alternate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-155
3.8.9 Blind Call Transfer / Move Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-156
3.8.10 Join Two CallsTransfer Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-156
3.8.11 Deflect a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-157
3.8.12 Shift Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-157
3.8.13 Phone-Based Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-157
3.8.14 Accept Call via Headset (OpenStage 40/60/80). . . . . . . . . . . . . . . . . . . . . . . . 1-158
3.8.15 Do Not Disturb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-158
3.8.16 Group Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-159
3.8.17 Repertory Dial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-159
3.8.18 Hunt Group: Send Busy Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-160
3.8.19 Mobile User Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-160
3.8.20 Directed Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-161
3.8.21 Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-161
3.8.22 Cancel Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-162
3.8.23 Consultation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-162
3.8.24 Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-162
3.8.25 Call recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-163
3.8.26 Auto Answer With Zip Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-164
3.8.27 Server Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-164
3.8.28 BLF Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-164
3.8.29 Start Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-165
3.8.30 Send Request via HTTP/HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-165
3.8.31 Built-in Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-168
3.8.32 2nd Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-168
Page 7
bkTOC.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
7
Nur für den internen Gebrauch Content
3.8.33 Start Phonebook (OpenStage 40/15 only starting with V2R1) . . . . . . . . . . . . 1-168
3.8.34 Show phone screen (OpenStage 15 and OpenStage 40 only) . . . . . . . . . . . . 1-169
3.8.35 Mute (OpenStage 15 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-169
3.8.36 Release (OpenStage 15 only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-169
3.9 Preset Function Keys (OpenStage 40 US only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-170
3.10 Fixed Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-170
3.10.1 Fixed Function Keys on OpenStage 40 US. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-170
3.11 Multiline Appearance/Keyset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-171
3.11.1 Line key configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-171
3.11.2 Configure Keyset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-177
3.11.3 Line Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-183
3.11.3.1 Preview and Preselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-184
3.11.4 Immediate Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-185
3.11.5 Direct Station Select (DSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-185
3.11.5.1 General DSS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-186
3.11.5.2 Settings for a DSS key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-187
3.11.6 Distinctive Ringers per Keyset Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-189
3.12 Key Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-192
3.13 Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-194
3.13.1 Canonical Dialing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-194
3.13.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-198
3.13.3 Phone location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-200
3.13.4 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-201
3.14 Distinctive RingingRinger Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-204
3.14.1 Distinctive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-204
3.14.2 Map to Specials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-206
3.14.3 Special Ringers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-207
3.15 Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-210
3.16 Transferring Phone Software, Application, and Media Files . . . . . . . . . . . . . . . . . 1-212
3.16.1 FTP/HTTPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-212
3.16.2 Common FTP/HTTPS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-212
3.16.3 Phone Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-214
3.16.3.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-214
3.16.3.2 Download/Update Phone Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-217
3.16.4 Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-218
3.16.4.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-218
3.16.4.2 Download Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-220
3.16.5 Picture Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-221
3.16.5.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-221
3.16.5.2 Download Picture Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-223
3.16.6 LDAP Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-224
3.16.6.1 FTP/HTTPS Access Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-224
3.16.6.2 Download LDAP Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-226
Page 8
Content Nur für den internen Gebrauch
A31003-S2030-M100-11-76A9, 01/2015
8 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
bkTOC.fm
3.16.7 Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-227
3.16.7.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-227
3.16.7.2 Download Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-229
3.16.8 Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-230
3.16.8.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-230
3.16.8.2 Download Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-232
3.16.9 Ringer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-233
3.16.9.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-234
3.16.9.2 Download Ringer File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-236
3.16.10 Dongle Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-237
3.16.10.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-237
3.16.10.2 Download Dongle Key File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-239
3.17 Corporate Phonebook: Directory Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-240
3.17.1 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-240
3.18 Speech . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-242
3.18.1 RTP Base Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-242
3.18.2 Codec Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-243
3.18.3 Audio Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-245
3.19 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-246
3.19.1 XML Applications/Xpressions (OpenStage 60/80) . . . . . . . . . . . . . . . . . . . . . . 1-246
3.19.1.1 Setup/Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-246
3.19.1.2 HTTP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-252
3.19.1.3 Modify an Existing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-254
3.19.1.4 Remove an Existing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-255
3.19.1.5 Application Start by Programmable Key . . . . . . . . . . . . . . . . . . . . . . . . . . 1-255
3.20 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-256
3.21 Troubleshooting: Lost Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-257
3.22 Restart Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-257
3.23 Factory Reset . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-257
3.24 SSH – Secure Shell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-258
3.25 Display License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-259
3.26 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-260
3.26.1 Display General Phone Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-260
3.26.2 View Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-261
3.26.3 User Access to Diagnostic Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-263
3.26.4 Diagnostic Call (V3R1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-263
3.26.5 LAN Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-265
3.26.6 LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-266
3.26.7 IP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-268
3.26.8 Process and Memory Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-269
3.26.9 Fault Trace Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-271
3.26.10 EasyTrace Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-278
3.26.10.1 Bluetooth Handsfree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-278
Page 9
bkTOC.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
9
Nur für den internen Gebrauch Content
3.26.10.2 Bluetooth Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-279
3.26.10.3 Call Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-279
3.26.10.4 Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-280
3.26.10.5 Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-280
3.26.10.6 DAS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-281
3.26.10.7 DLS Data Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-281
3.26.10.8 Help Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-282
3.26.10.9 Key Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-282
3.26.10.10 LAN Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-283
3.26.10.11 Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-283
3.26.10.12 Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-284
3.26.10.13 Phone administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-284
3.26.10.14 LDAP Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-285
3.26.10.15 Local Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-285
3.26.10.16 Server based applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-286
3.26.10.17 Sidecar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-286
3.26.10.18 SIP standard multiline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-287
3.26.10.19 SIP standard singleline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-287
3.26.10.20 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-288
3.26.10.21 Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-288
3.26.10.22 USB Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-289
3.26.10.23 Voice Dialling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-289
3.26.10.24 Web Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-290
3.26.10.25 802.1x problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-290
3.26.10.26 No Tracing for All Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-291
3.26.11 Bluetooth Advanced Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-292
3.26.12 QoS Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-293
3.26.12.1 Conditions and Thresholds for Report Generation . . . . . . . . . . . . . . . . . 1-293
3.26.12.2 View Report . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 1-296
3.26.13 Core dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-300
3.26.14 Remote Tracing – Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-301
3.26.15 HPT Interface (For Service Staff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-302
3.27 Bluetooth (OpenStage 60/80) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-303
3.28 MWI LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-305
3.29 Missed Call LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-307
Page 10
Content Nur für den internen Gebrauch
A31003-S2030-M100-11-76A9, 01/2015
10 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
bkTOC.fm
3.30 Impact Level Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-308
4 Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-311
4.1 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-311
4.1.1 Web Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-311
4.1.1.1 Menu Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-311
4.1.1.2 Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-315
4.1.2 Local Phone Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-361
4.2 Default Port List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-373
4.3 Troubleshooting: Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-375
5 Examples and HowTos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-377
5.1 Canonical Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-377
5.1.1 Canonical Dialing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-377
5.1.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-378
5.1.2.1 Conversion examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-379
5.2 How to Create Logo Files for OpenStage Phones . . . . . . . . . . . . . . . . . . . . . . . . . . 1-381
5.2.1 For OpenStage 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-381
5.2.2 For OpenStage 60/80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-382
5.3 How to Set Up the Corporate Phonebook (LDAP) . . . . . . . . . . . . . . . . . . . . . . . . . . 1-385
5.3.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-385
5.3.2 Create an LDAP Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-386
5.3.3 Load the LDAP Template onto the Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-390
5.3.4 Configure LDAP Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-391
5.3.5 Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-391
5.4 An LLDP-Med Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-394
5.5 Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-396
5.5.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-396
5.5.2 Dial Plan Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-396
5.5.3 How To Set Up And Deploy A Dial Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-398
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-401
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-408
Page 11
uebersicht.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
11
Overview
Important Notes
1Overview
1.1 Important Notes
Do not operate the equipment in environments where there is a danger of explosions.
For safety reasons the phone should only be operating using the supplied plug in power unit.
Use only original accessories. The use of other accessories may be hazardous and
will render the warranty, extended manufacturer’s liability and the CE marking invalid.
Never open the telephone or add-on equipment. If you encounter any problems, contact System Support.
Installation requirement for USA, Canada, Norway, Finland and Sweden: Connection
to networks which use outside cables is prohibited. Only in-house networks are permitted.
7
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.
7
7
7
7
Page 12
Overview
A31003-S2030-M100-11-76A9, 01/2015
12 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
uebersicht.fm
Maintenance Notes
1.2 Maintenance Notes
1.3 About the Manual
The instructions within this manual will help you in administering and maintaining the OpenStage 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 OpenStage phone and who have a fundamental understanding of VoIP, SIP,
and IP networking. The tasks described in this guide are not intended for end users. Many of
these tasks affect the ability of a phone to function on the network and require an understanding
of IP networking and telephony concepts.
These instructions are laid out in a user-oriented manner, which means that you are led through
the functions of the OpenStage phone step by step, wherever expedient. For the users, a separate manual is provided.
You can find further information on the official Unify website (http://www.unify.com/.)
and on the Unify Wiki (http://wiki.unify.com/.
).
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. All WBM screenshots are taken from OpenStage 60/80. As some
WBM input masks have been changed with firmware updates, the screenshots are selected after the following rules:
• If a later version contains more or less parameters compared to previous software versions, the screenshot of the older version is shown.
Do not operate 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 a key module. If you encounter any problems, contact
System Support.
7
7
7
Page 13
uebersicht.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
13
Overview
Conventions for this Document
• If the title of a mask (e.g. "Pixel saver" vs. "Energy saving") or the name of a parameter
(e.g. "Time Zone" vs. "DST zone") has changed, the later version is shown.
• If a parameter has moved from one mask to another, both older and later versions are
shown. The same is true for the local menu paths.
This document describes the software version V3R3.
Page 14
Overview
A31003-S2030-M100-11-76A9, 01/2015
14 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
uebersicht.fm
The OpenStage Family
1.5 The OpenStage Family
1.5.1 OpenStage 60/80
1 With the handset, the user can pick up and dial calls in the usual manner.
2 The graphic display provides intuitive support for telephone operation.
3 The mode keys provide easy access to the phone’s applications.
4 With the TouchGuide, the user/administrator can navigate in the phone func-
tions, applications, and configuration menus.
5 The free programmable keys enable the user to customize the telephone in
line with his/her personal needs by assigning individual phone numbers and
functions.
6 The fixed function keys provide access to frequently used telephony func-
tions.
7 With the audio keys, the user can control the audio settings.
8 With the TouchSlider, the user can adjust the volume, e.g. of ringtones.
9 Inbound calls are visually signaled via the alert bar.
10 The keypad is used for entering phone numbers and text.
Tabelle 1-1
2
7
1
1
4
6
5
9
3
8
Page 15
uebersicht.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
15
Overview
The OpenStage Family
1.5.2 OpenStage 40
1With the handset, the user can pick up and dial calls in the usual manner.
2The graphic display provides intuitive support for telephone operation.
3The fixed function keys provide access to frequently used telephony func-
tions.
4 With the 5-way navigator, the user/administrator can navigate in the various
phone functions, applications, and configuration menus.
5The free programmable keys enable the user to customize the telephone in
line with his/her personal needs by assigning individual phone numbers and
functions.
6With the audio keys, the user can control the audio settings.
7 Inbound calls are visually signaled via the alert bar.
8The keypad is used for entering phone numbers and text.
Tabelle 1-2
1
2
3
4
5
6
7
8
Page 16
Overview
A31003-S2030-M100-11-76A9, 01/2015
16 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
uebersicht.fm
The OpenStage Family
1.5.3 OpenStage 40 US
1 With the handset, the user can pick up and dial calls in the usual manner.
2 The graphic display provides intuitive support for telephone operation.
3 The fixed function keys provide access to frequently used telephony func-
tions.
4 With the 5-way navigator, the user/administrator can navigate in the various
phone functions, applications, and configuration menus.
5 The OpenStage 40 US telephone comes with six programmable lit sensor
keys, preset to the following factory settings:
•Shift
• Phonebook
• Group pickup
• Call Forward
• DND
• Show phone
The user can customize the telephone with his/her personal needs by assigning individual phone numbers and functions. After a factory reset, the system
will be reset to these values.
6 With the audio keys, the user can control the audio settings.
7 Inbound calls are visually signaled via the alert bar.
8 The keypad is used for entering phone numbers and text.
Tabelle 1-3
1
2
3
4
5
6
7
8
1
Page 17
uebersicht.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
17
Overview
The OpenStage Family
1.5.4 OpenStage 20
1With the handset, the user can pick up and dial calls in the usual manner.
2The display provides intuitive support for telephone operation.
3The fixed function keys provide access to frequently used telephony func-
tions.
4With the audio keys, the user can control the audio settings.
5 With the 3-way navigator, the user/administrator can navigate in the various
phone functions, applications, and configuration menus.
6The keypad is used for entering phone numbers and text.
Tabelle 1-4
1
3
2
4
5
6
Page 18
Overview
A31003-S2030-M100-11-76A9, 01/2015
18 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
uebersicht.fm
The OpenStage Family
1.5.5 OpenStage 15
1 With the handset, the user can pick up and dial calls in the usual manner.
2 The display provides intuitive support for telephone operation.
3 With the audio keys, the user can control the audio settings.
4 The fixed function keys provide access to frequently used telephony func-
tions.
5 The keypad is used for entering phone numbers and text.
6 With the navigation keys, the user/administrator can navigate in the various
phone functions, applications, and configuration menus.
7 The free programmable keys enable the user to customize the telephone in
line with his/her personal needs by assigning individual phone numbers and
functions.
Tabelle 1-5
7
1
5
3
4
2
6
7
Page 19
uebersicht.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
19
Overview
Administration Interfaces
1.6 Administration Interfaces
You can configure the OpenStage phone by using any of the methods described in this chapter.
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.
1.6.2 DLS (Deployment Service)
The Deployment Service (DLS) is an OpenScape Management application for administering
phones and soft clients in communication networks. It has a Java-supported, web-based user
interface, which runs on an internet browser. For further information, please refer to the Deployment Service Administration Guide.
1.6.3 Local Phone Menu
This method provides direct configuration of the OpenStage phone. Direct access to the phone
is required.
>
To use this method, the phone must first obtain IP connectivity.
>
As long as the IP connection is not properly configured, you have to use this method
to set up the phone.
Page 20
Startup
A31003-S2030-M100-11-76A9, 01/2015
20 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Prerequisites
2Startup
2.1 Prerequisites
The OpenStage 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.
• Phone Administration server.
• An FTP Server for file transfer, e. g. firmware, configuration data, application software.
• A DHCP (Dynamic Host Configuration Protocol) server (recommended).
• DLS (Deployment Service) for advanced configuration and software deployment (recommended).
For additional information see: http://wiki.unify.com/wiki/IEEE_802.1x.
7
Only use switches in the LAN to which the OpenStage phone is connected. An
operation at hubs can cause serious malfunctions in the hub and in the whole
network.
Page 21
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
21
Startup
Assembling and Installing the Phone
2.2 Assembling and Installing the Phone
2.2.1 Shipment
• Phone
• Handset
• Handset cable
• Document "Information and Important Operating Procedures"
2.2.2 Connectors at the bottom side
OpenStage 60
PC
Switch
Headset
Handset
Power supply
Key Module
USB
Stick
Page 22
Startup
A31003-S2030-M100-11-76A9, 01/2015
22 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Assembling and Installing the Phone
OpenStage 40 (OpenStage 15 and 20 similar, except 1)
2.2.3 Assembly
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.2.4 Connecting the Phone
1. Plug the LAN cable into the connector at the bottom of the telephone and connect the
cable to the LAN resp. switch. If PoE (Power over Ethernet) is to be used, the PSE (Power
Sourcing Equipment) must meet the IEEE 802.3af specification.
For details about the required power supply, see the following table:
Model Power Consumption/Supply
OpenStage 15
1
Power Class 1
OpenStage 15 G
1
Power Class 2
OpenStage 20 E Power Class 1
OpenStage 20 Power Class 1
OpenStage 20 G Power Class 2
OpenStage 402, OpenStage 40 US
2
Power Class 2
PC
Switch
Headset
[1]
Handset
Power supply
Key Module
[1]
[1] OpenStage 40 andd
Page 23
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
23
Startup
Assembling and Installing the Phone
2. Only if Power over Ethernet (PoE) is NOT supported:
Plug the power supply unit into the mains. Connect the plug-in power supply unit to the
jack at the bottom of the phone.
OpenStage 40 + 2nd Key Module Power Class 2
OpenStage 40 G2,OpenStage 40 G US
2
Power Class 3
OpenStage 40 G or OpenStage 40 G US + 2nd Key
Module
Power Class 3
OpenStage 60/80
3
Power Class 3
OpenStage 60/80 + 2nd Key Module Power Class 3
OpenStage 60/80 G
3
Power Class 3
OpenStage 60/80 G + 2nd Key Module External power unit required
1 Includes 1 Key Module 15.
2 Includes 1 Key Module.
3 Includes 1 Key Module + USB-Extension with Acoustic Unit.
7
The order no. for the plug-in power supply is region specific:
EU: C39280-Z4-C510
UK: C39280-Z4-C512
USA: C39280-Z4-C511
Model Power Consumption/Supply
Page 24
Startup
A31003-S2030-M100-11-76A9, 01/2015
24 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Assembling and Installing the Phone
3. If applicable, connect the following optional jacks:
• LAN connection to PC
• Headset (accessory)
• Connection to add-on device (accessory)
• Connection to external keyboard (accessory)
• USB master for connection to a USB device (e. g. accessory USB Acoustic
Adapter)
7
To prevent damage on the OpenStage phone, connect an USB stick using
the adapter cable C39195-Z7704-A5.
7
Do not connect a USB hub to the phone’s USB port, as this may lead to
stability problems.
Page 25
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
25
Startup
Quick Start
2.3 Quick Start
This section describes a typical case: the setup of an OpenStage 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.
2.3.1 Accessing the Web Interface (WBM)
1. Open your web browser (MS Internet Explorer or Firefox) and enter the appropriate URL.
Example: https://192.168.1.15 or https://myphone.phones
For configuring the phone’s DNS name, please refer to Section 3.3.7.1, “DNS Domain
Name”.
If the browser displays a certificate notification, accept it. The start page of the web interface appears. In the upper right corner, the phone number, the phone’s IP address, as well
as the DNS name assigned to the phone are displayed. The left corner contains the user
menu tree.
>
Alternatively, the DLS (Deployment Service) administration tool can be used. Its
Plug & Play functionality allows to provide the phone with configuration data by assigning an existing data profile to the phone’s MAC address or E.164 number. For
further information, see the Deployment Service Administration Manual.
>
Any settings made by a DHCP server are not configurable by other configuration
tools.
Page 26
Startup
A31003-S2030-M100-11-76A9, 01/2015
26 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
2. Click on the tab "Administrator Pages". In the dialog box, enter the admin password:
3. 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 in the right
column.
2.3.2 Set the Terminal Number
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 Section 3.5.1.1, “Terminal Identity”. With the WBM, the terminal number
is configured as follows:
In the left column, select System > System Identity to open the "System Identity" dialog. Enter
the terminal number, i. e. the SIP name / phone number.
2.3.3 Basic Network Configuration
For basic functionality, DHCP must provide the following parameters:
• IP Address: IP Address for the phone.
• Subnet Mask (option #1): Subnet mask of the phone.
• Default Route (option #3 "Router"): IP Address of the default gateway which is used for
connections beyond the subnet.
• DNS IP Addresses (option #6 "Domain Server"): IP Addresses of the primary and
secondary DNS servers.
If no DHCP server is present, see Section 3.3.4, “IP Address - Manual Configuration” for IP address and subnet mask, and Section 3.3.5, “Default Route/Gateway” for the default route.
Admin Login
Enter Admin password:
Login
Reset
Terminal name
Display identity
Enable ID
Web name
DNS name construction
System Identity
4711
Terminal number
4711
Submit
Reset
openstage
Only number
;
Page 27
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
27
Startup
Quick Start
2.3.4 DHCP Resilience
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.
In the left column, select Network > IPv4 configuration to open the "System Identity" dialog. Select the check box to enable DHCP lease reuse.
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 timezone 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.
• Timezone 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 Section 3.5.5, “Date and Time”.
LLDP-MED Enabled
DHCP lease reuse
IP address
Subnet mask
Default route
Route 1 IP address
Route 1 gateway
Route 1 mask
IPv4 configuration
192.168.1.235
192.168.1.2
DHCP Enabled
Submit
Reset
255.255.255.0
Route 2 IP address
Route 2 gateway
Route 2 mask
Page 28
Startup
A31003-S2030-M100-11-76A9, 01/2015
28 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
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 Section 3.5.6.1, “SIP Addresses”.
2.3.7 Extended Network Configuration
To have constant access to other subnets, you can enter a total of two more network destinations. For each further domain/subnet you wish to use, first the IP address for the destination,
and then that of the router must be given. The option’s name and code are as follows:
• option #33 "Static Routing Table"
For manual configuration of specific/static routing see Section 3.3.6, “Specific IP Routing”.
Also the DNS domain wherein the phone is located can be specified by DHCP. The option’s
name and code are as follows:
• option #15 "Domain Name"
For manual configuration of the DNS domain name see Section 3.3.7.1, “DNS Domain Name”.
2.3.8 Vendor Specific: VLAN Discovery And DLS Address
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 Section
3.2.2.2, “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 startup.
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 Section 3.3.8, “Configuration & Update Service (DLS)”.
For the configuration of vendor-specific settings by DHCP, there are two alternative methods:
1) the use of a vendor class, or 2) the use of DHCP option 43.
>
The VLAN ID can also be configured by LLDP-MED (see Section 3.2.2.2, “Automatic
VLAN discovery using DHCP”).
Page 29
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
29
Startup
Quick Start
2.3.8.1 Using a Vendor Class
It is recommended to define a vendor class on the DHCP server, thus enabling server and
phone to exchange vendor-specific data exclusively. The data is disclosed from other clients.
In the following, the configuration of vendor classes is explained both for a Windows DHCP
Server and for Unix/Linux.
Configuration of the Windows DHCP Server
1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.
2. In the DHCP console menu, right-click the DHCP server in question and select Define
Vendor Classes... in the context menu.
3. A dialog window opens with a list of the classes that are already available.
>
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 re-assigned using the
DHCP console.
This error was corrected in Windows 2003 Server SP2.
Page 30
Startup
A31003-S2030-M100-11-76A9, 01/2015
30 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
4. Press Add... to define a new vendor class.
5. 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.
Click OK to apply the changes. The new vendor class now appears in the list:
6. Exit the window with Close.
Page 31
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
31
Startup
Quick Start
7. In the DHCP console menu, right-click the DHCP server in question and select Set Pre-
defined 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.)
Page 32
Startup
A31003-S2030-M100-11-76A9, 01/2015
32 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
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".
• 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.
Page 33
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
33
Startup
Quick Start
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.
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 10 (Hex: 2A).
If you do not intend to configure the DLS address, click OK and continue with step 15.
Page 34
Startup
A31003-S2030-M100-11-76A9, 01/2015
34 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
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.
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.
Page 35
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
35
Startup
Quick Start
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.
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.
Page 36
Startup
A31003-S2030-M100-11-76A9, 01/2015
36 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
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.
Page 37
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
37
Startup
Quick Start
Setup using a DHCP server on Unix/Linux
The following snippet from a DHCP configuration file (usually dhcpd.conf) shows how to set up
a configuration using a vendor class and the "vendor-encapsulated-options" option.
class "OptiIpPhone" {
option vendor-encapsulated-options
# The vendor encapsulated options consist of hexadecimal values for
the option number (for instance, 01), the length of the value (for instance, 07), and the value (for instance, 53:69:65:6D:65:6E:73). The
options can be written in separate lines; the last option must be followed by a ’;’ instead of a ’:’.
# Tag/Option #1: Vendor 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 25s dlp: //1 92 .168.3 . (...etc.)
03:19:73:64:6C:70:3A:2F:2F:31:39:32:2E:31:36:38:2E:33:2E:33:30:
3A:31:38:34:34:33;
match if substring (option vendor-class-identifier, 0, 11) =
"OptiIpPhone";
}
2.3.8.2 Using 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 hostname
The Vendor name tag is coded as follows (the first line indicates the ASCII values, the second
line contains the hexadecimal values):
Code Length Vendor name
1 7 Si emens
01 07 53 69 65 6D 65 6E 73
Page 38
Startup
A31003-S2030-M100-11-76A9, 01/2015
38 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
The following example shows a VLAN ID with the decimal value "10". Providing:
For manual configuration of the VLAN ID see Section 3.2.2.3, “Manual configuration of a VLAN
ID”.
The DLS IP address tag consists of the protocol prefix "sdlp://", the IP address of the DLS server, and the DLS port number, which is "18443" by default. The following example illustrates the
syntax:
Setup using the Windows DHCP Server
1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.
2. Select the DHCP server and the scope. Choose Configure Options in the context menu
using the right mouse button.
Code Length VLAN ID
240010
02 04 00 00 00 0A
Code Length DLS IP address
3 25 sdl p: / / 192. 168. 3. 30: 18443
03 19
73646C703A2F2F3139322E3136382E332E33303A3138343433
Page 39
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
39
Startup
Quick Start
3. Enter tag 1, that is the vendor tag. The value has to be "Siemens".
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).
Page 40
Startup
A31003-S2030-M100-11-76A9, 01/2015
40 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
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>
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.
>
For ensuring proper functionality, the port number should not be followed by any
character.
Page 41
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
41
Startup
Quick Start
6. The DHCP console now shows the information that will be transmitted to the corresponding
workpoints.
Page 42
Startup
A31003-S2030-M100-11-76A9, 01/2015
42 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Quick Start
2.3.9 Registering at Phone Administration
For registration at the OpenStage SIP V3R3 SIP server, a SIP user ID and password must be
provided by the phone. The following procedure describes the configuration using the web interface (see Section 2.3.1, “Accessing the Web Interface (WBM)”; if the web interface is not
applicable, please refer to Section 3.5.7, “Authenticated Registration”) for configuration via the
local menu.
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 ad-
dress.
3. In the Server type field, select "OS Voice".
4. In Realm, enter the SIP realm the targeted user/password combination refers to.
5. In the User ID and Password fields, enter the user name/password combination for the
phone.
SIP server address
SIP registar Address
SIP gateway address
Registration
SIP Survivability
SIP Session
SIP Addresses
192.168.1.165
Session timer enabled
Session duration (seconds)
Registration timer (seconds)
3600
3600
Server type
HiQ8000
Submit
Reset
192.168.1.165
Backup registration allowed
Backup proxy address
Backup registration timer (seconds)
3600
;
Backup transport
Backup OBP flag
UDP
Realm
User ID
Password
Page 43
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
43
Startup
Startup Procedure
2.4 Startup Procedure
The following flowchart shows the startup process for OpenStage phones:
Manual
configured
VLAN-ID
Power Up
L2 interface
configured
Start 802.1x
Suppplicant
in auth. mode
Start 802.1x
Suppplicant
in Proxy-EAPOL-
Logoff mode
No
Yes
Yes
No
LLDP-Med
assigns
VLAN-ID
No
No
Manual
configured
IP addresses
Contact DLS
and
get conf. data
No network-
access
No network-
access
No
Yes
Yes
GuestVLAN
or
AuthfailVLA N
LLDP-Med
assigns
VLAN-ID
DHCP
assigns
VLAN-ID
No
No
Yes
Yes
802.1x
credential
802.1x
auth.
GuestVLAN
or
untagged VLAN
DHCP
assigned
IP addresses
Yes
Voic eVL AN
Manual
configured
VLAN-ID
No
Yes
DHCP
assigns
VLAN-ID
No
Yes
No network-
access
No
No
Yes
L3 not
configured
L2
conf. data
changed
Yes
No
No
Conf. finished
OpenStage boot sequence using VoiceVLAN
and no DHCP reuse
GuestVLAN
Description:
In case OpenStage i s in state
„Proxy-EAPOL-Logoff“, it
does not make sense to
posess a VLAN-ID, because
the OpenStage phone is not
authorized for any
authenticated VLAN.
802.1x enabled on
authenticator
Yes
No
802.1x enabled on
authenticator
Yes
No
Page 44
Startup
A31003-S2030-M100-11-76A9, 01/2015
44 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Cloud Deployment
2.5 Cloud Deployment
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 Unify Redirect server1 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 Unify 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.
2.5.1 Process of Cloud Deployment
The following flow chart shows the way from a factory start-up until a user prepared OpenStage
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
• The LAN connection provides access to the public internet
1. The address for the Unify Redirect server is hardcoded as "'cloud-setup.com"
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
Start
Phone broadcasts a DHCP
request
A DHCP server responds
with IP addresses
The phone detects that a
cloud deployment is re-
quired
Page 45
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
45
Startup
Cloud Deployment
The phone is locked so that the
mode keys & FPKs etc cannot be
used
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 Kapitel 2, “Aborting cloud deployment process by
User”
• DLS address (set to the name of
the Deployment server)
• Language optional)
• DLS port (optional)
The phone stars the cloud
deployment process
The phone obtains the IP ad-
dress of the Unify Redirect
server ("cloud-setup.com")
from the DNS
The phone gets the pin from
the user
Phone displays the Progress
prompt
Phone contacts the Unify
Redirect server using DLS-
Phone receives configura-
tion items from the Unify Re-
direct server
Page 46
Startup
A31003-S2030-M100-11-76A9, 01/2015
46 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Cloud Deployment
If the language is changed then the
display is updated
The stored DLS address is not
changed by the result of the DNS
lookup
The hash of the pin is provided as
an Inventory item to the Deployment server
Phone saves the
configuration data
Phone updates, and
displays, the Progress
prompt
The phone obtains the IP ad-
dress of the Deployment
server from the DNS by looking up the DLS address if ap-
propriate.
Phone contacts the Deployment server using DLS-WPI
Deployment server config-
ures the phone and the
phone saves the changes
Deployment server termi-
nates the DLS-WPI session
Page 47
inbetriebnahme.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
47
Startup
Cloud Deployment
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.
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.
The phone exits the cloud
deployment process and enables the mode keys & FPKs
etc. to act as normal
Phone removes the
Progress prompt and dis-
plays a timed success pop-
up, indicating that cloud de-
ployment is done
The phone verifies that it
now has an e.164 address
registered
Page 48
Startup
A31003-S2030-M100-11-76A9, 01/2015
48 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
inbetriebnahme.fm
Cloud Deployment
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.
• It is shown to notify the phone User that deployment failed to complete as expected.
• It is a non-timed warning popup
• It is non-dismissible by user action
• It is shown over the idle screen only
• It is shown/re-shown whenever the idle screen is displayed or redisplayed to the user
• It is formatted as the warning icon followed by a warning text which ends in a code displayed in round brackets.
• The warning text is = "Deployment incomplete"
• It displays only the highest priority error condition should more than one error condition apply (note that priority 1 is the highest)
Code Priority Cause
AU 1 Abandoned by user
Occurs when the pin prompt is dismissed
RS 1 Unable to get the address for the Unify Redirect server
DNS lookup failed
RN 3 Unable to establish contact with Unify Redirect server – no reply
RR 2 Unable to establish contact with Unify Redirect server – refused
RU 1 Unable to establish contact with Unify Redirect server - unauthorised
RO 3 Unable to establish contact with Unify Redirect server - no or invalid
OCSP response
RV 2 Unable to establish contact with Unify Redirect server - certificate re-
voked
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 49
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
49
Administration
Access via Local Phone
3 Administration
This chapter describes the configuration of every parameter available on the OpenStage
phones. For access via the local phone menu, see the following; for access using the web interface, please refer to Section 2.3.1, “Accessing the Web Interface (WBM)”.
3.1 Access via Local Phone
1. Access the Admin Menu
OpenStage 60/80:
The menu key
v toggles between the Settings menu, the Applications menu, and the ap-
plications currently running. Press the v key repeatedly until the "Settings" tab is active.
OpenStage 40:
Press the keys D, l, and i consecutively to select Settings > Admin (the administration
menu).
OpenStage 40 US:
Press the keys "Services", l, and i consecutively to select Settings > Admin (the admin-
istration menu).
2. Enter Password
When the Admin menu is active, you will be prompted to enter the administrator password.
The default admin password is "123456". It is highly recommended to change the password (see Section 3.20, “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 around the input
modes as follows:
(Abc) -> (abc) -> (123) -> (HEX) -> (ABC) -> back to start.
Usable characters are 0-9 A-Z a-z .*#,?!’+-()@/:_
>
The data entered in input fields is parsed and controlled by the phone. Thus, data is
accepted only if it complies to the value range.
Page 50
Administration
A31003-S2030-M100-11-76A9, 01/2015
50 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Access via Local Phone
3. Navigate within the Admin Menu
OpenStage 60/80
Use the TouchGuide to navigate and execute administrative actions in the Admin menu.
OpenStage 40
Use the 5-way navigator to navigate and execute administrative actions in the administration
menu.
Press the m key briefly:
- scroll up
Hold down:
- scroll to top of list
Press the
l key briefly:
- scroll down
Hold down:
- scroll to end of list
Press the
g key:
- open a context menu
- down one level
Press the
h key:
- cancel a function
- delete character left
of cursor
- up one level
Press the
i key:
- confirm entries
- perform an action
Run your finger around the
inner sensor ring W:
- browse lists and menus
- set up volume
Press the mkey briefly:
- scroll up
Hold down:
- scroll to top of list
Press the
l key briefly:
- scroll down
Hold down:
- scroll to end of list
Press the
g key:
- open a context menu
- down one level
Press the
h key:
- cancel a function
- delete character left
of cursor
- up one level
Press the
i key:
- confirm entries
- perform an action
Page 51
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
51
Administration
Access via Local Phone
OpenStage 20
Use the 3-way navigator to navigate and execute administrative actions in the administration
menu.
OpenStage 15
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 (on OpenStage 80,60, and 40 displays only). Press
the
i key to enter the selective list. Use the Sensor Wheel resp. the m and l key to scroll
up and down in the selective list. To select a list entry, press the
i key.
5. Enter the parameter value
For selecting numbers and characters, you can use special keys. See the following table:
Key Function
*
Switch to punctuation and special characters.
#
Toggle between lowercase characters, uppercase characters, and digits in
the following order:
(Abc) -> (abc) -> (123) -> (ABC) -> back to start.
Press the m key briefly:
- scroll up
Hold down:
- scroll to top of list
Press the
l key briefly:
- scroll down
Hold down:
- scroll to end of list
Press the
l key:
- confirm entries
- perform an action
Press the m key briefly:
- scroll up
Press the
l key:
In idle mode:
- Open idle menu
In lists and menus:
- scroll down
Press the
i key:
- confirm entries
- perform an action
Page 52
Administration
A31003-S2030-M100-11-76A9, 01/2015
52 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Access via Local Phone
OpenStage 60/80
If a parameter is set by entering a number or character data, the onscreen keypad is used.
Press the i key to enter the editor. Within the editor, solely use the key numbers or the
Sensor Wheel for selecting numbers, characters, or groups of characters. The h key deletes one character in the input field, and the g key moves the cursor to the OK field.
The following figure describes the elements of the onscreen keypad and their functions:
Additionally, you can use the following keys on the keypad as shortcuts for the selection of
character groups
OpenStage 15/20/40
With the OpenStage 15/20/40, use the keypad for entering parameters. With the 3 way/5
way navigator, you can enter, delete, copy, and paste characters and numbers as well as
navigate within an entry and toggle the input mode.
6. Save and exit
When you are done, select Save & exit and press .
Element Function
*
Switch to punctuation and special characters.
#
Toggle between lowercase characters, uppercase characters, and digits.
Element with focus
Letters, digits, punctuation marks or special characters
Cancel
Shift to numeric entry Shift to punctuation and special characters Shift to numeric entry
Shift to upper/lower case Shift to upper/lower case
Insert clipboard contents at cursor position
Move cursor left/right
Shift to punctuation and special characters
Copy contents of active field to clipboard
Confirm
Page 53
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
53
Administration
LAN Settings
3.2 LAN Settings
3.2.1 LAN Port Settings
The OpenStage phone provides an integrated switch which connects the LAN, the phone itself
and a PC port. By default, the switch will auto negotiate transfer rate (10/100 Mb/s, 1000 Mb/s
with OpenStage 15/20/40/60/80 G) 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.
The PC Ethernet port 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.
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" and, additionally, for OpenStage 20/40/60/80 G, "1 Gbps 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" and, additionally, for OpenStage 20/40/60/80 G, "1 Gbps full
duplex"
Default: "Automatic"
• PC port mode / PC port status: Controls the PC port.
Value range: "disabled", "enabled", "mirror".
Default: "disabled"
>
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.
>
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.
Page 54
Administration
A31003-S2030-M100-11-76A9, 01/2015
54 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
LAN Settings
• PC port autoMDIX: Switches between MDI and MDI-X automatically.
Value range: "On", "Off"
Default: "Off"
Administration via WBM
Network > Port configuration
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- Port Configuration
|--- LAN port type
|--- PC port status
|--- PC port type
|
--- PC port autoMDIX
SIP local
Backup proxy
RTP base
Download server (default)
LDAP server
HTTP proxy
LAN port speed
PC port speed
389
Port configuration
5060
21
Automatic
SIP gateway
5060
Submit
Reset
Automatic
0
5060
5010
SIP Server
SIP registrar
5060
5060
PC port mode
PC port autoMDIX
disabled
Page 55
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
55
Administration
LAN Settings
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.
In a layer 1 VLAN, the ports of a VLAN-aware switch are assigned to a VLAN statically. The
switch only forwards traffic to a particular port if that port is a member of the VLAN that the traffic
is allocated to. Any device connected to a VLAN-assigned port is automatically a member of
this VLAN, without being a VLAN aware device itself. If two or more network clients are connected to one port, they cannot be assigned to different VLANs. When a network client is moving from one switch to another, the switches’ ports have to be updated accordingly by hand.
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 OpenStage. 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:
• Manually
• By DHCP
•By LLDP-MED
>
The implementation of a voice network based on VLANs requires the network infrastructure (the switch fabric) to support VLANs.
Page 56
Administration
A31003-S2030-M100-11-76A9, 01/2015
56 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
LAN Settings
3.2.2.1 Automatic VLAN discovery using LLDP-MED
As an alternative, 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, and the switch
provides an appropriate TLV (Type-Length-Value) element containing the VLAN ID, this VLAN
ID will be used. If no appropriate TLV is received, DHCP will be used for VLAN discovery.
Administration via WBM
Network > General IP configuration
To enable VLAN discovery via LLDP-MED, activate the LLDP-MED Enabled checkbox and se-
lect 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.
|
--- Admin
|
--- Network
|
--- General IP configuration
|
--- Protocol mode
|
--- Use LLDP-MED
|
--- Use DHCP
|
--- Use DHCPv6
|
--- VLAN discovery
|
--- VLAN ID
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
LLDP-MED
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
;
Page 57
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
57
Administration
LAN Settings
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". LLDP-MED 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
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.
|
--- Admin
|
--- Network
|
--- General IP configuration
|
--- Protocol mode
|
--- Use LLDP-MED
|
--- Use DHCP
|
--- Use DHCPv6
|
--- VLAN discovery
|
--- VLAN ID
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
DHCP
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 58
Administration
A31003-S2030-M100-11-76A9, 01/2015
58 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
LAN Settings
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
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 by Manual, select Manual in the VLAN discovery option.
|
--- Admin
|
--- Network
|
--- General IP Configuration
|
--- VLAN ID
|
--- Admin
|
--- Network
|
--- General IP configuration
|
--- VLAN discovery
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
Manual
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 59
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
59
Administration
LAN Settings
3.2.3 LLDP-MED Operation
OpenStage phones support LLDP-MED (Link Layer Discovery Protocol-Media Endpoint Discovery) for auto-configuration and network management. The auto-configurable parameters
are VLAN ID (see Section 3.2.2, “VLAN”) and Quality of Service parameters (see Section 3.3.1,
“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-to-date, a specific TTL
(Time To Live) is specified in LLDP. This value tells a device how long the received information
is valid. For OpenStage phones, the value range is 40, 60, 80, 100, 110, 120, 140, 180, 240,
320, 400.
An example for LLDP-MED operation an OpenStage phones can be found in Section 5.4, “An
LLDP-Med Example”.
Administration via WBM
Network > LLDP-MED operation
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- LLDP-MED operation
|
--- Extended power display only
|
--- Network policy (voice) display only
|
--- LLDP-MED cap’s display only
|
--- MAC-Phy config display only
|
--- System Cap’s display only
|
--- TTL
|
--- TTL
LLDP-MED operation
Submit
Reset
Time to live (seconds)
120
Page 60
Administration
A31003-S2030-M100-11-76A9, 01/2015
60 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
3.3 IP Network Parameters
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.
3.3.1.1 Layer 2 / 802.1p
QoS on layer 2 is using 3 Bits in the 802.1q/p 4-Byte VLAN tag which has to be added in the
Ethernet header.
The CoS (class of service) value can be set from 0 to 7. 7 is describing the highest priority and
is reserved for network management. 5 is used for voice (RTP-streams) by default. 3 is used
for signaling by default.
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 video: Sets the CoS (Class of Service) value for video.
Value range: 0-7
Default: 4
• Layer 2 default: Sets the default CoS (Class of Service) value.
Value range: 0-7
Default: 0
>
Layer 2 and 3 QoS for voice transmission can be set via LLDP-MED (see Section
3.26.6, “LLDP-MED”). If so, the value can not be changed by any other interface.
Three Bits Used for CoS
(User Priority)
PREAM. SFD DA SA
TAG
4 Bytes
PT DATA FCS
Page 61
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
61
Administration
IP Network Parameters
Administration via WBM
Network > QoS
Administration via Local Phone
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.
Traffic flows are classified into 3 per-hop behavior groups:
1. Default
Any traffic that does not meet the requirements of any of the other defined classes is placed
in the default per-hop behaviour group. Typically, the forwarding has best-effort forwarding
characteristics. The DSCP (Diffserv Codepoint) value for Default is "000000".
2. Expedited Forwarding (EF referred to RFC 3246)
|
--- Admin
|
--- Network
|
--- QoS
|
--- Service
|--- Layer 2
|--- Layer 2 voice
|--- Layer 2 signalling
|
--- Layer 2 video
|
--- Layer 2 default
Layer 2 signalling
Layer 2 video
Layer 3 voice
Layer 3 signalling
Layer 2 voice
Layer 2
5
4
QoS
3
Layer 3
EF
AF31
Immediate
Flash
Flash override
Priority
EF
EF
Submit Reset
EF
EF
Service
MLPP
;
Layer 3 video
AF41
Layer 2 default
0
Page 62
Administration
A31003-S2030-M100-11-76A9, 01/2015
62 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
Expedited Forwarding is used for voice (RTP streams) by default. It effectively creates a
special low-latency path in the network. The DSCP (Diffserv Codepoint) value for EF is
"101110".
3. Assured Forwarding (AF referred to RFC 2597)
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"
• Layer 3 video: Sets the CoS (Class of Service) value for video.
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: "AF41"
Page 63
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
63
Administration
IP Network Parameters
Administration via WBM
Network > QoS
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- QoS
|
--- Service
|--- Layer 3
|--- Layer 3 voice
|
--- Layer 3 signalling
|
--- Layer 3 video
Layer 2 signalling
Layer 2 video
Layer 3 voice
Layer 3 signalling
Layer 2 voice
Layer 2
5
4
QoS
3
Layer 3
;
EF
AF31
Immediate
Flash
Flash override
Priority
EF
EF
Submit Reset
EF
EF
Service
MLPP
Layer 3 video
AF41
Layer 2 default
0
Page 64
Administration
A31003-S2030-M100-11-76A9, 01/2015
64 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
3.3.2 Protocol Mode IPv4/IPv6
An IPv4 address consists of 4 number blocks, each between 0 and 255, separated by ".".
Example:
1.222.44.123
An IPv6 address consists of 8 hexadecimal number blocks, separated by ":".
Example:
2001:0db8:85a3:08d3:1319:8a2e:0370:7347 or, if not all blocks are used:
2000:1::3
Administration via WBM
Network > General IP configuration
Set the Protocol Mode to "IPv4" or "IPv6" or both (the default setting is IPv4_IPv6). Afterwards,
click Submit.
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- General IP Configuration
|
--- Protocol Mode
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
Manual
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 65
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
65
Administration
IP Network Parameters
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.
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)
• 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)
>
The phone is able to maintain its IP connection even in case of DHCP server failure.
For further information, please refer to Section 2.3.4, “DHCP Resilience”.
Page 66
Administration
A31003-S2030-M100-11-76A9, 01/2015
66 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
• 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
Network > General IP configuration
Set DHCP Enabled to selected. Afterwards, click Submit.
Administration via Local Phone
or/and
|
--- Admin
|
--- Network
|
--- IPv4 configuration
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
DHCP
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
;
Page 67
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
67
Administration
IP Network Parameters
Administration via WBM
Network > General IP configuration
Set DHCPv6 Enabled to selected (the default setting is Enabled). Afterwards, click Submit.
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- IPv6 configuration
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
DHCP
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 68
Administration
A31003-S2030-M100-11-76A9, 01/2015
68 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
3.3.4 IP Address - Manual Configuration
3.3.4.1 Configuration
If not provided by DHCP dynamically, the phone’s IP address and subnet mask must be
specified manually.
By default, IP configuration by DHCP and LLDP-MED is enabled. For manual IP configuration,
please proceed as follows:
1. Navigate to Network > General IP configuration. Set DHCP Enabled, DHCPv6 Enabled
and LLDP-MED to "not selected". Afterwards, click Submit.
2. Navigate to Network > General IP configuration> IPv4 configuration or IPv6 configu-
ration depending on settings in Section 3.3.2, “Protocol Mode IPv4/IPv6”. Enter the IP ad-
dress and the Subnet mask. If applicable, enter the Default route. Afterwards, click Sub-
mit.
3. After the phone’s network service has restarted, the other IP parameters can be
configured.
>
IP addresses can be entered in the following formats:
– Decimal format. Example: 11.22.33.44 or 255.255.255.0 (no leading ze-
roes).
– 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)
LLDP-MED Enabled
DHCP lease reuse
IP address
Subnet mask
Default route
Route 1 IP address
Route 1 gateway
Route 1 mask
IPv4 configuration
192.168.1.235
192.168.1.2
DHCP Enabled
Submit
Reset
255.255.255.0
Route 2 IP address
Route 2 gateway
Route 2 mask
Global Address
Global Address Prefix Len
Global Gateway
Link Local Address
Route 1 Dest.
Route 1
Prefix Len
LLDP-MED Enabled
IPv6 configuration
DHCPv6 Enabled
DHCPv6 lease reuse
Submit
Reset
Route 1
Gateway
Route 2 Dest.
Route 2
Prefix Len
Route 2
Gateway
Page 69
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
69
Administration
IP Network Parameters
Administration via Local Phone
|
--- Admin
|
--- Network
General IP configuration
|--- Use LLDP-MED
|
--- Use DHCP
|
--- Use DHCPv6
|
--- Admin
|
--- Network
IPv4 configuration
|--- IP address
|
--- Subnet mask
|
--- Admin
|
--- Network
IPv4 configuration
|--- Global address
|
--- Global Prefix Len
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
Manual
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 70
Administration
A31003-S2030-M100-11-76A9, 01/2015
70 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
3.3.5 Default Route/Gateway
If not provided by DHCP dynamically (see Section 3.3.3, “Use DHCP”), enter the IP address of
the router that links your IP network to other networks. If the value was assigned by DHCP, it
can only be read.
Administration via WBM
Network > IPv4 configuration
Enter the IP address of the router that links your IP network to other networks. Afterwards, click
Submit.
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- IPv4 configuration
|
--- Route (Default)
LLDP-MED Enabled
DHCP lease reuse
IP address
Subnet mask
Default route
Route 1 IP address
Route 1 gateway
Route 1 mask
IPv4 configuration
192.168.1.235
192.168.1.2
DHCP Enabled
Submit
Reset
255.255.255.0
Route 2 IP address
Route 2 gateway
Route 2 mask
;
Page 71
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
71
Administration
IP Network Parameters
Administration via WBM
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
|
--- Admin
|
--- Network
|
--- IPv6 configuration
|
--- Global Gateway
Global Address
Global Address Prefix Len
Global Gateway
Link Local Address
Route 1 Dest.
Route 1
Prefix Len
LLDP-MED Enabled
IPv6 configuration
DHCPv6 Enabled
DHCPv6 lease reuse
Submit
Reset
Route 1
Gateway
Route 2 Dest.
Route 2
Prefix Len
Route 2
Gateway
Page 72
Administration
A31003-S2030-M100-11-76A9, 01/2015
72 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
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.
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 IP address of the router that links your IP network to other networks. Click Submit.
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- IPv4 configuration
|--- Route 1 IP
|--- Route 1 gateway
|--- Route 1 mask
|--- Route 2 IP
|--- Route 2 gateway
|
--- Route 2 mask
LLDP-MED Enabled
DHCP lease reuse
IP address
Subnet mask
Default route
Route 1 IP address
Route 1 gateway
Route 1 mask
IPv4 configuration
192.168.1.235
192.168.1.2
DHCP Enabled
Submit
Reset
255.255.255.0
Route 2 IP address
Route 2 gateway
Route 2 mask
;
Page 73
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
73
Administration
IP Network Parameters
IPv6 Route Configuration
Data required
• Route 1/2 destination: IPv6 address of the selected route.
• Route 1/2 prefix len: Prefix length for the selected route.
• Route 1/2 gateway: IPv6 address of the gateway for the selected route.
Administration via WBM
Network > IPv6 configuration
Enter the IP address of the router that links your IP network to other networks. Afterwards, click
Submit.
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- IPv6 configuration
|--- Route 1 dest
|--- Route 1 prefix len
|--- Route 1 gateway
|--- Route 2 dest
|--- Route 2 prefix len
|
--- Route 2 gateway
Global Address
Global Address Prefix Len
Global Gateway
Link Local Address
Route 1 Dest.
Route 1
Prefix Len
LLDP-MED Enabled
IPv6 configuration
DHCPv6 Enabled
DHCPv6 lease reuse
Submit
Reset
Route 1
Gateway
Route 2 Dest.
Route 2
Prefix Len
Route 2
Gateway
Page 74
Administration
A31003-S2030-M100-11-76A9, 01/2015
74 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
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 OpenStage phone, it is necessary to configure the
DNS domain the phone belongs to, as well as the name servers needed for DNS resolving.
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
|
--- Admin
|
--- Network
|
--- General IP configuration
|
--- DNS domain
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
Manual
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 75
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
75
Administration
IP Network Parameters
3.3.7.2 DNS Servers
If not provided by DHCP automatically, a primary and a secondary DNS server can be configured.
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
Enter the IP addresses of the primary and the secondary DNS server. Afterwards, click Submit.
Administration via Local Phone
>
Enhanced survivability using DNS SRV is available. To make use of it, a special configuration is required. For details, please refer to Section 3.5.10, “Resilience and
Survivability”.
|
--- Admin
|
--- Network
|
--- General IP configuration
|--- Primary DNS
|
--- Secondary DNS
LLDP-MED Enabled
DHCPv6 Enabled
VLAN discovery
VLAN ID
DNS domain
Protocol Mode
Primary DNS
Secondary DNS
HTTP proxy
IPv4_IPv6
General IP configuration
Manual
;
DHCP Enabled
Submit
Reset
192.168.1.105
192.168.1.2
Page 76
Administration
A31003-S2030-M100-11-76A9, 01/2015
76 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
3.3.7.3 Terminal Hostname
The phone’s hostname can be customized.
The corresponding DNS domain is configured in Network > IP configuration > DNS domain
(see Section 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.
The DNS name can be constructed from pre-defined parameters and free text. Its composition
is defined by the DNS name construction parameter. The following options are available:
• "None":
• "MAC based": The DNS name is built from the prefix "OIP" followed by the phone’s MAC
address.
• "Web name": The DNS name is set to the the string entered in Web name.
• "Only number": The DNS name is set to the Terminal number, that is, the phone’s call
number (see Section 3.5.1, “Terminal and User Identity”).
• "Prefix number": The DNS name is constructed from the the string entered in Web name,
followed by the Terminal number.
Administration via WBM
System > System Identity
Administration via Local Phone
>
It is recommended to inform the user about the DNS name of his/her phone. The
complete WBM address can be found under User menu > Network information >
Web address.
|
--- Admin
|
--- System
|
--- Identity
|--- Web name
|
--- DDNS hostname
Terminal name
Display identity
Enable ID
Web name
DNS name construction
System Identity
4711
Terminal number
4711
Submit
Reset
openstage
Only number
;
Page 77
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
77
Administration
IP Network Parameters
3.3.8 Configuration & Update Service (DLS)
The Deployment Service (DLS) is a HiPath Management application for administering workpoints in both HiPath and non-HiPath networks. Amongst the most important features are: security (e.g. PSS generation and distribution within an SRTP security domain), mobility for optiPoint and OpenStage SIP phones, software deployment, plug&play support, as well as error
and activity logging.
DLS address, i.e. the IP address or hostname of the DLS server, and Default mode portDLS
port, i.e. the port on which the DLS server is listening, are required to enable proper commu-
nication between phone and DLS.
The Contact gap parameter is not used.
Set Revert to default security to disable mutual authentication and return to DEFAULT mode.
SECURE mode related settings are reset and certificates are removed.
The ModeSecurity mode determines whether the communication between the phone and the
DLS is secure. A secure connection is established by exchanging credentials between the DLS
and the phone for mutual authentication. After this, the communication is encrypted, and a different port is used.
A Security PIN can be provided which is used for decrypting data provided by the DLS during
bootstrap. For further information, please refer to the DLS documentation.
>
It is possible to operate the DLS server behind a firewall or NAT (Network Address
Translation), which prevents the DLS from sending ContactMe messages directly to
the phone. Only outbound connections from the phone are allowed. To overcome
this restriction, a DLS Contact-Me proxy (DCMP) can be deployed. The phone periodically polls the DCMP (DLS Contact-Me Proxy), which is placed outside of the
phone’s network, for pending contact requests from the DLS. If there are contact requests, the phone will send a request to the DLS in order to obtain the update, just
as with a regular DLS connection.
The URI of the DCMP, as well as the polling interval, are configured by the DLS. For
this purpose, it is necessary that the phone establishes a first contact to the DLS,
e. g. by phone restart or local configuration change.
Page 78
Administration
A31003-S2030-M100-11-76A9, 01/2015
78 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
Data required
• DLS address: IP address or hostname of the server on which the Deployment Service is
running.
• Default mode portDLS port: Port on which the DLS Deployment Service is listening.
Default: 18443
• Contact gap: The parameter is not used.
• Revert to default security: When set, security mode will be set to default. When using
local phone administration, this will be set by selection option ’Default security’ after
pressing Save&exit.
• ModeSecurity 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)
Administration via Local Phone
|
--- Admin
|
--- Network
|
--- Update Service (DLS)
|--- DLS address
|--- Default mode portDLS port
|--- Contact gap
|--- Mode
|
--- Security PIN
Default mode port
Contact gap
Revert to default security
Mode
Security PIN
Update Service (DLS)
300
DLS address
192.168.1.242
Submit
Reset
18443
Default
Page 79
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
79
Administration
IP Network Parameters
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.
OpenStage phones support SNMPv1.
There are currently 4 trap categories that can be sent by the phones:
Standard SNMP traps
OpenStage phones support the following types of standard SNMP traps, as defined in RFC
1157:
• coldStart: sent if the phone does a full restart.
• warmStart: sent if only the phone software is restarted.
• linkUp: sent when IP connectivity is restored.
QoS Related traps
These traps are designed specifically for receipt and interpretation by the QDC collection system. The traps are common to SIP phones, HFA phones, Gateways, etc.
Traps for important high level SIP related problems
Currently, these traps are related to problems in registering with a SIP Server and to a failure
in remotely logging off a mobile user. These traps are aimed at a non-expert user (e.g. a standard Network Management System) to highlight important telephony related problems.
Traps specific to OpenStage phones
Currently, the following traps are defined:
TraceEventFatal: sent if severe trace events occur; aimed at expert users.
TraceEventError: sent if severe trace events occur; aimed at expert users.
Data required
• Trap sending enabled: Enables or disables the sending of a TRAP message to the SNMP
manager.
Value range: "Yes", "No"
Default: "No"
• Trap destination: IP address or hostname of the SNMP manager that receives traps.
• Trap destination port: Port on which the SNMP manager is receiving TRAP messages.
• Default: 162
Page 80
Administration
A31003-S2030-M100-11-76A9, 01/2015
80 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
IP Network Parameters
• Trap community: SNMP community string for the SNMP manager receiving TRAP messages.
Default: "snmp"
• Queries allowed: Allows or disallows queries by the SNMP manager.
• Query password: Password for the execution of a query by the SNMP manager.
• Diagnostic sending enabled: Enables or disables the sending of diagnostic data to the
SNMP manager.
Value range: "Yes", "No"
Default: "No"
• Diagnostic destination: IP address or hostname of the SNMP manager receiving diagnostic data.
• Diagnostic destination port: Port on which the SNMP manager is receiving diagnostic
data.
• Diagnostic community: SNMP community string for the SNMP manager receiving diagnostic data.
• Diagnostic to generic destination / 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 81
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
81
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
|--- QCU port
|--- QCU community
|
--- QoS to generic dest.
Traping sending enabled
Trap destination
Trap destination port
Trap community
Queries allowed
Query password
SNMP
QoS report traps
Diagnistic traps
Generic traps
****
Diagnostic sending enabled
Diagnostic destination
Diagnostic destination port
Diagnostic community
Diagnostic to generic destination
Submit
Reset
162
QoS traps to QCU
QCU address
QCU port
12010
QCU community
QoS togeneric destination
*****
Page 82
Administration
A31003-S2030-M100-11-76A9, 01/2015
82 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
3.4 Security
3.4.1 Speech Encryption
3.4.1.1 General Configuration
OpenStage phones support secure (i.e. encrypted) speech transmission via SRTP. For enabling secure (encrypted) calls, a TLS connection to the Phone Administration 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.
If SIP server certificate validation resp. Backup SIP server certificate validation is
activated, the phone will validate the server certificate sent by the Phone Administration 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.
When Use SRTCP is activated (together with Use secure calls), the phone will use SRTCP
(Secure RTCP) to transmit and receive RTP control packets.
>
For secure (encrypted) calls, it is required that both endpoints support SRTP. The
secure call indication tells the user that the other endpoint has acknowledged the secure connection.
>
In order to use SRTP, the phone must be configured for NTP (for further information
please see Section 3.5.5, “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 SRTP is enabled, ANAT interworking (see Section 3.5.8.3, “Media/SDP”) is only
possible if SDES is configured as the key exchange protocol for SRTP.
Page 83
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
83
Administration
Security
Administration via WBM
System > Security > System
Administration via Local Phone
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.
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 Section 3.4.1.3, “SDES Configuration”)
The SRTP Type and Use SRTCP options are only available for secure (encrypted) calls, i.e.
these parameters are only enabled if Use secure calls is activated.
When Use SRTCP is activated (together with Use secure calls), the phone will use SRTCP
(Secure RTCP) to transmit and receive RTP control packets.
|
--- Admin
|
--- System
|
--- Security
|--- Server cerfificate
|--- Use secure calls
|--- SRTP type
|
--- Use SRTCP
>
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.
System
SIP server certificate validation
Use secure calls
SRTP type
MIKEY
Submit
Reset
Use SRTCP
Page 84
Administration
A31003-S2030-M100-11-76A9, 01/2015
84 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
Administration via WBM
System > Security > System
Administration via Local Phone
>
If SRTP is enabled, ANAT interworking (see Section 3.5.8.3, “Media/SDP”) is only
possible if SDES is configured as the key exchange protocol for SRTP.
|
--- Admin
|
--- System
|
--- Security
|--- Server cerfificate
|--- Use secure calls
|--- SRTP type
|
--- Use SRTCP
System
SIP server certificate validation
Use secure calls
SRTP type
MIKEY
Submit
Reset
Use SRTCP
Page 85
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
85
Administration
Security
3.4.1.3 SDES Configuration
When "SDES" is selected as SRTP negotiation method (see Section 3.4.1.1, “General Configuration”), it can be configured further.
The SDES status parameter enables or disables SDES, just like SRTP type in System > Security > System (see Section 3.4.1.1, “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:
• "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
SDES config
Submit
Reset
SHA1-80 ranking
SHA1-32 ranking
SDES status
SRTP + RTP
SDP negotiation
Disabled
X
X
Page 86
Administration
A31003-S2030-M100-11-76A9, 01/2015
86 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
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 is disabled. With "Enable", there are
no restrictions.
With Factory reset claw, the ’hooded claw’ keypad mechanism to initiate a factory reset with-
out 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.
Administration via WBM
System > Security > Access control
Access control
Submit
Reset
Factory reset claw
CCE access
No Password
Serial port
Enable
;
Page 87
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
87
Administration
Security
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.
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 disabled, every new entry will trigger a save (only possible via DLS). The
possible values are "10%”, ”20%”, ”30%”, ”35%”, ”40%”, ”45%”, ”50%”, ”55%”, ”60%”, ”65%”,
”70%”, ”80%”, ”90%”.
The security log upload may be accomplished in two ways:
• If "Archive to DLS" is enabled, if the security log reaches the threshold % for unachieved
entries, the phone will initiate an upload.
• If "Archive to DLS" is NOT enabled and the security log reaches the threshold % for unachieved entries, the phone only sets the "archive-me" flag, it does not initiate the a r c h i v e .
It is up to the DLS to recognize the flag and initiate an upload.
Last archived shows the date when the security log was last archived to the DLS.
Administration via WBM
System > Security > Logging
>
The security log cannot be disabled.
Logging
Submit
Reset
Archive to DLS
Max. lines
50%
Archive when at
500
20101105-0010
Last archived
Page 88
Administration
A31003-S2030-M100-11-76A9, 01/2015
88 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
3.4.4 Security-Related Faults
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 certifi-
cate 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
>
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
OCSR Failure
User access
Cancel faults
Faults
20111009-2206
Admin access
All
Submit Reset
Page 89
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
89
Administration
Security
3.4.5 Password Policy
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. This only applies to users, not to administrators.
Tries allowed specifies the maximum number of password entry trials before the password is
suspended. Values: 0 (no limits), 2, 3, 4, 5
No change for (hours) specifies a period before a password is allowed to be changed again.
Value range: 0 to 99
Suspended for (mins) defines how long a password will be suspended after the number of
failed retries has exceeded. Value range: 0 to 99
History valid for (days) defines a period in days during which the history is valid. Passwords
no longer used are kept in history lists for the user and admin passwords to prevent reuse of
past passwords. This list is organised as FIFO (First In, First Out) so that it always contains the
latest passwords.
Administration via WBM
Security and Policies > Password > Generic Policy
Warn before (days)
Force changed
Tries allowed
No change for (hours)
History valid for (days)
0
Generic policy
Expires after (days)
99
Submit
Reset
1
5
0
Suspended for (mins)
5
Page 90
Administration
A31003-S2030-M100-11-76A9, 01/2015
90 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
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 "Ac-
tive", 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
Expiry date
Minimum length
Password history
Current status
Admin policy
6
Submit
Reset
2038-01-19T03:14:07+00:00
0
Active
Page 91
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
91
Administration
Security
3.4.5.3 User Policy
Expiry date shows the date and time when the user password will expire.
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
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. 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
Expiry date
Minimum length
Password history
Current status
User policy
6
Submit
Reset
2038-01-19T03:14:07+00:00
0
Active
Page 92
Administration
A31003-S2030-M100-11-76A9, 01/2015
92 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
Administration via WBM
Security and Policies > Password > Character set
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 Section 3.20, “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
|
--- Admin password
|
--- New password
|
--- Confirm password
Special chars reqd
Bar repeat length
Min char difference
Character set
0
Digits required
Submit
Reset
0
0
Ucase chars reqd.
Lcase chars reqd.
0
0
0
Change Admin password
Old password
New password
Confirm password
Submit
Reset
Change User password
Admin password
New password
Confirm password
Submit
Reset
Page 93
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
93
Administration
Security
3.4.6 Certificate Policy
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
Generic
Submit
Reset
OCSP check
OCSR 1 address
OCSR 2 address
Page 94
Administration
A31003-S2030-M100-11-76A9, 01/2015
94 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
Security
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 Section
3.16.2, “Common FTP/HTTPS 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 Section 3.8.30, “Send Request via HTTP/HTTPS”).
Secure SIP server sets the authentication level for the SIP server connected to the phone (see
Section 3.5.7, “SIP Registration”).
Secure 802.1x sets the authentication level for the 802.1x authentication server.
XML Applications sets the authentication level for the XML applications server (see Section
3.19, “Applications”).
Administration via WBM
Security and Policies > Certificates > Authentication policy
Administration via Local Phone
|
--- Admin
|
--- Security & policies
|
--- Certificates
|
--- Authentication policy
|--- Secure file transfer
|
--- Secure send URL
Secure 802.1x
XML Applications
Authentication policy
None
Secure SIP server
Submit
Reset
None
Secure file transfer
Secure send URL
None
None
None
Page 95
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
95
Administration
System Settings
3.5 System Settings
3.5.1 Terminal and User Identity
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.
Administration via WBM
System > System Identity
Administration via Local Phone
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.
|
--- Admin
|
--- System
|
--- Identity
|--- Terminal number
|
--- Terminal name
Terminal name
Display identity
Enable ID
Web name
DNS name construction
System Identity
4711
Terminal number
4711
Submit
Reset
openstage
Only number
;
Page 96
Administration
A31003-S2030-M100-11-76A9, 01/2015
96 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
System Settings
Administration via WBM
System > System Identity
Administration via Local Phone
|
--- Admin
|
--- System
|
--- Identity
|--- Display identity
|
--- Enable ID
Terminal name
Display identity
Enable ID
Web name
DNS name construction
System Identity
4711
Terminal number
4711
Submit
Reset
openstage
Only number
;
Page 97
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
97
Administration
System Settings
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.
If a mailbox located at a remote server shall be used, its Voice mail number must be entered.
Administration via WBM
System > Features > Configuration
>
If more than one emergency number is needed, additional numbers can be configured in the canonical dial settings (Section 3.13.1, “Canonical Dialing Configuration”).
Voice Mail number
Allow refuse
Hot/warm phone
Hot/warm destination
Initial digit timer (seconds)
Emergency number
Allow uaCSTA
Server features
Not used timeout (minutes)
Transfer on hangup
3335
Configuration
Recorder Address
Recording Mode
Audible Notification
Off
Disabled
Call Recording
Bluetooth
Audio
General
Bridging enabled
Dial plan enabled
FPK program timer
On
No action
30
5
Group pickup tone allowed
Group pickup as ringer
Group pickup visual alert
BLF alerting
Beep
Prompt
Enable Bluetooth interface
;
;
;
;
;
;
MWI LED
Key & AlertBar
MLPP ringer
Callback ringer
alert-internal
;
Submit
Reset
Missed call LED
Key only
Impact level ringer
Page 98
Administration
A31003-S2030-M100-11-76A9, 01/2015
98 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
System Settings
Administration via Local Phone
3.5.3 Energy Saving (OpenStage 40/60/80)
After the phone has been inactive within the timespan specified in Backlight time, the display
backlight is switched off to save energy.
The possible values are: 1 minute, 5 minutes, 30 minutes, 60 minutes, 2 hours, 4 hours or 8
hours. Moreover, with OpenStage 40 and 60, this parameter can also be configured by the user.
Administration via WBM
Local functions > Energy saving
Administration via Local Phone
|
--- Admin
|
--- System
|
--- Features
|
--- Configuration
|
--- General
|--- Emergency number
|
--- Voicemail number
|
--- Admin
|
--- Local Functions
|
--- Energy saving
|
--- Backlight time
Backlight time
Energy saving
2 hours
Submit
Reset
Page 99
administration.fm
A31003-S2030-M100-11-76A9, 01/2015
OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
99
Administration
System Settings
3.5.4 Call logging
This configuration item allows the phone to detect if a number dialled by the User is likely to be
a Feature Access Code (FAC) by comparing the start of the dialled number with the configured
FAC prefixes. If the dialled number does match a FAC prefix and the SIP server has provided
a different number for the called party then the number shown in the Dialled tab list of Call Log
is changed from the dialled number to the server provided number. If the new configuration item
is left empty then the Dialled tab list display will remain as currently populated (i.e. the dialled
number is shown in the list).
A further enhancement for an entry matched to a FAC in the Dialled tab list of Call Log is that
the context menu for the list entry now provides both numbers from the last call associated with
the entry as Dial options in the context menu for the list entry (similar to that already provided
by the context menu for the Details form of such an entry). Note that the Call Log display on
OS15 has been simplified [3] so that an entry only displays a name or a number (not both) and
there is no access to entry details. However this only limits the display and the default dialling
number for an OS15 entry is determined as above.
Call Log entry grouping rules for the Dialled tab list remain unchanged, if multiple FACs all map
to numbers associated with one contact then they are grouped together.
Data required
• FAC prefixes: A comma separated list of feature prefixes considered to represent feature
codes configured at the SIP server for abbreviated dialling.
Administration via WBM
Local functions > Call logging
FAC prefixes
Call logging
Submit
Reset
Page 100
Administration
A31003-S2030-M100-11-76A9, 01/2015
100 OpenStage SIP V3R3 for OpenScape Voice, Administration Manual
administration.fm
System Settings
3.5.4.1 Logging of Missed Calls Answered Elsewhere (via User menu)
This feature allows the user to
• distinguish logged calls based on the device on which the calls were completed, and
• decide whether missed calls that were answered elsewhere shall be
– included into the call log, or
– excluded from the call log, i.e. not logged at all
• decide whether a number which also exists in missed calls tab of call log is to be deleted
from call log when this number is called
– manually
– when called
In the Call Lists, missed calls that were completed elsewhere are marked with a check mark.
For details, please refer to the User manual.
Forwarded calls are not logged under "Missed calls", but under "Forwarded" in the call log.
Administration via WBM (User menu)
User > Configuration > Call logging > General
User > Configuration > Call logging > Missed calls
Loading...