Toggle sidebar Toggle sidebar

Can't see or hear participants in WebConference

Status
Not open for further replies.

TTBruce

Customer
Joined
Dec 16, 2019
Messages
15
Reaction score
1
TTBruce said:
I am experiencing the exact same issue as the user in this thread: https://www.3cx.com/community/threads/cant-see-or-hear-participants-in-webconference.63538/

That thread is closed so I can't post there, but everything about that post is exactly what is happening to me. No users are able to receive audio/video of participants, but they can see their own webcam. Am able to connect to non-3cx WebRTC meetings...
Click to expand...
Where is the 3CX server hosted?

How are the phones provisioned? (STUN, SBC, Local, VPN)

Does the firewall checker passes?
 
I was the poster of the original problem from a year ago - despite numerous upgrades the original problem still exists..
 
Where is the 3CX server hosted?
Amazon AWS

How are the phones provisioned? (STUN, SBC, Local, VPN)
SBC

Does the firewall checker passes?
Yes

I just realized that this works from outside of our network. Maybe I'm missing something with the firewall setup on the client side?
 
  • Like
Reactions: Evolute IT
TTBruce said:
Where is the 3CX server hosted?
Amazon AWS

How are the phones provisioned? (STUN, SBC, Local, VPN)
SBC

Does the firewall checker passes?
Yes

I just realized that this works from outside of our network. Maybe I'm missing something with the firewall setup on the client side?
Click to expand...
Check your DNS and check that you don't have outgoing block rules. See here for all ports used (in and out) : https://www.3cx.com/docs/manual/firewall-router-configuration/
 
Frederick Marcoux said:
Check your DNS and check that you don't have outgoing block rules. See here for all ports used (in and out) : https://www.3cx.com/docs/manual/firewall-router-configuration/
Click to expand...

Thanks for the suggestion. I've gone through this list again and again with no luck. I've monitored blocked traffic and created temporary rules to pass all traffic. If I monitor packets, I can see traffic on port 443 that does not appear to be blocked. Here's the packets I see when I try a call between two local PCs with IPs 192.168.1.222 and 192.168.1.69:

