Results 1 to 5 of 5

Thread: Stream Name Alias Over riding RTMP Push Stream

  1. #1

    Default Stream Name Alias Over riding RTMP Push Stream

    Hi There,

    I'm having a problem with the Stream Name Alias AddOn over riding a Push RTMP Authenticated Stream Name.

    I've created a live repeater-origin application and setup RTMP Authentication, Secure Token between the origin and edge servers and also setup Stream Name Alias within the live repeater-origin application.

    Before setting up the stream name alias module in the origin application, I would use the streammanager and start a stream under the application with name "rtmp-live" for example. Using wirecast, I could publish an RTMP live stream using the username and password in publish.password file and it worked fine.

    Other IP cameras that I was streaming live, I would put the RTSP url into files with .stream extensions in the content folder. Now that I have implemented the stream name alias addon module, I have all of the IP cams in the conf/aliasmap.stream.txt file like so:

    # Default Rule = *=${Stream.Name}
    # IP Cam RTSP Stream Alias File
    # ++ China Cams ++
    ipcamera1=rtsp://user:password@ip:554/media/video1
    ipcamera2=rtsp://user:password@ip:554/media/video1

    This works just fine for all of the IP cams. It seems now that when I use the streammanager and start a stream under the origin application with the name ramp-live for example... that the server is getting confused and not seeing that name in the alias map.stream.txt file. So when I try to publish the RTMP Authenticated feed using wirecast, it doesn't work.

    I don't want to have to create a separate liverepeater-origin application for the wirecast published RTMP feeds... I would rather keep all of the RTMP and IP camera feeds published into the one liverepeater-origin application and the same edge server application on each edge server that I bring up. Following are some of the logs. Any assistance would be much appreciated.

    Thank you,

    Tim



    2012-02-25 21:19:52 UTC comment server INFO 200 - ModuleStreamNameAlias.nameToAlias[play]: streamName:iphone-live alias:{pattern: "*" alias:"${Stream.Name}" wildcardMatches:{[0]: "iphone-live"}} result:iphone-live - - - 456.859 - - - - - - - - - - - - - - - - - - -
    :q!
    2012-02-25 21:19:53 UTC comment server INFO 200 - ModuleStreamNameAlias.nameToAlias[stream]: streamName:iphone-live alias:{pattern: "iphone-live" alias:"iphone-live" wildcardMatches:null} result:iphone-live - - - 458.311 - - - - - - - - - - - - - - - - - - - -
    2012-02-25 21:19:56 UTC comment server INFO 200 - ModuleStreamNameAlias.nameToAlias[stream]: streamName:iphone-live alias:{pattern: "iphone-live" alias:"iphone-live" wildcardMatches:null} result:iphone-live - - - 461.354 - - - - - - - - - - - - - - - - - - - -
    2012-02-25 21:19:56 UTC comment server INFO 200 - ModuleStreamNameAlias.nameToAlias[stream]: streamName:iphone-live alias:{pattern: "iphone-live" alias:"iphone-live" wildcardMatches:null} result:iphone-live - - - 461.455 - - - - - - - - - - - - - - - - -
    Last edited by rrlanham; 02-25-2012 at 04:08 PM.

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Seems like you using StreamManager to start streams that you are publishing to Wowza with StreamManager, which is not correct.

    You can use one application to start (pull) MediaCaster streams (your IP cams in this case), and publish (push) RTMP or RTP streams to Wowza with an encoder like Wirecast. But for the Wirecast streams, do not start them in StreamManager. The conf/aliasmap.stream.txt pertains to MediaCaster streams, not push streams as Wirecast produces. Just avoid using any alias that is the same as stream name you are going to publish to Wowza with Wirecast

    Richard

  3. #3
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    btw, I disabled smilies in your post, so the URLs do not embedded smilies, is why I show up as editing.

  4. #4

    Default

    Quote Originally Posted by rrlanham View Post
    btw, I disabled smilies in your post, so the URLs do not embedded smilies, is why I show up as editing.
    Richard,

    You are a miracle worker! Thank you. That did the trick. I didn't realize that I didn't have to enter the RTMP push (Wirecast) stream into the streammanager.

    Thanks again,

    Tim

  5. #5
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Tim,

    Cool! Thanks for the update. Glad it's working.

    Richard

Similar Threads

  1. issue about push rtmp stream to Akamai CDN.
    By markyao in forum AddOn: Other AddOns
    Replies: 2
    Last Post: 01-05-2012, 07:29 PM
  2. Push the wowza RTMP stream to FMS (Flah media server).
    By shekarkcb in forum Live Streaming and Encoder Discussion
    Replies: 1
    Last Post: 10-28-2011, 11:02 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •