I recently experienced an issue when attempting to check the audio quality from a Lync 2010 client. When clicking the “Check” button under the enterprise voice tab of the client, I was greeted with a “Call has not completed or has ended” error. After some investigation it turned out this had occurred due to the primary SIP domain being renamed after the Lync Server installation had been performed and as a result the Test Call auto attendant still had the old SIP domain appended to it. To resolve this issue the following actions were performed:
1. Log on to your Lync server and open the Lync Server Management Shell. When the Management Shell opens type in the following command without quotations, “Get-CSAudioTestServiceApplication” and press return. You should now be presented with a service output and the key part we are looking for is the following:
OwnerUrn: urn:application:testbot
SipAddress: sip:R[email protected]
In my case, my primary SIP domain was no longer contoso.local, this was not even a secondary SIP domain. This ment that when attempting to perform a test call, the SIP address associated with the test bot could not be reached.
2. Now that you have confirmed the SIP address being used for the test call is incorrect, we can now look at a second section of the Get-CSAudioTestServiceApplication output in order to identify exactly what Active Directory attribute we need to modify. Under the identity section of the output you should see a similar string to the following:
Identity: CN={46577062-9cae-404b-b89c-a3d39511e4cc},CN=Application Contacts,CN=RTC Service,CN=Services,CN=Configuration,DC=contoso,DC=local
The CN={46577062-9cae-404b-b89c-a3d39511e4cc} attribute is the one which holds the SIP information for the test call bot. Now we know what attribute we need to modify, you can perform the following actions:
3. Logon to domain controller. From the Run dialog box type adsiedit.msc and click ok to open the ADSI Editor.
4. Right click ADSI Edit and then choose Connect To, and then select Configuration from the “Select a well known Naming Context list” and click ok.
5. Click on node CN={46577062-9cae-404b-b89c-a3d39511e4cc}, CN=Application Contacts, CN=RTC Service, CN=Service, CN=Configuration, DC=yourdomain, DC=local, and then right click this node and then select properties.
Note: Replace the “CN=46577062-9cae-404b-b89c-a3d39511e4cc” attribute that was identified in the Get-CSAudioTestServiceApplication output with the GUID for your organisation. The GUID’s specified are unquie to my Active Directory domain.
6. Choose the msRTCSIP-PrimaryUserAddress attributes, and change the domain part of value to sip:RtcApplication-0e0e407a-6283-4c93-99fa-c0e252b8af09@yourdomain.co.uk, opposed to your domain.local. Essentially the domain part of the attribute must match what ever your primary SIP domain is.
7. Log on to your Lync 2010 front end server and restart Audio Test Service. Once the service has been restarted, attempt a test call from Lync 2010 client.
That’s it, you should now be able to make test audio calls from Lync clients.
The “Set-CSAudioTestServiceApplication” script has a -sipaddress switch, that should be able to rename the SIP account. At least that is what the help summary line of this script suggests (unfortunately it does not literally says that the SIP address can be renamed, but in that case why the hell does it have such a switch?).
Sadly, I could not manage to rename the sipadress via this switch, my only other idea is the adsiedit as well….
I am a little confused with Step 5.
Where do I get the correct GUID of my organization to replace the ” Replace the “CN=46577062-9cae-404b-b89c-a3d39511e4cc” attribute that was identified in the Get-CSAudioTestServiceApplication output with the GUID for your organisation. “?
In the Lync Management Shell run the Get-CSAudioTestServiceApplication command. When this command is run, next to the “Identity” field is the “CN=” attribute that you require for step 5. If you need any further assistance, let me know.
Thanks! That seemed to have worked.
We had to rename our SIP domain in the topology and the Audio Test service had trouble starting up.
This fixed it.
In my case, the route to this configuration was:
CN=Application Contacts,CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=local
And works perfectly!
Thanks!