Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager Release 7.1(2)
Message Sequence Charts
Downloads: This chapterpdf (PDF - 0.99MB) The complete bookPDF (PDF - 9.8MB) | Feedback

Message Sequence Charts

Table Of Contents

Message Sequence Charts

Abbreviations

Manual Outbound Call

Blind Transfer

Redirect Set Original Called (TxToVM)

Shared Lines-Initiating a New Call Manually

Presentation Indication

Making a Call Through Translation Pattern

Blind Transfer Through Translation Pattern

Forced Authorization and Client Matter Code Scenarios

Manual Call to a Destination that Requires an FAC

Manual Call to a Destination that Requires both FAC and CMC

lineMakeCall to a Destination that Requires an FAC

lineMakeCall to a Destination that Requires Both FAC and CMC

Timeout Waiting for FAC or Invalid FAC

Refer and Replaces Scenarios

In-Dialog Refer - Referrer in Cisco Unified Communications Manager Cluster

In-Dialog Refer Where ReferToTarget Redirects the Call in Offering State

In-Dialog Refer Where Refer Fails or Refer to Target is Busy

Out-of-Dialog Refer

Invite with Replace for Confirmed Dialog

Refer with Replace for All in Cluster

Refer with Replace for All in Cluster, Replace Dialog Belongs to Another Station

3XX

SRTP

Media Terminate by Application (Open Secure CTI Port or RP)

Media Terminate by TSP Wave Driver (open secure CTI port)

Intercom

Application Invoking Speeddial

Agent Invokes Talkback

Change the SpeedDial

Secure Conferencing

Conference with All Parties as Secure

Hold or Resume in Secure Conference

Monitoring and Recording

Monitoring a Call

Automatic Recording

Application-Controlled Recording

Conference Enhancements

Noncontroller Adding Parties to Conferences

Chaining Two Ad Hoc Conferences by Using Join

Calling Party IP Address

Basic Call

Consultation Transfer

Consultation Conference

Redirect

Click to Conference

Drop Party by Using Click-2-Conference

Drop Entire Conference by Using Click-2-Conference Feature

Calling Party Normalization

Incoming Call from PSTN to End Point

Incoming Call from National PSTN to CTI-Observed End Point

Incoming Call from International PSTN to CTI-Observed End Point

Outgoing Call from CTI-Observed End Point to PSTN Number

Outgoing Call from CTI-Observed End Point to National PSTN Number

Outgoing Call from CTI-Observed End Point to International PSTN Number

Do Not Disturb-Reject

Application Enables DND-R on a Phone

Normal Feature Priority

Feature Priority - Emergency

Join Across Lines

IPv6 Use Cases

Direct Transfer Across Lines

Swap or Cancel Support

Drop Any Party

Park Monitoring

Logical Partitioning Support

Support for Cisco IP Phone 6900 Series


Message Sequence Charts


This appendix contains message sequences or call scenarios and illustrates a subset of these scenarios that are supported by the Cisco Unified TSP. Be aware that the event order is not guaranteed in all cases and can vary depending on the scenario and the event.

This appendix contains the following sections:

Abbreviations

Manual Outbound Call

Blind Transfer

Redirect Set Original Called (TxToVM)

Shared Lines-Initiating a New Call Manually

Presentation Indication

Forced Authorization and Client Matter Code Scenarios

Refer and Replaces Scenarios

3XX

SRTP

Intercom

Secure Conferencing

Monitoring and Recording

Conference Enhancements

Calling Party IP Address

Click to Conference

Calling Party Normalization

Do Not Disturb-Reject

Join Across Lines

IPv6 Use Cases

Direct Transfer Across Lines

Swap or Cancel Support

Drop Any Party

Park Monitoring

Logical Partitioning Support

Support for Cisco IP Phone 6900 Series

Abbreviations

The following list gives abbreviations that are used in the CTI events that are shown in each scenario:

NP—Not Present

LR—LastRedirectingParty

CH—CtiCallHandle

GCH—CtiGlobalCallHandle

RIU—RemoteInUse flag

DH—DeviceHandle

Manual Outbound Call

Table A-1 describes the message sequences for Manual Outbound Call when party A is idle.

Table A-1 Message Sequences for Manual Outbound Call 

Action
CTI Messages
TAPI Messages
TAPI Structures

1. Party A goes off-hook

NewCallEven
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_APPNEWCALL
hDevice=A
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent,
CH=C1,
State=Dialtone,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALTONE
dwParam2=UNAVAIL
dwParam3=0

No change

2. Party A dials Party B

CallStateChangedEvent,
CH=C1,
State=Dialing,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

3. Party B accepts call

CallStateChangedEvent,
CH=C1,
State=Proceeding,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent,
CH=C1,
State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

No change

4. Party B answers call

CallStateChangedEvent,
CH=C1,
State=Connected,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=ACTIVE
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=B
dwRedirectionID=NP
dwRedirectionID=NP

CallStartReceptionEvent, DH=A, CH=C1

LINE_DEVSPECIFIC1
hDevice=hCall-1
dwCallBackInstance=0
dwParam1=StartReception
dwParam2=IP Address
dwParam3=Port

No change

CallStartTransmissionEvent, DH=A, CH=C1

LINE_DEVSPECIFIC2
hDevice=hCall-1
dwCallBackInstance=0
dwParam1=StartTransmission
dwParam2=IP Address
dwParam3=Port

No change

1 LINE_DEVSPECIFIC events are sent only if the application has requested them by using lineDevSpecific()

2 LINE_DEVSPECIFIC events are sent only if the application has requested them by using lineDevSpecific()


Blind Transfer

Table A-2 describes the message sequences for Blind Transfer when A calls B, B answers, and A and B are connected.

Table A-2 Message Sequences for Blind Transfer 

Action
CTI Messages
TAPI Messages
TAPI Structures

Party B does a lineBlindTranfser() to blind transfer call from party A to party C

Party A

CallPartyInfoChangedEvent,
CH=C1,
CallingChanged=False,
Calling=A,
CalledChanged=True,
Called=C,
OriginalCalled=B,
LR=B,
Cause=BlindTransfer

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTEDID, REDIRECTINGID, REDIRECTIONID

TSPI LINECALLINFO
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NULL
dwRedirectingID=NP
dwRedirectionID=NP

Party B

CallStateChangedEvent,
CH=C2,
State=Idle,
Reason=Direct,
Calling=A,
Called=B,
OriginalCalled=B,
LR=NULL

TSPI: LINE_CALLSTATE
|hDevice=hCall-1
dwCallbackInstance=0
dwParam1=IDLE
dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NULL
dwRedirectingID=NULL
dwRedirectionID=NULL

Party C

NewCallEvent,
CH=C3,
origin=Internal_Inbound,
Reason=BlindTransfer,
Calling=A,
Called=C,
OriginalCalled=B,
LR=B

TSPI: LINE_APPNEWCALL hDevice=C
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwReason=TRANSFER
dwCallerID=A
dwCalledID=C
dwConnectedID=NULL
dwRedirectingID=B
dwRedirectionID=C

Party C is offering

Party A

CallStateChangeEvent,
CH=C1,
State=Ringback,
Reason=Direct,
Calling=A,
Called=C,
OriginalCalled=B,
LR=B

TSPI: LINE_CALLSTATE, hDevice=hCall-1, dwCallbackInstance=0, dwParam1= RINGBACK dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NULL
dwRedirectingID=B
dwRedirectionID=C

Party C

CallStateChangedEvent,
CH=C3,
State=Offering,
Reason=BlindTransfer,
Calling=A,
Called=C,
OriginalCalled=B, LR=B

TSPI: LINE_CALLSTATE, hDevice=hCall-1, dwCallbackInstance=0, dwParam1= OFFERING dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwCallerID=A
dwCalledID=C
dwConnectedID=NULL
dwRedirectingID=B
dwRedirectionID=C


Redirect Set Original Called (TxToVM)

Table A-3 describes the message sequences for Redirece Set Original Called (TxToVM) feature where A calls B, B answers, and A and B are connected.

Table A-3 Message Sequences for Redirect Set Original Called (TxToVM) 

Action
CTI Messages
TAPI Messages
TAPI Structures

Party B does lineDevSpecific for REDIRECT_SET_ORIG_CALLED with DestDN = C's VMP and SetOrigCalled = C

Party A

CallPartyInfoChangedEvent, CH=C1, CallingChanged=False, Calling=A, CalledChanged=True, Called=C, OriginalCalled=NULL, LR=NULL, Cause=Redirect

LINE_CALLINFO, hDevice=hCall-1, dwCallbackInstance=0, dwParam1=CONNECTEDID, REDIRECTINGID, REDIRECTIONID

TSPI LINECALLINFO
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=C
dwConnectedID=NULL
dwRedirectingID=NP
dwRedirectionID=NP

Party B

CallStateChangedEvent,
CH=C2,
State=Idle,
reason=DIRECT,
Calling=A,
Called=B,
OriginalCalled=B,
LR=NULL

TSPI: LINE_CALLSTATE, hDevice=hCall-1, dwCallbackInstance=0, dwParam1=IDLE dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NULL
dwRedirectingID=NULL
dwRedirectionID=NULL

Party C's VMP

NewCallEvent,
CH=C3,
origin=Internal_Inbound,
reason=Redirect,
Calling=A,
Called=C,
OriginalCalled=C,
LR=B

TSPI: LINE_APPNEWCALL
hDevice=C
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwReason=REDIRECT
dwCallerID=A
dwCalledID=C
dwConnectedID=NULL
dwRedirectingID=B
dwRedirectionID=C's VMP

Party C is offering

Party A

CallStateChangeEvent,
CH=C1,
State=Ringback,
Reason=Direct,
Calling=A,
Called=C,
OriginalCalled=C,
LR=B

TSPI: LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1= RINGBACK
dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NULL
dwRedirectingID=B
dwRedirectionID=C's VMP

Party C
CallStateChangedEvent,
CH=C3,
State=Offering,
Reason=Redirect,
Calling=A,
Called=C,
OriginalCalled=C,
LR=B

TSPI: LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1= OFFERING
dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwCallerID=A
dwCalledID=C
dwConnectedID=NULL
dwRedirectingID=B
dwRedirectionID=C


Shared Lines-Initiating a New Call Manually

Table A-4 describes the message sequences for Shared Lines-Initiating a new call manually where Party A and Party A' represent shared line appearances. Also, Party A and Party A' are idle.

Table A-4 Message Sequences for Shared Lines-Initiating a New Call Manually 

Action
CTI Messages
TAPI Messages
TAPI Structures

1. Party A goes off-hook

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct,
RIU=false

LINE_APPNEWCALL
hDevice=A
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent,
CH=C1,
State=Dialtone,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
RIU=false

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALTONE
dwParam2=UNAVAIL
dwParam3=0

No change

Party A'

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A',
Called=NP,
OrigCalled=NP,
LR=NP, S
tate=Dialtone,
Origin=OutBound,
Reason=Direct,
RIU=true

LINE_APPNEWCALL
hDevice=A'
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-2
dwParam3=OWNER

LINECALLINFO (hCall-2)
hLine=A'
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A'
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent,
CH=C1,
State=Dialtone,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
RIU=true

LINE_CALLSTATE
hDevice=hCall-2
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=INACTIVE
dwParam3=0

No change

2. Party A dials Party B

Party A

CallStateChangedEvent,
CH=C1,
State=Dialing,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
RIU=false

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

Party A'

None

None

None

3. Party B accepts call

Party A

CallPartyInfoChangedEvent,
CH=C1,
CallingChanged=False,
Calling=A,
CalledChanged=true,
Called=B,
Reason=Direct,
RIU=false

Ignored

No change

CallStateChangedEvent,
CH=C1,
State=Proceeding,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP,
RIU=false

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=
CALLERID, CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent,
CH=C1,
State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP,
RIU=false

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

No change

3. Party B accepts call (continued)

Party A'

CallPartyInfoChangedEvent,
CH=C1,
CallingChanged=False,
Calling=A',
CalledChanged=true,
Called=B,
Reason=Direct,
RIU=true

Ignored

No change

CallStateChangedEvent,
CH=C1,
State=Proceeding,
Cause=CauseNoError,
Reason=Direct,
Calling=A',
Called=B,
OrigCalled=B,
LR=NP,
RIU=true

LINE_CALLSTATE
hDevice=hCall-2
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=INACTIVE
dwParam3=0

LINE_CALLINFO
hDevice=hCall-2
dwCallbackInstance=0
dwParam1=
CALLERID, CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-2)
hLine=A'
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A'
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent,
CH=C1, State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A', Called=B,
OrigCalled=B,
LR=NP, RIU=true

LINE_CALLSTATE
hDevice=hCall-2
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=INACTIVE
dwParam3=0

No change

4. Party B answers call

Party A

CallStateChangedEvent,
CH=C1,
State=Connected,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP,
RIU=false

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=ACTIVE
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTEDID
dwParam2=0, dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=B
dwRedirectionID=NP
dwRedirectionID=NP

Party A'

CallStateChangedEvent, CH=C1,
State=Connected,
Cause=CauseNoError,
Reason=Direct,
Calling=A',
Called=B,
OrigCalled=B,
LR=NP,
RIU=true

LINE_CALLSTATE
hDevice=hCall-2
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=INACTIVE
dwParam3=0

LINE_CALLINFO
hDevice=hCall-2
dwCallbackInstance=0
dwParam1=CONNECTEDID
dwParam2=0, dwParam3=0

LINECALLINFO (hCall-2)
hLine=A'
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A'
dwCalledID=B
dwConnectedID=B
dwRedirectionID=NP
dwRedirectionID=NP


Presentation Indication

Making a Call Through Translation Pattern

Table A-5 describes the message sequences for the Presentation Indication scenario of making a call through translation pattern. In the Translation Pattern admin pages, both the callerID/Name and ConnectedID/Name get set to "Restricted".

Table A-5 Message Sequences for Making a Call Through Translation Pattern 

Action
CTI Messages
TAPI Messages
TAPI Structures

Party A goes off-hook

NewCallEvent,
CH=C1, GCH=G1,
Calling=A, Called=NP, OrigCalled=NP, LR=NP, State=Dialtone, Origin=OutBound, Reason=Direct

LINE_APPNEWCALL
hDevice=A
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1, State=Dialtone, Cause=CauseNoError, Reason=Direct, Calling=A, Called=NP, OrigCalled=NP, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALTONE
dwParam2=UNAVAIL
dwParam3=0

No change

Party A dials Party B through Translation pattern

CallStateChangedEvent, CH=C1, State=Dialing, Cause=CauseNoError, Reason=Direct, Calling=A, Called=NP, OrigCalled=NP, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

Party B accepts the call

CallStateChangedEvent, CH=C1, State=Proceeding, Cause=CauseNoError, Reason=Direct, Calling=A, CallingPartyPI=Allowed, Called=B, CalledPartyPI= Restricted, OrigCalled=B, OrigCalledPI=restricted, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=
PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A dwCallerIDName=A's Name
dwCalledID=B
dwCalledIDName=B's name dwConnectedID=NP
dwConnectedIDName=NP
dwRedirectionID=NP dwRedirectionIDName=NP
dwRedirectionID=NP dwRedirectionIDName=NP

Party B accepts the call
(continued)

CallStateChangedEvent, CH=C1, State=Ringback, Cause=CauseNoError, Reason=Direct, Calling=A, CallingPI = Allowed, Called=B, CalledPI = Restricted, OrigCalled=B, OrigCalledPI = Restricted, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedIDFlags = LINECALLPARTYID_
BLOCKED dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP

Party B answers the call

CallStateChangedEvent, CH=C1, State=Connected, Cause=CauseNoError, Reason=Direct, Calling=A, CallingPI = Allowed, Called=B, CalledPI = Restricted, OrigCalled=B, OrigCalledPI = Restricted, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=ACTIVE
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A dwCallerIDName=A's Name
dwCalledID=B dwCalledIDName=B's Name
dwConnectedID=A, dwConnectedIDName=
A's Name,
dwRedirectingID=NP
dwRedirectingIDName=NP
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP dwRedirectionIDName=NP

CallStartReceptionEvent, DH=A, CH=C1

LINE_DEVSPECIFIC1
hDevice=hCall-1
dwCallBackInstance=0
dwParam1=
StartReception
dwParam2=IP Address
dwParam3=Port

No change

CallStartTransmissionEvent, DH=A, CH=C1

LINE_DEVSPECIFIC1
hDevice=hCall-1
dwCallBackInstance=0
dwParam1=
StartTransmission
dwParam2=IP Address
dwParam3=Port

No change

1 LINE_DEVSPECIFIC events only get sent if the application requested them by using lineDevSpecific().


Blind Transfer Through Translation Pattern

Table A-6 describes the message sequences for the Presentation Indication scenario of Blind Transfer through Translation Pattern. In this scenario, A calls via translation pattern B, B answers, and A and B are connected.

Table A-6 Message Sequences for Blind Transfer Through Translation Pattern 

Action
CTI Messages
TAPI Messages
TAPI Structures

Party B does a lineBlindTranfser() to blind transfer call from party A to party C via translation pattern

Party A
 

CallPartyInfoChangedEvent, CH=C1, CallingChanged=False, Calling=A,
CallingPartyPI=Restricted, CalledChanged=True, Called=C,
CalledPartyPI=Restricted, OriginalCalled=NULL, OriginalCalledPI=Restricted,
LR=NULL, Cause=BlindTransfer

LINE_CALLINFO, hDevice=hCall-1, dwCallbackInstance=0, dwParam1=CONNECTEDID, REDIRECTINGID, REDIRECTIONID

