[asterisk-bugs] [Asterisk 0016747]: Caller ID info is destroyed after FXS channel is ringed

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16747 
====================================================================== 
Reported By:                viniciusfontes
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   16747
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Target Version:             1.6.2.8
Asterisk Version:           SVN 
JIRA:                       SWP-836 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-02-01 13:18 CST
Last Modified:              2010-04-06 13:53 CDT
====================================================================== 
Summary:                    Caller ID info is destroyed after FXS channel is
ringed
Description: 
This is just after Asterisk is started:

pabx*CLI> dahdi show channel 5
Channel: 5
File Descriptor: 24
Span: 2
Extension: 
Dialing: no
Context: ddd
Caller ID: 7025
Calling TON: 0
Caller ID name: ALMOX
Mailbox: none
Destroy: 0
InAlarm: 0
Signalling Type: FXO Kewlstart
Radio: 0
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no
Busy Detection: yes
    Busy Count: 3
    Busy Pattern: 0,0
TDD: no
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
DND: no
Echo Cancellation:
	256 taps
	(unless TDM bridged) currently OFF
Wait for dialtone: 0ms
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Onhook


Then after a call is made to that channel:

pabx*CLI> dahdi show channel 5
Channel: 5
File Descriptor: 24
Span: 2I> 
Extension: 
Dialing: no
Context: ddd
Caller ID: 
Calling TON: 0
Caller ID name: 
Mailbox: none
Destroy: 0
InAlarm: 0
Signalling Type: FXO Kewlstart
Radio: 0> 
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: noI> 
Busy Detection: yes
    Busy Count: 3
    Busy Pattern: 0,0
TDD: noI> 
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
DND: noI> 
Echo Cancellation:
pabx*CLI256 taps
pabx*CLI(unless TDM bridged) currently OFF
Wait for dialtone: 0ms
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Onhook


Notice how both CID name and number are gone.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015985 CallerID problem
related to          0015883 NewChannel AMI event on DAHDI (or Zapte...
has duplicate       0016968 [patch] Callerid  Channel dahdi port FX...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-06 13:53 svnbot         Status                   assigned => resolved
2010-04-06 13:53 svnbot         Resolution               open => fixed       
======================================================================