Wowza Latest Version
Luciana
The sslLogProtocolInfo property instructs Wowza Streaming Engine to log SSL cipher and protocol information on startup. This information helps build a list of ciphers and protocols for the HostPort SSLConfig/CipherSuites and SSLConfig/Protocols filters in the virtual host.
After saving changes to the VHost.xml, restart the Wowza Streaming Engine & Manager services. Test with your player or client using a known Protocol and Version. If you do not know which protocol or version your client is using, please refer to the "Debug SSL connection filtering" section.
In the event, a client/player request is allowed/rejected by Wowza Streaming Engine on the basis of TLS versioning, the sslLogConnectionInfo property can be used to debug SSL connection filtering by instructing Wowza Streaming Engine to log SSL connection information (protocol, cipher suite, and provider) for each SSL/HTTPS connection.
Knowing the TLS version used by the client, and cross-referencing it against the SSLInfo.ProtocolsEnabled and SSLInfo.ProtocolsSupported logging results, the client's TLS version can be allowed/blocked as needed.
The Wowza Video service naturally evolves over time as we improve thestreaming experience. As part of this evolution, we add new features aswell as remove functionality that becomes outdated. Our goal is toprovide a well-maintained REST API that delivers reliably. To do this,we actively manage the lifecycle of the Wowza Video REST API.
Our API lifecycle begins at the Beta stage, and 4 versions of ourREST API are available at any given time. To ensure a stable API andminimize disruption to your streaming solutions, we add new features andremove outdated functionality in the Beta version of the API.
We recommend that you migrate to the new Current version of the RESTAPI as it becomes available. This ensures you're using the mostup-to-date, stable version of the API. As a version cycles through thestages, it becomes increasingly outdated and when it reachesDeprecated, it may no longer function as expected.
While we strive to maintain backwards compatibility between versions ofthe API to simplify your migration, it's not always possible when we addsignificant new functionality or improve architectural features. Stayingcurrent with the REST API is an easier migration task than migratingfrom an API version several stages removed from the current version withmore cumulative changes.
We recommend that you use the current version of the API, always. Usethe Query for version status endpoint to automate notification whenthere's a new current version of the REST API available, then plan andexecute your migration to the new current version.
The sample response looks similar to this, but differs according tocurrent version status. Because current and supported APIs are the onlyones intended for production use, those are the only statuses returnedin the response.
We'll soon be replacing the existing IP addresses for Wowza CDN on Fastly stream targets. While the change hasn't gone into effect yet, if you stream directly to Wowza CDN from Wowza Streaming Engine, you should add these IP addresses to your firewall rules so your integration continues to work seamlessly when the change occurs. When we've completed the transition to these new IP addresses, you should remove the old addresses from your rules. We'll add information to these release notes when the transition is complete so you know when to remove the old addresses.
We've enabled functionality that lets you switch between the legacy version of the Wowza Video UI and the new version. See Switch between Wowza Video Legacy and the new Wowza Video user experience for more information.
We've added origin_id, a query parameter to the GET /videos endpoint which returns all the videos originated from a live stream or real-time stream associated with that ID. origin_id is returned in the response of the GET /videos/id endpoint.
We've added response caching to the following endpoints to reduce bandwidth, latency, and the load on servers. If the time range queried is less than 60 minutes, the response cache time is 10 seconds. If the time range queried is 60 minutes or greater, the response cache time is 60 seconds. In the API reference, we've updated the description of each of the following endpoints with the new response cache times. For example, see the description of the GET /analytics/viewers/live_streams/id endpoint.
We've updated the user experience in Wowza Video to take advantage of Wowza Video's versatile live streaming functionality and Flowplayer OVP's superior player, video content management system, ad insertion technology, video playlist curation, and player analytics. For more information about these enhancements, see About Wowza Video.
Use this to set a unique ID returned in object_data of real-time streams webhook payloads. This is useful if you have an ID in your system or application you want to associate with real-time stream events.
Historically, the Wowza Video REST API has had designations for Supported 1 and Supported 2 versions. Beginning in October 2023, we'll begin the process of moving to only a single supported version. Once the existing API versions complete their lifecycle, we'll no longer maintain more than one supported version.
We are also no longer re-routing the endpoints of the Deprecated API version to the Supported 2 version. This preserves the deprecated API version functionality without the introduction of compatibility issues due to re-routing.
As previously communicated, we have now replaced the older IP addresses for Wowza CDN on Fastly stream targets. If you stream directy to Wowza CDN from Wowza Streaming Engine, you should remove any of these old IP addresses from your firewall rules:
We've published developer.wowza.com! Soon to be your one-stop sitefor all things Wowza integration. During this first iteration, we'veadded Wowza Flowplayer developer documentation and the Wowza Video RESTAPI reference to the developer portal. We'll continue to add developerdocumentation for all of our products, as well as development tools,resources, support, and so much more!
With Wowza Streaming Engine 4.8.18, we've updated to OpenJDK Java SE JRE 11.0.2. Wowza Streaming Engine 4.8.18 requires Java 11 at a minimum, but can be used with Java versions 11 - 12. For more information about this update, refer to the Wowza Streaming Engine 4.8.18 installation and update considerations and breaking changes.
6. See if the services are running. If you're running Wowza Streaming Engine as a service and it won't start, the installer might have misidentified the init system for your operating system. Use one of the following commands to change the init system between sysvinit/upstart and systemd:
The player object was added in beta 1.12, but, removed to support 2.0 functionality. Most customers will only notice the addition of logo_image, logo_position, video_poster_image, and width in the real_time_stream object since 1.12 is a beta and not meant for use in production environments.
In v2.0 of the API, we added new endpoints for our new video content management system, /videos. These endpoints will replace /assets, /recordings, and /vod_streams from v1.11 of the API. We also added additional video management functionality with /categories.
This topic covers REST API changes that occurred between the release ofversion 1.10 and version 1.11. If you are upgrading from a versionearlier than version 1.10, also review all other API changes that applyto your migration:
Wowza Streaming Engine is a robust, customizable, and scalable media server software that powers reliable streaming of high-quality video and audio to any device, anywhere. Wowza Streaming Engine 4.8.20 contains several enhancements and fixes that help to improve the functionality of the media server software.
If you are updating to Wowza Streaming Engine 4.8.20 from a base installation of Wowza Streaming Engine 4.8.17 or earlier, before you update, you need to install a supported version of Java, such as Java 11-12 or the OpenJDK Java SE JRE 11.0.2 installed with Wowza Streaming Engine 4.8.18 (available from the Downloads tab of My Account). Then instruct Wowza Streaming Engine to use that version of Java according to the instructions in Manually install and troubleshoot Java on Wowza Streaming Engine.
When using the Wowza Streaming Engine 4.8.18 installer to install a new instance of Wowza Streaming Engine on Windows, you may need to install additional dependencies in order to ingest SRT MediaCaster streams or use the generic SRT stream targets destination to publish an SRT stream. To address this, install the latest version of the Microsoft Visual C++ Redistributable for Visual Studio appropriate to your operating system.
You can now start a trial in your My Account portal if you already have a Wowza paid subscription or free trial. If you're an org owner, under the Products tab in My Account, click Start free trial to be taken to a screen to complete information and start your trial. You can access:
We'll be replacing the existing IP addresses for Wowza CDN on Fastly stream targets. While the change hasn't gone into effect yet, if you stream directly to Wowza CDN from Wowza Streaming Engine, you should add these IP addresses to your firewall rules, so your integration continues to work seamlessly when the change occurs. When we've completed the transition to these new IP addresses, you should remove the old addresses from your rules. We'll add information to these release notes when the transition is complete, so you know when to remove the old addresses.
The feature set for the Wowza Video service naturally evolves over time,and sometimes a feature may need to be updated or removed from the RESTAPI. We also provide performance improvements in newer API versions toincrease efficiency. Deprecation and sunsetting may involve individualparameters, endpoints, or an entire version of the API. We provide adeprecation policy andschedule so ourusers can plan migration to newer functionality and versions as they areavailable. Our goal is to improve the streaming experience withoutdisrupting applications that depend on the Wowza Video REST API.
c80f0f1006