This section includes:
The goal of this page is to help with Cloud Connector Edition (CCE) deployment and troubleshooting issues.
We recommend running the SBC and SbcComms firmware 6.1.2 before deploying CCE.
Once CCE deployment is complete, confirm the following:
Log into the SBC Edge WebUI.
Access Tasks > Application Solution Module > Operational Status.
Operational Status
If there is only the AD VM, and you are using a proxy on the ASM host, exclude the Management Network and Local Network from the proxy usage. To bypass the proxy, specify the WinHTTP Proxy settings set with your Proxy Server and a Bypass list including the 192.168.213.* network used by your Cloud Connector Managements services and the Local subnet used by your VM.
> netsh winhttp set proxy "10.10.10.175:8080" bypass-list="192.168.213.*;192.168.214.*". > netsh winhttp show proxy Current WinHTTP proxy settings: Proxy Server(s) : 10.34.207.20:8080 Bypass List : 192.168.213.*;192.168.214.*
Ensure four VMs are displayed. If not, restart the deployment.
Ensure the latest Software Installed Version (CCE) is installed.
CCE - Sosftware Installed Version
Ensure the Auto Maintenance Status is set as None.
CCE - Auto Maintenance Status
Ensure the proper version is displayed as the Software Running Version.
CCE - Software Running Version
Connect the SBC Edge VM, open Services and ensure the following six Skype for Business Servers are Running. See below.
Skype for Business Services
If Edge Servers Do Not Start
Problem - What to Check | Most Likely Cause | Solution |
---|---|---|
If all of the below issues are true:
| Communication Issue | On ASM: type "Switch-CcVersion -Force" |
If all of the below issues are true:
| Public Certificate Issue |
|
If all of the below issues are true:
| Public Certificate Issue |
|
On HyperV manager, check the Networking for each VM and confirm that the Corpnet Adapter is always attached to the SfB CCE Corpnet Switch. If a VM has two IPv4 addresses on the Corpnet Adapter, and one is beginning with 169, there is most likely an IP address conflict with local equipment.
HyperV Networking - Corpnet Connection Adapter
On HyperV manager, check the Networking for the Edge VM and confirm that the Internet Adapter is attached to the SfB CCE Internet Switch. If the Edge VM has two IPv4 addresses on the Internet Adapter, and one is beginning with 169, there is most likely an IP address conflict with DMZ equipment.
HyperV Networking - Internet Connection Adapter
On the Office 365 Tenant, confirm that OsUpdate is not currently running:
PS> Get-CsHybridPSTNAppliance -Identity 091287a9-1c8f-416e-b8ba-b250fba56181 Identity : 091287a9-1c8f-416e-b8ba-b250fba56181 . RegistrationStatus : RegisteredAndDeployed . DeploymentStatus : {"Status":"Deployed","Version":"1.4.1","Error":null,"StartTime":"2016-12-19T21:10:50.9209Z"} OsUpdateStatus : {"Status":"None","Error":null,"StartTime":null}
If OsUpdateStatus displays the status below, wait for the update to complete. To set a time window for the update, see: Managing Your Office 365 Tenant.
{"Status":"Updating","Error":null,"StartTime":"2016-10-31T11:47:04.1526Z"},
At this point, the CCE is running.
On SBC Edge WebUI, access Settings > Signaling Groups. On the CCE Signaling Group, ensure the "Service Status" is Up.
Click on Counters and ensure Options are flowing in both directions and that the number of 2xx answers is matching.
Request Counters
If there are no Options flowing, log into the ASM using Remote Desktop.
Execute the following command on a shell of the ASM Host:
ipconfig /all
Confirm :
At this point, both the CCE and SBC are up and running.
Confirm the public SBC Edge FQDN is properly mapped to the External IP used in Configure CCE (via SBC Edge WebUI).
From a PC with open internet access, run Nslookup on the public CCE FQDN. If the result is "Error: Requested name myccesite1.mydomain.com could not be resolved", the Public DNS server needs to be corrected.
nslookup av.contoso.com
Ensure the IP address returned is the Edge Server External Public IP. If the IP is not the correct one, you need to fix your Public DNS server.
IP Address
Run the command below for all the domains assigned on your O365 tenant. If the command returns as Unknown, modify the firewall to open the port from "Internet facing DMZ" to the Internet.
nslookup -q=cname lyncdiscover.domain.com. 8.8.8.8 nslookup -q=cname sip.domain.com. 8.8.8.8 nslookup -type=SRV _sip._tls.domain.com. 8.8.8.8 nslookup -type=SRV _sipfederationtls._tcp.domain.com. 8.8.8.8
For details, see Managing Your Office 365 Tenant.
Confirm that PSTN connectivity is "On-Premises".
Confirm User State
On Office 365 Tenant, use "Get-CsOnlineUser" to confirm that the user is activated for EnterpriseVoice, HostedVoiceMail and HybridVoice.
PS> $user = Get-CsOnlineUser site2user1 PS> $user.EnterpriseVoiceEnabled True PS> $user.HostedVoiceMail True PS> $user.VoicePolicy HybridVoice
On Office 365 Tenant, use "Get-CsUserPstnSettings" to confirm that the user is assigned to the proper HybridPstnSiteName.
PS> Get-CsUserPstnSettings -Identity Site2User1 RunspaceId : aa696d9a-67b1-4580-9a60-179cb90fd854 UserPrincipalName : site2user1@SonusMS01.com SipAddress : sip:site2user1@SonusMS01.com AllowInternationalCalls : True HybridPstnSiteName : AEPSITE2 HybridPstnSiteFqdn : AEPSITE2.SONUSMS01.COM
Connect a Skype for Business client using the account below:
Skype for Business Client
On the CCE SG, click on Counters.
Ensure there is Incoming Invite and that the number of 1xx answer is matching .If you get a "Additional Information: Failed Reason Q.850 Cause Code: 1.", ensure that:
Test A Call
Modify Counters
Make a call from the Skype client to a PSTN number that does not exist on your Office365 Tenant.
From the CCE Signaling Group, click on Counters.
Ensure there is an Incoming Invite and that the number of 1xx answer matches.
If the PSTN provider is slow to route the call, the Skype client may cancel the call too fast. Access Tasks / Cloud Connector Edition / Setup / Confgure CCE / Raw Ini config, and add the EnableFastFailoverTimer=false parameter into the section [TrunkConfiguration].
Request Message Counters
Ensure there is an Outgoing Invite, and that the number of 1xx answer matches.
Outgoing Invite
If the Forward/Transfer or Conference are failing to escalate from Online call to CCE call:
Verify that the Mediation server have been added to the teantusing the command:
Get-CsOnlineUser -Filter "HostingProvider -like '*.<YourDomain.com>'" | Get-CsHybridMediationServer
Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings] ProxySettingsPerUser dword:00000000.
Group Policy: Computer>Administrative Templates>Windows Components> Internet Explorer: Make Proxy settings per machine (rather than per user).
Select Enable CCE Logging.
CCE Logging
Click Download Log and specify a time window.
EndTime. The current time. Refer to the time in the upper right corner of the WebUI.
Download Log
Cloud Link is affected by an issue on Windows Server 2012R2 and Cloud Connector Edition; this issue creates a memory leak on the CCE Virtual Machine. As a result, the Mediation Server runs out of memory after a few weeks. As a fix to this issue, ensure the Window's service version is 6.3.9600.17552 and the Windows Update KB2919355 is installed on the CCE VM, as follows:
Right-click on the filename profsvc.dll and select Properties.
Select File
If the file version is 6.3.9600.17930, no action is required.
File Details
Verify prerequisite KB2919355 is already installed on the VM.
Verify file via Command Prompt
Access the Control Panel and select System and Security > Windows Update.
Following Windows checking for updates, click on the “<number> important updates are available" link.
Automatic Updates
Select Update for Windows Server 2012 R2 (KB3078676) and click Install.
After installiationiscomplete, the option to restart the PC to complete the update is displayed. You must turn off Windows Update before restarting.
DO NOT RESTART THE PC PRIOR TO TURNING OFF WINDOWS UPDATE.
Turn off windows update before you restart to prevent the VM from automatically doing other updates. See Change Settings.
Restart Option
Through System and Security > Windows Update, click Change Settings and change Important updates to “Never check for updates (not recommended) and click OK.
Important Updates
Restart the virtual machine.
Restart the VM
Right-click on the filename profsvc.dll and select Properties.
Click View update history.
View Update History
Review Update History
Verify File version of profsvc.dll has been updated to 6.3.9600.17930.
Verify product version is 6.3.9600.17930.
Select File
Select Details