Standardizing Information and Communication Systems

(1)

S t a n d a r d i z i n g I n f o r m a t i o n a n d C o m m u n i c a t i o n S y s t e m s

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL:http://www.ecma.ch - Internet: [email protected]

Scenarios for Computer Supported

Telecommunications Applications

(CSTA) Phase III

(2)

(3)

ECMA Technical Report TR/82

December 2000

S t a n d a r d i z i n g I n f o r m a t i o n a n d C o m m u n i c a t i o n S y s t e m s

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL:http://www.ecma.ch - Internet: [email protected]

Scenarios for Computer Supported

Telecommunications Applications

(CSTA) Phase III

(4)

(5)

Brief History

This Technical Report provides example call scenarios based upon Phase III of Services for Computer Supported

Telecommunications Applications (CSTA). This Technial Report is part of a Suite of Standards and Technical

Reports for Phase III of CSTA. All of the Standards and Technical Reports in the Suite are based on practical

experience of ECMA member companies and each one represents a pragmatic and widely-based consensus.

The evolution of this Suite began with CSTA Phase I, which included only the CSTA Services and Protocol

Standards (ECMA-179 and ECMA-180). In Phase II, Technical Report ECMA TR/68 was added illustrating how

CSTA services and events may be used in typical call scenarios.

Phase III of CSTA extends the previous Phase II Standards (ECMA-217 and ECMA-218) in major theme directions

as well as numerous details. This incorporates technology based upon the versit CTI Encyclopedia (Version 1.0),

which was contributed to ECMA by versit. Major areas of advancement include:

• New categories of services and events such as capabilities exchange, charging, media attach services, call data

recording (CDR), etc.

• Additional services and events for call and device control.

• Enhancement to existing services and events.

• Organization of services and events to reflect a grouping based on function (call control, device control, etc.).

• Use of a consistent template for services and events that includes initial/final connection state, connection state

transitions, event monitoring sequences, etc.

(6)

(7)

List of Corrected Errata for TR

/

82

01 April 2008

(8)

(9)

Table of Contents

1 Scope

1

2 References

1

3 Definitions and Abbreviations

1

4 Call Origination Scenarios

3

4.1

Make Call service - calling device is prompted to go off-hook

3

4.2

Make Call service - calling device is in hands free mode

5

4.3

Make Call service - calling device is already off-hook

6

4.4

Manually dialled call

7

4.5

Manually dialled call showing individual digits dialled

8

4.6

Dialling using Dial Digits service

10

4.7

Multi-stage dialling

11

4.8

Make Call service - called device is busy

13

4.9

Make Call service - call attempted to a busy calling device (negative acknowledgement)

15

4.10

Make Call service - called number is an invalid number (negative acknowledgement)

16

4.11

Manually dialled call - dialled number is invalid

17

5 Answering Call Scenarios

19

5.1

Answer Call service

19

5.2

Manually answering a call

20

6 Call and Connection Termination Scenarios

21

6.1

Device disconnects from a call by going on-hook (remaining device is cleared from the call)

21

6.2

Device disconnects from a call by going on-hook (remaining device goes blocked)

22

6.3

Device disconnects from a call using the Clear Connection service (remaining device is cleared) 23

6.4

Device disconnects from a call using the Clear Connection service (remaining device goes blocked) 24

6.5

Device disconnects from a conference call using the Clear Connection service

25

6.6

Clearing a two-party call using the Clear Call service

26

6.7

Clearing a conference call using the Clear Call service

27

6.8

Call is cleared after an alerting time-out

28

7 External Outgoing Call Scenarios

29

7.1

Make Call service - called device is outside the CSTA sub-domain

29

7.2

Manually dialled call to a device outside the CSTA sub-domain

31

7.3

Make Call service - busy called device is outside the CSTA sub-domain

33

8 External Incoming Call Scenarios

35

(10)

8.2

External incoming call (with network information)

36

8.3

External incoming call to a busy device (with network information)

37

9 Forwarding Call Scenarios

39

9.1

Call forward - no answer

39

9.2

Call forward - immediate

40

9.3

Call forward - immediate (with Diverted events)

41

9.4

Call forward - busy

42

9.5

Call forward - busy (with Diverted events)

43

10 Call Movement Scenarios

45

10.1

Deflect Call service

45

10.2

Directed Pickup Call service

46

10.3

Group Pickup Call service

47

10.4

Manual group pick up

48

10.5

Park Call service

50

11 Holding/Retrieving Call Scenarios

51

11.1

Hold Call service

51

11.2

Retrieve Call service

52

12 Consultation Call Scenarios

53

12.1

Consultation Call service

53

12.2

Manual consultation call

55

12.3

Consultation Call service (negative acknowledgement)

56

12.4

Consultation Call service - consulted party is busy

57

12.5

Consulted party disconnects using the Clear Connection service

59

12.6

Held party disconnects using the Clear Connection service

60

12.7

Reconnect Call service

61

12.8

Alternate Call service

63

12.9

Manual alternate call

64

13 Transfer Call Scenarios

65

13.1

Transfer Call service - screened transfer (with fixed view in Transferred event)

65

13.2

Transfer Call service - screened transfer (with local view in Transferred event)

66

13.3

Transfer Call Call service - blind transfer (with local view in Transferred event)

67

13.4

Single Step Transfer Call service

68

14 Conference Call Scenarios

71

14.1

Conference Call service

71

(11)

15 Call Completion Scenarios

73

15.1

Call Back Call-Related service - called device is busy

73

15.2

Camp On Call service

75

16 Distributing Call Scenarios

77

(12)

(13)

1

Scope

