cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1033
Views
5
Helpful
5
Replies

Edge95MXP_Has anybody seen this kind of error?

MasamiNakajima
Level 1
Level 1

Hi all,

Does anybody know what kind of error this is?

Should we apply a RMA? or can we fix this error somehow?

Error detected, MB 1128 - 1128 lost; backtracking looking for SC.

Warning H263Huff: Unexpected GOB 10 at 1229 (tmp = 1280)

Warning H263Huff: Unexpected GOB 21 at 2669 (tmp = 2688)

Warning H263Huff: Unexpected GOB 14 at 1697 (tmp = 1792)

Warning H263Huff: Unexpected GOB 17 at 1408 (tmp = 2176)

Warning H263Huff: Unexpected GOB 18 at 1408 (tmp = 2304)

Warning H263Huff: Unexpected GOB 15 at 1280 (tmp = 1920)

Error in CBPY

Error detected, MB 128 - 148 lost; backtracking changing picture type.

Retry successful at mb 256

ERROR: Tcoeff overflow (72)

Error detected, MB 2411 - 2411 lost; backtracking changing picture type.

ERROR: Tcoeff overflow (72)

0x52bea3bc 56 a4 48 2e 1e 62 32 ed 47 ba 00 00 80 72 1c e0 V.H..b2.G....r..

0x52bea3cc 01 04 90 bf ec 05 bf ff ff ff ff ff ff ff ff ff ................

Error detected, MB 2411 - 2411 lost; backtracking looking for SC.

Warning H263Huff: Unexpected GOB 18 at 1920 (tmp = 2304)

Warning H263Huff: Too few COD bits. MbNumber 1894

Warning H263Huff: Unexpected GOB 17 at 2048 (tmp = 2176)

Warning H263Huff: Unexpected GOB 14 at 1664 (tmp = 1792)

Warning H263Huff: Unexpected GOB 16 at 1948 (tmp = 2048)

ERROR: mvx[0] -16 out of range at PixelCol0

MbNumber = 1856

Error detected, MB 1839 - 1856 lost; backtracking changing picture type.

ERROR: Tcoeff overflow (65)

0x52bea3be e8 ea 80 65 f5 90 bf 44 55 73 ea 38 07 14 a6 26 ...e...DUs.8...&

0x52bea3ce 55 7c 5e 08 6a 7e ae 97 67 d5 81 cf 28 03 7d 1e U|^.j~..g...(.}.

Error detected, MB 1839 - 1839 lost; backtracking looking for SC.

Retry successful at mb 1839

Warning H263Huff: Unexpected GOB 17 at 1024 (tmp = 2176)

Warning H263Huff: Unexpected GOB 6 at 757 (tmp = 768)

Error in MCBPC_P

Error detected, MB 2672 - 2673 lost; backtracking changing picture type.

ERROR: Tcoeff overflow (65)

Thank you,

Masami

1 Accepted Solution

Accepted Solutions

I'd strongly recommend that you update the software on that codec.  There were a whole bunch of video issues fixed in F7 and F8.  If you can, upgrade the device to the latest F9.3.1.

You may be interested in this security advisory which should enable you to at least get to F9.1 even if you don't have a service contract.

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

View solution in original post

5 Replies 5

Martin Koch
VIP Alumni
VIP Alumni

If you could tell us a bit more, like how does your deployment look like,

when you see this error message and what impact it has for the endpoint.

Also add some more info, like if its in a call whats the remote device.

Please remember to rate helpful responses and identify helpful or correct answers.

Please remember to rate helpful responses and identify

Patrick Pettit
Cisco Employee
Cisco Employee

Would be helpful to know what the problem is to. 

You have video problems, packet loss etc?

I'd get that and also what Martin has asked to.

VR

Patrick

MasamiNakajima
Level 1
Level 1

Hi Patrick, Martin and people who read.

Thank you for your comment.

I thought some people can understand what is happenning on the system when you read the logs, so I didn't write any detail. Sorry about that

Well, our client uses Edge95MXP which software ver. is F6.3 and we all know that is really old.

And complains when they start presentation, the dual stream (in particular PC stream) is shown on the monitor and it's blurred from side to side.

The resolution of PC output is 1024x768 and they changed the DVI-VGA cable but it didn't get better.

They also told us after they rebooted the system, it got better.

The part of log I copied and pasted repeats from the event log starts until the ends so I decided to ask you guys if the log is telling us something bad or not.

Do you find any problem in the log?

Thank you,

Masami

I'd strongly recommend that you update the software on that codec.  There were a whole bunch of video issues fixed in F7 and F8.  If you can, upgrade the device to the latest F9.3.1.

You may be interested in this security advisory which should enable you to at least get to F9.1 even if you don't have a service contract.

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Hi Wayne and people who read,

We all know that they should upgrade the software and if they we can do that we do as soon as possible.

However, they won't be able to do that because of the interoperability with another VC systems which aren't Cisco's and are quite old...

If the log which I pasted isn't telling any bad and we can ignore those errors, I mean if they don't have to think the system is breakingdown, that's fine.

I've told them we can't do anything if the problem occurs because of the software's bug, as long as they keep their software version.

Thank you for the tips.