Operation Manual

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.