Siemens OpenStage 15 Administration Manual

Add to my manuals
284 Pages

advertisement

Siemens OpenStage 15 Administration Manual | Manualzz

Documentation

Asterisk

OpenStage 15, OpenStage 20, OpenStage 40,

OpenStage 60, OpenStage 80

Administration Manual

A31003-S2000-M102-2-76A9

Communication for the open minded

Siemens Enterprise Communications www.siemens.com/open

Communication for the open minded

Siemens Enterprise Communications www.siemens.com/open

Copyright © Siemens Enterprise

Communications GmbH & Co. KG 2007

Hofmannstr. 51, D-80200 München

Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG

Reference No.: A31003-S2000-M102-2-76A9

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

OpenScape, OpenStage and HiPath are registered trademarks of Siemens Enterprise

Communications GmbH & Co. KG.

All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.

Nur für den internen Gebrauch bkTOC.fm

Content

Content

0

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

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

1.2 Maintenance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.3 About the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.4 Conventions for this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.5 The OpenStage Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1.5.1 OpenStage 60/80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1.5.2 OpenStage 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

1.5.3 OpenStage 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.5.4 OpenStage 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1.6 Administration Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1.6.1 Web-based Management (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1.6.2 DLS (Deployment Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

1.6.3 Local Phone Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

2 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

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

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

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

2.2.3 Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.2.4 Connecting the Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.3 Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.3.1 Access the Web Interface (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.3.2 Set the Terminal Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.3.3 Basic Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.3.4 Date and Time / SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.3.5 SIP Server Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

2.3.6 Extended Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.3.7 Vendor Specific: VLAN Discovery And DLS Address . . . . . . . . . . . . . . . . . . . . . 2-11

2.3.8 Example DHCP server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

2.3.9 Registering At Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

2.3.10 Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

3 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

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

3.2 LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.2.1 LAN Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.2.2 VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.2.2.1 Automatic VLAN discovery using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.2.2.2 Automatic VLAN discovery using LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . 3-9

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

0-1

bkTOC.fm

Content

Nur für den internen Gebrauch

3.2.2.3 Manual configuration of a VLAN ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

3.2.3 LLDP-MED Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.3 IP Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.1 Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.1.1 Layer 2 / 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

3.3.1.2 Layer 3 / Diffserv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

3.3.2 Use DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

3.3.3 IP Address - Manual Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

3.3.4 Default Route/Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

3.3.5 Specific IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

3.3.6 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

3.3.6.1 DNS Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

3.3.6.2 DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

3.3.6.3 Customised DNS Name (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

3.3.7 Configuration & Update Service (DLS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.3.8 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.4.1 Terminal and User Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.4.1.1 Terminal Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.4.1.2 Display Identity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

3.4.2 Emergency and Voice Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

3.4.3 Energy Saving (OpenStage 40/60/80) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

3.4.4 Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

3.4.4.1 SNTP is available, but no automatic configuration by DHCP server . . . . . . . 3-34

3.4.4.2 No SNTP server available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

3.4.5 SIP Addresses and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

3.4.5.1 SIP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

3.4.5.2 SIP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

3.4.6 SIP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

3.4.7 SIP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

3.4.7.1 Outbound Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

3.4.7.2 SIP Transport Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

3.4.8 SIP Session Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44

3.4.9 Resilience and Survivability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

3.4.9.1 TLS Connectivity Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

3.4.9.2 Response Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

3.4.9.3 Non-INVITE Transaction Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48

3.4.9.4 Maximum Registration Backoff Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

3.4.9.5 Backup SIP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

3.5 Features - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3.5.1 Allow Refuse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3.5.2 Hot/Warm Phone (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

3.5.3 Initial Digit Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

3.5.4 Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

0-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch bkTOC.fm

Content

3.5.4.1 Transfer on Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

3.5.4.2 Transfer on Hangup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

3.5.5 Message Waiting Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59

3.5.6 Indicate Messages (V2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60

3.5.7 Server Based Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62

3.5.8 uaCSTA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63

3.5.9 Local Menu Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64

3.6 Programmable Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

3.6.1 Selected Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

3.6.2 Repeat Dialing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

3.6.3 Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.6.4 Ringer Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

3.6.5 Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

3.6.6 Alternate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

3.6.7 Blind Call Transfer / Move Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

3.6.8 Join Two Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.6.9 Deflect A Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.6.10 Shift Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68

3.6.11 Phone-Based Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

3.6.12 Accept Call Via Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

3.6.13 Do Not Disturb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.6.14 Repertory Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.6.15 Consult And Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

3.6.16 Toggle Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

3.6.17 Server Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

3.6.18 Monitoring Another Extension Via BLF Key . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

3.6.19 Send Request via HTTP/HTTPS (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73

3.6.20 Start application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.6.21 Clear (no feature assigned). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.6.22 Programmable Call Forwarding Key (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.6.23 Mute (OpenStage 15 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

3.6.24 Release (OpenStage 15 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

3.6.25 Key Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

3.7 Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

3.7.1 Canonical Dialing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

3.7.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83

3.7.3 Dial Plan (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

3.8 Distinctive Ringing (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

3.9 Transferring Phone Software, Application and Media Files . . . . . . . . . . . . . . . . . . . . 3-89

3.9.1 FTP/HTTPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89

3.9.2 Common FTP/HTTPS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89

3.9.3 Phone Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91

3.9.3.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91

3.9.3.2 Download/Update Phone Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

0-3

bkTOC.fm

Content

Nur für den internen Gebrauch

3.9.4 Music on Hold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94

3.9.4.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94

3.9.4.2 Download Music on Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96

3.9.5 Picture Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97

3.9.5.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97

3.9.5.2 Download Picture Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99

3.9.6 LDAP Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

3.9.6.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

3.9.6.2 Download LDAP Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102

3.9.7 Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103

3.9.7.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103

3.9.7.2 Download Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105

3.9.8 Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106

3.9.8.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106

3.9.8.2 Download Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108

3.9.9 Ringer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109

3.9.9.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110

3.9.9.2 Download Ringer File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112

3.9.10 HPT Dongle Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113

3.9.10.1 FTP/HTTPS Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113

3.9.10.2 Download Dongle Key File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115

3.10 Corporate Phonebook: Directory Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116

3.10.1 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116

3.11 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119

3.11.1 RTP Base Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119

3.11.2 Codec Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120

3.11.3 Audio Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122

3.12 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123

3.12.1 XML Applications/Xpressions (OpenStage 60/80) . . . . . . . . . . . . . . . . . . . . . . 3-123

3.12.1.1 Setup/Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123

3.12.1.2 HTTP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

3.12.1.3 Modify an Existing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129

3.12.1.4 Remove an Existing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130

3.12.1.5 Application Start by Program Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-131

3.13 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132

3.14 Troubleshooting: Lost Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133

3.15 Restart Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134

3.16 Factory Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135

3.17 SSH - Secure Shell Access (V2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136

3.18 Display License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137

3.19 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138

3.19.1 Display General Phone Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138

3.19.2 LAN Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139

3.19.3 LLDP-MED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140

0-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch bkTOC.fm

Content

3.19.4 IP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-142

3.19.5 Process and Memory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143

3.19.6 Fault Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145

3.19.7 Easy Trace Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152

3.19.7.1 Bluetooth Handsfree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152

3.19.7.2 Bluetooth Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152

3.19.7.3 Call Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153

3.19.7.4 Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153

3.19.7.5 LDAP Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154

3.19.7.6 DAS Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154

3.19.7.7 DLS Data Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154

3.19.7.8 802.1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

3.19.7.9 Help Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

3.19.7.10 Sidecar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

3.19.7.11 Key Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156

3.19.7.12 LAN Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156

3.19.7.13 Local Phonebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156

3.19.7.14 Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157

3.19.7.15 Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157

3.19.7.16 Phone administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157

3.19.7.17 Server based applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158

3.19.7.18 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158

3.19.7.19 Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158

3.19.7.20 USB Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158

3.19.7.21 Voice Dialling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-159

3.19.7.22 Web Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-159

3.19.7.23 No Tracing for All Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160

3.19.8 Bluetooth Advanced Traces (V2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-161

3.19.9 QoS Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-162

3.19.9.1 Conditions and Thresholds for Report Generation . . . . . . . . . . . . . . . . . . 3-162

3.19.9.2 View Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-165

3.19.10 Core dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-169

3.19.11 Remote Tracing - Syslog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-169

3.19.12 HPT Interface (For Service Staff) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-170

3.20 Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-171

4 Examples and HowTos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Canonical Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.1 Canonical Dialing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.2 Canonical Dial Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.1.2.1 Conversion examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4.2 How to Create Logo Files for OpenStage Phones. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4.2.1 For OpenStage 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4.2.2 For OpenStage 60/80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

4.3 How to Set Up the Corporate Phonebook (LDAP). . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

0-5

bkTOC.fm

Content

Nur für den internen Gebrauch

4.3.1 Prerequisites: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

4.3.2 Create an LDAP Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

4.3.3 Load the LDAP Template into the Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

4.3.4 Configure LDAP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

4.3.5 Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

4.4 An LLDP-Med Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

4.4.1 How To Set Up And Deploy A Dial Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

5 Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1.1 Web Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1.1.1 Menu Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1.1.2 Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5.1.2 Local Phone Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37

5.2 Troubleshooting: Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

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

0-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

uebersicht.fm

Overview

Important Notes

1

1.1

Overview

Important Notes

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

Q

For safety reasons the phone should only be operating using the supplied plug in power unit.

Use only original Siemens accessories!

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

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

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

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.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

1-1

uebersicht.fm

Overview

Maintenance Notes

1.2

Maintenance Notes

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

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

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

System Support.

1.3

About the Manual

The instructions within this manual will help you in administering and maintaining the Open-

Stage 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 SIP. 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 Siemens Enterprise Communications website

( http://www.enterprise-communications.siemens.com

) and on the Siemens Enterprise Wiki

( http://wiki.siemens-enterprise.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 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 "/".

1-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

uebersicht.fm

Overview

The OpenStage Family

4

5

1

2

3

8

9

6

7

10

1.5

1.5.1

1

The OpenStage Family

OpenStage 60/80

9

2

6

3

5

7

8

4

10

The Handset lets you pick up and dial calls in the usual manner.

The Graphics Display provides intuitive support for telephone operation.

The user-friendly Application Keys provide easy access to your telephone’s applications.

With the TouchGuide, the user/administrator can navigate in the various phone functions, applications, and configuration menus.

You can customize your telephone in line with your personal needs by assigning individual phone numbers and functions to the Program Keys.

Press the Function Keys to access frequently used telephony functions.

The Audio Keys let you optimize the audio settings on your telephone.

With the TouchSlider, the user can adjust the volume, e.g. of ringtones.

Inbound calls are visually signaled on the Call Display.

The Keypad is used for entering phone numbers and text.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

1-3

5

6

7

8

9

1

2

3

4 uebersicht.fm

Overview

The OpenStage Family

1.5.2

OpenStage 40

1

6

8

2

3

5

7

4

9

The Handset lets you pick up and dial calls in the usual manner.

The Graphics Display provides intuitive support for telephone operation.

The user-friendly Application Keys provide easy access to your telephone’s applications.

With the Navigation Key, the user/administrator can navigate in the various phone functions, applications, and configuration menus.

You can customize your telephone in line with your personal needs by assigning individual phone numbers and functions to the Program Keys.

Press the Function Keys to access frequently used telephony functions.

The Audio Keys let you optimize the audio settings on your telephone.

Inbound calls are visually signaled on the Call Display.

The Keypad is used for entering phone numbers and text.

1-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

uebersicht.fm

Overview

The OpenStage Family

1.5.3

OpenStage 20

2

1

3

4

4

5

6

1

2

3

5

6

The Handset lets you pick up and dial calls in the usual manner.

The Display provides intuitive support for telephone operation.

The user-friendly Application Keys provide easy access to your telephone’s applications.

Press the Function Keys to access frequently used telephony functions.

With the Navigation Key, the user/administrator can navigate in the various phone functions, applications, and configuration menus.

The Keypad is used for entering phone numbers and text.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

1-5

uebersicht.fm

Overview

Administration Interfaces

1.5.4

OpenStage 15

1

2

3 4

5

6

7

3

4

1

2

5

6

7

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

The Display provides intuitive support for telephone operation.

With the Audio Keys, the user can optimize the audio settings.

Press the Function Keys to access frequently used telephony functions.

The Keypad is used for entering phone numbers and text.

With the Navigation Keys, the user/administrator can navigate in the various phone functions, applications, and configuration menus.

The Program Keys enable the user to customize the telephone in line with his/her personal needs by assigning individual phone numbers and functions.

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 HTTP or HTTPS. It is applicable for remote configuration of individual IP phones in your network. Direct access to the phone is not required.

1-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

uebersicht.fm

Overview

Administration Interfaces

>

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

The remote configuration is not applicable while the phone is not in idle mode.

1.6.2

DLS (Deployment Service)

The Deployment Service (DLS) is a HiPath Management application for administering phones and soft clients in both HiPath and non-HiPath 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 an the OpenStage phone. Direct access to the phone is required.

>

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

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

1-7

uebersicht.fm

Overview

Administration Interfaces

1-8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

Startup

Prerequisites

2 Startup

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.

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.

• Asterisk SIP 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).

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-1

inbetriebnahme.fm

Startup

Assembling and Installing the Phone

2.2

Assembling and Installing the Phone

2.2.1

Shipment

• Phone

• Handset

• Handset cable

• Subpackage:

• Document "Information and Important Operating Procedures"

• Emergency number sticker

• Emergency Number Sticker

2.2.2

Connectors at the bottom side

OpenStage 60

Power supply

USB

Extension

Keyboard

PC

Switch

Headset

Key Module

Handset

2-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

Startup

Assembling and Installing the Phone

OpenStage 40 (OpenStage 15 and 20 similar, except

1

)

[1] OpenStage 40 andd

OpenStage 15 only

Power supply

PC

Switch

Headset

[1]

Key Module

[1]

Handset

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-3

inbetriebnahme.fm

Startup

Assembling and Installing the Phone

2.2.3

Assembly

1.

Handset

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

2.

Emergency Number Sticker

Write your telephone number and those for the fire and police departments on the included label and attach it to the telephone housing underneath the handset (see arrow).

2-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

Startup

Assembling and Installing the Phone

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

OpenStage 15

1

OpenStage 20 E

OpenStage 20

OpenStage 20 G

OpenStage 40

2

OpenStage 40 + 2nd Key Module

OpenStage 40 G

2

OpenStage 40 G + 2nd Key Module

OpenStage 60/80

3

OpenStage 60/80 + 2nd Key Module

OpenStage 60/80 G

3

OpenStage 60/80 G + 2nd Key Module

1 Includes 1 Key Module 15.

2 Includes 1 Key Module.

3 Includes 1 Key Module + USB-Extension with Acoustic Unit.

2.

Only if Power over Ethernet (PoE) is NOT supported:

Power Consumption/Supply

Power Class 1

Power Class 1

Power Class 1

Power Class 2

Power Class 2

Power Class 3

Power Class 3

External power unit required

Power Class 3

Power Class 3

Power Class 3

External power unit required

7

Use only the plug-in power supply unit fitting the OpenStage phone:

EU: C39280-Z4-C510

UK: C39280-Z4-C512

USA: C39280-Z4-C511

Plug the power supply unit into the mains. Connect the plug-in power supply unit to the jack at the bottom of the phone.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-5

inbetriebnahme.fm

Startup

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.

2-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

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.

>

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

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

>

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

2.3.1

Access the Web Interface (WBM)

1.

Open your web browser and enter the appropriate URL, which can be an IP address or a

DNS name, for example: https://192.168.1.15 or http://myphone.phones (firmware V2)

For configuring the phone’s DNS name, which is possible which firmware V2, please refer

to Section 3.3.6.3, “Customised DNS Name (V2)”.

The phone uses the standard port for HTTPS, 443.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-7

inbetriebnahme.fm

Startup

Quick Start

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.

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-8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

Startup

Quick Start

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 extension 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.4.1.1, “Terminal Identity”. With the WBM, the termi-

nal 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, the following parameters must be provided, preferably by DHCP:

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.3, “IP Address - Manual Configuration” for IP ad-

dress and subnet mask, and Section 3.3.4, “Default Route/Gateway” for the default route.

2.3.4

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 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.4.4, “Date and Time”.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-9

inbetriebnahme.fm

Startup

Quick Start

2.3.5

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.4.5.1, “SIP Addresses”.

2-10

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

Startup

Quick Start

2.3.6

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.5, “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.6.1, “DNS Domain Name”.

2.3.7

Vendor Specific: VLAN Discovery And DLS Address

>

The VLAN ID can also be configured by LLDP-MED (see Section 3.2.2.1, “”).

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.1, “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.7, “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.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-11

inbetriebnahme.fm

Startup

Quick Start

2.3.8

Example DHCP server configuration

The following description demonstrates by example how a DHCP server can be configured in order to build up a working infrastructure for OpenStage phones.

The configuration example is tested with ISC DHCP server version 3 running on Debian Linux

(packagename: dhcp3-server).

On startup, the OpenStage phone sends a DHCP discovery message which contains the vendor-class-identifier option. The fixed value is OptiIpPhone. This identifier is used by the DHCP server to send a specified set of sub-options to each OpenStage phone by means of vendor encapsulated options. The vendor-encapsulated-options option allows for defining custom-made options in either a single series of bytes or a sequence of parameters which is structured as follows: 1) single-byte vendor-specific option code; 2) single-byte length indication for the option data (the length does not include itself or the option code); 3) the data itself in as many bytes of data as are specified in the length indication.

The value of the vendor-encapsulated-options option can either be set directly by coding the bytes in hexadecimal notation, or, preferably, by using the option space statement.

This statement is available with ISC DHCP 3.0.

To assign the specific vendor-encapsulated-options to the appropriate devices, the use of classes is recommended. In the example, the class vendor-classes is divided into subclasses automatically for each vendor-class-identifier option that is received from the clients. As OpenStage phones send the value

OptiIpPhone, the specifications for theses phones are defined in the correpsonding sub-class.

2-12

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

inbetriebnahme.fm

Startup

Quick Start

Example dhcpd.conf

# General configuration for all clients in the subnet subnet 192.168.2.0 netmask 255.255.255.0 {

option domain-name-servers 192.168.2.2;

option broadcast-address 192.168.2.255;

option routers 192.168.2.251;

option subnet-mask 255.255.255.0;

option domain-name "phones.intranet";

option ntp-servers 192.43.244.18;

option time-offset 3600;

default-lease-time 864000;

max-lease-time 8640000;

}

# Set up an option space to contain the vendor-encapsulated options option space OpenStage; option OpenStage.vendor code 1 = string; option OpenStage.vlanid code 2 = unsigned integer 32; option OpenStage.dls code 3 = string;

# Each vendor-class-identifier will constitute a class class "vendor-classes" {

match option vendor-class-identifier;

}

# Specifications for OpenStage phones subclass "vendor-classes" "OptiIpPhone" {

vendor-option-space OpenStage;

option OpenStage.vendor "Siemens";

option OpenStage.vlanid 4;

option OpenStage.dls "sdlp://192.168.2.103:18443";

option sip-server 192.168.2.117;

}

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-13

inbetriebnahme.fm

Startup

Quick Start

2.3.9

Registering At Asterisk

For registration at the Asterisk SIP server, a SIP user ID and passwort must be provided by the

phone. The following procedure describes the configuration using the web interface (see Section 2.3.1, “Access the Web Interface (WBM)”; if the web interface is not applicable, please refer

to Section 3.4.6, “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 Asterisk server. If not provided by DHCP or a provisioning service, enter the appropriate values. If the phone is to register with a gateway, enter the appropriate SIP Gateway

address.

3.

In the Server type field, select "other".

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.

2-14

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2.3.10

Startup Procedure

The following flowchart shows the startup process for OpenStage phones: inbetriebnahme.fm

Startup

Quick Start

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

2-15

inbetriebnahme.fm

Startup

Quick Start

2-16

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

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 in-

terface, please refer to Section 2.3.1, “Access the Web Interface (WBM)”.

3.1

Access via Local Phone

>

The data entered in input fields is parsed and controlled by the phone. Thus, data is accepted only if it complies to the value range.

1.

Access the Administration Menu

OpenStage 60/80:

The v

key toggles between the Settings menu, the Applications menu, and the applications currently running. Press the v

key repeatedly until the "Settings" tab is active. (The v

key toggles between the Settings menu, the Applications menu, and the applications currently running.)

OpenStage 15/20/40:

Press the keys

D

, l

, and i consecutively to select the administration 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 pass-

word (see Section 3.13, “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) -> (ABC) -> back to start.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-1

administration.fm

Administration

Access via Local Phone

3.

Navigate within the Administration Menu

OpenStage 60/80

Use the TouchGuide to navigate and execute administrative actions in the administration menu.

Press the

- scroll up m

key briefly:

Press the i

key:

- confirm entries

Press the h

key:

- cancel a function

Press the g

key:

- open a context menu

Press the l

key briefly:

- scroll down

Run your finger around the sensor ring

W:

- browse lists and menus

- set up volume

OpenStage 40

Use the 5-way Navigator to navigate and execute administrative actions in the administration menu.

Press the

- scroll up m

Hold down: key briefly:

- scroll to top of list

Press the h

key:

- cancel a function

- delete character left of cursor

- up one level

Press the l

key briefly:

- scroll down

Hold down:

- scroll to end of list

Press the i

key:

- confirm entries

- perform an action

Press the g

key:

- open a context menu

- down one level

3-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Access via Local Phone

OpenStage 20

Use the 3-way Navigator to navigate and execute administrative actions in the administration menu.

Press the

- scroll up m

key briefly:

Hold down:

- scroll to top of list

Press the l

key:

- confirm entries

- perform an action

Press the l

- scroll down

Hold down:

key briefly:

- scroll to end of list

OpenStage 15

Press the

- scroll up m

key briefly:

Press the i

key:

- confirm entries

- perform an action

Press the l

key:

In idle mode:

- Open idle menu

In lists and menues:

- scroll down

4.

Select a parameter

If a parameter is set by choosing a value from a selective list, an arrow symbol appears in the parameter field that has the focus. Press the 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.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-3

administration.fm

Administration

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:

Element with focus

Letters, digits, punctuation marks or special characters

Command line

Copy contents of active field to clipboard

Insert clipboard contents at cursor position

Move cursor left/right

Shift to punctuation and special characters

Shift to numeric entry

Shift to upper/lower case

Additionally, you can use the following keys on the keypad as shortcuts for the selection of character groups

Element

*

#

Function

Switch to punctuation and special characters.

Toggle between lowercase characters, uppercase characters, and digits.

OpenStage 15/20/40

With the OpenStage 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 .

3-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

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

>

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. If the phone is set up to manually configure the switch port settings, the cable detection mechanism is disabled. In this case, care must be taken to use the correct cable type.

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 half duplex" , "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 half duplex" , "1 Gbps full duplex"

Default: "Automatic".

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

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

Default: "disabled".

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-5

administration.fm

Administration

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

|

--- Administration

|

--- Network

|

--- Port Configuration

|--- LAN port type

|--- PC port status

|--- PC port type

|

--- PC port autoMDIX

3-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

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).

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

>

The implementation of a voice network based on VLANs requires the network infrastructure (the switch fabric) to support VLANs.

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 possible to assign one device, i.e. one MAC address, to different VLANs.

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

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-7

administration.fm

Administration

LAN Settings

3.2.2.1

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". This is the default configuration.

The DHCP server must be configured to supply the Vendor Unique Option in the correct Siemens 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 > IP configuration

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

Network > IP configuration > change mode

To enable VLAN discovery by DHCP, select DHCP used in the Discovery mode menu. Afterwards, click Submit.

3-8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

LAN Settings

Administration via Local Phone

To enable VLAN discovery by DHCP, select DHCP used in the Discovery mode menu.

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- Discovery mode

3.2.2.2

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 > IP configuration

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

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-9

administration.fm

Administration

LAN Settings

Network > IP configuration > change mode

To enable VLAN discovery by LLDP-MED, select LLDP-MED with DHCP in the Discovery

mode menu. Afterwards, click Submit.

Administration via Local Phone

To enable VLAN discovery by DHCP, select LLDP-MED with DHCP in the Discovery mode menu.

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- Discovery mode

3-10

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

LAN Settings

3.2.2.3

Manual configuration of a VLAN ID

To configure layer 2 VLAN manually, first make shure that VLAN discovery is set to "Manual"

(see Section 3.2.2.1, “Automatic VLAN discovery using DHCP”). Then, the phone must be pro-

vided 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 > IP configuration

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

Network > IP configuration > change mode

To enable manual VLAN configuration, select Manual settings in the Discovery mode menu.

Afterwards, click Submit.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-11

administration.fm

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 (Manegement 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 4.4, “An

LLDP-Med Example”.

Administration via WBM

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- LLDP-MED operation

|

--- TTL

3-12

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

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.

>

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

3.19.3, “LLDP-MED”). If so, the value can not be changed by any other interface.

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.

Three Bits Used for CoS

(User Priority)

PREAM.

SFD DA SA

TAG

4 Bytes

PT DATA FCS

Data required

Layer 2: Activates or deactivates QoS on layer 2.

Value range: "Yes", "No".

Default: "Yes".

Layer 2 voice: Sets the CoS (Class of Service) value for voice data (RTP streams).

Value range: 0-7.

Default: 5.

Layer 2 signalling: Sets the CoS (Class of Service) value for signaling.

Value range: 0-7.

Default: 3.

Layer 2 default: Sets the default CoS (Class of Service) value.

Value range: 0-7.

Default: 0.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-13

administration.fm

Administration

IP Network Parameters

Administration via WBM

Network > QoS

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- QoS

|

--- Service

|--- Layer 2

|--- Layer 2 voice

|--- Layer 2 signalling

|

--- Layer 2 default

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 "0 0 0 0 0 0".

2.

Expedited Forwarding (EF referred to RFC 3246)

Expedited Forwarding is used for voice (RTP streams) by default. It effectively creates a special low-latency path in the network. The DSCP (Diffserv Codepoint) value for EF is

"1 0 1 1 1 0".

3.

Assured Forwarding (AF referred to RFC 2597)

Assured forwarding is used for signaling messages by default (AF31). It is less stringent than EF in a multiple dropping system. The AF values are containing two digits X and Y

(AFXY), where X is describing the priority class and Y the drop level.

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

3-14

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

IP Network Parameters

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: "AF11", "AF12", "AF13", "AF21", "AF22", "AF23", "AF31", "AF32", "AF33",

"AF41", "AF42", "AF43", "EF", "CS7", "CS3", "CS4", "CS5"

Default: "EF"

Layer 3 signalling: Sets the CoS (Class of Service) value for signaling.

Value range: "AF11", "AF12", "AF13", "AF21", "AF22", "AF23", "AF31", "AF32", "AF33",

"AF41", "AF42", "AF43", "EF", "CS7", "CS3", "CS4", "CS5"

Default: "AF31"

Administration via WBM

Network > QoS

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- QoS

|

--- Service

|--- Layer 3

|--- Layer 3 voice

|

--- Layer 3 signalling

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-15

administration.fm

Administration

IP Network Parameters

3.3.2

Use DHCP

For an example configuration, see Section 2.3.8, “Example DHCP server configuration”.

If this parameter is set to "Yes", 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)

• SNTP IP Address (NTP Server option 42)

• Timezone offset (Time Server Offset option 2)

• Primary/Secondary IP Addresses (DNS Server option 6)

• DNS Domain Name (DNS Domain option 15)

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

• Vendor Unique (option 43)

3-16

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via WBM

Network > IP configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- Use DHCP administration.fm

Administration

IP Network Parameters

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-17

administration.fm

Administration

IP Network Parameters

3.3.3

IP Address - Manual Configuration

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

Data required

IP address: used for addressing the phone.

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

Administration via WBM

Network > IP configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|--- IP address

|

--- Subnet mask

3-18

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

IP Network Parameters

3.3.4

Default Route/Gateway

If not provided by DHCP dynamically (see Section 3.3.2, “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 > IP configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- Route (default)

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-19

administration.fm

Administration

IP Network Parameters

3.3.5

Specific IP Routing

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

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 > IP configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|--- Route 1 IP

|--- Route 1 gateway

|--- Route 1 mask

|--- Route 2 IP

|--- Route 2 gateway

|

--- Route 2 mask

3-20

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

IP Network Parameters

3.3.6

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 nameservers needed for DNS resolving.

3.3.6.1

DNS Domain Name

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

Administration via WBM

Network > IP configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- DNS domain

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-21

administration.fm

Administration

IP Network Parameters

3.3.6.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 > IP configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- IP Configuration

|--- Primary DNS

|

--- Secondary DNS

3-22

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

IP Network Parameters

3.3.6.3

Customised DNS Name (V2)

With OpenStage firmware V2, the phone’s hostname for registration with the DNS server can be customised. The phone will send the specified hostname to the DNS server using DDNS.

Therefore, the DNS server must support DDNS.

The corresponding DNS domain is configured in Network > IP configuration > DNS domain

(see Section 3.3.6.1, “DNS Domain Name”).

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

>

It is recommended to inform the user about the DNS name of his/her phone. The complete WBM address can be found under User menu > Network information >

Web address.

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

• "None": The phone does not attempt to change its DNS name via DDNS.

• "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.4.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

|

--- Administration

|

--- Identity

|--- Web name

|

--- DDNS hostname

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-23

administration.fm

Administration

IP Network Parameters

3.3.7

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 opti-

Point 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 DLS port, i.e. the port on which the DLS server is listening, are required to enable proper communication between phone and DLS.

The Contact gap parameter controls a security function. It specifies a minimum time interval that must elapse between individual HTTP requests from the phone which are responding to a

ContactMe request from the DLS. The ContactMe request is sent by the DLS each time the

DLS wants to execute an action on the phone, e. g. software deployment, or a configuration change. Any requests coming within that time will be ignored. The purpose is to prevent DoS

(Denial of Service) attacks on the phone.

The Security 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.

>

With firmware V2, 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.

Data required

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

DLS port: Port on which the DLS Deployment Service is listening.

Default: 18443.

Contact gap: Minimum time interval in seconds that must elapse between responses to a

ContactMe request from the DLS, in order to prevent DoS attacks.

Default: 300.

3-24

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

IP Network Parameters

Security mode / Security status: Determines whether the communication between the phone and the DLS is secure.

Value range: "Default mode", "Secure mode".

Default: "Default".

Administration via WBM

Network > Update Service (DLS)

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- Update Service (DLS)

|--- DLS address

|--- DLS port

|--- Contact gap

|

--- Security status

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-25

administration.fm

Administration

IP Network Parameters

3.3.8

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.

3-26

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

IP Network Parameters

Trap community: SNMP community string for the SNMP manager receiving TRAP messages.

Default: "snmp".

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

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

Diagnostic sending enabled: Enables or disables the sending of diagnostic data to the

SNMP manager.

Value range: "Yes", "No".

Default: "No".

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

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

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

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 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 / QoS to generic device: Enables or disables the sending of

QoS traps to a generic destination.

Value range: "Yes", "No".

Default: "No".

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-27

administration.fm

Administration

IP Network Parameters

Administration via WBM

System > SNMP

3-28

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via Local Phone

|

--- Administration

|

--- 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 device administration.fm

Administration

IP Network Parameters

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-29

administration.fm

Administration

System Settings

3.4

3.4.1

3.4.1.1

System Settings

Terminal and User Identity

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

|

--- Administration

|

--- System

|

--- Identity

|--- Terminal number

|

--- Terminal name

3-30

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

3.4.1.2

Display Identity

If an individual name oder 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 or Terminal name.

Administration via WBM

System > System Identity

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Identity

|--- Display identity

|

--- Enable ID

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-31

administration.fm

Administration

System Settings

3.4.2

Emergency and Voice Mail

It is important to have an Emergency number configured. If the phone is locked, a clickable area for making an emergency call is created.

>

If more than one emergency number is needed, additional numbers can be configu-

red in the canonical dial settings (Section 3.7.1, “Canonical Dialing Configuration”).

If a mailbox located at a remote server shall be used, its Voice mail number must be entered.

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|--- Emergency number

|

--- Voicemail number

3-32

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

3.4.3

Energy Saving (OpenStage 40/60/80)

After the phone has been inactive within the timespan specified here, the display backlight is switched off. The length of this timespan ranges from 2 hours to 8 hours. The default value is

3 hours.

Administration via WBM

Local functions > Energy saving

Administration via Local Phone

|

--- Administration

|

--- Local Functions

|

--- Energy saving

|

--- Backlight timeout

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-33

administration.fm

Administration

System Settings

3.4.4

Date and Time

If the DHCP server in your network provides the IP address of the SNTP server, no manual configuration is necessary. If not, you have to set the SNTP IP address parameter manually.

For correct display of the current time, the Timezone offset must be set appropriately. This is the time offset from UTC (Coordinated Universal Time). If, for instance, the phone is located in

Munich, Germany, the offset is +1 (or simply 1); if it is located in Los Angeles, USA, the offset is -8. For countries or areas with half-our time zones, like South Australia or India, non-integer values can be used, for example 10.5 for South Australia (UTC +10:30).

If the phone is located in a country with daylight saving, the administrator can choose whether daylight saving time is activated manually or automatically. If Daylight saving is enabled, and

Auto time change is disabled, daylight saving time (DST) is in effect immediately. If Auto time

change is enabled, daylight saving is controlled by the Time zone parameter. This selects the daylight saving time zone which is characterized by the start and end date for daylight saving time.

The Difference (minutes) provides the time difference for daylight saving time in minutes. This parameter is required also when Auto time change is enabled. In Germany, for instance, as in most countries, this is +60.

3.4.4.1

SNTP is available, but no automatic configuration by DHCP server

Data required

SNTP IP address: IP address or hostname of the SNTP server.

Timezone offset (hours): Shift in hours corresponding to UTC.

Daylight saving: Enables or disables daylight saving time in conjunction with Auto time

change.

Value range: "Yes", "No".

Difference (minutes): Time difference when daylight saving time is in effect.

Auto time change / Auto DST: Enables or disables automatic control of daylight saving time according to the Time zone.

Value range: "Yes", "No".

Time zone / DST zone: Area with common start and end date for daylight saving time.

Value range: "Australia 2007 (ACT, South Australia, Tasmania, Victoria)", "Australia 2007

(New South Wales)", "Australia (Western Australia)", "Australia 2008+ (ACT, New South

Wales, South Australia, Tasmania, Victoria)", "Brazil", "Canada", "Canada (Newfoundland)", "Europe (Portugal, United Kingdom)", "Europe (Finland)", "Europe (Rest)", "Mexico", "United States".

3-34

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via WBM

Date and Time

Administration via Local Phone

|

--- Administration

|

--- Date and Time

|--- SNTP IP address

|

--- Timezone offset administration.fm

Administration

System Settings

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-35

administration.fm

Administration

System Settings

3.4.4.2

No SNTP server available

If no SNTP server is available, date and time must be set manually.

>

The manual setting of time and tate is located in the user menu, not in the administrator menu.

Data required

Local time (hh:mm): Local time.

Local date (day, month, year): Local date.

Allow daylight saving: Defines whether there is daylight is set.

Difference (minutes): Timezone offset in minutes.

Administration via WBM

(User pages >) Date and time

Administration via Local Phone

|

--- Menu

|

--- Date and Time

|--- Time

|--- Date

|--- Daylight saving

|

--- Difference (mins)

3-36

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

3.4.5

SIP Addresses and Ports

3.4.5.1

SIP Addresses

In this group of parameters, the IP addresses or host names for the SIP server, the SIP registrar, and the SIP gateway are defined.

SIP server address provides the IP address or host name of the SIP proxy server. This is necessary for outgoing calls. SIP registrar address contains the IP address or host name of the registration server, to which the phone will send REGISTER messages. When registered, the phone is ready to receive incoming calls. SIP gateway address gives the IP address or host name of the SIP gateway. A SIP gateway is able to perform a conversion of SIP to TDM, which enables to send calls directly into the public network.

Data required

SIP server address: IP address or host name of the SIP proxy server.

SIP registrar address: IP address or host name of the registration server.

SIP gateway address: IP address or host name of the SIP gateway.

Administration via WBM

System > Registration

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-37

administration.fm

Administration

System Settings

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Registration

|

--- SIP Addresses

|--- SIP server

|--- SIP registrar

|

--- SIP gateway

3.4.5.2

SIP Ports

In this group of parameters, the ports for the SIP server, the SIP registrar, and the SIP gateway

are defined (for further information see Section 3.4.5.1, “SIP Addresses”), as well as the SIP

port used by the phone (SIP local).

Data required

SIP server: Port of the SIP proxy server.

Default: 5060.

SIP registrar: Port of the server at which the phone registers.

Default: 5060.

SIP gateway: Port of the SIP gateway.

Default: 5060.

SIP local: Port used by the phone for sending and receiving SIP messages.

Default: 5060.

Administration via WBM

Network > Port configuration

3-38

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- Port Configuration

|--- SIP server

|--- SIP registrar

|--- SIP gateway

|

--- SIP local

3.4.6

SIP Registration

Registration is the process by which centralized SIP Server/Registrars become aware of the existence and readiness of an endpoint to make and receive calls. The phone supports a number of configuration parameters to allow this to happen. Registration can be authenticated or un-authenticated depending on how the server and phone is configured.

For operation with an Asterisk server, set Server type to "Other". The expiry time of a registration can be specified by Registration timer.

Unauthenticated Registration

For unauthenticated registration, the following parameters must be set on the phone: Terminal

number or Terminal name (see Section 3.4.1.1, “Terminal Identity”), SIP server and SIP regis-

trar address (see Section 3.4.5.1, “SIP Addresses”).

In unauthenticated mode, the server must pre-authenticate the user. This procedure is server specific and is not described here.

Authenticated Registration

The phone supports the digest authentication scheme and requires some parameters to be configured in addition to those for unauthenticated registration. By providing a User ID and a

Password which match with a corresponding account on the SIP registrar, the phone authenticates itself. Optionally, a Realm can be added. This parameter specifies the protection domain wherein the SIP authentication is meaningful. The protection domain is globally unique, so that each protection domain has its own arbitrary user names and passwords.

>

A challenge from the server for authentication information is not only restricted to the

REGISTER message, but can also occur in response to other SIP messages, e. g.

INVITE.

>

If registration has not succeeded at startup or registration fails after having been previously successfully registered the phone will try to re-register every 30 seconds.

This is not configurable.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-39

administration.fm

Administration

System Settings

Data required

Registration timer (seconds): Expiry time of the registration in seconds.

Default value: 3600.

Server type: Type of server the phone will register to.

Value range: "Other", "OS Voice".

Default value: "OS Voice".

Realm: Protection domain for authentication.

User ID: Username required for an authenticated registration.

Password: Password required for an authenticated registration.

Administration via WBM

System > Registration

3-40

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Registration

|

--- SIP Session

|--- Registration timer

|--- Server type

|--- Realm

|--- User ID

|

--- Password administration.fm

Administration

System Settings

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-41

administration.fm

Administration

System Settings

3.4.7

SIP Communication

3.4.7.1

Outbound Proxy

If this option set to "Yes", the phone routes outbond requests to the configured proxy. The outbound proxy will fulfill the task of resolving the domain contained in the SIP request. If "No" is set, the phone will attempt to resolve the domain by itself.

If a Default OBP (Outbound Proxy) domain is set and the number or name dialed by the user does not provide a domain, this value will be appended to the name or number. Otherwise, the domain of the outbound proxy will be appended.

Data required

Outbound proxy: Determines whether an outbound proxy is used or not.

Value range: "Yes", "No".

Default: "No".

Default OBP domain: Alternative value for the domain that is given in the outbound request.

Administration via WBM

System > SIP interface

Administration via Local Phone

|

--- Administration

|

--- System

|

--- SIP Interface

|--- Outbound proxy

|

--- Default OBP domain

3-42

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

3.4.7.2

SIP Transport Protocol

Selects the transport protocol to be used for SIP messages. The values "UDP", "TCP", and

"TLS" are available. The default is "UDP".

>

If TLS is to be used, please ensure that the SIP over TLS connection between phones and sever work properly.

Administration via WBM

System > SIP interface

Administration via Local Phone

|

--- Administration

|

--- System

|

--- SIP Interface

|

--- SIP transport

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-43

administration.fm

Administration

System Settings

3.4.8

SIP Session Timer

Session timers provide a basic keep-alive mechanism between 2 user agents or phones. This mechanism can be useful to the endpoints concerned or for stateful proxies to determine that a session is still alive. This is achieved by the phone sending periodic re-INVITEs to keep the session alive. If no re-INVITE is received before the interval passes, the session is considered terminated. Both phones are supposed to terminate the call, and stateful proxies can remove any state for the call.

This feature is sufficiently backward compatible such that only one end of a call needs to implement the SIP extension for it to work.

The parameter Session timer enabled determines whether the mechanism shall be used, and

Session duration (seconds) sets the expiration time, and thus the interval between refresh re-INVITEs.

>

Some server environments support their own mechanism for auditing the health of a session. In these cases, the Session timer must be deactivated.

Data required

Session timer enabled: Activates or deactivates the session timer mechanism.

Value range: "Yes", "No".

Default value: "No".

Session duration (seconds): Sets the expiration time for a SIP session.

Default: 3600.

3-44

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

Administration via WBM

System > Registration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Registration

|

--- SIP session

|--- Session timer

|

--- Session duration

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-45

administration.fm

Administration

System Settings

3.4.9

Resilience and Survivability

To allow for a stable operation even in the presence of network or server failure, OpenStage phones have the capability to switch to a fallback system. The switchover is controlled by various configurable check and timeout intervals.

In survivability mode, it is expected that some features and functionality will not be available.

The user will be informed by a message in the Call View display.

3.4.9.1

TLS Connectivity Check

A regular check ensures that the TLS link to the main SIP server is active. When the Connec-

tivity check timer is set to a non-zero value, test messages will be sent at the defined interval.

If the link is found to be dead, the phone uses DNS SRV to find another SIP server.

>

If TLS is to be used, please ensure that the SIP over TLS connection between phones and sever work properly.

Administration via WBM

System > SIP interface

3-46

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

3.4.9.2

Response Timer

The Call trans timer is started whenever the phone sends a new INVITE message to the SIP server.

If the call transaction timer expires before the phone gets a response from the SIP server, the phone assumes that the server had died and then attempts to contact the backup server, if configured. If there is no backup server configured, the phone just tidies up internally.

The data is given in milliseconds. The default value is 32 000.

Administration via WBM

System > SIP interface

Administration via Local Phone

|

--- Administration

|

--- System

|

--- SIP Interface

|

--- Response timer (ms)

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-47

administration.fm

Administration

System Settings

3.4.9.3

Non-INVITE Transaction Timer

The NonCall trans timer is started whenever the phone sends a non-INVITE message to the

SIP server. If the timer expires before the phone gets a response from the SIP server, the phone assumes that the server had died and then attempts to contact the backup server, if configured. If no backup server is configured, the phone just tidies up internally.

The data is given in milliseconds. The default value is 32 000.

Administration via WBM

System > SIP interface

Administration via Local Phone

|

--- Administration

|

--- System

|

--- SIP Interface

|

--- NonCall transactions (ms)

3-48

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

System Settings

3.4.9.4

Maximum Registration Backoff Time

If a registration attempt should result in a timeout, the phone waits a random time before sending another REGISTER message. The Reg. backoff (seconds) parameter determines the maximum waiting time.

Administration via WBM

System > SIP interface

Administration via Local Phone

|

--- Administration

|

--- System

|

--- SIP Interface

|

--- Reg. backoff

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-49

administration.fm

Administration

System Settings

3.4.9.5

Backup SIP Server

The Backup registration flag indicates whether or not the phone treats the backup proxy server as a SIP registrar. If set to "Yes", the phone tries to register its SIP address with the server whose IP address or hostname is specified by Backup proxy address.

The Backup registration timer determines the duration of a registration with the SIP server.

The Backup transport option displays the current transport protocol used to carry SIP messages to the Backup proxy server.

The Backup OBP flag indicates whether or not the Backup proxy server is used as an outbound proxy.

Data required

Backup registration allowed / Backup registration flag: Determines whether or not the backup proxy is used as a SIP Registrar.

Value Range: "Yes", "No".

Default: "Yes".

Backup proxy address: IP address or hostname of the backup proxy server.

Backup registration timer: Expiry time of the registration in seconds.

Default: 3600.

Backup transport: Transport protocol to be used for messages to the backup proxy.

Value range: "TCP", "UDP", "TLS".

Default: "UDP".

Backup OBP flag: Determines whether or not the backup proxy is used as an outbound proxy.

Value range: "Yes", "No".

Default: "No".

• Network > Port Configuration > Backup proxy: Port of the backup proxy server.

Default: 5060.

3-50

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via WBM

System > Registration

Network > Port configuration administration.fm

Administration

System Settings

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-51

administration.fm

Administration

System Settings

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Registration

|

|

--- SIP Session

--- SIP Survivability

|--- Backup registration flag

|--- Backup proxy address

|--- Backup transport

|

--- OBP flag

|

--- Administration

|

--- Network

|

--- Port Configuration

|

--- Backup proxy

3-52

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Features - Configuration

3.5

Features - Configuration

3.5.1

Allow Refuse

This parameter defines whether the Refuse Call feature is available on the phone. The possible values are "Yes" or "No". The default is "Yes".

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|

--- Allow refuse

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-53

administration.fm

Administration

Features - Configuration

3.5.2

Hot/Warm Phone (V2)

With firmware version V2, hot/warm phone functionality is available. If the phone is configured as hot phone, the number specified in Hot warm destination is dialed immediately when the user goes off-hook. For this purpose, Hot warm phone must be set to "Hot phone". If set to

"Warm phone", the specified destination number is dialed after a delay which is defined in Au-

todial delay (seconds) in the user menu. During the delay period, the user can dial a number which will be used instead of the hot/warm destination. In addition, the user will be provided with a dial tone during the delay period. With the setting "No action", hot phone or warm phone functionality is disabled.

Administration via WBM

System > Features > Configuration

(User menu) > Configuration > Outgoing calls

3-54

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|--- Hot / warm phone

|

--- Hot / warm destination

|

--- User

|

--- Configuration

|

--- Outgoing calls

|

--- Autodial delay administration.fm

Administration

Features - Configuration

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-55

administration.fm

Administration

Features - Configuration

3.5.3

Initial Digit Timer

This timer is started when the user goes off-hook, and the dial tone sounds. When the user has not entered a digit until timer expiry, the dial tone is turned off, and the phone changes to idle mode. The Initial digit timer (seconds) parameter defines the duration of this timespan.

Administration via WBM

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|

--- Initial digit timer

3-56

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Features - Configuration

3.5.4

Call Transfer

3.5.4.1

Transfer on Ring

If this function is active, a call can be transferred after the user has dialled the third participant’s number, but before the third party has answered the call. This feature is enabled or disabled in the User menu. The default is "Yes".

Administration via WBM

(User) Configuration > Outgoing calls

Administration via Local Phone

|

--- User

|

--- Configuration

|

--- Outgoing calls

|

--- Transfer on ring

3.5.4.2

Transfer on Hangup

This feature applies to the following scenario: While A is talking to B, C calls A. A accepts the call, so B is on hold and the call between A and C is active. If Transfer on hangup is enabled, and A goes on-hook, B gets connected to C. If disabled, C will be released when A hangs up, and A has the possibility to reconnect to B. By default, the feature is disabled.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-57

administration.fm

Administration

Features - Configuration

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|

--- Transfer on hangup

3-58

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Features - Configuration

3.5.5

Message Waiting Address

The MWI (Message Waiting Indicator) is an optical signal which indicates that voicemail messages are on the server. Depending on the SIP server / gateway in use, the Message waiting

server address, that is the address or host name of the server that sends message waiting notifications to the phone, must be configured.

With Asterisk, this setting is not typically necessary for enabling MWI functionality.

Administration via WBM

System > Features > Services

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Addressing

|

--- MWI server URI

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-59

administration.fm

Administration

Features - Configuration

3.5.6

Indicate Messages (V2)

With firmware version V2, the indication of old and new messages on the display can be configured. There are 4 categories of voicemail messages: new, new urgent, old, and old urgent.

For each category, the administrator can define whether the message count is shown or hidden, and set a header for the category.

Data required

New items: Determines whether new items are indicated.

Fixed Value: "Show".

Alternative label: Label for new items.

New urgent items: Determines whether new urgent items are indicated.

Value range: "Show", "Hide".

Alternative label: Label for new urgent items.

Old items: Determines whether new urgent items are indicated.

Value range: "Show", "Hide".

Alternative label: Label for old items.

Old urgent items: Determines whether old urgent items are indicated.

Value range: "Show", "Hide".

Alternative label: Label for old urgent items.

Administration via WBM

Local functions > Messages settings

3-60

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via Local Phone

|

--- Administration

|

--- Locatl functions

|

--- Messages settings

|--- New items

|--- Alternative label

|--- New urgent items

|--- Alternative label

|--- Old items

|--- Alternative label

|--- Old urgent items

|

--- Alternative label administration.fm

Administration

Features - Configuration

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-61

administration.fm

Administration

Features - Configuration

3.5.7

Server Based Features

The use of server based call forwarding is enabled or disabled here. When DND and phone based call forwarding are to be used, Server features must be deactivated. This is the default setting. For using server based Call Forwarding, it must be activated.

>

Before switching Server features on or off, please ensure that Call Forwarding is not activated. Otherwise, the user will not be able to control the feature any more.

It is recommended to set Server features when setting up the phone, and avoid further changes, as possible.

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|

--- Server features

3-62

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Features - Configuration

3.5.8

uaCSTA Interface

User Agent CSTA (uaCSTA) is a limited subset of the CSTA protocol, which allows external

CTI applications to interact with the phone.

If Allow uaCSTA is enabled, applications which support the uaCSTA standard will have access to the OpenStage phone. The default is "Yes".

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|

--- Allow uaCSTA

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-63

administration.fm

Administration

Features - Configuration

3.5.9

Local Menu Timeout

The timeout for the local user and admin menu is configurable. When the time interval is over, the menu is closed and the administrator/user is logged out.

The timeout may be helpful in case a user does a long press on a program key unintentionally, and thereby invokes the key configuration menu. The menu will close after the timeout, and the key will return to normal line key operation.

The timeout ranges from 1 to 5 five minutes. The default value is 2.

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- General

|

--- Not used timeout

3-64

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

3.6

Programmable Keys

OpenStage 15/40/60/80 phones feature freely programmable keys (FPKs) which can be associated with special phone functions.

In the Administrator pages of the WBM, the program keys menu can be accessed via System

> Features > Program keys.

At the phone, the configuration menu for a specific key is called by a long press on the related key.

The functions available and their parameters are described in the following sub-sections.

3.6.1

Selected Dialing

On key press, a pre-defined call number is called.

The label displayed to the left of the key is defined in Key label <key number>.

The call number defined in the Dial number parameter is dialed on key press.

Administration via WBM

System > Features > Program keys > Selected dialling

3.6.2

Repeat Dialing

On key press, the call number that has been dialed lastly is dialed again.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Repeat dialling

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-65

administration.fm

Administration

Programmable Keys

3.6.3

Call Forwarding

This key function controls phone based call forwarding. If forwarding is enabled, the phone will forward incoming calls to the predefined call number, depending on the current situation.

>

To use phone based call forwarding, Server features must be switched off (see Section 3.5.7, “Server Based Features”).

The label displayed to the left of the key is defined in Key label <key number>.

The Forwarding type parameter determines the forwarding behaviour. If "All calls" is selected, any incoming call will be forwarded. If "On no reply" is set, the call will be forwarded when the user has not answered within a specified timespan. The timespan is configured in the WBM user pages under Configuration > Incoming calls > Forwarding > No replay delay (seconds). If

"On busy" is selected, incoming calls will be forwarded when the phone is busy.

Administration via WBM

System > Features > Program keys > Forwarding

3.6.4

Ringer Off

Turns off the ringtone. Incoming calls are indicated via LEDs and display only.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Ringer off

3-66

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

3.6.5

Hold

The call currently selected or active is put on hold.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Hold

3.6.6

Alternate

Toggles between two calls; the currently active call is put on hold.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Alternate

3.6.7

Blind Call Transfer / Move Blind

A call is transferred without consultation, as soon as the phone goes on-hook or the target phone goes off-hook.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Move blind

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-67

administration.fm

Administration

Programmable Keys

3.6.8

Join Two Calls

Call transfer, applicable when there is one active call and one call on hold. The active call and the held call are connected to each other, while the phone that has initiated the transfer is disconnected.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Join

3.6.9

Deflect A Call

On key press, an incoming call is deflected to the specified destination.

The label displayed to the left of the key is defined in Key label <key number>.

The target destination is defined in the Destination parameter.

Administration via WBM

System > Features > Program keys > Deflect

3.6.10

Shift Level

Shift the level for the program keys. When activated, the functions assigned to the shifted level are available on the program keys.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Shift

3-68

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

3.6.11

Phone-Based Conference

Establishes a three-party conference from an active call and a held call.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Conference

3.6.12

Accept Call Via Headset

On key press, incoming call is accepted via headset. This feature is available on OpenStage

40/60/80 phones.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Headset

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-69

administration.fm

Administration

Programmable Keys

3.6.13

Do Not Disturb

If this feature is activated, incoming calls will not be indicated to the user.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Do Not Disturb

3.6.14

Repertory Dial

Special calling functions. The desired function is selected via the Dial string parameter. The

"<" character disconnects a call; "~" puts a call on hold for consultation; ">" starts a call; "-" enters a pause, e. g. for international dialing.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Repertory dial

3.6.15

Consult And Transfer

When the phone is engaged in an active call, this function opens a dialing menu to make a consulation call.

The label displayed to the left of the key is defined in Key label <key number>.

3-70

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

Administration via WBM

System > Features > Program keys > Consult and transfer

3.6.16

Toggle Call Waiting

Enables or disables the call waiting feature. If enabled, calls from a third party are allowed during an active call.

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys > Call waiting toggle

3.6.17

Server Feature

Invokes a feature on the SIP server. The status of the feature can be monitored via the LED associated to the key.

The label displayed to the left of the key is defined in Key label <key number>.

The code entered in Feature code will be sent in a SIP INVITE to the SIP server.

The code entered in DTMF digits will be sent to the SIP server as a DTMF signal. As a precondition, an audio path routed via the SIP server must exist.

The SIP URI configured in LED control will receive the status notifications (SIP NOTIFY) from the SIP server. The LED is switched on or off accordingly.

Administration via WBM

System > Features > Program keys > Server feature

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-71

administration.fm

Administration

Programmable Keys

3.6.18

Monitoring Another Extension Via BLF Key

This function offers the possibility to monitor another extension, and to pick up calls for the monitored extension.

The label for the key is defined in Key label <key number>.

The Monitored phone parameter stores the call number or SIP URI of the monitored phone.

If Audible alert is enabled, an alert beep or ringtone will indicate an incoming call for the monitored phone. The BLF alerting parameter in System > Features > Configuration determines whether the alert beep or the ringtone is used.

If Popup alert is enabled, a popup window will indicate an incoming call for the monitored phone.

Administration via WBM

System > Features > Program keys > BLF

System > Features > Configuration

3-72

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

3.6.19

Send Request via HTTP/HTTPS (V2)

With this function, the phone can send a specific HTTP or HTTPS request to a server. The function is available at any time, irrespective of registration and call state. Possible uses are HTTPcontrolled features on the SIP server, e. g. hunt group login/logout, or functions on a web server that can only be triggered by HTTP/HTTPS request, e. g. login/logout for flexible working hours.

The Protocol parameter defines whether HTTP or HTTPS is to be used for sending the URL to the server.

The Web server address is the IP address or DNS name of the remote server to which the

URL is to be sent.

The Port is the target port at the server to which the URL is to be sent.

The Path is the server-side path to the desired function, i. e. the part of the URL that follows the IP address or DNS name. Example: webpage/checkin.html

In the Parameters field, one or more key/value pairs in the format

"<key>=<value>" can be added to the request, separated by an ampersand (

&).

Example: phonenumber=3338&action=huntGroupLogon

>

The question mark will be automatically added between the path and the parameters. If a question mark has been entered at the start of the parameters, it will be automatically stripped off.

The Method parameter determines the HTTP method to be used, which can either be GET or

POST. If GET is selected, the additional parameters (Parameters) and the user id/password

(Web server user ID/Web server password) are part of the URL. If POST is selected, these data form the body of the message.

In case the web server requires user authentication, the parameters Web server user ID and

Web server password can be used. If not null, the values are appended between the serverside path (Path) and the additional parameters (Parameter).

If the LED controller URI is given, the LED associated with this key indicates the state of the call number or SIP URI specified here. This function is similar to the LED function of the BLF

key described in Section 3.6.18, “Monitoring Another Extension Via BLF Key”.

Data required

Key label <n>: Label for the key.

Protocol: Transfer protocol to be used.

Value range: "HTTP", "HTTPS".

Web server address: IP address or DNS name of the remote server.

Port: Target port at the server.

Path: Server-side path to the function.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-73

administration.fm

Administration

Programmable Keys

Parameters: Optional parameters to be sent to the server.

Method: HTTP method used for transfer.

Value range: "GET", "POST".

Web server user ID: User id for user authentication at the server.

Web server password: Password for user authentication at the server.

LED controller URI: Indicates the state of the call number specified.

Administration via WBM

System > Features > Program keys > Send URL

3-74

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

3.6.20

Start application

With this key, the user can start a pre-defined XML application (see Section 3.12, “Applications”). XML applications are available for OpenStage 60/80 phones.

The label displayed to the left of the key is defined in Key label <key number>.

The Application name parameter selectes the XML application to be started.

Administration via WBM

System > Features > Program keys

3.6.21

Clear (no feature assigned)

The label displayed to the left of the key is defined in Key label <key number>.

Administration via WBM

System > Features > Program keys

3.6.22

Programmable Call Forwarding Key (V2)

>

This function is available for all OpenStage phones except OpenStage 15, which has no forwarding key.

By default, the fixed forwarding key r controls the phone’s built-in forwarding functionality.

Alternatively, server-based fcall orwarding can be assigned to this key. For this purpose, an appropriate feature code or DTMF signal is sent to the SIP server in order to toggle forwarding.

The parameters Feature code, DTMF digits, and LED control are the same as with the server

feature key; pleaser refer to Section 3.6.17, “Server Feature”.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-75

administration.fm

Administration

Programmable Keys

The Key functionality parameter controls the behaviour of the forwarding key. To have the

LED of the forwarding key controlled by the SIP server, the SIP URI/Call number entered in

LED control must relate to the corresponding SIP subscription.The following options are possible:

• "Toggle call forwarding": On pressing the key, the user will be presented with a prompt

"Toggle call forwarding", allowing him/her to accept or reject the action. When accepted, the configured feature code or DTMF sequence will be sent to the external server. The LED and the forwarding icon in the call view screen are controlled by the SIP server.

• "Unspecified call forwarding": No prompt will be presented to the user. The configured feature code or DTMF sequence will be sent to the external server immediately. It is not assumed that the key is used to toggle call forwarding, but that the key is generally call forwarding related. The phone’s built-in forwarding is disabled, and the LED will be controlled by the SIP server, but not the forwarding icon in the call view screen.

• "Unspecified": No prompt will be presented to the user. The configured feature code or

DTMF sequence will be sent to the external server immediately. No assumptions will be made as to the operation of the key. The phone’s built-in forwarding is not disabled. The

LED will be controlled by the SIP server, but not the forwarding icon in the call view screen.

Administration via WBM

System > Features > Fixed Keys

1.

Built-in forwarding selected:

2.

Server feature selected:

3-76

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Programmable Keys

3.6.23

Mute (OpenStage 15 Only)

On pressing this key, the microphone is turned off. This programmable key function is available only for OpenStage 15 phones, which have no fixed mute key.

3.6.24

Release (OpenStage 15 Only)

On pressing this key, the current call is disconnected. This programmable key function is available only for OpenStage 15 phones, which have no fixed release key.

3.6.25

Key Modules

A Key Module provides 12 additional program keys. Key Modules are available for OpenStage

15/40/60/80 phones. A maximum of 2 key modules can be connected to one phone.

The following table shows which key modules can be connected to the particular phone types.

Phone Type

OpenStage 15

OpenStage 40

OpenStage 60/80 -

OpenStag Key Module 15 OpenStage Key Module

1

1

-

2

2

>

Please note that OpenStage Key Modules (self-labeling) and

OpenStage Key Module 15 (paper label) can not be combined. For Key Labelling, a special tool is available; please refer to: http://wiki.siemens-enterprise.com/index.php/Key_Labelling_Tool

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

Administration via WBM

System > Features > Key module 1/2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-77

administration.fm

Administration

Programmable Keys

3-78

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Dialing

3.7

Dialing

3.7.1

Canonical Dialing Configuration

Call numbers taken from a directory application, LDAP for instance, are mostly expressed in canonical format. Moreover, call numbers entered into the local phone book are automatically converted and stored in canonical format, thereby adding "+", Local country code, Local na-

tional code, and Local enterprise number as prefixes. If, for instance, the user enters the extension "1234", the local country code is "49", the local national code is "89", and the local enterprise number is "722", the resulting number in canonical format is "+49897221234".

For generating an appropiate dial string, a conversion from canonical format to a different format may be required. The following parameters determine the local settings of the phone, like

Local country code or Local national code, and define rules for converting from canonical format to the format required by the PBX.

>

To enable the number conversion, all parameters not marked as optional must be

provided, and the canonical dial lookup settings must be configured (see Section

3.7.2, “Canonical Dial Lookup”).

Data required

Local country code: E.164 Country code, e.g. "49" for Germany, "44" for United Kingdom.

Maximum length: 5.

National prefix digit: Prefix for national connections, e.g. "0" in Germany and United Kingdom. Maximum length: 5.

Local national code: Local area code or city code, e.g. "89" for Munich, "20" for London.

Maximum length: 6.

Minimal local number length: Minimum number of digits in a local PSTN number, e.g.

3335333 = 7 digits.

Local enterprise number: Number of the company/PBX wherein the phone is residing.

Maximum length: 10. (Optional)

PSTN access code: Access code used for dialing out from a PBX to a PSTN. Maximum length: 10. (Optional)

International access code: International prefix used to dial to another country, e.g. "00" in Germany and United Kingdom. Maximum length: 5.

Operator codes: List of extension numbers for a connection to the operator. The numbers entered here are not converted to canonical format. Maximum length: 50. (Optional)

Emergency number: List of emergency numbers to be used for the phone. If there are more than one numbers, they must be separated by commas. The numbers entered here are not converted to canonical format. Maximum length: 50. (Optional)

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-79

administration.fm

Administration

Dialing

Tthese emergency numbers can also be dialed when the phone is locked, in line with the

emergency number configured in Features > Configuration (see Section 3.4.2, “Emergency and Voice Mail”).

Initial extension digits / Initial digits: List of initial digits of all possible extensions in the local enterprise network. When a call number could not be matched as a public network number, the phone checks if it is part of the local enterprise network. This is done by comparing the first digit of the call number to the value(s) given here. If it matches, the call number is recognized as a local enterprise number and processed accordingly.

If, for instance, the extensions 3000-5999 are configured in the PBX, each number will start with 3, 4, or 5. Therefore, the digits to be entered are 3, 4, 5.

• Internal numbers

>

To enable the phone to discern internal numbers from external numbers, it is

crucial that a canonical lookup table is provided (Section 3.7.2, “Canonical Dial

Lookup”).

• "Local enterprise form": Default value. Any extension number is dialled in its simplest form. For an extension on the local enterprise node, the node ID is omitted. If the extension is on a different enterprise node, then the appropriate node ID is prefixed to the extension number. Numbers that do not correspond to an enterprise node extension are treated as external numbers.

• "Always add node": Numbers that correspond to an enterprise node extension are always prefixed with the node ID, even those on the local node. Numbers that do not correspond to an enterprise node extension are treated as external numbers.

• "Use external numbers": All numbers are dialled using the external number form.

External numbers

• "Local public form": Default value. All external numbers are dialled in their simplest form. Thus a number in the local public network region does not have the region code prefix. Numbers in the same country but not in the local region are dialled as national numbers. Numbers for a different country are dialled using the international format.

• "National public form": All numbers within the current country are dialled as national numbers, thus even local numbers will have a region code prefix (as dialling from a mobile). Numbers for a different country are dialled using the international format.

• "International form": All numbers are dialled using their full international number format.

External access code

• "Not required": The access code to allow a public network number to be dialled is not required.

3-80

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Dialing

• "For external numbers": Default value. All public network numbers will be prefixed with the access code that allows a number a call to be routed outside the enterprise network. However, international numbers that use the + prefix will not be given access code.

International gateway code:

• "Use national code": Default value. All international formatted numbers will be dialled explicitly by using the access code for the international gateway to replace the "+" prefix.

• "Leave as +": All international formatted numbers will be prefixed with "+".

Administration via WBM

Local functions > Locality > Canonical dial settings

Local functions > Locality > Canonical dial

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-81

administration.fm

Administration

Dialing

Administration via Local Phone

|

--- Administration

|

--- Local Functions

|

--- Locality

|

--- Canonical dial settings

|--- Local country code

|--- National prefix digit

|--- Local national code

|--- Minimum local number length

|--- Local enterprise node

|--- PSTN access code

|--- International access code

|--- Operator code

|--- Emergency number

|

--- Initial digits

|

--- Administration

|

--- Local Functions

|

--- Locality

|

--- Canonical dial

|--- Internal numbers

|--- External numbers

|--- External access code

|

--- International access code

3-82

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Dialing

3.7.2

Canonical Dial Lookup

The parameters given here are important for establishing outgoing calls and for recognizing incoming calls.

In the local phonebook, and, mostly, in LDAP directories, numbers are stored in canonical format. In order to generate an appropriate dial string according to the settings in Internal num-

bers and External numbers (-> Section 3.7.1), internal numbers must be discerned from ex-

ternal numbers. The canonical lookup table provides patterns which allow for operation.

Furthermore, these patterns enable the phone to identify callers from different local or international telephone networks by looking up the caller’s number in the phone book. As incoming numbers are not always in canonical format, their composition must be analyzed first. For this purpose, an incoming number is matched against one or more patterns consisting of country codes, national codes, and enterprise nodes. Then, the result of this operation is matched against the entries in the local phone book.

>

To make sure that canonical dial lookup works properly, at least the following parameters of the phone must be provided:

Local country code (-> Section 3.7.1)

Local area code (-> Section 3.7.1)

Local enterprise code (-> Section 3.7.1)

Up to 5 patterns can be defined. The Local code 1 ... 5 parameters define up to 5 different local enterprise nodes, whilst International code 1... 5 define up to 5 international codes, that is, fully qualified E.164 call numbers for use in a PSTN.

Data required

Local code 1 ... 5: Local enterprise code for the node/PBX the phone is connected to.

Example: "722" for Siemens Munich.

International code 1 ... 5: Sequence of "+", local country code, local area code, and local enterprise node corresponding to to one or more phone book entries.

Example: "+4989722" for Siemens Munich.

Administration via WBM

Locality > Canonical dial lookup

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-83

administration.fm

Administration

Dialing

Administration via Local Phone

|

--- Administration

|

--- Local Functions

|

--- Locality

|

--- Canonical Dial Lookup

|--- Local code 1

|--- International code 1

|--- Local code 2

|--- International code 2

|--- Local code 3

|--- International code 3

|--- Local code 4

|--- International code 4

|--- Local code 5

|

--- International code 5

3-84

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Dialing

3.7.3

Dial Plan (V2)

With firmware version V2, OpenStage phones may optionally use a phone-side dial plan. By means of the dial plan, the phone can infer from the digits entered by the user that a complete call number has been entered. Thus, the phone can start the dialing process without the user explicitly having to select a further option such as "dial" or "OK" after entering the last digit. The standard timer, which is found on the WBM under User menu > Configuration > Outgoing calls

> Autodial delay (seconds), is overridden.

A dial plan consists of rules defining patterns, timeouts and actions to be performed when a pattern is matched and/or a timeout has expired. The phone can store one dialplan, which can contain up to 48 different rules.

It is very important that the phone’s dial plan does not interfere with the dial plan in the SIP server, PBX, or public network.

The dial plan can be created and uploaded to the phone using the DLS (please refer to the Deployment Service Administration Manual). The DLS can also export and import dial plans in

.csv format. For details about the composition of a dial plan, please refer to Section 4.4.1, “How

To Set Up And Deploy A Dial Plan”.

The current dial plan, along with its status (enabled/disabled) and error status can be displayed on the WBM via Diagnostics > Fault trace configuration > Download dial plan file.

To make use of the dial plan facility, the following requirements must be met:

• A correct dial plan must be loaded to the phone.

• In the user menu, Allow immediate dialing must be enabled

Dial plan enabled must be checked.

Administration via WBM

User menu > Configuration > Outgoing calls > Allow immediate dialing

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-85

administration.fm

Administration

Dialing

System > Features > Configuration > Dial plan enabled

Administration via Local Phone

|

--- User

|

--- Configuration

|

--- Outgoing calls

|

--- Immediate dialing

|

--- Administration

|

--- Features

|

--- Configuration

|

--- General

|

--- Dial plan

3-86

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Distinctive Ringing (V2)

3.8

Distinctive Ringing (V2)

The SIP server may provide information indicating a specific type of call within an incoming call.

With firmware V2, the phone can use this information to choose a ring tone according to the call type.

The relevant information is carried as a string in the SIP Alert-Info header. When this string matches a specific Name, the corresponding ringer is triggered. In the Asterisk dial plan

( extensions.conf), this is done by the SIPAddHeader() function. The following example line from an extensions.conf, which precedes the line containing the Dial() function, adds the specific string alert-internal to the SIP header for a specific number pattern: exten => _3XXX,1,SIPAddHeader("Alert-Info:alert-internal")

Thus, in this example, the value for Name would be "alert-internal".

The Ringer sound parameter determines whether a pattern, i. e. melody, or a specific sound file shall be used as ringer.

Pattern Melody selects the melody pattern that will be used if Ringer sound is set to "Pattern".

Pattern sequence determines the length for the melody pattern, and the interval between the repetitions of the pattern. There are 3 variants:

• "1": 1 sec ON, 4 sec OFF

• "2": 1 sec ON, 2 sec OFF

• "3": 0.7 sec ON, 0.7 sec OFF, 0.7 sec ON, 3 sec OFF

The Duration parameter determines how long the phone will ring on an incoming call. The range is 0-300 sec.

With the Audible parameter, the ringer can be muted. In this case, an incoming call will be indicated only visually.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-87

administration.fm

Administration

Distinctive Ringing (V2)

Administration via WBM

Ringer setting

3-88

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9

Transferring Phone Software, Application and Media Files

New software images, hold music, picture clips for phonebook entries, LDAP templates, company logos, screensaver images, and ringtones can be uploaded to the phone via DLS (Deployment Service) or WBM (Web Based Management).

>

For all user data, which includes files as well as phonebook content, the following amounts of storage place are available:

• OpenStage 15/20/40: 4 MB

• OpenStage 60/80: 8 MB

3.9.1

FTP/HTTPS Server

There are no specific requirements regarding the FTP server for transferring files to the

OpenStage phone. Any FTP server providing standard functionality will do.

3.9.2

Common FTP/HTTPS Settings

For each one of the various file types, e.g. phone software, hold music, and picture clips, specific FTP/HTTPS access data can be defined. If some or all file types have the parameters

Download method, FTP Server, FTP Server port, FTP account, FTP username, FTP path, and HTTPS base URL in common, they can be specified here. These settings will be used for a specific file type if its Use defaults parameter is set to "Yes".

>

If Use defaults is activated for a specific file type, any specific settings for this file type are overridden by the defaults.

Data required

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP server in use.

FTP Server port: Port number of the FTP server in use. For HTTPS, port 443 is assumed, unless a different port is specified in the HTTPS base URL.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use. If no port number is specified here, port 443 is used. Only applicable if Download method is switched to

"HTTPS".

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-89

administration.fm

Administration

Transferring Phone Software, Application and Media Files

Administration via WBM

File transfer > Defaults

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Defaults

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|

--- HTTPS base URL

3-90

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.3

Phone Software

The firmware for the phone can be updated by downloading a new software file to the phone.

7

Do not disconnect the phone from the LAN or power unit during software update. An active update process is indicated by blinking LEDs and/or in the display.

3.9.3.1

FTP/HTTPS Access Data

If the default FTP/HTTPS Access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-91

administration.fm

Administration

Transferring Phone Software, Application and Media Files

Administration via WBM

File transfer > Phone application

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Phone app

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

3-92

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.3.2

Download/Update Phone Software

If applicable, phone software should be deployed using a provisioning service, such as the Deployment Service (DLS). Alternatively, the download can be triggered from the web interface or from the Local phone menu. When the download has been successful, the phone will restart and boot up using the new software.

Start Download via WBM

In the File transfer > Phone application dialog, set After submit to "start download" and press the Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Phone app.

|

--- Administration

|

--- File Transfer

|

--- Phone app

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-93

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.4

Music on Hold

If enabled by the user, the Music on Hold (MoH) sound file is played when a call is put on hold.

>

The file size for a Music on Hold file is limited to 1MB. If the file is too large or the contents of the file are not valid, the file will not be stored in the phone.

The following formats for Music on Hold are supported:

• Proprietary Music on Hold format for optiPoint 410/420 phones

• WAV format. The recommended specifications are:

• Audio format: PCM

• Bitrate: 16 kB/sec

• Sampling rate: 8 kHz

• Quantization level: 16 bit.

• MIDI format.

• MP3 format (OpenStage 60/80 only). A bitrate of 48 kB/sec is recommended.

3.9.4.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use Default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

3-94

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

Administration via WBM

File transfer > Hold music

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Hold Music

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-95

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.4.2

Download Music on Hold

If applicable, Music on Hold should be deployed using a provisioning service, such as the Deployment Service (DLS). Alternatively, the download can be triggered from the web interface or from the Local phone menu.

Start Download via WBM

In the File transfer > Hold music dialog, set After submit to "start download" and press the

Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Hold Music.

|

--- Administration

|

--- File Transfer

|

--- Hold Music

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

3-96

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.5

Picture Clips

>

Picture clips are available only on OpenStage 60/80 phones.

>

The file size for a picture clip is limited to 300 KB. If the file is too large or the contents of the file are not valid, the file will not be stored in the phone.

Picture Clips are small images used for displaying a picture of a person that is calling on a line.

The supported file formats for picture clips are JPEG and PNG (recommended).

3.9.5.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-97

administration.fm

Administration

Transferring Phone Software, Application and Media Files

Administration via WBM

File transfer > Picture clip

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Picture Clip

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

3-98

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.5.2

Download Picture Clip

The download can be triggered from the web interface or from the local phone menu.

Start Download via WBM

In the File transfer > Picture clip dialog, set After submit to "start download" and press the

Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Picture clip.

|

--- Administration

|

--- File Transfer

|

--- Picture clip

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-99

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.6

LDAP Template

>

LDAP is available only on OpenStage 60/80 phones.

The LDAP template is an ASCII text file that uses an allocation list to assign directory server attributes to input and output fields on an LDAP client. The LDAP template must be modified correctly for successful communication between the directory server and the LDAP client.

>

The OpenStage phone supports LDAPv3.

3.9.6.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTPServer address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

3-100

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via WBM

File transfer > LDAP administration.fm

Administration

Transferring Phone Software, Application and Media Files

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- LDAP

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-101

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.6.2

Download LDAP Template

If applicable, LDAP templates should be deployed using a provisioning service, such as the Deployment Service (DLS). Alternatively, the download can be triggered from the web interface or from the Local phone menu.

>

The OpenStage phone supports LDAPv3.

Start Download via WBM

In the File transfer > LDAP dialog, set After submit to "start download" and press the Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to LDAP.

|

--- Administration

|

--- File Transfer

|

--- LDAP

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

3-102

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.7

Logo

On OpenStage 40/60/80, a custom background image for the telephony interface can be supplied. In most cases, this will be the company logo.

On OpenStage 40, monochrome bitmap files (BMP) are supported. The ideal size is as follows:

• Width: 144 px

• Height: 32 px

On OpenStage 60/80, the supported file formats are JPEG and PNG. The ideal size values are is as follows:

OpenStage 60:

• Width: 240 px

• Height: 70 px

OpenStage 80:

• Width: 480 px

• Height: 148 px

If the size should deviate from these values, the image will appear skewed.

For guidance on creating a logo file for OpenStage 40/60/80, see Section 4.2, “How to Create

Logo Files for OpenStage Phones”.

3.9.7.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-103

administration.fm

Administration

Transferring Phone Software, Application and Media Files

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

Administration via WBM

File transfer > Logo

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Logo

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

3-104

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.7.2

Download Logo

If applicable, logos should be deployed using a provisioning service, such as the Deployment

Service (DLS). Alternatively, the download can be triggered from the web interface or from the

Local phone menu.

Start Download via WBM

In the File transfer > Logo dialog, set After submit to "start download" and press the Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Logo.

|

--- Administration

|

--- File Transfer

|

--- Logo

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-105

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.8

Screensaver

The screensaver is displayed when the phone is in idle mode. It performs a slide show consisting of images which can be uploaded using the web interface.

>

Screensavers are available only on OpenStage 60/80 phones.

>

The file size for a screensaver image is limited to 300 KB. If the file is too large or the contents of the file are not valid, the file will not be stored in the phone.

For screensaver images, the following specifications are valid:

• Data format: JPG or PNG. JPG is recommended.

• Screen format: 4:3. The images are resized to fit in the screen, so that images with a width/ height ratio differing from 4:3 will appear with deviant proportions.

• Resolution: The phone’s screen resolution is the best choice for image resolution:

• OpenStage 60: 320x240

• OpenStage 80: 640x480

3.9.8.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

3-106

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

Administration via WBM

File transfer > Screensaver

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Screensaver

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-107

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.8.2

Download Screensaver

If applicable, screensavers should be deployed using a provisioning service, such as the Deployment Service (DLS). Alternatively, the download can be triggered from the web interface or from the Local phone menu.

Start Download via WBM

In the File transfer > Screensaver dialog, set After submit to "start download" and press the

Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Screensaver.

|

--- Administration

|

--- File Transfer

|

--- Screensaver

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

3-108

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.9

Ringer File

Custom Ringtones can be uploaded to the phone.

>

The file size for a ringer file is limited to 1 MB. If the file is too large or the contents of the file are not valid, the file will not be stored in the phone.

The following file formats are supported:

• WAV format. The recommended specifications are:

• Audio format: PCM

• Bitrate: 16 kB/sec

• Sampling rate: 8 kHz

• Quantization level: 16 bit

• MIDI format.

• MP3 format (OpenStage 60/80 only). The OpenStage 60/80 phones are able to play MP3 files from 32 kbit/s up to 320 kbit/s. As the memory for user data is limited to 8 MB, a constant bitrate of 48 kbit/sec to 112 kbit/s and a length of max. 1 minute is recommended.

Although the phone software can play stereo files, mono files are recommended, as the phone has only 1 loudspeaker.

See the following table for estimated file size (mono files):

Length

0:15 min

0:30 min

0:45 min

1:00 min

64 kbit/s

0,12 MB

0,23 MB

0,35 MB

0,47 MB

80 kbit/s

0,15 MB

0,29 MB

0,44 MB

0,59 MB

96 kbit/s

0,18 MB

0,35 MB

0,53 MB

0,70 MB

112 kbit/s

0,21 MB

0,41 MB

0,62 MB

0,82 MB

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-109

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.9.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to "Yes", and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: "Yes", "No".

Default: "No".

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: "FTP", "HTTPS".

Default: "FTP".

FTP Server address: IP address or hostname of the FTP/HTTPS server in use.

FTP Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to "HTTPS".

Administration via WBM

File transfer > Ringer file

3-110

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Ringer

|--- Use default

|--- Download method

|--- FTP Server

|--- FTP Port

|--- FTP Account

|--- FTP Username

|--- FTP Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename administration.fm

Administration

Transferring Phone Software, Application and Media Files

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-111

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.9.2

Download Ringer File

If applicable, ring tone files should be deployed using a provisioning service, such as the Deployment Service (DLS). Alternatively, the download can be triggered from the web interface or from the Local phone menu.

Start Download via WBM

In the File transfer > Ringer dialog, set After submit to "start download" and press the Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Ringer.

|

--- Administration

|

--- File Transfer

|

--- Ringer

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

3-112

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.10

HPT Dongle Key

The HPT dongle key is a special file that contains a secret hash number which is required to connect the HPT tool to the phone. This testing tool is used exclusively by the service staff.

3.9.10.1

FTP/HTTPS Access Data

If the default FTP/HTTPS access settings (see Section 3.9.2, “Common FTP/HTTPS Settings”)

are to be used, Use default must be set to „Yes“, and only the Filename must be specified.

Data required (in every case)

Use default: Specifies whether the default FTP/HTTPS access settings shall be used. Value range: „Yes“, „No“.

Default: „No“.

Filename: Specifies the file name of the phone software.

Data required (if not derived from Defaults)

Download method: Selects the protocol to be used.

Value range: „FTP“, „HTTPS“.

Default: „FTP“.

Server address: IP address or hostname of the FTP/HTTPS server in use.

Server port: Port number of the FTP/HTTPS server in use.

Default: 21.

FTP account: Account at the server (if applicable).

FTP username: User name for accessing the server.

FTP password: Password corresponding to the user name.

FTP path: Path of the directory containing the files.

HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if

Download method is switched to „HTTPS“.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-113

administration.fm

Administration

Transferring Phone Software, Application and Media Files

Administration via WBM

File transfer > Dongle key

Administration via Local Phone

|

--- Administration

|

--- File Transfer

|

--- Dongle key

|--- Use default

|--- Download method

|--- Server

|--- Port

|--- Account

|--- Username

|--- Password

|--- FTP path

|--- HTTPS base URL

|

--- Filename

3-114

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Transferring Phone Software, Application and Media Files

3.9.10.2

Download Dongle Key File

If applicable, dongle key files should be deployed using a provisioning service, such as the Deployment Service (DLS). Alternatively, the download can be triggered from the web interface or from the Local phone menu.

Start Download via WBM

In the File transfer > Dongle key dialog, set After submit to „start download“ and press the

Submit button.

Start Download via Local Phone

1.

In the administration menu, set the focus to Dongle key.

|

--- Administration

|

--- File Transfer

|

--- Dongle key

2.

Press the g

key. A context menu opens. In the context menu, select Download. The download will start immediately.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-115

administration.fm

Administration

Corporate Phonebook: Directory Settings

3.10

3.10.1

Corporate Phonebook: Directory Settings

LDAP

>

LDAP is available only on OpenStage 60/80 phones.

The Lightweight Directory Access Protocol enables access to a directory server via an LDAP client. Various personal information is stored there, e.g. the name, organisation and contact data of persons working in an organisation. When the LDAP client has found a person’s data, e. g. by looking up the surname, the user can call this person directly using the displayed number.

>

The OpenStage phone supports LDAPv3.

For connecting the phone’s LDAP client to a LDAP server, the required access data must be configured. The parameters Server address and Server port specify the IP address and hostname as well as the port used by the LDAP server. If the Authentication is not set to "Anonymous", the user must authenticate himself with the server by providing a User name and a corresponding Password. The user name is the string in the LDAP bind request, e. g.

"C=GB,O=SIEMENS COMM,OU=COM,L=NTH,CN=BAYLIS MICHAEL". The internal structure will depend on the specific corporate directory.

For a quick guide on setting up LDAP on an OpenStage phone, please refer to Section 4.3,

“How to Set Up the Corporate Phonebook (LDAP)”.

With firmware V2, the OpenStage 60/80 GUI features a new search field for LDAP requests.

The search string is submitted to the LDAP server as soon as the i

key is pressed, or when the Search trigger timeout expires.

Data required

Server address: IP address or hostname of the LDAP server.

Server port: Port on which the LDAP server is listening for requests.

Default: 389.

Authentication: Authentication method used for connecting to the LDAP server. value range: "Anonymous", "Simple".

Default: "Anonymous".

User name: User name used for authentication with the LDAP server in the LDAP bind request.

Password: Password used for authentication with the LDAP server.

3-116

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Corporate Phonebook: Directory Settings

Search trigger timeout (V2 on OpenStage 60/80): Timespan between entering the last character and search string submission to the LDAP server.

Administration via WBM

Local Functions > Directory settings

Administration via Local Phone

|

--- Administration

|

--- Local Functions

|

--- Directory Settings

|--- Server address

|--- Server port

|--- Authentication

|--- User name

|

--- Password

Administration via WBM (V2)

Local Functions > Directory settings

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-117

administration.fm

Administration

Corporate Phonebook: Directory Settings

Administration via Local Phone (V2)

|

--- Administration

|

--- Local Functions

|

--- LDAP Settings

|--- server address

|--- server port

|--- Timeout (sec)

|--- authentication

|--- user name

|

--- password

3-118

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Speech

3.11

Speech

3.11.1

RTP Base Port

The port used for RTP is negotiated during the establishment of a SIP connection. The RTP base port number defines the starting point from which the phone will count up when negotiating. The default value is 5010.

The number of the port used for RTCP will be the RTP port number increased by 1.

Administration via WBM

Network > Port Configuration

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- Port Configuration

|

--- RTP base

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-119

administration.fm

Administration

Speech

3.11.2

Codec Preferences

If Silence suppression is activated, the transmission of data packets is suppressed on no conversation, that is, if the user doesn’t speak.

The OpenStage phone provides the codecs G.711, G.722, and G.729. When a SIP connection is established between two endpoints, the phones negotiate the codec to be used. The result of the negotiation is based on the general availability and ranking assigned to each codec. The administrator can allow or disallow a codec as well as assign a ranking number to it.

The Packet size, i. e. length in milliseconds, of the RTP packets for speech data, can be set to 10ms, 20ms, 30ms or to automatic detection.

Data required

Silence suppression: Suppression of data transmission on no conversation.

Value range: "On", "Off".

Default: "Off".

Packet size: Size of RTP packets in milliseconds.

Value range: "10 ms", "20ms", "30ms", "Automatic".

Default: "Automatic".

G.711: Parameters for the G. 711 codec.

Value Range: "Choice 1", "Choice 2", "Choice 3", "Disabled", "Enabled".

Default: "Choice 1".

G.729: Parameters for the G. 729 codec.

Value Range: "Choice 1", "Choice 2", "Choice 3", "Disabled", "Enabled".

Default: "Choice 2".

G.722: Parameters for the G. 722 codec.

Value Range: "Choice 1", "Choice 2", "Choice 3", "Disabled", "Enabled".

Default: "Disabled".

Administration via WBM

Speech > Codec preferences

3-120

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via Local Phone

|

--- Administration

|

--- Speech

|

--- Codec Preferences

|--- Silence suppression

|--- Packet size

|--- G.711

|--- G.729

|

--- G.722 administration.fm

Administration

Speech

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-121

administration.fm

Administration

Speech

3.11.3

Audio Settings

The usage of microphone and speaker for speakerphone mode can be controlled by the administrator.

Both microphone and loudspeaker can be switched on or off separately. By default, both microphone and loudspeaker are switched on.

>

The microphone control is not valid for OpenStage 20E, as this model has no builtin microphone.

Administration via WBM

Speech > Audio Settings

Administration via Local Phone

|

--- Administration

|

--- Speech

|

--- Audio Settings

|--- Disable microphone

|

--- Disable loudspeech

3-122

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Applications

3.12

3.12.1

Applications

XML Applications/Xpressions (OpenStage 60/80)

3.12.1.1

Setup/Configuration

The XML interface enables server-based applications with a set of GUI elements. The technologies commonly used in web applications can be used: Java Servlets, JSP, PHP, CGI etc., delivered by servers such as Tomcat, Apache, Microsoft IIS.

>

A maximum number of 20 XML applications can be configured on OpenStage 60/80 phones.

An XML application can be started by using the v

key to navigate to the Applications tab and then selecting an application, or by assigning it to a program key (System > Features > Program keys).

>

Xpressions is a special Unified Communications application which also uses the

XML interface. Thus, the configuration is just the same as with other XML applications, except a few parameters, which are pre-configured. For details, please refer to the relevant Xpressions documentation. When configured on the phone, a press on x

will invoke this application.

>

XML Phonebook is a preconfiguration intended for a regular XML application with phonebook functionality. When configured on the phone, a press on u

will invoke this application, in place of the personal (local) or corporate (LDAP) phonebook.

For detailed information about the OpenStage XML application interface, please see the Open-

Stage 60/80 XML Applications Developer’s Guide. You can find the current version under http://wiki.siemens-enterprise.com/index.php/OpenStage_XML_Applications

To set up a new XML application, enter the access data for the application on the server, which is described in the following.

The Display name can be defined freely. This name will appear in the applications tab once the application is configured, and it will appear in a newy created tab when the application is running. With Xpressions, this value is predefined as "Xpressions".

The Application name is used by the phone software to identify the XML application running on the phone. With Xpressions, this value is predefined as "Xpressions".

The Protocol for exchanging XML data with the server-side program can be set to "HTTP" or

"HTTPS".

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-123

administration.fm

Administration

Applications

The HTTP Server address is the IP address or domain name of the server which hosts the remote program. Server port number specifies the corresponding port.

Program name specifies the relative path to the servlet or to the first XML page of the application on the server. The relative path refers to the root directory for documents on the web server. The program name cannot be longer than 100 characters.

XML trace enabled determines whether debugging information is sent to a special debugging program on the remote server. The relative path for the debugging program is given by the De-

bug program name parameter.

If desired, XML applications can have internal tabs. The number of these tabs is specified in

Number of tabs.

Tab 1...3 Display Name provides the label text for the corresponding tab.

Tab 1...3 Application Name is required if the application has internal tabs. This is a unique name for the specified tab. The remote program will use this name to provide the tab with specific content.

Auto restart / Restart after change (V2): If checked, a running XML application is automatically restarted after it has been modified. Please note that a restart will take place even if no changes have been made for the application selected for modification in the Modify application mask, and Submit has been pressed. After the XML application has restarted, this option is automatically unchecked. If Auto restart is checked whilst the XML application is not running, there will be no restart, and the option is automatically unchecked.

Data required

Display name: Program name to be displayed on the phone.

Value specifications:

• It must be unique on the phone.

• It cannot contain the ’^’ character.

• It cannot not be empty.

• Its length cannot not exceed 20 characters.

Application name: Used internally to identify the XML application running on the phone.

Value specifications:

• It must be unique on the phone.

• It cannot contain non-alphanumeric characters, spaces for instance.

• The first character must be a letter.

• It must not be empty.

• Its length must not exceed 20 characters.

3-124

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Applications

Protocol: Communication protocol for the data exchange with the server.

Value range: "HTTP", "HTTPS".

Default: "HTTPS".

HTTP Server address: IP address or domain/host name of the server that provides the application or the XML document.

Server port number: Number of the port that the server uses to provide the application or

XML document.

Program name: Relative path to the servlet or to the first XML page of the application on the server.

XML trace enabled: Enables or Disables the debugging of the XML application.

Value range: "Yes", "No".

Default: "No".

Debug program name: The relative path to a special servlet that receives the debug information.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-125

administration.fm

Administration

Applications

Administration via WBM

Applications > XML Applications > Add application

Applications > XML Applications > Modify application

3-126

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Applications

Administration via Local Phone

|

--- Administration

|

--- Applications

|

--- XML

|

--- Add application

|--- Display name

|--- Application name

|--- Server address

|--- Server port

|--- Protocol

|--- Program name

|--- XML trace enabled

|

--- Debug program name

3.12.1.2

HTTP Proxy

For the HTTP data transfer between the phone and the server hosting the remote program, an

HTTP proxy can be used.

First, the proxy itself must be configured. Enter the IP address of the proxy it in the Network >

IP configuration > HTTP proxy parameter, and the corresponding port in the Network > Port configuration > HTTP proxy parameter.

Use proxy enables or disables the use of the proxy. If disabled, the phones connects directly to the server. By default, the use of a proxy is disabled.

Administration via WBM

Applications > XML Applications > Add application

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-127

administration.fm

Administration

Applications

Applications > XML Applications > Modify application

Network > IP Configuration

3-128

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Applications

Administration via Local Phone

|

--- Administration

|

--- Applications

|

--- XML

|--- Add application

|

|

--- Use proxy

|

--- Add Xpressions

|

--- Use proxy

|

--- Administration

|

--- Network

|

--- IP Configuration

|

--- HTTP proxy

|

--- Administration

|

--- Network

|

--- Port configuration

|

--- HTTP proxy

3.12.1.3

Modify an Existing Application

An existing application can be modified by changing its parameters. Please ensure to select the desired application before changing the parameters.

Administration via WBM

Applications > XML applications > Modify application

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-129

administration.fm

Administration

Applications

Administration via Local Phone

|

--- Administration

|

--- Applications

|

--- XML

|

--- <Application to be modified>

|--- Display name

|--- Application name

|--- Server address

|--- Server port

|--- Protocol

|--- Program name

|--- XML trace enabled

|

--- Debug program name

3.12.1.4

Remove an Existing Application

An existing application can be removed. Please ensure to select the desired application before changing the parameters.

Administration via WBM

Applications > XML applications > Modify application

3-130

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Applications

Administration via Local Phone

|

--- Administration

|

--- Applications

|

--- XML

|

--- <Application to be deleted>

3.12.1.5

Application Start by Program Key

To offer more convenience to the user, a previously configured application can be started by a freely programmable key. For this purpose, the appropriate Application name and a Key label must be entered.

Administration via WBM

System > Features > Program Keys

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-131

administration.fm

Administration

Password

3.13

Password

The passwords for user and administrator can be set here. They have to be confirmed after entering. The factory setting is "123456"; it should be changed after the first login.

Administration via WBM

Authentication > Change Admin password

Authentication > Change User password

Administration via Local Phone

|

--- Administration

|

--- Password

|--- Admin

|--- Confirmation

|--- User

|

--- Confirmation

3-132

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Troubleshooting: Lost Password

3.14

Troubleshooting: Lost Password

If the administration and/or user password is lost, and there is no DLS available, new passwords must be provided. For this purpose, a factory reset is necessary. Take the following steps to initiate a factory reset:

1.

On the phone, press the v

key to activate the administration menu (the v

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

2.

Press the number keys 2-8-9 simultaneously. The factory reset menu opens.

3.

In the input field, enter the special password for factory reset: "124816".

4.

Confirm by pressing i

.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-133

administration.fm

Administration

Restart Phone

3.15

Restart Phone

If necessary, the phone can be restarted from the administration menu.

Administration via WBM

3-134

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Factory Reset

3.16

Factory Reset

This function resets all parameters to their factory settings. A special reset password is required for this operation: "124816".

Administration via WBM

Maintenance > Factory reset

Administration via Local Phone

|

--- Administration

|

--- Maintenance

|

--- Factory reset

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-135

administration.fm

Administration

SSH - Secure Shell Access (V2)

3.17

SSH - Secure Shell Access (V2)

With firmware V2, the phone’s operating system can be accessed via SSH for special troubleshooting tasks. Hereby, the administrator is enabled to use the built-in Linux commands. As soon as SSH access has been enabled using the WBM, the system can be accessed by the user "admin" for a specified timespan. When this timespan has expired, no connection is possible any more. The user "admin" has the following permissions:

• Log folder and files: read only

• User data folder and files: read/write access

• Opera deploy folders and files: read only

• Version folder: read/write access; version files: read only

>

It is not possible to logon as root via SSH.

When Enable access is enabled, and the parameters described underneath are specified,

SSH access is activated. By default, SSH access is disabled.

With the Session password parameter, a password for the "admin" user is created. This password is required. It will be valid for the timespan specified in the parameters described underneath.

Access minutes defines the timespan in minuts within which the SSH connection must be established. After it has expired, a logon via SSH is not possible. The possible values are 1, 3, 5,

10, 15.

Session minutes defines the maximum length in minutes for an SSH connection. After it has expired, the "admin" user is logged out. The possible values are 5, 10, 20, 30, 60.

Administration via WBM

3-136

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Display License Information

3.18

Display License Information

The license information for the OpenStage phone software currently loaded can be viewed via the local menu.

|

--- Administration

|

--- Licence information

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-137

administration.fm

Administration

Diagnostics

3.19

Diagnostics

3.19.1

Display General Phone Information

General information about the status of the phone can be displayed if desired.

Displayed Data

MAC address: Shows the phone’s MAC address.

Software version: Displays the version of the phone’s firmware.

Last restart: Shows date and time of the last reboot.

Display on the WBM

General information

Display on the Local Phone

|

--- Administration

|

--- General Information

|--- MAC address

|--- Software version

|

--- Last restart

3-138

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.2

LAN Monitoring

The LAN port mirror facility allows for monitoring all network traffic at the phone’s LAN port. For

further information, see Section 3.2.1, “LAN Port Settings”.

Additionally, there is a possibility to monitor LAN traffic and port settings in the Local user menu:

|

--- User

|

--- Network information

|--- IP address

|--- WBM URL

|--- DNS domain

|--- LAN RX

|--- LAN TX

|--- PC RX

|--- PC TX

|--- LAN autonegotiated

|--- LAN information

|--- PC autonegotiated

|

--- PC information

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-139

administration.fm

Administration

Diagnostics

3.19.3

LLDP-MED

When the phone is connected to a switch with LLDP-MED capabilities, it can receive a VLAN

ID and QoS parameters and advertise its own network-related properties. The data is exchanged in TLV (Type-Length-Value) format.

Both sent and received LLDP-MED data can be monitored at the administrator interface.

>

For details on LLDP-MED, please refer to the ANSI/TIA-1057 standard.

For a network configuration example that shows LLDP-MED in operation, please refer to

Section 4.4, “An LLDP-Med Example”.

Displayed Data

Extended Power: Power Consumption; relevant for PoE.

Network policy (voice): VLAN ID and QoS (Quality of Service) parameters for voice transport.

Network policy (signalling): VLAN ID and QoS (Quality of Service) parameters for signalling.

LLDEP-MED capabilities: The LLDP-MED TLVs supported by the phone and the switch as well as the specific device class they belong to.

MAC_Phy configuration: Identifies the possible duplex and bit-rate capability of the sending device, its current duplex and bit-rate capability, and whether theses settings are the result of auto-negotiation during the initialization of the link, or of manual set override actions.

System capabilities: The devices advertise their potential and currently enabled functions, e. g. "Bridge", "Telephone".

TTL: Time To Live. This parameter determines how long the TLVs are valid. When expired, the devices TTL will send a new set of TLVs.

3-140

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

View Data From WBM

Diagnostics > LLDEP-MED TLVs administration.fm

Administration

Diagnostics

View Data From Local Menu

If both sent and received values are concordant, OK is appended to the parameter. If not, an error message is displayed.

|

--- Administration

|

--- Network

|

--- LLDP-MED operation

|--- Extended Power

|--- Network policy (voice)

|--- LLDEP-MED cap’s

|--- MAC_Phy config

|--- System cap’s

|

--- TTL

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-141

administration.fm

Administration

Diagnostics

3.19.4

IP Tests

For network diagnostics, the OpenStage phone can ping any host or network device to determine whether it is reachable. Additionally, the IP route to a host or network device can be traced using the traceroute tool contained in the phone software.

The Pre Defined Ping tests provide pinging for a pre-defined selection of servers: SIP server and SIP registrar.

Ping tests enables the pinging of a random IP address.

The Pre Defined Trace tests provide traceroute tests for a pre-defined selection of servers:

DLS, SIP server, and SIP registrar.

Traceroute enables traceroute tests for a random IP address.

Administration via WBM

Diagnostics > Miscellaneous > IP tests

3-142

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.5

Process and Memory Information

The processes currently running on the phone’s operating system as well as their CPU and memory usage can be monitored here. 100 processes are displayed on the web page. For further information, please refer to the manual of the "top" command for Unix/Linux systems, or to related documentation.

With firmware version V2, the amount of free memory is checked on a regular basis in order to prevent problems caused by low memory. This check determines whether a recovery is necessary.

When Disable reboot is checked, no reboot will take place when a memory problem has been found. However, recovery requires a reboot.

The recovery process will be triggered when the available main memory (RAM) falls below a given threshold value. As memory consumption is assumed to be higher during working hours, two thresholds are configurable. The High Threshold (MBs) parameter defines the threshold for off-time. For OpenStage 15/20/40, the default value is 10 MB, and for OpenStage 60/80, it is 30 MB. With Low Threshold (MBs), the threshold for off-time is defined. For OpenStage 15/

20/40, the default value is 8 MB, and for OpenStage 60/80, it is 20 MB.

The beginning and end of the working hours are defined in 24 hours format with Working Hour

Start (Default: 5) and Working Hour End (Default: 24).

When memory shortage has occured, information about the incident is written to a log file which can be viewed via the Download memory info file link. If there has been a previous case of memory shortage, the corresponding log file can be viewed via Download memory info file.

Administration via WBM (up to V1R5)

Diagnostics > Miscellaneous > Memory information

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-143

administration.fm

Administration

Diagnostics

Administration via WBM (V2)

Diagnostics > Miscellaneous > Memory information

3-144

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.6

Fault Trace Configuration

Error tracing and logging can be configured separately for all components, i. e. the services and applications running on the OpenStage phone. The resulting files can be viewed in the WBM web pages over the Download links.

The File size (bytes) parameter sets the maximum file size. When the maximum size is reached, the file is deleted, and a new file is generated. The trace data is then written to the new file. The default value is 65536.

The Trace timeout (minutes) determines when to stop tracing, i. e. writing to the trace file.

When the value is 0, no trace file will be written.

If Automatic clear before start is checked, the existing trace file will be deleted on pressing the Submit button, and a new, empty trace file will be generated. By default, it is unchecked.

You can read the log files by clicking on the appropriate hyperlinks (the hyperlinks work only if the file in question has been created). The following logs can be viewed:

• Download trace file

The trace data according to the settings specified for the services.

Download boot file (not present with V2)

The system messages of the booting process. With firmware version V2, these messages are incorparated in the syslog file (see Download syslog file underneath).

• Download saved trace file

Normally, the trace file is saved only in the phone RAM. When the phone restarts in a controlled manner, the trace file will be saved in permanent memory.

Download saved boot file (not present with V2)

Normally, the boot file is saved only in the phone RAM. When the phone restarts in a controlled manner, the boot file will be saved in permanent memory. With firmware version V2, these messages will be incorparated in the syslog file (see Download syslog file underneath).

• Download upgrade trace file

The trace log created during a software upgrade.

Download upgrade error file (not present with V2)

The error messages created during a software upgrade. With firmware version V2, these messages will be incorparated in the syslog file (see Download syslog file underneath).

• Download exception file

If an exceptions occurs in a process running on the phone, a message is written to this file.

Download old exception file (not present with V2)

The exception file is stored permanent memory. When the file has reached its size limit, it will be saved as old exception file, and the current exception file is emptied for future messages. The old exception file can be viewed here.

• Download old trace file

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-145

administration.fm

Administration

Diagnostics

The trace file is stored permanent memory. When the file has reached its size limit, it will be saved as old trace file, and the current exception file is emptied for future messages.

The old trace file can be viewed here.

Download error file (not present with V2)

All error messages the phone has created, according to the settings for the individual services.

• Download syslog file

Messages from the phone’s operating system.

Download old syslog file (with V2)

Old messages from the phone’s operating system.

Download saved syslog file (with V2)

Saved messages from the phone’s operating system.

• Download Database file

Configuration parameters of the phone in SQLite format.

• Download HPT remote service log file

Log data from the HPT service.

• Download dial plan file

If a dial plan has been uploaded to the phone, it is displayed here, along with its status (en-

abled/disabled) and error status. For details, please refer to Section 3.7.3, “Dial Plan (V2)”.

By pressing Submit, the trace settings are submitted to the phone. With Reset, the recent changes can be canceled.

The following trace levels can be selected:

OFF: Default value. Only error messages are stored.

ERROR: Error messages are stored.

TRACE: Trace messages are stored. These contain detailed information about the processes taking place in the phone.

DEBUG: All types of messages are stored.

Brief Descriptions of the Components/Services

• Administration

Deals with the changing and setting of parameters within the phone database, from both the User and Admin menus.

• Application framework

All applications within the phone, e.g. Call view, Call log or Phonebook, are run within the application framework. It is responsible for the switching between different applications and bringing them into and out of focus as appropriate.

• Application menu

This is where applications to be run on the phone can be started and stopped.

• Bluetooth service

3-146

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

Handles the Bluetooth interactions between external Bluetooth devices and the phone.

Bluetooth is available only on OpenStage 60/80 phones.

• Call log

The Call log application displays the call history of the phone.

• Call view

Handles the representation of telephony calls on the phone screen.

• Certificate management

Handles the verification and exchange of certificates for security and verification purposes.

• Communications

Involved in the passing of call related information and signaling to and from the CSTA service.

• Component registrar

Handles data relating to the type of phone, e.g. OpenStage 20/40 HFA/SIP, OpenStage 60/

80 HFA/SIP.

• CSTA service

Any CSTA messages are handled by this service. CSTA messages are used within the phone by all services as a common call progression and control protocol.

• Data Access service

Allows other services to access the data held within the phone database.

• Desktop

Responsible for the shared parts of the phone display. Primarily these are the status bar at the top of the screen and the FPK labels.

• Digit analysis service

Analyses and modifies digit streams which are sent to and received by the phone, e.g. canonical conversion.

• Directory service

Performs a look up for data in the phonebook, trying to match incoming and outgoing numbers with entries in the phonebook.

• DLS client management

Handles interactions with the DLS (only with OpenScape Voice).

• Health service

Monitors other components of the phone for diagnostic purposes and provides a logging interface for the services in the phone.

• Help

Handles the help function.

• Instrumentation service

Used by the Husim phone tester to exchange data with the phone for remote control, testing and monitoring purposes.

• Java

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-147

administration.fm

Administration

Diagnostics

Any Java applications running on the phone will be run in the Java sandbox controlled by the Java service.

• Journal service

Responsible for saving and retrieving call history information, which is used by the Call log application.

• Media control service

Provides the control of media streams (voice, tones, ringing etc. ) within the phone.

• Media processing service

This is a layer of software between the media control service, the tone generation, and voice engine services. It is also involved in the switching of audio devices such as the handset and loudspeaker.

• Mobility service

Handles the mobility feature whereby users can log onto different phones and have them configured to their own profile.

• OBEX service

Involved with Bluetooth accesses to the phone.

Bluetooth is available only on OpenStage 60/80 phones.

• Openstage client management

Provides a means by which other services within the phone can interact with the database.

• Phonebook

Responsible for the phonebook application.

• POT service

Takes over control of basic telephony if the callview application fails.

• Performance Marks

Aid for measuring the performance of the phone. For events triggered by the user, a performance mark is written to the trace file, together with a timestamp in the format hh:mm:ss yyyy.milliseconds, and information about the event. The timespan between two performance marks is an indicator for the performance of the phone.

>

The trace level must be set to "TRACE" or "DEBUG".

• Password management service

Verifies passwords used in the phone.

• Physical interface service

Handles any interactions with the phone via the keypad, mode keys, fixed feature buttons, clickwheel and slider.

• Service framework

This is the environment within which other phone services operate. It is involved in the starting and stopping of services.

3-148

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

• Service registry

Keeps a record of all services currently running inside the phone.

• SIP call control

Contains the call model for the phone and is associated with telephony and call handling.

• SIP messages

Traces the SIP messages exchanged by the phone.

>

After changing the level for the tracing of SIP messages, the phone must be rebooted. Otherwise the changes would have no effect.

• SIP signalling

Involved in the creation and parsing of SIP messages. This service communicates directly with the SIP stack.

• Sidecar service

Handles interactions between the phone and any attached sidecars.

• Team Service

Primarily concerned with keyset operation.

• Tone generation service

Handles the generation of the tones and ringers on the phone.

• Transport service

Provides the IP (LAN) interface between the phone and the outside world.

• USB backup service

Used to make backup/restore to/from USB stick by using password. This item is available in the phone GUI.

• vCard parser service

Handles parsing and identification of VCard information while sending or getting VCards via Bluetooth.

• Voice engine

Provides a switching mechanism for voice streams within the phone. This component is also involved in QDC, Music on hold and voice instrumentation.

• Voice mail

Handles the voice mail functionality.

• Voice recognition

Used by the voice dial facility for recognizing spoken dialing commands.

• Web Server service

Provides access to the phone via web browser.

• 802.1x service

Provides authentication to devices attached to a LAN port, establishing a point-to-point connection or preventing access from that port if authentication fails. The service is used for certain closed wireless access points,

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-149

administration.fm

Administration

Diagnostics

Administration via WBM (up to V1R5)

Diagnostics > Fault Trace Configuration

3-150

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Administration via WBM (V2)

Diagnostics > Fault Trace Configuration administration.fm

Administration

Diagnostics

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-151

administration.fm

Administration

Diagnostics

3.19.7

Easy Trace Profiles

In order to simplify tracing for a specific problem, the tracing levels can be adjusted using predefined settings. The Easy Trace profiles provide settings for a specific area, e. g. call connection. On pressing Submit, those pre-defined settings are sent to the phone. If desired, the settings can be modified anytime using the general mask for trace configuration under

Diagnostics > Fault Trace Configuration (see Section 3.19.6, “Fault Trace Configuration”).

If desired, the tracing for all services can be disabled (see Section 3.19.7.23, “No Tracing for

All Services”).

The following sections describe the Easy Trace profiles available for the phone.

3.19.7.1

Bluetooth Handsfree

Diagnostics > Easy Trace Profiles > Bluetooth handsfree profile

3.19.7.2

Bluetooth Headset

Diagnostics > Easy Trace Profiles > Bluetooth headset profile

3-152

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.7.3

Call Connection

Diagnostics > Easy Trace Profiles > Call connection

>

This Easy Trace profile contains the tracing of SIP messages. Please note that after changing the level for the tracing of SIP messages, the phone must be rebooted.

3.19.7.4

Call Log

Diagnostics > Easy Trace Profiles > Call log problems

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-153

administration.fm

Administration

Diagnostics

3.19.7.5

LDAP Phonebook

Diagnostics > Easy Trace Profiles > Phonebook (LDAP) problems

3.19.7.6

DAS Connection

Diagnostics > Easy Trace Profiles > DAS connection

3.19.7.7

DLS Data Errors

Diagnostics > Easy Trace Profiles > DLS data errors

3-154

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3.19.7.8

802.1x

Diagnostics > Easy Trace Profiles > 802.1x

3.19.7.9

Help Application

Diagnostics > Easy Trace Profiles > Help application problems administration.fm

Administration

Diagnostics

3.19.7.10

Sidecar

Diagnostics > Easy Trace Profiles > Sidecar problems

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-155

administration.fm

Administration

Diagnostics

3.19.7.11

Key Input

Diagnostics > Easy Trace Profiles > Key input problems

3.19.7.12

LAN Connectivity

Diagnostics > Easy Trace Profiles > LAN connectivity problems

3.19.7.13

Local Phonebook

Diagnostics > Easy Trace Profiles > Phonebook (local) problems

3-156

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3.19.7.14

Messaging

Diagnostics > Easy Trace Profiles > Messaging application problems administration.fm

Administration

Diagnostics

3.19.7.15

Mobility

Diagnostics > Easy Trace Profiles > Mobility problems

3.19.7.16

Phone administration

Diagnostics > Easy Trace Profiles > Phone administration problems

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-157

administration.fm

Administration

Diagnostics

3.19.7.17

Server based applications

Diagnostics > Easy Trace Profiles > Server based application problems

3.19.7.18

Speech

Diagnostics > Easy Trace Profiles > Speech problems

3.19.7.19

Tone

Diagnostics > Easy Trace Profiles > Tone problems

3.19.7.20

USB Backup/Restore

Diagnostics > Easy Trace Profiles > USB backup/restore

3-158

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3.19.7.21

Voice Dialling

Diagnostics > Easy Trace Profiles > Voice recognition problems administration.fm

Administration

Diagnostics

3.19.7.22

Web Based Management

Diagnostics > Easy Trace Profiles > Web based management

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-159

administration.fm

Administration

Diagnostics

3.19.7.23

No Tracing for All Services

Diagnostics > Easy Trace Profiles > Clear all profiles

3-160

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.8

Bluetooth Advanced Traces (V2)

For OpenStage 60/80 phones with firmware V2, low level Bluetooth traces can be controlled and viewed via web interface, in addition to the tracing facilities available in previous firmware

versions (see Section 3.19.6, “Fault Trace Configuration”). Internally, the phone uses the hc-

dump utility for creating the traces. It is also possible to run the trace from the shell via SSH (for

information about the SSH access, please refer to Section 3.17, “SSH - Secure Shell Access

(V2)”).

If Automatic clear before start is enabled, the log file will be emptied before the Start button is pressed, so that the log file will only containd newly created entries. By default, this parameter is enabled.

The File size (Max 6290000 bytes) parameter determines the maximum size of the log file. If this value is exceeded, no more data will be written to the file. The default value is 265536.

If Extended dump is enabled, all hexadecimal and ASCII data is displayed for each packet. If disabled, only the packet type is displayed. By default, this parameter is enabled.

If Verbose decoding is enabled, the packets are decoded in a more verbose way. By default, this parameter is enabled.

With the Start/Stop button, tracing is started or halted. The label depends on whether tracing is active or not.

On clicking the Download trace file link, the trace file is displayed.

With Submit, the changes on the parameters described above are sent to the phone.

With Reset, parameter changes that have been made in the form, but not yet sent to the phone, are cancelled.

Administration via WBM

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-161

administration.fm

Administration

Diagnostics

3.19.9

3.19.9.1

QoS Reports

Conditions and Thresholds for Report Generation

>

For details about the functionality, please refer to the release notes.

The generation of QoS (Quality of Service) reports which are sent to a QCU server (see Section 3.3.8, “SNMP”) is configured here.

Data required

Report mode: Sets the conditions for generating a QoS report.

Value range:

• "OFF": No reports are generated.

• "EOS Threshold exceeded": Default value. A report is created if a) a telephone conversation longer than the Minimum session length has just ended, and b) a threshold value has been exceeded during the conversation.

• "EOR Threshold exceeded": A report is created if a) the report interval has just passed, and b) a threshold value has been exceeded during the observation interval.

• "EOS (End of Session)": A report is created if a telephone conversation longer than the Minimum session length has just ended.

• "EOR (End of Report Interval)": A report is created if the report interval has just passed.

Report interval (seconds): Time interval between the periodical observations.

Default: 60.

Observation interval (seconds): During this time interval, the traffic is observed.

Value: 10.

Minimum session length (100 millisecond units): When the Report mode is set to "EOS

Threshold exceeded" or "EOS (End of Session)", a report can be created only if the duration of the conversation exceeds this value.

Default: 20.

Maximum jitter (milliseconds): When the jitter exceeds this value, a report is generated.

Default: 20.

Average round trip delay (milliseconds): When the average round trip time exceeds this value, a report is generated.

Default: 100.

3-162

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

Non-compressing codecs / Compressing codes:

Lost packets (per 1000 packets): When the number of lost packets exceeds this maximum value during the observation interval, a report is created.

Default: 10.

Consecutive lost packets: When the number of lost packets following one another exceeds this maximum value during the observation interval, a report is created.

Default: 2.

Consecutive good packets: When the number of good packets following one another falls below this minimum value, a report is created.

Default: 8.

Resend last report: If checked, the previous report is sent once again on pressing Sub-

mit.

Value range: "Yes", "No".

Default: "No".

The transmission of report data can be triggered manually by pressing Send now in the local menu.

Administration via WBM

Diagnostics > QoS Reports > Generation

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-163

administration.fm

Administration

Diagnostics

Administration via Local Phone

|

--- Administration

|

--- Network

|

--- QoS

|

--- Reports

|--- Generation

| |--- Mode

| |--- Report interval

| |--- Observe interval

|

|

--- Minimum session length

|--- Send now

|

--- Thresholds

|--- Maximum jitter

|--- Round-trip delay

|--- Non-compressing:

|--- ...Lost packets (K)

|--- ...Lost consecutive

|--- ...Good consecutive

|--- Compressing:

|--- ...Lost packets (K)

|--- ...Lost consecutive

|

--- ...Good consecutive

3-164

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.9.2

View Report

OpenStage phones generate QoS reports using a specific format, QDC (QoS Data Collection).

The reports created for the last 6 sessions, i. e. conversations, can be viewed on the WBM.

To enable the generation of reports, please ensure that:

the switch QoS traps to QCU (System > SNMP) is activated (see Section 3.3.8, “SNMP”);

the conditions for the generation of reports are set adequately (see Section 3.19.9.1, “Conditions and Thresholds for Report Generation”).

For details about QoS reports, see the HiPath QoS Data Collection V 1.0 Service Manual.

A QoS report contains the following data:

Start of report period - seconds: NTP time in seconds for the start of the report period.

Start of report period - fraction of seconds: Additional split seconds to be added to the seconds for an exact start time.

End of report period - seconds: NTP time in seconds for the end of the report period.

End of report period - fraction of seconds: Additional split seconds to be added to the seconds for an exact end time.

SNMP specific trap type: The trap type is a 5 bit value calculated from a list of thresholdexceeding bits. Every time a threshold is exceeded, the associated bit is set, otherwise it is cleared.

The trace type bits are defined as follows:

• Bit 0: Jitter threshold was exceeded.

• Bit 1: Delay threshold was exceeded.

• Bit 2: Threshold for lost packets was exceeded.

• Bit 3: Threshold for consecutive lost packets was exceeded.

• Bit 4: Threshold for consecutive good packets was exceeded.

IP address (local): IP address of the local phone.

Port number (local): RTP receiving port of the local phone.

IP address (remote): IP address of the remote phone that took part in the session.

Port number (remote): RTP sending port of the local phone.

SSRC (receiving): RTP Source Synchronization Identifier of the local phone.

SSRC (sending): RTP Source Synchronization Identifier of the remote phone.

Codec: Number of the Payload Type applied in the session; see RFC 3551 (Table 4 and

5).

Maximum packet size: Maximum size (in ms) of packets received during the report interval.

Silence suppression: Number of silence suppression activation objects found in the RTP stream received. A silence suppression activation object is defined as a period of silence when no encoded voice signals were transmitted by the sender.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-165

administration.fm

Administration

Diagnostics

Count of good packets: Total amount of good packets.

Maximum jitter: Maximum jitter (in ms) found during the report interval.

Maximum inter-arrival jitter: Maximum of the interarrival jitter values (in ms). The interarrival jitter is the smoothed absolute value of the jitter measurements. It is calculated continuously. For details about the calulation, see RFC 3550.

Periods jitter threshold exceeded: Number of observation intervals in which the threshold for maximum jitter was exceeded.

Round trip delay: Average value of delay calculated for each RTCP packet. The first value is available after about 15 sec.

Round trip delay threshold exceeded: Set to "true" if the average round trip delay threshold value was exceeded in the report interval.

Count of lost packets: Number of packets lost in the course of speech decoding.

Count of discarded packets: Number of the packets discarded without transferring the contents.

Periods of lost packets: Number of observation intervals in which the threshold for lost packets was exceeded.

Consecutive packet loss (CPL): List of sequences consecutive packets that were all lost, grouped according to the amount of packets per sequence. The first number in the list counts single lost packets, the second number counts sequences of two lost packets, and so on. The last number counts sequences of more than 10 lost packets.

Periods of consecutive lost packets: Number of observation intervals in which the threshold for consecutive lost packets was exceeded.

Consecutive good packets (CGP): List of sequences consecutive packets that were all processed, grouped according to the amount of packets per sequence. The first number in the list counts single good packets, the second number counts sequences of two good packets, and so on. The last number counts sequences of more than 10 good packets. All values are reset to 0 after an interval without packet loss.

Periods of consecutive good packets: Number of intervals in which the count of lost packets went below the threshold.

Count of jitter buffer overruns: Number of packets rejected because the jitter buffer was full.

Count of jitter buffer under-runs: Increased by one whenever the decoder requests new information on decoding and finds an empty jitter buffer.

Codec change on the fly: The value is 1, if there has been a codec or SSRC change during the observation period, and 0, if there has been no change.

Periods with at least one threshold exceeded: Number of observation intervals with at least one threshold exceedance. If there is no data, the value is 255. The threshold values included are:

• maximum jitter;

• lost packets;

3-166

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

• consecutive lost packets;

• consecutive good packets.

HiPath Switch ID: Unique number identifying the HiPath switch to which the endpoints are assigned.

LTU number: In HiPath 4000 only, the shelf identification is taken from the shelf containing a gateway.

Slot number: The slot number where the phoneis connected in the shelf.

Endpoint type: Type of the local phone.

Version: Software version of the local phone.

Subscriber number type: Type of subscriber number assigned to the local phone. The possible types are:

• 1: local number, extension only;

• 2: called number, network call

• 3: E.164 number of the local phone.

Subscriber number: Subscriber number of the local phone.

Call ID: SIP call id.

MAC address: MAC address of the local phone.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-167

administration.fm

Administration

Diagnostics

Data viewing via WBM

Diagnostics > QoS reports > View Session Data

3-168

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Diagnostics

3.19.10

Core dump

If Enable core dump is checked, a core dump will be initiated in case of a severe error. The core dump will be saved to a file. By default, this function is activated.

When File size unlimited is checked, there is no size limit for the core dump file. By default, it is not checked.

The maximum size for core dump files in MBytes can be chosen in the Limited file size (MBs) field. The possible values are 1, 5, 10, 25, 50, 75, and 100. The default value is 100.

If Delete core dump is activated, the current core dump file is deleted on Submit. By default, this is not activated.

If one or more core dump file exist, hyperlinks for downloading will be created automatically.

Administration via WBM

Diagnostics > Miscellaneous > Core dump

3.19.11

Remote Tracing - Syslog

All trace messages created by the components of the phone software can be sent to a remote server using the syslog protocol. This is helpful especially for long-term observations with a greater number of phones.

To enable remote tracing, Remote trace status must be set to "Enabled". Furthermore, the IP address of the server receiving the syslog messages must be entered in Remote ip, and the corresponding server port must be given in Remote port.

Administration via Local Phone

|

--- Administration

|

--- Maintenance

|

--- Remote trace

|--- Remote trace status

|--- Remote ip

|

--- Remote port

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-169

administration.fm

Administration

Diagnostics

3.19.12

HPT Interface (For Service Staff)

For special diagnosis and maintenance tasks, the service staff may employ the HPT tool, which is able to control and observe an OpenStage phone remotely. For security reasons, this tool

can only be used when a dongle key file is uploaded to the phone (see Section 3.9.10, “HPT

Dongle Key”). This key is accessable to the service staff only. It is specific for a particular SIP

firmware version, but it will also be valid for previous versions.

There are 2 types of HPT sessions, control session and observation session.

A control session allows for activating phone functions remotely. When a control session is established, the following changes will occur:

• The display shows a message indicating that remote service is active.

• Handset, microphone, speaker, headset, and microphone are disabled.

An observation session allows for supervising events on the phone, like, for instance, pressing a key, incoming calls or navigating in the menus. Before an observation session is started, the user is prompted for allowing the observation. During an observation session, the phone operates normally, including loudspeaker, microphone and ringer. Thus, the local user can demonstrate an error towards the service staff that is connected via HPT.

The HPT interface is enabled by downloading the dongle key file to the phone (see Section

3.9.10, “HPT Dongle Key”). It can be disabled via local menu or WBM. Thereby, the dongle key

file is deleted. To enable the HPT interface again, the file must be downloaded anew.

The session data is written to a log file on the phone. It can be downloaded from the Diagnostics

> Fault trace configuration menu (see Section 3.19.6, “Fault Trace Configuration”).

Administration via WBM

Maintenance > HPT interface

Administration via Local Phone

|

--- Administration

|

--- Maintenance

|

--- Disable HPT / Enable HTP

3-170

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

administration.fm

Administration

Bluetooth

3.20

Bluetooth

The Bluetooth interface can be enabled or disabled in the admin menu. By default, it is enabled.

If Bluetooth is enabled, the user has the possibility to activate or deactivate it. The Bluetooth address is displayed.

>

Bluetooth is available only on OpenStage 60/80 phones.

Administration via WBM

System > Features > Configuration

Administration via Local Phone

|

--- Administration

|

--- System

|

--- Features

|

--- Configuration

|

--- Bluetooth

|--- Local device address

|

--- Enable

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

3-171

administration.fm

Administration

Bluetooth

3-172

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

Canonical Dialing

4 Examples and HowTos

4.1

Canonical Dialing

4.1.1

Canonical Dialing Settings

The following example shows settings suitable for the conversion of given dial strings to canonical format. The example phone is located in Nottingham, UK.

Parameter

Local country code

National prefix digit

Local national code

Minimum local number length

Local enterprise node

PSTN access code

Operator codes

Emergency numbers

Initial extension digits

Example value Explanation

44

0

International country code for the UK.

Used in front of national codes when dialled without international prefix.

115

7

780

Area code within the UK (here: Nottingham).

Minimum number of digits in a local PSTN number (e. g. 3335333 = 7 digits).

Prefix to access Nottingham numbers from within the Siemens network.

Prefix to make an international call in the UK.

9

0, 7800 Set of numbers to access the local operators.

999, 555 Set of numbers to access emergency services.

2, 3, 4, 5, 6, 8 1 st

digits of numbers that are used for extension numbers on the local node.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-1

beispiele.fm

Examples and HowTos

Canonical Dialing

4.1.2

Canonical Dial Lookup

The following example shows settings suitable for recognizing incoming numbers and assigning them to entries in the local phone book, and for generating correct dial strings from phone book entries, depending on whether the number is internal or external.

Parameter

Local code <1>

International code <1>

Local code <2>

International code <2>

Example value Explanation

780

+44115943

Enterprise node prefix (here: Nottingham).

Equivalent prefix to access numbers on this node from the PSTN. Here, the prefix used by the PSTN (DID/DDI: direct inward dialing) is

943, which differs from the enterprise node prefix used within the enterprise network.

722

+4989722

Enterprise node prefix (here: Munich).

Equivalent prefix to access numbers on this node from the PSTN. Here, the prefix used by the PSTN for direct inward dialing is identical to the enterprise node prefix.

4-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

Canonical Dialing

4.1.2.1

Conversion examples

In the following examples, numbers entered into the local phonebook by the user are converted according to the settings given above.

Example 1: Internal number, same node as the local phone

User entry

External numbers

External access code

International gateway code

Number stored in the phone book

Dial string sent when dialing from the phone book

Internal numbers = Local enterprise form

Internal numbers = Always add node

Internal numbers = Use external numbers

Example 2: Internal number, different node

2345

Local public form

Not required

Use national code

+441159432345

1234

7802345

9432345

User entry

External numbers

External access code

International gateway code

Number stored in the phone book

Dial string sent when dialing from the phone book

Internal numbers = Local enterprise form

Internal numbers = Always add node

Internal numbers = Use external numbers

7222345

Local public form

Not required

Use national code

+49897222345

2345

7802345

9432345

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-3

beispiele.fm

Examples and HowTos

Canonical Dialing

Example 3: External number, same local national code as the local phone

User entry

External numbers

External access code

International gateway code

Number stored in the phone book

Dial string sent when dialing from the phone book

External numbers = Local public form

External numbers = National public form

External numbers = International form

011511234567

Local public form

Not required

Use national code

+4411511234567

234567

011511234567

004411511234567

4-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

How to Create Logo Files for OpenStage Phones

4.2

How to Create Logo Files for OpenStage Phones

4.2.1

For OpenStage 40

1.

Create a New Image

Create an image with the following specifications:

• Width: 144 px

• Height: 32 px

• Color Mode: 1 bit (monochrome)

Adobe Photoshop:

2.

Insert the Logo

Place the logo image on the background, e.g. by copying it from a source file. Due to the size and color specifications, some adaptations may be necessary.

Adobe Photoshop Example:

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-5

beispiele.fm

Examples and HowTos

How to Create Logo Files for OpenStage Phones

3.

Save the Image

Finally, save the image in BMP format. You can now upload the logo file to the phone as

described in Section 3.9.7, “Logo”.

4.2.2

For OpenStage 60/80

In the following, the creation of a transparent image suitable for use as a logo in OpenStage 60/

80 is described. This description is based on Adobe Photoshop, but any similar graphics software can be used as well.

>

Because of performance issues, half transparency in the alpha channel of the PNG files is not allowed on OpenStage phones. Therefore only 100% transparency or no transparency is used in the phone’s UI elements.

1.

Select the Background Color

For production purposes, we set the background color to the background color of the skin currently selected on the phone. Later, the background color will be replaced by transparency, which facilitates placing a logo on a gradient background. The following table lists the hexadecimal values, as used in HTML:

Phone Type Skin

OpenStage 60 Crystal Sea

OpenStage 60 Warm Grey

OpenStage 80 Crystal Sea

Color Code

#BDBDBD

#424242

1

#E6EBEF

OpenStage 80 Warm Grey #3A3D3A

1 The background color on WP4 - skin 1 is a gradient; the colour listed here is an average value.

Adobe Photoshop:

Click on the Background Color icon on the Color palette group, then type the color code without leading "#" into the # field)

4-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

How to Create Logo Files for OpenStage Phones

2.

Create a New Image

Create an image with the size according to the phone type:

Phone Type

OpenStage 60

OpenStage 80

Adobe Photoshop:

Size (px)

240 x 70

480 x 142

3.

Insert the Logo

Place the logo image on the background, e.g. by copying it from a source file.

Adobe Photoshop Example:

4.

Merge Layers

Merge the two layers to one.

Adobe Photoshop:

In the Panel, select both the background layer and the new layer containing the inserted logo. Afterwards, go to Layer in the Menu bar, and select Merge Layers.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-7

beispiele.fm

Examples and HowTos

How to Create Logo Files for OpenStage Phones

v

5.

Background Transparency

Delete the background colour so that only the exact former background colour is 100% transparent.

Adobe Photoshop:

Make sure that the background color is selected by clicking on the Background Color icon.

In the Tool palette, click on the Eraser symbol with the right Mouse button and select the

Magic Eraser Tool. After this, got to the Menu bar and set the Tolerance field to "0".

6.

Save the Image

Finally, save the image in PNG format. You can now upload the logo file to the phone as

described in Section 3.9.7, “Logo”.

4-8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

4.3

How to Set Up the Corporate Phonebook (LDAP)

The Corporate Phonebook function is based on an LDAP client that can be connected to the company’s LDAP service. A variety of LDAP servers can be used, for instance Microsoft Active

Directory, OpenLDAP, or Apache Directory Server.

>

The Corporate Phonebook is available only on OpenStage 60/80.

4.3.1

Prerequisites:

1.

An LDAP server is present and accessible to the phone’s network. The standard port for

LDAP is 389.

2.

Query access to the LDAP server must be provided. Unless anonymous access is used, a user name and passwort must be provided. It might be feasible to use a single login/password for all OpenStage phones.

3.

To enable dialing internal numbers from the corporate phonebook, an LDAP entry must be provided that contains the proper number format required by the PBX.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-9

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

4.3.2

Create an LDAP Template

The user interface of the corporate phonebook application provides a form which is used both for search and retrieval.

The task of an LDAP template is to map the phone’s search and display fields to LDAP attributes that can be delivered by the server. In the LDAP template, the fields are represented by hard-coded names:

ATTRIB01, ATTRIB02, and so on. These field names are assigned to

LDAP attributes, as appropriate.

4-10

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

The following examples show the relations between GUI field names, the attribute labels used in the template, and exemplary mappings to LDAP attributes.

Generic Example (Standard Attributes)

OpenStage Field LDAP

Template

Lables

Last name

First name

Business 1

Business 2

Mobile

Private

Company

Address 1

Address 2

Job function

Email

LDAP Attribute Example

Value

ATTRIB01 sn

ATTRIB02 givenName

Doe

John

ATTRIB03 telephoneNumber 9991234

ATTRIB04 facsimileTelephoneNumber 9992345

ATTRIB05 mobile

ATTRIB06 homePhone

ATTRIB07 o

ATTRIB08 departmentNumber

017711223344

441274333444

Example Inc.

0815

ATTRIB09

ATTRIB10 title

ATTRIB11 mail

Product Manager [email protected]

Given "example.com" as the LDAP subtree to be searched, the LDAP template file would look like this:

OpenStage LDAP TEMPLATE (v.1)

SEARCHBASE="dc=example,dc=com"

ATTRIB01="sn"

ATTRIB02="givenname"

ATTRIB03="telephoneNumber"

ATTRIB04="facsimileTelephoneNumber"

ATTRIB05="mobile"

ATTRIB06="homePhone"

ATTRIB07="o"

ATTRIB08="departmentNumber"

ATTRIB09=""

ATTRIB10="title"

ATTRIB11="mail"

EOF

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-11

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

Microsoft Active Directory Specific Example

OpenStage Field LDAP

Template

Attribute

Last name

First name

Business 1

Business 2

Mobile

Private

Company

Address 1

Address 2

Job function

Email

LDAP Attribute

ATTRIB01 sn

ATTRIB02 givenName

ATTRIB03 ipPhone

ATTRIB04 otherTelephone

ATTRIB05 mobile

ATTRIB06 homePhone

ATTRIB07 company

ATTRIB08 department

ATTRIB09

ATTRIB10 title

ATTRIB11 mail

Example

Value

Doe

John

9991234

9992345

017711223344

441274333444

Example Inc.

Administration

Product Manager [email protected]

Given "example.com" as the LDAP subtree to be searched, the LDAP template file would look like this:

OpenStage LDAP TEMPLATE (v.1)

SEARCHBASE="dc=example,dc=com"

ATTRIB01="sn"

ATTRIB02="givenname"

ATTRIB03="ipPhone"

ATTRIB04="otherTelephone"

ATTRIB05="mobile"

ATTRIB06="homePhone"

ATTRIB07="company"

ATTRIB08="department"

ATTRIB09=""

ATTRIB10="title"

ATTRIB11="mail"

EOF

4-12

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

4.3.3

Load the LDAP Template into the Phone

When you have configured the LDAP template, you can upload it to the phone:

1.

Save the template under a suitable name, for example, ldap-template.txt.

2.

Copy the template file to the FTP server designated for deploying LDAP templates.

3.

Upload the file using the WBM (see Section 3.9.6, “LDAP Template”), or, alternatively, the

Local menu. For an example configuration, see the following WBM screenshot (path: File

transfer > LDAP):

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-13

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

4.3.4

Configure LDAP Access

To enter the access data using the WBM, take the following steps:

1.

Navigate to Local Functions > Directory Settings.

2.

Enter the following parameters:

Server address (IP address or hostname of the LDAP server)

Server port (port used by the LDAP, typically 389)

Authentication (authentication method for the connection to the LDAP server)

User name (only required if simple authentication is selected); Password (relating to the user name).

3.

Press Submit.

4.3.5

Test

If everything went well, you can run a test query on your OpenStage phone.

1.

To navigate to the phone’s corporate phonebook, press the u

button twice.

2.

Press g

on the TouchGuide. In the context menu, select Find by pressing i

.

3.

In the query mask, select the entry to be searched, for instance Last Name. Press i

to open the onscreen keypad for text input.

4-14

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

4.

Enter the text to be searched. For information on using the onscreen keypad, see Section

3.1, “Access via Local Phone”, step 5.

5.

Navigate to the Find option and press i

. If the query was successful, at least one entry will be listed in the following manner:

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-15

beispiele.fm

Examples and HowTos

How to Set Up the Corporate Phonebook (LDAP)

6.

Navigate to the desired entry and press g

on the TouchGuide to open the context menu.

You can select one of the following options:

• Dial the Business 1 number.

• Dial the Mobile number.

• Have the entry’s details, that is, all attributes displayed.

• Start a new search.

• Clear the list of search results.

4-16

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

An LLDP-Med Example

4.4

An LLDP-Med Example

The following example illustrates the mode of operation of LLDP-MED. In order to evoke a reaction from LLDP-MED, the LAN switch has been set to auto-negotiation, whereas the phone’s

LAN port (see Section 3.2.1, “LAN Port Settings”) is set to 100Mbit/s, hence a fixed value. This

configuration error is discovered by LLDP-MED. The following sceenshots from the phone’s local menu will show the error messages.

This screenshot shows the LLDP-MED operation submenu (see Section 3.2.3, “LLDP-MED

Operation”). Please note the status of MAC_Phy config.

When MAC_Phy config is selected, the details are displayed.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-17

beispiele.fm

Examples and HowTos

An LLDP-Med Example

4-18

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

An LLDP-Med Example

4.4.1

How To Set Up And Deploy A Dial Plan

For creating and deploying a dial plan to an OpenStage phone, a working installation of the

DLS (version V2R4 onwards) is required. This HowTo describes the creation of a simple dial plan for OpenStage phones by example. Unless otherwise stated, the actions described underneath are made in the DLS.

1.

Log on to the DLS with an account that has suitable rights for deploying a dial plan. For details, please refer to the Deployment Service Administration Manual.

2.

Navigate to IP Devices > IP Phone Configuration > Features > "Dialplan" tab.

3.

Check Dialplan, if not checked already.

4.

Enter a suitable Dialplan ID.

5.

Click on to create the first dial plan rule.

6.

Enter the following data:

Parameter

Digit string

Action

Value

3

S

Description/Remarks

This rule matches numbers beginning with 3. For instance, theses might be internal numbers.

When all criteria are met, the number is sent to the server.

This rule matches numbers with a length of 4 digits.

Minimum length 4

Maximum length 4

Timer 0 The specified Action will take place without delay when all other criteria are met.

Summary: This rule determines that digit strings which begin with 3 and have a length of 4 digits are sent to the server without delay after the last digit has been entered.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-19

beispiele.fm

Examples and HowTos

An LLDP-Med Example

7.

Click on to create the second dial plan rule.

8.

Enter the following data:

Parameter

Digit string

Action

Value

0

C

Description/Remarks

This rule matches numbers beginning with 0. In the

USA, this number calls the operator.

When Minimum length, Maximum length, and the length of the digit string entered by the user match, the

Timer is started. When it expires, the digits are sent to the server. When another digit is entered before expiry, the next dial plan entry will come into operation.

This rule matches numbers with a length of 1 digits.

Minimum length

1

Maximum length

1

Timer

1

The phone waits 1 second for further digits. If the user does not enter any further digits, the action specified in

Action is initiated.

Summary: When 0 is entered as first digit, the phone will wait 1 second. After this, 0 will be sent to the server, which might result in a call to an operator, for instance. When further digits are entered during the 1 second timespan, the next dial plan rule will take control.

9.

Click on to create the third dial plan rule.

4-20

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

beispiele.fm

Examples and HowTos

An LLDP-Med Example

10. Enter the following data:

Parameter

Digit string

Action

Minimum length

Maximum length

Timer

Terminating

Character

Value

011

S

4

13

3

#

Description/Remarks

This rule matches numbers beginning with 011. In the

USA, this digit string is the prefix international calls.

When the entered digit string reaches the Minimum

length, the Timer is started. On expiry, the digit string is sent.

When the length of the digit sequence entered by the user reaches this value, the Timer is started.

When the length of the digit sequence entered by the user reaches this value, the digits are sent to the server immediately. The Timer is overridden.

When the length of the digit sequence entered by the user reaches the Minimum length, the phone waits 3 seconds for further digits. If the user does not enter any further digits, the Action is triggered.

When this character is entered, the digits are sent to the server immediately, regardless of the criteria contained in this rule.

Summary: Any numbers that start with 011 and have a length of 13 digits are sent to the server immediately. Shorter numbers with a length from 4 digits onwards are sent after a

3 seconds delay.

11. The example dial plan is completed; it should look like this:

12. You can check the dial plan using the phone’s web interface; navigate to Diagnostics >

Fault trace configuration > Download dial plan file.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

4-21

beispiele.fm

Examples and HowTos

An LLDP-Med Example

4-22

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Menus

5

5.1

Technical Reference

Menus

>

This section describes the structure of the administration menus of the OpenStage phone. For information on user menus, please refer to the user manual.

5.1.1

Web Interface Menu

5.1.1.1

Admin Login

Menu Structure

Applications (OpenStage 60/80)

XML applications

Add application

Modify application

Xpressions

XML Phonebook

Bluetooth

Network

IP configuration

QoS

Port configuration (OpenStage 20/40) / Port configuration (OpenStage 60/80)

LLDP-MED operation

System

System Identity / System Identity (V2)

SIP interface

Registration

SNMP

Features

Configuration (OpenStage 20/40) / Configuration (OpenStage 20/40 V2) / Configura-

tion (OpenStage 60/80) / Configuration (OpenStage 60/80 V2)

Program keys

Key Module 1

Key Module 2

Fixed Keys

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-1

referenz.fm

Technical Reference

Menus

Keyset operation / Keyset operation (V2)

Services

Security

File transfer

Defaults

Phone application

Hold music

Picture Clip (OpenStage 60/80)

LDAP (OpenStage 60/80)

Logo (OpenStage 40/60/80)

Screensaver (OpenStage 60/80)

Ringer file

Dongle key

Local functions

Directory settings (OpenStage 60/80)

Messages Settings (V2)

Locality

Canonical dial settings

Canonical dial lookup

Canonical dial

Energy saving

Date and time

Speech

Codec preferences

Audio settings

General information

Authentication

Change Admin password

Change User password

Ringer Setting (V2)

Diagnostics

LLDP-MED TLVs

Fault trace configuration / Fault trace configuration (V2)

EasyTrace Profiles

Bluetooth handsfree profile (OpenStage 60/80)

Bluetooth headset profile (OpenStage 60/80)

5-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Call connection

Call log problems

DAS connection

Help application problems (OpenStage 60/80)

Key input problems

LAN connectivity problems

Messaging application problems

Mobility problems

Phone administration problems

Phonebook (LDAP) problems (OpenStage 60/80)

Phonebook (local) problems (OpenStage 60/80)

Server based application problems (OpenStage 60/80)

Sidecar problems

Speech problems

Tone problems

USB backup/restore

Voice recognition problems (OpenStage 60/80)

Web based management / Web based management (V2)

802.1x problems

Clear all profiles

Bluetooth Advanced Traces (V2)

QoS Reports

Generation

View Session Data

Miscellaneous

IP tests

Memory information / Memory information (V2)

Core dump

Maintenance

Remote trace

Restart phone

Factory reset

Secure Shell (V2)

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-3

referenz.fm

Technical Reference

Menus

5.1.1.2

Web Pages

Admin Login

Add application

5-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Modify application

Xpressions

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-5

referenz.fm

Technical Reference

Menus

XML Phonebook

Bluetooth

5-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

IP configuration

QoS

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-7

referenz.fm

Technical Reference

Menus

Port configuration (OpenStage 20/40)

Port configuration (OpenStage 60/80)

LLDP-MED operation

5-8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

System Identity

System Identity (V2)

SIP interface

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-9

referenz.fm

Technical Reference

Menus

Registration

SNMP

5-10

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Configuration (OpenStage 20/40)

referenz.fm

Technical Reference

Menus

Configuration (OpenStage 20/40 V2)

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-11

referenz.fm

Technical Reference

Menus

Configuration (OpenStage 60/80)

Configuration (OpenStage 60/80 V2)

5-12

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Program keys

Key Module 1

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-13

referenz.fm

Technical Reference

Menus

Key Module 2

Fixed Keys

Keyset operation

5-14

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Menus

Keyset operation (V2)

Services

Security

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-15

referenz.fm

Technical Reference

Menus

Defaults

Phone application

Hold music

5-16

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Menus

Picture Clip

LDAP

Logo

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-17

referenz.fm

Technical Reference

Menus

Screensaver

Ringer file

Dongle key

5-18

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Directory settings (OpenStage 60/80)

Directory settings (V2)

Messages Settings

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-19

referenz.fm

Technical Reference

Menus

Canonical dial settings

Canonical dial lookup

Canonical dial

Energy saving

5-20

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Menus

Date and time

Codec preferences

Audio settings

General information

Change Admin password

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-21

referenz.fm

Technical Reference

Menus

Change User password

Ringer Setting

5-22

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

LLDP-MED TLVs

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-23

referenz.fm

Technical Reference

Menus

Fault trace configuration

5-24

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Fault trace configuration (V2)

referenz.fm

Technical Reference

Menus

Bluetooth handsfree profile

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-25

referenz.fm

Technical Reference

Menus

Bluetooth headset profile

Call connection

Call log problems

DAS connection

5-26

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Help application problems

Key input problems

LAN connectivity problems

Messaging application problems

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-27

referenz.fm

Technical Reference

Menus

Mobility problems

Phone administration problems

Phonebook (LDAP) problems

Phonebook (local) problems

5-28

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Server based application problems

Sidecar problems

Speech problems

Tone problems

USB backup/restore

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual referenz.fm

Technical Reference

Menus

5-29

referenz.fm

Technical Reference

Menus

Voice recognition problems

Web based management

Web based management (V2)

5-30

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Menus

802.1x problems

Clear all profiles

Bluetooth Advanced Traces (V2)

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-31

referenz.fm

Technical Reference

Menus

Generation

5-32

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

View Session Data

referenz.fm

Technical Reference

Menus

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-33

referenz.fm

Technical Reference

Menus

IP tests

Memory information

5-34

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Memory information (V2)

referenz.fm

Technical Reference

Menus

Core dump

Remote trace

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-35

referenz.fm

Technical Reference

Menus

Remote trace (V2)

Restart phone

Factory reset

Secure Shell

5-36

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Menus

5.1.2

Local Phone Menu

Menu

|--- Administration

| |--- Applications

1

| | |--- CPP

| | |--- Java

| |

|

--- XML

| | |--- Add application

| | | |--- Display name

| | | |--- Application name

| | | |--- Server address

| | | |--- Server port

| | | |--- Protocol

| | | |--- Program name

| | | |--- Use proxy

| | | |--- XML trace enabled

| | | |--- Debug program name

| | | |--- Number of tabs

| | | |--- Tab 1 display name

| | | |--- Tab 1 application name

| | | |--- Tab 2 display name

| | | |--- Tab 2 application name

| | | |--- Tab 3 display name

| | | |--- Tab 3 application name

| | |

|

--- Restart after change

| | |--- Add Xpressions

| | | |--- Display name

| | | |--- Application name

| | | |--- Server address

| | | |--- Server port

| | | |--- Protocol

| | | |--- Program name

| | | |--- Use proxy

| | | |--- XML trace enabled

| | | |--- Debug program name

| | | |--- Number of tabs

| | | |--- Tab 1 display name

| | | |--- Tab 1 application name

| | | |--- Tab 2 display name

| | | |--- Tab 2 application name

| | | |--- Tab 3 display name

| | | |--- Tab 3 application name

| | |

|

--- Restart after change

| |

|

--- Add phonebook

| | |--- Display name

| | |--- Application name

| | |--- Server address

| | |--- Server port

| | |--- Protocol

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Further information ...

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

5-37

referenz.fm

Technical Reference

Menus

Menu

| | |--- Program name

| | |--- Use proxy

| | |--- XML trace enabled

| | |--- Debug program name

| | |--- Number of tabs

| | |--- Tab 1 display name

| | |--- Tab 1 application name

| | |--- Tab 2 display name

| | |--- Tab 2 application name

| | |--- Tab 3 display name

| | |--- Tab 3 application name

| |

|

--- Restart after change

| |--- Bluetooth

1

| |

|

--- Enable

| |--- Network

| | |--- IP configuration

| | | |--- Discovery mode

| | | |--- Use LLDP-Med

| | | |--- Use DHCP

| | | |--- IP address

| | | |--- Subnet mask

| | | |--- Route (default)

| | | |--- DNS domain

| | | |--- Primary DNS

| | | |--- Secondary DNS

| | | |--- Route 1 IP

| | | |--- Route 1 gateway

| | | |--- Route 1 mask

| | | |--- Route 2 IP

| | | |--- Route 2 gateway

| | | |--- Route 2 mask

| | | |--- VLAN discovery

| | | |--- VLAN ID

| | |

|

--- HTTP proxy

| | |--- QoS

| | | |--- Service

| | | | |--- Layer 2

| | | | |--- Layer 2 voice

| | | | |--- Layer 2 signalling

| | | | |--- Layer 2 default

| | | | |--- Layer 3

| | | | |--- Layer 3 voice

| | | |

|

--- Layer 3 signalling

| | |

|

--- Reports

| | | |--- Generation

| | | | |--- Mode

| | | | |--- Report interval

| | | | |--- Observe interval

| | | |

|

--- Minimum session length

| | | |--- Send now

| | |

|

--- Thresholds

5-38

Further information ...

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.12.1

-> Section 3.20

-> Section 3.2.2

-> Section 3.2.2

-> Section 3.2.2

-> Section 3.3.3

-> Section 3.3.3

-> Section 3.3.4

-> Section 3.3.6.1

-> Section 3.3.6.2

-> Section 3.3.6.2

-> Section 3.3.6

-> Section 3.3.6

-> Section 3.3.6

-> Section 3.3.6

-> Section 3.3.6

-> Section 3.3.6

-> Section 3.2.2.1

-> Section 3.2.2.3

-> Section 3.12.1.2

-> Section 3.3.1.1

-> Section 3.3.1.1

-> Section 3.3.1.1

-> Section 3.3.1.1

-> Section 3.3.1.2

-> Section 3.3.1.2

-> Section 3.3.1.2

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9.1

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Menu

| | | |--- Maximum jitter

| | | |--- Round-trip delay

| | | |--- Non-compressing:

| | | |--- ...Lost packets (K)

| | | |--- ...Lost consecutive

| | | |--- ...Good consecutive

| | | |--- Compressing:

| | | |--- ...Lost packets (K)

| | | |--- ...Lost consecutive

| | |

|

--- ...Good consecutive

| | |--- Port configuration

| | | |--- SIP server

| | | |--- SIP registrar

| | | |--- SIP gateway

| | | |--- SIP local

| | | |--- Backup proxy

| | | |--- RTP base

| | | |--- LDAP server port

1

| | | |--- LAN port type

| | | |--- PC port status

| | | |--- PC port type

| | | |--- PC port autoMDIX

| | |

|

--- HTTP proxy

| |

|

--- LLDP-MED operation

| | |--- Extended Power

| | |--- Network policy (voice)

| | |--- LLDEP-MED cap’s

| | |--- MAC_Phy config

| | |--- System cap’s

| |

|

--- TTL

| |--- System

| | |--- Identity

| | | |--- Terminal number

| | | |--- Terminal name

| | | |--- Display identity

| | | |--- Enable ID

| | | |--- Web name

| | |

|

--- DDNS hostname

| | |--- SIP Interface

| | | |--- Outbound proxy

| | | |--- Default OBP domain

| | | |--- SIP transport

| | | |--- Call trans (ms)

| | | |--- NonCall trans (ms)

| | | |--- Registration backoff

| | |

|

--- Connectivity timer (ms)

| | |--- Registration

| | | |--- SIP addresses

| | | | |--- SIP server

| | | | |--- SIP registrar

| | | |

|

--- SIP gateway

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual referenz.fm

Technical Reference

Menus

Further information ...

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.19.9

-> Section 3.4.5.2

-> Section 3.4.5.2

-> Section 3.4.5.2

-> Section 3.4.5.2

-> Section 3.4.9.5

-> Section 3.11.1

-> Section 3.10.1

-> Section 3.2.1

-> Section 3.2.1

-> Section 3.2.1

-> Section 3.2.1

-> Section 3.12.1.2

-> Section 3.19.3

-> Section 3.19.3

-> Section 3.19.3

-> Section 3.19.3

-> Section 3.19.3

-> Section 3.2.3

-> Section 3.4.1.1

-> Section 3.4.1.1

-> Section 3.4.1.2

-> Section 3.4.1.2

-> Section 3.4.7.1

-> Section 3.4.7.1

-> Section 3.4.7.2

-> Section 3.4.9.2

-> Section 3.4.9.3

-> Section 3.4.9.4

-> Section 3.4.9.1

-> Section 3.4.5.1

-> Section 3.4.5.1

-> Section 3.4.5.1

5-39

referenz.fm

Technical Reference

Menus

Menu

| | | |--- SIP session

| | | | |--- Session timer

| | | | |--- Session duration (s)

| | | | |--- Registration timer (s)

| | | | |--- Server type

| | | | |--- Realm

| | | | |--- User ID

| | | |

|

--- Password

| | |

|

--- SIP survivability

| | | |--- Backup registration flag

| | | |--- Backup proxy address

| | | |--- Backup registration timer (s)

| | | |--- Backup transport

| | |

|

--- OBP flag

| | |--- SNMP

| | | |--- Queries allowed

| | | |--- Query password

| | | |--- Trap sending enabled

| | | |--- Trap destination

| | | |--- Trap destination port

| | | |--- Trap community

| | | |--- Diagnostic sending enabled

| | | |--- Diagnostic destination

| | | |--- Diagnostic destination port

| | | |--- Diagnostic community

| | | |--- QoS traps to QCU

| | | |--- QCU address

| | | |--- QCU port

| | | |--- QCU community

| | |

|

--- QoS to generic destination

| |

|

--- Features

| | |--- Configuration

| | | |--- General

| | | | |--- Emergency number

| | | | |--- Voicemail number

| | | | |--- Allow refuse

| | | | |--- Hot/warm phone

| | | | |--- Hot/warm destination

| | | | |--- Initial digit timer

| | | | |--- Allow uaCSTA

| | | | |--- Server features

| | | | |--- Transfer on hangup

| | | | |--- Not used timeout

| | | | |--- DSS Pickup timer

| | | |

|

--- Bridging enabled

| | | |--- Audio

| | | |

| | |

|

|

--- BLF alerting

--- Bluetooth

1

| | | |--- Local device address

| | |

|

--- Enable

| |

|

--- Addressing

5-40

Further information ...

-> Section 3.4.8

-> Section 3.4.8

-> Section 3.4.6

-> Section 3.4.6

-> Section 3.4.6

-> Section 3.4.6

-> Section 3.4.6

-> Section 3.4.9.5

-> Section 3.4.9.5

-> Section 3.4.9.5

-> Section 3.4.9.5

-> Section 3.4.9.5

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.3.8

-> Section 3.4.2

-> Section 3.4.2

-> Section 3.5.1

-> Section 3.5.3

-> Section 3.5.8

-> Section 3.5.7

-> Section 3.5.4.2

-> Section 3.5.9

-> Section 3.20

-> Section 3.20

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Menu

| | |--- MWI server URI

| |

|

--- BLF pickup code

| |--- File Transfer

| | |--- Defaults

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | |

|

--- HTTPS base URL

| | |--- Phone app

| | | |--- Use default

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

|

--- Filename

| | |--- Hold Music

| | | |--- FTP Use default

| | | |--- FTP Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

|

--- Filename

| | |--- Ringer

| | | |--- Use default

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

|

--- Filename

| | |--- Picture clip

1

| | | |--- Use default

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual referenz.fm

Technical Reference

Menus

Further information ...

-> Section 3.5.5

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.2

-> Section 3.9.3

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.3.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.4.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.5.1

5-41

referenz.fm

Technical Reference

Menus

Menu

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

|

--- Filename

| | |--- LDAP

1

| | | |--- Use default

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

|

--- Filename

| | |--- Logo

2

| | | |--- Use default

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

|

--- Filename

| | |--- Screensaver

1

| | | |--- Use default

| | | |--- Download method

| | | |--- FTP Server

| | | |--- FTP Port

| | | |--- FTP Account

| | | |--- FTP Username

| | | |--- FTP Password

| | | |--- FTP path

| | | |--- HTTPS base URL

| | |

| |

|

|

--- Filename

--- Java midlets

1

| | |--- Use default

| | |--- Download method

| | |--- FTP Server

| | |--- FTP Port

| | |--- FTP Account

| | |--- FTP Username

| | |--- FTP Password

| | |--- FTP path

| | |--- HTTPS base URL

| |

|

--- Filename

| |--- Local Functions

| | |--- Directory Settings

1

5-42

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Further information ...

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.5.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.6.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.7.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

-> Section 3.9.8.1

Menu

| | | |--- Server address

| | | |--- Server port

| | | |--- Timeout (sec) for Search Trigger

| | | |--- Authenticate

| | | |--- User name

| | |

|

--- Password

| | |--- Locality

| | | |--- Canonical settings

| | | | |--- Local country code

| | | | |--- National prefix digit

| | | | |--- Local national code

| | | | |--- Minimum local number length

| | | | |--- Local enterprise node

| | | | |--- PSTN access code

| | | | |--- International access code

| | | | |--- Operator code

| | | | |--- Emergency number

| | | |

|

--- Initial digits

| | | |--- Canonical lookup

| | | | |--- Local code 1

| | | | |--- International code 1

| | | | |--- Local code 2

| | | | |--- International code 2

| | | | |--- Local code 3

| | | | |--- International code 3

| | | | |--- Local code 4

| | | | |--- International code 4

| | | | |--- Local code 5

| | | |

|

--- International code 5

| | |

|

--- Canonical dial

| | | |--- Internal numbers

| | | |--- External numbers

| | | |--- External access code

| | |

|

--- International access code

| | |--- Energy saving

2

| | |

|

--- Backlight timeout

| |

|

--- Messages settings

| | |--- New items

| | |--- Alternative Label

| | |--- New urgent items

| | |--- Alternative label

| | |--- Old items

| | |--- Alternative label

| | |--- Old urgent items

| |

|

--- Alternative label

| |--- Date and Time

| | |--- Time source

| | | |--- SNTP IP address

| | |

|

--- Timezone offset

| |

|

--- Daylight saving

| | | |--- Daylight saving

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual referenz.fm

Technical Reference

Menus

Further information ...

-> Section 3.10.1

-> Section 3.10.1

-> Section 3.10.1

-> Section 3.10.1

-> Section 3.10.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.2

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.7.1

-> Section 3.4.3

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.5.6

-> Section 3.4.4.1

-> Section 3.4.4.1

-> Section 3.4.4.1

-> Section 3.4.4.1

-> Section 3.4.4.1

5-43

referenz.fm

Technical Reference

Menus

Menu

| | | |--- Difference (mins)

| | | |--- Auto DST

| | |

|

--- DST zone

| |--- Speech

| | |--- Codec Preferences

| | | |--- Silence suppression

| | | |--- Packet size

| | | |--- G.711

| | | |--- G.729

| | |

|

--- G.722

| |

|

--- Audio Settings

| | |--- Disable microphone

| |

|

--- Disable loudspeech

| |--- General Information

| | |--- MAC address

| | |--- Software version

| | |--- Last restart

| |--- Licence information

| |--- Password

| | |--- Admin

| | |--- Confirm admin

| | |--- User

| |

|

--- Confirm user

|

|

--- Maintenance

| |--- Factory reset

| |--- Remote trace

| | |--- Remote trace status

| | |--- Remote ip

| |

|

--- Remote port

|

|

--- Remote trace

| |--- Disable reboot

| |--- High treshold

| |--- Low treshold

| |--- Working Hour Start

|

|

--- Working Hour End

1 OpenStage 60/80 only.

2 OpenStage 40/60/80 only.

Further information ...

-> Section 3.4.4.1

-> Section 3.4.4.1

-> Section 3.4.4.1

-> Section 3.11.2

-> Section 3.11.2

-> Section 3.11.2

-> Section 3.11.2

-> Section 3.11.2

-> Section 3.11.3

-> Section 3.11.3

-> Section 3.19.1

-> Section 3.19.1

-> Section 3.19.1

-> Section 3.18

-> Section 3.13

-> Section 3.13

-> Section 3.13

-> Section 3.13

-> Section 3.16

-> Section 3.19.11

-> Section 3.19.11

-> Section 3.19.11

5-44

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

referenz.fm

Technical Reference

Troubleshooting: Error Codes

5.2

Troubleshooting: Error Codes

For a set of error cases, specific error codes are defined. These error codes are shown in brackets on the display, following a general error note. Example: „No Telephony possible

(LP1)“.

Problem

Network Problem

Not Initialised

Description

No network connection

Waiting for data

Unable to use LAN 802.1x error

Unable to use LAN Physical connection missing

Unable to Register Server timeout

Unable to Register Server failed

Unable to Register Authentication failed

Unable to Register No number configured

Unable to Register No server configured

Unable to Register No registrar configured

Unable to Register No DNS domain configured

Unable to Register Rejected by server

Unable to Register No phone IP address set

Survivability Backup route active

Survivability

Survivability

Survivability

Backup not configured

Backup timeout

Backup authentication failed

RA2

RN2

RS2

RG2

RD2

RR2

RI2

B8

Error code

LI1

I1

LX1

LP1

RT2

RF2

RS8

RT8

RA8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

5-45

referenz.fm

Technical Reference

Troubleshooting: Error Codes

5-46

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch bkglos.fm

Glossary

Glossary

X

A

Address of Record (AoR)

A ->SIP ->URI that represents the "public address" of a SIP user resp. a phone or line. The

format is similar to an E-mail address: "username@hostname". (for a definition, see RFC

3261)

ADPCM

Adaptive Differential Pulse Code Modulation. A compressed encoding method for audio

signals which are to be transmitted by a low bandwidth. As opposed to regular ->PCM, a

sample is coded as the difference between its predicted value and its real value. As this difference is usually smaller than the real, absolute value itself, a lesser number of bits can be used to encode it.

C

CSTA

Computer Supported Telecommunications Applications. An abstraction layer for telecom-

munications applications allowing for the interaction of ->CTI computer applications with te-

lephony devices and networks.

CTI

Computer Telephony Integration. This term denotes the interaction of computer applications with telephony devices and networks.

D

DFT

Digital Feature Telephone. A phone with no line keys.

DHCP

Dynamic Host Configuration Protocol. Allows for the automatic configuration of network endpoints, like IP Phones and IP Clients.

DiffServ

Differentiated Services. Specifies a layer 3 mechanism for classifying and managing net-

work traffic and providing quality of service (->QoS) guarantees on ->IP networks. DiffServ

can be used to provide low-latency, guaranteed service for e. g. voice or video communication.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

X-1

bkglos.fm

Glossary

Nur für den internen Gebrauch

DNS

Domain Name System. Performs the translation of network domain names and computer

hostnames to ->IP addresses.

DTMF

Dual Tone Multi Frequency. A means of signaling between a phone and e. g. a voicemail facility. The signals can be transmitted either in-band, i. e. within the speech band, or outband, i. e. in a separate signaling channel.

E

EAP

Extensible Authentication Protocol. An authentication framework that is frequently used in

WLAN networks. It is defined in RFC 3748.

F

FTP

File Transfer Protocol. Used for transferring files in networks, e. g., to update telephone software.

G

G.711

ITU-T standard for audio encoding, used in ISDN and ->VoIP. It requires a 64 kBit/s band-

width.

G.722

ITU-T standard for audio encoding using split band ->ADPCM. The audio bandwidth is 7

kHz at a sampling rate of 16 kHz. There are several transfer rates ranging from 32 to 64 kBit/s, which correspond to different compression degrees. The voice quality is very good.

G.729

ITU-T standard for audio encoding with low bandwidth requirements, mostly used in VoIP.

The standard bitrate is 8 kBit/s. Music or tones such as ->DTMF or fax tones cannot be

transported reliably with this codec.

Gateway

Mediation components between two different network types, e. g., ->IP network and ISDN

network.

GUI

Graphical User Interface.

X-2

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch bkglos.fm

Glossary

H

HTTP

Hypertext Transfer Protocol. A standard protocol for data transfer in ->IP networks.

I

IP

Internet Protocol. A data-oriented network layer protocol used for transferring data across a packet-switched internetwork. Within this network layer, reliability is not guaranteed.

IP address

The unique address of a terminal device in the network. It consists of four number blocks of 0 to 255 each, separated by a point.

J

Jitter

Latency fluctuations in the data transmission resulting in distorted sound.

L

LAN

Local Area Network. A computer network covering a local area, like an office, or group of buildings.

Layer 2

2nd layer (Data Link Layer) of the 7-layer OSI model for describing data transmission interfaces.

Layer 3

3rd layer (Network Layer) of the 7-layer OSI model for describing the data transmission interfaces.

LCD

Liquid Crystal Display. Display of numbers, text or graphics with the help of liquid crystal technology.

LDAP

Lightweight Directory Access Protocol. Simplified protocol for accessing standardized directory systems, e.g., a company telephone directory.

LED

Light Emitting Diode. Cold light illumination in different colours at low power consumption.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

X-3

bkglos.fm

Glossary

Nur für den internen Gebrauch

LLDP

Link Layer Discovery Protocol (IEEE Standard 802.1AB). Provides a solution for the discovery of elements on a data network and how they are connected to each other.

M

MAC Address

Media Access Control address. Unique 48-bit identifier attached to network adapters.

MDI-X

Media Dependent Interface crossover (X). The send and receive pins are inverted. This

MDI allows the connection of two endpoints without using a crossover cable. When Auto

MDI-X is available, the MDI can switch between regular MDI and MDI-X automatically, depending on the connected device.

MIB

Management Information Base. A type of database used to manage the devices in a communications network.

MWI

Message Waiting Indicator. A signal, typically a LED, to notify the user that new mailbox messages have arrived.

P

PBX

Private Branch Exchange. Private telephone system that connects the internal devices to each other and to the ISDN network.

PCM

Pulse Code Modulation. A digital representation of an analog signal, e. g. audio data, which consists of quantized samples taken in regular time intervals.

PING

Packet Internet Gro(u)per. A program to test whether a connection can be made to a defined IP target. Data is sent to the target and returned from there during the test.

PoE

Power over Ethernet. The IEEE 802.3af standard specifies how to supply power to compliant devices over Ethernet cabling (10/100Base-T).

Port

Ports are used in ->IP networks to permit several communication connections simulta-

neously. Different services often have different port numbers.

X-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch bkglos.fm

Glossary

PSTN

Public Switched Telephone Network. The network of the world's public circuit-switched telephone networks.

Q

QoS

Quality of Service. The term refers to control mechanisms that can provide different priority to different users or data flows, or guarantee a certain level of performance to a data flow in accordance with requests from the application program. The OpenStage phone allows for the setting of QoS parameters on layer 2 and layer 3 (DiffServ).

QDC

QoS Data Collection. A HiPath IP service that is used to collect data from HiPath products in order to analyze their voice and network quality.

QCU

Quality of Service Data Collection Unit. A service tool that collects QoS report data from

IP endpoints.

QoS

Quality of Service. Provides different priority to different users or data flows, or guarantee a certain level of performance to a data flow.

R

RAM

Random Access Memory. Memory with read / write access.

ROM

Read Only Memory. Memory with read only access.

RTCP

Realtime Transport Control Protocol. Controls the ->RTP stream and provides information

about the status of the transmission, like QoS parameters.

RTP

Realtime Transport Protocol. This application layer protocol has been designed for audio

and video communication. Typically, the underlying protocol is ->UDP.

S

SDP

Session Description Protocol. Describes and initiates multimedia sessions, like web con-

ferences. The informations provided by SDP can be processed by ->SIP.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

X-5

bkglos.fm

Glossary

Nur für den internen Gebrauch

SIP

Session Initiation Protocol. Signaling protocol for initialising and controlling sessions, used

e. g. for ->VoIP calls.

SNMP

Simple Network Management Protocol. Used for monitoring, controlling, and administration of network and network devices.

SNTP

Simple Network Time Protocol. Used to synchronize the time of a terminal device with a timeserver.

Subnet Mask

To discern the network part from the host part of an ->IP address, a device performs an

AND operation on the IP address and the network mask. The network classes A, B, and C each have a subnet mask that demasks the relevant bits: 255.0.0.0 for Class A,

255.255.0.0 for Class B and 255.255.255.0 for Class C. In a Class C network, for instance,

254 IP addresses are available.

Switch

Network device that connects multiple network segments and terminal devices. The for-

warding of data packets is based on ->MAC Addresses: data targeted to a specific device

is directed to the switch port that device is attached to.

T

TCP

Transfer Control Protocol. The protocol belongs to the transport layer and establishes a connection between two entities on the application layer. It guarantees reliable and in-order

delivery of data from sender to receiver, as opposed to ->UDP.

TLS

Transport Layer Security. Ensures privacy between communicating applications. Typically, the server is authenticated, but mutual authentication is also possible.

U

UDP

User Datagram Protocol. A minimal message-oriented transport layer protocol used espe-

cially in streaming media applications such as ->VoIP. Reliability and order of packet deliv-

ery are not guaranteed, as opposed to ->TCP, but ->UDP is faster and more efficient.

URI

Uniform Resource Identifier. A compact string of characters used to identify or name a resource.

X-6

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch bkglos.fm

Glossary

URL

Uniform Resource Locator. A special type of ->URI which provides means of acting upon

or obtaining a representation of the resource by describing its primary access mechanism or network location.

V

VLAN

Virtual Local Area Network. A method of creating several independent logical networks within a physical network. For example, an existing network can be separated into a data and a voice VLAN.

VoIP

Voice over IP. A term for the protocols and technologies enabling the routing of voice con-

versations over the internet or through any other ->IP-based network

W

WAP

Wireless Application Protocol. A collection of protocols and technologies aiming at enabling access to internet applications for wireless devices. WAP can also be used by the

OpenStage phone.

WBM

Web Based Management. A web interface which enables configuration of the device using a standard web browser.

WML

Wireless Markup Language. An XML-based markup language which supports text,

graphics, hyperlinks and forms on a ->WAP-browser.

WSP

Wireless Session Protocol. The protocol is a part of the ->WAP specification. Its task is to

establish a session between the terminal device and the WAP gateway.

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

X-7

bkglos.fm

Glossary

Nur für den internen Gebrauch

X-8

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch

OperaAdminSIX.fm

Index

Index

Z

A

Address of Record (AoR) 6-1

Administration Menu (Local Menu) 3-1, 3-2

Application Keys 1-3, 1-4, 1-5

Audio Keys 1-3, 1-4, 1-6

B

Bluetooth 3-171

C

Call Display 1-3, 1-4

Call Transfer 3-57

Canonical Dial Lookup 3-83

Canonical Dialing 3-79

CSTA 3-63, 6-1

CTI 6-1

D

Date and Time (SNTP) 2-9, 3-34

Daylight Saving 3-34

Default Route 3-19

DFT (Digital Feature Telephone) 6-1

DHCP 3-16, 6-1

Diffserv 3-14

DLS (Deployment Service) 3-24, 6-2

DNS 3-21, 6-2

DNS Domain Name 3-21

DST Zone (Daylight Saving Time Zone) 3-34

E

Emergency Number 3-32, 3-79

External Access Code 3-80

External Numbers 3-80

F

FTP Settings 3-89

Function Keys 1-3, 1-4, 1-5, 1-6

G

Graphics Display 1-3, 1-4

H

Handset 1-3, 1-4, 1-5, 1-6

I

Initial Digits 3-80

Internal Numbers 3-80

International Code (Local Country Code) 3-

79

International Gateway Code 3-81

International Prefix (International Access Code) 3-79

IP

Address 2-9

Address (Manual Configuration) 3-18

IP 6-3

Specific Routing 3-20

K

Keypad 1-3, 1-4, 1-5, 1-6

L

LAN 6-3

LAN Port 3-5

LDAP 6-3

LDAP Template (Download) 3-100

Local Area Code (Local National Code) 3-79

Local Country Code (International Code) 3-

79

Local Enterprise Number 3-79

Local National Code (Local Area Code) 3-79

Logo (Create) 4-5

Logo (Download) 3-103

M

MAC Address 6-4

MDI-X 3-5, 6-4

MIB 6-4

Music on Hold (Download) 3-94

MWI 3-59

MWI (Message Waiting Indicator) 6-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Z-1

OperaAdminSIX.fm

Index

Nur für den internen Gebrauch

N

National Prefix (Trunk Prefix) 3-79

O

Operator Code 3-79

Outbound Proxy 3-42

P

Password, change 3-132

Password, enter 3-1

PBX 6-4

Phone Software (Download) 3-91

Picture Clips (Download) 3-97

PoE (Power over Ethernet) 2-5, 6-4

Program Keys 1-3, 1-4, 1-6

PSTN 6-5

PSTN Aaccess Code 3-79

Q

QCU 3-27

QoS 3-13

R

RTP 6-5

S

Screensaver (Download) 3-106

SIP

Registration 3-39

Server Addresses 3-37

Server Ports 3-38

Session Timer 3-44

Transport Protocol 3-43

SNMP 3-26, 6-6

Subnet Mask 2-9

Subnet Mask (Manual Configuration) 3-18

T

TCP 6-6

Terminal Number 2-9, 3-30

Timeout (Not used) 3-64

Timezone Offset 2-9, 3-34

TLS 6-6

TouchGuide 1-3, 1-4, 1-5, 1-6

TouchSlider 1-3

Z-2

Trunk Prefix (National Prefix) 3-79

U

uaCSTA 3-63

UDP 6-6

V

VLAN 2-11, 3-7

Voice Mail Number 3-32

W

WBM (Web Based Management) 1-6, 2-7, 6-

7

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Nur für den internen Gebrauch

OperaAdminSIX.fm

Index

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

Z-3

OperaAdminSIX.fm

Index

Nur für den internen Gebrauch

Z-4

A31003-S2000-M102-2-76A9, 28/05/2009

OpenScape Voice - OpenStage Family, Administration Manual

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Related manuals

Download PDF

advertisement

Table of contents