Your not listening. I said that the DBS carriers have a vested interest (two actually) in knowing that your receivers are operating at your address of record. The required land line connection is the best method there is to do that.
No, I listened VERY carefully to what YOU asked, which was:
Do you have a bulletproof recommendation for what they should be using in lieu of a land line to verify that your receiver is connected to your residence phone? As the E* prohibition on DNS illustrates, making sure that the subscriber gets only the programming that they're entitled to is critical.
And I answered your question like this:
Why/where DO you keep getting this idea the phone line allows/disallows entitled prog? The "entitled" prog is authorized over the sat & has absolutely NOTHING to do with a phone line.
And instead of answering my question, you just keep regurgitating "the landline is the best way to do it..."
And since your (still) not listening - please tell me exactly HOW (in technical terms) having a landline tells the carrier "my service is at a specific address" - as opposed to my friend's, neighbor's, parent's house, etc.? How DO they know WHERE my phone# is - they sure cannot ask the phone co! As I am going to repeat for the last time, a landline does NO such thing - PERIOD! Just because you keep saying it does, or your D* or E* trainer tells you it does, doesn't mean it's true. (you sound like a new DBS CSR that's reading out of their new training manual - don't believe everything that they tell you
)
I've also already told you if you would do a search on this board, (being that you are a relative newbie here) you'll see MANY examples of folks such as me that have moved & continue to use our very SAME landline# with NO issues. There's a good reason why it works & I've just explained it to you. (again) You might actually learn something doing a search...
Reason 1: The DBS companies are not allowed to deliver out-of-market locals without waivers (this one carries some hefty penalties).
And please find ONE single requirement in either providers DNS requirements that you MUST have a landline for DNS service & post them here - even if you're a one receiver DNS customer. I've been doing satellite since the big dishes & have NEVER seen such a requirement. What does DNS have anything to do with landlines anyway???
(& yea, I know all about DNS - since I AM a dealer...)
Reason 2: They want to know that you're not using your receiver(s) outside your residence (this one represents substantial lost revenues).
How (prey tell) does having ALL my receivers at a place different from where the physical location is
supposed to be making the carrier loose revenue? I would be paying EXACTLY the same amount whether I was in Chicago, St.Louis or Springfield - please make some sense here. Again, if you are talking about account stacking, then yes it will stop that, but otherwise it ain't gonna help stop movers - not to mention the fact movers are NOT loosing revenue for either E* or D*, but actually in most cases MAKE money for them, since most movers "move" to be able to get local nets AT ALL, since there are still many markets that do not have locals at all. (Hmm, is it sinking in why both providers "look the other way" when people move...
)
E* has a feature on their ViP622 called DishComm that enables communications between receivers, but one of them must still be connected to a land line. Knowing that all of the receivers are together is half the battle, but knowing where they are is no less important.
And (again) for the last time - a phone connection is NOT going to solve the "location" problem even with DishComm - only that ALL receivers on an account are in the same loc.
I'm done with this, as you just don't want to accept reality - you can stay in fantasy land & the rest of us will get back to the OP's subject at hand, which BTW...