Video Module FAQ

Document created by kristina on Mar 3, 2011Last modified by Michelle Gantt on Feb 10, 2020
Version 23Show Document
  • View in full screen mode

 

Installation

Do I need a license or plugin?

Yes, your Jive license must include the Video module.  Once purchased, our Support department will direct you to the module set up case in your Jive Community customer group and provide video keys to enter in the admin console.

 

Can I use the video module if my Jive instance is on-premise (self-managed)?

Yes. The video module makes use of the Jive Video Service which is a Jive-hosted-only component, but it is fully compatible with on-premise Jive instances.  The Jive Video Service is hosted by Perceptive Media, perviously known as Twistage.

How does the video module work?  Is there an architecture diagram?

See the attached Jive Video Module Architecture document.

 

Why does the video service need to communicate through my firewall to my on-premise Jive SBS instance?

 

The video service needs to make inbound connections to the Jive instance for two processes.

 

First, after a video is uploaded, the video service will encode the asset and make it available for streaming. When that publish process completes, the service calls into the Jive instance and passes metadata about the uploaded asset. That process is called the Publish Callback. This requires an inbound connection to {jiveURL}/pubcallback.jspa.

 

The other process requiring the video service to communicate with your Jive instance is related to the security of video playback. When a user presses the play button on our embedded video player, the video CDN will not initiate playback until it validates the authorization. To do that, the video service calls into your Jive instance, passing info about the requested asset and a corresponding authorization token that was generated when the page containing the player was rendered. The Jive instance will then tell the CDN that it can initiate playback of the video. This process is called the Auth Callback. The authentication validation requires an inbound connection to the {jiveURL}/authcallback.jspa.

 

Both of these callbacks must be permitted from the following IP ranges on ports 80 and 443.

 

107.21.212.16

107.22.216.172

174.129.240.31

174.29.238.27

184.72.239.40

184.73.232.18

23.21.76.80

23.23.90.48

23.23.94.7

46.137.165.93

50.16.187.111

50.16.210.98

50.19.127.228

52.206.223.205

52.22.44.102

52.22.98.14

52.4.125.148

52.44.119.45

52.45.236.90

52.45.54.219

52.54.180.117

52.6.145.21

54.195.246.169

54.197.254.218

54.204.24.127

54.217.228.206

54.243.35.52

75.101.144.40

79.125.11.104

79.125.12.197

79.125.20.107

79.125.24.56

79.125.25.81

79.125.6.182

79.125.6.237

 

The client web browser needs to be able to make outbound connections to load the Flash player and stream content.

 

Clients should be able to talk directly to the IP ranges above on ports 80 and 443. There are two options for allowing a firewall to do this, either by domain or by IP.

 

If whitelisting by domain, add domains *.jivesoftware.com, *.twistage.com, *.edgecastcdn.net, *.alphacdn.net, *.betacdn.net, and *.omegacdn.net.

 

If whitelisting by IP, add the IPs listed above and the CDN IPs which serve the actual content for their region.

 

To allow access worldwide access, whitelist the following IP ranges:

5.104.64.0/21

46.22.64.0/20

61.49.62.128/25

61.221.181.64/26

68.232.32.0/20

72.21.80.0/20

88.194.45.128/26

93.184.208.0/20

101.226.203.0/24

108.161.240.0/20

110.232.176.0/22

117.18.232.0/21

117.103.183.0/24

120.132.137.0/25

121.156.59.224/27

121.189.46.0/23

152.195.0.0/16

180.240.184.0/24

192.16.0.0/18

192.30.0.0/19

192.229.128.0/17

192.229.156.0/23

194.255.210.64/26

198.7.16.0/20

203.74.4.64/26

213.64.234.0/26

213.65.58.0/24

61.49.52.0/26

120.132.137.192/26

 

IPs in AWS:

 

US

23.21.76.80

23.23.90.48

23.23.94.7

34.193.164.199

34.194.69.63

34.197.195.21

34.197.38.169

50.16.187.111

50.16.210.98

50.19.127.228

52.206.223.205

52.22.44.102

52.22.98.14

52.23.89.187

52.44.119.45

52.45.236.90

52.45.54.219

52.54.180.117

52.6.145.21

54.197.254.218

54.204.24.127

54.243.35.52

75.101.144.40

107.21.212.16

107.22.216.172

174.129.238.27

174.129.240.31

184.72.239.40

184.73.232.18

23.22.3.153

3.82.85.231
35.169.60.220
54.210.231.86
107.20.113.129

EU

46.137.165.93

46.51.175.207

54.195.246.169

54.217.228.206

54.75.240.33

54.75.255.96

79.125.11.104

79.125.12.197

79.125.19.129

79.125.20.107

79.125.24.56

79.125.25.81

79.125.6.182

79.125.6.237

34.248.243.247
34.242.131.27
63.32.187.35
34.248.186.115
63.32.87.167

 

 

To allow narrower access to specific CDN regions, whitelist the relevant IPs. (Note: this list is currently missing some entries and needs to be updated.)

 

ContinentCityCodeIP BlocksIP Blocks V6Last Updated
AsiaBatamBTH180.240.184.128 /252405:8f00:EDCB:0000:0000:0000:0000:0000 /487/7/14 17:48
AsiaHong KongHHP108.161.247.0 /24;110.232.176.0 /24;192.229.154.0 /242606:2800:6010:0000:0000:0000:0000:0000 /47;2606:2800:6040:0000:0000:0000:0000:0000 /48;2606:2800:6041:0000:0000:0000:0000:0000 /484/10/13 19:22
AsiaJakartaCGK180.240.184.0 /252405:8F00:EDCA:0000:0000:0000:0000:0000 /488/28/13 19:23
AsiaKaohsiungKHH61.221.181.64 /26;203.74.4.64 /262001:b032:c101:0000:0000:0000:0000:0000 /4811/26/13 23:02
AsiaOsakaKIX117.103.183.0 /242606:2800:6028:0000:0000:0000:0000:0000 /475/15/13 18:08
AsiaSeoulICN121.156.59.224 /27;121.189.46.0 /24;121.189.47.0 /2410/23/14 21:06
AsiaSingaporeSIN46.22.71.0 /24;117.18.236.0 /242606:2800:6000:0000:0000:0000:0000:0000 /474/10/13 19:22
AsiaTokyoNRT110.232.177.0 /24;117.18.233.0 /24;192.16.56.0 /24;192.16.57.0 /24;198.7.26.0 /242606:2800:6020:0000:0000:0000:0000:0000 /47;2606:2800:6023:0000:0000:0000:0000:0000 /48;2606:2800:602b:0000:0000:0000:0000:0000 /482/6/14 18:46
AsiaTokyo (NRT2)HND192.16.4.0 /24;192.16.5.0 /242606:2800:6022:0000:0000:0000:0000:0000 /485/13/14 4:43
AustraliaMelbourneMEL192.16.2.0 /242606:2800:6032:0000:0000:0000:0000:0000 /476/3/13 16:37
AustraliaSydneySYD110.232.179.0 /24;117.18.235.0 /242606:2800:6030:0000:0000:0000:0000:0000 /474/10/13 19:22
EuropeAmsterdamAMS46.22.70.0 /24;46.22.72.0 /23;93.184.208.0 /24;93.184.209.0 /24;93.184.217.0 /242606:2800:5040:0000:0000:0000:0000:0000 /478/27/14 1:30
EuropeAmsterdam (AMS2)RTM192.16.52.0 /24;192.16.53.0 /242606:2800:5041:0000:0000:0000:0000:0000 /488/27/14 1:30
EuropeCopenhagenCPH194.255.210.64 /262001:2011:c002:0000:0000:0000:0000:0000 /4810/1/13 19:42
EuropeFrankfurt (FRA2)FCN5.104.64.0 /23;192.229.159.0 /242606:2800:5070:0000:0000:0000:0000:0000 /475/13/14 4:44
EuropeFrankfurt (FRF)FRF192.229.134.0 /24;192.229.135.0 /242606:2800:5021:0000:0000:0000:0000:0000 /482/11/15 20:35
EuropeFrankfurt (Peering)FRA72.21.89.0 /24;93.184.212.0 /24;93.184.213.0 /242606:2800:5020:0000:0000:0000:0000:0000 /4812/4/14 22:25
EuropeHelsinkiHEL88.194.45.128 /262001:2060:bffb:0000:0000:0000:0000:0000 /4810/1/13 19:43
EuropeLondonLHR5.104.71.0 /24;46.22.74.0 /23;93.184.210.0 /242606:2800:5010:0000:0000:0000:0000:0000 /484/22/14 21:19
EuropeLondon (LHR2)LCY72.21.90.0 /24;93.184.211.0 /24;192.16.28.0 /24;192.16.29.0 /242606:2800:5011:0000:0000:0000:0000:0000 /485/13/14 4:44
EuropeMadridMAD46.22.66.0 /232606:2800:5000:0000:0000:0000:0000:0000 /4810/27/14 18:51
EuropeMadrid (MAD2)TOJ192.229.136.0 /24;192.229.137.0 /242606:2800:5001:0000:0000:0000:0000:0000 /4810/8/14 0:55
EuropeMilanMXP192.16.14.0 /24;192.16.15.0 /242606:2800:5080:0000:0000:0000:0000:0000 /4810/31/13 5:36
EuropeParisCDG46.22.68.0 /24;93.184.214.0 /242606:2800:5030:0000:0000:0000:0000:0000 /482/25/14 21:19
EuropeParis (CDG2)ORY5.104.66.0 /24;5.104.67.0 /242606:2800:5032:0000:0000:0000:0000:0000 /475/13/14 4:44
EuropeStockholmSTO213.64.234.0 /26;213.65.58.192 /262001:2040:c006:0000:0000:0000:0000:0000 /4810/1/13 19:43
EuropeStockholmARN5.104.69.0 /24;5.104.70.0 /242606:2800:5060:0000:0000:0000:0000:0000 /474/10/13 19:22
EuropeViennaVIE5.104.68.0 /24;108.161.242.0 /232606:2800:5050:0000:0000:0000:0000:0000 /474/10/13 19:22
EuropeWarsawWAW192.16.22.0 /24;192.16.23.0 /242606:2800:5090:0000:0000:0000:0000:0000 /481/31/14 18:26
North AmericaAshburnDCA68.232.36.0 /24;72.21.83.0 /24;108.161.254.0 /242606:2800:4200:0000:0000:0000:0000:0000 /483/27/14 21:54
North AmericaAshburn (DCA2)IAD198.7.24.0 /24;198.7.25.0 /242606:2800:4202:0000:0000:0000:0000:0000 /485/13/14 4:43
North AmericaAtlantaATL72.21.88.0 /24;72.21.93.0 /24;108.161.252.0 /242606:2800:4220:0000:0000:0000:0000:0000 /476/5/14 0:09
North AmericaAtlanta (ATL2)FTY192.16.46.0 /24;192.16.47.0 /242606:2800:4248:0000:0000:0000:0000:0000 /485/13/14 2:49
North AmericaChicagoORD46.22.76.0 /24;68.232.38.0 /24;72.21.87.0 /242606:2800:4210:0000:0000:0000:0000:0000 /479/7/13 1:21
North AmericaChicago (ORD2)MDW198.7.18.0 /24;198.7.19.0 /242606:2800:4212:0000:0000:0000:0000:0000 /485/13/14 4:43
North AmericaDallasDFW68.232.39.0 /24;72.21.86.0 /24;108.161.244.0 /242606:2800:4100:0000:0000:0000:0000:0000 /488/27/13 21:51
North AmericaDallas (DFW2)FTW108.161.250.0 /23;192.229.132.0 /242606:2800:4102:0000:0000:0000:0000:0000 /475/13/14 4:44
North AmericaLos AngelesOXR192.229.130.0 /24;192.229.131.0 /242606:2800:4001:0000:0000:0000:0000:0000 /487/22/14 18:31
North AmericaLos AngelesBLA192.16.10.128 /25;192.16.10.224 /272606:2800:4048:0000:0000:0000:0000:0000 /4810/23/14 0:37
North AmericaLos AngelesBUR108.161.240.0 /24;108.161.241.0 /24;108.161.253.0 /24;192.16.60.0 /242606:2800:4002:0000:0000:0000:0000:0000 /484/10/13 19:22
North AmericaLos AngelesLAX46.22.69.0 /24;68.232.40.0 /24;72.21.84.0 /24;72.21.94.0 /24;93.184.218.0 /242606:2800:4000:0000:0000:0000:0000:0000 /489/7/13 1:20
North AmericaLos Angeles (LAX2)CPM108.161.248.0 /23;192.16.51.0 /242606:2800:4004:0000:0000:0000:0000:0000 /47;2606:2800:4008:000e:0000:0000:0000:0000 /1275/13/14 4:45
North AmericaMiamiMIA46.22.64.0 /23;198.7.23.0 /242606:2800:4230:0000:0000:0000:0000:0000 /471/29/14 23:55
North AmericaMiami (MIA2)FLL192.16.6.0 /24;192.16.7.0 /24;192.229.161.0 /242606:2800:4232:0000:0000:0000:0000:0000 /485/13/14 4:46
North AmericaNew York (EWR)EWR198.7.20.0 /232606:2800:4242:0000:0000:0000:0000:0000 /48;2606:2800:4244:0000:0000:0000:0000:0000 /482/11/15 20:34
North AmericaNew York (LGA)LGA68.232.37.0 /24;192.16.18.0 /24;192.16.19.0 /242606:2800:4246:0000:0000:0000:0000:0000 /48;2606:2800:424f:0000:0000:0000:0000:0000 /482/11/15 20:35
North AmericaNewark (BNJ)BNJ192.229.147.0 /242606:2800:424d:0000:0000:0000:0000:0000 /489/10/14 17:21
North AmericaNewark (CSTG)CNJ192.229.146.0 /242606:2800:424c:0000:0000:0000:0000:0000 /489/2/14 18:12
North AmericaPhiladelphiaPHL192.229.156.0 /24;192.229.157.0 /242606:2800:4250:0000:0000:0000:0000:0000 /4812/18/14 22:54
North AmericaSan JoseSJC46.22.78.0 /24;46.22.79.0 /24;198.7.22.0 /242606:2800:4010:0000:0000:0000:0000:0000 /486/27/14 16:37
North AmericaSan Jose (SJC2)RHV192.229.128.0 /24;192.229.129.0 /242606:2800:4011:0000:0000:0000:0000:0000 /486/27/14 16:38
North AmericaSeattleSEA72.21.85.0 /24;108.161.246.0 /24;198.7.28.0 /242606:2800:4020:0000:0000:0000:0000:0000 /478/1/14 19:12
North AmericaSeattle (SEA2)PAE192.16.54.0 /24;192.16.55.0 /242606:2800:4021:0000:0000:0000:0000:0000 /48;2606:2800:4022:0000:0000:0000:0000:0000 /48;2606:2800:4023:0000:0000:0000:0000:0000 /48;2606:2800:4024:0000:0000:0000:0000:0000 /488/30/14 3:32
South AmericaSao PauloCGH192.16.41.0 /24;192.16.42.0 /242606:2800:420b:0000:0000:0000:0000:0000 /485/1/14 17:22

 

 

