Calling my phone results in rapid busy signal 2/3 times.

Just purchased and activated my Sanyo 8100 3 days ago ($100/mo for
unlimited internet and 2,000 anytime minutes) and it would seem that
from day one people have been receiving a rapid busy signal when they
dial my phone. It wasn't brought to my attention until yesterday when
several people told me they were unable to get through to me on my new
number. I then tried myself and received the same thing.

I called technical support last night and they walked me through
reprogramming my phone, and of course it worked after that song and
dance. But guess what, I call it this morning and get the SAME rapid
busy signal. So I call technical support again and THIS time they tell
me it's been a known software/telephone # routing issue, for the past
3 weeks, afflicting random phone numbers in random areas.

Now, I have another SprintPCS phone that I have had for over 3 years
and have NEVER had this problem with it. The rep also said the problem
wouldn't be fixed for another 2 weeks!!

Has anyone else gotten this line of bunk? I'm in West Los Angeles and
would like to know if I should wait or just cancel this new plan and
move to Nextel.

Cheers, Chris

---

› See More: Calling my phone results in rapid busy signal 2/3 times.

In article <[email protected]>,
[email protected] (Chris) wrote:

> Just purchased and activated my Sanyo 8100 3 days ago ($100/mo for
> unlimited internet and 2,000 anytime minutes) and it would seem that
> from day one people have been receiving a rapid busy signal when they
> dial my phone. It wasn't brought to my attention until yesterday when
> several people told me they were unable to get through to me on my new
> number. I then tried myself and received the same thing.

You do realize that the "Vision" (Internet) is only free for the first
two months, and then you get charged $15/month for it?

Sounds like you have a defective phone; and hopefully you bought it
locally so it will be easy to return for replacement.

In article <[email protected]>,
[email protected] (Chris) wrote:

> Now, I have another SprintPCS phone that I have had for over 3 years
> and have NEVER had this problem with it. The rep also said the problem
> wouldn't be fixed for another 2 weeks!!

Of course they say that. After 2 weeks, you can't return it. You only
have 14 days. BRING IT BACK NOW !

Actually on the 2,000 min plan vision is free! After two months it still will
be free!

[email protected] (Chris) wrote in message news:<[email protected]>...
> Just purchased and activated my Sanyo 8100 3 days ago ($100/mo for
> unlimited internet and 2,000 anytime minutes) and it would seem that
> from day one people have been receiving a rapid busy signal when they
> dial my phone. It wasn't brought to my attention until yesterday when
> several people told me they were unable to get through to me on my new
> number. I then tried myself and received the same thing.
>
> I called technical support last night and they walked me through
> reprogramming my phone, and of course it worked after that song and
> dance. But guess what, I call it this morning and get the SAME rapid
> busy signal. So I call technical support again and THIS time they tell
> me it's been a known software/telephone # routing issue, for the past
> 3 weeks, afflicting random phone numbers in random areas.
>
> Now, I have another SprintPCS phone that I have had for over 3 years
> and have NEVER had this problem with it. The rep also said the problem
> wouldn't be fixed for another 2 weeks!!
>
> Has anyone else gotten this line of bunk? I'm in West Los Angeles and
> would like to know if I should wait or just cancel this new plan and
> move to Nextel.
>
> Cheers, Chris


I'm not too far from West LA and have 3 phones on my account. I have
never received a fast busy signal like that when calling any Sprint
phone.

"Larry Thomas" <[email protected]> wrote in message
news:[email protected]...
> [email protected] (Chris) wrote in message
news:<[email protected]>...
> > Just purchased and activated my Sanyo 8100 3 days ago ($100/mo for
> > unlimited internet and 2,000 anytime minutes) and it would seem that
> > from day one people have been receiving a rapid busy signal when they
> > dial my phone. It wasn't brought to my attention until yesterday when
> > several people told me they were unable to get through to me on my new
> > number. I then tried myself and received the same thing.
> >
> > I called technical support last night and they walked me through
> > reprogramming my phone, and of course it worked after that song and
> > dance. But guess what, I call it this morning and get the SAME rapid
> > busy signal. So I call technical support again and THIS time they tell
> > me it's been a known software/telephone # routing issue, for the past
> > 3 weeks, afflicting random phone numbers in random areas.
> >
> > Now, I have another SprintPCS phone that I have had for over 3 years
> > and have NEVER had this problem with it. The rep also said the problem
> > wouldn't be fixed for another 2 weeks!!
> >
> > Has anyone else gotten this line of bunk? I'm in West Los Angeles and
> > would like to know if I should wait or just cancel this new plan and
> > move to Nextel.
> >
> > Cheers, Chris

