Jump to content

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


larryt510
 Share

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

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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • I did mention it before, but I don't remember if I did post a picture of it, so I did a 2-for-1 special the second time around. Ah, so that is what I saw. I walk by Boys and Girls field if the C train takes forever to show up in the late evening, but I cared more about getting home than investigating it lol
    • August update finally arrived for S22+ unlocked tonight 👍
    • You also snagged a shot of the new oDAS in there, too.    I also spotted one while on LIRR above Atlantic Ave. They’re starting to really get rolled out now.
    • I have added T-Mobile eNB 879366, a Sprint convert site, to the list of gig+ sites, as I was able to break the 800 Mbps ceiling with it. I'm still trying to understand the DAS mess at LGA and locate them, but the bad thing about it is inside the terminals I can occasionally pick up the macros inside. It anchors 5G, which is great for a speed boost, but occasionally data hangs because my device is having a handoff frenzy trying to pick the best macro and/or band for the 5G connection.   I have spotted 2 more Dish sites, one on the corner of Church Avenue and East 16th (photo below), and the other is an in progress site co-located with Verizon eNB 81069.   At Verizon eNB 81069, the ports on the Dish panel weren't connected yet, brand new racks were being used on the roof Verizon is on, and it looks like Sprint's equip is still up on the building next door.
    • Neat!  Thanks.  Most of my issues at the moment are from inexperience.  I've never used AT commands and I'm bad at Python.  I'm not really sure what the best way is to send AT commands to the modem; socat seems to work, and there are Python libraries that should do it, but I don't really know what I'm doing.  - Trip
  • Recently Browsing

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