McDewey

Call Initiated From TAPI From Phone A and B on Cluster 1 B Sets Up Conference to Phone C(1000) on Cluster 2 with PSTN Failover Rule Configuration SCCP phone A and B are registered to cluster A Phones A(1900) and B(1901) are associated with the end-user cluster1 SCCP phone C(1000) registered to cluster B Phones C are associated with the end-user cluster2 CUCM learns a pattern 10XX, plus PSTN failover rule as 0:1408972 from SAF network Procedure Application monitors A and B Application sends a lineMakeCall at A to call B Table 56: Call Initiated From TAPI From Phone A and B on Cluster 1, B Sets Up Conference to Phone C(1000) on Cluster 2 with PSTN Failover Rule TAPI messages CTI messages Action A: LINE_APPNEWCALL, LINE_CALLSTATE (LINECALLSTATE_DIALTONE/ LINECALLSTATE_DIALING, LINECALLSTATE_CONNECTED,) CallerID = A / CalledID = B B: LINE_APPNEWCALL, LINE_CALLSTATE (LINECALLSTATE_OFFERING/ LINECALLSTATE_RINGING, LINECALLSTATE_CONNECTED) CallerID = A / CalledID = B A receives NewCallEvent and CallStateChangeEvent (Dialtone/Dialing/Proceeding /ringback/connected) B receives NewCallEvent and CallStateChangeEvent (offering/ringing/ connected) A dials B Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 489 Message Sequence Charts Call Initiated From TAPI From Phone A and B on Cluster 1 B Sets Up Conference to Phone C(1000) on Cluster 2 with PSTN Failover Rule