<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Thanks for the quick response. I mistakenly assumed the create bridge command took a list of types. After taking a look at the swagger UI I figured out it was merely a list of acceptable values. I had an issue with de-serializing the json response which confused the matter. I wrote a custom deserializer and it works fine now.</div>
<div><br></div><div>Thanks for the example from your python code. I followed that example and it worked fine. Considering a bridge needs to be created for a simple dial application - do you see any pitfalls of creating a pool of bridges for the application to share - assuming I take care of the bridge-state internally?</div>
<div><br></div><div>Also... with ARI, I see no hooks into provisioning devices, I assume I need to use AMI <i>updateconfig</i>? Thanks!!!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 8 May 2014 14:43:17 -0500<br>
From: Samuel Galarneau <<a href="mailto:sgalarneau@digium.com">sgalarneau@digium.com</a>><br>
To: Asterisk Application Development discussion<br>
<<a href="mailto:asterisk-app-dev@lists.digium.com">asterisk-app-dev@lists.digium.com</a>><br>
Subject: Re: [asterisk-app-dev] ARI Bridge and Dial<br>
Message-ID:<br>
<CAGZGSQ7Z8AeP7VBvT1o_aRRJJDS+8zY2J=<a href="mailto:ubAqn-1hBDMLmOXA@mail.gmail.com">ubAqn-1hBDMLmOXA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Jim, please see my responses in line.<br>
<br>
<br>
> Hi,<br>
><br>
> I have a few questions regarding ARI after experimenting with it for a<br>
> while.<br>
><br>
> Bridging. When I create a bridge, I provide a single type ('mixing') I get<br>
> a '200' OK back but when I retrieve details on the bridge, the type 'list'<br>
> is NULL. The bridge seems to work - but I wanted to make sure there wasn't<br>
> an issue.<br>
><br>
<br>
What do you mean by type 'list'? What ARI operation are you using to get<br>
details for the bridge?<br>
<br>
<br>
><br>
> Let's say I want to create a simple Dial application. By trial and error,<br>
> what seems to work is a call comes into my dial plan and off to my app. I<br>
> answer, create a bridge and add this channel to the bridge. I then create a<br>
> channel for the destination SIP when it picks-up and add this to the<br>
> bridge. I should now have 2 connected phones. Thanks!!<br>
><br>
<br>
This sounds about right. After the first channel enters your application,<br>
you need to originate a call to the second channel and then put them both<br>
in the bridge. Once that is done, getting the details of that bridge will<br>
show both channels under the channels property, which will be an array of<br>
channel ids. Please see<br>
<a href="https://github.com/asterisk/ari-py/blob/master/examples/originate_example.pyfor" target="_blank">https://github.com/asterisk/ari-py/blob/master/examples/originate_example.pyfor</a><br>
an example of how to do this using ari-py. The same functionality<br>
could<br>
be accomplished by making direct calls to ARI of course.<br>
<br>
<br>
Samuel Fortier-Galarneau<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20140508/f4902357/attachment-0001.html" target="_blank">http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20140508/f4902357/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
asterisk-app-dev mailing list<br>
<a href="mailto:asterisk-app-dev@lists.digium.com">asterisk-app-dev@lists.digium.com</a><br>
<a href="http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev" target="_blank">http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev</a><br>
<br>
<br>
End of asterisk-app-dev Digest, Vol 8, Issue 3<br>
**********************************************<br>
</blockquote></div><br></div></div>