Jump to content

Recommended Posts

Posted
Just leave it overnight. It does multiple resets and firmware upgrades when you first set it up. It takes about a day to start functioning reliably.

Sent from my Pixel 2 XL using Tapatalk

The problem is that it's already been a day, and still no sign of improvement. I'll give it more time and see I guess.

Sent from my SM-G950U using Tapatalk

Posted
The problem is that it's already been a day, and still no sign of improvement. I'll give it more time and see I guess.

Sent from my SM-G950U using Tapatalk

As long as it's still cycling on it's own, it's almost certainly still doing updates.

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Posted

So I was having issues with my Pixel refusing to grab the CDMA side of the Airave 3 at my house when there was even the slightest 1x800 macro signal to connect to.. suddenly those issues are gone. As long as I'm connected to the LTE side of the Airave, when I make a call it grabs the CDMA side instead of dropping back to the weak macro site connection. Oddly, if I force my Pixel into 3G mode, it still typically grabs the 1x800 macro site (but EV-DO is definitely coming from the Airave) and doesn't want to let go.

I'm guessing there was an Airave software update that changed this behavior recently. It's so much better now!

-Mike

Posted

Is the CDMA side of the LTE 3 supposed to have 1- or 2-way hadoffs to the macro sites?  Just like the old Airaves, for me it seems to drop calls when you come into or walk away from it.

Posted
31 minutes ago, Handyman said:

Is the CDMA side of the LTE 3 supposed to have 1- or 2-way hadoffs to the macro sites?  Just like the old Airaves, for me it seems to drop calls when you come into or walk away from it.

It has one way handoff from the Airave to the Macro network but not the other way around. Actually for me when I come in to Airave coverage from macro coverage it drops the call. 

Posted
As long as it's still cycling on it's own, it's almost certainly still doing updates.

Sent from my Pixel 2 XL using Tapatalk

Still no improvement for my airave. It keeps cycling on both sides. At most I get around 10 minutes where everything is green and fine, then it cycles. After a long while, the net and lte lights will go solid red on the data side, and the wan on the CDMA side will go solid red. Then after some more time, it will cycle again, rinse, and repeat. I'm at a loss as to how to get this thing working. Putting it in front of my router is not an option, due to the placement of my router. I do have a sprint airave tech calling tomorrow, but I'm not hopeful that this thing will work.

Sent from my SM-G950U using Tapatalk

Posted
3 hours ago, travisc said:

Still no improvement for my airave. It keeps cycling on both sides. At most I get around 10 minutes where everything is green and fine, then it cycles. After a long while, the net and lte lights will go solid red on the data side, and the wan on the CDMA side will go solid red. Then after some more time, it will cycle again, rinse, and repeat. I'm at a loss as to how to get this thing working. Putting it in front of my router is not an option, due to the placement of my router. I do have a sprint airave tech calling tomorrow, but I'm not hopeful that this thing will work.

Sent from my SM-G950U using Tapatalk
 

Can you tell me a little about your network? I have a feeling something is dropping the VPN tunnel to Sprint. 

Posted
Still no improvement for my airave. It keeps cycling on both sides. At most I get around 10 minutes where everything is green and fine, then it cycles. After a long while, the net and lte lights will go solid red on the data side, and the wan on the CDMA side will go solid red. Then after some more time, it will cycle again, rinse, and repeat. I'm at a loss as to how to get this thing working. Putting it in front of my router is not an option, due to the placement of my router. I do have a sprint airave tech calling tomorrow, but I'm not hopeful that this thing will work.

Sent from my SM-G950U using Tapatalk

Have you set it up with the GPS antenna properly placed?

Sent from my Pixel using Tapatalk

Posted
Can you tell me a little about your network? I have a feeling something is dropping the VPN tunnel to Sprint. 
It's a typical home network. Motorola modem that feeds comcast internet to an asus router. Airave is airave is hardwired to the router. I opened up the ports on the router mentioned in the startup guide.

Sent from my SM-G950U using Tapatalk

Posted
Have you set it up with the GPS antenna properly placed?

Sent from my Pixel using Tapatalk

GPS lock seems to be fine. I have the antenna on the window sill laying flat.

Sent from my SM-G950U using Tapatalk

Posted
10 minutes ago, travisc said:

GPS lock seems to be fine. I have the antenna on the window sill laying flat.

Sent from my SM-G950U using Tapatalk
 

Ask for an exchange then. 

Posted
Ask for an exchange then. 
I do have an airave tech calling me tomorrow morning to try and figure out what's going on. When I get off work tonight, i'm going to unplug my router and hook the airave directly behind the modem and see if it connects and stays connected, to rule out hardware failure. Most likely will be asking for an exchange if all else fails.

Sent from my SM-G950U using Tapatalk

Posted

Quick question, does anybody use comcast as their ISP? Could they be blocking ports that need to be open?

Sent from my SM-G950U using Tapatalk

Posted
On 12/11/2017 at 2:11 PM, rocketr said:

It has one way handoff from the Airave to the Macro network but not the other way around. Actually for me when I come in to Airave coverage from macro coverage it drops the call. 

How about LTE? Does that side handoff (thinking Calling Plus here...)

