Dial-In Audio Issues

Status
Not open for further replies.

Fabian Zimbalev

Forum User
Joined
Jun 19, 2019
Messages
12
Reaction score
0
Hi,

we´re testing the scheduled Webmeeting and we´re able to dial-in as well as connect with the browser but I can´t hear people that dial in.
I then found this forum entry: https://www.3cx.com/community/threa...tc-users-and-dial-in-users.66474/#post-285859
The Parameter that was set there is "1" for our Phone-System so changing that won´t help.
Any other ideas about what might be the issue ?

Also, I saw that port 443 has to be opened to the network that will host the Webmeeting ?
I got the Video-Stream so I guess that´s fine ?

Best regards,
Fabian Zimbalev
 
Little Update:
We created an any-rule for inbound and outbound communication onto the 3cx Server to make sure we don´t have any NAT issues. Voice from VoiP to the webmeeting still does not work, both ways.
Is there anyone who has an Idea about what could be the issue ?
I also contacted another 3cx partner and we compared our bridges and everything we could find regarding conference calls and it all looked the same.

Best regards,
Fabian Zimbalev
 
Hi Fabian,



The video stream is separate. The PBX needs to be able to reach the 3CX MCU servers to send the audio of the dial-in members and merge it to the online meeting.

If this is not possible, the dial-in members will hear each other as soon as there is more than one person in the dial-in session, but they will never merge with the rest of the group.

You will need your HTTPS port open (usually 5001 unless you changed it during setup) and your audio ports open (firewall checker should tell you that) https://www.3cx.com/docs/ports/

What version is your PBX and where is it hosted?
 
Hi John,

it´s version 16.0.2.910 and it´s running on a virtual machine on our servers so it´s not hosted anywhere.
Port 5001 is open and I can access the Management console from outside our company so I guess there´s no issue with 5001.
We have all the RTP ports open and the firewall checker is green, the only two ports that are not open but listed on the site you send are 443 (It sais that it doesn´t have to be opened to the 3cx ?) and 5061 aka Secure-Sip. Also, we already allowed any port inbound for a few minutes to test if we have firewall issues, that did not fix the issue so we don´t think that´s where the issue is.

Any further ideas ?

Best regards,
Fabian
 
I would suggest to open 443 and retest if possible, the PBX will need it for the Webmeeting Bridge which reaches the 3CX MCU
 
  • Like
Reactions: Evolute IT
Port 443 is now open but it is not being listened on. I tested it anyways and it didn´t change anything for the webmeeting.
I then created a vhost confg for ngnix adding 443 to make sure that it´s reachable from outside and I can open up my configured page so 443 is definately open but it does not solve the issue.

Best regards,
Fabian
 
Hi Fabian,

In order to assist you further, please do the following:

  1. Schedule a conference (not quick-meeting, as those do not support dial in)
  2. Enter the meeting to start
  3. Have someone dial in, can be from their deskphone by calling 700 and entering the conf. ID
  4. You should see the dial in user appear in the list of attendees shortly
  5. They will stop hearing music on hold and they will connect to the meeting

Did you see them appear in the list? Was there audio in this case?

If not then please send me a PM with the meeting URL
 
Hi John,

done and this is the result:
I see a person joining in the list and I get audio confirmation (a short tone). If he joins using the webclient, he can hear me as long as I use the webclient as well. If one uses the phone and the other one the webclient, we cannot hear each other. If both use the phone, we can hear us.

I´ll send you my webmeeting-url in a pm.

Best regards,
Fabian
 
Hi Fabian,

Is it possible that the server IP is blocked on your network?

If you log on to your PBX machine can you reach the IP of the MCU if you FTP it for example?

It will not allow you to log in but you can at least see if it connects, meaning it's reachable
 
Hi John,

the Server we use (aa002-fra.3cx.net) resolves to 3.122.15.121 for me.
The FTP port does not seem to be opened, as well as the ssh port. Anyways, 443 is open and I can telnet onto it but it does not server a website, I guess that´s intended.
Connection seems to be fine, can you confirm that FTP port is open there ?

Best regards,
Fabian
 
If you can telnet to 443 (as opposed to being unreachable) when connecting from your PBX machine then it should be reachable and the dial in members should merge with the main webmeeting.

Now the question is whether the server can reach you back
 
I´ll send you our hostname via PM with the ports that should definately be reachable.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

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