[asterisk-bugs] [Asterisk 0015157]: Annoying "Unknown RTP codec 126 received" messages confuse people
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed May 20 09:45:23 CDT 2009
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: feedback
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-20 09:45 CDT
======================================================================
Summary: 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
======================================================================
----------------------------------------------------------------------
(0105107) tilghman (administrator) - 2009-05-20 09:45
https://issues.asterisk.org/view.php?id=15157#c105107
----------------------------------------------------------------------
Yes, but this isn't an Asterisk problem, per se. It's an X-Lite problem
that they did not first negotiate codec 126 in the SIP dialog before
sending it. It is explicitly a violation of the SIP specification to send
an non-negotiated codec, and we WANT to know when that happens, so we can
inform vendors to fix their clients.
Issue History
Date Modified Username Field Change
======================================================================
2009-05-20 09:45 tilghman Note Added: 0105107
======================================================================
More information about the asterisk-bugs
mailing list