Aircell Isn’t Blocking all Forms of VoIP

Filed under: business,connectivity,Services,travel,wifi - 22 Aug 2008 1:36

Andy made a big splash on Twitter (and throughout the blogosphere) when he announced that he had a call on an airplane thanks to Phweet. I, of course, don’t deny it happened, but I want to warn everyone that this could easily be blocked in the future.

This probably won’t make a lot of sense without knowing what Aircell and Phweet are. Aircell is American Airlines new WiFi in the sky service that recently launched. The reported restrictions on this service are that VoIP applications are disallowed. Skype, interestingly enough, can be used without using the voice calling.

Phweet is Stuart Henshall and David Beckemeyer’s latest brainchild, making it possible for two (or more) people to set up a voice call using only your twitter credentials. No phone numbers needed. One of the ways you can connect into Phweet is through a flash widget provided by TringMe, which uses standard HTTP to communicate.

And therein lies the hole. Unlike with SIP-based solutions like SightSpeed, which reportedly failed after about 10 seconds, TringMe’s widget was able to bust through whatever Aircell is doing to block VoIP calls on the planes. The reason? The traffic looks like normal web traffic.

In some sense, that’s correct. However, if you were to look at that HTTP traffic more closely, you can figure out that something doesn’t look right about that HTTP traffic. An HTTP proxy seems to thwart the TringMe widget. Forcing the traffic through a proxy–or looking for the “signature” of this TringMe widget–is all you need to be able to block thhis flash widget without impacting other widgets (e.g. YouTube, Hulu).

Of course, like porn finds its way around the filters, you can likely find ways around this blockage. That being said, voice traffic has a certain fingerprint that is hard to mask, even if you were to encrypt the traffic. I have no doubt that Aircell, if it so chooses, could make it very difficult for this traffic to get through. I wouldn’t count on this “hole” working for long.

Reblog this post [with Zemanta]

Tags: , , , Fnord

6 Comments

  1. Pingback by VoIP Blogging

    links from Technoratit work we tried a Flash based solution through Phweet (you use your Twitter account to sign in). Some related posts from Technorati and Google. [The PhoneBoy Blog]Aircell Isn’t Blocking all Forms of VoIP: Unlike with SIP-based solutions like SightSpeed, which reportedly failed after about 10 seconds, TringMe’s widget was able to bust through whatever Aircell is doing to block VoIP calls on the planes. The reason?

  2. Pingback by Communications and Technology Blog - Tehrani.com

    links from Technoratiblocking on planes and the associated ways of getting around said blocking. Long story short — SIP was being blocked on American Airline flights but Flash widgets were not blocked. Andy Abramson has an original post on the matter and PhoneBoy hasthoughtson why airplane broadband providers can likely block anything thrown at them. Like I said a while back — isn’t it amazing how much effort airlines throw at stopping passengers from talking on phones when they don’t get paid by the minute? I remember

  3. Pingback by Andy’s Phweet Aircell call — Alec Saunders SquawkBox

    [...] Aircell Isn’t Blocking all Forms of VoIP [...]

  4. Pingback by links for 2008-08-23 | stuart henshall

    Kramer auto Pingback[...] Aircell Isn’t Blocking all Forms of VoIP on One Phweet Conversation Over AirCell”: made a big splash on Twitter (and throughout the blogosphere) when… [...]

  5. Comment by JimAtJaxtr

    Perhaps they haven’t moved to block that loophole yet because there aren’t enough people using it yet to really impact revenue. Could be a cost thing that it’s more costly to figure out how to fix it currently than to let the small number of people using that route do it. It’ll be interesting to see what they do.

  6. Pingback by TringMe - In New and Blogs

    Kramer auto Pingback[...] Aircell Isn’t Blocking all Forms of VoIP | Aug 22, 2008 [...]

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.