Phone Scoop

printed September 2, 2014
See this page online at:
http://www.phonescoop.com/carriers/forum.php?fm=m&ff=6&fi=1996551

Home  ›  Carriers  ›

Nextel

Info & Phones News Reviews › Forum  

Back to message list

Replying to:  Blackberry Curve 8350i Feedback and Echo by f38urry   Feb 6, 2009, 9:04 PM

Re: Blackberry Curve 8350i Feedback and Echo

by cellphonesaretools    Feb 7, 2009, 11:32 AM

Echo-back is a fairly common ocurrence, can happen with any of the carriers from time-to-time. It is far more likely to be the network than your son't handset, but read on...

When I have had echo-back on my iDEN handset I only know about it when I hear it on my end. I've never had anyone on the other end complain that THEY hear echo-back.

Years ago I went through a severe echo-back problem that the iDEN NETS engineer eventually traced to a bad circuit board in one of the switches/controllers in one of the tower base-stations in my local area. That was back when Nextel worked very diligently to solve network problems quickly, and they would actually assign a genuine network engineer to your issue and the engineer himself/herself would actually call you personally and work with you until the problem was solved. Since Sprint took over, that way of solving issues has unfortunately been deep-sixed.

I suggest these steps:

1) FIRST, make sure both parties have their volume control no more than half-way up. If either or both parties have volume control maxed out, that can cause mild echo-back, expecially if one or both parties is on speakerphone.

2) Have your son note the following data whenever the problem occurs (keep a pocket notebook handy, and be accurate):

a) Date & time of the problem call (incl AM or PM)

b) Location of both parties involved (either an actual street address, or the names of the closest two intersecting streets, etc.)

c) Both phone numbers involved, and whether each is a mobile or landline.

d) Which party initiated the call.

e) Accurately describe what each party experienced/heard.

f) After recording the above information, disconnect the call and try again, and note the results for the re-tried call. If it does the same thing again, jot that down, disconect the second call, and have the OTHER party try placing the call the third time. Note the results.

I know that seems like a lot of trouble, but that is the minimum information that the network engineers require to be able to track down the problem.

Always report the problem within 24 hours of each occurrence, because if you wait too long, the super-detailed call data gets overwritten and the trail goes cold.

I wish you the best of luck. As I said, the former Nextel would work with you until the issue was solved. With the new Sprint-Nextel, I will be pleasantly surprised if you make any headway with the stonewalling tactics of front-line CS agents they put on the phones these days. But, it's worth a try. If calling in doesn't get you anywhere, send an email to "Dan@Sprint.com" or to "YouTellUs@Sprint.com" and explain the problem to them. At least that will increase the chance that a higher-level CS person will actually talk to a network engineer on your behalf.

Good luck, and be sure to post back to us with your results.

Report to moderator

Replies


Reply You must log in to reply.

Back to message list

‹ all carrier forums

Subscribe to Phone Scoop News with RSS Follow @phonescoop on Twitter Phone Scoop on Facebook Phone Scoop on Google+ Subscribe to Phone Scoop on YouTube Follow on Instagram

 

All content Copyright 2001-2014 Phone Factor, LLC. All Rights Reserved.
Content on this site may not be copied or republished without formal permission.
2