Long messages get split incorrectly

[tomngo]

Summary

Long messages get split incorrectly by Restcomm.

• Each message has unexpected extra bytes at the start of its text. This part is 100% repeatable.
• Often some pieces are missing. This part is sporadic.

Impact

Every message that long enough to be split into parts is affected.

I believe there is no workaround, but am obviously open to it.

Isolated to Restcomm

I've changed every variable outside of Restcomm, and the behavior is identical:

• The same thing happens when the message is sent from my handset (on T-Mobile) through a Restcomm instance, whether that Restcomm instance is tied to Teli ([email protected]), or to Hook ([email protected]).
• The same thing happens when the message is sent from my Google Voice line through a Restcomm instance, whether that Restcomm instance is tied to Teli ([email protected]), or to Hook ([email protected]).
• A message carrying an identical string arrives intact if sent from my handset to my Google Voice line without going through Restcomm, or vice versa.
• The corruption is visible in the Restcomm logs, i.e., before reaching our platform.

Examples

Well, wouldn’t you know it. They’ve changed the schedule again. I can do 11/21 at noon.

• Restcomm via Hook: SmsSid SMfe423584b54249f8a8ac1269d770070e and SM61f436dd78bb419b938d704fdb9e5880 (originally one message)
• Restcomm via Teli: SmsSid SM3f18c0c6b30f4faeb47b103f016370d4 and SM6c34a40bd7ba40ac85f70870235c8b29 (originally one message)

My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe. My name is Joe.

• Restcomm via Hook: SmsSid SM7536e05ab049433fb1330855ac027637 and SM603995c7faa848af9443861144df77ea (originally one message)
• Restcomm via Teli: SmsSid SM05567b3538124365bd8376cb86ea5e97 and SM3db77067758d4a31b181dc5b23ddb0da (originally one message)

[nhanth87]

Hello,
We have fixed the stranger character at beginning of splited SMS. You will have it in next release