Provider certification record
TELECOM XCHANGE
Listed- RMD number
- RMD0004338
- FRN
- 0024601833
- OCN
Identity
- Legal business name
- TELECOM XCHANGE
- Doing-business-as
- TelecomsXChange
- Foreign Voice Service Provider
- No
- Business address
- 1100 NW 163rd Dr, Miami FL 33169
- Filing contact
- Ameed Jamous
CTO · Technology
a.jamous@telecomsxchange.com
(954) 240-5411
1100 NW 163rd Dr Miami FL 33169
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Principals: Ameed Jamous, CEO Affiliates: None Subsidiaries:None.
Classification
- Provider role(s)
- Intermediate provider
- STIR/SHAKEN implementation
Role Implementation Intermediate provider None Overall None - Exemption rules
- Our company operates as a marketplace developer and aggregator, facilitating transactions between carriers. While we proxy SIP calls and perform Authentication, Authorization, and Accounting (AAA), we do not directly originate or terminate calls on our network. As such, the STIR/SHAKEN authentication framework implementation requirements do not apply to our business model. However, we maintain a robust robocall mitigation program, which includes: 1- Reasonable steps to avoid proxying illegal robocall traffic. - Require RMD number for anyone who wants to send calls to the USA. - We proxy any STIR/SHAKEN data we receive over our network to the terminating aggregator/telecom provider. 2- A commitment to respond fully and within 24 hours to all traceback requests from the Commission, law enforcement, and the industry traceback consortium. 3- Full cooperation in investigating and stopping any illegal robocallers using our platform.; We certify that all calls carried or processed on our network are subject to a robust robocall mitigation program consistent with 47 CFR § 64.6305(c). This program includes: 1- Reasonable steps to avoid carrying or processing illegal robocall traffic. 2- A commitment to respond fully and within 24 hours to all traceback requests from the Commission, law enforcement, and the industry traceback consortium. 3- Full cooperation with investigations to stop illegal robocallers using our services. As a marketplace/aggregator and non-gateway intermediate provider, we do not directly originate or terminate calls and do not implement the STIR/SHAKEN authentication framework. Therefore, we select Option 3: No STIR/SHAKEN Implementation, however if STIR/SHAKEN is used in SIP Payload we do properly support forwarding that to the next hop.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Ameed Jamous
- Date
- 2025-03-08No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2025-03-08 | New | Initial certification filed and added to database. |