George Joseph
2022-Aug-16 12:48 UTC
[asterisk-users] [External] Geo location 18.14.0-rc1 question
On Mon, Aug 15, 2022 at 1:59 PM Dan Cropp <dan at amtelco.com> wrote:> Thank you George. > > > > Good idea on the passthrough profile. > > > > Is there a way to set the GEOLOC_PROFILE values from the AMI Originate > command? > > > > I tried the following, but it doesn’t like the GEOLOC_PROFILE values in > the variable parameter. If there is a way to do this, the passthrough > would solve the problem of Geo Location information settings needing to be > provided by a third-party application. > > > > Action: Originate > > Channel: PJSIP/1234 at 192.168.33.31 > > Exten: createcall > > Context: mycontext > > Priority: 1 > > Timeout: 60000 > > CallerID: John Smith <8005551234> > > Variable: > GEOLOC_PROFILE(format)=civicAddress,GEOLOC_PROFILE(method)=Manual,GEOLOC_PROFILE(location_info) > *==* > "country=US,A1=Florida,A3=Orlando,HNO=100,RD=Main,STS=Street",CALLERID(num-pres)=allowed_passed_screen > > Async: true > > >You've got 2 equals signs when you set location_info :). I just tried GEOLOC_PROFILE(format)=civicAddress,GEOLOC_PROFILE(location_info)="country=US,A3=\"New York\"",GEOLOC_PROFILE(pidf_element)=device and it worked. I believe this portion believe indicates Asterisk treats the> GEOLOC_PROFILE(xxx) as GEOLOCPROFILESTATUS variable name. >GEOLOCPROFILESTATUS is the variable GEOLOC_PROFILE sets to indicate success or failure. The value of "0" indicates success. What was the actual result in the channel?> > > [08/15 13:41:41.609] DEBUG[42424] manager.c: Examining AMI event: > > Event: VarSet^M > > Privilege: dialplan,all^M > > Channel: PJSIP/192.168.33.31-00000000^M > > ChannelState: 0^M > > ChannelStateDesc: Down^M > > CallerIDNum: <unknown>^M > > CallerIDName: <unknown>^M > > ConnectedLineNum: <unknown>^M > > ConnectedLineName: <unknown>^M > > Language: en^M > > AccountCode: 20^M > > Context: IS^M > > Exten: s^M > > Priority: 1^M > > Uniqueid: 1660588901.0^M > > Linkedid: 1660588901.0^M > > Variable: GEOLOCPROFILESTATUS^M > > Value: 0^M > > ^M > > > > Dan > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Check out the new Asterisk community forum at: > https://community.asterisk.org/ > > New to Asterisk? Start here: > https://wiki.asterisk.org/wiki/display/AST/Getting+Started > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20220816/5b1cc5ff/attachment.html>
Dan Cropp
2022-Aug-16 14:07 UTC
[asterisk-users] [External] [External] Geo location 18.14.0-rc1 question
Thank you George. As you pointed out, my mistake of the double equal sign caused the problem. Using the passthrough profile and in the AMI Originate setting the Variable: GEOLOC_PROFILE(name) is exactly what we need. My software will receive the GEO settings from third party software. If third party passed a field/value that doesn’t match the Asterisk defaults, our software will add the GEOLOC_PROFILE(name) to the Originate Variable field. Then I send the Originate packet to Asterisk via AMI. Thank you for all your work on this!!! Dan From: asterisk-users <asterisk-users-bounces at lists.digium.com> On Behalf Of George Joseph Sent: Tuesday, August 16, 2022 7:49 AM To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users at lists.digium.com> Subject: Re: [External] [asterisk-users] [External] Geo location 18.14.0-rc1 question On Mon, Aug 15, 2022 at 1:59 PM Dan Cropp <dan at amtelco.com<mailto:dan at amtelco.com>> wrote: Thank you George. Good idea on the passthrough profile. Is there a way to set the GEOLOC_PROFILE values from the AMI Originate command? I tried the following, but it doesn’t like the GEOLOC_PROFILE values in the variable parameter. If there is a way to do this, the passthrough would solve the problem of Geo Location information settings needing to be provided by a third-party application. Action: Originate Channel: PJSIP/1234 at 192.168.33.31<mailto:1234 at 192.168.33.31> Exten: createcall Context: mycontext Priority: 1 Timeout: 60000 CallerID: John Smith <8005551234> Variable: GEOLOC_PROFILE(format)=civicAddress,GEOLOC_PROFILE(method)=Manual,GEOLOC_PROFILE(location_info)=="country=US,A1=Florida,A3=Orlando,HNO=100,RD=Main,STS=Street",CALLERID(num-pres)=allowed_passed_screen Async: true You've got 2 equals signs when you set location_info :). I just tried GEOLOC_PROFILE(format)=civicAddress,GEOLOC_PROFILE(location_info)="country=US,A3=\"New York\"",GEOLOC_PROFILE(pidf_element)=device and it worked. I believe this portion believe indicates Asterisk treats the GEOLOC_PROFILE(xxx) as GEOLOCPROFILESTATUS variable name. GEOLOCPROFILESTATUS is the variable GEOLOC_PROFILE sets to indicate success or failure. The value of "0" indicates success. What was the actual result in the channel? [08/15 13:41:41.609] DEBUG[42424] manager.c: Examining AMI event: Event: VarSet^M Privilege: dialplan,all^M Channel: PJSIP/192.168.33.31-00000000^M ChannelState: 0^M ChannelStateDesc: Down^M CallerIDNum: <unknown>^M CallerIDName: <unknown>^M ConnectedLineNum: <unknown>^M ConnectedLineName: <unknown>^M Language: en^M AccountCode: 20^M Context: IS^M Exten: s^M Priority: 1^M Uniqueid: 1660588901.0^M Linkedid: 1660588901.0^M Variable: GEOLOCPROFILESTATUS^M Value: 0^M ^M Dan -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20220816/9b96dde1/attachment-0001.html>