Hi Jess,
Thank you for your patience and let me explain what I'm trying to do:
We have been long time users of Wowza and Kaltura. We have provided VOD services for some customers with Kaltura but not Live services. We used to provision our Wowza livestreams manually but now we want to integrate them with the Kaltura VOD platform.
The aim is to serve a relatively high volume traffic (more than 600 TB/month). We have setup our own frontend/delivery (CDN) mainly because of traffic cost issues. Akamai or any other alternatives are simply to expensive.
I have a production and a staging environments that are almost identical. Right now I have just upgraded to Kaltura 12 + latest Wowza (4.x) and installed the kaltura Wowza libs according to the instructions (in the same server).
Provisioning the live streams was the easy part. Y create an entry in Kaltura and Wowza is able to authenticate and receive the broadcast (FMLE or Wirecast).
What I haven't been able to do is to pass the correct delivery URL to the player. After debugging Kaltura, I noticed that Wowza was trying to register a media_server called localhost.localdomain. I went through the API console and added a server_node called localhost.localdomain with a mediaServerPlaybackDomainConfig called cdn01.calipso.com.co and Bingo ! Kaltura registered the stream and I was able to watch it with something live http://cdn01.calipso.com.co:1935/kLive/...
The problem is that we need to serve all the http traffic via ports 80 and 443, something that is relatively easy to do with our own frontend without modifying Wowza.
After configuring the Wowza ssl service, I got stuck with the problem that the HLS/APPLEHTTP delivery URLs are not modified when the media server gets registered. I guess is something related to the URL parsing because it affects the expressions with the HLS manifest (playlist.m3u8). All other default protocols get the right media_server URL. I get something like this:
KalturaLiveStreamConfiguration
hds
http://cdn01.calipso.com.co:8080/kLive/smil:0_0ck9iu4p_all.smil/manifest.f4m
KalturaLiveStreamConfiguration
hls
http://localhost.localdomain:1935/kLive/smil:0_0ck9iu4p_all.smil/playlist.m3u8
I tried adding different delivery__profiles via the admin console and mysql console but it doesn't work either. Right now I have just the default kaltura live delivery profiles:
mysql> select * from delivery_profile where partner_id=0;
| id | partner_id | created_at | updated_at | name | type | system_name | description | url | host_name | recognizer | tokenizer | status | media_protocols | streamer_type | is_default | parent_id | custom_data | priority |
+------+------------+---------------------+---------------------+------------------------------------------------+------+---
| 1 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HTTP Delivery Profile | 10 | Default_Akamai_HLS_direct | Default Akamai HLS direct | http://cloudvideodevl.cdn.net.co | cloudvideodevel.cdn.net.co | NULL | NULL | 0 | NULL | applehttp | 1 | 0 | NULL | 0 |
| 2 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HTTP Delivery Profile | 14 | Default HTTP Delivery Profile | Default HTTP Delivery Profile | http://cloudvideodevel.cdn.net.co | cloudvideodevel.cdn.net.co | NULL | NULL | 0 | NULL | http | 1 | 0 | NULL | 0 |
| 3 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HLS Live Delivery Profile | 1001 | Default_HLS_Live_Delivery_Profile | Default HLS Live Delivery Profile | | NULL | NULL | NULL | 0 | NULL | applehttp | 1 | 0 | NULL | 0 |
| 4 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HLS Network Live Delivery Profile | 1001 | Default_HLS_Network_Live_Delivery_Profile | Default HLS Nework Live Delivery Profile | NULL | NULL | NULL | NULL | 0 | NULL | hls | 1 | 0 | NULL | 0 |
| 5 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HLS To Multicast Live Delivery Profile | 1006 | Default_HLS_To_Multicast_Live_Delivery_Profile | Default HLS To Multicast Live Delivery Profile | | NULL | NULL | NULL | 0 | NULL | applehttp_to_mc | 1 | 0 | NULL | 0 |
| 301 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default MPEG-DASH Live Delivery Profile | 1003 | Default MPEG-DASH Live Delivery Profile | Default MPEG-DASH Live Delivery Profile | NULL | NULL | NULL | NULL | 0 | NULL | mpegdash | 1 | 0 | NULL | 0 |
| 302 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HD Network Live Delivery Profile | 1002 | Default_HD_Network_Live_Delivery_Profile | Default HD Network Live Delivery Profile | NULL | NULL | NULL | NULL | 0 | NULL | hdnetworkmanifest | 1 | 0 | NULL | 0 |
| 303 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default HDS Live Delivery Profile | 1002 | Default_HDS_Live_Delivery_Profile | Default HDS Live Delivery Profile | NULL | NULL | NULL | NULL | 0 | NULL | hds | 1 | 0 | NULL | 0 |
| 304 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Default RTMP Live Delivery Profile | 1005 | Default_RTMP_Live_Delivery_Profile | Default RTMP Live Delivery Profile | NULL | NULL | NULL | NULL | 0 | NULL | rtmp | 1 | 0 | a:1:{s:12:"enforceRtmpe";s:1:"0";} | 0 |
| 1001 | 0 | 2016-05-15 15:51:07 | 2016-05-15 15:51:07 | Kaltura HLS segmentation | 61 |
That's it. Sorry for the long post but I think it's easier to understand what I'm doing.The kaltura documentation does not explain clearly how the media server registration works so I'm stuck in that point.
Regards,
David