Forum Discussion
Cloud PBX + Cloud Connector Edition resulting in calls not in service
I've got a Cloud PBX subscription with a few users enabled for testing. We also have Cloud Connector Edition installed, and according to our Skype for Business Online admin portal, it is reporting i...
We haven't been worrying about incoming calls since we forward our main number into an Auto Attendant. I'll have to unforward that and do an inbound call test at some point.
I'll be looking into the event logs on the edge and mediation servers.
Unified messaging is disabled on users.
Problem seems to be across all users.
And here's a sanitized Get-CSOnlineUser. Also, the PSTN Settings for the user include the sitename and the edge server FQDN so thats correct as well...
RunspaceId : 8fb97b90-b8e7-49e1-a518-4677947de9af
UserAccountControl : PasswordNotRequired, NormalAccount
Id : CN=92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6,OU=88c87be0-cf12-4a16-a8cc-ef7fff55d35d,OU=OCS
Tenants,DC=lync2a001,DC=local
CountryAbbreviation : US
CountryOrRegionDisplayName : United States
Company :
Department :
Description : {Administrator}
Fax :
HomePhone :
IPPhone :
City : Rehoboth
Manager :
MobilePhone : aaaaaaaaaa
OriginatorSid :
OtherTelephone : {}
Office :
PostalCode : 02769
PreferredLanguage : en-US
Puid : 10037FFEA1CE11F9
ServiceInfo : {}
StateOrProvince : MA
Street :
StreetAddress : street address
ThumbnailPhoto :
Title :
Phone : bbb-bbb-bbbb x2
WebPage :
AdminDescription :
AssignedPlan : {<XmlValueAssignedPlan xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="3afef5df-3756-40e7-87c7-ffa126e720a3"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Enabled"
AssignedTimestamp="2017-09-15T22:50:50Z" ServicePlanId="3e26ee1f-8a5f-4d52-aee2-b81ce45c8f40"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11">
<Capability>
<Capability Plan="MCOMEETADD" xmlns="http://schemas.microsoft.com/online/MCO/2009/01" />
</Capability>
</Plan>
</XmlValueAssignedPlan>, <XmlValueAssignedPlan xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="8a2a79ba-5fde-403a-9ebf-8ce97dd5a6f1"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Enabled"
AssignedTimestamp="2017-09-15T22:50:50Z" ServicePlanId="4828c8ec-dc2e-4779-b502-87ac9ce28ab7"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11">
<Capability>
<Capability Plan="MCOEV" xmlns="http://schemas.microsoft.com/online/MCO/2009/01" />
</Capability>
</Plan>
</XmlValueAssignedPlan>, <XmlValueAssignedPlan xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="b6af42c0-5a7f-4398-85b2-35fff291e98d"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Enabled"
AssignedTimestamp="2017-09-15T22:50:50Z" ServicePlanId="0feaeb32-d00e-4d66-bd5a-43b5b83db82c"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11">
<Capability>
<Capability Plan="MCOProfessional"
xmlns="http://schemas.microsoft.com/online/MCO/2009/01" />
</Capability>
</Plan>
</XmlValueAssignedPlan>, <XmlValueAssignedPlan xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="98236811-e581-4903-b9ef-4e4af7e278fd"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Deleted"
AssignedTimestamp="2017-09-15T15:47:19Z" ServicePlanId="4ed3ff63-69d7-4fb7-b984-5aec7f605ca8"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11">
<Capability>
<Capability Plan="MCOPSTN1" xmlns="http://schemas.microsoft.com/online/MCO/2009/01" />
</Capability>
</Plan>
</XmlValueAssignedPlan>}
InterpretedUserType : PureOnline
Alias : rfischman
BaseSimpleUrl :
DirSyncEnabled :
ObjectId : 92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6
UsageLocation : US
HideFromAddressLists : False
OnPremHideFromAddressLists : False
ProvisionedPlan : {<XmlValueProvisionedPlan xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="8a2a79ba-5fde-403a-9ebf-8ce97dd5a6f1"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Enabled"
AssignedTimestamp="2017-09-15T22:50:50Z" ProvisioningStatus="Success"
ProvisionedTimestamp="2017-09-15T23:57:50.0375131Z"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11" />
</XmlValueProvisionedPlan>, <XmlValueProvisionedPlan
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="3afef5df-3756-40e7-87c7-ffa126e720a3"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Enabled"
AssignedTimestamp="2017-09-15T22:50:50Z" ProvisioningStatus="Success"
ProvisionedTimestamp="2017-09-15T23:57:50.0375131Z"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11" />
</XmlValueProvisionedPlan>, <XmlValueProvisionedPlan
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="b6af42c0-5a7f-4398-85b2-35fff291e98d"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Enabled"
AssignedTimestamp="2017-09-15T22:50:50Z" ProvisioningStatus="Success"
ProvisionedTimestamp="2017-09-15T23:55:24.6156401Z"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11" />
</XmlValueProvisionedPlan>, <XmlValueProvisionedPlan
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Plan SubscribedPlanId="98236811-e581-4903-b9ef-4e4af7e278fd"
ServiceInstance="MicrosoftCommunicationsOnline/NOAM-2A-S6" CapabilityStatus="Deleted"
AssignedTimestamp="2017-09-15T15:47:19Z" ProvisioningStatus="Success"
ProvisionedTimestamp="2017-09-15T16:13:40.9297247Z"
xmlns="http://schemas.microsoft.com/online/directoryservices/change/2008/11" />
</XmlValueProvisionedPlan>}
ProvisioningStamp :
SubProvisioningStamp :
UpgradeRetryCounter : 0
SyncingCounter :
ProvisioningCounter : 0
SubProvisioningCounter : 0
PublishingStamp :
PublishingCounter : 0
OnPremHostingProvider :
OnPremOptionFlags : 0
OnPremEnterpriseVoiceEnabled : False
OnPremSIPEnabled :
OnPremSipAddress :
OnPremLineURI : tel:+1bbbbbbbbbb
MCOValidationError : {}
ShadowProxyAddresses : {}
SipProxyAddress : sip:rfischman@SIPDOMAIN.org
ServiceInstance : microsoftcommunicationsonline/noam-2a-s6
StsRefreshTokensValidFrom : 6/4/2017 4:55:27 PM
LicenseRemovalTimestamp :
LastSyncTimeStamp : 9/15/2017 7:54:56 PM
LastProvisionTimeStamp : 9/15/2017 7:55:24 PM
LastPublishTimeStamp : 9/29/2017 6:26:48 AM
LastSubProvisionTimeStamp : 9/29/2017 6:26:34 AM
ExchUserHoldPolicies : {}
OwnerUrn :
ContactOptionFlags :
OnlineDialinConferencingPolicy : ServiceAllowed
OverridePreferredDataLocation :
PreferredDataLocation :
SubProvisionLineType :
UserProvisonType : NormalProvision
SamAccountName : $CP9LB3-B185JLBIMFPI
UserPrincipalName : rfischman@SIPDOMAIN.org
FirstName : Firstname
LastName : Lastname
WindowsEmailAddress : rfischman@SIPDOMAIN.org
Sid : S-1-5-21-782800828-1820537485-3938890916-112895788
LineServerURI :
SoftDeletionTimestamp :
PendingDeletion : False
AudioVideoDisabled : False
IPPBXSoftPhoneRoutingEnabled : False
RemoteCallControlTelephonyEnabled : False
PrivateLine :
AcpInfo : {<acpInformation default="true">
<tollNumber>15085566648</tollNumber>
<participantPassCode>0</participantPassCode>
<domain>resources.lync.com</domain>
<name>Microsoft</name>
<url>https://dialin.lync.com/6f92fa88-330f-4102-8d4a-06783f547f47</url>
</acpInformation>}
OriginalPreferredDataLocation :
HostedVoiceMail : True
DisplayName : First Last
ProxyAddresses : {SMTP:rfischman@SIPDOMAIN.org, sip:rfischman@SIPDOMAIN.org}
HomeServer :
TargetServerIfMoving :
EnterpriseVoiceEnabled : True
EnabledForRichPresence : True
ExchangeArchivingPolicy : Uninitialized
NonPrimaryResource : False
MNCReady : True
OnPremLineURIManuallySet : True
OptionFlags : 196992
LineURI : tel:+1bbbbbbbbbb
SipAddress : sip:rfischman@SIPDOMAIN.org
Enabled : True
TenantId : <TENANT ID>
UserRoutingGroupId : 9ced8589-94e4-593d-8988-4a09dd202495
TargetRegistrarPool :
VoicePolicy : HybridVoice
CallerIdPolicy :
CallingLineIdentity :
MobilityPolicy : MobilityEnableOutsideVoice
ConferencingPolicy : BposSAllModality
BroadcastMeetingPolicy :
CloudMeetingPolicy :
CloudMeetingOpsPolicy :
TeamsMeetingPolicy :
TeamsCallingPolicy :
TeamsInteropPolicy :
ClientUpdatePolicy :
ClientUpdateOverridePolicy :
OnlineVoicemailPolicy :
PresencePolicy :
VoiceRoutingPolicy : InternationalCallsDisallowed1
RegistrarPool : sippooldm12a05.infra.lync.com
DialPlan : US
TenantDialPlan :
IPPhonePolicy :
LocationPolicy :
ClientPolicy :
ClientVersionPolicy :
ArchivingPolicy :
LegalInterceptPolicy :
PinPolicy :
CallViaWorkPolicy :
GraphPolicy :
ExternalAccessPolicy : FederationAndPICDefault
HostedVoicemailPolicy : BusinessVoice
PersistentChatPolicy :
UserServicesPolicy :
ExperiencePolicy : W15DefaultUX
XForestMovePolicy :
PreferredDataLocationOverwritePolicy :
AddressBookPolicy :
SmsServicePolicy :
ExternalUserCommunicationPolicy :
ThirdPartyVideoSystemPolicy :
CloudVideoInteropPolicy :
OnlineDialOutPolicy :
HostingProvider : sipfed.online.lync.com
ExUmEnabled : False
Name : 92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6
DistinguishedName : CN=92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6,OU=88c87be0-cf12-4a16-a8cc-ef7fff55d35d,OU=OCS
Tenants,DC=lync2a001,DC=local
Identity : CN=92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6,OU=88c87be0-cf12-4a16-a8cc-ef7fff55d35d,OU=OCS
Tenants,DC=lync2a001,DC=local
Guid : e971e425-7b04-4464-b807-f1efd2b377f9
ObjectCategory : CN=Person,CN=Schema,CN=Configuration,DC=lync2a001,DC=local
ObjectClass : {top, person, organizationalPerson, user}
WhenChanged : 10/2/2017 6:07:20 AM
WhenCreated : 6/5/2017 8:58:26 PM
OriginatingServer : BLU2A00ADS01.lync2a001.local
IsByPassValidation : True
IsValid : True
ObjectState : Unchanged
I am checking ur output now. Meanwhile, I assumed u have ASD Synce in place in ur environment and there is no issue in directory synchronisation?
Fistly, I would like to accentuate that I am trying to resolve your issue voluntarily based on best of my understanding with absolutely no guarantee or warranty fitting to your issue/environment.
As a community contributor, I strongly recommend you open a ticket with Microsoft and/or engage a professoinal assistance to resolve your issue as it seems that "a live troubleshooting" is needed.
Having said that if you are still willing to try on your own, here are some steps,Based on my best understanding of your issue, you would have to re-enable your AADSync.
A good example is here:
Ref: http://www.wapshere.com/missmiis/breaking-the-aadconnect-link-an-alumni-example.
In short,
- You have to put a user into an OU, for example, "USEROU"
- Launch AADConnect, choose NOT to sync "USEROU" in the sync scope options
- Run AADSync
- Cloud will (soft) delete the user in the AD
- Then you try to restore using the following commands
Restore-MsolUser -UserPrincipalName $user.UserPrincipalName -AutoReconcileProxyConflicts -NewUserPrincipalName $user.UserPrincipalName
- Assign an appropriate license to the user
- The user will become a pure Cloud user.
- Once it's confirmed working, please do the same for all users by putting all uesrs in a new OU.
So its been several days and the problem is still exactly the same.
- I suggest you wait for 1-2 days.
Microsoft office cloud is still seeing all ur users as "users synced from on-Prem ad" as I pointed out as the root cause of the issue .
Meanwhile, u may open a ticket with Microsoft as there may be a case whereby Microsoft has to make changes in their backend system.
Since the root cause and what's to be done to fix is known, the rest is pretty much hands-on. As another point of reference, I created a brand new account in the Office365 cloud and assigned it an E5 license, then enabled enterprise voice and hosted voicemail, assigned it an onprem PSTN number Finally, attempted to login as that user and make phone calls. Exact same errors - the snooper logs show all numbers as coming back with the ms diagnostics 1003 " User not found"
I ran through these steps, and was also able to set the Immutable to $null using Set-MSOLUser -UserPrincipalName <name> -ImmubatbleID "$null"
Unfortunately, I still seem to have the issue (and yes, directory sync is showing false)... CAlls are going "fast busy" and the snooper logs still show "User not found"
Also tried it with another account and the same issue persists.
SOLUTION
You want to manage objects in Office 365, Azure, or Intune and you no longer want to use directory synchronization.- Install the Azure Active Directory Module for Windows PowerShell. For more info, go to the following Microsoft website: http://aka.ms/aadposh
- Connect to Azure AD by using Windows PowerShell. For more info about how to do this, go to the following Microsoft website:http://technet.microsoft.com/library/jj151815.aspx#bkmk_connect
- Disable directory synchronization. To do this, type the following cmdlet, and then press Enter:
Set-MsolDirSyncEnabled –EnableDirSync $false
- Check that directory synchronization was fully disabled by using the Windows PowerShell. To do this, run the following cmdlet periodically:This cmdlet will return True or False. Continue to run this cmdlet periodically until it returns False, and then go to the next step.
(Get-MSOLCompanyInformation).DirectorySynchronizationEnabled
Note It may take 72 hours for deactivation to be completed. The time depends on the number of objects that are in your cloud service subscription account.
- Install the Azure Active Directory Module for Windows PowerShell. For more info, go to the following Microsoft website:
It's confirmed that Microsoft Office365 portal is still seeing all your users as "Synced with on-premise Active Directory"
Root Cause: Microsoft Office365 portal is still seeing all your users as "Synced with on-premise Active Directory" after you migrated your AD users to Office365.
This has been a long strech of finding out what's going on. Finally, I managed to pin down the "Root Cause of the Issue" in conclusive manner. :D
As you can see, the ImmutableID is still showing GUID which means Office365 portal is still seeing all your users as "Synced with on-premise Active Directory"
ImmutableId : i9Zr9uuYH0ugtQvi2vE3WQ==
If it is a pure Cloud user, you shold see "blank" in ImmutableID paramter.
Let me see how to fix/workaround over it.
Here's the output of the user I'm testing with. Happens to be my account..
ExtensionData : System.Runtime.Serialization.ExtensionDataObject AlternateEmailAddresses : {ALTEMAIL} AlternateMobilePhones : {} AlternativeSecurityIds : {} BlockCredential : False City : CITY CloudExchangeRecipientDisplayType : 1073741824 Country : United States Department : DirSyncProvisioningErrors : {} DisplayName : DISPLAY NAME Errors : Fax : FirstName : FIRST NAME ImmutableId : i9Zr9uuYH0ugtQvi2vE3WQ== IndirectLicenseErrors : {} IsBlackberryUser : False IsLicensed : True LastDirSyncTime : LastName : LAST NAME LastPasswordChangeTimestamp : 6/4/2017 8:55:27 PM LicenseReconciliationNeeded : False Licenses : {rfischmanrehobothambulance:ENTERPRISEPREMIUM, rfischmanrehobothambulance:EMS} LiveId : 10037FFEA1CE11F9 MSExchRecipientTypeDetails : MobilePhone : MOBILEPHONE ObjectId : 92e1bd1e-bbb7-453f-bea6-a1dec1dad6b6 Office : OverallProvisioningStatus : PendingInput PasswordNeverExpires : XXXXXXX PasswordResetNotRequiredDuringActivate : PhoneNumber : OFFICE PHONE PortalSettings : PortalSettings PostalCode : ZIP PreferredDataLocation : PreferredLanguage : en-US ProxyAddresses : {SMTP:EMAIL ADDRESS} ReleaseTrack : ServiceInformation : {} SignInName : SIGNIN NAME SoftDeletionTimestamp : State : STATE StreetAddress : STREET ADDRESS StrongAuthenticationMethods : {Microsoft.Online.Administration.StrongAuthenticationMethod, Microsoft.Online.Administration.StrongAuthenticationMethod} StrongAuthenticationPhoneAppDetails : {} StrongAuthenticationProofupTime : StrongAuthenticationRequirements : {} StrongAuthenticationUserDetails : Microsoft.Online.Administration.StrongAuthenticationUserDetails StrongPasswordRequired : True StsRefreshTokensValidFrom : 6/4/2017 8:55:27 PM Title : UsageLocation : US UserLandingPageIdentifierForO365Shell : UserPrincipalName : USERPRINCIAPLNAME UserThemeIdentifierForO365Shell : UserType : Member ValidationStatus : Healthy WhenCreated : 5/28/2017 1:34:44 PMAnd I noticed provisoning status shows pending input. Here's the status of the assigned products:
ServicePlan ProvisioningStatus ----------- ------------------ FORMS_PLAN_E5 Success STREAM_O365_E5 Success THREAT_INTELLIGENCE Success Deskless Success FLOW_O365_P3 Success POWERAPPS_O365_P3 Success TEAMS1 Success ADALLOM_S_O365 PendingInput EQUIVIO_ANALYTICS Success LOCKBOX_ENTERPRISE Success EXCHANGE_ANALYTICS Success SWAY Success ATP_ENTERPRISE PendingProvisioning MCOEV Success MCOMEETADV Success BI_AZURE_P2 Success INTUNE_O365 PendingActivation PROJECTWORKMANAGEMENT Success RMS_S_ENTERPRISE Success YAMMER_ENTERPRISE Success OFFICESUBSCRIPTION Success MCOSTANDARD Success EXCHANGE_S_ENTERPRISE Success SHAREPOINTENTERPRISE Success SHAREPOINTWAC Success
- An output of one user account will do.
- Connect to Microsoft Online (msol) using powerrshell using admin account.
Run:
#get-msoluser -all
and paste ur output here, I interest particularly in "immutableid" parameter. - AD MIgration was several months ago. ANd my O365 portal doesn't show me any status as to whether it was on-prem or cloud. However, the user in question was sourced from an on-prem AD prior to retiring it IS there a way to switch the users to show as cloud?
- I see, that says it all. Look no further, its AD related issue.
When did u do AD migration? 1 week ago?
When u login to o365 portal > users > do u see users as "sync from on-Prem ad" or "Cloud" under Status? We've migrated to online only. I ran AZ AD Sync with our on-prem AD to migrate our users online. Once that was done, we retired the on-prem AD. THe only AD On-prem now is the one associated with CCE.