locked
Lync 2013 AVMCU pool RRS feed

  • Question

  • Hello,

    Apologies if this has been asked before, but I am wondering about AVMCU deployment for Lync 2013 (Enterprise edition). In particular, is this configurable to the same level as Lync 2010? I have access to Lync 2010 Enterprise edition and I am able to configure AVMCUs for each of my avpools.

    Is there an equivalent for Lync 2013? Where is this setting?  During the install I don't remember installing/configuring any dedicated AVMCU servers for Lync 2013.  Any more info would be greatly appreciated.

    Thanks,

    Simon

    Thursday, January 16, 2014 11:46 PM

Answers

  • In 2013, we no longer have option to install dedicated AVMCU. Conference usage (including potential grouth) shoud be taken in consideration during the planning phase.

    Drago


    http://www.lynclog.com

    Friday, January 17, 2014 2:21 AM
  • In Lync Server 2013, A/V Conferencing, Monitoring, and Archiving run on Front End Servers and are no longer separate server roles.

    Lisa Zheng
    TechNet Community Support

    • Marked as answer by Lisa.zheng Monday, February 3, 2014 8:38 AM
    Monday, January 20, 2014 9:44 AM

All replies

  • In 2013, we no longer have option to install dedicated AVMCU. Conference usage (including potential grouth) shoud be taken in consideration during the planning phase.

    Drago


    http://www.lynclog.com

    Friday, January 17, 2014 2:21 AM
  • Thanks Drago.

    Is there no concept of an AVMCU in Lync 2013 though? I see that Lync 2013 supports "large conference" mode. What part of the system takes care of instantiating that and maintaining the conference state (and processing of each participants media)?  I see the suggested way is to have multiple Front End servers with mirrored back end servers.

    Sunday, January 19, 2014 4:53 PM
  • There is a lot of logic built-in in to EE pool in regards of modalities, internal load balancing and MCU assignment.

    For example, when EE pool with three servers would host conference, one will host AVMCU, another DataMCU, end so on. When next conference starts (around the same time) different members of the pool will host modalities i.e. you will never end up with all conferences at the moment utilizing server #1 for AVMCU.

    If you plan to host large conferences, >250 participants, it is imperative that you plan for dedicated LC (Large Conference) pool and work the Conference Policies very careful. There are many conditions to consider for LC... We can take this topic offline since it is a long story :-)

    Conferencing is big topic and TechNet offers a lot of resources - getting familiar with the planning phase is key, because any conferencing solution (not Lync specifically) could turn to disaster if not planned correctly.

    Do you have specific concerns or questions?

    .

    Drago


    http://www.lynclog.com

    Sunday, January 19, 2014 5:14 PM
  • The main question I have surrounds configuration of the "servers" you mention in your 2nd paragraph.  In Lync 2010, different servers can be configured through the topology builder and I can spin up / configure more servers running the AVMCU component as required. Is there a similar configuration in Lync 2013?  Where do I configure these servers? I don't recall this being configured during our lab's 2013 install (I can check with our sysadmin though).
    Sunday, January 19, 2014 7:41 PM
  • Ah, I see now. In 2013, we do not have option to "block" (de-select) installation of MCU's components i.e. those are irrevocable part of SE or EE Front End. It is also true that we no longer can provision dedicated AVMCU. The rationale behind this decision is the re-designed (optimized) architecture of Lync 2013.

    This article (http://technet.microsoft.com/en-us/library/dn362852.aspx) describes the usage of “Lync Server 2013 Capacity Planning Calculator” which will help you to scale your deployment properly.

    .

    Drago


    http://www.lynclog.com

    Sunday, January 19, 2014 10:40 PM
  • Many thanks for your reply. Presumably CCCP is still used internally on the front end server between the conference focus and the component for audio-video "modality" conferences?  I had just got my head round this setup (and the protocols used between the Lync front edge and the Lync 2010 AV-MCUs) for Lync 2010 and it seems to have changed for 2013 :-/

    Looking at this knowledge base (http://kbalertz.com/article/2901554) it looks like port 444 is still used for intra-server communications between the front-end and the MCUs.  I'm basically after a front-end server internal flow-diagram type thing showing all the ports / TCP connections / conference establishment paths etc.

    Sunday, January 19, 2014 11:05 PM
  • In Lync Server 2013, A/V Conferencing, Monitoring, and Archiving run on Front End Servers and are no longer separate server roles.

    Lisa Zheng
    TechNet Community Support

    • Marked as answer by Lisa.zheng Monday, February 3, 2014 8:38 AM
    Monday, January 20, 2014 9:44 AM