Quantcast
Viewing all articles
Browse latest Browse all 7410

liveStreaming API

Hi jess,

my contact responsible for the customers ‘on-premise’ setup setup a livestream entry and provided me a rtmp link of the form

rtmp://live1.kaltura.xxxxx.net:1935/kLive/?p=201&e=0_heoi78ld&i=0&t=660be99b

there are no IP restrictions for this entry whatsoever. using your ffmpeg example together with this url fails anyway (as a similar gstreamer pipeline fails):

ffmpeg -re -i /path/to/some.mp4 -c:v copy -c:a libmp3lame -f flv -rtmp_live 1 rtmp://live1.kaltura.xxxxx.net:1935/kLive/?p=201&e=0_heoi78ld&i=0&t=660be99b

on network level, it looks like this:

  • client sends handshake C0+C1, ACK by server
  • server sends handshake S0+S1+S2, ACK by client
  • client sends connect(’/kLive/?p=201&e=0_heoi78ld&i=0&t=660be99b’), ACK by server
  • server sends _result(‘Netconnection.connect.success’), ACK by client
  • client sends releaseStream(’’) + FCPublish(’’) + createStream(), ACKs by server
  • server sends onFCPublish() + _result(), ACK by client
  • clients sends publish(’’)
  • server sends ‘Stream Begin’
  • servers sends TCP FIN, ACK = closes tcp connection <----------------------------********* --------------------
  • clients sends FCUnpublish() + deleteStream()

do you have any idead what is wrong here on protocol level? are there any possibilities to debug this stuff on the rtmp server side?

regards
harald glanzer


Viewing all articles
Browse latest Browse all 7410

Trending Articles