This Technical Report illustrates call scenarios for Services for Computer Supported Telecommunications

Applications (CSTA) Phase III (ECMA-269).

The scenarios are only for information and as such ECMA-269 (Services) and ECMA-285 (Protocol) Standards may

define additional options or parameters. The purpose of this Technical Report is to provide examples of some CSTA

Service invocations and illustrate associated call event reports. It is not an exhaustive document and some

implementations may not perform as illustrated within this document, while still conforming to the Standard.

Each scenario includes a textual description and an illustration. Illustrations use the same key as described within

ECMA-269. For each scenario, message sequences are listed for all device type monitored devices - call type

monitors have not been illustrated. All devices have device type monitors set with no events masked. The columns

in each scenario represent the following:

• The Activity column includes a brief description of the telephony activity. The activity can either be initiated by

a service invocation or manually.

• The Monitored Device(s) columns list events generated for the specified device-type monitor or a service

request and service response.

• The Comments column describes additional information on the activity.

All mandatory parameters is CSTA messages are provided. In addition, all conditional parameters that are required

in the context of the scenario are provided. Optional parameters are generally not included unless they are useful in

the context of illustrating a specific scenario. The mandatory, conditional, and optional classification of parameters

in CSTA messages are specified in ECMA-269.

The monitorCrossRefID parameter in events is not shown.

DeviceIDs are illustrated by Dn and ConnectionIDs in the form DnCn. All Device IDs are within the same

switching sub-domain unless otherwise indicated or stated. Any exception comments are made in the final column

Comments.

2

References

ECMA-269

Services for Computer Supported Telecommunications Applications (CSTA) Phase

III, 4th edition (June 2000)

ECMA-285

Protocol for Computer Supported Telecommunications Applications (CSTA) Phase

III, 2nd edition (June 2000)

ECMA TR/72

Glossary of definitions and terminology for Computer Supported

Telecommunications Applications (CSTA) Phase III, 3rd edition (June 2000)

3

Definitions and Abbreviations

(14)

(15)

4

C

all Origination S

cenarios

This

clause

includes

examples of

how ca

lls can be

in

it

iated

, eith

er by usin

g the Make Call serv

ice or by

m

anual

o

perat

ion.

The first flow il

lustrates how a call is origin

ated usin

g the Make

Call

serv

ice.

In thi

s flow th

e

cal

ling

d

evice is pro

m

pt

ed to

go

o

ff-ho

ok, and then

t

he

cal

l is estab

lished

b

et

w

een

tw

o d

evices.

A

ddi

tion

al cal

l o

ri

ginat

ion

flows

are

pro

vided

t

hat

illu

strat

e ho

w t

o o

ri

ginat

e a

cal

l

using

th

e Make

Call

serv

ice wi

th

hand

s

free dialling, manual

di

all

ing, mu

lti

-stage di

allin

g,

an

d scen

ario

s th

at sh

ow calls that

fail, etc.

4.1

Make Call service -

calling device

is pr

ompted to go off-hook

This

scenario illus

trates a success

ful

Make

Call from device

D1 to

device D2. In this

scenario both devices are available and v

alid, device D1

is

permitted

to make the

call

and the call

is answered

by device

D2.

In t

his scenario

the

Make Call

serv

ice specifies t

hat d

evice D

1

sho

uld

be p

rom

pt

ed to

go

off-hook

(v

ia t

he aut

oOrigi

nate p

aram

eter) before D2

devi

ce is

called.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

A M ake Call

service to a valid device is invo

ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDirector yNu m ber • autoOrigi nate D1 D2 Prom pt T he Make Call service sp ecif ies that device D1 s hou ld be pr om pted to go o ff -h oo k. Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Indi cation that the service ha s be en init iated

from this device

. ServiceI nit iatedEvent • initi atedC onne ction • initi atedDevice • loc alConnectionSta te • cause D1C1 D1 Initiated mak eC all T he generation of thi s eve nt is switch specif ic. T he MakeCall caus e indica tes

that the device

D1 is being pr om pted (v ia ri ng ing, fo r examp le) to go o ff -h ook .

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

(16)

Device D1 goes of f ho ok a nd is

connected in the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all Device D2 begin s to ri ng and D1 receives rin gi ng to ne . Delivere dE vent • connection • alert ingDevice • callingD evi ce

• calledDevice • lastRedirectionDevice • loc

alConnectionSta te • cause D2C1 D2 D1 D2 NR Conn ected new C all

DeliveredEvent • connection • alertingDevice • callingDe

vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • e ventCause D2 C1 D2 D1 D2 NR Alerting newCall Device D2 ans w ers the ca ll by manually go in g of f-h oo k. Es tab lis he dE ven t • establishedConnection • ans w eringD evic e • callingD evi ce

alConnectionSta te • cause D2C1 D2 D1 D2 NR Conn ected new C all E stablish edE vent • es tab lishedCo nnection • an sw er in gD ev ic e • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e D2 C1 D2 D1 D2 NR Conn ected newCall

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

(17)

4.2

Make Call service -

calling device is in h

ands fr

ee mode

This

scenario illustrates

the cas

e when

the

calling devic

e

is requested to automa

tically connect

to the call (“hands free”

mode).

This

scenario dif

fers

from the firs

t scenari

o in th

e

foll

owin

g ways:

•

The Mak

e Cal

l servi

ce

request (via th

e

au

toOrig

inate paramet

er)

speci

fies th

at the call

ing d

ev

ice shoul

d be auto

mat

ically

co

nne

cted to the

call

(“hands

free”) mode.

•

The NewCall cause on the Service

Initia

ted even

t indi

cates

th

at the dev

ice is

no

t bein

g pro

m

pt

ed to go

o

ff-ho

ok.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

A M akeCall service to a va lid device is in vo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDirector yNu m ber • autoOrigi nate D1 D2 Do No tP ro mpt T he autoOr iginate pa rameter specifie s tha t the call ing device should be automatic ally connect ed to the call (not pr om pted) . Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Indi cation that the service ha s be en init iated

from this device

. ServiceI nit iatedEvent • initi atedC onne ction • initi atedDevice • loc alConnectionSta te • cause D1C1 D1 Initiated NewCall T he generation of thi s eve nt is switch specif ic. T he Service Initiated event with the Ne wCall ca use indicate s tha t there is no prompting at the device. Device D1 is automatica lly

connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all

Since the aut

oOr iginate parameter indicates “D oN ot -Pr ompt ”, devi ce D1 is connected to the ca ll without manual inter -ventio n (h ands f ree mod e). ... scen ar io p roce eds as sh ow n in 4. 1.

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

(18)

4.3

Make Call service -

calling device is alr

eady off-hook

Thi

s scenario

ill

ustrates th

e i

nvok

ing

o

f

a call

th

at

alread

y

was

in

iti

ated by a

us

er goin

g off-h

ook on

a telep

hone. Th

e

cal

l i

s in

vok

ed fro

m

devi

ce D1

to

device D2.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

Device D1 manually initiates a

call by goin g of f-hook . ServiceI nit iatedEvent • initi atedC onne ction • initi atedDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all MakeCall service is invo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDevice D1 D2 Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Call proceeds from device D1. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all ... scen ar io p roce eds as sh ow n in 4. 1.

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

C1

i

(19)

4.4

Manu

ally dialled call

This scenario

illustrates a

call orig

inated through manual device

activity

.

The scenario dif

fers

from the firs

t scenari

o in the fo

llo

win

g

w

ays:

•

The Make Call

service is not in

cluded

.

•

The cause on the

Service

Initiate

d

event does indicate prompting.

N

ote

that

in

thi

s

scen

ario

th

e im

plem

ent

ation

bu

ffers th

e di

alled

dig

its u

nti

l t

he com

pl

ete di

alli

ng

seq

uence h

as been

dial

led

and provides the complete

dialled

digits

in the Originated ev

ent

(i.e., no Di

gits Di

al

led event

(s)

are provided

in

this

scenario).

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

User at D evic e D1 goes of f-hook an d re ce iv es d ial tone. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all

Device D1 completes dialling device D2 and

is

connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all ... scen ar io p roce eds as sh ow n in 4. 1.

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

(20)

4.5

Manu

ally dialled call showing

individual digits

dial

led

This

scenario differs from the

il

lustrates how

an individual Digi

ts

Dialled

event is generated fo

r each

dig

it di

alled. After al

l

digits are dialled the

Orig

inated event

provides the

complete

dialled

sequence.

N

ote that

i

t is

im

pl

emen

tatio

n sp

ecifi

c

ho

w ma

ny

digits are buffered before

they are sent in a Digits

Dialled event,

or

if the

digits are buffered until the

co

mp

lete seq

uence of

di

git

s

is

di

alled (i.e.,

no

Digi

ts Dialled events prior

to

an Originated event).

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

User at D evic e D1 goes of f-hook an d re ce iv es d ial tone. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all Digit “2” is dialled. DigitsDialledE vent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 “2” Initiated norm al Digit “ 2” is dialled. Digit “3” is dialled. DigitsDialledE vent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 “3” Initiated norm al Digit “ 3” is dialled. Digit “4” is dialled. DigitsDialledE vent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 “4” Initiated norm al Digit “ 4” is dialled. Digit “3” is dialled. DigitsDialledE vent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 “3” Initiated norm al Digit “ 3” is dialled.

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

(21)

Device D1 ha

s

completed dialling a

nd is

connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all All of the digits for D 2 (“2343”) have been dial led. T he Or iginate d event cont ains the complete dialling s equence. ... scen ar io p roce eds as sh ow n in 4. 1.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

(22)

4.6

Di

alling using Dial

Di

gits service

This scenario

illustrates the

use of

the

Dial Digits service

for

a call that

has al

read

y been est

abli

sh

ed by the user

m

anual

ly

goi

ng off-hoo

k.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

Device D1 manually initiates a

call by goin g of f-hook . ServiceI nit iatedEvent • initi atedC onne ction • initi atedDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all The Dial D igits service with the

complete dialling sequence is prov

id ed . DialDigitsServic e • dia llingConnection • dia llingSeque nce e D1C1 D2 Ackn owl -edgement. DialDigitsResult The e vent indica tes that the re quested di gits w ere di alled. DialDigitsEvent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 D2 Initiated norm al T he dialling

sequence is complete and device

D1

is

connected in the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all ... scen ar io p roce eds as sh ow n in 4. 1.

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

C1

(23)

4.7

Multi-stage dialling

This

the use

of the Di

al Digits service

to

complete dialling

a

call that

w

as establ

ished vi

a

a Make Call s

ervice.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

A M akeCall

service to a valid device is invo

ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDirector yNu m ber • autoOrigi nate D1 “2;” Prom pt T he Ma

ke Call service specifie

s a

partia

l dialling string that

begins with a (“2”) and the pa rtial dialling indicator (“;”). Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Indi cation that the service ha s be en init iated

from this device

. ServiceI nit iatedEvent • initi atedC onne ction • initi atedDevice • loc alConnectionSta te • cause D1C1 D1 Initiated mak eC all T he generation of thi s eve nt is switch specif ic. T he MakeCall caus e indica tes

that the device

