On Mon, Dec 9, 2013 at 4:32 PM, David M. Lee <dlee@xxxxxxxxxx> wrote: > > On Dec 9, 2013, at 4:14 PM, Richard Mudgett <rmudgett@xxxxxxxxxx> wrote: > > On Mon, Dec 9, 2013 at 3:09 PM, David M. Lee <dlee@xxxxxxxxxx> wrote: >> >> >> On Dec 6, 2013, at 3:43 PM, Matthew Jordan <mjordan@xxxxxxxxxx> 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. > As a follow up to this thread, ASTERISK-23120 was created for this improvement: https://issues.asterisk.org/jira/browse/ASTERISK-23120 -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org _______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
