search

bensari / mediaserver

Automatically exported from code.google.com/p/mediaserver
1 stars 0 forks source link

Increase logging information in DEBUG mode #50

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When working with MMS, logging is not thorough even if the debug level is set 
to DEBUG. When set to DEBUG the only extra information is the packet sizes 
received by the MGCP controller. This makes debugging the media server tedious 
when there is a problem.

Original issue reported on code.google.com by quintana...@gmail.com on 11 Jul 2012 at 10:57

GoogleCodeExporter commented 8 years ago 
What can be done to make logging better as this a very important aspect of 
support to help diagnose issues ?

Original comment by jean.deruelle on 16 Jul 2012 at 3:44

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 16 Jul 2012 at 3:44

GoogleCodeExporter commented 8 years ago 
MMS logging is an increasing problem. We continue seing problems with 
conferencing and it takes too long to diagnose the issue. At a minimum, it 
should be possible to correlate RTP sessions to MGCP sessions to SIP sessions.

When we receive messages that the codecs were changed by the client on the RTP 
stream, we should be able to trace back the session IDs and find out the DID of 
the caller that is causing these RTP changes. There is currently no easy way to 
do this kind of basic correlation. Here is all that there is coming from MMS at 
the moment:

2012-07-16 16:13:48,443 INFO  [JitterBuffer] (pool-1-thread-2) Format has been 
changed: 0 AudioFormat[pcmu,8000,8,mono]
2012-07-16 16:13:48,483 INFO  [JitterBuffer] (pool-1-thread-3) Format has been 
changed: 0 AudioFormat[pcmu,8000,8,mono]
2012-07-16 16:13:48,764 INFO  [JitterBuffer] (pool-1-thread-3) Format has been 
changed: 0 AudioFormat[pcmu,8000,8,mono]
2012-07-16 16:13:48,823 INFO  [JitterBuffer] (pool-1-thread-2) Format has been 
changed: 0 AudioFormat[pcmu,8000,8,mono]
2012-07-16 16:13:48,863 INFO  [JitterBuffer] (pool-1-thread-1) Format has been 
changed: 0 AudioFormat[pcmu,8000,8,mono]

this is all the info even in DEBUG and TRACE modes.

Original comment by ivelin.a...@gmail.com on 17 Jul 2012 at 1:18

GoogleCodeExporter commented 8 years ago 
Changing priority to critical because it is preventing us from fixing a problem 
with a live instance on EC2. Because of the issue, the conferencing stops 
working frequently without any early sign.

Original comment by ivelin.a...@gmail.com on 17 Jul 2012 at 1:20

GoogleCodeExporter commented 8 years ago 
Add Endpoint Name + Connection Name to Jitter Buffer

Original comment by oifa.yul...@gmail.com on 18 Jul 2012 at 3:08

GoogleCodeExporter commented 8 years ago 
Okay this is an issue that will take some time to completely get right but the 
attached patch adds logging for all exceptions and replaces 
System.out.println(...) to logger.info(...) which makes sure that all log 
messages are in the log file for examination. The patch also adds more logging 
info where appropriate like for example MgcpProvider logs information which may 
be useful when debugging the MGC(media gateway controller).

Note: This patch does not touch the SS7 or Dahdi packages.

Original comment by quintana...@gmail.com on 18 Jul 2012 at 7:15

Attachments:

GoogleCodeExporter commented 8 years ago 
Applied patch
Closed by revision a1168a3d74fd

Original comment by oifa.yul...@gmail.com on 21 Jul 2012 at 10:43