cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1282
Views
0
Helpful
4
Replies
Highlighted

CISCO C20 is not reacting on remote control

Dear Community,

There is a CISCO C20 Codec which works fine. The problem which occurs is, that suddenly in a VC Call it is not any longer possible to control the system via remote control. You need to reboot the system, then hopefully it works again. To everyone who can help here, i can send the logs for analysis.

kind regards

christian

4 REPLIES 4
Highlighted
Enthusiast

Hi Chris,

to see you again

as per teh logs teh very first theing i will suggest is go ahead and upgrade the unit

current version is  TC4.1.1.253451 a very old version

go to the latest version if have any restriction upgrading the unit then we need to make them understand that its a old version, after the upgarde my understanding is the issue will get resolve if not we will look further.

if you are moving to TC 6.1.2  (latest) no requirement for relase keys

else uptill tc 6.0.x  you can generate the licecnse key online on the licensing page.

Let me know the results

Thanks

Ravi kr.

Highlighted

Also reproted some Dsp  errors

Jun 12 12:59:11 (none) main: 2558.96 MC I: RemoteInputGate::setIncomingModeReport(ig=15,p=2) [Video (2): H.264 1024x576@33.63  0k ]

Jun 12 12:59:13 arm2 video2: DEC_ReportErrorCallback errorCode 2628 id 70074

Jun 12 12:59:13 arm2 video2: H264D_TI: FAILED, frame 70074: ERROR 0x00000a44|Corrupt Data|Concealment Applied|H264D_ERR_IMPL_FRAMELOSS_DETECTED

so i suggest upgrading the first step as the newer version have betterhandling of dsps mechanism.

Highlighted
Cisco Employee

Hello,

I see lots of these messages in the log.

Jun 12 12:18:01 (none) main: 88.53 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.53 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.53 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.54 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.54 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.54 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.55 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.55 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.55 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.55 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.56 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Jun 12 12:18:01 (none) main: 88.56 APPL_Facade I: <- ***:CommandReq SetIRLed on=0

Normal settings are such that the camera picks up IR, and sends the commands to the codec via VISCA protocol.

The messages above I have never seen. Is this the camera trying to turn off IR on the codec?

What's your config on the codec?

xConfiguration SystemUnit IrSensor:

Danny.

Highlighted

An easy way to check whether the IR messages are reaching the codec is by doing following when logged in as admin :

xfeedback register /event

** end

When you then use the remote you should see the keys being pressed.

*e KeyDown Key: "Grab"

** end

*e KeyRelease Key: "Grab"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "Grab"

** end

*e KeyRelease Key: "Grab"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

*e KeyDown Key: "1"

** end

*e KeyRelease Key: "1"

** end

Content for Community-Ad