Qnext, Truly Connected, continued

Finally had a chance to try it out with kleinejan. The interface is quite usable, but might need some more tweaking to make things really obvious. If you’re behind a firewall things will not work out of the box. Unlike Skype, Qnext does not automatically look for proxy servers to use. This means that you need to either punch some holes in your firewall, or find someone without a firewall to proxy for you. You need to forward TCP 5235, TCP 5236 and UDP 5237 to your NATed box to be visible. It would be nice if Qnext ran some proxy servers themselves. Once I made the ports forwards kleinejan became visible even as he was behind NAT. A VOIP session was one way only. Looks like both parties need to do port forwarding for this to work. However, Qnext clearly documents all these facts. And unlike Skype, where sharing your connection is mandatory, you need to explicitly enable yourself as a proxy. Tomorrow we’re trying Qnext with a proxy on the co-lo.

This entry was posted in Home. Bookmark the permalink.

One Response to Qnext, Truly Connected, continued

  1. Zach says:

    can you write or email a tutorial on how to forward TCP 5235, TCP 5236 and UDP 5237? i’ve never ran an ftp before because i could never get around the firewall issue. i thought i’d give qnext a shot, but i’m not sure how to do this.

    thanx,
    Zach