D1 is being pr om pted (v ia ri ng ing, fo r examp le) to go o ff -h ook . The e vent indica tes that a pa rtial dial ling sequence was rece iv ed . DialDigitsEvent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 “2;” Initiated norm al A “;” char acter indica tes that there is an incomplete dia lling str ing. The Dial D igits service with the re mainder of

the dialling sequence is prov

id ed . DialDigitsServic e • dia llingConnection • dia llingSeque nce e D1C1 “3456 ” A “;” is

not provided in the

dialling s tring s ince the re ar e no more digits to be dialled. Ackn owl -edgement. DialDigitsResult

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D2

(called)

D2

C1

(24)

The e vent indica tes that the re quested di gits w ere di alled. DialDigitsEvent • dia llingConnection • dia llingDevice • dia llingSeque nce • loc alConnectionSta te • cause D1C1 D1 “3456 ” Initiated norm al A complete dialli ng seque nce has been re ceived (no “;” ch ar acter ). T he dialling

sequence is complete and device

D1

is

connected in the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all D2 is the call ed de vice . I t contains the digits “23456” in this scenario. ... scen ar io p roce eds as sh ow n in 4. 1.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

(25)

4.8

Make Call service -

called device is busy

This

a Make

Call from device

D1

to

device

D2, where

device D2 is

bus

y and

is

no

t set to

forw

ard busy

call

s.

The call fails

because the

cal

led party is busy.

This

scenario differs

from the firs

t scenari

o in th

e

foll

owin

g ways:

•

The Failed

even

t is

ge

nerat

ed to ind

icate th

at

the ca

ll has

encountered

a busy device.

N

ote that in

th

is

exam

pl

e the Make Call servi

ce is

su

ccessful

(po

si

tiv

e ackno

wled

gemen

t) and

th

e

events indicate

that device D2

is

busy. Anot

her possib

le

scenario is where

the Make Call service

is

negatively acknowledged

with

an

error code ind

icatin

g that

d

ev

ice D2 is in an inv

ali

d state.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

MakeCall service is invo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDirector yNu m ber • autoOrigi nate D1 D2 Prom pt Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Device D1 notified of initi -ating call. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated Mak eCall T he generation of thi s eve nt is switch specif ic. The c all is be ing

attempted from device

D1 . OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all

be

for

e

sce

nar

io

D1

(calling)

D2

(called)

af

te

r F

ai

led

ev

en

t

D1

(c alling)

C1

f

c

[b

us

y]

D2

(c alled)

[b

usy]

(26)

Device D2 is busy

- the call

cannot be completed. Device D1 hear

s bus y tone. FailedE vent • faile dConnection • failingDevice • callingD evi ce

alConnectionSta te • cause D2C1 D2 D1 D2 NR Conn ected busy FailedE vent • failedConnection • failingD evi ce • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e D2 C1 D2 D1 D2 NR Failed bus y T his illustra tes connection fa

ilures that report

the Faile

d

event for

all devices involved

with the c

all and tha

t will

provide

a

complete c

onnectionID for the

fa iled connection. Se e ECM A -26 9, claus e 2. 8. 2, item 2. Device D1 replace s ha nd se t. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Failed normalClearing

Failed connection D2C1 also clear

s. C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D2 C1 D2 Nu ll normalClearing

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

(27)

4.9

Make Call service -

call attempted to a busy

call

ing dev

ice (neg

ativ

e

ackno

wled

gement)

Thi

s scenario

il

lustrates a

Make

Call

fro

m

devi

ce D1

to

devi

ce D3, where device D1 is busy. Th

e ca

ll fails

be

cause

the

calling

device is busy.

This

scenario differs

from the firs

t scenari

o in th

e

foll

owin

g ways:

•

The (negative) response to the Make Call

se

rvice reques

t indicates

that the call

attemp

t has

failed. No subsequent events

are

ge

nerated.

The

Make

Call

request

is

negat

ivel

y ack

now

ledged

b

ecau

se th

e cal

lin

g p

arty

, dev

ice D

1, i

s

bu

sy

w

hen

a M

ake C

all

requ

est

is i

ssu

ed.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Mon

it

ore

d Devi

ce

D3

Comments

A M akeCall service is invo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDevice D1 D3 Negative Ackn owl -edgement. MakeCallE rror • stateIncompatibility invalid cal ling device state M ake Call servic e fa ils be caus e callin g par ty is bu sy .

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D1

(calling)

D3

(called)

D2

C1

c

D2

D3

(called)

[busy]

[busy

]

(28)

4.1

0

Make Call service -

called number

is

an

invalid n

u

mber (negative ack

n

owledgemen

t)

This scenario

illustrates

a M

ake Call

from

device D1 to device

D2. In

this

scenario

de

vice D1 is availab

le,

val

id and permit

ted

to

make the call. Device

D

2 (il

lustrated

by

a b

ox

wit

h a

do

tted

li

ne aroun

d i

t) is

actual

ly

an i

nval

id

num

ber (e.g

., t

he n

um

ber

is

co

rrectly

form

atted

b

ut it is

no

t part

of

the dial

lin

g

plan)

and the call fails.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

MakeCall service is invo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDevice D1 D2 Negative Ackn owl -edgement. Mak eCall E rr or • operationalE rror Invali dCalled -Device

b

e

fo

re

se

rv

ice

a

ft

er

se

rvi

ce

D1

(calling)

D2

(called)

D2

(29)

4.1

1

Manu

ally dialled call -

dial

led

number is i

n

valid

This scenario illus

trates

a manually dialled

call

from

device D1 to device D2.

In this

scenario device D1 is

available, valid

and perm

it

ted to make the call.

D

evice D2 (ill

ustrated by

a bo

x wit

h a dott

ed lin

e arou

nd it

) is

actual

ly an in

valid

num

ber

(e.g

., the number is correctly form

at

ted bu

t it i

s no

t part of

th

e

dialling plan) and

the

call fails

.

N

ote that in thi

s scen

ario

th

e

dial

led dig

its

are

bu

ffered

in

t

he swi

tchi

ng funct

ion

un

til

the

comp

lete

dial

ling

sequen

ce has b

een

di

alled and is

provi

din

g

th

e comp

lete di

al

led di

gits in

th

e

O

rig

inat

ed ev

ent (i

.e.,

no Digits

Dialled e

vent(s) ar

e provid

ed in thi

s

scenario).

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

Device D1 goes of f-ho ok a nd re ce iv es d ial tone. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all

Device D1 completes dialling device D2 and

is

connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all Device D2 is a n

invalid number the call

cannot be completed. Device D1 rece iv es re or der ton e. FailedE vent • faile dConnection • failingDevice • callingD evi ce

alConnectionSta te • cause D1C1 D1 D1 D2 NR Failed reor der T on e Device D1 goes on -hoo k. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing

be

for

e

sce

nar

io

a

ft

er

Failed ev

ent

D1

(calling)

D2

(called)

D2

C1

f

(30)

(31)

5

Answer

ing Call Sc

enario

s

This

clause

illustrates how calls

are

an

swered,

manually and

by CSTA services.

5.1

A

ns

w

er Call service

This

the s

ucces

sful use of the

An

swer Call

service invoked

on behalf of

device

D2.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

Answer C all service is invo ke d on be half of d ev ice D2. Answe rCallReque st • callT oBeAnswer ed D2 C1 An error w ill be returned if the

device is not able to a

nswer

the

call

without manual intervention.

Ackn owl -edgement. Answe rCallResult Device D2 ha s be en ans w ered. Es tab lis he dE ven t • establishedConnection • ans w eringD evic e • callingD evi ce

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D1

c

D2

C1

D1

a,

q

c

D2

(32)

5.2

Manu

ally

an

sweri

n

g a

call

Thi

s

scenario il

lustrates

th

e event sequen

ce

wh

en alert

ing

d

ev

ice D2 goes off-hook

to

answer th

e

call

.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

Device D2 ans w ers the ca ll by goin g of f-hook . Es tab lis he dE ven t • establishedConnection • ans w eringD evic e • callingD evi ce

b

e

fo

re

se

rv

ice

a

ft

er

se

rvi

ce

C1

D1

c

D2

C1

D1

a,

q

c

D2

(33)

6

Call and Connection T

ermination Scenarios

This

clause

illustrates how cal

ls

and

connections are ended.

6.1

D

evic

e dis

co

nnec

ts fr

om

a ca

ll

by

go

ing

on-hoo

k (r

ema

ining

de

vic

e is clea

re

d fr

om

the c

all)

The user

at device D1,

while

connected

to

device D2, replaces

the

handset.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

D1 goes on-hook . ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • c au se D1 C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • cause D1 C1 D1 Conn ected normalClearing Since D2 is the on ly device in the call, it i s clear ed as the result of D1 be in g clear ed. C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • cause D2 C1 D2 Nu ll normalClearing

be

for

e

sce

nar

io

aft

er sc

ena

rio

D1

C1

c

D2

c

D2

D1

(34)

6.2

D

evic

e dis

co

nnec

ts fr

om

a ca

ll

by

go

ing

on-hoo

k (r

ema

ining

de

vic

e go

es bloc

ke

d)

In thi

s scenario devi

ce

D

1

is

m

anual

ly put

o

n-h

ook

to

release itself

fro

m

the call

. The rem

aini

ng devi

ce

go

es

bl

ocked

, unt

il th

e

de

vi

ce goes on-hoo

k.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

Device D1 goes on -hoo k. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Conn ected normalClearing As a result of the “f ar e nd di sc on ne ct”, the re maining

connection D2C1 goes block

ed . FailedE vent • failedConnection • failingD evi ce • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e D2 C1 D2 D1 D2 NR Failed block ed While D2C1 is

blocked, the user

at the device may be hear

ing er

ro

r

tone

.

The remaining device

g oes on -hook . C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D2 C1 D2 Nu ll normalClearing

be

for

e

sce

nar

io

aft

er sc

ena

rio

D1

C1

c

D2

c

D2

D1

(clear ing )

(35)

6.3

De

vi

ce

di

sc

on

ne

cts

fr

om

a

c

all

us

ing

the

Cl

ea

r

C

onnection

service (r

emaining device is cle

ar

ed)

The Clear Conne

ction

service is

used

to di

sconnect

device D1 from

the call.

In this

example,

the remaining device

in the call,

D2,

is

cleared after D1 has

been rem

oved from

the call.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

A Clea r Connection service is invo ke d on D1s be half . ClearConnec tionRequest • connectionT oB eC leared D1C1 Ackn owl -edgement. ClearConnec tionResult Event indica tes that connection D1 C 1 has be en re mov ed fr om the call. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Conn ected normalClearing Since D2 is the on ly device in the call, it i s clear ed as the result of D1 be in g clear ed. C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • cause D2 C1 D2 Nu ll normalClearing

be

for

e

sce

nar

io

aft

er sc

ena

rio

D1

C1

c

D2

c

D2

D1

(36)

6.4

De

vi

ce

di

sc

on

ne

cts

fr

om

a

c

all

us

ing

the

Cl

ea

r

Co

nnection

service (r

emaining device goe

s blocked)

