H175: After upgrade to new firmware there is no video is shown on H175 when calling Tandberg MCU

Doc ID    SOLN294184
Version:    3.0
Status:    Published
Published date:    28 May 2017
Created Date:    04 Aug 2016
Author:   
Yuriy Drumov
 

Details

Call Flow : H175 => SM => SIP trunk => 3rd Party MCU & Video Terminal. 

Issue occurs after FW upgrade from H1xx-IPT-SIP-R1_0_1_0-121115 to H1xx-IPT-SIP-R1_0_2_1-052216.

The same problem also occurred for FW H1xx-IPT-SIP-R1_0_2_0-032716.  

H175 with previous FW H1xx-IPT-SIP-R1_0_1_0-121115  is working well.

Tandberg MCU 4501 Software version 4.2

Avaya Scopia XT5000, software version 8_3_5_31. This codec direct registered at Avaya Aura Session Manager.

TANDBERG Codec C20, software version 5.1.4.295090. This codec direct registered at Avaya Aura Session Manager.

TANDBERG Codec C20, software version 5.1.0.280662. This codec direct registered at Avaya Aura Session Manager.

CM version - R016x.03.0.124.0

SM version - 6.3.17.0.631705

SMGR version - 6.3.17.14.4616

 

Problem Clarification

No video for calls between H175 and 3rd Party Tandberg MCU. Video calls to Scopia are working fine.

Other participants also connected to this MCU. Local video presented to H175.

Remote video not working all the time when the H175 connect to MCU.

SBC is not involved. It is direct SIP connection from Avaya Session Manager to Tandberg MCU.

 

 

Cause

With the old firmware in the SDP H.175 sends

    Media Attribute (a): rtpmap:109 H264/90000

    Media Attribute (a): fmtp:109 profile-level-id=420028;parameter-add=0

    Media Attribute (a): rtpmap:111 H264/90000

    Media Attribute (a): fmtp:111 profile-level-id=420028;packetization-mode=1;parameter-add=0

    Media Attribute (a): rtpmap:110 H264/90000

    Media Attribute (a): fmtp:110 profile-level-id=640028;packetization-mode=1;parameter-add=0

    Media Attribute (a): rtpmap:112 H264/90000

    Media Attribute (a): fmtp:112 profile-level-id=640028;parameter-add=0

 

With the new firmware:

    Media Attribute (a): rtpmap:109 H264/90000

    Media Attribute (a): fmtp:109 profile-level-id=420028;packetization-mode=1;parameter-add=0

    Media Attribute (a): rtpmap:111 H264/90000

    Media Attribute (a): fmtp:111 profile-level-id=420028;parameter-add=0

    Media Attribute (a): rtpmap:110 H264/90000

    Media Attribute (a): fmtp:110 profile-level-id=640028;packetization-mode=1;parameter-add=0

    Media Attribute (a): rtpmap:112 H264/90000

    Media Attribute (a): fmtp:112 profile-level-id=640028;parameter-add=0

 

As you can see the new firmware swaps profiles 109 and 110 and adds

packetization-mode=1

parameter to profile 109.

 

Our guess is that the Tandberg (Codian) MCU does not support packetization-mode=1 in reality and simply ignored this parameter

and kept sending H264 packets with packetization-mode=0.

So the problem is at the Tandberg side.

 

Solution

Info about video codecs: http://www.c21video.com/microsoft_lync/h323_sip_codecs.html

 NOTE:

Codian is a former supplier of video conferencing products. The company became part of Tandberg in 2007, which became part of Cisco Systems in 2010.

Here is the link:

http://www.cisco.com/c/en/us/support/conferencing/telepresence-mcu-4501/model.html

Current 4501 firmware at the customer is 4.2:

User-Agent: Codian MCU 4501 v4.2 (1.50)

 

This looks to be a rather obsolete firmware.

Customer should upgrade that 4501 to the latest available software to resolve the issue.  

Or they can keep using the old H175 firmware: H1xx-IPT-SIP-R1_0_1_0-121115

 


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy