I am unable to send SMS's exceeding 160 characters even after setting the Property: "Max. No of SMSes per message" to 2 in the Delivery Activity as shown in the below screenshot.
My message text is
Today is quite sunny. What's your plan to celebrate today?
Workout or healthy lunch? Or both?
Make your day better by listening music or dancing or painting.
From XXX Campaign Service team
Within the Audit log, I am getting error : The SMS message content is too long. It contains 267 characters whereas the maximum authorized is 160.
I am able to send SMS having content within the 160 char. limit. I am using SMPP setup.
Solved! Go to Solution.
Your text message is 234 chars (utf-8) without the emoticon.
The emoticon encoding is not 1 char but several chars (see ISO table encoding of emoticons).
Moreover, when you submit a proof it adds some extra chars ("[FCP] " by default so 6 chars).
Try by putting 3 SMS per message please.
Hope this helps.
It rather looks like a warning from a typology rule 'Message Size validation ' than an error during the delivery analysis.
Can you share the error log in the delivery logs.
Thanks for your response.
I increased the Max. Number of messages per SMSes to 4. Even then, I am getting the same error.
Unable to understand the root cause.
There were no errors in the delivery logs. Not sure if there are any errors @ mid-sourcing for delv: DM302747.
As you suspected, the default typology rule:Message size validation is possibly restricting the delivery. As, I received a SMS after removing this rule from the typology. However, I have few further queries in this regard:
1. What could be the possible implications of removing this rule? Is it required to modify the default code used in it?
2. I received single message for this SMS instead of two. Like to understand the expected behaviour in such cases.
3. The status of Delivery and Delivery Logs were "Being Edited" and "Pending" respectively after 2 hours of receiving this message. Would like to discuss it as well.