| Summary: | ASTERISK-17590: Busy()/Congestion() apps don't work in chan-dahdi with h-extension and priindication=outofband | ||
| Reporter: | Igor Nikolaev (microlana) | Labels: | |
| Date Opened: | 2011-03-22 03:38:09 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | Open/New | Components: | Applications/General |
| Versions: | 1.8.3 13.18.4 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When inbound calls landing on [context] to the extensions 123 or 456, if h-extension in the same context epsent, BUSY/CONGESTION is successfully sent to PRI channel. If h-extension present, BUSY/CONGESTION isn't sent to the PRI channel until h-extension execution in progress. Therefore, it's impossible to initiate callback feature by AGI into h-extension if a reason of drop incoming call is Busy() or Congestion() application. ****** ADDITIONAL INFORMATION ****** extensions.conf [context] exten => 123,1,Congestion() exten => 456,1,Busy() exten => h,1,AGI(...) chan_dahdi.conf priindication=outofband | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-04-01 14:24:29 Per rmudgett: I think the reporter for mantis 19008 has a point. chan_dahdi basically just sets the softhangup flag and returns when processing AST_CONTROL_BUSY/AST_CONTROL_CONGESTION in that configuration. The builtin Busy() and Congestion() apps then just wait for hangup. I think chan_dahdi should queue an AST_CONTROL_HANGUP instead so the wait for hangup will not happen. | ||