Traffic pumping

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Traffic pumping, also known as access stimulation,[1] is a controversial practice by which some local exchange telephone carriers in rural areas of the United States inflate the volume of incoming calls to their networks, and profit from the greatly increased intercarrier compensation fees to which they are entitled by the Telecommunications Act of 1996.[2]

As of March 2010, traffic pumping is the subject of an ongoing legal and regulatory dispute involving AT&T, Google Voice, rural phone carriers, and the U.S. Federal Communications Commission (FCC).[3][4]

Definition

Under the regulatory mechanisms of the Telecommunications Act of 1996, wireless, and long distance carriers, such as AT&T, Sprint, T-Mobile US, and Verizon, pay access fees to local exchange carriers (LECs) for calls to those carriers' subscribers. The FCC permits rural carriers to charge substantially higher access fees than carriers in urban areas, based on the rationale that they must pay for substantial fixed infrastructure costs while handling lower call volume.[2][5][6]

To increase the incoming call volume to those rural areas, and thereby fees earned, rural carriers partner with certain telephone service providers to route their calls through the rural carrier. These services typically include phone sex and conference call providers, which expect a high volume of incoming calls. Notably, these service providers do not need to establish a physical, local presence for routing these calls.[2][3][5] As a consequence of this arrangement, the rural carriers can receive millions of dollars of fees, which they share with the service providers.[2]

Payment for inbound long distance calls to small rural telephone companies is normally handled through a shared pool, the National Exchange Carrier Association ("NECA"). Individual telcos are free to opt out of this process. For the first two years, they may bill interexchange carriers directly at an initially-high rural rate of five to thirteen cents per minute.[7] After two years the carrier either rejoins the NECA pool, provides evidence to support continuing to charge the high rural rate or reduces rates to a level that can be supported.[8] A sudden increase in inbound calling volume at about the same time as a telephone company leaves the NECA pool therefore can represent profitable two years for that firm.

The numbers used for the service belong to a competitive local exchange carrier or independent telephone company and may be located in a rural numbering plan area in a sparsely-populated state, such as area code 218 in northern Minnesota or area code 712 in western Iowa.[9]

Voice over IP

In 2006, various startup companies began to offer voice over IP or Internet fax services which purported to be "free"; these operated from Iowa or used Iowa local numbers.[10] One such service, callchinaforfree.com, invited users to call a number in Iowa's area code 641 to reach a voice-over-Internet gateway from which calls could be made to China (country code +86) at no additional cost.[11] Another, talkdigits.com, operated under multiple names (FreeDigits, TalkDigits, OfficeDigits, FaxDigits, ClickDigits, and SIPnumber) to offer a "free US phone number" to receive "free inbound calls" and voicemail[12] or "free fax service" with "unlimited incoming faxes"[13] which would then be delivered outside the region via broadband Internet.

By 2007, the calls to China for the price of a call to rural Iowa were no more[14] as AT&T disputed millions of dollars in calls.[15] By 2008, the offer of a free Iowa number for inbound Internet voice and fax calls had also been withdrawn.[16] As of 2014, IPKall offered "free" Washington (state) numbers to voice over IP subscribers anywhere on the Internet, but chose to discontinue services after May 1, 2016.

Consequences

End-users of traffic-pumped phone services often do not pay directly for the high fees collected by rural local carriers and service providers. Many wireless and land line customers now have unlimited long-distance plans, and thus the entire inflated cost of using these services is borne by their long-distance carrier.[2][3][5] Providers of traffic-pumped conference calling services assert that these long-distance carriers still profit when their customers use traffic-pumped services.[17]

In 2007, AT&T estimated that it would spend an additional $250 million to connect such calls,[2][3] and has warned that it may have to raise its customers' calling plan prices unless regulators address the issue of traffic pumping. However, providers of traffic-pumped conference calls claim that AT&T has refused to provide evidence of these costs, and that it is a ploy by AT&T to leverage its market power to put competing conference calling providers out of business.[17]

AT&T and other long-distance carriers have in some cases attempted to avoid these costs by blocking their customers from calling the phone numbers of traffic-pumping services. However, the FCC has forbidden common carriers from this kind of selective blocking,[18] and so the long-distance carriers are essentially obligated to complete these calls.[2]

Based upon an independent study of 50% of long distance calls originating on wireless networks in the U.S., calls terminating to carriers meeting a traffic pumping profile were estimated to cost $95 million annually, representing 11% of all long distance costs in the study. Extending to all wireless service providers, the cost is estimated to be more than $190 million annually.[19]

Role in dispute between AT&T and Google

Lua error in package.lua at line 80: module 'strict' not found. The Google Voice telecommunications service offers a service similar to long-distance telephone calling at no cost, using VoIP to connect users with their calling destinations. In order to avoid paying high connection fees to traffic-pumping carriers, Google Voice blocked calls to some of these carriers.[1] As of 2014, Google Voice no longer blocks calls to these carriers, but charges its users a fee to reach them (while not charging for other calls to USA phone numbers).[20]

AT&T has appealed to the FCC to intervene,[3][21] charging that Google Voice ought to be required to connect these calls just as plain old telephone service (POTS) carriers are required to do so.[6] Google has responded[22][23] that its service, and those of VoIP providers such as Skype, is distinct from those of a traditional POTS common carrier, and that it should not be obligated to complete these calls.[1] Google further charges that AT&T is trying to distract the FCC from concerns regarding network neutrality, and accuses AT&T of conducting regulatory capitalism, in which businesses exploit laws and regulations to stifle competition and slow innovation. Finally, Google urges the FCC to revise "outdated carrier compensation rules" to end the practice of traffic pumping.[1]

AT&T has written to the FCC, stating that Google's blocking of calls to traffic pumping numbers gives it a substantial cost advantage over traditional carriers.[24] AT&T further argues that the issue of network neutrality is highly relevant, since Google is violating its own statement of the principle of non-discrimination, that "a provider 'cannot block fair access' to another provider."[24][25] AT&T agrees with Google that the FCC should act to forbid traffic pumping schemes in the first place, calling them "patently unlawful", but asks that Google be required to accept the same common carrier requirements even if they are not shut down.[24]

A bipartisan group of U.S. Representatives has joined in AT&T's complaint, urging the FCC to investigate Google Voice's practice of blocking calls to high-fee rural local exchange carriers.[4] Some of these legislators have received significant campaign contributions from AT&T, and represent districts where rural carriers profit from traffic pumping. Sam Gustin of DailyFinance suggests that there may be issues of conflict of interest and pork barrel politics involved in these legislators' efforts.[3]

Legal rulings

Lua error in package.lua at line 80: module 'strict' not found.

State administrative commission rulings

The Iowa Utilities Board issued its final order in 2009 in a complaint proceeding brought by Qwest and intervened by AT&T and Sprint Nextel against eight rural telephone companies in Iowa. Except for one call blocking finding against Sprint, the decision was unfavorable for the rural carriers, which may have to return the fees they received for calls directed to traffic-pumped services by Iowa residents.[26][27] However, damages have not yet been assessed and the Iowa Utilities Board does not have jurisdiction over the vast majority of disputed calls—those that were directed to Iowa from callers in other states—so the reach of its decision is limited. Moreover, the Board has indicated that it is reconsidering its decision and several appeals have been filed challenging the lawfulness of the Board's order, thus it is not yet a final decision.

The FCC subsequently issued a ruling in 2009 on this case.[7]

Federal Communications Commission administrative rulings

In 1996, AT&T filed a Section 208 complaint with the FCC against Jefferson Telephone Company, a rural incumbent local exchange carrier (ILEC) based in Iowa, which entered into a commercial agreement with a chat line provider.[28] AT&T's complaint alleged that Jefferson violated Section 201(b) of the Communications Act of 1934 because it "acquired a direct interest in promoting the delivery of calls to specific telephone numbers." AT&T also argued that the access revenue-sharing arrangement with the chat-line provider was unreasonably discriminatory in violation of Section 202(a) of the Act, because Jefferson did not share revenues with all its customers. The FCC rejected both these arguments and denied AT&T's complaint.

In 2002, the FCC issued two more orders, denying similar complaints by AT&T directed at LECs that shared access revenues with chat-line providers. In AT&T v. Frontier Communications, the Commission rejected AT&T's allegations that "revenue-sharing arrangements" constituted unreasonable discrimination in violation of Section 202(a) or violations of the ILECs' common carrier duties under Section 201(b).[29] In AT&T v. Beehive Telephone, the FCC again denied AT&T's complaint against a LEC that engaged in a commercial relationship with a chat-line provider for the same reasons.[30]

The FCC has more recently issued an order in a case involving an Iowa carrier relating to interstate calls (calls made from any state other than Iowa to an Iowa telephone number).[7] In that order, the FCC determined that the Iowa carrier was not entitled to collect the entire amounts it billed to a long distance carrier, but that it was nevertheless entitled to some compensation. The exact amount of payment has not yet been fixed by the FCC.[when?]

Court rulings

Cases remain pending in several courts across the country, including federal courts in Iowa, South Dakota, Minnesota, Michigan, Kentucky, and New York. Several courts have recently asked the FCC for additional guidance on determining the appropriate rate that should be paid by the long distance carriers for calls directed to traffic-pumped services, calling it an area of regulation "in dynamic flux."[31]

State legislation

Several long distance carriers lobbied[citation needed] the South Dakota legislature to propose legislation forbidding rural telephone carriers from entering into revenue-sharing agreements with traffic-pumped services.[32] However, the legislation was defeated.[33]

See also

References

  1. 1.0 1.1 1.2 1.3 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 3.5 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.. (PDF) . Retrieved on 2014-06-15.
  9. is one example of a conference bridge using +1-218 Minnesota and +1-712 Iowa extensively.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.. Web.archive.org (2008-09-26). Retrieved on 2014-06-15.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.. Web.archive.org (2007-04-03). Retrieved on 2014-06-15.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Explanation on Google Product Forums
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 24.2 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. AT&T Corp. v. Jefferson Tel. Co., 16 FCC Rcd. 16130 (2001)
  29. AT&T Corp. v. Frontier Commcn's of Mt. Pulaski, Inc., 17 FCC Rcd. Rcd. 4041-42, ¶¶ 1, 2 (2002).
  30. AT&T v. Beehive Tel. Co., 17 FCC Rcd. Rcd. 11641 (2002).
  31. All Am. Tel. Co., Inc. v. AT&T, Inc., 07 Civ. 861 (WHP), Docket 88 (Jan. 19, 2010)
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.

External links