Solved No audio for dial-in users (no audio between 3CX server and Webmeeting server)

Status
Not open for further replies.

completeware

Forum User
Basic Certified
Joined
Jan 11, 2011
Messages
13
Reaction score
3
We have had the webmeeting and dial in function in use for a while, but the other day I got notified that the dial in audio was not working. There is audio between all dial-in users (on the 3CX server) but no audio is sent between the 3CX and Webmeeting server and hence no online participants are able to hear the dial-in users.

I thought it might be a problem with the firewall on the the 3CX, but nothing has changed. Never the less, I tried to disable the firewall completely, and I still get a "Full Cone Test failed" for all media ports between 10600-10999. Ports 9000-9398 does not fail.

With the firewall enabled I have configured full access from the 3CX to the web, and inbound is allowed for 5060, 5090, 9000-10999 as well as http and https.

Running the firewall test, with the firewall enabled gives a failure on port 5060 (Full Cone Test Failed), but thats due to only traffic from our SIP provider is allowed on that port.

The server is a 3CX Express setup, running on a OVH VPS, with the OVH control panel firewall disabled, and directly connected to the internet with a public IP address. We use IPtables / Firehol as firewall configuration. and the firehol config is this:

interface4 any world
client all accept
server https accept
server http accept
server ssh accept
server sip accept src $unitel
server custom if1_1 tcp/5090 any accept
server custom if1_2 udp/5090 any accept
server custom if1_3 udp/9000:10999 any accept


I do believe the problem is somewhere in the communication between the 3CX Server and the webmeeting servers, but I'm stuck in how to troubleshoot it further.

Does anybody have suggestions to what I might have missed? Thank you
 
Just for the interest of anybody else having same issue and using OVH, I found the issue.

It seems like because it was an old setup on OVH, the setup and usage of OpenStack had changed, and I needed to go to OVH Horizion (OpenStack) and edit the firewall rules there as well.

So in total there was 3 "firewalls" or Network security settings in use; IPtable on the Debian instance, the network firewall rules on the instance in OVH control panel and the security groups in OVH Horizon.

With all them aligned to allow port 9000-10999 webmeeting sound is working flawless again :)
 
  • Like
Reactions: JohnS_3CX
Glad to hear it was resolved!
 
Status
Not open for further replies.

Forum statistics

Threads
111,973
Messages
590,076
Members
164,895
Latest member
jasonkkrause