Module2

Module 2Designing and Implementing Exchange Server 2013 Unified Messaging

Microsoft Official Course120342A2: Designing and Implementing Exchange Server 2013 Unified MessagingModule OverviewDesigning a Unified Messaging DeploymentDeploying and Configuring Unified Messaging ComponentsDesigning and Implementing Exchange Server 2013 Unified Messaging Integration with Lync Server 2013Presentation: 45 minutesLab: 60 minutesAfter completing this module, students will be able to:Design a deployment of Hyper-V in Microsoft Exchange Server 2013.Define the virtualization requirements for Exchange Server 2013.Required MaterialsTo teach this module, you need the Microsoft Office PowerPoint file 20342A_04.pptx.Important: We recommend that you use PowerPoint 2007 or a newer version to display the slides for this course. If you use PowerPoint Viewer or an older version, all the features of the slides might not display correctly.Preparation TasksTo prepare for this module:Read all of the materials for this module.Practice performing the demonstrations and the lab exercises.Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance.

220342A2: Designing and Implementing Exchange Server 2013 Unified MessagingLesson 1: Designing a Unified Messaging DeploymentBusiness Requirements for Unified MessagingCollecting Information For a Unified Messaging DesignDesigning Infrastructure Requirements for Unified MessagingDesign Considerations for VoIP GatewaysDesigning for Server ScalabilityDesigning Highly Available DeploymentsDesigning for Office 365 Unified MessagingDesigning for Unified Messaging SecurityConsideration of Codecs and File FormatsHighlight the importance of planning the Unified Messaging deployment before implementation. Before deploying Unified Messaging, the organization needs to understand the business requirements that will be met by the deployment, and how Unified Messaging will fit in the existing infrastructure.QuestionDiscussion: Designing a Unified Messaging Server DeploymentAnswerA. Datum has a consolidated datacenter running a single Exchange 2013 server with both the Mailbox Server and Client Access server roles deployed on the server. The Exchange 2013 server and an IP-PBX are deployed in London. A. Datum has opened branch offices in Munich, Germany and in Singapore. Stand-alone PBX are deployed in each branch office. The London location has about 500 users, the office in Munich has about 100 users and the Singapore office has about 10 users. A. Datum has asked you enhance their Exchange 2013 infrastructure and fulfill the following requirements:You need to implement Exchange 2013 Unified MessagingExchange 2013 servers should be deployed only in the London data center.The Unified Messaging system must be high availableUsers in all locations must be able to use Unified MessagingAn auto-attendant must be available for the London and Munich officesWhat changes will you need to make to the infrastructure to address these requirements?What new server and hardware components will need to be deployed? What potential issues would you see with the deployment?320342A2: Designing and Implementing Exchange Server 2013 Unified MessagingBusiness Requirements for Unified MessagingConsolidated access to voice mail and emailVoice Mail ProtectionAuto Attendant servicesReduction of administrative overheadAvailability requirements

Highlight for students the importance of understanding the organizations business requirements before starting the Unified Messaging design. The business requirements will provide guidance on the scope of the design as well as define how the different components will be deployed. Ask students what they see as the primary business requirement for Unified Messaging in their organization. 420342A2: Designing and Implementing Exchange Server 2013 Unified MessagingCollecting Information For a Unified Messaging DesignIdentify the number of phone and voice mail usersand the anticipated call volumes Document the current telephony environment Identify the storage requirements for voice mail Identify the network requirements for Unified Messaging Describe the different types of information that need to be collected before implementing Unified Messaging. In most cases, the most important information to gather will be the total number of users and the expected call volumes. This will be the most important information when you plan the size of the Unified Messaging infrastructure. Also make sure that you understand the current telephone system. Exchange 2013 Unified Messaging must integrate with the telephone system to provide any functionality, so ensure that the current telephone system can be integrated with Unified Messaging, or that there is a plan in place to implement a compatible system.520342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDesigning Infrastructure Requirements for Unified MessagingServer Mailbox server Client Access serverOther infrastructure requirements: AD DS PBX VoIP gateway VoIP phoneFor Unified Messaging, you need additional MegaCycles (CPU) and RAM on all Mailbox Servers with Unified Messaging enabled users.Voice Mail processing is a CPU-intensive process and needs to store the audio file in RAM.Mention that Lync Server 2013 can be implemented in place of the PBX and VoIP gateway. In the configuration, Lync Server 2013 provides the telephone system, and integrates with Exchange Server 2013 Unified Messaging. 620342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDesign Considerations for VoIP GatewaysVerify that the IP-PBX or VoIP gateways are compatible with Exchange Server 2013Plan the relationship between multiple IP gateways and Client Access serversImplement multiple components for multi-location organizationsPlan for telephony providers Call Number Block switching

