Troubleshooting SNAPmobile

1. Verify a microphone is detected
   
    
2. Once a microphone is connected check if SNAPmobile Web is registered. If it still is not registered, move on to step 3.
   1. If a microphone is connected to your computer but SNAPmobile Web says that there isn't, make sure you're allowing apps access to your Microphone. You can check this under Start > Settings > Privacy > Microphone and making sure Allow apps to access your microphone is set to On.
      
3. Ensure Google Chrome is up-to-date.
   1. Click the Ellipsis
   2. Go to Help > About Google Chrome.
      
   3. Under About Chrome, you will be able to see which version you are running and if any updates are available.
   4. Note: Older versions of Chrome will sometimes say that they are up to date when they actually are not. If you believe that you are running an older version of Chrome and would like to manually update:
      1. Download Chrome
      2. Run the "ChromeSetup.exe" file, once install is completed, the most recent version of Chrome will open automatically.
          
4. Clear your Browser Cache/ Cookies
   • Close the SNAPmobileWeb
   • With Chrome open, hold Ctrl + Shift + Delete (or navigate to More tools > Clear browsing data)
   • This is going to open the Clear browsing data menu. For the time range, select All Time, check Cookies and other site data and Cached images and files, and then click Clear data.
     
   • Re-open SNAPmobile Web from Apps Navigation
      
      
5. Select the SNAPmobile Web window, press CTRL + SHIFT + V (Windows), or COMMAND + SHIFT + V (MAC) to launch the Developer Tools.
    
6. At the DevTools window, click the Console tab
   
    
7. Click the SNAPmobileWeb window and press CTRL + R to refresh.  This will refresh the page and will cause it to re-register
    
8. At the DevTools Console tab, check if there are any errors. Make notes of these errors.
    
9. Check Web Socket Connection 
   1. At DevTools, click Network -> WS tab
   2. Hit Refresh on the SNAPmobileWeb window.   
   3. A working example would look similar below
   4. An example of when the SMW is not able to connect.  port 9002 is currently unavailable or blocked on the firewall.  
   5. An example of when the SMW is not able to connect due to 503 on a single server that it is set to.  Be default, there would be another server that the SMW will try to connect to. In this case, there's only one server defined with WS_SERVERS. This would also happen if all GEO servers were to go down or if someone accidentally set 503 on all nodes.
       
10. Log any errors in the ticket that you found and escalate to T2 or higher

Enable Debug Options for Webphone

1. When SNAPMobile Web opens, press F12 to open the DevTools.
2. Select Application at the top.
   
3. Under Storage, select the drop-down menu under Local Storage, click on the FQDN (https://manage.oitvoip.com/webphone/)
   
4. Filter for SIP
   
5. Change the following values
   1. netsapiens-webphone_sip-log: From: error To: debug
   2. netsapiens-webphone_sip-trace: From: false To: true
      
6. Select the Console tab
7. Click back on the webphone tab and hit F5 to refresh.
8. Log any registration information found in the console in the ticket that you found, and escalate to T2 or higher