<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=utf-8">
<meta name=Generator content="Microsoft Word 12 (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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ryan one more thing I want to see is a call recording feature
from GUI if possible you can add it in lists of things to do (if not already added),
and a question again (sorry ) how we can install Asterisk-GUI on AsteriskNow
1.5 beta which has Freepbx instead?<o:p></o:p></span></p>
<div>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'>Regards,<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'>Rajesh Kumar<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'><a href="mailto:raj@alshaya-group.com"><span style='color:blue'>raj@alshaya-group.com</span></a><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'>Alshaya Group International<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'>Tel: +965 298-0555 Ext.- 307<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#548DD4'>Mobile: +965 722-4083<o:p></o:p></span></b></p>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
asterisk-gui-bounces@lists.digium.com
[mailto:asterisk-gui-bounces@lists.digium.com] <b>On Behalf Of </b>Ryan Brindley<br>
<b>Sent:</b> Wednesday, March 25, 2009 9:10 PM<br>
<b>To:</b> Asterisk GUI project discussion<br>
<b>Subject:</b> Re: [asterisk-gui] On Trunks and Incoming Calling Rules<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>Marvin,<br>
Cool. Thanks for the input!<br>
<br>
--
<br>
Ryan Brindley
<br>
Digium, Inc. | Software Developer
<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
<br>
main: +1 256-428-6000 fax: +1 256-864-0464
<br>
Check us out at: http://digium.com & http://asterisk.org<br>
<br>
----- Original Message -----<br>
From: "Marvin Whitfield" <marvin.whitfield@gmail.com><br>
To: "Asterisk GUI project discussion"
<asterisk-gui@lists.digium.com><br>
Sent: Wednesday, March 25, 2009 12:57:26 PM GMT -06:00 US/Canada Central<br>
Subject: Re: [asterisk-gui] On Trunks and Incoming Calling Rules<br>
<br>
Ryan,<br>
<br>
Not a bad idea at all. There's nothing else on that page so why not. I<br>
can't remember how deleting trunks currently affects incoming rules<br>
but I think it also deletes that context, but if not, adding incoming<br>
rules to the trunks page would also make that simpler...I think its a<br>
good idea.<br>
<br>
--<br>
Marvin<br>
<br>
On 3/25/09, Ryan Brindley <rbrindley@digium.com> wrote:<br>
> Hey guys,<br>
> I'm currently in the process of organizing the core code and came across
one<br>
> of the areas many users get confused with. Anyway, I was interested to
hear<br>
> the thoughts on the idea of moving 'Incoming Calling Rules' into the<br>
> 'Trunks' page. It makes sense to me as Incoming Calling Rules is limited<br>
> within the scope of Trunks. I would guess that creating incoming calling<br>
> rules is one of the most common thoughts just after an admin has created a<br>
> trunk, so having it right there would be that much easier.<br>
><br>
> --<br>
> Ryan Brindley<br>
> Digium, Inc. | Software Developer<br>
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
> main: +1 256-428-6000 fax: +1 256-864-0464<br>
> Check us out at: http://digium.com & http://asterisk.org<br>
><br>
<br>
<br>
-- <br>
Thank you,<br>
Marvin Whitfield<br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by http://www.api-digital.com--<br>
<br>
asterisk-gui mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
http://lists.digium.com/mailman/listinfo/asterisk-gui<o:p></o:p></span></p>
</div>
</div>
</body>
</html>