]> git.ipfire.org Git - thirdparty/asterisk.git/commit
res_geolocation: Add built-in profiles
authorGeorge Joseph <gjoseph@digium.com>
Tue, 16 Aug 2022 12:25:10 +0000 (06:25 -0600)
committerFriendly Automation <jenkins2@gerrit.asterisk.org>
Sat, 10 Sep 2022 16:04:43 +0000 (11:04 -0500)
commit1fc0298f87119b0da1982ca208aa9775d8d890c3
tree00d2161501b0a35c40da1771ba6288e877449a0f
parentfb11296a9b38f71923919ed493d23f11c97a3540
res_geolocation:  Add built-in profiles

The trigger to perform outgoing geolocation processing is the
presence of a geoloc_outgoing_call_profile on an endpoint. This
is intentional so as to not leak location information to
destinations that shouldn't receive it.   In a totally dynamic
configuration scenario however, there may not be any profiles
defined in geolocation.conf.  This makes it impossible to do
outgoing processing without defining a "dummy" profile in the
config file.

This commit adds 4 built-in profiles:
  "<prefer_config>"
  "<discard_config>"
  "<prefer_incoming>"
  "<discard_incoming>"
The profiles are empty except for having their precedence
set and can be set on an endpoint to allow processing without
entries in geolocation.conf.  "<discard_config>" is actually the
best one to use in this situation.

ASTERISK-30182

Change-Id: I1819ccfa404ce59802a3a07ad1cabed60fb9480a
configs/samples/geolocation.conf.sample
doc/CHANGES-staging/res_geolocation.txt [new file with mode: 0644]
res/res_geolocation/geoloc_config.c