[asterisk-bugs] [Asterisk 0015157]: [patch] Annoying "Unknown RTP codec 126 received" messages confuse people

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15157 
====================================================================== 
Reported By:                jcovert
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15157
Category:                   Core/RTP
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.9 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-19 12:51 CDT
Last Modified:              2009-05-21 12:05 CDT
====================================================================== 
Summary:                    [patch] Annoying "Unknown RTP codec 126 received"
messages confuse people
Description: 
The X-Lite Softphone, one of the most commonly used softphones on Asterisk,
sends RTP codec 126 messages, which annoy and confuse users who are running
with verbosity set to 3, the most likely verbosity setting for watching a
system in operation.

I propose:

a. modifying main/rtp.c to test VERBOSITY_ATLEAST(4) prior to the call to
ast_log(LOG_NOTICE, "Unknown RTP codec %d received from...",...)

b. (and/or possibly) explicitly ignoring 126 no matter what the
verbosity.

I will generate a patch in the next two or three days; in the interim I
welcome any comments.

I also note that in trunk rtp.c has been replaced by rtp_engine.c; I have
not yet determined whether a similar issue exists.  Comments?

Regards/john
====================================================================== 

---------------------------------------------------------------------- 
 (0105240) jcovert (reporter) - 2009-05-21 12:05
 https://issues.asterisk.org/view.php?id=15157#c105240 
---------------------------------------------------------------------- 
Additional info:

There is a draft IETF spec for keep-alives

http://tools.ietf.org/html/draft-ietf-avt-app-rtp-keepalive-05

which states:

   The RECOMMENDED solution is thus the "RTCP packets multiplexed with
   RTP packets" (Section 4.3).  However, when this mechanism cannot be
   negotiated, it is RECOMMENDED to use the fallback "RTP Packet with
   Unknown Payload Type" mechanism (Section 4.6) as it will always work. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-21 12:05 jcovert        Note Added: 0105240                          
======================================================================