Handleiding Unify OpenScape Desk Phone CP600 (pagina 45 van 189) (Engels)

680295

Verklein

Vergroot

Pagina terug

1/189

Pagina verder

OpenScape Desk Phone

CP200/CP205/CP400/CP600

Phone Administration HFA

Administration Manual

A31003-C1000-M102-5-76A9

Our Quality and Environmental Management Systems are

implemented according to the requirements of the ISO9001 and

ISO14001 standards and are certified by an external certification

company.

Mies-van-der-Rohe-Str. 6, 80807 Munich/Germany

Reference No.: A31003-C1000-M102-5-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.

Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and

Solutions GmbH & Co. KG. All other company, brand, product and service names are

trademarks or registered trademarks of their respective holders.

unify.com

Startup

A31003-C1000-M102-5-76A9, 09/2017

30 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

inbetriebnahme.fm

Quick Start

6. In the DHCP console menu, right-click the DHCP server in question and select Set Pre-

defined Options from the context menu.

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

a new option.

inbetriebnahme.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Startup

Quick Start

8. Enter the following data for the new option:

1. First Pass: Option 1

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

• Data type: "String"

• Code: "1"

• Description: Free text.

2. Second Pass: Option 2

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

• Data type: "Long"

• Code: "2"

• Description: Free text.

9. Enter the value for this option.

1. First Pass: "Siemens"

2. Second Pass: VLAN ID

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

Startup

A31003-C1000-M102-5-76A9, 09/2017

32 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

inbetriebnahme.fm

Quick Start

Defining the scope for the new vendor class

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

Configure Options... in the context menu.

12. Select the Advanced tab. Under Vendor class, select the class that you previously de-

fined (OptiIpPhone) and, under User class, select Default User Class.

Activate the check boxes for the options that you want to assign to the scope (in the exam-

ple, 001, 002, and 003). Click OK.

13. The DHCP console now shows the information that will be transmitted for the correspond-

ing workpoints. Information from the Standard vendor is transmitted to all clients, whereas

information from the OptiIpPhone vendor is transmitted only to the clients (workpoints) in

this vendor class.

inbetriebnahme.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Startup

Quick Start

Setup using a DHCP server on Unix/Linux

The following snippet from a DHCP configuration file (usually dhcpd.conf) shows how to set up

a configuration using a vendor class and the "vendor-encapsulated-options" option.

class "OptiIpPhone" {

option vendor-encapsulated-options

# The vendor encapsulated options consist of hexadecimal values for

the option number (for instance, 01), the length of the value (for in-

stance, 07), and the value (for instance, 53:69:65:6D:65:6E:73). The

options can be written in separate lines; the last option must be fol-

lowed by a ’;’ instead of a ’:’.

# Tag/Option #1: Vendor "Siemens"

#1 7 S i e m e n s

01:07:53:69:65:6D:65:6E:73:

# Tag/Option #2: VLAN ID

#2 4 00 1 0

02:04:00:00:00:0A;

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

"OptiIpPhone";

}

2.3.8.2 Using Option #43 "Vendor Specific"

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

• Tag 001: Vendor name

• Tag 002: VLAN ID

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

line contains the hexadecimal values):

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

For manual configuration of the VLAN ID see Section 3.2.2.1, “Automatic VLAN discovery using

LLDP-MED”.

Code Length Vendor name

17Siemens

01 07 53 69 65 6D 65 6E 73

Code Length VLAN ID

240010

02 04 00 00 00 0A

Startup

A31003-C1000-M102-5-76A9, 09/2017

34 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

inbetriebnahme.fm

Quick Start

Setup using the Windows DHCP Server

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

2. Select the DHCP server and the scope. Choose "Configure Options" in the context menu

using the right mouse button.

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

Bytes long.

inbetriebnahme.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Startup

Quick Start

2.3.9 DLS Server Address

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

It is recommended to configure the DLS server address by DCHP, as this method enables full

Plug & Play and ensures the authenticity of the DLS server.

For manual configuration of the DLS server address see Section 3.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.

2.3.9.1 Using Vendor Class