Posted
Quick question, does anybody use comcast as their ISP? Could they be blocking ports that need to be open?

Sent from my SM-G950U using Tapatalk


Comcast shouldn't be blocking it. From the way you described it, it sounds like possibly the UDP NAT connection timeout could be too low on your router, resulting in the VPN tunnel being dropped. That, or it's a defective device. Timeout settings are an advanced setting in routers, and I don't think most make it accessible. The defaults for most routers should be fine though, unless you're doing lots of torrents or P2P that utilizes lots of connections (which would cause the lookup table to get full and drop the VPN connection)
How about LTE? Does that side handoff (thinking Calling Plus here...)
It should, LTE should be seamless handoffs.

Sent from my Pixel 2 XL using Tapatalk

Posted

There are lots of NAT bugs with your router. I'd try searching for a NAT timeout option or disable NAT acceleration. 

Posted

Update: It's a miracle! I don't know what I did, but it's been up with no disconnects now for over a day. I tried it without the router directly hooked into the modem overnight a couple nights ago to no avail. Then tried with a different router I had lying around, to no avail. Fed up, I hooked up my main router again, reset both sides of the airave, again, and left it. Now it finally is fully connected and hasn't dropped, that I can tell. I've never had so much difficulty in getting a piece of hardware running. Crossing fingers it stays this way. Now comes the task of placing it where I need to after I run new ethernet, and hoping I don't have the same problems again.

Sent from my SM-G950U using Tapatalk

  • Like 2
Posted



Update: It's a miracle! I don't know what I did, but it's been up with no disconnects now for over a day. I tried it without the router directly hooked into the modem overnight a couple nights ago to no avail. Then tried with a different router I had lying around, to no avail. Fed up, I hooked up my main router again, reset both sides of the airave, again, and left it. Now it finally is fully connected and hasn't dropped, that I can tell. I've never had so much difficulty in getting a piece of hardware running. Crossing fingers it stays this way. Now comes the task of placing it where I need to after I run new ethernet, and hoping I don't have the same problems again.

Sent from my SM-G950U using Tapatalk




Edit: I got my hopes up too soon. I came home tonight to find the airave back to cycling its self again. I think i'm going to try for an exchange and see if that makes a difference.

I disabled nat acceleration and put it in the DMZ. I'll leave it overnight and see if that works.

Sent from my SM-G950U using Tapatalk

Posted
1 minute ago, travisc said:


 

 


Edit: I got my hopes up too soon. I came home tonight to find the airave back to cycling its self again. I think i'm going to try for an exchange and see if that makes a difference.

I disabled nat acceleration and put it in the DMZ. I'll leave it overnight and see if that works.

Sent from my SM-G950U using Tapatalk
 

 

I doubt it is the router.  We have very sophisticated firewall at our office and Airave worked fine behind it.  This was last week we installed our Airave. 

Posted
11 minutes ago, JG001 said:


Hi. How Can I get ahold  of an Airave 3 LTE for   prepaid accounts. The Airave 3 LTE is really needed at my location. Thank you.

It is not available. You would need to go to postpaid to get one. 

Posted

Thank you. I heard that Sprint offers the S1000 LTE femtocell  that does not go onto a account. I have been told by a Magic Box project lead that the CommScope S1000 LTE femtocell does not have to be attached to an account of any kind   

Posted
On 12/5/2017 at 5:18 PM, ingenium said:

It SHOULD work as long as both NATs handle UDP connections correctly. The Airave sets up 2 outgoing IPSec VPN tunnels using the standard ports, one for CDMA and one for LTE. UDP NAT timeouts tend to be lower than TCP, but as long as the airave sends or receives a packet every minute or so it should be fine. I think UDP NAT entries tend to be cleared after 1-5 minutes of no activity. I imagine this is already done to prevent NAT from clearing the connection thinking it's finished.

A second NAT shouldn't be any more problematic than single NAT in this regard, so you should be fine.

I was able to get Sprint to send the Airave 3 to my mom's house and hooked it up a week ago. Setup was pretty straightforward once I found a place out of the way where all the cords would reach and I could get a GPS lock with the included puck. (My only peeve: the power cord could stand to be a bit longer.)

So far even though she has a pretty cruddy broadband connection (10/1), which I'm sure would disappoint anyone who gets close enough to her house to connect to the band 41 signal, it seems to be working fine for data, voice, and SMS indoors, even on the LAN side of the router (even though she appears to be triple NATed!).

Posted

When VoLTE is 100% implemented on Sprint some day, will LTE call handoffs to and from the macro network work with the Airave? 

From what I understand, handoffs do not work in all scenarios over 1x CDMA on the Airave currently. 

Posted
When VoLTE is 100% implemented on Sprint some day, will LTE call handoffs to and from the macro network work with the Airave? 
From what I understand, handoffs do not work in all scenarios over 1x CDMA on the Airave currently. 
1x hands off from an Airave to the macro network, but not the other way around. VoLTE will handoff in both directions. Calling+ does this now.

Sent from my Pixel 2 XL 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.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • 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! 😂
    • 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.
    • 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:
    • 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?
    • 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...