Provider certification record
IP PBX Support, Inc
Listed- RMD number
- RMD0005787
- FRN
- 0031376379
- OCN
Identity
- Legal business name
- IP PBX Support, Inc
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 63 Bovet Road, #122, San Mateo CA 94402
- Filing contact
- Shawn Frye
Director · Tech Support
support@ippbxsupport.com
(650) 887-0158
63 Bovet Road #122 San Mateo CA 94402 California
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Shawn Frye
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider Partial Overall Partial - Exemption rules
- The filer qualifies for an ongoing extension from full STIR/SHAKEN implementation under 47 CFR § 64.6304(d), which exempts portions of networks that cannot initiate, maintain, or terminate SIP calls (non-IP segments) or, by extension, portions where full authentication is not yet implemented due to technical rollout phasing. Although the filer's network is fully IP-based (colocation datacenter with FreePBX/Asterisk/FreeSWITCH systems routing SIP traffic to upstream wholesalers), STIR/SHAKEN has been implemented only on applicable IP portions where the filer has direct control and customer validation, authenticating eligible originating calls with its own SPC token/cert and B-level (partial) attestation during ongoing rollout (effective [Jan/Feb 2026 date]).For originating calls not yet signed by the filer's B-level process (e.g., during phased rollout or on segments reliant on upstream providers), the filer relies on upstream carriers to apply STIR/SHAKEN authentication, including A- or B-level attestations with valid Identity headers. This hybrid approach ensures all originating calls are subject to authentication or mitigation consistent with FCC requirements, while avoiding origination/transmission of illegal robocalls through upstream vetting, monitoring, DNO lists, analytics, and traceback cooperation as detailed in the robocall mitigation program description (plan-2026.pdf). Full implementation across every originating call is not yet complete due to rollout phasing and lack of end-to-end control in certain segments, making partial implementation appropriate under the rules.
Prior investigations / actions
- Description
- Action: on 12/10/24, our company was flagged for not having a current/correct/updated Robocall Mitigation Database certification or mitigation program description (.PDF). We were not aware of this action until we were notified about FCC order number DA 25-694 (for) removal from the RMD (for non-compliance) on/about 08/06/25. We had no knowledge about this action/flagging/notifications. To solve this: We had thought our initial (original) RMD portal filing was active and current. We have since signed up for weekly RMD email updates (arriving each Tuesday), and we have added to our company practice to do quarterly check-ins with the RMD portal and/or how to contact RMD/FCC/FRN team members (via email). Action: on 08/06/25, we were notified our company was being removed from the RMD for not having a Robocall Mitigation Database certification and/or a mitigation program description (.PDF). This action was being taken due to the FCC order number DA 25-694. To solve this: We fixed this on 08/07/25 by updating our information in the RMD portal and by uploading and completing our Robocall Mitigation Database certification and mitigation program description (,PDF).
Robocall mitigation plan
Declaration
- By
- Shawn Frye
- Date
- 2026-02-25Last Recertified 2026-02-25
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-02-25 | New | Initial certification filed and added to database. |