There are some requirements for number utilization that are vague to me. I haven?t really found the exact requirements, but didn?t try super hard. We get very few disconnects, and don?t have a specific routine for returning them, it?s more of running a report and deciding when to export a kill list. We have a couple of customers with ?too many? numbers that they don?t use, and it doesn't seem to be an issue. We simply charge a trivial amount to keep them active. But these are business customers with dozens or hundreds of numbers and active service. I think from a business perspective I?d recommend that you have some sort of maintenance mode to suspend service but keep the number, just a few bucks a month. On May 15, 2023 at 10:29:37 AM, Matthew Crocker via VoiceOps < voiceops at voiceops.org> wrote:
Hello,
It is our practice to release numbers back to the original carrier when a customer cancels service and doesn?t port the number away. We have some residential customers that want to cancel service over the winter and have us retain the number so they can re-use it in the spring. I?m trying to find some FCC or NANPA documentation that says we are/aren?t allowed to do that for a customer. Ultimately we will probably convert the customer from their FTTH/ONT voice to a soft phone voice during the off-season, that way they are still a customer and still paying for service. I don?t want to just camp on numbers and have to maintain the inventory.
Anyone have any documentation on the correct way to handle disconnected numbers?
-Matt
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops