• Port 5080: HTTP (For example for file upload and download)
  • Port 1935: RTMP (Flash Stream and Remoting/RPC)

Additionally red5 uses some ports internally. However those ports are not in use by OpenMeetings by default.

Configure alternative ports

You need to change two files:

  • Server-Side configuration: $RED5_HOME/conf/red5.properties, you need to restart the red5-service so that changes are online.

Config-Name Default-value Name in red5.properties
HTTP 5080 http.port
RTMP 1935 rtmp.port

Preventing Firewall issues

A common way of bypassing the firewall is to change HTTP port to 80

A short description about the connection mechanism: The application first tries connecting to rtmp 3 times, because rtmp is the protocol that is less performance hungry. If that fails the application will fallback to rtmpT.

OpenMeetings over SSL

You can run OpenMeetings completely over SSL. See RTMPSAndHTTPS.

Back to top

Apache OpenMeetings, OpenMeetings, Apache, the Apache feather, and the Apache OpenMeetings project logo

are trademarks of the Apache Software Foundation.