Supported Local Media Triggers

The Oracle® Enterprise Session Border Controller (ESBC) can generate media locally based on end station signaling, local media playback configuration, and other ESBC configuration.

Local media playback capabilities are dependent upon your choice of media generation method. Be aware of the few operational differences between these methods. Most new deployments use the transcoding-based method.

Deployments Configured for Transcoding Resources

The Oracle® Enterprise Session Border Controller (ESBC) supports the following playback triggers when configured for transcoding resources:
  • Playback on 180 Ringing
  • Playback on 180 Ringing when 180 does not include SDP
  • Playback on 183 Session Progress
  • Playback on REFER
  • Playback upon both 183 and REFER
  • Playback on header, where the header is P-Acme-Playback

You can also configure the ESBC with HMR response code mapping on the SIP call egress side to map a 183 into a 180 response, thereby triggering playback on 180 Ringing. This requires that you map a 183 response into a 180 response, which then triggers playback.

Deployments Configured with SPL

The ESBC supports the following playback triggers when configured with SPL:
  • Playback on 183 Session Progress
  • Playback on REFER
  • Playback on header, where the header is P-Acme-Playback
The ESBC does not support the following operations for local media playback when configured with SPL:
  • SRTP
  • Call recording
  • SIPREC