Hello, I have a asterisk server that has 300 trunks inside it. These trunks are registered from the inside to the outside. I have 300 records in my register string(sip show registry). The problem is that after a time, instead of once send register after the expiration time, some trunks send registers several times. With different call IDs, this number can even reach 5 registers at a time. I tested different modes as follows:
In the first step, I changed the default expire value from 120 to 300 and observed that after 300 seconds, the registers are still sent out several times. However, with one difference, only in one of the packets the expire value was changed to 300, and the rest of the duplicate packets had the same value of 120. they seemed to exist in the database and were not deleted. The only way to delete these duplicates is to type the command ‘service asterisk restart’ . even with a ‘sip reload’ this recurring problem is not solved.
And there is only one register string record for that trunk.
I have questions. First, what database are the register string records stored in so that I can just delete it and not have to ‘service restart Asterisk’?
And the next question is whether there is another solution ?
And I don’t know how this problem occurs. when the number of requests to the provider increases, it block this trunk.
On Monday 05 May 2025 at 14:57:22, hamed.rasstegar via Asterisk Community
wrote:
os = Debian 10 (buster)
asterisk = 13.37.0.s.2
Asterisk 13 is no longer supported - it went End-of-Life in 2021:
Whilst we’re discussing End-of-Life, Debian 10 is in the same status, since
last summer: Debian -- Debian Releases
Finally, you’re still using the deprecated and unsupported chan_sip channel
driver, which very few people are going to be able to help with, especially
with a fairly unusual requirement such as you have described.
I recommend you use a current supported version of Asterisk on an up-to-date
Operating System, using the PJSIP channel driver, and see whether the problem
persists.
If it doesn’t, you’ve solved your problem and you have a supported setup
again.
If it does persist, there will be far more people here able to help you debug
the problem.
Incidentally, where exactly do you see that version number string
“13.37.0.s.2” and how did you install Asterisk? The version that’s packaged
for Debian 10 is 16.28.0 Debian -- Package Search Results -- asterisk
Version 16 is still End-of-Life, but I’m puzzled about the mis-match.
Antony
–
“I estimate there’s a world market for about five computers.”
Thanks, I did a lot of configuration on Asterisk 13 and I’m installing the package with the remastered iso. I just wanted to know if anyone had this problem and if updating Asterisk fixed it. Because changing Asterisk is a very time-consuming task for me.