Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHSYM-23022
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c9, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

 

Panel

This section includes:

Table of Contents
maxLevel3

 

...

  1. Log into the

    Spacevars
    0product
    WebUI.

  2. Access Tasks > Application Solution Module > Operational Status.  

    Caption
    0Figure
    1Operational Status

     

    1. 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.*
      
    2. Ensure four VMs are displayed. If not, restart the deployment.

  3. Ensure the latest Software Installed Version (CCE) is installed.

    Caption
    0Figure
    1CCE - Sosftware Installed Version

  4. Ensure the Auto Maintenance Status is set as None.

    Caption
    0Figure
    1CCE - Auto Maintenance Status

     

    1. If the status is Update OS or Bits, you should wait until the end of the update.
    2. If the status is Auto-Recover, check: https://blogs.technet.microsoft.com/sfbhybridvoice/2017/03/10/understanding-cloud-connector-edition-auto-recovery.
  5. Ensure the proper version is displayed as the Software Running Version.

    Pagebreak
    Caption
    0Figure
    1CCE - Software Running Version

     

    1. If the Software Running version is None or Unknown, log into the ASM using Remote Desktop.
    2. Connect the SBC Edge VM, open Services and ensure the following six Skype for Business Servers are Running. See below.

      Caption
      0Figure
      1Skype for Business Services


      c. If the Edge Servers do not start, see below for identifying solutions.
      Caption
      0Figure
      1If Edge Servers Do Not Start
       Problem - What to CheckMost Likely CauseSolution

      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 IssueOn 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

...

  1. 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
    0Figure
    1HyperV Networking - Corpnet Connection Adapter

  2. 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
    0Figure
    1HyperV Networking - Internet Connection Adapter

     

    Pagebreak

Confirm Office 365 Tenant

...

  1. On 

    Spacevars
    0product
    WebUI, access Settings > Signaling Groups. On the CCE Signaling Group, ensure the "Service Status" is Up.

  2. Click on Counters and ensure Options are flowing in both directions and that the number of 2xx answers is matching.

    Caption
    0Figure
    1Request Counters

    Image Modified

     

    1. If there are no Options flowing, log into the ASM using Remote Desktop.

    2. Execute the following command on a shell of the ASM Host:

      Code Block
       ipconfig /all
    3. 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
    4. If unable to confirm, and the node has come directly form Manufacturing, a re-initialization will solve the issue.

...

  1. On the 
    Spacevars
    0product
    WebUI, access Diagnostics> Test a Call.
  2. Enter the phone number of your Skype Client and select your Call Routing Table "From Sip Trunk". The call should reach your Skype Client.
  3. Access Settings > Signaling Groups.
  4. On the CCE SG, click on Counters.

  5. 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
    0Figure
    1Test A Call

    Pagebreak
    Caption
    0Figure
    1Modify Counters

    Image Modified

  6. Click on Reset Counters.
  7. Make a call from the Skype client to a PSTN number that does not exist on your Office365 Tenant.

  8. From the CCE Signaling Group, click on Counters.

  9. Ensure there is an Incoming Invite and that the number of 1xx answer matches.

    1. 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
      0Figure
      1Request Message Counters

  10. Click on Reset Counters.
  11. Make a call from the PSTN to the Skype Client number on your Office365 Tenant.
  12. From the CCE Signaling Group, click on Counters.
  13. Ensure there is an Outgoing Invite, and that the number of 1xx answer matches.

    Caption
    0Figure
    1Outgoing Invite

  14. Click on Reset Counters.

Pagebreak

Confirm the call status

  1. 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.

  2. If the call is having bad audio quality:
    • Use the Call Quality Dashboard to ensure the firewall is properly configured.
  3. If the Forward/Transfer or Conference are failing to escalate from Online call to CCE call:

    1. Verify the Mediation server have been added to the teantusing the command:

      Code Block
      Get-CsOnlineUser -Filter "HostingProvider -like '*.<YourDomain.com>'" | Get-CsHybridMediationServer
    2. If the Mediation Server is missing, follow "Configure Online Hybrid Mediation Server settings" on https://technet.microsoft.com/en-us/library/mt740651.aspx.
    3. Ensure the SBC and CCE are perfectly in sync with the Internet time.
    4. 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).

Pagebreak

Collect Log on CCE

  1. Log into
    Spacevars
    0product
    WebUI.
  2. Access Diagnostics> Cloud Connector Edition Logging>  Logging Configuration.
  3. Select Enable CCE Logging.

    Caption
    0Figure
    1CCE Logging

  4. Place a call.
  5. Click Download Log and specify a time window.

    1. StartTime. The time you run Start-CCLogging. Refer to the time in the upper right corner of the WebUI.
    2. EndTime. The current time. Refer to the time in the upper right corner of the WebUI.

      Caption
      0Figure
      1Download Log

  6. Open the Log file using the latest version of Snooper.

...