Jump to content

How does an Airave work?


Recommended Posts

I had an old router when I activated Wi-Fi calling.  The Wi-Fi calling worked fine when I had very little other traffic flowing over the router.

But when the the internet traffic picked up, the calls got choppy.  My router worked fine otherwise, but the QOS on the router would not fix the choppy calls.  The new router from Sprint did.

The only issue I have with the Wi-Fi calling is the delay. The two people in the conversation are talking over each other because of the delay.  The Wi-Fi calling also just disconnects mostly at night and I have to restart it.  For some reason, it drops and when it does, it requires a manual restart.  Using a Galaxy S-5. My new router arrived in about 2 days and was totally Free.

 

I just called them and they said they had to create an escalated ticket for the Wifi Connect router request since the offer was not currently linked to my account.  They said it was no problem to get the Wifi Connect router but instead of the normal 7 business days it would take to receive they said it would take 10 business days because of the need to get a request.  That sounds so much longer than the 2 days you quoted.  Hopefully it will only take a week to arrive.

Link to comment
Share on other sites

Not sure if this is the right place to ask this but I've noticed that when I'm on my airave, I can't pick up eHRPD, only EVDO Rev. A. Does anyone else have this problem and a possible resolution?

 

eHRPD is EV-DO.  There is no problem, no resolution.

 

AJ

Link to comment
Share on other sites

I know the air interface is the same, my question is as to why I'm going through a legacy core, not an LTE EPC?

 

Any Airave is a legacy device.  An LTE Airave type device does not yet exist.  eHRPD requires LTE compatibility, as it maintains IP continuity between LTE and EV-DO.

 

AJ

  • Like 1
Link to comment
Share on other sites

Any Airave is a legacy device. An LTE Airave type device does not yet exist. eHRPD requires LTE compatibility, as it maintains IP continuity between LTE and EV-DO.

 

AJ

I have used eHRPD on newer airaves (at other ppl's houses). I'm aware they don't support LTE but they do support eHRPD for smooth handoff between the airave and LTE I thought.

Link to comment
Share on other sites

 I don't think we will see LTE airaves. Wifi routers like the one that is available now from Sprint are simpler to set up and the equipment is less costly.

 

Any Airave is a legacy device.  An LTE Airave type device does not yet exist.  eHRPD requires LTE compatibility, as it maintains IP continuity between LTE and EV-DO.

 

AJ

 

  • Like 2
Link to comment
Share on other sites

  • 3 months later...

Has anyone heard of an AirRave 2.5 that doesn't communicate properly? It seems to never complete booting up. In almost one month, 0 packets are ever received on that switch interface. Dead box?

Do you have the correct pretty forwarding setup on your router? I personally found that it works more reliably putting it in the DMZ rather than just port forwarding. All it does is setup an IPsec VPN, but putting it in the DMZ means it won't use UDP encapsulation which may explain why that works better.

 

Sent from my Nexus 6P

Link to comment
Share on other sites

 

 

Do you have the correct pretty forwarding setup on your router? I personally found that it works more reliably putting it in the DMZ rather than just port forwarding. All it does is setup an IPsec VPN, but putting it in the DMZ means it won't use UDP encapsulation which may explain why that works better.

 

Sent from my Nexus 6P

It initially worked, got unplugged for some unknown amount of time and then didn't work. Port forwarding wouldn't come into play yet as the AirRave literally never sends a packet. The inbound packet counter on the switch interface is zero.

 

I wouldn't think being in a DMZ would affect TCP vs UDP. I also won't put anything into a DMZ due to security concerns.

 

I do have an atypical routing setup, but that's not coming into play as the AirRave is completely unresponsive on the network port.

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

It initially worked, got unplugged for some unknown amount of time and then didn't work. Port forwarding wouldn't come into play yet as the AirRave literally never sends a packet. The inbound packet counter on the switch interface is zero.

 

I wouldn't think being in a DMZ would affect TCP vs UDP. I also won't put anything into a DMZ due to security concerns.

 

I do have an atypical routing setup, but that's not coming into play as the AirRave is completely unresponsive on the network port.

 

Sent from my Nexus 6 using Tapatalk

What I meant was that IPsec ideally doesn't use UDP or TCP, it has it's own type of IP packet that gets encapsulated within a UDP packet when behind NAT. Sprint recommends putting the airave in front of your router actually (perhaps because of this?), but the passthrough performance is awful.

 

What do the status lights on your airave indicate? I'm guessing not all of them are solid green. Does it have a GPS lock? One of them is probably blinking or red, and that should indicate the problem.

 

Sent from my Nexus 6P

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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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