FCC Web Documents citing 64.3001

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

• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.pdf
  • (E911 First Report and Order)); In the Matter of Wireless E911 Location Accuracy Requirements, PS Docket No. 07-114, Second Report and Order, __ FCC Rcd ____ ¶ 33 (2010)(Location Accuracy Second Report and Order). The basic 911 rules require covered carriers to deliver all 911 calls to the appropriate PSAP or a designated answering point. See 47 C.F.R. §§ 20.18(b), 64.3001. Basic 911 requirements, however, do not address what information the PSAP should receive from that call; rather they are designed to ensure the appropriate delivery of 911 calls. See E911 First Report and Order, 11 FCC Rcd at 18679, 18692-99 ¶¶ 4, 29-46. The Commission therefore adopted Enhanced 911 rules requiring covered wireless carriers to be capable of delivering the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-2069A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-2069A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-2069A1.txt
  • with E911 service as described in this section; (2) Interconnected VoIP service providers must transmit all 911 calls, as well as ANI and the caller's Registered Location for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers pursuant to Sec. 64.3001 of this chapter, provided that ``all 911 calls'' is defined as ``any voice communication initiated by an interconnected VoIP user dialing 911;'' (3) All 911 calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network; and (4) The Registered Location must be available to the appropriate PSAP, designated statewide default answering
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-218375A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-218375A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-218375A1.txt
  • concerning the provision of translation software WILL BECOME EFFECTIVE UPON approval by the Office of Management and Budget. In Appendix B, the amendments to Part 64 are corrected in the Table of Contents and in the text of the regulations by redesignating Subpart Z as Subpart AA and by redesignating sections 64.2501, 64.2502, 64.2503, 64.2504, and 64.2505 as sections 64.3000, 64.3001, 64.3002, 64.3003, and 64.3004, respectively. Appendix B is further amended in newly designated section 64.3000, ``Definitions,'' by designating the definition for ``Statewide default answering point'' as paragraph (d). Appendix B is further amended in newly designated section 64.3002(a), (b) and (d), entitled ``Transition to 911 as the universal emergency telephone number,'' by replacing the word ``August'' with the word ``September''
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-243546A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-243546A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-243546A1.txt
  • is amended to read as follows: (b) Basic 911 Service. CMRS providers subject to this section must transmit all wireless 911 calls without respect to their call validation process to a Public Safety Answering Point, or, where no Public Safety Answering Point has been designated, to a designated statewide default answering point or appropriate local emergency authority pursuant to § 64.3001 of this chapter, provided that "all wireless 911 calls" is defined as "any call initiated by a wireless user dialing 911 on a phone using a compliant radio frequency protocol of the serving carrier." 3. Section 20.18(c) is amended to read as follows: (c) TTY Access to 911 Services. CMRS providers subject to this section must be capable of transmitting
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-351A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-351A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-351A1.txt
  • 302, 303, and 337 unless otherwise noted. Interpret or apply sections 201, 218, 225, 226, 227, 229, 332, 48 Stat. 1070, as amended. 47 U.S.C. 201-204, 208, 225, 226, 227, 229, 332, 501 and 503 unless otherwise noted. 5. Add subpart AA to part 64 to read as follows: Subpart AA - Universal Emergency Telephone Number Sec. 64.3000. Definitions. Sec. 64.3001. Obligation to transmit 911 calls. Sec. 64.3002. Transition to 911 as the universal emergency telephone number. Sec. 64.3003 Obligation for providing a permissive dialing period. Sec. 64.3004 Obligation for providing an intercept message. AUTHORITY: 47 U.S.C. 151, 154(i), 154(j), 157, 160, 210, 202, 208, 214, 251(e), 301, 303, 308, 309(j), and 310. * * * * * § 64.3000 Definitions.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-326A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-326A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-326A1.txt
  • Order, at para. 18, n.56. , visited Sept. 13, 2002. E.g., the Ford Vehicle Communications Systems (VCS) requires a service contract with Sprint PCS. Daimler-Chrysler is developing a telematics offering that is based on WLAN technology that does not require reliance on the public switched telephone network (PSTN). . ; http://www.lincolnvehicles.com/vehicles/interior/asp?sVehi=LS. >. See 47 C.F.R. § 20.18(b); 47 C.F.R. §§ 64.3001, 64.3002. 47 C.F.R. § 20.18(k) (stating that ``a service provider covered by [Section 20.18] who offers dispatch service to customers may meet the requirements of this section by either complying with the requirements set forth in paragraphs (b) through (e) of this section or by routing the customer's emergency calls through a dispatcher. If the service provider chooses the latter
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1.txt
  • and technical information needed for MLTS support of E9-1-1.'' While we fully support the goal of the proposal, we are concerned that the proposed Part 64 amendments may be too vague, making them operationally unenforceable. Further, we note that the record is unclear as to the extent to which LECs offer E911 compatible trunking. Finally, we note that the section 64.3001 of the Commission's rules requires all telecommunications carriers to transmit all 911 calls to appropriate public safety authorities. Thus, we believe that where a state requires MLTS E911 implementation, our rules would require telecommunications carriers to transmit the location information provided by the MLTS operator. Although we decline to adopt the Part 64 revision here, we seek comment on NENA's
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1_Erratum.doc
  • and technical information needed for MLTS support of E9-1-1.'' While we fully support the goal of the proposal, we are concerned that the proposed Part 64 amendments may be too vague, making them operationally unenforceable. Further, we note that the record is unclear as to the extent to which LECs offer E911 compatible trunking. Finally, we note that the section 64.3001 of the Commission's rules requires all telecommunications carriers to transmit all 911 calls to appropriate public safety authorities. Thus, we believe that where a state requires MLTS E911 implementation, our rules would require telecommunications carriers to transmit the location information provided by the MLTS operator. Although we decline to adopt the Part 64 revision here, we seek comment on NENA's
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-116A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-116A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-116A1.txt
  • with E911 service as described in this section; (2) Interconnected VoIP service providers must transmit all 911 calls, as well as ANI and the caller's Registered Location for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers pursuant to section 64.3001 of this chapter, provided that ``all 911 calls'' is defined as ``any voice communication initiated by an interconnected VoIP user dialing 911''; (3) All 911 calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network; and (4) The Registered Location must be available to the appropriate PSAP, designated statewide default answering
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-151A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-151A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-151A1.txt
  • transmit all 911 and E911 calls, as well as a call back number, the name of the relay provider, the CA's identification number, and the caller's Registered Location for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers under section 64.3001 of the Commission's rules. These calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network, and the Registered Location must be available from or through the ALI Database. Internet-based TRS providers may satisfy this requirement by interconnecting indirectly through a third party such as a competitive LEC, interconnecting directly with the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-78A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-78A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-78A1.txt
  • handling requirements as applied to Internet-based TRS providers, to the VoIP rules and the obligations placed on telecommunications carriers generally, however, we require Internet-based TRS providers to make the outbound emergency call to ``an appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority.'' See VoIP 911 Order, 20 FCC Rcd at 10269-70, para. 42; 47 C.F.R. § 64.3001. We note that in the VRS/IP Relay 911 NPRM the Commission sought comment generally on ways in which the requirements of the VoIP 911 Order may be applied to VRS and IP relay to ensure access to emergency services. VRS/IP Relay 911 NPRM, 20 FCC Rcd at 19487, para. 24. We amend our rules to reflect this change. See Appendix
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.txt
  • (E911 First Report and Order)); In the Matter of Wireless E911 Location Accuracy Requirements, PS Docket No. 07-114, Second Report and Order, __ FCC Rcd ____ ¶ 33 (2010)(Location Accuracy Second Report and Order). The basic 911 rules require covered carriers to deliver all 911 calls to the appropriate PSAP or a designated answering point. See 47 C.F.R. §§ 20.18(b), 64.3001. Basic 911 requirements, however, do not address what information the PSAP should receive from that call; rather they are designed to ensure the appropriate delivery of 911 calls. See E911 First Report and Order, 11 FCC Rcd at 18679, 18692-99 ¶¶ 4, 29-46. The Commission therefore adopted Enhanced 911 rules requiring covered wireless carriers to be capable of delivering the
