<div dir="ltr"><font face="arial, sans-serif">Thanks! </font><span style="font-family:arial,sans-serif;font-size:13px">Matthew and Dan. </span></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 9, 2013 at 10:18 PM, Matthew Jordan <span dir="ltr"><<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 05/09/2013 08:16 AM, Dan Cropp wrote:<br>
> I believe you will have to monitor for the Newexten event, then send an<br>
> AMI Getvar command.<br>
><br>
> It doesn’t make sense to pass all the possible channel variables along<br>
> with a Newexten event. There may be a ton of extra variables that<br>
> someone may not want or need on the AMI. Better to have them ask for<br>
> specific variables that are not standard.<br>
><br>
><br>
><br>
> Action: Getvar<br>
><br>
> ActionID: ValueYouCanIdentify<br>
><br>
> Channel: IAX2/X.X.X.X:4572-5011<br>
><br>
> Variable: fu_callerid<br>
><br>
><br>
><br>
> This will result in a response from AMI…<br>
><br>
><br>
><br>
> Response: Success<br>
><br>
> ActionID: ValueYouCanIdentify<br>
><br>
> Variable: fu_callerid<br>
><br>
> Value: 141688xyxzz<br>
><br>
><br>
><br>
> The ActionID is very important if you want to watch for an exact response to your request.<br>
><br>
<br>
</div></div>If you know the names of the channel variables, you can also configure<br>
manager to send them with every channel event.<br>
<br>