missed calls

One thing that happens on about 20% of the calls I get on my Kyocera 7135
and my wife gets on her Motorola T720, we'll have 4 bars and get a
voicemail. It is clear that somebody just called and the phone never rang.
Does anybody else have this happen? I've talked to some Verizon people and
they have lots of guesses but so far no real suggestions on how to fix this.
I'm curious if their network in San Diego is just too crowded. Also it
sounds like they might be using an older switch here in San Diego. Any
ideas on how to get this fixed? It's very frustrating!

paul

constantly on my T720.....nver had it happen on my Kyocera 6035 though

On Sat, 4 Oct 2003 00:39:50 -0700, "Paul J"
<no_spam_today_please@cox.net> wrote:

>One thing that happens on about 20% of the calls I get on my Kyocera 7135
>and my wife gets on her Motorola T720, we'll have 4 bars and get a
>voicemail. It is clear that somebody just called and the phone never rang.
>Does anybody else have this happen? I've talked to some Verizon people and
>they have lots of guesses but so far no real suggestions on how to fix this.
>I'm curious if their network in San Diego is just too crowded. Also it
>sounds like they might be using an older switch here in San Diego. Any
>ideas on how to get this fixed? It's very frustrating!
>
>paul
>

See another post but I'll tell you that VZ will always give the canned
"equipment" response and suggest you buy another phone and of course extend
the contract another year or 2 and it won't get better because they'll tell
you to buy whatever is a high profit maker for them. Been there and fell for
it. It's their service. If it gets any better SPCS will start to look good

Larry
"Paul J" <no_spam_today_please@cox.net> wrote in message
news:5Pufb.40935$gv5.38359@fed1read05...
> One thing that happens on about 20% of the calls I get on my Kyocera 7135
> and my wife gets on her Motorola T720, we'll have 4 bars and get a
> voicemail. It is clear that somebody just called and the phone never
rang.
> Does anybody else have this happen? I've talked to some Verizon people
and
> they have lots of guesses but so far no real suggestions on how to fix
this.
> I'm curious if their network in San Diego is just too crowded. Also it
> sounds like they might be using an older switch here in San Diego. Any
> ideas on how to get this fixed? It's very frustrating!
>
> paul
>
>

"Paul J" <no_spam_today_please@cox.net> wrote in message
news:5Pufb.40935$gv5.38359@fed1read05...
> One thing that happens on about 20% of the calls I get on my Kyocera 7135
> and my wife gets on her Motorola T720, we'll have 4 bars and get a
> voicemail. It is clear that somebody just called and the phone never
rang.
> Does anybody else have this happen? I've talked to some Verizon people
and
> they have lots of guesses but so far no real suggestions on how to fix
this.
> I'm curious if their network in San Diego is just too crowded. Also it
> sounds like they might be using an older switch here in San Diego. Any
> ideas on how to get this fixed? It's very frustrating!
>
> paul
>
>

I have been having the same problem (I travel full time and sometimes calls
go direct to voicemail even if I have the phone on), I was told a
possibility (don't know if it's accurate, but it sounded good). Supposedly
each cell site has a list of phones that are active on that site, when you
turn on the phone, you get added to the top of the list so the site knows
you are there, as more people log on, you get moved down the list. If you go
out of the area, or go somewhere with no signal your phone can't say "I'm
still here" and you are taken off the list, if you leave it turned on and
charging (like I used to do), after a while there are so many active phone
numbers on the list, you get "bumped" and no longer appear on the list of
active phones (hence go to email, same as phone being off or out of the
area). Like I said, I don't know how accurate that is, but I have noticed
that lost calls usually only happen when the phones been on for a while,
never when I first turn it on. There supposedly is a *xx number you can dial
to register again on the network <I forget what the correct number is, maybe
someone here knows>, but it does the same thing as turning the phone off and
back on again, and forces you back to the top of the list.

On Sat, 4 Oct 2003 05:14:33 -0700, "Peter Pan"
<Marcs1102NOSPAM@Hotmail.com> posted in alt.cellular.verizon:

>There supposedly is a *xx number you can dial
>to register again on the network <I forget what the correct number is, maybe
>someone here knows>, but it does the same thing as turning the phone off and
>back on again, and forces you back to the top of the list.

