This happens mostly on roaming charge sessions. If the connection is somehow interrupted, the chargespot does not send a stop order to the backend. Therefore, we have to stop the session manually. Follow the guide below to stop the charge session:
This happens mostly on roaming charge sessions. If the connection is somehow interrupted, the chargespot does not send a stop order to the backend. Therefore, we have to stop the session manually. Follow the guide below to stop the charge session: