Dan Cropp
2022-Aug-23 20:47 UTC
[asterisk-users] I think there may be a bug in 18.14.0 ${GEOLOC_PROFILE(profile_precedence)}, seems to always return prefer_incoming
Running into a problem when retrieving the profile_precedence in the extensions.conf Creating a very basic geolocation.conf to allow passing through geolocation values for outbound. [discard_config] type = profile profile_precedence = discard_config [discard_incoming] type = profile profile_precedence = discard_incoming [prefer_config] type = profile profile_precedence = prefer_config [prefer_incoming] type = profile profile_precedence = prefer_incoming I have tried setting the pjsip.conf geoloc_incoming_call_profile to all four of these profiles for inbound call testing. The discard_incoming correctly blocks the geo location information. Other 3 pass the geo location values through [192.168.33.31] type = endpoint context = IS transport = transport1 aors = 192.168.33.31 accountcode = 20 dtmf_mode = inband device_state_busy_at = 1600 moh_passthrough = no identify_by = username,ip,header disallow = all allow = ulaw acl = acl1 geoloc_incoming_call_profile = prefer_config geoloc_outgoing_call_profile = prefer_config When I have the following line in the extensions.conf, it's retrieving the GEOLOC_PROFILE(profile_precedence) to the variable, but it's being set to prefer_incoming even when it should be discard_config or prefer_config. same => n,Set(MY__GEO_PROFILE_PRECEDENCE=${GEOLOC_PROFILE(profile_precedence)}) Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20220823/7bc50a6c/attachment.html>
George Joseph
2022-Aug-24 13:51 UTC
[asterisk-users] I think there may be a bug in 18.14.0 ${GEOLOC_PROFILE(profile_precedence)}, seems to always return prefer_incoming
Yeah, that's weird. I opened an issue for this... https://issues.asterisk.org/jira/browse/ASTERISK-30190 On Tue, Aug 23, 2022 at 2:47 PM Dan Cropp <dan at amtelco.com> wrote:> Running into a problem when retrieving the profile_precedence in the > extensions.conf > > > > Creating a very basic geolocation.conf to allow passing through > geolocation values for outbound. > > > > [discard_config] > > type = profile > > profile_precedence = discard_config > > > > [discard_incoming] > > type = profile > > profile_precedence = discard_incoming > > > > [prefer_config] > > type = profile > > profile_precedence = prefer_config > > > > [prefer_incoming] > > type = profile > > profile_precedence = prefer_incoming > > > > > > I have tried setting the pjsip.conf geoloc_incoming_call_profile to all > four of these profiles for inbound call testing. The discard_incoming > correctly blocks the geo location information. Other 3 pass the geo > location values through > > > > [192.168.33.31] > > type = endpoint > > context = IS > > transport = transport1 > > aors = 192.168.33.31 > > accountcode = 20 > > dtmf_mode = inband > > device_state_busy_at = 1600 > > moh_passthrough = no > > identify_by = username,ip,header > > disallow = all > > allow = ulaw > > acl = acl1 > > geoloc_incoming_call_profile = prefer_config > > geoloc_outgoing_call_profile = prefer_config > > > > When I have the following line in the extensions.conf, it’s retrieving the > GEOLOC_PROFILE(profile_precedence) to the variable, but it’s being set to > prefer_incoming even when it should be discard_config or prefer_config. > > > > same => > n,Set(MY__GEO_PROFILE_PRECEDENCE=${GEOLOC_PROFILE(profile_precedence)}) > > > > 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/20220824/87cc82e2/attachment.html>