pullStream error
I\’m trying to make a simple connection test. using the command:
pullStream uri=rtsp://52.205.163.115:1935/7dias/0be3_610.stream keepAlive=1 localStreamName=test
I am sure the RTSP is valid, it runs on VLC and there is no connection issues with the AWS instance(tested pulling the stream with FFMPEG directly on the instance)
But I receive the following error:
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `sdplang` with value `en` not parsed
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `range` with value `npt=now-` not parsed
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `cliprect` with value `0,0,368,640` not parsed
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `framesize` with value `97 640-368` not parsed
/thelib/src/protocols/rtp/sdp.cpp:817 Video doesn\’t have sprop-parameter-sets
/thelib/src/protocols/rtp/sdp.cpp:98 Video track index high not found
/thelib/src/protocols/rtp/sdp.cpp:151 Audio track index high not found
/thelib/src/protocols/rtp/basertspappprotocolhandler.cpp:1439 No compatible tracks found
/thelib/src/protocols/rtp/rtspprotocol.cpp:397 Unable to handle content
/thelib/src/netio/epoll/tcpcarrier.cpp:91 Unable to read data from connection: (Far: 52.205.163.115:1935; Near: 10.109.203.205:39786) CTCP(26) <-> [TCP(365)] <-> RTSP(366). Signaling upper protocols failed Some metadata from the stream: rtsp, from \’rtsp://52.205.163.115:1935/7dias/0be3_610.stream\’:
Metadata:
title : 0be3_610.stream
Stream #0:0: Video: h264 (Baseline), yuvj420p(pc), 640×368, 15 fps, 10.25 tbr, 90k tbn, 30 tbc
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `range` with value `npt=now-` not parsed
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `cliprect` with value `0,0,368,640` not parsed
/thelib/src/protocols/rtp/sdp.cpp:516 Attribute `framesize` with value `97 640-368` not parsed
/thelib/src/protocols/rtp/sdp.cpp:817 Video doesn\’t have sprop-parameter-sets
/thelib/src/protocols/rtp/sdp.cpp:98 Video track index high not found
/thelib/src/protocols/rtp/sdp.cpp:151 Audio track index high not found
/thelib/src/protocols/rtp/basertspappprotocolhandler.cpp:1439 No compatible tracks found
/thelib/src/protocols/rtp/rtspprotocol.cpp:397 Unable to handle content
/thelib/src/netio/epoll/tcpcarrier.cpp:91 Unable to read data from connection: (Far: 52.205.163.115:1935; Near: 10.109.203.205:39786) CTCP(26) <-> [TCP(365)] <-> RTSP(366). Signaling upper protocols failed Some metadata from the stream: rtsp, from \’rtsp://52.205.163.115:1935/7dias/0be3_610.stream\’:
Metadata:
title : 0be3_610.stream
Stream #0:0: Video: h264 (Baseline), yuvj420p(pc), 640×368, 15 fps, 10.25 tbr, 90k tbn, 30 tbc
1 Answers
Hello,
From EMS point of view (in its current state), it is necessary to have audio track/video track/sps/pps in the SDP being sent during the RTSP handshake. Without those, EMS would not be able to properly establish an RTSP session needed to have a stream.
The SDP that the RTSP source gave to EMS is currently not supported because the video track defined in it did not have sps/pps parameter in it.