TSPI LINECALLINFO
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerIDFlags = LINECALLPARTYID_
BLOCKED
dwCallerID=NP dwCallerIDName=NP
dwCalledID=B dwCalledIDName=B's name
dwConnectedIDFlags = LINECALLPARTYID_
BLOCKED dwConnectedID=NP dwConnectedIDName=NP dwRedirectingID=B
dwRedirectingIDName=
B's name
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP dwRedirectionIDName=NP

 
Party B
 

CallStateChangedEvent, CH=C2,
State=Idle, Reason=Direct,
Calling=A, CallingPartyPI=Restricted, Called=B, CalledPartyPI=Restricted, OriginalCalled=B, OrigCalledPartyPI=Restricted, LR=NULL

TSPI: LINE_CALLSTATE, hDevice=hCall-1, dwCallbackInstance=0, dwParam1=IDLE dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerIDFlags = LINECALLPARTYID_
BLOCKED
dwCallerID=NP dwCallerIDName=NP
dwCalledID=B dwCalledIDName=B's name
dwConnectedIDFlags = LINECALLPARTYID_
BLOCKED dwConnectedID=NP dwConnectedIDName=NP dwRedirectingID=B
dwRedirectingIDName=
B's name
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP dwRedirectionIDName=NP

Party B does a lineBlindTranfser() to blind transfer call from party A to party C via translation pattern (continued)

Party C

NewCallEvent,
CH=C3,
origin=Internal_Inbound,
Reason=BlindTransfer,
Calling=A,
CallingPartyPI=Restricted,
Called=C,
CalledPartyPI=Restricted,
OriginalCalled=B, OrigCalledPartyPI=Restricted,
LR=B,
LastRedirectingPartyPI=
Restricted

TSPI: LINE_APPNEWCALL hDevice=C
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwReason=TRANSFER
dwCallerIDFlags = LINECALLPARTYID_
BLOCKED
dwCallerID=NP dwCallerIDName=NP
dwCalledID=NP dwCalledIDName=NP
dwConnectedIDFlags = LINECALLPARTYID_
BLOCKED dwConnectedID=NP dwConnectedIDName=NP dwRedirectingID=B
dwRedirectingIDName=
B's name
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP dwRedirectionIDName=NP

Party C is offering

Party A

CallStateChangeEvent, CH=C1,
State=Ringback, Reason=Direct,
Calling=A,
CallingPartyPI=Restricted,
Called=C,
CalledPartyPI=Restricted,
OriginalCalled=B, OrigCalledPartyPI=Restricted,
LR=B, LastRedirectingPartyPI=
Restricted

TSPI: LINE_CALLSTATE, hDevice=hCall-1, dwCallbackInstance=0, dwParam1= RINGBACK dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerIDFlags = LINECALLPARTYID_
BLOCKED
dwCallerID=NP dwCallerIDName=NP
dwCalledID=B dwCalledIDName=B's name
dwConnectedIDFlags = LINECALLPARTYID_
BLOCKED dwConnectedID=NP dwConnectedIDName=NP dwRedirectingID=B
dwRedirectingIDName=
B's name
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP dwRedirectionIDName=NP

Party C is offering (continued)

Party C

CallStateChangedEvent, CH=C3,
State=Offering, Reason=BlindTransfer, Calling=A,
CallingPartyPI=Restricted,
Called=C,
CalledPartyPI=Restricted,
OriginalCalled=B,
OrigCalledPartyPI=Restricted,
LR=B, LastRedirectingPartyPI=
Restricted

TSPI: LINE_CALLSTATE, hDevice=hCall-1, dwCallbackInstance=0, dwParam1= OFFERING dwParam2=0
dwParam3=0

TSPI LINECALLINFO
dwOrigin=INTERNAL
dwCallerIDFlags = LINECALLPARTYID_
BLOCKED dwCallerID=NP dwCallerIDName=NP
dwCalledID=NP dwCalledIDName=NP
dwConnectedIDFlags = LINECALLPARTYID_
BLOCKED dwConnectedID=NP dwConnectedIDName=NP dwRedirectingID=B
dwRedirectingIDName=
B's name
dwRedirectionIDFlags = LINECALLPARTYID_
BLOCKED dwRedirectionID=NP dwRedirectionIDName=NP


Forced Authorization and Client Matter Code Scenarios

Manual Call to a Destination that Requires an FAC

Table A-7 describes the message sequences for the Forced Authorization and Client Matter Code scenario of Manual Call to a Destination that requires an FAC.

Preconditions

Party A is Idle. Party B requires an FAC.

The scenario remains similar if Party B requires a CMC instead of an FAC.

Table A-7 Message Sequences for Manual Call to a Destination that Requires an FAC 

Actions
CTI Message
TAPI Messages
TAPI Structures

Party A goes off-hook

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_APPNEWCALL
hDevice=A
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Dialtone,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALTONE
dwParam2=UNAVAIL
dwParam3=0

No change

Party A dials Party B

CallStateChangedEvent, CH=C1,
State=Dialing, Cause=CauseNoError, Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

CallToneChangedEvent, CH=C1,
Tone=ZipZip, Feature=FACCMC, FACRequired=True, CMCRequired=False

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3=
CZIPZIP_FACREQUIRED

No change

Party A dials the FAC, and Party B accepts the call

CallStateChangedEvent, CH=C1,
State=Proceeding,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

No change


Manual Call to a Destination that Requires both FAC and CMC

Table A-8 describes the message sequences for the Forced Authorization and Client Matter Code scenario of a manual call to a destination that requires both FAC and CMC.

Preconditions

Party A is Idle. Party B requires an FAC and a CMC.

Table A-8 Message Sequences for Manual Call to a Destination that Requires both FAC and CMC 

Actions
CTI Message
TAPI Messages
TAPI Structures

Party A goes off-hook

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_APPNEWCALL
hDevice=A
dwCallbackInstance=0
dwParam1=0
dwParam2=hCall-1
dwParam3=OWNER

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Dialtone,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALTONE
dwParam2=UNAVAIL
dwParam3=0

No change

Party A dials Party B

CallStateChangedEvent, CH=C1,
State=Dialing,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

CallToneChangedEvent, CH=C1,
Tone=ZipZip,
Feature=FACCMC,
FACRequired=True,
CMCRequired=True

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3=
CZIPZIP_FACREQUIRED,
CZIPZIP_CMCREQUIRED

No change

Party A dials the FAC

CallToneChangedEvent, CH=C1,
Tone=ZipZip,
Feature=FACCMC,
FACRequired=False,
CMCRequired=True

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3= CZIPZIP_CMCREQUIRED

No change

Party A dials the CMC, and Party B accepts the call

CallStateChangedEvent, CH=C1,
State=Proceeding,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

No change


lineMakeCall to a Destination that Requires an FAC

Table A-9 describes the message sequences for the Forced Authorization and Client Matter Code scenario of lineMakeCall to a destination that requires an FAC.

Preconditions

Party A is Idle. Party B requires an FAC. Note that the scenario is similar if Party requires a CMC instead of an FAC.

Table A-9 Message Sequences for lineMakeCall to a Destination that Requires an FAC 

Actions
CTI Message
TAPI Messages
TAPI Structures

Party A does a lineMakeCall() to Party B

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=ORIGIN
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=
REASON, CALLERID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Dialing,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

CallToneChangedEvent, CH=C1, Tone=ZipZip, Feature=FACCMC, FACRequired=True, CMCRequired=False

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3=
CZIPZIP_FACREQUIRED

No change

Party A does a lineDial() with the FAC in the dial string and Party B accepts the call

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

No change


lineMakeCall to a Destination that Requires Both FAC and CMC

Table A-10 describes the message sequences for the Forced Authorization and Client Matter Code scenario of lineMakeCall to a destination that requires both FAC and CMC. In this scenario, Party A is Idle and Party B requires both an FAC and a CMC.

Table A-10 Message Sequences for lineMakeCall to a Destination that Requires Both FAC and CMC 

Actions
CTI Message
TAPI Messages
TAPI Structures

Party A does a lineMakeCall() to Party B

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=ORIGIN
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=
REASON, CALLERID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Dialing,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

CallToneChangedEvent, CH=C1,
Tone=ZipZip,
Feature=FACCMC,
FACRequired=True,
CMCRequired=True

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3=
CZIPZIP_FACREQUIRED,
CZIPZIP_CMCREQUIRED

No change

Party A does a lineDial() with the FAC in the dial string

CallToneChangedEvent, CH=C1,
Tone=ZipZip,
Feature=FACCMC,
FACRequired=False,
CMCRequired=True

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3= CZIPZIP_CMCREQUIRED

No change

Party A does a lineDial() with the CMC in the dial string and Party B accepts the call

CallStateChangedEvent, CH=C1,
State=Proceeding,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=PROCEEDING
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CALLEDID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Ringback,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=B,
OrigCalled=B,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=RINGBACK
dwParam2=0
dwParam3=0

No change


Timeout Waiting for FAC or Invalid FAC

Table A-11 describes the message sequences for the Forced Authorization and Client Matter Code scenario of timeout waiting for FAC or invalid FAC entered. Here, Party A is Idle and Party B requires an FAC.

The scenario remains similar if Party B required a CMC instead of a FAC.

Table A-11 Message Sequences for Timeout Waiting for FAC or Invalid FAC

Actions
CTI Message
TAPI Messages
TAPI Structures

Party A does a lineMakeCall() to Party B

NewCallEvent,
CH=C1,
GCH=G1,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP,
State=Dialtone,
Origin=OutBound,
Reason=Direct

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=ORIGIN
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=
REASON, CALLERID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectionID=NP

CallStateChangedEvent, CH=C1,
State=Dialing,
Cause=CauseNoError,
Reason=Direct,
Calling=A,
Called=NP,
OrigCalled=NP,
LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DIALING
dwParam2=0
dwParam3=0

No change

CallToneChangedEvent, CH=C1,
Tone=ZipZip,
Feature=FACCMC,
FACRequired=True,
CMCRequired=False

LINE_DEVSPECIFIC
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=SLDSMT_CALL_TONE_CHANGED
dwParam2=CTONE_ZIPZIP
dwParam3=
CZIPZIP_FACREQUIRED

No change

T302 timer times out waiting for digits, or Party A does a lineDial() with an invalid FAC

CallStateChangedEvent, CH=C1, State=Disconnected,
Cause=
CtiNoRouteToDDestination,
Reason=FACCMC,
Calling=A, Called=NP,
OrigCalled=NP, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=DISCONNECTED
dwParam2=DISCONNECT
MODE_FACCMC1
dwParam3=0

No change

CallStateChangedEvent, CH=C1, State=Idle, Cause=CtiCauseNoError, Reason=Direct, Calling=A, Called=NP, OrigCalled=NP, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=IDLE
dwParam2=0
dwParam3=0

No change

1 dwParam2 get set to DISCONNECTMODE_FACCMC if the extension version on the line is set to at least 0x00050000. Otherwise, dwParam2 get set to DISCONNECTMODE_UNAVAIL.

Refer and Replaces Scenarios

In-Dialog Refer - Referrer in Cisco Unified Communications Manager Cluster

Table A-12 describes the message sequences for the Refer and Replaces scenario of in-dialog refer where referer is in Cisco Unified Communications Manager cluster.

Table A-12 Message Sequences for In-Dialog Refer - Referrer in Cisco Unified Communications
Manager Cluster 

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

Referrer (A), Referee (B), and Refer-to-Target (C) exist in Cisco Unified Communications Manager cluster, and CTI is monitoring those lines

A-->B has a call in connected state. The call party information at A should be {calling=A, called=B, LRP=null, origCalled=B, reason=direct}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = B
dwReason = Direct
dwOrigin =LINECALL
ORIGIN_INTERNAL

A-->B has a call in connected state. The call party information at B should be {calling=A, called=B, LRP=null, origCalled=B, reason=direct}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = A
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

 

(A) initiates REFER (B) to (C)

A gets LINECALLSTATE_
UNKNOWN | CLDSMT_
CALL_WAITING_STATE
with extended reason = REFER

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = B
dwReason = Direct
dwOrigin =LINECALL
ORIGIN_INTERNAL

 

NewCallEvent should be {calling=B, called=C, LRP=A, origCalled=C, reason=REFER}

LINECALLSTATE_OFFERING

TAPI CallInfo
dwCallerID = B
dwCalledID = C
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = ""
dwReason =LINECALL
REASON_UNKNOWN with extended REFER
dwOrigin = LINECALL
ORIGIN_INTERNAL

C answers the call, and Refer is successful

LINECALLSTATE_IDLE with extended REFER reason

CallPartyInfoChangedEvent @ B with {calling=B, called=C, LRP=A, origCalled=C, reason=REFER}

TAPI callInfo
dwCallerID = B
dwCalledID = B
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = C
dwReason = DIRECT
dwOrigin = LINECALL
ORIGIN_INTERNAL

LINECALLSTATE_CONNECTED

TAPI callInfo
dwCallerID = B
dwCalledID = C
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = B
dwReason = LINECALL
REASON_UNKNOWN with extended REFER
dwOrigin = LINECALL
ORIGIN_INTERNAL


In-Dialog Refer Where ReferToTarget Redirects the Call in Offering State

Table A-13 describes the message sequences for the Refer and Replaces scenario of in-dialog refer where ReferToTarget redirects the call in Offering state.

Table A-13 Message Sequences for In-Dialog Refer Where ReferToTarget Redirects the Call in
Offering State 

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

Referrer (A), Referee (B), and Refer-to-Target (C) exist in Cisco Unified Communications Manager cluster, and CTI is monitoring those lines

A-->B has a call in connected state. The call party information at A should be {calling=A, called=B, LRP=null, origCalled=B, reason=direct}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = B
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

A-->B has a call in connected state. The call party information at B should be {calling=A, called=B, LRP=null, origCalled=B, reason=direct}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = A
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

 

(A) initiates REFER (B) to (C)

A gets LINECALLSTATE_
UNKNOWN | CLDSMT_
CALL_WAITING_STATE
with extended reason = REFER

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = B
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

B gets CPIC with (calling = B, called = C, ocdpn=C, LRP = A, reason = REFER, call state = Ringback)

TAPI CallInfo
dwCallerID = B
dwCalledID = C
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = null
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

NewCallEvent should be {calling=B, called=C, LRP=A, origCalled=C, reason=REFER}

LINECALLSTATE_OFFERING

TAPI callInfo
dwCallerID = B
dwCalledID = C
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = null
dwReason = LINECALL
REASON_UNKNOWN with extended REFER
dwOrigin = LINECALL
ORIGIN_INTERNAL

C Redirects the call to D in offering state, and D answers

LINECALLSTATE_IDLE with extended reason = REFER

(REFER considered as successful when D answers)

CallPartyInfoChangedEvent @ B with {calling=B, called=D, LRP=C, origCalled=C, reason=Redirect}

Callstate = connected

TAPI callInfo
dwCallerID = B
dwCalledID = B
dwRedirectingID = C
dwRedirectionID = D
dwConnectedID = D
dwReason = DIRECT
dwOrigin = LINECALL
ORIGIN_INTERNAL

IDLE with reason = Redirect

TAPI LINECALLSTATE_IDLE

D will get NewCallEvent with reason = Redirect call info same as B's call info. (calling=B, called=D, ocdpn = C, LRP = C, reason = redirect)

Offering/accepted/connected


In-Dialog Refer Where Refer Fails or Refer to Target is Busy

Table A-14 describes the message sequences for the Refer and Replaces scenario of in-dialog refer fails or refer to target is busy.

Table A-14 Message Sequences for In-Dialog Refer Where Refer Fails or Refer to Target is Busy 

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

Referrer (A), Referee (B,) and Refer-to-Target (C) exist in Cisco Unified Communications Manager cluster, and CTI is monitoring those lines

A-->B has a call in connected state. The call party information at A should be {calling=A, called=B, LRP=null, origCalled=B, reason=direct}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = B
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

A-->B has a call in connected state. The call party information at B should be {calling=A, called=B, LRP=null, origCalled=B, reason=direct}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = A
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

 

(A) initiates REFER (B) to (C)

A gets LINECALLSTATE_
UNKNOWN | CLDSMT_
CALL_WAITING_STATE with extended reason = REFER

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = B
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

No change

 

C is busy / C does not answer

A gets LINECALLSTATE_ CONNECTED with extended reason = REFER

(REFER considered as failed)

If B goes to ringback when call is offered to C (C does not answer finally) it should also receive Connected Call State and CPIC event

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = A
dwReason = Direct
dwOrigin = LINECALL
ORIGIN_INTERNAL

 

Out-of-Dialog Refer

Table A-15 describes the message sequences for the Refer and Replaces scenario of out-of-dialog refer.

Table A-15 Message Sequences for Out-of-Dialog Refer 

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

Referrer (A), Referee (B), and Refer-to-Target (C) exist in Cisco Unified Communications Manager cluster, and CTI is monitoring those lines

There is no preexisting call between A and B.

There is no preexisting call between A and B.

 

A initiates REFER B to (C)

 

B should get NewCallEvent with call info as {calling=A, called=B, LRP=null, origCalled=B, reason=REFER}

TAPI CallInfo
dwCallerID = A
dwCalledID = B
dwRedirectingID = null
dwRedirectionID = null
dwConnectedID = A
dwReason = LINECALL
REASON_ UNKNOWN with extended REFER
dwOrigin =LINECALL
ORIGIN_EXTERNAL

 

B answers

 

Call state = connected (media does not flow between A and B when call goes to connected state)

TAPI CallInfo (no change)

 

Cisco Unified Communications Manager redirects the call to C

 

CallPartyInfoChangedEvent @ B with {calling=B, called=C, LRP=A, origCalled=C, reason=REFER}

TAPI callInfo
dwCallerID = B
dwCalledID = B
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = C
dwReason = LINECALL
REASON_ UNKNOWN with extended REFER
dwOrigin = LINECALL
ORIGIN_EXTERNAL

