Project

General

Profile

Bug #1685

OsmoNITB - Bug #1604: Easier / more direct SIP integration

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

Added by zecke over 2 years ago. Updated about 2 months ago.

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

0%

Resolution:

Description

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

History

#1 Updated by laforge over 2 years ago

  • Category set to osmo-sip-connector

#2 Updated by laforge over 1 year ago

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

#3 Updated by laforge 9 months ago

  • Assignee changed from zecke to sysmocom

#4 Updated by laforge 3 months ago

  • Assignee changed from sysmocom to osmith

#5 Updated by laforge 2 months ago

#6 Updated by osmith about 2 months 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?

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)