Plantronics + Polycom. Now together as Poly Logo

SoundPoint IP 650 lockups

SOLVED
Highlighted
Polycom Employee & Community Manager

Re: SoundPoint IP 650 lockups

Hello cityguru,

welcome back to the Polycom Community.

Your two original post's => here <= and => here <=  have unfortunately never been followed up so anyone looking at these would never receive any insight if you solved your issue or followed up as advise.

 

In regards to your new question UC Software is no longer a supported version and UC Software 4.0.10 should be used instead.

 

An Upgrade from prior 4.0.0 will always format the file system and does not need any user interaction.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 41 of 45
Highlighted
Occasional Visitor

Re: SoundPoint IP 650 lockups

Hello, has this problem ever been solved?  We are running 3CX and have 15 or so SP IP 550 and 560 phones that all lock up with BLF.  What is odd, we never had issues with BLF before and have been running it for years.  Now, we have phones on every version from 3.3.X to 4.0.10 that lock up if they have BLF from a memory leak.

 

I'd like to know if there is a published solution somewhere other than just go to 4.0.7 as our phones have locked up on that and all others since. We'd love to fix this issue but are frustrated with 3CX support who just say it's not their problem and we don't have a certified vendor to open a case on our behalf.

Message 42 of 45
Highlighted
Occasional Visitor

Re: SoundPoint IP 650 lockups

We have been seeing similar lock ups on every release of 4.0.x code when using BLF on Soundpoint IP 550 and 560 phones.   We are using 3CX Version 15 SP5 and found this issue to much more present after applying this patch. 3CX would not give any details but just said, call Polycom.  The phones are currently running 4.0.10.X

 

Here is what we see in the logs just before the phone freezes and has to be powered off and back on as it freezes and cannot be access via browser config interface.

 

We have 15 phones out of 100 that are unusable now and are having a hard time getting ticket opened with Polycom but seeing this similar issue a couple revs back makes me think this is NOT resolved yet.

 

<131>Apr 17 15:39:23 192.168.2.135 0417153923|utilm|4|03|utilBufferCompress: Couldn't start compression, error -4          192.168.2.135    17/04 15:39:24.315        
<131>Apr 17 15:39:23 192.168.2.135 0417153923|sec  |4|03|utilCryptoLightBufferEncrypt: Could not compress buffer size 1149.      192.168.2.135    17/04 15:39:24.315        
<130>Apr 17 15:39:23 192.168.2.135 0417153923|cfg  |5|03|RT|cfgWriteAnyConfigToFlash: Could not encrypt flash data length 1149              192.168.2.135    17/04 15:39:24.315        
<131>Apr 17 15:39:23 192.168.2.135 0417153923|so   |4|03|SoNcasC::saveMwiInfoRequest - Failed writing flash parameters   192.168.2.135    17/04 15:39:24.331        
<134>Apr 17 15:39:23 192.168.2.135 0417153923|sys  |*|03|0x955b09c0 (utilGenTask): memPartAlloc: block too big - 65536 in partition 0x94e5c19c.      192.168.2.135    17/04 15:39:24.331     
<134>Apr 17 15:39:23 192.168.2.135 0417153923|sys  |*|03|0x955b09c0 (utilGenTask): memPartAlloc: block too big - 65536 in partition 0x94e5c19c.      192.168.2.135    17/04 15:39:24.331     
<134>Apr 17 15:45:15 192.168.2.135 0417154515|sys  |*|03|0x9573da50 (tPktProSys): memPartAlloc: block too big - 680 in partition 0x94e5c19c.           192.168.2.135    17/04 15:45:15.571     
<131>Apr 17 15:45:17 192.168.2.135 0417154517|wdog |4|03|Task 957695d0 is suspended               192.168.2.135    17/04 15:45:18.572        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:45:19.712        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:45:49.712        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:46:19.713        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:46:49.713        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:47:19.714        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:47:49.714        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:48:19.715        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:48:49.716        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:49:19.701        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:49:49.701        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:50:19.702        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:50:49.702        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:51:19.703        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:51:49.703        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:52:19.704        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:52:49.705        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:53:19.690        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:53:49.690        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:54:19.691        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:54:49.691        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:55:19.692        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:55:49.692        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:56:19.693        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:56:49.694        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:57:19.679        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:57:49.678        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:58:19.679        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:58:49.680        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:59:19.681        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 15:59:49.682        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:00:19.683        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:00:49.684        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:01:19.669        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:01:49.686        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:02:19.672        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:02:49.674        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:03:19.675        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:03:49.677        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:04:19.679        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:04:49.665        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:05:19.667        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:05:49.668        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:06:19.670        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:06:49.672        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:07:19.674        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:07:49.675        
<130>Apr 17 15:45:18 192.168.2.135 0417154518|lldp |5|03|Could not allocate space for LLDP packet.       192.168.2.135    17/04 16:08:19.677        

 

Message 43 of 45
Highlighted
Polycom Employee & Community Manager

Re: SoundPoint IP 650 lockups

Hello Tex,

welcome to the Polycom Community.

Simply post a MAC address and I can look up who would be able to support you.

 

Please be aware if your phone is out of warranty to expect a PPI / Pay Per Incident support.

 

Usually I would suggest to utilize a currently supported version like 4.0.11

 

In addition please be aware not to use more than 50 BLF's on the phone.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 44 of 45
Highlighted
Valued Contributor

Re: SoundPoint IP 650 lockups

Tex,

 

It definitely looks like you have hit a memory leak, but I'm not convinced it is the same or even related.  If you don't see "Dialog session is not found" also appearing in your logs, it is unlikely to be the same issue.  We have been running 4.0.7 since its release (only just started playing with 4.0.11, so cannot confirm or deny if there has been a regression since then) and the problem is absolutely gone for us.

 

If you remove all BLF config from the affected phones, does the problem for sure go away?

 

-- Nathan

Message 45 of 45