How does a Cisco TCS process incoming video calls?

When a call arrives at the TCS, it is matched to a Recording Alias that determines how the call is handled; the Recording Alias maps to a Template that defines encoding, layout, and output settings; finally, the Media Server Configuration specified within the Template governs where and how recorded content is stored or streamed. This sequence is the canonical call-handling architecture for TCS as documented by Cisco.

This sequence incorrectly places Media Server Configuration before Template - the Template must be resolved first to define recording settings before the media server configuration can be applied for output.

This option incorrectly inserts H.323 as a distinct named processing stage - H.323 is a signaling protocol used to establish the call connection, not a separate step in the TCS internal workflow.

This option incorrectly introduces 'Workflow' as an explicit intermediate step - the correct TCS processing sequence goes directly from Recording Alias to Template without a separately named workflow stage.