umair-khokhar / red5-screenshare

Automatically exported from code.google.com/p/red5-screenshare
1 stars 0 forks source link

confused 1935 or 5080 #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Screenshare.jar and jnlp
2.
3.

What is the expected output? What do you see instead?
I am running the red5 server ie localhost:5080 and then download your 
screenshare and to run it using do_run2.cmd that says ""C:\Program 
Files\Java\jdk1.6.0_24\bin\java" -classpath screenshare.jar 
org.redfire.screen.ScreenShare localhost screenshare 1935 screen_share flashsv2 
pause" command line that shows the screenshare java console and tried to 
connect "start sharing" but does not work through screenviewer.html
Let me know if you have any ideas 

What version of the product are you using? On what operating system?
red5 and Windows

Please provide any additional information below.

Original issue reported on code.google.com by AabhasG...@gmail.com on 7 Aug 2011 at 6:42

GoogleCodeExporter commented 9 years ago
Here is output errors as below 

Java Web Start 1.6.0_24
Using JRE version 1.6.0_24-b07 Java HotSpot(TM) Client VM
User home directory = C:\Users\aabhas
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
m:   print memory usage
o:   trigger logging
p:   reload proxy configuration
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
0-5: set trace level to <n>
----------------------------------------------------
User home C:\Users\aabhas
User Dir C:\Users\aabhas\Downloads
imgsun.awt.image.ToolkitImage@1da669c
initialized
captureScreenStart
ScreenShare startStream
[INFO] [pool-1-thread-1] org.redfire.screen.ScreenClientHandler - channel 
opened: [id: 0x0189c036] OPEN
[INFO] [New I/O client worker #1-1] 
org.redfire.screen.ScreenClientHandshakeHandler - connected, starting handshake
[INFO] [New I/O client worker #1-1] com.flazr.rtmp.RtmpHandshake - using client 
version 00000000
[INFO] [New I/O client worker #1-1] org.redfire.screen.ScreenClientHandler - 
handshake complete, sending 'connect'
[INFO] [New I/O client worker #1-1] org.redfire.screen.ScreenClientHandler - 
sending command (expecting result): [0 COMMAND_AMF0 c3 #0 t0 (0) s0] name: 
connect, transactionId: 1, object: {app=screenshare, flashVer=WIN 9,0,124,2, 
tcUrl=rtmp://localhost:1935/screenshare, fpad=false, audioCodecs=1639.0, 
videoCodecs=252.0, objectEncoding=0.0, capabilities=15.0, videoFunction=1.0}, 
args: null
[INFO] [New I/O client worker #1-1] org.redfire.screen.ScreenClientHandler - 
server command: _result
[INFO] [New I/O client worker #1-1] org.redfire.screen.ScreenClientHandler - 
result for method call: connect
[INFO] [New I/O client worker #1-1] org.redfire.screen.ScreenClientHandler - 
sending command (expecting result): [0 COMMAND_AMF0 c3 #0 t0 (0) s0] name: 
createStream, transactionId: 2, object: null, args: []
[INFO] [New I/O client worker #1-1] org.redfire.screen.ScreenClientHandler - 
channel closed: [id: 0x0189c036, /127.0.0.1:52888 => localhost/127.0.0.1:1935] 
CLOSED

Let me know 
Aabhas

Original comment by AabhasG...@gmail.com on 7 Aug 2011 at 6:49

GoogleCodeExporter commented 9 years ago
i had the same question . 
Let me know , please.
rocky

Original comment by tag...@gmail.com on 29 Aug 2011 at 7:04

GoogleCodeExporter commented 9 years ago
Make sure the RTMP application name and stream name are the same for both 
publisher and viewer

Original comment by olajide....@gmail.com on 3 Sep 2011 at 9:36

GoogleCodeExporter commented 9 years ago
I still have the same problem. Both names are the same. Any tips?

Original comment by emmanuel...@gmail.com on 24 Feb 2014 at 5:52