*18 if you're in a native verizon area.

Another possibility is that the cell is overloaded. The signal
strength is still good, but the cell can't handle any more calls.
Even though the number of calls a CDMA cell can handle is dynamic,
there's a limit.

If this usually happens around 5:15PM on a weekday, but never at 3:AM
on a weekday, that could be the problem.

I am in my home area and just tried *18. Received the following
message: "Welcome to Verizon Wireless, Your call can not be completed as
dialed. Please check the number and dial again, 59002".

Al Klein <rukbat@pern.org> wrote in article
<3trtnvseui752g4egg5ref1h989crnqn4o@Pern.rk>:
> On Sat, 4 Oct 2003 05:14:33 -0700, "Peter Pan"
> <Marcs1102NOSPAM@Hotmail.com> posted in alt.cellular.verizon:
>
> >There supposedly is a *xx number you can dial
> >to register again on the network <I forget what the correct number is, maybe
> >someone here knows>, but it does the same thing as turning the phone off and
> >back on again, and forces you back to the top of the list.
>
> *18 if you're in a native verizon area.
>
> Another possibility is that the cell is overloaded. The signal
> strength is still good, but the cell can't handle any more calls.
> Even though the number of calls a CDMA cell can handle is dynamic,
> there's a limit.
>
> If this usually happens around 5:15PM on a weekday, but never at 3:AM
> on a weekday, that could be the problem.

[posted via phonescoop.com]

I have experienced this occasionally over the past few years while using a
variety of different phones. Because I live in a major metropolitan area, I
have always worked under the assumption that when the call was placed, all
the channels on my local cell site were in use, causing the call to be
diverted to voicemail.

Sometimes you can experience the same thing using a landline if you try to
call Uncle Bob or grandma long distance on Christmas or Thanksgiving (when
everyone else in the country is doing the same thing). However in that case,
rather than go to voice mail the call is diverted to a message that says all
circuits are busy.


"Paul J" <no_spam_today_please@cox.net> wrote in message
news:5Pufb.40935$gv5.38359@fed1read05...
> One thing that happens on about 20% of the calls I get on my Kyocera 7135
> and my wife gets on her Motorola T720, we'll have 4 bars and get a
> voicemail. It is clear that somebody just called and the phone never
rang.
> Does anybody else have this happen? I've talked to some Verizon people
and
> they have lots of guesses but so far no real suggestions on how to fix
this.
> I'm curious if their network in San Diego is just too crowded. Also it
> sounds like they might be using an older switch here in San Diego. Any
> ideas on how to get this fixed? It's very frustrating!
>
> paul
>
>

On Sat, 04 Oct 2003 16:44:49 -0000, als@net.net (Al S) posted in
alt.cellular.verizon:

>I am in my home area and just tried *18. Received the following
>message: "Welcome to Verizon Wireless, Your call can not be completed as
>dialed. Please check the number and dial again, 59002".

I just tried it. I got the 3 short beeps that signify that a service
has worked.

Different areas, different bugs.

(Try *230.)

I tried *18 and got about 15 short quick beeps. Do you supposed this means
it worked or was an error??

paul

"Al Klein" <rukbat@pern.org> wrote in message
news:8tfunvc5ci64dokaj3mllf72dcos80kt6d@Pern.rk...
> On Sat, 04 Oct 2003 16:44:49 -0000, als@net.net (Al S) posted in
> alt.cellular.verizon:
>
> >I am in my home area and just tried *18. Received the following
> >message: "Welcome to Verizon Wireless, Your call can not be completed as
> >dialed. Please check the number and dial again, 59002".
>
> I just tried it. I got the 3 short beeps that signify that a service
> has worked.
>
> Different areas, different bugs.
>
> (Try *230.)

It's called "multipath". Radio signals bounce off conductive objects,
like buildings, mountains, airplanes (RF loves airplanes), etc. The
signal that comes straight at you from a tower at some distance gets
to you a few microseconds before the signal that bounced off American
634 headed to Phoenix. Both signals have data on them for your little
toyphone computer, including the ESN they're trying to call. The data
gets confused in the process because the TIMING, ever important in
every computer circuit in the world, is screwed up by the multipath.
So, you get no ring, no call, no answer, dropped calls, nada, crappy
service.