Upload

What formats are supported for uploads?

Your video can be uploaded to the Jive Video Service if it uses a supported container type, video codec, and audio codec.


  • Supported video container types: AVI, MOV, WMV, MP4, MPEG, FLV, F4V, 3GP, and 3G2.
  • Supported video codecs: all of the popular MPEG-4 variants like DivX, XviD, H264, 3IVX, and MSMPEG4, plus Windows Media 9.
  • Supported audio codecs: MP2, MP3, WAV, AAC (typically seen in QuickTime files), Windows Media audio, and, for mobile devices, AMR in both narrow-band and wide-band varieties.

 

What is the max video upload size?

Unlimited.  Timeouts and other undesirable behaviors can happen with large video uploads (> 1GB), but those are generally attributed to internet/network/browser issues.

 

What are the optimal upload video settings?

The best thing to do is resize the video to the target width of 768. Do not perform any pre-compression on the video before uploading.

 

How is video encoded? Bit rate? FPS? Size? What is the resolution?

H.264 @ 500kbps, audio quality 64.0 kpbs.  The player is sized at 400x333 for pre-4.5 and 500x328 for 4.5  and the video has a resolution width of 768.

 

Playback

 

I uploaded a video.  When I can I watch it?  (How long does it take to encode a video?)

Double the time of the video length.  After you have successfully uploaded a video, the system encodes the file into a format that is optimized for web playback.

 