NewCallEvent should be {calling=B, called=C, LRP=A, origCalled=C, reason=REFER} This info is exactly same as though caller (A) performed REDIRECT operation (except the reason is different here).

TAPI callInfo
dwCallerID = B
dwCalledID = C
dwRedirectingID = A
dwRedirectionID = C
dwConnectedID = B
dwReason = LINECALL
REASON_ UNKNOWN with extended REFER
dwOrigin = LINECALL
ORIGIN_INTERNAL


Invite with Replace for Confirmed Dialog

Table A-16 describes the message sequences for the Refer and Replaces scenario of invite with replace for confirmed dialog. Here, A, B, and C exist inside Cisco Unified Communications Manager. A confirmed dialog occurs between A and B. C initiates Invite to A with replace B's dialog ID.

Table A-16 Message Sequences for Invite with Replace for Confirmed Dialog

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

Confirmed dialog occurs between A and B

Call State = connected,
Caller=A,
Called=B,
Connected=B,
Reason =direct,
gcid = GC1

Call State = connected
Caller=A,
Called=B,
Connected=A,
Reason =direct,
gcid = GC1

 

C Invites A by replacing B's dialog

   

NewCall at C gcid = GC2, reason=REPLACEs,
Call state = Dialing,
Caller=C,
Called=null,
Reason = REPLACEs

Cisco Unified Communications Manager joins A and C in a call and disconnects call leg @ B

GCID Changed to GC2,
Reason = REPLACEs

CPIC Caller = C,
Called = A,
ocdpn = A,
LRP = B
Reason = REPLACEs

Callstate = connected

TAPI callinfo
caller=C,
called=B,
connected=C,
redirecting=B,
redirection=A, reason=DIRECT with extended REPLACEs,
callID=GC2

Call State = IDLE,
extended reason = REPLACEs

CPIC changed

Caller = C,
Called = A,
ocdpn = A,
LRP = B,
Reason=REPLACEs

CallState = connected

TAPI callinfo
Caller=C,
Called=A,
Connected=A,
Redirecting=B,
Redirection=A, reason=UNKNOWN with extended REPLACEs,
callID=GC2


Refer with Replace for All in Cluster

Table A-17 describes the message sequences for the Refer and Replaces scenario of refer with replace for all in cluster. Here, a confirmed dialog exists between A and B and A and C. A initiates Refer to C with replace B's dialog ID.

Table A-17 Message Sequences for Refer with Replace for All in Cluster

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

Dialog between A and B and dialog between A and C

Call State = onhold,
GC1,
Caller=A,
Called=C,
Connected=C,
Reason =direct

CallState = connected,
GC2,
Caller = A,
Called = B,
Connected=B,
Reason =direct

Call State = connected
Caller=A,
Called=B,
Connected=A,
Reason =direct,
gcid = GC2

Call State = connected
Caller=A,
Called=C,
Connected=A,
Reason =direct,
gcid = GC1

A completes Refer to C replacing A->B's dialog (B is referred to target)

From CTI (callState = IDLE with reason = TRANSFER)

TAPI call state IDLE with Reason = DIRECT with extended reason TRANSFER

GCID changed from
CTI reason = TRANSFER

CPIC Changed from CTI Caller=B,
Called=C,
Origcalled = C,
LRP=A,
Reason=TRANSFER

TAPI callinfo
Caller=B,
Called=B,
Connected = C,
Redirecting=A,
Redirection=C,
Reason = DIRECT with extended reason TRANSFER.
CallId=GC1

CPIC Changed from CTI with Caller=B,
Called=C,
Origcalled = C,
LRP=A,
Reason=TRANSFER

TAPI callinfo caller=B, called=C, connected=B, redirecting=A, redirection=C, reason=direct with extended TRANSFER. callId=GC1


Refer with Replace for All in Cluster, Replace Dialog Belongs to Another Station

Table A-17 describes the message sequences for the Refer and Replaces scenario of refer with replace for all in cluster, where replace dialog belongs to another station. In this scenario:

A is Referrer, D is Referee, and C is Refer-to-Target.

A confirmed dialog exists between A(d1) and B & C(d2) and D.

A initiates Refer to D on (d1) with Replaces (d2).

Table A-18 Message Sequences for Refer with Replace for All in Cluster, Replace Dialog Belongs to Another Station 

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@B
CallState/CallInfo
@Refer-to-Target (C)
CallState/CallInfo
@Referree (D)

Dialog between A and B and dialog between C and D

Call State = onhold,

Caller=A,
Called=B,
Connected=B,
Reason =direct,
gcid=GC1

Call State = connected

Caller=A,
Called=B,
Connected=A,
Reason =direct,
gcid = GC1

Call State = connected

Caller=C,
Called=D,
Connected=D,
Reason =direct,
gcid = GC2

Call State = connected

Caller=C,
Called=D,
Connected=C,
Reason =direct,
gcid = GC2

A initiates Refer to D on (d1) with Replaces (d2)

From CTI
(callState = IDLE with reason = REFER)

TAPI call state IDLE with reason = DIRECT with extended reason = REFER

CPIC Changed from CTI Caller=B,
Called=C,
Origcalled = D,
LRP=C,
Reason=REPLACEs

TAPI callinfo
Caller=B,
Called=B,
Connected = D,
Redirecting=C,
Redirection=D,
Reason=DIRECT with extended REPLACEs, CallId=GC1

From CTI
(callState = IDLE with reason = REPLACEs.)

TAPI call state IDLE with reason = DIRECT with extended reason = REPLACEs

GCID changed from CTI to GC1

CPIC Changed from CTI with
Caller=B (referee), Called=D,
Origcalled = D,
LRP=C, Reason=REPLACEs

TAPI callinfo
caller=B,
called=D,
connected=B,
redirecting=C,
redirection=D,
reason=DIRECT with extended REPLACEs, callId=GC1


3XX

Application monitors B.

Table A-19 3XX

Actions
CallState/CallInfo
@Referrer (A)
CallState/CallInfo
@Referree (B)
CallState/CallInfo
@Refer-to-Target (C)

A calls external phone that is running SIP, which has CFDUNC set to B

 

TSPI: LINE_APPNEWCALL

Reason = LINECALL
REASON_REDIRECT

 

SRTP

Media Terminate by Application (Open Secure CTI Port or RP)

Negotiate version

Sends LineOpen with extension version as 0x8007000

Send CciscoLineDevSpecificUserSetSRTPAlgorithmID

Send CCiscoLineDevSpecificUserControlRTPStream

Now, the CTI port or RP gets registered as secure port

Make call from secure IP phone to the CTI port or RP port

Answer the call from application

SRTP indication gets reported as LineDevSpecific event

SRTP key information get stored in LINECALLINFO::devSpecifc for retrieval

Media Terminate by TSP Wave Driver (open secure CTI port)

Negotiate version

Sends LineOpen with extension version as 0x4007000

Send CciscoLineDevSpecificUserSetSRTPAlgorithmID

Send CciscoLineDevSpecificSendLineOpen

Now, the CTI port gets registered as secure port

Make call from secure IP phone to the CTI port

Answer the call from application

SRTP indication gets reported as LineDevSpecific event

SRTP key information get stored in LINECALLINFO::devSpecifc for retrieval

Intercom

This configuration gets used for all the following use cases:

1. IPPhone A has two lines, line1 (1000) and line2 (5000). Line2 represents an intercom line. Speeddial to 5001 with label ìAssistant_1î gets configured.

2. IPPhone B has three lines, line1 (1001), line2 (5001), and Line3 (5002). Line2 and Line3 represent intercom lines. Speeddial to 5000 with label ìManager_1î gets configured on line2. Line 3 does not have Speeddial configured for it.

3. IPPhone C has two lines, line1 (1002) and line2 (5003). 5003 represents an intercom line that is configured with Speeddial to 5002 with label ìAssistant_5002î.

4. IPPhone D has one line (5004). 5004 represnts an intercom line.

5. CTIPort X has two lines, line1 (2000) and line2 (5555). Line2 represents an intercom line. Speedial to 5001 gets configured with label ìAssistant_1î.

6. Intercom lines (5000 to 5003) exists in same partition = Intercom_Group_1 and they remain reachable from each other. 5004 exists in Intercom_Group_2.

7. Application monitoring all lines on all devices.

Assumption: Application initialized and CTI provided the details on speeddial and lines with intercom line on all the devices. Behavior should act the same for phones that are running SCCP, and those that are running SIP.

Application Invoking Speeddial

Action
Events

LineOpen on 5000 & 5001

Initiate InterCom Call on 5000

For 5000

receive LINE_CALLSTATE

cbInst=x0

param1=x03000000

param2=x1, ACTIVE

param3=x0,

Receive StartTransmission event

For 5001

receive LINE_CALLSTATE

cbInst=x0

param1= x03000000

param2=x1, ACTIVE

param3=x0,

Receive StartReception event

Receive zipzip tone with reason as intercom


Agent Invokes Talkback

Table 1:
Action
Events

Continuing from the previous use case, 5001 initiates LineTalkBack from application on the InterCom call

For 5000

receive LINE_CALLSTATE

device=x10218

param1=x100, CONNECTED

param2=x1, ACTIVE

param3=x0,

Receive StartReception event

For 5001

receive LINE_CALLSTATE

device=x101f6

cbInst=x0

param1=x100, CONNECTED

param2=x1, ACTIVE

param3=x0,

Receive StartTransmission event


Change the SpeedDial

Action
Events

Open line 5000

LineChangeSpeeddial request (speeddial to 5003, label = "Assistant_5003")

The new speed dial and label is successfully set for the intercom line

Receive LineSpeeddialChangeEvent from CTI

Send LINE_DEVSPECIFIC to indicate that speeddial and label changed

Application issues LIneGetDevCaps to retrieve speeddial/label that is set on the line

TAPI returns configured speeddial/label that is configured on the line.


Secure Conferencing

Conference with All Parties as Secure

The conference bridge includes security profile. MOH is not configured. A, B, and C get registered as Encrypted.

Action
CTI Messages
TAPI Messages
TAPI Structures

A calls B; B answers the call

Party A

 

CallStateChangedEvent, CH=C1, GCH=G1, Calling=A, Called=B, OrigCalled=B, LR=NP, State=Connected, Origin=OutBound, Reason=Direct

SecurityStaus= NotAuthenticated

CtiCallSecurityStatusUpdate

LH = A, CH = C1

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=A
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=B dwRedirectionID=NP
dwRedirectingID=NP

Devspecific Data :

CallSecurityInfo = Encrypted

 

Party B

 

CallStateChangedEvent, CH=C2, GCH=G1, Calling=A, Called=B, OrigCalled=B, LR=NP, State=Connected, Origin=OutBound, Reason=Direct

SecurityStaus=NotAuthenticated

CtiCallSecurityStatusUpdate

LH = B, CH = C2

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=B
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=B
dwCallID=T1
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=A dwRedirectionID=NP
dwRedirectingID=NP

Devspecific Data :

CallSecurityInfo = Encrypted

B does lineSetUpConference

Party B

 

CtiCallSecurityStatusUpdate

LH = B, CH = C2

SecurityStaus= NotAuthenticated

LINE_CALLDEVSPECIFIC
hDevice=B
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=B
dwCallID=T1
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=A
dwCalledID=B
dwConnectedID=A dwRedirectionID=NP
dwRedirectingID=NP

Devspecific Data :

CallSecurityInfo = NotAuthenticated

B calls C; C answers the call

Party B

 

CallStateChangedEvent, CH=C3, GCH=G2, Calling=A, Called=B, OrigCalled=B, LR=NP, State=Connected, Origin=OutBound, Reason=Direct

SecurityStaus=NotAuthenticated

CtiCallSecurityStatusUpdate

LH = B, CH = C3

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=B
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=B
dwCallID=T2
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=C
dwConnectedID=C dwRedirectionID=NP
dwRedirectingID=NP

Devspecific Data :

CallSecurityInfo = Encrypted

 

Party C

 

CallStateChangedEvent, CH=C4, GCH=G2, Calling=B, Called=C, OrigCalled=C, LR=NP, State=Connected, Origin=OutBound, Reason=Direct SecurityStaus= NotAuthenticated

CtiCallSecurityStatusUpdate

LH = C, CH = C4

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=C
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=B
dwCalledID=C
dwConnectedID=B dwRedirectionID=NP
dwRedirectingID=NP

Devspecific Data :

CallSecurityInfo = Encrypted

B completes conf

Party B

 

CtiCallSecurityStatusUpdate

LH = B, CH = C2

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=B
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=B
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP

dwRedirectionID=NP
dwRedirectingID=NP

Devspecific Data :

CallSecurityInfo = Encrypted


Hold or Resume in Secure Conference

Conference bridge includes security profile. MOH gets configured. A, B, and C represent secure phones and exist in conference with overall call security status as secure.

Action
CTI Messages
TAPI Messages
TAPI Structures

A does lineHold

Party A

 

CtiCallSecurityStatusUpdate,

LH = A, CH = C1,

SecurityStaus= NotAuthenticated

LINE_CALLDEVSPECIFIC
hDevice=A
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP dwRedirectionID=NP
dwRedirectionID=NP

Devspecific Data : CallSecurityInfo = NotAuthenticated

 

Party B

 

CtiCallSecurityStatusUpdate,

LH = B, CH = C2,

SecurityStaus= NotAuthenticated

LINE_CALLDEVSPECIFIC
hDevice=B
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=B
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP dwRedirectionID=NP
dwRedirectionID=NP

Devspecific Data : CallSecurityInfo = CtiCallSecurityStatusUpdate,

LH = A, CH = C1,

SecurityStaus= NotAuthenticated

 

Party C

 

CtiCallSecurityStatusUpdate,

LH = A, CH = C1,

SecurityStaus= NotAuthenticated

LINE_CALLDEVSPECIFIC
hDevice=C
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP dwRedirectionID=NP
dwRedirectionID=NP

Devspecific Data : CallSecurityInfo = NotAuthenticated

A does lineResume

Party A

 

CtiCallSecurityStatusUpdate,

LH = A, CH = C1,

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=A
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP dwRedirectionID=NP
dwRedirectionID=NP

Devspecific Data : CallSecurityInfo = Encrypted

 

Party B

 

CtiCallSecurityStatusUpdate,

LH = B, CH = C2,

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=B
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=B
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP dwRedirectionID=NP
dwRedirectionID=NP

Devspecific Data : CallSecurityInfo = Encrypted

 

Party C

 

CtiCallSecurityStatusUpdate,

LH = C, CH = C4,

SecurityStaus= Encrypted

LINE_CALLDEVSPECIFIC
hDevice=C
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_CALL_SECURITY_STATUS
dwParam3=0

LINECALLINFO (hCall-1)
hLine=
dwCallID=T1
dwOrigin=CONFERENCE
dwReason=UNKNOWN
dwCallerID=NP
dwCalledID=NP
dwConnectedID=NP dwRedirectionID=NP
dwRedirectionID=NP

Devspecific Data : CallSecurityInfo = Encrypted


Monitoring and Recording

Monitoring a Call

A (agent) and B (customer) get connected. BIB on A gets set to on.

Action
CTI Messages
TAPI Messages
TAPI Structures
 

Party C

C(supervisor) issues start monitoring req with A's permanentLineID as input

NewCallEvent, CH=C3, GCH=G2, Calling=C, Called=NP, OrigCalled=NP, LR=NP, State=Dialtone, Origin=OutBound, Reason=Direct

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=ORIGIN
dwParam2=0
dwParam3=0

LINE_CALLINFO
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=REASON, CALLERID
dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=C
dwCalledID=NP
dwConnectedID=NP
dwRedirectionID=NP
dwRedirectingID=NP

A's BIB automatically answers

Party C

 

CallStateChangedEvent, CH=C3, State=Connected, Cause=CauseNoError, Reason=Direct, Calling=C, Called=A, OrigCalled=A, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=ACTIVE
dwParam3=0

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=C
dwCalledID=A
dwConnectedID=A
dwRedirectionID=NP
dwRedirectingID=NP

 

Party A

 

MonitoringStartedEvent,

CH = C1

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_MONITOR_STARTED

dwParam2=0
dwParam3=0

LINECALLINFO (hCall-2)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B
dwRedirectionID=NP
dwRedirectingID=NP

 

Party C

 

LineCallAttributeInfoEvent,

CH=C3, Type = 2 (MonitorCall_Target),

CI = C1,

Address=A's DN, Partition=A's Partition, DeviceName = A's Name

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_LINECALLINFO_DEVSPECIFICDATA

dwParam2=SLDST_CALL_ATTRIBUTE_INFO
dwParam3=0

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=C
dwCalledID=A
dwConnectedID=A
dwRedirectionID=NP
dwRedirectingID=NP

DevSpecifc Data:

Type: CallAttribute_SilentMonitorCall_Target,

CI = C1,

DN = A's DN,

Partition = A's Partition,

DeviceName = A's Name

 

Party A

 

LineCallAttributeInfoEvent,

CH=C1, Type = 1 (MonitorCall),

CI = C3

Address=C's DN, Partition=C's Partition, DeviceName = C's Name

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_LINECALLINFO_DEVSPECIFICDATA

dwParam2=SLDST_CALL_ATTRIBUTE_INFO
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B
dwRedirectionID=NP
dwRedirectingID=NP

DevSpecifc Data:

Type:CallAttribute_SilentMonitorCall,

CI = C3

DN = C's DN,

Partition = C's Partition,

DeviceName = C's Name

C drops the call

Party C

 

CallStateChangedEvent, CH=C3, State=Idle, Cause=CauseNoError, Reason=Direct, Calling=C, Called=A, OrigCalled=A, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=IDLE
dwParam2=0
dwParam3=0

 
 