It's not bunk. It's a known issue in markets that use Lucent switches. Some
sort of software problem. A fix was rolled out in one market and if it is
successful will be rolled out to the other markets in less than two weeks,
at least as of the last thing I saw. It's not a secret, I've been working
trouble tickets and calling customers and telling them about this for 2
weeks now. All trouble specialists should be aware of this. I'd be surprised
if any regular specialists knew about it, though. The information is
available to them, but I've found it's a rare specialist who actually keeps
up with the changing info daily.

I probably shouldn't slam my co-workers, but I'm off work, and I'm cranky
from spending too much time the last few days reprogramming phones that
someone didn't program right the first time

Leisa

Leisa wrote:


>
> It's not bunk. It's a known issue in markets that use Lucent switches. Some
> sort of software problem. A fix was rolled out in one market and if it is
> successful will be rolled out to the other markets in less than two weeks,
> at least as of the last thing I saw.

Totally dumb question from someone who knows little about these things:
would this same bug happen to affect roaming? For the longest time,
roaming carriers have been unable to verify my ESN as being active on
Sprint, and they always see my ESN as being in unactivated phone, which
gets dumped to a roaming swindl... err, operator. Considering I've
tried and owned a great number of phones while being with Sprint and ALL
have been giving me the same thing, I doubt my handset is the problem.

It's not a huge issue as I have yet to truly need to roam, but there
have been one or two cases where it would have been nice.





--
E-mail fudged to thwart spammers.
Transpose the c's and a's in my e-mail address to reply.

"Isaiah Beard" <[email protected]> wrote in message
news:[email protected]...
> Leisa wrote:
>
>
> >
> > It's not bunk. It's a known issue in markets that use Lucent switches.
Some
> > sort of software problem. A fix was rolled out in one market and if it
is
> > successful will be rolled out to the other markets in less than two
weeks,
> > at least as of the last thing I saw.
>
> Totally dumb question from someone who knows little about these things:
> would this same bug happen to affect roaming? For the longest time,
> roaming carriers have been unable to verify my ESN as being active on
> Sprint, and they always see my ESN as being in unactivated phone, which
> gets dumped to a roaming swindl... err, operator. Considering I've
> tried and owned a great number of phones while being with Sprint and ALL
> have been giving me the same thing, I doubt my handset is the problem.
>
> It's not a huge issue as I have yet to truly need to roam, but there
> have been one or two cases where it would have been nice.
>

No, I think that's 2 different issues. It sounds like you need an
authentication override, or if that doesn't work, a ticket needs to be
created to let the upper network folks look into it.

Leisa

"Leisa" <[email protected]> wrote in message
news:h5xAb.323974$ao4.1088935@attbi_s51...
>
> "Isaiah Beard" <[email protected]> wrote in message
> news:[email protected]...
> > Leisa wrote:
> >
> >
> > >
> > > It's not bunk. It's a known issue in markets that use Lucent switches.
> Some
> > > sort of software problem. A fix was rolled out in one market and if it
> is
> > > successful will be rolled out to the other markets in less than two
> weeks,
> > > at least as of the last thing I saw.
> >
> > Totally dumb question from someone who knows little about these things:
> > would this same bug happen to affect roaming? For the longest time,
> > roaming carriers have been unable to verify my ESN as being active on
> > Sprint, and they always see my ESN as being in unactivated phone, which
> > gets dumped to a roaming swindl... err, operator. Considering I've
> > tried and owned a great number of phones while being with Sprint and ALL
> > have been giving me the same thing, I doubt my handset is the problem.
> >
> > It's not a huge issue as I have yet to truly need to roam, but there
> > have been one or two cases where it would have been nice.
> >
>
> No, I think that's 2 different issues. It sounds like you need an
> authentication override, or if that doesn't work, a ticket needs to be
> created to let the upper network folks look into it.
>
> Leisa