It is recommended to define a vendor class on the DHCP server, thus enabling server and

phone to exchange vendor-specific data exclusively. The data is disclosed from other clients. If

not done already, create a vendor class by the name of "OptiIpPhone".

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

Setting up a new vendor class using the Windows DHCP Server

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

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

Vendor Classes... in the context menu.

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Administration

Bluetooth Interface

3 Administration

This chapter describes the configuration of every parameter available on the OpenScape Desk

Phone CP phones. Please refer to Section 2.3.1, “How to Access the Web Interface (WBM)”.

3.1 Bluetooth Interface

3.1.1 Feature Access

You can activate and deactivate the Bluetooth interface. If the Bluetooth interface is deactivated

no Bluetooth services are available.

Administration via WBM

Bluetooth

Administration via Local Phone

Bluetooth is available only on Open Scape Desk Phone CP600.

--- Bluetooth

Server Address

Server Port

Zone

Off

Disabled

Localization client

Submit

Reset

Bluetooth

Enable Bluetooth interface

;

Feature Access

Enable

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Administration

System Settings

3.5.11.2 Access control

The CCE access parameter controls TCP and UDP access for the CCE (CommsChannel

Extender). This affects the operation of the OpenStage Manager, local CTI access, and HPT

access. When Disable is selected, both TCP and UDP are disabled. With Enable, there are no

restrictions.

With Factory reset claw, the ’hooded claw’ keypad mechanism to initiate a factory reset with-

out requiring an authenticated access can be enabled or disabled.

The Serial port parameter controls access to the serial port. When set to No password, a ter-

minal connected to the port can interact with the phone’s operating system without restric-

tions. When Passwd reqd is selected, the serial port requires a password for access (root user

is not available). When Unavailable is chosen, the serial port is not accessible.

As a prerequisite, the root user needs to create a user and to define a password via Serial

Access, so that access can be granted when the Password required prompt is issued.

Administration via WBM

System > Security > Access control

Administration via Local Phone

--- Administration

--- System

--- Security

--- Access control

|--- CCE access

|--- Factory reset claw

--- Serial port

Factory reset claw

Access control

Submit

Reset

Serial port

Unavailable

CCE access

Enable

Administration

A31003-C1000-M102-5-76A9, 09/2017

82 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Dialing

3.6 Dialing

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

tension "1234", the local country code is "49", the local national code is "89", and the local en-

terprise number is "722", the resulting number in canonical format is "+49897221234".

For generating an appropiate dial string, a conversion from canonical 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 re-

quired by the PBX.

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

dom. 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 node: Number of the company/PBX wherein the phone is residing. Max-

imum 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 numbers: 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)

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

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

“Canonical Dialing Configuration”).

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Administration

Dialing

• 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 com-

paring the first digit of the call number to the value(s) given here. If it matches, the call num-

ber is recognized as a local enterprise number and processed accordingly.

If, for instance, the extensions 3000-5999 are configured in the OpenScape Desk Phone

IP, each number will start with 3, 4, or 5. Therefore, the digits to be entered are 3, 4, 5.

• Internal numbers

• "Local enterprise form": Default value. Any extension number is dialed in its simplest

form. For an extension on the local enterprise node, the node ID is omitted. If the ex-

tension 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 exten-

sion are treated as external numbers.

• "Always add node": Numbers that correspond to an enterprise node extension are al-

ways prefixed with the node ID, even those on the local node. Numbers that do not cor-

respond 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 dialed 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 mo-

bile). Numbers for a different country are dialled using the international format.

• "International form": All numbers are dialled using their full international number for-

mat.

• External access code

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

required.

• "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 net-

work. However, international numbers that use the + prefix will not be given access

code.

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

crucial that a canonical lookup table is provided (Section 3.6.1, “Canonical Di-

aling Configuration”).

Administration

A31003-C1000-M102-5-76A9, 09/2017

84 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Dialing

• 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 "+" pre-

fix.

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

Administration via WBM

Local functions > Locality > Canonical dial settings

Local functions > Locality > Canonical dial

Canonical dial settings

Local country code

National prefix digit

Local national code

Minimum local number length

Local enterprise node

