Chris' Blog » problems http://www.cs278.org/blog “A metal loving, web developing, open source contributor.” Sun, 03 Apr 2011 14:36:34 +0000 en hourly 1 http://wordpress.org/?v=3.0 Ekiga VoIP client and SIPGate http://www.cs278.org/blog/2007/11/29/ekiga-voip-client-and-sipgate/ http://www.cs278.org/blog/2007/11/29/ekiga-voip-client-and-sipgate/#comments Thu, 29 Nov 2007 17:17:13 +0000 Chris http://www.cs278.org/blog/2007/11/29/ekiga-voip-client-and-sipgate/ Continue reading →]]> Ekiga is a VoIP client for GNOME. I recently registered with SIPGate.co.uk as I am planning to have a go at setting up Asterisk sometime in the near future. Sadly it wasn’t a well documented process and after searching Google, SIPGate’s website and Ubuntu Forums for help I found some tips on debugging Ekiga. Armed with this knowledge ekiga --debug=[1-6] I managed to discover the required ports for successful NAT traversal. They are as follows:

  • 5060 – 5100/udp
  • 8000 – 8012/udp
  • 5004/udp
  • 10000/udp
  • 3478 – 3497/udp
  • 3478 – 3497/tcp
  • 1720/udp
  • 30000 – 30010/tcp

I am sure they could be refined and there maybe some that are unnecessary but it Works or Me™, use them at your own risk.

]]> http://www.cs278.org/blog/2007/11/29/ekiga-voip-client-and-sipgate/feed/ 0 Subversion and Apache Gotcha http://www.cs278.org/blog/2007/11/29/subversion-and-apache-gotcha/ http://www.cs278.org/blog/2007/11/29/subversion-and-apache-gotcha/#comments Thu, 29 Nov 2007 16:48:36 +0000 Chris http://www.cs278.org/blog/2007/11/29/subversion-and-apache-gotcha/ Continue reading →]]> So, this is the second time I have tried to address the problem I was getting with some Subversion repositories I was trying to configure to be served by Apache. I was trying to use the SVNPath directive to serve one repository but it was not having any of it, so instead I ended up serving them as a temporary measure using SVNParentPath in the format http://svn.example.com/~name/repos/ which is not what I wanted. I am using the Location container in Apache configuration to configure up my repositories, the path I had specified was /~name/. This is where the problem comes in, I would try to checkout the repository over the network and be greeted with a 405 Method Not Allowed error like so:

svn: PROPFIND request failed on '/~name'
svn: PROPFIND of '/~name': 405 Method Not Allowed (http://svn.example.com)

This stuck me as odd, it seemed the Apache was not serving the repository URI using the WebDAV module. When I gave up on an earlier attempt I reverted to using SVNParentPath and accessing the repository over the URI http://svn.example.com/~name/repos/ which worked perfectly and I couldn’t spot why. Turns out I made a single character mistake, my Apache configuration was set to use the path of /~name/ I should have used /~name because SVN truncates the trailing slash even if you specify it on the command line. Bugger!

]]> http://www.cs278.org/blog/2007/11/29/subversion-and-apache-gotcha/feed/ 0