What about something as simple as getting an new telephone number assigned
to Chris? If this is a random problem, it should clear up the problem post
haste ...

Bob

"Tim Harrick" <[email protected]> wrote in message
news:[email protected]...
> In article <[email protected]>,
> [email protected] (Chris) wrote:
>
> > Just purchased and activated my Sanyo 8100 3 days ago ($100/mo for
> > unlimited internet and 2,000 anytime minutes) and it would seem that
> > from day one people have been receiving a rapid busy signal when they
> > dial my phone. It wasn't brought to my attention until yesterday when
> > several people told me they were unable to get through to me on my new
> > number. I then tried myself and received the same thing.
>
> You do realize that the "Vision" (Internet) is only free for the first
> two months, and then you get charged $15/month for it?
>
> Sounds like you have a defective phone; and hopefully you bought it
> locally so it will be easy to return for replacement.

Ah ... come on Phillipe, spread some more additional misinformation why
don't you! Vision is provided @ no charge on accounts with 2000 AT minutes.

As to the fast busy signal, Chris did say that SPCS told him it might be
random routing problem ... I've never heard of this happening because of a
defective handset. The answer might be is for Chris to call in via a
landline, get into Tier 2 tech support, and help Chris to program a new
phone number to his phone.

Bob

That's a great idea Bob! Leisa, can I do that? Also, does this
problem affect every phone # starting with 310-497-xxxx? I just got
this # 4 days ago now so I don't care if I get a new phone # as long
as my phone works!

Chris


"Bob Smith" <[email protected]> wrote in message news:<%[email protected]>...
> "Leisa" <[email protected]> wrote in message
> news:h5xAb.323974$ao4.1088935@attbi_s51...
> >
> > "Isaiah Beard" <[email protected]> wrote in message
> > news:[email protected]...
> > > Leisa wrote:
> > >
> > >
> > > >
> > > > It's not bunk. It's a known issue in markets that use Lucent switches.
> Some
> > > > sort of software problem. A fix was rolled out in one market and if it
> is
> > > > successful will be rolled out to the other markets in less than two
> weeks,
> > > > at least as of the last thing I saw.
> > >
> > > Totally dumb question from someone who knows little about these things:
> > > would this same bug happen to affect roaming? For the longest time,
> > > roaming carriers have been unable to verify my ESN as being active on
> > > Sprint, and they always see my ESN as being in unactivated phone, which
> > > gets dumped to a roaming swindl... err, operator. Considering I've
> > > tried and owned a great number of phones while being with Sprint and ALL
> > > have been giving me the same thing, I doubt my handset is the problem.
> > >
> > > It's not a huge issue as I have yet to truly need to roam, but there
> > > have been one or two cases where it would have been nice.
> > >
> >
> > No, I think that's 2 different issues. It sounds like you need an
> > authentication override, or if that doesn't work, a ticket needs to be
> > created to let the upper network folks look into it.
> >
> > Leisa
>
> What about something as simple as getting an new telephone number assigned
> to Chris? If this is a random problem, it should clear up the problem post
> haste ...
>
> Bob

