I'm sorry to hear that you are having issues. Have you tried to powercycle the Airave and your device? Thank you. *Paida
did you ever find a solution to this issue? i have the same problem. Sprint has no clue and they deny that the airave is the problem.
Thanks for the update. Glad that resetting your Airave did the trick! This may help many others here on the Sprint Community.
Social Care Team
I saw the suggestion to reset/restart the Airave (by pressing the tiny button on the device). Totally works! I recently hooked up the Airave and my 4s would not send texts (although I received them without an issue). I was annoyed as hell by that. But the fix was easy enough. Reset the device!!
Hope it works for you.
Well said. Simply responding to this to bump it back up the discussion board. I've read more posts than I care to, many simply looking for a straight answer versus the seeming 'spin' we get from Customer Service. What I struggle with is trying to understand why Sprint continues to foster this type of method for dealing with issues with the Airave? I for one, would appreciate so much more a straight answer acknowledging the issue(s) and that there isn't a solution right now. I fully understand that every customer may have their own unique problem which a blanket statement wouldn't cover. But simply take a look at this board and there are plenty of recurring and common issues. Just lay it out there and take your lumps - It's got to be better than getting crushed in boards like this on a daily basis from a company goodwill perspective.
Disclosures - Current 2.5 'user' with send/receive text issues and calls that more often than not go straight to VM. 10+years as a Sprint customer
"This problem with the Airave 2.0 is being researched, and software updates for the Airave are being tested."
The usual reply from Sprint which I have heard for over ten months.
Not only do I have to utilize a piece of equipment in order to simply receive better than a -106dbu signal in my home, I have to still pay Sprint for data, which is being supplied through my ISP, which (because of the Airave) I'm suddenly forced to shared its RF, as well as it's data connection to my ISP with every Sprint customer in my neighborhood. Despite what Sprint claims, you cannot restrict other users on the Airave, a simple dump of the TX/RX logs from the Airave supports this assertion.
Now... to add insult to injury: my girlfriend got a HTC EVO 3-D about ten months ago and we were immediately met with the dreaded text issue when she connected to the Airave.The first three of six phone calls to Sprint had me being told that no such issue exists, despite the huge amount of complaints on boards like this. After having one "customer service rep" give me the laughable solution of: "place the phone battery on top of the Airave and reset it..." claiming that my phone was the problem, NOT the Airave... Finally, I got someone to admit that there was a known problem with the Airaves. Sadly, the only solution they could offer me: "...there will be a firmware upgrade expected by early March of 2012 and we'll send you an email when it is available." March comes and goes, several more phone calls to Sprint yeilding the same, mixed results of denial, ignorance and blaming of everything BUT the device, I was yet again told a firmware upgrade for the Airave is due by late June of 2012.
Here it is, October of 2012 and it appears that in addition to not creating a RF backbone infrastructure, which actually supplies usable signal to Sprint customers, Sprint is still handing out the "firmware update" response to what amounts to a weak, Band-Aid fix to systemic RF coverage problems.
As a retired engineer from Motorola, I find it appalling that Sprint has dragged it's feet for as long as it has in implemeting a solution to the Airave issue. Not to mention the fact that the only reason why so many people need an Airave: is because Sprint (a communcations company) simply refuses to provide substancial, usable signal in their communications service areas.
I live a stones throw from Philadelphia, PA. It is not as if I am out in the boondocks, where poor signal quality is reasonably expected. I am in the middle of a major metropolitan area, yet the signal strength and quality are simply not usable.
I can assure Sprint that since they seemingly are unwilling to resolve neither their poor signal strength problems nor the problems with the "fix" they supply via the Airave, I will NOT be willing to renew my commercial contract nor will my girlfriend renew her consumer contract with Sprint, once they expire.
I know that the mere $400.00 a month loss from this is completely meaningless to Sprint; but if enough long-term customers leave Sprint due to their lack of providing tangible solutions, maybe they will perk their ears up and provide something more than the endlessly repeated, "we're working on it" routine.
It happens occasionally. Like I stated earlier, the call may come through sometimes, but it takes the caller several attempts to get through to me. Usually it goes straight to my voicemail.
I just did a VOIP test and everything came back within the requirements you posted.
The qos was at a default of 768kb on the airave settings.
In that case what do you see for download, upload, QoS, Packet loss, and Jitter when you run a VOIP test while cabled directly to the Airave's LAN2 port, while you are having trouble receiving calls? do you use Cable, or DSL service?