Jump to content

How does an Airave work?

Moropo
 Share

Recommended Posts

ericdabbs Member Level: LTE Advanced

ericdabbs

Posted
Posted

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.

  • Replies 86
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

irev210
irev210

When using an airave, there is no wifi connection active between the airave and your phone.   The airave uses Sprint's licensed PCS spectrum and connects to the sprint network through your home inte

WiWavelength
WiWavelength

It is witchcraft. Ooh eeh ooh ah aah ting tang walla walla bing bang...     AJ

lilotimz
lilotimz

1-866-556-7310

RAvirani Member Level: LTE Advanced

RAvirani

Posted
Posted

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?

WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

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

RAvirani Member Level: LTE Advanced

RAvirani

Posted
Posted

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

 

AJ

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?

WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

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
RAvirani Member Level: LTE Advanced

RAvirani

Posted
Posted

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.

mozamcrew Member Level: eHRPD

mozamcrew

Posted
Posted

 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
  • 3 months later...
mhammett Member Level: 4G WiMax

mhammett

Posted
Posted

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?

ingenium Member Level: 4G WiMax

ingenium

Posted
Posted

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

mhammett Member Level: 4G WiMax

mhammett

Posted
Posted

 

 

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

ingenium Member Level: 4G WiMax

ingenium

Posted
Posted

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

nowerlater Member Level: eHRPD

nowerlater

Posted
Posted

All mine are green except mobile, waiting for sprint to call back now about it. I do have the 2.5

 

Sent from my SM-G928P using Tapatalk

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
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Well you officially fried my brain. Many of these topics are well beyond my very rudimentary amateur knowledge.. this has my head spinning even more than usual. When someone figures it out, just let me know what I need to do with the app! 😂
    • PedroDaGr8
      SignalCheck Beta Crew Forum

      By PedroDaGr8 · Posted

      Confusingly, there are two different types of Cell IDs, the NR Cell ID (NCI) and the Local Cell ID, which I will call the LCID from here on out. From my understanding, @Trip is trying to get the LCID from the NCI but the same gNB is showing up for multiple sites in the app. Some background for those that don’t know about NCIs (NR Cell ID) and how they relate to gNBs and LCIDs. Just like the E/GCI which is comprised of the eNB + LCID with the eNB denoting the site, the NCI is comprised of the gNB + LCID with the gNB denoting the site. A major difference is that the eNB is a fixed number of bits in the E/GCI but the gNB can vary between 22-32 bits (out of 36) in the NCI and there is nothing transmitted which tells you what the length is. The reason for the mentioning LTE sites is that Verizon’s gNB numbering scheme in most of the USA is based upon the sites eNB (using the rules I mentioned) and a 22-bit gNB. Additionally, their LCIDs start at 25 and increment by compinations of 16 and 1. Basically, it is common to see LCID sets of 25/26/27, 41/42/43, and 57/58/59. Looking at Trip’s data and some other data from the area, they are not following the format used in the rest of the USA.  From what I can tell, they are using a 29-bit or 30-bit gNB (that gives LCIDs that follow Verizon’s standard patterning). 29-bit shares the same gNB across the two locations, while 30-bit splits the two sets: 18504107674 - gNB 144563341 + CLID 26 (29-bit) or 289126682 + CLID 26 (30-bit) 18504107690 - gNB 144563341 + CLID 42 (29-bit) or 289126682 + CLID 42 (30-bit)  18504107691 - gNB 144563341 + CLID 43 (29-bit) or 289126682 + CLID 43 (30-bit)  18504107706 - gNB 144563341 + CLID 58 (29-bit) or 289126682 + CLID 58 (30-bit)  18504107707 - gNB 144563341 + CLID 59 (29-bit) or 289126682 + CLID 59 (30-bit) 18504107738 - gNB 144563341 + CLID 90 (29-bit) or 289126683 + CLID 26 (30-bit)  18504107739 - gNB 144563341 + CLID 91 (29-bit) or 289126683 + CLID 27 (30-bit)  If true, this is a problem for SignalCheck and other mapping apps because this means they are using at least two different gNB lengths depending on the location in the USA.
    • uecker87
      SignalCheck Beta Crew Forum

      By uecker87 · Posted

      Yeah I can confirm that the status bar is updating correctly and as often as the main app!  Great to have that back after so long. Waiting on the app to pick up the 5G data.  I'm on AT&T and I find that it only reports the 5G signal data a fraction of the time.  Once I can get it to pop back up I'll send a report with the LTE RSRP showing up in the status bar instead of the NR RSRP. I am not sure if it is new behavior with the Beta because I had it set to just show the Band since I couldn't display the band and signal at the same time. Edit:  Sent a diagnostic and here's a screenshot:
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Yes, for various reasons the beta mapping project was limited to S4GRU sponsors at launch. It's still a work in progress but I have added a few users as it has evolved. I am inclined to leave it as-is for now -- it's not completely off-limits to discuss here (especially if there's an outage), but with so many posts I just try to keep discussions organized. RAvirani handles the map server and he monitors the other thread closer.   I might be confused, but are we talking apples and oranges here? My interpretation was Trip is talking about NR cells on different sites sharing cell IDs as far as the app is concerned, while the other comments are about LTE to NR cell ID calculations?
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      I hope this is true!! The Android development team did claim this bug was fixed several months ago, and it is typical for it to take several releases before changes are included. I was on the Android beta until I got my Pixel 9, now I am back on the public releases. With each monthly update, I have optimistically checked this icon and been disappointed. This would be fantastic to get back!   Could you send some diagnostic reports when you see this please? It is new behavior with QPR Beta 3?

  • Recently Browsing

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