Skip to main content

AT&T has some shady billingness going on.

At my company we use a service named "Webex" to do remote presentations and conferencing.  So here you are, you join a Webex session on your iPhone.   See Cisco (the makers of Webex) made an iPhone app where you can view presentations and participate in an online presentation right on the Phone!  It's great!    You sign into a webex, and the webex app says "Hey, you want me to dial the conf number for you", Why sure!  You can dial the number, and then I can pop back over to the webex app!? Phenomenal.  Great technology, great to see it.
So it kicks you over to the Call screen where it proceeds to dial 8664693239 ,,<confcode>,,<attendee id>#  (commas are pauses in the Phone world)

The way that Cisco sends the number to the call app, inserts that space after the actual phone number, which makes the phone app format the aforementioned number as an international number.
So, the iPhone appears to dial the number as +8664693239.  You know what +86 is as a country code?  China.
So, that's not the problem, not the problem at all.  The iPhone dials the number correctly (even though it shows up incorrectly), you connect to the 866 toll free call and everything!
The problem is on AT&T's billing side, somewhere, where it receives the number under a different format, and the number on your bill shows up as 866-469-3239.
Know what it's billed as?  A call to +86.  Yup. China.

So, my most recent bill from AT&T showed a 200+ dollar call to China.
My question is, how common is this?  Is AT&T charging people like this for calls that aren't processed in the billing system correctly?  AT&T is just expecting people to pay the bill?  My bill was almost 500 dollars this month because of 4 or 5 calls like this.  (I do a lot of presentations.)
AT&T, fix your billing system.  Something is screwed up.

Comments

Joel said…
I sent this article out to a couple co-workers, and I received about 5 responses of people that have had the same exact thing happen to you. My 200 bill was on the extreme low side as well.
Joel Esler said…
I sent this article out to a couple co-workers, and I received about 5 responses of people that have had the same exact thing happen to you. My 200 bill was on the extreme low side as well.
Joel Esler said…
I sent this article out to a couple co-workers, and I received about 5 responses of people that have had the same exact thing happen to you. My 200 bill was on the extreme low side as well.

Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:


Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button