在 Lync Server 2013 中驗證音訊/視訊會議Validating audio/video conferences in Lync Server 2013

 

主題上次修改日期: 2014-06-05Topic Last Modified: 2014-06-05

驗證排程Verification schedule

每日Daily

測試控管Testing tool

Windows PowerShellWindows PowerShell

必要的權限Permissions required

使用 Lync Server 管理命令介面在本機執行時,使用者必須是 RTCUniversalServerAdmins 安全性群組的成員。When run locally using the Lync Server Management Shell, users must be members of the RTCUniversalServerAdmins security group.

使用 Windows PowerShell 的遠端實例執行時,必須為使用者指派具有執行 Test-CsAVConference Cmdlet 許可權的 RBAC 角色。When run using a remote instance of Windows PowerShell, users must be assigned an RBAC role that has permission to run the Test-CsAVConference cmdlet. 若要查看可使用此 Cmdlet 的所有 RBAC 角色清單,請從 Windows PowerShell prompt 中執行下列命令:To see a list of all RBAC roles that can use this cmdlet, run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Test-CsAVConference"}

描述Description

Test-CsAVConference Cmdlet 會檢查是否有兩個測試使用者可以參與音訊/視頻 (A/V) 會議。The Test-CsAVConference cmdlet checks whether two test users can participate in an audio/video (A/V) conference. 執行 Cmdlet 時,會將兩位使用者登入系統。When the cmdlet runs, the two users are logged on to the system. 在他們成功登入後,第一個使用者會建立 A/V 會議,然後等候第二位使用者加入該會議。After they face successfully logged on, the first user creates an A/V conference, and then waits for the second user to join that conference. 資料一開始短暫的交換後,就會刪除會議,而這兩個測試使用者已登出。After a brief exchange of data, the conference is deleted and the two tests users are logged off.

請注意,Test-CsAVConference 不會在兩個測試使用者之間進行實際的 A/V 會議。Note that Test-CsAVConference does not conduct an actual A/V conference between the two test users. 相反地,指令程式會驗證這兩個使用者是否可以進行所有必要的連線,以進行這類會議。Instead, the cmdlet verifies that the two users can make all the connections necessary to conduct such a conference.

您可以在 Test-CsAVConference找到此命令的進一步範例。Further examples for this command can be found at Test-CsAVConference.

執行測試Running the test

您可以使用一對預先設定的測試帳戶來執行 Test-CsAVConference Cmdlet (請參閱設定測試帳戶以執行 Lync Server 測試) 或任何兩個已啟用 Lync Server 之使用者的帳戶。The Test-CsAVConference cmdlet can be run using either a pair of preconfigured test accounts (see Setting Up Test Accounts for Running Lync Server Tests) or the accounts of any two users who are enabled for Lync Server. 若要使用測試帳戶執行此檢查,您只需要指定所測試之 Lync Server 集區的 FQDN。To run this check using test accounts, you just have to specify the FQDN of the Lync Server pool being tested. 例如:For example:

Test-CsAVConference -TargetFqdn "atl-cs-001.litwareinc.com"

若要使用實際使用者帳戶執行這項檢查,您必須建立兩個 Windows PowerShell 認證物件 (包含每個帳戶之帳戶名稱和密碼) 的物件。To run this check using actual user accounts, you must create two Windows PowerShell credentials objects (objects that contain the account name and password) for each account. 然後,您必須在呼叫 Test-CsAVConference 時,包含這兩個帳戶的認證物件和 SIP 位址:You must then include those credentials objects and the SIP addresses of the two accounts when they call Test-CsAVConference:

$credential1 = Get-Credential "litwareinc\kenmyer"
$credential2 = Get-Credential "litwareinc\davidlongmire"
Test-CsAVConference -TargetFqdn "atl-cs-001.litwareinc.com" -SenderSipAddress "sip:kenmyer@litwareinc.com" -SenderCredential $credential1 -ReceiverSipAddress "sip:davidlongmire@litwareinc.com" -ReceiverCredential $credential2

如需詳細資訊,請參閱 Test-CsAVConference Cmdlet 的說明文件。For more information, see the Help documentation for the Test-CsAVConference cmdlet.

決定成功或失敗Determining Success or Failure

如果指定的使用者可以成功完成 A/V 會議,您會收到類似下列的輸出,並將 Result 屬性標示為 [ 成功]:If the specified users can successfully complete an A/V conference, you'll receive output similar to this, with the Result property marked as Success:

TargetFqdn: atl-cs-001.litwareinc.comTargetFqdn : atl-cs-001.litwareinc.com

結果:成功Result : Success

延遲:00:00:02.6841765Latency : 00:00:02.6841765

錯誤:Error :

診斷:Diagnosis :

如果使用者無法完成會議,則結果會顯示為 [失敗],而且會在 [錯誤] 和 [診斷] 屬性中記錄其他資訊:If the users can not complete the conference, then the Result will be shown as Failure, and additional information will be recorded in the Error and Diagnosis properties:

TargetFqdn: atl-cs-001.litwareinc.comTargetFqdn : atl-cs-001.litwareinc.com

結果:失敗Result : Failure

