Configure Office 365 UM for on premises Lync Server 2013 and Skype for Business Server 2015

Standard

As Office 365 is becoming more and more popular with larger organizations, many Lync \ S4B customers would like to host their voicemail in the cloud. This post will guide you through the steps required to configure Hosted UM on Office 365 for an on premises Lync deployment.

Considering you have a full Lync \ S4B 2013 enterprise voice solution already deployed in you organization, additional prerequisites for this would be:

  • A Lync 2013 Edge server.
  • A spare DDI number for Subscriber Access (Outlook Voice Access).
  • On premises users must be synced to Office 365 by either DirSync or Azure.
  • Office 365 Exchange Online licensing that allows UM.
  • administrative permissions on both the on premises Lync side ad the Office 365 management portal.

It took 7 days to create the world, and seven steps to configure voice mail:

1. Office 365 Admin Center

From the Admin drop-down menu, choose “Exchange”:

Admin-Exchange

Under “Exchange” choose “Unified Messaging”:

UM

In “UM Dial plans”, click the ‘+’ sign to add a new dial plan:

New UM Dial plan

In the new UM Dial Plan window:

  1. Give your dial plan a name.
  2. Configure the extension digit length as used in your organization (In my case: 4).
  3. In Dial plan type: Always choose SIP URI.
  4. Choose your Audio Language.
  5. Enter your country code (No ‘+’, just the code),

UMDialPlan

Click “Save”, the window will close.

You now have a new Dial plan, click “Configure” to continue:

UMDialPlan2

This will open a new window. View your settings in the “General” page. These are not changeable, so if you made a mistake, now would be a good time to start things over.

General

If it’s ok – continue to “dial codes” and enter your country\region code. In my case: 353.

DialCodes

Continue to Outlook Voice Access.
Keep the default greeting and announcement unless you have a pre-recorded file, and go to “E.164 routing numbers for your SIP server”. This is where you enter your Subscriber Access number in an E.164 format. In my case: “+35315556789”.
On the next box, “Outlook Voice Access numbers”, enter the number you entered for the previous box, and the regular display number (e.g. 015556789). Reason is that Outlook voice Access will only correspond to matching numbers, and you would like to have this configured as well:

OVA

Next, go to “Settings” and configure as desired:

Settings

Continue to Dialing rules: You can leave this as it is, or add a rule to allow Outlook to play on phone:
Click the ‘+’ sign to add a new dialing rule:

Dialing rules Add

In the new Dialing rule window:

  1. Name your rule.
  2. Add ‘*’ in “Number pattern” and “Dialed Number”:

New Dialing Rule

Click “OK” to save and go to “Dialing Authorization”. Click the ‘+’ button to add:

dialing auth new

And choose the previously created rule:

select dialing rule gruops

In “Transfer and Search”, I normally change the “Allow callers to search…” to “In the entire organization”:

TransferAndSearch

Click “Save”, and this part of the configuration is done!

2. On premises Lync Server

We’ll be using mostly PowerShell (Lync Management Shell) to configure this. Not a big deal, just make sure you double-check everything for typos…

Start with finding out your current configuration. From an elevated Lync Management Shell, run the following command:
Get-CsAccessEdgeConfiguration
You’re looking for the following parameters:

  1. AllowFederatedUsers (Should be set to True).
  2. EnablePartnerDiscovery (Should be set to True).
  3. RoutingMethod (Should be set to UseDnsSrvRouting)

Should look like this:

Get-CSAccessEdgeConf

If one of the parameters is missing, run the following command:
Set-CsAccessEdgeConfiguration -AllowFederatedUsers $true -EnablePartnerDiscovery $true -UseDnsSrvRouting

Now, add Office 365 Exchange Online as a new hosting provider:
New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn “exap.um.outlook.com” -IsLocal $False -VerificationLevel UseSourceVerification

This has configured your Edge server to be able to communicate with Office 365.
Verify that it’s replicated to the Edge server by running:
Get-CsManagementStoreReplicationStatus (If replicated to all, should be “UpToDate: True” on all servers),
and last, check that it’s configured and displayed correctly by running:
Get-CsHostingProvider -LocalStore, this should be the result:

get-cshostingprovider

3. Office 365 Management Shell

To continue configuring Lync on premises, we need some details about the Office 365 domains and tenants.
To do so, open a new elevated PowerShell window and connect to Office 365 using the following steps:

Run: $cred = Get-Credential and press Enter.
This will pop up a credential prompt, enter your Office 365 administrator credentials and press Ok:

Credentials

