VoLTE and SMS VSAs
The SBC reports session-specific information for VoLTE calls and for Short Message Service (SMS) messages. Much of this information overlaps both session types as they address similar variables within their environments.
This table lists and describes the VoLTE and SMS attributes and includes attribute name, attribute description, attribute value, attribute value type, and messages.
Note:
See the Oracle RADIUS Acme-Extended-Attributes VSAs section for an explanation of the attribute extensions included in the tables below.| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-Access-Network-Information | Extracted from Access-Network-Information
field from P-Access-Network-Info headers.
For MO calls it should be the PANI headers of the outgoing INVITE (after the NPLI procedure). For MT calls it should be the PANI headers of the outgoing 18x response (after the NPLI procedure). |
248 | SMS and VoLTE | Start
Interim-Update Stop |
| Acme-P-GW IP Address | Obtained from PCRF RAR/AAA in Access-Network-Charging-Address (501) AVP. | 249, ext 1 | VoLTE call | Start
Interim-Update Stop |
| Acme-S-GW IP Address | Obtained from PCRF AAA/RAR in AN-GW-Address (1050) AVP | 249, ext 2 | VoLTE call | Start
Interim-Update Stop |
| Acme-Originating-IOI | Extracted from the Originating-IOI field in
the P-Charging-Vector header.
For MT, MO (MESSAGE/INVITE) calls, the field is extracted from SIP reply(20X). |
249, ext 3 | SMS and VoLTE call | Start
Interim-Update Stop |
| Acme-Terminating-IOI | Extracted from the Terminating-IOI field in
the P-Charging-Vector header.
For MT, MO (MESSAGE/INVITE) calls, the field is extracted from SIP reply(20X). |
249, ext 4 | SMS and VoLTE call | Start
Interim-Update Stop |
| Acme-IMEI | Extracted from the registration cache or
Initial request.
(The Initial request takes priority.) |
249, ext 5 | SMS and VoLTE call | Start
Interim-Update Stop |
| Acme-Node-Functionality | Configured with a single, global Node
Functionality value. This is done in the SIP config's node functionality
parameter.
However, if the node functionality parameter is also configured in a realm config, the ingress realm's node functionality value supersedes the global value. |
249, ext 6 | SMS and VoLTE call | Start
Interim-Update Stop |
| Acme-SMS Message Type | Extracted from initial SIP MESSAGE. | 249, ext 7 | SMS |
Stop |
| Acme-SMS Calling party number | Extracted from initial SIP MESSAGE.
For MO, from the P-Asserted-Identity header For MT, from the TP-Originating-Address |
249, ext 8 | SMS |
Stop |
| Acme-SMS Called party number | Extracted from initial SIP MESSAGE.
For MO, from the TP-Destination-Address For MT, from the To header of the SIP MESSAGE |
249, ext 9 | SMS |
Stop |
| Acme-Message Length | Extracted from SIP MESSAGE field TP-User-Data-Length | 249, ext 10 | SMS |
Stop |
| Acme-History-Info | Extracted from History-Info sip headers,
ingress interface and it taken from initial message.
In case of multiple History-Info headers, concatenated into a single header values in CDR. |
250 | VoLTE call | Start
Interim-Update Stop |
| Acme-Visited-Network-Identifier | Extracted from Visited-Network-Identifier field from
P-Visited-Network-Id headers.
For MO calls, the field is extracted from initial request, or from the ingress sip-interface if the PVNI is not received in the initial request. For MT calls, the field is extracted from the initial request. |
251 | SMS and VoLTE call | Start
Interim-Update Stop |
| Acme-IMSI | Extracted from the registration cache or
Initial request.
(The Initial request takes priority.) |
252 | SMS and VoLTE call | Start
Interim-Update Stop |
This information appears in RADIUS CDRs, CSV CDRs, and the Oracle VSA dictionary. The SBC reports with AVP information that is equivalent to the VSA information below.
The SBC generates SMS call records when you configure the generate-event parameter with the messages value. Fields supporting message accounting include:
- Acme-Access-Network-Information (248)
- Acme-Visited-Network-Identifier (251)
- Acme-Originating-IOI (249, extension 3)
- Acme-Terminating-IOI (249, extension 4)
- Acme-IMSI (252)
- Acme-IMEI (249, extension 5)
- Acme-Node-Functionality (249, extension 6)
- Acme-SMS Message Type (249, extension 7)
- Acme-SMS Calling party number (249, extension 8)
- Acme-SMS Called party number (249, extension 9)
- Acme-Message Length (249, extension 10)
- Acme-Timestamp
The SBC generates VoLTE call records under the same scenarios and using the same configuration as other SIP calls. Fields supporting VoLTE call accounting include:
- Acme-Access-Network-Information (248)
- Acme-Visited-Network-Identifier (251)
- Acme-Originating-IOI (249, extension 3)
- Acme-Terminating-IOI (249, extension 4)
- Acme-IMSI (252)
- Acme-IMEI (249, extension 5)
- Acme-History-Info (250)
- Acme-Node-Functionality (249, extension 6)
- Acme-P-GW IP Address (249, extension 1)
- Acme-S-GW IP Address (249, extension 2)
Note:
The SBC includes this same information within equivalent records managed over diameter. VSAs do not have the "Acme" prefix in their name, and the VSA identification information is specific to diameter VSAs.