On 04/09/2010 06:57 AM, Disconnect wrote:
At least google voice isn't VOIP, and ISTR that neither is skype (although that may have changed with recent releases.) They both function by dialing special-use numbers (google voice uses http to set up a line to remote mapping, so that when you call 202-111-2345 gvoice connects you to 202-123-4567 and remaps the source #, etc. ISTR the skype app just phone-carded it - dial a generic access #, then dial codes to get connected..)

Skype is VoTCP, more specifically (ick, but it's their NAT/firewall traversal
mechanism). They have TDM gateways which you pay for but they're accessed
via IP. They may have more access mechanisms these days, but that's what
the original Skype did.

Not familiar with sipdroid or fring, and as of 1.5 or so it became possible to manipulate the audio stream so they may well be proper sip clients now :)

I've always been mystified why people consider voice a creature apart
from everything else; it's just a media recorder hooked into media player
transported by the net in real time. Sure it has complications -- like 3g's
latency being horrible, and handoff considerations and cpu consumption
for codecs, echo cancellation, comfort noise, etc -- but there's nothing
really *new* about those things. If people approached it without thinking
about telephony _at all_, they'd probably be a lot better off :)

Mike


On Fri, Apr 9, 2010 at 9:45 AM, Mark Murphy <mmur...@commonsware.com <mailto:mmur...@commonsware.com>> wrote:

    alexdonnini wrote:
    > Probably, you have heard of the iPhone application called
    "Line2". In
    > short, it gives an iPhone a second phone number and line
    complete with
    > contacts list, voice mail, etc., etc.

    It is more generically referred to as "voice over IP" (VOIP).

    > I was wondering if anyone has thoughts as to how the Android
    security/
    > permission issues inherent when attempting to develop an application
    > such as Line2 could be resolved.

    What, specifically, do you feel are "the Android security/permission
    issues inherent when attempting to develop" a VOIP app?

    I ask because there are several VOIP apps for Android (such as Google
    Voice, Skype, SipDroid, and Fring, to name four off the top of my
    head).
    Hence, it would seem unlikely that there are "Android
    security/permission issues" in implementing a VOIP app, otherwise
    those
    apps would not exist.

    --
    Mark Murphy (a Commons Guy)
    http://commonsware.com | http://twitter.com/commonsguy

    Android Consulting: http://commonsware.com/consulting

    --
    You received this message because you are subscribed to the Google
    Groups "Android Developers" group.
    To post to this group, send email to
    android-developers@googlegroups.com
    <mailto:android-developers@googlegroups.com>
    To unsubscribe from this group, send email to
    android-developers+unsubscr...@googlegroups.com
    <mailto:android-developers%2bunsubscr...@googlegroups.com>
    For more options, visit this group at
    http://groups.google.com/group/android-developers?hl=en

    To unsubscribe, reply using "remove me" as the subject.


--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to