followed this doc http://blog.wmspanel.com/2015/12/rtsp-publish-control-setup.html to set up publish control framework.
executed python publish_signature_generator.py to create publisher signature. see setup of publish_signature_generator.py file below:
from time import gmtime, strftime
id = "clydelive"
ip = ""
password = "l1v3"
m = md5.new()
m.update(id + stream_name + password + ip)
base64hash = base64.b64encode(m.digest())
urlsignature = "id=" + id + "&sign=" + base64hash + "&ip=" + ip
base64urlsignature = base64.b64encode(urlsignature)
initial_url = "rtsp://126.96.36.199:554/live/clydelive"
signedurlwithvalidinterval = initial_url + "?publishsign=" + base64urlsignature
when i attempt to connect to nimble streamer from larix using,
i get error in larix window saying "unknown connection failure" and does not connect.
nimble log says the following:
[2016-08-04 07:23:36 P5234-T5251] [rtsp] E: invalid(signature match) publishsign=[aWQ9Y2x5ZGVsaXZlJnNpZ249QVB1TEk4bDRjUGd4RlBaU1RDV0RBdz09JmlwPQ==], for [/live/clydelive][188.8.131.52]
[2016-08-04 07:23:36 P5234-T5251] [rtsp] E: url auth failed, url=rtsp://184.108.40.206:554/live/clydelive?publishsign=aWQ9Y2x5ZGVsaXZlJnNpZ249QVB1TEk4bDRjUGd4RlBaU1RDV0RBdz09JmlwPQ== client=22
i can steam find using single application with publishing credentials.
can someone point me in the right directions?
Please upgrade your server to the latest version, you should be able to publish the stream using URL you generated after the upgrade.
what are you talking about? i keep my server and all installed software up to date.
what is publish control framework validating against other than what is listed in publish_signature_generator.py?
Does anything need to be added to nimble.conf/rules.conf to turn on publish control framework feature? I will search the docs again!
BTW! my servers are aws cloud instances.
I mean you need to upgrade Nimble Streamer to the latest version, you have not the latest one installed now.
I guess I need to download a new version from your site?
apt-get on debian jessie tells me i have the latest at Version: 3.0.6-6
Please run "apt-get update" first and then "apt-get install nimble".
The latest available version in the repository now is 3.0.7-11
have run the commands from above multiple times. no change.
still shows Maintainer: Max Tomilov <email@example.com>
uname Linux sw1.blackswann.net 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux
BINGO! Connecting fine via Publish Control Framework.
I followed the same doc but ported the script to php.
Every time I try to connect via Obs i get the invalid(signature match) error.
- I created an application "myapp"
- I added "myapp" to the control section with pw 55555
- generated my signature
$uuid = Uuid::uuid5(Uuid::NAMESPACE_DNS,'example.org');
$id = $uuid->toString();
$password = "55555";
$stream_name = '/myapp/live';
$hash = md5($id . $stream_name . $password);
$base64Hash = base64_encode($hash);
$urlsignature = "id=" . $id . "&sign=" . $base64Hash;
$base64urlsignature = base64_encode($urlsignature);
$initial_url = "rtmp://192.168.178.45:27001".$stream_name;
$signedurlwithvalidinterval = $initial_url ."?publishsign=" . $base64urlsignature;
- configured Obs:
url = rtmp://192.168.178.45:27001/myapp?publishsign=aWQ9YWFkMDM2ODEtOGI2My01MzA0LTg5ZTAtOGNhOGY0OTQ2MWI1JnNpZ249WlRFNU9EQXlNMlV6WXpjM05HUTJZemhoT0RoaU0yRmtNREUyWldNeFpqST0=
key = live
(I also tried other combinations but non of them work
Ok I found my error.
I misinterpreted the md5 function in python.
you have to use
$hash = md5($id . $stream_name . $password,true);
in php in order to get the raw output of md5
Thanks for clarifying. Please also take a look at the example from our github account to see the same usage of that function:
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the