Forum Discussion
Cloud PBX + Cloud Connector Edition resulting in calls not in service
So I'd actually run both those hybrid commands during the initial configuration and installation of cloud connector, so obviously they didn't help the problem.
When I searched for user sessions, there was nothing found in the time period desipte several attempts at test calls.
The output of the Get-CsTenantHybridConfiguration is below.
Identity : Global
HybridPSTNSites : {Index=1;Name=RAC;EdgeFQDN=ap.rehobothambulance.org;EnableAutoUpdate=True;LastTopologyUpdateTime=09/30/2017
19:36:58;BitsUpdateTimeWindowList=BitsUpdateDefault;OsUpdateTimeWindowList=OsUpdateDefault}
HybridPSTNAppliances : {Identity=8eb5905f-e506-4cb9-8cca-1a30a129c409;Name=RACHYPERV;SiteIndex=1;MediationServerIPAddress=192.168.3.212;MediationServerFqdn=MedServer.rac.local;Mediation
ServerGruu=sip:MedServer.rac.local@rehobothambulance.org;gruu;opaque=srvr:MediationServer:Ff5N1ODPQ1C7cKYyZpotzwAA;MaintenanceMode=False;ConfigurationReplicatedOn
=09/30/2017 22:56:26;ConfigurationSnapshot={"EnableBypass":false,"EnableReferSupport":true,"EnableFastFailoverTimer":true,"ForwardCallHistory":false,"ForwardPAI":
false};ConfigurationSnapshotUpdatedOn=09/30/2017
22:56:38;RegistrationStatus=RegisteredAndDeployed;RegistrationAction=Register;RunningVersion=2.0.1;RunningStatus=Running;RunningError=;OsUpdatedOn=10/01/2017
04:54:47;DeployedOn=09/30/2017 22:45:22;StatusUpdatedOn=10/01/2017
04:54:47;DeploymentVersion=2.0.1;DeploymentStatus=Deployed;DeploymentError=;DeploymentStartTime=09/30/2017
19:39:16;OsUpdateStatus=None;OsUpdateError=;OsUpdateStartTime=10/01/2017 04:11:35}
TenantUpdateTimeWindows : {Name=BitsUpdateDefault;Type=Weekly;StartTime=00:00:00;Duration=1.00:00:00;DayOfMonth=;WeeksOfMonth=;DaysOfWeek=1,
Name=OsUpdateDefault;Type=Monthly;StartTime=00:00:00;Duration=1.00:00:00;DayOfMonth=;WeeksOfMonth=1;DaysOfWeek=1}
PeerDestination : ap.rehobothambulance.org
HybridConfigServiceInternalUrl :
HybridConfigServiceExternalUrl :
UseOnPremDialPlan : FalseOne other thing I noticed when I used Get-CSOnlineUser to look at my user configuration is the users are all using InternationalCallsDisallowed, which is OK since we don't need international calling. When I look at the voice routing policy for InternationalCallsDisallowed, I noticed the following:
Identity : Tag:InternationalCallsDisallowed
PstnUsages : {}
Description :
Name : InternationalCallsDisallowed
AllowInternationalCalls : False
HybridPSTNSiteIndex : 0And when I looked at Get-CsHybridPstnSite, I see the following:
RunspaceId : 605d99cc-f1be-47ef-9f35-7b08ef10d734
Identity : RAC
EdgeFQDN : ap.rehobothambulance.org
Index : 1
EnableAutoUpdate : True
LastTopologyUpdateTime : 9/30/2017 7:36:58 PM
BitsUpdateTimeWindowList : {BitsUpdateDefault}
OsUpdateTimeWindowList : {OsUpdateDefault}It looks like the PSTN Site Index has a mismatch... The voicerouting policy is matching to index 0, but the PSTN site shows that it's index is 1...
The PstnUsages is empty... Is this potentially why calls aren't routing out to the PSTN? The voice routing policy doens't know what to use it for..
Some more information. Here's the error report information from using Snooper to examine the client logs of a Skybe for Business online client:
- <reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
- <error toUri="sip:+1##########@SIPDOMAIN.org;user=phone"
callId="8e7b229fe4d342c691cc22f1e0c8389f"
fromTag="02c2a3c5f3"
toTag="CDA1DBB01E51BD29E26FCFE674ED47CD"
contentType="application/sdp;call-type=audiovideo"
responseCode="404"
requestType="INVITE">
<diagHeader>1003;reason="User does not exist";domain="SIPDOMAIN.org";source="sipfed2a.online.lync.com";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="No";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"</diagHeader>
<progressReports/>
- </error>
</reportError>the actual phone number dialed has been replaced with ##########, but it is a valid 10 digit US phone number. Also replace domain with SIPDOMAIN.org
- thet naingOct 01, 2017Iron ContributorThis is an output from my working CCE configuration.
PS C:\Windows\system32> Get-CsTenantFederationConfiguration
Identity : Global
AllowedDomains : Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowAllKnownDomains
BlockedDomains : {}
AllowFederatedUsers : True
AllowPublicUsers : True
TreatDiscoveredPartnersAsUnverified : False
SharedSipAddressSpace : True
You run "Get-CsTenantFederationConfiguration" , and post your output here, if yours and mine are different, please make it to be the same configuration and test again, it should work.
So far I have checked, your configuration looks good.- Reuben FischmanOct 01, 2017Copper Contributor
Mine looks identical to yours.
- thet naingOct 01, 2017Iron Contributor1. How about incoming call(s)?,
2. Did you enabled UM for that user? If you did, u disable UM and try again.
3. Login to your edge VM, look up "Evnet Viewer" for possible root cause.
4. Login to your Mediation server VM, look up "Evnet Viewer" for possible root cause.
Also, plz share your output of "Get-CsOnlineUser -Identity user@domain.org"