Didn't have a lot of luck frame copying directly from the channel. I imagine it has something to do with not being able to actually answer the spyee channel in snoop for blocking reasons.
Can I trouble you for one more clue: might extending Snoop with the Framehook API be an option? And then I imagine creating some sort of frame buffer (similar to the Audiohook's slin buffer) that snoop_read accesses at the same/similar interval internal?
Please forgive me if I'm overextending the purpose of this list, I'm newish to the world of Asterisk development at the source level and having a time just getting used to some of the general "givens" of the environment.
Also, FWIW, when I stripped out the Audiohook references from the Snoop driver, the CPU issue stopped showing up.
On Fri, Apr 3, 2015 at 4:43 PM, George Ladoff <georgeladoff@xxxxxxxxx> wrote:
Good to know, at least as a starting point. Thank you Joshua. Greatly appreciated.On Fri, Apr 3, 2015 at 4:41 PM, Joshua Colp <jcolp@xxxxxxxxxx> wrote:George Ladoff wrote:
Gotcha. In most cases I do just need to snoop one direction.
Do you mean that the audiohook API would work in the way I was hoping in
those cases? Or do you mean that I may have some options of altering the
audiohook API but only if that were the case?
I *think* it would be possible to extend the Snoop channel functionality so it would copy the frame as-is instead of turning it into signed linear, outside the audiohook API.
--
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org
_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@lists.digium.com
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
_______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
