<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html>
<head>
<meta http-equiv='Content-Type' content='text/html;charset=us-ascii'>
<style>BODY{font:10pt Tahoma, Verdana, sans-serif;}</style>
</head>
<body>
About a year ago, Mark Michelson introduced a helpful dialplan function called AUDIOHOOK_INHERIT which enables the dialplan writer to specify whether or not [an] audiohook(s) should propagate to a new channel during a masquerade. <br><br>I would like to start a discussion regarding the current behavior of audiohooks and more specifically whether audiohooks should propagate to the new channel during a masquerade by default. In my opinion, the edge cases are where the dialplan writer would not want audiohooks to propagate to the new channel during a masquerade. It is also my opinion that the average dialplan writer does not want to know which dialplan functions/applications/etc use audiohooks or masquerades under-the-hood.<br><br>My proposal is to merge the functionality of func_audiohookinherit.c into audiohook.c and to retain the AUDIOHOOK_INHERIT function for the edge cases where the dialplan writer wants to disable (or re-enable) the inheritance of audiohooks on a channel.<br><br>If the Asterisk community and Digium agree, I would be more than happy to provide the patch.<br><br>regards,<br>Dwayne Hubbard<br><br></body></html>