Project

General

Profile

Actions

Feature #1685

open

osmo-sip-connector: Review and define log statements and which info to include

Added by zecke over 6 years ago. Updated about 3 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
Start date:
03/31/2016
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

Define how to handle logging and which fields to include. It should be call + leg. Right now it is only leg.

Actions #1

Updated by laforge over 6 years ago

  • Category set to osmo-sip-connector
Actions #2

Updated by laforge over 5 years ago

  • Project changed from OsmoNITB to osmo-sip-connector
  • Category deleted (osmo-sip-connector)
Actions #3

Updated by laforge over 4 years ago

  • Assignee changed from zecke to sysmocom
Actions #4

Updated by laforge about 4 years ago

  • Assignee changed from sysmocom to osmith
Actions #5

Updated by laforge about 4 years ago

Actions #6

Updated by osmith about 4 years ago

  • Status changed from New to In Progress

Define how to handle logging and which fields to include.

laforge, keith:
  • Which additional log messages would be useful and which fields should they have?
  • Are there missing fields in existing messages?
  • Is there unhelpful information that we should not display at all or only output when increasing the log level?

It should be call + leg. Right now it is only leg.

  • Do you guys want an additional log message when a call has been initiated?
  • Which other call related log messages would be helpful?
Actions #7

Updated by laforge about 3 years ago

  • Tracker changed from Bug to Feature
  • Parent task deleted (#1604)
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)