Comment 1 for bug 38210

Causing serious problems on my installation.

http://bugs.digium.com/view.php?id=7335&nbn=9

Claims it is fixed in SVN 34462 but I have no idea which release that corresponds too. Have not tested the fix.

Here is my transaction. However, where it shows the values coming back in order, I am actually only able to retrieve in one off order.

 -- Launched AGI Script /var/lib/asterisk/agi-bin/agistardead.agi
AGI Tx >> agi_request: agistardead.agi
AGI Tx >> agi_channel: SIP/2002-bd53
AGI Tx >> agi_language: en
AGI Tx >> agi_type: SIP
AGI Tx >> agi_uniqueid: asterisk-4771-1156401546.98
AGI Tx >> agi_callerid: unknown
AGI Tx >> agi_calleridname: lukas
AGI Tx >> agi_callingpres: 0
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 0
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: 18005551212
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: default
AGI Tx >> agi_extension: h
AGI Tx >> agi_priority: 1
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode:
AGI Tx >>
AGI Rx << Aug 24 07:39:28 WARNING[30315]: asterisk.c:807 ast_set_priority: Unable to set normal priority /* bogus command */
AGI Tx >> 510 Invalid or unknown command /* bogus result received after executing the next command */
AGI Rx << GET VARIABLE ANSWEREDTIME
AGI Tx >> 200 result=1 (10)
AGI Rx << GET VARIABLE DIALSTATUS
AGI Tx >> 200 result=1 (ANSWER)
AGI Rx << GET VARIABLE DIALEDTIME
AGI Tx >> 200 result=1 (22)
AGI Rx << GET VARIABLE BILLSTATUS
AGI Tx >> 200 result=0