Voice over Internet Protocol - Yesterday, Today and Back to Yesterday

By Rozanne Andersen

November 28, 2017


Sadly, most people in the ARM industry –  including defense attorneys and judges – have little idea how to determine whether a Voice over internet Protocol (VoIP) call is subject to the TCPA.  How do you go about your analysis? First, let’s make sure you understand the definition of a VoIP call, know a bit about statutory construction, and recognize where you’re at risk.

For additional clarification see,


What is a VoIP call anyway? How is it useful?

According to Webopedia, Voice over internet Protocol is a category of hardware and software that enables people to use the internet as the transmission medium for telephone calls by sending voice data in packets using IP rather than by traditional circuit transmissions of the PSTN. VoIP can turn a standard internet connection into a means of placing and receiving phone calls on free software. The practical upshot here is that by using some of the free VoIP software available to make internet phone calls, you’re bypassing the phone company (and its charges) entirely. Many businesses and consumers use VoIP technology to place and receive calls.


What does the TCPA say about VoIP calls?


There is no specific reference to the term VoIP or calls placed using voice over internet protocol in the TCPA’s text or its regulations.  However, within the context of restrictions placed on the use of automated telephone equipment and prerecorded messages to place calls to cellular phones, the TCPA seemingly grabs VoIP calls into the mix. In 47 U.S. Code § 227 (b)(1) the TCPA provides,

It shall be unlawful for any person within the United States or any person outside the United States if the recipient is within the United States—

(A) to make any call (other than a call made for emergency purposes or made with the prior express consent of the called party) using any automatic telephone dialing system or an artificial or prerecorded voice— …

(iii) to any telephone number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service, or any service for which the called party is charged for the call, unless such call is made solely to collect a debt owed to or guaranteed by the United States…

This section of the TCPA has been broadly interpreted to apply to calls placed to consumers who use a  VoIP service.


Has there been any precedent set?
As reported in insideARM, the Fourth Circuit Court of Appeals ruled that calls made to a residential line using an autodialer can violate the TCPA if the residential line service charges for incoming calls. In Lynn v. Monarch Recovery Management, Inc., No. 13-2358, 2014 U.S. App. LEXIS 18858, — Fed. Appx.— (4th Cir. Oct. 2, 2014), the Fourth Circuit affirmed a District Court of Maryland decision holding a debt collector violated the TCPA when it used an (ATDS) to call a residential line that had been converted to a Voice over Internet Protocol (VoIP) service for which the debtor was charged a monthly rate, along with a fee for incoming calls and for transmission of incoming calls.

The called party was using a VoIP subscription that carried per-call charges to deliver numerous debt collection calls to the plaintiff. On the appeal, the court affirmed the lower court’s decision that because the VoIP service charged for incoming calls, it met the definition under the TCPA.

“… [t]he language of the TCPA goes beyond cell numbers, stating, “making any call…using any [ATDS] or an artificial or prerecorded voice…to any telephone number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service, or any service for which the called party is charged for the call.

But, at least one other court has held that when a VoIP app requires a flat, monthly fee without incurring charges for each call, that VoIP service is not a “service for which the called party is charged for the call.” Karle v. Sw. Credit Sys., No. 14-cv-30058, 2015 WL 5025449, at *6 (D. Mass. June 22, 2015). Additionally, several courts outside the Seventh Circuit have weighed in, concluding that the call-charged provision applies to VoIP apps. “Except where there is no evidence that the called party was charged for the call, courts generally” recognize that, when a plaintiff pays for services on a per-call basis, like paying for minutes on a cell phone, the plaintiff has a viable claim under 47 U.S.C. § 227(b)(1)(A)(iii). See Jones v. Experian Info. Sols., No. 14-cv-10218, 2016 WL 3945094, at *7 (D. Mass. July 19, 2016).

Little more has been done by the judiciary to advance the analysis of VoIP calls under the TCPA than conduct a literal reading of the statute. Most recently in June of 2017, the court in Baemmert v. Credit One Bank, N.A., once again ruled VoIP calls that trigger a charge to the called party on a per use basis were subject to the TCPA.

In this case, the plaintiff claimed the defendant’s collection agencies placed calls to his VoIP number using an ATDS without the plaintiff’s consent. The defendant disagreed and argued such calls were not placed using an ATDS; and if they were, the calls were received by the plaintiff’s VoIP line and were therefore not subject to the TCPA.

On the parties’ cross motions for summary judgment, the court disagreed with the defendant and ruled in favor of the plaintiff. As of this writing I am not aware of an appeal of this ruling. This court’s 18-page analysis is none the less worth noting.

