RTMP Connection doesn't continue

[laylash]

I tested the broadcaster with both red5 server and a python rtmp server, but am getting the following on the default values:

Context creation succeeded
RTMPStatus: 1
RTMPStatus: 2
RTMPStatus: 3
RTMPStatus: 4
RTMPStatus: 5
RTMPStatus: 6

received server bandwidth

Changing frame rate to 15 and bandwidth to 65000 gives the following result:
Context creation succeeded
RTMPStatus: 1
RTMPStatus: 2
RTMPStatus: 3
RTMPStatus: 4
RTMPStatus: 5
RTMPStatus: 6
received server bandwidth
received invoke _result
tracked command: connect
RTMPStatus: 7
received unknown packet type: 0x00
received invoke _result

tracked command: releaseStream

What can be wrong and should i change frame rate and bandwidth to other values?? or the problem is from the server??

[jgh-]

This appears to be related to #47

[jgh-]

It seems like some incompatibility with crtmpserver, red5 and a python rtmp server. Wowza, nginx-rtmp and Edgecast work fine at this time. I will have to set up these servers locally and do some testing.

[jgh-]

@laylash as of 0.1.10.3 I have changed the way that the commands are parsed, this may resolve your issue.

[laylash]

thanks i will give it a try

[gpwebresearch]

@laylash is it working on your end?

[laylash]

no it didn't work :(
am going to test on nignx-rtmp

[jgh-]

@laylash @gpwebresearch I installed red5 server and made some updates, we weren't handling invocations from RTMP Chunk Type 1 correctly. This should be fixed in 0.1.12, please test.

[gpwebresearch]

with evostream/crtmpserver I have the same issue.

received server window size: 1048576
received peer bandwidth limit: 2500000 type: 2
received ping, sending pong.
Received invoke
pktId: 1
received invoke _result
tracked command: connect
received unknown packet type: 0x1E
Received invoke
pktId: 2
received invoke _result
tracked command: releaseStream
received unknown packet type: 0x00

Thanks

[jgh-]

Hm, ok I'll try to get evostream setup and see what the issue is with that one.

[jgh-]

OK I see what the problem is, working on a fix for now.

[gpwebresearch]

Thanks! :)

On Sep 26, 2014, at 11:27 PM, james h notifications@github.com wrote:

OK I see what the problem is, working on a fix for now.

—
Reply to this email directly or view it on GitHub.