Jump to content

Will NV upgraded sites reduce/eliminate NID border missed call issue?


larryt510

Recommended Posts

I've been wondering if the new network vision equipment will finally solve the old problem of missed incoming calls while moving between two or more cell sites that are located on different network switches (NID's). When I say a 'missed incoming call' I am referring to incoming calls that never make it to the phone and instead get dumped to voicemail. Calls that get lost in the network paging channel before the phone can see the call.

 

This has been a problem here for as long as I can remember dating back to 1997 when I first signed up with Sprint. I spend a significant amount of my time while connected and bouncing back and forth between one cell site located on Irvine switch #1 and Irvine switch #2 here in Orange County, CA. Oddly Verizon has/had the exact same NID border location as Sprint here. No idea if that was just a coincidence or not.

 

The issue has already improved a lot since about 2009. Instead of missing 2-3 calls per day it only seems to happen about once every other day now. Not sure if today's modern phones are better at finding incoming calls or some sort of software patch was made on the network side by the vendors that helped.

 

Have any of the resident technology experts here heard anything about this? I know it's not a commonly known about or discussed problem but thought I would ask anyway.

Link to comment
Share on other sites

Likely, no, Network Vision will not provide any service improvement along NID boundaries, as Network Vision does not change the geography of NIDs and MSCs.

 

About the only improvement you can hope for is that the enhanced signal strength from a CDMA1X 800 site/sector on one side of the NID boundary is sufficient to overcome pilot pollution from other sites/sectors on the other side of the NID boundary. That could be enough to keep your handset registered with one NID, rather than bouncing between two of them.

 

AJ

Link to comment
Share on other sites

Yeah that's what I suspected but was hoping that maybe the new equipment would have software patches that addressed the missed call/NID boundary issue. You would think by now that they would have been able to come up with a fix after 15+ years.

Link to comment
Share on other sites

Yeah that's what I suspected but was hoping that maybe the new equipment would have software patches that addressed the missed call/NID boundary issue. You would think by now that they would have been able to come up with a fix after 15+ years.

 

Software on the network side will not fix anything. Idle handsets are not under network control. And the handsets are operating exactly as designed. In deploying a cellular network across hundreds of thousands of square miles, the SID/NID boundary issue is just the nature of the beast.

 

AJ

Link to comment
Share on other sites

Well I'm pretty sure that something changed to improve this over the past 4-5 years. Maybe an improvement with the handsets? Because it's a lot better now than it used to be and nothing else has changed with the cell sites around here that I know about.

Link to comment
Share on other sites

Well I'm pretty sure that something changed to improve this over the past 4-5 years. Maybe an improvement with the handsets? Because it's a lot better now than it used to be and nothing else has changed with the cell sites around here that I know about.

 

CDMA2000 devices use a quick paging channel that is about 20 times faster than the previous cdmaOne paging channel. So, likely, devices can switch between NIDs/MSCs and register more quickly.

 

AJ

  • Like 1
Link to comment
Share on other sites

Interesting. When did the CDMA2000 devices begin?

 

CDMA2000 began with CDMA1X.

 

AJ

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

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

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