Party A

 

MonitoringEndedEvent,

CH = C1

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_MONITOR_ENDED

dwParam2= DisconnectMode_Normal
dwParam3=0

 
       

Automatic Recording

Recording type on A (agent Phone) is configured as Automatic. D is configured as a Recorder Device.

Action
CTI Messages
TAPI Messages
TAPI Structures

A recieves a call from B, and A answers the call

Recording session gets established between the agent phone and the recorder

Party A

 

CallStateChangedEvent, CH=C1, State=Connected, Cause=CauseNoError, Reason=Direct, Calling=B, Called=A, OrigCalled=A, LR=NP

LINE_CALLSTATE
hDevice=hCall-1
dwCallbackInstance=0
dwParam1=CONNECTED
dwParam2=ACTIVE
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=INTERNAL
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B
dwRedirectionID=NP
dwRedirectingID=NP

 

RecordingStartedEvent,

CH = C1

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_RECORDING_STARTED

dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1 dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B dwRedirectionID=NP
dwRedirectingID=NP

 

LineCallAttributeInfoEvent

CH = C1, Type = 3 (Automatic Recording), Address = D's DN, Partition = D's Partition, DeviceName = D's Name

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_LINECALLINFO_DEVSPECIFICDATA

dwParam2=SLDST_CALL_ATTRIBUTE_INFO
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B
dwRedirectionID=NP
dwRedirectingID=NP

DevSpecifc Data:

Type: App Controlled Recording,

DN = D's DN,

Partition = D's Partition,

DeviceName = D's Name


Application-Controlled Recording

