[PHREAKNET-7] Subscriber Service Disconnect Request Option

DOCS-1

Kickstart the wiki

ASTERISK-9

indications: Add support for >2 frequencies

INTERLINKED-6

PhreakNet Forums

ASTERISK-7

Improve sound control capabilities

PHREAKNET-11

Yealink T33G: add provisioning support

PHREAKNET-10

Enhanced utilization of Feature Group D

ASTERISK-11

chan_dahdi: Add wink guard

ASTERISK-10

Proctor application for DAHDI

PHREAKNET-9

General WKSHWIAXCG0 enhancements

PHREAKNET-8

Setup a Patreon to cover expenses

INTERLINKED-5

Update blue box

PHREAKSCRIPT-10

Update CiscoCallManager patch URL

ASTERISK-8

Optimize boilerplate RSA to MD5 fallback

INTERLINKED-4

InterLinked Issues API

PHREAKNET-7

Subscriber Service Disconnect Request Option

INTERLINKED-3

InterLinked API site is down

PHREAKNET-6

Verification flags international calls

ASTERISK-4

XML documentation examples

INTERLINKED-2

PhreakNet Email for BoD Members

PHREAKSCRIPT-8

Boilerplate force MD5 broken

ASTERISK-6

Resonant Filter To Simulate N-Carrier

PHREAKNET-3

Provide commissions to 976 number owners

PHREAKSCRIPT-9

Add DAHDI to build tests

PHREAKSCRIPT-7

Boilerplate musiconhold.conf is wrong

PHREAKSCRIPT-6

Trace autosend

INTERLINKED-1

Phone verification is broken

PHREAKSCRIPT-5

coindsp patch missing

PHREAKNET-5

Semipublic inward boilerplate broken

PHREAKSCRIPT-4

Add less invasive/deterministic modes

PHREAKNET-4

Hosted lines defaults exchange on error

PHREAKNET-2

Asterisk reload following unsuccessful call

PHREAKSCRIPT-3

Report failure as requested

ASTERISK-5

Various ADSI issues

PHREAKNET-1

Add third-party billing integration

ASTERISK-3

Asterisk Wiki issues

PHREAKSCRIPT-2

Remove absolute sbin path

PHREAKSCRIPT-1

Hangs when certain invalid commands entered

ASTERISK-2

func_notchfilter: ISO C90 compiler fixes

ASTERISK-1

Add Assert application

← Issues Home || New Issue →

Sort Normal || Priority

Details

Category: PhreakNet Network
Type: New Feature
Severity: Minor
Visibility: Public
Reported: 6/19/2022 12:45 PM
Last Active: 6/20/2022 9:18 PM
Status: Open
Reporter: KurisuYamato
Watching: KurisuYamato
Assigned To: Nobody

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.


Comments

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?

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 logged in to leave a comment.