[Home]

Summary:ASTERISK-00290: D-channel failure does not result in call rejection
Reporter:John Todd (jtodd)Labels:
Date Opened:2003-09-19 15:21:27Date Closed:2011-06-07 14:05:29
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When a call is passed in from an IAX2 channel and is then mapped to a Zap channel on a PRI, it is the case that if the D-channel is down, then the call will continue to ring.  This should produce an error, and not simply try to keep passing the call out the PRI.

****** ADDITIONAL INFORMATION ******

gw3*CLI>
   -- Accepting AUTHENTICATED call from 204.91.156.10, requested format = 4, actual format = 4
   -- Executing SetCallerID("IAX2[pdx1@pdx1]/16384", "3015841514") in new stack
   -- Executing Dial("IAX2[pdx1@pdx1]/16384", "Zap/g1/14102241145") in new stack
   -- Called g1/14102241145
 == D-Channel on span 1 down
   -- Hungup 'Zap/12-1'
 == Spawn extension (from-pdx1, 14102241145, 2) exited non-zero on 'IAX2[pdx1@pdx1]/16384'
   -- Executing SetCallerID("IAX2[pdx1@pdx1]/16384", "3025871514") in new stack
   -- Executing Dial("IAX2[pdx1@pdx1]/16384", "Zap/g1/h") in new stack
   -- Called g1/h
   -- Hungup 'Zap/13-1'
 == Spawn extension (from-pdx1, h, 2) exited non-zero on 'IAX2[pdx1@pdx1]/16384'
   -- Hungup 'IAX2[pdx1@pdx1]/16384'
 == D-Channel on span 1 down
gw3*CLI>
Comments:By: x martinp (martinp) 2003-09-21 14:48:31

What if you have extensions:

exten => _X.,1,Dial(Zap/g2/${EXTEN})
exten => _X.,2,Hangup

?
By: John Todd (jtodd) 2003-10-07 12:42:00

It is difficult for me to test with this, since it requires my D-channel to fail, which has not happened in a few weeks.  I will have updates when a failure occurs on our main switch, and I will test your experiment.
By: John Todd (jtodd) 2003-10-14 15:34:13

Yes, adding the hangup line does seem to solve the problem.