Next, run the following command:
$365 = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic –AllowRedirection
This will connect you to Office 365. You might receive a warning saying “WARNING: Your connection has been redirected to the following URI:
https://pod51048psh.outlook.com/powershell-liveid?PSVersion=3.0 “, This is normal.

Last, run:
$importresults = Import-PSSession $365

You should end up with an output similar to this:

Loaded

Now that you’re connected to Office 365, run: Get-Mailbox, to see you recognize what’s going on, and then run: Get-AcceptedDomain. Now let’s pause here for a second:

Take a good look at your domain list. What we’re looking for is the original “.OnMicrosoft.com” domain. This is the one we’re going to use to communicate with Office 365.
Find that domain and mark it:

AcceptedDomains

Whatever your domain is (for example: y0av.onmicrosoft.com), this is what we’ll use in the following steps:

4. Back to Lync Management Shell

Now that we know our “OnMicrosoft” domain, we can configure Lync to communicate with it:

First, we’ll create a new Hosted Voicemail Policy. From Lync Management Sell, run the following:
New-CsHostedVoicemailPolicy -identity Office365UM -Destination exap.um.outlook.com -Description “Office 365 Voicemail” -Organization “YOURDOMAIN.onmicrosoft.com”

Make sure you replaced “YOURDOMAIN” with your domain!

Next step: create a Lync-Exchange contact:
New-csexumcontact -displaynumber <E.164Number>–sipaddress <SIP:Ex365UM@Domain.com> -registrarpool <LyncFE> -ou “<YourDesiredOU>"
So for example, these are my details:

  1. Display Number: +35315556789 (This is the Subscriber Access Number we used on Exchange Online earlier)
  2. Contact’s SIP address: Ex365UM@y0av.com
  3. Lync registrar: LyncFE01.y0av.local
  4. OU: Lync Devices

My command would look like this:
New-csexumcontact -displaynumber +35315556789 –sipaddress SIP:Ex365UM@y0av.com -registrarpool LyncFE01.y0av.local -ou “OU=Lync Devices,DC=y0av,DC=local"

Once running this command, you’ll get an output with the contact’s details. Note the contact’s GUID:

CSexum

This is also found in Active Directory where you created it:
I usually add a description to this contact, as Sys Admins sometimes delete strings they’re not familiar with…

UMContact

Copy the contact’s identity from PowerShell and use it in the following command to grant the policy you created earlier to the user you just created:
Grant-cshostedvoicemailpolicy –identity “CN={92011efc-5608-4c7e-88ed-d79e035c39e6},OU=Lync Devices,DC=y0av,DC=local” –policyname Office365UM

So now we have a UM Policy, and a UM Contact that’s configured with that policy. You can run Get-CsExUmContact to check that:

get-csexumcontact

5. Back to Office 365 Management Shell…

Last thing we need to do before it works, is connect the on premises and the cloud voice policies.
So from the previously used Office 365 Management Shell window, run the following:
Set-UMmailboxpolicy -identity “CloudUMPolicy” -SourceForestPolicyNames “OnPremUMPolicy”
In this scenario we used the same name for both policies – that’ll work too:
Set-UMmailboxpolicy -identity “Office365UM” -SourceForestPolicyNames “Office365UM”
But if you have a different name for each policy – configure that as desired.

6. Back to Lync Management Shell – last time!

The only thing left to do now is grant Lync users with the new hosted voicemail policy and enable them for hosted UM.
You can use any pipe known to humanity to do this, but here’s the basics:

To grant the policy to a user, run:
Grant-cshostedvoicemailpolicy –identity LocalDomain\y0av –policyname Office365UM

To enable the user for Hosted Voicemail, run:
Set-csuser –identity LocalDomain\y0av –hostedvoicemail $true

7. Enable the user for UM

Log on to the Office 365 admin center and enable the user for Unified messaging:

Enable

Assign the UM policy you created earlier:

Enable2

Verify the details on the next screen and that’s it. You’ve voice mail configured.

LyncClient

If you’re having issues enabling users, you might want to check the “Notes from the field” post I published after getting some feedback on this post.

Advertisements

