SIP Mass Exodus

Home » Asterisk Users » SIP Mass Exodus
Asterisk Users 2 Comments

Hi all,

I’ve been seeing some strangeness lately on my 10.2.1 server. It’s gotten to the point that a few times each day, I see masses of SIP
clients becoming unreachable. They’re not all on the same network, and we don’t see any calls drop. In a few seconds, they all come back.

I don’t think it’s a connectivity issue because we don’t drop calls, and the endpoints aren’t on the same networks. We don’t see excessive CPU load when it happens.

It does SEEM to happen most right after someone accesses their voicemail.

We are using RT SIP registration as well as database voicemail storage
(mysql). The database is on the same machine as the asterisk server.

Have we grown beyond the ability to host both the db and * on the same hardware? Or is this a known issue with a (hopefully) known fix?

TIA,

Mike Diehl.

2 thoughts on - SIP Mass Exodus

  • We saw this happen on a 1.4 server a couple of years ago shortly after 2am each day. It was only after a study of the cron schedule we narrowed it down to a number of rsync backup jobs which were run at that time.

    As in your case, it wasn’t a connectivity or bandwidth issue – in the end we put it down to a disk I/O bottleneck. It might be worth running something like iostat on your box to see if you see a spike in iowait as voicemail is being checked. We resolved it simply by rate limiting our rsync jobs. In your case with a busy database, you might want to look at your MySQL indexes and/or cache settings – this might be something worth asking about on the respective MySQL discussion groups as well as here.

    Kind regards,

    Chris

  • Mike,

    Am 14.11.2013 01:48, schrieb Chris Bagnall:

    you could also throw in some more stuff like the following and run it for 24 hours every second, then check the log for the timestamp to figure out what happened:

    while true; do echo `date`; asterisk -rx ‘sip show peers’; asterisk -rx
    ‘sip show channelstats’; mysqladmin –password=yourpass processlist; ps auxww; vmstat; iostat; echo; echo; echo; sleep 1; done >> log.txt

    Regards Markus