Private OLT access
Use the selected network path to reach supported OLT management interfaces that are not publicly exposed.
PRIVATE DEVICE ACCESS
Reach private network devices through the client MikroTik workflow when direct public access is not appropriate.
Sweet Billing can use a selected client MikroTik VPN path for supported private devices while retaining conventional port-forward based deployment where required.
WORKFLOW FOCUSMikroTik Cloud VPN for Private ISP Devices
Evaluate this use case together with customer lifecycle, finance and network ownership—not as an isolated feature.
What to evaluate
Operational questions that matter in this workflow.
These are practical considerations for comparing software and designing your deployment.
Switch and access point workflows
Extend the same operational concept to supported switches, access points and other private devices.
Controlled router association
Make the selected client MikroTik part of the device-access configuration so the path is understandable.
Keep deployment options
VPN-based access can complement rather than eliminate conventional direct or port-forward deployment choices.
Why the connection matters
Subscriber state affects more than one department.
A payment can change service state. A support issue can depend on session or ONU context. A reseller collection belongs to a financial hierarchy. Sweet Billing is structured around those relationships.
Billingcycle & ledger
AccessPPPoE / Hotspot
NetworkMikroTik / OLT
Customerportal / support