![]() Look for low-level diagnostic messages about SSL failures, and double-check that you’re using SNI in the handshake. If the URL and port are correct, your SSL library might not be handling the certificate correctly. Confirm that you’re connecting to port 443. If the URL looks correct but you still get an SSL error, you might be connecting to the wrong port. Make sure that the server name you use has “rtmps” in it - note the “s”. If you attempt to create an SSL connection but get an invalid certificate, then you are probably connecting to a YouTube server that expects RTMP. An initialized SSL connection has the same API as a standard TCP connection, and so the RTMP library should be able to work with both of them identically. Once the SSL connection is established, use it as the connection for your RTMP client library. So make sure you add the SNI extension (Server Name Indication) to your SSL handshake, and set the server name to the server hostname you’re connecting to. Since TLS works only with the transport layer, the server hostname is not strictly required to initiate the connection however, it is required for authentication with our servers. ![]() Use your preferred socket library to create an SSL/TLS connection to port 443 at the server that the ingestion URL specifies. If you support dual ingestion, the backup address is. In the response, the field specifies the RTMPS URL. Send a LiveStreams insert (POST) request to create a new ingestion stream. If your encoder already uses the YouTube Live API, then the process for getting an RTMPS ingestion URL is similar to the one for RTMP. The multimedia stream must be sent with RTMPS that is, using RTMP over an SSL connection.The connection must be made to port 443 on the ingestion server.The path must be a valid YouTube Live RTMP application name.The server must be a valid YouTube RTMPS ingestion endpoint. ![]() Each part of the connection URL ( :///) must be correct:.Sending RTMPS to YouTube Live has a few prerequisites: See the Ingestion Protocol Comparison for an overview of the different ingestion protocols that YouTube Live Streaming supports. RTMPS is a good choice for most ordinary user content, especially if it requires low latency. This document is intended for encoder vendors who want to add support for RTMPS to encoders that already support RTMP. RTMPS is a regular RTMP (RealTime Messaging Protocol) video stream tunneled through an SSL connection. This document explains how to use RTMPS to stream live data on YouTube from an encoder. Delivering Live YouTube Content via RTMPS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |