Hi folks- several of our IP 650 phones are crashing / rebooting spontaneously. It's happening on a daily basis, and I sure would appreciate some help if anyone can provide assistance.
Today I was able to capture the logging data from two such crashes. See attached files: one set is from Extension 201 and the other set is from Extension 214.
In both cases, the phone was on an active call and this caused it to hang up on the customer(s). So you can imagine this is a rather pressing situation, and I am tasked with getting it resolved as soon as possible.
Software version: 4.07.2514 (latest)
Phone Model: IP 650 (3150-11530-407)
SIP Platform: Asterisk 11
I read several other posts in this forum regarding phones crashing, including the one about a memory leak bug. But that thread said the bug was fixed in the latest firmware version. So I'm not sure if that's the issue in this case or not?
I will also note that we do not have a Polycom reseller to work with. We took over this office from another business which had closed, and we do not know where the phones were purchased from.
Thanks in advance for any help you can provide!
welcome to the Polycom Community.
I am currently dealing with a similar issue in EMEA but due lack of details from your end I cannot 100% verify if this is the same as this depends on your configuration and setup.
I have attached a file that you can import which monitor's the CPU & Memory usage.
Please apply this to the phones and let syslog run and you can post this here if the phone crashes.
In order to raise a support ticker are the details for the phones:
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
Thank you so very much Mr. Baier- I do appreciate your fast reply in our time of need! I will apply that change to our phones straight away. We just had the problem happen two more times this morning, so I believe we'll have some more data for you shortly.
I'll hold on to the reseller information too, in case we need to use that and we're able to follow that channel.
More details soon....!
You can seek advice from a phone system provider, I am sure they will be able to guide you.
Ok Steffen- here is the syslog from our latest phone crash today, from a phone that has the additional monitoring turned on.
I sure do thank you for you taking a look! If you're able to advise what we might be able to do to resolve the crashing issue, I would appreciate it greatly.
the log is incomplete
It starts at 09:48:01 and finishes at 09:53:12
Ok- I thought that would help if I provided the section of the syslog which was relevant to that phone crashing.
But we had another crash a few minutes ago, so this time I'll provide the entire syslog for the last several hours. (In this file the crash is at 14:57, about 3/4 of the way down. It's extension 214 and you'll see the crash in there)
Thanks, ok: is this file sufficient?
we need to see the memory and CPU consumption or I am unable to compare this to a known case.
Please apply the provided configuration to as many phones as possible and ensure they are all writing to a syslog server.
Ok- I did already apply that configuration to all the phones last night, and then rebooted them all. They do all write to the syslog, so that's all set up.
If it's still not showing you the info you need, are there any other changes we should make to the config? Here's what we've got at the moment, in all our phones:
<memory log.sched.1.name="memShow" log.sched.1.level="2" log.sched.1.period="30" log.sched.1.startMode="rel" log.sched.1.startTime="30" log.sched.1.startDay="0" log.sched.2.name="showCpuLoad" log.sched.2.level="2" log.sched.2.period="30" log.sched.2.startMode="rel" log.sched.2.startTime="30" log.sched.2.startDay="0" log.level.change.slog="2"/>
Ah, I think I see what's up: according to the manual, the section containing these parameters is supposed to be named <log/> rather than <memory/>. Does that sound correct? I could change that and see if it helps get the CPU & memory usage info you're looking for.