From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Call Barring and MMI Supplementary Service codes
Date: Tue, 19 Oct 2010 12:13:07 -0500 [thread overview]
Message-ID: <4CBDD1A3.4050909@gmail.com> (raw)
In-Reply-To: <AANLkTinR2KBpu+Qs4Y-Tgu1AKCZFFKzAndzZkzFYv3T+@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Hi Pekka,
On 10/19/2010 10:30 AM, Pekka Pessi wrote:
> Hi Denis,
>
> 2010/10/19 Denis Kenzior <denkenz@gmail.com>:
>> So let me repeat what you said in my own words. The lowlevel register
>> message has these variations:
>>
>> - All data circuit sync
>> - All sync services
>>
>> - All data circuit async
>> - All async services
>>
>> In both cases they actually refer to the same set of bearer services.
>
>> So sending one vs the other makes no difference. So instead of
>> deprecating the 'all sync' and 'all async' versions of the low level
>> register messages the spec still expects us to send them for whatever
>> reason.
>
> There is also a set of PLMN-specific services. I suppose it is up to
> network to decide which are sync or async and which involve data
> circuits... There are some traces in Nokia modems indicating even that
> they have been actually used at some point.
>
Yep I've always wondered how anyone could implement these with an AT
based modem.
Anyway, this has been fixed by commit
b75a5574f5a5652880ab2fe4760c2f3272815496
Please test and report back if the conformance cases pass now.
Regards,
-Denis
prev parent reply other threads:[~2010-10-19 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 9:21 Call Barring and MMI Supplementary Service codes Predon, Frederic
2010-10-15 21:03 ` Rajesh.Nagaiah
2010-10-18 21:26 ` Denis Kenzior
2010-10-19 5:27 ` Rajesh.Nagaiah
2010-10-19 11:37 ` Pargada, Carlos
2010-10-19 15:11 ` Denis Kenzior
2010-10-19 15:30 ` Pekka Pessi
2010-10-19 17:13 ` Denis Kenzior [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=4CBDD1A3.4050909@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/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