Hi Michael,
> >> In theory there might be more than one IMS APN for a operator,
>
> >> but I really don't see this as a real life scenario for this.
>
> >> If anyone disagrees please speak out and explain...
>
>
>
> One such scenario is the in-vehicle use model, where the ISP provides
> netw
>> In theory there might be more than one IMS APN for a operator,
>> but I really don't see this as a real life scenario for this.
>> If anyone disagrees please speak out and explain...
One such scenario is the in-vehicle use model, where the ISP provides network
connectivity via one APN and the
Hi Rémi,
Rémi wrote:
> > + The registered application is tracked, if the
> > + application exits the registration will be
> > + automatically released.
> > +
> > + Related AT command: AT+EISR.
>
> Is this a standard command?
Hi Rémi,
>> > > + boolean PreConditionCheck(string Type, string
>> > > PeerAddress, + uint16 PeerPort,
>> > > uint16 LocalPort) +
>> >
>> > That stuff is per context. Should it not be in the context object rather
>> > than in the IMS manager?
>>
>>
On Tuesday 08 February 2011 18:22:43 ext Sjur Brændeland, you wrote:
> > > + boolean PreConditionCheck(string Type, string
> > > PeerAddress, + uint16 PeerPort,
> > > uint16 LocalPort) +
> >
> > That stuff is per context. Should it not be in the con
Hi Redouane,
>> + void UnRegister(object path)
>> +
>> + Un-register a IpMultimediaSubsystemAgent.
>
> Register and UnRegister functions are not really symmetric here ...
> How object path is used by UnRegister function ??
> Maybe we should have :
> void UnRegister(
Hi Rémi,
> > +Service org.ofono
> > +Interface org.ofono.IpMultimediaSubsystem
> > +Object path [variable prefix]
>
> I guess this is meant to be a modem object path, but it seems the oFono
> documentation is already a bit sloppy on this point.
Yes, this should be the modem objec
Hi Sjur,
> + void Register(string type)
> +
> + Register a IMS Application. It must register
> + with one of the types:
> + "voice", "messaging", "voice_messaging".
> +
> + This registration will inform mo
On Tuesday 08 February 2011 16:29:17 ext Sjur Brændeland, you wrote:
> From: Sjur Brændeland
>
> Thanks for lots of useful feedback from last RFC,
> here is my next revision on the LTE/IMS API.
> Comments are still very much welcome!
>
> Changes from RFC-V1:
> - Renamed IMS to IpMultimedia
From: Sjur Brændeland
Thanks for lots of useful feedback from last RFC,
here is my next revision on the LTE/IMS API.
Comments are still very much welcome!
Changes from RFC-V1:
- Renamed IMS to IpMultimediaSubsystem (some places)
- Changed registration of IMS application.
10 matches
Mail list logo