Why is FreePBX 17 working much worse then the most Hardware systems?

Yes correct. It’s their cloud telephone system but it’s working good. For external connection you need the Trunk. But i mean only the solution is easy and good and working well.

Depends what you or your customer wants. Easybell is a great provider, but with the cloud you have monthly costs and you can’t do any internal calls if the internet is down. The SIP-Trunk is extremenly competitive and you have all under your control.

As mentioned, I run three FreePBX instances on Proxmox with no issues at all. Every one has at least one Easybell SIP trunk, plus my private one Telekom Company Flex.

You should follow the advises here like from @joni1802 to get down to the root cause of your issues. It’s not a FreePBX common thing.

@rene.hoehle I saw in your other thread that you’re running Asterisk 21 … all my FPBX 17 instances are using Asterisk 22.5.0. Maybe you try the version switch and check if you still have the issues?

@JaCoTec i’ve discussed that with @jcolp perhaps i try to upgrade to Asterisk 22 perhaps that will fix some problems. Is there a tutorial how to upgrade the Aasterisk version without breaking my whole system?

But i will do some more debug and yes Easybell is great and also the Cloud i use that for small things. The others are SIP-Trunks. Thats why it’s so annoying when my customers tell me that the solutions is much worse then the Auerswald solution before.

@jcolp i had a tcpdump running until someone tell me that there is a problem. Today the one worker told me that he couldn’t get an active line outside. There was an error soming and nothing happen. I could find the call in the dump.

The comment in that line is “INVITE 200 487”. The interesting thing is the “Duration” is 49 seconds but the call is empty.

After some minutes he called the number again and it was working well.

If that is a trace with the provider, then in the first one the provider has replied back that the remote side is ringing. No answer is received and the caller eventually gives up. There’s nothing that looks out of the ordinary with it.

@jcolp thats my problem. There was not connection and an error on the telephone. Then after some minutes he tried again and it was working. But on the second call there was no “Ringback” to hear. New i have asked Vodafone and what did they tell you? They have no problem they don’t really read my explanation they tell me directly that they have no problem.

The interesting thing is they have answered me that they couldn’t find that call that was terminated on their end. There was a ringing call over 49 seconds but they can’t find it.

But i hope you understand my problem for that post. All the people tell me that it’s working bad because of a lot of things and i can’t find any problems.

Hi.

If you’ve got a such issue, you can start to check your network.

Usually for a good pratice, you must separate your network in at least two sections.
Let say:

  • VLAN 10 - VoIP (FreePBX serveur, SIP Phones…etc)
  • VLAN 11 - Data (Workstation…Etc).
  • VLAN xx - Whatever you want.

Next, you must apply the QoS on your network.

  • Diffserv 46 for RTP (Audio).
  • Diffserv 40 for SIP protocol

Remember that RTP stands for Audio, and therefore RTP stands for Real Time Protocol all small packets have priority.

Next you can check the MTU on your NIC device.
Don’t use it in Auto but set it up manually with the value at 1500.
You can try, step by step with 1501, 1502… but at a moment, the problems would arrive maybe at 1506.
If you are not sure, leave it at 1500.

Next, check if your issue arrives for any type of calls (Internal, external) or only with external calls, or only with internal calls or both.

Next, check your NAT settings with your external firewall or router.
Don’t forget to check your networks in SIP settings. Clicking on auto-detect, and add your netwokk. If you have different networks, add them too.

If your issue is with external calls, then check you configs (Invite…etc). Maybe your session is tarminated during your call. Add a keep alive…etc

Just an idea like that.

@rene.hoehle With the limited information I don’t really have anything else to add. I can only state what has happened in the packet capture, I don’t know what happened upstream - and it is concerning that they said they could not find the call as there are clearly responses from them.

@franckdanard thanks for you reply. So the connection from our FreePBX and the Vodafone is without any rules and QOS is enabled but our internet connection is not near the limit. This was a fresh FreePBX 17 installation on a standalone computer. I will lower the keepalive to test.

@jcolp after telling them thats not possible because their site has answered they investigate now :smiley:

Ok. you can test indeed.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.