Jump to content

Airave Handoff with neighbor, calls dropping


spotmeterf64

Recommended Posts

I had an Airave for a few months, and it worked fine for a while. After about 2 months of using it, somebody moved in to this apartment complex and also had an Airave. My phone would attempt to handoff the call to the other Airave (even though my Airave obviously provided a much stronger signal) and my voice quality would decline for about 15 seconds, then the call would drop. This happened without fail 5-10 minutes into EVERY phone call. My signal strength would go from full signal to 1 bar, then the call would drop. Also, texts would come in late in one big batch and calls would be sent to Voicemail.

 

I ended up sending the Airave back, since everything they suggested wouldn't work. I even posted here for help; nothing worked. It wasn't until I sent the Airave back that I discovered my neighbor also has an Airave (I kept hearing the three tones before connecting the call even after my Airave was boxed back up, initially I thought I was going nuts).

 

My question is, if I do go to Sprint and get a new Airave sent to me (the signal isn't getting any better), is there a way to prevent my phone from attempting to handoff the call to the other Airave? Or is there some other way of dealing with this issue, minus putting up copper mesh along my walls to block the other Airave's signal?

 

I really want to figure this out, since Sprint works perfectly everywhere else I need it but my neighborhood near RDU Airport. Thanks!

Link to comment
Share on other sites

Your neighbor needs to lock down his Airave so that only permitted devices use it.

 

AJ

Link to comment
Share on other sites

Can the neighbor do this through calling Airave customer service, or the standard Sprint customer service line?

 

Will this prevent my phone from connecting to their Airave all together, or will it simply block services once I do connect? I've heard conflicting information on this. I am about to call Sprint's Airave CS line to get some detailed information on how this can be accomplished.

 

Thanks for that tip; hopefully this is the secret I need. I hope this will fix the problem and allow me to get a new Airave; breaking a cell contract is a lot cheaper than breaking an apartment lease.

Edited by spotmeterf64
Link to comment
Share on other sites

Update: Called Sprint's Airave Technical Support (not the standard phone support, the number listed on sprint.com/airave) and they said they can contact the other Airave user and walk them through blocking my device from connecting. In the meantime, they are sending me a new Airave.

 

Thanks for the tip, WiWavelength!

Link to comment
Share on other sites

Update: Called Sprint's Airave Technical Support (not the standard phone support, the number listed on sprint.com/airave) and they said they can contact the other Airave user and walk them through blocking my device from connecting. In the meantime, they are sending me a new Airave.

 

Thanks for the tip, WiWavelength!

 

I think you need to give this number to the other user in the Network forum. :D

Link to comment
Share on other sites

when did they finally fix the blocking settings?

 

Also, wont you still connect to the neighbors but be restricted from making calls through it?

 

I suppose they're working now! The way the Airave tech made it sound, it will actually block me from connecting to the Airave. This remains to be seen. I'll update once the new Airave comes and it's set up as it should be.

Link to comment
Share on other sites

The other thought would be to get your Airave on a different carrier channel from that of your neighbor's Airave. Honestly, that should be configurable -- either by Sprint tech support or via a little bit of end user hacking -- but I am not sure that it is. Sprint has seven potential CDMA2000 carrier channel assignments in Raleigh-Durham, so there is enough spectrum to go around, though that could be a problem in other markets.

 

AJ

Link to comment
Share on other sites

I suppose they're working now! The way the Airave tech made it sound, it will actually block me from connecting to the Airave. This remains to be seen. I'll update once the new Airave comes and it's set up as it should be.

 

Honestly, i think you will still connect to it...just you will receive an error when you try to make any calls which puts you in worse shape than you are in. I believe the error states something to the effect of connecting to a sprint private network.

 

Back when the airave first came out, users complained of not being able to make any calls when in range of an airave that had been locked down. Shortly after, sprint disabled these settings.

 

I think your neighbor would be better off lowering the strength of their unit. I think there is three power settings.

Link to comment
Share on other sites

I wish that would work, mc_gusto. These are 1 bedroom apartments (800 sqft or so), so even if they were are on opposite sides they would probably still overlap.

 

I got my Airave in the mail the day before yesterday. So far it's been flawless on my GNex and BlackBerry; signal is always 5 bars (-63dBm pretty consistently throughout the apartment). Texts come in quickly and go out quickly. Calls are amazingly clear, no static or dropouts. I Have not had a single dropped call, nor has my phone even once connected to my neighbor's Airave, even when I stand beside the wall we share. I suppose the blocking thing Sprint did really worked.

 

They sent me an Airave 2 rather than the 2.5 though, which I thought was interesting. I'm not complaining, it's been working perfectly so far and I don't even know what the difference is.

  • Like 2
Link to comment
Share on other sites

They sent me an Airave 2 rather than the 2.5 though, which I thought was interesting. I'm not complaining, it's been working perfectly so far and I don't even know what the difference is.

 

Airave 2 has a phone jack so you can plug in a landline phone and use the VoIP service. 2.5 removes that phone jack, but makes the Airave smaller (compact) in size. Another difference is the GPS module; it looks a little different but should function the same.

 

Sent from my Rooted Galaxy Note II using Tapatalk 2.

 

 

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

    • As far as I know it's ubiquitous. Ultimately the network decides if you should use VoNR vs VoLTE but pretty much anytime my phone is in standalone mode and I place a call, it goes over NR.   Yup, it was terrible. After a while, I just connected to the WiFi, and that worked fine at about 90Mbps. I get the feeling that rather than doing a "real" upgrade where they install new antennas, upgrade backhaul, etc., T-Mobile instead installed new radios onto the existing and already overloaded DAS and called it a day, which isn't enough. Compared to Yankee Stadium, where they actually went and deployed new antennas/radios for their n41 upgrade, and you're able to get upwards of 200Mbps at sold-out games, Arthur Ashe really is a joke. What's worse is that the folks in their NOC likely know this already, but no effort is being made to change that. I'm not asking for T-Mobile to deploy mmWave everywhere like Verizon but there is a real use case for it at stadiums.
    • Does anyone know how well implemented is VoNR in the 5 boroughs. Does anyone use it? I have an iPhone 15 Pro. Does anyone know if T-Mobile is still working on upgrading their network? It seems like the service has gone down. My phone struggles in parts of the Belt Pkwy, and data is slow. 
    • I come to the US Open men’s semifinals and finals every year, and I’ve never been able to use my T-Mobile phone successfully. Usually AT&T is the top performer—good to hear Verizon has upped their game. 
    • One sector down, two more to go — — — — —  I was at Arthur Ashe Stadium for the U.S. Open today and the good news is that there is an n25/41 DAS setup throughout USTA Billie Jean King National Tennis Center. From the "boardwalk" to the outdoor concession area, to inside the stadium; you connect to standalone n41 and n25 everywhere via oDAS and iDAS. The bad news is that in the actual stadium it's beyond useless. While I saw strong coverage as indicated by signal bars and I was able to make calls and send texts, there was no data throughput at all. Running a speed test failed 9 out of 10 times. The only time I got a speed test to work was by switching to LTE funnily enough or by using NSA 5G where the test would initiate via LTE and then n41 would kick in giving me ~20Mbps. T-Mobile has so much traffic on their 5G network that now n41 gets bogged down before LTE. That was a first for me! In the stadium in the same area Verizon got 1.2Gbps on mmWave and LTE kept timing out when trying to test it. My Boost line on AT&T got upwards of 150Mbps on C-band and I know they have mmWave deployed as I saw their Nokia mmWave antennas deployed but I was unable to test it. In the outdoor concession area T-Mobile performed well getting over 150Mbps on n41. AT&T in these areas saw over 250Mbps on C-band and I didn't get the opportunity to test Verizon there. It just seems like 140MHz n41 is not enough capacity for the amount of people inside the stadium. Hopefully T-Mobile is considering deploying n258 to all of these stadiums since they now own that mmWave nationwide. It'd make a world of difference in terms of capacity at these venues. Bonus Pics: Verizon and AT&T mmWave Hidden carrier neutral DAS: 
  • Recently Browsing

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