C20 hangs up every time upon receiving a SIP call

[hashimoto.kotaro]

Hi all,

A C20 (TC5.1.5 or TC5.1.4)  hangs up evey time upon receiving a SIP call from Panasonic endpoint(KX-VC300, version 3.0).

Meanwhile the KX-VC300 can receive a call from the C20 by SIP without any problem.

And when it hangs up, we have no choise but to reboot the C20 by pressing power switch.

We use no SIP registrar but directly call from Panasonic endpoint to C20 by SIP.

This does not happen on TC5.1.3 so I guess some software changes about SIP have been made on TC5.1.4.

Does anybody know good workaround about this?

Best Regards,

Kotaro Hashimoto

[Danny De Ridder]

So the C20 becomes unresponsive when it gets a call and you need to repower it?

If so, maybe the historical logs will tell us something.

Can you get the historical log files using your WEB browser?

http://10.60.142.199/wsgi/logs/bundle/old

Just replace the IP address above with your codec's IP address and attach the tar file in your reply.

[Tomonori Taniguchi]

If you add CapFilter for H.264 RCDO and NIL and just advantaging base H.264, will that makes difference (I belive KX Endpoint only support H.264 Baseline)?

You can filter those capability by executing following command.

  xConfiguration Experimental CapsetFilter: "H.264RCDO;H.264NIL”

[hashimoto.kotaro]

Hi Danny, Taniguchi-san

Thank you for your information.

I tried "xConfiguration Experimental CapsetFilter: "H.264RCDO;H.264NIL” but unfortunately it did not resolve the issue.

Could you please check the hisgorical log?

Best Regards,

Kotaro Hashimoto

[vivsing2]

Hi Kotaro,

First thing which I will mention that for SIP call this is not correct scenario, when C20 dial or receive call without SIP registrar.

I saw in historical log that on 21 Dec you received SIP call:

Dec 21 07:51:21 (none) main: 312.95 SipCall I: sip_call_handler::handleSIPMCallInd(na/0/0): Incoming callrate=4000000 to sip:10.188.253.156 from sip:CodianMCU4510@10.188.253.166

As well as some error related to H264 Decoder.

Dec 21 07:51:23 arm2 video2: H264D_TI: IS_IDR_EXPECTED_ERROR (frame 1: ERROR 0x00008860|Corrupt Data|Concealment NOT Applied|H264D_ERR_IMPL_PPSUNAVAIL)

Dec 21 07:51:23 arm2 video2: 314.05 DEC_FSM-1 I: Decode Err: frame 1: ERROR 0x00008860|Corrupt Data|Concealment NOT Applied|H264D_ERR_IMPL_PPSUNAVAIL

Dec 21 07:51:23 arm2 video2: 314.05 DEC_FSM-1 I: intra request

Dec 21 07:51:23 arm2 video2: H264D_TI: IS_IDR_EXPECTED_ERROR (frame 2: ERROR 0x00008860|Corrupt Data|Concealment NOT Applied|H264D_ERR_IMPL_PPSUNAVAIL)

Dec 21 07:51:23 arm2 video2: 314.06 DEC_FSM-1 I: Decode Err: frame 2: ERROR 0x00008860|Corrupt Data|Concealment NOT Applied|H264D_ERR_IMPL_PPSUNAVAIL

Dec 21 07:51:23 arm2 video2: H264D_TI: IS_IDR_EXPECTED_ERROR (frame 3: ERROR 0x00008860|Corrupt Data|Concealment NOT Applied|H264D_ERR_IMPL_PPSUNAVAIL)

Dec 21 07:51:23 arm2 video2: 314.10 DEC_FSM-1 I: Decode Err: frame 3: ERROR 0x00008860|Corrupt Data|Concealment NOT Applied|H264D_ERR_IMPL_PPSUNAVAIL

Dec 21 07:51:23 arm0 video0: 314.10 ENC_FSM-0 I: start standard h.264, width 1280, height 720, source_width 1280, source_height: 720, framerate 3000, bitrate 2000000, packetsize 0, fragmentsize 1360, dynamic mbps 108000, static mbps 108000

This might be reason your codec freeze and you have to reboot your codec.

I would suggest if you disable H264 completely using following command and check if issue persist or not

xConfiguration Experimental CapsetFilter: "H.264RCDO;H.264NIL;H.264"

Danny and Tomonori might add more detail.

Regards,

Vivek

[hashimoto.kotaro]

Thank you Vivek,

I have tried the command you mentioned but the issue persisted.

In addition, I found the same issue happened also on EX60 (TC5.1.5).

So I decided to open a SR to resolve this soon.

Thank you for your advice.

Best Regards,

Kotaro Hashimoto

[hashimoto.kotaro]

I received an answer from a TAC engineer that this is a software bug found in TC5.1.4, which is already fixed and will be released in TC5.1.7.

Until then, a workaround for this issue is only to use TC5.1.3.

Thank you all,  for your information.

Best Regards,

Kotaro Hashimoto

[hashimoto.kotaro]

An additional information.
They say this will be fixed in TC6.0 also.

Sent from Cisco Technical Support iPhone App