This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Ron ron.menez at entropysolution.comHi Pau and Keith, We updated to the latest version and the SMS for both osmo-nitb and osmo-bsc are now working fine. Thanks for the advised. Best Regard, Ron Menez ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com> On Mar 25, 2018, at 6:21 PM, Keith Whyte <keith at rhizomatica.org<mailto:keith at rhizomatica.org>> wrote: On 23/03/18 16:24, Ron wrote: Hi All, Hi Ron. Can anyone confirm if the maximum MO-SMS that can be sent is less than 60 characters including spaces? I have worked quite extensively with SMS and have not experienced any such limitation at all, or any deviation from standard. AFAIK an SMS payload is 140 bytes, Always. What you get in there depends on other things, like what character are in the message. For OSMO-NITB, we reach a maximum of 59 characters for MO-SMS, while for OSMO-BSC, we only reach a maximum of 50 characters (MO-SMS). Can you elaborate about your setup, what it is you are doing? What is it you are experiencing when you send a longer message? Are you using SMPP, or only inside the nitb/bsc? It is the MS that forms the SMS, not the network. I've never seen anything where the network says "sorry too big, split that SMS into two", I don't believe such a thing exists. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180416/26b3c6dd/attachment.htm>