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