Yes thanks Lonnie for those options. I have begun modifying cdrlog.php and it will probably be easier than I thought. Really all they need is to add the room number (extension) and the date of stay and out pops charges based on rated call prefixes. The billsecs is already there and I can just add a couple more columns (and remove some) and have a total at the end. They just add the total to the incidentals on their hotel management system! International will be a bit of a pain as so many rates but I could block them I suppose.
Yes I do like 2) as well if their reservation system has an API. Im afraid 3) & 4) are out of the question as interestingly our mobile calls are more expensive that most international calls. Regards Michael Knill On 31 May 2015, at 12:15 am, Michael Keuter <li...@mksolutions.info> wrote: Am 30.05.2015 um 16:02 schrieb Lonnie Abelbeck <li...@lonnie.abelbeck.com>: > Hi Michael, > > I don't have any experience with scripting CDR billing, but a few thoughts... > > 1) You can enable CDR Call Logging with SQL using the file > /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3 > > CDR Call Logging with SQL > http://doc.astlinux.org/userdoc:tt_asterisk-odbc#cdr_call_logging_with_sql > > Nuf said for the benefits of this. :-) > > 2) Possibly when a call completes a shell script is called in the background > to generate a transaction via 'curl' to another system. Possibly there is > some way to generate a comment or such in their hotel management system, such > that at checkout the phone charges could be added from the comment data. > > 3) Simplify the Phone billing, charge only per call at a fixed price ($1 or > so) and block expensive international calls. Here in the US phone calls were > once a revenue source for hotels before the advent of cell phones. I suspect > they are mostly for in-house calls now. Here $1 per US call and block all > international calls would probably work out. A cron job could email the > number of outbound calls / room once a day. > > 4) Don't charge for inexpensive phone calls and block expensive calls, > provide that as a service, and forget CDR's :-) > > To get a very accurate tally you need the cdr-odbc.sqlite3 plus the > checkin-checkout times which are on a different system. > > Lonnie > > > On May 30, 2015, at 12:06 AM, Michael Knill > <michael.kn...@ipcsolutions.com.au> wrote: > >> Gosh so much searching with very little progress. Im very tempted to add >> more functionality to the existing cdrlog.php. >> >> Regards >> Michael Knill >> >> On 30 May 2015, at 12:36 pm, Michael Knill >> <michael.kn...@ipcsolutions.com.au> wrote: >> >> Hi group >> >> On a different subject, it looks like I am going to pick up a small hotel >> which I will be installing Astlinux. >> Although their requirements are pretty basic, I am concerned about the CDR >> Billing system for charging out calls to their customers. >> >> Does anyone have any recommendations here? >> >> Regards >> Michael Knill Hi Michael, if you figure out something useful from the above, I would also be interested :-), but not for a hotel. I need to get the length of incoming calls to a support hotline for various accounts/projects and send it to an ERP system. Lonnie's No. 2 sounds interesting for that purpose. Michael http://www.mksolutions.info ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org. ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
