Direct Connect Delays

I was wondering if anyone else is having problems with direct connect. I am
using the phone in Southern California. When I try to direct connect to
some one, I get long delays or user not available. Sometimes I'll just
finished talking to someone and they will have a hard time to reply; again,
they get user not available or some other error. They may have to try
several times to connect. I was wondering if Nextel started having these
problems after they started Nationwide direct connect.

Jason

---

› See More: Direct Connect Delays

"Jason McGehee" <[email protected]> wrote in article
<[email protected]>:
> I was wondering if anyone else is having problems with direct connect. I am
> using the phone in Southern California. When I try to direct connect to
> some one, I get long delays or user not available. Sometimes I'll just
> finished talking to someone and they will have a hard time to reply; again,
> they get user not available or some other error. They may have to try
> several times to connect. I was wondering if Nextel started having these
> problems after they started Nationwide direct connect.
>
> Jason
>

NEXTEL is selling the sh*t out of its service right now and seems that
75% of the phone users I see around here has NEXTEL. They need to
expand their system capacity to fix some of these issues. Maybe this
will change when they finally decide to implement the new 12:1 PTT and
6:1 cellular vo-coder but I'm sure the voice quality will degrade.

On the technical there is also a flaw in iDEN that will cause this
especially while your mobile. Unfortunately when you, or the person
your talking to, is mobile while in PTT the phone's neighboring site
look up is only for 2 neighboring sites (while the cellular is 6 sites).
If your mobile you could move thru more than 2 sites while your talking
and the phone gets lost and has to look up the available site list all
over again once you let the button go.

There is no way to distinguish if it's capacity or site look up though
when it say's "User not Available" so its something that always happens
especially during prime time.

Mark

[posted via phonescoop.com - free web access to the alt.cellular groups]

Same problem in Las Vegas. Delays in PTT have really been popping up
lately.


> I was wondering if anyone else is having problems with direct connect. I am
> using the phone in Southern California. When I try to direct connect to
> some one, I get long delays or user not available. Sometimes I'll just
> finished talking to someone and they will have a hard time to reply; again,
> they get user not available or some other error. They may have to try
> several times to connect. I was wondering if Nextel started having these
> problems after they started Nationwide direct connect.
>
> Jason
>
>

I wondered if it was a broader problem than just my area. We've been
experiencing that constantlt here. Some may have been from the bad electral
storms, but it seems to be way beyond just that.

BD

"Ralph E. Decker" <[email protected]> wrote in message
news:BB75FFB3.1D898%[email protected]...
> Same problem in Las Vegas. Delays in PTT have really been popping up
> lately.
>
>
> > I was wondering if anyone else is having problems with direct connect.
I am
> > using the phone in Southern California. When I try to direct connect to
> > some one, I get long delays or user not available. Sometimes I'll just
> > finished talking to someone and they will have a hard time to reply;
again,
> > they get user not available or some other error. They may have to try
> > several times to connect. I was wondering if Nextel started having
these
> > problems after they started Nationwide direct connect.
> >
> > Jason
> >
> >
>

We have been seeing more of this in the Chicago market as well. It
started about the same time as they turned on NWDC.

FYI, test results on the voice quality of 6:1 indicates it will sound
better than the current system. I have not herd, however, that DC
will be on a 12:1 system.

Can anyone confirm?

-D

"BD" <[email protected]> wrote in message news:<[email protected]>...
> I wondered if it was a broader problem than just my area. We've been
> experiencing that constantlt here. Some may have been from the bad electral
> storms, but it seems to be way beyond just that.
>
> BD
>
> "Ralph E. Decker" <[email protected]> wrote in message
> news:BB75FFB3.1D898%[email protected]...
> > Same problem in Las Vegas. Delays in PTT have really been popping up
> > lately.
> >
> >
> > > I was wondering if anyone else is having problems with direct connect.
> I am
> > > using the phone in Southern California. When I try to direct connect to
> > > some one, I get long delays or user not available. Sometimes I'll just
> > > finished talking to someone and they will have a hard time to reply;
> again,
> > > they get user not available or some other error. They may have to try
> > > several times to connect. I was wondering if Nextel started having
> these
> > > problems after they started Nationwide direct connect.
> > >
> > > Jason
> > >
> > >
> >

The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
Currently its 6:1 DC and 3:1 cellular.

