最新的Microsoft Enterprise Voice & Online Services with Microsoft Lync Server 2013 (070-337日本語版) - 070-337日本語免費考試真題

Explanation/Reference:
The URI Type must be set to SIP URI and the VoIP Security was set to Secured. Reference: Lync and Exchange UM Integration

說明：（僅 Fast2test 成員可見）

Explanation/Reference:
http://lync70337.freeforums.org/wingtip-lync-server-2013-infrastructure-t40.html
Ensure that the New York users and the Boston users who have IP-PBX phones can call each other without
using the PSTN.
2 Mediation server matches Enterprise Voice Requirement.
MUST not depend on a single component.
2 lync trunks are to Chicago and Boston
NY already has 2 gateways. No more need to be added.

Explanation/Reference:
^(\d{7})$
local seven-digit number
^0(\d{9})$
Long distance within Netherlands. Add prefix 0.
International. Add prefix 00

Explanation:
http://technet.microsoft.com/en-us/library/aa997471(v=exchg.141).aspx
Dials 0 Box 1: Key Mapping Box 2: Operator Extension
Dials 1 Box 3: Key Mapping Box 4: Normalization rule
Waits Box 5: Dialing rule entry Box 6: Operator extension
Operator Extension Enter the extension you want callers to connect with when they press zero. Could be an Auto Attendant, a specific person, or an external
Dial-in conferencing users can press keys on the telephone keypad to perform dual-tone multi frequency (DTMF) commands. DTMF commands enable users who dial in to a conference to control conference settings (such as muting and unmuting themselves or locking and unlocking the conference) by using the keypad on their telephone. You can use cmdlets to modify the keys used for the DTMF commands.
number.
A dialing rule entry is used to define the telephone numbers and number masks for incountry/ region and international calls that can be made by UM-enabled users who are associated with a UM mailbox policy. Each dialing rule determines the types of calls that users within a dialing rule group can make.

說明：（僅 Fast2test 成員可見）

Explanation:
Box 1: Snooper utility Box 2: Microsoft Office Communications Server Remote Connectivity Analyzer Box 3: Office 365 Lync Online Transport Reliability IP Prope (TRIPP) tool Box 4: Microsoft Online Service Diagnostics and Logging (MOSDAL) Support Toolkit
Lync Online - Transport Reliability IP Probe (TRIPP Tool) This reliability tool tests your Internet connection to a Microsoft Lync Online Service data center and measures the response times, bandwidth, allowed ports, route taken, and overall connection quality with respect to Real Time Media. The results can help you evaluate your network configuration for potential use with the Microsoft Lync Online Service. This tool does not engage any of the offerings from Microsoft Lync Online Service.
Microsoft Office Communications Server Remote Connectivity Analyzer The Office Communications Server Remote Connectivity Analyzer is a great tool for performing testing, troubleshooting, and diagnostics on Communications Server 2007 and Communications Server 2007 R2 deployments, and should server as your initial stop when attempting to troubleshoot a Communications Server Edge Server connectivity issue. The Office Communications Server Remote Connectivity Analyzer is a web site that Communications Server administrators can use to validate and diagnose end-to-end Communications Server scenarios. The site simulates multiple Office Communications Server client access scenarios from outside the customer's infrastructure and reports whether the test was successful. If the test fails, the tool informs you exactly where in the process the test failed, as well as provides troubleshooting tips about resolving the issue.
The Microsoft Online Services Diagnostics and Logging (MOSDAL) Support Toolkit performs network diagnostics and collects system configuration, network configuration, and logging information for applications that are used to connect to Microsoft Business Productivity Online Standard Suite (BPOSS) or to Microsoft Office 365. The logs and diagnostic information that the tool generates provide data that helps technical support professionals troubleshoot configuration, network, installation, and other service-related issues. The MOSDAL Support Toolkit collects log files, registry keys, and configuration settings that would otherwise require time-consuming and labor-intensive collection by using separate tools.

Explanation:
http://lync70337.freeforums.org/contoso-plan-the-subnets-for-call-admission-control-cac-t42.html
TechNet CLEARLY tells, with black letters on white background:
1) A/V EDGE to get involved in CAC-related Subnet definition and 2) YES we DO use 32-bit mask...
so for New York this is 131.107.100.3/32 ...
NO .../24: why include WHOLE subnet where we only need public IP of A/V Edge?
First all, the question is 'for CAC and media bypass'.
Now, from link: http://technet.microsoft.com/en-us/library/gg398585.aspx, we know
####
Media bypass and bandwidth reservation are mutually exclusive. If a media bypass is employed for a call,
call admission control is not performed for that call. The assumption here is that there are no links with
constrained bandwidth involved in the call. If call admission control is used for a particular call that involves
the Mediation Server, that call cannot employ media bypass.
#####
For CAC itself, link: http://technet.microsoft.com/en-us/library/gg398334.aspx. Read bottom of the page, "it
is important that subnets entered during network configuration on the server are actual subnets instead of
virtual subnets". It explained why 192.168.8.0/21, 30.0/23, ..
Now considering A/V edge server, link: http://technet.microsoft.com/en-us/library/gg425827.aspx. It says: If you deploy Audio/Video Edge Servers, the public IP addresses of each Edge Server must be associated with the network site where the Edge Server is deployed. Each public IP address of the A/V Edge Server must be added to your network configuration settings as a subnet with a subnet mask of 32
NY: 131.107.100.0/24 192.168.8.0/21
LA: 192.168.30.0/23
Miami: 192.168.20.0/24
Houston: 192.168.40.0/24
The 192.168.x.x configurations as per defined in scenario.
Then we need a public network address for New York. We must not use the /32 network mask.