Actually, they pertain specifically to my point: There are significantly more steps, greater challenges, potential for problems, and overall greater expense and resource allocation required for femtocells than WiFi calling.
You're shooting from the hip.
If you look at Verizon's FAQ, they make a point of mentioning more than once that the extender will only work "in many places within the Verizon Wireless coverage area." If you happen to be in parts of the US where Verizon does not have native coverage (and there actually are quite a few such spots), then the extender will refuse to work. If you try to trick it by making sure the GPS doesn't work, or if there's any other reason a position fix can'tt be obtained, the extender won't work either.
So, not so much 1, 2, 3.
Of course there is no guarantee, they need to cover themselves, however, using the same extender on the west and east coast it works as advertised, one, two, three. You actually have to find a spot where the network extender doesn't work and then tell me it doesn't work there rather than a generic cya from a faq. I can see VZW implementing the same rules "if" they had wifi calling available.
And of course, the kicker is if there is no wifi available, you are still stuck.
That's a little unfortunate, considering that you are saying that someone can't possibly disagree with you and be right unless you are convinced that they know what they're talking about... and when they do actually start talking about it, you decide you "could give a hoot."
That is what I am saying, you made a specific claim on this forum and are unable to show anything other than a wild guess as to the veracity of your claim. Also you seem to flip-flopping: are you referring to user setup or IT setup? It's clear from your posts you can't possibly know or what difficulty or ease a Telco company has when it sets up a new calling path. And when you are challenged all sorts of irrelevant things wind up in posts.
I believe you said it best when you said: making such statements requires that you know what you're talking about. You just made it clear you do not, and don't want to.
Same.
I think you yourself have readily admitted here, that you don't have the desire to know anything about it, which would mean that by default I probably know maybe a little more about it than you even want to know. And that's perfectly fine. A user shouldn't have to know what's going on. They should be able to just flick a setting on their screen. And that alone will cause the phone and the carrier to do all that fancy highfalutin' "one, two three" stuff that you shouldn't care about, in order to just make it happen.
I don't think guessing at the engineering aspects of the back-end computer systems qualifies anybody to say they understand a process.
Fortunately, Apple is doing exactly this with WiFi calling in iOS 8. No silly extra boxes to hook up or plug in. No having to be told that your assumptions about where that silly box will work might be a little off the mark. Not even a "one, two three." More like a "one"... and it just works.
And I happen to think that's a really good thing, that all carriers should be actively supporting, regardless of how good their networks are, or how good we think their networks are. Doing so will be easier on the carriers, and easier on the customers, too.
Well somewhere someone (in this case Apple and Tmobile) spent time engineering the complexity so you don't see it when:
1- get wifi
2-flip the switch
3- make call.
Wifi calling is a good thing, but a network extender is a different solution to the same problem with it's own set of pro's and cons. The signal penetration for one is better than both the 2.4 and 5 ghz bands, so within the radius of the device, which is greater than my router, it works flawlessly. Obviously a con is that it is it's own hardware, while another pro it's not clearly not subject to mitm attacks like wifi in 2014.
But a lot of what you posted is just nonsense, especially three year old articles about network extenders being hacked, which has been addressed not even recently. That has nothing to do with anything.
Last edited: