Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with Critical Memory Alarms possibly related to my SIP Trunk

tac84

Programmer
Mar 15, 2019
446
AU
Hi all,

I raised an issue some time ago on here under (https://www.tek-tips.com/threads/critical-alarm-memory-exhausted.1831337/) where I was finding that my SD card was rapidly reducing over the space of say a few days, ultimately causing the IPO to issue Critical Memory Alarms and reboot on its own. If I reboot it manually, the SD card usage would drop back down to 30% and slowly start increasing again over a few days, repeating indefinitely. I haven't been able to resolve the issue.

This problem has been in place for around 6-7 months now and I've tried everything from recreating the SD card (8GB), replacing the SD card (8GB), replacing the IPO hardware, upgrading to R11.1.3.2.0 build 6 (current).

I found a similar post on here from back in 2021 (https://www.tek-tips.com/threads/ip500v2-memory-leak-on-11-0-4-sp-6-11-0-4-6.1811992/) that sounds identical where the user found that the problem was related to his SIP trunk and the network switch. I've had my network switch (UDM Pro) and network infrastructure for a few years before the problem, but I can see the IP Office is sending a registration request to my SIP trunk provider every 30 seconds, even though in Line | SIP | SIP Credentials I have the expiry set for 60 mins. I've tried changing this number, however the SIP provider is still receiving registration requests every 30 seconds..... Where can I change this in the system? How often should registration occur?

Based on the other similar post, I'm trying to rule everything out and SIP trunk registration interval is where I'm at....any assistance would be greatly appreciated :)

system status screenshot.png
 
You have to check.the 200 OK response to.the Register received from your provider.

Within the message you will find a text "expires=xxx" where xxx is a number of seconds the registration is valid. IPO renews the registration after 80 or 90% of that time range.

Be aware that your configuration will be sent to the provider as a suggestion (expires=xxx) but the provider decides how long a registration will valid and informs you with the OK message.
 
Thanks @derfloh

This is the message I get back.

09:31:58 147241mS SIP Rx: UDP 103.140.134.2:5060 -> 10.10.10.2:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.2:5060;rport=5060;branch=z9hG4bKbfab02c72a52931118472363597173b3;received=10.10.10.2
From: <sip:XXXXXXXX@sip.biz.crazytel.net.au>;tag=2dcdc7119f06e290
To: <sip:XXXXXXXX@sip.biz.crazytel.net.au>;tag=996afb99ae817c18438c71c33b3902c7.92f0
Call-ID: a8efd55f4381720bd214f04efcd04c15
CSeq: 1916855569 REGISTER
Contact: <sip:XXXXXXXX@10.10.10.2:5060;transport=udp>;expires=60
Server: kamailio (5.2.6 (x86_64/linux))
Content-Length: 0

So is this the provider forcing registration every 60 seconds?
 
I also noticed in the system status application that the retry time to re-register the SIP trunk is happening every 30 seconds.
 

Part and Inventory Search

Sponsor

Back
Top