[asterisk-bugs] [LibPRI 0014378]: Two odd error messages on BRI PtMP lines

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14378 
====================================================================== 
Reported By:                timking
Assigned To:                mattf
====================================================================== 
Project:                    LibPRI
Issue ID:                   14378
Category:                   General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-31 11:41 CST
Last Modified:              2009-11-22 06:10 CST
====================================================================== 
Summary:                    Two odd error messages on BRI PtMP lines
Description: 
I am running libpri-1.4.9 in a production environment. I notice the
following in the logs, apparently at random.
[Jan 30 15:33:11] ERROR[7615] chan_dahdi.c: XXX Message longer than it
should be?? XXX
[Jan 30 15:33:15] ERROR[7615] chan_dahdi.c: XXX Message longer than it
should be?? XXX
[Jan 30 15:33:50] ERROR[7614] chan_dahdi.c: XXX Message longer than it
should be?? XXX
[Jan 30 15:33:54] ERROR[7614] chan_dahdi.c: XXX Message longer than it
should be?? XXX
[Jan 30 15:34:29] ERROR[7615] chan_dahdi.c: !! < Unknown IE 224 (cs0, len
= 1)
====================================================================== 

---------------------------------------------------------------------- 
 (0114109) timking (reporter) - 2009-11-22 06:10
 https://issues.asterisk.org/view.php?id=14378#c114109 
---------------------------------------------------------------------- 
I doubt it's in outgoing calls - the message is in q931_receive.
A temporary fix is to make the error handling better as noted above.
Simply change the return -1 after the error message to break and it
actually handles the call OK.

lmadsen  - any chance of that one-line improvement going in to trunk? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-22 06:10 timking        Note Added: 0114109                          
======================================================================