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

[Fallon, Michael F]

>> My understanding is that oFono abstracts the 3G modem interface, and
>> that ConnMan sits on top of oFono. So applications should then access
>> the modem via ConnMan, which in turn accesses 3G through oFono. 
>> Now for SIP signaling protocol processing there is the sofia-sip
>> component of the telepathy package via Mission Control. I understand
>> applications should use the user agent library ?nua? interface of
>> telepathy?s sofia-sip library. 

>I think you are confusing different concepts here.
>Telepathy is the framework for IM and video/audio calls.
>Telepathy-sofiasip is the bit of the framework that does SIP.
>Mission control is the component that handles the accounts, put you
>online on all of them, and dispatch incoming communication channels
>(like a new video call) to the program that is supposed to handle them.

>You don't use telepathy-sofiasip directly, but through the Telepathy
>DBus API, that is conveniently wrapped by the Telepathy-Qt4 library (or
>telepathy-glib if you prefer that).

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? 

>> How do telepathy?s sofia-sip and oFono interact, if at all? Does
>> sofia-sip call into ConnMan and then oFono via d-bus for 3G modem (AT
>> command) access? What is the relationship here?

>To be honest, I'm not sure what you are asking. What are you trying to
>achieve?

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 SIM, and then I'd like to initiate connections (SIP INVITE, etc) using 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 two interact, so my question was regarding interactions between oFono (3G modem/SIM card) and Telepathy-sofia-sip (SIP session signaling stack). 

And further, how would one issue hardware specific AT commands to the 3G modem within the Qt framework? Thanks again!

Mike


----------------------------------------------------------------------

Message: 1
Date: Tue, 23 Nov 2010 10:10:39 -0700
From: "Fallon, Michael F" <michael.f.fallon at intel.com>
To: "meego-architecture at lists.meego.com"
	<meego-architecture at lists.meego.com>
Subject: [Meego-architecture] Telepathy/sofia-sip and oFono
Message-ID:
	<FF74A84A5BBBCA439D6B6F41A35AAF010CD0F6F9 at azsmsx502.amr.corp.intel.com>
	
Content-Type: text/plain; charset="us-ascii"

My understanding is that oFono abstracts the 3G modem interface, and that ConnMan sits on top of oFono. So applications should then access the modem via ConnMan, which in turn accesses 3G through oFono.

Now for SIP signaling protocol processing there is the sofia-sip component of the telepathy package via Mission Control. I understand applications should use the user agent library "nua" interface of telepathy's sofia-sip library.

So questions then are:
How do telepathy's sofia-sip and oFono interact, if at all? Does sofia-sip call into ConnMan and then oFono via d-bus for 3G modem (AT command) access? What is the relationship here?

Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-architecture/attachments/20101123/aaa8f2a5/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 23 Nov 2010 17:39:19 +0000
From: Marco Barisione <marco.barisione at collabora.co.uk>
To: meego-architecture at lists.meego.com
Subject: Re: [Meego-architecture] Telepathy/sofia-sip and oFono
Message-ID: <1290533959.7676.23.camel at morngond>
Content-Type: text/plain; charset="UTF-8"

On Tue, 2010-11-23 at 10:10 -0700, Fallon, Michael F wrote:
> My understanding is that oFono abstracts the 3G modem interface, and
> that ConnMan sits on top of oFono. So applications should then access
> the modem via ConnMan, which in turn accesses 3G through oFono. 
> Now for SIP signaling protocol processing there is the sofia-sip
> component of the telepathy package via Mission Control. I understand
> applications should use the user agent library ?nua? interface of
> telepathy?s sofia-sip library. 

I think you are confusing different concepts here.
Telepathy is the framework for IM and video/audio calls.
Telepathy-sofiasip is the bit of the framework that does SIP.
Mission control is the component that handles the accounts, put you
online on all of them, and dispatch incoming communication channels
(like a new video call) to the program that is supposed to handle them.

You don't use telepathy-sofiasip directly, but through the Telepathy
DBus API, that is conveniently wrapped by the Telepathy-Qt4 library (or
telepathy-glib if you prefer that).

> How do telepathy?s sofia-sip and oFono interact, if at all? Does
> sofia-sip call into ConnMan and then oFono via d-bus for 3G modem (AT
> command) access? What is the relationship here?

To be honest, I'm not sure what you are asking. What are you trying to
achieve?

-- 
Marco Barisione



------------------------------