PSTN access code

723

International access code

Submit

Reset

Operator codes

Emergency numbers

Initial extension digits

1,2,3,4

Canonical dial

Internal numbers

External numbers

External access code

Not required

Local public form

International gateway code

Use national code

Submit

Reset

Local enterprise form

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Administration

Dialing

Administration via Local Phone

3.6.2 Canonical Dial Lookup

The parameters given here are important for establishing outgoing calls and for recognizing in-

coming calls.

In the local phonebook, and, mostly, in LDAP directories, numbers are stored in canonical for-

mat. In order to generate an appropriate dial string according to the settings in Internal num-

bers and External numbers, internal numbers must be discerned from external numbers. The

canonical lookup table provides patterns which allow for operation.

Furthermore, these patterns enable the phone to identify callers from different local or interna-

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

--- Admin

--- Local Functions

--- Locality

--- Canonical settings

|--- Local country code

|--- National prefix digit

|--- Local national code

|--- Min(imum) local num(ber) length

|--- Local enterprise node

|--- PSTN access code

|--- International access code

|--- Operator code

|--- Emergency number

--- Initial extension digits

--- Admin

--- Local Functions

--- Locality

--- Canonical dial

|--- Internal numbers

|--- External numbers

|--- External access code

--- Internat(iona)l access

Administration

A31003-C1000-M102-5-76A9, 09/2017

86 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Dialing

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: "7007" for Unify 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: "+49897007" for Unify Munich.

Administration via WBM

Locality > Canonical dial lookup

Administration via Local Phone

To make sure that canonical dial lookup works properly, at least the following para-

meters of the phone must be provided:

• Local country code

• Local area code

• Local enterprise code

--- Admin

--- Local Functions

--- Locality

--- Canonical lookup

|--- Local code 1

|--- International 1

|--- Local code 2

|--- International 2

|--- Local code 3

|--- International 3

|--- Local code 4

|--- International 4

|--- Local code 5

--- International 5

Canonical dial lockup

Local code 1:

Local code 2:

Local code 3:

Local code 4:

Local code 5:

Submit

Reset

International code 1:

International code 2:

International code 3:

International code 4:

International code 5:

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Administration

Distinctive Ringing

3.7 Distinctive Ringing

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

call. The phone can use this information to choose a ring tone according to the call type. A list

of different ring types is maintained in the phone.

Any ringer sound may either be

• OpenScape specified tones

• Audio file (selected from the pool of ringer files on the phone)

• Constructed (from melody and tone sequence settings)

The ringer sounds are system controlled by default.

Once distinctive ringing is configured locally a system control of the ringer parameters is not

possible. If system control of the ringer is desired the ringer mode must be set to “HiPath”.

Even though the ringers are configured locally the behaviour of the ringers should be the same

as system controlled ones. In particular, cyclic ringers shall be played endlessly until the switch

commands to stop playing (and therefore repeated if necessary), whereas single shot ringers

should play for just a short period - the intention being to alert the phone user to a new state of

the phone but not to hinder the ongoing conversation. This short period is defined to be 3 sec-

onds. It should be possible to interrupt the playing of the cyclic ringer to play the single shot

ringer and after timeout the cyclic ringing should resume. This behaviour is independent of

whether low or high quality ringer files are played or whether the ringer is pattern generated.

The value in Octet 12 in the CorNet AU_RINGER_START message is used as an index into

ringers configured on the phone. The indexed entry indicates the ringing to be used for the call.

In any cases if a distinctive ring is requested then the associated ring type is used instead of

the default ringer. The ringing is played immediately when requested. If distinctive ringing is not

requested or cannot be matched to a ringer then, the tone specified in the CorNet ringer mes-

sage by the OpenScape system will be used to construct the ring tone.

Distinctive ringer naming

There is no configuration necessary to set the names. CorNet specifies the ringer types and

enumerations. Please be aware that the naming refers to the call type as sent in the CorNet

message, not to be confused with a feature or a call scenario. The mapping of calltype to fea-

ture or call scenario occurs in the system and this may be configurable (e.g. in HiPath 4000 by

means of AMO ZAND). It is up to the administrator to configure such that the user hears the

