Search results

I believe that function is called "whisper" or "agent guidance"

Thats why I'm suspicious about the handsets radios, it fels like they are sliding on their tdma slots. @glennbtn why don't you swap those 2 handsets with some cheaper gigasets for a couple of days?

And with some of our locations which are behind CGNAT even before the net reaches their modem, without rport turned on (yealink units) the phone can not even register to fusionpbx.

What I meant was move the extensions to different handsets but you made the same test ina much harder way :) At the moment I'm pretty sure that your handsets have faulty radio units.

To make sure that this is caused (or not caused) by fusionpbx, can you move one ıf the extension numbers to the not problematic handset and test it?

What ports are open and forwarded to your fusionpbx?

Out of cruosity, is it happening on a specific handset or both parties hear it?

Take a look at here: https://www.pbxforums.com/threads/no-entries-in-cdr.7600/#post-31029

The thing in your logs are, your fritz box is sending the comunication as "yyyyyyyyyyy@192.168.10.40" which the fusionpbx is comparing against thedomains you have setup on your system, which I assume do not have a domain called "192.168.10.40" :) if you have given a domain name to your default...

You need a domain on the system as "fritz.box" with the proper gateway(your fritz device.) or if you can configure your fritz box, make it report a different domain of your choice. Most of this firsr issues end up being about domains and the ip's not being in the acl.

Hi Shox, thanks for the reply but I've already tried doing what is suggested on that page (selecting multiple options from the drop down list) but the system only takes the last one selected into account. Can you give your system as an example? I need a lşttle bit guidance on how you achieve...

Hi everyone, I've looked around the forum but couldn't get an exact answer for this question. In general we have 3 types of numbers to dial out, 1XX, 7 digit and 11 digit. What type of method should I follow to implement all 3? A single outbound route with necesary edits or 3 different routes?

Personally I'm using MicroSip on PC's and Sipnetic on Android, and I'm happy with both of them, they both work very good with FusionPBX

It works as its supposed to, on Debian :) I've only enabled my country in whitelist and tried accessing it from one of my other VM's and it is blocked :)

Hey, this was in my mind this morning and seeing it on the forum made my day :) thanks for sharing! I'll go ahead and test it on debian and will let you know the results

I was just wondering how to do that, and voila :)

@ardyhash, I believe that this is caused by the installation scripts but I don't know any detail. Because I've installed the same VDS with debian 11, upgraded to debian 12, installed fusionpbx, and noticed that the iptables rules were not applied. This is not happening for the first time...

OK second feedback for followers; I've installed the VDS with Debian 11, upgraded to Debian 12 installled FusionPBX, noticed that iptables rules were not loaded, run iptables.sh manually, make a few test calls, and CDS works out of the box. Now I've been seeing this iptables rules not being...

I'm glad that it did worked out for you, and honestly I saw that instructions on your first post in this thread :) anyway, we now know how to fix this issue and maybe developers also may benefit from this outcome.

Ok first feedback: Before reformatting my VDS which is on OVH and Debian 12 installed (not upgraded), I've tried the suggestions on this page: Version Upgrade — FusionPBX Docs documentation docs.fusionpbx.com Especially this part: And it started to show all the CDR's right away.