A (C1) and B (C2) connect. Recording Type on A gets configured as `Application Based'. D gets configured as a Recorder Device.

Action
CTI Messages
TAPI Messages
TAPI Structures

A issues start recording request

Recording session gets established between the agent phone and the recorder

Party A

 

RecordingStartedEvent,

CH = C1

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_RECORDING_STARTED

dwParam2=0
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1 dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B dwRedirectionID=NP
dwRedirectingID=NP

 

LineCallAttributeInfoEvent

CH = C1, Type = 4 (App Controlled Recording), Address = D's DN, Partition = D's Partition, DeviceName = D's Name

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_LINECALLINFO_DEVSPECIFICDATA

dwParam2=SLDST_CALL_ATTRIBUTE_INFO
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B
dwRedirectionID=NP
dwRedirectingID=NP

DevSpecifc Data:

Type: App Controlled Recording,

DN = D's DN,

Partition = D's Partition,

DeviceName = D's Name

A issues stop monitoring request

RecordingEndedEvent,

CH = C1

LINE_CALLDEVSPECIFIC

hDevice=hCall-1
dwCallbackInstance=0

dwParam1 = SLDSMT_RECORDING_ENDED

dwParam2= DisconnectMode_Normal
dwParam3=0

LINECALLINFO (hCall-1)
hLine=A
dwCallID=T1
dwOrigin=OUTBOUND
dwReason=DIRECT
dwCallerID=B
dwCalledID=A
dwConnectedID=B
dwRedirectionID=NP
dwRedirectingID=NP


Conference Enhancements

Noncontroller Adding Parties to Conferences

A,B, and C exist in a conference that A created.

Action
Events

A,B, and C exist in a conference

At A:

Conference - Caller="A", Called="B", Connected="B"

Connected

Conference - Caller="A", Called="C", Connected="C"

At B:

Conference - Caller="A", Called="B", Connected="A"

Connected

Conference - Caller="B", Called="C", Connected="C"

At C:

Conference - Caller="B", Called="C", Connected="B"

Connected

Conference - Caller="C", Called="A", Connected="A"

C issues a linePrepareAddToConference to D

At A:

Conference - Caller="A", Called="B", Connecgted="B"

Connected

Conference - Caller="A", Called="C", Connecgted="C"

At B:

Conference - Caller="A", Called="B", Connecgted="A"

Connected

Conference - Caller="B", Called="C", Connecgted="C"

At C:

Conference - Caller="B", Called="C", Connecgted="B"

OnHoldPendConf

Conference - Caller="C", Called="A", Connecgted="A"

Connected - Caller="C", Called="D", Connecgted="D"

At D:

Connected - Caller="C", Called="D", Connecgted="C"

C issues a lineAddToConference to D

At A:

Conference - Caller="A", Called="B", Connecgted="B"

Connected

Conference - Caller="A", Called="C", Connecgted="C"

Conference - Caller="A", Called="D", Connecgted="D"

At B:

Conference - Caller="A", Called="B", Connecgted="A"

Connected

Conference - Caller="B", Called="C", Connecgted="C"

Conference - Caller="B", Called="D", Connecgted="D"

At C:

Conference - Caller="B", Called="C", Connecgted="B"

Connected

Conference - Caller="C", Called="A", Connecgted="A"

Conference - Caller="C", Called="D", Connecgted="D"

At D:

Conference - Caller="C", Called="D", Connecgted="C"

Connected

Conference - Caller="D", Called="A", Connecgted="A"

Conference - Caller="D", Called="B", Connecgted="B"


Chaining Two Ad Hoc Conferences by Using Join

Table 2:
Actions
TSP CallInfo

A calls B, B answers, then B initiates conference to C, C answers, and B completes the conference

At A:

GCID-1

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = A

Called = B

CONFERENCED : Caller = A

Called = C

At B:

GCID-1

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = A

Called = B

CONFERENCED : Caller = B

Called = C

At C:

GCID-1

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = B

Called = C

CONFERENCED : Caller = C

Called = A

C initiates or completes conference to D and E

No Change for A and B

At C:

- First conference

GCID-1

ONHOLD : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = A

Called = B

CONFERENCED : Caller = A

Called = C

- Second conference

GCID-2

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = C

Called = D

CONFERENCED : Caller = C

Called = E

At D:

GCID-2

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = C

Called = D

CONFERENCED : Caller = D

Called = E

At E:

GCID-2
CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = C

Called = E

CONFERENCED : Caller = E

Called = D

C initiates JOIN request to join to conference call together, with GCID as the primary call

At A:

GCID-1
CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = A

Called = B

CONFERENCED : Caller = A

Called = C

CONFERENCED : Caller = A

Called = Conference-2

At B :

GCID-1

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = A

Called = B

CONFERENCED : Caller = B

Called = C

CONFERENCED : Caller = B

Called = Conference-2

At C:

- First conference

GCID-1

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = B

Called = C

CONFERENCED : Caller = C

Called = A

CONFERENCED : Caller = C

Called = Conference-2

 

At D:

GCID-2

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = D

Called = E

CONFERENCED : Caller = D

Called = Conference-1

At E :

GCID-2

CONNECTED : Caller = Unknown

Caller = Unknown

CONFERENCED : Caller = E

Called = D

CONFERENCED : Caller = E

Called = Conference-1


Calling Party IP Address

Basic Call

TAPI application monitors party B

Party A represents an IP phone

A calls B

IP Address of A is available to TAPI application that is monitoring party B

Consultation Transfer

TAPI application monitors party C

Party B represents an IP phone

A talks to B

B intiates a consultation transfer call to C

IP Address of B is available to TAPI application that is monitoring party C.

B Completes the transfer

Calling IP address of A is not available to TAPI application that is monitoring party C (not a supported scenario).

Consultation Conference

TAPI application monitors party C

Party B represents an IP phone

A talks to B

B initiates a consultation conference call to C

IP Address of B is available to TAPI application that is monitoring party C.

B Completes the conference

Calling IP address of A and B is not available to TAPI application that is monitoring party C (not a supported scenario)

Redirect

TAPI application monitors party B and party C

Party A represents an IP phone

A calls B

IP Address of A is available to TAPI application that is monitoring party B

Party A redirects B to party C

Calling IP address is not available to TAPI application that is monitoring party B (not a supported scenario)

Calling IP address B is available to TAPI application that is monitoring party C

Click to Conference

Third-party conference gets created by using click-2-conference feature:

Action
Events

Use Click-to-Call to create call from A to B, and B answers

For A:

CONNECTED

reason = DIRECT

Calling = A, Called = B, Connected = B

For B:

CONNECTED

reason = DIRECT

Calling = A, Called = B, Connected = A

Use Click-2-Conference feature to add C into conference, and C answers

For A:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = B

CONFERENCED

Calling = A, Called = C, Connected = C

For B:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = A

CONFERENCED

Calling =B, Called = C, Connected = C

For C

CONNECTED

Reason = UNKNOWN

ExtendedCallReason = ClickToConference

CONFERENCED

Calling = C, Called = A, Connected = A

CONFERENCED

Calling = C, Called = B, Connected = B


Creating Four-Party Conference by Using Click-2-Conference Feature

Action
Events

Use Click-to-Call to create call from A to B

For A:

CONNECTED

reason = DIRECT

Calling = A, Called = B, Connected = B

For B:

CONNECTED

reason = DIRECT

Calling = A, Called = B, Connected = A

Use Click-2-Conference feature to add C into conference

For A:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = B

CONFERENCED

Calling = A, Called = C, Connected = C

For B:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = A

CONFERENCED

Calling = C, Called = C, Connected = C

For C

CONNECTED

Reason = DIRECT

ExtendedCallReason = ClickToConference

CONFERENCED

Calling = C, Called = A, Connected = A

CONFERENCED

Calling = C, Called = B, Connected = B

Use Click-2-Conference feature to add party D

For A:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = B

CONFERENCED

Calling = A, Called = C, Connected = C

CONFERENCED

Calling = A, Called = D, Connected = D

For B:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = A

CONFERENCED

Calling = B, Called = C, Connected = C

CONFERENCED

Calling = B, Called = D, Connected = D

For C

CONNECTED

Reason = UNKNOWN

ExtendedCallReason = ClickToConference

CONFERENCED

Calling = C, Called = A, Connected = A

CONFERENCED

Calling = C, Called = B, Connected = B

CONFERENCED

Calling = C, Called = D, Connected = D

For D

CONNECTED

Reason = UNKNOWN

ExtendedCallReason = ClickToConference

 

CONFERENCED

Calling = D, Called = A, Connected = A

CONFERENCED

Calling = D, Called = B, Connected = B

CONFERENCED

Calling = D, Called = C, Connected = C


Drop Party by Using Click-2-Conference

Action
Events

Conference gets created by using Click-2-Conference feature to add C into conference

For A:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = B

CONFERENCED

Calling = A, Called = C, Connected = C

For B:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = A

CONFERENCED

Calling = B, Called = C, Connected = C

For C

CONNECTED

Reason = UNKNOWN

ExtendedCallReason = ClickToConference

CONFERENCED

Calling = C, Called = A, Connected = A

CONFERENCED

Calling = C, Called = B, Connected = B

Drop C from Click-2-Conference feature

For A

CONNECTED

Reason = DIRECT

ExtendedCallReason = DIRECT

Calling = A, Called = B, Connected = B

For B

CONNECTED

Reason = DIRECT

ExtendedCallReason = DIRECT

Calling = A, Called = B, Connected = A

For C

IDLE


Drop Entire Conference by Using Click-2-Conference Feature

Action
Events

Conference gets created by using Click-2-Conference feature to add C into conference

For A:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = B

CONFERENCED

Calling = A, Called = C, Connected = C

For B:

CONNECTED

reason = DIRECT

ExtendedCallReason = DIRECT

CONFERENCED

Calling = A, Called = B, Connected = A

CONFERENCED

Calling = B, Called = C, Connected = C

For C

CONNECTED

Reason = UNKOWN

ExtendedCallReason = ClickToConference

CONFERENCED

Calling = C, Called = A, Connected = A

CONFERENCED

Calling = C, Called = B, Connected = B

Drop entire conference

For A

IDLE

For B

IDLE

For C

IDLE


Calling Party Normalization

Incoming Call from PSTN to End Point

Action
CTI Messages
TAPI Messages
TAPI Structures

A Call gets offered from a PSTN number 5551212/<SUBSCRIBER> through a San Jose gateway to a CCM end point 2000

CallStateChangedEvent, UnModified Calling Party=5551212, UnModified Called Party=2000, UnModified Original Called Party=2000, Modified Calling Party=5551212, Modified Called Party=2000, Modified Original Called Party=2000, Globalized Calling party = +14085551212, Calling Party Number Type=SUBSCRIBER, Called Party Number Type=UNKNOWN, Original Called Party Number Type,=UNKNOWN State=Connected, Origin=OutBound, Reason = Direct

LINE_CALLSTATE = CONNECTED

LINECALLINFO

Displayed Calling Party=5551212, Displayed Called Party=2000, Displayed Redirection Party=, Displayed Redirected Party=, Globalized Calling Party = +14085551212, Calling Party Number Type=SUBSCRIBER, Called Party Number Type= UNKNOWN, Redirection Party Number Type=, Redirecting Party Number Type=


Incoming Call from National PSTN to CTI-Observed End Point

Action
CTI Messages
TAPI Messages
TAPI Structures

A Call gets offered from a Dallas PSTN number 5551212/<NATIONAL> through a San Jose gateway to a CCM end point 2000

CallStateChangedEvent, UnModified Calling Party=9725551212, UnModified Called Party=2000, UnModified Original Called Party=2000, Modified Calling Party=9725551212, Modified Called Party=2000, Modified Original Called Party=2000, Globalized Calling party = +19725551212, Calling Party Number Type=NATIONAL, Called Party Number Type=UNKNOWN, Original Called Party Number Type,=UNKNOWN State=Connected, Origin=OutBound, Reason = Direct

LINE_CALLSTATE = CONNECTED

LINECALLINFO

Displayed Calling Party=9725551212, Displayed Called Party=2000, Displayed Redirection Party=, Displayed Redirected Party=, Globalized Calling Party = +19725551212, Calling Party Number Type=NATIONAL, Called Party Number Type= UNKNOWN, Redirection Party Number Type=, Redirecting Party Number Type=


Incoming Call from International PSTN to CTI-Observed End Point

Action
CTI Messages
TAPI Messages
TAPI Structures

A Call gets offered from a PSTN number in India 22221111/<INTERNATIONAL> through a San Jose gateway to a CCM end point 2000

CallStateChangedEvent, UnModified Calling Party=011914422221111, UnModified Called Party=2000, UnModified Original Called Party=2000, Modified Calling Party=011914422221111, Modified Called Party=2000, Modified Original Called Party=2000, Globalized Calling party = +914422221111, Calling Party Number Type=INTERNATIONAL, Called Party Number Type=UNKNOWN, Original Called Party Number Type,=UNKNOWN State=Connected, Origin=OutBound, Reason = Direct

LINE_CALLSTATE = CONNECTED

LINECALLINFO

Displayed Calling Party=011914422221111, Displayed Called Party=2000, Displayed Redirection Party=, Displayed Redirected Party=, Globalized Calling Party = +914422221111, Calling Party Number Type=INTERNATIONAL, Called Party Number Type = UNKNOWN, Redirection Party Number Type=, Redirecting Party Number Type=


Outgoing Call from CTI-Observed End Point to PSTN Number

Action
CTI Messages
TAPI Messages
TAPI Structures

A Call gets initiated from a CCM end point 2000 through a San Jose gateway to a PSTN number 5551212/<NATIONAL>

CallStateChangedEvent, UnModified Calling Party=2000, UnModified Called Party=5551212, UnModified Original Called Party=5551212, Modified Calling Party=2000, Modified Called Party=5551212, Modified Original Called Party=5551212, Globalized Calling party = +14085551212, Calling Party Number Type=UNKNOWN, Called Party Number Type=SUBSCRIBER, Original Called Party Number Type,=SUBSCRIBER State=Connected, Origin=OutBound, Reason = Direct

LINE_CALLSTATE = CONNECTED

LINECALLINFO

Displayed Calling Party=2000, Displayed Called Party=5551212, Displayed Redirection Party=, Displayed Redirected Party=, Globalized Calling Party = +14085551212, Calling Party Number Type=UNKNOWN, Called Party Number Type= SUBSCRIBER, Redirection Party Number Type=, Redirecting Party Number Type=


Outgoing Call from CTI-Observed End Point to National PSTN Number

Action
CTI Messages
TAPI Messages
TAPI Structures

A Call gets initiated from a CCM end point 2000 through a San Jose gateway to a Dallas PSTN number 9725551212/<NATIONAL>

CallStateChangedEvent, UnModified Calling Party=2000, UnModified Called Party=9725551212, UnModified Original Called Party=9725551212, Modified Calling Party=2000, Modified Called Party=9725551212, Modified Original Called Party=9725551212, Globalized Calling party = +19725551212, Calling Party Number Type=UNKNOWN, Called Party Number Type=NATIONAL, Original Called Party Number Type,=NATIONAL State=Connected, Origin=OutBound, Reason = Direct

LINE_CALLSTATE = CONNECTED

LINECALLINFO

Displayed Calling Party=2000, Displayed Called Party=9725551212, Displayed Redirection Party=, Displayed Redirected Party=, Globalized Calling Party = +19725551212, Calling Party Number Type=UNKNOWN, Called Party Number Type= NATIONAL, Redirection Party Number Type=, Redirecting Party Number Type=


Outgoing Call from CTI-Observed End Point to International PSTN Number

Action
CTI Messages
TAPI Messages
TAPI Structures

A Call gets initiated from a CCM end point 2000 through a San Jose gateway to a PSTN number in India 914422221111/<INTERNATIONAL>

CallStateChangedEvent, UnModified Calling Party=2000, UnModified Called Party=011914422221111, UnModified Original Called Party=011914422221111, Modified Calling Party=2000, Modified Called Party=011914422221111, Modified Original Called Party=011914422221111, Globalized Calling party = +914422221111, Calling Party Number Type=UNKNOWN, Called Party Number Type=INTERNATIONAL, Original Called Party Number Type,=INTERNATIONAL State=Connected, Origin=OutBound, Reason = Direct

LINE_CALLSTATE = CONNECTED

LINECALLINFO

Displayed Calling Party=2000, Displayed Called Party=011914422221111, Displayed Redirection Party=, Displayed Redirected Party=, Globalized Calling Party = +914422221111, Calling Party Number Type=UNKNOWN, Called Party Number Type = INTERNATIONAL, Redirection Party Number Type=, Redirecting Party Number Type=


Do Not Disturb-Reject

Application Enables DND-R on a Phone

Action
TAPI Messages
TAPI Structures

Phone A enables DND-Reject in the admin pages

LINE_CALLDEVSPECIFIC
hDevice=C
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_DND_OPTION_STATUS
dwParam3=2

 

Normal Feature Priority

Action
TAPI Messages
TAPI Structures

With Phone B DND-R enabled, Phone A calls Phone B with feature priority as Normal

Party A

 

LINE_CALLSTATE = IDLE

Party B

No TAPI messages


Feature Priority - Emergency

Action
TAPI Messages
TAPI Structures

With Phone B DND-R enabled, Phone A calls Phone B with feature priority as Emergency

Party A

LINE_CALLSTATE = CONNECTED

dwParam1 = 0x00000100

dwParam2 = 0x00000001

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=INTERNAL
dwCallerID=A
dwCalledID=B
dwRedirectionID=NP
dwRedirectingID=NP

Party B

LINE_CALLSTATE = CONNECTED

dwParam1 = 0x00000100

dwParam2 = 0x00000001

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=INTERNAL
dwCallerID=A
dwCalledID=B
dwRedirectionID=NP
dwRedirectingID=NP


Shared Line Scenario for DND-R

Action
TAPI Messages
TAPI Structures

Phones B and B' represents shared lines. Phone B' is DND-R enabled but not B. Phone A calls Phone B with feature priority normal

Party A

LINE_CALLSTATE = CONNECTED

dwParam1 = 0x00000100

dwParam2 = 0x00000001

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=INTERNAL
dwCallerID=A
dwCalledID=B
dwRedirectionID=NP
dwRedirectingID=NP

Party B

LINE_CALLSTATE = CONNECTED

dwParam1 = 0x00000100

dwParam2 = 0x00000001

LINECALLINFO (hCall-1)
hLine=C
dwCallID=T2
dwOrigin=INTERNAL
dwCallerID=A
dwCalledID=B
dwRedirectionID=NP
dwRedirectingID=NP

Party B'

 

LINE_CALLSTATE = CONNECTED

dwParam1 = 0x00000100

dwParam2 = 0x00000002

 

Application Disables DND-R or Changes the Option for DND

Action
TAPI Messages
TAPI Structures

Phone A changes from DND-Reject to DND-RingerOff.

LINE_CALLDEVSPECIFIC
hDevice=C
dwCallbackInstance=0
dwParam1= SLDSMT_LINECALLINFO_DEVSPECIFICDATA
dwParam2=SLDST_DND_OPTION_STATUS
dwParam3=1

 

Join Across Lines

Setup

Line A on device A

Line B1 and B2 on device B

Line C on device C

Line D on device D

Line B1' on device B1', B1' is a shared line with B1

Join Two Calls from Different Lines to B1

Action
Expected Events

A B1 is HOLD

For A

C B2 is connected

LINE_CALLSTATE param1=x100, CONNECTED Caller = A, Called = B1 Connected B1

 

For B1: LINE_CALLSTATE param1=x100, HOLD Caller = A, Called = B1, Connected = A

 

For B2: LINE_CALLSTATE param1=x100, CONNECTED Caller = C, Called = B2 , Connected = C

 

For C: LINE_CALLSTATE param1=x100, CONNECTED Caller = C, Called = B2, Connected = B2

 

For B1': LINE_CALLSTATE param1=x100, CONNECTED, INACTIVE Caller = A, Called = B1, Connected = A

Application issues lineDevSpecific(SLDST_JOIN) with the call on B1 as survival call

For A

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B1

 

CONFERENCED Caller=A Called=C, Connected=C

 

For B1

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

For B2

 

Call will go IDLE

 

For C

 

CONNECTED

 

CONFERENCED Caller=C, Called=B2, Connected=B1 (or A)

 

CONFERENCED Caller=C Called=A, Connected=A (or B1)

 

For B1'

 

CONNECTED INACTIVE

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C


Join Three Calls from Different Lines to B1

Action
Expected Events

A B1 is hold,

 

C B2 is hold

 

D B2 is connected

For A:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = A, Called = B1 Connected B1

 

For B1:

 

LINE_CALLSTATE

 

param1=x100, HOLD Caller = A, Called = B1, Connected = A

 

For B2:

 

LINE_CALLSTATE for call-1

 

param1=x100, HOLD Caller = C, Called = B2 , Connected = C

 

LINE_CALLSTATE for call-2

 

param1=x100, CONNECTED Caller = D, Called = B2 , Connected = D

 

For C:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2, Connected = B2

 

For D:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = D, Called = B2, Connected = B2

 

For B1':

 

LINE_CALLSTATE

 

param1=x100, HOLD Caller = A, Called = B1, Connected = A

Application issues lineDevSpecific(SLDST_JOIN) with the call on B1 as survival call

For A

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B1

 

CONFERENCED Caller=A Called=C, Connected=C

 

CONFERENCED Caller=A Called=D, Connected=D

 

For B1

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

CONFERENCED Caller=B1 Called=D, Connected=D

 

For B2

 

Call-1 and call-2 will go IDLE

 

For C

 

CONNECTED

 

CONFERENCED Caller=B1, Called=C, Connected=B1

 

CONFERENCED Caller=C Called=A, Connected=A

 

CONFERENCED Caller=C Called=D, Connected=D

 

For D

 

CONNECTED

 

CONFERENCED Caller=B1, Called=C, Connected=B1

 

CONFERENCED Caller=D Called=A, Connected=A

 

CONFERENCED Caller=D Called=C, Connected=C

 

For B1'

 

CONNECTED INACTIVE

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

CONFERENCED Caller=B1 Called=D, Connected=D


Join Calls from Different Lines to B1 with Conference

Action
Expected Events

A,B1,C in conference where B1 is controller

For A:

D B2 Connected

 
 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=A Called=C, Connected=C

 

For B1:

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

For B2:

 

LINE_CALLSTATE for call-1

 

param1=x100, CONNECTED Caller = D, Called = B2 , Connected = D

 

For C:

 

CONNECTED

 

CONFERENCED Caller=C, Called=A, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

For D:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = D, Called = B2, Connected = B2

 

For B1':

 

LINE_CALLSTATE

 

CONNECTED INACTIVE

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

Application issues lineDevSpecific(SLDST_JOIN) with the call on B1 as survival call

For A

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B1

 

CONFERENCED Caller=A Called=C, Connected=C

 

CONFERENCED Caller=A Called=D, Connected=D

 

For B1

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

CONFERENCED Caller=B1 Called=D, Connected=D

 

For B2

 

Call will go IDLE

 

For C

 

CONNECTED

 

CONFERENCED Caller=B1, Called=C, Connected=B1

 

CONFERENCED Caller=C Called=A, Connected=A

 

CONFERENCED Caller=C Called=D, Connected=D

 

For D

 

CONNECTED

 

CONFERENCED Caller=B1, Called=C, Connected=B1

 

CONFERENCED Caller=D Called=A, Connected=A

 

CONFERENCED Caller=D Called=C, Connected=C

 

For B1'

 

CONNECTED INACTIVE

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C

 

CONFERENCED Caller=B1 Called=D, Connected=D


Join Two Calls from Different Lines to B1 while B1 is not Monitored by TAPI

Action
Expected Events

A B1 is HOLD,

 

C B2 is connected

For A:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = A, Called = B1 Connected B1

 

For B2:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2 , Connected = C

 

For C:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2, Connected = B2

User issues join request from phone with the call on B1 as survival call

For A

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B1

 

CONFERENCED Caller=A Called=C, Connected=C

 

For B2

 

Call will go IDLE

 

For C

 

CONNECTED

 

CONFERENCED Caller=C, Called=B2, Connected=B1 (or A)

 

CONFERENCED Caller=C Called=A, Connected=A (or B1)


Join Two Calls from Different Lines to B2

Action
Expected Events

A B1 is HOLD,

 

C B2 is connected

For A:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = A, Called = B1 Connected B1

 

For B1:

 

LINE_CALLSTATE

 

param1=x100, HOLD Caller = A, Called = B1, Connected = A

 

For B2:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2 , Connected = C

 

For C:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2, Connected = B2

 

For B1':

 

LINE_CALLSTATE

 

param1=x100, HOLD Caller = A, Called = B1, Connected = A

Application issues lineDevSpecific(SLDST_JOIN) with the call on B1 as survival call

For A

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B1

 

CONFERENCED Caller=A Called=C, Connected=C

 

For B1

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C ??

 

For B2

 

Call will go IDLE

 

For C

 

CONNECTED

 

CONFERENCED Caller=C, Called=B2, Connected=B1 (or A)

 

CONFERENCED Caller=C Called=A, Connected=A (or B1)

 

For B1'

 

CONNECTED INACTIVE

 

CONFERENCED Caller=A, Called=B1, Connected=A

 

CONFERENCED Caller=B1 Called=C, Connected=C


Action
Expected Events

A B1 is HOLD,

For A:

B1 issues setup conference

 

C B2 is connected

 
 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = A, Called = B1 Connected B1

 

For B1:

 

Primary call

 

LINE_CALLSTATE

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B1

 

Consult call

 

DIALTONE

 

For B2:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2 , Connected = C

 

For C:

 

LINE_CALLSTATE

 

param1=x100, CONNECTED Caller = C, Called = B2, Connected = B2

 

For B1':

 

LINE_CALLSTATE

 

param1=x100, HOLD Caller = A, Called = B1, Connected = A

Application issues lineDevSpecific(SLDST_JOIN) with the call on B2 as survival call

For A:

 

CONNECTED

 

CONFERENCED Caller=A, Called=B1, Connected=B2

 

CONFERENCED Caller=A Called=C, Connected=C

 

For B1

 

Both calls will go IDLE

 

For B2

 

CONNECTED

 

CONFERENCED Caller=B1, Called=A, Connected=A

 

CONFERENCED Caller=C Called=B1, Connected=C

 

For C

 

CONNECTED

 

CONFERENCED Caller=C, Called=B2, Connected=B2 (or A)

 

CONFERENCED Caller=C Called=A, Connected=A (or B2)

 

For B1'

 

Calls go IDLE


B1 Performs a Join Across Line Where B1 is already in a Conference Created by A

Action
Expected Events

A, B1, C are in a conference created by A

For A:

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="A"

 

Connected

 

Conference - Caller="B1", Called="C", Connected="C"

 

For C:

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

For A:

 

B2 calls D, D answers

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="A"

 

OnHold

 

Conference - Caller="B1", Called="C", Connected="C"

 

For B2:

 

Connected - Caller="B2", Called="D", Connected="D"

 

For C:

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

Connected - Caller="B2", Called="D", Connected="B2"

B1 issues a lineDevSpecific(SLDST_JOIN) to join the calls on B1 and B2.

For A:

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

Conference - Caller="A", Called="D", Connected="D"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Conference - Caller="A", Called="B1", Connected="A"

 

Connected

 

Conference - Caller="B1", Called="C", Connected="C"

 

Conference - Caller="B1", Called="D", Connected="D"

 

For B2:

 

Call will go IDLE

 

For C:

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

Conference - Caller="C", Called="D", Connected="D"

 

For D:

 

Conference - Caller="B1", Called="D", Connected="B1"

 

Connected

 

Conference - Caller="D", Called="A", Connected="A"

 

Conference - Caller="D", Called="C", Connected="C"


B2 Performs a Join Across Line Where B1 is already in a Conference Created by A

Action
Expected Events

A,B1,C are in a conference created by A

For A:

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="A"

 

Connected

 

Conference - Caller="B1", Called="C", Connected="C"

 

For C:

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

B2 calls D, D answers

For A:

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="A"

 

OnHold

 

Conference - Caller="B1", Called="C", Connected="C"

 

For B2:

 

Connected - Caller="B2", Called="D", Connected="D"

 

For C:

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

For D:

 

Connected - Caller="B2", Called="D", Connected="B2"

B2 issues a lineDevSpecific(SLDST_JOIN) to join the calls on B1 and B2.

For A:

 

Conference - Caller="A", Called="B1", Connected="B2"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

Conference - Caller="A", Called="D", Connected="D"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="A"

 

Connected

 

Conference - Caller="B1", Called="C", Connected="C"

 

Conference - Caller="B1", Called="D", Connected="D"

 

For B2:

 

Call will go IDLE

 

For C:

 

Conference - Caller="B2", Called="C", Connected="B2"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

Conference - Caller="C", Called="D", Connected="D"

 

For D:

 

Conference - Caller="B2", Called="D", Connected="B2"

 

Connected

 

Conference - Caller="D", Called="A", Connected="A"

 

Conference - Caller="D", Called="C", Connected="C"


B1 Performs a Join Across Line Where B1 is in One Conference and B2 is in a Separate Conference

Action
Expected Events

A,B1,C are in conference1

For A (GCID-1):

D, B2, E are in conference2

 
 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

For B1 (GCID-1):

 

Conference - Caller="A", Called="B1", Connected="A"

 

OnHold

 

Conference - Caller="B1", Called="C", Connected="C"

 

For C (GCID-1):

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

For D (GCID-2):

 

Conference - Caller="D", Called="B2", Connected="B2"

 

Connected

 

Conference - Caller="D", Called="E", Connected="E"

 

For B2 (GCID-2):

 

Conference - Caller="D", Called="B2", Connected="D"

 

Connected

 

Conference - Caller="B2", Called="E", Connected="E"

 

For E (GCID-2):

 

Conference - Caller="B2", Called="E", Connected="B2"

 

Connected

 

Conference - Caller="E", Called="D", Connected="D"

B1 issues a lineDevSpecific(SLDST_JOIN) to join the calls on B1 and B2.

For A:

 

Conference - Caller="A", Called="B1", Connected="B1"

 

Connected

 

Conference - Caller="A", Called="C", Connected="C"

 

Conference - Caller="A", Called="CFB-2", Connected=" CFB-2"

 

For B1:

 

Conference - Caller="A", Called="B1", Connected="A"

 

Connected

 

Conference - Caller="B1", Called="C", Connected="C"

 

Conference - Caller="B1", Called=" CFB-2", Connected=" CFB-2"

 

For B2:

 

Call will go IDLE

 

For C:

 

Conference - Caller="B1", Called="C", Connected="B1"

 

Connected

 

Conference - Caller="C", Called="A", Connected="A"

 

Conference - Caller="C", Called=" CFB-2", Connected=" CFB-2"

 

For D:

 

Connected

 

Conference - Caller="D", Called="E", Connected="E"

 

conference - Caller="D", Called=" CFB-1", Connected=" CFB-1"

 

For E:

 

Connected

 

Conference - Caller="E", Called="D", Connected="D"

 

Conference - Caller="E", Called=" CFB-1", Connected=" CFB-1"


IPv6 Use Cases

The use cases related to IPv6 are provided below:

Register CTI Port with IPv4 when Unified CM is IPv6 Disabled and Common Device Configuration is IPv4 .

Steps
Expected Result

1. Enterprise parameter for IPv6 is disabled. IP addressing mode for CTI Port = IPv4 only on common device config page.

2. Open provider and do a LineNegotiateExtensionVersion with the higher bit set on both dwExtLowVersion and dwExtHighVersion

3. Application does a LineOpen with new Ext ver. The lineopen will be delayed till user specifies the Addressing mode

4. Application uses CCiscoLineDevSpecificSetIPAddressMode to set the addressing mode as IPv4. Application uses CciscoLineDevSpecificSendLineOpen to trigger Lineopen.

Application is able to register CTI Port with IPv4 address.


Register CTI Port with IPv6 when Unified CM is IPv6 Disabled and Common Device Configuration is IPv6.

Steps
Expected Result

1. Enterprise parameter for IPv6 is disabled. IP addressing mode for CTI Port = IPv6 only on common device config page.

2. Open provider and do a LineNegotiateExtensionVersion with the higher bit set on both dwExtLowVersion and dwExtHighVersion

3. Application does a LineOpen with new Ext ver. The lineopen will be delayed till user specifies the Addressing mode

4. Application uses CCiscoLineDevSpecificSetIPAddressMode to set the addressing mode as IPv6. Application uses CciscoLineDevSpecificSendLineOpen to trigger Lineopen.

Application is not able to register CTI Port. TSP returns error LINEERR_OPERATIONUNAVAIL


Register CTI Port with IPv6 when Unified CM is IPv6 Disabled and Common Device Configuration is IPv4_v6.

Steps
Expected Result

1. Enterprise parameter for IPv6 is disabled. IP addressing mode for CTI Port = IPv4_v6 on common device config page.

2. Open provider and do a LineNegotiateExtensionVersion with the higher bit set on both dwExtLowVersion and dwExtHighVersion

3. Application does a LineOpen with new Ext ver. The lineopen will be delayed till user specifies the Addressing mode

4. Application uses CCiscoLineDevSpecificSetIPAddressMode to set the addressing mode as IPv6. Application uses CciscoLineDevSpecificSendLineOpen to trigger Lineopen.

Application is not able to register CTI Port. TSP returns error LINEERR_OPERATIONUNAVAIL


IPv6 Phone A calls IPv6 Phone B

Steps
Expected Result

1. Enterprise parameter for IPv6 is enabled.

2. Open two lines A and B

3. Phone A which is IPv6 calls Phone B which is IPv6

4. Events at Phone B

5. While Media is established:

Events on phone A

Event on phone B

FireCallState = Offering, Do a GetlineCallInfo.

LineCallInfo contains the following in devspecific part,

FarEndIPAddress: Blank

FarEndIPAddressIpv6: IPv6 address of A

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of B.

ReceptionRTPDestinationAddress = IPv6 address of A.

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of A.

ReceptionRTPDestinationAddress = IPv6 address of B.


IPv4_v6 Phone calls IPv6 Phone.

Steps
Expected Result

1. Enterprise parameter for IPv6 is enabled.

2. Open two lines A and B

3. Phone A which is IPv4_v6 calls Phone B which is IPv6

4. Events at Phone B

5. While Media is established:

Events on phone A

Event on phone B

FireCallState = Offering, Do a GetlineCallInfo.

LineCallInfo contains the following in devspecific part,

FarEndIPAddress: IPv4 address of A

FarEndIPAddressIpv6: IPv6 address of A

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of B.

ReceptionRTPDestinationAddress = IPv6 address of A.

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of A.

ReceptionRTPDestinationAddress = IPv6 address of B.


IPv4 Phone Calls IPv6 Phone.

Steps
Expected Result

1. Enterprise parameter for IPv6 is enabled.

2. Open two lines A and B

3. Phone A which is IPv4 calls Phone B which is IPv6

4. Events at Phone B

5. While Media is established:

Events on phone A

Event on phone B

FireCallState = Offering, Do a GetlineCallInfo.

LineCallInfo contains the following in devspecific part,

FarEndIPAddress: IPv4 address of A

FarEndIPAddressIpv6:

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv4 address of MTP Resource.

ReceptionRTPDestinationAddress = IPv4 address of A.

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of MTP Resource.

ReceptionRTPDestinationAddress = IPv6 address of B.


IPv6 Phone Calls IPv4 Phone.

Steps
Expected Result

1. Enterprise parameter for IPv6 is enabled.

2. Open two lines A and B

3. Phone A which is IPv6 only calls Phone B which is IPv4

4. Events at Phone B

5. While Media is established:

Events on phone A

Event on phone B

FireCallState = Offering, Do a GetlineCallInfo.

LineCallInfo contains the following in devspecific part,

FarEndIPAddress:

FarEndIPAddressIpv6: IPv6 address of A

Do a GetLinecallInfo,

LineCallInfo will contain the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of MTP Resource.

ReceptionRTPDestinationAddress = IPv6 address of A.

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv4 address of MTP Resource.

ReceptionRTPDestinationAddress = IPv4 address of B.


IPv6 Phone Calls IPv4_v6 Phone.

Steps
Expected Result

1. Enterprise parameter for IPv6 is enabled.

2. Phone A which is IPv6 only calls Phone B which is IPv4_v6 only.

3. Open lines A and B

4. Events at Phone B

5. While Media is established:

Events on phone A

Event on phone B

Existing Call, Do a GetlineCallInfo.

LineCallInfo contains the following in devspecific part,

FarEndIPAddress:

FarEndIPAddressIpv6: IPv6 address of A

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of MTP Resource.

ReceptionRTPDestinationAddress = IPv6 address of A.

Do a GetLinecallInfo,

LineCallInfo contains the following in devspecific part,

TransmissionRTPDestinationAddress = IPv6 address of Phone A.

ReceptionRTPDestinationAddress = IPv6 address of B.


Common Device C onfiguration Device Mode Changes from IPv4_v6 to IPv4.

Steps
Expected Result

User changes the device configuration on common device configuration from IPv4_v6 to IPv4 only

Application receives LineDevSpecific for the opened CTI Ports/RP in the device config indicating that Addressing mode has changed. All lines registered as IPv6 get a LINE_CLOSE Event. Application can then re-register these lines later.


Common Device Configuration Device Mode Changes from IPv4 to IPv6 .

Steps
Expected Result

User changes the device configuration on common device configuration from IPv4 only to IPv6 only

Application receives LineDevSpecific for the opened CTI Ports/RP in the device config indicating that Addressing mode has changed. All lines registered as IPv4 get a LINE_CLOSE Event. Application can then re-register these lines later.


Direct Transfer Across Lines

Use cases related to Direct Transfer Across Lines feature are mentioned below:


Note The device mentioned in the use cases also apply to SCCP device and SIP TNP phones when Direct Transfer is issued from application.


Direct Transfer across Lines on RoundTable Phones via Application

Device A, B, and C where B is roundtable phone and has line B1 and B2 configured.

Action
Expected Events

A B1 is connected,

C B2 is on hold

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1 Connected B1

For B1:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1, Connected = A

For B2:

LINE_CALLSTATE

param1=x100, HOLD

Caller = C, Called = B2 , Connected = C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = C, Called = B2, Connected = B2

Application sends CciscoLineDevSpecificDirectTransfer on B1 with B2 as consult call

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1 Connected C

For B1:

Call goes IDLE

For B2:

Call goes IDLE

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = C, Called = B2, Connected = A


Direct Transfer on Same Line on RoundTable Phones via Application

Device A, B, C where B is roundtable phone .

Action
Expected Events

A B (c1) is connected,

C B (c2) is on hold

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

For B:

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

Call-2

LINE_CALLSTATE

param1=x100, HOLD

Caller = C, Called = B, Connected = C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = C, Called = B, Connected = B

Application sends CciscoLineDevSpecificDirectTransfer on B (c1) with c2 as consult call

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected C

For B:

Call-1 and Call-2 will go IDLE

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = C, Called = B, Connected = A


Direct Transfer Across Lines on RoundTable Phones via Application with call in Offering State

Device A, B, C where B is roundtable phone and has line B1 and B2 configured .

Action
Expected Events

A (c1) B1(c2) is on hold,

B2 (c3) C (c4) is ringing

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1 Connected B1

For B1:

LINE_CALLSTATE

param1=x100, HOLD

Caller = A, Called = B1, Connected = A

For B2:

LINE_CALLSTATE

param1=x100, RINGBACK

Caller = B2, Called = C

For C:

LINE_CALLSTATE

param1=x100, OFFERING

Caller = B2, Called = C

Application sends CciscoLineDevSpecificDirectTransfer on B1 (c2) with B2 (c3) as consult call

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected C

For B1:

Call goES IDLE

For B2:

Call goes IDLE

For C:

LINE_CALLSTATE

param1=x100, OFFERING

Caller = C, Called = B,


Failure of Direct Transfer Calls Across Lines

Device A, B, C where B is roundtable phone and has line B1 and B2 configured .

Action
Expected Events

A (c1) B1(c2) is on hold,

Initiate new call (c3) on B2

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1 Connected B1

For B1:

LINE_CALLSTATE

param1=x100, HOLD

Caller = A, Called = B1, Connected = A

For B2:

LINE_CALLSTATE

param1=x100, DIALTONE

Application sends CciscoLineDevSpecificDirectTransfer on B1 (c2) with B2 (c3) as consult call

CciscoLineDevSpecificDirectTransfer gets error as LINEERR_INVALCALLSTATE.


Direct Transfer Calls Across Lines in Conference Scenario

Device A, B, C, D and E where C is roundtable phone and has line C1 and C2 configured .

Action
Expected Events

A/B/C1 in conference, B is controller, call on C1 is in hold state.

C2 /D/E in conference, D is controller, call on C2 is in connect state.

For A:

CONNECTED

CONFERENCED

Caller = A, called = B, connected = B

CONFERENCED

Caller = A, called = C1, connected = C1

For B:

CONNECTED

CONFERENCED

Caller = A, called = B, connected = B

CONFERENCED

Caller = B, called = C1, connected = C1

For C1:

ONHOLD

CONFERENCED

Caller = B, called = C1, connected = B

CONFERENCED

Caller = C1, called = A, connected = A

For C2:

CONNECTED

CONFERENCED

Caller = C2, called = D, connected = D

CONFERENCED

Caller = C2, called = E, connected = E

For D:

CONNECTED

CONFERENCED

Caller = D, called = C1, connected = C1

CONFERENCED

Caller = D, called = E, connected = E

 

For E:

CONNECTED

CONFERENCED

Caller = D, called = E, connected = D

CONFERENCED

Caller = E, called = C2, connected = C2

Application sends CciscoLineDevSpecificDirectTransfer on C1 with C2-call as consult call

CciscoLineDevSpecificDirectTransfer will succeed.

For A:

CONNECTED

CONFERENCED

Caller = A, called = B, connected = B

CONFERENCED

Caller = A, called = CB-2, connected = CB-2

For B:

CONNECTED

CONFERENCED

Caller = A, called = B, connected = B

CONFERENCED

Caller = B, called = CB-2, connected = CB-2

For C1:

IDLE

For C2:

IDLE

For D:

CONNECTED

CONFERENCED

Caller = D, called = CB-1, connected = CB-1

CONFERENCED

Caller = D, called = E, connected = E

For E:

CONNECTED

CONFERENCED

Caller = D, called = E, connected = D

CONFERENCED

Caller = E, called = CB-1, connected = CB-1


Connect Transfer Across Lines on RoundTable Phones

Device A, B, C where B is roundtable phone and has line B1 and B2 configured .

Action
Expected Events

A B1 is connected,

C B2 is on hold

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1 Connected B1

For B1:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1, Connected = A

For B2:

LINE_CALLSTATE

param1=x100, HOLD

Caller = C, Called = B2, Connected = C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = C, Called = B2, Connected = B2

User performs connect transfer on B.

For A:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B1 Connected C

For B1:

Call goes IDLE

For B2:

Call goes IDLE

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = C, Called = B2, Connected = A


Swap or Cancel Support

Use cases related to Swap or Cancel feature are mentioned below:

Connected Transfer

Device A, B, C where A is a Cisco Unified IP Phone (future version)..

Action
Expected Events

A C is on hold

A B is connected,

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A press transfer

For A:

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = B Connected B

Call-3 DIALTONE

A picks "Active Calls"

Call-3 goes IDLE

A picks call (AC) and presses transfer to complete transfer

For A:

Both calls go IDLE

For B1:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = B


Connected Transfer on Phones with Shared Lines

Device A, B, C, A' where A and A' are sharedline .

Action
Expected Events

A C is on hold

A B is connected,

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

For A':

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED_INACTIVE

Caller = A, Called = B Connected B

User performs connected transfer on Cisco Unified IP phone (future version)

For A and A':

All calls go IDLE

For B1:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = B


Connected Transfer: Initiate from Phone, Complete from CTI

Device A, B, C .

Action
Expected Events

A C is on hold

A B is connected,

For A:

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

Application sends either CompleteTransfer or DirectTransfer on A

For A and A':

All calls go IDLE

For B1:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = B


Consult Transfer: Resume Primary Call (Implicit Cancel).

Action
Expected Events

A B

A setup consult transfers to C

And C answer

For A:

Call-1

LINE_CALLSTATE

param1=x100, ONHOLDPENDINGTRANSFER

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A press resume to resume A B call

For A:

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A


Consult Transfer: Swap Calls.

Action
Expected Events

A B

A setup consult transfer to C

And C answer

For A:

Call-1

LINE_CALLSTATE

param1=x100, ONHOLDPENDINGTRANSFER

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A press Swap

For A:

The scenario will look exactly the same when resume primary call.

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

 

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A press "Transfer" to complete transfer

For A:

Calls go IDLE

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = C

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = B


Consult Transfer on Phone: Swap Calls; CTI sends SetupTransfer on Connected Call

Action
Expected Events

A B

A setup consult transfer to C

And C answer

For A:

Call-1

LINE_CALLSTATE

param1=x100, ONHOLDPENDINGTRANSFER

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A press Swap

For A:

The scenario will look exactly the same when resume primary call.

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

Application calls LineSetupTransfer on A's connected call (AB) to initiate transfer

Request succeeds as phone cancels existing feature plan and allow CTI request to go through.


Consult Transfer: Swap and Cancel

Action
Expected Events

A B

A setup consult transfer to C

And C answer

For A:

Call-1

LINE_CALLSTATE

param1=x100, ONHOLDPENDINGTRANSFER

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A press Swap

For A:

The scenario will look exactly the same when resume primary call.

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A presses Cancel

No TSP event since it is handled during swap operation


RoundTable Connected Conference.

Action
Expected Events

A B

A puts call on hold

A creates new call to C, C answer

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A presses "Conference"

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, ONHOLDPENDINGCONFENRENCE

Caller = A, Called = C Connected C

Call-3

DIALTONE

A picks active call (A C) on phone UI, and presses "Conference" to complete the conference

For A:

CONNECTED

CONFERENCED

Caller=A, called = B, connected = B

CONFERENCED

Caller = A, called = C, connected = C

Call-3

IDLE

For B:

For A:

CONNECTED

CONFERENCED

Caller=A, called = B, connected = B

CONFERENCED

Caller = B, called = C, connected = C

For C:

For A:

CONNECTED

CONFERENCED

Caller=A, called = C, connected = C

CONFERENCED

Caller = C, called = B, connected = B


RoundTable Connected Conference: Cancel.

Action
Expected Events

A B

A puts call on hold

A creates new call to C, C answers

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A presses "Conference"

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, CONFERENCED

Caller = A, Called = C Connected C

Call-3

LINE_CALLSTATE

param1=x100, ONHOLDPENDINGCONFENRENCE

Caller = A, Called = C Connected C

Call-4

DIALTONE

A picks "Active Calls"

For A:

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

Call-3 / Call-4

IDLE

A presses Cancel softkey

For A:

Call-1

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A


Set Up Consult Conference from RT, then Swap and Complete Conference from RT.

Action
Expected Events

A B

A sets up conference to C, C answer

For A:

ONHOLDPENDINGCONF

CONFERENCED

Caller = A, called = B, connected = B

CONNECTED

Caller = A, called = C, connected = C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A presses "Swap"

For A:

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x100, HOLD

Caller = A, Called = C Connected C

A presses "Conference" to complete conference

For A:

CONNECTED

CONFERENCED

Caller=A, called = B, connected = B

CONFERENCED

Caller = A, called = C, connected = C

For B:

CONNECTED

CONFERENCED

Caller=A, called = B, connected = B

CONFERENCED

Caller = B, called = C, connected = C

For C:

For A:

CONNECTED

CONFERENCED

Caller=A, called = C, connected = C

CONFERENCED

Caller = C, called = B, connected = B


Set Up Consult Conference from RT, then Swap and Cancel from Phone with Shared Line Scenario

A and A' are shared lines..

Action
Expected Events

A B

A sets up conference to C, C answers

For A:

ONHOLDPENDINGCONF

CONFERENCED

Caller = A, called = B, connected = B

CONNECTED

Caller = A, called = C, connected = C

For A'

CONNECTED INACTIVE

Caller = A, celled = B, connected = B

CONNECTED INACTIVE

Caller = A, celled = C, connected = C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A presses "Swap"

For A:

The scenario looks the same when primary call resumes

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

A presses "Cancel"

For A:

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected = C

For A'

Call-1

LINE_CALLSTATE

CONNECTED INACTIVE

Caller = A, Called = B Connected = B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected = C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A


Set Up Consult Conference from RT: Resume Primary Call (Implicit Cancel).

Action
Expected Events

A B

A sets up conference to C, C answer

For A:

ONHOLDPENDINGCONF

CONFERENCED

Caller = A, called = B, connected = B

CONNECTED

Caller = A, called = C, connected = C

For A'

CONNECTED INACTIVE

Caller = A, celled = B, connected = B

CONNECTED INACTIVE

Caller = A, celled = C, connected = C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A

A resumes AB call

For A:

Call-1

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B Connected B

Call-2

LINE_CALLSTATE

param1=x400, HOLD

Caller = A, Called = C Connected C

For B:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = B, Connected = A

For C:

LINE_CALLSTATE

param1=x100, CONNECTED

Caller = A, Called = C, Connected = A


User is Removed from Standard Supports Connected Xfer/Conf Group.

Action
Expected Events

User is in Standard Supports Connected Xfer/Conf group

RT phone A is in user's control list

Application does LineInitialize

RT PHONE/LINE is enumerated to APP

Remove user from "Standard Supports Connected Xfer/Conf" user group

APP receives PHONE_REMOVE / LINE_REMOVE


User is Removed from Standard Supports Connected Xfer/Conf Group.

Action
Expected Events

User is in Standard Supports Connected Xfer/Conf group

RT phone A is in user's control list

Application does LineInitialize

RT PHONE/LINE is enumerated to APP

Remove user from Standard Supports Connected Xfer/Conf user group

APP receives PHONE_REMOVE / LINE_REMOVE


User is Removed from Standard Supports Connected Xfer/Conf Group while Line is Open.

Action
Expected Events

user is in "Standard Supports Connected Xfer/Conf" group

RT phone A is in user's control list

Application does LineInitialize

RT PHONE/LINE is enumerated to APP

App sends LineOpen to open line on Cisco Unified IP phone (future version) phone

Successful

Remove user from Standard Supports Connected Xfer/Conf group

TSP sends LINE_CLOSE

APP receives LINE_REMOVE


User is Added to Standard Supports Connected Xfer/Conf Group.

Action
Expected Events

user is not in "Standard Supports Connected Xfer/Conf" group

RT phone A is in user's control list

Application does LineInitialize

RT PHONE/LINE is not enumerated to APP

Add user to Standard Supports Connected Xfer/Conf group

APP receives PHONE_CREATE / LINE_CREATE


Drop Any Party

Use cases related to Drop Any Party feature are mentioned below:

Conference: Unified CM Service Parameter Advanced Ad Hoc Conference Enabled = False.

Action
Expected Events

A,B,C and D are in conference; B is conference Controller.

Conference Model:

Each line in conference will be having 4 callLegs, 3 conferenced and 1 connected

CallLegs on A:

Connected - to Conference Bridge

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - C)

Conferenced - (Connected Id - D)

CallLegs on B:

Connected - to Conference Bridge

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - C)

Conferenced - (Connected Id - D)

CallLegs on C:

Connected - to Conference Bridge

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - D)

CallLegs on D:

Connected - to Conference Bridge

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - C)

Application does a LineOpen (B) with new Ext ver.

 

1. Application does LineRemoveFromConference on the `Conferenced' callLeg on B which is connected to A.

