ng
> character before passing the +CUSD: string to the consumer of the USSD
> response.
>
> Regards,
> Reinhard
Sorry to butt in, but if you do that won't any USSD messages that have
backslashes embedded be mistaken for the badly encoded ones and fixed up
erroneously.
--
And
> this device? Or is this only an issue to the consumer of the USSD
> responses?
What I think curious is that 0x0a is a valid GSM0338 character and should have
been interpreted as linefeed
ftp://ftp.unicode.org/Public/MAPPINGS/ETSI/GSM0338.TXT
Were both modem session
rk name etc which
they may expect to contain rich characters etc are prime candidates.
--
Andrew Bird <a...@spheresystems.co.uk>
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
istinfo/modemmanager-devel
>
It looks like there are plans(2017) to change the format of ISO/7812 allowing
an 8 digit IIN at the expense of the account number. I suspect you'll need to
get hold of that spec, though I don't beleive it's available for free. See
https://en.wikipedia.org/wiki/I
