Jump to content

Brick wall: Sprint eChat and eCSFB issues


burnout8488

Recommended Posts

I've been reporting eCSFB issues through eChat to Sprint for about a month now. My local market (Binghamton, NY) is generally B25 LTE complete, however triband phones cannot place or receive calls when connected to LTE. I've tested this on multiple phones, on multiple sites all around the area.

 

I've provided them with site numbers, but all they come back with is that the upgrades are complete in my area and that they are sorry. We are not 1x800 accepted yet. Is 800 acceptance going to be what fixes these eCSFB issues? 

 

When I use my N5 in the Lehigh Valley market on 1x800 + LTE accepted sites, I can place and receive calls flawlessly when connected to LTE. So I know it's not the device. 

 

My local area has been like this since January - this means that pretty much every (triband) customer here hasn't been able to make or receive calls since then on the LTE sites. I find it hard to believe. 

 

Is it common that LTE accepted sites without 1x800 have these calling issues? Is a 1x800 acceptance really what will fix this eventually? (Not because it's 800, but because THEN the site will be fully upgraded?)

Link to comment
Share on other sites

  • 2 weeks later...

how to i get a tower that constantly fails escalated nicely .  I don't want to come of as D***.  But i get cdma 800 of distant tower no data. Spo i swapped with gs4 same issue.  I keep getting, from sprint  i pin pointed  your tower and let techs know.  I know im not on my tower i have gotten lte at my house and its at -119 and ehrpd is -111.  When my tower is up i get -77db.    I call in monthly and get same response.    :wall:

Link to comment
Share on other sites

how to i get a tower that constantly fails escalated nicely . I don't want to come of as D***. But i get cdma 800 of distant tower no data. Spo i swapped with gs4 same issue. I keep getting, from sprint i pin pointed your tower and let techs know. I know im not on my tower i have gotten lte at my house and its at -119 and ehrpd is -111. When my tower is up i get -77db. I call in monthly and get same response. :wall:

Try the phone number in the link that you just quoted.

Link to comment
Share on other sites

I called last week, nothing has changed so far. I vaguely remember seeing something on the forums about opening a ticket. They merely pinpointed the sites I was having eCSFB issues on (all of them in my market). Do I need to create a ticket to further escalate this issue? 

 

The representative mentioned that there had already been six other calls about this same issue in my market, and at six, they start to take action. 

 

I mentioned eCSFB and got no response - this team should know what that is, right?

Link to comment
Share on other sites

I called last week, nothing has changed so far. I vaguely remember seeing something on the forums about opening a ticket. They merely pinpointed the sites I was having eCSFB issues on (all of them in my market). Do I need to create a ticket to further escalate this issue? 

 

The representative mentioned that there had already been six other calls about this same issue in my market, and at six, they start to take action. 

 

I mentioned eCSFB and got no response - this team should know what that is, right?

 

Pinpoint is useless for eCSFB issues. You have to get a ticket open. And no, even most of the advanced support team is clueless about eCSFB. Some of them are aware that tri-band devices have specific issues, but generally they aren't any more knowledgeable than that.

Link to comment
Share on other sites

Pinpoint is useless for eCSFB issues. You have to get a ticket open. And no, even most of the advanced support team is clueless about eCSFB. Some of them are aware that tri-band devices have specific issues, but generally they aren't any more knowledgeable than that.

I'll call back tomorrow then. (Or Monday if they're closed on weekends)

Link to comment
Share on other sites

  • 2 weeks later...

After the 72786 my phone number is changed to 000-000-9576 and the MIN is 0000009576. I spent about an hour in a Sprint store. Before resorting to a factory reset, he tried a 72786 on an LG G2 and it ended up broken also. He thought it was a network problem because it also screwed up the G2. Does that sound reasonable? I also spent about an hour this evening on the phone with Sprint tech support. She was going to check the network and call me back, but I didn't get a call back.

Link to comment
Share on other sites

After the 72786 my phone number is changed to 000-000-9576 and the MIN is 0000009576. I spent about an hour in a Sprint store. Before resorting to a factory reset, he tried a 72786 on an LG G2 and it ended up broken also. He thought it was a network problem because it also screwed up the G2. Does that sound reasonable? I also spent about an hour this evening on the phone with Sprint tech support. She was going to check the network and call me back, but I didn't get a call back.

I had to restore my nexus 5 after doing this. Being connected to WiFi didn't seem to help, but it didn't have self activation in settings.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...