16:51:56.413938 IP <IP1>.80 > 192.168.1.222.53480: tcp 0
16:51:56.414454 IP <IP1>.80 > 192.168.1.222.53480: tcp 278
16:51:56.434983 IP 192.168.1.69.1305 > 192.168.1.1.443: tcp 0
16:51:56.437558 IP 192.168.1.222.61716 > <IP4>.48004: UDP, length 155
16:51:56.460980 IP 192.168.1.222.53480 > <IP1>.80: tcp 0
16:51:56.461100 IP 192.168.1.222.53481 > <IP3>.80: tcp 0
16:51:56.466865 IP <IP3>.80 > 192.168.1.222.53481: tcp 0
16:51:56.468768 IP 192.168.1.222.53481 > <IP3>.80: tcp 0
16:51:56.468978 IP 192.168.1.222.53481 > <IP3>.80: tcp 298
16:51:56.475207 IP <IP3>.80 > 192.168.1.222.53481: tcp 0
16:51:56.475687 IP <IP3>.80 > 192.168.1.222.53481: tcp 447
16:51:56.481030 IP 192.168.1.222.53480 > <IP1>.80: tcp 287
16:51:56.515696 IP 192.168.1.69.1305 > 192.168.1.1.443: tcp 83
16:51:56.515731 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 0
16:51:56.517298 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 1310
16:51:56.517327 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 1310
16:51:56.517336 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 1310
16:51:56.517343 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 1310
16:51:56.517353 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 1310
16:51:56.518759 IP 192.168.1.69.1305 > 192.168.1.1.443: tcp 0
16:51:56.518798 IP 192.168.1.1.443 > 192.168.1.69.1305: tcp 543
16:51:56.518802 IP 192.168.1.69.1305 > 192.168.1.1.443: tcp 0
16:51:56.519674 IP 192.168.1.69.1305 > 192.168.1.1.443: tcp 0
16:51:56.521630 IP 192.168.1.222.53481 > <IP3>.80: tcp 0
16:51:56.545123 IP <IP1>.80 > 192.168.1.222.53480: tcp 278
16:51:56.552870 IP 192.168.1.222.53481 > <IP3>.80: tcp 301
16:51:56.560523 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560537 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560550 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560562 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560575 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560587 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560598 IP <IP3>.80 > 192.168.1.222.53481: tcp 1310
16:51:56.560610 IP <IP3>.80 > 192.168.1.222.53481: tcp 1064
16:51:56.563346 IP 192.168.1.222.53481 > <IP3>.80: tcp 0
16:51:56.593622 IP 192.168.1.222.53480 > <IP1>.80: tcp 0
16:51:56.636404 IP 192.168.1.222.53481 > <IP3>.80: tcp 0
16:51:56.636612 IP 192.168.1.222.53480 > <IP1>.80: tcp 0
16:51:56.642950 IP <IP3>.80 > 192.168.1.222.53481: tcp 0
16:51:56.644718 IP 192.168.1.222.53481 > <IP3>.80: tcp 0
16:51:56.679791 IP 192.168.1.222.53404 > <IP4>.443: tcp 236
16:51:56.685958 IP 192.168.1.222.53389 > 64.4.54.18.443: tcp 0
16:51:56.698943 IP <IP1>.80 > 192.168.1.222.53480: tcp 0
16:51:56.700738 IP 192.168.1.222.53480 > <IP1>.80: tcp 0
16:51:56.718821 IP <IP4>.443 > 192.168.1.222.53404: tcp 0
16:51:56.718833 IP <IP4>.443 > 192.168.1.222.53404: tcp 864
16:51:56.728029 IP 64.4.54.18.443 > 192.168.1.222.53389: tcp 0
16:51:56.729946 IP 192.168.1.222.53389 > 64.4.54.18.443: tcp 0
16:51:56.761286 IP 192.168.1.222.53404 > <IP4>.443: tcp 0
16:51:56.768752 IP 192.168.1.69.137 > 192.168.1.255.137: UDP, length 50
16:51:56.889176 IP 192.168.1.222.61716 > <IP4>.48004: UDP, length 100
16:51:56.926392 IP <IP4>.48004 > 192.168.1.222.61716: UDP, length 88
16:51:56.926404 IP <IP4>.48004 > 192.168.1.222.61716: UDP, length 120
16:51:56.927850 IP 192.168.1.222.61716 > <IP4>.48004: UDP, length 64
16:51:57.062360 IP 192.168.1.69.54496 > <IP4>.48001: UDP, length 100
16:51:57.098997 IP <IP4>.48001 > 192.168.1.69.54496: UDP, length 88
16:51:57.099009 IP <IP4>.48001 > 192.168.1.69.54496: UDP, length 120
16:51:57.100221 IP 192.168.1.69.54496 > <IP4>.48001: UDP, length 64
16:51:57.128930 IP 192.168.1.222.61716 > <IP4>.48004: UDP, length 155
16:51:57.166582 IP <IP4>.48004 > 192.168.1.222.61716: UDP, length 95
16:51:57.166617 IP <IP4>.48004 > 192.168.1.222.61716: UDP, length 631
16:51:57.258713 IP 192.168.1.222.53402 > <IP1>.80: tcp 181
16:51:57.321989 IP <IP1>.80 > 192.168.1.222.53402: tcp 279
16:51:57.324916 IP 192.168.1.222.53403 > <IP3>.80: tcp 195
16:51:57.333307 IP <IP3>.80 > 192.168.1.222.53403: tcp 392
16:51:57.340113 IP 192.168.1.222.53402 > <IP1>.80: tcp 181
16:51:57.364343 IP 192.168.1.69.1307 > <IP4>.443: tcp 236
16:51:57.379364 IP 192.168.1.222.53403 > <IP3>.80: tcp 0
16:51:57.402125 IP <IP4>.443 > 192.168.1.69.1307: tcp 864
16:51:57.403924 IP <IP1>.80 > 192.168.1.222.53402: tcp 279
16:51:57.406962 IP 192.168.1.222.53403 > <IP3>.80: tcp 195
16:51:57.413093 IP <IP3>.80 > 192.168.1.222.53403: tcp 392
16:51:57.444290 IP 192.168.1.69.1307 > <IP4>.443: tcp 0
16:51:57.447440 IP 192.168.1.222.53402 > <IP1>.80: tcp 0
16:51:57.458866 IP 192.168.1.222.53403 > <IP3>.80: tcp 0
16:51:57.471846 IP 192.168.1.222.53482 > <IP2>.443: tcp 0
16:51:57.515484 IP <IP2>.443 > 192.168.1.222.53482: tcp 0
16:51:57.517475 IP 192.168.1.222.53482 > <IP2>.443: tcp 0
16:51:57.518159 IP 192.168.1.222.53482 > <IP2>.443: tcp 217
16:51:57.519191 IP 192.168.1.69.137 > 192.168.1.255.137: UDP, length 50
16:51:57.562639 IP <IP2>.443 > 192.168.1.222.53482: tcp 0
16:51:57.562767 IP <IP2>.443 > 192.168.1.222.53482: tcp 1310
16:51:57.562781 IP <IP2>.443 > 192.168.1.222.53482: tcp 1310
16:51:57.562899 IP <IP2>.443 > 192.168.1.222.53482: tcp 1310
16:51:57.562912 IP <IP2>.443 > 192.168.1.222.53482: tcp 166
16:51:57.565730 IP 192.168.1.222.53482 > <IP2>.443: tcp 0
16:51:57.606805 IP <IP2>.443 > 192.168.1.222.53482: tcp 1310
16:51:57.606820 IP <IP2>.443 > 192.168.1.222.53482: tcp 837
16:51:57.608823 IP 192.168.1.222.53482 > <IP2>.443: tcp 0
16:51:57.611339 IP 192.168.1.222.53482 > <IP2>.443: tcp 126
16:51:57.653194 IP <IP2>.443 > 192.168.1.222.53482: tcp 274
16:51:57.656390 IP 192.168.1.222.53482 > <IP2>.443: tcp 558
16:51:57.697806 IP <IP2>.443 > 192.168.1.222.53482: tcp 669
16:51:57.701908 IP 192.168.1.222.53482 > <IP2>.443: tcp 0
16:51:57.718083 IP 192.168.1.222.53483 > <IP1>.80: tcp 0
16:51:57.743059 IP <IP2>.443 > 192.168.1.222.53482: tcp 31
16:51:57.743072 IP <IP2>.443 > 192.168.1.222.53482: tcp 0
16:51:57.745010 IP 192.168.1.222.53482 > <IP2>.443: tcp 0
16:51:57.781002 IP <IP1>.80 > 192.168.1.222.53483: tcp 0
16:51:57.782999 IP 192.168.1.222.53483 > <IP1>.80: tcp 0
 
