From: Sicelo <absicsz@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@lists.linux.dev
Subject: Re: Improper Handling for Messages That Do Not Specify Source/Address Port
Date: Sun, 12 Nov 2023 22:29:08 +0200 [thread overview]
Message-ID: <ZVE1lIgh8uJg9amK@tp440p.steeds.sam> (raw)
In-Reply-To: <e48fe212-7a30-4bae-a892-f22d3495e169@gmail.com>
Hi Denis
On Sun, Nov 12, 2023 at 12:34:29PM -0600, Denis Kenzior wrote:
> Hi Sicelo,
>
> On 11/10/23 04:20, Sicelo wrote:
> > Hi
> >
> > While running ofono in debug mode, I discovered that there are certain
> > types of sms-like messages that arrive in ofono core, but are discarded
> > without being sent to the client. For these, the ofono log shows a lot
> > of:
> >
> > ofonod[3424627]: Got an 8-bit encoded message, however no valid src/address port, ignore
> >
>
> When that code was written, this was what the spec wanted. There was no way
> to identify the 8-bit character set of SMS messages, any 8-bit messages had
> to be a binary SMS with port/destination provided.
>
> Maybe this has changed since, but I'd need some link / document to refer to ...
I am also not sure, but on an Android phone, for example, it shows up
somewhat similar to what most of us call flash messages.
> > These messages are valid, and ofono should not discard them. In my case,
> > for example, the messages come in while connected to mobile data. They
> > are sent by the carrier periodically to notify me about the credit that
> > has been deducted from my prepaid plan.
>
> Sure, so how does oFono interpret these? ASCII? Latin1? UTF8?
From tracing on isimodem on the Nokia N900, it seemed to be plain ASCII,
i.e. one byte-per-character. Unfortunately this message is carrier
initiated, so I don't have an easy way to get them to send it at will.
When I eventually get to it, I guess I will start by testing with
commenting out the code that checks for the src/dst port, and see where
things go.
Sicelo
prev parent reply other threads:[~2023-11-12 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 10:20 Improper Handling for Messages That Do Not Specify Source/Address Port Sicelo
2023-11-12 18:34 ` Denis Kenzior
2023-11-12 20:29 ` Sicelo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZVE1lIgh8uJg9amK@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=denkenz@gmail.com \
--cc=ofono@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).