Results 1 to 2 of 2

Thread: Configure origin repeater url and packetizer

  1. #1

    Default Configure origin repeater url and packetizer

    Hi there I am working with a custom module which seems to be setting a repeater path but then for some reason initiating an rtmp stream from the origin. I believe wowza would do this internally correct ? ie

    instance.getMediaCasterStreams().acquire

    ...

    rtmpStream.play

    Also within the play method

    public void play

    its trying to setup the rtmpstream also ?

    I believe by doing this its causing the origin to lose connection and the HLS to drop out.

    Creating the rtmp stream here is not necessary I think correct ?

    Also regarding to the HLS packetizer if I set it to the repeater packetizer

    ie

    <LiveStreamPacketizers>cupertinostreamingrepeater, smoothstreamingrepeater, sanjosestreamingrepeater, mpegdashstreamingrepeater</LiveStreamPacketizers>

    Is this being done on the edge server or from the origin ? I presume it would be happening on the edge server.

    So when the application starts up if I simply just manage dynamically the original server url with authentication as a query string, wowza should handle the rest correct, no requirement to try and start an rtmp stream from the origin ?

    setRepeaterOriginUrl
    setRepeaterQueryString

    Hopefully this isn't confusing thanks.

  2. #2
    Join Date
    May 2013
    Posts
    680

    Default

    Hello

    While I'm not 100% clear on the problem(s) you are having, I've attempted to address your concerns below:

    > instance.getMediaCasterStreams().acquire

    If you are just trying to initiate a connection via stream file, I'd recommend using the following api.

    > public void play

    This event handler will be invoked when a rtmp playback connection is initiated. I'm not sure what you are doing in the handler but it shouldn't inhibit the existing stream. I'd wonder if you are being sure to execute the invokePrevious(this, client, function, params) method after you've completed your business logic there.

    > LiveStreamPacketizers

    The repeaters are necessary for a liverepeater-edge application type. So you can identify the origin via the OriginURL element within your application.xml or can extend functionality further by using the IMediaStreamNameAliasProvider2 interface.

    Thanks,
    Matt

Similar Threads

  1. PCMU depacketizer and packetizer
    By cmasque in forum General Forum
    Replies: 9
    Last Post: 03-18-2015, 11:44 PM
  2. Live Repeater Origin-Edge and HTTP Caching Origin
    By vjagannathan in forum General Forum
    Replies: 3
    Last Post: 06-18-2014, 02:56 AM
  3. Origin/Edge: "illegal" characters in the Origin URL?
    By HelderConde in forum General Forum
    Replies: 4
    Last Post: 05-09-2014, 06:08 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
  •