延遲:00:00:00Latency : 00:00:00

錯誤:404,未找到Error : 404, Not Found

診斷: ErrorCode = 4005、Source = atl-cs-001.litwareinc.com、Diagnosis : ErrorCode=4005,Source=atl-cs-001.litwareinc.com,

原因 = 未啟用 SIP 的目的 URI 或不是Reason=Destination URI either not enabled for SIP or does not

存在。exist.

DiagnosticHeader。Microsoft.Rtc.Signaling.DiagnosticHeader

例如,上一個輸出會指出測試失敗的原因是,至少有兩個使用者帳戶之一無效,原因是該帳戶不存在,或是尚未對 Lync Server 啟用該帳戶。For example, the previous output states that the test failed because at least one of the two user accounts was not valid, either because the account does not exist or because the account has not been enabled for Lync Server. 您可以執行類似如下的命令,確認兩個測試帳戶是否存在,以及是否已為 Lync Server 啟用:You can verify the existence of the two test accounts, and whether they were enabled for Lync Server, by running a command similar to the following:

"sip:kenmyer@litwareinc.com","sip:davidlongmire@litwareinc.com" | Get-CsUser | Select-Object SipAddress, enabled

如果 Test-CsAVConference 失敗,則您可能想要重新執行測試,這次包括 Verbose 參數:If Test-CsAVConference fails, then you might want to rerun the test, this time including the Verbose parameter:

Test-CsAVConference -TargetFqdn "atl-cs-001.litwareinc.com" -Verbose

包含 Verbose 參數時 Test-CsAVConference 會傳回每個動作的逐步帳戶,檢查它在檢查指定的使用者是否有權參加 AV 會議時所嘗試的每一個動作。When the Verbose parameter is included Test-CsAVConference will return a step-by-step account of each action it tried when it checked the ability of the specified users to participate in an AV conference. 例如,假設您的測試失敗,且您收到下列診斷:For example, suppose that your test fails and you receive the following Diagnosis:

ErrorCode = 1008,Source = accessproxy = litwareinc,Reason = 無法解析 DNS SRV 記錄ErrorCode=1008,Source=accessproxy.litwareinc.com,Reason=Unable to resolve DNS SRV record

如果您使用 Verbose 參數重新執行測試,傳回的逐步資訊將會包含類似以下的輸出:If you rerun the test using the Verbose parameter, the step-by-step information returned will include output similar to this:

詳細:「註冊」活動已開始。VERBOSE: 'Register' activity started.

傳送註冊要求:Sending Registration request:

目標 Fqdn = atl-cs-001.litwareinc.comTarget Fqdn = atl-cs-001.litwareinc.com

使用者 Sip 位址 = sip:davidlongmire@litwareinc.comUser Sip Address = sip:davidlongmire@litwareinc.com

註冊機構埠 = 5061。Registrar Port = 5061.

已選取 Auth Type ' Trusted」。Auth Type 'Trusted' is selected.

「註冊」活動已開始。'Register' activity started.

傳送註冊要求:Sending Registration request:

目標 Fqdn = atl-cs-001.litwareinc.comTarget Fqdn = atl-cs-001.litwareinc.com

使用者 Sip 位址 = sip:kenmyer@litwareinc.comUser Sip Address = sip:kenmyer@litwareinc.com

註冊機構埠 = 5061。Registrar Port = 5061.

已選取 Auth Type ' Trusted」。Auth Type 'Trusted' is selected.

無法註冊端點的例外狀況。An exception 'The endpoint was unable to register. 如需特定原因,請參閱 ErrorCode。 'See the ErrorCode for specific reason.' 工作流程期間發生occurred during Workflow

該輸出的最後一行指出使用者 sip:kenmyer@litwareinc.com 無法向 Lync Server 註冊。The last line in that output indicates that the user sip:kenmyer@litwareinc.com was unable to register with Lync Server. 這表示您應該確認 SIP 位址 sip:kenmyer@litwareinc.com 是否有效,以及是否已為 Lync Server 啟用相關聯的使用者。That means that you should verify that the SIP address sip:kenmyer@litwareinc.com is valid, and that the associated user is enabled for Lync Server.

測試可能失敗的原因Reasons why the test might have failed

以下是一些 Test-CsAVConference 可能失敗的常見原因:Here are some common reasons why Test-CsAVConference might fail:

  • 您指定的使用者帳戶無效。You specified a user account that is not valid. 您可以執行類似如下的命令,以確認使用者帳戶是否存在:You can verify that a user account exists by running a command similar to this:

    Get-CsUser "sip:kenmyer@litwareinc.com"
    
  • 使用者帳戶有效,但目前未啟用 Lync Server 的帳戶。The user account is valid, but the account is currently not enabled for Lync Server. 若要確認是否已為 Lync Server 啟用使用者帳戶,請執行類似下列的命令:To verify that a user account is enabled for Lync Server, run a command similar to the following:

    Get-CsUser "sip:kenmyer@litwareinc.com" | Select-Object Enabled
    

    如果 Enabled 屬性設定為 False,表示目前未啟用 Lync Server 的使用者。If the Enabled property is set to False that means that the user is currently not enabled for Lync Server.