Make sure the students understand the need for certification of connected components, such as gateways or PBXs. Microsoft will only provide support for the environment if certified components are used.720342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDesigning for Server Scalability ProcessorMinimum: 2 processor coresRecommended: 8 processor coresWith Outlook Voice Access: 12 processor cores MemoryMinimum: 4 GB for Unified MessagingRecommended: 2 GB per processor core StorageNumber of usersNumber of language packsProvide scalability by deploying multiple Client Access and Mailbox serversMention to students that the hardware requirements listed in this topic are preliminary and may be updated as Microsoft provides more information on scaling Exchange 2013 servers. 820342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDesigning Highly Available DeploymentsPlan for multiple PSTN connections or multiple SIP trunksPlan for multiple VoIP gateways connected to redundant PSTN connectionsImplement multiple Client Access servers and Mailbox servers in a highly available configurationEmphasize the importance of ensure that all components in the Unified Messaging deployment are highly available. 920342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDesigning for Office 365 Unified Messaging

PBXIP PBXVoIP GatewayLync 2013Border ControllerExchange UMOffice 365Lync 2013Internal IP NetworkPublic IP NetworkSIP/TLS, SRTPSIP/TCP, SIP/TLS, RTP, SRTPSIP/TCP, SIP/TLS, RTP, SRTPSIP/TLS, SRTPAsk students if they are considering implementing Exchange Online for email messaging. If they are, then spend some additional time on this slide describing the communication flow between the local phone system and Exchange Unified Messaging hosted at Exchange Online.1020342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDesigning for Unified Messaging SecurityThe VoIP Security mode can be set as:SIP secured, which only encrypts SIP trafficSecured, which encrypts SIP and Media trafficUnsecured, which uses no encryptionEnsure that other VoIP devices support the level of encryption configured on the Exchange 2013 serversVoIP security requires trusted certificates on the Exchange 2013 Client Access and Mailbox servers, and on other VoIP devicesAsk students how strict their organizations are about requiring encryption for traffic on their internal networks. Most organizations do not see this as a high priority, so they find using the unsecured option for VoIP acceptable. Other organizations may see this as a higher priority and will choose to implement mutual TLS for VoIP.The other critical factor in making this choice is whether the other VoIP devices on the network can support mutual TLS. Remind students that they need to review the specifications for all VoIP devices to ensure that the selected security model is supported. 1120342A2: Designing and Implementing Exchange Server 2013 Unified MessagingConsideration of Codecs and File FormatsCodecs for encoding media streamsG.711 (PCMA or PCMU) G.723.1 defaultRTAudio available with Lync Server onlyChoosing a codec for encoding voice messagesMP3 default codec, provides a good balance of supported devices, quality and compressionWMA provides the highest combination of compression and sound quality GSM 06.10 - no compression, highest qualityG.711 PCM Linear high compression and qualityUse the Set-UMDialPlan to configure codec settings

Students may not have any familiarity with audio codecs, and it is not critical that you spend a lot of time explaining this. One of the key points is to ensure that students understand that a compatible codec is required for communication between the Exchange servers and the VoIP gateways. In most cases, the default setting should be fine. The second key point to stress is that students need to consider the effect that the codec will have on the size of voice mail messages. In most situations, the default setting using the MP3 codec should be fine. If higher quality recordings are required, the WMA codec should be the second choice.1220342A2: Designing and Implementing Exchange Server 2013 Unified MessagingLesson 2: Deploying and Configuring Unified Messaging ComponentsOverview of the Unified Messaging Deployment ProcessConfigure UM IP Gateway ObjectConfiguring UM Dial Plan ObjectsDemonstration: Configuring UM Dial Plans and UM IP GatewaysConfiguring Hunt Group ObjectConfiguring UM Mailbox PoliciesDemonstration: Configuring Mailbox Policy Objects and Enabling Mailboxes for Unified MessagingImplementing UM Auto AttendantsDemonstration: Configuring UM Auto AttendantsConfiguring Protected Voice Mail1320342A2: Designing and Implementing Exchange Server 2013 Unified MessagingOverview of the Unified Messaging Deployment ProcessPrepare the telephone system for integration with Unified MessagingConfigure UM dial plans. UM dial planConfigure UM IP gatewaysConfigure UM hunt groupsConfigure UM mailbox policiesUM-enable usersConfigure UM auto attendants

Use this topic to provide a high level overview of the steps required to deploy Unified Messaging. Do not go into detail at this point, the details come later.1420342A2: Designing and Implementing Exchange Server 2013 Unified MessagingConfigure UM IP Gateway ObjectThe UM IP gateway object:Defines the connecting point between Exchange 2013 servers and the telephone networkRequired a name and IP addressWill contain one or more hunt groups which connect the UM IP gateway to a UM dial planCan be configured in the EAC or Exchange Management ShellRemind the students that the correlation between UM IP Gateway and the physical IP gateway is always 1:1. If the organization is deploying more than one physical IP gateway, they will need to create additional UM IP gateway objects in Exchange.1520342A2: Designing and Implementing Exchange Server 2013 Unified MessagingConfiguring UM Dial Plan ObjectsA UM dial planIs an Active Directory object that logically represents PBXs that share user extensionsCan have a one to one or one to many relationship with PBXsCan be one of three types:Telephone extensionSIP URIE.164May require planning to ensure complete coverage of all company extensions and locationsEmphasize the importance of understanding the PBX configuration in the organization when implementing the UM dial plans. In most cases, the UM dial plan will copy the PBX dial plan. The number of UM dial plans is also determined by the number of PBX and the PBX extension design.1620342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDemonstration: Configuring UM Dial Plans and UM IP GatewaysIn this demonstration, you will see how to:Configure a UM Dial planConfigure a UM IP GatewayPreparation StepsTo perform this demonstration, ensure that the 20342A-LON-DC1, 20342A-LON-MBX1, and 20342A-LON-CAS1 virtual machines are running. Sign into all virtual machines using the Adatum\Administrator account with the password Pa$$w0rd.Demonstration StepsOn LON-CAS1, open Internet Explorer and connect to https://LON-CAS1.adatum.com/ecp.Sign in as Adatum\administrator using the password Pa$$w0rd.In the Features pane, click unified messaging.On the UM dial plans tab, click New.In the new UM dial plan window, type UM-Dialplan in the Name field.Verify that the Extension length (digits) field is set to 5.Under Dial plan type, click Telephone extension. Under VoIP security mode, click Unsecured.Under Audio language, accept the default. Only the English (United States) is available because it is the only language pack that is installed.In the Country/Region Code field, type 1 for the US country code. Click save.Click UM-Dialplan and click Edit.In the UM-Dialplan window, click configure.In the second UM-Dialplan window, click dial codes.In the Outside line access code field, type 9.In the International access code field, type 00.1720342A2: Designing and Implementing Exchange Server 2013 Unified Messaging(More notes on the next slide)On the Outlook Voice Access tab, in the Outlook Voice Access numbers field, type 12224445555 and click Add.On the settings tab, review the default settings.On the dialing authorization tab, review the default settings.On the transfer & search tab, review the default settings.. Click save, and then click close.Click the UM IP gateways tab.Click Add.In the new UM IP gateway window, type UM-Gateway in the Name field.In the Address field, type 172.16.0.40.Under UM dial plan, click browse.Click UM-Dialplan and click ok.Click save.Leave the EAC open for the next demonstration.1820342A2: Designing and Implementing Exchange Server 2013 Unified MessagingConfiguring Hunt Group ObjectA hunt group:Is a group of PBX or Lync resources or extension numbers, that represent a collection of like endpointsIs used to distribute calls efficiently into or out of a given business unitIs accessed by using a pilot number

