login | register
Fri 09 of May, 2008 [19:44 UTC]

voip-info.org

Navigation
Today's Deals
Recently Visited Pages
Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Last Changes
Shoutbox
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
  • Christopher Faust, Wed 07 of May, 2008 [15:28 UTC]: When I try to startx I ge input not supported. Though before installing asterisk I had no video issue to start the GUI
  • Christopher Faust, Wed 07 of May, 2008 [15:26 UTC]: Hi Nick, I got centos 5.1 and asterisk up But now I cannot start startx I have set the depth from 24 to 16 for the video i810 driver for the i845 on my netvista machine but I cannot start GNOME. Please advise
  • Nick Barnes, Wed 07 of May, 2008 [10:01 UTC]: Howard - You'll need to provide a lot more information if you really want help.
  • Nick Barnes, Wed 07 of May, 2008 [10:00 UTC]: Christopher - Search the Wiki and you'll find a page I wrote detailing exactly what you have to do for Asterisk 1.4 + CentOS 5.1.
Server Stats
  • Execution time: 0.37s
  • Memory usage: 2.18MB
  • Database queries: 29
  • GZIP: Disabled
  • Server load: 1.70

get full variable

Usage: GET FULL VARIABLE <variablename> [<channel name>]

This is basically GET VARIABLE for "full" $-expressions:
  • GET FULL VARIABLE ${foo} is equivalent to GET VARIABLE foo
  • GET FULL VARIABLE ${func(bar)} is equivalent to GET VARIABLE func(bar)
  • GET FULL VARIABLE $[expr] has no GET VARIABLE equivalent

Note that in some bugged version of Asterisk 1.2, GET FULL VARIABLE was the only way to retrieve global dialplan variables.

Returns:
failure or not set: 200 result=0
success: 200 result=1 <value>

See also


Go back to Asterisk AGI
Created by pinhole, Last modification by waba on Tue 13 of Nov, 2007 [15:00 UTC]

Comments

Comments Filter

Return Buil-in Expression

by Alejandro Gonzalez on Thursday 14 of February, 2008 [19:31:43 UTC]
take care, isn't the same

GET FULL VARIABLE PBX_IN_DID SIP/7854-09c3f8c8

and

GET FULL VARIABLE ${PBX_IN_DID} SIP/7854-09c3f8c8

In first case GetFullVariable onli check if variable PBX_IN_DID exist (yust like say "200 result=1 (PBX_IN_DID) "), in the second case GetFullVariable construct the variable and return the content of PBX_IN_DID

what should I expect?

by George M. Zouganelis on Tuesday 07 of August, 2007 [17:23:04 UTC]
I am trying this with Asterisk v1.4.9, but it returns as value, the requested variable name:

GET FULL VARIABLE PBX_IN_DID SIP/7854-09c3f8c8

and I get

200 result=1 (PBX_IN_DID)

Is this a bug ?

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:
Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver