George,
Is it possible to set the GEOLOC_PROFILE fields similar to the way
PJSIP_HEADER(add, …) works?
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@192.168.12.34
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
Oh, for now, you can also use something like this to conditionally set an
element:
${IF(${EXISTS(${MyA3})}?A3=${MyA3})}
On Mon, Aug 15, 2022 at 9:57 AM George Joseph wrote:
> The email was getting too long for the mailing list so I've truncated it.
> Anyway...
>
> Dan, Have you tried using the
The email was getting too long for the mailing list so I've truncated it.
Anyway...
Dan, Have you tried using the GEOLOC_PROFILE dialplan function to create a
profile on the fly? I'm not sure how this would fit into your use of
Originate but...
Create a dummy geoloc profile.
[]
type=profile
prof
On Sat, Aug 13, 2022 at 1:48 PM Michael Maier wrote:
> Hello,
>
> I'm getting
>
> Error 1016 Ray ID: 73a2e9e50d869bb2 • 2022-08-13 16:44:07 UTC
> Origin DNS error
>
> when calling https://blogs.asterisk.org
>
> Coul you please take a look?
>
The current URL for the Asterisk blog is https://www
On Sat, Aug 13, 2022 at 3:55 PM Dan Cropp wrote:
> Thank you George.
>
>
>
> rc2 did fix the issue.
>
Whew.
>
>
> I am now able to program the variables in the location_info and pass
> values via the AMI Originate variables.
>
>
>
> Is there a way to make the location_info optional?
>
I _beli
