To reset your server,

  • Click Account Settings from the top right corner.
  • A drop-down menu opens, and click Reset.

Note: If you give Reset, all your settings, channels and recordings will be deleted.

RTMP Stats

To view your RTMP stats,

  • Go to System from the navigation menu and click Viewers Report.
RTMP stats
  • In viewers report page, go to RTMP Stats, where you can get the statistics report of your streaming channels.
RTMP stats

Service Restart

While applying any new changes or creating a channel, the changes are implemented only after giving Service Restart.

  • Click Service Restart from the top right corner. A dialog box opens where you can click OK to apply new changes to your Livebox server.  
Service Restart
service restart in livebox

Note: Giving Service Restart after mis-configuration can result in corrupting of the server.

The Speed Test

Livebox Speed test checks server’s speed, internet and also the receiver’s speed. To check your server’s speed,

  • Go to the navigation menu and select System. A Speed Test page opens, where you can see the speed meter scales on both sides.
  • Click Go on the screen to start the speed test.
conducting speed test
  • The speed test starts and you will get your server’s download and upload speed results.

The System Interface Settings

To set your system interface or in case of any error occurs in your system overview,

  • Go to Settings from the navigation menu and click the System Settings option.
system settings in livebox
  • Under System Settings, click the drop-down menu to select your Interface and Disk R/W and then click Submit.
system settings
  • Now go to Dashboard and right-click to Reload Frame.
Reload frame

  • Your system interface is now set.
system interface is set

You can now check your server’s CPU load, memory usage, disk read, disk write, in and out bandwidth usage from Livebox dashboard at one go.

Streaming URL and an Embed Code

     The streaming RTMP URL link plays an important role throughout your live streaming process, on the other hand, an embed code is for broadcasting on your website/blog. Both the RTMP URL and embed code are generated by Livebox respective to the channel you create.

To get your RTMP URL link,

  • Log in to your Livebox server and create your channel.
  • Go to Manage Channel from the navigation menu and click the Streaming URL button.
channel dashboard

And copy the displayed RTMP streaming URL to paste in your encoder settings.

streaming URL
RTMP streaming URL

To get your embed code,

  • Log in to your Livebox server and create your channel.
  • Go to Manage Channel from the navigation menu and click the Embed code button.  
Embed code
Embed code for broadcasting

Note: If your site is secured i.e. HTTPs encrypted, then you have to copy the Secure Embed Code.

scure embed code
  • Now login to your broadcasting website/blog, and copy-paste the embed code of your channel on the web page of your site/blog.
embed code in web page/blog
  • If your website is of WordPress, then you have a few more settings to undergo. So, click here to know how to publish your live streaming contents on the WordPress websites.
  • Then click Update. Your broadcasting is done successfully.
broadcasting in webpage/blog

By following these steps you can get your streaming URL and Embed code and get started with your live streaming across various media platforms.