In my case the server is local and I see very similar traffic (or lack thereof) between local participants. If I use WebRTC from another server such as https://www.webrtc-experiment.com/video-conferencing it works fine. The firewall test passes without failures, but if I test port 443 through canyouseeme.org, it says that connections are refused. However, the firewall (pfsense) shows that requests to port 443 are sent to the PBX server. (which is apparently refusing the connection) This was a problem I reported a year ago, and despite promises that it would be fixed in a near-term release, the only response I received was the closing of the ticket without any resolution being provided. I'd really like to get webconferencing working as the rest of 3CX works flawlessly.
 
Here is a capture between the 3CX webmeeting server (158.69.227.118) and two local participants. It appears that data is flowing back and forth from the local pcs to the server, but no audio or video shows up on the local PCs.

1 0.000000 192.168.30.91 158.69.227.118 STUN 142 Binding Request user: 3438303131:pcHJ

2 0.058884 158.69.227.118 192.168.30.91 STUN 130 Binding Success
Response XOR-MAPPED-ADDRESS: aaa.bbb.ccc.ddd:30282

3 0.059794 158.69.227.118 192.168.30.91 STUN 162 Binding Request
user: pcHJ:3438303131

4 0.060114 192.168.30.91 158.69.227.118 STUN 106 Binding Success
Response XOR-MAPPED-ADDRESS: 158.69.227.118:48011