"Bob Smith" <[email protected]> wrote in message
news:%[email protected]...
>
> "Leisa" <[email protected]> wrote in message
> news:h5xAb.323974$ao4.1088935@attbi_s51...
> >
> > "Isaiah Beard" <[email protected]> wrote in message
> > news:[email protected]...
> > > Leisa wrote:
> > >
> > >
> > > >
> > > > It's not bunk. It's a known issue in markets that use Lucent
switches.
> > Some
> > > > sort of software problem. A fix was rolled out in one market and if
it
> > is
> > > > successful will be rolled out to the other markets in less than two
> > weeks,
> > > > at least as of the last thing I saw.
> > >
> > > Totally dumb question from someone who knows little about these
things:
> > > would this same bug happen to affect roaming? For the longest time,
> > > roaming carriers have been unable to verify my ESN as being active on
> > > Sprint, and they always see my ESN as being in unactivated phone,
which
> > > gets dumped to a roaming swindl... err, operator. Considering I've
> > > tried and owned a great number of phones while being with Sprint and
ALL
> > > have been giving me the same thing, I doubt my handset is the problem.
> > >
> > > It's not a huge issue as I have yet to truly need to roam, but there
> > > have been one or two cases where it would have been nice.
> > >
> >
> > No, I think that's 2 different issues. It sounds like you need an
> > authentication override, or if that doesn't work, a ticket needs to be
> > created to let the upper network folks look into it.
> >
> > Leisa
>
> What about something as simple as getting an new telephone number assigned
> to Chris? If this is a random problem, it should clear up the problem post
> haste ...
>
> Bob

The problem is not with his phone number, it's with the switch. The problem
will happen intermittently no matter what the number is as long as it's
going through a Lucent switch. Unless he changed his number to one out of a
state served by a Nortel switch, which would be pretty dumb

Leisa

"Chris" <[email protected]> wrote in message
news:[email protected]...
> That's a great idea Bob! Leisa, can I do that? Also, does this
> problem affect every phone # starting with 310-497-xxxx? I just got
> this # 4 days ago now so I don't care if I get a new phone # as long
> as my phone works!
>
> Chris
>
>

You can try it if you aren't attached to your number, but there's no
guarantee, and I doubt it would work. The problem is with the switch, not
the number, and no matter what your number is, the calls will route through
the same switch. This is a very rough description, but for the most part,
Lucent switches are West Coast and northern East Coast, and the middle of
the US is Nortel or Motorola switches. If you changed your number to one
from a state served by Nortel switches, you'd probably be fine, but even
then it might happen, because of your location at some point calls to your
phone will hit those Lucent switches anyway. And then people calling your
PCS phone from their home phone would have to pay LD charges and wouldn't be
too thrilled with you


Leisa

In article=20
<[email protected]>,=20
[email protected] says...
> Now, I have another SprintPCS phone that I have had for over 3 years
> and have NEVER had this problem with it. The rep also said the problem
> wouldn't be fixed for another 2 weeks!!
>=20
> Has anyone else gotten this line of bunk? I'm in West Los Angeles and
> would like to know if I should wait or just cancel this new plan and
> move to Nextel.
>=20

Seriously, it's not bunk. Apparently, Some regions where=20
we installed some Lucent hardware are getting misdirected=20
calls, and various forms of unavailable notice. I've only=20
had two calls on this, but there *is* an open service alert=20
on it. We're working with Lucent to try to figure out what=20
it is. At least, that's what the service alert says. It=20
only lists an open/closed status for us, not an up-to-the-
minute update.

--=20
-+-
R=D8=DF
O/Siris
I work for SprintPCS
I *don't* speak for them.

"Chris" <[email protected]> wrote in message
news:[email protected]...
> Just purchased and activated my Sanyo 8100 3 days ago ($100/mo for
> unlimited internet and 2,000 anytime minutes) and it would seem that
> from day one people have been receiving a rapid busy signal when they
> dial my phone. It wasn't brought to my attention until yesterday when
> several people told me they were unable to get through to me on my new
> number. I then tried myself and received the same thing.

A rapid busy is usually from a local exchange and not from Sprint PCS
(directly that is). That usually means an exchange is at capacity. A
hardline issue, not a wireless issue. So, it could be because Sprint has
not purchansed enough phone circuits for the particular tower you are using,
or it could be that the people in your area that are trying to call your
phone are calling *from* an overloaded system ... or the system (local phone
provider) your tower is on is overloaded. When you have trouble again, it
might be worth seeing if you can get somebody to call your cell phone from
outside your area (say a different phone company altogether, or long
distance). It does seem rather unlikely it is a capacity issue unless it is
because Sprint doesn't have enough phone circuits for the tower you are
using.

Tom Veldhouse