Media Setup & Playback

For each session requiring media playback, the Oracle® Enterprise Session Border Controller sets up media that supports standard RTP parameters. From the original media (if present), the 
Oracle® Enterprise Session Border Controller preserves the synchronization source (SSRC), timestamp, and sequence number.

For all playback options besides playback-on-header, the playback duration is continuous, meaning that the media file loops if it fails to cover the entire playback period.

The playback duration for the playback on header scenario changes according to the settings in the P-Acme-Playback header. This header contains a duration=<ms-value|once|continuous> value, so you can customize the playback duration.

  • Continuous—Media playback continues until the point at which the playback scenario defines its stop; media file loops if it fails to cover the entire playback duration.
  • Once—The file plays until either the playback scenario defines its stop or until the media file runs out.
  • Ms-value—Playback continues for a specific duration (in milliseconds) and will loop if necessary.

Once playback is in progress, the Oracle® Enterprise Session Border Controller mutes the session in the playback direction so that only the playback media can be heard.

Media Spirals

Certain call flows cause media to traverse the Oracle® Enterprise Session Border Controller multiple times, resulting in media spirals. For local playback, this means that multiple playback files can be triggered to play. In situations like this, the Oracle® Enterprise Session Border Controller uses the playback closest to the endpoint receiving the media playback. Origination A in the diagram below is played Local playback #1, even though the scenario also triggers Local playback #2.

The ESBC supporting playback during media spirals.

Media Files

You must upload a file containing to /code/media to the E-SBC for the media that you want played. This file must be raw media binary containing data for the desired codec. A separate file is required for each different codec type, even if the media itself is the same.

Your configuration must specify a playback rate in bytes per second, as this setting defines how many bytes of data per unit of ptime are needed.

To preserve system memory resources, media files are limited to 2MB.