3CX Linux Memory Usage Issues; Only Added Polycom VVX501 Phones

[JCLloyd]

We've been cruising along on the 3CX Linux distro for almost exactly a year, and the PBX has been awesome. The boss wanted us to use the software phone and USB handsets/headsets, but finally showed up with a dozen IP phones after constant device issues. He bought Polycom VVX501 phones, a few weeks ago.

I got them to work respectably, even though they are on the legacy and unsupported list. But, I have seen the PBX slowly eating RAM. It has gone from idling on 4% of RAM (3GB of 8GB) of RAM to hitting 95% within a week. Rebooting obviously clears RAM, but why is this happening?

After poking around the forums, I am seeing some comments that indirectly point to the Polycom VVX502 phones being the issue. I am hoping this is an incorrect observation, and something easy to fix.

Any out there knowledgeable on the Linux distro suddenly eating RAM?

______________________________________
Specifics:

• We are on Update "Professional Annual 15.5.15502.6".
• Logging level is on "Low".
• Two SIP trunks (Primary and Rollover), both from Broadvoice with 10 Simultaneous calls.
• Six Inbound Rules, doubled for Rollover.
  
• Three Digital Receptionists: Open, Closed, & Holiday.
• Two Ring Groups: Open & Closed.
• No Call queues.
  
• SSD 256GB; 6% used.
• RAM: 8GB; Boots to 4%... at 9% in 12 hours (from 08:50PM to 08:50AM - We opened at 08:00AM.
• Core i3 7th Gen
  
• Extensions: 14 total; 5 active users, others mostly idle.

 

[JCLloyd]

Bump... Anyone? RAM was at 18%, 24 hours later. Now, 4 more hours later, it is at 20%.

This just started two or three weeks ago.

 

[cobaltit]

I think this will answer your question:

https://www.linuxatemyram.com/

 

[JCLloyd]

Cobaltit, thank you for posting that link. I will keep an eye on the system, and see what it does. As long as it doesn't lock up at some inopportune time...

This would make sense, if it had started it doing this immediately after the system was installed. {SQL does the same thing, but sometimes doesn't want to give memory back when requested.} That it waited 11 months to start doing this, after installing 12 IP phones to system that only had soft phones, leads me to still be cautionary.

The 3CX ".6" update went in sometime in October, and RAM seemed to stay at 4% consumption up to the third week of December.

At 27%, now... 23% in 3 days... I guess I will find out in 12 days or so!

Update: By the way, "free -m" shows that available memory is tracking with the 3CX Dashboard... 71.5% available (5496 of 7680; free is 3823). From that link, I was expecting closer to 310 for available.