Hunt group objects:Represent a hunt group configured at the PBX, to direct calls to a VoIP gatewayAre contained within a UM IP gateway object

A default hunt group is automatically generated when you create a UM IP gateway object. You can create additional hunt group objects if required.1920342A2: Designing and Implementing Exchange Server 2013 Unified MessagingConfiguring UM Mailbox PoliciesUM mailbox policy properties can include:Dial plan (required)Maximum greeting length and speech-to-text announcementNumber of unsuccessful login attempts before password resetMinimum digits required in a PINNumber of days until a new PIN is requiredCalling restrictionsWhen planning UM mailbox policies:Use the default UM mailbox policy if all users need the same settingsCreate additional UM mailbox policies if some users require different settingsMention to students that you will demonstrate the UM mailbox policy settings in the next demonstration.Ask students whether they anticipate needing more than one UM mailbox policy in their organization. If they need more than one, ask them to describe the requirements that will require them to create more than one policy.2020342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDemonstration: Configuring Mailbox Policy Objects and Enabling Mailboxes for Unified MessagingIn this demonstration, you will see how to:Configure UM mailbox policiesEnable mailboxes for UMPreparation StepsTo perform this demonstration, ensure that the 20342A-LON-DC1, 20342A-LON-MBX1, and 20342A-LON-CAS1 virtual machines are running. Sign into all virtual machines using the Adatum\Administrator account with the password Pa$$w0rd.Demonstration StepsOn LON-CAS1, in the EAC, click the UM dial plans tab.Double click UM-Dialplan.In the UM Mailbox Policies section, double click UM-Dialplan Default Policy.Click the general tab and review the general UM mailbox policy settingsClick the message text and review the message text options. These messages are sent to users when the listed UM actions occur.Click the PIN policies tab and review the PIN setting options.Click the dialing authorization and review the UM outgoing call restrictionsClick the protected voice mail tab and review the RMS protection settingsClick cancel, and then click close.In the EAC, click recipients in the Features pane.Click Amr Zaki, and click edit.Click mailbox features.Under Phone and Voice Features, click Enable.In the Enable UM mailbox window, under UM mailbox policy, click browse.Click UM-Dialplan Default Policy, and click ok.2120342A2: Designing and Implementing Exchange Server 2013 Unified Messaging(More notes on the next slide)Click next.In the Extension number field, type 22222.Click Type a PIN (minimum length: 6) and type 135792.Click finish, and then click save.Leave the EAC open for the next demonstration.2220342A2: Designing and Implementing Exchange Server 2013 Unified MessagingImplementing UM Auto AttendantsUM auto attendants:Provide an automated call answering serviceEnable callers to search the organization phone listCan be configured with many organization-specific settingsCan be configured to support multiple languagesInstall the language pack for each language on the mailbox serversConfigure a UM auto attendant for each languageConfigure the main UM auto attendant with prompts to choose alternate languagesEveryone has experience with auto attendant services. Ask students about their experience. Which auto attendant services have they found useful and which auto attendant services have they found irritating. Ask students to describe the features of auto attendants that they enjoyed using and use these features to provide guidance on how they should design the auto attendants in their organization.2320342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDemonstration: Configuring UM Auto AttendantsIn this demonstration, you will see how to configure an auto attendantPreparation StepsTo perform this demonstration, ensure that the 20342A-LON-DC1, 20342A-LON-MBX1, and 20342A-LON-CAS1 virtual machines are running. Sign into all virtual machines using the Adatum\Administrator account with the password Pa$$w0rd.Demonstration StepsOn LON-CAS1, in the EAC, in the unified messaging pane, click the UM dial plans tab.Double-click UM-Dialplan.In the UM Auto Attendants section, click New.In the Name field, type UMAutoAttendant.Select the Create this auto attendant as enabled check box.Select the Set the auto attendant to respond to voice commands check box.In the Access numbers field, type 12224443333, and click Add.Click the save button to save the configuration.In the EAC, double-click UMAutoAttendant.On the general tab, review the available settings.On the greetings tab, review the available settings.On the business hours tab, review the available settings.On the menu navigation tab, review the available settings.On the address book and operator access tab, review the available settings.On the dialing authorization tab, review the available settings.Click cancel, and then click close.2420342A2: Designing and Implementing Exchange Server 2013 Unified MessagingConfiguring Protected Voice MailProtected Voice Mail applies AD RMS protection to voice messages so they cannot be read by unauthorized users and cannot be forwardedTo configure:Implement Exchange Server 2013 Unified MessagingConfigure a UM mailbox policy to use Protected Voice MailDeploy and configure the integration with AD RMSVerify that users are using a supported client

