Project

General

Profile

Feature #3636

detailed call statistics (with rate counters)

Added by osmith 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/08/2018
Due date:
% Done:

0%

Resolution:

Description

Follow up to #1679: rate counter statistics in OsmoMSC would be useful for:

How many calls were;
  • busy
  • rang out (unanswered)
  • unreachable,
    etc, etc...

There are already call rate counters present, but they don't specify an exact reason why a call was terminated.

            call:mo_setup:          0 (0/s 0/m 0/h 0/d) Received setup requests from a MS to init a MO call.
      call:mo_connect_ack:          0 (0/s 0/m 0/h 0/d) Received a connect ack from MS of a MO call. Call is now succesful connected up.
            call:mt_setup:          0 (0/s 0/m 0/h 0/d) Sent setup requests to the MS (MT).
          call:mt_connect:          0 (0/s 0/m 0/h 0/d) Sent a connect to the MS (MT).
              call:active:          0 (0/s 0/m 0/h 0/d) Count total amount of calls that ever reached active state.
            call:complete:          0 (0/s 0/m 0/h 0/d) Count total amount of calls which got terminated by disconnect req or ind after reaching active state.
          call:incomplete:          0 (0/s 0/m 0/h 0/d) Count total amount of call which got terminated by any other reason after reaching active state.

Related issues

Related to osmo-sip-connector - Feature #1679: osmo-sip-connector: Add stats for call handlingStalled2016-03-31

History

#1 Updated by osmith 2 months ago

  • Related to Feature #1679: osmo-sip-connector: Add stats for call handling added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)