A customer is integrating two video solutions between regions using a Cisco Unified Border Element and finds that some of the RTP payloads are not compatible with the Cisco Unified Border Element…

Question

Options

• ASpecify the video payload on the voice service.
• BConfigure a transparent codec on the dial peers.
• CConfigure RTP payload mapping on the dial peers.
• DConfigure asymmetric payload on the voice service.
• ESet up a voice class for the video codec.

• A
  57% (31)
• B
  28% (15)
• D
  6% (3)
• E
  9% (5)

Explanation

When RTP payload types are incompatible across a Cisco Unified Border Element (CUBE), Cisco recommends two actions: (A) Specify the video payload type on the voice service configuration so CUBE recognizes and processes the non-standard payload correctly; and (C) Configure RTP payload type mapping on the dial peers, which allows CUBE to translate one payload type number to another between the inbound and outbound call legs. Transparent codec passthrough does not resolve payload type mismatches. Asymmetric payload handles mismatched audio/video payload separately but is not the primary fix. A voice class for video codec addresses codec negotiation, not payload mapping.

No community discussion yet for this question.