Provider certification record
TrioPBX PTY Ltd
Listed- RMD number
- RMD0020620
- FRN
- 0035290808
- OCN
Identity
- Legal business name
- TrioPBX PTY Ltd
- Doing-business-as
- Foreign Voice Service Provider
- Yes
- Business address
- 1/24 GranView Grove Bayswater Melbourne VIC 3153, Australia, Victoria Melbourne, Australia
- Filing contact
- Muhammad Sohaib
CTO · Tech
info@triopbx.com
+61 408 103 502
1/24 GranView Grove Bayswater Melbourne VIC 3153, Australia Victoria Melbourne, Australia
Australia - Principals, Affiliates, Subsidiaries, and Parent Companies
- Principals of TrioPBX PTY LTD refer to followings that hold significant ownership or decision-making authority within the organization. Muhammad Hassan Role: CEO and Owner Description: As the CEO and owner of TrioPBX PTY LTD, Muhammad Hassan provides strategic direction and leadership for the company. With a strong background in telecommunications and business management, he oversees the overall operations, including business development, client relations, and financial management. Muhammad Hassan is committed to driving innovation and delivering high-quality hosted PBX services to our customers. Muhammad Sohaib Role: Chief Technology Officer (CTO) Description: As the Chief Technology Officer of TrioPBX PTY LTD, Muhammad Sohaib leads the technical team responsible for the development and maintenance of our hosted PBX platform. With extensive expertise in telecommunications technology and software development, he drives the innovation and implementation of cutting-edge solutions to enhance our service offerings. Muhammad Sohaib plays a crucial role in ensuring the reliability, scalability, and security of our hosted PBX services, keeping them at the forefront of industry standards. Additional Information: TrioPBX PTY LTD does not have any affiliations, subsidiaries, or parent companies. The company operates independently under the leadership of Muhammad Hassan and Muhammad Sohaib, who are dedicated to providing exceptional hosted PBX services to our clients.
Classification
- Provider role(s)
- Intermediate provider
- STIR/SHAKEN implementation
Role Implementation Intermediate provider None Overall None - Exemption rules
- "We, TrioPBX PTY LTD., hereby seek exemption from the implementation of the STIR/SHAKEN authentication framework on our network. Our request for exemption is grounded in two primary factors: technical limitations and the effectiveness of our existing robocall mitigation program. Firstly, due to the intricate nature of our network infrastructure, implementing the STIR/SHAKEN framework across our entire network poses significant technical challenges. Our services, tailored specifically for taxi/cab booking over the phone, operate within a unique telecommunications framework, which presents complexities in integrating the required authentication protocols seamlessly. Secondly, we assert that our robust robocall mitigation program has consistently demonstrated its efficacy in preventing illegal robocall traffic and collaborating with regulatory authorities to investigate and halt illicit robocallers. Our stringent measures include real-time monitoring, advanced filtering algorithms, and prompt response mechanisms to all traceback requests from the Commission, law enforcement agencies, and industry consortiums. Furthermore, it's imperative to note that our clientele exclusively comprises reputable taxi and cab booking companies. We do not extend our services to unknown or unverified entities, thereby significantly reducing the likelihood of facilitating illegal robocalls. This targeted client base reinforces the integrity and safety of our telecommunications services in mitigating the risk of robocall abuse. In light of the aforementioned factors, we respectfully request the Commission's consideration for exemption from the STIR/SHAKEN implementation mandate. We remain committed to upholding the highest standards of call authenticity and integrity within our operational scope while ensuring seamless service delivery to our trusted clients.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Muhammad Sohaib
- Date
- 2026-02-17Last Recertified 2026-02-17
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-02-18 | New | Initial certification filed and added to database. |