A is dropped out of conference.

CallLegs after the Party is dropped from Conference:

Each line in conference will be having 4 callLegs, 2 Conferenced,1 IDLE and 1 connected

CallLegs on A:

All 4 CallLegs will be in IDLE state

CallLegs on B:

Connected - to Conference Bridge

Conferenced - (Connected Id - C)

Conferenced - (Connected Id - D)

IDLE - ( on the conferenced callLeg which was connected to A)

CallLegs on C:

Connected - to Conference Bridge

IDLE - ( on the conferenced callLeg which was connected to A)

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - D)

CallLegs on D:

Connected - to Conference Bridge

IDLE - ( on the conferenced callLeg which was connected to A)

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - C)

Note All IDLE CallLegs will have CallStateChange Reason as CtiDropConferee.

Application does a LineOpen (A) with new Ext ver.

 

2. Application does LineRemoveFromConference on the `Conferenced' callLeg on A which is connected to B.

Error Message LINEERR_OPERATIONUNAVAIL will be sent to application


Conference - Unified CM Service Parameter Advanced Ad Hoc Conference Enabled = True'

Action
Expected Events

A,B,C and D are in conference; B is conference Controller.

Conference Model:

Each line in conference will be having 4 callLegs, 3 conferenced and 1 connected

CallLegs on A:

Connected - to Conference Bridge

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - C)

Conferenced - (Connected Id - D)

CallLegs on B:

Connected - to Conference Bridge

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - C)

Conferenced - (Connected Id - D)

CallLegs on C:

Connected - to Conference Bridge

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - D)

CallLegs on D:

Connected - to Conference Bridge

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - B)

Conferenced - (Connected Id - C)

Application does a LineOpen (A) with new Ext ver.

Application does LineRemoveFromConference on the `Conferenced' callLeg on A which is connected to B.

 

