Provider certification record
BEM COMM LLC
Listed- RMD number
- RMD0042663
- FRN
- 0039076294
- OCN
Identity
- Legal business name
- BEM COMM LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 19560 Clay Road, Suite J, Katy TX 77449
- Filing contact
- Fernando J. Arellano
Member · Management
info@bem.solutions
(832) 983-9000
19560 Clay Road Suite J Katy TX 77449
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Fernando J. Arellano (sole member); BEM Solutions LLC (affiliate under common ownership)
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- 47 CFR § 64.6304(d) (voice service providers incapable of obtaining an SPC token). BEM COMM LLC is a newly formed Texas LLC (FRN 0039076294) that resells interconnected VoIP service to small-business end users. Under the STI Governance Authority's token access policy, a provider must have a current FCC Form 499-A on file, an Operating Company Number (OCN) and a Robocall Mitigation Database certification to receive an SPC token. BEM COMM has no 499-A history (its Form 499 filer registration with USAC is in progress) and no OCN, so it cannot obtain an SPC token at this time and therefore cannot sign calls itself. Until it can, the calls it originates are carried by upstream providers listed in the Robocall Mitigation Database, and all of its traffic is subject to the robocall mitigation program in the attached description (know-your-customer checks, caller ID limited to numbers assigned to the customer, call analytics with automatic holds, 24-hour traceback response). BEM COMM will request an SPC token as soon as it meets the Governance Authority's requirements, implement STIR/SHAKEN, and update this filing within 10 business days.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- fernando arellano
- Date
- 2026-11-05No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-11-04 | New | Initial certification filed and added to database. |