TAPI messages CTI messages Action A:CPIC event received on party A LineA: LINE_CALLSTATE (LINECALLSTATE_RINGBACK / LINECALLSTATE_CONNECTED) CallReason = LINECALLREASON_DIRECT LINECALLINFO.dwCallID = 0x00400BBA LINECALLINFO.dwOrigin = 0x00000001 LINECALLINFO.dwReason=0x00000001 LINECALLINFO.dwCallerID = 1900(A) LINECALLINFO.dwCallerIDName = LINECALLINFO.dwCalledID = 1000: LINECALLINFO.dwCalledIDName = CCD Pattern LINECALLINFO.dwConnectedID = 1000(B) LINECALLINFO.dwConnectedIDName

LINECALLINFO.dwRedirectionID = 1000 LINECALLINFO.dwRedirectionIDName

LINECALLINFO.dwRedirectingID = 1000 LINECALLINFO.dwRedirectingIDName = CCD Pattern ExtendCallReason = CtiReasonSAF_CCD_PSTNFailover(2B) A receives CPIC and CallStateChangeEvent (Ringback/connected) Provide TSPI_LinegetcallInfo on A connected with B CCD Requesting feature will start PSTN failover by directing this caller to 1000’s PSTN failover number, that is, 14089721000. Call is sent out to a PSTN GW BasicCallInitiatedFromTAPIFromPhoneAonCluster1toPhoneBonCluster2withPSTNFailover Rule Not Set Configuration SCCP phone A are registered to cluster A. Phones A are associated with the end-user “cluster1”. SCCP phone B(1000) registered to cluster B. Phones B are associated with the end-user “cluster2”. CUCM learns a pattern 10XX, plus PSTN failover rule as 0:1408972 from SAF network is not set. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 483 Message Sequence Charts Basic Call Initiated From TAPI From Phone A on Cluster 1 to Phone B on Cluster2 with PSTN Failover Rule Not Set