search

kaltura / server

The Kaltura Platform Backend. To install Kaltura, visit the install packages repository.
https://github.com/kaltura/platform-install-packages
GNU Affero General Public License v3.0
367 stars 173 forks source link

DeliveryProfile's URL instead of Entry's baseUrl #1412

Open visomar opened 10 years ago

visomar commented 10 years ago

I think when the entry uses a custom delivery profile, it should use the delivery's url attribute, instead of its own baseUrl.

As a test, I'm creating a livestream entry (MANUAL) and leaving the baseUrl (in the test console, streamUrl) empty. The protocol used is RTMP. Kaltura is creating a manifest with the field "baseUrl" = "rtmp://" instead of my DeliveryProfile's URL.

shaktidhar commented 9 years ago

It seems this is similar issue to https://github.com/kaltura/server/issues/1422 ... I am also getting errors and failure with rtmp being returned instead of the delivery profile's url.

visomar commented 9 years ago

No, it's not exactly the same. The issue you're having is related to the configuration of the delivery profiles. Have you tried to do all the steps sharonadar told you to do? Also, don't forget to review that the delivery profile created manually has your partner (it's created with partner -2).

The issue I'm reporting is, when the application uses a delivery profile created by you (and it's working for me, I checked), It should ignore the baseUrl field (as well as the other URL fields) of the entry. It's more like a way of proceeding instead of a bug, but I think if you want to use a different baseUrl for your entry, you could do a general delivery profile where you don't introduce any url and therefore use everytime the field filled in the entry.

Regards.