• Home
  • Troubleshooting

Troubleshooting Not Provisioned e911

Written by Marissa Orsini

Updated at April 27th, 2023

Contact Us

  • The Essentials
    FAQs Forms
  • Announcements
    Carrier Events mFax Events Platform Events Release Notes
  • Billing Administration
    Datagate OneBill
  • Faxing
    mFax - Analog mFax - Digital Native Fax
  • Hardware & Software
    Manual Configuration Provisioning NDP Axis Cisco Fanvil Grandstream Polycom Snom Yealink Mobile Applications Desktop Applications Mobile-X SNAPbuilder TeamMate Connector UC Integrator
  • Hosted Voice
    Auto Attendants Branding Call Queues Call Routing CDRs Conferencing E-911 Features Fraud Integrations Inventory / Phone Numbers Local & Toll Free Porting Onboarding Recommendations SNAP.HD SIP Trunking SMS / MMS Users Voicemail Caller ID
  • Troubleshooting
    VoIPmonitor Firewalls PBX
  • Ray's Stuff
+ More

Table of Contents

e911 Summary Troubleshooting e911

Scope:

This document serves as a guideline on what to look for when OMP shows that all previously provisioned e911 is unprovisioned

 

Requirements:

  • Access to dashboard.dashcs.com
  • SSH Access on Core Servers
  • T3 Skills Required
 

 

e911 Summary

As of writing this KB, e911 is provisioned with Bandwidth.  It makes api calls to their emergency service.


Troubleshooting e911

  1. The first thing you want to check with e911 that is showing as unprovisioned in the OMP is to check the portal debug log. 
  2. Establish an ssh connection to the core server ( please see the library )
ssh -l <username> -p
  1. Turn on OMP debugging
    Open portal_config.php
sudo vi/etc/netsapiens/portal_config.php
  1. Set nsdebug to 2 and save the file and exit
     
  2. Once you're back to the cli prompt, copy and paste the following
tail -f /usr/local/NetSapiens/netsapiens-portals/tmp/logs/debug.log | grep -i -B10 -A10 Bw911
  1. Navigate to OMP -> Inventory -> 911 Numbers to generate debug logs. From here, watch the output of the tail command above and look for anything that refers to Credentials error.

    Look at the output of api curl url to make sure it is being sent to https://service.dashcs.com/dash-api/xml/emergencyprovisioning/v1?wsdl
    Get the api curl curl_result output and save it on your notepad

    Look for the api response code, if the response code is not 200 then make note of the response code and save it on your notepad for escalation.
  2. If the above logs show credentials error, then we need to verify the credentials via dashboard.dashcs.com
  3. Navigate to https://dashboard.dashcs.com (refer to the library for credentials)
  4. Once logged in, click Users
  5. Make note of the user that is Named as API OIT-BW API
  6. Verify Sip Peers to make sure that core-atl is on that list
  7. Now go to the cli prompt and open portal_config.php to verify the username is set with the credentials as confirmed in the ( credential library ) is accurate
sudo vi /etc/netsapiens/portal_config.php
  1. You should have these three configs
  2. If you have confirmed the credentials and that they are accurate and it is still showing as unprovisioned and the API debug log is showing as invalid credentials, then we have to reset the password.
  3. Go back to dashboard.dashcs.com -> Users and click on the API user you noted above.
  4. Click Change password, choose a randomized password, and save the new password.
  5. Go back to the cli prompt where you have the portal_config.php open and update the password with the new password.
  6. Go to Inventory -> 911 Numbers tab to resubmit the API request.
  7. If you've done all of these and it is still not working, open a ticket with Bandwidth support then open a Ticket with Netsapiens Support, Create an IP Case and Tag the next Engineer and provide a link to this KB that you've followed and any details that you may have found during this troubleshooting.

 

provisioning errors e911 issues

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • IP Addresses & Ports
  • Quick Response to a Compromised User/Device
  • Network Configuration Best Practices

Knowledge Base Software powered by Helpjuice

Expand