[asterisk-bugs] [Asterisk 0017269]: DAHDI FXS channels: CALLERID(num) and CALLERID(name) are empty after first hangup

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Apr 30 14:04:52 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17269 
====================================================================== 
Reported By:                evandro
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17269
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.27-rc2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-30 12:47 CDT
Last Modified:              2010-04-30 14:04 CDT
====================================================================== 
Summary:                    DAHDI FXS channels: CALLERID(num) and CALLERID(name)
are empty after first hangup
Description: 
As related by issue 16968, the problem persist. I took a look at
chan_dahdi.c, and realized that this occurs on lines 4532 and 4533, between
#ifdef HAVE_OPENR2 code.
Commenting these two lines solve the problem, but I don't know how that
may affect another functions.
====================================================================== 

---------------------------------------------------------------------- 
 (0121249) pabelanger (manager) - 2010-04-30 14:04
 https://issues.asterisk.org/view.php?id=17269#c121249 
---------------------------------------------------------------------- 
We will need to see some debug logs reproducing the issue.  Be sure to
check https://issues.asterisk.org/view.php?id=16968 for an example.

http://svn.digium.com/svn/asterisk/trunk/doc/HOWTO_collect_debug_information.txt

---
Thank you for taking the time to report this bug and helping to make
Asterisk better. 

Unfortunately, we cannot work on this bug because your description did not
include enough information. 

You may find it helpful to read the Asterisk Issue Guidelines
http://www.asterisk.org/developers/bug-guidelines. 

We\'d be grateful if you would then provide a more complete description of
the problem.

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

This likely includes output from the console with debug level logging, a
SIP trace (if this is SIP related), and configuration information such as
dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf).

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-30 14:04 pabelanger     Note Added: 0121249                          
======================================================================




More information about the asterisk-bugs mailing list