1 $Id: TODO,v 1.42 2000-03-06 14:12:56 ivan Exp $
3 If you are interested in helping with any of these, please join the mailing
4 list (send a blank message to ivan-freeside-subscribe@sisd.com) to avoid
9 more email which should make it into a more organized TODO list:
11 I would also love to see Freeside support bandwidth billing by reading the
12 Cisco NetFlow Accounting data so we and other ISP's could automatically bill
13 co-located servers and even potentially other virtually hosted sites like
14 MUD, Palace Chat, IRC Chat, etc based on the bandwidth they use or average
15 sustained rates or whatever. I'm not much of a programmer so I don't know
16 what all this entails but I did download a NetFlow client agent/whatever for
19 It would also be nice to see Freeside be able to read Apache log files and
20 bill customers for web traffic that way as an option also. Plus an option to
21 bill for excessive disk usage without having to use quotas if you didn't
22 want to, would be a nice feature as well. So you could monitor with a script
23 or something to see how much disk space a user was using then get some
24 average and charge a certain amount for anything above some preset limit for
25 that account type. I might be able to hack something like this up, but I'm
26 not 100% sure where to start or if there is something out there that could
29 Do you think that you will ever support the HKS CCVS (Hell's Kitchen
30 Software Credit Card Verification Software) since Red Hat bought them out
31 and is going to be including that for credit card processing when you buy
32 the professional version? What about possibly supporting the OpenCCVS which
33 is a GNU/GPL version of a credit card program? I haven't had time to comb
34 through the Freeside code to see how hard it would be to add support for
35 these as externally called programs.
37 Also any thoughts on help desk, and knowledge base stuff? Any thoughts on
38 this stuff, and how possible and what kinds of work or time frame would be
49 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
50 (User Info) http://www.fxp.org/~jedgar
51 The links above are your best bet for basic cvs server configuration. Once you have a pserver set up, you
52 may consider using cvs via ssh. All you need to do is the following:
54 1) Have ssh and sshd set up on the client and server machines
55 2) Set CVSROOT="joe@example.com:/home/ncvs"
56 3) Set CVS_RSH="/usr/local/bin/ssh"
58 (Obviously, insert the proper host/paths above)
60 You can also set up cvs/ssh to not need a password every time (similiar to an initial 'cvs login'):
62 1) run ssh-keygen on client machine using no passphrase.
63 2) copy/add ~/.ssh/identity.pub on the client to ~/.ssh/authorized_keys on the server
64 (man ssh for more details)
66 The main reason I mentio
68 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
69 (User Info) http://www.fxp.org/~jedgar
72 There's no way to do this currently, though it would be pretty
73 straightforward to modify the source - specifically, the _collect_
74 subroutine in FS::cust_main.
76 On Mon, Dec 13, 1999 at 04:05:32PM -0700, Jeff Garner wrote:
77 > Freeside will e-mail my users when they are billed if they are setup as
80 > When setup by credit card it does not e-mail them. Is there a way to
81 > turn on e-mail invoices for those who are billed via credit card? Kind
82 > of like a recipt of billing....
85 doc: http://www.softagency.co.jp/mysql/qmail.en.html
87 sql1992.txt standard is 18 character column names. shoot for that, not just
88 32 (postgresql default)
90 Also note that (AFAIK) Freeside won't display any package that has more
91 than one service on the "Add Customer" page. The reason for this is
92 because there's no way to dynamically alter the displayed html form
93 based on which package is selected. One possible solution would be to
94 make an additional page that's used in the signup process that would
95 display the form for each package, like a MS-style "Wizard". The first
96 page lets you select the package, then the second page has the custom
97 form with fields for each service in that package and a save button. Of
98 course, that would require a little perl work.
101 Scott Cruzen <sic@boernenet.com>
104 Your suggested script with back up /usr/local/etc/freeside, but will miss
105 any database not named `freeside'. Both of our scripts are specific to
106 MySQL. If you're interested in contributing to Freeside, maybe you could
107 work on a script which: reads the mapsecrets configuration file and then
108 each secrets file to find out what specific database engine(s) (MySQL,
109 PostgreSQL, etc.) and database(s) need to be backed up, then does so,
110 serializing backups of the same engine, i.e. stop mysql, do all the mysql
111 backups, start mysql, stop postgresql, do all the postgresql backups,
112 start postgresql, etc.
115 > mysqldump -t freeside > fs-backup.sql
117 > tar -Pzcvf fs-backup-`date +%y%m%d%H%M%S`.tgz fs-backup.sql /usr/local/etc/freeside/
120 I chose to use counters in the filesystem because there is no standard way
121 to get the value of an auto-incrementing keyfield which is common across
122 all databases (as seen through DBI/DBD).
124 It certainly wouldn't be a bad idea to use the database-specific methods,
127 htdocs/edit/svc_acct.cgi:
128 (Does the `*HIDDEN*' show up when you are adding a new account, and
129 specify the password, then receive an error and are returned to the form?)
132 Thought some of you might be interested in this:
134 <ftp://ftp.minivend.com/pub> has CyberCash compatibility modules for
135 Paymentnet <http://www.paymentnet.com> and Authorizenet
136 <http://www.authorizenet.com> which should allow you process transactions
137 using those services as well as CyberCash.
139 The files are named CCLib.pm.paymentnet and CCLib.pm_authorizenet,
140 respectively, and are installed by renaming to CCLib.pm and moving to your
141 site_perl directory. Otherwise, follow the directions for Cybercash v2 in
142 htdocs/docs/config.html
145 fs_passwd/ is a client-server replacement for the `passwd', `chfn' and
146 `chsh' commands that updates the Freeside database. (so for that to be
147 useful, you'd have to be exporting that data periodically)
149 fs_radlog/ is a client-server RADIUS log parser that stuffs the data into
150 SQL. It isn't finished, and probably won't be unless someone who I can't
151 convince to use one of the RADIUS daemons that logs to SQL directly pays
152 me money or something.
154 fs_signup/ is a client-server signup server. i'm just finishing it up
155 now; probably isn't on your machine yet.
158 http://www.sisd.com/freeside/list-archive/msg00812.html
160 package definitions should be implicit allow wrt agent types, not implicit deny
161 (with the old behavior possible via a config file)
163 > So is there anyway it could be setup to allow you to select a "primary
164 > service" from each package? This service would be the one you were prompted
165 > for. Could the signup server then be expanded to allow users to go into
166 > their package and "turn-on" the remaining non-primary services(using the
169 take the GPL'ed whois proxy stuff at www.geektools.com and turn it into
170 intelligence for Net::Whois.
172 A web version of the fs_passwd stuff would be nifty.
174 If you have Cistron authenticating directly from MySQL, you can replicate
175 in real-time instead of exporting periodically. See
176 <http://www.mysql.com/Manual_chapter/manual_Common_problems.html#Replication>.
179 <http://www.sisd.com/freeside/list-archive/msg00546.html>, and
180 <http://www.sisd.com/freeside/list-archive/msg00554.html>
182 and http://www.sisd.com/freeside/list-archive/msg00423.html
184 > > 5: Is there anyway to get freeside to send a sysadmin a warning when a
185 > > credit card has expired?
186 No, but there should be.
188 Put this in the doc (quoting Mark Wells <mark@pc-intouch.com>):
189 >Of course, thanks to the sheer coolness of SQL and MyODBC, you can do
190 >whatever reports you want in basically whatever application you want.
191 >There's no need for Freeside itself to do any reports at all.
193 middle names and titles
195 On Wed, Jul 07, 1999 at 01:11:40PM -0400, Frank Nazario wrote:
196 > Playing and entering information to Freeside i encountered the following
199 > View Customers by Agent
201 > View Pending Invoices
204 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
205 Not to say that it shouldn't be a configurable option.
207 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
208 (at least until the idea of a default domain goes away)
210 FS::Record::qsearch does an eval every loop iteration (which is itself not
211 guaranteed to work across all DBD's and should be fixed). This has got to be
212 slow. Fix it. (I think recent Perls might have a way to accept a variable
213 there, no eval needed?)
215 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
216 `shells' configuration file before importing, and removed them afterwords?
217 (even better if svc_acct.import did that automatically - it could just
218 munge and restore @FS::svc_acct::shells... hmm.)
220 > BTW, Ivan, I am trying to verify in an additional database table that a
221 > particular user doesn't exist. This database is used to store email aliases a$
222 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
223 > with the idea of just writing the aliases to an email only svc_acct that
224 > doesn't write to the password file, but that isn't really how I want to do it.
226 Actually, I think that's a pretty good way to do it. Cerkit contributed
227 support a little while back for svc_acct.pm and svc_acct.export for
228 multiple export targets. It needs to be cleaned up and documented, which
229 I'll try to get to soon. For this to work correctly, the svc_acct_sm
230 table should go away, along with the concept of a "default" domain.
232 default setting for new packages should allow all agents to purchase them...
233 with a config file for the old behaviour
235 fix or replace Term::Query (Quiz::Question doesn't do what i need)
237 Check config file reading stuff from CPAN
239 Authorizenet module from CPAN!
241 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
244 I'm hoping Freeside can support arbitrailly complex pricing plans
245 because of a simple concept: all prices are perl expressions. So if
246 you use `19.95' for example, perl evalates that to be `19.95'. But if
247 you need to do a complex pricing scheme, you just need to write an
248 appropriate perl expression, which will most likely pull data from the
249 database to return pricing. Some things will already log to SQL; for
250 example most RADIUS servers can or have a patch available. Getting
251 Freeside to bill based on any sort of data then becomes a matter of
252 importing the data into the database.
254 There are some issues involved with pro-rating, partial month charges,
255 that sort of thing. Expressions will need a standard way to have the
256 applicable time/data ranges passed to them. Also the expressions are
257 currently running under the Safe perl module, and the opmask might not
258 be right in all situations. I'll try to spend some time working on
259 this if you are using it.
261 > 2. can customers view their bills on-line.
263 Not yet; it needs to be proxied from Freeside to a customer web server in
264 a secure way using something not completely unlike the fs_passwd,
265 fs_passwdd, fs_passwd_server trio.
268 > Lastly, if someone over pays on an invoice, the credit part does not flow
269 > over to other invoices..
271 The total balance flows over correctly, but individual payments don't.
272 The code you're looking for is in FS::cust_pay::insert
274 The question of what to do with overpayments that don't have another
275 invoice to flow into (yet.. or possibly not) is still an open one. The
276 legacy system Freeside replaced long ago had a separate place for this
277 (payments waiting for an invoice) for each customer, and it gave our
281 option to relax username uniqueness in favor of username+domain or mail/shell
282 vs. radius to ease import for isp's with namespace problems or who buy others.
284 do i have to store anything for radius realms besides regular radius attributes
285 (which are handled fine now)?
287 warn or complain or something when invoice_from is empty (and we use it)
289 Right now Freeside uses the `freq' field of a package definition as a
290 number of months. The specific section of code you're looking for is in
293 #change this bit to use Date::Manip?
294 #$sdate=$cust_pkg->bill || time;
295 #$sdate=$cust_pkg->bill || $time;
296 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
297 my ($sec,$min,$hour,$mday,$mon,$year) =
298 (localtime($sdate) )[0,1,2,3,4,5];
299 $mon += $part_pkg->getfield('freq');
300 until ( $mon < 12 ) { $mon -= 12; $year++; }
301 $cust_pkg->setfield('bill',
302 timelocal($sec,$min,$hour,$mday,$mon,$year));
303 $cust_pkg_mod_flag = 1;
305 ..and when I went poking for this, looks like it tells us just what needs
306 to be done! Hehehe...
308 Date::Manip can handle cool things like "+ 1 month" (actually the current
309 case of /^(\d+)$/ would have to be added as a special case of "+ $1
310 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
313 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
314 > I can't quite seem to figure out how this exporting works. From what I
315 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
316 > /etc/shadow, etc. files. Is this only for initial setups with the
317 > export hooks being in the pm's?
319 You can use both, or just one method. The configuration files control
320 this. One of the things in the TODO is to take out the last few things
321 that aren't customizable wrt this and put them in config files.
323 http://www.daemonnews.org/199905/user-mgmt.html
325 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
326 submitted upstream!), or remove requirement from bin/svc_acct.import and
327 bin/svc_acct_sm.import and take it out of the install instructions.
329 use this cool link to explain the Freeside API
330 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
332 Multiple tax rates by geographic region (county, state, and county) are
333 supported; just choose View/Edit tax rates from the main menu.
335 Multiple tax rates by package are not (yet) supported.
337 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
338 > How would you handle something like multiple tax rates and multiple
339 > states? For example in Connecticut, they just changed computer and/or
340 > data processing services to 3% (whatever that is), and everything else
344 > Second, when trying to add a new user I get two types of errors; first one
345 > is when I place an e-mail address and select the "submit," Freeside
346 > complains with "Error: Unknown local account (specified literally)"
348 You probably put a (local) email address in for email invoices. Freeside
349 stores these as references to the database records, so (for example) they
350 follow username changes.
352 I'm guessing you put in the email address that you were creating, and got
353 that error because it didn't exist yet. Sounds like a buglet to me. I'll
354 try to fix that soon; in the meantime you can add the invoicing email
357 (workaround for postgres before 6.5) (unlikely to ever be implemented)
358 In the mean-time, this could probably be fixed with the reverse of
359 the kludge in FS::Record::new. This removes `$' and `,' from money fields
360 coming out of the database. Something which fixed up the data so Postgres
361 was happy with it could go in FS::Record::_quote, for data going into the
364 our data display problem might be a Freeside problem wrt not using
365 Oracle-compatible DBI syntax (uses the return value from $sth->execute as
366 a number of rows). Fixing this is on the TODO.
368 hooks for arbitrary commands out of configuration files
369 svc_acct.pm svc_acct_sm.pm etc.
371 Add this to a FAQ, along with doing it for middle names:
374 > What I'm finding difficult is how to easily
375 > customize fields. For example, I am trying to add a "middle name" field
376 > to the Customer Edit, view, etc. If I'm going about it right, it appears
377 > I have to edit the cust_main.cgi under edit and edit/process and the
378 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
379 > some light on the best way of doing this.
381 You have the basic idea. To implement that completely, I would:
382 - Add the new field to bin/fs-setup for new users
383 - Document the field in htdocs/docs/schema.html
384 - Document the change in a new file, htdocs/docs/upgrade4.html
385 * Run bin/dbdef-create
386 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
388 For bonus points, I'd grep around for the various bits which use "$first
389 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
390 , like search/cust_main.cgi
392 document security model:
393 Don't forget about Apache usernames - since, via the mapsecrets file, each
394 user can login to the SQL database with a different username and
395 password, you can utitilize the security model of the SQL database as
396 well. Also, each username here can point to a different configuration
397 directory where you could store user-specific configuration info. Then
398 you could link each username to one-to-many agents.
399 (The web demo works using a trivial version of this.)
401 Yes, queue processing or the equivalent via checkpoint fields on various
402 talbes (which you pick up via a pretty simple SELECT) would be really
405 default (and ordering) state/county/country config file
407 cust_main_county table to provide a preferred ordering, so the most common
408 entries would be at the top of the selection box. automatically, based on
411 hmm... maybe svc_acct__shell should check off the legal shells list if
412 applicable? yeah... cool.
414 payinfo field should me much larger than 16
417 [Mon Apr 12 20:31:21 1999] [error] [Mon Apr 12 20:31:21 1999] null: Error closing true: Broken pipe at /usr/local/lib/site_perl/FS/cust_main.pm line 615.
419 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
420 (view/cust_pkg and view/svc_*)
422 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
423 (all the actual date handling uses UNIX timestamps and is fine)
425 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
428 one-time/per-customer/? changes in rates and descriptions ('remembered
429 invoices'): implement by creating a new package on the fly... but it isn't
430 associated with any agent types so it won't show up for other customers to buy.
431 (but also... make sure they go away when the customer does! - need this? :
432 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
433 with custnum and partpkg (like type_pkgs)
434 (what happens if you hit "custom pricing" but the pricing is already custom?)
436 Lay out any remaining ugly forms better.
438 remove "records identical" warning? gets in the way of more important stuff.
439 or fix logic which tries to update identical records??
440 1.2 should be quiet enough that the error log is useful, hopefully.
442 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
443 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
444 (22 characters!) It seems that stuff over the limit is silently ignored,
445 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
446 stock Postgres. see rfc2138 for what's affected
447 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
448 (mysql has a 64 character max column length. others?)
450 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
451 (when sending mail in cust_main.pm::bill or svc_domain.pm)
453 look at DBIx::Recordset! (and Tie::DBI, and...)
455 undefined conf/lpr gives this uninfomative error:
456 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
458 l5/site_perl/FS/cust_main.pm line 629.
459 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
461 l5/site_perl/FS/cust_main.pm line 631.
462 So give a meaningful error!
464 password and slipip stuff in svc_acct.pm store need to be split into two fields or something, so the silliness in svc_acct.pm and svc_acct.export with looking at the data to decide what to do with it can be fixed
466 i10n: Apache::Language
468 Apache::Session? Other useful Apache::* ?
470 email invoices are only sent for the BILL payby. If setup, should statements
471 (since they're not invoices) be sent for COMP and CARD as well?
473 $cgi->keywords is causing the (hard to trace) error:
474 Use of uninitialized value at (eval 5) line 5
476 edit/cust_main.cgi gives an uninformative error message:
477 > Can't call method "agentnum" without a package or object reference at
478 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
479 if there are no agents.
481 (is this missing on any web screens? (easy with $cust_svc->label)
482 Add the ability for services to filter information up to the package level
483 for web screens, so you can select a particlar package based
484 on username or domain name, etc.
486 Allow a cancelled/suspended/active status from packages to bubble up to
487 the customer lists. Put active, then suspended, then cancelled accounts.
488 Similar ordering on the package listing inside a single customer.
490 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
491 the web interface in general needs to be redone in a more abstract way.
493 false laziness: some of search/svc_acct_sm.cgi was copied to search/svc_domain.cgi. but web interface in general needs to be rewritten in a mucho cleaner way.
495 Portability: in FS::Record, $sth->execute does not return a number of rows for all DBD's. see man DBI
497 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
499 add a select method to FS::Record?
501 one-time/per-customer/? changes in rates and descriptions ('remembered
502 invoices'): implement by creating a new package on the fly... but it isn't
503 associated with any agent types so it won't show up for other customers to buy.
504 (but also... make sure they go away when the customer does! - need this? :
505 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
506 with custnum and partpkg (like type_pkgs)
507 (what happens if you hit "custom pricing" but the pricing is already custom?)
509 You can't delete the stuff under administration yet. Add this,
510 _including_ making sure the thing you are deleting is not in use!
512 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
514 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
515 loading of configuration. (pry need same idea, but will run immediately if
516 context allows). Looks like error is masked by 'use FS::cust_svc' which in
517 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
520 Allow a cancelled/suspended/active status from packages to bubble up to
521 the customer lists. Put active, then suspended, then cancelled accounts.
522 Similar ordering on the package listing inside a single customer.
524 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
527 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
529 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
531 .us domains and others!
532 site_perl/svc_domain.cgi (hmm... or maybe should have a button? or maybe svc_domain.pm should handle this) should set $whois_hack for non-internic domains, so you can add them...
534 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
535 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
537 (test cust_main.pm with cybercash v2 and v3, especially with the callback
538 stuff AND with mod_perl w/cybercash v2 kludge in package main)
539 (callback stuff should be eliminated by now)
541 bah, table/itable/*table in FS::CGI is silly.
543 doc Apache::AuthDBI as well
545 Provide sample httpd.conf files.
547 hey look: Tie::DBI! Check that out. Override its commit with something that
548 does perl-side caching for ? a performance improvement and as an emulation
549 layer to plug in f.ex mysql's atomic transactions
551 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
552 Fix it anyway unless we migrate to Tie::DBI.
556 cust_bill.pm uses '==' comparison on dates because they're currently ints
558 config file for allowed card types
560 write instructions for adding new services w/svc_Common.pm. Get rid of all
561 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
564 test and document libapache-dbi-logger (woo!)
566 radius logfile parsing and perl expression check.
568 Fix in cust_bill BUGS:
569 There is an off-by-one error in print_text which causes a visual error (Page 1
570 of 2 printed on some single-page invoices).
572 fields should be a method against a FS::Record or derived object, as well as
573 being something you can call as FS::Record::fields('tablename'). Might
574 even be able to handle both in the same routine (that would be neato).
576 Immediate removal of incorrectly entered check payments (can't take too
577 long to do this, or accounting is fubared).
579 Add code to move from one service to another (POP to SLIP/PPP, etc.).
580 This _should_ be possible by working off the rules in part_svc rather than
581 hardcoding anything in. The rules in part_svc may need some elaboration,
584 Use ut_ FS::Record methods in all derived classes (possibly some from dbdef?... eventually all from dbdef??? - but then `dbdef-create' would be impossible as there would be metadata we couldn't ask the backend for. hmm.)
586 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
587 Expand the HylaFAX interface (also possibly generalize for other fax
588 softwar ie .comfaxe); allow things like arbitrary faxes of sales
589 literature, specific troubleshooting documents and so on. Maybe even
590 allow users to do this (though that might not belong in Freeside).
592 misc/process/sendconfig.cgi
593 Configure fax recipients via a separate box rather than using the finger
594 name or first+last from cust_main.
596 move all phone number logic out of Freeside - let HylaFAX or whatever
599 soundex searches for customer name and company? where are free soundex tools? (standard Text::Soundex duh) - I could have sworn I saw Text::Soundex on CPAN?!
601 should be able to link on some field in email alias (right now you can link
602 on username or domain with a fallback to svcnum)
604 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
606 deleting an svc_domain should delete all associated svc_acct_sm records.
607 same with a svc_acct.
609 periodic password encrypter
611 Automated, configurable notification, suspension and cancellation of
616 Allow for a future setup date on accounts.
618 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
621 edit (not just import, export and allow default/fixed) arbitrary radius stuff
623 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
625 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
627 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
629 what else (besides l10n) for i18n? (money!)
631 audit htdocs/* for things that should be libraried and things that should be
632 new methods on the objects (need to do this before implementing a new UI)
633 all the big things are done
635 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
636 Decide based on whether or not the "error" should show up in logs.
638 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
639 for HTML creation. Maybe Embperl or something along those lines. ?
641 When running bin/bill, Fix this (Annoying but harmless):
642 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
643 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
644 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
646 all cgi (but internal to the isp) places where package names are listed should also have
647 comment (like agent_type)
649 clean up $recref and other silliness and use -> calls where possible, or
650 one other alternative. clean up everything else.
651 should FS::Record use Tie::Hash? That would be very clean, but where do we
652 store the other information? Maybe you could ask any FS::Record object for a
655 change all file access from regular open(FILE,) stuff to OO, because of
656 problems scoping and passing filehandles like that.
658 the web interface should create a new object and use it instead of a blank
659 form for new records. the create method of svc_ objects should set defaults
662 sub check in man FS::table_name should be rewriteen. Get rid of $recref
663 stuff. Make sure all fields that refer to other database are checked.
665 Integration with signup disks (are there any free ones? Netscape?).
667 One-button cancel (+refund) for lusers who can't get online.
669 Keep information on virtual web servers (hostname, IP, host machine,
670 directory, etc.) and export this information for importation into the ISPs
673 Remove requirement that the first mail alias be the catchall? Still make
674 sure only one catchall per domain is defined in any case, of course.
676 Ability to move cust_pkg records from one customer to another? (proably
677 will need to cancel the old and create a new like when we move services
680 Auto-increment expired cards one year, and try again?
682 More non-US stuff - zip codes, country codes, foreign currencies, etc.
684 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
686 Nicer set of integrated reporting possibilities, like weekly sales totals
687 by customer, package, agent, referral, etc., aging reports sorted by lots
688 of different things, and so on.
690 Client/server setup for users to modify their own passwords, shells, etc,
691 via passwd or secure web interface (prelminary passwd/chfn/chsh
692 replacement done). Complicated by the fact that we don't want to allow
693 incoming connections to the machine running Freeside, so we probably need
694 to have a daemon on each external shell or web machine that is contacted
695 by the Freeside machine. Be very very careful for both traditional
696 security issues and DoS problems.
698 An extension of the above to allow users to modify selected parts of their
699 own information, order and cancel services. A web interface for new
702 Expand domain name stuff to house all domain information. Export
703 named.boot/named.conf (primary and secondary) and named.{domain} files.
704 Add more registries (not just InterNIC's com org net edu)
706 Nice postscript paper invoices, rather than current ASCII invoices.
708 think about race-condititions in FS::Record and derived ->check ->insert
709 and so on, uid and username checks in svc_acct, etc.
711 Move to rsync over ssh file exportation rather than scp.
713 check 'n fix the proactive password checker. (cracklib?)
715 refunds of "BILL" payments: generate pseudo-check.
717 write batch senders and batch parsers for the different credit card processors
719 More CC processors/methods.
721 you should be able to fiddle the setup date in cust_pkg. (at least initially)
723 delete options in administration section
725 write a generic batch senders and batch parsers.
727 need a way to override svc_acct export on a per-machine basis; just use config files based on machine name i suppose; document that. (no, import desync_hosts
728 type stuff from cerkit)
730 add a table with column of export services (passwd, shadow, master.passwd, .qmail file update, dns update, etc.) and rows machine groups and whether or not to export that (and any necessary parameters). wasn't matt (vunderkid, not matt@michweb) working on this? find him? each machine goes in a group of its own as well as a group based on function. add a table with only svcpart and machine group. now, when you import from each machine, it can get its own accounts with one svcpart and universal accounts with another svcpart. (though that does make the username duplicate checking more interesting)
732 you should be able to get column types as a method against an FS::Record object
733 as well as dbdef->table($table)->column($column)->type
735 move to perl module for fuzzy and soundex searching.
737 package view needs to list extraneous services; we need to prevent the
738 creation of them so this never happens (and mark it as such in the source)
739 (the creation problem should be fixed - though they will still happen if people
740 fsck around in the data manually, so list them anyway)
742 add attribute dictionary to fs-setup as a menu, plus analyze users file to
745 Check for and report on duplicate billing accounts (cust_main, though many
746 will have a need for these so probably don't disable them outright.)
748 create a ->warn as well as a ->check method for all FS::table classes?
751 something to automate making a release and updating the web demo
753 export a debian-style (also redhat and?) /etc/group file aswell!
755 svc_acct_sm.import qmail import should pull in recipientmap people too.
757 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
758 should fork and do them in a child.
760 i18n/l10n: take ALL messages and catalog them in english.txt or in database or something, so we can eventually go int'l. int'l currency support would be a help aswell.
762 get some of { city, county, state, zip } from the missing bits if
763 possible (where can i get the data to do this? usps.gov?)
765 additional interfaces (perltk? java?)
767 Put the GPL notice in all files.
769 integrate w/IDEA's signup server
771 $cust_bill->owed database field to be eliminated, replaced by a method call
772 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
773 same for cust_credit->credited
775 Export quota information.
777 move all configuration to a central place. maybe in blob's in the
778 database. maybe even things like the code to execute when a username is
779 changed can be in there, so less of the distributed scripts change between
782 Implement setup and recurring fees as Safe perl expressions rather than
783 numbers, to allow for variable-rate services. Backwards compatibility is
784 obtained because { 43 } in perl is still 43. :) Define API to pass
785 starting and ending dates and any other necessary data to expression
786 (fees are currently evaluated as Safe expressions but more work needs to
787 be done to define an opmask for various needs, write examples
788 (usage-based billing, etc.) and so on).
790 Add the ability to modify the next billing date in cust_pkg, and take
791 appropriate action. This will allow the implementation of pro-rate/1st of
792 the month billing as well as the ability to manually fiddle with
793 anniversary dates in cust_pkg, so you can sync a customer's anniversary
794 date even if you're using anniversary billing (manually or automatically).
795 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
796 charges - anything more complicated should figure it out itself given
797 starting and ending dates [document that!])
799 Daily Radius log parsing into database; other logfile formats?
801 Callbacks to enforce hourly limits on accounts (suspend until the end of
802 the billing period?), for those who limit customers rather than tack on
805 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
806 example) need to charge tax on equipment but not service (separate flags
807 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
808 recur_tax and recur_notax fees, and possibly something more flexible if
811 Allow for a variable number of invoices for customers who need multiple
814 Add a mail alias service with table svc_acct (not domain mail aliasing
815 which is domain with svc_acct_sm)
817 (bring back from fsold) Change customer comment field from its current kludge to something more
820 Better work orders with more information. Should eventually open a ticket
821 when we have such a thing.
823 edit/process/svc_wo.cgi
824 Call tracking and trouble tickets.
826 More accoutability for complimentary accounts: approval, expiration, term
827 (no more than x months in advance) and notification.
828 Flag particular users (or all users, for that matter) as having their
829 passwords hidden and/or locked from users of Freeside (maybe need Freeside
830 security levels first?).
832 Better Freeside-level configurable access, for those ISP's who have
833 employees they can't trust. Right now you're "stuck" with setting up
834 .htaccess stuff yourself. This should really just be integrated.
836 configuration/setup should get web interface
838 /usr/local/etc/freeside should be configurable
840 (probably as part of some automated installation process?)
842 This requires some serious magic in FS::Record:
843 ok, if date_type in fs-setup is to be something besides int,
844 now we need to create wrappers
845 for them so they behave identically across RDBMS's, ie date pops out as as
846 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
847 is a string not a hashref for backwards compatibility?) and so on. (remember
848 to treat '0' as Not a Date instead of 1/1/70.
850 Add Freeside-level transactions for RDBMS's which don't support
851 transcations? (Currently we assume a minimal RDBMS which has no rollback,
852 transactions or atomic updates). Or just require a RDBMS that supports
853 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
854 interface had this kludge on top of it but is a technical dead-end in most
855 other ways, unless it can gain an SQL parser and DBD interface.
857 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
858 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
859 an FS::Record have something to do with a tied hash? But we don't want
860 performance to go gaga... maybe something with commit to help out here?
862 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
864 Better automated comparison of our CC records with processors (CyberCash,
865 at least, has not always had 100% accuracy, though recent versions are
868 Expect or other pty based login check, where we actually connect to a
869 terminal server or shell machine and test logging in as the user (if we
870 are keeping a cleartext password for that user) (This is something tech
871 support often needs for new customers)
873 Use cust_main table for pre-sales tracking as well?
875 Automatic commision report and check generation via freq and prog (to
876 become a Safe perl expression) fields in agent table, and possibly others.
878 Database and add a mailed-out date and method for disk/CD mailing, so a
879 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
882 Inventory tracking for physical items such as routers (for sale or
883 lease... probably doesn't make a difference in the ordering... but if you
884 cancel a router lease the inventory should come back. hmm.)
886 -- Matt's wishlist ---
888 From matt@michweb.net Fri Feb 20 16:39:53 1998
889 Date: Thu, 19 Feb 1998 23:20:11 -0500
890 From: Matt Simerson <matt@michweb.net>
891 Reply-To: quadran-developer@netgoth.com
892 To: quadran-developer@netgoth.com
893 Subject: Re: Welcome to quadran-developer
895 >Whats it based on and what is it supposed to do? I'm interested, but
896 >unfortunatly, I don't have that much time to help on the project (I'm busily
897 >working on one of my own based around MySQL and Qt right now -- don't know
898 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
899 >it is designed around our system)...
901 That's what I set out to find, but didn't find anything on the web site.
902 I'm looking for something that will do the following:
904 Single point of entry for users on a secure system:
905 Creates account on user (public) systems
906 update /etc/passwd/master.passwd file
907 update radius database (if necessary)
908 Set up up disk quotas (although I hacked adduser to do this)
909 Option for adding user to a mailing list(s)
910 Export of new user info to customizable report (for automated entry
912 accounting software, etc...)
915 Export credit card info for batch processing and have hooks built
916 in for other forms of electronic processing.
917 Batch-Payment (apply payments from formatted text file).
918 Customizable reports for manual entry/importing into Accounting
920 Email or laser print invoices
921 Sanity checks credit card numbers before processing (code available)
923 Simple method for disabling an account.
924 Arbitrary Expiration Dates (on a given day, in x days)
926 Changing password to '*'
927 Virtual customers disabling dns, http server, log processing, etc..
929 Billing for different account types:
930 Dialup monthly flat rate. Prorates for partial months.
931 Dialup monthly flat rate for x hours + hourly usage.
934 Virtual Web accounts - w/multiple mailboxes
936 Disk space used over quota.
937 Tech support minimum + hourly charges
938 Other for misc stuff (modem, RAM, etc...)
940 Per user definable RADIUS attributes (ties in with above)
943 IP filters (for dialup email only)
945 Keep logs of modem usage generated daily from radius accounting logs stored
946 on multiple radius servers.
948 Keep logs of disk usage generated from quota.
950 Method of adding virtual domains to your system:
951 Automatically grabs an IP address from a preassigned pool.
952 Creates a domain.com database file from database fields
953 Updates /etc/named.conf or /etc/named.boot and reloads named.
954 Add's virtual.com to /etc/sendmail.cw or qmail control files.
955 Edits your web servers httpd.conf file and restarts http server.
956 An optional section for adding vif's can be added if the users OS
957 supports adding them on the fly. Otherwise it's up to the end
958 user. Make a hook that can run a custom script that the user
959 tweaks for his system.
960 Update or create the config file your web stats analyzer needs. I've
961 done this for analog (free) and http-analyze. Probably
962 should only officially support analog and let users hack
963 it to their hearts desire.
964 I've already written scripts that do most of the virtual web stuff on my
965 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
966 as long as all the info was stored in the database (username, domain name,
967 and ip pool) this could easily just be run as an external script that the
968 user tweaks to match his system.
970 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
971 Payroll, Tax stuff, and most everything else we could need. It's already
972 set up for the type of checks we have, etc, etc... I just need something to
973 do the billing part. I can import/export sales and payments directly once
974 the billing part is done. You can't write accounting software as good as