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 in as a on premisis PSTN equipment that is running. We've double checked all of the configuration settings against the variety of config guides availalbe and it looks like we've got everything configured correctly. However, when any of our test users make a call from their Skybe for Business Client to an outside line, the call results in a fast busy or a "Number not in service" message (iPhone client). I've sniffed traffic to/from our edge server and I'm not seeing ANY inbound traffic at the time of the test calls on the SIP port or the media ports. I confirmed that the prots are open on our firewall, and also tried connecting through the firewall with a telnet client to ensure the ports were open and I see those connection attempts with the packet captures. Any help in troubleshooting why calls aren't routing correctly from the Cloud PBX to the edge server would be appreciated.
Time to upgrade your Cloud Connector Editions (for the last time!)
First published on TECHNET on Aug 31, 2016 AUTHOR: Jamie Stark - MicrosoftSkype for Business Cloud Connector Edition has been one of the most exciting new products we've released in the last year, and that's saying quite a lot considering the work we have done - from PSTN Conferencing and Calling to Broadcast Meetings and Mobile.Cloud PBX and CLoud Connector Edition support through office 365?
SInce Cloud PBX is an office 365 offering, and cloud conector edition is used with CLoud PBX, is there support for Cloud PBX through Office 365 support? I've tried multiple times to get support for cloud pbx + CCE and office 365 support keeps telling me they don't support this..
Failover-Backup options for S4B CCE on Prem
We are looking into what options we have for a failover process more in the lines of if my ISP goes down. While digging through my INI file, on my CCE on prem S4B server, my DMZ IPv4 address might be holding me back with making this an easy proces. We currently have one AudioCodes appliance running my CCE on prem servers connecting to physical PRI's from a local vendor in my area. We have two different ISP Circuits in my building provided by two different vendors. Is there a good way to cut back and forth between the two circuits if my primary circuit should go down?CCE ON-Premise users voicemail fails after the outage yesterday
I created a ticket with Microsoft already but I figured maybe someone can help in the meantime as Microsoft doesn't appear to be responding very quickly on this matter. After yesterday's widespread outage for our Skype for Business Online users, we are now having issues with our S4B-CCE On-Prem users and voicemail. When someone calls an On-Prem user they can reach the user but they never make it to their voicemail greeting. I grabbed some of the sip messages and this is a snippet from what I'm seeing. ms-diagnostics: 23;source="MedServer.domain.local";reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote";component="MediationServer";Exception="Proxy side ICE connectivity check failed.";ICEWarningFlags="BaseAddress="{localipaddress1}:54784";LocalSite="{localipaddress1}:50070";RemoteSite="{remoteipaddress1}:5446";MediaEpBlob="ICEWarn=0x412a,ICEWarnEx=0x0,LocalMR={localipaddress2}:3478,RemoteMR={remoteipaddress1}:51816,PortRange=49152:57500,RemoteMRTCPPort=51816,LocalLocation=2,RemoteLocation=1,FederationType=0,StunVer=0,CsntRqOut=0,CsntRqIn=0,CsntRspOut=0,CsntRspIn=0,Interfaces=0x2,BaseInterface=0x2,IceRole=1,RtpRtcpMux=0,AllocationTimeInMs=210,FirstHopRTTInMs=0,TransportBytesSent=6387,TransportPktsSent=219,IceConnCheckStatus=5,PrelimConnChecksSucceeded=0,IceInitTS=3728302164984,ContactSrvMs=204,AllocFinMs=254,FinalAnsRcvMs=4422,ReinviteSntMs=14925,BlobGenTime=3728302179909,MediaDllVersion=6.0.8953.265,BlobVer=1"" ms-diagnostics-public: 23;reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote";component="MediationServer";Exception="Proxy side ICE connectivity check failed." ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet IP addresses have been removed for security reasons.
