...
Caption | ||||
---|---|---|---|---|
| ||||
|
Diameter Message | IMS Node Triggering of SIP Methods / ISUP Messages | ||
---|---|---|---|
ACR [Start] | IMS Node sends ACR (Start) to Rf Accounting server when SIP 200 OK acknowledging an Initial SIP INVITE is received. | ||
ACR [Interim] | IMS Node sends ACR (Interim) to Rf Accounting server, when "Accounting Interim interval" for the session expires. | ||
When "Acct-Interim-Interval" AVP is received from the AAA server in ACA message, SBC treats the value received as the "Accounting Interim interval" for the session. | |||
When "Acct-Interim-Interval" AVP is NOT received from the AAA server in ACA message, SBC treats the default "Accounting Interim interval" value configured on the system as "Accounting Interim Interval" for the session. | |||
When "Acct-Interim-Interval" AVP is NOT received from the AAA server in ACA message and "Accounting Interim Interval" value configured on the system is '0', SBC does NOT send ACR (Interim) Message for the session. | |||
When "Acct-Interim-Interval" AVP is received from the AAA server in ACA message, SBC sends ACR (Interim) Message for the session based on the value received in "Acct-Interim-Interval AVP", irrespective of "Accounting interim interval" value configured on the system. | |||
ACR [Stop] | IMS Node sends ACR (STOP) with Cause-Code AVP (AVP code 861) to Rf Accounting server when session is terminated. (Session for which ACR (Start) was originally sent by the node). Termination examples:
| ||
When an ongoing SIP session has been normally released either by the user or by the network (SIP BYE message initiated by the user or initiated by the network has been received by the IMS node after the reception of the SIP ACK message), SBC sends the ACR (STOP) as below. | |||
When the SIP session is not successfully established (that is, Timer H expires and SIP ACK is not received, or SIP BYE is received after reception of the 200 OK final response and SIP ACK is not received), SBC sends the ACR: Cause-code AVP (AVP code 861) = "Unsuccessful session setup" 2 | |||
When the SIP session is terminated by the IMS node because of a system error (for example, system wide error or failure, crash, card failure) after session is established, SBC sends the ACR: Cause-code AVP (AVP code 861) = "Unspecified error" 1
| |||
ACR [Attempt] | IMS Node sends the ACR (EVENT) to Rf Accounting server to report a failed session attempt in following scenarios:
| ||
IMS Node sends the ACR (EVENT) to Rf Accounting server, to report a redirection of a session attempt in following scenario.
| |||
IMS Node sends the ACR (EVENT) to Rf Accounting server to report a redirection of a session attempt in following scenario.
| |||
ACR [Event] | IMS Node sends the ACR (EVENT) to Rf Accounting server to report non-session related SIP Message events on receipt of following messages.
| ||
When a successful transaction terminating the Registration dialog is detected by the IMS node, the node sends the ACR as below.
In the following scenarios:
| |||
When the SIP transaction is terminated due to an IMS node receiving/initiating a 3xx Final response, Node sends the ACR as below.
| |||
When the SIP transaction (INVITE or Non-INVITE transaction) is terminated due to an IMS node receiving/initiating a Failure response (that is, 4xx, 5xx, 6xx) error response, Node sends the ACR with appropriate Cause-code AVP (AVP code 861) value as below.
| |||
When the SIP transaction (INVITE or Non-INVITE transaction) is terminated due to an IMS node has internal or Unknown error (for example, error in processing a request/response), Node sends one of the cause codes in the ACR as below.
| |||
When a successful transaction terminating the Subscription dialog is detected by the IMS node, the node sends the ACR with cause-code AVP (AVP code 861) = End of SUBSCRIBE dialog (-2).
| |||
When
|
Note |
---|
On the Rf interface there is no ACR (ATTEMPT) record type, ACR (EVENT) is used to report attempt records |
...