required ring tones for the various features/call scenarios. Also note that only the set of call

types actually implemented by the system should be offered for configuration of the ringers.

Currently OpenScape Business only implements a subset of those in CorNet. It is assumed that

this set is relatively stable.

Administration

A31003-C1000-M102-5-76A9, 09/2017

88 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Distinctive Ringing

Ringer setting and preview

The configuration of distinctive ringers overlaps considerably with the general ringer configura-

tion feature and the ability to preview (manually and automatically) what a ringer sounds like.

Data required

• Name: Selects the call type to be used. In OpenScape 4000, for “Speaker call” function the

call type “Rollover call” is used in the CorNet AU_RINGER_START message.

Value range OpenScape 4000: "Internal call", "External call", "Buzz call", "Rollover call",

"Alert (simple)", "Alert (multiple)", "Special #1", "Special #2", "Special #3", "Attention ring-

er", "Unspecified call", " US DSN precedence ring", "US DSN routine ring", "Emergency

call"

Value range OpenScape Business: "Internal call", "External call", "Attention ringer"

Default: "Internal call".

• Ringer sound: ‘Pattern’ or the name of the selected ring tone file. Sets the distinctive ring-

er to use the currently set pattern (melody and sequence). This is the pattern that will be

used if the configured ring tone file cannot be played for any reason.

Value range: "Pattern", "<audio file>"

Default: "Pattern".

• Pattern melody: Selects the melody pattern that will be used if Ringer sound is set to

"Pattern".

Value range: "1"... "8"

Default: "2".

• Pattern sequence: Determines the length for the melody pattern, and the interval between

the repetitions of the pattern.

Value range: "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

Default: "2".

• User changeable: Selects if the user is allowed to change destinctive ringer settings.

Value range: "Yes", "No"

Default: "Yes".

• Mode: Determines the source of ringer tone.

Value range: "HiPath ", "Local ringer"

Default: "HiPath".

Administration via WBM

OpenScape 4000: Admin > Ringer > Local ringers

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

Administration

Distinctive Ringing

OpenScape Business: Admin > Ringer > Local ringers

Internal

Extermal

Buzz

Rollover

Simple alert

Multiple alert

Special 1

Submit

Reset

Name Ringer sound Pattern melody Pattern sequence

Pattern

Local ringers

Pattern

Special 2

Pattern

Special 3

Pattern

Attention

Pattern

Unspecified

Pattern

US DSN-Precedence

Pattern

US DSN-Routine

Pattern

Emergency

Pattern

Submit

Reset

Local ringers

Name Ringer sound Pattern melody Pattern sequence

Internal

Pattern

External

Pattern

Attention

Pattern

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

137

Administration

Diagnostics

• Download old exception file

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

sages. The old exception file can be viewed here.

• Download H.323 trace file

• Download upgrade trace file

The trace log created during a software upgrade.

• Download upgrade error file

The error messages created during a software upgrade. These messages are incorporat-

ed in the syslog file (see Download syslog file also).

• Download Database file

Configuration parameters of the phone in SQLite format.

• Download HPT remote service log file

Log data from the HPT service.

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.

• FATAL: Only fatal error messages are stored.

• ERROR: Error messages are stored.

• WARNING: Warning messages are stored.

• LOG: Log messages are stored.

• TRACE: Trace messages are stored. These contain detailed information about the pro-

cesses taking place in the phone.

• DEBUG: All types of messages are stored.

Brief Descriptions of the Components/Services

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

• Administration

Deals with the changing and setting of parameters within the phone database, from both

the User and Admin menus.

• AGP Phonelet

Phonelet that manages XML applications.

• Application framework

Administration

A31003-C1000-M102-5-76A9, 09/2017

138 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Diagnostics

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.

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

• Clock Service

Handles the phone’s time and date, including daylight saving and SNTP functionality.

• Communications

Involved in the passing of call related information and signaling to and from the CSTA ser-

vice.

• Component registrar

Handles data relating to the type of phone, e.g. OpenScape Desk Phone CP200/205/400/

600 HFA.

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

