Set up WebRTC streaming with Wowza Streaming Engine

WebRTC is a free, open-source project that enables real-time communication of audio, video, and data in web browsers and mobile applications. Wowza Streaming Engine can ingest source WebRTC audio and video content and deliver it to WebRTC supporting players. It can also transmux or transcode WebRTC to other streaming protocols, including HLS, MPEG-DASH, RTMP, and RTSP. In addition, Wowza Streaming Engine can ingest a non-WebRTC source stream and play it back with WebRTC (or WebRTC plus other scalable HTTP-based streaming protocols like HLS). This article focuses on how to both publish and play a stream over WebRTC.

Note: Wowza Streaming Engine™ media server software version 4.7.7 and later supports WebRTC streaming, however, we recommend that you update to version 4.8.5 or later to capitalize on expanded functionality and enhancements to publisher reliability.

Video tutorial: Using WebRTC with Wowza Streaming Engine

See how to configure Wowza Streaming Engine to publish and play streams over WebRTC.

Before you start

You should complete the following tasks:

Create a live application according to Create applications.

Review the supported codecs, browsers, and workflows for publishing and playing WebRTC streams in About WebRTC workflows in Wowza Streaming Engine.
Obtain an SSL/TLS certificate and configure Wowza Streaming Engine to use it. We recommend using the free Wowza StreamLock certificate service according to Get SSL/TLS certificates from the Wowza Streaming Engine StreamLock service.
Note: If you plan to use your own SSL/TLS certificate instead, the following resources may help you convert your certificate to the Java KeyStore (JKS) format that's required by Wowza Streaming Engine. Although it's possible to use self-signed certificates with WebRTC, note that you must ensure the browser you're using to test accepts traffic encrypted with any self-signed certificates in use.
- Request an SSL certificate for Wowza Streaming Engine from a certificate authority
- Troubleshoot SSL certificate configuration for Wowza Streaming Engine

1. Configure SSL/TLS encryption for WebRTC

Encryption is required for all components of the WebRTC workflow. You must have a secure HTTP (HTTPS) connection to a web camera for WebRTC publishing and playback. As a result, due to cross-domain issues, you need to configure an SSL/TLS certificate to secure the connection between the browser and Wowza Streaming Engine for the SDP data exchange and enable WebRTC signaling for the SSL/TLS host port.

You must enable WebRTC signaling for the SSL/TLS host port you configured with your SSL/TLS certificate to support an SDP exchange for the WebRTC session.

The next two tabs describe how to enable WebRTC signaling using either Wowza Streaming Engine Manager or via XML. Select the method that works best for you by toggling the corresponding tab to view the steps.

Wowza Streaming Engine Manager

Click the Server tab, and then click Virtual Host Setup in the contents panel.
On the Virtual Host Setup page, click Edit.
Under Host Ports, locate the port you configured for SSL/TLS and click the edit icon.
Ensure that Use WebRTC is selected.
Click Apply and then click Save.
Restart the virtual host.

XML

Navigate to [install-dir]/conf/ and open VHost.xml in a text editor.
Locate the <HostPort> container for the port you configured for SSL/TLS and add the following <HTTPProvider> as the second-to-last entry in the <HTTPProviders> container element. The new HTTP provider must be the second-to-last provider in the section.
```
<HTTPProvider>
    <BaseClass>com.wowza.wms.webrtc.http.HTTPWebRTCExchangeSessionInfo</BaseClass>
    <RequestFilters>*webrtc-session.json</RequestFilters>
    <AuthenticationMethod>none</AuthenticationMethod>
</HTTPProvider>
```
Save your changes to VHost.xml.
Restart Wowza Streaming Engine.

Note: The 443 host port with SSL/TLS is commented out by default in VHost.xml. When you're ready to stream over WebRTC, comment it back in by removing the lines ,  from around the <HostPort> container.

2. Configure WebRTC publishing and playback

