Configuring Local Media Playback

You can configure local media playback either with or without transcoding resources. All configurations are RTC supported.

RTC Support

The playback configuration is supported by real-time configuration (RTC). Media files located in the /code/media directory and referenced by playback configuration entries are loaded at boot time and when you activate a configuration. The system does not reload any media being played to an endpoint. Playbacks that start after the boot or configuration activation use updated media files.

Note:

If you change an existing media file but preserve the filename, you must reboot for the changes to take effect.

RBT TrFO Configuration

You configure the SBC to avoid using transcoding resources by setting the feature-trfo parameter in the applicable realm-config .

  1. Access the media-manager configuration element
    ORACLE# configure terminal
ORACLE(configure)# media-manager
ORACLE(media-manager)# realm-config
ORACLE(realm-config)# select
  2. feature-trfo—Set the parameter to ringback.
    ORACLE(realm-config)# feature-trfo ringback
  3. Type done and save your configuration.

Configuring Local Media Playback with Transcoding Resources

You can configure local media playback with the transcoding-based method on a session-agent, sip-interface or realm-config, using this precedence when determining which configuration to use if there are overlapping configurations. This example procedure configures playback on a realm using the 180-force trigger.

Although the procedure below sets parameters to a realm-config, you can apply the same parameters and values to a session-agent and a sip-interface.
  1. In Superuser mode, use the following command sequence to access realm configuration: 
    ORACLE# configuration terminal
ORACLE(configure)# media-manager
ORACLE(media-manager)# realm-config
ORACLE(realm-config)#
  2. Set the ringback file. 
    ORACLE(realm-config)# ringback-file my-media.wav
  3. Set the ringback trigger. 
    ORACLE(realm-config)# ringback-trigger 180-force
  4. Use done and exit to complete the configuration.
  5. Use save, verify-config and activate to apply the policy to the running configuration.

The verify-config command checks and reports on the following playback configuration issues:

  • ringback-file refers to a file that exists under /code/media/
  • ringback-file refers to a file that does not surpass the maximum size allowed 5 MB
  • ringback-trigger and playbackConfig are not both configured

Configuring Network Announcements for 4xx/5xx/6xx Responses

You map error codes to media files on the session router and enable network announcements for them on a sip-interface or realm-config, with the realm taking precedence when there are overlapping configurations.

Configuring the Error Announcement Map

You map error codes to media files on the session router in the error-announcement-map element. The same map is used for all realms and interfaces for which announcement-on-error is set to enabled.

  1. Access the entries configuration element for the error-announcement-map:
    ORACLE# configure terminal
ORACLE(configure)# session-router
ORACLE (session-router)# error-announcement-map
ORACLE (error-announcement-map)# entries
ORACLE (error-announcement-map-entry)#
  2. Set the following parameters:
    1. sip-response-code: Set to the SIP response code to map the playback file to. Either this or q850-cause-code is required (you can specify both).
    2. q850-cause-code: Set to the Q.580 cause code to map the playback file to. Either this or sip-response-code is required (you can specify both).
    3. announcement-file: Required. Set this to the name of the file containing the announcement to play when the callee sends the mapped response code. This file must be present in the /code/media directory, can be a maximum of 32 characters (including the extension), and may not contain a slash (/).
  3. Save and activate your changes.

You can add up to 100 entries, update existing entries, and delete entries using the standard ACLI configuration commands. Each entry must contain a unique combination of sip-response-code and q850-cause-code. You cannot map the same combination to two different announcement files.

For example, because the following three entries use different combinations of SIP and Q.850 codes, they are all valid, even though the individual codes are the same:

error-announcement-map
        entries
                sip-response-code       400
                q850-cause-code         18
                announcement-file       file1.pcm
        entries
                sip-response-code       400
                announcement-file       file2.pcm
        entries
                q850-cause-code         18
                announcement-file       file3.pcm

However, adding the following entry would be invalid, because the specified code combination already matches file1.pcm: 

error-announcement-map
        entries
                sip-response-code       400
                q850-cause-code         18
                announcement-file       file2.pcm

Enabling Network Announcements for Realms and Interfaces

You enable realms and interfaces to play network announcements with the announcement-on-error parameter. The same error-announcement-map applies to all enabled realms and interfaces. In case of overlapping configurations, the realm takes precedence.

  1. Access one of the following configuration elements:
    • realm-config:
      ORACLE# configure terminal
ORACLE(configure)# media-manager
ORACLE(media-manager)# realm-config
ORACLE(realm-config)#
    • sip-interface:
      ORACLE# configure terminal
ORACLE(configure)# session-router
ORACLE(session-router)# sip-interface
ORACLE(sip-interface)#
  2. Set the announcement-on-error parameter to enabled:
    • realm-config:
      ORACLE(realm-config)# announcement-on-error enabled
    • sip-interface:
      ORACLE(sip-interface)# announcement-on-error enabled
  3. Save and activate your configuration.