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

    • 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...