nonical conversion.

• Directory service

Performs a look up for data in the phonebook, trying to match incoming and outgoing num-

bers with entries in the phonebook.

• DLS client management

Handles interactions with the DLS (Deployment Service).

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

139

Administration

Diagnostics

• H.323 messages

Used on HiPath 4000 systems as SME platforms do not use H.323 with HFA V3, this traces

the H.323 messages which are exchanged between the phone, gateway and other phones

for DMC calls.

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

• HFA service agent

This trace will enable the Stimulus FPK Programming and HFA Stimulus, Messages Menu

Phonelet and HFA Phonelet Utilities that are directly managed by PBX

• HTTP Service

Handles the HTTP Service messages.

• Instrumentation service

Used by the Husim phone tester to exchange data with the phone for remote control, test-

ing and monitoring purposes.

• 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 hand-

set 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 (Not applicable for OpenScape Desk Phone CP200/CP205)

Involved with Bluetooth accesses to the phone.

Bluetooth is available only on OpenScape Desk Phone CP600 phones.

• OpenStage client management

This trace allows you to control the data flow of the system in case a configuration item on

Local Menu,WEBM or DLS is deleted/updated/added. It resides in the middle of all ser-

vices and provides interface to all other services for data management.

• Password management service

Verifies passwords used in the phone.

Administration

A31003-C1000-M102-5-76A9, 09/2017

140 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Diagnostics

• Performance Marks

Aid for measuring the performance of the phone. For events triggered by the user, a per-

formance 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 perfor-

mance marks is an indicator for the performance of the phone.

• Phonebook

Responsible for the phonebook application.

• Physical interface service

Handles any interactions with the phone via the keypad, mode keys, fixed feature buttons,

clickwheel and slider.

• Security Log Service

Handles the Security Log messages

• Service framework

This is the environment within which other phone services operate. It is involved in the

starting and stopping of services.

• Service registry

Keeps a record of all services currently running inside the phone.

• Sidecar service

Handles interactions between the phone and any attached sidecars.

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

• Voice engine service

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.

The trace level must be set to "TRACE" or "DEBUG".

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

141

Administration

Diagnostics

Administration via WBM

Diagnostics > Fault trace configuration

AGP Phonelet

Application menu

Call View

Clock Service

Component registrar

Data Access service

Fault trace configuration

802.1 x service

DLS client management

Health service

HFA service agent

Instrumentation service

Media control service

Mobility service

Digit analysis service

Performance Marks

Physical interface service

OpenStage client management

Trace levels for components

File size (bytes)

Trace timeout (minutes)

65536

Automatic clear before start

Sidecar service

Transport service

Service framework

Voice recognition

Voice generation service

OFF

Application framework

Call log

Certificate management

Communications

CSTA service

Desktop

Administration

Help

HTTP Service

Journal service

Media procession service

OBEX service

Directory service

Phonebook

Security Log Service

Password management service

Tone generation service

USB backup service

Service registry

Web server service

Voice mail

OFF

Download trace file Download saved trace file Download upgrade trace file Download old trace file

Download syslog file

Download upgrade error file

Download old syslog file

Download HPT remote service log file

Download saved syslog file

Download dial plan file

Download Database file

Submit

Reset

H.323 messages

Administration

A31003-C1000-M102-5-76A9, 09/2017

142 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Diagnostics

3.20.3 EasyTrace Profiles

In order to simplify tracing for a specific problem, the tracing levels can be adjusted using pre-

defined settings. The EasyTrace profiles provide settings for a specific area, e. g. call connec-

tion. On pressing Submit, those pre-defined settings are sent to the phone. If desired, the set-

tings can be modified anytime using the general mask for trace configuration under

Diagnostics > Fault Trace Configuration (see Section 3.20.2, “Fault Trace Configuration”).

If desired, the tracing for all services can be disabled (see Section 3.20.3.21, “No Tracing for

All Services”).

The following sections describe the EasyTrace profiles available for the phone.

3.20.3.1 Call Connection

Diagnostics > EasyTrace Profiles > Call connection

This EasyTrace profile contains the tracing of H.323 messages. Please note that af-

