2774 - Provisioning of SIP Signaling Flow Information
This feature supports of Provisioning of SIP Signaling Flow Information as described in 3GPP TS 29.213 section B1b [1], and the procedures specified in TS 29.214 section 4.4.5a.
The feature applies to the scenario when the Oracle Communications Session Border Controller (A-SBC / P-CSCF) uses its external policy server functionality and connects to a PCRF via Rx interface in bandwidth-management mode.
This feature deals with the information that the Oracle Communications Session Border Controller includes in an AAR message it sends to the PCRF when an endpoint registers, re-registers, and de-registers. The following diagram shows the typical scenario.
Configuration Conflict
The npli-upon-register component of an npli-profile invalidates the provision-signaling-flow configuration when they overlap. Exercise caution when applying a provision-signaling-flow to ensure it does not conflict with any npli-profile configuration. The SBC provides a configuration verification error when it detects this conflict.
Initial Registration
When an endpoint registers, the Oracle Communications Session Border Controller creates and sends an AAR message to a PCRF which includes the following information:
<AA-Request>::= < Diameter Header: 265, REQ, PXY >
| AVP | AVP Contents |
|---|---|
| Session-ID | OriginHost;0;0;<Key to Registration
Cache>
Key is usually the endpoint’s AoR. |
| Auth-Application-ID | Application-ID of Rx (16777236) |
| Origin-Host | <ext-policy-server_name>.<ext-policy-realm>.<domain-name-suffix> |
| Origin-Realm | <ext-policy-realm>.<domain-name-suffix> |
| Destination-Realm | <IP Address of endpoint>@<destination realm of this AAR> |
| Framed-IP-Address AVP - v4 address
Framed-IPv6-Prefix AVP - v6 address |
Layer 3 Endpoint-IP-address
v4 - Framed-IP-Addressor v6 - Framed-IPv6-Prefix |
| Media-Component | Grouped AVP description follows |
Media-Component-Description AVP ::= < AVP Header: 517 >
| AVP | AVP Contents |
|---|---|
| Media-Component-Number | 0 |
| Media-Sub-Component | Grouped AVP description follows |
Media-Sub-Component ::= < AVP Header: 519 >
| AVP | AVP Contents |
|---|---|
| Flow-Number | 1 |
| Flow-Description | Permit in <ip> from <Endpoint IP:Port> to <SBC Sip
Interface IP:Port>
Permit out <ip> from <SBC SIP Interface IP:Port> to <Endpoint IP Port> Where <ip> is (UDP: 17, TCP: 6) if wildcard-trans-protocol = disabled. |
| Flow-Status | Set to: ENABLED (2) |
| Flow-Usage | Set to: AF_SIGNALLING (2) |
| AF-Signalling-Protocol | Set to: SIP (1) |
Register Refresh
When a registration Refresh is received before the half time of the registration expiry, the registration cache is not updated and the Oracle Communications Session Border Controller responds with 200OK to the UE. This is standard registration cache functionality. No additional AAR is sent to the PCRF.
If a registration Refresh is received after the half time of the registration expiry, or if any registration information changes, the Oracle Communications Session Border Controller sends an AAR to the PCRF after it receives and forwards a 200 OK response from registrar. The AAR includes the same session-id as the initial AAR that was to PCRF. This lets PCRF correlate the AAR with the earlier AAR that it received.
De-Registration
When an contact de-registers with expires=0, it means that the endpoint is removing all of its contacts from registration. When this occurs, the Oracle Communications Session Border Controller sends an STR message to the PCRF to terminate the session. If the de-registration message does not reflect a complete de-registration, the Oracle Communications Session Border Controller does not send the STR message to the PCRF. The STR message includes the following information:
<ST-Request> ::= < Diameter Header: 275, REQ, PXY >
| AVP | AVP Contents |
|---|---|
| Session-ID | OriginHost;0;0;<Key to Registration
Cache>
Key is usually the endpoint’s AoR. |
| Auth-Application-ID | Application-ID of Rx (16777236) |
| Origin-Host | <ext-policy-server_name>.<ext-policy-realm>.<domain-name-suffix> |
| Origin-Realm | <ext-policy-realm>.<domain-name-suffix> |
| Destination-Realm | <IP Address of endpoint>@<destination realm of this AAR> |
| Destination-Host | N/A |
| Termination-Cause | DIAMETER LOGOUT (1) - User initiated a disconnect |
Failure Response to Re-Register
Upon reception of a failure response from the REGISTRAR for a subsequent Registration refresh from endpoint, the Oracle Communications Session Border Controller performs de-registration actions, i.e. an STR message to the PCRF.
Provisioning SIP Signaling Flows Configuration
To enable correct provisioning of signaling flows upon registration:
Troubleshooting
Upon receipt of AAA response from PCRF for the AAR sent, the Oracle Communications Session Border Controller logs the status of the AAA received. Successful AAAs are noted by session-ID in EBMD logs. The log will look like:
Provision of SIP Signaling Flow (<session-ID>) via Diameter Rx on realm <realm-id> successful.Failed AAA response are noted at NOTICE level EBMD logs citing the failure response to AAR request with the session-ID sent. An a MINOR non-health-affecting alarm is also raised with the following text:
Provision of SIP Signaling Flow (<session-ID>) via Diameter Rx on realm <realm-id> failed.show ext-band-mgr
The show ext-band-mgr command has been augmented to include the Register and DeRegister counts. For example:
ORACLE# show ext-band-mgr
13:55:49-166
EBM Status -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Client Trans 0 0 0 7 4 1
Server Trans 0 0 0 0 0 0
Sockets 1 1 0 1 1 1
Connections 0 0 0 1 1 1
---- Lifetime ----
Recent Total PerMax
Reserve 0 0 0
Modify 0 0 0
Commit 0 4 2
Remove 0 2 1
Register 1 1 1
DeRegister 1 1 1
EBM Requests 0 6 3
EBM Installs 0 6 3
EBM Req. Errors 0 0 0
EBM Rejects 0 0 0
EBM Expires 0 0 0
EBMD Errors 0 0 0