How can I fix the 1080P resolution using H.323 to SIP or SIP to H.323 Protocols through VCS on EX90, C60 both?

[quake3bak]

Hi, I'm a junior network engineer in korea.

and, for the first, I excuse to my bad writing to read within uncomportable. sorry, Eng is not my mother language.

I tested on SIP to SIP call and H.323 to H.323. These cases are all works correctly in 1080P(1920*1080),

BUT

SIP to H.323 or H.323 to SIP dosen't work through VCS. The devices types are EX90, C60.

Devices Status : HD-Resolution license is activated, Default Bandwith 6000K,

and their is no external issues, because it's on LAP Test on the same LAN network.

I tried many times, but these devices connect somtimes 720P(1280*720) and sometimes connect 1080P Resolution each other.

Is anybody knows make the devices fix their resolution to 1080P not the 720P?

I'll look forward to your good kindness.

thanks for read my bad writing.

[sagsheth]

Hi Jinsung,

Please help in understanding you issue.

When you make interworking call i.e SIP-to-H323 or vice versa, call never connect at 1080p. Please correct me if i am wrong.

-Sagar

[Patrick Pettit · Accepted solution]

Hi Jinsung.  Would be important to know what SW version running on VCS as well.  Prior to X7.1, VCS would set the media lines for SIP leg of the call to BW to 1920, and this is resolved in this release.  I'd ask, if you can, upgrade your VCS to X7.1 and retry the call again.  This may be what is capping you at the moment and achieving 1080p on interworked call.

CSCtx32717

Symptoms: An interworked call will find its video bandwidth capped at 2mbps in one direction.

Conditions: Video sent from the SIP side to the H323 will be capped at 2mbps. This may result in a different codec being chosen, or a lower bandwidth on the preferred codec.

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/release_note/Cisco_VCS_Release_Note_X7-1.pdf

You can try:

Workaround would be to set optimal definition to high on both 
endpoints or avoid interworking to achieve 1080p in the meantime.  

Let us know the outcome.  

Thanks in advance. 

VR
P2

[vivsing2]

Hi Partick,

Meanwhile we are waiting software version of VCS

I just want to confirm according to Jinsung, "

I tried many times, but these devices connect somtimes 720P(1280*720) and sometimes connect 1080P Resolution each other.

Is anybody knows make the devices fix their resolution to 1080P not the 720P?

"

So it seems that call very b/w 1080p and some time 720p, so whether this bug can lead this inconsistency while interworking call.

Regards,

Vivek

[quake3bak]

Thanks to check this, The VCS ver is X5.2 now, I'll soon test after upgrading to X7.2

[quake3bak]

My VCS is X5.2 Ver now, So I will upgrade X.7.2 as u recommanded and then after, I'll test again. thanks.

[quake3bak]

Thanks to your reply~ I'll check it.

[quake3bak]

Well... I tried to upgrade VCS Ver X7.1, but, failed, because of release key issue.

My Key is expired, so there is no other way to upgrade except ask about continue the license key expiration to cisco

But, I'm not sure my company will adopt this asking to Cisco. So, I might close this discussion...

Anyway, thanks to everyone who replied this page.

[Patrick Pettit · Accepted solution]

HI Jinsung.  The one way we had to work around this in a customers case was set to the main camera's optimal defintion to HIGH under Advanced Configuration>Video Input 1 (which is our main camera)>Optimal Definition to HIGH.  This *should* allow you to achieve the desired result or even 720p60 operating around 2 meg.  This may be something viable for you to try.  Let us know if you decide to do so. 

Thanks in advance.

VR

Patrick

[vivsing2 · Accepted solution]

Hi Patrick,

I agree with Patrick, according to following table

It look like we have something to do with 60 fbps as well, so i recommend one more setting to change i.e. Threshold 60fbps

xConfiguration Video Input Source [1..5] o p timalDefinition Threshold60fps

For each video input, this setting tells the system the lowest resolution where it should transmit 60fps.

So for all resolutions lower than this, the maximum transmitted framerate would be 30fps, while

above this resolution 60fps would also be possible, if the available bandwidth is adequate.

Requires user role:  ADMIN

Value space: <512 _ 288/768 _ 448/1024 _ 576/1280 _ 720/Never>