80 thoughts on “Configure Office 365 UM for on premises Lync Server 2013 and Skype for Business Server 2015

  1. Lee Sands

    This is a great guide – thanks for sharing. Everything is working for us apart from the subscriber access. From an external number I can reach the announcer and enter an extension, I get “2750 is not a valid extension”. From an internal UM enabled user the call is ended without ever connecting to the UM Attendant.

    The actual voicemail system is working and users can leave voicemails and they can play them in outlook or the Lync Client…any ideas??

    Thanks

    • Hi Lee,
      Glad you found this guide useful.
      The Subscriber Access is answering, and that’s good news. If you’re getting a “2750 is not a valid extension” message, check the following:
      – Are you using 4 digit extensions?
      – Are your numbers formatted according to E.164 (tel:+44-85-5555555;ext=5555)?
      From an internal user – verify that the number is normalized correctly on the clients and check Lync’ logging tool logs.

      Let me know how that goes for you.

      • Lee Sands

        Thanks for quick response.

        Think I have found the problem – although I am unsure how to fix it.

        We have a mixture of DID’s and extensions. My test user has a DID and no “ext” defined in the URI….is this the issue?

        If it is how do I configure my setup to use both?

      • Hi Lee,

        I believe this is the root cause for your issue.
        You must choose a method and stick with it. The correct way would be to use the “;ext=xxxx” with all numbers. Ken Lasko wrote a detailed article on this some time ago.
        Once you configure all Line URIs correctly your routing issues should be resolved.

  2. Lee Sands

    This is still causing me issues. I now have a uri set as follows “Tel:+442477XXXXXX;ext=XXXX” and still I get “XXXX is not a valid extension” from external access to Subscriber number and internal access fails completely without ever connecting.

    Are there any specific dial plans I should set up for Voice mail normalisation?

    • Lee Sands

      for internal access I have tried dialling subscriber access, holding the number 1 on the phone keypad (HP 4120), clicking “Change Greetings” from Lync client….all fail without ever connecting.

      They do however get reported as missed calls….to myself

      • Mahmoud

        Hi LEE;

        Sorry for the late request;
        did you have a solution for your problem, we are currently face the same problem, UM is reachable from external only

  3. NOE

    i have a UM same Dialplan but no visible voicemail in Outlook or OWA or Lync. but yes put message to dial ex365um to user.

    any ideas???

    additional i agree in powershell Exchange onpremise

    Set-UMmailboxpolicy -identity “DP policy onperm” -SourceForestPolicy “Office365UM”

    is the same problema.

    • Hi NOE,

      running Set-UMmailboxpolicy -identity “DP policy onperm” -SourceForestPolicy “Office365UM” is not correct.
      Set-UMmailboxpolicy should be run from the Lync server.
      -identity shoud be followed by the user’s name or sip address.
      -SourceForestPolicy is not a valid parameter in Set-UMmailboxpolicy. The next parameter should be -PolicyName.

      • NOE

        1. I chek
        federation, parthner discovery =TRUE an routing method is OK
        ———————————-
        2. I run in Lync Onprem:
        ———————————-
        New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn “exap.um.outlook.com” -IsLocal $False -VerificationLevel UseSourceVerification

        3. New-CsHostedVoicemailPolicy -identity CloudUM -Destination exap.um.outlook.com -Description “Office 365 Voicemail” -Organization “tennant.onmicrosoft.com”

        4. in portal 365 Exchange I configure my Dial Plan.
        ———————————-
        5. In Lync Onprem
        ———————————-
        New-CsExUmContact -DisplayNumber +4444 -SipAddress SIP:UM365SA@dominio.com -RegistrarPool LyncPool.dominio.local -OU “OU=xxxUSUARIOS,DC=xxx,DC=xxx,DC=xxx,DC=xx”

        6. Grant-cshostedvoicemailpolicy –identity “GUID” –policyname CloudUM

        ———————————-
        In Exch Online Power Shell
        ———————————-

        7. Set-UMmailboxpolicy -identity “Default Policy Cloud” -SourceForestPolicy “CloudUM”

        8. Set-UMmailboxpolicy -identity “Default Policy Cloud” -SourceForestPolicy “Default Policy Exchange Onprem”

        ———————————-
        In Exch OnPrem Power Shell
        ———————————-

        9. Set-UMMailboxPolicy -Identity “Default Policy Exchange Onprem” -SourceForestPolicy “Default Policy Cloud”

        ———————————-
        10. In Lync Onprem
        ———————————-

        Grant-cshostedvoicemailpolicy –identity “testlync@dominio.com” –policyname CloudUM

        Set-csuser –identity “testlync@dominio.com” –hostedvoicemail $true

        THKS

        any ideas???

  4. Dan

    Hi, nice article! I am going throught several artciles, but I can’t find the answer to a very small question nowhere for the moment. Let me try here, if you do not mind:
    – Lync on-prem, several location, thus several Lync dial plans for each office:
    – Canada, Singapore, etc.
    – Exchange online

    I create a UM dial plan Canada (name is equal to Lync dialplan) and inside this plan I create AutoAttendant. When I call AA from external phone and type extension of Canada, my call is not processed in Lync Canada dial plan, but in Global dial plan of Lync. Is there a way to tell that specific online AA should use specific dial plan Inside Lync on-prem? It was possible for Exchange on-prem, but seems to be missing in Online?

    • Hi Dan,

      If I understand you correctly, this should be an easy one.
      To force an AA to use a specific Dialplan in Lync, use the following command:
      Get-CsExUmContact -Identity “” | Grant-CsDialPlan -PolicyName “”.

  5. Dan

    Nope, I tested this already, this does not work. The thing is (if I understand correctly), when AA routes a call, it uses caller’s dial plan. If I call AA from Lyncuser and then dial ext. I see in the logs that Lync will take lyncuser dialplan and will normalise it there. But if I call from external phone, Lync will consider it as no-location-defined and will assign Global dial plan. If I take a cls log and I will see that mediation server take a decision to convert into sip:3750;phone-context=DefaultProfile@mydomain.com;user=phone
    (DefaultProfile is a short name of Global dial plan, at the same time AA contact has Canada dialplan).

    • In this case, I believe you’ll have to use Exchange Online’s dialling rules.
      There are dial plans in Exchange online, but we’re usually using them as wildcards…
      These dialling rules are not as advanced as Lync (they allow only numbers and wild cards, no regular expressions). Once you create a rule that matches your requirements, you can assign it to your AA (“authorize”).

  6. Daren

    This is a great article…thanks for posting!!

    Is it possible to have an onprem Lync environment with voice by tied to multiple O365 tenants specifically for Exchange UM?

    I have 2 different companies sharing the same Lync environment each using different sip domains and dial plans, but they have separate O365 tenants for Exchange.

    • Hi Daren,

      IF you have two different tenants and link them to two different dial plans, and then enable the users to use a specific hosted voicemail policies, you should be able to accomplish this.

  7. Farrukh Anwar

    I am doing it first time, appreciate clarification for two points.

    1- is the SA and AA number has to be different than currently configured on-premises Lync.
    2- we are in saudi Arabia, would like to know how the call will connect to UM hosted outside Saudi Arabia or my understanding is wrong?
    3- while creating the UM plan, do we need to type the saudi Arabia number or the one where UM is hosted.

    Thanks
    Anwar

    • Hi Farrukh,
      1. You can’t use the same line URI fro two EX-UM accounts. You’ll have to use a different number.
      2. Lync connects the calls to the UM service over IP, so there’s no actual “PSTN” dialling involved.
      3. This decision is based on your business requirements and on your topology. You must have Lync (Server or an SBA) installed where you want calls to terminate.

  8. Carlos Venancio

    Carlos Venancio,
    Great Guidance Yoav,
    I want to help a colleague do this but I don’t know if it’s possible and I would really be grateful if can clarify the point below.

    I was asked to to go configure Skype for Business and I went activated the trial but failed to install the O365 Pro Plus and the Services. that’s simply the cause they are running Office 2013 in their PCs and I know the do not co-exist since are the same. the option is to uninstall Office 2013 before installing O365 ( but the person is reluctant to remove the Office 2013)

    1- Is it possible to configure the normal Lync client, that is already installed with Office 2013 with Skype for Business service in the cloud/online. If its possible how is it done? please advise

    Kind Regards,
    Carlos

    • Hi Carlos,

      The Skype for Business and Lync clients operate identically, so there is no problem using a Lync client with the Skype for Business Online service.
      If you already configured all the necessary DNS records to automatically sign-in you should have no problem signing in.
      If you haven’t – there’s this post that describes how to manually configure your Lync \ S4B client.

      • Carlos Venancio

        Hi Yoav,

        Thanks for the quick response. That’s clear some doubts and have few more questions below.

        I believe they have configured the DNS records. Do you have any post on how to Publish SRV records, if yes please post a link. Cause am not sure about the SRV records.
        So do not have to worry about O365 Management Shell and the Lync 2013 Edge server?
        Is the IP address sipdir.online.lync.com:443 the same in very internal and external server?
        And They are not synced to Synced to O365 direct sync or Azure, is this not a problem?

        Thanks,
        Carlos

      • Hi Carlos,
        Your Office 365 Management portal will guide you on how to publish and configure the required SRV records for auto sign-in.
        If you’re using S4B Online you don’t have an Edge server. Please note this post is about connecting On-prem Lync or S4B to Exchange Online.
        Sipdir.online.lync.com:443 is the A record used to connect to Lync\S4B Online.
        S4B Online does not necessarily require any Azure or O365 Direct Sync.

  9. Jason

    This may be a dumb question but how do you format or use the OU parameter when it’s inside another OU – I have tried it multiple ways and always get an error “Management object not found for identity “OU=LyncObjects,OU=Phones,OU=User Account,DC=contoso,DC=com”

    • Hi Jason,

      Ran this command on my environment against a nested OU (“OU=Lync Demo Accounts,OU=Test,DC=y0av,DC=local”
      ) and it completed with no problems. If this is a newly created OU maybe allow it some time to replicate.

      *** After replying to your comment I noticed you had 3 OUs nested so I ran the command again against the same structure (“OU=3rd OU,OU=Lync Demo Accounts,OU=Test,DC=y0av,DC=local”). Still successful… 🙂

  10. rodney

    Will this procedure work with some mailboxes on-premise, and some in the cloud? Currently in the process of doing a staged migration of mailboxes from on-premise Exchange 2007 to Exchange Online Plan 2. Will the steps for the on-premise Lync configuration break UM for mailboxes still homed on the on-premise Exchange 2007 environment?

    • Hi Rodney,
      You’ll be using two different UM Mailbox policies; one for users hosted on the On-prem server, and one for users hosted online.
      They can work perfectly together.
      Furthermore, since a UM mailbox is tied to the UM server, you won’t be able to migrate the mailbox to Exchange Online until you disable the users’ UM mailbox. Worry not, all mailbox settings (excl. policy specific settings: PIN, lockout, etc.) will be saved and you can re-enable M for the migrated users – the greetings and all messages are saved.

      Hope that answers your question.

      • rodney

        Hi Y0AV,

        Thanks for your response!

        I assume once I have all my user mailboxes in Exchange Online, and on-premise Exchange 2007 is fully retired, I will I need to re-create all the auto attendant configuration in Exchange Online?

        BTW your blog is an awesome resource. Please keep doing what you’re doing. Much appreciated!

      • Hi Rodney,
        Correct, you’ll have to recreate all AAs in Exchange Online and run a New-CsExumContact command for them too.
        Thanks for the kind words!

      • Rodney

        Is there any configuration needed under UM IP Gateways in Exchange Online? Again, I am in the middle of a migration and may have mailboxes in the on-premise environment, and some in Exchange Online (currently 1 for testing).

    • Rodney

      Finally getting around to getting our auto attendants configured/migrated…(current auto attendant is still on-premise). Can the “UM auto attendant access number” be the same as the one configured for the UM dial plan (the number I have configured under “E.164 routing numbers for your SIP server” and “Outlook Voice Access numbers” or do I need another available number? Or would I just use an available extension?

      Office 365 voicemail has been working using your awesome guide, and I’m trying to avoid breaking something when configuring the auto attendants.

  11. Kunal

    Hello,

    Nice Post, I am in process of migrating mailboxes (Exchange 2010 Sp3) from On-prem (Exchange 2013 Hybrid) to office 365- E3 license. For UM enabled user on prem to be migrated to cloud I created O365 Dialplan & mailbox policy and mapping was done “Sourceforestpolicyname”. I have Lync 2013 Integration with UM On prem

    However VM still does not work post migration, can you please confirm after following above steps on Lync 2013 on-prem Voice mail will be working for migrated mailboxes
    What will be the UM IP gateway in Office 365 ?

    • Hi Kunal,
      These steps will of course work for migrated mailboxes.
      Make sure you enabled the migrated users for Hosted Voicemail and assigned them with the right policy:
      Grant-cshostedvoicemailpolicy –identity LocalDomain\y0av –policyname Office365UM
      Set-csuser –identity LocalDomain\y0av –hostedvoicemail $true

      There’s no need to configure a UM IP gateway for this to work.

      Hope this helps 🙂

  12. Peter

    Hi y0av,

    Awesome post, really detailed. Followed every step, but for some reason, I can’t connect to my voice mail trough our Lync client.
    I’m running a Lync 2010 on premise, Exchange 2010 Hybrid with O365 E3, with all users migrated to O365 with the UM feature disabled prior to migration. Activated now after following your guide to my own account on O365. Seeing old voice mails, and can play them aswell.

    Seeing errors on Lync Server:
    “Attempts to route to servers in an Exchange UM Dialplan failed”

    More worrying i seem to have lost federation with external users on Skype and/or Lync.

      • Peter Loft

        Thanks for quick reply! 🙂
        This is how the edge server set up:

        Get-CsHostingProvider:

        Identity : LyncOnline
        Name : LyncOnline
        ProxyFqdn : sipfed.online.lync.com
        VerificationLevel : AlwaysVerifiable
        Enabled : True
        EnabledSharedAddressSpace : False
        HostsOCSUsers : False
        IsLocal : False

        Identity : Exchange Online
        Name : Exchange Online
        ProxyFqdn : exap.um.outlook.com
        VerificationLevel : UseSourceVerification
        Enabled : True
        EnabledSharedAddressSpace : True
        HostsOCSUsers : False
        IsLocal : False

      • Peter Loft

        According to Microsoft Lync Server 2010 Cumulative Update Installer we should be running the latest and gratest (2010) verions.

        Pulled this from WMI:

        Microsoft Lync Server 2010, Mediation Server 4.0.7577.183
        Microsoft Lync Server 2010, Mobility Service 4.0.7577.217
        Microsoft Lync Server 2010, Conferencing Announcement Service 4.0.7577.0
        Microsoft Lync Server 2010, Resource Kit Tools 4.0.7577.197
        Microsoft Lync Server 2010, Web Components Server 4.0.7577.713
        Microsoft Lync Server 2010, Conferencing Attendant 4.0.7577.272
        Microsoft Lync Server 2010, Response Group Service 4.0.7577.276
        Microsoft Lync Server 2010, Web Conferencing Server 4.0.7577.199
        Microsoft Lync Server 2010, Core Components 4.0.7577.713
        Microsoft Lync Server 2010, Call Park Service 4.0.7577.0
        Microsoft Lync Server 2010, Core Management Server 4.0.7577.0
        Microsoft Lync Server 2010, Audio Test Service 4.0.7577.0
        Microsoft Lync Server 2010, Application Host 4.0.7577.0
        Microsoft Lync Server 2010, Administrative Tools 4.0.7577.190
        Microsoft Lync Server 2010, Reach Fonts 4.0.7577.0
        Microsoft Lync Server 2010, Front End Server 4.0.7577.710
        Microsoft Lync Server 2010, Conferencing Server 4.0.7577.709

  13. Peter Loft

    When I click the voicemail icon in Lync, this error is generated on the Lync Server:

    Attempts to route to servers in an Exchange UM Dialplan failed

    No server in the dialplan [Hosted__exap.um.outlook.com__XXXXXXXXXX.onmicrosoft.com] accepted the call with id [06d571c031f64f1d9efde106f627516e].
    Cause: Dialplan is not configured properly.
    Resolution:
    Check the configuration of the dialplan on Exchange UM Servers.

    • Hi Peter,

      Make sure you assigned the EXUM contact with the right dial plan.
      Note this change (and every user you enabled for hosted UM and assigned with a policy) must be synced to Office 365 to work properly.

      • Peter Loft

        Hi thanks, I checked, rechecked and tripple checked.

        Looking at the attributes to the EXUM contact in AD, i see the following:
        SIP:Ex365UM@xxxxxxxx.xxx;opaque=app:exum;voicemail-destination=default

        I’m guessing the voicemail-destionation=default points to the policy on Office365, but Office365 for some reason denies this as valid.

        The two earlier/onpremise AA and SA contacts still works on their assigned numbers, if that has anything to say.

        Any thoughts on why all of a sudden federated connectivity is failing after adding the Exchange Online hosting provider?

  14. Hi Yoav, i’m strugglin with this part hope you can have some thoughts

    PS C:\Users\Administrator.ac-onebox> New-csexumcontact -displaynumber +XXXXXXXXX –sipaddress SIP:Ex365UM@domain.com -registrarpool lyncpool.ac-onebox.com -ou “OU=ExUmContacts,DC=domain,DC=com”
    New-csexumcontact : Received a referral to “summo.com” when requesting “OU=ExUmContacts,DC=domain,DC=com” from “UC-DC.ac-onebox.com”. You have specified the wrong server for this operation.
    At line:1 char:1
    + New-csexumcontact -displaynumber +XXXXXXXXX –sipaddress SIP:Ex365UM@domain.com …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [New-CsExUmContact], ADReferralException
    + FullyQualifiedErrorId : Microsoft.Rtc.Management.ADConnect.ADReferralException,Microsoft.Rtc.Management.AD.Cmdlets.NewOcsUmContactCmdlet

    Hope any comments on this error

  15. RichW

    Article works perfectly however I would like to state in case anyone else comes across this in the future.
    The default SIP domain needs to be a domain that is registered for the company in O365. Otherwise UM won’t work. I have this issue where customer had 2 domains in S4B and 1 domain in O365. However the default SIP domain was not registered on O365 as they were migrating away from it.

  16. Pavel

    Hi,

    can you tell me please if HostedVoiceMailPolicy from Get-CsOnlineUser is set to BusinessVoice or is empty for a hybrid user?

    • We have already figured it out, the only thing we are not able to do is for an complete online officve attach a online dial in number, for people to dial in to the online voicemail system.

  17. Majid

    thank for the article but I’ve a problem:
    O365 users can access their Voicemail from external without issues. but then can’t when they are inside company’s network.issed calls. moreover the exum365@xxxx.com appears offline. any clues?

    • Hi,
      If they can access the Office 365 UM service when outside of the organizational network but can’t access it when their on the LAN, this would normally indicate an issue with your Edge servers. Double check that you’re allowing all required ports to go through the Edge.

      • Majid

        how should the static route looks like ?

        I’ve an external eth: 10.10.10.2 (with Gateway/Public dns – 8.8.8.8)
        I’ve internal eth: 192.168.0.177 (without gateway/DNS)

      • Majid

        HI Y0AV;

        My I have your patience please. I do appreciate your support, but the fact that we do not use a firewall between internal & lyncedge.

        May I provide you with with : ‘netstat -anb’ on lyncedge? I can’t paste or attach it

      • Majid

        Hello;

        this is the TCP:
        TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
        TCP 0.0.0.0:50001 0.0.0.0:0 LISTENING
        TCP 0.0.0.0:50002 0.0.0.0:0 LISTENING
        TCP 0.0.0.0:50003 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:5059 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:5061 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:5061 157.56.187.202:31098 ESTABLISHED
        TCP 10.10.10.2:5061 157.56.187.202:62712 ESTABLISHED
        TCP 10.10.10.2:5061 213.186.176.165:51766 ESTABLISHED
        TCP 10.10.10.2:49661 131.253.130.237:5061 ESTABLISHED
        TCP 10.10.10.2:50038 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50042 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50106 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50135 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50140 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50195 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50208 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50290 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50296 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50308 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50362 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50422 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50431 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50446 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50455 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50462 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50476 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50489 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50494 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50524 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50537 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50545 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50546 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50553 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50588 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50599 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50614 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50662 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50663 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50686 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50691 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50692 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50699 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50718 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50828 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50831 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50874 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50890 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50913 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50919 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50952 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:50976 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51005 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51015 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51020 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51150 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51175 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51208 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51210 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51228 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51236 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51246 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51274 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51277 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51281 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51299 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51332 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51365 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51401 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51417 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51464 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51469 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51478 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51486 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51489 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51490 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51531 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51555 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51575 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51587 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51589 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51593 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51598 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51602 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51625 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51647 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51661 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51663 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51667 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51669 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51671 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51720 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51736 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51763 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51767 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51774 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51810 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51848 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51856 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51894 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51916 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51952 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:51972 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52028 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52044 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52088 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52098 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52120 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52144 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52193 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52203 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52208 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52216 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52266 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52273 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52373 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52399 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52411 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52420 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52435 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52447 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52479 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52517 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52526 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52545 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52546 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52572 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52585 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52601 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52605 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52615 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52621 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52652 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52665 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52670 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52718 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52725 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52729 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52734 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52743 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52762 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52791 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52794 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52822 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52827 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52833 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52842 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52864 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52964 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52975 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:52980 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53022 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53059 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53068 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53133 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53135 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53137 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53156 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53189 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53195 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53199 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53202 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53206 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53226 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53244 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53256 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53321 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53324 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53337 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53354 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53371 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53384 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53441 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53454 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53543 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53635 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53636 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53645 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53650 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53651 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53652 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53669 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53713 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53735 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53765 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53766 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53782 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53798 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53811 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53852 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53910 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53960 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53962 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53980 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:53995 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54005 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54051 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54082 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54097 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54137 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54160 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54164 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54174 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54179 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54203 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54216 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54230 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54235 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54282 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54292 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54329 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54348 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54369 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54411 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54414 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54428 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54448 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54466 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54473 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54485 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54510 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54530 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54556 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54602 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54610 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54611 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54638 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54649 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54660 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54673 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54683 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54695 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54716 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54721 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54747 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54844 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54859 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54863 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54869 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54903 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54909 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54910 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54953 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54983 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:54994 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55012 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55016 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55017 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55022 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55032 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55048 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55073 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55133 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55139 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55169 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55178 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55210 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55232 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55235 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55266 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55280 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55292 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55342 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55350 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55356 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55384 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55394 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55397 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55398 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55401 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55415 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55444 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55445 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55460 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55466 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55471 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55487 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55498 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55533 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55569 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55618 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55658 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55664 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55668 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55677 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55678 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55698 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55705 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55727 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55734 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55753 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55776 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55779 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55787 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55789 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55832 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55858 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55911 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55915 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55916 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55935 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55960 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55988 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:55997 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56011 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56017 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56046 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56090 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56100 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56165 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56179 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56187 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56202 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56222 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56249 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56275 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56290 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56311 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56380 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56413 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56440 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56447 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56463 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56484 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56485 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56502 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56521 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56539 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56603 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56611 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56626 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56638 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56726 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56749 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56775 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56786 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56864 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56866 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56896 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56911 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56913 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56935 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56947 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56960 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56968 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:56970 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57037 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57051 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57061 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57063 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57090 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57100 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57132 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57133 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57187 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57193 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57194 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57201 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57213 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57266 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57270 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57304 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57309 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57313 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57328 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57331 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57335 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57355 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57379 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57407 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57453 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57533 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57541 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57544 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57546 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57551 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57566 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57587 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57589 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57590 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57591 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57610 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57635 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57658 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57679 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57697 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57787 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57796 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57801 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57816 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57821 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57835 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57837 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57843 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57848 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57854 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57857 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57866 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57965 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57969 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57972 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:57987 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58047 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58054 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58056 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58073 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58107 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58108 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58123 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58181 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58193 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58195 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58199 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58219 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58245 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58254 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58267 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58270 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58275 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58300 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58317 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58430 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58435 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58458 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58462 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58480 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58485 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58509 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58513 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58551 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58570 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58583 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58590 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58624 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58630 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58636 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58680 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58681 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58688 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58713 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58717 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58762 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58769 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58861 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58872 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58873 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58918 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:58974 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59026 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59029 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59041 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59049 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59073 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59103 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59151 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59199 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59208 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59248 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59280 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59305 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59318 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59329 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59330 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59344 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59345 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59356 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59365 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59366 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59368 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59384 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59421 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59438 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59484 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59519 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59544 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59545 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59555 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59576 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59608 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59616 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59631 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59637 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59639 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59645 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59656 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59673 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59679 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59707 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59733 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59734 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59754 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59775 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59781 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59785 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59789 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59807 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59826 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59829 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59886 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59899 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59906 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59910 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59947 0.0.0.0:0 LISTENING
        TCP 10.10.10.2:59973 0.0.0.0:0 LISTENING
        TCP 192.168.0.177:5061 0.0.0.0:0 LISTENING
        TCP 192.168.0.177:5061 192.168.0.175:53391 ESTABLISHED
        TCP 192.168.0.177:5061 192.168.0.175:54644 ESTABLISHED
        TCP 192.168.0.177:5061 192.168.0.175:59778 ESTABLISHED
        TCP 192.168.0.177:5061 192.168.0.175:60124 ESTABLISHED
        TCP 192.168.0.177:5062 0.0.0.0:0 LISTENING
        TCP 192.168.0.177:5062 192.168.0.175:59970 ESTABLISHED
        TCP 192.168.0.177:8057 192.168.0.175:56938 ESTABLISHED
        TCP 192.168.0.177:8057 192.168.0.175:56939 ESTABLISHED
        TCP 192.168.0.177:8057 192.168.0.175:56940 ESTABLISHED
        TCP 192.168.0.177:8057 192.168.0.175:56941 ESTABLISHED
        TCP 192.168.0.177:49388 192.168.0.175:5061 ESTABLISHED
        TCP 192.168.0.177:49532 192.168.0.175:5061 ESTABLISHED
        TCP 192.168.0.177:49607 192.168.0.175:5061 ESTABLISHED
        TCP 192.168.0.177:49644 192.168.0.175:5061 ESTABLISHED

      • Hi Majid,
        What we’re looking for might not be found here… Your internal clients use the Edge Server to communicate with Office 365. The preferred media path would be via port 3478 UDP in both directions, traversed via the Edge. Netstat will not show us UDP packets, so you’ll have to confirm somehow that your configuration allows this traffic.

  18. Hello Yoav, we have all this working but i need you assistance on one thing, we are going to move 225 users from Skype 2013 on-premise to Skype online. if i have to do that one by one by hand and add the numbers to them and activate voicemail for them individual, it would take me days to accomplish that. So we have create some basic scripting which will allow us everything ,except that we are able to activate voicemail, but the users are not receiving the email that voicemail has been created. which works when we do this via the Web gui. Do you know which powershell command we have to use to do this?

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