[asterisk-app-dev] Question on implementation of "assigned" uniqueid when creating channels.

[Scott Griepentrog]

These changes have been completed and tested (minus recording which already
has a user supplied id in the filename).  Here are the reviewboard posts:

Main code (large, sorry):  https://reviewboard.asterisk.org/r/3191/

AMI originate test: https://reviewboard.asterisk.org/r/3243/

Starpy change required for AMI originate test:
https://reviewboard.asterisk.org/r/3242/

ARI tests (originate, bridge, playback, snoop):
https://reviewboard.asterisk.org/r/3277/ (includes upgrades to ari.py to
provide full test-config.yaml based ARI testing)

Incidental testsuite improvements discovered along the way:

Better yaml error reporting: https://reviewboard.asterisk.org/r/3287/

Fix for version check zombies: https://reviewboard.asterisk.org/r/3258/



On Mon, Mar 3, 2014 at 2:27 PM, Paul Belanger
<paul.belanger at polybeacon.com>wrote:

> On Mon, Mar 3, 2014 at 2:47 PM, Scott Griepentrog
> <sgriepentrog at digium.com> wrote:
> >
> > As an update, the following plan is being implemented (resulting from a
> combination of comments on app-dev and on reviewboard):
> >
> > For each object type (channels, bridge, playback, recording, snoop)
> there will be a:
> >
> > POST /objecttype/specifiedid
> >
> > operation that will create the object with that ID.  The
> >
> > POST /objecttype
> >
> > will also create the object, but will use the previously existing unique
> id creation method.  It will also have the optional objectId query
> parameter to allow it to be specified (since there are already two methods
> defined in the code, and it makes reusing existing libraries more
> convenient by adding a param instead of changing the URI processing).
> >
> > For the channels object type, there is a query parameter otherChannelId
> which provides the name for the second channel when originating with a
> Local channel.  If otherChannelId is not specified, but a uniqueid for the
> first channel is given, the second channel will be assigned the same value
> with a ;2 suffix (matching the channel name convention).
> >
> > The AMI implementation of channel origination matches ARI except that
> there is one origination method with two optional parameters, ChannelId and
> OtherChannelId.
> >
> > Also: in both AMI and ARI, the otherChannelId value is ignored if
> channelId is not specified.
> >
> +1
>
> --
> Paul Belanger | PolyBeacon, Inc.
> Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
> Github: https://github.com/pabelanger | Twitter:
> https://twitter.com/pabelanger
>
> _______________________________________________
> asterisk-app-dev mailing list
> asterisk-app-dev at lists.digium.com
> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
>



-- 
[image: Digium logo]
Scott Griepentrog
Digium, Inc · Software Developer
445 Jan Davis Drive NW · Huntsville, AL 35806 · US
direct/fax: +1 256 428 6239 · mobile: +1 317 507 4029
Check us out at: http://digium.com · http://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20140304/dcca73c5/attachment.html>