JOTIcafe, the virtual cafe for scouts to meet. With JOTIcafe you can meet Scouts while chatting and talking with video.

JOTIcafe checklist

To ensure the best possible quality and to use JOTIcafe without any problems, use the following checklist. When you have followed the checklist you are fully prepared for JOTIcafe.

  • Make sure your webcam and microphone are connected and functional
  • Update your web browser to the latest version (We advise the use of Chrome or Opera)
  • Update Adobe Flash to the latest version
  • When speaking to other Scouts, use English as the main language.
  • Verify any network firewall to accept outgoing UDP traffic. See “Network issues” on the bottom of this page for more information (Only needed when using SOHO or corporate routers/firewalls)

Ready? Go! login 

JOTIcafe features and functions

  • Simple “click to connect” video with other Scouts
  • Chat channels for you region and language, country and continent, makes it easy to connect.

Demonstration video:


Network configuration and issues

JOTIcafe uses the protocol RTMFP to communication between clients and The Real-Time Media Flow Protocol (RTMFP) is a communication protocol from Adobe that enables direct end user to end user peering communication between multiple instances of the Adobe® Flash® Player client and applications built using the Adobe AIR® framework for the delivery of rich, live, real-time communication.

Not all firewalls will except outgoing UDP traffic. If you are using a “default” home or SOHO router to connect your clients to the Internet most of the times there is no problem and JOTIcafe will work.
If you have a more advanced router that also does a good job at fire-walling, JOTIcafe won’t work. The video won’t be able to connect to the public Internet.

UDP port 1935 and ports 10000+ are used by the servers. The UDP ports used on client computers could be any port from 1024 to 65535.

In order to just connect to the servers, you must be able to send and receive UDP packets with any UDP port on your client computer (source port for outgoing, destination port for incoming) and port 1935 and ports 10000+ on the JOTI servers (destination port for outgoing, source port for incoming).

*just* connecting to isn’t useful, though, since all it can do is help you to connect directly to other clients running JOTIcafe. Other client computers, just like your client computer, will be using a random UDP port in the range 1024..65535. Therefore, in order to communicate P2P with other client computers using JOTIcafe (RTMFP), you must do one of the two following things:

1) Allow all UDP with a source or destination port from 1024..65535.

2) Have a “stateful firewall” that allows bidirectional UDP connections to and from any UDP ports in the range 1024 through 65535 inclusive as long as a first packet is sent outbound through the firewall. This is commonly called “allowing outbound UDP”. Sending the first packet outbound through your firewall to allow return packets is commonly called “UDP hole punching”. Searching on these terms should give you more information.

in general, a firewall that blocks UDP will block RTMFP communication.

Our advice is to configure the following firewall rules to allow UDP traffic for;

purpose source service destination
Client to Client your client network RTMFP UDP 1024:65535 any
Client to your client network macromedia-fcs TCP/UDP 1935
RTMFP UDP 1024:65535

Why UDP ports? “Skype works without it..”

That is correct. But we can’t deliver the big serverpower that Skype, Microsoft, Yahoo or Google has. So we designed it so that all of the users do a little server work.

Helpful links