16 Apr 2006

So, I now have cppunit support for subunit – the patch cppunit-subunit-1.10.2.patch adds a TestProgressListener subclass of SubunitTestProgressListener.

So subunit is now able to integrate into one seamless whole test suites from python, C, C++ and shell using the primary xUnit implementation for those languages. Woo!

15 Apr 2006

I snuck in some more subunit hacking today…

Theres now a C library (libsubunit) with child bindings, a patch for ‘check’ to enable a subunit UI (use CK_SUBUNIT) in the runner. I’m partway through a view for gunit to do the same, but it looks like it requires some changes to the core to get clean access to the needed data – which is quite surprising given the close-to-xUnit style it claims.

14 Apr 2006

Easter Friday – always a fun day.

Went and saw Ice Age 2 – mildly disappointed. Lovely animation, lots of laughs, but their continuity and consistency sucked.

Later on, I bound subunit to ShUnit with this patch. This means that when you decide to add a hacky little shell script to some larger project, you can integrate the tests into your unit test framework rather than having to have multiple separate test suites…. which means your IDE’s red/green test status bar will show those test results. ROCKING.

08 Apr 2006

Yay for siproxd. Working multi-user sip is a beautiful thing.

Key notes:

You need to configure siproxd, allow siproxd to use some ports on the firewall, and configured your sip client.

after installing the package, edit /etc/siproxd.conf and set



hosts_allow_reg=your internal network/netmask

do not set hosts_allow_sip – I found it interacted strangely and got 408 ‘timeouts’ – which is how siproxd shows ‘access denied’ to the client.

edit /etc/default/siproxd and set it to enabled.

do a sudo invoke-rc.d siproxd start

Now, in your iptables rules you need to allow the following ports for ‘INBOUND’ on your inside and outside interfaces:

5060 (sip)

7070-7079 (rtp – the voice and video data)

Activate those rules, and you are done on the infrastructure, now its just each client that you need to configure.

So fire up your sip client. It should have a sip proxy field – in there put ‘sip:’ + your gateway address/ip.

if you have STUN configured – disable it. The sip proxy will forward registration and all traffic for you, STUN will at best confuse the issue.

And bingo, you should have working sip.