RESTCOM-1927: Workaround, hardcode submit_sm encoding to UTF-8 #2877
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
abdulazizali77
force-pushed
the
RESTCOMM-1927
branch
from
10229a5
to
9ff37f9
Compare
abdulazizali77
force-pushed
the
RESTCOMM-1927
branch
2 times, most recently
from
82cef66
to
4ffd579
Compare
gvagenas
force-pushed
the
RESTCOMM-1927
branch
from
4ffd579
to
2ecf8ed
Compare
gvagenas
force-pushed
the
master
branch
2 times, most recently
from
9469191
to
c67f142
Compare
gvagenas
force-pushed
the
RESTCOMM-1927
branch
from
2ecf8ed
to
79ff863
Compare
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.
What this PR does / why we need it:
Hardcode outgoing SMS encoding to UTF-8 for Provider
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #RESTCOMM-1927
Special notes for your reviewer:
Theres an ongoing support ticket with our main Provider and some special characters are still not encoded properly eg \u20ac