Documentation says that StopMixMonitor "Stops the audio recording that was started with a call to MixMonitor() on the current channel", and I don't see a way to run Joe's channel through dialplan. Perhaps I am not understanding something here.

Anyway, this is just one example where pushable pre-bridge handlers would be useful. It seems to me that many things would be easier/possible if they were introduced. If nobody else finds them useful, I guess I am missing something.

On 17. 07. 2020. 14:45, Jim Van Meggelen wrote:
Pass stopmixmonitor the mixmonitorid of Joe's channel.

I'll admit it might end up being somewhat kludgy, but I figure a database can keep track of all that for you, so it's just a query at the right moment, and then passing the correct mixmonitorid in the local channel.

I can tell you this: if you need new functionality built into Asterisk, that's really only going to happen if you're willing to fund the development, or you can convince Sangoma there's a business case.




On Fri, Jul 17, 2020 at 8:17 AM Nikša Baldun <i...@voxdiversa.hr <mailto:i...@voxdiversa.hr>> wrote:

    Hello Jim,

    thanks for the reply. Consider the following scenario:

    Joe calls Mary and asks to speak to Jill. Recording a call with
    Mary is allowed, so recording on Joe's channel is turned on. Mary
    makes an attended transfer to Jill. Both Mary's channels are hung
    up, and Joe's and Jill's channels are now bridged. Recording a
    call with Jill is not allowed, so StopMixMonitor should be
    executed on Joe's channel before bridging. How can Local channel
    help me do that?

    For the specific use case you've described, I should think a Local/ channel
    could be built to implement the necessary logic. In fact I'm pretty sure we
    do that in our Local/ channel handler for queue agents.



    On Fri, Jul 17, 2020 at 5:04 AM Nikša Baldun <it at voxdiversa.hr  
<http://lists.digium.com/mailman/listinfo/asterisk-dev>> wrote:

    >/Hello, />//>/I have been using Asterisk for years, and the one thing that 
I
    believe />/is sorely missing, but I can't find any mention of it on the
    Internet, />/and that is pushable pre-bridge handlers. In current setup,
    there are />/following limitations: />//>/1. Pre-bridge handler can only be 
attached to the B-leg channel,
    not the />/A-leg channel. />//>/2. The handler will only be executed before 
a bridge resulting
    from Dial />/application, but a channel can be bridged multiple times during its 
/>/lifetime (by SIP attended transfer, for example). />//>/So, for example, if I 
want to turn call recording on/off
    depending on />/who the channel is bridged to, there is no way to do that 
via
    dialplan />/(that I know of). />//>/There is a possibility to attach hangup 
handlers to any channel
    by using />/CHANNEL(hangup_handler_push), but no similar feature for 
pre-bridge />/handlers, which are much more important, IMO. So, has there been
    any />/discussion among developers about this topic? />//>/Best regards. 
/>//>//>/-- />/_____________________________________________________________________
    />/-- Bandwidth and Colocation Provided by
    http://www.api-digital.com <http://www.api-digital.com/> -- />//>/asterisk-dev 
mailing list />/To UNSUBSCRIBE or update options visit: 
/>/http://lists.digium.com/mailman/listinfo/asterisk-dev /


-- _____________________________________________________________________
    -- Bandwidth and Colocation Provided by http://www.api-digital.com --

    asterisk-dev mailing list
    To UNSUBSCRIBE or update options visit:
    http://lists.digium.com/mailman/listinfo/asterisk-dev


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to