512_288: Set the threshold to 512x288.

768_448: Set the threshold to 768x448.

1024_576: Set the threshold to 1024x576.

1280_720: Set the threshold to 1280x720.

Never: Do not set a threshold for transmitting 60fps.

xConfiguration Video Input Source 1 OptimalDefinition Threshold60fps: Never

xConfiguration Video Input Source 1 OptimalDefinition Profile: High

This command will help to achieve 1080p calll, if we have optimal defination set to High and when you have bandwidth more then 1472 Kbps

Please let me know whether provided information helped or not.

Regards,

Vivek

[quake3bak]

Vivek Singh , Patrick Pettit  you 2 men gave me a great answer. It works now. I can see with 1080p on both devices.

thanks a lot~! I'll greatly pleasured by two of you~!

but steel remain a question,

how can I full use of this bandwith on both?

I can see 1080p with Full bandwith when I call Sip to Sip or H.323 to H.323.

but, when I call to SIP to H.323 or H.323 to SIP, default bandwith is 6000K but, real data bandwith is 19xx~ 24xx...

what suppose to be a cause?... even u cannot answer this, I'm glad enough~.

thanks~ very much to repliers.

is this problem caused from this?

CSCtx32717

Symptoms: An interworked call will find its video bandwidth capped at 2mbps in one direction.

Conditions: Video sent from the SIP side to the H323 will be capped at 2mbps. This may result in a different codec being chosen, or a lower bandwidth on the preferred codec.

[Patrick Pettit · Accepted solution]

HI Jinsung.  Yes.  The issue still is this CDETS quoted to you. 

If you place a SIP call targetting an H323 System, the initial INVITE on the SIP side will contain total session BW and transport independent BW. 

The BW listed here when placing the SIP call is 6 Meg

b=AS:6000

m=video 2434 RTP/AVP 97 98 99 34 31

b=TIAS:6000000

a=rtpmap:97 H264/90000

a=fmtp:97 profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9000;max-smbps=245000;max-fps=6000

a=rtpmap:98 H264/90000

a=fmtp:98 profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9000;max-smbps=245000;packetization-mode=1;max-fps=6000

a=rtpmap:99 H263-1998/90000

a=fmtp:99 custom=1280,768,3;custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000

-------------------------------------------------

IWF Function will look for the H323 Side of the call and allow it to connect. The H323 side of this call is also requesting and has been approved to run at 6 Meg also. Once the call connects and terminal capability sets are exchanged, the IWF function will formulate a response back to the SIP side of the call.  The 200 OK response sets the following in its 200 OK with SDP:

m=video 50042 RTP/SAVP 97 98 99 34 31

b=TIAS:1920000 <----INCORRECT MEDIA LINE BW

a=rtpmap:97 H264/90000

a=fmtp:97 profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9216;max-smbps=245000

a=rtpmap:98 H264/90000

a=fmtp:98 profile-level-id=428016;max-br=5000;max-mbps=245000;max-fs=9216;max-smbps=245000;packetization-mode=1

a=rtpmap:99 H263-1998/90000

a=fmtp:99 custom=1280,720,3;custom=1024,768,1;custom=1024,576,2;custom=800,600,1;cif4=1;custom=720,480,1;custom=640,480,1;custom=512,288,1;cif=1;custom=352,240,1;qcif=1;maxbr=20000

a=rtpmap:34 H263/90000

---------------------------------------------------

So when this call connects, one side will only get around 1800 k or so of BW for video and without changing the settings on the codec like Vivek has indicated, you won't be able to achieve 1080p on this leg of the call, while the H323 side most certainly will.

If you place a call from the H323 side and target a SIP endpoint, same applies, but the IWF function will send ACK to 200 OK with SDP and set the same "m" line for video to 1920 k vice 6000 k as requested. 

Ran this again on X7.1, and it works fine without making the changes.  Moved the same two devices to X7.0.3 and see this issue. 

Hope this helps, but yes, currently running the code you have on VCS, you will more likely see this issue unless changing the codec settings like Vivek mentioned. 

Hope this helps. 

VR

Patrick

[quake3bak]

Patrick, your explanation is quite helpful to understand why doesn't work.

thanks very much. and my upper head decided to keep this unlicensed status.

I think they thought lincense is expensive...