FCC Web Documents citing 10.260

as compiled by hallikainen.com/FccRules on 2012 07 01

• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DOC-285192A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DOC-285192A1.pdf
  • Nothing in this Erratum affects the statutory requirement that, by September 8, 2008 (i.e., 30 days after the Commission released the CMAS Third Report and Order), Commercial Mobile Service (CMS) Providers must submit an election to the Commission indicating whether or not they intend to transmit emergency alerts as part of the Commercial Mobile Alert System. Finally, we revise Section 10.260 set forth in Appendix C of the CMAS Third Report and Order to read as follows: A CMS provider that elects not to transmit CMAS Alert Messages, in part or in whole, must comply with §§ 10.240 and 10.250 no later than 60 days following an announcement by the Commission that the Alert Aggregator/Gateway system is operational and capable of
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-08-184A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-08-184A1.pdf
  • is available, the CMS provider shall provide the required notification via U.S. mail. If no mailing address is available, the CMS provider shall use any reasonable method at its disposal to alert the customer to a change in the terms and conditions of service and directing the subscriber to voice-based notification or to a website providing the required notification. § 10.260 Timing of Subscriber Notification The provider notification requirements set forth in §§ 10.240 and 10.250 will become effective sixty (60) days following an announcement by the Commission that the Alert Aggregator/Gateway system is operational and capable of delivering emergency alerts to participating CMS providers. § 10.270 Subscribers' Right to Terminate Subscription If a CMS provider that has elected to provide
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-12-419A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-12-419A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-12-419A1.txt
  • their customers. Because CMAS is a voluntary program, not all CMS providers currently intend to provide CMAS service or do not intend to provide CMAS service throughout their entire service areas. The notice requirements in 47 C.F.R. §§ 10.240 and 10.250 are designed to prevent consumer confusion about CMAS availability from service providers. PSHSB takes this action pursuant to Section 10.260 of the Commission's rules, which requires that CMS providers electing not to transmit CMAS alerts, in whole or in part throughout their service areas, must comply with customer notification requirements set out in sections 10.240 and 10.250 ``no later than 60 days following an announcement by the Commission that the Alert Aggregator/Gateway system is operational and capable of delivering emergency
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-285192A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-285192A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-285192A1.txt
  • Nothing in this Erratum affects the statutory requirement that, by September 8, 2008 (i.e., 30 days after the Commission released the CMAS Third Report and Order), Commercial Mobile Service (CMS) Providers must submit an election to the Commission indicating whether or not they intend to transmit emergency alerts as part of the Commercial Mobile Alert System. Finally, we revise Section 10.260 set forth in Appendix C of the CMAS Third Report and Order to read as follows: A CMS provider that elects not to transmit CMAS Alert Messages, in part or in whole, must comply with §§ 10.240 and 10.250 no later than 60 days following an announcement by the Commission that the Alert Aggregator/Gateway system is operational and capable of
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-97A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-97A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-97A1.txt
  • 99.888 0.112 99.889 0.111 0.011 0.001 11.100 San Francisco 99.882 0.118 99.871 0.129 99.870 0.130 0.011 (0.001) 9.500 San Diego 99.936 0.064 99.928 0.072 99.930 0.070 0.008 0.002 13.208 Los Angeles 99.959 0.041 99.953 0.047 99.955 0.045 0.006 0.002 13.902 Denver 99.970 0.030 99.966 0.034 99.967 0.033 0.004 0.001 14.527 Baton Rouge 99.752 0.248 99.726 0.274 99.727 0.273 0.025 0.001 10.260 New Orleans 99.740 0.260 99.714 0.286 99.714 0.286 0.026 0.000 10.176 Shreveport 99.805 0.195 99.786 0.214 99.786 0.214 0.019 0.000 9.873 Billings 99.977 0.023 99.975 0.025 99.975 0.025 0.003 0.001 12.532 Fargo 99.893 0.107 99.882 0.118 99.882 0.118 0.011 0.000 10.173 Salt Lake City 99.988 0.012 99.986 0.014 99.987 0.013 0.002 0.001 15.683 Omaha 99.816 0.184 99.781 0.219 99.797 0.203
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-184A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-184A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-184A1.txt
  • is available, the CMS provider shall provide the required notification via U.S. mail. If no mailing address is available, the CMS provider shall use any reasonable method at its disposal to alert the customer to a change in the terms and conditions of service and directing the subscriber to voice-based notification or to a website providing the required notification. § 10.260 Timing of Subscriber Notification The provider notification requirements set forth in §§ 10.240 and 10.250 will become effective sixty (60) days following an announcement by the Commission that the Alert Aggregator/Gateway system is operational and capable of delivering emergency alerts to participating CMS providers. § 10.270 Subscribers' Right to Terminate Subscription If a CMS provider that has elected to provide