2520342A2: Designing and Implementing Exchange Server 2013 Unified MessagingLesson 3: Designing and Implementing Exchange Server 2013 Unified Messaging Integration with Lync Server 2013What is Lync Server 2013?Demonstration: Exploring Lync 2013 FeaturesEnterprise Voice Components in Lync Server 2013Overview of Exchange Server 2013 and Lync Server 2013 IntegrationImplementing Exchange Server Unified Messaging Integration with Lync Server2620342A2: Designing and Implementing Exchange Server 2013 Unified MessagingWhat Is Lync Server 2013?Lync Server 2013 provides the following features:Instant messagingPresence informationWeb conferencingAudio conferencingIntegration with Office applicationsVoIP telephonyResponse Group serviceSupport for remote usersSupport for federation

Ask students whether any of them have deployed Lync Server or Office Communications Server. If students have not worked with these products before, you might want to spend some extra time explaining the features available in Lync. You can also combine this topic with the next demonstration to demonstrate the features as you discuss them.2720342A2: Designing and Implementing Exchange Server 2013 Unified MessagingDemonstration: Exploring Lync 2013 FeaturesIn this demonstration, you will see how to:Enable user accounts for Lync Server 2013Use Instant Messaging and Desktop Sharing in Lync 2013Create and join a Lync MeetingThe purpose of this demonstration is to provide students with an overview of Lync Server 2013. Feel free to show other features if students are interested.Preparation StepsTo perform this demonstration, ensure that the 20342A-LON-DC1, 20342A-LON-MBX1, 20342A-LON-CAS1, 20342A-LON-LY1, 20342A-LON-CL1, and the 20342A-LON-CL2 virtual machines are running. Sign into all virtual machines except for 20342A-LON-CL1 and 20342A-LON-CL2 using the Adatum\Administrator account with the password Pa$$w0rd. Do not sign into the client virtual machines until instructed to do so in the demonstration. Demonstration StepsOn LON-LY1, on the Start screen, click Lync Server Control Panel.In the Security window sign in as Administrator, using the password Pa$$w0rd.In the Lync 2013 Control Panel, click Users.Click Enable users.In the New Lync Server User window, click Add.In the Search field, type April and click Find.Click April Reagan and click OK.Under Assign users to a pool, click LON-LY1.ADATUM.COM.Under Generate users SIP URI verify that Use users email address is selected.Accept the other defaults, and click Enable in the taskbar.Repeat steps 4-10 to enable Brad Suttons account.Connect to the 20342A-LON-CL1 virtual machine.Sign in as April, using the password Pa$$w0rd.Connect to the 20342A-LON-CL2 virtual machine.2820342A2: Designing and Implementing Exchange Server 2013 Unified Messaging(More notes on the next slide)Sign in as Brad, using the password Pa$$w0rd.On LON-CL1, right-click the Start screen, and click All apps.Click Outlook 2013.On the Welcome to Outlook 2013 page, click Next.On the Add an Email Account page, click Next.On the Auto Account Setup page, click Next.If a Security Alert screen appears, click Yes.Click Finish.In the First things first dialog box, click Ask me later, and click Accept.On LON-CL2, repeat steps 16-23, creating a user profile for Brad Sutton.On LON-CL1, right-click the Start screen, and click All apps.Click Lync 2013.In the Windows Security Alert dialog box, click Allow access.In the User Account Control dialog box, type Administrator as the user name and Pa$$w0rd as the password. Click Yes.Verify that April is automatically logged on to Lync 2013.On LON-CL2, repeat steps 25-29 logging Brad on to Lync 2013.On LON-CL2, in the Find someone field, type April@adatum.com and press Enter.In the Instant Message dialog box that opens, type a short message and press Enter.On LON-CL1, click the Instant Message popup, respond to Brads message, and press Enter.In the Instant Message window, click the Manage Presentable Content icon at the bottom of the window, and click Desktop.29(More notes on the next slide)20342A2: Designing and Implementing Exchange Server 2013 Unified MessagingIn the Lync message, click OK.On LON-CL2, click Accept Meeting Content. Verify that Brads desktop is shared.Click Request Control.On LON-CL1, click Yes to give April control of the desktop.On LON-CL2, verify that April has control of the desktop.On LON-CL2, click Release Control. On LON-CL1, click Stop Presenting.On LON-CL2, in Outlook, click the Calendar icon.Click New Lync Meeting.In the To field, type April, in the Subject field, type a subject. In the Start time field, click a time within the next 30 minutes. Click Send.On LON-CL1, in the meeting request from Brad, click Accept, and then click Send the Response Now.In the Calendar, open the meeting request, and click Join Lync Meeting.Click Dont join audio, and click OK.On LON-CL2, open the meeting request, and click Join Lync Meeting. Click Dont join audio, and click OK.Verify that both users can connect to the meeting request. Close all open windows on LON-CL1 and LON-CL2.3020342A2: Designing and Implementing Exchange Server 2013 Unified MessagingEnterprise Voice Components in Lync Server 2013Placing and receiving voice callsPSTN connectivityBasic call featuresAdvanced calling featuresEmergency servicesVoice resiliencyStress that Enterprise Voice is designed to be a complete VoIP-based voice solution. It provides almost all of the same functionality as any advanced PBX.3120342A2: Designing and Implementing Exchange Server 2013 Unified MessagingOverview of Exchange Server 2013 and Lync Server 2013 IntegrationExchUCUtil script:Grants the Lync server accounts permission to read Exchange Unified Messaging objectsCreates a UM IP gateway for each Lync Server 2013 poolAssociates the gateway with the UM IP dial plansExchange UM Integration Utility:Creates contact objects in AD DS for UM subscriber access and auto attendant objectsDeploy trusted certificates on all Exchange Servers and Lync serversUse the topic to describe the integration objects that are required to enable Lync Server 2013 and Exchange Server 2013 to communicate with each other. From the Exchange perspective, it just needs a SIP URI dial plan, and a UM IP gateway so that it knows how to route all calls associated with the dial plan. From the Lync perspective, it needs the contact numbers with the associated SIP addresses and phone numbers so that it knows how to route the calls to the Exchange 2013 Client Access server.3220342A2: Designing and Implementing Exchange Server 2013 Unified MessagingImplementing Exchange Server Unified Messaging Integration with Lync ServerInstall Lync Server 2013Configure Enterprise Voice in Lync ServerVerify certificatesConfigure a secure SIP URL dial plansAdd all Client Access and Mailbox servers to the SIP dial planSet the Unified Messaging services to dual modeRun the ExchUCUtil.ps1 script on an Exchange ServerRun OcsUMUtil.exe on a Lync serverEnable users for Unified Messaging and Enterprise VoiceThis topic provides a high level overview of what the students will be doing in the lab, so use the slide to explain each step in the implementation process. 3320342A2: Designing and Implementing Exchange Server 2013 Unified MessagingLab: Designing and Implementing Exchange Server 2013 Unified MessagingExercise 1: Designing the Unified Messaging ImplementationExercise 2: Configuring Unified Messaging FeaturesExercise 3: Configuring Unified Messaging Integration with Lync Server 2013Exercise 4: Verify Unified Messaging FunctionalityLogon InformationVirtual machines20342A-LON-DC120342A-LON-CAS120342A-LON-MBX120342A-LON-CL120342A-LON-CL20342A-LON-LY1

