Which three services are supported by CUBE when supporting H323-to-SIP calls? (Choose three)

A.
SIP cause codes

B.
media flow-around

C.
media flow-through

D.
codec transparent support

E.
Transport Layer Security

F.
H.261, H.263, and H.264 video codecs

Explanation:
Media flow through and media flow around mode is supported on the Cisco Unified Border Element (CUBE). The CUBE is always involved in the call setup (signaling) portion of the call, but the media (RTP bearer stream) may flow through the CUBE or be routed around the platform. Media flow through must be used to support many of the features available like IP address translation and IP address hiding. Media flow around allows the CUBE greater scalability in the number of calls that can be processed by one CUBE router.

For Media flow through option, the media packets are passed through the CUBE, they will get terminated and re-originates with CUBEs IP address and port number, so here we cannot find the original gateways ip address. This is one of the security feature in the CUBE. The default option is media flow-through.

Use the codec transparent command to configure codec pass-through. Use this command to enable endpoint-to-endpoint codec negotiation

without a Cisco UBE router -> D is correct.

Transport Layer Security (TLS) is a security protocol that enables encrypted network communications. TLS on CUBE can be configured on a per-leg basis in order to allow a TLS to non-TLS SIP call. For example, CUBE uses IPSec in order to secure signaling and support calls from H.323 to SIP with the H.323 leg, while the SIP leg uses TLS -> E is correct

The questions only let us choose 3 answers but I think B media flow-around can be used for H323-to-SIP calls. We just cant use media flow-around for SIP-to-SIP calls.

For your information, H.323-to-SIP interworking is configured using the allow-connection h323 to SIP command. Then issue the allow-connections sip to h323 command to enable SIP to H.323 calls.