I'll try to dig my insider to see a deployment date as he wasn't aware
of it being anytime soon, although he did advise that the equipment at
the sites local to me are ready for the new vo-coder deployment.
--
Mark


[email protected] (dep_blueman) wrote in article
<[email protected]>:
> We have been seeing more of this in the Chicago market as well. It
> started about the same time as they turned on NWDC.
>
> FYI, test results on the voice quality of 6:1 indicates it will sound
> better than the current system. I have not herd, however, that DC
> will be on a 12:1 system.
>
> Can anyone confirm?
>
> -D
>
> "BD" <[email protected]> wrote in message news:<[email protected]>...
> > I wondered if it was a broader problem than just my area. We've been
> > experiencing that constantlt here. Some may have been from the bad electral
> > storms, but it seems to be way beyond just that.
> >
> > BD
> >
> > "Ralph E. Decker" <[email protected]> wrote in message
> > news:BB75FFB3.1D898%[email protected]...
> > > Same problem in Las Vegas. Delays in PTT have really been popping up
> > > lately.
> > >
> > >
> > > > I was wondering if anyone else is having problems with direct connect.
> > I am
> > > > using the phone in Southern California. When I try to direct connect to
> > > > some one, I get long delays or user not available. Sometimes I'll just
> > > > finished talking to someone and they will have a hard time to reply;
> > again,
> > > > they get user not available or some other error. They may have to try
> > > > several times to connect. I was wondering if Nextel started having
> > these
> > > > problems after they started Nationwide direct connect.
> > > >
> > > > Jason
> > > >
> > > >
> > >

[posted via phonescoop.com - free web access to the alt.cellular groups]

Also having problems with long delays in Central PA. I spoke to customer
care and they said it had something to do with the deployment of NWDC. I
don't buy it!

"Mark F" <[email protected]> wrote in message
news:[email protected]...
> The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
> Currently its 6:1 DC and 3:1 cellular.
>
> I'll try to dig my insider to see a deployment date as he wasn't aware
> of it being anytime soon, although he did advise that the equipment at
> the sites local to me are ready for the new vo-coder deployment.
> --
> Mark
>
>
> [email protected] (dep_blueman) wrote in article
> <[email protected]>:
> > We have been seeing more of this in the Chicago market as well. It
> > started about the same time as they turned on NWDC.
> >
> > FYI, test results on the voice quality of 6:1 indicates it will sound
> > better than the current system. I have not herd, however, that DC
> > will be on a 12:1 system.
> >
> > Can anyone confirm?
> >
> > -D
> >
> > "BD" <[email protected]> wrote in message
news:<[email protected]>...
> > > I wondered if it was a broader problem than just my area. We've been
> > > experiencing that constantlt here. Some may have been from the bad
electral
> > > storms, but it seems to be way beyond just that.
> > >
> > > BD
> > >
> > > "Ralph E. Decker" <[email protected]> wrote in message
> > > news:BB75FFB3.1D898%[email protected]...
> > > > Same problem in Las Vegas. Delays in PTT have really been popping
up
> > > > lately.
> > > >
> > > >
> > > > > I was wondering if anyone else is having problems with direct
connect.
> > > I am
> > > > > using the phone in Southern California. When I try to direct
connect to
> > > > > some one, I get long delays or user not available. Sometimes I'll
just
> > > > > finished talking to someone and they will have a hard time to
reply;
> > > again,
> > > > > they get user not available or some other error. They may have to
try
> > > > > several times to connect. I was wondering if Nextel started
having
> > > these
> > > > > problems after they started Nationwide direct connect.
> > > > >
> > > > > Jason
> > > > >
> > > > >
> > > >
>
> [posted via phonescoop.com - free web access to the alt.cellular groups]

Upstate NY here.Numerous complaints in this area.40 people I know so far
saying delayed "DC" service and "under unavailable".Sucks
Wayne



"Jason McGehee" <[email protected]> wrote in message
news:[email protected]...
> I was wondering if anyone else is having problems with direct connect. I
am
> using the phone in Southern California. When I try to direct connect to
> some one, I get long delays or user not available. Sometimes I'll just
> finished talking to someone and they will have a hard time to reply;
again,
> they get user not available or some other error. They may have to try
> several times to connect. I was wondering if Nextel started having these
> problems after they started Nationwide direct connect.
>
> Jason
>
>

That should free up a heck of a lot of time slots once they start
cranking out the new phones.

