I've been switching all my devices to run over TLS if possible, but TCP if not. Polycom has been giving me the most grief lately. When changing from UDP to TCP on a Polycom SoundPoint IP 330 or 335, I would continually get the following message in my Asterisk logs:

[Jun 7 10:12:04] WARNING[4747]: chan_sip.c:3905 __sip_xmit: sip_xmit of 0xa0b1338 (len 583) to x.x.x.x:48356 returned -2: No such file or directory

With even a few days to spare, here are the slides for my upcoming presentation at OpenWest 2014.

I've started work on a Perl DUNDi library. At this point it does some basic parsing of input, but nothing regarding output.

You can follow along at https://www.zmonkey.org/blog/project/perl-dundi-library/about. Source is on Github at https://github.com/heytensai/dundi.

To learn more about DUNDi, see http://www.voip-info.org/wiki/view/Asterisk+DUNDi+Call+Routing.

Since changing my website to be only available via TLS, I've noticed a dramatic decrease in page loads. Most of the missing hits seem to be ones I didn't want anyway, comment spammers and other wastes of electrons. So could TLS be a short-term solution to spam?

Caller ID doesn't always contain the best data, especially with mobile phones. To remedy that, it's nice to use Asterisk to re-write the Caller ID. Instead of maintaining a separate list, I chose to export my contact list from Gmail and import that.