Software responsibility & compliance.
Read this before you launch
UDSOFTSOL is a software vendor. We provide the switching and billing engine. We do not provide phone numbers, PSTN connectivity, or voice minutes. Clients are solely responsible for their carrier relationships (BYOC), end-user KYC, and regulatory filings.
What UDSOFTSOL provides
- Class 4 and Class 5 softswitch software, routing and SIP trunking
- Real-time CDR rating, billing, invoicing and balance management
- Multi-tenant reseller hierarchy, packages and customer portals
- DID management, call center and WebRTC modules
- Reporting, dashboards, REST API and CRM integration capability
- Deployment, configuration and onboarding support
What UDSOFTSOL does not provide
- Phone numbers, DID inventory or number porting execution
- PSTN connectivity, voice minutes or termination capacity
- A carrier-of-record relationship with your end users
- Carrier contracts, rates or regulatory licensing
- End-user KYC, credit checks or identity verification
- Collected, remitted or accounted regulatory taxes and fees
Responsibility matrix
The same split applies on every deployment — hosted, private cloud or custom.
| Area | UDSOFTSOL | Your business (client) |
|---|---|---|
| Switching, routing, billing software | Owns | Configures and operates |
| Carrier relationship and contract | Not involved | Owns |
| Numbers, DID inventory and porting | Not involved | Owns |
| End-user KYC / identity verification | Not involved | Owns |
| Regulatory filings (RMD, licences, A2P 10DLC) | Not involved | Owns |
| STIR/SHAKEN attestation and calling-party identity | Platform capability to carry and record it | Owns the filing and the attestation policy |
| Toll fraud prevention policy and credit controls | Tools: credit limits, rate decks, call reports | Owns the policy and enforcement |
| End-user support and billing disputes | Platform-level support | Owns customer-facing support |
| Revenue, margin and carrier settlement | Not involved | Owns |
This matrix describes the standard commercial relationship. It does not replace legal advice — your counsel should review the obligations that apply in the jurisdictions where you operate.
Filings that commonly apply to BYOC operators
This is not an exhaustive legal list — it is the set of obligations we hear about most often, so nothing is a surprise later.
FCC RMD & Filings
If you are providing services to end users in the United States, responsible organisation documentation and any required registrations are your obligation.
STIR/SHAKEN
Calling-party identity attestation, your SHAKEN certificates and your calling-party name policy sit with your operation, not the platform.
Local & State Licences
Many jurisdictions require their own telecom licence for services delivered into that region. Filing, fees and renewals are yours.
End-User KYC
Know-your-customer checks on your subscribers, account opening, and keeping records of identity verification documents.
A2P 10DLC
If you send automated or application-originated messages, brand and campaign registration with carriers is a separate obligation from the software.
Taxes & Remittance
Where you're the party responsible for collecting and remitting taxes, surcharges or regulatory fees on traffic, that remains with your operation.
Software support for your compliance programme
We can't file your paperwork for you — and we won't pretend to. What we do is make the obligations that live in software straightforward to implement and evidence.
- Per-user, per-reseller and per-tenant permissions so your staff only see what they should
- SIP security tooling and detailed CDR records to support investigations and audits
- Credit limits, rate decks and real-time call reporting for toll-fraud controls
- Tenant isolation so customer and sub-reseller data stays separated in your deployment
- Configuration guidance from engineers who have run live carrier deployments
In a private cloud deployment
Where you need to prove where your data lives, a dedicated instance changes the conversation — the platform runs inside your infrastructure and your account, not ours.
- The instance runs in your cloud account or data centre
- You control data residency, backup and retention policy
- Custom SLA, support terms and escalation paths agreed in writing
Compliance questions, answered
Does UDSOFTSOL act as my carrier of record?
No. UDSOFTSOL provides software only. Under the BYOC model you contract directly with your carrier, hold the numbers and answer to your regulators as the service provider.
Can you resell numbers or minutes to my customers?
No. We do not sell phone numbers, PSTN connectivity or voice minutes, and we take no margin on your carrier spend. Your commercial relationship with your carrier and with your subscribers is entirely yours.
Who does end-user KYC?
You do. The platform gives you places to record and manage account and subscriber information, but collecting, verifying and retaining identity evidence is your responsibility as the party providing the service.
What happens if a regulator contacts one of my customers?
The customer relationship is yours, so the engagement is yours. Our role is to provide accurate CDR records, user and account data, and an audit trail that supports your response — which is why detailed call reporting is a core part of the platform.
Is the platform itself certified?
Certification status varies by deployment and is covered in your agreement rather than advertised as a blanket site-wide claim. Ask us for the current position for the specific deployment you're evaluating — we will give you a straight answer, including where we are not yet covered.
Can we sign a data processing agreement?
Yes. Our privacy policy and terms of service set out the baseline, and a DPA or equivalent can be executed as part of onboarding for enterprise and private cloud deployments.
Want the contract to say the same thing?
Send us your requirements. We'll show you the software, answer the compliance questions directly, and put the boundaries in writing before you commit.