This past week I’ve been travelling with a new Plantronics Voyager Legend Bluetooth headset. This is the fourth headset in the Voyager range that I’ve used. You may recall that not so long ago I bought a Voyager Pro HD. That headset has been completely satisfactory. I was not intending to purchase a replacement. So it is that I’ll start by describing how I came to have this little beasty, which is a bit of a curious story and the tale of my first Tweet-Up, aka Twitter Party.
Back in October my wife took a business trip to Anaheim CA for a few days. This was something of a turning of the tables for I am the frequent business traveller in the family. She rarely travels on business.
It was decided (i.e. I was told) that since she had to be away I would need to be taking care of things at home that week. I found myself tending the homestead without some of the normal distractions of our daily life. I had some extra time to tinker for a few evenings.
I was incensed as a result of the past weeks trouble with the cable card swap that Comcast imposed. After considerable time spent on the phone in the afternoon I detailed the situation in a blog post early last evening. At the point when I wrote that post we had no clear path to solution, just the promise that someone would call us back.
Shortly after the blog post went live a twitter message was automatically sent to highlight that post. This caught the attention of @comcastcares, which is Frank Eliason, Director Of Digital Care at Comcast.
Frank & his staff are based in Philadelphia PA. The fact that Comcast has been using Twitter to stay on top of customer service has been known for some time. I had some cursory interaction with them during the long service outage in the aftermath of Hurricane Ike.
It’s been very frustrating dealing with the utility companies with respect to restoring service in the post-Ike period. At issue is their inability to get and redistribute information about who’s on, who’s not, and routine progress reports. Today for a short while my focus turned to Comcast as our cable tv and cable modem service remains down.
Earlier this week Andy Abramson discovered that he could make a Phweet call via Twitter, thereby circumventing the VoIP blocking provisions used by American Airlines Aircell operated GoGo in-flight wifi service.
This is definitely interesting as Aircell somehow manages to allow Skype IM, but stop Skype voice calls. This implies that the Tring Me Flash VoIP widget is doing something at least a little unusual.
After hearing about Phweet earlier this week, and giving it a look, I was able to connect with co-founder Stuart Henshall this morning. It seems that he was hanging out on the service all day getting conferences started and explaining things to people.
My impression of the service evolved a little over the course of half an hour actually using it. My initial impression was that it was principally for spawning calls between Twitter users. That’s pretty cool indeed.
Now here’s a new service that in makes perfect sense to me. Phweet bridges the divide between your Twitter account and your phone.
You can invite a call from someone on Twitter without passing them your contact details. Within the Phweet service each user establishes how they’ like to be contacted by either SIP, PhoneGnome, Gizmo5 or FWD.
They also seem to have Flash based soft phone that can invoke the call right in a browser window. In my case Phweet points to a SIP URI hosted by Junction Networks, making the resulting call free for me. It rings through to a Polycom phone on my desk, snom m3 cordless and soft phone when I’m traveling.
The service just launched in a public alpha. I wish them well. I will certainly be giving it a workout.