Call Flow Statistics Logs

The following are the synopsis of the Call Flow Statistics Logs to trigger session management policies towards the SMF:

  • Currently, each call flow has the following general labels and other specific labels:

    • Attempted

    • Success

    • Failure + Reason

  • All the call flow statistics gets integrated with EndProcedure.

  • Each DispositionEnd used to end the call flow in the procedure, concludes either as a success or a failure scenario. Each failure scenario has a reason for integration as well.

  • Failure causes can be classified into different levels. They are further mapped and classified as the following:

    • Major or Error

      • Internal Error—All internal errors due to which the call flow is failing, are categorized as error.

      • Transaction Timeout Error—On interfaces, outbound response timeouts (transaction timeouts) are categorized as errors.

    • Minor or Warning

      • Server Error—On interfaces, outbound responses with the http status code 5xx (server errors) are categorized as a warning.

      • Client Error—On interfaces, inbound responses with the http status code 4xx (client errors) or timeouts are categorized as a warning.

    • Normal

      • Server Error—On interfaces, inbound responses with the http status code 5xx (server errors) are categorized as normal.

      • Client Error—On interfaces, outbound responses with http status code 4xx (client errors) are categorized as normal.

  • Unknown—Those scenarios, where the call flow gets failed, but the reason doesn't get populated, fall under the unknown cause.

  • Further, these scenarios can be enhanced to cases, other statistics labels of statistics, which get integrated to empty statuses.

    Example: RAT type integrated as empty, DNN type not integrated, and so on.