User NameAdatum\AdministratorPasswordPa$$w0rdEstimated Time: 75minExercise 1: Designing the Unified Messaging ImplementationNote: Refer to the student manual for the detailed scenario.Exercise 2: Configuring Unified Messaging FeaturesNow that you have completed your design, the next step is to configure the Unified Messaging components on the Exchange 2013 servers based on your design.

Exercise 3: Configuring Unified Messaging Integration with Lync Server 2013A. Datum has deployed Lync Server 2013 as its VoIP solution. You now need to configure the integration of Unified Messaging and Lync Server 2013 and verify that the integration is correctly configured.Lync is deployed in London data center and it has only a London PSTN connection established via SIP Trunk, it is representing UK, US and France phone numbers.If a customer place a call to the AutoAttendant, they must be able to connect a call to all three region using either the employee name or the given 5-digit extension.You need to configure the entire system integration between Exchange Server 2013 and Lync Server 2013.Instructor Note: Since we do not have an IPGateway for Lync configured/ installed, calls can only be made and simulated via internal Lync SIP users.Exercise 4: Verify Unified Messaging FunctionalityNow that you have configured Exchange 2013 Unified Messaging and configure the integration with Lync Server 2013, you need to verify the deployment. You will enable two users in Lync or Enterprise Voice and verify that the users can call each other using the Lync client. You will then verify that users can use the Exchange Server 2013 Unified Messaging features.Note: This lab exercise requires an audio headset for each student. If a head set is not available, you will not be able to complete this exercise. If you have a headset available, plug the headset in now.

