Enterprise Voice and Online Services with Microsoft Lync Server 2013 — Lesson 1: Lync Voice Architecture and Planning

Learning Objectives

• Understand server roles, sites, pools, voice features, topologies, and dependencies
• Assess users, locations, numbers, bandwidth, gateways, trunks, and resilience
• Create an enterprise voice and online-services design

Detailed Topics

• Understand server roles: Understand server roles, sites, pools, voice features, topologies, and dependencies
• Assess users: Assess users, locations, numbers, bandwidth, gateways, trunks, and resilience
• Create an enterprise voice and online-services design: Create an enterprise voice and online-services design

Guided Demonstration

1. Review the requirement, users, data, dependencies, permissions, risks, and expected result.
2. Demonstrate the relevant configuration, development, administration, collaboration, analysis, or automation workflow step by step.
3. Capture settings, outputs, logs, screenshots, calculations, test results, and other useful evidence.
4. Compare the observed result with acceptance criteria and explain any corrective action.

Hands-On Activity

Develop a Lync Server 2013 voice architecture.

• Document assumptions, prerequisites, and the planned sequence before starting.
• Complete the activity and preserve evidence of normal, boundary, and failure behavior.
• Record issues, corrective actions, reusable notes, and the next improvement priority.

Scenario Analysis

• Identify the business or technical decision that must be made.
• Compare valid implementation approaches and their trade-offs.
• Consider security, privacy, accessibility, performance, support, and operational impact.

Troubleshooting Focus

• Separate symptoms from causes and collect evidence before applying a fix.
• Check configuration, data, permissions, dependencies, capacity, connectivity, and recent changes.
• Validate rollback, recovery, ownership, user impact, and business continuity.

Validation Checklist

• The requirement, scope, inputs, and expected outcome are clear.
• The selected design or configuration is documented and follows approved standards.
• Normal, boundary, failure, security, accessibility, and operational conditions are reviewed.
• The result is supported by evidence and the next improvement is prioritized.

Lesson Outcome

Learners can explain and apply Lync Voice Architecture and Planning in a realistic scenario and validate the result with documented evidence.