1 $Id: TODO,v 1.52 2000-10-27 20:15:50 ivan Exp $
3 If you are interested in helping with any of these, please join the
4 *development* mailing list (send a blank message to
5 ivan-freeside-devel-subscribe@sisd.com) to avoid duplication of effort.
9 > 1. A Web Form to the user get his account added automatically . The
10 > /etc/raddb/users and /etc/passwd would be updated automatically (these
11 > file are on the same machine Freeside is). I guess the the Add
13 > page with some customization could be the work.
14 > 2. A Canceling Account Web Form available to user cancel his account
17 > 3. A Password Changing Web Form where the user could change your
18 > password by sending your username, old and new password.
19 > 4. Additional POP Accounts Creation where the user supply only his
21 > username/password (probably provided from a PPP Account already
23 > and his POP username/password for this specific account.
24 (actually need something more general i guess - probably need some way to say
25 which accounts (svc_acct) can log in and make changes per customer (cust_main) )
27 this is awfully vauge, perhaps email for more info? don't want to alientate
28 someone with accounting experience, but i just don't have time right now.
32 Thanks for the information. It took me a little while to figure it out, but I
34 able to create an invoice. As a lamer and an accountant, may I make a few
37 On the Customer view page:
38 1) Layout the information in the manner the invoicing process is conducted.
39 a) Customer information
41 c) Add a "Create & Edit Invoice" section - this allows auditing of the
42 invoice before it is processed.
43 d) then put the billing section to actually process the invoice
44 e) then put payment history information
47 Mark Roberts <mroberts@iopenenterprises.com>
50 new overdue code might be overzealous. test carefully.
52 Port Freeside to use the modules that were abstracted from it:
53 Net::SSH, Net::SCP, DBIx::DataSource and DBIx::DBSchema, at least.
55 "first package" and email invoice (?) not sticky on errors in new/edit customer
58 http://www.ipmeter.com/ integration would be useful
60 http://tangram.sourceforge.net/
63 mmm, http://pootpoot.com/~dlowe/DBIx-Table/
65 The cybercash links in htdocs/docs/config.html are b0rken.
67 Yes. Which is what I've been trying to tell you. (destination user,
68 destination domainname) would be represented by the svcnum of a record in
69 svc_acct. (In retrospect, using the uid instead of the svcnum was a bad
70 choice). (domuser, domain name) would be part of the svc_acct_sm record,
71 as domuser and domsvc.
73 Upon further consideration, I'll probably eliminate the svc_acct_sm table
74 completely, and just add a field for the svcnum of a domain and the svcnum
75 of a destination mailbox to svc_acct (or perhaps a one-to-many
76 relationship - multiple svcnum(s) for multiple destination mailboxes.
79 > > > > Longer-term, I need to do something about the length of the
80 > > > > column names -
81 > > > > The SQL1992 standard defines 18 character column names,
82 > > > > which would be a
83 > > > > reasonable goal.
85 > > > Maybe the thing to do would be to separate these out to separate
87 > > > then we could simply use something like id, attrib_name,
90 > > > store all of the radius values.
92 > > Hmm, no, that's not quite right. You don't want to store the actual
93 > > strings in the records for each account. Probably need a table that
94 > > corresponds to the RADIUS dictionary file, with a list of
96 > > attribute id's, then reference the attribute by id and not name.
98 > > The more difficult bit is handling the service definitions
100 > > part_svc and it's effects.
102 > Yes that could be a bit tricky. Perhaps just one "radius" field in
103 > part_svc that held a list of id's from the radius table that applied
104 > that particular service?
106 No, that wouldn't let you set defaults or fixed values for each attribute,
107 like part_svc currently does.
111 hmm - if you delete an account in svc_acct somehow that a mail alias points to,
112 svc_acct_sm.export will fail. make sure this can't be done using
115 Bug: during the linking process apparantly you can link too many services to
118 zip code i18n is not very good :( but at least US, CA, HU, ?
120 ut_phonen doesn't check data length. several
121 orthogonal cleanup projects here. *sigh*
123 update the cybercash links in config.html and in the homepage. add more explicit support for other payment types. etc.
125 From "Tim Jung" <tjung@igateway.net>
127 Automatic CC Decline Notices via email
128 Block Time billing for prepaid internet cards (400 hours or whatever block
130 Trouble Ticket System with simple search function for Knowledge Base feature
132 Credit Card System support for Red Hat's CCVS, and other Linux credit card
134 Contact Manager/Lead Tracking
136 Cisco NetFlow Account for IP traffic billing
137 VoIP and FoIP billing
138 Roaming per minute billing based on Radius Proxy support or number they
139 dialed into from Radius logs (800# etc)
140 Support for OpenSRS Domain Registration
141 Support for TUCOWS signup CDs
144 dbdef-create for postgres
146 pro-rating, fiddling dates
148 It looks like svc_acct.import doesn't deal well with comments and
149 multi-attribute lines.
151 ivan@rootwood:~/freeside_current$ rgrep -r domuid * | cut -d: -f1 | sort |
156 bin/svc_acct_sm.export
157 bin/svc_acct_sm.import
158 htdocs/docs/man/svc_acct_sm.txt
159 htdocs/docs/schema.html
160 htdocs/edit/CVS/Base/part_svc.cgi
161 htdocs/edit/part_svc.cgi
162 htdocs/edit/process/svc_acct_sm.cgi
163 htdocs/edit/svc_acct_sm.cgi
164 htdocs/search/svc_acct_sm.cgi
165 htdocs/view/svc_acct_sm.cgi
166 site_perl/svc_acct_sm.pm
168 rootwood:COMPLETEHOST/TODO
170 Currently, you set a value in the %FS::UID::callback hash with a coderef
171 of the code you want to execute, but this was bad design and will shortly
172 be changed to a subroutine to which you pass your coderef to register it.
174 This is not a bug, it is how the system is currently designed. After
175 defining a new package, you need to specifically allow agent types to
176 purchase packages. You can do this from the edit screen of the new agent
179 It wouldn't be a bad idea to add a configuration value that makes new
180 packages available for all currently existing agent types automatically.
182 On Fri, Apr 07, 2000 at 10:50:35AM -0500, David Morton wrote:
183 > For some reason, the type_pkgs table didn't get updated when I tried to
184 > create a domain service and package... insert into type_pkgs values
185 > (4,1); fixed it up so that I could actually order the package.
188 From: Chuck Cochems <zaphod@tdl.com>
190 1) automated generating of late notices. So far the only way I know to
191 generate one is to re-invoice manually.
193 2) smart credit card rejection handling. It should e-mail a note at
194 least, explainig that it did't go through, and why.
196 3)coment field in the main customer record.
198 4) streamlined payment entry feature. the current scheme has it fairly
201 5) queries to show al customers who owe money,and such stuff as that.
204 credits aren't counted against past invoices? hmm. something needs to be
205 done to "apply payment" genericly. and zero out invoices etc.
207 more email which should make it into a more organized TODO list:
209 I would also love to see Freeside support bandwidth billing by reading the
210 Cisco NetFlow Accounting data so we and other ISP's could automatically bill
211 co-located servers and even potentially other virtually hosted sites like
212 MUD, Palace Chat, IRC Chat, etc based on the bandwidth they use or average
213 sustained rates or whatever. I'm not much of a programmer so I don't know
214 what all this entails but I did download a NetFlow client agent/whatever for
217 It would also be nice to see Freeside be able to read Apache log files and
218 bill customers for web traffic that way as an option also. Plus an option to
219 bill for excessive disk usage without having to use quotas if you didn't
220 want to, would be a nice feature as well. So you could monitor with a script
221 or something to see how much disk space a user was using then get some
222 average and charge a certain amount for anything above some preset limit for
223 that account type. I might be able to hack something like this up, but I'm
224 not 100% sure where to start or if there is something out there that could
227 Do you think that you will ever support the HKS CCVS (Hell's Kitchen
228 Software Credit Card Verification Software) since Red Hat bought them out
229 and is going to be including that for credit card processing when you buy
230 the professional version? What about possibly supporting the OpenCCVS which
231 is a GNU/GPL version of a credit card program? I haven't had time to comb
232 through the Freeside code to see how hard it would be to add support for
233 these as externally called programs.
235 Also any thoughts on help desk, and knowledge base stuff? Any thoughts on
236 this stuff, and how possible and what kinds of work or time frame would be
241 Internet Gateway Inc.
246 CVS via SSH (Score:1)
247 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
248 (User Info) http://www.fxp.org/~jedgar
249 The links above are your best bet for basic cvs server configuration. Once you have a pserver set up, you
250 may consider using cvs via ssh. All you need to do is the following:
252 1) Have ssh and sshd set up on the client and server machines
253 2) Set CVSROOT="joe@example.com:/home/ncvs"
254 3) Set CVS_RSH="/usr/local/bin/ssh"
256 (Obviously, insert the proper host/paths above)
258 You can also set up cvs/ssh to not need a password every time (similiar to an initial 'cvs login'):
260 1) run ssh-keygen on client machine using no passphrase.
261 2) copy/add ~/.ssh/identity.pub on the client to ~/.ssh/authorized_keys on the server
262 (man ssh for more details)
264 The main reason I mentio
265 CVS via SSH (Score:1)
266 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
267 (User Info) http://www.fxp.org/~jedgar
270 There's no way to do this currently, though it would be pretty
271 straightforward to modify the source - specifically, the _collect_
272 subroutine in FS::cust_main.
274 On Mon, Dec 13, 1999 at 04:05:32PM -0700, Jeff Garner wrote:
275 > Freeside will e-mail my users when they are billed if they are setup as
278 > When setup by credit card it does not e-mail them. Is there a way to
279 > turn on e-mail invoices for those who are billed via credit card? Kind
280 > of like a recipt of billing....
283 doc: http://www.softagency.co.jp/mysql/qmail.en.html
285 sql1992.txt standard is 18 character column names. shoot for that, not just
286 32 (postgresql default)
288 Also note that (AFAIK) Freeside won't display any package that has more
289 than one service on the "Add Customer" page. The reason for this is
290 because there's no way to dynamically alter the displayed html form
291 based on which package is selected. One possible solution would be to
292 make an additional page that's used in the signup process that would
293 display the form for each package, like a MS-style "Wizard". The first
294 page lets you select the package, then the second page has the custom
295 form with fields for each service in that package and a save button. Of
296 course, that would require a little perl work.
299 Scott Cruzen <sic@boernenet.com>
302 Your suggested script with back up /usr/local/etc/freeside, but will miss
303 any database not named `freeside'. Both of our scripts are specific to
304 MySQL. If you're interested in contributing to Freeside, maybe you could
305 work on a script which: reads the mapsecrets configuration file and then
306 each secrets file to find out what specific database engine(s) (MySQL,
307 PostgreSQL, etc.) and database(s) need to be backed up, then does so,
308 serializing backups of the same engine, i.e. stop mysql, do all the mysql
309 backups, start mysql, stop postgresql, do all the postgresql backups,
310 start postgresql, etc.
313 > mysqldump -t freeside > fs-backup.sql
315 > tar -Pzcvf fs-backup-`date +%y%m%d%H%M%S`.tgz fs-backup.sql /usr/local/etc/freeside/
318 I chose to use counters in the filesystem because there is no standard way
319 to get the value of an auto-incrementing keyfield which is common across
320 all databases (as seen through DBI/DBD).
322 It certainly wouldn't be a bad idea to use the database-specific methods,
325 htdocs/edit/svc_acct.cgi:
326 (Does the `*HIDDEN*' show up when you are adding a new account, and
327 specify the password, then receive an error and are returned to the form?)
330 Thought some of you might be interested in this:
332 <ftp://ftp.minivend.com/pub> has CyberCash compatibility modules for
333 Paymentnet <http://www.paymentnet.com> and Authorizenet
334 <http://www.authorizenet.com> which should allow you process transactions
335 using those services as well as CyberCash.
337 The files are named CCLib.pm.paymentnet and CCLib.pm_authorizenet,
338 respectively, and are installed by renaming to CCLib.pm and moving to your
339 site_perl directory. Otherwise, follow the directions for Cybercash v2 in
340 htdocs/docs/config.html
343 fs_passwd/ is a client-server replacement for the `passwd', `chfn' and
344 `chsh' commands that updates the Freeside database. (so for that to be
345 useful, you'd have to be exporting that data periodically)
347 fs_radlog/ is a client-server RADIUS log parser that stuffs the data into
348 SQL. It isn't finished, and probably won't be unless someone who I can't
349 convince to use one of the RADIUS daemons that logs to SQL directly pays
350 me money or something.
352 fs_signup/ is a client-server signup server. i'm just finishing it up
353 now; probably isn't on your machine yet.
356 http://www.sisd.com/freeside/list-archive/msg00812.html
358 package definitions should be implicit allow wrt agent types, not implicit deny
359 (with the old behavior possible via a config file)
361 > So is there anyway it could be setup to allow you to select a "primary
362 > service" from each package? This service would be the one you were prompted
363 > for. Could the signup server then be expanded to allow users to go into
364 > their package and "turn-on" the remaining non-primary services(using the
367 take the GPL'ed whois proxy stuff at www.geektools.com and turn it into
368 intelligence for Net::Whois.
370 A web version of the fs_passwd stuff would be nifty.
372 If you have Cistron authenticating directly from MySQL, you can replicate
373 in real-time instead of exporting periodically. See
374 <http://www.mysql.com/Manual_chapter/manual_Common_problems.html#Replication>.
377 <http://www.sisd.com/freeside/list-archive/msg00541.html> (was 546), and
379 and http://www.sisd.com/freeside/list-archive/msg00421.html (was 423)
381 > > 5: Is there anyway to get freeside to send a sysadmin a warning when a
382 > > credit card has expired?
383 No, but there should be.
385 Put this in the doc (quoting Mark Wells <mark@pc-intouch.com>):
386 >Of course, thanks to the sheer coolness of SQL and MyODBC, you can do
387 >whatever reports you want in basically whatever application you want.
388 >There's no need for Freeside itself to do any reports at all.
390 middle names and titles
392 On Wed, Jul 07, 1999 at 01:11:40PM -0400, Frank Nazario wrote:
393 > Playing and entering information to Freeside i encountered the following
396 > View Customers by Agent
398 > View Pending Invoices
401 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
402 Not to say that it shouldn't be a configurable option.
404 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
405 (at least until the idea of a default domain goes away)
407 FS::Record::qsearch does an eval every loop iteration (which is itself not
408 guaranteed to work across all DBD's and should be fixed). This has got to be
409 slow. Fix it. (I think recent Perls might have a way to accept a variable
410 there, no eval needed?)
412 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
413 `shells' configuration file before importing, and removed them afterwords?
414 (even better if svc_acct.import did that automatically - it could just
415 munge and restore @FS::svc_acct::shells... hmm.)
417 > BTW, Ivan, I am trying to verify in an additional database table that a
418 > particular user doesn't exist. This database is used to store email aliases a$
419 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
420 > with the idea of just writing the aliases to an email only svc_acct that
421 > doesn't write to the password file, but that isn't really how I want to do it.
423 Actually, I think that's a pretty good way to do it. Cerkit contributed
424 support a little while back for svc_acct.pm and svc_acct.export for
425 multiple export targets. It needs to be cleaned up and documented, which
426 I'll try to get to soon. For this to work correctly, the svc_acct_sm
427 table should go away, along with the concept of a "default" domain.
429 default setting for new packages should allow all agents to purchase them...
430 with a config file for the old behaviour
432 fix or replace Term::Query (Quiz::Question doesn't do what i need)
434 Check config file reading stuff from CPAN
436 Authorizenet module from CPAN!
438 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
441 I'm hoping Freeside can support arbitrailly complex pricing plans
442 because of a simple concept: all prices are perl expressions. So if
443 you use `19.95' for example, perl evalates that to be `19.95'. But if
444 you need to do a complex pricing scheme, you just need to write an
445 appropriate perl expression, which will most likely pull data from the
446 database to return pricing. Some things will already log to SQL; for
447 example most RADIUS servers can or have a patch available. Getting
448 Freeside to bill based on any sort of data then becomes a matter of
449 importing the data into the database.
451 There are some issues involved with pro-rating, partial month charges,
452 that sort of thing. Expressions will need a standard way to have the
453 applicable time/data ranges passed to them. Also the expressions are
454 currently running under the Safe perl module, and the opmask might not
455 be right in all situations. I'll try to spend some time working on
456 this if you are using it.
458 > 2. can customers view their bills on-line.
460 Not yet; it needs to be proxied from Freeside to a customer web server in
461 a secure way using something not completely unlike the fs_passwd,
462 fs_passwdd, fs_passwd_server trio.
465 > Lastly, if someone over pays on an invoice, the credit part does not flow
466 > over to other invoices..
468 The total balance flows over correctly, but individual payments don't.
469 The code you're looking for is in FS::cust_pay::insert
471 The question of what to do with overpayments that don't have another
472 invoice to flow into (yet.. or possibly not) is still an open one. The
473 legacy system Freeside replaced long ago had a separate place for this
474 (payments waiting for an invoice) for each customer, and it gave our
478 option to relax username uniqueness in favor of username+domain or mail/shell
479 vs. radius to ease import for isp's with namespace problems or who buy others.
481 do i have to store anything for radius realms besides regular radius attributes
482 (which are handled fine now)?
484 warn or complain or something when invoice_from is empty (and we use it)
486 Right now Freeside uses the `freq' field of a package definition as a
487 number of months. The specific section of code you're looking for is in
490 #change this bit to use Date::Manip?
491 #$sdate=$cust_pkg->bill || time;
492 #$sdate=$cust_pkg->bill || $time;
493 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
494 my ($sec,$min,$hour,$mday,$mon,$year) =
495 (localtime($sdate) )[0,1,2,3,4,5];
496 $mon += $part_pkg->getfield('freq');
497 until ( $mon < 12 ) { $mon -= 12; $year++; }
498 $cust_pkg->setfield('bill',
499 timelocal($sec,$min,$hour,$mday,$mon,$year));
500 $cust_pkg_mod_flag = 1;
502 ..and when I went poking for this, looks like it tells us just what needs
503 to be done! Hehehe...
505 Date::Manip can handle cool things like "+ 1 month" (actually the current
506 case of /^(\d+)$/ would have to be added as a special case of "+ $1
507 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
510 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
511 > I can't quite seem to figure out how this exporting works. From what I
512 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
513 > /etc/shadow, etc. files. Is this only for initial setups with the
514 > export hooks being in the pm's?
516 You can use both, or just one method. The configuration files control
517 this. One of the things in the TODO is to take out the last few things
518 that aren't customizable wrt this and put them in config files.
520 http://www.daemonnews.org/199905/user-mgmt.html
522 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
523 submitted upstream!), or remove requirement from bin/svc_acct.import and
524 bin/svc_acct_sm.import and take it out of the install instructions.
526 use this cool link to explain the Freeside API
527 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
529 Multiple tax rates by geographic region (county, state, and county) are
530 supported; just choose View/Edit tax rates from the main menu.
532 Multiple tax rates by package are not (yet) supported.
534 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
535 > How would you handle something like multiple tax rates and multiple
536 > states? For example in Connecticut, they just changed computer and/or
537 > data processing services to 3% (whatever that is), and everything else
541 > Second, when trying to add a new user I get two types of errors; first one
542 > is when I place an e-mail address and select the "submit," Freeside
543 > complains with "Error: Unknown local account (specified literally)"
545 You probably put a (local) email address in for email invoices. Freeside
546 stores these as references to the database records, so (for example) they
547 follow username changes.
549 I'm guessing you put in the email address that you were creating, and got
550 that error because it didn't exist yet. Sounds like a buglet to me. I'll
551 try to fix that soon; in the meantime you can add the invoicing email
554 (workaround for postgres before 6.5) (unlikely to ever be implemented)
555 In the mean-time, this could probably be fixed with the reverse of
556 the kludge in FS::Record::new. This removes `$' and `,' from money fields
557 coming out of the database. Something which fixed up the data so Postgres
558 was happy with it could go in FS::Record::_quote, for data going into the
561 our data display problem might be a Freeside problem wrt not using
562 Oracle-compatible DBI syntax (fixed using the return value from $sth->execute
563 as a number of rows - something else?).
565 hooks for arbitrary commands out of configuration files
566 svc_acct.pm svc_acct_sm.pm etc.
568 Add this to a FAQ, along with doing it for middle names:
571 > What I'm finding difficult is how to easily
572 > customize fields. For example, I am trying to add a "middle name" field
573 > to the Customer Edit, view, etc. If I'm going about it right, it appears
574 > I have to edit the cust_main.cgi under edit and edit/process and the
575 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
576 > some light on the best way of doing this.
578 You have the basic idea. To implement that completely, I would:
579 - Add the new field to bin/fs-setup for new users
580 - Document the field in htdocs/docs/schema.html
581 - Document the change in a new file, htdocs/docs/upgrade4.html
582 * Run bin/dbdef-create
583 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
585 For bonus points, I'd grep around for the various bits which use "$first
586 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
587 , like search/cust_main.cgi
589 document security model:
590 Don't forget about Apache usernames - since, via the mapsecrets file, each
591 user can login to the SQL database with a different username and
592 password, you can utitilize the security model of the SQL database as
593 well. Also, each username here can point to a different configuration
594 directory where you could store user-specific configuration info. Then
595 you could link each username to one-to-many agents.
596 (The web demo works using a trivial version of this.)
598 Yes, queue processing or the equivalent via checkpoint fields on various
599 talbes (which you pick up via a pretty simple SELECT) would be really
602 default (and ordering) state/county/country config file
604 cust_main_county table to provide a preferred ordering, so the most common
605 entries would be at the top of the selection box. automatically, based on
608 hmm... maybe svc_acct__shell should check off the legal shells list if
609 applicable? yeah... cool.
611 payinfo field should me much larger than 16
614 [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.
616 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
617 (view/cust_pkg and view/svc_*)
619 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
620 (all the actual date handling uses UNIX timestamps and is fine)
622 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
625 one-time/per-customer/? changes in rates and descriptions ('remembered
626 invoices'): implement by creating a new package on the fly... but it isn't
627 associated with any agent types so it won't show up for other customers to buy.
628 (but also... make sure they go away when the customer does! - need this? :
629 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
630 with custnum and partpkg (like type_pkgs)
631 (what happens if you hit "custom pricing" but the pricing is already custom?)
633 Lay out any remaining ugly forms better.
635 remove "records identical" warning? gets in the way of more important stuff.
636 or fix logic which tries to update identical records??
637 1.2 should be quiet enough that the error log is useful, hopefully.
639 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
640 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
641 (22 characters!) It seems that stuff over the limit is silently ignored,
642 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
643 stock Postgres. see rfc2138 for what's affected
644 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
645 (mysql has a 64 character max column length. others?)
647 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
648 (when sending mail in cust_main.pm::bill or svc_domain.pm)
650 look at DBIx::Recordset! (and Tie::DBI, and...)
652 undefined conf/lpr gives this uninfomative error:
653 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
655 l5/site_perl/FS/cust_main.pm line 629.
656 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
658 l5/site_perl/FS/cust_main.pm line 631.
659 So give a meaningful error!
661 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
663 i10n: Apache::Language
665 Apache::Session? Other useful Apache::* ?
667 email invoices are only sent for the BILL payby. If setup, should statements
668 (since they're not invoices) be sent for COMP and CARD as well?
670 $cgi->keywords is causing the (hard to trace) error:
671 Use of uninitialized value at (eval 5) line 5
673 edit/cust_main.cgi gives an uninformative error message:
674 > Can't call method "agentnum" without a package or object reference at
675 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
676 if there are no agents.
678 (is this missing on any web screens? (easy with $cust_svc->label)
679 Add the ability for services to filter information up to the package level
680 for web screens, so you can select a particlar package based
681 on username or domain name, etc.
683 Allow a cancelled/suspended/active status from packages to bubble up to
684 the customer lists. Put active, then suspended, then cancelled accounts.
685 Similar ordering on the package listing inside a single customer.
687 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
688 the web interface in general needs to be redone in a more abstract way.
690 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.
692 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
694 add a select method to FS::Record?
696 one-time/per-customer/? changes in rates and descriptions ('remembered
697 invoices'): implement by creating a new package on the fly... but it isn't
698 associated with any agent types so it won't show up for other customers to buy.
699 (but also... make sure they go away when the customer does! - need this? :
700 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
701 with custnum and partpkg (like type_pkgs)
702 (what happens if you hit "custom pricing" but the pricing is already custom?)
704 You can't delete the stuff under administration yet. Add this,
705 _including_ making sure the thing you are deleting is not in use!
707 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
709 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
710 loading of configuration. (pry need same idea, but will run immediately if
711 context allows). Looks like error is masked by 'use FS::cust_svc' which in
712 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
715 Allow a cancelled/suspended/active status from packages to bubble up to
716 the customer lists. Put active, then suspended, then cancelled accounts.
717 Similar ordering on the package listing inside a single customer.
719 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
722 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
724 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
726 .us domains and others!
727 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...
729 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
730 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
732 (test cust_main.pm with cybercash v2 and v3, especially with the callback
733 stuff AND with mod_perl w/cybercash v2 kludge in package main)
734 (callback stuff should be eliminated by now)
736 bah, table/itable/*table in FS::CGI is silly.
738 doc Apache::AuthDBI as well
740 Provide sample httpd.conf files.
742 hey look: Tie::DBI! Check that out. Override its commit with something that
743 does perl-side caching for ? a performance improvement and as an emulation
744 layer to plug in f.ex mysql's atomic transactions
746 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
747 Fix it anyway unless we migrate to Tie::DBI.
751 cust_bill.pm uses '==' comparison on dates because they're currently ints
753 config file for allowed card types
755 write instructions for adding new services w/svc_Common.pm. Get rid of all
756 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
759 test and document libapache-dbi-logger (woo!)
761 radius logfile parsing and perl expression check.
763 Fix in cust_bill BUGS:
764 There is an off-by-one error in print_text which causes a visual error (Page 1
765 of 2 printed on some single-page invoices).
767 fields should be a method against a FS::Record or derived object, as well as
768 being something you can call as FS::Record::fields('tablename'). Might
769 even be able to handle both in the same routine (that would be neato).
771 Immediate removal of incorrectly entered check payments (can't take too
772 long to do this, or accounting is fubared).
774 Add code to move from one service to another (POP to SLIP/PPP, etc.).
775 This _should_ be possible by working off the rules in part_svc rather than
776 hardcoding anything in. The rules in part_svc may need some elaboration,
779 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.)
781 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
782 Expand the HylaFAX interface (also possibly generalize for other fax
783 softwar ie .comfaxe); allow things like arbitrary faxes of sales
784 literature, specific troubleshooting documents and so on. Maybe even
785 allow users to do this (though that might not belong in Freeside).
787 misc/process/sendconfig.cgi
788 Configure fax recipients via a separate box rather than using the finger
789 name or first+last from cust_main.
791 move all phone number logic out of Freeside - let HylaFAX or whatever
794 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?!
796 should be able to link on some field in email alias (right now you can link
797 on username or domain with a fallback to svcnum)
799 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
801 deleting an svc_domain should delete all associated svc_acct_sm records.
802 same with a svc_acct.
804 periodic password encrypter
806 Automated, configurable notification, suspension and cancellation of
811 Allow for a future setup date on accounts.
813 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
816 edit (not just import, export and allow default/fixed) arbitrary radius stuff
818 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
820 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
822 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
824 what else (besides l10n) for i18n? (money!)
826 audit htdocs/* for things that should be libraried and things that should be
827 new methods on the objects (need to do this before implementing a new UI)
828 all the big things are done
830 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
831 Decide based on whether or not the "error" should show up in logs.
833 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
834 for HTML creation. Maybe Embperl or something along those lines. ?
836 When running bin/bill, Fix this (Annoying but harmless):
837 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
838 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
839 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
841 all cgi (but internal to the isp) places where package names are listed should also have
842 comment (like agent_type)
844 clean up $recref and other silliness and use -> calls where possible, or
845 one other alternative. clean up everything else.
846 should FS::Record use Tie::Hash? That would be very clean, but where do we
847 store the other information? Maybe you could ask any FS::Record object for a
850 change all file access from regular open(FILE,) stuff to OO, because of
851 problems scoping and passing filehandles like that.
853 the web interface should create a new object and use it instead of a blank
854 form for new records. the create method of svc_ objects should set defaults
857 sub check in man FS::table_name should be rewriteen. Get rid of $recref
858 stuff. Make sure all fields that refer to other database are checked.
860 Integration with signup disks (are there any free ones? Netscape?).
862 One-button cancel (+refund) for lusers who can't get online.
864 Keep information on virtual web servers (hostname, IP, host machine,
865 directory, etc.) and export this information for importation into the ISPs
868 Remove requirement that the first mail alias be the catchall? Still make
869 sure only one catchall per domain is defined in any case, of course.
871 Ability to move cust_pkg records from one customer to another? (proably
872 will need to cancel the old and create a new like when we move services
875 Auto-increment expired cards one year, and try again?
877 More non-US stuff - zip codes, country codes, foreign currencies, etc.
879 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
881 Nicer set of integrated reporting possibilities, like weekly sales totals
882 by customer, package, agent, referral, etc., aging reports sorted by lots
883 of different things, and so on.
885 Client/server setup for users to modify their own passwords, shells, etc,
886 via passwd or secure web interface (prelminary passwd/chfn/chsh
887 replacement done). Complicated by the fact that we don't want to allow
888 incoming connections to the machine running Freeside, so we probably need
889 to have a daemon on each external shell or web machine that is contacted
890 by the Freeside machine. Be very very careful for both traditional
891 security issues and DoS problems.
893 An extension of the above to allow users to modify selected parts of their
894 own information, order and cancel services. A web interface for new
897 Expand domain name stuff to house all domain information. Export
898 named.boot/named.conf (primary and secondary) and named.{domain} files.
899 Add more registries (not just InterNIC's com org net edu)
901 Nice postscript paper invoices, rather than current ASCII invoices.
903 think about race-condititions in FS::Record and derived ->check ->insert
904 and so on, uid and username checks in svc_acct, etc.
906 Move to rsync over ssh file exportation rather than scp.
908 check 'n fix the proactive password checker. (cracklib?)
910 refunds of "BILL" payments: generate pseudo-check.
912 write batch senders and batch parsers for the different credit card processors
914 More CC processors/methods.
916 you should be able to fiddle the setup date in cust_pkg. (at least initially)
918 delete options in administration section
920 write a generic batch senders and batch parsers.
922 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
923 type stuff from cerkit)
925 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)
927 you should be able to get column types as a method against an FS::Record object
928 as well as dbdef->table($table)->column($column)->type
930 move to perl module for fuzzy and soundex searching.
932 package view needs to list extraneous services; we need to prevent the
933 creation of them so this never happens (and mark it as such in the source)
934 (the creation problem should be fixed - though they will still happen if people
935 fsck around in the data manually, so list them anyway)
937 add attribute dictionary to fs-setup as a menu, plus analyze users file to
940 Check for and report on duplicate billing accounts (cust_main, though many
941 will have a need for these so probably don't disable them outright.)
943 create a ->warn as well as a ->check method for all FS::table classes?
946 something to automate making a release and updating the web demo
948 export a debian-style (also redhat and?) /etc/group file aswell!
950 svc_acct_sm.import qmail import should pull in recipientmap people too.
952 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
953 should fork and do them in a child.
955 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.
957 get some of { city, county, state, zip } from the missing bits if
958 possible (where can i get the data to do this? usps.gov?)
960 additional interfaces (perltk? java?)
962 Put the GPL notice in all files.
964 integrate w/IDEA's signup server
966 $cust_bill->owed database field to be eliminated, replaced by a method call
967 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
968 same for cust_credit->credited
970 Export quota information.
972 move all configuration to a central place. maybe in blob's in the
973 database. maybe even things like the code to execute when a username is
974 changed can be in there, so less of the distributed scripts change between
977 Implement setup and recurring fees as Safe perl expressions rather than
978 numbers, to allow for variable-rate services. Backwards compatibility is
979 obtained because { 43 } in perl is still 43. :) Define API to pass
980 starting and ending dates and any other necessary data to expression
981 (fees are currently evaluated as Safe expressions but more work needs to
982 be done to define an opmask for various needs, write examples
983 (usage-based billing, etc.) and so on).
985 Add the ability to modify the next billing date in cust_pkg, and take
986 appropriate action. This will allow the implementation of pro-rate/1st of
987 the month billing as well as the ability to manually fiddle with
988 anniversary dates in cust_pkg, so you can sync a customer's anniversary
989 date even if you're using anniversary billing (manually or automatically).
990 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
991 charges - anything more complicated should figure it out itself given
992 starting and ending dates [document that!])
994 Daily Radius log parsing into database; other logfile formats?
996 Callbacks to enforce hourly limits on accounts (suspend until the end of
997 the billing period?), for those who limit customers rather than tack on
1000 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
1001 example) need to charge tax on equipment but not service (separate flags
1002 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
1003 recur_tax and recur_notax fees, and possibly something more flexible if
1006 Allow for a variable number of invoices for customers who need multiple
1009 Add a mail alias service with table svc_acct (not domain mail aliasing
1010 which is domain with svc_acct_sm)
1012 (bring back from fsold) Change customer comment field from its current kludge to something more
1015 Better work orders with more information. Should eventually open a ticket
1016 when we have such a thing.
1018 edit/process/svc_wo.cgi
1019 Call tracking and trouble tickets.
1021 More accoutability for complimentary accounts: approval, expiration, term
1022 (no more than x months in advance) and notification.
1023 Flag particular users (or all users, for that matter) as having their
1024 passwords hidden and/or locked from users of Freeside (maybe need Freeside
1025 security levels first?).
1027 Better Freeside-level configurable access, for those ISP's who have
1028 employees they can't trust. Right now you're "stuck" with setting up
1029 .htaccess stuff yourself. This should really just be integrated.
1031 configuration/setup should get web interface
1033 /usr/local/etc/freeside should be configurable
1035 (probably as part of some automated installation process?)
1037 This requires some serious magic in FS::Record:
1038 ok, if date_type in fs-setup is to be something besides int,
1039 now we need to create wrappers
1040 for them so they behave identically across RDBMS's, ie date pops out as as
1041 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
1042 is a string not a hashref for backwards compatibility?) and so on. (remember
1043 to treat '0' as Not a Date instead of 1/1/70.
1045 Add Freeside-level transactions for RDBMS's which don't support
1046 transcations? (Currently we assume a minimal RDBMS which has no rollback,
1047 transactions or atomic updates). Or just require a RDBMS that supports
1048 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
1049 interface had this kludge on top of it but is a technical dead-end in most
1050 other ways, unless it can gain an SQL parser and DBD interface.
1052 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
1053 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
1054 an FS::Record have something to do with a tied hash? But we don't want
1055 performance to go gaga... maybe something with commit to help out here?
1057 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
1059 Better automated comparison of our CC records with processors (CyberCash,
1060 at least, has not always had 100% accuracy, though recent versions are
1063 Expect or other pty based login check, where we actually connect to a
1064 terminal server or shell machine and test logging in as the user (if we
1065 are keeping a cleartext password for that user) (This is something tech
1066 support often needs for new customers)
1068 Use cust_main table for pre-sales tracking as well?
1070 Automatic commision report and check generation via freq and prog (to
1071 become a Safe perl expression) fields in agent table, and possibly others.
1073 Database and add a mailed-out date and method for disk/CD mailing, so a
1074 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
1077 Inventory tracking for physical items such as routers (for sale or
1078 lease... probably doesn't make a difference in the ordering... but if you
1079 cancel a router lease the inventory should come back. hmm.)
1081 -- Matt's wishlist ---
1083 From matt@michweb.net Fri Feb 20 16:39:53 1998
1084 Date: Thu, 19 Feb 1998 23:20:11 -0500
1085 From: Matt Simerson <matt@michweb.net>
1086 Reply-To: quadran-developer@netgoth.com
1087 To: quadran-developer@netgoth.com
1088 Subject: Re: Welcome to quadran-developer
1090 >Whats it based on and what is it supposed to do? I'm interested, but
1091 >unfortunatly, I don't have that much time to help on the project (I'm busily
1092 >working on one of my own based around MySQL and Qt right now -- don't know
1093 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
1094 >it is designed around our system)...
1096 That's what I set out to find, but didn't find anything on the web site.
1097 I'm looking for something that will do the following:
1099 Single point of entry for users on a secure system:
1100 Creates account on user (public) systems
1101 update /etc/passwd/master.passwd file
1102 update radius database (if necessary)
1103 Set up up disk quotas (although I hacked adduser to do this)
1104 Option for adding user to a mailing list(s)
1105 Export of new user info to customizable report (for automated entry
1107 accounting software, etc...)
1110 Export credit card info for batch processing and have hooks built
1111 in for other forms of electronic processing.
1112 Batch-Payment (apply payments from formatted text file).
1113 Customizable reports for manual entry/importing into Accounting
1115 Email or laser print invoices
1116 Sanity checks credit card numbers before processing (code available)
1118 Simple method for disabling an account.
1119 Arbitrary Expiration Dates (on a given day, in x days)
1121 Changing password to '*'
1122 Virtual customers disabling dns, http server, log processing, etc..
1124 Billing for different account types:
1125 Dialup monthly flat rate. Prorates for partial months.
1126 Dialup monthly flat rate for x hours + hourly usage.
1129 Virtual Web accounts - w/multiple mailboxes
1130 Leased line accounts
1131 Disk space used over quota.
1132 Tech support minimum + hourly charges
1133 Other for misc stuff (modem, RAM, etc...)
1135 Per user definable RADIUS attributes (ties in with above)
1138 IP filters (for dialup email only)
1140 Keep logs of modem usage generated daily from radius accounting logs stored
1141 on multiple radius servers.
1143 Keep logs of disk usage generated from quota.
1145 Method of adding virtual domains to your system:
1146 Automatically grabs an IP address from a preassigned pool.
1147 Creates a domain.com database file from database fields
1148 Updates /etc/named.conf or /etc/named.boot and reloads named.
1149 Add's virtual.com to /etc/sendmail.cw or qmail control files.
1150 Edits your web servers httpd.conf file and restarts http server.
1151 An optional section for adding vif's can be added if the users OS
1152 supports adding them on the fly. Otherwise it's up to the end
1153 user. Make a hook that can run a custom script that the user
1154 tweaks for his system.
1155 Update or create the config file your web stats analyzer needs. I've
1156 done this for analog (free) and http-analyze. Probably
1157 should only officially support analog and let users hack
1158 it to their hearts desire.
1159 I've already written scripts that do most of the virtual web stuff on my
1160 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
1161 as long as all the info was stored in the database (username, domain name,
1162 and ip pool) this could easily just be run as an external script that the
1163 user tweaks to match his system.
1165 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
1166 Payroll, Tax stuff, and most everything else we could need. It's already
1167 set up for the type of checks we have, etc, etc... I just need something to
1168 do the billing part. I can import/export sales and payments directly once
1169 the billing part is done. You can't write accounting software as good as