• http://wireless.fcc.gov/releases/fcc01-351.pdf http://wireless.fcc.gov/releases/fcc01-351.txt
  • 302, 303, and 337 unless otherwise noted. Interpret or apply sections 201, 218, 225, 226, 227, 229, 332, 48 Stat. 1070, as amended. 47 U.S.C. 201-204, 208, 225, 226, 227, 229, 332, 501 and 503 unless otherwise noted. 5. Add subpart AA to part 64 to read as follows: Subpart AA ­ Universal Emergency Telephone Number Sec. 64.3000. Definitions. Sec. 64.3001. Obligation to transmit 911 calls. Sec. 64.3002. Transition to 911 as the universal emergency telephone number. Sec. 64.3003 Obligation for providing a permissive dialing period. Sec. 64.3004 Obligation for providing an intercept message. AUTHORITY: 47 U.S.C. 151, 154(i), 154(j), 157, 160, 210, 202, 208, 214, 251(e), 301, 303, 308, 309(j), and 310. * * * * * § 64.3000 Definitions.
• http://www.fcc.gov/cgb/voip911order.pdf
  • Commanding Officer, Communications Division/NYC E-911, New York City Police Department, to Marlene H. Dortch, Secretary, FCC, WC Docket No. 04-36 (filed Apr. 22, 2005) (New York City Apr. 22, 2005 Ex Parte Letter). 18 The basic 911 rules require covered carriers to deliver all 911 calls to the appropriate PSAP or a designated answering point. See 47 C.F.R. §§ 20.18(b), 64.3001. Basic 911 requirements, however, do not address what information the PSAP should receive from that call; rather they are designed to ensure the appropriate delivery of 911 calls. See Notice, 19 FCC Rcd at 4898, para. 52; E911 First Report and Order, 11 FCC Rcd at 18679, 20862- 69, paras. 4, 29-46. The Commission therefore adopted enhanced 911 rules requiring
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.pdf
  • (E911 First Report and Order)); In the Matter of Wireless E911 Location Accuracy Requirements, PS Docket No. 07-114, Second Report and Order, __ FCC Rcd ____ ¶ 33 (2010)(Location Accuracy Second Report and Order). The basic 911 rules require covered carriers to deliver all 911 calls to the appropriate PSAP or a designated answering point. See 47 C.F.R. §§ 20.18(b), 64.3001. Basic 911 requirements, however, do not address what information the PSAP should receive from that call; rather they are designed to ensure the appropriate delivery of 911 calls. See E911 First Report and Order, 11 FCC Rcd at 18679, 18692-99 ¶¶ 4, 29-46. The Commission therefore adopted Enhanced 911 rules requiring covered wireless carriers to be capable of delivering the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-2069A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-2069A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-2069A1.txt
  • with E911 service as described in this section; (2) Interconnected VoIP service providers must transmit all 911 calls, as well as ANI and the caller's Registered Location for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers pursuant to Sec. 64.3001 of this chapter, provided that ``all 911 calls'' is defined as ``any voice communication initiated by an interconnected VoIP user dialing 911;'' (3) All 911 calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network; and (4) The Registered Location must be available to the appropriate PSAP, designated statewide default answering
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-218375A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-218375A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-218375A1.txt
  • concerning the provision of translation software WILL BECOME EFFECTIVE UPON approval by the Office of Management and Budget. In Appendix B, the amendments to Part 64 are corrected in the Table of Contents and in the text of the regulations by redesignating Subpart Z as Subpart AA and by redesignating sections 64.2501, 64.2502, 64.2503, 64.2504, and 64.2505 as sections 64.3000, 64.3001, 64.3002, 64.3003, and 64.3004, respectively. Appendix B is further amended in newly designated section 64.3000, ``Definitions,'' by designating the definition for ``Statewide default answering point'' as paragraph (d). Appendix B is further amended in newly designated section 64.3002(a), (b) and (d), entitled ``Transition to 911 as the universal emergency telephone number,'' by replacing the word ``August'' with the word ``September''
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-243546A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-243546A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-243546A1.txt
  • is amended to read as follows: (b) Basic 911 Service. CMRS providers subject to this section must transmit all wireless 911 calls without respect to their call validation process to a Public Safety Answering Point, or, where no Public Safety Answering Point has been designated, to a designated statewide default answering point or appropriate local emergency authority pursuant to § 64.3001 of this chapter, provided that "all wireless 911 calls" is defined as "any call initiated by a wireless user dialing 911 on a phone using a compliant radio frequency protocol of the serving carrier." 3. Section 20.18(c) is amended to read as follows: (c) TTY Access to 911 Services. CMRS providers subject to this section must be capable of transmitting
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-351A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-351A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-351A1.txt
  • 302, 303, and 337 unless otherwise noted. Interpret or apply sections 201, 218, 225, 226, 227, 229, 332, 48 Stat. 1070, as amended. 47 U.S.C. 201-204, 208, 225, 226, 227, 229, 332, 501 and 503 unless otherwise noted. 5. Add subpart AA to part 64 to read as follows: Subpart AA - Universal Emergency Telephone Number Sec. 64.3000. Definitions. Sec. 64.3001. Obligation to transmit 911 calls. Sec. 64.3002. Transition to 911 as the universal emergency telephone number. Sec. 64.3003 Obligation for providing a permissive dialing period. Sec. 64.3004 Obligation for providing an intercept message. AUTHORITY: 47 U.S.C. 151, 154(i), 154(j), 157, 160, 210, 202, 208, 214, 251(e), 301, 303, 308, 309(j), and 310. * * * * * § 64.3000 Definitions.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-326A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-326A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-326A1.txt
  • Order, at para. 18, n.56. , visited Sept. 13, 2002. E.g., the Ford Vehicle Communications Systems (VCS) requires a service contract with Sprint PCS. Daimler-Chrysler is developing a telematics offering that is based on WLAN technology that does not require reliance on the public switched telephone network (PSTN). . ; http://www.lincolnvehicles.com/vehicles/interior/asp?sVehi=LS. >. See 47 C.F.R. § 20.18(b); 47 C.F.R. §§ 64.3001, 64.3002. 47 C.F.R. § 20.18(k) (stating that ``a service provider covered by [Section 20.18] who offers dispatch service to customers may meet the requirements of this section by either complying with the requirements set forth in paragraphs (b) through (e) of this section or by routing the customer's emergency calls through a dispatcher. If the service provider chooses the latter
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1.txt
  • and technical information needed for MLTS support of E9-1-1.'' While we fully support the goal of the proposal, we are concerned that the proposed Part 64 amendments may be too vague, making them operationally unenforceable. Further, we note that the record is unclear as to the extent to which LECs offer E911 compatible trunking. Finally, we note that the section 64.3001 of the Commission's rules requires all telecommunications carriers to transmit all 911 calls to appropriate public safety authorities. Thus, we believe that where a state requires MLTS E911 implementation, our rules would require telecommunications carriers to transmit the location information provided by the MLTS operator. Although we decline to adopt the Part 64 revision here, we seek comment on NENA's
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-290A1_Erratum.doc
  • and technical information needed for MLTS support of E9-1-1.'' While we fully support the goal of the proposal, we are concerned that the proposed Part 64 amendments may be too vague, making them operationally unenforceable. Further, we note that the record is unclear as to the extent to which LECs offer E911 compatible trunking. Finally, we note that the section 64.3001 of the Commission's rules requires all telecommunications carriers to transmit all 911 calls to appropriate public safety authorities. Thus, we believe that where a state requires MLTS E911 implementation, our rules would require telecommunications carriers to transmit the location information provided by the MLTS operator. Although we decline to adopt the Part 64 revision here, we seek comment on NENA's
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-116A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-116A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-116A1.txt
  • with E911 service as described in this section; (2) Interconnected VoIP service providers must transmit all 911 calls, as well as ANI and the caller's Registered Location for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers pursuant to section 64.3001 of this chapter, provided that ``all 911 calls'' is defined as ``any voice communication initiated by an interconnected VoIP user dialing 911''; (3) All 911 calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network; and (4) The Registered Location must be available to the appropriate PSAP, designated statewide default answering
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-151A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-151A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-151A1.txt
  • transmit all 911 and E911 calls, as well as a call back number, the name of the relay provider, the CA's identification number, and the caller's Registered Location for each call, to the PSAP, designated statewide default answering point, or appropriate local emergency authority that serves the caller's Registered Location and that has been designated for telecommunications carriers under section 64.3001 of the Commission's rules. These calls must be routed through the use of ANI and, if necessary, pseudo-ANI, via the dedicated Wireline E911 Network, and the Registered Location must be available from or through the ALI Database. Internet-based TRS providers may satisfy this requirement by interconnecting indirectly through a third party such as a competitive LEC, interconnecting directly with the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-78A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-78A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-08-78A1.txt
  • handling requirements as applied to Internet-based TRS providers, to the VoIP rules and the obligations placed on telecommunications carriers generally, however, we require Internet-based TRS providers to make the outbound emergency call to ``an appropriate PSAP, designated statewide default answering point, or appropriate local emergency authority.'' See VoIP 911 Order, 20 FCC Rcd at 10269-70, para. 42; 47 C.F.R. § 64.3001. We note that in the VRS/IP Relay 911 NPRM the Commission sought comment generally on ways in which the requirements of the VoIP 911 Order may be applied to VRS and IP relay to ensure access to emergency services. VRS/IP Relay 911 NPRM, 20 FCC Rcd at 19487, para. 24. We amend our rules to reflect this change. See Appendix
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-200A1.txt
  • (E911 First Report and Order)); In the Matter of Wireless E911 Location Accuracy Requirements, PS Docket No. 07-114, Second Report and Order, __ FCC Rcd ____ ¶ 33 (2010)(Location Accuracy Second Report and Order). The basic 911 rules require covered carriers to deliver all 911 calls to the appropriate PSAP or a designated answering point. See 47 C.F.R. §§ 20.18(b), 64.3001. Basic 911 requirements, however, do not address what information the PSAP should receive from that call; rather they are designed to ensure the appropriate delivery of 911 calls. See E911 First Report and Order, 11 FCC Rcd at 18679, 18692-99 ¶¶ 4, 29-46. The Commission therefore adopted Enhanced 911 rules requiring covered wireless carriers to be capable of delivering the
• http://wireless.fcc.gov/releases/fcc01-351.pdf http://wireless.fcc.gov/releases/fcc01-351.txt
  • 302, 303, and 337 unless otherwise noted. Interpret or apply sections 201, 218, 225, 226, 227, 229, 332, 48 Stat. 1070, as amended. 47 U.S.C. 201-204, 208, 225, 226, 227, 229, 332, 501 and 503 unless otherwise noted. 5. Add subpart AA to part 64 to read as follows: Subpart AA ­ Universal Emergency Telephone Number Sec. 64.3000. Definitions. Sec. 64.3001. Obligation to transmit 911 calls. Sec. 64.3002. Transition to 911 as the universal emergency telephone number. Sec. 64.3003 Obligation for providing a permissive dialing period. Sec. 64.3004 Obligation for providing an intercept message. AUTHORITY: 47 U.S.C. 151, 154(i), 154(j), 157, 160, 210, 202, 208, 214, 251(e), 301, 303, 308, 309(j), and 310. * * * * * § 64.3000 Definitions.
• http://www.fcc.gov/cgb/voip911order.pdf
  • Commanding Officer, Communications Division/NYC E-911, New York City Police Department, to Marlene H. Dortch, Secretary, FCC, WC Docket No. 04-36 (filed Apr. 22, 2005) (New York City Apr. 22, 2005 Ex Parte Letter). 18 The basic 911 rules require covered carriers to deliver all 911 calls to the appropriate PSAP or a designated answering point. See 47 C.F.R. §§ 20.18(b), 64.3001. Basic 911 requirements, however, do not address what information the PSAP should receive from that call; rather they are designed to ensure the appropriate delivery of 911 calls. See Notice, 19 FCC Rcd at 4898, para. 52; E911 First Report and Order, 11 FCC Rcd at 18679, 20862- 69, paras. 4, 29-46. The Commission therefore adopted enhanced 911 rules requiring