FWIW, Chicago has been much better on the DC side today. I don't know
if it is the post-holiday thing or what but I did not get the User Not
Available CO at all that I am used to getting so often.

-D

[email protected] (Mark F) wrote in message news:<[email protected]>...
> The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
> Currently its 6:1 DC and 3:1 cellular.
>
> I'll try to dig my insider to see a deployment date as he wasn't aware
> of it being anytime soon, although he did advise that the equipment at
> the sites local to me are ready for the new vo-coder deployment.
> --
> Mark
>
>
> [email protected] (dep_blueman) wrote in article
> <[email protected]>:
> > We have been seeing more of this in the Chicago market as well. It
> > started about the same time as they turned on NWDC.
> >
> > FYI, test results on the voice quality of 6:1 indicates it will sound
> > better than the current system. I have not herd, however, that DC
> > will be on a 12:1 system.
> >
> > Can anyone confirm?
> >
> > -D
> >
> > "BD" <[email protected]> wrote in message news:<[email protected]>...
> > > I wondered if it was a broader problem than just my area. We've been
> > > experiencing that constantlt here. Some may have been from the bad electral
> > > storms, but it seems to be way beyond just that.
> > >
> > > BD
> > >
> > > "Ralph E. Decker" <[email protected]> wrote in message
> > > news:BB75FFB3.1D898%[email protected]...
> > > > Same problem in Las Vegas. Delays in PTT have really been popping up
> > > > lately.
> > > >
> > > >
> > > > > I was wondering if anyone else is having problems with direct connect.
> I am
> > > > > using the phone in Southern California. When I try to direct connect to
> > > > > some one, I get long delays or user not available. Sometimes I'll just
> > > > > finished talking to someone and they will have a hard time to reply;
> again,
> > > > > they get user not available or some other error. They may have to try
> > > > > several times to connect. I was wondering if Nextel started having
> these
> > > > > problems after they started Nationwide direct connect.
> > > > >
> > > > > Jason
> > > > >
> > > > >
> > > >
>
> [posted via phonescoop.com - free web access to the alt.cellular groups]

Somewhere about Sat, 30 Aug 2003 09:06:44 GMT, someone called "Jason McGehee"
<[email protected]> said:

>I was wondering if anyone else is having problems with direct connect. I am
>using the phone in Southern California. When I try to direct connect to

I have noticed this in S. Fl. I have also noticed interrupted calls where
someone breaks into the conversation. (see my other message)

-3M TA3

Somewhere about Sat, 30 Aug 2003 09:06:44 GMT, someone called "Jason McGehee"
<[email protected]> said:

>I was wondering if anyone else is having problems with direct connect. I am
>using the phone in Southern California. When I try to direct connect to

I have noticed this in S. Fl. I have also noticed interrupted calls where
someone breaks into the conversation. (see my other message)

-3M TA3

Mark F <[email protected]> wrote:

> The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
> Currently its 6:1 DC and 3:1 cellular.

They started off as 6:1 voice, and it was horrible. They then changed to
3:1...primarily because they wanted to move beyond their traditional
"blue collar" customer base to "white collar."

I'd be very surprised if they moved to 6:1 voice again.

Mark F <[email protected]> wrote:

> The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
> Currently its 6:1 DC and 3:1 cellular.

They started off as 6:1 voice, and it was horrible. They then changed to
3:1...primarily because they wanted to move beyond their traditional
"blue collar" customer base to "white collar."

I'd be very surprised if they moved to 6:1 voice again.

Joel Horner wrote:
> Mark F <[email protected]> wrote:
>
>
>>The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
>>Currently its 6:1 DC and 3:1 cellular.
>
>
> They started off as 6:1 voice, and it was horrible. They then changed to
> 3:1...primarily because they wanted to move beyond their traditional
> "blue collar" customer base to "white collar."
>
> I'd be very surprised if they moved to 6:1 voice again.

They start rollout of 6:1 in the 4th quarter.

Joel Horner wrote:
> Mark F <[email protected]> wrote:
>
>
>>The next NEXTEL vocoder upgrade will be 12:1 DC and 6:1 cellular.
>>Currently its 6:1 DC and 3:1 cellular.
>
>
> They started off as 6:1 voice, and it was horrible. They then changed to
> 3:1...primarily because they wanted to move beyond their traditional
> "blue collar" customer base to "white collar."
>
> I'd be very surprised if they moved to 6:1 voice again.

They start rollout of 6:1 in the 4th quarter.