<br><br><div class="gmail_quote">On Wed, Mar 17, 2010 at 11:29 AM, Mark Sobkow <span dir="ltr"><<a href="mailto:m.sobkow@marketelsystems.com">m.sobkow@marketelsystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As per Andrew Thompson's suggestion, I changed the processing of the<br>
call recording to start recording as part of processing a CHANNEL_BRIDGE<br>
event. It turns out that (at least with Erlang) the call is not<br>
actually bridged when the api command to bridge a call returns ok; the<br>
ok only means the bridge command was successfully queued for processing,<br>
not that it's completed.<br>
<br>
I guess I wouldn't call this a bug with call recording, but it's<br>
definitely a "gotcha".<br></blockquote><div><br>Nope, not a bug - that's by design. The transmission of the CHANNEL_BRIDGE event means it was successful. The OK+ from the API call to bridge simply means that the bridge command was successfully submitted for processing, not that the processing of it was successful. This is the power, beauty, and elegance of the event system in FS. Events tell you pretty much *everything* that is going on and you can pretty much do *anything* when you harness the power of events.<br>
-MC<br><br></div></div>