| Summary: | ASTERISK-02627: Monitor with option 'b' records silence when bridging Zap channels | ||
| Reporter: | chadscott (chadscott) | Labels: | |
| Date Opened: | 2004-10-18 20:56:36 | Date Closed: | 2011-06-07 14:10:07 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When I do a Monitor with option 'b', it records silence when two channels on the same Zap PRI bridge together. ****** ADDITIONAL INFORMATION ****** I have calls coming in on a Zap PRI and entering into this logic that then bridges the call to another channel on the same Zap PRI: exten => 8001,1,Answer exten => 8001,2,Wait(1) exten => 8001,3,Monitor(wav49,my-monitor-${TIMESTAMP},bm) exten => 8001,4,Dial(Zap/r1/18005551212,,m) The Monitor app is called as expected, and I see soxmix running after the call completes, but the resulting file is silence. If I remove the 'b' option, it works fine, except I hear the music on hold in the file. | ||
| Comments: | By: Anthony Minessale (anthm) 2004-10-22 09:51:27 I tried this same secenrio on a pri and mine worked although the recording contained ringing because the bridge begins before the call actually does due to the fact that as soon as the pri connects with the pstn the call is considered bridged. I also tested it between 2 channels on a tdm400 and it worked there too By: chadscott (chadscott) 2004-10-22 10:22:22 Okay, let me repro this again and get back to you... there may be some nuance I'm not noticing. By: Brian West (bkw918) 2004-10-24 00:55:37 Any update? By: chadscott (chadscott) 2004-10-26 02:08:26 Sorry for the delay. After running several test cases, I can't seem to replicate this anymore. Apparently this isn't my week for accurate bug reporting. :| | ||