Error pulling RTSP streams using EvoStream 2.0

Written by on 16 Feb 2018. Posted in

Support Forum › Category: Integration and Customization › Error pulling RTSP streams using EvoStream 2.0

thachhoang asked 4 years ago

We are using EvoStream 2.0 to pull RTSP streams (only video, no audio). I have a .vod file in the media folder that looks like this:


    uri=rtsp://example.com/name.stream

When I try to play it from the VOD page of the EMS Web UI, the stream fails to load, and I see these errors in the logs:


    ..\..\..\sources\thelib\src\netio\iocp\tcpcarrier.cpp:78 Unable to read data from connection: (Far: 127.0.0.1:4000; Near: 127.0.0.1:64831) CTCP(476) <-> [TCP(157)] <-> OHTT2(158) <-> ORPC(159). EOF encountered

and


    ..\..\..\sources\thelib\src\protocols\rtp\sdp.cpp:151 Audio track index high not found

and


    ..\..\..\sources\thelib\src\protocols\rtp\streaming\innetrtpstream.cpp:97 Sampling rate: 90000.000000

At the same time, the HTML5 player repeatedly prints these debugging messages:


    1518726213286: No stream data. Restarting player...
    1518726205434: VIDEO stalled event triggered.
    1518726205434: VIDEO stalled event triggered.
    1518726202289: Media source is now ready.
    1518726202287: VIDEO loadstart event triggered.
    1518726202287: VIDEO loadstart event triggered.
    1518726202281: Initializing player...

For comparison, this is what a DESCRIBE for the stream looks like:


    DESCRIBE rtsp://example.com/name.stream RTSP/1.0


    RTSP/1.0 200 OK
    CSeq: 0
    Server: Wowza Streaming Engine 4.7.4 build21380
    Cache-Control: no-cache
    Expires: Thu, 15 Feb 2018 15:20:25 EST
    Content-Length: 365
    Content-Base: rtsp://example.com/name.stream/
    Date: Thu, 15 Feb 2018 15:20:25 EST
    Content-Type: application/sdp
    Session: 732878497;timeout=60
     
    v=0
    o=- 732878497 732878497 IN IP4 127.0.0.1
    s=name.stream
    c=IN IP4 0.0.0.0
    t=0 0
    a=sdplang:en
    a=range:npt=now-
    a=control:*
    m=video 0 RTP/AVP 97
    a=rtpmap:97 H264/90000
    a=fmtp:97 packetization-mode=1;profile-level-id=4D0029;sprop-parameter-sets=Z00AKeKQPBH9YC3AQEB4eJEV,aO48gA==
    a=cliprect:0,0,270,480
    a=framesize:97 480-270
    a=control:trackID=1

How should I configure this stream for successful pulling and playback? Thank you for your time.

6 Answers

0 Vote Up Vote Down

thachhoang answered 4 years ago

rjimenez, “rtsp://example.com/name.stream” is just an example, because I don’t want to post the actual stream URI here. I’ve sent the real stream URI to Ryan Go / sales@evostream.com. That stream is playable by VLC.

1 Vote Up Vote Down

erika Staff answered 4 years ago

Hi thachhoang, I tried to use your source. It happens to me as well. I recommend to add forceTcp=1 parameter in your pullstream command. The parameter will force a TCP connection. This works on my end.

pullStream uri=rtsp://example.com/name.stream keepAlive=1 localStreamName=test forceTcp=1

Hopefully this resolves your issue. Thank you!

0 Vote Up Vote Down

thachhoang answered 4 years ago

I can confirm that adding the parameter forceTcp=1 fixes the problem. Thanks for your help!

« Previous 1 2

Error pulling RTSP streams using EvoStream 2.0

CONTACT US

Offcanvas