Multiple Media Profiles
You can use the media profiles configuration to set up:
- One media profile for a particular SIP SDP encoding (such as G729), where the name of the profile identifies it uniquely. This behavior is your only option in Oracle® Enterprise Session Border Controller release prior to Release C6.1.0.
- Multiple media profiles for the same SIP SDP encoding. Available in Release C6.1.0 and forward, you can create multiple media profiles for the same encoding. To do so, you add a subname to the configuration, thereby identifying it uniquely using two pieces of information rather than one.
The sections below provide two descriptions of deployments where using multiple profiles for the same codec would solve codec and packetization problems for service providers.
Use Case 1
Service Provider 1 peers with various carriers, each of which uses different packetization rates for the same codec. For example, their Peer 1 uses 10 milliseconds G.711 whereas their Peer 2 uses 30 milliseconds for the same codec. The difference in rates produces a difference in bandwidth consumption—resulting in a difference in SLA agreements and in Oracle® Enterprise Session Border Controller call admission control (CAC) and bandwidth policing. Service Provider 1 uses the Oracle® Enterprise Session Border Controller’s media profile configuration parameters to determine CAC (req-bandwidth) and bandwidth policing (avg-rate-limit). Because this service provider’s peers either do not use the SDP p-time attribute or use it inconsistently, it is difficult to account for bandwidth use. And so it is likewise difficult to set up meaningful media profiles.
The best solution for this service provider—given its traffic engineering and desire for the cleanest routing and provisioning structures possible—is to define multiple media profiles for the same codec.
Use Case 2
Service Provider 2 supports H.263 video, for which the Oracle® Enterprise Session Border Controller offers a pre-provisioned media profile with a set bandwidth value. And yet, H.263 is not a codec that has a single bandwidth value. Instead, H.263 can have different bandwidth values that correspond to various screen resolution and quality. While it is true that the Oracle® Enterprise Session Border Controllercan learn the requisite bandwidth value from SDP, not all SDP carries the bandwidth value nor do system operators always trust the values communicated.
Configuring multiple media profiles for the same codec (here, H.263) helps considerably with this problem—and moves closer to complete solution. Service Provider 2 can configure H.263 media profiles capable of handling the different bandwidth values that might appear.
