Notification Question: Strobeplayer rtmp url pointing to edge server, player resides on separate web server

  • 1
  • Question
  • Updated 6 years ago
  • Answered
Is it possible to setup notification emails that look like the following?

webserver.domain.com/playerContent/strobe/10.1/StrobeMediaPlayback.swf?src=rtmp://edgeserver.domain.com:1935/vod/published/camrelay

If so, how?

"edgeserver" is running Wowza Media Server
"webserver" is an IIS server hosting a copy of StrobePlayer


Photo of scott

scott

  • 3 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of Walter Pelowski

Walter Pelowski, Customer Solutions Engineer

  • 226 Posts
  • 19 Reply Likes
Scott,

  Please email me with your phone number because we'll probably have to have a call about this to see if we can accomplish what you're trying to do.  I assume the last part of the querystring URL is the path to the Relay video?  /camrelay/RELAYVIDEONAME.mp4?

Walter Mitchell Pelowski
w.pelowski@techsmith.com
Customer Solutions Engineer
http://www.techsmith.com

Photo of scott

scott

  • 3 Posts
  • 0 Reply Likes
Thank you for the reply, but no need, I figured this out...  

I needed to create the following global variables:

{g:edgeHost} edgeserver.domain.com
{g:edgePort} 1935
{g:rtmpUrl} rtmp

Then, I set the publish account URL to:

webserver.domain.com/playerContent/strobe/10.1/StrobeMediaPlayback.swf?src={g:rtmpUrl}://{g:edgeHost}:{g:edgePort}/vod/published/mp4:camrelay


This way, the system doesn't state that my output URL is invalid.  



Photo of Walter Pelowski

Walter Pelowski, Customer Solutions Engineer

  • 226 Posts
  • 19 Reply Likes
Scott,

  That's an interesting work-around that you found.  We currently do not test URLs that have variables in the path (as many variables will be determined at run-time) and your solution allows it to then match our regular expression used for validation.  I trust that you did test the output URL and it still worked as expected?

  We can look to update this regex for future versions.  We honestly never intended it to be used to pass another file along the querystring; that wasn't one of our use-cases, but I'm glad you were able to get it to work.

Walter Mitchell Pelowski
Customer Solutions Engineer
http://www.techsmith.com

Photo of scott

scott

  • 3 Posts
  • 0 Reply Likes
Yes it has tested to work properly.

 

Another note:  Although it doesn't relate to our current use case, it would be a nice feature to provide more flexibility in terms of where the player html should be deployed as opposed to what the Output path and Output URL defines for the stream uri.  

When we deliver media over RTMP, or any other streaming protocol that Wowza supports, the player page that actually gets sent to the client isn't going to come from the same server that hosts the stream.  Rather than emailing the presenter a link the stream uri, and leaving it up to them as to how they will embed it on a page, it would nice if we could direct them to the address that hosts the player page, which would already be customized to use the stream as it's source.  

This would also give us the ability to lock down access to individual player.html files that have been pre-configured to load only the stream configured within them.  We could then use (in flash) secure tokens and url obfuscation to secure the actual stream back to Wowza.

For example: Camtasia would create the necessary player file, updating the netConnection and url parameters with the value taken from Output URL.  Then, Camtasia would publish the MP4 file out to the streaming server using the value from Publish URL.  Next, Camtasia would publish the customized player html to the webserver, and send the presenter a link to the player.


Photo of Walter Pelowski

Walter Pelowski, Customer Solutions Engineer

  • 226 Posts
  • 19 Reply Likes
Scott,

  Thank you for the suggestion.  As you can tell, this is not a usage case that we've optimized for our product experience this far.  It is something that we may consider for future release if/when it makes sense for us to do that.

  If you want to send me your email address, I'll add it to my list of subject matter experts because we would probably want to get your opinion on this functionality if/when we decide to implement it.

  Thanks.

Sincerely,
Walter Mitchell Pelowski
w.pelowski@techsmith.com
Customer Solutions Engineer
http://www.techsmith.com

This conversation is no longer open for comments or replies.