3420342A2: Designing and Implementing Exchange Server 2013 Unified MessagingLab ScenarioA. Datum is an engineering and manufacturing company. The organization is based in London, England, but is rapidly expanding the London location as well as internationally. A. Datum has deployed the core functionality available in Exchange Server 2013, but is now planning to implement some additional features in Exchange Server. A. Datum is deploying Lync 2013 as a VOIP solution. In order to provide a full VOIP solution, A. Datum is planning to deploy Exchange Server 2013 Unified Messaging3520342A2: Designing and Implementing Exchange Server 2013 Unified MessagingLab ReviewWhy did you need to install certificates on the Exchange 2013 Mailbox servers in this lab?How would the lab have changed if you would have implemented the full design that you created in Exercise 1?QuestionWhy did you need to install certificates on the Exchange 2013 Mailbox servers in this lab?AnswerYou had to install the certificates on the Mailbox servers so that the Mailbox servers could establish secure SIP sessions with the Lync 2012 server. The Mailbox servers by default only required self-signed certificates, but they would not have been trusted by the Lync Server.QuestionHow would the lab have changed if you would have implemented the full design that you created in Exercise 1?AnswerYou would need to create additional UM dial plans for each office. Each dial plan would need to be configured with an Outlook Voice Access number and an auto attendant number, and then you would have had to create these additional contacts for Lync Server.3620342A2: Designing and Implementing Exchange Server 2013 Unified MessagingModule Review and TakeawaysReview QuestionsBest PracticeCommon Issues and Troubleshooting TipsReview QuestionsQuestionWhat are the various levels of VoIP security available in Exchange Unified Messaging? If Lync Server 2013 is encrypting both signaling and media, what is the appropriate setting for VoIP security in Exchange Unified Messaging? AnswerThe levels of VoIP security include: Secured, SIPSecured, and Unsecured. The appropriate setting for VoIP security in Exchange Unified Messaging if Lync Server 2013 is encrypting both signaling and media is Secured.Best Practice: Before implementing Unified Messaging, verify the state of your network. If your network has limited available bandwidth, or high latency, the user experience with Unified Messaging will not be positive.For the broadest compatibility, leave Exchange Unified Messaging configured to record voicemail in MP3 format. For maximum compression, configure Exchange UM to record voicemail in WMA format.Common Issues and Troubleshooting TipsCommon Issue: The Lync 2013 client displays warnings that connectivity to Exchange is limitedTroubleshooting Tip: Configure the Autodiscover URL on the Client Access servers to use the name Autodiscover.domain name. Common Issue: Calls to Exchange Unified Messaging cannot be completed.Troubleshooting Tip: Ensure that the VoIP security settings are set appropriately given Lync Server 2013 configuration. 3720342A2: Designing and Implementing Exchange Server 2013 Unified Messaging