5 0.929012 192.168.30.125 158.69.227.118 TLSv1.2 302 Application Data

6 0.987202 158.69.227.118 192.168.30.125 TLSv1.2 928 Application Data

7 0.987541 192.168.30.125 158.69.227.118 TCP 66 60130 → 443 [ACK]
Seq=237 Ack=863 Win=1444 Len=0 TSval=1273452778 TSecr=3528423036

8 1.342837 192.168.30.91 158.69.227.118 TLSv1.2 302 Application Data

9 1.412082 158.69.227.118 192.168.30.91 TLSv1.2 930 Application Data

10 1.412253 192.168.30.91 158.69.227.118 TCP 66 51608 → 443 [ACK]
Seq=237 Ack=865 Win=501 Len=0 TSval=1163840983 TSecr=3528423142

11 1.737517 192.168.30.125 158.69.227.118 STUN 142 Binding Request
user: 3438303139:2OTQ

12 1.798920 158.69.227.118 192.168.30.125 STUN 130 Binding Success
Response XOR-MAPPED-ADDRESS: aaa.bbb.ccc.ddd:31594

13 1.803803 158.69.227.118 192.168.30.125 STUN 162 Binding Request
user: 2OTQ:3438303139

14 1.804910 192.168.30.125 158.69.227.118 STUN 106 Binding Success
Response XOR-MAPPED-ADDRESS: 158.69.227.118:48019

15 2.500269 192.168.30.91 158.69.227.118 STUN 142 Binding Request
user: 3438303131:pcHJ

16 2.589901 158.69.227.118 192.168.30.91 STUN 130 Binding Success
Response XOR-MAPPED-ADDRESS: aaa.bbb.ccc.ddd:30282

17 2.590891 158.69.227.118 192.168.30.91 STUN 162 Binding Request
user: pcHJ:3438303131

18 2.591172 192.168.30.91 158.69.227.118 STUN 106 Binding Success
Response XOR-MAPPED-ADDRESS: 158.69.227.118:48011

19 2.924409 192.168.30.125 158.69.227.118 TLSv1.2 302 Application Data

20 3.012219 158.69.227.118 192.168.30.125 TLSv1.2 928 Application Data

21 3.012549 192.168.30.125 158.69.227.118 TCP 66 60130 → 443 [ACK]
Seq=473 Ack=1725 Win=1444 Len=0 TSval=1273453285 TSecr=3528423539

22 3.343195 192.168.30.91 158.69.227.118 TLSv1.2 302 Application Data

23 3.409166 158.69.227.118 192.168.30.91 TLSv1.2 930 Application Data

24 3.409347 192.168.30.91 158.69.227.118 TCP 66 51608 → 443 [ACK]
Seq=473 Ack=1729 Win=501 Len=0 TSval=1163842980 TSecr=3528423640

25 4.238075 192.168.30.125 158.69.227.118 STUN 142 Binding Request
user: 3438303139:2OTQ

26 4.362147 158.69.227.118 192.168.30.125 STUN 130 Binding Success
Response XOR-MAPPED-ADDRESS: aaa.bbb.ccc.ddd:31594

27 4.362161 158.69.227.118 192.168.30.125 STUN 162 Binding Request
user: 2OTQ:3438303139

28 4.363593 192.168.30.125 158.69.227.118 STUN 106 Binding Success
Response XOR-MAPPED-ADDRESS: 158.69.227.118:48019
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,973
Messages
590,078
Members
164,896
Latest member
sameage
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom