[PHREAKNET-20] Billing based on individual CLLI zip codes

PHREAKNET-29

Requested Line

PHREAKNET-28

Phone Verification Failed

INTERLINKED-10

Telegrams can be sent by phone to non-subscribers

INTERLINKED-9

Phreaknet Directory link broken

INTERLINKED-8

Cannot use phreaknet wizard

PHREAKSCRIPT-12

Cannot utilize script because of patch issues

ASTERISK-13

Asterisk Framehook: DTMF to MF

INTERLINKED-7

TTY BBS lines (45.5+50) issues

PHREAKNET-22

Weather line international lookup problem

PHREAKNET-24

[REQ] TTY Telegrams

PHREAKNET-23

Wakeup calls not dialling at scheduled time

PHREAKNET-20

Billing based on individual CLLI zip codes

DOCS-2

Website not allowing me to log in

PHREAKNET-17

Director Listing Bulk Uploads Not Showing

PHREAKNET-16

RCMAC Provisioning is broken

ASTERISK-12

chan_dahdi: Make pulsemaketime, etc configurable

PHREAKNET-14

1+ calls do not work for single numbers

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: Improvement
Severity: Minor
Visibility: Public
Reported: 8/13/2023 10:39 AM
Last Active: 8/26/2023 5:52 PM
Status: Open
Reporter: KurisuYamato
Watching: KurisuYamato
Assigned To: Nobody

The current billing system uses the zip code assigned to a given user and / or the zip code assigned to a given Asterisk installation to generate billing charges based on the known 1977 rate table provided by the "phone thing" advertisement (linked in the relevant billing documentation on PhreakNet/) Of importance here is that this billing scheme has different values for ranges between 1-30 miles, which coincides well with the range of a modest metropolitan area.

This spawns a concept that a larger Asterisk installation on PhreakNet (one with many office codes) would naturally be simulating a larger urban and suburban area and those offices codes would, in reality, be located many miles away from one another.

The current billing system, however, applies just one zip code to the entire Asterisk install, thus putting all office codes on that install into effectively the same physical location.

The idea is that to better take advantage of the current rate-step billing system having such rate steps that are rarely used having an option to base the billing on the the zip code of an individual CLLI, taking real distances into account and making billing more dynamic for PhreakNet users living in these areas.

While purely a novelty change, it may spur more creativity in office code selection and creation as the network grows and potentially special interest groups common to a particular geographic area join and create their own spaces on the network.

I realize fully this has its greatest impact with localized areas who have a large number of calls being made to various answering numbers over a multiple CLLI based slice of the network, but the inspiration this can provide may well help the network continue to grow with more more creative diversity than ever.


Comments

8/26/2023 5:52 PM — KurisuYamato

An additional aspect of this which will be of benefit to the overall user experience is that with offices having specific zip codes the location of the office may be better represented; a zip code in a suburb of Memphis, for example, might display as "Bartlett, TN" rather than "Memphis, TN" on the bill statement, adding some diversity to the field of locations called, and making dialing random codes a bit more, for lack of a better phrasing, fun.

You must be logged in to leave a comment.