Quote
Evidently I'm not the only one to find issues with the UC500. UC500 support issues
It's kind of disturbing when you don't even understand what the problem is, much less how to fix it.

Quote
re-INVITE dropped when CME with rtp-nte and CUE rtp-nte , Fixed CSCsz73632
Or how about this jewel:
Quote
Access class routers (for example a 2811 or a 3825) would experience this crash. Symptoms of the crash are as follows: #1 sh version would contain the following: System returned to ROM by error - a Software forced crash, PC 0x40091930 at 07:32:18 GMT Fri Mar 30 2007 #2 show stack would contain the following: System was restarted by error - a Software forced crash, PC 0x40091930 at 07:32:18 GMT Fri Mar 30 2007 2800 Software (C2800NM-SPSERVICESK9-M), Version 12.4(9)T1, RELEASE SOFTWARE (fc2) Technical Support: https://www.cisco.com/techsupport Compiled Wed 30-Aug-06 16:22 by prod_rel_team Image text-base: 0x400B132C, data-base: 0x42C80000 Stack trace from system failure: FP: 0x4678D7A8, RA: 0x40091930 FP: 0x4678D7A8, RA: 0x4008F528 FP: 0x4678D7D0, RA: 0x400E06D4 FP: 0x4678D808, RA: 0x400B7340 FP: 0x4678D830, RA: 0x400CD47C FP: 0x4678D870, RA: 0x42C5F4E0 FP: 0x4678D890, RA: 0x40B723D8 FP: 0x4678E138, RA: 0x40B71A64 #3 Contents relating to log entries written in the crashinfo file would contain %IPPHONE-6-REG_ALARM: 10: Name=SEP0015C6245001 Load=4.0(03.01) Last=Failback %SYS-2-CHUNKBADREFCOUNT: Bad chunk reference count, chunk 4727F554 data 4728A328 refcount FFFFFFFF alloc pc 40B8FAA8. -Process= "Skinny Msg Server", ipl= 0, pid= 34 -Traceback= 0x414A8A98 0x400E06BC 0x400B7340 0x400CD47C 0x42C5F4E0 0x40B723D8 0x40B71A64 0x40B6EE64 0x426D50F0 0x426D50D4 chunk_diagnose, code = 3 chunk name is MallocLite current chunk header = 0x4728A318 data check, ptr = 0x4728A328 next chunk header = 0x4728A3A8 data check, ptr = 0x4728A3B8 previous chunk header = 0x4728A288 data check, ptr = 0x4728A298 If you see #1 through #3 and running 12.4(9)T or prior releases, then there is high probability that you are affected by this IOS bug. The resolution for this requires you to load 12.4(9)T2 OR 12.4(11)T or later IOS releases. For confirmation (if needed) OR if you are running a different IOS release, open a TAC case and provide the sh tech (taken from the enable mode) and TAC will be able to confirm if you are affected by this or something else.
Workaround: None.
Note the comment at the bottom.

Somehow I suspect a lot of CGs don't know what that means, much less telephone techs.

Is this the new world of telecom we're heading to? I don't think the transmission shop customer is going to care for paying for the all day service call because something like the above happened out of warranty and his desk phone quit.

I'm hoping the vendor we are looking at has a good handle on these type of things.