...

Confirm CCE state

Confirm CCE Status

Once CCE deployment is complete, confirm the following:

...

At this point, the CCE is running.

Confirm SBC state

1. On 

   Spacevars
   0 product

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

    

   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.

At this point, both the CCE and SBC are up and running.

Confirm environmental state

Confirm the public SBC Edge FQDN is properly mapped to the External IP used in Configure CCE (via SBC Edge WebUI).

...

• • Log into the ASM using Remote Desktop.
  • Connect to the the Edge VM, and open the Powershell command prompt.

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

    Code Block
    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

Confirm the user state

1. Access the Office 365 portal, access Admin Center>  Skype for Business> Voice> Voice User.
   
2. Confirm the user has a phone number and a license assigned.

3. Confirm that PSTN connectivity is "On-Premises".

   Caption
   0 Figure 1 Confirm User State

4. Log into your Office 365 Tenant using PowerShell

5. On Office 365 Tenant, use "Get-CsOnlineUser" to confirm that the user is activated for EnterpriseVoice, HostedVoiceMail and HybridVoice.

   Code Block
   PS> $user = Get-CsOnlineUser site2user1 PS> $user.EnterpriseVoiceEnabled True PS> $user.HostedVoiceMail True PS> $user.VoicePolicy HybridVoice

6. On Office 365 Tenant, use "Get-CsUserPstnSettings" to confirm that the user is assigned to the proper HybridPstnSiteName.

   Code Block
   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

7. Connect a Skype for Business client using the account below:

   Caption
   0 Figure 1 Skype for Business Client

Confirm the call establishment

1. On the 

   Spacevars
   0 product

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

   Caption
   0 Figure 1 Modify Counters

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

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
    0 Figure 1 Outgoing Invite

14. Click on Reset Counters.

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, you should verify :

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

Confirm Auto-Update

1. 1. Ensure the SBC and CCE are perfectly in sync with the Internet time.
   2. 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].

Confirm Auto-Update

1. Check https://blogsCheck https://blogs.technet.microsoft.com/sfbhybridvoice/2017/04/07/troubleshooting-cloud-connector-edition-1-4-2-updates-and-new-deployments/

...

Group Policy: Computer>Administrative Templates>Windows Components> Internet Explorer: Make Proxy settings per machine (rather than per user).

Collect Log on CCE

1. Log into

   Spacevars
   0 product

   WebUI.
2. Access Diagnostics> Cloud Connector Edition Logging>  Logging Configuration.

3. Select Enable CCE Logging.

   Caption
   0 Figure 1 CCE 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
      0 Figure 1 Download Log

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

Update and Confirm Window's Service Version

1. Through Windows, log into the CCE's VM.
2. Locate C:\Windows\System32\profsvc.dll.

3. Right-click on the filename profsvc.dll and select Properties.

   Caption
   0 Figure 1 Select File
   Image Added

4. Select the Details tab.

5. If the file version is 6.3.9600.17930, no action is required.

   Caption
   0 Figure 1 File Details
   Image Added

6. Access the cmd prompt and execute the systeminfo.ext command.

7. Verify prerequisite KB2919355 is already installed on the VM.

   Caption
   0 Figure 1 Verify file via Command Prompt
   Image Added

8. Access the Control Panel and select System and Security > Windows Update.

9. Click Automatic Updates.

10. Following Windows checking for updates, click on the “<number> important updates are available" link.

    Caption
    0 Figure 1 Automatic Updates
    Image Added

11. Navigate to the Windows Update Options and turn on Check for Updates Automatically.

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

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

    Caption
    0 Figure 1 Restart Option
    Image Added

     

     

13. Anchor
    Change Settings Change Settings

    Through System and Security > Windows Update, click Change Settings and change Important updates to “Never check for updates (not recommended) and click OK.

    Caption
    0 Figure 1 Important Updates
    Image Added

14. Restart the virtual machine.

    Caption
    0 Figure 1 Restart the VM
    Image Added

15. Check windows update history to verify KB3078676 was installed successfully as follows:
    1. Locate C:\Windows\System32\profsvc.dll.

    2. Right-click on the filename profsvc.dll and select Properties.

    3. Click View update history.

       Caption
       0 Figure 1 View Update History
       Image Added

       Caption
       0 Figure 1 Review Update History
       Image Added

16. Verify File version of profsvc.dll has been updated to 6.3.9600.17930.

    1. Locate  C:\Windows\System32\profsvc.dll.
    2. Right-click on the filename profsvc.dll and select Properties.
    3. Click Details.

    4. Verify product version is 6.3.9600.17930.

       Caption
       0 Figure 1 Select File
       Image Added

       Caption
       0 Figure 1 Select Details
       Image Added