[asterisk-bugs] [LibPRI 0017568]: [patch] DNID does not get cleard on new call

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17568 
====================================================================== 
Reported By:                wuwu
Assigned To:                
====================================================================== 
Project:                    LibPRI
Issue ID:                   17568
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.2.9 
JIRA:                       SWP-1836 
libpri Version:             1.4.11 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2010-06-30 07:13 CDT
Last Modified:              2010-07-12 02:39 CDT
====================================================================== 
Summary:                    [patch] DNID does not get cleard on new call
Description: 
with chan_dahdi - when you are using immediate=yes - and you get a call
with dnid provided - and after this call you get a call without a dnid -
then the second call will also have the dnid of the first call assigned,
because chan_dahdi does not reset the dnid field on the new call.
====================================================================== 

---------------------------------------------------------------------- 
 (0124477) klaus3000 (reporter) - 2010-07-12 02:39
 https://issues.asterisk.org/view.php?id=17568#c124477 
---------------------------------------------------------------------- 
Please ignore the problem reported by me - it is cleary different as it
happens only with trunk whereas this bug happpens with 1.6.2.

I have created another bugreport for my issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-12 02:39 klaus3000      Note Added: 0124477                          
======================================================================