1. Drop Ad Hoc Conference = Never

B is dropped out of conference.

CallLegs after the Party is dropped from Conference:

Each line in conference will be having 4 callLegs, 2 Conferenced,1 IDLE and 1 connected

CallLegs on B:

All 4 CallLegs will be in IDLE state

CallLegs on A:

Connected - to Conference Bridge

Conferenced - (Connected Id - C)

Conferenced - (Connected Id - D)

IDLE - ( on the conferenced callLeg which was connected to B)

CallLegs on C:

Connected - to Conference Bridge

IDLE - ( on the conferenced callLeg which was connected to B)

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - D)

CallLegs on D:

Connected - to Conference Bridge

IDLE - ( on the conferenced callLeg which was connected to B)

Conferenced - (Connected Id - A)

Conferenced - (Connected Id - C)

Note All IDLE CallLegs will have CallStateChange Reason as CtiDropConferee.

2. Drop Ad Hoc Conference = `When Conference Controller Leaves'

B is dropped out of conference and Conference will be ended.

CallLegs after the Party is dropped from Conference:

Each line in conference will be having 4 callLegs, all in IDLE state

CallLegs on A,B,C and D:

All 4 CallLegs will be in IDLE state


Shared Line-Scenario

Action
Expected Events

A,B,C and A' are in conference; A is conference Controller

Unified CM Parameter "Drop Ad Hoc Conference = Never"

Conference Model:

Lines B and C in conference will be having 4 callLegs, 3 conferenced and 1 connected

Lines A and A' will be having 8 CallLegs

CallLegs on A:

Connected - to Conference Bridge (Active)

Conferenced - (caller Id - A ;Called Id - B; Connected Id - B) (Active)

Conferenced - (caller Id - A ;Called Id - C; Connected Id - C) (Active)

Conferenced - (caller Id - A ;Called Id - A' ; Connected Id - A') (Active)

Connected - to Conference Bridge (Remote in Use)

Conferenced - (caller Id - A' ;Called Id - B; Connected Id - B) (Remote in Use)

Conferenced - (caller Id - A' ;Called Id - C; Connected Id - C) (Remote in Use)

Conferenced - (caller Id - A' ;Called Id - A; Connected Id - A) (Remote in Use)

CallLegs on A':

Connected - to Conference Bridge (Active)

Conferenced - (caller Id - A' ;Called Id - B; Connected Id - B) (Active)

Conferenced - (caller Id - A' ;Called Id - C; Connected Id - C) (Active)

Conferenced - (caller Id - A' ;Called Id - A; Connected Id - A) (Active)

Connected - to Conference Bridge (Remote in Use)

Conferenced - (caller Id - A ;Called Id - B; Connected Id - B) (Remote in Use)

Conferenced - (caller Id - A ;Called Id - C; Connected Id - C) (Remote in Use)

Conferenced - (caller Id - A ;Called Id - A'; Connected Id - A') (Remote in Use)

 

CallLegs on B:

Connected - to Conference Bridge

Conferenced - (caller Id - B ;Called Id - A; Connected Id - A)

Conferenced - (caller Id - B ;Called Id - C; Connected Id - C)

Conferenced - (caller Id - B ;Called Id - A'; Connected Id - A')

CallLegs on C:

Connected - to Conference Bridge

Conferenced - (caller Id - C ;Called Id - A; Connected Id - A)

Conferenced - (caller Id - C ;Called Id - B; Connected Id - B)

Conferenced - (caller Id - C ;Called Id - A' ; Connected Id - A')

Application does a LineOpen (A) with new Ext ver.

Unified CM Parameter `Advanced Ad Hoc Conference Enabled = False'

 

1. Application does LineRemoveFromConference on the `Conferenced' CallLeg on A which is connected to B and mode is "Inactive or Remote In use".

Error LINEERR_INVALCALLSTATE is sent to application.

2. Application does LineRemoveFromConference on the `Conferenced' CallLeg on A which is connected to B and mode is `Active'.

B will be dropped out of conference.

LINECALLSTATE Event will be sent to Application with state = Idle.

CallLegs after the Party is dropped from Conference:

CallLegs on A:

Connected - to Conference Bridge (Active)

IDLE - (on the conferenced callLeg which was connected to A - B)

Conferenced - (caller Id - A ;Called Id - C; Connected Id - C) (Active)

Conferenced - (caller Id - A ;Called Id - A'; Connected Id - A') (Active)

Connected - to Conference Bridge (Remote in Use)

