>"We're sorry all circuits are busy now" WHAT THE f.ck IS THIS?
>
>Excuse my language but, cingular is pissing me off. I'm trying to call
>someone and I have dial their number at least 60 times before I get through
>and that's no exaggeration. They need to do something about this.
I suggest you call Customer Service, and ask for a credit on your bill.
That's the way to get their attention. Ranting here does no good.

Signature
Best regards,
John Navas <http://navasgrp.home.att.net/> HELP PAGES FOR
CINGULAR GSM + ERICSSON PHONES: <http://navasgrp.home.att.net/#Cingular
>"We're sorry all circuits are busy now" WHAT THE f.ck IS THIS?
My goodness, Even complete IDIOTS know what that means!!!!
And they usually don't cuss......
That being said, you must be something less than a complete idiot.
--
John S.
e-mail responses to - john at kiana dot net
N W - 28 Jun 2003 05:26 GMT
xyexotiche@aol.comspamfree (John S.) wrote in article
<20030627214529.16978.00001896@mb-m06.aol.com>:
> >"We're sorry all circuits are busy now" WHAT THE f.ck IS THIS?
>
[quoted text clipped - 7 lines]
> John S.
> e-mail responses to - john at kiana dot net
Where are you from, have you dropped your phone lately, and what type of
phone is it?
not just a congested network can cause a call to fail
> "We're sorry all circuits are busy now" WHAT THE f.ck IS THIS?
>
> Excuse my language but, cingular is pissing me off. I'm trying to call
> someone and I have dial their number at least 60 times before I get through
> and that's no exaggeration. They need to do something about this.
The auto-anouncement quoted above is provided to all callers whose
call encounters a route blockage due to a temporary unavailability of
network resources. Virtually all U.S. telecommunication carriers -
landline and wireless - are obligated by FCC regulations to provide
this exact same message for the exact same reason.
I would agree Cingular needs to fix it, assuming it was Cingular's
network that was broken. Since Cingular is only responsible for their
own network resources, one would have to know which network resource
was impaired, and who is responsible for successful call completions
on said network. What did Cingular's customer service say when you
reported this anomaly? Did they feign ignorance? Did they laugh or
cry and feign ignorance? Or did they commit to routing your complaint
to the proper maintenance personnel? And the even larger question is,
is it still a problem today?
If a Cingular client attempts to make a long distance call, and Farmer
Joe has dug up a buried telephone cable owned by AT&T while plowing
his back forty, is it Cingular's responsibility to roll truck loads of
cable repair splicers to the plow site? My book says no.
We can all understand you frustration, but if you don't know who's
responsible for fixing something like this, it's patently unfair and
disingenuous to make wild accusations.

Signature
jer email reply - I am not a 'ten' ICQ = 35253273
"All that we do is touched with ocean, yet we remain on the shore of
what we know." -- Richard Wilbur
Jova - 29 Jun 2003 21:15 GMT
Yes their was a call to Cingular and no I'm not less than a complete idiot.
I think John S. you are a "complete idiot" because you didn't understand
what I trying to say. What I mean by saying "What is that." It's an
expression like saying you are a complete idiot it just an expression.
Anyway, there was a call to Cingular. They claimed their was setting on the
phone that was causing the problem and supposedly had fix it. It work fine
for about a week. But, then again it just started screwing up (another
expression John S. don't take it serious) again. I know a couple of people
that have the same problem with their phone. When you call them it says the
same thing for them. You would have to dial their cell number numerous
times before you can get through.
Thank jer for understanding what I meant about this whole situation.
> > "We're sorry all circuits are busy now" WHAT THE f.ck IS THIS?
> >
[quoted text clipped - 31 lines]
> "All that we do is touched with ocean, yet we remain on the shore of
> what we know." -- Richard Wilbur