Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Caption
0Table
1SBC Handling of Diameter Messages

 

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:

  • SIP BYE request received for SIP INVITE session from Calling or called Party
  • Any Abnormal SIP session release (Internal error or call released by SBC, for example, call release because of inactivity timer expiry, long duration call, call drop because of card failure and so on.)
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

Note
 "Unspecified error" is used when Specific Cause-codes not defined. SBC sends "1" for any "Internal" or unspecified errors which cannot be mapped to any existing cause-codes.

ACR [Attempt]

IMS Node sends the ACR (EVENT) to Rf Accounting server to report a failed session attempt in following scenarios:

  • Terminate Session due to receipt of SIP CANCEL before INVITE session is established,
  • Terminate Session due to receipt of Final SIP response (4xx, 5xx, 6xx) before INVITE session is established,
  • Any Abnormal SIP session release due to Internal error, for example, call drop because of card failure etc. before INVITE session is established.
Note

On the Rf interface there is no ACR (ATTEMPT) record type, ACR (EVENT) is used to report attempt records.

 

IMS Node sends the ACR (EVENT) to Rf Accounting server, to report a redirection of a session attempt in following scenario.

  • Session is redirected because of receipt of Final SIP response (3xx) before INVITE session is established,
 

IMS Node sends the ACR (EVENT) to Rf Accounting server to report a redirection of a session attempt in following scenario.

  • Redirect Session due to receipt of Final SIP response (3xx) before INVITE session is established
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.

  • SIP 200 OK Message to acknowledge SIP NOTIFY transaction
  • SIP 200 OK Message to acknowledge SIP MESSAGE transaction
  • SIP 200 OK Message to acknowledge Initial SIP REGISTER transaction
  • SIP 200 OK Message to acknowledge Initial SIP SUBSCRIBE transaction
  • SIP 200 OK Message to acknowledge SIP PUBLISH transaction
  • SIP 200 OK Message to acknowledge SIP OPTIONS RELAY transaction
  • SIP 202 OK Message to acknowledge SIP REFER transaction

 

When a successful transaction terminating the Registration dialog is detected by the IMS node, the node sends the ACR as below.

  • Cause-code AVP (AVP code 861) = "End of REGISTER dialog"   -3

In the following scenarios:

  • SIP De-register request received from User (Expires =0).
  • SIP NOTIFY with "reg evnt" received notifying deletion of registration.
  • Deletion of registration on Expiry of registration expiry timer.
  • SIP registration administratively deleted using CLI/GUI.
 

When the SIP transaction is terminated due to an IMS node receiving/initiating a 3xx Final response, Node sends the ACR as below.

  • · Cause-code AVP (AVP code 861) = "3xx Redirection"    -3xx
 

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.

  • "4xx Request failure"    4xx
  • "5xx Request failure"    5xx
  • "6xx Request failure"    6xx
 

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.

  • · Cause-code AVP (AVP code 861) = "Unspecified error"     1
Note

Transaction failures which do not map to previous requirements should be logged as Internal or Unknown errors. This is a catch-all cause-code.

 

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).

  • SIP Unsubscribe request is received from User (Expires =0)
  • SIP NOTIFY (in-dialog) with subscription-state header is set to 'terminated' notifying deletion of subscription
  • Subscription is deleted on Expiry of subscription timer
  • SIP subscription is administratively deleted using CLI/GUI
 

When eventAcctState flag is enabled, EVENT records are generated for OOD SUBSCRIBE, REFER, NOTIFY, REGISTER, OPTIONS, MESSAGE, and PUBLISH.

 

Note

On the Rf interface there is no ACR (ATTEMPT) record type, ACR (EVENT) is used to report attempt records

...