Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | SYM-23022 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c9, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} |
---|
|
Panel |
---|
This section includes: |
...
Log into the
WebUI.Access Tasks > Application Solution Module > Operational Status.
Caption |
---|
0 | Figure |
---|
1 | 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.
Code Block |
---|
> 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.
Caption |
---|
0 | Figure |
---|
1 | CCE - Sosftware Installed Version |
---|
|
|
Ensure the Auto Maintenance Status is set as None.
Caption |
---|
0 | Figure |
---|
1 | CCE - Auto Maintenance Status |
---|
|
|
- If the status is Update OS or Bits, you should wait until the end of the update.
- If the status is Auto-Recover, check: https://blogs.technet.microsoft.com/sfbhybridvoice/2017/03/10/understanding-cloud-connector-edition-auto-recovery.
Ensure the proper version is displayed as the Software Running Version.
Caption |
---|
0 | Figure |
---|
1 | CCE - Software Running Version |
---|
|
|
- If the Software Running version is None or Unknown, log into the ASM using Remote Desktop.
Connect the SBC Edge VM, open Services and ensure the following six Skype for Business Servers are Running. See below.
Caption |
---|
0 | Figure |
---|
1 | Skype for Business Services |
---|
|
|
c. If the Edge Servers do not start, see below for identifying solutions. Caption |
---|
0 | Figure |
---|
1 | If Edge Servers Do Not Start |
---|
|
Problem - What to Check | Most Likely Cause | Solution |
---|
If all of the below issues are true: - On HyperV Manager, there is no Virtual Switch assigned on the VM (on the ASM)
- Some Skype for Business Server services are not running
- Windows Lync Event Log report Errors with Event ID 42004,19005 and 14624
| Communication Issue | On ASM: type "Switch-CcVersion -Force" | If all of the below issues are true: - Some Skype for Business Server services are not running
- Windows Lync Event Logs report Errors with Event ID 19008 and 19005
| Public Certificate Issue | - Generate a new CSR on CCE Wizard.
- Sign the Certificate on your Public CA.
- Import the certificate returned by your Public CA on CCE Wizard.
- Run the Step "Prepare CCE" on CCE wizard.
- If you are on CCE 1.4.1 only: Run Install-CcInstall
| If all of the below issues are true: - Some "Skype for Business Server" service are not running
- Windows Lync Event Logs reports Error with Event ID 14623 and 12303
| Public Certificate Issue | - Generate a new CSR on CCE Wizard.
- Sign the Certificate on your Public CA.
- Import the certificate returned by your Public CA on CCE Wizard.
- Run the Step "Prepare CCE" on CCE wizard.
- If you are on CCE 1.4.1 only: Run Install-CcInstall
|
|
...
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.
Caption |
---|
0 | Figure |
---|
1 | 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.
Caption |
---|
0 | Figure |
---|
1 | HyperV Networking - Internet Connection Adapter |
---|
|
|
Confirm Office 365 Tenant
...
On
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.
Caption |
---|
|
Image Modified |
If there are no Options flowing, log into the ASM using Remote Desktop.
Execute the following command on a shell of the ASM Host:
Confirm :
- "Ethernet adapter vEthernet (SfB CCE Corpnet Switch)" adapter MAC start by 00:90
- "Ethernet adapter vEthernet (SfB CCE Internet Switch)" adapter MAC start by 00:10
- If unable to confirm, and the node has come directly form Manufacturing, a re-initialization will solve the issue.
...
- On the WebUI, access Diagnostics> Test a Call.
- Enter the phone number of your Skype Client and select your Call Routing Table "From Sip Trunk". The call should reach your Skype Client.
- Access Settings > Signaling Groups.
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:
- You are calling a number that exists in O365.
- You are using the proper SG.
- Your Calling Number Translation are sending E164 to CCE.
Caption |
---|
|
|
Caption |
---|
|
Image Modified |
- Click on Reset 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].
Caption |
---|
0 | Figure |
---|
1 | Request Message Counters |
---|
|
|
- Click on Reset Counters.
- Make a call from the PSTN to the Skype Client number on your Office365 Tenant.
- From the CCE Signaling Group, click on Counters.
Ensure there is an Outgoing Invite, and that the number of 1xx answer matches.
Caption |
---|
|
|
- Click on Reset Counters.
Confirm the call status
- If the call is not presenting a calling number:
- When using a SIP Trunk, you may have to Disable the "Send Assert Header" if your Sip Trunk provider does not support multiple PAI.
- If the call is having bad audio quality:
- Use the Call Quality Dashboard to ensure the firewall is properly configured.
If the Forward/Transfer or Conference are failing to escalate from Online call to CCE call:
Verify the Mediation server have been added to the teantusing the command:
Code Block |
---|
Get-CsOnlineUser -Filter "HostingProvider -like '*.<YourDomain.com>'" | Get-CsHybridMediationServer |
- If the Mediation Server is missing, follow "Configure Online Hybrid Mediation Server settings" on https://technet.microsoft.com/en-us/library/mt740651.aspx.
- Ensure the SBC and CCE are perfectly in sync with the Internet time.
- 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].
...
Group Policy: Computer>Administrative Templates>Windows Components> Internet Explorer: Make Proxy settings per machine (rather than per user).
Collect Log on CCE
- Log into WebUI.
- Access Diagnostics> Cloud Connector Edition Logging> Logging Configuration.
Select Enable CCE Logging.
Caption |
---|
|
|
- Place a call.
Click Download Log and specify a time window.
- StartTime. The time you run Start-CCLogging. Refer to the time in the upper right corner of the WebUI.
EndTime. The current time. Refer to the time in the upper right corner of the WebUI.
Caption |
---|
|
|
- Open the Log file using the latest version of Snooper.
...