node-rtsp-rtmp-server
node-rtsp-rtmp-server copied to clipboard
I cannot publish stream from Rtspclient
i use https://github.com/fyhertz/libstreaming and try to publish live streaming to RTSP Server (node) but it doesn't work.
What am I missing?
I've tried Spydroid app which is linked from that page, but the streaming didn't work on Android 6.0.1. Could you post a sample apk or an Android project?
https://www.dropbox.com/sh/f4hyolapb5smnbe/AAADqdQBgKgxVeaUZNQGR_vGa?dl=0
For the example app, it allow us to change setting for rtsp server address, port and stream name
I modified it, rtsp://
Is RTSP Server(node-rtsp-rtmp-server) allowing Record and receipt streaming that push by client?
thank you lizukanao,
Thanks. I've tried your code, but the RTSP library you are using is very buggy and server can't handle that unusual behavior. I don't recommend using that library.
I'm actually trying to accomplish the same. I notice that when starting up a stream, node-rtsp-rtmp-server (on port 87) shows the following from which I conclude it is going ok'ish;
2016-04-03 17:09:53.252 [rtsp/http/rtmpt:client=c16] connected 2016-04-03 17:09:53.254 Unknown (not implemented) SDP: i=N/A 2016-04-03 17:09:53.254 Error: rtpmap attribute in SDP must have audio channels; assuming 2 2016-04-03 17:09:53.265 [rtsp/http/rtmpt:client=c16] started uploading stream test
I can also see that my android phone running libstreaming is pushing data. This is configured to push to rtsp://ip:87/live/test
However, nothing seems to be recorded on disk (recording is enabled in the config) and opening the stream in VLC from node-rtsp-rtmp-server by navigating to rtsp://ip:87/live/test results in this message;
error: no data received in 10s, aborting
Would you be so kind as to enlighten us a bit on what's buggy about libstreaming? As it seems that data is sent, but node-rtsp-rtmp-server isn't picking it up for some reason. This could indeed very well be caused by libstreaming, but why?
Thank you for your assistance.
Some additional information from the android device;
04-04 14:34:32.970 3879-3897/? D/RtspClient: Connecting to RTSP server...
04-04 14:34:32.982 3879-3897/? I/RtspClient: ANNOUNCE rtsp://10.0.0.4:87/live/test RTSP/1.0
04-04 14:34:33.026 3879-3897/? D/RtspClient: Response from server: 200
04-04 14:34:33.026 3879-3897/? V/RtspClient: RTSP server name unknown
04-04 14:34:33.026 3879-3897/? I/RtspClient: SETUP rtsp://10.0.0.4:87/live/test/trackID=0 RTSP/1.0
04-04 14:34:33.035 3879-3897/? D/RtspClient: Response from server: 200
04-04 14:34:33.035 3879-3897/? D/RtspClient: Setting destination ports: 7044, 7045
04-04 14:34:33.035 3879-3897/? I/RtspClient: SETUP rtsp://10.0.0.4:87/live/test/trackID=1 RTSP/1.0
04-04 14:34:33.037 3879-3897/? D/RtspClient: Response from server: 200
04-04 14:34:33.037 3879-3897/? D/RtspClient: Setting destination ports: 7042, 7043
04-04 14:34:33.037 3879-3897/? I/RtspClient: RECORD rtsp://10.0.0.4:87/live/test RTSP/1.0
04-04 14:34:33.041 3879-3897/? D/RtspClient: Response from server: 200
04-04 14:34:33.846 3879-3897/com.example.mv96ti.test I/RtspClient: OPTIONS rtsp://10.0.0.4:87/live/test RTSP/1.0
04-04 14:34:33.850 3879-3897/com.example.mv96ti.test D/RtspClient: Response from server: 200
SDP:
v=0
o=- 0 0 IN IP4 null
s=Unnamed
i=N/A
c=IN IP4 10.0.0.4
t=0 0
a=recvonly
m=audio 7044 RTP/AVP 96
a=rtpmap:96 mpeg4-generic/8000
a=fmtp:96 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1588; SizeLength=13; IndexLength=3; IndexDeltaLength=3;
a=control:trackID=0
m=video 7042 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=42c029;sprop-parameter-sets=Z0LAKY1oCQNyAeEQjUA=,aM4BqDXI;
a=control:trackID=1
Thanks again.
@miinion were you able to achieve streaming using libstreaming.jar with node-rtsp-rtmp-server ?
no, i gave up. I finally decided to use RTMP instead
To use libstreaming, please follow these steps for now:
- Use ignore-port branch of node-rtsp-rtmp-server (this is a temporary branch for testing)
- Use the latest version of libstreaming
- In libstreaming, use UDP instead of TCP (apparently their TCP support is still experimental)