Advanced Settings


  • RTMP– The block which holds all RTMP settings.
  • Server- Declares RTMP server instance.
  • Listen- Adds a listening socket for accepting RTMP connections.
  • Application- Creates an RTMP application. Unlike RTMP location, application name cannot be a pattern.
  • Timeout (Socket timeout)- This value is primarily used for writing. Most of time RTMP module does not expect any activity on all sockets except for publisher socket. If you want the broken socket to get quickly disconnected use active tools like keepalive or RTMP ping. The default is 1 minute.
  • Ping (RTMP ping interval)- Zero turns ping off. RTMP ping is a protocol feature for active connection check. A special packet is sent to a remote peer and a reply is expected within a timeout specified with the ping_timeout directive. If ping reply is not received within this time then the connection is closed. The default value for ping is 1 minute. Default ping timeout is 30 seconds.
  • Ping_timeout- See ping description above.
  • Max_streams- Sets the maximum number of RTMP streams. Data streams are multiplexed into a single data stream. Different channels are used for sending commands, audio, video, etc. The default value is 32 which is usually ok for many cases.
  • Ack_window- Sets RTMP acknowledges window size. It’s the number of bytes received after which peer should send acknowledge packet to the remote side. The default value is 5000000.
  • Chunk_size- Maximum chunk size for stream multiplexing. The default is 4096. The bigger the value the lower CPU overhead. This value cannot be less than 128.
  • Max_queue
  • Max_message- The maximum size of the input data message. All input data comes split into messages (and further in chunks). A partial message is kept in memory while waiting for it to complete. In theory, the incoming message can be very large which can be a problem for server stability. Default value 1M is enough for many cases.
  • Buflen- Sets default buffer length. Usually, the client sends the RTMP set_buflen command before playing and resets this setting. The default is 1000 ms.
  • Out_queue
  • Out_cork
  • Access (Allows)- Allow publishing/playing from addresses specified or from all addresses. Allow/deny directives are checked in order of appearance.
  • Deny See allow for description.
  • Exec- Exec_push Specifies external command with arguments to be executed on every stream published. When publishing stops the process is terminated. Full path to binary should be specified as the first argument. There are no assumptions about what this process should do. However, this feature is useful with FFmpeg for stream transcoding. FFmpeg is supposed to connect to RTMP as a client and output transcoded stream back to RTMP as publisher. Shell-style redirects can be specified in the exec_push directive for writing output and accepting input. Make sure there’s no space between redirection character and stream name/number. You can specify the full path to the command to execute or short command name. In the latter case, binary is looked up in directories specified by the PATH environment variable. By default, it clears the environment which will usually make RTMP module run only binaries located in standard directories like /bin and /usr/bin. To make this always work please keep the original PATH variable value with the following directive. The following FFmpeg call transcodes incoming stream to HLS-ready stream (H264/AAC). FFmpeg should be compiled with libx264 & libfaac support for this example to work.
  • Exec_pull- Specifies external command with arguments to be executed on play event. The command is executed when the first client connects to the stream and is killed when the last one disconnects. This directive makes it possible to pull the remote stream in any format for local clients. The feature works reliably only in single-worker mode. The reason for this is we cannot make sure the external process always connects to the right worker. It will obviously connect to a random one. While this will still work in most cases it’s not a recommended architecture, it will be unstable and buggy. Directive arguments are the same as for exec_push. In the above configuration, exec_pull directive serves all streams. That leads to certain limitations on remote stream name format. It should be possible to construct the remote URL using available variables like the $app, $name, etc. When it’s not possible you can add exec_options on a directive which permits setting additional stream options in exec-family directives. The only option supported now is name option.
  • Exec – Exec is an alias of exec_push
  • Exec_options- The directive toggles exec options mode. When activated you can add exec-family directive options. The only exec option supported is name. This option makes it possible to apply exec only to the specified stream. The Default is off.
  • Exec_static- Similar to exec but runs specified command at the start. Does not support substitutions since has no session context.
  • Exec_kill_signal- Sets process termination signal. The default is kill (SIGKILL). You can specify a numeric or symbolic name (for POSIX.1-1990 signals).
  • Respawn- If turned on respawns child process when it’s terminated while publishing is still on. The default is on.
  • Respawn_timeout- Sets respawn timeout to wait before starting a new child instance. The default is 5 seconds.
  • Exec_publish- Specifies external command with arguments to be executed to publish an event. The return code is not analyzed. Substitutions of exec are supported here as well. In addition, the args variable is supported holding query string arguments.
  • Exec_play- Specifies external command with arguments to be executed on play event. The return code is not analyzed. Substitution list is the same as for exec_publish.
  • Exec_play_done- Specifies external command with arguments to be executed on the play_done event. The return code is not analyzed. Substitution list is the same as for exec_publish.
  • Exec_publish_done Specifies external command with arguments to be executed on the publish_done event. The return code is not analyzed. Substitution list is the same as for exec_publish.
  • Exec_record_done Specifies external command with arguments to be executed when recording is finished.
  • Live- Live Toggles live mode i.e., one-to-many broadcasting.
  • Meta (Sets metadata sending mode)- The value of on makes subscribers receive reconstructed metadata packets containing predefined fields like width, height, etc. The value of copy makes clients receive an exact copy of publisher metadata block including both standard and specific fields. The value of off turns off sending any RTMP metadata to subscribers. The defaults to on.
  • Interleave (Toggles interleave mode)- In this mode, audio and video data are transmitted on the same RTMP chunk stream. Defaults to off.
  • Wait_key- Makes video stream start with a keyframe. Defaults to off.
  • Wait_video- Disable audio until the first video frame is sent. Defaults to off. Can be combined with wait_key to make client receive video keyframe with all other data following it. However, this usually increases connection delay. You can tune keyframe interval in your encoder to reduce the delay. Recent versions of IE need this option to be enabled for normal playback.
  • Publish_notify- Send NetStream.Play.PublishNotify and NetStream.Play.UnpublishNotify to subscribers. Defaults to off.
  • Drop_idle_publisher- Drop publisher connection which has been idle (no audio/video data) within a specified time. The default is off. Note this only works when the connection is in publish mode (after sending publish command).
  • Sync (Synchronize audio and video streams)- If subscriber bandwidth is not enough to receive data at publisher rate, some frames are dropped by the server. This leads to the synchronization problem. When timestamp difference exceeds the value specified as sync argument an absolute frame is sent fixing that. The default is 300ms.
  • Play_restart- If enabled RTMP sends NetStream.Play.Start and NetStream.Play.Stop to each subscriber every time the publisher starts or stops publishing. If disabled each subscriber receives those notifications only at the start and end of playback. The default is off.
  • Idle_streams- If disabled RTMP prevents subscribers from connecting to idle/nonexistent live streams and disconnects all subscribers when stream publisher disconnects. The default is on.
  • Record (Record Toggles record mode)- The stream can be recorded in the FLV file.
  • Record_path- Specifies the record path to put recorded FLV files to.
  • Record_suffix (Sets record file suffix)- Defaults to ‘.FLV’. Record suffix can be a pattern in strftime format.
  • Record_unique- If turned on appends a current timestamp to recorded files. Otherwise, the same file is re-written each time new recording takes place. The default is off.
  • Record_append (Toggles file append mode)- When turned on recorder appends new data to the old file or creates it when it’s missing. There’s no time gap between the old data and the new data in the file. The default is off.
  • Record_lock When turned on currently recorded file gets locked with the fcntl call. That can be checked from elsewhere to find out which file is being recorded. The default is off. On FreeBSD, you can use flock tool to check that. On Linux flock and fcntl are unrelated so you are left with writing a simple script checking file lock status. Here’s an example of such script
  • Record_max_size- Set maximum recorded file size.
  • Record_max_frames- Sets the maximum number of video frames per recorded file.
  • Record_interval- Restart recording after this number of milliseconds. Off by default. Zero means no delay between recordings. If record_unique is off then all record fragments are written to the same file. Otherwise, the timestamp is appended which makes files differ (given record_interval is longer than 1 second).
  • Recorder (Create a recorder block)- Multiple recorders can be created within a single application. All the above mentioned recording-related directives can be specified in recorder{} block. All settings are inherited from higher levels.
  • Record_notify- Toggles sending NetStream.Record.Start and NetStream.Record.Stop status messages (onStatus) to the publisher when a specific recorder starts or stops recording file. Status description field holds recorder name (empty for default recorder). Off by default.
  • Video on demand  Play- Play FLV or mp4 file from a specified directory or HTTP location. If the argument is prefixed with http:// then it is assumed that file should be downloaded from remote HTTP location before playing. Note playing is not started until the whole file is downloaded. Multiple play locations can be specified in a single play directive. When multiple play directives are specified the location lists are merged and inherited from higher scopes. An attempt to play each location is made until a successful location is found. If such location is not found error status is sent to the client. Indexed FLVs are played with random seek capability. Unindexed FLVs are played with seek/pause disabled (restart-only mode). Use FLV indexer (for example, yamdi) for indexing. If you play FLVs recorded with the record directive please do not forget to index them before playing. They are created unindexed. MP4 files can only be played if both video and audio codec is supported by Rtmp. The most common case is H264/AAC. Playing /var/flvs/dir/file.flv: The two slashes after vod make ffplay use vod and application name and the rest of the URL as playpath.
  • Play_temp_path- Sets location where remote VOD files are stored before playing. Default is /tmp;
  • Play_local_path- Sets location where remote VOD files copied from play_temp_path directory after they are completely downloaded. Empty value disables the feature. By default, it’s empty. The feature can be used for caching remote files locally. This path should be on the same device as play_temp_path.
  • Relay– Pull Creates pull relay. The stream is pulled from a remote machine and becomes available locally. It only happens when at least one player is playing the stream locally. Url syntax: [rtmp://]host[:port][/app[/playpath]]. If the application is missing then the local application name is used. If playpath is missing then current stream name is used instead. If a value for a parameter contains spaces then you should use quotes around the WHOLEkey=value pair like this: ‘pageUrl=FAKE PAGE URL’.
  • Push- Push has the same syntax as a pull. Unlike pull-push directive publishes a stream to the remote server.
  • Push_reconnect- Timeout to wait before reconnecting pushed connection after disconnect. The default is 3 seconds.
  • Session_relay- Toggles session relay mode. In this mode, the relay is destroyed when the connection is closed. When the setting is off relay is destroyed when the stream is closed so that another relay could possibly be created later. The default is off.
  • Notify– On_connect Sets HTTP connection callback. When clients issues connect command an HTTP request is issued asynchronously and command processing is suspended until it returns a result code. If HTTP 2xx code is returned then RTMP session continues. The code of 3xx makes RTMP redirect to another application whose name is taken from the Location HTTP response header. Otherwise, the connection is dropped. Note this directive is not allowed in application scope since the application is still unknown at the connection stage. HTTP request receives a number of arguments. POST method is used with application/x-www-form-urlencoded MIME type. In addition to the above-mentioned items, all arguments passed explicitly to connect command are also sent with the callback. You should distinguish connect arguments from the play/publish arguments. Players usually have a special way of setting connection string separate from the play/publish stream name. As an example, here’s how these arguments are set in JWPlayer FFplay (with librtmp) example
  • On_play- Sets HTTP plays callback. Each time a clients issues play command an HTTP request is issued asynchronously and command processing is suspended until it returns a result code. The HTTP result code is then analyzed. Http request receives a number of arguments. POST method is used with application/x-www-form-urlencoded MIME type. In addition to the above-mentioned items, all arguments passed explicitly to play command are also sent with the callback. For example, if stream is accessed with the URL rtmp://localhost/app/movie?a=100&b=face&foo=bar then a, b & foo are also sent with callback.
  • On_publish- The same as on_play above with the only difference that this directive sets callback on publish command. Instead of a remote pull-push is performed in this case.
  • On_done- Sets play/publish terminate callback. All the above applies here. However, the Http status code is not checked for this callback.
  • On_play_done- Same behavior as on_done but only for play end event.
  • On_publish_done- Same behavior as on_done but only r publish end event.
  • On_record_done- Set record_done callback.
  • On_update- Set update callback. This callback is called with a period of notify_update_timeout. If a request returns HTTP result other than the 2xx connection is terminated. This can be used to synchronize expired sessions.
  • Notify_update_timeout- Sets timeout between on_update callbacks. The default is 30 seconds.
  • Notify_update_strict- Toggles strict mode for on_update callbacks. The default is off. When turned on all connection errors, timeouts, as well as HTTP parse errors and empty responses, are treated as update failures and lead to connection termination. When off only valid HTTP response codes other than 2xx lead to failure.
  • Notify_relay_redirect- Enables local stream redirect for on_play and on_publish remote redirects. The new stream name is an MD5 hash of RTMP URL used for the remote redirect. The default is off.
  • Notify_method- Sets HTTP method for notifications. Default is POST with application/x-www-form-urlencodedcontent type. In certain cases GET is preferable, for example, if you plan to handle the call in http{}section. In this case, you can use arg_* variables to access arguments.
  • HLS– HLS Toggles HLS on the application.
  • HLS_path- Sets HLS playlist and fragment directory. If the directory does not exist it will be created.
  • HLS_fragment- Sets HLS fragment length. Defaults to 5 seconds.
  • HLS_playlist_length- Sets HLS playlist length. Defaults to 30 seconds.
  • HLS_sync- Sets HLS timestamp synchronization threshold. The default is 2ms. This feature prevents crackling noises after conversion from low-resolution RTMP (1KHz) to high-resolution MPEG-TS (90KHz).
  • HLS_continuous- Toggles HLS continuous mode. In this mode, the HLS sequence number is started from where it stopped last time. Old fragments are kept. The default is off.
  • HLS_nested- Toggles HLS nested mode. In this mode, a subdirectory of hls_path is created for each stream. Playlist and fragments are created in that subdirectory. The default is off.
  • HLS_base_url- Sets base URL for HLS playlist items. When empty those items have no prefix and assumed to be at the same location as parent playlist or one level lower when hls_nested is used. This feature applies both to master (variant) and slave HLS playlists. It can let you download the playlist and play it locally since it contains full references to child playlists or fragments. Empty by default.
  • HLS_cleanup- Toggles HLS cleanup. By default, the feature is on. In this mode, the cache manager process removes old HLS fragments and playlists from HLS directory.
  • HLS_fragment_naming- Sets fragment naming mode.
  • HLS_fragment_naming_granularity- Sets granularity for HLS fragment ids. If above zero, changes ids to divide the provided value. The default is zero.
  • HLS_fragment_slicing- Sets fragment slicing mode.
  • HLS_variant- Adds HLS variant entry. When the suffix is matched on stream name then variant playlist is created for the current stream with all entries specified by hls_variant directives in the current application. A stripped name without a suffix is used as a variant stream name. The original stream is processed as usual. Optional parameters following the suffix are appended to EXT-X-STREAM-INF in the m3u8 playlist. See HLS spec. 3.3.10. EXT-X-STREAM-INF for the full list of supported parameters.
  • HLS_type- Sets HLS playlist type specified in X-PLAYLIST-TYPE playlist directive. Live HLS stream is usually played from the current live position which is several fragments to the end of the playlist. Event HLS stream is always played from the start of the playlist. When in event mode make sure playlist length is enough for the whole event. The default
  • HLS_keys- Enables HLS encryption. The AES-128 method is used to encrypt the whole HLS fragments. Off by default. Here’s the example configuration using the HLS encryption. This configuration requires that is built with –with-http_ssl_module for https support.
  • HLS_key_path- Sets the directory where auto-generated HLS keys are saved. Key files have .key extension and pseudo-random 16-byte content created with the OpenSSL RAND_bytes() routine. If the directory does not exist it’s created in runtime. By default, hls_path directory is used for key files. Remember however you should normally restrict access to key files which is easier when these files are stored separately from playlist and fragments.
  • HLS_key_url- Sets URL for HLS key file entries. When empty those items have no prefix and keys are assumed to be at the same location as the playlist. Empty by default.
  • HLS_fragments_per_key- Sets the number of HLS fragments encrypted with the same key. Zero means only one key is created at the publish start and all fragments within the session are encrypted with this key. The default is zero.
  • MPEG-DASH– Dash Toggles MPEG-DASH on the application.
  • Dash_path Sets MPEG-DASH playlist and fragment directory. If the directory does not exist it will be created.
  • Dash_fragment- Sets MPEG-DASH fragment length. Defaults to 5 seconds.
  • Dash_playlist_length- Sets MPEG-DASH playlist length. Defaults to 30 seconds.
  • Dash_nested- Toggles MPEG-DASH nested mode. In this mode, a subdirectory of dash_path is created for each stream. Playlist and fragments are created in that subdirectory. The default is off.
  • Dash_cleanup- Toggles MPEG-DASH cleanup. By default, the feature is on. In this mode, the cache manager process removes old MPEG-DASH fragments and manifests from the MPEG-DASH directory. Init fragments are deleted after stream manifest is deleted.
  • Access log– Access_log Sets access log parameters. Logging is turned on by default. To turn it off use access_log offdirective. By default, access logging is done to the same file as HTTP access logger (logs/access.log). You can specify another log file path in the access_log directive. The second argument is optional. It can be used to specify a logging format by name. See log_format directive for more details about formats.
  • Log_format- Creates named log format. Log formats look very much the same as HTTP log formats.
  • Limits– Max_connections Sets the maximum number of connections for the Rtmp engine. Off by default.
  • Statistics– Statistics The module is the HTTP module unlike all other modules listed here.
  • RTMP_stat- Sets RTMP statistics handler to the current HTTP location. RTMP statistics is a dynamic XML document. To watch this document in browser as XHTML page use rtmp_stat_stylesheet directive.
  • RTMP_stat_stylesheet- Adds XML stylesheet reference to statistics XML to make it viewable in a browser. See RTMP_stat description and example for more information.
  • Multi-worker live streaming– Multi-worker live streaming is implemented by pushing the stream to remain workers.
  • RTMP_auto_push- Toggles auto-push (multi-worker live streaming) mode. The default is off.
  • RTMP_auto_push_reconnect Sets auto-push reconnect timeout when a worker is killed. The default is 100 milliseconds.
  • RTMP_socket_dir- Sets directory for UNIX domains sockets used for stream pushing. The default is /tmp.
  • Control– The control module is the HTTP module and should be located within http{} block.
  • RTMP_control Sets RTMP control handler to the current HTTP location.

Livebox Glossary

  1. Attempts– A number of attempts that you want your streaming media to make if there occurs any interruption while it is being streamed.
  2. App Store- In the Livebox app store, you can install or uninstall the apps based upon your needs.
  3. APK builder– The APK builder is for generating different kinds of ready to use white-labeled mobile apps directly from Livebox.
  4. Autostream– You can create a playlist from your local files or from the existing videos of your YouTube channel and automate it live on Facebook, Twitter, Periscope or any other RTMP server channel.
  5. Branding Settings– In Branding settings, the Livebox server can be white-labeled under the client’s business or brand identity.
  6. CG Editor– It is an editor available in Livebox playout software which enables the adding of texts, image, crawling ticker, rolling ticker, date and time for your live streams.
  7. Channel Logo– By creating a unique logo for your streaming channel, you can establish your live streaming brand and make the viewers recognize all of your live streams.
  8. Clappr – It is the embeddable video player which is built-in to view your preview.
  9. Client Portal– It is the login page accessed by the sub-user, where they can stream and re-stream live contents.
  10. DASH-It is also known as MPEG-DASH which is an alternative for HLS. It supports Android, iOS, Windows, Mac, Linux, Chrome OS, smart TV, games, set-top boxes.
  11. Dashboard– A control panel where you can preview your live stream, check the HTTP hits, select your channel and know about disc space and other system overviews.
  12. Delay– It indicates the setting of the time interval between consecutive streaming videos.
  13. Destinations– It includes several media destinations like Facebook, YouTube, Periscope and other media which support RTMP sources.
  14. Disk space– It shows the used storage space and the left storage space in Livebox Server.
  15. Download speed– It shows the Internet speed of the downloaded streaming media.
  16. Embed code– It is the autogenerated HTML code. Copy-paste the embedded code in your broadcasting page, so to stream live your video.
  17. FLV recording– (Flash video) It is the recording of digital video content which includes audio, video, text and data.
  18. HLS recording-HLS is also known as HTTP live streaming. It is the recording of digital video content which includes audio, video, text and data.
  19. HTTP Redirection– You can enable/disable HTTPS redirection of your server domain (Secure/ Not Secure mode).
  20. Idle Streams– To rectify Encoder disconnection/re-connectivity issues with the server you can Turn On Idle Streams option in RTMP Settings under Channel Settings.
  21. Load– Load shows HTTP hits, i.e. the number of access that the server experience.
  22. Loop– Loop enables continuous live streaming. If you set priority for your streams and turn on loop, then your streams will be streamed on one after the other.
  23. MP4 recording– It is the recording of MPEG-4 Part 14 (MP4) media content which includes audio, video, subtitles, and other data.
  24. Multi-bitrate– Multi-Bitrate helps you to stream in multiple formats to achieve seeing qualities. If your stream is of high-quality resolution then you can convert the stream into the lower quality and the other way around by using Multi-Bitrate.
  25. Multi-CDN– Through multi-CDN you can set up the alternate servers as the back-up to run the streaming program uninterrupted when the server fail-over occurs.
  26. PIP– Picture-in-picture(PIP) is similar to multi-window mode, where you can pin several small source window on the same screen and broadcast it on your channel.
  27. Playout– It is the Livebox in-built software in which you can add your content, and then encode your source to make it ready for your live streaming without being dependent on any other external encoders.
  28.  Player Customization– You can customize the player theme and notification in Player Settings under Channel Settings.
  29. Player Logo– Like a channel logo, you can also create a logo for the player. When a logo is added to the player, then the logo is fixed only to that player. So, adding a logo to the player is beneficial when the same content is reproduced to multiple destinations/channel.
  30. Preset– It is the set of resolutions for your live streams. In streaming like Multi-Bitrate and Transcoding, you can set or even change your required resolution.
  31. Preview– By clicking play in the preview, you can view your streams before it’s been broadcasted or streamed in real-time.
  32. Priority– It sets the sequential order for your streaming.
  33. Push destination– It is the process of pushing your streams to several media destinations.
  34. Queues– In queues, you can set your encoding tasks based on your priority.
  35. Re-stream– Re-stream happens inside Client Portal. It is the sub-user who will be re-streaming Livebox’s live streams to their accessed destinations (media platforms). Re-stream is the process in which the sub-user is given access to stream the content which is streamed by the Livebox admin.
  36. RTMP URL-It is the flash-based streaming protocol that sends the stream from your encoder to several other media destinations.
  37. Service monitor– It allows monitoring of Livebox services and its status. In service monitor you can give factory reset for all your services and start, stop or restart any service you want.
  38. Service restart– By clicking the Service restart, all your new changes will come into existence.
  39. Stream key– A stream key is one of the essential components of your streaming process. In the Livebox streaming server, the streaming RTMP URL is auto-generated, and from the streaming URL, you can easily obtain your stream key.
  40. Streaming URL– It is the autogenerated HTML code that should be copy-pasted to make your live stream happen.
  41. Stretch– By using the stretch option, video size can be increased to fill the player screen aspect ratio.
  42. Sub-users– Admin has the power to create sub-users and assign a separate login portal for sub-users to hand over control of a particular channel.
  43. Thumbnail– Turn on thumbnail setting to get displayed snapshot copies of your streams in the preview box.
  44. Transcoding – Transcoding is the conversion of live streamed encoded digital video into another digital format.
  45. UDP– By using the UDP option in the Queues feature, you can convert the cable TV channels sources into streamable sources.
  46. Upload speed– It shows the Internet speed of the uploaded streams.
  47. Video Conferencing– You can conduct Videoconferencing with your teammate, customer, employee, business partner, online students using the Video conferencing feature in Livebox.
  48. Video 360-degree– Livebox supports 360-degree camera and its source. You can easily capture and live stream 360-degree sources on all your social media accounts and live streaming platforms by enabling the Video 360 option.
  49. Website– In Websites, you can create high-quality WordPress, GRAV and Typesetter sites for your business, events, organizations, churches, education for cost-free.

An Overview

Livebox, a streaming server which provides easy streaming service to its users. Livebox is the only streaming server that allows multi-channel live video streaming with transcoding, and it comes inclusive of all hardware required on the cloud. Livebox also includes a fully licensed playout, mixing and encoding software at absolutely no additional cost to the user. So, we give promising service to our Livebox users to stream live videos to any media platform from anywhere at an affordable price.
There you go, for all your live streaming of sports, news telecast, concerts, movies, TV shows, tutorials, wedding events or any event organization and so on and on, Livebox comes in handy.
Note: Transcoding 24/7 benefit is applicable for one channel depending on the plan that is purchased or the configuration of the server.
Key concepts
  • Streaming
    Audio-video sources are digitized for broadcasting on media platforms.
  • Recording
    Recording of FLV, MP4, HLS sources are incorporated in such a way that the user can view recorded files before the entire file is transmitted to the network.
  • Encoding
    Livebox is the only streaming server that acts as an encoder by itself. Recorded videos can be added to the queues to be encoded and then to be streamed. Above all, the user can also download Encoder-Mixer-Playout software at free of cost.
  • Transcoding
    Converts existing encoded digital format into another digital format.

Business Tools

Dashboard It consists of Preview to view your video source, number of created channels, disk space usage, and other system overviews.
System overview It provides information on CPU load, Memory usage, Disk write and Disk read, In and Out Bandwidth.
Chatting Chatting is enabled between the event organizer, channel owner or Livebox admin with the viewers.
Channelization A number of channels can be created and managed.
Speed test It consists of testers to show Download speed and upload speed.
Video mixer It enables adding advertisements or any video mixing while live streaming is streamed on.
Playout Software The in-built software in which you can add your content, and then encode your source to make it ready for your live streaming without being dependent on any other external encoders.
360-degree videos It supports live streaming of videos which are recorded from the 360-degree camera.
Cloud Playout It is a feature to create your playlist with the local files or recorded videos.
Livebox Playlist A bunch of playlists can be created from the existing YouTube videos of your channel.
Websites It helps you to create WordPress sites for your businesses at free of cost.
Livebox TV With Livebox TV you can set up your own TV station.
Videoconferencing It is customized to start your video calls and chatting within Livebox.

Supported by,
• iOS
• Android
• Windows
• HLS sources

Getting Started!

   The wait is over! Within two clicks you can get started with your Livebox Streaming Server and witness the world’s user-friendly streaming server. The first and foremost thing you got to do after being an official owner of Livebox server is, take a look at the mail sent by our IVB7 team, and pick up on the credentials provided for your initial log in. And you can start streaming your live events and take them across the world without any difficulty by using just one Livebox.

Note: You can always change your server password for your security in the future, which we recommend too.

Happy Live Streaming with Livebox!

  • This is how the mail looks. The mail provides you a link to your interface along with your log in details. Click on the link so to enter your access page.

mail from IVB7 team

  • You are on the first step of your Livebox streaming. To start your streaming journey, log in to your Dashboard.

livebox login page

  • This is the second step of your Livebox streaming server. Enter the given Username and password from your mail to log in.

Livebox login

  • Finally! You are on your Livebox Dashboard. Explore and experience your Livebox server.

Livebox dashboard

Dashboard– the place where you get most of your server’s information and easy access to other major settings of your server from the navigation menu. Some of them are:
  • Under Manage Channels, you can record, transcode and also MBR (Multi-Bitrate) streaming.
  • In System, you can test the speed of your server and create Sub-User.
  • To change your password and for other privacy settings, you can go to Security.
  • Channels– it is one of the important things that your server holds. Whatever the content you might stream but you always need a channel to take through your live streams to several media platforms. So, create your channel in Livebox to stay connected with the World. We have also provided you with a default channel for your ease. All you have to do get the RTMP URL of your channel, connect your encoder and GO LIVE.
  • System overview– you can get information about your server’s performance, all at one place without much wanderings.

    To learn other info and overviews, and to explore Livebox, go to “About Livebox” from our Knowledgebase site.

You are almost ready!
Congratulations! To you and your professional start out.