In Lync 2013, trunk configuration settings define a relationship between Mediation Server and PSTN gateway, IP-public branch exchange (PBX), or Session Border Controller (SBC) in the service provider. There are cmdlets to create, modify, and delete trunks. In addition, there is a cmdlet Test-CsTrunkConfiguration, which allows us to validate a trunk configuration against a phone number. The previously mentioned cmdlet is part of a particular category of commands, and is known as Lync Synthetic Transactions, which enables testing core functionality by simulating interaction between users, computers, and so on, without having to fire up test workstations with the client installed.
- We can test
2ndtest_encryption_trunk, which we defined in the previous section. Its characteristic is that it has theSRTPModeparameter set toRequired. - The synthetic test will require the trunk configuration. The easiest way to manage this is to save the trunk configuration information in a variable as follows:
$tc = Get-CsTrunkConfiguration –Identity Service:PstnGateway:2ndtest_encryption_trunk
- The last step is to launch the test that verifies a phone number to dial
Test-CsTrunkConfiguration -dialednumber +44981234567 -TrunkConfiguration $tc.
We are able to check whether the current user is enabled to use the Test-CsTrunkConfiguration synthetic test with the Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Test-CsTrunkConfiguration"} cmdlet that verifies the Role-Based Access Control (RBAC) permissions.
Murali Krishnan has published a script in his blog that automatically performs many synthetic tests for a single pool deployment at http://unifiedme.co.uk/2013/11/lync-server-2013-synthetic-test-script/. The Topology Validator in the Lync 2010 resource kit is able to (also) perform more than 40 synthetic tests, but there is a similar tool in the Lync 2013 version of the resource kit (http://www.microsoft.com/en-us/download/details.aspx?id=36821).