IntenseDebate - Jeff Schertz

9 years ago @ Jeff Schertz's Blog - Adding Custom Presence... · 0 replies · +1 points

No, the Away status cannot be defined on a custom presence setting.

9 years ago @ Jeff Schertz's Blog - Video Interoperability... · 0 replies · +1 points

No, like I said that is not how it works. Those two codecs are not compatible.

9 years ago @ Jeff Schertz's Blog - Lync Phone Edition and... · 0 replies · +1 points

Max, that approach also can work in some cases and was covered in this older article by Lync MCM Kevin Peters: http://ocsguy.com/2012/05/19/lync-phone-edition-c...

In some scenarios one or both of these options can help resolve the issues. Thanks for the additional input.

9 years ago @ Jeff Schertz's Blog - Lync Phone Edition and... · 0 replies · +1 points

I haven't tried that yet but that may be a more appropriate container for subordinate certificates. Try it out an report back with the results.

9 years ago @ Jeff Schertz's Blog - Video Interoperability... · 0 replies · +1 points

Testing comments on older articles...

9 years ago @ Jeff Schertz's Blog - Video Interoperability... · 2 replies · +2 points

George, you are getting caught up in the details here. The point is that these are NOT compatible. The implementation of H.264 AVC High-Profile that is supported on many Polycom room systems is not directly compatible with H.264 SVC in Lync. It does not matter if the spec documents define capabilities across different codecs with similarly named profiles, the media payload is only one part of a much larger puzzle. The only third party devices directly compatible with Lync 2013 clients are utilizing X-H264UC in some capacity, or leveraging RTV for legacy compatibility. Lync clients cannot negotiate a video session with any systems advertising only H.264 AVC support.

9 years ago @ Jeff Schertz's Blog - SILK Audio in Lync Mob... · 0 replies · +1 points

Thanks Aaron. I don't know exactly when this happened as I haven't tracked the history of mobile client releases as closely as other clients.

9 years ago @ Jeff Schertz's Blog - Video Interoperability... · 4 replies · +1 points

No, that is not the case. While the media payload might be based on AVC the implementation is completely unique and thus the need to support X-H264UC at some level, Lync does not advertise any standard H.264 codec support. The Network Abstraction Layer (NAL) data can be ignored by one side to basically 'drop' the additional SVC data so an AVC decoder can handle it but this does not work natively between H.264 AVC only endpoints and Lync clients. SVC is an annex of H.264 that is completely independent of the AVC profiles like baseline or high.

9 years ago @ Jeff Schertz's Blog - Lync Edge STUN versus ... · 0 replies · +1 points

You cannot control this behavior directly. Only by preventing routes between candidates, and causing the connection tests to fail can you influence which candidates are ultimately used for the sessions. Modifying the SDP would be quite unsupported in Lync and could cause any sort of unknown problems.

9 years ago @ Jeff Schertz's Blog - Video Interoperability... · 6 replies · +1 points

Neither. Polycom to Lync video calls will use either H.264 SVC or RTV depending on the product and version. There is no AVC intero; the profile is irrelevant.

IntenseDebate Comment System

Description

Connect with Jeff Schertz

People I'm following

Jeff Schertz