SMS Message Length

[FASTDEVICE]

I have a question regarding the message length of SMS. I see the length following the 160 character limit before being split. However, when messages are larger than 160, they are following the 153 segment split but are not being rebuilt by the recipients device as a single message.  They come in as multipart messages. Any thoughts as to why or what should be done to enforce the device to rebuild as a single message? 

[lazedo]

that depends mostly from the providers & apps & gateways. Our implementation does segmentation & reassembly

https://en.wikipedia.org/wiki/Segmentation_and_reassembly

 

[FASTDEVICE]

@lazedo We are seeing messages coming in assembled from other SMS providers but not the one from 2600hz. Do we have to perform the re-assembly?  

[lazedo]

7 minutes ago, FASTDEVICE said:

but not the one from 2600hz

not sure what that means. 

 

8 minutes ago, FASTDEVICE said:

Do we have to perform the re-assembly?  

depends on your carrier and how you connect to your carrier

[FASTDEVICE]

@lazedo We are using your carriers, SMS provider and API https://docs.2600hz.com/supported/applications/crossbar/doc/sms/#about-sms

Whenever we receive an SMS that is 160 chars or less, we receive one SMS message. When we receive a message that is longer than 160 characters, it comes in as more than one SMS messages.  Using a different SMS provider, ie. Telynx  when we receive an SMS message greater than 160 chars, it comes in as one SMS message. 

[lazedo]

@FASTDEVICE  can you provide a real use case and trackable numbers from/to (you can send the number in private) ?

1) when you use the /v2/.../sms api you can send messages with more than 160 characters, we do segmentation or use udh depending on the number provider

2) when your webhook is called (after a text is received for the number), you should receive the ALL text, again, provider may use udh or segmentation. in the case of segmentation we reassemble before delivering to webhook or device

thanks

 

[FASTDEVICE]

Any further thoughts on why we are receiving SMS messages greater than 160 characters segmented into several messages? Again, this is not happening with other SMS providers that we tested and I suspect there may be a setting on the 2600hz side that needs to be addressed. Otherwise, we are going to release our SMS to Email application for 2600hz with this segmentation issue as there is nothing we can do but send the SMS body using your API with a limit of 700 characters. 

[FASTDEVICE]

2600hz resolved the segmentation issue by enabling concatenated SMS on their provider's gateway. Thank you 2600hz support!