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