Provider certification record

Teamnex Solution LLC

Listed
RMD number
RMD0040857
FRN
0038688842
OCN
 

Identity

Legal business name
Teamnex Solution LLC
Doing-business-as
 
Foreign Voice Service Provider
No
Business address
484 S Atlantic Avenue, Ormond FL 32176
Filing contact
Shiv Patel
Director · Executive
finance@teamnex.solutions
(386) 320-3501
484 S Atlantic Avenue Ormond FL 32176
United States of America

Classification

Provider role(s)
  • Voice service provider
STIR/SHAKEN implementation
RoleImplementation
Voice service providerNone
OverallNone
Exemption rules
The filer provides hosted PBX services to a limited number of small business customers. The filer does not independently implement STIR/SHAKEN authentication because it is presently incapable of obtaining an SPC Token under the STI Governance Authority eligibility requirements. The filer does not currently possess an Operating Company Number (OCN) and does not hold direct numbering resources, and therefore is not currently eligible to obtain an SPC Token or STI certificates necessary to authenticate calls pursuant to 47 CFR § 64.6301. The filer's platform permits customers to connect either the filer's supported upstream SIP carrier or a SIP trunk obtained independently by the customer from a carrier of their choosing. Customers retain control over their SIP trunk credentials and telephone numbers where they elect to use their own carrier. When the filer's upstream carrier is used, outbound PSTN traffic is delivered through that carrier, which performs STIR/SHAKEN authentication and applies A-level attestation where appropriate under its own implementation. As part of the filer's robocall mitigation program, customers are prohibited from transmitting caller identification using telephone numbers that have not been assigned to them or for which they do not have the legal right to use. The platform is configured to permit only authorized caller IDs associated with the customer's provisioned service or verified trunk configuration. The filer performs customer due diligence, monitors for abusive or suspicious traffic, maintains call records as appropriate, and commits to responding promptly to traceback requests and cooperating with law enforcement, the FCC, and the registered industry traceback consortium. Based on the foregoing, the filer believes the exemption applicable to voice service providers that are incapable of obtaining an SPC Token due to STI Governance Authority policy applies to its current operating model. The Filer is currently in talks with advisors over obtaining the required certifications in order to hold its own SPC token and STI certificates.

Prior investigations / actions

Description
 

Robocall mitigation plan

PDF Robocall Mitigation Program V1.pdfFiled 2026-07-24 · 224 KB

Declaration

By
Shiv Patel
Date
2026-07-24No Recertification Date

Listing history

DateEventDetail / diff
2026-08-10NewInitial certification filed and added to database.