[asterisk-users] [External] [External] [External] [External] Geo location 18.14.0-rc1 question
Joshua C. Colp
jcolp at sangoma.com
Fri Aug 12 08:04:12 CDT 2022
On Fri, Aug 12, 2022 at 10:01 AM George Joseph <gjoseph at sangoma.com> wrote:
>
>
> On Thu, Aug 11, 2022 at 8:43 AM Dan Cropp <dan at amtelco.com> wrote:
>
>> Thank you George.
>>
>>
>>
>> I am still running on asterisk 18.14.0-rc1 and have not retrieved the
>> patches yet.
>>
>> Did this version have a bug with the variables?
>>
>
> It's quite possible. RC2 was just released so you should try that.
>
>>
>>
>> I’m trying the location_info and variables in the AMI Originate you
>> recommended at the end of the previous e-mail.
>>
>>
>>
>> In case it’s not coming through correctly via e-mail, the variable names
>> are preceeded with a single underscore in the AMI and in the location_info
>> values.
>>
>>
>>
>>
>>
>> [IS_loc_5]
>>
>> type = location
>>
>> format = civicAddress
>>
>> location_info = country=${_MY_GEO_COUNTRY}
>>
>> location_info = A1=${_MY_GEO_NATIONAL_SUBDIVISION}
>>
>> location_info = A2=${_MY_GEO_NATSUB}
>>
>> location_info = A3=${_MY_GEO_CITY}
>>
>> location_info = HNO=${_MY_GEO_HNO}
>>
>> location_info = RD=${_MY_GEO_RD}
>>
>> location_info = STS=${_MY_GEO_STS}
>>
>> location_info = PC=${_MY_GEO_PC}
>>
>
Underscore refers to variable inheritance. For usage you don't include the
underscore. I don't think the code strips out the underscore when
substituting or retrieving, so it could very well end up empty during that
process.
--
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20220812/359e63b3/attachment.html>
More information about the asterisk-users
mailing list