| Summary: | ASTERISK-22671: AUDIOHOOK_INHERIT Fails on Outbound Attended Transfer | ||
| Reporter: | Ross Beer (rossbeer) | Labels: | |
| Date Opened: | 2013-10-09 11:27:59 | Date Closed: | 2013-11-10 19:04:13.000-0600 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | Functions/func_audiohookinherit |
| Versions: | 1.8.23.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS 6.4 | Attachments: | |
| Description: | The AUDIOHOOK_INHERIT function fails when making an outgoing call and then transferring the call. The recording stops as soon as the REFER is received:
====== CLI INFO ====== [Oct 9 17:10:01] NOTICE[26668]: chan_sip.c:21171 handle_response_notify: Got OK on REFER Notify message == Spawn extension (from-vh-internal, d-ANSWER, 5) exited non-zero on 'SIP/<ACCOUNT>-000000b1' -- Executing [h@from-vh-internal:1] Hangup("SIP/<ACCOUNT>-000000b1", "") in new stack == Spawn extension (from-vh-internal, h, 1) exited non-zero on 'SIP/<ACCOUNT>-000000b1' == MixMonitor close filestream == Executing [mv /record/sip08-1381334954.179.wav /store/sip08-1381334954.179.wav] == End MixMonitor Recording SIP/<ACCOUNT>-000000b1 ======================= The dial plan has the following config: {code} exten => _.,n,MixMonitor(${crfile},b,mv ${crfile} /store/${crfile}) exten => _.,n,Set(AUDIOHOOK_INHERIT(MixMonitor)=yes) {code} This feature worked in the past however has stopped in recent versions. It appears that the inherit does not get copied to the outgoing channel leg which is bridged to the attended transfer location. | ||
| Comments: | By: Rusty Newton (rnewton) 2013-10-17 19:36:19.628-0500 Thanks for the report Ross, can you attach a full log showing the issue? Be sure both VERBOSE and DEBUG are enabled and turned up. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Matt Jordan (mjordan) 2013-11-10 19:04:01.709-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||