Recently, while solving a customer service issue, the subscriber mentioned to me that they no longer wished to use 3 previously provided lines and that I could disconnect those. That was, of course, a trivial process -- remove the configuration from sip / pjsip.conf files, delete the reference in phreaknet-hints, and lastly removal of the line in the hosted lines page.
The act of doing such isn't a problem, of course -- it's just the reverse of setting up a line, but the fact that the user had to mention this to me while we had a chance situation to talk made me think that a select-able option to request a line be disconnected may be useful in these cases to slightly speed up the process and keep the network "clean" of numbers that aren't in use but are still assigned.
I would imagine the function would send a message to the relevant switch owner and could possibly flag the hosted line on the manage hosted lines page with some kind of color coding or other indication that this line has been requested to be disconnected, helping the switch owner take action on that line and cleanly remove it from active use.
6/20/2022 9:18 PM — KurisuYamato
Thinking about it the idea of immediate deletion from the provisioning system and sending a notification would speed things along, and help any potential conflicts from re-provisioning an ATA to another host while the previous provisioning information is still active.
To that end I feel deleting the line outright and sending a notification actually would be the better option.
You must be
6/20/2022 5:24 PM — InterLinked
To that end, would you want it to merely notify the switch owner that it's pending deletion? (in addition to possible color coding)?
How would you feel about just deleting the line outright, as well as sending you the notification?