1 $Id: TODO,v 1.46 2000-06-27 12:15:50 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 zip code i18n is not very good :( but at least US, CA, HU, ?
11 ut_phonen doesn't check data length. several
12 orthogonal cleanup projects here. *sigh*
14 update the cybercash links in config.html and in the homepage. add more explicit support for other payment types. etc.
16 From "Tim Jung" <tjung@igateway.net>
18 Automatic CC Decline Notices via email
19 Block Time billing for prepaid internet cards (400 hours or whatever block
21 Trouble Ticket System with simple search function for Knowledge Base feature
23 Credit Card System support for Red Hat's CCVS, and other Linux credit card
25 Contact Manager/Lead Tracking
27 Cisco NetFlow Account for IP traffic billing
29 Roaming per minute billing based on Radius Proxy support or number they
30 dialed into from Radius logs (800# etc)
31 Support for OpenSRS Domain Registration
32 Support for TUCOWS signup CDs
35 dbdef-create for postgres
37 pro-rating, fiddling dates
39 It looks like svc_acct.import doesn't deal well with comments and
40 multi-attribute lines.
42 ivan@rootwood:~/freeside_current$ rgrep -r domuid * | cut -d: -f1 | sort |
47 bin/svc_acct_sm.export
48 bin/svc_acct_sm.import
49 htdocs/docs/man/svc_acct_sm.txt
50 htdocs/docs/schema.html
51 htdocs/edit/CVS/Base/part_svc.cgi
52 htdocs/edit/part_svc.cgi
53 htdocs/edit/process/svc_acct_sm.cgi
54 htdocs/edit/svc_acct_sm.cgi
55 htdocs/search/svc_acct_sm.cgi
56 htdocs/view/svc_acct_sm.cgi
57 site_perl/svc_acct_sm.pm
59 rootwood:COMPLETEHOST/TODO
61 Currently, you set a value in the %FS::UID::callback hash with a coderef
62 of the code you want to execute, but this was bad design and will shortly
63 be changed to a subroutine to which you pass your coderef to register it.
65 This is not a bug, it is how the system is currently designed. After
66 defining a new package, you need to specifically allow agent types to
67 purchase packages. You can do this from the edit screen of the new agent
70 It wouldn't be a bad idea to add a configuration value that makes new
71 packages available for all currently existing agent types automatically.
73 On Fri, Apr 07, 2000 at 10:50:35AM -0500, David Morton wrote:
74 > For some reason, the type_pkgs table didn't get updated when I tried to
75 > create a domain service and package... insert into type_pkgs values
76 > (4,1); fixed it up so that I could actually order the package.
79 From: Chuck Cochems <zaphod@tdl.com>
81 1) automated generating of late notices. So far the only way I know to
82 generate one is to re-invoice manually.
84 2) smart credit card rejection handling. It should e-mail a note at
85 least, explainig that it did't go through, and why.
87 3)coment field in the main customer record.
89 4) streamlined payment entry feature. the current scheme has it fairly
92 5) queries to show al customers who owe money,and such stuff as that.
95 credits aren't counted against past invoices? hmm. something needs to be
96 done to "apply payment" genericly. and zero out invoices etc.
98 more email which should make it into a more organized TODO list:
100 I would also love to see Freeside support bandwidth billing by reading the
101 Cisco NetFlow Accounting data so we and other ISP's could automatically bill
102 co-located servers and even potentially other virtually hosted sites like
103 MUD, Palace Chat, IRC Chat, etc based on the bandwidth they use or average
104 sustained rates or whatever. I'm not much of a programmer so I don't know
105 what all this entails but I did download a NetFlow client agent/whatever for
108 It would also be nice to see Freeside be able to read Apache log files and
109 bill customers for web traffic that way as an option also. Plus an option to
110 bill for excessive disk usage without having to use quotas if you didn't
111 want to, would be a nice feature as well. So you could monitor with a script
112 or something to see how much disk space a user was using then get some
113 average and charge a certain amount for anything above some preset limit for
114 that account type. I might be able to hack something like this up, but I'm
115 not 100% sure where to start or if there is something out there that could
118 Do you think that you will ever support the HKS CCVS (Hell's Kitchen
119 Software Credit Card Verification Software) since Red Hat bought them out
120 and is going to be including that for credit card processing when you buy
121 the professional version? What about possibly supporting the OpenCCVS which
122 is a GNU/GPL version of a credit card program? I haven't had time to comb
123 through the Freeside code to see how hard it would be to add support for
124 these as externally called programs.
126 Also any thoughts on help desk, and knowledge base stuff? Any thoughts on
127 this stuff, and how possible and what kinds of work or time frame would be
132 Internet Gateway Inc.
137 CVS via SSH (Score:1)
138 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
139 (User Info) http://www.fxp.org/~jedgar
140 The links above are your best bet for basic cvs server configuration. Once you have a pserver set up, you
141 may consider using cvs via ssh. All you need to do is the following:
143 1) Have ssh and sshd set up on the client and server machines
144 2) Set CVSROOT="joe@example.com:/home/ncvs"
145 3) Set CVS_RSH="/usr/local/bin/ssh"
147 (Obviously, insert the proper host/paths above)
149 You can also set up cvs/ssh to not need a password every time (similiar to an initial 'cvs login'):
151 1) run ssh-keygen on client machine using no passphrase.
152 2) copy/add ~/.ssh/identity.pub on the client to ~/.ssh/authorized_keys on the server
153 (man ssh for more details)
155 The main reason I mentio
156 CVS via SSH (Score:1)
157 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
158 (User Info) http://www.fxp.org/~jedgar
161 There's no way to do this currently, though it would be pretty
162 straightforward to modify the source - specifically, the _collect_
163 subroutine in FS::cust_main.
165 On Mon, Dec 13, 1999 at 04:05:32PM -0700, Jeff Garner wrote:
166 > Freeside will e-mail my users when they are billed if they are setup as
169 > When setup by credit card it does not e-mail them. Is there a way to
170 > turn on e-mail invoices for those who are billed via credit card? Kind
171 > of like a recipt of billing....
174 doc: http://www.softagency.co.jp/mysql/qmail.en.html
176 sql1992.txt standard is 18 character column names. shoot for that, not just
177 32 (postgresql default)
179 Also note that (AFAIK) Freeside won't display any package that has more
180 than one service on the "Add Customer" page. The reason for this is
181 because there's no way to dynamically alter the displayed html form
182 based on which package is selected. One possible solution would be to
183 make an additional page that's used in the signup process that would
184 display the form for each package, like a MS-style "Wizard". The first
185 page lets you select the package, then the second page has the custom
186 form with fields for each service in that package and a save button. Of
187 course, that would require a little perl work.
190 Scott Cruzen <sic@boernenet.com>
193 Your suggested script with back up /usr/local/etc/freeside, but will miss
194 any database not named `freeside'. Both of our scripts are specific to
195 MySQL. If you're interested in contributing to Freeside, maybe you could
196 work on a script which: reads the mapsecrets configuration file and then
197 each secrets file to find out what specific database engine(s) (MySQL,
198 PostgreSQL, etc.) and database(s) need to be backed up, then does so,
199 serializing backups of the same engine, i.e. stop mysql, do all the mysql
200 backups, start mysql, stop postgresql, do all the postgresql backups,
201 start postgresql, etc.
204 > mysqldump -t freeside > fs-backup.sql
206 > tar -Pzcvf fs-backup-`date +%y%m%d%H%M%S`.tgz fs-backup.sql /usr/local/etc/freeside/
209 I chose to use counters in the filesystem because there is no standard way
210 to get the value of an auto-incrementing keyfield which is common across
211 all databases (as seen through DBI/DBD).
213 It certainly wouldn't be a bad idea to use the database-specific methods,
216 htdocs/edit/svc_acct.cgi:
217 (Does the `*HIDDEN*' show up when you are adding a new account, and
218 specify the password, then receive an error and are returned to the form?)
221 Thought some of you might be interested in this:
223 <ftp://ftp.minivend.com/pub> has CyberCash compatibility modules for
224 Paymentnet <http://www.paymentnet.com> and Authorizenet
225 <http://www.authorizenet.com> which should allow you process transactions
226 using those services as well as CyberCash.
228 The files are named CCLib.pm.paymentnet and CCLib.pm_authorizenet,
229 respectively, and are installed by renaming to CCLib.pm and moving to your
230 site_perl directory. Otherwise, follow the directions for Cybercash v2 in
231 htdocs/docs/config.html
234 fs_passwd/ is a client-server replacement for the `passwd', `chfn' and
235 `chsh' commands that updates the Freeside database. (so for that to be
236 useful, you'd have to be exporting that data periodically)
238 fs_radlog/ is a client-server RADIUS log parser that stuffs the data into
239 SQL. It isn't finished, and probably won't be unless someone who I can't
240 convince to use one of the RADIUS daemons that logs to SQL directly pays
241 me money or something.
243 fs_signup/ is a client-server signup server. i'm just finishing it up
244 now; probably isn't on your machine yet.
247 http://www.sisd.com/freeside/list-archive/msg00812.html
249 package definitions should be implicit allow wrt agent types, not implicit deny
250 (with the old behavior possible via a config file)
252 > So is there anyway it could be setup to allow you to select a "primary
253 > service" from each package? This service would be the one you were prompted
254 > for. Could the signup server then be expanded to allow users to go into
255 > their package and "turn-on" the remaining non-primary services(using the
258 take the GPL'ed whois proxy stuff at www.geektools.com and turn it into
259 intelligence for Net::Whois.
261 A web version of the fs_passwd stuff would be nifty.
263 If you have Cistron authenticating directly from MySQL, you can replicate
264 in real-time instead of exporting periodically. See
265 <http://www.mysql.com/Manual_chapter/manual_Common_problems.html#Replication>.
268 <http://www.sisd.com/freeside/list-archive/msg00541.html> (was 546), and
270 and http://www.sisd.com/freeside/list-archive/msg00421.html (was 423)
272 > > 5: Is there anyway to get freeside to send a sysadmin a warning when a
273 > > credit card has expired?
274 No, but there should be.
276 Put this in the doc (quoting Mark Wells <mark@pc-intouch.com>):
277 >Of course, thanks to the sheer coolness of SQL and MyODBC, you can do
278 >whatever reports you want in basically whatever application you want.
279 >There's no need for Freeside itself to do any reports at all.
281 middle names and titles
283 On Wed, Jul 07, 1999 at 01:11:40PM -0400, Frank Nazario wrote:
284 > Playing and entering information to Freeside i encountered the following
287 > View Customers by Agent
289 > View Pending Invoices
292 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
293 Not to say that it shouldn't be a configurable option.
295 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
296 (at least until the idea of a default domain goes away)
298 FS::Record::qsearch does an eval every loop iteration (which is itself not
299 guaranteed to work across all DBD's and should be fixed). This has got to be
300 slow. Fix it. (I think recent Perls might have a way to accept a variable
301 there, no eval needed?)
303 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
304 `shells' configuration file before importing, and removed them afterwords?
305 (even better if svc_acct.import did that automatically - it could just
306 munge and restore @FS::svc_acct::shells... hmm.)
308 > BTW, Ivan, I am trying to verify in an additional database table that a
309 > particular user doesn't exist. This database is used to store email aliases a$
310 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
311 > with the idea of just writing the aliases to an email only svc_acct that
312 > doesn't write to the password file, but that isn't really how I want to do it.
314 Actually, I think that's a pretty good way to do it. Cerkit contributed
315 support a little while back for svc_acct.pm and svc_acct.export for
316 multiple export targets. It needs to be cleaned up and documented, which
317 I'll try to get to soon. For this to work correctly, the svc_acct_sm
318 table should go away, along with the concept of a "default" domain.
320 default setting for new packages should allow all agents to purchase them...
321 with a config file for the old behaviour
323 fix or replace Term::Query (Quiz::Question doesn't do what i need)
325 Check config file reading stuff from CPAN
327 Authorizenet module from CPAN!
329 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
332 I'm hoping Freeside can support arbitrailly complex pricing plans
333 because of a simple concept: all prices are perl expressions. So if
334 you use `19.95' for example, perl evalates that to be `19.95'. But if
335 you need to do a complex pricing scheme, you just need to write an
336 appropriate perl expression, which will most likely pull data from the
337 database to return pricing. Some things will already log to SQL; for
338 example most RADIUS servers can or have a patch available. Getting
339 Freeside to bill based on any sort of data then becomes a matter of
340 importing the data into the database.
342 There are some issues involved with pro-rating, partial month charges,
343 that sort of thing. Expressions will need a standard way to have the
344 applicable time/data ranges passed to them. Also the expressions are
345 currently running under the Safe perl module, and the opmask might not
346 be right in all situations. I'll try to spend some time working on
347 this if you are using it.
349 > 2. can customers view their bills on-line.
351 Not yet; it needs to be proxied from Freeside to a customer web server in
352 a secure way using something not completely unlike the fs_passwd,
353 fs_passwdd, fs_passwd_server trio.
356 > Lastly, if someone over pays on an invoice, the credit part does not flow
357 > over to other invoices..
359 The total balance flows over correctly, but individual payments don't.
360 The code you're looking for is in FS::cust_pay::insert
362 The question of what to do with overpayments that don't have another
363 invoice to flow into (yet.. or possibly not) is still an open one. The
364 legacy system Freeside replaced long ago had a separate place for this
365 (payments waiting for an invoice) for each customer, and it gave our
369 option to relax username uniqueness in favor of username+domain or mail/shell
370 vs. radius to ease import for isp's with namespace problems or who buy others.
372 do i have to store anything for radius realms besides regular radius attributes
373 (which are handled fine now)?
375 warn or complain or something when invoice_from is empty (and we use it)
377 Right now Freeside uses the `freq' field of a package definition as a
378 number of months. The specific section of code you're looking for is in
381 #change this bit to use Date::Manip?
382 #$sdate=$cust_pkg->bill || time;
383 #$sdate=$cust_pkg->bill || $time;
384 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
385 my ($sec,$min,$hour,$mday,$mon,$year) =
386 (localtime($sdate) )[0,1,2,3,4,5];
387 $mon += $part_pkg->getfield('freq');
388 until ( $mon < 12 ) { $mon -= 12; $year++; }
389 $cust_pkg->setfield('bill',
390 timelocal($sec,$min,$hour,$mday,$mon,$year));
391 $cust_pkg_mod_flag = 1;
393 ..and when I went poking for this, looks like it tells us just what needs
394 to be done! Hehehe...
396 Date::Manip can handle cool things like "+ 1 month" (actually the current
397 case of /^(\d+)$/ would have to be added as a special case of "+ $1
398 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
401 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
402 > I can't quite seem to figure out how this exporting works. From what I
403 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
404 > /etc/shadow, etc. files. Is this only for initial setups with the
405 > export hooks being in the pm's?
407 You can use both, or just one method. The configuration files control
408 this. One of the things in the TODO is to take out the last few things
409 that aren't customizable wrt this and put them in config files.
411 http://www.daemonnews.org/199905/user-mgmt.html
413 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
414 submitted upstream!), or remove requirement from bin/svc_acct.import and
415 bin/svc_acct_sm.import and take it out of the install instructions.
417 use this cool link to explain the Freeside API
418 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
420 Multiple tax rates by geographic region (county, state, and county) are
421 supported; just choose View/Edit tax rates from the main menu.
423 Multiple tax rates by package are not (yet) supported.
425 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
426 > How would you handle something like multiple tax rates and multiple
427 > states? For example in Connecticut, they just changed computer and/or
428 > data processing services to 3% (whatever that is), and everything else
432 > Second, when trying to add a new user I get two types of errors; first one
433 > is when I place an e-mail address and select the "submit," Freeside
434 > complains with "Error: Unknown local account (specified literally)"
436 You probably put a (local) email address in for email invoices. Freeside
437 stores these as references to the database records, so (for example) they
438 follow username changes.
440 I'm guessing you put in the email address that you were creating, and got
441 that error because it didn't exist yet. Sounds like a buglet to me. I'll
442 try to fix that soon; in the meantime you can add the invoicing email
445 (workaround for postgres before 6.5) (unlikely to ever be implemented)
446 In the mean-time, this could probably be fixed with the reverse of
447 the kludge in FS::Record::new. This removes `$' and `,' from money fields
448 coming out of the database. Something which fixed up the data so Postgres
449 was happy with it could go in FS::Record::_quote, for data going into the
452 our data display problem might be a Freeside problem wrt not using
453 Oracle-compatible DBI syntax (fixed using the return value from $sth->execute
454 as a number of rows - something else?).
456 hooks for arbitrary commands out of configuration files
457 svc_acct.pm svc_acct_sm.pm etc.
459 Add this to a FAQ, along with doing it for middle names:
462 > What I'm finding difficult is how to easily
463 > customize fields. For example, I am trying to add a "middle name" field
464 > to the Customer Edit, view, etc. If I'm going about it right, it appears
465 > I have to edit the cust_main.cgi under edit and edit/process and the
466 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
467 > some light on the best way of doing this.
469 You have the basic idea. To implement that completely, I would:
470 - Add the new field to bin/fs-setup for new users
471 - Document the field in htdocs/docs/schema.html
472 - Document the change in a new file, htdocs/docs/upgrade4.html
473 * Run bin/dbdef-create
474 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
476 For bonus points, I'd grep around for the various bits which use "$first
477 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
478 , like search/cust_main.cgi
480 document security model:
481 Don't forget about Apache usernames - since, via the mapsecrets file, each
482 user can login to the SQL database with a different username and
483 password, you can utitilize the security model of the SQL database as
484 well. Also, each username here can point to a different configuration
485 directory where you could store user-specific configuration info. Then
486 you could link each username to one-to-many agents.
487 (The web demo works using a trivial version of this.)
489 Yes, queue processing or the equivalent via checkpoint fields on various
490 talbes (which you pick up via a pretty simple SELECT) would be really
493 default (and ordering) state/county/country config file
495 cust_main_county table to provide a preferred ordering, so the most common
496 entries would be at the top of the selection box. automatically, based on
499 hmm... maybe svc_acct__shell should check off the legal shells list if
500 applicable? yeah... cool.
502 payinfo field should me much larger than 16
505 [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.
507 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
508 (view/cust_pkg and view/svc_*)
510 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
511 (all the actual date handling uses UNIX timestamps and is fine)
513 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
516 one-time/per-customer/? changes in rates and descriptions ('remembered
517 invoices'): implement by creating a new package on the fly... but it isn't
518 associated with any agent types so it won't show up for other customers to buy.
519 (but also... make sure they go away when the customer does! - need this? :
520 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
521 with custnum and partpkg (like type_pkgs)
522 (what happens if you hit "custom pricing" but the pricing is already custom?)
524 Lay out any remaining ugly forms better.
526 remove "records identical" warning? gets in the way of more important stuff.
527 or fix logic which tries to update identical records??
528 1.2 should be quiet enough that the error log is useful, hopefully.
530 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
531 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
532 (22 characters!) It seems that stuff over the limit is silently ignored,
533 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
534 stock Postgres. see rfc2138 for what's affected
535 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
536 (mysql has a 64 character max column length. others?)
538 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
539 (when sending mail in cust_main.pm::bill or svc_domain.pm)
541 look at DBIx::Recordset! (and Tie::DBI, and...)
543 undefined conf/lpr gives this uninfomative error:
544 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
546 l5/site_perl/FS/cust_main.pm line 629.
547 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
549 l5/site_perl/FS/cust_main.pm line 631.
550 So give a meaningful error!
552 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
554 i10n: Apache::Language
556 Apache::Session? Other useful Apache::* ?
558 email invoices are only sent for the BILL payby. If setup, should statements
559 (since they're not invoices) be sent for COMP and CARD as well?
561 $cgi->keywords is causing the (hard to trace) error:
562 Use of uninitialized value at (eval 5) line 5
564 edit/cust_main.cgi gives an uninformative error message:
565 > Can't call method "agentnum" without a package or object reference at
566 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
567 if there are no agents.
569 (is this missing on any web screens? (easy with $cust_svc->label)
570 Add the ability for services to filter information up to the package level
571 for web screens, so you can select a particlar package based
572 on username or domain name, etc.
574 Allow a cancelled/suspended/active status from packages to bubble up to
575 the customer lists. Put active, then suspended, then cancelled accounts.
576 Similar ordering on the package listing inside a single customer.
578 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
579 the web interface in general needs to be redone in a more abstract way.
581 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.
583 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
585 add a select method to FS::Record?
587 one-time/per-customer/? changes in rates and descriptions ('remembered
588 invoices'): implement by creating a new package on the fly... but it isn't
589 associated with any agent types so it won't show up for other customers to buy.
590 (but also... make sure they go away when the customer does! - need this? :
591 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
592 with custnum and partpkg (like type_pkgs)
593 (what happens if you hit "custom pricing" but the pricing is already custom?)
595 You can't delete the stuff under administration yet. Add this,
596 _including_ making sure the thing you are deleting is not in use!
598 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
600 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
601 loading of configuration. (pry need same idea, but will run immediately if
602 context allows). Looks like error is masked by 'use FS::cust_svc' which in
603 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
606 Allow a cancelled/suspended/active status from packages to bubble up to
607 the customer lists. Put active, then suspended, then cancelled accounts.
608 Similar ordering on the package listing inside a single customer.
610 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
613 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
615 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
617 .us domains and others!
618 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...
620 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
621 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
623 (test cust_main.pm with cybercash v2 and v3, especially with the callback
624 stuff AND with mod_perl w/cybercash v2 kludge in package main)
625 (callback stuff should be eliminated by now)
627 bah, table/itable/*table in FS::CGI is silly.
629 doc Apache::AuthDBI as well
631 Provide sample httpd.conf files.
633 hey look: Tie::DBI! Check that out. Override its commit with something that
634 does perl-side caching for ? a performance improvement and as an emulation
635 layer to plug in f.ex mysql's atomic transactions
637 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
638 Fix it anyway unless we migrate to Tie::DBI.
642 cust_bill.pm uses '==' comparison on dates because they're currently ints
644 config file for allowed card types
646 write instructions for adding new services w/svc_Common.pm. Get rid of all
647 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
650 test and document libapache-dbi-logger (woo!)
652 radius logfile parsing and perl expression check.
654 Fix in cust_bill BUGS:
655 There is an off-by-one error in print_text which causes a visual error (Page 1
656 of 2 printed on some single-page invoices).
658 fields should be a method against a FS::Record or derived object, as well as
659 being something you can call as FS::Record::fields('tablename'). Might
660 even be able to handle both in the same routine (that would be neato).
662 Immediate removal of incorrectly entered check payments (can't take too
663 long to do this, or accounting is fubared).
665 Add code to move from one service to another (POP to SLIP/PPP, etc.).
666 This _should_ be possible by working off the rules in part_svc rather than
667 hardcoding anything in. The rules in part_svc may need some elaboration,
670 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.)
672 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
673 Expand the HylaFAX interface (also possibly generalize for other fax
674 softwar ie .comfaxe); allow things like arbitrary faxes of sales
675 literature, specific troubleshooting documents and so on. Maybe even
676 allow users to do this (though that might not belong in Freeside).
678 misc/process/sendconfig.cgi
679 Configure fax recipients via a separate box rather than using the finger
680 name or first+last from cust_main.
682 move all phone number logic out of Freeside - let HylaFAX or whatever
685 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?!
687 should be able to link on some field in email alias (right now you can link
688 on username or domain with a fallback to svcnum)
690 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
692 deleting an svc_domain should delete all associated svc_acct_sm records.
693 same with a svc_acct.
695 periodic password encrypter
697 Automated, configurable notification, suspension and cancellation of
702 Allow for a future setup date on accounts.
704 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
707 edit (not just import, export and allow default/fixed) arbitrary radius stuff
709 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
711 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
713 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
715 what else (besides l10n) for i18n? (money!)
717 audit htdocs/* for things that should be libraried and things that should be
718 new methods on the objects (need to do this before implementing a new UI)
719 all the big things are done
721 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
722 Decide based on whether or not the "error" should show up in logs.
724 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
725 for HTML creation. Maybe Embperl or something along those lines. ?
727 When running bin/bill, Fix this (Annoying but harmless):
728 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
729 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
730 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
732 all cgi (but internal to the isp) places where package names are listed should also have
733 comment (like agent_type)
735 clean up $recref and other silliness and use -> calls where possible, or
736 one other alternative. clean up everything else.
737 should FS::Record use Tie::Hash? That would be very clean, but where do we
738 store the other information? Maybe you could ask any FS::Record object for a
741 change all file access from regular open(FILE,) stuff to OO, because of
742 problems scoping and passing filehandles like that.
744 the web interface should create a new object and use it instead of a blank
745 form for new records. the create method of svc_ objects should set defaults
748 sub check in man FS::table_name should be rewriteen. Get rid of $recref
749 stuff. Make sure all fields that refer to other database are checked.
751 Integration with signup disks (are there any free ones? Netscape?).
753 One-button cancel (+refund) for lusers who can't get online.
755 Keep information on virtual web servers (hostname, IP, host machine,
756 directory, etc.) and export this information for importation into the ISPs
759 Remove requirement that the first mail alias be the catchall? Still make
760 sure only one catchall per domain is defined in any case, of course.
762 Ability to move cust_pkg records from one customer to another? (proably
763 will need to cancel the old and create a new like when we move services
766 Auto-increment expired cards one year, and try again?
768 More non-US stuff - zip codes, country codes, foreign currencies, etc.
770 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
772 Nicer set of integrated reporting possibilities, like weekly sales totals
773 by customer, package, agent, referral, etc., aging reports sorted by lots
774 of different things, and so on.
776 Client/server setup for users to modify their own passwords, shells, etc,
777 via passwd or secure web interface (prelminary passwd/chfn/chsh
778 replacement done). Complicated by the fact that we don't want to allow
779 incoming connections to the machine running Freeside, so we probably need
780 to have a daemon on each external shell or web machine that is contacted
781 by the Freeside machine. Be very very careful for both traditional
782 security issues and DoS problems.
784 An extension of the above to allow users to modify selected parts of their
785 own information, order and cancel services. A web interface for new
788 Expand domain name stuff to house all domain information. Export
789 named.boot/named.conf (primary and secondary) and named.{domain} files.
790 Add more registries (not just InterNIC's com org net edu)
792 Nice postscript paper invoices, rather than current ASCII invoices.
794 think about race-condititions in FS::Record and derived ->check ->insert
795 and so on, uid and username checks in svc_acct, etc.
797 Move to rsync over ssh file exportation rather than scp.
799 check 'n fix the proactive password checker. (cracklib?)
801 refunds of "BILL" payments: generate pseudo-check.
803 write batch senders and batch parsers for the different credit card processors
805 More CC processors/methods.
807 you should be able to fiddle the setup date in cust_pkg. (at least initially)
809 delete options in administration section
811 write a generic batch senders and batch parsers.
813 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
814 type stuff from cerkit)
816 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)
818 you should be able to get column types as a method against an FS::Record object
819 as well as dbdef->table($table)->column($column)->type
821 move to perl module for fuzzy and soundex searching.
823 package view needs to list extraneous services; we need to prevent the
824 creation of them so this never happens (and mark it as such in the source)
825 (the creation problem should be fixed - though they will still happen if people
826 fsck around in the data manually, so list them anyway)
828 add attribute dictionary to fs-setup as a menu, plus analyze users file to
831 Check for and report on duplicate billing accounts (cust_main, though many
832 will have a need for these so probably don't disable them outright.)
834 create a ->warn as well as a ->check method for all FS::table classes?
837 something to automate making a release and updating the web demo
839 export a debian-style (also redhat and?) /etc/group file aswell!
841 svc_acct_sm.import qmail import should pull in recipientmap people too.
843 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
844 should fork and do them in a child.
846 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.
848 get some of { city, county, state, zip } from the missing bits if
849 possible (where can i get the data to do this? usps.gov?)
851 additional interfaces (perltk? java?)
853 Put the GPL notice in all files.
855 integrate w/IDEA's signup server
857 $cust_bill->owed database field to be eliminated, replaced by a method call
858 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
859 same for cust_credit->credited
861 Export quota information.
863 move all configuration to a central place. maybe in blob's in the
864 database. maybe even things like the code to execute when a username is
865 changed can be in there, so less of the distributed scripts change between
868 Implement setup and recurring fees as Safe perl expressions rather than
869 numbers, to allow for variable-rate services. Backwards compatibility is
870 obtained because { 43 } in perl is still 43. :) Define API to pass
871 starting and ending dates and any other necessary data to expression
872 (fees are currently evaluated as Safe expressions but more work needs to
873 be done to define an opmask for various needs, write examples
874 (usage-based billing, etc.) and so on).
876 Add the ability to modify the next billing date in cust_pkg, and take
877 appropriate action. This will allow the implementation of pro-rate/1st of
878 the month billing as well as the ability to manually fiddle with
879 anniversary dates in cust_pkg, so you can sync a customer's anniversary
880 date even if you're using anniversary billing (manually or automatically).
881 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
882 charges - anything more complicated should figure it out itself given
883 starting and ending dates [document that!])
885 Daily Radius log parsing into database; other logfile formats?
887 Callbacks to enforce hourly limits on accounts (suspend until the end of
888 the billing period?), for those who limit customers rather than tack on
891 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
892 example) need to charge tax on equipment but not service (separate flags
893 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
894 recur_tax and recur_notax fees, and possibly something more flexible if
897 Allow for a variable number of invoices for customers who need multiple
900 Add a mail alias service with table svc_acct (not domain mail aliasing
901 which is domain with svc_acct_sm)
903 (bring back from fsold) Change customer comment field from its current kludge to something more
906 Better work orders with more information. Should eventually open a ticket
907 when we have such a thing.
909 edit/process/svc_wo.cgi
910 Call tracking and trouble tickets.
912 More accoutability for complimentary accounts: approval, expiration, term
913 (no more than x months in advance) and notification.
914 Flag particular users (or all users, for that matter) as having their
915 passwords hidden and/or locked from users of Freeside (maybe need Freeside
916 security levels first?).
918 Better Freeside-level configurable access, for those ISP's who have
919 employees they can't trust. Right now you're "stuck" with setting up
920 .htaccess stuff yourself. This should really just be integrated.
922 configuration/setup should get web interface
924 /usr/local/etc/freeside should be configurable
926 (probably as part of some automated installation process?)
928 This requires some serious magic in FS::Record:
929 ok, if date_type in fs-setup is to be something besides int,
930 now we need to create wrappers
931 for them so they behave identically across RDBMS's, ie date pops out as as
932 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
933 is a string not a hashref for backwards compatibility?) and so on. (remember
934 to treat '0' as Not a Date instead of 1/1/70.
936 Add Freeside-level transactions for RDBMS's which don't support
937 transcations? (Currently we assume a minimal RDBMS which has no rollback,
938 transactions or atomic updates). Or just require a RDBMS that supports
939 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
940 interface had this kludge on top of it but is a technical dead-end in most
941 other ways, unless it can gain an SQL parser and DBD interface.
943 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
944 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
945 an FS::Record have something to do with a tied hash? But we don't want
946 performance to go gaga... maybe something with commit to help out here?
948 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
950 Better automated comparison of our CC records with processors (CyberCash,
951 at least, has not always had 100% accuracy, though recent versions are
954 Expect or other pty based login check, where we actually connect to a
955 terminal server or shell machine and test logging in as the user (if we
956 are keeping a cleartext password for that user) (This is something tech
957 support often needs for new customers)
959 Use cust_main table for pre-sales tracking as well?
961 Automatic commision report and check generation via freq and prog (to
962 become a Safe perl expression) fields in agent table, and possibly others.
964 Database and add a mailed-out date and method for disk/CD mailing, so a
965 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
968 Inventory tracking for physical items such as routers (for sale or
969 lease... probably doesn't make a difference in the ordering... but if you
970 cancel a router lease the inventory should come back. hmm.)
972 -- Matt's wishlist ---
974 From matt@michweb.net Fri Feb 20 16:39:53 1998
975 Date: Thu, 19 Feb 1998 23:20:11 -0500
976 From: Matt Simerson <matt@michweb.net>
977 Reply-To: quadran-developer@netgoth.com
978 To: quadran-developer@netgoth.com
979 Subject: Re: Welcome to quadran-developer
981 >Whats it based on and what is it supposed to do? I'm interested, but
982 >unfortunatly, I don't have that much time to help on the project (I'm busily
983 >working on one of my own based around MySQL and Qt right now -- don't know
984 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
985 >it is designed around our system)...
987 That's what I set out to find, but didn't find anything on the web site.
988 I'm looking for something that will do the following:
990 Single point of entry for users on a secure system:
991 Creates account on user (public) systems
992 update /etc/passwd/master.passwd file
993 update radius database (if necessary)
994 Set up up disk quotas (although I hacked adduser to do this)
995 Option for adding user to a mailing list(s)
996 Export of new user info to customizable report (for automated entry
998 accounting software, etc...)
1001 Export credit card info for batch processing and have hooks built
1002 in for other forms of electronic processing.
1003 Batch-Payment (apply payments from formatted text file).
1004 Customizable reports for manual entry/importing into Accounting
1006 Email or laser print invoices
1007 Sanity checks credit card numbers before processing (code available)
1009 Simple method for disabling an account.
1010 Arbitrary Expiration Dates (on a given day, in x days)
1012 Changing password to '*'
1013 Virtual customers disabling dns, http server, log processing, etc..
1015 Billing for different account types:
1016 Dialup monthly flat rate. Prorates for partial months.
1017 Dialup monthly flat rate for x hours + hourly usage.
1020 Virtual Web accounts - w/multiple mailboxes
1021 Leased line accounts
1022 Disk space used over quota.
1023 Tech support minimum + hourly charges
1024 Other for misc stuff (modem, RAM, etc...)
1026 Per user definable RADIUS attributes (ties in with above)
1029 IP filters (for dialup email only)
1031 Keep logs of modem usage generated daily from radius accounting logs stored
1032 on multiple radius servers.
1034 Keep logs of disk usage generated from quota.
1036 Method of adding virtual domains to your system:
1037 Automatically grabs an IP address from a preassigned pool.
1038 Creates a domain.com database file from database fields
1039 Updates /etc/named.conf or /etc/named.boot and reloads named.
1040 Add's virtual.com to /etc/sendmail.cw or qmail control files.
1041 Edits your web servers httpd.conf file and restarts http server.
1042 An optional section for adding vif's can be added if the users OS
1043 supports adding them on the fly. Otherwise it's up to the end
1044 user. Make a hook that can run a custom script that the user
1045 tweaks for his system.
1046 Update or create the config file your web stats analyzer needs. I've
1047 done this for analog (free) and http-analyze. Probably
1048 should only officially support analog and let users hack
1049 it to their hearts desire.
1050 I've already written scripts that do most of the virtual web stuff on my
1051 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
1052 as long as all the info was stored in the database (username, domain name,
1053 and ip pool) this could easily just be run as an external script that the
1054 user tweaks to match his system.
1056 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
1057 Payroll, Tax stuff, and most everything else we could need. It's already
1058 set up for the type of checks we have, etc, etc... I just need something to
1059 do the billing part. I can import/export sales and payments directly once
1060 the billing part is done. You can't write accounting software as good as