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.