What is the accepted maximum length of time for a video to load?

This is dependent on network/bandwidth, though is generally ~5-10 seconds.

 

How are the videos played back? Via Flash or something else?

Jive has full support for HTML5 video playback, with a flash player as a fallback.

 

Do you stream or use progressive playback?

Stream

 

What is the definition of a stream?  Is it when a person watches a video?  If a person plays a video over again, is it two streams, or is it just picked up from a browser local cache?

A stream is the initiation of a playback, regardless of how much of the video is watched.  It is not cached at the browser.

 

What network protocol is used for streaming of videos?

Videos are streamed using real time messaging protocol (RTMP), which runs on port 1935.  It also falls back to port 80 (RTMPT) if 1935 is unavailable.

 

What video sizes are supported, and what quality do you stream?

Videos will be converted to fit in a 768x640 format.

CodecWidthVideo QualityAudio Quality
H.264 Hi-Res768 px500 kbps64.0 kbps

What is the minimum bandwidth required?

At a minimum 2Mbps is required to play videos but recommend bandwidth should be about 4Mbps for best playback. If available bandwidth is less than the minimum amount required, video will buffer and users will get a buffering indicator in the player.

How much video can be watched per gigabyte of bandwidth used?

Convert kilobits/second into gigabytes/second:

  • 500 kilobits =  62.5 kilobytes = .061 megabytes = .00006 gigabytes
