[4.3] SUPP-22: do not normalize number if there is no dialplan or capture group #6632
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
…ture group (#6632) Do not normalize number if there is no dialplan or number is not from capture group when callflow wins the call. Normalizing twice may result the number to be classified differently so call won't be restricted.
jamesaimonetti
force-pushed
the
SUPP-22-4.3
branch
from
0996417
to
74e12ed
Compare
kageds
pushed a commit
to kageds/kazoo
that referenced
this pull request
Sep 24, 2020
…ture group (2600hz#6632) Do not normalize number if there is no dialplan or number is not from capture group when callflow wins the call. Normalizing twice may result the number to be classified differently so call won't be restricted.
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.
Do not normalize number if there is no dialplan or number is not from capture group when callflow wins the call.
Normalizing twice may result the number to be classified differently so call won't be restricted.