When you enter the presenter console, webinar.net will ask you for your preference and permission to use your PC's Webcam and Microphone.
Having issues getting connected?
If the connection prompt keeps spinning after selecting, a firewall, VPN, or another security layer may hinder a successful connection to the webinar.
In such cases, could you consider enabling our TCP Tunneling feature? This can bypass any blocking issues and allow webinar.net to establish a connection with your equipment successfully.
We suggest limiting the number of presenters to 2-3 when using webcam or screen sharing. This helps maintain optimal performance and ensures a smooth webinar experience for all participants.
How to enable Webinar.net TCP Tunneling:
If you are having persistent issues that stay after troubleshooting steps or a reload.
Then your first stop should be the "Troubleshooting & Help" center found via the raft icon on the left-hand nav rail to enable TCP Tunneling:
Once the center has been opened, scroll down to find the "Turn on TCP Tunneling" button.
Should you find that your connection is still not successful after enabling the TCP Tunneling, it's recommended to remove the feature for others who may need to use it.
TCP Tunneling is only recommended when your network blocks UDP traffic. Because the tunnel will re-route the presenter's connection, it's possible for TCP Tunneling to reduce a presenter's overall streaming quality. It's best used with an audio-only connection, and to avoid any use of screen share while the feature is enabled for that presenter.
In-Depth Details & Technical Information:
Control Connection:
WebRTC requires HTTPS over port 443.
Stream Channels:
Separate audio and video channels in both directions.
UDP Ports:
Audio and video connections use high UDP ports.
Port Blocks:
High ports may be blocked on large enterprise networks.
Browser Bridge Setup:
Attendee's browser establishes a bridge session using HTTPS.
Network Paths:
The bridge and browser search for paths in and out of the webinar.net network.
TURN Server Functionality:
Browser authenticates over TCP 443.
Determines NAT info from the response.
Connects to transmit audio and video via TLS to TURN server on port 443.
TURN server handles UDP high ports for VPB.
Proxy/Firewall must support/allow initial unencrypted traffic over 443 to TURN.
TCP Tunneling can be utilized by a single presenter, allowing the other presenters to use higher UDP ports, providing low overhead and higher speeds. If a presenter has audio and/or video difficulties, they can select the Enable TCP Tunneling checkbox to switch to a TCP connection.
For further assistance, contact us through chat or send us an email at support@webinar.net.