Beehive Telephone Co. v. Federal Communications Commission

179 F.3d 941, 336 U.S. App. D.C. 331, 16 Communications Reg. (P&F) 473, 1999 U.S. App. LEXIS 13636
CourtCourt of Appeals for the D.C. Circuit
DecidedJune 18, 1999
Docket97-1662
StatusPublished
Cited by5 cases

This text of 179 F.3d 941 (Beehive Telephone Co. v. Federal Communications Commission) is published on Counsel Stack Legal Research, covering Court of Appeals for the D.C. Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Beehive Telephone Co. v. Federal Communications Commission, 179 F.3d 941, 336 U.S. App. D.C. 331, 16 Communications Reg. (P&F) 473, 1999 U.S. App. LEXIS 13636 (D.C. Cir. 1999).

Opinion

Opinion for the Court filed by Circuit Judge GINSBURG.

GINSBURG, Circuit Judge:

The Federal Communications Commission, holding that access to the central database of routing information for toll-free telephone numbers is a common carrier telecommunications service, required the Bell Operating Companies (BOCs) to file a tariff of rates for that service. See In the Matter of Provision of Access for 800 Service (CompTel Declaratory Ruling), 8 F.C.C.R. 1423, ¶¶ 25-29 (1993). When the BOCs filed the tariff as directed, the Beehive Telephone Companies (collectively Beehive) filed a formal complaint against them, claiming that the Commission lacks authority to require that the service be tariffed. The Commission denied the complaint, and Beehive petitions for review, arguing, in addition to the question of the Commission’s authority, that the Commission violated its rules regarding ex parte contacts in complaint proceedings, and that the Commission has failed to implement a provision of the Telecommunications Act of 1996 that requires it to transfer operation of the toll-free database to an “impartial” entity, 47 U.S.C. § 251(e)(1).

We deny the petition for review. Beehive does not have standing under Article III of the Constitution to bring the first two claims; as to the third, it has not exhausted its administrative remedies.

I. Background

Toll-free telephone service (commonly called 800 service) involves a subscriber agreeing to pay an interexchange carrier (IXC) for all calls made to it using a predesignated 800 number. Toll-free service thus enables a business to provide its customers, potential customers, employees, and others with a free and convenient means of contacting it.

Since 1993 a nationwide computer-based Service Management System has been used to route each 800 call to the appropriate IXC, which then forwards the call to the subscriber. The SMS also makes 800 numbers portable; that is, a subscriber may change carriers without having to change its 800 number. Otherwise, once a business had created substantial goodwill *943 in a toll-free number through its advertising and use, or had obtained a number with substantial marketing value because of its mnemonic appeal (such as 1-800-FLOWERS), the cost of switching to another IXC would be the loss of that number, which would inhibit competition among IXCs.

The SMS database contains information associated with each 800 number, including the identity of the carrier selected by the subscriber. See 47 C.F.R. § 52.101(d). That information is downloaded to 12 regional databases, called Service Control Points. When a caller places an 800 call, a switch belonging to the caller’s local exchange carrier (LEC) queries the regional SCP for routing information. The SCP then instructs the switch to route the call to the subscriber’s chosen IXC, which delivers the call to the subscriber.

Database Service Management, Inc. (DSMI) manages the SMS, see 47 C.F.R. § 52.103(f)(1), but does not itself collect or update the data the SMS uses to route calls. Instead, so-called Responsible Organizations input and update the information contained in the SMS database. See CompTel Declaratory Ruling, 8 F.C.C.R. 1423, ¶ 19. Any entity that meets certain financial, technical, and service-related eligibility criteria — whether an IXC, an LEC, a subscriber, or another type of entity— may serve as a Responsible Organization. See id. at ¶¶ 41-47. Because DSMI is a monopolist, and because access to the SMS database is necessary to the provision of toll-free service, the Commission requires DSMI to provide Responsible Organizations with such access under a tariff; the agency’s purpose is to ensure “that SMS access is provided at reasonable rates and on nondiscriminatory terms.” Id. at ¶ 29.

In 1993 the Commission required the BOCs, which at that time jointly owned DSMI, to file an SMS access tariff. See id. at ¶ 31. The Commission then suspended that tariff for one day and instituted an investigation into its lawfulness. See In the Matter of the Bell Operating Companies’ Tariff for the 800 Serv. Mgmt. Sys., 8 F.C.C.R. 3242 (Com. Car. Bur. 1993). Eventually the Commission concluded that the rates the BOCs proposed to charge in the SMS access tariff were reasonable. See In the Matter of 800 Data Base Access Tariffs and the 800 Serv. Mgmt. Sys. Tariff, 11 F.C.C.R. 15,227, ¶ 251 (1996) (SMS Tariff).

Beehive is an LEC operating in rural Nevada and Utah. It is also a Responsible Organization. During the pendency of the above-mentioned investigation, Beehive filed a complaint against the BOCs alleging that the SMS access tariff is invalid because the Commission lacks jurisdiction under the Communications Act of 1934 to regulate SMS access as a common carrier service. See 47 U.S.C. § 153(10) (defining “common carrier”); id. § 153(52) (defining “wire communication”); id. §§ 201-203 (setting forth duties of common carriers). In the alternative Beehive claimed, that the tariffed rates are unjust and unreasonable. See id. § 201(b). In a subsequent pleading Beehive also alleged that the Commission violated its own rules governing whether and to what extent third parties are allowed to have ex parte contacts with the Commission concerning a complaint proceeding. See 47 C.F.R. §§ 1.1200-1.1216 (1993).

In 1995 the Commission denied Beehive’s complaint without ruling upon the issue of ex parte contacts. Beehive petitioned this court for review but before briefing was completed the Commission moved for a remand, which we granted, so it could pass upon the ex parte issue. In 1997 the Commission rejected Beehive’s ex parte contacts claim and re-adopted and reaffirmed the 1995 opinion and order that we had vacated at its request. See Beehive Tel., Inc. v. Bell Operating Cos., 12 F.C.C.R. 17,930, 17,950 (1997). Beehive again petitions for review.

II. Analysis

Beehive argues first that the Commission lacks authority under the Communications Act to regulate SMS access as a *944 common carrier service and therefore to require tariffed rates. Second, Beehive claims the Commission violated its ex parte rules governing complaint proceedings. Finally, Beehive asserts that the agency has failed in a timely fashion to require that the toll-free database be transferred to “one or more impartial entities,” as required by 47 U.S.C. § 251(e)(1).

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Teliax, Inc. v. AT&T Corp.
220 F. Supp. 3d 1094 (D. Colorado, 2016)
AdvnNewhse Comm v. FCC
460 F.3d 31 (D.C. Circuit, 2006)

Cite This Page — Counsel Stack

Bluebook (online)
179 F.3d 941, 336 U.S. App. D.C. 331, 16 Communications Reg. (P&F) 473, 1999 U.S. App. LEXIS 13636, Counsel Stack Legal Research, https://law.counselstack.com/opinion/beehive-telephone-co-v-federal-communications-commission-cadc-1999.