Are you serious? Don't make a fool of yourself—just give me back the money you took for yourself. Maybe I should take this to the appropriate authorities?
There seems to be a misunderstanding here, so let’s make the situation clear for everyone reading this thread.
Calling a SIP provider a “scam” simply because you could not get your PBX, dialer, softphone, or other SIP client configured correctly is not the same thing as proving that the SIP service itself is non-functional.
SIP trunking does not work like a normal application where you deposit money and everything on your side is automatically configured. The provider supplies the SIP account and the network-side service. The customer still has to configure their own equipment correctly and make sure the SIP credentials, registrar/domain, transport settings, codecs, firewall/NAT configuration, outbound route and other PBX parameters are correct.
In this particular case, the account was active and the balance was active. There was no failed deposit and the SIP credentials were not simply “dead.” The support request was primarily about how to use and configure the service on the customer's side.
That distinction is important.
If somebody buys a SIP account, puts the credentials into an incorrectly configured PBX, receives a registration failure or cannot place a call, that does not automatically demonstrate that the provider is offline. The same applies to Zoiper, MicroSIP, Asterisk, FreePBX, 3CX, or any other third-party software. A configuration problem inside a customer's environment cannot reasonably be presented as proof that the provider sold a non-functional account.
This is exactly why the setup guide was posted above. The basic procedure is straightforward:
- confirm that the SIP credentials being used are the current credentials from the account;
- enter them into a compatible SIP client or PBX;
- verify that the account actually registers;
- check the customer's outbound route and dial-plan;
- verify firewall/NAT and transport settings where applicable;
- only then start troubleshooting the actual call path.
If the account does not register despite correct credentials and a correctly configured SIP client, that is something support can investigate from the provider side.
What support cannot reasonably do is remotely configure every customer's PBX, dialer, firewall, NAT, softphone, operating system and third-party software for them. Those are customer-side components and configurations.
We have already explained this directly instead of simply ignoring the complaint. We can verify the status of the SIP account and investigate genuine server-side issues. But there is a difference between
“the SIP service is unavailable” and
“I don't know how to configure my PBX.”
The first is a provider-side problem.
The second is a configuration problem.
So before posting “SCAM,” “NON-FUNCTIONAL,” or telling other members not to use a service, please actually establish which of those two situations you're dealing with.
If you believe the account itself is genuinely non-functional, provide the relevant technical evidence: whether the SIP account registers, the exact error/response received, and enough information to determine whether the failure is occurring on the provider side or inside the customer's configuration.
Simply saying “I couldn't connect it” is not evidence that the service was non-functional.
And for everyone else reading this thread: if you are going to use a SIP trunk with your own PBX or softphone, make sure you understand that
buying the SIP access and configuring your own equipment are two separate steps. The fact that you successfully funded an account does not configure your PBX automatically.
We're not interested in arguing with anyone. If there is a genuine provider-side issue, report it and it will be checked. If the account is operational and the problem is on the customer's configuration side, calling the provider a scam doesn't change that fact.
SIP24.CC Operational Update & Route Status 
