[Progic] General Guide to Live Streaming / Live Broadcasts
In this article, you will learn the key concepts of live streaming, what RTMP is, and which validations should be performed before starting a live broadcast through Progic.
- How Live Streaming Works
- How to Configure the Streaming Tool
- What is RTMP?
- Pre-Live Validation Checklist
- Network Requirements
- Testing Before the Event
- Live Stream Checklist
- When to Involve the IT Team
- Best Practices
Live streams can originate from different platforms, such as Microsoft Teams, Google Meet, Zoom, or OBS Studio. Therefore, before the official event, it is important to perform tests and validate permissions, configurations, and network requirements.
How Live Streaming Works
A live stream is a real-time video broadcast over the internet.
In simple terms, it works in three stages:
Source Platform → Streaming Server → Players or End Audience
The source platform is the system used to start the broadcast. Some examples include:
- Microsoft Teams
- Google Meet
- Zoom
- OBS Studio
- Other tools that support RTMP streaming
The streaming server receives the video sent by the source platform and makes the content available for playback on Players or another configured destination.
See also the setup guides for each platform:
What Is RTMP?
RTMP is the protocol used to send live video from a streaming platform to a server.
In simple terms, RTMP can be understood as the technical path used to deliver the live stream.
When configuring an RTMP stream, two pieces of information are usually required:
- RTMP URL: the address of the server that will receive the stream.
- Stream Key: a code that identifies the live stream being broadcast.
These details must be entered into the platform used for broadcasting, such as Teams, Meet, Zoom, or OBS Studio.
Example:
RTMP URL + Stream Key = Live Stream Destination
If either the URL or the key is entered incorrectly, the stream may not reach its intended destination.
Before You Start
Before scheduling a live stream, make sure the selected platform supports RTMP streaming and that the account being used has permission to access this feature.
Some platforms may require:
- Prior approval from an administrator
- A specific subscription plan
- Internal permission configuration
- Live streaming feature activation
- Manual setup of the RTMP URL and Stream Key
Important:
Progic provides the tools required to configure and display the live stream. However, permissions, network restrictions, and third-party platform configurations depend on the customer's environment.
Required Validations Before a Live Stream
Before the official event, it is important to validate the items below.
Source Platform
Define which platform will be used to start the broadcast.
Examples:
- Teams
- Meet
- Zoom
- OBS Studio
After selecting the platform, confirm that it supports streaming to an external RTMP server.
Account Permissions
Verify that the account used for the live stream has permission to use RTMP.
In some cases, this configuration depends on the platform administrator or the company's IT team.
Validate:
- Whether the account allows live streaming
- Whether external RTMP output is enabled
- Whether there are restrictions related to the subscribed plan
- Whether an administrator must enable the feature
RTMP URL and Stream Key Configuration
The source platform must be configured with the correct live stream information.
Carefully verify:
- Whether the RTMP URL was copied correctly
- Whether the Stream Key was entered in the correct field
- Whether there are any extra spaces before or after the information
- Whether the information belongs to the correct live stream
Network Requirements for Streaming
If the live stream will be broadcast from a computer, the network must allow outgoing RTMP traffic.
RTMP streams typically use port 1935.
This requirement should be validated with the customer's IT team.
Important:
If port 1935 is blocked on the network, the streaming platform may not be able to send the video to the live streaming server.
Player Access
The Players that will display the live stream must also be able to access the playback address.
For live streams hosted in the Progic environment, validate access to:
live.progic.com.br
If the live stream uses YouTube, validate that the Players can also access YouTube-related addresses.
Connection Quality
A live broadcast depends on a stable internet connection.
Before the event, validate:
- Whether the connection at the streaming location is stable
- Whether there is sufficient upload bandwidth
- If possible, use a wired connection
- Whether audio and video are transmitted correctly
- Whether there are no interruptions or fluctuations during testing
Why Test in Advance?
We strongly recommend testing the live stream before the official event.
Performing tests in advance helps identify issues such as:
- Missing permissions on the source platform
- Network restrictions
- Port 1935 not being available
- Incorrect RTMP URL configuration
- Incorrect Stream Key configuration
- Players without access to the streaming address
- Audio issues
- Video issues
- Connection instability
- Restrictions related to YouTube or the live streaming environment
Avoid configuring the live stream for the first time on the day before or on the day of the event. If any restrictions are identified, you may need to involve administrators, IT staff, or external providers.
Live Stream Checklist
Before starting the broadcast, confirm the following items:
- The source platform has been defined.
- The selected platform supports RTMP streaming.
- The account being used has permission to stream via RTMP.
- The RTMP URL has been configured correctly.
- The Stream Key has been configured correctly.
- The network allows outbound traffic through port 1935.
- The Players can access
live.progic.com.br. - If YouTube is being used, the Players can access YouTube.
- Audio has been tested.
- Video has been tested.
- The live stream has been tested before the official event.
- The IT team has been involved if necessary.
When to Involve the IT Team
The customer's IT team should be involved whenever permissions, restrictions, or network access need to be validated.
Contact the IT team in situations such as:
- Firewall restrictions
- Corporate proxy usage
- Opening port 1935
- Access restrictions to
live.progic.com.br - Access restrictions to YouTube
- Administrative permissions in Teams, Meet, or Zoom
- Internal security policies
- Player network configurations
When to Contact Progic Support
Progic Support can assist with guidance related to live stream configuration on the platform and playback on Players.
Contact Support if you need help with:
- Finding or using live stream information
- Understanding how to configure the live stream in the Progic environment
- Validating live stream playback on Players
- Accessing supporting documentation
- Confirming whether the platform configuration is correct
Some items, however, depend on the customer's environment, including:
- Permissions in third-party platforms
- Firewall rules
- Proxy configurations
- Network security policies
- Corporate account administration
- Internet access for computers and Players
Best Practices
To reduce risks during a live stream, we recommend:
- Planning the broadcast in advance
- Avoiding first-time setup on the day of the event
- Performing a complete test before the official date
- Using, whenever possible, the same network and equipment that will be used during the event
- Validating audio, video, and Player access
- Involving the IT team early in the planning process
- Having a contingency plan in case issues occur
- Keeping the source platform documentation readily available
Final Considerations
A successful live stream depends on a combination of factors, including the platform, source tool, permissions, network configuration, and playback devices.
Even when the Progic configuration is correct, external restrictions may prevent the stream from being sent or displayed properly.
For this reason, configure and test your live stream in advance. This is the best way to identify technical issues before the official event and reduce the risk of disruptions during the broadcast.