| |||||||||||||||||||||||||||||||
|
Access Denied Members of the ISP-Marketing list discuss the path to a trouble-free billing system. Unfortunately, the journey involves navigating the maze-like universe of database systems.
On the ISP-Marketing list in March, JM inquired,
A number of respondents disclosed their favorites: [AD suggested] "Here are two resources that we use. They would work with Linux, and they are open source. SISD's Freeside ISP accounting system, and the SQL-Ledger web-based invoicing system." [TT offered] "The newest version of FileMaker Pro 5 is really good, and completely customizable. I find that it crashes a lot less than MS Access did." [SC advised] "Look at BillMax. It took us about six month to convert to it and we're still working out the bugs, but I think it is the best one out there. Don't try importing history; just do balance forward. And buy the support service: it will be worth it." There was some disagreement regarding one of the more popular solutions: [BR noted] "One of the best known of the accounting/billing/database systems designed for ISPs is Rodopi. However, we tried to implement a Rodopi solution last year and finally decided it wasn't for us: poor support, and an overall lack of understanding of the technical issues on the part of Rodopi reps. We're currently implementing a Platypus system, and while it will take a while to implement, it seems clearly superior to Rodopi, though not nearly as popular." [JL added] "We have Rodopi installed. We have some serious issues with the software, and they are not very supportive. We are moving everything to PRISM." [KM countered] "We've used Rodopi for over three years and it works just fine for us. I can't say I'm totally pleased with some of the decisions they've made over the past six months, but in general, for managing accounts, integrating with Radius, it works. I really wouldn't want to go through the hassle of changing to another system. We've learned to get support for the system not only from Rodopi directly, but from the user group. What works for us may not work for you; but it does work for us."
End
|
|
|||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||
#