I have been stuggling for day on this one with deep dives into the PBX, the router, the ISP, my Vlan network plus virtual switches, ports and adaptors , endppoints, ESXi 7.0 and countless tcpdumps and analysis. I set up a second PBX to determine if the behavious were essential the same and they are. My two PBX’s worked within each of thier respective domains and support trunking between them and EVERYTHING is working exactly as it should. On the first PBX I have been able to connect to an external end point so authentication and registration works but no audio and yup all the RTP and UTP ports are accessible. External PBX’s can’t connect. The second PBX much the same, works and trunks to my first PBX and can call out through an established remote extenstion and has two way audio. However, the external unit can’t call in and yup we have a inbound route.
I don’t expect anyone to solve my issues just wondering if anyone has had a similiar experience using a VM version of FreePBX. I built both PBX’s from the ISO ver. 17. My next step is to build a bare metal PBX and see if the behaviours follows. My TCPdumps seem to rule out an ISP or Router blocking issue. Any thoughts would be greatly appreciated. This has been a long road
Yup checked those and my ISP address is there and the four Vlans are defined. I also did tcpdumps looking at the ISP to my router front door and the other side of the router towards my PBX and they are being passed. Yet to the ourside world it seems my listening PORT is BLOCKED. We even took an existing port that was “OPEN” to another IP address and swapped it to my PBX. It immediately became “BLOCKED” to any scans vs. “CLOSED/AVAILABLE” which means it could be availabe but is closed. My PBX’s work perfectly in-house including truncks. When someone attempts to connect a trunk to me, it fails “BLOCKED” . Yet the FW has the forward rule so something downstream of the router is no happy. Bill, do you run a VM server and if so would it happen to be ESXi?
No, I don’t run in ESXi. I commented because the Asterisk SIP settings are probably the number-one cause of one-way/no audio or broken SIP signaling and wanted to make sure you checked that as an early step.
You might want to disable the FreePBX firewall (Connectivity menu) as an additional step while you are troubleshooting, to be sure you’re not fighting against multiple firewalls.