Comment 4 for bug 1741170

I'm really no asterisk expert but there are two cases:
a) you are really out of numbers (not a bug, just as it is)
b) asterisk thinks you are out of numbers due to a bug e.g. not freeing unused correctly

Could you confirm that we are looking at (b) in this case?

Also how easily is this reproducible for you?
If you can kind of intentionally trigger it I'd recommend you might try one of the newer versions available in newer Ubunutu releases - if those work reliably that might confirm that there already is a fix in the asterisk project that we have to look for to backport.

For the illegal opcode - there are (to my surprise) several of those issues found by search engines. Those issues usually are super rare - only if either the code is totally wrong, compiled against wrong libs/headers or virtual machines which do not provide all expected cpu features.

It sounds similar to [1], but that code is in the version you run.
Also [2] is similar but very old as well.
Maybe you find some tests/workarounds there still?

TL;DR - as unfortunate as it is for now I can't differ this between a bug or a config issue.
Waiting for your feedback - hopefully this is somewhat reproducible to be debuggeble by you.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611628
[2]: http://lists.digium.com/pipermail/asterisk-users/2008-September/218759.html