On Dec 9, 2013, at 4:14 PM, Richard Mudgett <rmudgett at digium.com> wrote: > On Mon, Dec 9, 2013 at 3:09 PM, David M. Lee <dlee at digium.com> wrote: > > On Dec 6, 2013, at 3:43 PM, Matthew Jordan <mjordan at digium.com> wrote: > >> With everything but channels, having an external actor provide the UUID for the resource being created shouldn't be a problem. Going down the list: >> * Bridges - currently have a UUID assigned during creation by the Bridging Framework. We'd have to add a new creation function that allows for the UUID to be passed in, but that's probably about it. > > This really isn?t a problem, since a bridge doesn?t generate any events until you put a channel into it. And you can only do that after the create call succeeds, at which point you have the bridge id. > > The bridge creation event is generated immediately on bridge creation. It is not generated when the first channel enters a bridge. That event won?t get sent out the ARI WebSocket unless an application is subscribed to it. That happens either with an explicit subscription, or when a channel is added to the bridge. -- David M. Lee Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20131209/31e2a6d9/attachment.html>