After enabling SSL/TLS for WebRTC streaming, you need to enable WebRTC publishing and playback for your live application. You can accomplish this task using either Wowza Streaming Engine or via XML. Select the method that works best for you by toggling the corresponding tab to view the steps.

Wowza Streaming Engine Manager

Click the Applications tab at the top of the page and then select your live application in the contents panel.
In the contents panel, click WebRTC.
On the Setup tab, click Edit to configure WebRTC.
Under WebRTC Enabled Features, select the appropriate settings:
1. Select Publish WebRTC to Wowza Streaming Engine to ingest WebRTC source streams to this application.
2. Select Play WebRTC from Wowza Streaming Engine to deliver WebRTC content for playback from this application.
3. Select Query published stream names to enable querying names of published WebRTC streams for this application.
Under ICE Candidate Setup, specify the network connections over which WebRTC communication can occur by clicking Add ICE Candidate and completing the following steps:
1. Select either UDP (recommended) or TCP as the ICE candidate transport protocol.
  Notes:
  - Firefox requires UDP. TCP is not supported.
  - If you use UDP ICE candidates, enabling NACK messages is recommended to allow for retransmission of lost packets. See the optional RTP properties in Configure custom WebRTC properties for information about how to enable NACK.
  - At this time, full session traversal utilities for NAT (STUN) negotiation aren't supported. Currently, Wowza Streaming Engine only supports traversal of symmetric NATs. A single STUN transport configuration (TCP or UDP) must be used. TURN servers are not supported at this time.
2. Change the IP address to the publicly-accessible Wowza Streaming Engine server IP address.
  
  Note: IPv6 addresses are not supported for WebRTC ICE candidates.
3. For TCP candidates, you must specify a port to use for WebRTC streaming. The default streaming port for Wowza Streaming Engine is 1935. For UDP candidates, the port is dynamically assigned.
  
  Note: Port 554 isn't supported for TCP ICE candidates. See WebRTC port configuration for more information about WebRTC ports.
4. Click OK to save your ICE Candidate.
5. If needed, add additional ICE Candidates, and adjust their preferred order using the Priority up and down arrows.
If you have Publish WebRTC to Wowza Streaming Engine enabled, specify one or more Publish Video Codecs in the preferred order of use:
1. Click Add Codec, and then select the codec from the drop down list.
2. If necessary, adjust the order of the video codecs using the Priority up and down arrows.
3. Click OK to save your Publish Video Codecs priority list.
Click Save and then restart the application.

XML

Open the Application.xml file for your live application ([install-dir]/conf/[application-name]) in a text editor.

In the <WebRTC> container element, configure the following properties:

Note: These instructions assume a new installation of Wowza Streaming Engine 4.7.7 or later. If you've updated from an earlier version, you must copy and paste the <WebRTC> container from the sample WebRTC Application.xml file into your Application.xml file.

