Provider certification record
Wappler Wireless LLC
Listed- RMD number
- RMD0039914
- FRN
- 0038359188
- OCN
Identity
- Legal business name
- Wappler Wireless LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 7055 Old Katy Road, 1240, Houston TX 77024
- Filing contact
- RObert Feliz
CTO · Service
rob@wapplerwireless.com
(713) 836-0788
7055 Old Katy Road 1240 Houston TX 77024
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Rob Feliz
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Rule: 47 CFR § 64.6304(d) (continuing extension for non-IP networks) and the recognized exemption for providers that lack control over the network infrastructure necessary to implement STIR/SHAKEN (as described in the Sixth Caller ID Authentication Report and Order and related FCC guidance). Explanation: The filer is a voice service provider that is in the startup phase with no customers and is building an IP-based voice service. Because the company has no active customers and is not yet originating any live voice traffic on its network, it currently has no operational calls to which STIR/SHAKEN authentication would apply. More fundamentally, as a pre-commercial startup, the filer does not yet exercise full control over the end-to-end network infrastructure necessary to implement, test, and operationally deploy the STIR/SHAKEN framework (including obtaining and using its own STI certificate/token, integrating signing/verification into call flows, and ensuring reliable performance in a production environment). STIR/SHAKEN implementation obligations under 47 CFR § 64.6301 apply to voice service providers on the IP portions of their networks. However, FCC rules and orders recognize that providers lacking control over the necessary network infrastructure are not required to implement STIR/SHAKEN until they are in a position to do so. This situation directly matches that exemption: the company is still in the development and testing phase, has zero subscribers or originated traffic, and has not yet activated full production call-handling infrastructure. Once the filer begins originating calls and brings its IP infrastructure fully online, it will promptly obtain the required STI certificate and implement STIR/SHAKEN authentication on its IP network (or partial implementation if any non-IP elements are later incorporated). In the interim, the filer will fully comply with all other obligations under 47 CFR § 64.6305, including maintaining a robust robocall mitigation program that covers any pre-launch testing traffic, know-your-customer (or know-your-upstream) procedures once customers are onboarded, cooperation with traceback requests within 24 hours, and blocking of illegal robocall traffic using reasonable analytics and a reasonable Do Not Originate (DNO) list. The robocall mitigation program description uploaded with this filing provides further details on these steps. This exemption applies precisely because the filer is not yet in a position to originate customer traffic and therefore does not control a live production network infrastructure capable of full STIR/SHAKEN deployment. The filer will update its RMD certification immediately upon any material change (e.g., launch of customer service or activation of production traffic) as required by FCC rules.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Robert Feliz
- Date
- 2026-04-29No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-05-15 | New | Initial certification filed and added to database. |