<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">That makes sense!
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">At the end of the day, I should only be getting information I can do something about, by default. And yes, I agree that it makes
sense to incorporate some options for the filtering too.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Ben<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> asterisk-app-dev-bounces@lists.digium.com [mailto:asterisk-app-dev-bounces@lists.digium.com]
<b>On Behalf Of </b>Kinsey Moore<br>
<b>Sent:</b> 23 October 2013 22:06<br>
<b>To:</b> Asterisk Application Development discussion<br>
<b>Subject:</b> [asterisk-app-dev] ARI Global Data Accessibility Changes<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hello App Developers,<br>
We have been thinking about what information is exposed via the ARI requests for lists of channels (GET /ari/channels) and bridges (GET /ari/bridges). Currently, these requests return all information about any channel or bridge in the system.<br>
<br>
As an example, imagine you have channels SIP/Alice and SIP/Bob in the Stasis() application being bridged by ARI-created bridge Foo. In the same system, you also have channels SIP/Charlie and SIP/David being bridged by Dial()-created bridge DialBridge. When
you GET /ari/channels, you will receive:<br>
[<br>
{ "name": "SIP/Alice", ... },<br>
{ "name": "SIP/Bob", ... },<br>
{ "name": "SIP/Charlie", ... },<br>
{ "name": "SIP/David", ... }<br>
]<br>
<br>
When you GET /ari/bridges, you will receive:<br>
[<br>
{ "id": "Foo", ... },<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> { "id": "DialBridge", ... }<br>
]<br>
<br>
This situation is non-ideal since channels SIP/Charlie and SIP/David and bridge DialBridge can not be acted upon via ARI. We propose limiting these queries to channels and bridges which ARI can affect. In this case, the /ari/channels query would return:<br>
[<br>
{ "name": "SIP/Alice", ... },<br>
{ "name": "SIP/Bob", ... }<br>
]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The /ari/bridges query would return:<br>
[<br>
{ "id": "Foo", ... }<br>
]<br>
<br>
The rework would also include an optional filter parameter for ARI user or Stasis application to increase the available granularity.<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
Kinsey Moore<br>
Digium, Inc. | Software Developer<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - US <o:p></o:p></p>
</div>
</div>
</body>
</html>