Name	Type	Description
EnablePublish	Boolean	Set to true to enable WebRTC publishing to this application.
EnablePlay	Boolean	Set to true to enable WebRTC playback from this application.
EnableQuery	Boolean	Set to true to enable querying of published stream names for this application.
IceCandidateIpAddresses	String	The IP address, transport, and port to use for WebRTC streaming. For the user datagram protocol (UDP), the value should be [wowza-streaming-engine-external-ip-address],udp where [wowza-streaming-engine-external-ip-address] is the external IP address of the Wowza Streaming Engine instance. The port is dynamically assigned for UDP delivery. For Transmission Control Protocol (TCP), the value should be set to *[wowza-streaming-engine-external-ip-address],tcp,[port]* where *[wowza-streaming-engine-external-ip-address]* is the external IP address of the Wowza Streaming Engine instance and *[port]* is one of the non-SSL/TLS-protected streaming HostPort entries defined in *[install-dir]/conf/VHost.xml. For example, to stream over port 1935, the entry would be 66.175.168.127,tcp,1935. For multiple IP addresses, use a pipe character to separate the lists. Notes:* IPv6 addresses are not supported for WebRTC ICE candidates. Firefox requires UDP. TCP is not supported. Port 554 isn't supported for TCP ICE candidates. See WebRTC port configuration for more information about WebRTC ports. If you use UDP ICE candidates, enabling NACK messages is recommended to allow for retransmission of lost packets. See the optional RTP properties for information about how to enable NACK. At this time, full session traversal utilities for NAT (STUN) negotiation aren't supported. Currently, Wowza Streaming Engine only supports traversal of symmetric NATs. A single STUN transport configuration (TCP or UDP) must be supplied using IceCandidateIpAddresses. TURN servers are not supported at this time.
UDPBindAddress	String	The local IP address of the network card you want to use for WebRTC UDP traffic. (This value is not used if streaming WebRTC over TCP.) For UDP delivery in general, it's okay to leave this property blank. The property is only needed if the server has multiple network interfaces. For some network situations, like running on a cloud instance, a value of 0.0.0.0 would be best instead of the local IP address of the network card to prevent connection problems.
PreferredCodecsAudio	String	A comma-separated list of audio codecs, in order of preference, for stream ingestion. The default is opus,pcmu,pcma.
PreferredCodecsVideo	String	A comma-separated list of video codecs, in order of preference, for stream ingestion. The default is vp8,h264. Valid values are vp8, vp9, and h264. If you want to stream in Chrome using VP9, use vp9,vp8,h264. If no value is specified, the WebRTC stream will not be ingested.
DebugLog	Boolean	Set to true to enable WebRTC debug logging.

Save your changes and then restart Wowza Streaming Engine.

After setting up WebRTC publishing and playback, you can optionally configure custom WebRTC properties or configure transcoding if needed.

Note: We recommend disabling B-frames for WebRTC streams. With Wowza Streaming Engine 4.8.14 and later, the Transcoder adds B-frames by default. To disable B-frames, see Configure B-frame generation in Wowza Streaming Engine.

3. (Optional) Configure custom WebRTC properties

After enabling WebRTC publishing and playback for your live application, you can optionally configure additional WebRTC functionality around FIR and NACK messages, handling out-of-order and retransmitted packets, packet loss, SDP playback compatibility, and more.

Open the Application.xml file for your live application ([install-dir]/conf/[application-name]) in a text editor.

In the <WebRTC>/<Properties> container element, add any of the following custom properties, including the Name, Type, and Value. For example:

<Property>
	<Name>...</Name>
	<Value>...</Value>
	<Type>...</Type>
</Property>

Name	Type	Description
webrtcCodecUpdates	Boolean	Set to true to allow codec updates for WebRTC connections to pass through the system. The default value is true. Enabling this property can lead to frequent calls to the onCodecInfoVideo method of the IMediaStreamActionNotify3 interface, depending on the publishing client's source encoder. See Listen for stream events and codec information with the Wowza Streaming Engine Java API.
webrtcFIRMessageScheme	String	The scheme for the FIR message interval. Use time to send a FIR message after a specified period of time, or use frame to send a FIR message after a specified number of frames are received. The default is time. FIR messages, which are enabled by default, provide resiliency for packet loss while publishing WebRTC streams to Wowza Streaming Engine.
webrtcFIRMessageInterval	Integer	The interval between Full Intra Request (FIR) messages. If webrtcFIRMessageScheme is set to time, the value is in milliseconds and the default is 1000 (1 second). If webrtcFIRMessageScheme is set to frame, the value is in frames and the default is 30.
webrtcIdleTimeout	Integer	The length of time, in milliseconds, after which a WebRTC session closes if there is no publish or playback activity. The default and recommended value is 10000 (10 seconds).

In the <RTP>/<Properties> container element, add any of the following custom properties, including the Name, Type, and Value:

