[asterisk-bugs] [Asterisk 0016398]: Error in ulaw

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16398 
====================================================================== 
Reported By:                globalnetinc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16398
Category:                   Codecs/codec_ulaw
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.11 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-04 22:50 CST
Last Modified:              2009-12-06 04:42 CST
====================================================================== 
Summary:                    Error in ulaw
Description: 
Every since upgrade from prior version 1.6.1.X we see these errors in the
debug log:
chan_sip.c: Bogus frame of format 'ulaw' received from
'SIP/4065877430-0000036d'!

These are Linksys ATAs 2102 running 5.2.10 of code
====================================================================== 

---------------------------------------------------------------------- 
 (0114824) davidw (reporter) - 2009-12-06 04:42
 https://issues.asterisk.org/view.php?id=16398#c114824 
---------------------------------------------------------------------- 
This is a SIP issue, not a codec issue.  Please follow the SIP problem
reporting procedures (including sip set debug output).

The message is not saying that there is any error in the handling of ulaw.
 It is actually saying that it has received an RTP frame, containing ulaw
encoded data, when it hasn't actually agreed that ulaw is an acceptable
format for the session.

What is actually going wrong, as issues should not be reported purely on
the basis of  messages output when debug logging is turned on.  Why did you
turn on debug logging? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-06 04:42 davidw         Note Added: 0114824                          
======================================================================