Using RADIUS with the OCSBC
Introduction
RADIUS is an accounting, authentication, and authorization (AAA) system. In general, RADIUS servers are responsible for receiving user connection requests, authenticating users, and returning all configuration information necessary for the client to deliver service to the user.
You can configure your OCSBC to send call accounting information to one or more RADIUS servers. This information can help you to see usage and QoS metrics, monitor traffic, and even troubleshoot your system. For more information about QoS, refer to the Admission Control and QoS chapter of the ACLI Configuration Guide.
For information about how to configure the OCSBC for RADIUS accounting use, refer to this guide’s Configuring Accounting chapter.
Licensing
In order to use RADIUS with your OCSBC, you must have the accounting license installed and activated on your system. For more information about licensing, see the Software Licensing section of the ACLI Configuration Guide’s Getting Started chapter. This chapter provides details about Oracle software licensing, including instructions for how to obtain and install licenses.
Overview
For H.323, SIP, and calls being interworked between H.323 and SIP (IWF), you can obtain sets of records that contain information to help you with accounting and that provide a quantitative and qualitative measurement of the call. For H.323 and SIP calls, the OCSBC generates one set of records; for calls requiring IWF, the OCSBC generates two sets of records.
You can use the RADIUS records generated by your OCSBC to assist you with:
- Usage accounting—See the calling and called parties for a call, the protocol used, the realm the call traversed (as well as local and remote IP address and port information), and the codec used
- Traffic monitoring—You can see information about the setup, connect, and disconnect times, as well as the SIP or H.323 disconnect cause
- SLA monitoring—The OCSBC supports RADIUS attributes that provide information about jitter, latency, and loss for H.323, SIP, and calls that require interworking between H.323 and SIP
- Troubleshooting—Obtain information about calls that can help you to identify and address issues with quality and how calls are setup and torn down.
Standard RADIUS Attributes
This section describes the standard RADIUS attributes that the OCSBC supports. These attributes appear along with VSAs (Vendor-Specific Attributes) in the CDRs that the OCSBC generates.
The Standard RADIUS Attributes Dictionary is a dictionary of the standard RADIUS attributes included in Accounting Request messages sent by the OCSBC to the RADIUS server. The CDR event information determines which messages are generated and which RADIUS attributes are included in the messages. Standard RADIUS messages and attributes are used whenever possible; however, RADIUS does not have attributes to record all important session information.
Possible messages are:
- Start—Marks the start of service delivery and describes the type of service being delivered and the user to whom it is being delivered
- Interim-Update—Indicates to the accounting server that the session parameters have changed
- Stop—
- Marks the end of service delivery
- Describes the type of service that was delivered
- Sometimes describes statistics such as elapsed time, input and output octets, or input and output packets
- On—Marks the start of accounting
- Off—Marks the end of accounting
VSAs are used to record the necessary session information missing from this list of standard RADIUS attributes.
For more information about RADIUS, see to the following Internet Engineering Task Force Request for Comments (IETF RFCs):
- RFC 2865, Remote Authentication Dial In User Service (RADIUS), Rigney, et al., June 2000 (http://www.ietf.org/rfc/rfc2865.txt)
- RFC 2866, RADIUS Accounting, C. Rigney, June 2000 (http://www.ietf.org/rfc/rfc2866.txt)
Standard RADIUS Attributes Dictionary
The table below lists and describes standard RADIUS attributes.
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| NAS-IP-Address | IP address of the SIP proxy or the H.323 stack’s call signaling address. | 4 | IP address |
|
| NAS-Port | SIP proxy port or the H.323 stack’s call signaling RAS port. | 5 | integer |
|
| Called-Station-Id | To field value of the SIP INVITE message (a type of message used to initiate a session) or the calledPartyNumber of the H.323 message. | 30 | string |
|
| Calling-Station-Id | From field value of the SIP INVITE message or the callingPartyNumber of the H.323 message. | 31 | string |
|
| NAS-Identifier | Value, if any, set in the optional NAS-ID field
for the accounting server that you configure as part of the accounting
configuration. This identifier sets the value that the remote server (the
accounting server) uses to identify the
OCSBC so that RADIUS
messages can be transmitted.
The remote server to which the accounting configuration will send messages uses at least one of two pieces of information for identification: NAS IP address: always included in the accounting message NAS identifier: configured in the NAS-ID parameter of the accounting server; if configured, the NAS identifier is sent to the remote server This attribute only appears if a value is configured in the NAS-ID field. |
32 | string |
|
| Acct-Status-Type | Whether this Accounting Request marks the beginning of the RADIUS message (Start), the middle (Interim-Update), or the end (Stop), and whether the accounting function is on or off (Accounting-On or Accounting-Off). | 40 | integer |
|
| Acct-Session-Id | Either the Call-ID field value of the SIP INVITE message, the callIdentifier of the H.323 message, or RADIUS client information. | 44 | string |
|
| Acct-Session-Time | How much time in seconds (or milliseconds if so configured) the user has received service. | 46 | integer |
|
| Acct-Terminate-Cause | How or why the session ended. | 49 | integer |
|
RADIUS Accounting Termination Causes
The table below describes the possible session termination causes for the Acct-Terminate-Cause RADIUS attribute.
| RADIUS Termination Cause | Related Integer Value (per RFC 2059) | Termination Event | Message |
|---|---|---|---|
| User Request | 1 | A SIP BYE message. | Stop |
| User Error | 17 | Input from user is erroneous; for example, SIP
signaling failed to establish the session. Used in combination with the Cisco
Systems Disconnect Cause.
(This termination cause is not used for H.323.) |
Stop |
| Lost Service | 3 | Service cannot be sustained for reasons such as a lost connection. | Stop |
| idle-timeout | 4 | Idle timer expired. | Stop |
| session-timeout | 5 | Maximum session length timer expired. | Stop |
| Admin Reset | 6 | OCSBC hard reset occurred: A hard reset occurs when you use the front panel’s orange Reset button; it reboots the OCSBC. | Off |
| Admin Reboot | 7 | OCSBC gracefully rebooted. | Off |
| NAS Request | 10 | RADIUS server is disabled; session terminated for non-error reason. | Off |
VSAs
This section describes the VSAs that the OCSBC supports. These attributes appear along with standard RADIUS attributes in the CDRs that the OCSBC generates.
VSAs are defined by vendors of remote access servers in order to customize how RADIUS works on their servers. This section describes the accounting VSAs for Oracle and for Cisco Systems.
Oracle RADIUS VSAs
Oracle’s vendor identification number is 9148. This number refers to the 4-octet VSA Vendor-ID field. The high-order octet is 0 and the low-order 3 octets are the SMI Network Management Private Enterprise Code of the Vendor in network byte order, defined in the Assigned Numbers RFC (http://www.faqs.org/rfcs/rfc1700.html; Reynolds, J. and J. Postel, Assigned Numbers, STD 2, RFC 1700, October 1994).
The table in this section is a dictionary of Oracle’s accounting VSAs. You can use this information to translate the Oracle VSAs in OCSBC RADIUS messages into human-readable form. Oracle maintains VSA dictionary definition files for the most popular RADIUS distributions; ask your Oracle account representative for details.
Grouped according to attribute function, this table contains the following sections:
- General Flow Attributes—Overall traits of the media flow, these attributes appear in all CDRs regardless of the session’s protocol; these attribute fields are only populated if there are media flows
- Inbound Flow Attributes—Detailed traits of the inbound media flow (including realm, remote IP address and port, and local IP address and port); these attribute fields are only populated if there are media flows
- Outbound Flow Attributes—Detailed traits of the outbound media flow (including realm, remote IP address and port, and local IP address and port); these attribute field are only populated if there are media flows
- Session Attributes—Information about the protocol type, ingress and egress realms used, and an identifier that links the H.323 and SIP legs of a call requiring IWF
- QoS Attributes—RADIUS call records are instantiated by individual signaling applications on the
OCSBC. The
OCSBC writes the following additional parameters to the call record for QoS (Quality of Service):
- RTP Lost packets
- RTP Jitter
- RTP Maximum Jitter
- RTCP Lost packets
- RTCP Jitter
- RTCP Latency
- RTCP Maximum Latency
- RTP Total Packets
- RTP Total Octets
Only RADIUS Stop records contain QoS information. For non-QoS calls, the attributes appear in the record, but their values are always be zero (0). When you review the list of QoS VSAs, please note that “calling” in the attribute name means the information is sent by the calling party and called in the attribute name means the information is sent by the called party.
Examples of how this information appears in CDRs appears in Appendix A of this guide. Please note that the contents of Interim-Update messages do not depend on what events cause a Start message to be generated.
R-Factor and MOS
The OCSBC reports R-Factor and MOS data for the calling and called segments at the end of a session. This information appears in RADIUS CDRs, and in the Oracle VSA dictionary:
- Acme-Calling-R-Factor (151)
- Acme-Calling-MOS (152)
- Acme-Called-R-Factor (153)
- Acme-Called-MOS (154)
Note:
These values are reported as * 100 in order to appear as integers.
Notes on Media Flow Attributes
The OCSBC records media flow attributes in RADIUS CDRs, and there can be multiple flows per session. In order to distinguish between the two flows that appear for a basic session (forward and reverse), the OCSBC supports unique media flow attribute names.
The term flow-set represents a pair of media flows, where one is the forward flow and one is the reverse. The flow attributes described in the table below have the designation FS1 or FS2, which identifies it as either the first or the second flow-set. In addition, all non-QoS attributes have a direction indicator: F for forward, and R for reverse.
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-CDR-Sequence-Number | Sequence number (that increases by 1) the OCSBC generates; recorded in each CDR. | 59 | integer | Start
Interim-Update Stop |
| Acme-Intermediate-Time | Time interval at which periodic interim records are generated during a call. | 63 | string | Interim-Update |
| Acme-Local-Time-Zone | Local GMT/UTC time zone that is provisioned on the OCSBC. | 57 | string | Start
Interim-Update Stop |
| Acme-Firmware-Version | Current software version running on the OCSBC. | 56 | string | Start
Interim-Update Stop |
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-FlowID_FS1_F | Unique identifier for every media flow
processed by the
OCSBC, flow-set 1
forward direction.
This VSA always prefaces other flow information. |
1 | string | Start
Interim-Update Stop On Off |
| Acme-FlowID_FS1_R | Unique identifier for every media flow
processed by the
OCSBC, flow-set 1
reverse direction.
This VSA always prefaces other flow information. |
78 | string | Start
Interim-Update Stop On Off |
| Acme-FlowID_FS2_F | Unique identifier for every media flow
processed by the
OCSBC, flow-set 2
forward direction.
This VSA always prefaces other flow information. |
90 | string | Start
Interim-Update Stop On Off |
| Acme-FlowID_FS2_R | Unique identifier for every media flow
processed by the
OCSBC, flow-set 2
reverse direction.
This VSA always prefaces other flow information. |
112 | string | Start
Interim-Update Stop On Off |
| Acme-FlowType_FS1_F | Codec that describes the flow, flow-set 1 forward direction: PCMU, PCMA, G722, G726, G723, G728, G729, H261, H263, T38. | 2 | string | Start
Interim-Update Stop On Off |
| Acme-FlowType_FS1_R | Codec that describes the flow, flow-set 1 reverse direction: PCMU, PCMA, G726, G723, G728, G729, H261, H263, T38. | 79 | string | Start
Interim-Update Stop On Off |
| Acme-FlowType_FS2_F | Codec that describes the flow, flow-set 2 forward direction: PCMU, PCMA, G726, G723, G728, G729, H261, H263, T38. | 91 | string | Start
Interim-Update Stop On Off |
| Acme-FlowType_FS2_R | Codec that describes the flow, flow-set 2 reverse direction: PCMU, PCMA, G726, G723, G728, G729, H261, H263, T38. | 113 | string | Start
Interim-Update Stop On Off |
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-Flow-In-Realm_FS1_F | Inbound realm identifier for flow-set 1, forward direction. | 10 | string | Start
Interim-Update Stop |
| Acme-Flow-In-Realm_FS1_R | Inbound realm identifier for flow-set 1, reverse direction. | 80 | string | Start
Interim-Update Stop |
| Acme-Flow-In-Realm_FS2_F | Inbound realm identifier for flow-set 2, forward direction. | 92 | string | Start
Interim-Update Stop |
| Acme-Flow-In-Realm_FS2_R | Inbound realm identifier for flow-set 2, reverse direction. | 114 | string | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Addr_FS1_F | Inbound source address (remote) information for flow-set 1, forward direction. | 11 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Addr_FS1_R | Inbound source address (remote) information for flow-set 1, reverse direction. | 81 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Addr_FS2_F | Inbound source address (remote) information for flow-set 2, forward direction. | 93 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Addr_FS2_R | Inbound source address (remote) information for flow-set 2, reverse direction. | 115 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Port_FS1_F | Inbound source (remote) port information for flow-set 1, forward direction. | 12 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Port_FS1_R | Inbound source (remote) port information for flow-set 1, reverse direction. | 82 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Port_FS2_F | Inbound source (remote) port information for flow-set 2, forward direction. | 94 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Src-Port_FS2_R | Inbound source (remote) port information for flow-set 2, reverse direction. | 116 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Addr_FS1_F | Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 1, forward direction. | 13 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Addr_FS1_R | Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 1, reverse direction. | 83 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Addr_FS2_F | Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 2, forward direction. | 95 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Addr_FS2_R | Inbound destination (local) address information (the IPv4 address field value of the steering pool configuration) for flow-set 2, reverse direction. | 117 | IP address | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Port_FS1_F | Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 1, forward direction. | 14 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Port_FS1_R | Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 1, reverse direction. | 84 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Port_FS2_F | Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 2, forward direction. | 96 | integer | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-Port_FS2_R | Inbound destination (local) port information (a port in the range between the start port and end port field values of the steering pool configuration) for flow-set 2, reverse direction. | 118 | integer | Start
Interim-Update Stop |
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-Flow-Out-Realm_FS1_F | Outbound realm identifier for flow-set 1, forward direction. | 20 | string | Start
Interim-Update Stop |
| Acme-Flow-Out-Realm_FS1_R | Outbound realm identifier for flow-set 1, reverse direction. | 85 | string | Start
Interim-Update Stop |
| Acme-Flow-Out-Realm_FS2_F | Outbound realm identifier for flow-set 2, forward direction. | 97 | string | Start
Interim-Update Stop |
| Acme-Flow-Out-Realm_FS2_R | Outbound realm identifier for flow-set 2, reverse direction. | 119 | string | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Addr_FS1_F | Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 1, forward direction. | 21 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Addr_FS1_R | Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 1, reverse direction. | 86 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Addr_FS2_F | Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 2, forward direction. | 98 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Addr_FS2_R | Outbound source (local) address information (the IPv4 address field value of the steering port configuration) for flow-set 2, reverse direction. | 120 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Port_FS1_F | Outbound source (local) port information for flow-set 1, forward direction (a port in the range between the start port and end port field values of the steering port configuration). | 22 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Port_FS1_R | Outbound source (local) port information for flow-set 1, reverse direction (a port in the range between the start port and end port field values of the steering port configuration). | 87 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Port_FS2_F | Outbound source (local) port information for flow-set 2, forward direction (a port in the range between the start port and end port field values of the steering port configuration). | 99 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-Port_FS2_R | Outbound source (local) port information for flow-set 2, reverse direction (a port in the range between the start port and end port field values of the steering port configuration). | 121 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Addr_FS1_F | Outbound destination (remote) address information for flow-set 1, forward direction. | 23 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Addr_FS1_R | Outbound destination (remote) address information for flow-set 1, reverse direction. | 88 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Addr_FS2_F | Outbound destination (remote) address information for flow-set 2, forward direction. | 100 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Addr_FS2_R | Outbound destination (remote) address information for flow-set 2, reverse direction. | 122 | IP address | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Port_FS1_F | Outbound destination (remote) port information for flow-set 1, forward direction. | 24 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Port_FS1_R | Outbound destination (remote) port information for flow-set 1, reverse direction. | 89 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Port_FS2_F | Outbound destination (remote) port information for flow-set 2, forward direction. | 101 | integer | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-Port_FS2_R | Outbound destination (remote) port information for flow-set 2, reverse direction. | 123 | integer | Start
Interim-Update Stop |
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-Session-Generic-Id | Common ID shared by H.323 and SIP call legs
of a session. This attribute is a combination of a time stamp (measured in
seconds) and a monotonically increasing 16-bit integer, followed by an at-sign
(@) and the MAC address of the rear interface (wancom).
This attribute is only used to correlate the H.323 and SIP legs of an interworking call/session. This VSA is not configurable; all CDRs contain this attribute. |
40 | string | Start
Interim-Update Stop |
| Acme-Session-Ingress-CallId | Call ID generated by the originating device. | 3 | string | Start
Interim-Update Stop |
| Acme-Session-Egress-CallId | Call ID generated by the OCSBC to represent a two-way transaction. | 4 | string | Start
Interim-Update Stop |
| Acme-Session-Ingress-Realm | Explicitly identifies the ingress realm, and
contains the name of the ingress realm for the session. All CDRs contain this
attribute.
This VSA is not configurable; all CDRs contain this attribute. |
41 | string | Start
Interim-Update Stop |
| Acme-Session-Egress-Realm | Explicitly identifies the egress realm, and
contains the name of the egress realm for the session. All CDRs contain this
attribute.
This VSA is not configurable. All CDRs contain this attribute, but it is only populated if an egress realm is found; a call without a route does not have an egress realm. |
42 | string | Start
Interim-Update Stop |
| Acme-Session-Protocol-Type | Signaling protocol used for a particular leg
of a session (in the case of IWF, there may be two legs). This attribute
contains the signaling protocol type; for example, SIP or H323.
This VSA is not configurable; all CDRs contain this attribute. |
43 | string | Start
Interim-Update Stop |
| Acme-Session-Charging-Vector | Appears when the
OCSBC inserts, passes,
or deletes the P-Charging-Vector header (SIP).
This attribute is only populated for SIP CDRs, and is not populated if the OCSBC does not have P-Charging-Vector information. |
54 | string | Start
Interim-Update Stop |
| Acme-Session-Charging-Function_Address | Appears when the
OCSBC inserts, passes,
or deletes the P-Charging-Function-Address.
This attribute is only populated for SIP CDRs, and is not populated if the OCSBC does not have P-Charging-Function-Address information. |
55 | string | Start
Interim-Update Stop |
| Acme-Session-Disposition | Status of the call attempt as it progresses from being initiated (using a SIP INVITE or H.323 Setup message) to being either answered or failing to be answered. | 60 | integer | Start
Interim-Update Stop |
| Acme-Post-Dial-Delay | Amount of time between session initiation and an alerting event. | 58 | integer | Start
Interim-Update Stop |
| Acme-P-Asserted-ID | P-Asserted ID as described in RFC 3325. | 69 | string | Start
Interim-Update Stop |
| Acme-SIP-Diversion | SIP Diversion header; communicates to the called party from whom and why a call diverted. | 70 | string | Start
Interim-Update Stop |
| Acme-Primary-Routing-Number | Primary routing number and phone context (or ingress SIP Request-URI). | 64 | string | Start
Interim-Update Stop |
| Acme-Egress-Final-Routing-Number | Final routing number and phone context (or egress SIP Request-URI). | 134 | integer | Stop |
| Acme-Disconnect-Initiator | Initiator of a call disconnect. | 61 | integer | Stop |
| Acme-Disconnect-Cause | Q.850 cause code value. | 62 | integer | Stop |
| Acme-SIP-Status | SIP status code for RFC 3326 support. | 71 | integer | Stop |
| Acme-Originating-Trunk-Group | Originating trunk group. | 65 | string | Start
Interim-Update Stop |
| Acme-Originating-Trunk-Context | Originating trunk group context. | 67 | string | Start
Interim-Update Stop |
| Acme-Terminating-Trunk-Group | Terminating trunk group. | 66 | string | Start
Interim-Update Stop |
| Acme-Terminating-Trunk-Context | Terminating trunk group context. | 68 | string | Start
Interim-Update Stop |
| Acme-Ingress-Local-Addr | Signaling IP address and port of the ingress OCSBC signaling interface. | 74 | string | Start
Interim-Update Stop |
| Acme-Ingress-Remote-Addr | Signaling IP address and port of the ingress remote signaling element. | 75 | string | Start
Interim-Update Stop |
| Acme-Egress-Local-Addr | Signaling IP address and port of the egress OCSBC signaling interface. | 76 | string | Start
Interim-Update Stop |
| Acme-Egress-Remote-Addr | Signaling IP address and port of the destination signaling element. | 77 | string | Start
Interim-Update Stop |
| Acme-Session-Ingress-RPH | RPH value received in the incoming call
(e.g., ets.1).
Only populated for NSEP calls. |
135 | string | Start
Interim-Update Stop |
| Acme-Session-Egress-RPH | RPH value sent in the outgoing call (e.g.,
ets.3).
Only populated for NSEP calls. |
136 | string | Start
Interim-Update Stop |
| Acme-Ingress-Network-Interface-Id | To differentiate overlapping IP address spaces (with the Acme-Ingress-Vlan-Tag-Value), gives the ID of the ingress network interface. | 137 | string | Start
Interim-Update Stop |
| Acme-Ingress-Vlan-Tag-Value | To differentiate overlapping IP address spaces (with the Acme-Ingress-Network-Interface-Id), gives the VLAN tag. | 138 | integer | Start
Interim-Update Stop |
| Acme-Egress-Network-Interface-Id | To differentiate overlapping IP address spaces (with the Acme-Egress-Vlan-Tag-Value), gives the ID of the ingress network interface. | 139 | string | Start
Interim-Update Stop |
| Acme-Egress-Vlan-Tag-Value | To differentiate overlapping IP address spaces (with the Acme-Egress-Network-Interface-Id), gives the VLAN tag. | 140 | integer | Start
Interim-Update Stop |
| Acme-Refer-Call-Transfer-Id | For SIP REFER call method transfer, communicates a call has been transferred from the referer to the referree | 141 | string | Stop |
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-Calling-RTCP-Packets-Lost_FS1 | Total lost packets reported via Real-time
Transport Protocol Control Protocol (RTCP), flow-set 1.
Populated only if QoS is enabled. |
32 | integer | Stop |
| Acme-Calling-RTCP-Packets-Lost_FS2 | Total lost packets reported via Real-time
Transport Protocol Control Protocol (RTCP), flow-set 2.
Populated only if QoS is enabled. |
104 | integer | Stop |
| Acme-Calling-RTCP-Avg-Jitter_FS1 | Average jitter reported via RTCP measured in
milliseconds, flow-set 1.
Populated only if QoS is enabled. |
33 | integer | Stop |
| Acme-Calling-RTCP-Avg-Jitter_FS2 | Average jitter reported via RTCP measured in
milliseconds, flow-set 2.
Populated only if QoS is enabled. |
105 | integer | Stop |
| Acme-Calling-RTCP-Avg Latency_FS1 | Average latency reported by comparing the
timestamps in RTCP packets for each direction of a call, flow-set 1.
Populated only if QoS is enabled. |
34 | integer | Stop |
| Acme-Calling-RTCP-Avg Latency_FS2 | Average latency reported by comparing the
timestamps in RTCP packets for each direction of a call, flow-set 2.
Populated only if QoS is enabled. |
106 | integer | Stop |
| Acme-Calling-RTCP-MaxJitter_FS1 | Maximum amount of jitter value reported via
RTCP measured in milliseconds, flow-set 1.
Populated only if QoS is enabled. |
35 | integer | Stop |
| Acme-Calling-RTCP-MaxJitter_FS2 | Maximum amount of jitter value reported via
RTCP measured in milliseconds, flow-set 3.
Populated only if QoS is enabled. |
107 | integer | Stop |
| Acme-Calling-RTCP-MaxLatency_FS1 | Maximum latency value measured in
milliseconds as observed through RTCP, flow-set 1.
Populated only if QoS is enabled. |
36 | integer | Stop |
| Acme-Calling-RTCP-MaxLatency_FS2 | Maximum latency value measured in
milliseconds as observed through RTCP, flow-set 2.
Populated only if QoS is enabled. |
108 | integer | Stop |
| Acme-Calling-Octets_FS1 | Bytes of RTP traffic for this call, flow-set
1.
Populated only if QoS is enabled. |
28 | integer | Stop |
| Acme-Calling-Octets_FS2 | Bytes of RTP traffic for this call, flow-set
2.
Populated only if QoS is enabled. |
102 | integer | Stop |
| Acme-Calling-Packets_FS1 | Number of RTP Packets, received by the SBC,
from the calling party, for flow-set 1.
Populated only if QoS is enabled. |
29 | integer | Stop |
| Acme-Calling-Packets_FS2 | Number of RTP Packets, received by the SBC,
from the calling party, for flow-set 2.
Populated only if QoS is enabled. |
103 | integer | Stop |
| Acme-Calling-RTP-Packets-Lost_FS1 | Total RTP packets lost in flow-set 1.
Populated only if QoS is enabled. |
37 | integer | Stop |
| Acme-Calling-RTP-Packets-Lost_FS2 | Total RTP packets lost in flow-set 2.
Populated only if QoS is enabled. |
109 | integer | Stop |
| Acme-Calling-RTP-Avg-Jitter_FS1 | Total jitter measured on RTP packets in
milliseconds, flow-set 1.
Populated only if QoS is enabled. |
38 | integer | Stop |
| Acme-Calling-RTP-Avg-Jitter_FS2 | Total jitter measured on RTP packets in
milliseconds, flow-set 2.
Populated only if QoS is enabled. |
110 | integer | Stop |
| Acme-Calling-RTP- MaxJitter_FS1 | Maximum jitter measured on RTP packets in
milliseconds, flow-set 1.
Populated only if QoS is enabled. |
39 | integer | Stop |
| Acme-Calling-RTP-Avg- MaxJitter_FS2 | Maximum jitter measured on RTP packets in
milliseconds, flow-set 2.
Populated only if QoS is enabled. |
111 | integer | Stop |
| Acme-Called-Octets_FS1 | Number of Octets (8 bits) of RTP traffic,
received by the SBC, from the called party, for flow-set 1.
Populated only if QoS is enabled. |
44 | integer | Stop |
| Acme-Called-Octets_FS2 | Number of Octets (8 bits) of RTP traffic,
received by the SBC, from the called party, for flow-set 2.
Populated only if QoS is enabled. |
124 | integer | Stop |
| Acme-Called-Packets_FS1 | Number of RTP Packets, received by the SBC,
from the called party, for flow-set 1.
Populated only if QoS is enabled. |
45 | integer | Stop |
| Acme-Called-Packets_FS2 | Number of RTP Packets, received by the SBC,
from the called party, for flow-set 2.
Populated only if QoS is enabled. |
125 | integer | Stop |
| Acme-Called-RTCP-Packets-Lost_FS1 | Total lost packets reported via Real-time
Transport Protocol Control Protocol (RTCP), flow-set 1.
Populated only if QoS is enabled. |
46 | integer | Stop |
| Acme-Called-RTCP-Packets-Lost_FS2 | Total lost packets reported via Real-time
Transport Protocol Control Protocol (RTCP), flow-set 2.
Populated only if QoS is enabled. |
126 | integer | Stop |
| Acme-Called-RTCP-Avg-Jitter_FS1 | Average jitter reported via RTCP measured in
milliseconds for the ingress side of the call, flow-set 1.
Populated only if QoS is enabled. |
47 | integer | Stop |
| Acme-Called-RTCP-Avg-Jitter_FS2 | Average jitter reported via RTCP measured in
milliseconds for the ingress side of the call, flow-set 2.
Populated only if QoS is enabled. |
127 | integer | Stop |
| Acme-Called-Avg-Latency_FS1 | Average latency reported via RTCP measured in
milliseconds for the ingress side of the call, flow-set 1.
Populated only if QoS is enabled. |
48 | integer | Stop |
| Acme-Called-Avg-Latency_FS2 | Average latency reported via RTCP measured in
milliseconds for the ingress side of the call, flow-set 2.
Populated only if QoS is enabled. |
128 | integer | Stop |
| Acme-Called-RTCP-MaxJitter_FS1 | Maximum amount of jitter reported via RTCP
measured in milliseconds for the ingress side of the call, flow-set 1.
Populated only if QoS is enabled. |
49 | integer | Stop |
| Acme-Called-RTCP-MaxJitter_FS2 | Maximum amount of jitter reported via RTCP
measured in milliseconds for the ingress side of the call, flow-set 2.
Populated only if QoS is enabled. |
129 | integer | Stop |
| Acme-Called-RTCP-MaxLatency_FS1 | Maximum amount of latency reported via RTCP
measured in milliseconds for the ingress side of the call, flow-set 1.
Populated only if QoS is enabled. |
50 | integer | Stop |
| Acme-Called-RTCP-MaxLatency_FS2 | Maximum amount of latency reported via RTCP
measured in milliseconds for the ingress side of the call, flow-set 2.
Populated only if QoS is enabled. |
130 | integer | Stop |
| Acme-Called-RTP-Packets-Lost_FS1 | Total lost RTP packets for the ingress side
of the call, flow-set 1.
Populated only if QoS is enabled. |
51 | integer | Stop |
| Acme-Called-RTP-Packets-Lost_FS2 | Total lost RTP packets for the ingress side
of the call, flow-set 2.
Populated only if QoS is enabled. |
131 | integer | Stop |
| Acme-Called-RTP-Avg-Jitter_FS1 | Average jitter reported via RTP measured in
milliseconds for the ingress side of the realm, flow-set 1.
Populated only if QoS is enabled. |
52 | integer | Stop |
| Acme-Called-RTP-Avg-Jitter_FS2 | Average jitter reported via RTP measured in
milliseconds for the ingress side of the realm, flow-set 2.
Populated only if QoS is enabled. |
132 | integer | Stop |
| Acme-Called-RTP-MaxJitter_FS1 | Maximum amount of jitter reported via RTP
measured in milliseconds for the ingress side of the call, flow-set1.
Populated only if QoS is enabled. |
53 | integer | Stop |
| Acme-Called-RTP-MaxJitter_FS2 | Maximum amount of jitter reported via RTP
measured in milliseconds for the ingress side of the call, flow-set 2.
Populated only if QoS is enabled. |
133 | integer | Stop |
| Acme-Calling-R-Factor | QoS R-Factor calculation for the calling side
of a session.
Populated only if QoS is enabled. This value is reported as * 100 in order to appear as an integer. |
151 | integer | Stop |
| Acme-Calling-MOS | QoS MOS calculation for the calling side of a
session.
Populated only if QoS is enabled. This value is reported as * 100 in order to appear as an integer. |
152 | integer | Stop |
| Acme-Called-R-Factor | QoS R-Factor calculation for the called side
of a session.
Populated only if QoS is enabled. This value is reported as * 100 in order to appear as an integer. |
153 | integer | Stop |
| Acme-Called-MOS
New in Release |
QoS MOS calculation for the called side of a
session.
Populated only if QoS is enabled. This value is reported as * 100 in order to appear as an integer. |
154 | integer | Stop |
| Acme-Session-Forked-Call-Id | The VSA is a string value, and appears as the header-value without the header parameters from the P-Multiring-Correlator header for a session identified as part of a forked call. | 171 | string | Stop |
| Acme-Flow-Calling-Media-Stop-Time_FS1 | calling side’s media stop time - stream 1 | 231 | string | Start
Interim-Update Interim-Update (error) Stop |
| Acme-Flow-Called-Media-Stop-Time_FS1 | called side’s media stop time - stream 1 | 232 | string | Start
Interim-Update Interim-Update (error) Stop |
| Acme-Flow-Calling-Media-Stop-Time_FS2 | calling side’s media stop time - stream 2 | 233 | string | Start
Interim-Update Interim-Update (error) Stop |
| Acme-Flow-Called-Media-Stop-Time_FS2 | called side’s media stop time - stream 2 | 234 | string | Start
Interim-Update Interim-Update (error) Stop |
IPv6 Support
The following table lists the media flow attributes for IPv6 flows.
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Acme-Flow-In-Src-IPv6_Addr_FS1_F | Inbound source IPv6 address (remote) information for flow-set 1, forward direction. | 155 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-IPv6_Addr_FS1_F | Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 1, forward direction. | 156 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-IPv6_Addr_FS1_F | Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 1, forward direction. | 157 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-IPv6_Addr_FS1_F | Outbound destination (remote) IPv6 address information for flow-set 1, forward direction. | 158 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Src-IPv6_Addr_FS1_R | Inbound source IPv6 address (remote) information for flow-set 1, reverse direction. | 159 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-IPv6_Addr_FS1_R | Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 1, reverse direction. | 160 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-IPv6_Addr_FS1_R | Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 1, reverse direction. | 161 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-IPv6_Addr_FS1_R | Outbound destination (remote) IPv6 address information for flow-set 1, reverse direction. | 162 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Src-IPv6_Addr_FS2_F | Inbound source address (remote) IPv6 information for flow-set 2, forward direction. | 163 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-IPv6_Addr_FS2_F | Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 2, forward direction. | 164 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-IPv6_Addr_FS2_F | Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 2, forward direction. | 165 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-IPv6_Addr_FS2_F | Outbound destination (remote) IPv6 address information for flow-set 2, forward direction. | 166 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Src-IPv6_Addr_FS2_R | Inbound source address (remote) IPv6 address information for flow-set 2, reverse direction. | 167 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-In-Dst-IPv6_Addr_FS2_R | Inbound destination (local) address information (the IPv6 address field value of the steering pool configuration) for flow-set 2, reverse direction. | 168 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Src-IPv6_Addr_FS2_R | Outbound source (local) address information (the IPv6 address field value of the steering port configuration) for flow-set 2, reverse direction. | 169 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Out-Dst-IPv6_Addr_FS2_R | Outbound destination (remote) IPv6 address information for flow-set 2, reverse direction. | 170 | ipv6addr | Start
Interim-Update Stop |
| Acme-Flow-Calling-Media-Stop-Time_FS1 | calling side’s media stop time - stream 1 | 231 | string | Start
Interim-Update Interim-Update (error) Stop |
| Acme-Flow-Called-Media-Stop-Time_FS1 | called side’s media stop time - stream 1 | 232 | string | Start
Interim-Update Interim-Update (error) Stop |
| Acme-Flow-Calling-Media-Stop-Time_FS2 | calling side’s media stop time - stream 2 | 233 | string | Start
Interim-Update Interim-Update (error) Stop |
| Acme-Flow-Called-Media-Stop-Time_FS2 | called side’s media stop time - stream 2 | 234 | string | Start
Interim-Update Interim-Update (error) Stop |
Oracle VSA Values
The table below defines the possible values for several Oracle VSAs.
| Oracle VSA Name | Attribute Value | Possible Values |
|---|---|---|
| Acme-PostDial-Delay | 58 | Unit value in milliseconds |
| Acme-Session-Disposition | 60 | 0=unknown
1=call_attempt 2=ringing 3=answered |
| Acme-Disconnect-Initiator | 61 | 0=UNKNOWN_DISCONNECT_INITIATOR
1=CALLING_PARTY_DISCONNECT 2=CALLED_PARTY_DISCONNECT 3=INTERNAL_DISCONNECT |
| Acme-Disconnect-Cause | 62 | 34=No circuit/channel available
47=Resource unavailable 3=No route destination 31=Normal, unspecified 88=Incompatible destination 111=Interworking, unspecified 38=Network out of order 42=Switching equip congestion 28=Invalid number format 41=Temporary failure 17=User busy 16=Normal call clearing 20=Subscriber absent 31=Normal call clearing 18=Request error timeout response 55=Forbidden error response 0=No reason cause presented |
| Acme-SIP-Diversion | 70 | SIP Diversion header based on this RFC draft: draft-levy-sip-diversion-05.txt |
| Acme-SIP-Status | 71 | This is a complete list of support status
codes; only a subset would be reported in a Stop record:
RESP_STATUS_TRYING 100 RESP_STATUS_RINGING 180 RESP_STATUS_FORWARD 181 RESP_STATUS_QUEUED 182 RESP_STATUS_PROGRESS 183 RESP_STATUS_OK 200 RESP_STATUS_CREATED 201 RESP_STATUS_ACCEPTED 202 RESP_STATUS_PART 206 RESP_STATUS_MAX_OK 299 RESP_STATUS_MULTIPLE 300 RESP_STATUS_MOVED 301 RESP_STATUS_MOVED_TMP 302 RESP_STATUS_USE_PROXY 305 RESP_STATUS_ALTERNATE 380 RESP_STATUS_BAD 400 RESP_STATUS_UNAUTH 401 RESP_STATUS_PAY_REQ 402 RESP_STATUS_FORBIDDEN 403 RESP_STATUS_NOT_FOUND 404 RESP_STATUS_NOT_ALLOW 405 RESP_STATUS_NOT_ACCEPT 406 RESP_STATUS_AUTH_REQ 407 RESP_STATUS_REQ_TMO 408 RESP_STATUS_CONFLICT 409 RESP_STATUS_GONE 410 RESP_STATUS_LEN_REQ 411 RESP_STATUS_TOO_BIG 413 RESP_STATUS_URI_TOO_BIG 414 RESP_STATUS_MEDIA 415 RESP_STATUS_URI_SCHEME 416 RESP_STATUS_BAD_EXT 420 RESP_STATUS_EXT_REQ 421 RESP_STATUS_TOO_SMALL 422 RESP_STATUS_TOO_BRIEF 423 RESP_STATUS_TMP_UNAVAIL 480 RESP_STATUS_NO_EXIST 481 RESP_STATUS_LOOP 482 RESP_STATUS_TOOMNY_HOPS 483 RESP_STATUS_ADDR_INCMPL 484 RESP_STATUS_AMBIGUOUS 485 RESP_STATUS_BUSY_HERE 486 RESP_STATUS_CANCELLED 487 RESP_STATUS_NOT_HERE 488 RESP_STATUS_BAD_EVENT 489 RESP_STATUS_PENDING 491 RESP_STATUS_UNDECIPH 493 RESP_STATUS_INT_ERR 500 RESP_STATUS_NOT_IMPL 501 RESP_STATUS_BAD_GTWY 502 RESP_STATUS_SVC_UNAVAIL 503 RESP_STATUS_GTWY_TMO 504 RESP_STATUS_BAD_VER 505 RESP_STATUS_MSG_TOO_BIG 513 RESP_STATUS_PRE_FAIL 580 RESP_STATUS_BUSY 600 RESP_STATUS_DECLINE 603 RESP_STATUS_DONT_EXIST 604 RESP_STATUS_NOTACCEPT 606 |
Authentication VSAs
The table below defines Oracle VSAs used for RADIUS authentication.
| Oracle VSA Name | Attribute Value | Attribute Values |
|---|---|---|
| Acme-User-Privilege | Describes at RADIUS login the privileges
granted to the administrator (VSA only available with admin security license
installed). Values can be:
sftpForAudit (SFTP is allowed for audit logs) sftpForAll (SFTP is allowed for logging, and audit logs) |
253 |
| Acme-User-Class | Identifies the type user on the OCSBC; used for RADIUS authentication only and does not apply to accounting. Values can be user, admin, and SystemAdmin (only with admin security license installed). | 254 |
Cisco Systems RADIUS Decodes
The following table is a dictionary of the Cisco Systems (vendor identification number is 9) accounting VSAs. These attribute names are vendor-specific and subject to change without notice.
You can use the information in this table to translate the Cisco Systems VSAs that sometimes appear in OCSBC RADIUS messages into a more human-readable form.
| Attribute Name | Attribute Description | Attribute Value | Attribute Value Type | Messages |
|---|---|---|---|---|
| Setup Time | The SETUP message is used to request a
connection (and therefore corresponds with the SIP INVITE).
Start record—Time that the first SIP INVITE or H.323 SETUP message was received. Interim record—Time that the applicable SIP REINVITE message was received. Stop record—Time that the last SIP REINVITE message was received. |
25 | string | Start
Interim Stop |
| Connect Time | Time that a SIP or H.323 session was accepted. This is the time a 200 OK SIP response to the SIP INVITE message was received or the time that a call ANSWERED/CONNECTED response to the H.323 SETUP message was received. | 28 | string | Start
Interim-Update Stop |
| Disconnect Time | Time that a SIP BYE or H.323 Release Complete message was received or the session terminated. This is the time a SIP INVITE or H.323 SETUP transaction terminates for any reason. | 29 | string | Stop |
| Disconnect Cause | SIP Reasons for Disconnection (normal,
redirection, client error, network error, global error, time-out, or user
abandon) or the H.323 Release Complete Reason code (bad format address,
unavailable, destination rejection, adaptive busy, etc.).
For more information, refer to this guide’s Mappings and Disconnect Cause Values section. |
30 | string | Stop |
Mappings and Disconnect Cause Values
This section provides information about H.323 and SIP disconnect cause values for RADIUS CDRs generated by the OCSBC.
SIP H.323 and Q.850 Mappings
This section provides tables that show the mappings between SIP Status and: H.323 Disconnect Reason, H.323 Release Complete Reason, and RAS error. It also shows the mapping for Q.850 cause to H.323 Release Complete Reason.
SIP Status to H.323 Disconnect Reason Mapping
| SIP Status | H.323 Disconnect Reason |
|---|---|
| 480 Temporarily Unavailable | No Bandwidth |
| 404 Not Found | Gatekeeper Resource |
| 404 Not Found | Unreachable Destination |
| 603 Decline | Destination Rejection |
| 505 Version Not Supported | Invalid Revision |
| 401 Unauthorized | No Permission |
| 503 Service Unavailable | Unreachable Gatekeeper |
| 480 Temporarily Unavailable | Gateway Resource |
| 400 Bad Request | Bad Format Request |
| 486 Busy Here | Adaptive Busy |
| 486 Busy Here | In Conference |
| 500 Internal Server Error | Undefined Reason |
| 486 Busy Here | Facility Call Deflection |
| 401 Unauthorized | Security Denied |
SIP Status to H.323 RAS Error Mapping
| SIP Status | H.323 RAS Error |
|---|---|
| 404 Not Found | Gatekeeper Resource |
| 401 Unauthorized | Invalid Permission |
| 503 Service Unavailable | Request Denied |
| 500 Internal Server Error | Undefined |
| 401 Unauthorized | Caller Not Registered |
| 305 User Proxy | Route Call to Gatekeeper |
| 500 Internal Server Error | Invalid Endpoint ID |
| 503 Service Unavailable | Resource Unavailable |
| 401 Unauthorized | Security Denial |
| 501 Not Implemented | QoS Control Not Supported |
| 484 Address Incomplete | Incomplete Address |
| 302 Moved Temporarily | Route Call to SCN |
| 485 Ambiguous | Aliases Inconsistent |
| 401 Unauthorized | Not Currently Registered |
SIP Status to H.323 Release Complete Reason Error Mapping
| SIP Status | H.323 RAS Error |
|---|---|
| 300 Multiple Choices | Undefined Reason |
| 401 Unauthorized | Security Denied |
| 402 Payment Required | Undefined Reason |
| 403 Forbidden | No Permission |
| 404 Not Found | Unreachable Destination |
| 405 Method Not Allowed | Undefined Reason |
| 606 Not Acceptable | Undefined Reason |
| 407 Proxy Authentication Required | Security Denied |
| 408 Request Timeout | Adaptive Busy |
| 409 Conflict | Undefined Reason |
| 410 Gone | Unreachable Destination |
| 411 Length Required | Undefined Reason |
| 414 Request-URI Too Large | Bad Format Address |
| 415 Unsupported Media Type | Undefined Reason |
| 420 Bad Extension | Bad Format Address |
| 480 Temporarily Unavailable | Adaptive Busy |
| 481 Call/Transaction Does Not Exist | Undefined Reason |
| 482 Loop Detected | Undefined Reason |
| 483 Too Many Hops | Undefined Reason |
| 484 Address Incomplete | Bad Format Address |
Q.850 Cause to H.323 Release Complete Reason Mapping
The table below describes how the Q.850 Causes and the H.323 release complete reasons are mapped internally on the OCSBC.
| Q.850 Cause | Numeric Code | H.323 Release Complete Reason |
|---|---|---|
| Not Route To Destination | 3 | Unreachable Destination |
| Normal Call Clearing | 16 | Destination Rejection |
| User Busy | 17 | In Conference |
| Subscriber Absent | 20 | Called Party Not Registered |
| Invalid Number Format | 28 | Bad Format Address |
| Normal Unspecified | 16 | Undefined Reason |
| No Circuit/Channel Available | 34 | No Bandwidth |
| Network Out of Order | 38 | Unreachable Gatekeeper |
| Temporary Failure | 41 | Adaptive Busy |
| Switching Equipment Congestion | 42 | Gateway Resource |
| Resource Unavailable | 47 | Gatekeeper Resource |
| Incompatible Destination | 88 | Invalid Revision |
| Interworking Unspecified | 111 | No Permission |
SIP-SIP Calls
The OCSBC maps SIP status codes and events to disconnect cause attribute values used by Cisco Systems Proxy Server (CSPS) accounting services.
| SIP Status Category/Event | CDR Disconnect Cause | Description |
|---|---|---|
| Undetermined reason | 0 | Undetermined reason |
| BYE | 1 | Normal clearing |
| 3xx: Redirection | 2 | Redirection |
| 4xx: Client Error | 3 | Client error |
| 5xx: Server Error | 4 | Server error |
| 6xx: Global Failure | 5 | Global error |
SIP-H.323 Calls with Interworking
For calls that require SIP-H.323 interworking, the OCSBC generates two sets of RADIUS CDRs: one for the SIP call-leg and one for the H.323 call leg. The values recorded in RADIUS Stop records for the disconnect cause depend on the nature and source of the call disconnect or rejection.
SIP Events and Errors
For calls rejected or disconnected because of SIP events and errors, the OCSBC records Q.850 cause values mapped from the SIP event/status code in the SIP CDR. For the H.323 CDR, the SIP status categories and events are mapped to Q.850 cause codes.
The entries in this table are determined by the SIP Status to H.323 Release Complete Reason Error Mapping.
| SIP Status Category/Event | SIP CDR Disconnect Cause | H.323 Disconnect Cause Value (Q.850) |
|---|---|---|
| BYE | 16—Normal call clearing | 16—Normal call clearing |
| 3xx | 23—Redirection to new destination | 16—Normal call clearing |
| 404 Not Found | 21—Call rejected | 3—No route to destination |
| 410 Gone | 21—Call rejected | 3—No route to destination |
| 403 Forbidden | 21—Call rejected | 111—Interworking unspecified |
| 408 Request Timeout | 21—Call rejected | 41—Temporary failure |
| 413 Request Entity Too Big | 21—Call rejected | 28—Invalid number format |
| 414 Request URI Too Large | 21—Call rejected | 28—Invalid number format |
| 420 Bad Extension | 21—Call rejected | 28—Invalid number format |
| 484 Address Incomplete | 21—Call rejected | 28—Invalid number format |
| 408 Request Timeout | 21—Call rejected | 41—Temporary failure |
| 480 Temporarily unavailable | 21—Call rejected | 41—Temporary failure |
| 486 Busy Here | 21—Call rejected | 17—User Busy |
| 401 Unauthorized | 21—Call rejected | 32—Normal unspecified |
| 407 Proxy Authentication Required | 21—Call rejected | 32—Normal unspecified |
| All other 4xx | 21—Call rejected | 16—Normal unspecified |
| 502 Bad Gateway | 38—Network out of order | 28—Invalid number format |
| 505 Bad Version | 38—Network out of order | 88—Incompatible destination |
| All other 5xx | 38—Network out of order | 16—Normal unspecified |
| 600 Busy Everywhere | 31—Normal unspecified | 41—Temporary failure |
| 603 Decline | 31—Normal unspecified | 31—Normal unspecified |
| 604 Does Not Exist Anywhere | 31—Normal unspecified | 3—No route to destination |
| All other 6xx | 31—Normal unspecified | 31—Normal unspecified |
H.323 Events and Errors
The Q.850 cause code value is recorded for the disconnect cause in the CDR for the H.323 call leg if the Q.850 cause is received. H.323 recommendations state that either Q.850 Cause of RelCompReason is mandatory for the RELEASE COMPLETE; the Cause information element (IE) is optional everywhere. The Cause IE and the ReleaseCompleteReason (part of the release complete message) are mutually exclusive.
If a Q.850 cause code is not received, the OCSBC records a Q.850 cause value mapped from the received ReleaseCompleteReason as defined in the table below.
The entries in this table are determined by the SIP Status to H.323 Disconnect Reason Mapping.
| H.323 ReleaseCompleteReason | H.323 CDR Disconnect Cause | SIP Status | SIP CDR Disconnect Cause |
|---|---|---|---|
| No Bandwidth | 34—No channel/circuit available | 480 Temporarily Unavailable | 21—Call rejected |
| Gatekeeper Resource | 47—Resource unavailable | 404 Not Found | 21—Call rejected |
| Unreachable Destination | 3—No route to destination | 404 Not Found | 21—Call rejected |
| Destination Rejected | 31—Normal unspecified | 603 Decline | 31—Normal unspecified |
| Invalid Revision | 88—Incompatible destination | 505 Version Not Supported | 38—Network out of order |
| No Permission | 111—Interworking unspecified | 401 Unauthorized | 21—Call rejected |
| Unreachable Gatekeeper | 38—Network out of order | 503 Service Unavailable | 38—Network out of order |
| Gateway Resource | 42—Switching equipment congestion | 480 Temporarily unavailable | 21—Call rejected |
| Bad Format Request | 28—Invalid number format | 400 Bad request | 21—Call rejected |
| Adaptive Busy | 41—Temporary failure | 486 Busy Here | 21—Call rejected |
| In Conference | 17—User busy | 486 Busy Here | 21—Call rejected |
| Undefined Reason | 16—Normal unspecified | 500 Internal Server Error | 38—Network out of order |
| Called Party Not Registered | 20—Subscriber absent | 404 Not Found | 21—Call rejected |
| Caller Not Registered | 31—Normal call clearing | ||
| New Connection Needed | 47—Resource Unavailable | 401 Unauthorized | 21—Call rejected |
H.225 RAS Errors
For calls that are rejected because of H.225 RAS, there is no CDR generated for the H.323 call leg as no Setup message is generated. The OCSBC maps RAS errors to SIP Status as specified in the table below. The SIP CDR disconnect cause values are the same as the CSPS disconnect cause values already mentioned and defined.
The entries in this table are determined by the SIP Status to H.323 RAS Error Mapping.
| H.225 RAS Error | SIP Status | SIP CDR Disconnect Cause |
|---|---|---|
| Called Party Not Registered | 404 Not Found | 21—Call Rejected |
| Invalid Permission | 401 Unauthorized | 21—Call Rejected |
| Request Denied | 503 Service Unavailable | 38—Network out of order |
| Undefined | 500 Internal Server Error | 38—Network out of order |
| Caller Not Registered | 401 Unauthorized | 21—Call Rejected |
| Route Call to Gatekeeper | 305 Use Proxy | 23—Redirection to new destination |
| Invalid Endpoint ID | 500 Internal Server Error | 38—Network out of order |
| Resource Unavailable | 503 Service Unavailable | 38—Network out of order |
| Security Denial | 401 Unauthorized | 21—Call Rejected |
| QoS Control Not Supported | 501 Not Implemented | 38—Network out of order |
| Incomplete Address | 484 Address Incomplete | 21—Call Rejected |
| Route Call to SCN | 302 Moved Temporarily | 2—Redirection |
| Aliases Inconsistent | 485 Ambiguous | 21—Call Rejected |
| Not Currently Registered | 401 Unauthorized | 21—Call Rejected |
SIP Call Tear Down Due to Media Guard Timer Expiration
When a SIP call is torn down by the OCSBC due to media timers expiring, the following standard and VS attributes and their corresponding values will appear in the CDR stop message:
CDR Output
The following CDR AVPs must be observed in the same CDR.
Acct-Terminate-Cause = Idle-Timeout h323-disconnect-cause = "6" Acme-Disconnect-Initiator = 3
Explanation
- Acct-Terminate-Cause = Idle-Timeout: This standard RADIUS AVP indicates the call was ended due to a timer expiring.
- h323-disconnect-cause = "6": This VSA AVP indicates the call was ended due to a timeout.
- Acme-Disconnect-Initiator = 3: This VSA AVP indicates the call disconnect was initiated internally from the OCSBC, and not from an endpoint or due to an unknown reason.
RTP Traffic Reporting per Call
The SBC reports total RTP traffic counts, both received and transmitted for calls through standard accounting interfaces on stop record generation. This traffic is reported in Packets and Octets, sent and received, for flow-sets 1 and 2. The QoS feature set must be enabled to report on RTP traffic, otherwise the values will be reported as 0
- RTP pass-thru sessions
- transcoded/transrated/inband (audio) DTMF-interworked RTP sessions
- RTP sessions where one or both call legs is encrypted (SRTP)
RTP traffic reporting does not capture MSRP B2BUA and MSRP NAT traffic.
- Calling/Called - call-leg the static reports on
- Octets/Packets - counter unit for traffic
- FS1/FS2 - flow set 1 or flow set 2
- blank/transmitted - traffic received (blank) or transmitted by the SBC
| Counter Definition | RADIUS/Local CDR (VSA #) output | AVP in Acme-Packet-Specific-Rf-QoS(37) |
|---|---|---|
| Number of Octets (8 bits) of RTP traffic, received by the SBC, from the calling party, for flow-set 1 | Acme-Calling-Octets-FS1 (28) | RTP-Calling-Octets-FS1 (38) |
| Number of RTP Packets, sent from the SBC, to the calling UA, for flow-set 1 | Acme-Calling-Packets-FS1 (29) | RTP-Calling-Packets-FS1(40) |
| Number of Octets (8 bits) of RTP traffic, sent from the SBC, to the called UA, for flow-set 1 | Acme-Called-Octets-FS1 (44) | RTP-Called-Octets-FS1 (62) |
| Number of RTP Packets, sent from the SBC, to the called UA, for flow-set 1 | Acme-Called-Packets-FS1 (45) | RTP-Called-Packets-FS1 (64) |
| Number of Octets (8 bits) of RTP traffic, received by the SBC, from the calling party, for flow-set 2 | Acme-Calling-Octets-FS2 (102) | RTP-Calling-Octets-FS2 (39) |
| Number of RTP Packets, sent from the SBC, to the calling UA, for flow-set 2 | Acme-Calling-Packets-FS2 (103) | RTP-Calling-Packets-FS2(41) |
| Number of Octets (8 bits) of RTP traffic, sent from the SBC, to the called UA, for flow-set 2 | Acme-Called-Octets-FS2 (124) | RTP-Called-Octets-FS2 (63) |
| Number of RTP Packets, sent from the SBC, to the called UA, for flow-set 2 | Acme-Called-Packets-FS2 (125) | RTP-Called-Packets-FS2 (65) |
| Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the calling party, for flow-set 1 | Acme-Calling-RTP-Octet-Transmitted-FS1 (240) | RTP-Calling-Octets-Transmitted-FS1 (42) |
| Number of RTP Packets, transmitted by the SBC, to the calling UA, for flow-set 1 | Acme-Calling-RTP-Packet-Transmitted-FS1 (241) | RTP-Calling-Packet-Transmitted-FS1 (44) |
| Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the called UA, for flow-set 1 | Acme-Called-RTP-Octet-Transmitted-FS1 (242) | RTP-Called-Octets-Transmitted-FS1 (66) |
| Number of RTP Packets, transmitted by the SBC, to the called UA, for flow-set 1 | Acme-Called-RTP-Packet-Transmitted-FS1 (243) | RTP-Called-Packet-Transmitted-FS1 (68) |
| Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the calling party, for flow-set 2 | Acme-Calling-RTP-Octets-Transmitted-FS2 (244) | RTP-Calling-Octets-Transmitted-FS2 (43) |
| Number of RTP Packets, transmitted by the SBC, to the calling UA, for flow-set 2 | Acme-Calling-RTP-Packet-Transmitted-FS2 (245) | RTP-Calling-Packet-Transmitted-FS1 (45) |
| Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the called UA, for flow-set 2 | Acme-Called-RTP-Octet-Transmitted-FS2 (246) | RTP-Called-Octets-Transmitted-FS2 (67) |
| Number of RTP Packets, transmitted by the SBC, to the called UA, for flow-set 2 | Acme-Called-RTP-Packet-Transmitted-FS2 (247) | RTP-Called-Packet-Transmitted-FS2 (69) |