Name	Type	Description
rtpDePacketizerWrapper	String	Set to com.wowza.wms.rtp.depacketizer.JitterBuffer to enable a jitter buffer for WebRTC that allows handling out-of-order and retransmitted packets. The jitter buffer is recommended for UDP-based WebRTC streams and adds a delay to the stream. The jitter buffer must be enabled for useNack to work when useNack is enabled.
jitterBufferDelay	Integer	Configures the delay, in milliseconds, added by the jitter buffer. This delay allows for retransmitted packets and out-of-order packets to be played into the system in order, provided they are received in time. If useNack is true, the recommended jitter buffer delay is 2 times the round trip time (RTT) plus overhead for processing. If useNack is false, the recommended jitter buffer delay is 100. The default is 500.
useNack	Boolean	Set to true to send Negative Acknowledgement (NACK) messages to publishing clients to allow for retransmission of lost packets. This property is for WebRTC streams only. The default is false. Using NACK messages is recommended for UDP-based WebRTC streams and adds a delay to the stream. The jitter buffer must also be enabled for this property to work when enabled.
jitterBufferDebug	Boolean	Set to true to log information about out-of-order packets that are received and inserted in time. Logged information includes the length of time to recover a packet, which can help determine an appropriate value for jitterBufferDelay. The default is false.
logPacketLoss	Boolean	Set to true to log when packets are lost and not recovered at the time when they should have been played into the system. The default is false.
rtpForceH264Constraint	Boolean	Set to true to allow the SDP information that is returned to contain different H.264 constraints than the WebRTC stream contains. The default value is false.
rtpForceH264ConstraintValue	Integer	Sets the H.264 constraint fields in the WebRTC SDP information if rtpForceH264Constraint is true. The default value, 192, works in most circumstances. Other valid values are 128, 224, and 240.
rtpUseLowestH264Constraint	Boolean	Set to true to compare the initial codec data and the first video unit to the profile data and use the lowest value to determine the H.264 video profile in the WebRTC SDP information. Use this or rtpUseHighestH264Constraint to help play the stream when an encoder doesn't send consistent codec information for the stream.
rtpUseHighestH264Constraint	Boolean	Set to true to compare the initial codec data and the first video unit to the profile data and use the highest value to determine the H.264 profile in the WebRTC SDP information. Use this or rtpUseLowestH264Constraint to help play the stream when an encoder doesn't send consistent codec information for the stream. Note: The rtpUseLowestH264Constraint and rtpUseHighestH264Constraint properties can't be used simultaneously. If both are set to true, rtpUseHighestH264Constraint is used.

Save your changes and then restart Wowza Streaming Engine.

4. Test the WebRTC workflow

In production environments, WebRTC playback and publishing pages must be hosted on a web server utilizing SSL/TLS encryption. For testing and learning purposes, Wowza provides hosted WebRTC test pages for publish and playback so you can see WebRTC in action more quickly.

WebRTC test page requirements

Wowza Streaming Engine – version 4.8.5 or later

Browsers – latest version of Chrome, Firefox, Safari, and Microsoft Edge version 79 and later. There is a resolved known issue with publishing and playing WebRTC streams using Safari on iOS 15. See WebRTC publishing and playback fails with Safari on iOS 15 for updates.

Screen share – not supported on mobile devices, Safari, or Firefox

4a. Publish a test stream over WebRTC

To test publishing a WebRTC stream, you can publish a basic stream, a stream with two composited video inputs with different layouts, or a meeting stream that others can join.

Go to the hosted WebRTC publish test page. From the Publish page, you can publish a basic WebRTC stream.
- If you want to test compositing two video inputs for your stream, click Composite.
- If you want to test creating and sharing a meeting stream, click Meeting.
For Signaling URL, enter the secure WebSocket URL to connect to the Wowza Streaming Engine WebRTC sessions listener in the following format:
wss://[ssl-certificate-domain-name]:[SSL-port-number]/webrtc-session.json

