Office 365 Auto Attendant with Lync 2013 On Premise

In my previous post I discussed Unified Messaging for the Voicemail feature of Office 365 with Lync 2013 on premise now in this article I will discuss how to configure the auto attendant in the same scenario.

Within The New Office 365 portal (Wave 15)

Select Dial Plan in O365 tenant > under UM Auto Attendants click + and fill out the information you can enable this straight away or come back and enable later on.

auto attendant

Then select the new Attendant and set the following as per the currently deployed options or query with customer.

general

greetings

business hours

menu

address

dialling author auto

Then with Lync 2013 on premise open PS and run the following command to create the account:

  • New-CsExUmContact –sipaddress SIP:EX_AA_365_SA@yourdomain.com -RegistrarPool “FEpool.com” -OU “OU=Blah,DC=yourcompany,dc=com” -DisplayNumber “+14255550101” -AutoAttendant $True
  • Grant-cshostedvoicemailpolicy –identity “post the GUID that has been created” –policyname CloudUM

Then within Exchange Online Powershell

  • Set-UMmailboxpolicy -identity “Policy Name in O365” -SourceForestPolicy “CloudUM”

Viola auto attendant should be ready to go. Bear in mind the settings show here are pretty much the defaults and can be changed as you choose.

Advertisements

10 thoughts on “Office 365 Auto Attendant with Lync 2013 On Premise

  1. i cannot get New-CsExUmContact –sipaddress SIP:EX_AA_365_SA@yourdomain.com -RegistrarPool “FEpool.com” -OU “OU=Blah,DC=yourcompany,dc=com” -DisplayNumber “+14255550101″ -AutoAttendant $True to work I cannot figure out what to put in for -OU our local domain is xxx.local our public domain is xxx.ca, we don’t have an OU in our DNS as far as I know

    • Hi Andrew

      The OU is the location you are creating the account into, so if you are putting the account into the users OU for example it would be OU=users,DC=domainname,dc=local As you are creating this within the local Active Directory. Hope that makes sense.

      • I created an OU named lync and that fixed it. We are having a strange problem with our Response Group. We are trying to get the phone line to ring a response group, and then if no one answers go to the AA. But the transfer is failing because the calling number is missing the +1, i.e. the system seems the calling number as SIP:5555555555 instead of SIP:+15555555555 and we have not been able to get it to make that correction.

        Must be the way the info is coming from our SIP provider.

      • Is the SIP trunk provider on Microsoft’s supported list for 2013/2010? As I found issues with a provider earlier this year who was on the 2010 list but had issues with 2013 and it turned out that they hadn’t carried out full testing of their trunks so they had known issues although wouldn’t admit them at the time.
        http://technet.microsoft.com/en-us/lync/fp179863

        Also Lync/Exchange will need the numbers in E164 format so if it is being presented without the +1 this will be an issue.

  2. We currently have Lync 2010 with Enterprise Voice and Exchange 2010 with UM and several auto-attendants enabled. We are looking to move all of our mailboxes to O365, but will leave Exchange on-premise in a hybrid configuration. I know that we must move UM to O365, but the question is, do I need to move auto-attendant. We would really like to leave it on premise. thanks.

    • Hi Dennis

      Very good question, my view on this is you shouldn’t. But technically it can be done as it is a separate endpoint BUT the caution I would emphasise here is that even with a hybrid deployment the auto attendants will be two different entities as the one premise will be independent of any you create in the cloud. So my next question would be what do your auto attendants current do e.g. can users call the auto attendant and be directed to a user for example as if so this will no longer work if the user is in Office 365 and this is one of many examples where leaving it on premise just wont work for you during a migration to Office 365 for migrated users.

      My other point to make is if the end game is to move all users to Office 365 what benefit are you really getting for keeping your hybrid server live is this a mail routing design choice or purely preference to keep the auto attendants on premise as at points in the near to long term future as Office 365 evolves the hybrid on premise will also need to keep pace and keeping the server maintained to me always defeats some of the principle points of organisations migrating to Office 365.

  3. Hi.

    Very interesting article.

    Can auto attendant be configured with Avaya telephony system. Like if we have avaya in office and want office365 to handle voicemail and greeting in case no one pickup the phone. So instead of Avaya handling voice mail, avaya should tranfer the call to office365 and then office365 handles from there?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s