Provider certification record
OnewayNetworks Technologies Private Limited
Listed- RMD number
- RMD0042591
- FRN
- 0039115332
- OCN
Identity
- Legal business name
- OnewayNetworks Technologies Private Limited
- Doing-business-as
- ownpbx
- Foreign Voice Service Provider
- Yes
- Business address
- b-52, UGF, Kesho ram park Uttam nagar New delhi, delhi 110059 new delhi, India
- Filing contact
- Ashish Kushwaha
Director · Compliance
ashish@ownpbx.in
+91 98119 74682
b-52, UGF, Kesho ram park Uttam nagar New delhi delhi 110059 new delhi, India
India - Principals, Affiliates, Subsidiaries, and Parent Companies
- Ashish Kushwaha, Director. Karan Sharma, Director. No parent company, subsidiaries, or affiliates
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Rule relied on: 47 CFR § 64.6301 (STIR/SHAKEN implementation) does not apply to the filer because it is a foreign voice service provider. Under 47 CFR § 64.6305, foreign voice service providers using U.S. NANP numbers must file in the Robocall Mitigation Database and maintain a robocall mitigation program, but are not required to identify a § 64.6304 extension. Why it applies: ONEWAYNETWORKS Technologies Private Limited (d/b/a ownpbx) is a private limited company incorporated in India with its registered office in New Delhi. It has no office, network facilities or switching equipment in the United States. It holds no Operating Company Number (OCN), has no direct access to U.S. numbering resources, and has not been issued an SPC token by the STI Policy Administrator, so it cannot sign calls under the STIR/SHAKEN framework. All calls ownpbx sends with U.S. NANP caller IDs are routed through [Upstream Carrier Name], a U.S. provider listed in the Robocall Mitigation Database, which authenticates them under its own STIR/SHAKEN certificate before they reach U.S. networks. All calls ownpbx originates are covered by the robocall mitigation program in the attached plan, including customer KYC, verification that customers are authorized to use their caller IDs, call-volume limits, traffic monitoring, and full response to all traceback requests within 24 hours. If ownpbx obtains an OCN and SPC token, it will implement STIR/SHAKEN and update this filing within 10 business days.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Ashish Kushwaha
- Date
- 2026-11-03No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-11-02 | New | Initial certification filed and added to database. |