McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 149

↗ View in doc context
page
149
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::133

When a user transfers or conferences an outbound call, the callType changes to TRANSFER or CONFERENCE. In Unified CCE deployments, the BAStatus of the call remains unchanged. In Unified CCX deployments, the BAStatus changes to TRANSFERRED or CONFERENCED for Progressive and Predictive outbound calls and remains OUTBOUND for Direct Preview outbound calls. When the failover occurs in a Unified CCE deployment, the callType and BAStatus remain unchanged. In Unified CCX deployments, the callType parameter is null or empty after failover for all outbound dialing modes. The BAStatus parameter is removed as the call no longer functions as an outbound call. Note Table 6: Outbound Call Types and BAStatus for Finesse with Unified CCE Direct Preview Preview Predictive Progressive callType: OUTBOUND_ DIRECT_ PREVIEW BAStatus: BLENDED_DIRECT_ PREVIEW_ OUTBOUND_ RESERVATION or DIRECT_ PREVIEW_ OUTBOUND_ RESERVATION callType: OUTBOUND_ PREVIEW BAStatus: BLENDED_PREVIEW_ OUTBOUND_ RESERVATION or PREVIEW_ OUTBOUND_ RESERVATION — — Reservation Call callType: OUTBOUND BAStatus: BLENDED_DIRECT_ PREVIEW_ OUTBOUND or DIRECT_ PREVIEW_ OUTBOUND callType: OUTBOUND BAStatus: BLENDED_PREVIEW_ OUTBOUND or PREVIEW_OUTBOUND callType: OUTBOUND BAStatus: BLENDED_ PREDICTIVE_ OUTBOUND or PREDICTIVE_ OUTBOUND callType: OUTBOUND BAStatus: BLENDED_PROGRESSIVE_ OUTBOUND or PROGRESSIVE_ OUTBOUND Customer Call callType: OUTBOUND_ DIRECT_ PREVIEW BAStatus: DIRECT_ PREVIEW_ OUTBOUND_ RESERVATION callType: OUTBOUND_ CALLBACK_PREVIEW BAStatus: PREVIEW_ OUTBOUND_ RESERVATION — — Callback Reservation Call Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 133 Cisco Finesse Desktop APIs Outbound Call Types and BAStatus

Image 1 from page 149