Skip to main content

Streaming to Telegram Live Chat

Purpose 

StreamHub can be configured to output streams using the RTMP or RTMPS protocol for streaming to social media platforms such as Telegram Live Chat.

Prerequisites 

  • StreamHub license
  • IP Output license (AW-OR-OIP)
  • Firewall and network configured to allow RTMP output
  • Telegram account with Telegram application on iPhone or Telegram Desktop 

Note

A StreamHub Live Encoding license (AW-OR-ENC) may be required depending on the characteristics of the input stream from the transmitter/encoder.

Procedure

  1. Create a new Group Chat in Telegram.

    In the Desktop App: 



    On a mobile phone (iOS only): 



  2. Obtain the Server URL and Stream Key from Telegram. 

    In the Desktop App: 



    On a mobile phone (iOS only):



  3. In a separate browser tab, access your StreamHub server.
  4. To create a new RTMP IP Output in StreamHub, click on the (+) icon in the IP Output section and then click the (+) button under IP Output Profiles.



  5. Click on the RTMP protocol button to create an RTMP output profile. 



  6. Configure the RTMP profile using the Stream URL (Stream Key) and Stream Key from Telegram (refer to step 2 above).



  7. Save the RTMP IP output profile.
  8. Select the RTMP IP Output profile by clicking on the associated radio button. An IP Output with the selected RTMP profile is enabled. 



  9. Configure the StreamHub Encoder. 

    Important

    There are certain requirements for the video / audio codec as well as for resolution and frame rate which can be managed by Telegram. If the source transmitter is using a non-supported configuration such as the HEVC video codec then a “Codec not supported” error will appear in the StreamHub RTMP output. In this case, it is necessary to transcode the stream first using the StreamHub encoder function to make it compatible with Telegram specifications.

    Tip

    Transcoding in StreamHub requires an encoder license and adequate resources for live encoding in a supported format.

    Note

    If the transmitter is already sending in a supported video/audio format, codec, resolution, and frame rate, this step can be skipped.

    1. Click on the (+) Icon in the StreamHub Encoder section and create a new Encoder Profile by pressing the next (+) button in the Encoder Profiles selection. 
    2. Provide a name and select the Web Streaming encoder preset. The example at left shows the recommended Telegram streaming parameters for 720p30:
       
      1. Video: H.264, bitrate up to 3000 Kbps 
      2. Audio: AAC LC, bitrate = 128 Kbps 

    3. Click on Save once satisfied with the settings.

    Note

    Currently there is no known specification published by the Telegram company to define the exact configuration, other than the fact that the video has to be H.264. However, it is not recommended to stream at high bitrates to avoid creating bottlenecks in the Telegram server.

  10. Select the saved Encoder Profile by clicking the associated radio button. An Encoder with the selected Encoder profile is enabled. 



  11. Link the workflow from Input > Encoder > Output. This allows the input stream to be transcoded first to a Telegram compatible format before outputting the stream to Telegram. There are two methods:

    Method A: Drag and drop the desired input icon onto the Encoder, and then drag and drop the Encoder onto the Output icon.



    Method B: From the Encoder drop down, select the input desired to be transcoded, and then select the Encoder in the output drop down to output to Telegram. 



    The input is now assigned to the Encoder for transcoding into a Telegram compatible format, and then the transcoded stream is set to output to the Telegram RTMP Server URL configured under RTMP IP Output.

  12. If the stream is not already live, click the Live button on the input (or from the transmitter unit) to start live streaming. 



    The live stream should appear in the Telegram Live Video view: 

    In the Desktop App: 



    On a mobile phone (iOS only): 






JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.