Run CLASSIFY_SOURCE prior to FILTER_REQUEST in default.cfg #137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Execute CLASSIFY_SOURCE route prior to FILTER_REQUEST route FILTER_REQUEST route checks for FLAG_TRUSTED_SOURCE which only gets set in CLASSIFY_SOURCE. This will cause INVITES from trusted IPs to be dropped, if the request domain is an IP address, which is the case with some carriers.
mooseable
changed the title
mooseable
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Execute CLASSIFY_SOURCE route prior to FILTER_REQUEST route
FILTER_REQUEST route checks for FLAG_TRUSTED_SOURCE which only gets set in CLASSIFY_SOURCE.
This will cause INVITES from trusted IPs to be dropped, if the request domain is an IP address, which is the case with some carriers.
Also discussed in https://forums.2600hz.com/forums/topic/11601-populating-trusted-ips-for-traffic_filter_role/