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/.
Holger Hans Peter Freyther holger at freyther.deOn Sun, Jul 07, 2013 at 09:08:26AM +0200, Holger Hans Peter Freyther wrote: > "If the total number of characters to be sent equals (8n-1) where > n=1,2,3 etc. then there are 7 spare bits at the end of the message. > To avoid the situation where the receiving entity confuses 7 binary > zero pad bits as the @ character, the carriage return or <CR> character > (defined in subclause 7.1.1) shall be used for padding in this situation, > just as for Cell Broadcast." And the change is incomplete as well: "If <CR> is intended to be the last character and the message (including the wanted <CR>) ends on an octet boundary, then another <CR> must be added together with a padding bit 0. The receiving entity will perform the carriage return function twice, but this will not result in misoperation as the definition of <CR> in subclause 7.1.1 is identical to the definition of <CR><CR>. The receiving entity shall remove the final <CR> character where the message ends on an octet boundary with <CR> as the last character." holger