Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Voice Resiliency in Lync Server 2010<br />Justin Morris<br />UC Consultant (and Australian)<br />@jm_deluxe<br />www.justi...
What’s your story?<br /><ul><li>Have you deployed Lync already?
Connected OCS/Lync to the PSTN before?
Know what a SIP 301 Redirect is?
Know what SDP and RTCP is?
Don’t know what I’m talking about? </li></li></ul><li>New Resiliency Features in Lync<br /><ul><li>DNS Load Balancing
Lync client caches front end IP addresses.
FEs balance users across servers.
HLB only for HTTP traffic.
Registrar Service on each Front End Server.
Backup Registrar.
Limited Functionality Mode in Lync.</li></li></ul><li>Business Requirements<br /><ul><li>Determine them!
Know what it is your organisation wants
Is it productivity gains? Cost savings?
Work out what features of Lync you will deploy.
What level of availability/recovery do you require?
In short - do the necessary due diligence.</li></li></ul><li>What technical solutions are available?<br /><ul><li>Within, ...
Enterprise Edition Front End Pool
Upcoming SlideShare
Loading in …5
×

Voice Resiliency in Lync Server 2010

6,753 views

Published on

Voice Resiliency in Lync Server 2010 presented by Justin Morris at MUCUGL July 2011

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Voice Resiliency in Lync Server 2010

  1. 1. Voice Resiliency in Lync Server 2010<br />Justin Morris<br />UC Consultant (and Australian)<br />@jm_deluxe<br />www.justin-morris.net<br />justin@justin-morris.net<br />
  2. 2. What’s your story?<br /><ul><li>Have you deployed Lync already?
  3. 3. Connected OCS/Lync to the PSTN before?
  4. 4. Know what a SIP 301 Redirect is?
  5. 5. Know what SDP and RTCP is?
  6. 6. Don’t know what I’m talking about? </li></li></ul><li>New Resiliency Features in Lync<br /><ul><li>DNS Load Balancing
  7. 7. Lync client caches front end IP addresses.
  8. 8. FEs balance users across servers.
  9. 9. HLB only for HTTP traffic.
  10. 10. Registrar Service on each Front End Server.
  11. 11. Backup Registrar.
  12. 12. Limited Functionality Mode in Lync.</li></li></ul><li>Business Requirements<br /><ul><li>Determine them!
  13. 13. Know what it is your organisation wants
  14. 14. Is it productivity gains? Cost savings?
  15. 15. Work out what features of Lync you will deploy.
  16. 16. What level of availability/recovery do you require?
  17. 17. In short - do the necessary due diligence.</li></li></ul><li>What technical solutions are available?<br /><ul><li>Within, and for your Central Site
  18. 18. Enterprise Edition Front End Pool
  19. 19. Metropolitan Data Centre Resiliency
  20. 20. Backup Registrar
  21. 21. For your Branch Sites
  22. 22. Survivable Branch Appliance (SBA)
  23. 23. Survivable Branch Server (SBS) + Gateway
  24. 24. Standard Edition Server + Gateway</li></li></ul><li>Resiliency within your Central Site<br /><ul><li>Enterprise Edition Front End Pool
  25. 25. Up to 10 Front End servers
  26. 26. AV Conferencing Server Role can be split out for greater scalability
  27. 27. Backend on SQL 2005-2008 R2 Cluster
  28. 28. Problem: snom phones don’t like EE pools because they can’t understand DNS load balancing</li></li></ul><li>Resiliency within your Central Site<br />
  29. 29. Resiliency for your Central Site<br /><ul><li>Backup Registrar
  30. 30. Requires a Standard Edition server allocated as a Backup Registrar for a pool in Topology Builder.
  31. 31. Secondary DNS SRV records must be created.
  32. 32. Client gets “limited functionality mode”.</li></li></ul><li>Resiliency for your Central Site<br />
  33. 33. Resiliency for your Central Site<br /><ul><li>Metropolitan Data Centre
  34. 34. The most difficult to deploy and manage.
  35. 35. Requires:
  36. 36. Stretched VLAN across sites.
  37. 37. Stretched SQL 2008/2008 R2 cluster.
  38. 38. Synchronous data replication.
  39. 39. <20 ms latency between sites.
  40. 40. Global hardware/DNS load balancing.</li></li></ul><li>Resiliency for your Central Site<br />
  41. 41. Branch Site Resiliency<br /><ul><li>Survivable Branch Appliance (SBA).
  42. 42. 1 RU chassis running Windows and Lync.
  43. 43. Has ISDN E1 ports in it for PSTN connectivity.
  44. 44. Made by hardware vendors.
  45. 45. For 25 - 1000 users.
  46. 46. Has no conferencing capability.
  47. 47. Just Registrar and Mediation services.
  48. 48. Users are homed on this pool (server).</li></li></ul><li>Branch Site Resiliency - SBA<br />
  49. 49. Branch Site Resiliency<br /><ul><li>Survivable Branch Server (SBS) + Gateway.
  50. 50. A Windows server you deploy.
  51. 51. For 1000 - 5000 users.
  52. 52. Has no conferencing capability.
  53. 53. Just Registrar and Mediation services.
  54. 54. Users are homed on this pool (server).</li></li></ul><li>Branch Site Resiliency - SBS<br />
  55. 55. Branch Site Resiliency<br /><ul><li>Standard Edition Server + Gateway
  56. 56. A Windows server you deploy.
  57. 57. For greater than 5000 users.
  58. 58. Does have full conferencing capability i.e. MCUs.
  59. 59. Users are homed on this server.</li></li></ul><li>Branch Site Resiliency – SE Server<br />
  60. 60. Conclusion<br /><ul><li>Know what your existing IT environment is capable of.
  61. 61. Engage your voice, network, security and server teams WELL in advance.
  62. 62. Ensure you understand your voice resiliency requirements and select a solution accordingly.
  63. 63. Enjoy the ride and the awesomeness. </li>

×