The undisputed facts established plaintiff’s phone was not a functioning cell phone with cellular service. The cellular service had been disconnected due to nonpayment. However, the plaintiff was able to place and receive calls on the phone using a VoIP app he downloaded to his cell phone which worked only when he was connected to the internet. Since the app plan charged the plaintiff for calls placed and received on a per call basis, the court opined the calls were made using a “service for which the called party is charged for the call” under 47 U.S.C. § 227(b)(1)(A)(iii).

If a VoIP service charges on a per-call basis, that service falls under the broad statutory language, “any service for which the called party is charged for the call.” 47 U.S.C. § 227(b)(1)(A)(iii). Until courts begin to apply the proper rules of statutory construction to this provision of the TCPA, callers must treat VoIP calls as calls to cells when using an ATDS, prerecorded message or artificial voice.

Tomorrow on the OS blog, Rozanne weighs in on the Breda v. Cellco Partnership case.


Rules of Statutory Construction – A Primer for Defense Attorneys and Judges
By John Bedard Jr., Bedard Law Offices
The Readers Digest version of the argument is this: Statement: When I grow up, I want to be like Michael Jordan, Reggie Jackson, Joe Montana or any fierce competitor. Statutory interpretation 101 demands that “or any fierce competitor” be interpreted in context. It is wrong to conclude that I want to grow up to be like Napoleon, who is undeniably a fierce competitor, *but not of the type identified in the specifically recited examples*. I want to be a fierce *athlete* competitor. This cannon of statutory interpretation, ejusdem generis, requires this result.  If it was interpreted any other way, then there would be no reason to recite Jordan, Jackson, and Montana because the catch-all would include (swallow) themInstead, Jordan, Jackson, and Montana give meaning to the limits of “any fierce competitor” else reciting them would have no meaning at all – the catch-all would yield the same result. To say it a different way, the sentence cannot mean the same thing if we removed Jordan, Jackson, and Montana.
These two sentences *do not* have the same meaning:
Sentence 1:  When I grow up, I want to be like any fierce competitor.
Sentence 2:  When I grow up, I want to be like Michael Jordan, Reggie Jackson, Joe Montana or any fierce competitor.
The recitation of Jordan, Jackson, and Montana serves to define the limitations of “any fierce competitor” to “any [similar] fierce competitor.” In this case, the similarity is that they are all athletes. (They are also all males, but that is not their similar “competitive” characteristic.)
For purposes of subsection (iii) the immediately preceding services are all “wireless” services i.e. radio common carrier, cellular telephone etc.  VoIP services are not wireless and the FCC has previously referred to them as “wireline” services.  Moreover, the number was not “assigned to” any service the type of which is described in the immediately preceding list of services – wireless services.  Why is this important? It means the TCPA should not be construed to apply to VoIP calls.
Reprinted with permission of John Bedard. For additional information readers may contact attorney, John H. Bedard, Jr., principal Bedard Law Group, P.C. at 2810 Peachtree Industrial Blvd., Suite D, Duluth, Georgia 30097, phone:  678-253-1871 ext. 244, email

Disclaimer: Ontario Systems is a technology company and provides this blog article solely for general informational and marketing purposes. You should not rely on the content of this material for any other purpose or as specific guidance for your company. Ontario Systems’ advice, services, tools and products described herein do not guarantee compliance with any law or industry standard. You are ultimately responsible for your own company’s actions and compliance efforts. Because everyone’s situation is different, you must consult your own attorneys, accountants, and/or other advisors to obtain specific advice on your company’s compliance, legal, tax, regulatory and/or other business needs. Despite Ontario Systems’ efforts to provide current and up-to-date information, you need to recognize that the information contained herein may become outdated quickly and may contain errors and/or other inaccuracies.

© 2017 Ontario Systems, LLC. All rights reserved. Information contained in this document is subject to change. Reproduction of this publication is not permitted without the express permission of Ontario Systems, LLC.

About the Author

Rozanne Andersen

Rozanne Andersen, J.D., serves as Ontario Systems’ Vice President and Chief Compliance Officer. She is responsible for leading Ontario Systems’ corporate efforts and response to the CFPB’s launch of compliance examinations in the ARM industry. Rozanne is a recognized thought leader in the area of compliance. Her advocacy work on behalf of the credit and collection industry has resulted in landmark legislation and regulation at both the state level and at the federal level with regard to the FDCPA, FCRA and HIPAA.

Sign Up For Email Updates