ter changing the level for the tracing of H.323 messages, the phone must be reboo-

ted.

Submit

Reset

Trace levels for components

Download H.323 trace file

Download saved trace file

Call connection

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Health service

Service registry

Call View

Communications

CSTA service

Component registrar

TRACE

LOG

TRACE

H.323 messages

DEBUG

Download trace file

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

143

Administration

Diagnostics

3.20.3.2 Call Log Problems

Diagnostics > EasyTrace Profiles > Call log problems

3.20.3.3 Call recording

Diagnostics > EasyTrace Profiles > Call recording

Trace levels for components

Call log problems

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Component registrar

Health service

Application framework

Desktop

Journal service

Call Log

TRACE

LOG

TRACE

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

Trace levels for components

Call log problems

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Communications

Media recording service

Call view

DEBUG

TRACE

LOG

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

Administration

A31003-C1000-M102-5-76A9, 09/2017

144 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Diagnostics

3.20.3.4 DAS Connection

Diagnostics > EasyTrace Profiles > DAS connection

3.20.3.5 DLS Data Errors

Diagnostics > EasyTrace Profiles > DLS data errors

Trace levels for components

DAS connection

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Component registrar

Health service

DLS client management

Service framework

Certificate management

LOG

TRACE

LOG

TRACE

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

Trace levels for components

DLS data errors

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Component registrar

Health service

DLS client management

Service framework

Certificate management

LOG

TRACE

LOG

TRACE

OpenStage client management

LOG

Data Access service

TRACE

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

administration.fm

A31003-C1000-M102-5-76A9, 09/2017

OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

145

Administration

Diagnostics

3.20.3.6 HFA registration and security

Diagnostics > EasyTrace Profiles > HFA registration and security

3.20.3.7 Help Application problems

Diagnostics > EasyTrace Profiles > Help application problems

Trace levels for components

HFA registration and security problems

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Communications

H.323 messages

TRACE

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

Submit

Reset

Trace levels for components

Download trace file Download saved trace file

Help application problems

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Component registrar

Health service

Application framework

Web server service

Application menu

LOG

TRACE

LOG

TRACE

Help

DEBUG

Download H.323 trace file

Administration

A31003-C1000-M102-5-76A9, 09/2017

146 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

administration.fm

Diagnostics

3.20.3.8 Key Input problems

Diagnostics > EasyTrace Profiles > Key input problems

3.20.3.9 LAN Connectivity problems

Diagnostics > EasyTrace Profiles > LAN connectivity problems

Trace levels for components

Key input problems

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Health service

Physical interface service

Component registrar

TRACE

LOG

DEBUG

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

Trace levels for components

LAN connectivity problems

File size (Max 6290000 bytes)

Trace timeout (minutes)

1048576

Automatic clear before start

Health service

Transport service

Component registrar

TRACE

LOG

TRACE

Submit

Reset

Download saved trace file

Download trace file

Download H.323 trace file

HTTP service

TRACE

Examples and HowTos

A31003-C1000-M102-5-76A9, 09/2017

170 OpenScape Desk Phone CP200/CP205/CP400/CP600 HFA, Administration Manual

beispiele.fm

Canonical Dialing

Example 3: External number, same local national code as the local phone

User entry 011511234567

External numbers Local public form

External access

code

Not required

International gate-

way code

Use national code

Number stored in the

phone book

+4411511234567

Dial string sent when

dialing from the

phone book

External numbers = Local public form 234567

External numbers = National public form 011511234567

External numbers = International form 004411511234567

Unify OpenScape Desk Phone CP600 Handleiding

Hulp nodig? Stel uw vraag in het forum

Misbruik melden

Product:

Spelregels forum

Abonneren

Ontvang uw handleiding per email

Stel vragen via chat aan uw handleiding

Andere handleiding(en) van Unify OpenScape Desk Phone CP600

Uw handleiding is per email verstuurd. Controleer uw email

Er is een email naar u verstuurd om uw inschrijving definitief te maken.

U heeft geen emailadres opgegeven

Uw vraag is op deze pagina toegevoegd

Info