Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Wowza 4.0.1 origin->edge

  1. #1
    Join Date
    Aug 2011
    Posts
    116

    Default Wowza 4.0.1 origin->edge

    Hi
    I jave installed wowza 4.0.1
    In Wowza 3.5 I had the fallowing configuration:
    origin -> repeter ->edges
    becouse of the long distance i am doing the packetsizing on the repeter and from there to the edges
    my question is what type of application do I select for the repeter in wowza 4.0 is it live->live->edges?
    is it still preferd to do the packetsizing on the repeter becouse of the distance?

    thanks
    /Asaf

  2. #2
    Join Date
    Sep 2011
    Posts
    1,931

    Default

    Hi,
    You could have two live applications and then edges if you wanted using Wowza Streaming Engine 4.
    The setup would be as you described (live-live-edges) and you could use PushPublishing to get the streams from the first live application to the second and then use the second live application to packetize for the edges.
    Take a look at the Push Publishing Article for configuration instructions.

    Jason

  3. #3
    Join Date
    Aug 2011
    Posts
    116

    Default

    Hi jason
    can i in the second server publish a stream and in the stream file add the rtmp for the first server?
    does push publish has an advantage over that?

  4. #4
    Join Date
    Sep 2011
    Posts
    1,931

    Default

    Hi,
    If you would rather use .stream files to pull the streams from the origin to the second server that can be done without issue.
    Either way can be done and it's personal preference as to which way you would like to configure the servers.

    When using PushPublishing you will only have to manage one file on the origin server, when using .stream files on the second server you will have to create one for each stream.
    If you have many streams this will require you creating many .stream files.

    We have an article on How to create and use .stream files in Wowza Streaming Engine Manager

    Jason

  5. #5
    Join Date
    Aug 2011
    Posts
    116

    Default

    Hi
    What i am doing now is vlc->live->live
    in the first live i have a stream file for each stream i am geting from vlc for example in live1.stream is have udp://0.0.0.0:10010
    and on the second live live2.stream has rtmp://x.x.x.x:1935/live/live1.stream so far so good.
    i want to pushpublish from the first live to the second as you have already mentiand, but even after reading the articale i have hard time understanding how to config it correctly.
    I have the fallowing line: myStream={profile:"rtmp", streamName:"myStream", host:"www.mydestination.com"}
    and a couple of questions:
    does "myStream" points to udp://0.0.0.0:10010? (still need to create a stream file)
    how do i configure the second live server? do i need a stream file for each incoming rtmp stream for each of my channels?

    thanks
    /asaf

  6. #6

    Default

    Hi,

    If you are pulling a stream from one server to the other then you use .stream files on the second server that is pulling the stream in.

    If you are pushing a stream from one server to another then you don't use .stream files on the second server.

    In the push publish configuration, the name to the left of the = is the name of the source stream. On your live1 server, that would be live1.stream. On the second server that is receiving the stream, it will use the name that is defined by the streamName parameter.

    If you don't set the streamName parameter then it will use the same name as the source.

    You can simplify the push publish configuration by using the following line in your configuration that will forward all streams from the first server to the second and use the original stream name on the second server.

    *={profile:"rtmp", host:"[second-server-wowza-ip]", userName:"[second-server-publish-user-name]", password:"[second-server-publish-password]"}
    The * matches all incoming streams and because the streamName is not set, the original name will be used. I added userName & password parameters because the default setting with Wowza Streaming Engine >= 4.0 is to require these for publishing.

    Roger.

  7. #7
    Join Date
    Aug 2011
    Posts
    116

    Default

    Hi
    thnaks for the quick response.
    now that i have Implemnted the push publish it workes good in rtsp but haveing problems in hls.....

    if i watch it in vlc it workes good for a couple of minutes and then pauses for 10 sec.
    in android (it already worked good) I see every couple of sec a scramble picture....
    this what is ha ve in the logs:

    2014-03-03      11:26:29        EET     stop    stream  INFO    200     live22.stream   -       _defaultVHost_  live    _definst_       31.536  xxx.xxx.xxx.xxx  1935    http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     192.168.1.1  http (cupertino)        -       VLC/2.1.3 LibVLC/2.1.3  1892629731      0       2387046 23      1536894 0       2386096 live22.stream   -       -       -       -       -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -
    2014-03-03      11:26:29        EET     destroy stream  INFO    200     live22.stream   -       _defaultVHost_  live    _definst_       31.536  xxx.xxx.xxx.xxx  1935    http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     192.168.1.1  http (cupertino)        -       VLC/2.1.3 LibVLC/2.1.3  1892629731      0       2387046 23      1536894 0       2386096 live22.stream   -       -       -       -       -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -
    2014-03-03      11:26:29        EET     disconnect      cupertino       INFO    200     1892629731      -       _defaultVHost_  live    _definst_       1129.974        xxx.xxx.xxx.xxx  1935    http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     192.168.1.1  http (cupertino)        -       VLC/2.1.3 LibVLC/2.1.3  1892629731      0       2387046 -       1536894 -       -       live22.stream   -       -       -       -       -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -
    
    2014-03-03      11:26:38        EET     connect cupertino       INFO    200     1892629731      -       _defaultVHost_  live    _definst_       1138.433        xxx.xxx.xxx.xxx  1935    http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     192.168.1.1  http (cupertino)        -       VLC/2.1.3 LibVLC/2.1.3  1892629731      0       0       -       0       -       -       live22.stream   -       -       -       -       -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -
    2014-03-03      11:26:38        EET     create  stream  INFO    200     live22.stream   -       _defaultVHost_  live    _definst_       0.001   xxx.xxx.xxx.xxx  1935    http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     192.168.1.1  http (cupertino)        -       VLC/2.1.3 LibVLC/2.1.3  1892629731      0       0       24      0       0       0       live22.stream   -       -       -       -       -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -
    2014-03-03      11:26:38        EET     play    stream  INFO    200     live22.stream   -       _defaultVHost_  live    _definst_       0.412   xxx.xxx.xxx.xxx  1935    http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     192.168.1.1  http (cupertino)        -       VLC/2.1.3 LibVLC/2.1.3  1892629731      0       412     24      1564694 0       0       live22.stream   -       -       -       -       -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8     http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -       http://xxx.xxx.xxx.xxx:1935/live/live22.stream/chunklist_w1892629731.m3u8        -
    2014-03-03      11:26:40        EET     comment server  INFO    200     -       LiveMediaStreamReceiver.onResult: Error Connecting to remote server: code: NetConnection.Connect.Rejected       -       -       -       60560.259       -   --       -       -       -       -       -       -       -
    Also on the second live server i see something like this on the incoming streams: wowz://[live1-ip-adreess]:56798 for each stream is that normal?
    thanks
    /Asaf
    Last edited by asaf32; 03-03-2014 at 04:49 AM.

  8. #8
    Join Date
    Aug 2011
    Posts
    116

    Default

    Hi
    In your previous answer you have mentiand the asterisk option to include all my incomeing streams.
    that option does not work.

    please advice

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

    Default

    I think that only works in Wowza 4.0 and higher. It doesn't work in my test on 3.6.4.02, but does work in Wowza 4.0.0

    Richard

  10. #10
    Join Date
    Aug 2011
    Posts
    116

    Default

    dosn't work for.... also I have send an email to support and they told me that it's actully not working and there is a confusion with something about streamNameAlias
    Last edited by asaf32; 03-12-2014 at 03:52 AM.

Page 1 of 2 12 LastLast

Similar Threads

  1. Live Repeater Origin-Edge and HTTP Caching Origin
    By vjagannathan in forum General Forum
    Replies: 3
    Last Post: 06-18-2014, 02:56 AM
  2. Replies: 1
    Last Post: 10-10-2013, 11:34 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
  •