Configuring Diameter-based RACF
In the following configuration examples, we assume that your baseline configuration passes SIP traffic, with the Oracle Communications Session Border Controller (SBC) in the role of an Access SBC. In this example, you perform realm configuration and external bandwidth manager configuration. You also configure media profiles with the bandwidth parameters you reserve at the RACF.
Diameter Support Realm Configuration
To configure the realm configuration for Diameter support in a CAC scenario:
Media Profile Configuration
Values for the following parameters can be found in the PacketCable™ Audio/Video Codecs Specification PKT-SP-CODEC-I06-050812 document.
To configure the media profile configuration for Diameter support in a CAC scenario:
Additional Diameter Compliance for the Rx Interface
When handling some Register and Message flows, the SBC default behavior does not include strict compliance with Diameter session teardown rules. Typically, the environment can proceed without issue, but the SBC provides an ext-policy-server option, called diam-rx-strict-compliance, that provides better compliance with Diameter session teardown rules.
Set the diam-rx-strict-compliance option on the applicable ext-policy-server to establish the following Diameter session behavior:
- For Register flows that do not establish a Diameter session with the PCRF due to a 3xxx, 4xxx or 5xxx error from the PCRF, the SBC does not send an STR to tear down the session when it receives a De-Register.
- For Message flows, when the SBC receives an ASR from PCRF, it stops the hold timer if it is running, then forwards the MESSAGE to the core, and sends an ASA with success.
- For unsuccessful Register flows that include an established Diameter session with the PCRF, the SBC sends an STR to tear down the session after the Register has failed due to, for example, responses from the core.
- If the SBC receives an S8HR Emergency Registration, with or without Authorization header, and either the Rx interface is not available or there is an error in AAA response sent by PCRF, the SBC replies with a 5xx response. (ACMECSBC-37498)
- If the SBC receives an S8HR Emergency Registration without an Authorization header and the EPC identities validation fails, the SBC sends a 403 error with the SIP reason header. If the SBC receives a REGISTER request with the authorization header, it sends a MIME XML body with a reason tag. (ACMECSBC-37497)
- For S8HR registrations and calls, the SBC adds the P-Visited-Network-ID header using the format "plmnIdPrefix.mncxxx.mccxxx.3gppnetwork.org". (ACMECSBC-37431)
- During an S8HR registration scenario, if the SBC receives a REGISTER request with the Authorization header and the next-hop is not configured, the SBC sends a 403 response if the EPC identities validation fails. (ACMECSBC-37459 )
- Within a register call flow wherein the SBC receives an AAA with a 3002 error code from the PCRF after the diameter transaction has timed out, the SBC does not send an STR to the PCRF.
- Within emergency REGISTER call flows when S8HR is enabled and there are no EPC level identities cached, the SBC does not issue an STR simultaneously with a 403 error code if it receives a 3002 error code from the PCRF.
Syntax for this option may or may not include the plus (+) sign, but note that setting the option with the + sign retains all other options set on the element. Omitting the + sign replaces any existing options with the one you set.
ACMEPACKET(ext-policy-server)# options +diam-rx-strict-complianceConfiguring the Rx Interface for SCTP
You configure the Rx interface for SCTP transport from the ext-policy-server element. See the SCTP Overview and configuration sections in this document's System Configuration chapter for information about SCTP operation and the global settings within the network-parameters element that apply to all SCTP operation.
CAC Debugging
A new argument has been added to the show command for viewing CAC statistics. From the user prompt, type show ext-band-mgr.
ORACLE# show ext-band-mgr
10:11:38-194
EBM Status -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Client Trans 0 0 0 0 0 0
Server Trans 0 0 0 0 0 0
Sockets 1 1 1 1 1 1
Connections 0 0 0 0 0 0
---- Lifetime ----
Recent Total PerMax
Reserve 0 0 0
Modify 0 0 0
Commit 0 0 0
Remove 0 0 0
EBM Requests 0 0 0
EBM Installs 0 0 0
EBM Errors 0 0 0
EBM Rejects 0 0 0
EBM Expires 0 0 0
EBMD Errors 0 0 0Retrieve the CAC statistics in the log.embd file.