[asterisk-users] [External] Geo location 18.14.0-rc1 question

[George Joseph]

On Mon, Aug 15, 2022 at 3:07 PM Dan Cropp <dan at amtelco.com> wrote:

> George,
>
>
>
> Is it possible to set the GEOLOC_PROFILE fields similar to the way
> PJSIP_HEADER(add, …) works?
>

I can try but unlike the HEADER functions, the profile has multiple levels
of name/value pairs so it might take a bit of work and testing.   Let me
finish the other things first then I'll evaluate this.


>
>
> Asking, because we already use the PJSIP_HEADER(add, xxx) from AMI
> Originate to add PJSIP headers to the outbound originate.
>
>
>
>
>
> Action: Originate
>
> ActionID: S62
>
> Channel: PJSIP/1234 at 192.168.12.34
>
> Exten: createcall
>
> Context: mycontext
>
> Priority: 1
>
> Timeout: 60000
>
> CallerID: John Smith <8005551212>
>
> Variable:
> PJSIP_HEADER(add,abc)=123,CALLERID(num-pres)=allowed_passed_screen
>
> Async: true
>
> Codecs: ulaw
>
>
>
> Dan
>
>
>
>
>
>
>
> *From:* Dan Cropp
> *Sent:* Monday, August 15, 2022 2:00 PM
> *To:* Asterisk Users Mailing List - Non-Commercial Discussion <
> asterisk-users at lists.digium.com>
> *Subject:* RE: [External] [asterisk-users] Geo location 18.14.0-rc1
> question
>
>
>
> 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
>
>
>
> I believe this portion believe indicates Asterisk treats the
> GEOLOC_PROFILE(xxx) as GEOLOCPROFILESTATUS variable name.
>
>
>
> [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/883c50a3/attachment.html>