How many seconds it takes to fill up one gigabyte:
  • 1 gigabyte / .00006 = 16666 / 60 = 277 minutes = 4.61 hours of video per gigabyte

 

Does the Jive Video Module include content delivery network (CDN) services?  Does Perceptive Media (Twistage) work with Akamai?

There is no need for Akamai.  The video service includes CDN services through Edgecast. No additional fees or configuration are required to take advantage of this.

 

Storage

Where is the data actually stored?

The video files, both original and transcoded renditions are saved to Amazon S3. For EU customers, Ireland AWS region is used, while for US customers we us US Standard (N. Virginia) region. In addition, rely on Amazon S3’s data durability policies for backups (https://aws.amazon.com/s3/faqs/#data-protection_anchor).  The videos also reside within the CDN for a limited time, as the CDN caches the videos themselves to optimize video delivery.

 

Which CDN is used?

We currently use Edgcast for video delivery.

 

Do you store the original video or just the final encoded version for playback?

We do not delete the original upon encoding it, storing both the original video and the encoded version.  We keep both so in the event we switch to different encoding we can re-encode from source without losing quality.

 

Are there storage guidelines based on volume of videos?

The size of the video, in bytes, depends on a variety of factors, but the two most significant factors are the duration and the quality of the video (as specified bitrate). A sample calculation for 30 seconds of video:

 

30 seconds x 500kbps / 8 kilobits per kilobyte = 1875KB

1875KB / 1024KB per MB = 1.8MB

 

The container that holds the video streams adds ~10% overhead.

1.8MB x 1.1 = 2MB

 

So, you can take the size of the source in MB and add 2MB and have a reasonable estimate regarding the storage used.

 

 

Security

 

How are my videos secured?

The video service uses authenticated streaming for delivering video content. Before the CDN begins playback of a video, it validates the requesting user's authentication token with the Jive instance that is associated with the video. This ensures that your video content cannot be viewed by users that are not members of your Jive community.

 

Does the Video Module support SSL?

Yes, the video module supports video playback over SSL 3.0 connections.

 

Does the Video Module support TLS 1.1+?

No, not currently (as of April 2015). If you disable SSL 3 support in your network then video playback will not function. Twistage has an effort underway to enable it, however an ETA has not been set.

 

 

Other

 

Can users download videos for offline viewing?

No.  Downloading video assets is not currently supported.

 

How can we monitor usage?

Creation, view, rating, and bookmarking activities are available through the analytics datamart.

 

Can you email me usage or utilization daily alerts? How do I get set up for that? Can I get that through the Jive Community?

Automated reporting is not available at this time.

 

Can I use the in-video advertising feature provided by Twistage?

No, not out of the box.  This would require a Professional Services customization.

jive-ask-a-question.png

Outcomes