OK, sorry

Yes, I moved several phones over without a proper planned works notice. I know we had lots of notices about new call server, but nothing saying explicitly when we would be trying to move lines over. It should have "just worked". For many it did. Sorry. I have been told off by my staff :-(

Sadly several people had issues and I made changes to work around some of them during the day.

What has been bugging me is the call server has crashed half a dozen times. Thankfully, unlike asterisk, calls in progress are not affected by it crashing, and it restarts in a few milliseconds - we just lose billing data. So not a major headache.

So I have been adding debug messages each time, and working through tcpdumps, and finally found the correlation. Every time one of my sky boxes at home tries to call home (via a sipura), bang! it crashes. So I have the offending message and should have it sorted in a few minutes.


  1. Fixed. Stupid error (aren't they all). Sipura send Remote-Party-Id but do not day if withheld or not (privacy=).

  2. I am really struggling to understand why you are seeing Asterisk crash so often. It's certainly not our experience - we have boxes which have been up for years and which, between them, have carried more than 1,000,000 calls - the only crashes we have ever had were on their implementation where I discovered an Asterisk/ODBC bug.

  3. Those crashes were aasip not asterisk.
    But yes, we see crashes on *


Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.

TOTSCO 66 is guidance, optional

I feel I need to explain this. The TOTSCO call today, first I have been on, and wow! But a key point was TOTSCO bulletin 66, which is actual...