The solution is much simpler than you can imagine! MORE towers CLOSER
together.....instead of more advertising, toy ringers, internet
service that sucks, video games, PTT or other get-rich-quick schemes
the company bureaucrats can dream up to waste the money that SHOULD
have been spent on INFRASTRUCTURE, but was diverted to pretty nonsense
for the teenage girls to woo over. It's a matter of company
priorities.....unless we can get the FCC interested in FORCING them to
PERFORM to their LICENSES.



On Sat, 4 Oct 2003 00:39:50 -0700, "Paul J"
<no_spam_today_please@cox.net> wrote:

>One thing that happens on about 20% of the calls I get on my Kyocera 7135
>and my wife gets on her Motorola T720, we'll have 4 bars and get a
>voicemail. It is clear that somebody just called and the phone never rang.
>Does anybody else have this happen? I've talked to some Verizon people and
>they have lots of guesses but so far no real suggestions on how to fix this.
>I'm curious if their network in San Diego is just too crowded. Also it
>sounds like they might be using an older switch here in San Diego. Any
>ideas on how to get this fixed? It's very frustrating!
>
>paul
>
>


Larry W4CSC

3600 planes with transponders are burning 8-10 million
gallons of kerosene per hour over the USA. R-12 car air
conditioners are responsible for the ozone hole, right?

"Al Klein" <rukbat@pern.org> wrote in message
news:3trtnvseui752g4egg5ref1h989crnqn4o@Pern.rk...
> On Sat, 4 Oct 2003 05:14:33 -0700, "Peter Pan"
> <Marcs1102NOSPAM@Hotmail.com> posted in alt.cellular.verizon:
>
> >There supposedly is a *xx number you can dial
> >to register again on the network <I forget what the correct number is,
maybe
> >someone here knows>, but it does the same thing as turning the phone off
and
> >back on again, and forces you back to the top of the list.
>
> *18 if you're in a native verizon area.

FWIW; I just tried it in Colorado Springs, CO and got the message "Welcome
to Verizon Wireless. Your feature has been activated. Message number 51
something."

"Paul J" <no_spam_today_please@cox.net> wrote in message
news:5Pufb.40935$gv5.38359@fed1read05...
> One thing that happens on about 20% of the calls I get on my Kyocera 7135
> and my wife gets on her Motorola T720, we'll have 4 bars and get a
> voicemail. It is clear that somebody just called and the phone never
rang.

Constantly on my 730. Never on my A310.

On Sat, 4 Oct 2003 15:19:06 -0700, "Paul J"
<no_spam_today_please@cox.net> posted in alt.cellular.verizon:

>I tried *18 and got about 15 short quick beeps. Do you supposed this means
>it worked or was an error??

It's supposed to be 3 beeps. I have no idea what 15 beeps means.
"Hard drive failure"?

On Sun, 5 Oct 2003 19:13:09 -0600, "Kirk-O-Scottland" <kos@kosiam.not>
posted in alt.cellular.verizon:

>"Al Klein" <rukbat@pern.org> wrote in message
>news:3trtnvseui752g4egg5ref1h989crnqn4o@Pern.rk.. .
>> On Sat, 4 Oct 2003 05:14:33 -0700, "Peter Pan"
>> <Marcs1102NOSPAM@Hotmail.com> posted in alt.cellular.verizon:

>> >There supposedly is a *xx number you can dial
>> >to register again on the network <I forget what the correct number is, maybe
>> >someone here knows>, but it does the same thing as turning the phone off and
>> >back on again, and forces you back to the top of the list.

>> *18 if you're in a native verizon area.

>FWIW; I just tried it in Colorado Springs, CO and got the message "Welcome
>to Verizon Wireless. Your feature has been activated. Message number 51
>something."

That means that you turned on "follow-me roaming", IIRC. Which
doesn't really exist, since roaming is (supposed to be) automatic
these days. But the network knew that your phone was available, so
you should have had no problem getting incoming calls after that.
(Whether you did or not before.)