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 reproduci
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to g
Function get_unused_callno issues "Out of call numbers"
And Function __find_callno issues "No more space" if the former fails
So this is no usual out of (disk) space or such.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I do not know if this is relevant, but there a kernel message which
seems suspicious to me:
[499321.365191] traps: asterisk[17039] trap invalid opcode
ip:7fb46af2dedc sp:7fb3e4c0b890 error:0 in
libpthread-2.23.so[7fb46af21000+18000]
--
You received this bug notification because you are a member
