tmobile wifi voice calls

[Greg Bonett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey, I've been trying to get twinkle (a sip client) compiled on the
openmoko, but I can't get GCC to work.  If we can get a c compiler I
think theres a good chance twinkle will work

Ken Restivo wrote:
> First we need a phone app that supports SIP.
> 
> I would very very much like to use the FR as a SIP phone. I don't need T-Mobile for that (and neither does anyone else), we just need a working phone app that supports VOIP as a back end, and access to open WiFi AP's (plenty of those around).
> 
> I have a Diamondcard/Ekiga account for phone calls to the POTS network, and it works great and is dirt cheap. I wouldn't want to deal with proprietary crap like whatever T-Mobile is going to foist upon people.
> 
> Is anyone porting Ekiga to the FR? I saw a component in ASU that looks like a VOIP "back end" for the Qtopia phone app; that'd kick ass if it was working. Any ideas what I'd need to do to get it to work?
> 
> -ken
> ----------------
> On Thu, Jul 17, 2008 at 07:14:09PM -0400, c d r wrote:
>>> I'll begin to pursue this via the provided links in my copious spare  
>>> time. Anyone interested in an ongoing dialog let me know.
>> how well integrated is it?
>>
>> i was planning on using a moko, primarily via SIP/IAX but with T-Mo prepaid SIM for occasional GSM needs
>>
>> if it can seamlessly roll between the two, preferring wifi/sip (or their equiv) when available, that would kick ass
>>
>>
>>> Chris
>>>
>>>
>>>
>>> On Jul 17, 2008, at 2:32 PM, Al Johnson wrote:
>>>
>>>> On Thursday 17 July 2008, Carl Karsten wrote:
>>>>> "Make and receive unlimited nationwide calls over Wi-Fi with your  
>>>>> home
>>>>> phone."
>>>>> http://www.t-mobile.com/shop/plans/cell-phone-plans-detail.aspx?tp=tb1&rate
>>>>> plan=T-Mobile- at Home
>>>>>
>>>>> Anyone know if the FR will work with whatever VoIP protocol t- 
>>>>> mobile uses?
>>>>> does anyone even know what protocol it uses?   I found this:
>>>>>
>>>>> "The technology T-Mobile is using is called Unlicensed Mobile  
>>>>> Access, or
>>>>> UMA. UMA takes the protocol used by GSM handsets and encapsulates  
>>>>> it into
>>>>> an IPSec VPN for transmission over the public Internet. The VPN is
>>>>> authenticated using the subscriber's SIM card via a protocol called
>>>>> EAP-SIM."
>>>>> http://www.voip-weblog.com/50226711/is_the_linksys_wrtu54g_voip.php
>>>> Nice prompt for a little background reading. From what I see it seems
>>>> unlikely. strongSWAN appears to support IKEv2 and EAP-SIM but  
>>>> somehow I doubt
>>>> T-Mobile will hand out the certificate needed in addition to the  
>>>> SIM. The bit
>>>> that looks tricky is the signalling part to tell the mobile phone  
>>>> network
>>>> that it can pass the call data over to the wifi connection. This is  
>>>> the sort
>>>> of thing that's normally buried in the cellular modem, and I don't  
>>>> know of an
>>>> open version of that. I could be pleasantly surprised though - it  
>>>> would be a
>>>> good addition to have.
>>>>
>>>> [1] http://www.embedded.com/underthehood/205916513
>>>> [2] http://www.linuxdevices.com/news/NS6470081317.html
>>>>
>>>> _______________________________________________
>>>> Openmoko community mailing list
>>>> community at lists.openmoko.org
>>>> http://lists.openmoko.org/mailman/listinfo/community
>>>
>>> _______________________________________________
>>> Openmoko community mailing list
>>> community at lists.openmoko.org
>>> http://lists.openmoko.org/mailman/listinfo/community
>> _______________________________________________
>> Openmoko community mailing list
>> community at lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
> 
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIf/ANR7UPrMLya90RAmjPAKDKfu9sF4f82giPmvzxYPLChbzHywCg1pBc
qvfNcEfxyGmDv5l1EQSDdzc=
=98cn
-----END PGP SIGNATURE-----