[asterisk-bugs] [JIRA] (ASTERISK-30182) res_geolocation: Add built-in profiles to use in fully dynamic configurations

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260095#comment-260095 ] 

Friendly Automation commented on ASTERISK-30182:
------------------------------------------------

Change 19190 merged by Friendly Automation:
res_geolocation:  Add built-in profiles

[https://gerrit.asterisk.org/c/asterisk/+/19190|https://gerrit.asterisk.org/c/asterisk/+/19190]

> res_geolocation: Add built-in profiles to use in fully dynamic configurations
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-30182
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30182
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_geolocation
>    Affects Versions: 16.26.0, 18.13.0, 19.5.0
>            Reporter: George Joseph
>            Assignee: George Joseph
>
> 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.  
> Instead, we should create 4 built-in profiles named...
> "<prefer_config>"
> "<discard_config>"
> "<prefer_incoming>"
> "<discard_incoming>"
> which are blank except for the profile_disposition field which set according to the name.  Setting one of those (most probably "<discard_config>") on an endpoint will allow the processing without the need to configure a profile in the conf file.



--
This message was sent by Atlassian JIRA
(v6.2#6252)