[Meego-architecture] Telepathy/sofia-sip and oFono

[Kai.Vehmanen at nokia.com]

Hi,

On 23 Nov 2010, Fallon, Michael wrote:
> Right. My understanding is as you described (though clearly my message
> didn't convey this, sorry). My confusion starts when you add to your
> description above the role of oFono. Through what software path does
> Telepathy-sofia-sip communicate with the 3G modem?

telepathy-sofiasip implements a SIP connection manager, which
can be run over any IP transport (WLAN, cellular data, ...). 
You use connman to setup a network interface and that's it.

> Thanks for your help. I'm trying to understand how I should use the
> MeeGo framework to first register two simultaneous IMS sessions (using
> two primary PDP context as stored on the SIM), authenticate using the

For this you need an IMS connection manager for Telepathy (IETF
SIP plus 3GPP extensions), which extends/is-based-on telepathy-sofiasip 
(the core SIP parts are the same). Basicly the needed extensions are not 
access agnostic, so you need to interact with the cellular modem directly
and oFono should be used for this. And note that for e.g. WLAN IMS has
different procedures.

> the same Qt infrastructure over each of these networks. I think my
> confusion stems from the idea that oFono "owns" the SIM, yet, as you
> point out, Telepathy provides the SIP stack. I see nothing on how the

Yes. To access the SIM , you need to use oFono. Current telepathy-sofiasip 
in MeeGo has no need for this, so it does not interact with oFono.

If you need to extend it to support IMS (or write a new CM), then it needs 
to start interacting with oFono directly as well. Once the IMS-enabled 
connection manager is implemented, all of this is abstracted by the 
Telepathy APIs and apps can justuse e.g. telepathy-qt4 (same API for 
all calls&messaging remains).

br,
-- 
Kai Vehmanen