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