[MOONSHOT] Verify that we own numbers purchased through FirstPoint/Endstream

[uncheckederror]

@uncheckederror If we buy a number from anyone besides FirstPoint/Endstream, it is safe to assume we own it. Otherwise it needs manual verification.

Originally posted by @danry25 in https://github.com/AccelerateNetworks/NumberSearch/issues/71#issuecomment-775471622

To verify that we own a number we'll need a FusionPBX API that we can use to place a call to the number in question and verify that this number is being route to us.

[uncheckederror]

@danry25 is this possible through the new dsip router APIs?

[danry25]

Yea, this is possible through the new dsiprouter APIs. I need to get this implemented,

[danry25]

I still need to provide you with an API to handle this. Call48 also needs number validation since we generally have to email them to manually assign our numbers ordered via API or their website (despite them automatically billing us for these numbers!).

[danry25]

@thefinn93 Could you assist in providing an API to place these test calls, then logic to catch calls from our test number in FusionPBX?

[thefinn93]

I have added actions originate and cdr-list to the FusionPBX API.

[thefinn93]

catching the test call and doing something special with it will require a little more BS, working on that now.

[danry25]

I can catch the verification call in FusionPBX using Call Block if we use a consistent caller ID, we can create a call to each number in Owned Numbers that is marked Active using Twilio's Make a Call REST API, then we can use the cdr-list endpoint after each 100 test calls to numbers in a given FusionPBX domain to see if the call actually completed.

Other erratta we should handle is if the call is answered (which should never ever happen) the phone number should be flagged for review by our Customer Support team in the daily briefings email and further test calls should cease until support toggles testing a given number back on (perhaps in Owned Numbers in Ops?).

Dan's ToDo API endpoints I have provided examples for:

• Twilio's Make a Call REST API
• Our FusionPBX API cdr-list endpoint
• Pulling Twilio's call records to see if a call connected (or perhaps this is included in the response? to the REST call?)

Tasks:

• [ ] Block inbound calls from 3603352884 to any number in a FusionPBX instance (pending this FusionPBX.com ticket)
• [x] Verify 3603352884 as a caller ID on Twilio
• [ ] Disable checking numbers not routed to a FusionPBX instance (need to work with @uncheckederror on a UX for this)