[CRTech] Christian Radio Tech [MSG 82799]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: SBE Regulatory Alert - Apr 23, 2018
To: CRTech <crtech@crtech.org>
Subject: Re: SBE Regulatory Alert - Apr 23, 2018
From: Michael Barnes <barnmichael@gmail.com>
Date: Fri, 27 Apr 2018 12:39:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=DtB5hYoRCZyn9m9jVWQBEeoimJlFfk7He1OVwCuj+CI=; b=H9Dka5iUmbrRsjY9y7Q3CFkk/C41smZwQ1surNLKgVnq0PuTv72wS53UZrkgEONPpe aW4TSg0wT9XG2oth54XvBI90wlt57POhRS6YanFSk7zsQduistMF6uC1FMsQtu7d2ZiO jgWcrfs6ZEs2G6HfdosCkhtYyWepoCzAYmgJoZSspNXLjI2ZX2QnQeX6xZ4Kc+KqhdbK 47PMjSAfmoz8wgMi0tPbDh0L+8Gjc19leWLUARr4LD4M2Klilv32XxdUgDDMbeQbS7Uq kTANVn7QpoFc4v6Rjt0L/EJ+tmE4clUxk7qKpW0fsGB9gK0fjsdkm160USvlfP0qwUeT xcew==
In-reply-to: <CAKr2A_sZefNrfpS7xDnWmgftrjgceWY7WA4QCjLgqtic2P1spQ@mail.gmail.com>
References: <CAAthHBZBXWTdLRxSXhgciKCOeariGQkiSN0xgHZFbMMgCUDEoQ@mail.gmail.com> <e058b127-4f6d-941c-9de0-c4a6d04efdff@knlr.com> <332291e1-422a-08a0-9861-d6fffe8a9116@reyware.us> <835ec0ff-912d-a1e7-99a8-9b3306941381@bosscher.org> <DM5PR20MB19778FBA65414B3A6691B8E8A48F0@DM5PR20MB1977.namprd20.prod.outlook.com> <4FF72227-3B28-434E-97FD-CD36031F917A@icloud.com> <BY1PR0801MB096743A01A483E9D47F247A3EF8F0@BY1PR0801MB0967.namprd08.prod.outlook.com> <6B1C3C77-7125-4920-BF82-641C473EC578@ieee.org> <CACci8U7jDGEahmhDSFZjc42hLweFG5u50qcpG67CC2EgK_2jdw@mail.gmail.com> <423C2102-AE5A-43E5-9CFE-F800EDC46DEB@ieee.org> <F67F4BF0-FA5E-4A72-99EE-FCB782292E6F@icloud.com> <003f01d3de54$e380bb00$aa823100$@pilgrimradio.com> <CAKr2A_sZefNrfpS7xDnWmgftrjgceWY7WA4QCjLgqtic2P1spQ@mail.gmail.com>
James Richardson,

Actually, there is a lot of programming that does not require any authorization. The uplink provider would have little or no knowledge of all the receivers. In the cases that do require authorization, the only thing the program provider would typically know is the name of the user and the serial number of the receiver. They would have no information on the facility, such as actual dish location, dish technical parameters, etc. Further, the uplink provider is only the licensee of the uplink, not the program provider who is simply passing through his facility.

For example, in the case of the Salem Radio Network, there are something like 13 satellite channels, most of which require no authorization. SRN sends the programming from facilities in Dallas, Texas and Nashville, Tennessee through the MicroSpace uplink facilities in Garner, North Carolina. MicroSpace is the licensee of the uplink, but has zero knowledge of any downlink facilities. The SRN folks keep track of the users of the subscription channels and manage the control channel that authorizes users to receive the paid programming. The only information they have is the user's identification and the serial number of the receiver. The user's address may be very different from the dish location. SRN provides recommended specifications on the user's dish, but otherwise has no knowledge of what the user actually has.

Hope that clears things up for you.

Michael


On Fri, Apr 27, 2018 at 12:18 PM, James Richardson <jreelectronics@gmail.com> wrote:
4.27.2018

So count me in on the confused side.  If the satellite uplink is licensed by the FCC, the uplink facility should have the information
of who is receiving the signal.  I can receive the satellite all day long rf wise, but cannot utilize what is on the signal until the 
satellite master control authorizes my receiver.  

Seems to me that the uplink people should be responsible and not the down link recipients.  My FM yagi in the back yard is not
licensed?

What am I missing?

J.R.Richardson
contract engineer
Westminster, MD

Follow-Ups: Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson <jreelectronics@gmail.com>, 27 Apr 2018 19:52:25 -0000)
References: SBE Regulatory Alert - Apr 23, 2018
(Michael Barnes <barnmichael@gmail.com>, 24 Apr 2018 22:40:48 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Terry Cowan <tcowan@knlr.com>, 24 Apr 2018 23:18:55 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(dave allen <crtech-mail@reyware.us>, 24 Apr 2018 23:32:50 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Tom Bosscher <tom@bosscher.org>, 25 Apr 2018 00:15:38 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Gregg Richwine <gmsnrich@live.com>, 25 Apr 2018 03:23:29 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Mark Johnson <linkupsat@icloud.com>, 25 Apr 2018 04:24:39 -0000)
RE: SBE Regulatory Alert - Apr 23, 2018
(Scott Foster <Scott.Foster@SalemMedia.com>, 25 Apr 2018 15:10:32 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Sherrod Munday <smunday@ieee.org>, 25 Apr 2018 18:00:38 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Dave Land <dave@klvv.com>, 25 Apr 2018 18:13:43 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Sherrod Munday <smunday@ieee.org>, 25 Apr 2018 18:34:36 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(Mark Johnson <linkupsat@icloud.com>, 25 Apr 2018 20:53:34 -0000)
RE: SBE Regulatory Alert - Apr 23, 2018
("Bill Hurne" <billhurne@pilgrimradio.com>, 27 Apr 2018 18:24:17 -0000)
Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson <jreelectronics@gmail.com>, 27 Apr 2018 19:18:28 -0000)
Prev by date: Remotes
(Bob Morris, 27 Apr 2018 19:32:03 -0000)
Next by date: Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson, 27 Apr 2018 19:52:25 -0000)
Prev by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson, 27 Apr 2018 19:18:28 -0000)
Next by thread: Re: SBE Regulatory Alert - Apr 23, 2018
(James Richardson, 27 Apr 2018 19:52:25 -0000)
CRTech.org