On this page
Quick start
Configure a gateway, routing group, tariff and first client in the correct order.
Before you start#
We provide the rented server with configured SMSFLARE and administrator access. You supply the connection details from your own SMS provider; our team handles the technical setup. The steps below explain the panel settings used during setup and day-to-day operations. Use test numbers approved for your integration. Demo sample gateways are deliberately disabled and cannot prove delivery.
First SMS connection#
- Open SMPP Gateways and create the provider connection. Match its host, port, login, bind settings and addressing parameters.
- Check the connection mode and authentication requirements. Enable the connection only when the provider is ready.
- Open SMPP Clients → Routing groups. Create a group and add the intended gateway with its weight.
- Create a tariff and destination-prefix rates before enabling client billing.
- Add the client, its login/password and permitted IP addresses. Choose SMPP and assign the group or direct gateway.
- Set prepay or postpay, the tariff and any required wallet balance or credit limit.
- Connect your application over SMPP. Submit a controlled test and save its submit ID.
Verify the whole chain#
Find the submit ID in CDRs. Compare received and changed content, gateway, parts, price and final status. Open the SMPP trace to distinguish acceptance from delivery. Confirm the receipt reaches the application and that the wallet change matches the configured billing model.
Add Voice separately#
Prepare a SIP/UDP gateway, a Voice group, a matching route and compatible IVR or TTS audio. Then select VOICE for a canary client. Read Voice routing before enabling it.
Keep useful evidence#
Record the timestamp and time zone, submit ID, gateway, SMPP/SIP error, selected route and expected result. Keep credentials out of support attachments.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.