The Enabling Technologies Blog


Dave Bergquist / /

Microsoft Office365 Skype Online Phone System (AKA Cloud PBX): Auto Attendant / Call Queue AD Objects Missing

While deployed in Microsoft Skype for Business Hybrid mode and adding Call Queues and/or Auto Attendants in Microsoft Office 365 Skype Online Phone System (formerly known as Cloud PBX) a warning is thrown stating the active directory entry is missing for these entities:

blog1.png

blog2.png

If you have Skype for Business Server 2015 CU5 (or later) you can run the recommended “New-CsHybridApplicationEndpoint” cmdlet on-premises as shown in the screenshot above. If you do not have CU5 or above, this cmdlet will return an error when attempting to execute. You can still meet the requirement by adding user objects to your on-premises Active Directory manually using the steps outlined below. This will allow your Call Queues and Auto Attendants to function correctly, suppressing the error seen in the Office 365 Skype for Business Admin Center portal. Additionally, adding this object will allow the objects to show up in your address book, in turn allowing on-premises users to “Skype” call as well as call via PSTN number.

blog3.png

 

blog4.png

 

The steps outlined below assume you haven’t created Auto-Attendants (AA) or Calls Queues (CQ) yet. If they are already built, you can skip to step 2.

  1. Create your AA and CQ in office635 Skype Online.
  2. A warning will be thrown as shown highlighted above (AD Objects missing). Gather the info supplied by warning (e.g. new-cshybridapplicationEndpoint -ApplicationID, etc”.
  3. Via Skype Online PowerShell, you can also gather this info via: get-csHuntgroup and get-csorganizationalAutoAttendant.
  4. Determine which OU on-premises that you want to apply the new user objects for AA and CQ.
  5. Create new User Objects for each AA / CQ entity using the following as an example:
    1. Full Name: AA (or CQ) Name
    2. User Login Name: AA sip address / primary URI (without sip: e.g. oaa_9f643a1301d641d38f97f61685fd3afb
    3. Domain: Select the appropriate domain for the user logon name.
    4. Set the following: Password never expires, and account is disabled, no password
    5. Finish, saving the new user object(s).
  6. Edit the newly created user object via attribute editor as follows:
    1. “msRTCSIP-ApplicationOptions”=256;
    2. ”msRTCSIP-ArchivingEnabled”=0;
    3. ”msRTCSIP-DeploymentLocator”=sipfed.online.lync.com;
    4. ”msRTCSIP-OptionFlags”=384;
    5. msRTCSIP-OwnerUrn”= urn:trustedonlineplatformapplication:ce933385-9390-45d1-9512-c8d228074e07 (NOTE: Use GUID / ApplicationID from the “new-CsHybridApplicationEndpoint cmdlet that was output during creation of the AA/CQ.
    6. ”msRTCSIP-PrimaryUserAddress”=sip:user@domain.com;
    7. ”msRTCSIP-UserEnabled”=TRUE;
    8. ”msRTCSIP-Line”=tel:+15556661212;ext=1234 (Use appropriate PSTN number assigned to the object)
    9. ”UserPrincipalName”=username@domain.com}
    10. Click “Apply” and “OK”
  7. Run ADSync (or wait for Object to Sync automatically)
  8. Open Skype for Business Online Admin Center / Call Routing. Check the status of your newly created AA and CQ entries. The status should be: “Active Directory entry out-of-sync”.
    1. Go to Auto Attendants, select the new Auto Attendant, click on “Edit”, and then “Save”. Wait a few minutes for the changes to synchronize.
    2. Go to Call Queues, select the new Call Queue, click on “Edit”, and then “Save”. Wait a few minutes for the changes to synchronize.
    3. Refresh the page or you may even have to exit out of the Skype for Business Online Admin Center and re-enter it. The Status of the objects should be cleared of all / any warnings.

Subscribe to Email Updates

Refine by

To expand the list, please click on the double arrows.

 

Search by Category or Author: