01-30-2013 02:29 PM - edited 03-18-2019 12:31 AM
Seeing inconsistent behaviour in TCS when dailing the on-demand number versus accessing the GUI and starting a recording. The TCS has the Premium resolution option key and is running TCS5.3
resolution different when using the static on demand recording alias vs. accessing the web gui and starting a recording.
On demand from Phone -
resolution is Windows Media Medium 796x448
MPEG-4 for Quicktime Medium 796x448
Windows Media and MPEG-4 Large 1280x720
presentation and main video was recorded as Joined
When logging in as a creator with own account, the resolutions were
Windows Media Medium 352x240
MPEG-4 for Quicktime Medium 352x240
Windows Media Large 352x240
MPEG-4 for Quicktime Large 352x240
Also, Dual Video listed as on in the Template, yet off while recording.
Any thoughts on why the output would be different when they are using the same template?
thx,
rf
02-13-2013 01:14 PM
Hi
When you dial the on-demand number (inbound to the TCS) vs. dialing out to endpoints to start a recording (outbound from the TCS), are there any differences in the protocol (SIP/H323), bandwidth used? You are using the same recording alias (same template) on the same TCS, are you using the same endpoint to test both scenarios? The recordings will have a range of resolutions which the TCS will negotiate with the encoder based on:
1/ Template format & size
2/ Received video resolution & bandwidth
3/ Stream type (onDemand or live)
For example:
OnDemand video streams will have a max resolution of 1080 p with Premium resolution option key if the call (h323/sip) connects to the TCS with more than 2 mbps of bandwidth using a switching template, and provided the codec's camera is set to favor sharpness instead of motion (favor motion will sacrifice resolution for frame rate). The same scenario for live streams will have a max resolution of 720 p (as designed), because a live stream consumes more resources than OnDemand. Obviously if you use the joined template, it has to sacrifice the height to fit the main video stream and content stream side by side.
For both of your scenarios dialing into the TCS or dialing from the TCS out, is the TCS is receiving the same resolution from the endpoint/bridge and connect at the same bandwidth (provided you are using the same device to test with). This may be a factor in why there is a difference in resolution when dialing in to TCS vs dialing out from TCS.
Hope this helps,
02-13-2013 02:07 PM
Ken,
What I found was that if the call was sent H.323 and interworked before reaching the CTS room, the resolution was poor. By simply dialing number@domian, the call setup was SIP and worked fine.
rf
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide