MCU BFCP configuration

[petark]

Hi Everyone,

We are running several MCUs(4505, 5320) and connecting a third-party h323 Gateway/Client to virtual rooms.

The problem is the content negotiation which fails if h323 Gateway tries to share only after the Cisco Telepresence EP(SX20, DX80).

I have escalated this issue with third-party support and they found out that "the MCU is offering BFCP server only which would force h323 Gateway into client mode which is not supported"

They are suggesting to configure the MCU to support BFCP in client mode...

Is there any way to do this?

Thanks,

Petar

[PJMack]

Do you have your MCU's configured for both SIP and H.323? It sounds like you do - BFCP is content for SIP, H.239 is for H.323. Since your third party gateway is just H.323, I'd probably suggest using only H.323, it should solve your problem. What are your SX/DX's registered to?

[Wayne DeNardi]

How do you have the Content configured on your MCU?

In the conference settings, you can change the Content Mode:

Content

Content mode

The MCU can decode and then re-encode incoming content to ensure that the majority of participants can receive the content. This is the Transcoded content mode. The MCU can also retransmit the content without having to decode it, which is known as Passthrough mode. In this mode, the incoming content packet stream is repackaged and sent to endpoints in the conference that are capable of decoding the original stream. Passthrough mode does not use up a content port for that conference. The MCU also has a Hybrid content mode. In Hybrid mode, the incoming content stream is passed through to participants who are able to support the same codec as the original content stream (the Passthrough content stream). The MCU also encodes a stream, using the specified Outgoing transcoded codec, for endpoints who cannot decode the Passthrough content stream. Hybrid mode uses up a video port. Choose from: Disabled: The MCU does not transmit content. Passthrough: The MCU does not transcode the content before transmission. The data is simply repackaged then sent to endpoints that support the original codec. Hybrid: The MCU sends a passthrough stream to eligible endpoints, and a transcoded stream to other endpoints that advertise support for the Outgoing transcoded codec. Transcoded: The MCU decodes the incoming stream and re-encodes it using the Outgoing transcoded codec, before sending it to all endpoints that support the Outgoing transcoded codec.