On 05/09/2013 08:16 AM, Dan Cropp wrote: > I believe you will have to monitor for the Newexten event, then send an > AMI Getvar command. > > It doesn’t make sense to pass all the possible channel variables along > with a Newexten event. There may be a ton of extra variables that > someone may not want or need on the AMI. Better to have them ask for > specific variables that are not standard. > > > > Action: Getvar > > ActionID: ValueYouCanIdentify > > Channel: IAX2/X.X.X.X:4572-5011 > > Variable: fu_callerid > > > > This will result in a response from AMI… > > > > Response: Success > > ActionID: ValueYouCanIdentify > > Variable: fu_callerid > > Value: 141688xyxzz > > > > The ActionID is very important if you want to watch for an exact response to > your request. >
If you know the names of the channel variables, you can also configure manager to send them with every channel event. >From manager.conf: ; ; Display certain channel variables every time a channel-oriented ; event is emitted: ; ;channelvars = var1,var2,var3 So if you want fu_callerid, set: channelvars = fu_callerid And, once that variable is set, you should get a NewExten event, you should see the following key/value pair: ChanVariable(SIP/1234-00000001): fu_callerid=foobar -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
