Hi Sjur,

2011/1/27 Sjur Brændeland <[email protected]>:
>> I think we need these in ConnectionContext, or perhaps a separate
>> DedicatedContext interface would be better.
>
> Yes, as I mentioned earlier I considered this as well. But do you see other
> scenarios than IMS where the NW will set up Dedicated Bearers?

I have no idea. On the other hand, there should be a straightforward
way to correlate these and the context that uses them; retrieving them
from the context is such a straightforward way.

>> Also the PcscfAddresses should be part of the Settings  or Settings6
>> in ConnectionContext.
>
> Do you think we will ever have more than one IMS ConnectionContext pr SIM?
> If not not we could probably keep the PcscfAddresses in this IMS API  (see
> object-path proposal below).

Unfortunately, yes.

>>> - The UE-Mode of operation, is primarily triggered by IMS application
>>>  registering to the RadioStack that it has registered on Voice and/or
>>>  SMS by setting the properties ImsVoiceRegistered or ImsSmsRegistered.
>>>
>>> - SIM identities used for IMS registration such as: PrivateImsIdentity,
>>>  PublicImsIdentity, HomeDomainName.
>>
>> These should be available from separate interface/object, one for each ISIM.
>
> I guess if you have more than one SIM, you would in fact have two
> modem instances
> and two instance of this API. In the next patch I should probably use
> [{modem1},{modem2}...] as the
> object-path of this IMS object.

ISIM is an application on SIM card (also known as UICC). There can be
multiple ISIMs on a single card but only a single USIM (3G SIM
application) or 2G SIM application.

-- 
Pekka.Pessi mail at nokia.com
_______________________________________________
ofono mailing list
[email protected]
http://lists.ofono.org/listinfo/ofono

Reply via email to