where ssl-certificate-domain-name is the secure domain name for your Wowza Streaming Engine instance. If you are connecting WebRTC sessions using a port other than the default SSL/TLS port 443, you must include that non-standard port in the URL. If using Wowza StreamLock and the default SSL/TLS port (443), for example, the Signaling URL looks something like this: wss://5ab4321c0d123.streamlock.net/webrtc-session.json.
Enter an Application Name that matches the WebRTC live application you configured.
For Stream Name, enter a unique name for the stream.
Configure the remaining settings selections as needed and then click Publish or Join to publish a stream to Wowza Streaming Engine:
- Publish page – The frame rate and frame size settings constrain the camera and microphone input and aren't included in the SDP provided to Wowza Streaming Engine. The browser may adjust the frame rate to accommodate changes in network conditions.
  
  Note: After publishing, to share your screen, click the arrow next to the video camera icon, select Screen Share, and then select which content to share. To toggle back to video, click Stop sharing or select a different option under Input Camera.
- Composite page – To share your screen, under Video Input 1, select Screen Share, and then select which content to share. After selecting your video and audio sources, select a video layout for the test stream.
- Meeting page – When you are ready to publish, you will click Join. Then, to add additional participants, click Copy config () to copy the configuration settings and share them. Participants must specify a unique Stream Name before joining the meeting.

To test publishing from a different browser or with a different device, click Copy config () to copy the configuration settings and share them.

4b. Play a test stream over WebRTC

In a new browser tab, go to the hosted WebRTC play test page.
Enter the same Signaling URL, Application Name, and Stream Name that you entered on the Publish page.
Click Play.

To test playback in a different browser or with a different device, click Copy config () to copy the configuration settings and share them.

Tip: When you're ready to implement WebRTC for production, consider using the Wowza Flowplayer Real-Time Streaming (WebRTC) plugin for playback. You can purchase Wowza Flowplayer and use it with Wowza Streaming Engine for playback.

Note: To test playback over other protocols, enable other playback protocols for the application you configured for WebRTC by clicking the Setup tab for your application and enabling any of the protocols listed under Playback Types. Then, you can use the playback URL for the protocol you want to test with the player of your choice or the Video Test Players webpage.

Next steps

For more advanced WebRTC learning and testing, we provide WebRTC examples on GitHub that demonstrate how to publish and play WebRTC streams with Wowza Streaming Engine. For more information, see Use WebRTC example pages with Wowza Streaming Engine.

Set up WebRTC streaming with Wowza Streaming Engine

Want To Try Us Out?

Video tutorial: Using WebRTC with Wowza Streaming Engine

Before you start

1. Configure SSL/TLS encryption for WebRTC

Wowza Streaming Engine Manager

XML

2. Configure WebRTC publishing and playback

Wowza Streaming Engine Manager

XML

3. (Optional) Configure custom WebRTC properties

4. Test the WebRTC workflow

4a. Publish a test stream over WebRTC

4b. Play a test stream over WebRTC

Next steps

More resources

Popular Video Topics

Video Resources

Partners

Company

Stay Connected

Stay Up to Date with the Blog

Set up WebRTC streaming with Wowza Streaming Enginefunction sendEmail() {var title = 'Set up WebRTC streaming with Wowza Streaming Engine'.replace("'","\'").replace("&#039;", "\'");window.location = 'mailto:?subject=' + title + '&body=' + window.location;}

Want To Try Us Out?

Video tutorial: Using WebRTC with Wowza Streaming Engine

Before you start

1. Configure SSL/TLS encryption for WebRTC

Wowza Streaming Engine Manager

XML

2. Configure WebRTC publishing and playback

Wowza Streaming Engine Manager

XML

3. (Optional) Configure custom WebRTC properties

4. Test the WebRTC workflow

4a. Publish a test stream over WebRTC

4b. Play a test stream over WebRTC

Next steps

More resources

Popular Video Topics

Video Resources

Partners

Company

Stay Connected

Stay Up to Date with the Blog

Set up WebRTC streaming with Wowza Streaming Engine