The

Clear Connection

se

rvice

is us

ed to di

sconnect device D1 from

the

call. In this

example, the remainin

g device in the call,

D2, is

go

es bl

ocked,

un

ti

l

it

is

cl

eared from

th

e call by m

anuall

y goi

ng on-hoo

k.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

A Clea r Connection service is invo ke d on D1s be half . ClearConnec tionRequest • connectionT oB eC leared D1C1 Ackn owl -edgement. ClearConnec tionResult Event indica tes that connection D1 C 1 has be en re mov ed fr om the call. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Conn ected normalClearing As a result of the “f ar e nd di sc on ne ct”, the re maining

connection D2C1 goes block

ed . FailedE vent • failedConnection • failingD evi ce • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e D2 C1 D2 D1 D2 NR Failed block ed While bloc

ked, the user

at the device may be hear ing er ror tone .

The remaining device

g oes on -hook . C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D2 C1 D2 Nu ll normalClearing

be

for

e

sce

nar

io

aft

er sc

ena

rio

D1

C1

c

D2

c

D2

D1

(clear ing )

(37)

6.5

D

evic

e dis

connec

ts fr

om a confer

ence

c

all using the Clear Conne

ction ser

vice

This

service releases

a specific device

from

a

call. In the cas

e of a

Conference Call

thi

s

resu

lts in th

e

speci

fic party bei

ng

removed

from this

conference.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Mon

it

ore

d Devi

ce

D3

Comments

A Clea r Connection service is invo ke d. ClearConnec tionRequest • connectionT oB eC leared D1C1 Ackn owl -edgement. ClearConnec tionResult Event indica tes that connection D1 C 1 has be en re mov ed fr om the call. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Conn ected normalClearing Connecti onCleare dE vent • dr opp edCo nnection • r eleasingD evic e • localConnect ionState • cau se D1C1 D1 Connecte d nor m al Clearing

Devices D2 and D3 remain connect

ed in the call.

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D3

c

C1

c

D2

c

D2

c

D3

D1

(clear ing )

(38)

6.6

C

le

ar

ing a two-party call using the Cle

ar Call service

Thi

s scenario

il

lustrates t

he

use o

f

th

e Clear

Call s

ervic

e. This s

ervice rel

eas

es all devices

from an existing call.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

A Clea r Call service is invo ke d. ClearCal lR equest • callT oClear D1C1 Ackn owl -edgement. ClearCal lR es ult The e vents indica te that D1 ha s dis co n-ne

cted from the

call. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Conn ected normalClearing The e vents indica te that D2 ha s dis co n-ne

cted from the

call. C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D2 C1 D2 Nu ll normalClearing

be

for

e

sce

nar

io

aft

er sc

ena

rio

D1

C1

c

D2

c

D2

D1

(39)

6.7

C

le

ar

ing a confer

ence

c

all

using the Clear Call

service

This

the use

of the Cl

ear

Call s

ervic

e. This s

ervice releas

es

all devices

from an existing conference

call

.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Mon

it

ore

d Devi

ce

D3

Comments

A Clea r Call service is invo ke d. ClearCal lR equest • callT oClear D1C1 Ackn owl -edgement. ClearCal lR es ult D1s conn ectio n to the call is clear ed. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D1 C1 D1 Conn ected normalClearing Connecti onCleare dE vent • dr opp edCo nnection • r eleasingD evic e • localConnect ionState • cau se D1C1 D1 Connecte d nor m al Clearing D1C1s Connection Cleare d event is r epo rt ed fo r a ll d evic e-ty pe monitors in the c all. D2s conn ectio n to the call is clear ed. C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D2 C1 D2 Nu ll normalClearing Connecti onCleare dE vent • dr opp edCo nnection • r eleasingD evic e • localConnect ionState • cau se D2C1 D2 Connecte d nor m al Clearing D2C1s Connection Cleare d event is r epo rt ed fo r a ll d evic es re mai ning in the call.

The remaining connection is clear

ed. Connecti onCleare dE vent • dr opp edCo nnection • r eleasingD evic e • localConnect ionState • cau se D3C1 D3 Null nor m al Clearing

be

for

e

sce

nar

io

aft

er sc

ena

rio

C1

D3

C1

c

D2

c

D2

c

D3

D1

(40)

6.8

Call is clear

ed after

an alerting time-out

In this

scenario,

the call is cleared

as

the result of an alerting

timer expiry.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

D2

Comments

D2C1 is cl eared as the result of an aler t timer expir y. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D2C1 D2 Conn ected callNotAn -sw ered C onnec tionClear edE vent • dr opp ed Con nection • r eleasingDevice • l oca lC onne ctionState • c aus e D2 C1 D2 Nu ll ca llNotAn -swe red T he c ause of “callN otA nswer ed” indic

ates that the call

was clea red as the result of a timer e xpiry.

Connection D1C1 clears as a result

of D1 clear ing. ConnectionClea redEvent • d ro pped C onn ectio n • relea si ngDevice • loc alConnectionSta te • cause D1C1 D1 Nul l normalClear ing

be

for

e

sce

nar

io

aft

er sc

ena

rio

D1

C1

c

D2

a

D2

D1

(41)

7

Ext

ernal Outgo

ing Call Sc

enarios

This section

includes

examples of

success

ful external ou

tgoing calls,

initiated manually

an

d by CSTA

services.

7.1

Make Call se

rvic

e -

ca

lled device is outside the CST

A

sub-domain

Thi

s

scenario il

lustrates

a Make Call

service requ

est

o

n behalf

of dev

ice

D

1 to the dev

ice

D

2 whi

ch

is

o

utsid

e th

e

CSTA sub-dom

ain.

Since device D2 is located

outs

ide this C

S

TA

su

b-d

om

ain,

it

can not

be directly mo

nit

ored

th

rou

gh this CSTA int

erface and there

fore n

o even

ts wi

ll

be

seen for that device.

Howeve

r,

device N2, which is

a networ

k interface

device (NID) (e.g.,

tru

nk interface), acts as

a proxy fo

r

devi

ce D

2, an

d

depen

din

g

upon

th

e

type of

sig

nall

ing avai

lable vi

a

th

e ex

ternal netw

ork

, som

e

sig

nalli

ng in

format

ion

can be m

ade

av

ailab

le

th

rough

th

e c

onnect

ion

of the NID.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

N2

Comments

A M ake Call

service to a valid dev

ice

outside the CSTA su

b-domain is invo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDevice • autoOrigi nate D1 D2 doNo tPro m pt T he s ervice re quest s pecif ies “hands f ree ” mode ( S ee 4. 2) . Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Indi cation that service h as be en init iated

from this device

. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all T he generation of thi s eve nt is switch specif ic. D1 is connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all

be

for

e

sce

nar

io

af

te

r sce

nar

io

C1

D1

c

D1

(calling)

D2

(called)

N2

D2

(called)

N2

(42)

The c all lea ves the CSTA sub-do m ain . NetworkReachedEvent • ou tb ou nd C onn ectio n • ne twor kI nte rfa ceUs ed • callingD evi ce

alConnectionSta te • cause N2C1 N2 D1 D2 NR Conn ected new C all NetworkReachedEvent • outb oun dCo nnection • n etw or kI nter fac eUs ed • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e N2 C1 N2 D1 D2 NR Conn ected newCall Device D2 is aler ted. Delivere dE vent • alert ingConnection • alert ingDevice • callingD evi ce

alConnectionSta te • cause • assoc. CalledDevice N2C1 D2 D1 D2 NR Conn ected netw or kSig na l N2 DeliveredEvent • aler tingC onn ectio n • a lertingDevice • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e • a ssoc.Ca lledD evic e N2 C1 D2 D1 D2 NR Conn ected networ kSignal N2 Recei ving thi s eve nt depends on the type of networ k interf ace. Th e caus e of Networ kSig nal indic ates that the eve nt is due to acti vity at the devic e located outside of the CSTA switching sub-domain (D2),

not the NID

(N 2) . Device D2 ans w ers the call. Es tab lis he dE ven t • establishedConnection • ans w eringD evic e • callingD evi ce

alConnectionSta te • cause • assoc. CalledDevice N2C1 D2 D1 D2 NR Conn ected netw or kSig na l N2 E stablish edE vent • es tab lishedCo nnection • an sw er in gD ev ic e • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e • a ssoc.Ca lledD evic e N2 C1 D2 D1 D2 NR Conn ected networ kSignal N2 Answer supervision is rec eive d fr om th e netw or k (th is d epe nd s

upon the type

of signa lling su pp or ted b y the ne twor k) . Th e caus e of Networ kSig nal indic ates that the eve nt is due to acti vity at the devic e located outside of the CSTA switching sub-domain (D2),

not the NID

(N 2) .

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

N2

Comments

(43)

7.2

Manu

ally dialled call to a devi

ce

ou

tsid

e the CS

T

A

sub-domain

In thi

s scenari

o

th

e device D1 is manu

ally

li

ft

ed

to

in

it

iate

a call,

and the call is

routed

ou

t o

f the CSTA

sub

-do

main

. The

us

er

dials

a trunk access code

and the NID

is

selected. Then the

us

er

co

mp

letes diall

ing

the external

number.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

N2

Comments

User at D evic e D1 goes Off -Hoo k and dials the trunk ac cess code. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all The c all lea ves the CSTA sub-do m ain . NetworkReachedEvent • ou tb ou nd C onn ectio n • ne twor kI nte rfa ceUs ed • callingD evi ce

alConnectionSta te • cause N2C1 N2 D1 NK NR Initiated new C all NetworkReachedEvent • outb oun dCo nnection • n etw or kI nter fac eUs ed • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e N2 C1 N2 D1 NK NR Conn ected newCall User at D evic e D1 complete s di alling device D2 and D1 is

connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause • assoc. CalledDevice D1C1 D1 D2 Conn ected new C all N2 Origina tedEvent • ori ginatedConnection • c allingDe vice • c alledDevice • l oca lC onne ctionState • c aus e • a ssoc.Ca lledD evic e D1 C1 D1 D2 Conn ected newCall N2 Device D2 is aler ted. Delivere dE vent • alert ingConnection • alert ingDevice • callingD evi ce

alConnectionSta te • cause • assoc. CalledDevice N2C1 D2 D1 D2 NR Conn ected netw or kSig na l N2 DeliveredEvent • aler tingC onn ectio n • a lertingDevice • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e • a ssoc.Ca lledD evic e N2 C1 D2 D1 D2 NR Conn ected networ kSignal N2 Recei ving thi s eve nt depends on the type of networ k interf ace. Th e caus e of Networ kSig nal indic ates that the eve nt is due to acti vity at the devic e located outside of the CSTA switching sub-domain (D2),

not the NID

(N 2) .

be

for

e

sce

nar

io

af

te

r sce

nar

io

C1

D1

c

D1

(calling)

D2

(called)

N2

D2

(called)

N2

(44)

Device D2 ans w ers the call. Es tab lis he dE ven t • establishedConnection • ans w eringD evic e • callingD evi ce

alConnectionSta te • cause • assoc. CalledDevice N2C1 D2 D1 D2 NR Conn ected netw or kSig na l N2 E stablish edE vent • es tab lishedCo nnection • an sw er in gD ev ic e • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e • a ssoc.Ca lledD evic e N2 C1 D2 D1 D2 NR Conn ected networ kSignal N2 Answer supervision is rec eive d fr om th e netw or k (th is d epe nd s

upon the type

of signa lling su pp or ted b y the ne twor k) . Th e caus e of Networ kSig nal indic ates that the eve nt is due to acti vity at the devic e located outside of the CSTA switching sub-domain (D2),

not the NID

(N 2) .

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

N2

Comments

(45)

7.3

Make Call se

rvic

e -

busy calle

d devi

ce is ou

tsid

e

the

CS

T

A

sub-domain

Thi

s

scenario il

lustrates

a Make Call

service requ

est

o

n behalf

of dev

ice

D

1 to a

bu

sy devi

ce

D2

o

utsid

e

th

e CSTA sub-dom

ain

.

Event information after the Netw

ork

R

each

ed event dep

ends on the ty

pe of th

e

net

w

ork int

erface.

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

N2

Comments

A M ake Call

service to a valid dev

ice

outside the CSTA su

b-domain is invo ke d on be half of d ev ice D1. M akeCallRequest • callingD evi ce • calledDevice • autoOrigi nate D1 D2 doNo tPro m pt Ackn owl -edgement. M akeCallResult • initi atedC all D1C1 Indi cation that service h as be en init iated

from this device

. ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • cause D1C1 D1 Initiated new C all D1 is connected to the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause D1C1 D1 D2 Conn ected new C all The c all lea ves the CSTA sub-do m ain . NetworkReachedEvent • ou tb ou nd C onn ectio n • ne twor kI nte rfa ceUs ed • callingD evi ce

alConnectionSta te • cause N2C1 N2 D1 D2 NR Conn ected new C all NetworkReachedEvent • outb oun dCo nnection • n etw or kI nter fac eUs ed • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e N2 C1 N2 D1 D2 NR Conn ected newCall

b

e

fo

re sc

en

a

rio

D1

(calling)

a

ft

er sc

en

a

rio

D1

(c alling)

C1

c

N2

D2

(called)

[busy

]

D2

(c a lled)

[b

usy]

(46)

Device D2 is busy

- the call

cannot be completed. Device D1 rece

iv es b us y tone. FailedE vent • faile dConnection • failingDevice • callingD evi ce

alConnectionSta te • cause • assoc. CalledDevice N2C1 D2 D1 D2 NR Conn ected netw or kSig na l N2 FailedE vent • failedConnection • failingD evi ce • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • c aus e • a ssoc.Ca lledD evic e N2 C1 D2 D1 D2 NR Conn ected networ kSignal N2 Recei ving thi s eve nt depends on the type of networ k interf ace. Th e caus e of Networ kSig nal indic ates that the eve nt is due to acti vity at the devic e located outside of the CSTA switching sub-domain (D2),

not the NID

(N 2) . A cause code of Busy m ay also be used .

Activity

Moni

tore

d Devi

ce

D1

Moni

tore

d De

vi

ce

N2

Comments

(47)

8

External Incoming Call Scenarios

This

section includes examples

of

success

ful external incoming calls.

8.1

Extern

al in

coming call

(no network

information)

This s

cenario illustrates

the

successful incoming call from device D1. B

eca

use de

vice D1 is located outs

ide t

he CSTA sub-dom

ain

, it

can no

t be m

oni

tored

and therefore

events will be

seen on

ly for the devices

N1

(NID - Network

Interface Devic

e, e.g., trunk)

and D2.

In thi

s scenario,

no

calli

ng party or

call

ed part

y inform

ati

on is

pass

ed

over the

NID. The

calle

d device is determi

ned vi

a a de

di

cat

ed tru

nk dev

ice.

Activity

Moni

tore

d Devi

ce

N1

Moni

tore

d De

vi

ce

D2

Comments

Indi cates an

external incoming call on the NID (

e.g. tr unk ). ServiceI nit iatedEvent • initi atedC onne ction • initi atingDevice • loc alConnectionSta te • eventCause • assoc. CallingDe vice N1C1 N1 Initiated new C all N1 Th e N ID has

connected in the call. OriginatedEvent • originated Connection • callingD evi ce • calledDevice • loc alConnectionSta te • cause • assoc. CallingDe vice N1C1 NK D2 Conn ected new C all N1 Device D2 is available a nd is aler ted. Delivere dE vent • alert ingConnection • alert ingDevice • callingD evi ce

alConnectionSta te • eventCause • assoc. CallingDe vice D2C1 D2 NK D2 NR Conn ected new C all N1 DeliveredEvent • aler tingC onn ectio n • a lertingDevice • c allingDe vice • c alledDevice • l astR edirectionD evic e • l oca lC onne ctionState • e ventCause • a ssoc.Ca llingDevice D2 C1 D2 NK D2 NR Alerting newCall N1 In this scena rio, th e networ k do es not provide cal

ling and calle

d device information.

be

fo

re sc

ena

rio

D1

(calling)

af

te

r sce

nar

io

C1

a

c

D2

(called)

N1

D1

D2

N1

(48)

8.2

Extern

al in

coming call

(w

ith network in

formation)

This scenario

illustrates the

su

cces

sful incoming call

from device D1.

In thi

s scenario,

th

e netw

ork

p

rov

ides the calli

ng and call

ed

pa

rt

y

in

form

atio

n over

th

e NID

.

Activity

Moni

tore

d Devi

ce

N1

Moni

<