Provider certification record
Keller PBX LLC
Listed- RMD number
- RMD0042154
- FRN
- 0038878807
- OCN
Identity
- Legal business name
- Keller PBX LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 15703 Pine Mountain Dr, Houston TX 77084
- Filing contact
- Isaac Murphy
President · Executive
isaac@kellerpbx.com
(409) 223-8317
15703 Pine Mountain Dr Houston TX 77084
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Isaac Murphy, President (sole member); Affiliates: Keller Computers; Parent: none; Subsidiaries: none
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- 47 CFR § 64.6304(b): "Voice service providers that are incapable of obtaining an SPC token due to Governance Authority policy are exempt from the requirements of § 64.6301 until they are capable of obtaining an SPC token." KELLER PBX LLC is a new interconnected VoIP provider. It was formed on September 14, 2026, and begins providing service to customers in October 2026. It is currently incapable of obtaining an SPC token due to Governance Authority policy. Under the STI Governance Authority's SPC Token Access Policy (Policy Decision 001, version 1.2), the STI Policy Administrator clears a provider for access to STI certificates only if the provider (1) has a current FCC Form 499-A on file with the Commission, (2) has been assigned an Operating Company Number (OCN), and (3) has certified to the Commission that it has implemented STIR/SHAKEN or complies with the robocall mitigation program requirements, and is listed in the Robocall Mitigation Database. The policy also provides alternatives for toll-free Responsible Organizations (proof of payment of the annual Resp Org fee in place of a Form 499-A, a Resp Org ID in place of an OCN, and a path for non-service-provider Resp Orgs with direct access to toll-free numbers). Those alternatives do not currently apply to the Company, which is not currently a Resp Org and has no Resp Org ID. If the Company becomes a Resp Org, it will update this filing within 10 business days (47 CFR § 64.6305(d)(5)). As of this filing, the Company does not meet the criteria. It has not been assigned an OCN, which by itself prevents it from obtaining a token. Its only FCC Form 499-A filing to date is its new-filer registration (Filer ID 839295). Its first annual Form 499-A, reporting its revenue for calendar year 2026, is due April 1, 2027. This is its first Robocall Mitigation Database certification, so it is not yet listed in the Database. The Company will be capable of obtaining an SPC token once it meets all of the Governance Authority's criteria, including a Form 499-A that the STI Policy Administrator accepts as current. In its September 29, 2026 annual reevaluation (DA 26-1050), the Wireline Competition Bureau found that this extension remains necessary without modification while the Commission considers whether to repeal or narrow it. Steps the Company is taking to obtain an SPC token. (1) By October 20, 2026, the Company will send written inquiries to NECA about obtaining an OCN as an interconnected VoIP provider, and to the STI Policy Administrator about whether its Form 499-A registration satisfies the current-Form 499-A requirement. (2) Within 30 days after NECA confirms its requirements, or by December 31, 2026 if NECA has not responded, the Company will apply to NECA for an OCN. If NECA requires a Commission authorization first, the Company will apply for that authorization within the same period and will apply for the OCN within 30 days after the authorization is granted. (3) Within 30 days after it meets all of the Governance Authority's criteria, including a Form 499-A that the STI Policy Administrator accepts as current, the Company will register with the STI Policy Administrator and apply for an SPC token. If the STI Policy Administrator does not treat the Company's registration filing as a current Form 499-A, the Company expects to meet that criterion when it files its first annual Form 499-A, due April 1, 2027. (4) Within 60 days after its SPC token is issued, the Company will diligently pursue and obtain an STI certificate and begin signing the calls it originates, either on its own platform or through Telnyx LLC acting as a third-party authentication service that signs with the Company's certificate under a written agreement that meets 47 CFR § 64.6301(b). The Company will update this filing within 10 business days after it is assigned an OCN, after it obtains an SPC token, after signing begins, and after any other change to the information in this filing (47 CFR § 64.6305(d)(5)). It will also update its CORES registration within 10 business days of any change to that registration (47 CFR § 1.8002(b)(2)). The Company does not base this extension on the absence of directly assigned numbering resources or on any other provider's authentication of its calls; Telnyx LLC's signing with its own certificate is not treated as the Company's implementation of STIR/SHAKEN. The Company's network is all-IP; it operates no non-IP network. Illegal-robocall risk is addressed by the attached robocall mitigation program (know-your-customer checks limited to ordinary small-business office tenants, number-rights checks, know-your-upstream-provider checks, 24-hour traceback response, do-not-originate/invalid/unassigned blocking that never applies to 911 or 933, and action on Commission notices).
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Isaac Murphy
- Date
- 2026-10-15No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-10-15 | New | Initial certification filed and added to database. |