Changing RTMP port from default 1935

1,073 views
Skip to first unread message

Hannu-Pekka

unread,
Aug 15, 2011, 1:47:11 AM8/15/11
to BigBlueButton-Setup
I've successfully changed Red5 to listen for RTMP on a different port
by editing file /usr/share/red5/conf/red5.properties

Then I added :port to every uri-attribute in /var/www/bigbluebutton/
client/conf/config.xml

Now the only problem seems to be the porttest-node in /var/www/
bigbluebutton/client/conf/config.xml. From what I've experimented, it
seems that the port number is hardcoded when executing this port test.
So if Red5's RTMP-port is changed this test fails every time.
BigBlueButton seems to require this test to be successful since
commenting the line out does not work either.

Any ideas how to get this to work?

Hannu-Pekka

unread,
Aug 15, 2011, 2:08:09 AM8/15/11
to BigBlueButton-Setup
Also, forgot to mention, tunneling through port 80 doesn't seem to be
working. Client is able to load BBB demo page but not join demo
meeting. Using version 0.71a

shi.chen

unread,
Aug 15, 2011, 5:40:30 AM8/15/11
to bigbluebutton-setup
bigbluebutton-setup,你好
 
Hi The 1935 port is Hardcode ..
You can check the source code from red5 website.
 
If you want to modify, You could only build red5 again.
 
refer to
 
 
 
 
 
2011-8-15
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To post to this group, send email to bigbluebu...@googlegroups.com.
To unsubscribe from this group, send email to bigbluebutton-setup+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bigbluebutton-setup?hl=en.

Reply all
Reply to author
Forward
0 new messages