IDLE - (on the conferenced callLeg which was connected to A' - B)

Conferenced - (caller Id - A' ;Called Id - C; Connected Id - C) (Remote in Use)

Conferenced - (caller Id - A' ;Called Id - A; Connected Id - A) (Remote in Use)

CallLegs on A':

Connected - to Conference Bridge (Active)

IDLE - (on the conferenced callLeg which was connected to A' - B)

Conferenced - (caller Id - A' ;Called Id - C; Connected Id - C) (Active)

Conferenced - (caller Id - A' ;Called Id - A; Connected Id - A) (Active)

Connected - to Conference Bridge (Remote in Use)

IDLE - (on the conferenced callLeg which was connected to A - B)

Conferenced - (caller Id - A ;Called Id - C; Connected Id - C) (Remote in Use)

Conferenced - (caller Id - A ;Called Id - A'; Connected Id - A') (Remote in Use)

CallLegs on B:

All 4 CallLegs are in IDLE state

 

CallLegs on C:

Connected - to Conference Bridge

Conferenced - (caller Id - C ;Called Id - A; Connected Id - A)

IDLE - (on the conferenced callLeg which was connected to C - B)

Conferenced - (caller Id - C ;Called Id - A'; Connected Id - A')

Application does a LineOpen (B) with new Ext ver. Unified CM Parameter Advanced Ad Hoc Conference Enabled = True

 

3. Application does LineRemoveFromConference on the `Conferenced' CallLeg on B which is connected to A and mode is "Active".

A will be dropped out of conference.

LINECALLSTATE Event will be sent to Application with state = Idle.

CallLegs after the Party is dropped from Conference:

CallLegs on A:

IDLE - (on the Connected callLeg which was connected to Conference Bridge,A- CFB)

IDLE - (on the conferenced callLeg which is connected to A - B)

IDLE - (on the conferenced callLeg which is connected to A - C)

IDLE -(on the conferenced callLeg which is connected to A - A')

Connected - to Conference Bridge (Remote in Use)

Conferenced - (caller Id - A' ;Called Id - C; Connected Id - C) (Remote in Use)

Conferenced - (caller Id - A' ;Called Id - B; Connected Id - B) (Remote in Use)

CallLegs on A':

IDLE - (on the Connected callLeg which was connected to Conference Bridge,A - CFB)

IDLE - (on the conferenced callLeg which is connected to A - B)

IDLE - (on the conferenced callLeg which is connected to A - C)

IDLE -(on the conferenced callLeg which is connected to A - A')

Connected - to Conference Bridge

Conferenced - (caller Id - A' ;Called Id - C; Connected Id - C) (Active)

Conferenced - (caller Id - A' ;Called Id - B; Connected Id - B) (Active)

CallLegs on B:

Connected - to Conference Bridge

Conferenced - (caller Id - B ;Called Id - A; Connected Id - A')

IDLE - (on the conferenced callLeg which was connected to B - A)

Conferenced - (caller Id - B ;Called Id - C; Connected Id - C)

 

CallLegs on C:

Connected - to Conference Bridge

Conferenced - (caller Id - C ;Called Id - A'; Connected Id - A')

IDLE - (on the conferenced callLeg which was connected to C - A)

Conferenced - (caller Id - C ;Called Id - B; Connected Id - B)


Chained Conference.

Action
Expected Events

A,B and CB2 are in conference(CB1); B is conference Controller

C,D and E are in Conference (CB2); D is conference Controller

Unified CM Parameter Advanced Ad Hoc Conference Enabled = True

Application does a LineOpen (A) with new Ext ver.

1. Application does LineRemoveFromConference on the Conferenced" CallLeg on A which is connected to B.

B is disconnected and dropped out of Conference.

A is now in conference with CB2.

LINECALLSTATE Event is sent to Application for Line B with state = Idle.


C-Barge: Unified CM Service Parameter Advanced Ad Hoc Conference Enabled = True.

Action
Expected Events

B call A and A';

A answers the call and on A' do c-Barge;

A,B and A' will be in conference; A is conference Controller

Unified CM Parameter "Drop Ad Hoc Conference = Never"

Application does a LineOpen (A) with new Ext ver.

 

Application does a LineOpen (A) with new Ext ver.

1. Application does LineRemoveFromConference on the "Conferenced" CallLeg on A which is connected to B and mode is Active

B is dropped out of conference.

LINECALLSTATE Event will be sent to Application with state = Idle.

CallLegs after the Party is dropped from Conference:

CallLegs on A:

Connected - (on the conferenced callLeg which was connected to A - A') (Active)

Connected - on the conferenced callLeg which was connected to A' - A) (Remote in Use)

IDLE - (on the conferenced callLeg which was connected to A - B)

IDLE - (on the connected callLeg which is connected to conference Bridge; A - CFB)

IDLE - (on the conferenced callLeg which was connected to A' - B)

IDLE - (on the connected callLeg which is connected to conference Bridge; A' - CFB)

CallLegs on A':

Connected - (on the conferenced callLeg which was connected to A' - A) (Active)

Connected - on the conferenced callLeg which was connected to A - A') (Remote in Use)

IDLE - (on the conferenced callLeg which was connected to A - B)

IDLE - (on the connected callLeg which is connected to conference Bridge; A - CFB)

IDLE - (on the conferenced callLeg which was connected to A' - B)

IDLE - (on the connected callLeg which is connected to conference Bridge; A' - CFB)

CallLegs on B:

All 4 CallLegs are in IDLE state

A' is dropped out of conference.

LINECALLSTATE Event will be sent to Application with state = Idle.

2. Application does LineRemoveFromConference on the Conferenced CallLeg on A which is connected to A' and mode is Active.

CallLegs after the Party is dropped from Conference:

CallLegs on A:

Connected -(on the conferenced callLeg which was connected to A - B) (Active)

IDLE -(on the conferenced callLeg which was connected to A' - B) (Remote in Use)

IDLE - (on the conferenced callLeg which was connected to A - A') (active)

IDLE - (on the connected callLeg which is connected to conference Bridge; A - CFB)

IDLE - (on the conferenced callLeg which was connected to A' - A) (Remote in Use)

IDLE - (on the connected callLeg which is connected to conference Bridge; A' - CFB)

CallLegs on A':

Connected -(on the conferenced callLeg which was connected to A - B) (Remote in Use)

IDLE -(on the conferenced callLeg which was connected to A' - B)

IDLE - (on the conferenced callLeg which was connected to A - A') (active)

IDLE - (on the connected callLeg which is connected to conference Bridge; A - CFB)

IDLE - (on the conferenced callLeg which was connected to A' - A) (Remote in Use)

IDLE - (on the connected callLeg which is connected to conference Bridge; A' - CFB)

CallLegs on B:

Connected -(on the conferenced callLeg which was connected to B - A)

IDLE -(on the conferenced callLeg which was connected to A' - B)

IDLE - (on the connected callLeg which is connected to conference Bridge; B - CFB)


Park Monitoring

Use cases related to Park Monitoring feature are mentioned below:

Park Monitoring Feature Disabled

Setup:

The Park Monitoring message flag is disabled by default.

Cisco Unified IP Phones (future version) running SIP: A(3000), B(3001)

All lines are monitered by TSP

Action
Expected Events

1. A(3000) calls B(3001)

2. B(3001) receives the call and parks the call

Application will not be notified about the New Parked call through LINE_NEWCALL event as the park Monitoring flag is disabled.


Park Monitoring Feature Enabled

Setup:

Cisco Unified IP Phones (future version) running SIP: A(3000), B(3001),C(3002)

All lines are monitered by TSP

Action
Expected Events

Scenario 1:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) receives the call and parks the call at 5555

Park Status Event on B:

At Step 3:

Application will be notified about the New Parked call through LINE_NEWCALL event

At Step 3:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName : TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 2

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.

Scenario 2:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) receives the call and parks the call at 5555

4. The Park Monitoring Reversion Timer expires while the call is still parked.

Park Status Event on B:

At Step 3:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Reminder.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName : TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 3

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.

Scenario 3:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. The Park Monitoring Forward No Retrieve destination configured on B(3001) as C(3002)

3. A(3000) calls B(3001)

4. B(3001) receives the call and parks the call

5. The Park Monitoring Reversion Timer Expires while the call is still parked.

6. The Park Monitoring Forward No Retrieve timer expires and now the call is forwarded to the Park Monitoring Forward No Retrieve Destination C(3002).

Park Status Event on B:

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 5:

Application will receive the LINE_CALLSTATE event with the Park Status = Reminder.

At Step 6:

Application will receive the LINE_CALLSTATE event with the Park Status = Forwarded

Application will receive the LINE_CALLSTATE event with callstate IDLE.

The reason code CtiReasonforwardedNoRetrieve will be updated in the LINECALLINFO::dwDevSpecificData.ExtendedCallInfo.dwExtendedCallReason = CtiReasonforwardedNoRetrieve.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName : TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 6

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.

Scenario 4:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) receives the call and parks the call

4. A(3000) hangs up the call.

Park Status Event on B:

At Step 3:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Abandoned.

Application will receive the LINE_CALLSTATE event with callstate IDLE.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 4

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.

Scenario 5:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) receives the call and parks the call

4. The Park Monitoring Reversion Timer Expires while the call is still parked.

5. C(3002) retrieves the call

Park Status Event on B:

At Step 3:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Reminder.

At Step 5:

Application will receive the LINE_CALLSTATE event with the Park Status = Retrieved.

Application will receive the LINE_CALLSTATE event with callstate IDLE.

Application does a LineGetCallInfo.

hline: LH = 1

dwCallID: CallID

dwReason: LINECALLREASON_PARKED

dwRedirectingIDName: TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 5

dwCallerID: ParkDN = 5555

dwCallerName: ParkDNPartition = P1

dwcalled: ParkedParty = 3000

dwCalledIDName: ParkedPartyPartition = P1.

Scenario 6:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. The Park Monitoring Forward No retrieve destination not configuered.

3. A(3000) calls B(3001)

4. B(3001) receives the call and parks the call

5. The Park Monitoring Reversion Timer Expires while the call is still parked

6. The Park Monitoring Forward No Retrieve timer expires and the call is forwarded to the Parkers line.

Park Status Event on B

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 5:

Application will receive the LINE_CALLSTATE event with the Park Status = Reminder.

At Step 6:

Application will receive the LINE_CALLSTATE event with the Park Status = Forwarded.

Application will receive the LINE_CALLSTATE event with callstate IDLE.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline: LH = 1

dwCallID: CallID

dwReason: LINECALLREASON_PARKED

dwRedirectingIDName: TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 6

dwCallerID: ParkDN = 5555

dwCallerName: ParkDNPartition = P1

dwcalled: ParkedParty = 3000

dwCalledIDName: ParkedPartyPartition = P1.

Scenario 7:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. The Park Monitoring Forward No retrieve destination configuered as self(Parkers Line)

3. A(3000) calls B(3001)

4. B(3001) receives the call and parks the call

5. The Park Monitoring Reversion Timer Expires while the call is still parked

6. The Park Monitoring Reversion Timer Expires while the call is still parked

7. The Park Monitoring Forward No Retrieve timer expires and the call is forwarded to the Parkers line.

Park Status Event on B

At Step 5:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 6:

Application will receive the LINE_CALLSTATE event with the Park Status = Reminder.

At Step 7:

Application will receive the LINE_CALLSTATE event with the Park Status = Forwarded.

Application will receive the LINE_CALLSTATE event with callstate IDLE.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline: LH = 1

dwCallID: CallID

dwReason: LINECALLREASON_PARKED

dwRedirectingIDName: TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 6

dwCallerID: ParkDN = 5555

dwCallerName: ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.


Parked Call Exists

Setup:

Cisco Unified IP Phones (future version) running SIP: A(3000), B(3001).

B is not monitered by TSP.

Action
Expected Events

Scenario 1:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) receives the call and parks the call

4. Now the Line B(3001) is monitered by TSP

Park Status Event on B:

At Step 4:

Application will be notified about the Parked call through LINE_NEWCALL event.when ever cisco TSP recives the LINE_PARK_STATUS event for already parked call.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 2

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.


Shared Line Scenario

Setup:

A(3000) ,D(3003) are Cisco Unified IP Phones (future version) running SIP

B(3001) and B'(3001) are shared lines for Cisco Unified IP Phones (future version) running SIP

C(3002) and C'(3002) are shared lines where C is a Cisco Unified IP Phone (future version) running SIP and C' is a Cisco Unified IP Phone 7900 Series running SIP .

For the shared lines the events will be delivered to the phone which parks the call .Events will not be delivered to the other phone though the line is shared.

Action
Expected Events

Scenario 1:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) and B'(3001) starts ringing. B(3001) receives the call and parks the call

4. Park Monitoring reversion timer expires while the call is still parked.

5. D(3003) retrieves the call

Park Status Event on B:

At Step 3:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Reminder.

At Step 5:

Application will receive the LINE_CALLSTATE event with the Park Status = Retrieved

Application will receive the LINE_CALLSTATE event with callstate IDLE.

Application does a LineGetCallInfo.

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName :TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 5

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.

Scenario 2:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. The Park Monitoring Forward No retrieve destination configuered as B(3001)

3. A(3000) calls B(3001)

4. B(3001) and B'(3001) starts ringing. B(3001)receives the call and parks the call

5. The Park Monitoring Reversion Timer Expires while the call is still parked.

6. The Park Monitoring Forward No Retrieve timer expires and call is forwarded to B(3001).Both B(3001) and B'(3001) starts ringing as they are shared lines.

Park Status Event will be sent only to B not B'.

At Step 4:

Application will receive the LINE_CALLSTATE event with the Park Status = Parked.

At Step 5:

Application receives the LINE_CALLSTATE event with the Park Status = Reminder.

At Step 6:

Application receives the LINE_CALLSTATE event with the Park Status = Forwarded.

Application receive the LINE_CALLSTATE event with callstate IDLE.

Application does a LineGetCallInfo.

LineCallInfo contains the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName : TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 6

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.

Scenario 3:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls C(3002)

3. C(3002) and C'(3002) starts ringing. C'(3002) receives the call and parks the call

4. D(3003) retrieves the call

Park Status Event on C'.

At Step 3:

Application is notified about the New Parked call through LINE_NEWCALL event as the call is parked by the Normal TNP phone.


Park Monitoring Feature Disabled

Setup:

The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for line B(3001).

A(3000), D(3003) is a Cisco Unified IP Phones (future version)

Application invokes the Line_open () API on provider to monitor ParkDN

.

Action
Expected Events

Scenario 1:

1. The Park Monitoring message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line B(3001).

2. A(3000) calls B(3001)

3. B(3001) receives the call and parks the call

4. The Park Monitoring Reversion Timer Expires while the call is still parked.

Park Status Event on B:

At Step 3:

Application receives the LINE_NEW_CALL event for PARKDN.

At Step 3:

Application receives the LINE_PARK_STATUS event with the Park Status = Parked.

At Step 4:

Application will receive the LINE_CALL_STATE event with the Park Status = Reminder.

Application does a LineGetCallInfo.

LineCallInfo will contain the following:

hline : LH = 1

dwCallID : CallID

dwReason :LINECALLREASON_PARKED

dwRedirectingIDName :TransactionIDID = Sub1.

dwBearerMode: ParkStatus = 3

dwCallerID : ParkDN = 5555

dwCallerName : ParkDNPartition = P1

dwcalled : ParkedParty = 3000

dwCalledIDName : ParkedPartyPartition = P1.


Logical Partitioning Support

Use cases related to Logical Partitioning feature are mentioned below:

Basic Call Scenario

Basic Call Scenario ; Logical partitioning Enabled = true

Description

Basic Call failure due to Logical partitioning Feature Policy.

Test Setup

A (VOIP) on one Geolocation

A calls B:

LineMakeCall on A

Dails B (DN)

Variant 1: B Geo-Location was not Configured;B(PSTN);Policy Config : Interior to Interior

Variant 2: B (PSTN) on another GeoLocation

Expected Results

Variant 1: Call will be successful; Reason: LP_IGNORE.

Variant 2: A goes to Proceeding State and then On A there will be a DISCONNECTED call state will be sent to application with cause as LINEDISCONNECTMODE_UNKNOWN.


Redirect Scenario

Redirect Scenario ; Logical partitioning Enabled = true

Description

Redirect Call failure due to Logical partitioning Feature Policy.

Test Setup

Two Clusters (Cluster1 and Cluster2) configured with logical partition policy that will restrict the VOIP calls from Cluster1 to PSTN calls on Cluster2. (vice versa PSTN to VIOP)

A on Cluster1 (VOIP)

B on Cluster2 (VOIP)

C on Cluster2 (PSTN)

A calls B

B redirects the call to C

Expected Results

Operation fails with error code LINEERR_OPERATION_FAIL_PARTITIONING_POLICY.

Error code is processed on Cluster2

Variants

For Forward Operation same behaviour will be observed.


Transfer Call Scenario

Transfer Call Scenario ; Logical partitioning Enabled = true

Description

Transfer Call failure due to Logical partitioning Feature Policy.

Test Setup

A (VOIP) in one GeoLocation (GeoLoc 1)

B (VOIP) in another GeoLocation(GeoLoc 2)

C (PSTN)in same GeoLocation as B (GeoLoc 2)

A calls B

SetUpTransfer on B.

On Consult Call at B; Dials C.

Complete Transfer on B.

Expected Results

Operation fails with error code "LINEERR_OPERATIONUNAVAIL".

Variants

For Operation Adhoc Conference same behaviour will be observed.


Join Scenario

Join Scenario; Logical partitioning Enabled = true

Description

Join failure due to Logical partitioning Feature Policy.

Test Setup

A (VOIP) in one GeoLocation (GeoLoc 1)

B (VOIP) in another GeoLocation(GeoLoc 2)

C (VOIP)in same GeoLocation as B (GeoLoc 2)

D (PSTN) in same GeoLocation as B (GeoLoc 2)

B has Three Calls

1. B -> A

2. B -> C

3. B -> D

Variant 1: Join on B with B -> A as Primary Call.

Variant 2: Join on B with B -> D as Primary Call.

Variant 3: Join on B with B -> C as Primary Call.

Expected Results

Variant 1: A, B and C will be in conference.

Variant 2: B, C and D will be in conference.

Variant 3:Either A or D will be in conference with B and C.


Shared Line Scenario

CallPickUp Scenario ; Logical partitioning Enabled = true

Description

CallPickUp Failure due to Logical partitioning Feature Policy.

Test Setup

A (PSTN) on one Geolocation - GeoLoc1

B (VOIP) on one Geolocation - GeoLoc1

C (VOIP) on one Geolocation - GeoLoc2

A Dails B

B Parks the call

C does LineUnPark

Expected Results

Call will be successful on A and A' call will not be present

Variants

Shared line features like barge, cbarge, hold & remote resume should be disabled for calls.


CallPark: Retrieve Scenario

CallPickUp Scenario ; Logical partitioning Enabled = true

Description

CallPickUp Failure due to Logical partitioning Feature Policy.

Test Setup

A (PSTN) on one Geolocation - GeoLoc1

B (VOIP) on one Geolocation - GeoLoc1

C (VOIP) on one Geolocation - GeoLoc2

A Dails B

B Parks the call

C does LineUnPark

Expected Results

CallUpark Will fail with error code "LINEERR_OPERATIONUNAVAIL".


Basic Call Scenario

Basic Call Scenario ; Logical partitioning Enabled = true

Description

Basic Call failure due to Logical partitioning Feature Policy.

Test Setup

A (VOIP) on one Geolocation

A calls B:

LineMakeCall on A

Dails B (DN)

Variant 1: B Geo-Location was not Configured;B(PSTN);Policy Config: Interior to Interior

Variant 2: B (PSTN) on another GeoLocation

Expected Results

Variant 1: Call will be successful; Reason: LP_IGNORE.

Variant 2: A goes to Proceeding State and then On A there will be a DISCONNECTED call state will be sent to application with cause as LINEDISCONNECTMODE_UNKNOWN.


Support for Cisco IP Phone 6900 Series

Use cases related to Cisco Unified IP Phone 6900 Series support feature are mentioned below:

Monitoring Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll over Mode when User is Added to New User Group

Monitoring Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 behavior when User is added to new user Group.

Test Setup

A - Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 Phone with Roll Over Mode

User is added to New User Group.

Application does Line Initialize

Expected Results

Lines on the Cisco Unified IP Phone 7931 will be enumerated.

Application would be able to Open Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 and it would be able to control and perform call operations on Phone.


Monitoring Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

Monitoring Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 behavior when User is added to new user Group.

Test Setup

A - Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

Step 1: Application does Line Initialize

Step 2: User is added to New User Group.

Expected Results

Step 1: Lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 will not be enumerated

Application will not be notified about the device A and it will not be able to monitor.

Step 2: Application will be receiving PHONE_CREATE and LINE_CREATE events for the Device and lines on that Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode.

Now Applications would be able to Monitor and control Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.


Transfer Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

Transfer Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Transfer scenario on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to new user Group.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - "Roll Over to any Line"

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

SetupTransfer on A.

Variants: Application Opens only Line A on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931

Expected Results

Call on A will go to OnHold State.

New call will be created on Line B.

Application then has to complete Transfer using DTAL feature.

Variants: Applications would not be able to Complete Transfer from Application as the Line B is not monitored.


Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is added to New User Group

Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll over Mode when User is added to New User Group

Description

Testing Conference Scenario on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to New User Group.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D are two SCCP phones

Outbound Roll Over Mode - "Roll Over to any Line"

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize

C calls A,A answers

SetupConference on A.

Expected Results

Call on A will go to OnHold State.

New call will be created on Line B.

Application then has to complete Conference using Join Across Lines feature.


Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll over Mode when User is Added to New User Group

Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is added to New User Group

Description

Testing Transfer/Conference Scenario on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - "Roll Over to any Line"

Max Number of Calls: 2

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

SetupTransfer on A.

Expected Results

Call on A will go to OnHoldPendingTransfer/OnHoldPendingConference.

New Consult call will be created on Line A.

Application then has to complete Transfer using CompleteTransfer or DTAL feature.

Variants

Test the same Scenario with Conference

LineCompleteTransfer with Mode as Conference to complete Conference


Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Transfer/Conference Scenario on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 When User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - Roll Over to any Line

Max Number of Calls: 2

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

SetupTransfer on A.

Expected Results

Call on A will go to OnHoldPendingTransfer/OnHoldPendingConference.

New Consult call will be created on Line A.

Application then has to complete Transfer using CompleteTransfer or DTAL feature.

Variants

Test the same Scenario with Conference

LineCompleteTransfer with Mode as Conference to complete Conference


Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Transfer/Conference Scenario on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Lines A and B are configured with Different DN

Outbound Roll Over Mode - Roll Over within same DN

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

SetupTransfer on A.

Expected Results

SetupTransfer Request will fail with error "LINEERR_CALLUNAVAIL".

Variants

Test the same Scenario with SetupConference


Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

Transfer/Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Transfer/Conference Scenario on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Lines A and B are configured with Different DN

Outbound Roll Over Mode - Roll Over within same DN

Max Number of Calls: 2

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

SetupTransfer on A.

Expected Results

Call on A will go to OnHoldPendingTransfer/Conference State.

New Consult call will be created on Line A.

Application then has to complete Transfer using CompleteTransfer or DTAL feature.

Variants

Test the same Scenario with SetupConference


LineMakeCall Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

LineMakeCall Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing LineMakeCall Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Lines A and B are configured with Different DN

Outbound Roll Over Mode - Roll Over within same DN" or "Roll Over to Any Line

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

LineMakeCall on A.

Expected Results

LineMakeCall Operation will fail with error "LINEERR_CALLUNAVAIL".

Roll Over Doesn't Happen to second line as the roll over is only for Outbound Calls.


LineUnPark Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll over Mode when User is Added to New User Group

LineUnPark Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing LineUnPark Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 When User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Lines A and B are configured with Different DN

Outbound Roll Over Mode - Roll Over within same DN" or "Roll Over to Any Line

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

LineUnPark on A.( tires to retrieve the available Parked Call from Park DN)

Expected Results

LineUnPark Operation will fail with error "LINEERR_CALLUNAVAIL".

Roll Over Doesn't Happen to second line as the roll over is only for Outbound Calls.


EM Login/Logout Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

EM Login/Logout Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing EM Log In/Out Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 When User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

EM Profile is logged onto the Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

Test the Use Case from UseCase#1 to UseCase#10

Expected Results

Same as the Use Case tested.


Manual Transfer Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is A dded to New User Group

Manual Transfer Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Existing Call Events on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 when User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - Roll Over to any Line

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

Step 1: From Phone C call A

Step 2: Answer the Call on A

Step 3: Press Transfer Button on Cisco Unified IP Phone 6900 Series and Dial D.

Step 4: Answer the Call on D

Step 5: Complete Transfer from Phone A

Variant: Monitor Phones after Transfer is completed from Phone.

Expected Results

Step 4:

Call on Line A will be in OnHold State.

Call on Line B will be in Connected State.

Note When consult call is created on the same Line; Call will be on ONHOLDPENDINGTRANSFER state.

Step 5:

Both the calls on A and B will go to IDLE state.

C and D will be in Simple Call.

Variant: Same as this Use Case


Manual Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is A dded to New User Group

Manual Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 behavior When User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - "Roll Over to any Line"

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

Step 1: From Phone C call A

Step 2: Answer the Call on A

Step 3: Press conference Button on Cisco Unified IP Phone 6900 Series and Dial D.

Step 4: Answer the Call on D

Step 5: Complete Conference from Phone

Variant: Monitor Phones after Conference is completed from Phone.

Expected Results

Step 4:

Call on Line A will be in OnHold State.

Call on Line B will be in Connected State.

Note When consult call is created on the same Line; Conference Model is created as today on Non-Cisco Unified IP Phone 6900 Series.

Step 5: A ,C and D will be in conference

Conference model will be created on Line A.

Variant: Same as this Use Case.


Manual Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is A dded to New User Group

Manual Conference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 behavior When User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - "Roll Over to any Line"

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

Step 1: From Phone C call A

Step 2: Answer the Call on A

Step 3: Press conference Button on Cisco Unified IP Phone 6900 Series Phone and Dial D.

Step 4: Answer the Call on D

Step 5: Complete Conference from Phone

Variant: Monitor Phones after Conference is completed from Phone.

Expected Results

Step 4:

Call on Line A will be in OnHold State.

Call on Line B will be in Connected State.

Note When consult call is created on the same Line; Conference Model is created as today on Non-Cisco Unified IP Phone 6900 Series Phone.

Step 5: A ,C and D will be in conference

Conference model will be created on Line A.

Variant: Same as this Use Case.


SetupConference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

SetupConference Operation on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 behavior When User is added to New User Group and different Roll Over Mode.

Test Setup

User is added to New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - "Roll Over to any Line"

Max Number of Calls: 1

Busy Trigger : 1

Application does Line Initialize; Application opens all the lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

C calls A,A answers

Step 1: SetupTransfer on A.

Step 2: Complete Conference From Phone.

Expected Results

Step 1:

Call on Line A will be in OnHold State.

Call on Line B will be in Connected State.

Step 5: A ,C and D will be in conference

Conference model will be created on Line A.


BWC on Cisco Unified IP Phone 7931 in Non Roll Over Mode when User is Removed from New User Group

BWC on Cisco Unified IP Phone 7931 in Non Roll Over Mode When User is removed from New User Group

Description

Testing Cisco Unified IP Phone 7931 Phone behavior in Non Roll Over Mode When User is removed from New User Group.

Test Setup

User is Removed from New User Group.

A,B are two lines on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Non-Roll Over Mode

C, D is two SCCP phones.

Outbound Roll Over Mode - "Non Roll Over Mode"

Max Number of Calls: 1

Busy Trigger: 1

Application does Line Initialize

Expected Results

Lines on the Cisco Unified IP Phone 7931 will be enumerated.

Application would be able to Open Cisco Unified IP Phone 7931 with Non-Roll Over Mode and it would be able to control and perform call operations on Phone.


Acquire Device on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode when User is Added to New User Group

Acquire Device on Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode When User is added to New User Group

Description

Testing Behavior of Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 on Super Provider when User is added to new user Group.

Test Setup

A - Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 with Roll Over Mode

User is Added to New User Group.

Step 1: Application does Line Initialize

Step 2: LineDevSpecific to Acquire Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931.

Step 3: User is removed from New User Group.

Expected Results

Step 2: Application will be receiving PHONE_CREATE and LINE_CREATE events for the Device and lines on that Cisco Unified IP Phone 6900 Series/Cisco Unified IP Phone 7931 in Roll Over Mode.

Step 3: Application will be receiving LINE_REMOVE and PHONE_REMOVE for the Cisco Unified IP Phone 7931 and Application will no longer be able to monitor or control that device.