Bandwidth Number Pinger

Status

Active, Maintained, and In Production

Purpose

Ensure that numbers that have been ported out, or are otherwise unavailable from bandwidth, are not allocated to customers.

Checks the status of numbers to ensure they are still in service at BW. Numbers that are not in service (have been ported out) and are removed from Vunber stock.

Technology

Application is a C# .net4.6 console app.

Built with Microsoft Visual Studio Professional 2022 / 17.3.2

Source code

Application source code is stored ..... (SVN/Devops/Git)

Project: bwnumberstockpinger

Repo: https://vumber.visualstudio.com/_git/bwnumberstockpinger

Deployment Method

Selecting the 'webdeploy' build configuration will complile a release version to C:\webdeploy\numberpinger.

From there files are copy and pasted onto the production server

Description

The application retreived a list of number to check from the DB

For each number it calls the BW API at https://dashboard.bandwidth.com/api/tns

The application will set the status of the number based on the result of the API call.

Either the number will be 'active' or 'ported out'

Hosted

VM: vumWeb1

Run as a Scheduled Task every hour 

Logging

Logged locally and on the logging server, currently VumTest2:

L:\Logs\LogReceiverService\BwNumberPinger\_unauthenticated

Notes

Next Steps

• Automatically cancel unused numbers

• Get Canadian numbers available for selection so users are able to select by themselves

  1. Numbers that are not introduced back into stock at after three months (so six months after the user cancelled) should be cancelled.
  2. Add this to the number test routine:
     • Select number with > n calls in last x months - set status = 888 (pending disconnect with carrier)
  3. For now manually disconnect these numbers