Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Call Accounting Mate Q&A / Re: CA Mate Genarating Reports Very Slow
« Last post by tboggs13 on October 05, 2010, 08:01:57 PM »
No this product is not dead. We have been working on a new release to this product for the past year. We expect it to be available in the new year!

So, another year and no major upgrade. Last bug fix released per your Version History was 11/2009, which actually occurred before your quote. I realize you still have a couple of months to produce the new version, but I won't get my hopes up since I have been waiting for 4 years for a major overhaul of the software. As you can see in this thread, you have been promising that major new version every year for the past four years and have not delivered.

That is pretty much why you lost me as a customer.
22
Call Accounting Mate Q&A / All greetings!
« Last post by lorneenue on September 26, 2010, 05:19:06 PM »
All greetings! I the first day at a forum. How are you?
23
Starting with version 0.6 (released 30 Aug 2005), Asterisk-MySQL driver allows to be configured to take billable extension from various sources and determine call direction from channels used to make the call.

Common steps
To configure driver properties following steps are necessary:
- open Configuration/PBX Communication page
- activate Driver tab
- select Asterisk-MySQL in the PBX Driver field
- check that there is Version 0.6 in the driver comments (in case it's not please download and install the latest version of the driver from our support site)
- activate Properties tab to get access to the driver properties

Configuring billable extension source
- to configure source of the billable extension 'Take billable extension from' field is used
- this field has 4 options:
  • Call Source - driver uses 'src' and 'dst' fields to fill user extension for outgoing and incoming calls
  • Channel - driver parses 'channel' and 'dstchannel' fields to extract user extension from there
  • Account Code - driver uses 'accountcode' field to fill user extension
  • Account/Source - driver uses 'accountcode' field to fill user extension. In case the 'accountcode' field is empty driver uses 'src' and 'dst' fields for this purpose

Configuring call direction
Driver determines call direction by examining the 'channel' and 'dstchannel' fields (this requires to setup which channels are connected to the PSTN, otherwise known as COs or Trunks in other PBXs). Knowing of what channel is connected to PSTN the driver decides of what is the call direction depending of whether PSTN appears in 'channel' or 'dstchannel' field. Thus before using the driver you need to list all channels connected to PSTN.

Driver uses a partial match when searching the channel names, i.e. it compares all symbols of the defined channel name against captured string from the string first symbol to the defined name length and ignores rest of the captured string, thus Zap/1-  will match Zap/1-1, Zap/1-2 etc. Trailing dash in the channel name pattern is necessary to avoid situations like when Zap/1 will match both Zap/1-1 and Zap/11-1. Exact pattern for channel names depends on the way your Asterisk reports the channels.

There are 2 options (2 places) to list these channels:
- CO/Trunk lines lookup table
- Driver settings on the Properties tab
Both options are equal and it's question of convenience which one you will choose (e.g. if you already have CO/Trunk lookup table filled you may prefer the 1st option).

Using CO/Trunk lines lookup table
- use Settings/Line Numbers page to fill and manage list of channels connected to PSTN
- in the driver settings (Configuration/PBX Communication Properties tab) select 'CO/Trunk table' in the Take PSTNs from' field
- every time you change something on the Settings/Line Numbers page you will have to reload the driver by opening Configuration/PBX Communication page and clicking the Save button there

Using the driver settings
- use Configuration/PBX Communication Properties tab to manage list of channels connected to PSTN
- select 'Driver Settings' in the Take PSTNs from' field, this enables PSTNs section at the bottom of the tab
- enter channel name in the New PSTN field in the section and press '>>' button to add the channel to the list; alternatively you may use <Ctrl>+<Enter> keys to add the channel
- select group of channels in the list using mouse and <Ctrl> and <Shift> keys and press '<<' button to remove channel names from the list
- after editing the list press Save button on the page to save the settings


Thanks for the info.Version you mentioned above I already used.
24
Asterisk Integration / Re: compiling on asterisk 1.6.2.11
« Last post by mwelch on September 07, 2010, 10:28:48 AM »
Can someone help me with this?  TIA
25
Asterisk Integration / compiling on asterisk 1.6.2.11
« Last post by mwelch on August 26, 2010, 06:34:12 AM »
Running through the instructions to install on our asterisk box to feed Call Accounting Mate, we get errors on the gmake.  This asterisk server is a yum install of asterisk on a Centos 5.4 OS.

Here's the errors we get:
[root@dtw-pbxprod01 Asterisk]# gmake
cdr_camate.c:27:30: error: asterisk/channel.h: No such file or directory
cdr_camate.c:28:26: error: asterisk/cdr.h: No such file or directory
cdr_camate.c:29:29: error: asterisk/module.h: No such file or directory
cdr_camate.c:30:29: error: asterisk/config.h: No such file or directory
cdr_camate.c:31:30: error: asterisk/options.h: No such file or directory
cdr_camate.c:32:29: error: asterisk/logger.h: No such file or directory
cdr_camate.c:33:26: error: asterisk/cli.h: No such file or directory
cdr_camate.c:34:27: error: asterisk/lock.h: No such file or directory
cdr_camate.c:35:28: error: asterisk/utils.h: No such file or directory
cdr_camate.c:95: warning: data definition has no type or storage class
cdr_camate.c:95: warning: type defaults to ‘int’ in declaration of ‘AST_MUTEX_DEFINE_STATIC’
cdr_camate.c:95: warning: parameter names (without types) in function declaration
cdr_camate.c: In function ‘cache_add’:
cdr_camate.c:121: warning: implicit declaration of function ‘ast_mutex_lock’
cdr_camate.c:121: error: ‘cache_lock’ undeclared (first use in this function)
cdr_camate.c:121: error: (Each undeclared identifier is reported only once
cdr_camate.c:121: error: for each function it appears in.)
cdr_camate.c:124: warning: implicit declaration of function ‘ast_mutex_unlock’
cdr_camate.c: In function ‘cli_cdr_status’:
cdr_camate.c:135: error: ‘RESULT_SUCCESS’ undeclared (first use in this function)
cdr_camate.c:138: warning: implicit declaration of function ‘ast_cli’
cdr_camate.c:146: error: ‘cache_lock’ undeclared (first use in this function)
cdr_camate.c: At top level:
cdr_camate.c:165: error: variable ‘cdr_status_cli’ has initializer but incomplete type
cdr_camate.c:166: error: extra brace group at end of initializer
cdr_camate.c:166: error: (near initialization for ‘cdr_status_cli’)
cdr_camate.c:166: warning: excess elements in struct initializer
cdr_camate.c:166: warning: (near initialization for ‘cdr_status_cli’)
cdr_camate.c:167: warning: excess elements in struct initializer
cdr_camate.c:167: warning: (near initialization for ‘cdr_status_cli’)
cdr_camate.c:168: warning: excess elements in struct initializer
cdr_camate.c:168: warning: (near initialization for ‘cdr_status_cli’)
cdr_camate.c:171: warning: excess elements in struct initializer
cdr_camate.c:171: warning: (near initialization for ‘cdr_status_cli’)
cdr_camate.c: In function ‘load_config’:
cdr_camate.c:181: warning: implicit declaration of function ‘ast_load’
cdr_camate.c:181: warning: assignment makes pointer from integer without a cast
cdr_camate.c:185: warning: implicit declaration of function ‘ast_variable_browse’
cdr_camate.c:185: warning: assignment makes pointer from integer without a cast
cdr_camate.c:187: warning: implicit declaration of function ‘ast_log’
cdr_camate.c:187: error: ‘LOG_WARNING’ undeclared (first use in this function)
cdr_camate.c:190: warning: implicit declaration of function ‘ast_variable_retrieve’
cdr_camate.c:190: warning: assignment makes pointer from integer without a cast
cdr_camate.c:192: warning: implicit declaration of function ‘ast_true’
cdr_camate.c:198: warning: assignment makes pointer from integer without a cast
cdr_camate.c:202: warning: assignment makes pointer from integer without a cast
cdr_camate.c:206: warning: assignment makes pointer from integer without a cast
cdr_camate.c:211: warning: assignment makes pointer from integer without a cast
cdr_camate.c:215: warning: assignment makes pointer from integer without a cast
cdr_camate.c:221: warning: assignment makes pointer from integer without a cast
cdr_camate.c:226: warning: implicit declaration of function ‘ast_destroy’
cdr_camate.c:228: error: ‘LOG_DEBUG’ undeclared (first use in this function)
cdr_camate.c: In function ‘open_log’:
cdr_camate.c:240: error: storage size of ‘ahp’ isn’t known
cdr_camate.c:242: warning: implicit declaration of function ‘ast_gethostbyname’
cdr_camate.c:242: warning: assignment makes pointer from integer without a cast
cdr_camate.c:244: error: ‘LOG_ERROR’ undeclared (first use in this function)
cdr_camate.c:247: error: invalid use of undefined type ‘struct sockaddr_in’
cdr_camate.c:247: error: dereferencing pointer to incomplete type
cdr_camate.c:247: error: invalid use of undefined type ‘struct sockaddr_in’
cdr_camate.c:248: error: invalid use of undefined type ‘struct sockaddr_in’
cdr_camate.c:248: warning: implicit declaration of function ‘htons’
cdr_camate.c:249: error: invalid use of undefined type ‘struct sockaddr_in’
cdr_camate.c:257: error: invalid application of ‘sizeof’ to incomplete type ‘struct sockaddr_in’
cdr_camate.c:240: warning: unused variable ‘ahp’
cdr_camate.c: In function ‘ack_log’:
cdr_camate.c:284: error: array type has incomplete element type
cdr_camate.c:286: error: ‘POLLIN’ undeclared (first use in this function)
cdr_camate.c:289: warning: implicit declaration of function ‘poll’
cdr_camate.c:291: error: ‘LOG_ERROR’ undeclared (first use in this function)
cdr_camate.c:293: error: ‘LOG_WARNING’ undeclared (first use in this function)
cdr_camate.c:298: error: ‘option_verbose’ undeclared (first use in this function)
cdr_camate.c:299: warning: implicit declaration of function ‘ast_verbose’
cdr_camate.c:306: error: ‘LOG_DEBUG’ undeclared (first use in this function)
cdr_camate.c:284: warning: unused variable ‘s’
cdr_camate.c: In function ‘send_log’:
cdr_camate.c:327: error: ‘option_verbose’ undeclared (first use in this function)
cdr_camate.c:331: error: ‘LOG_ERROR’ undeclared (first use in this function)
cdr_camate.c: At top level:
cdr_camate.c:346: warning: ‘struct ast_cdr’ declared inside parameter list
cdr_camate.c:346: warning: its scope is only this definition or declaration, which is probably not what you want
cdr_camate.c: In function ‘cdr_post’:
cdr_camate.c:370: error: invalid application of ‘sizeof’ to incomplete type ‘struct ast_cdr’
cdr_camate.c:377: error: dereferencing pointer to incomplete type
cdr_camate.c:378: error: dereferencing pointer to incomplete type
cdr_camate.c:379: error: dereferencing pointer to incomplete type
cdr_camate.c:380: error: dereferencing pointer to incomplete type
cdr_camate.c:381: error: dereferencing pointer to incomplete type
cdr_camate.c:382: error: dereferencing pointer to incomplete type
cdr_camate.c:383: error: dereferencing pointer to incomplete type
cdr_camate.c:384: error: dereferencing pointer to incomplete type
cdr_camate.c:385: error: dereferencing pointer to incomplete type
cdr_camate.c:386: error: dereferencing pointer to incomplete type
cdr_camate.c:387: error: dereferencing pointer to incomplete type
cdr_camate.c:388: error: dereferencing pointer to incomplete type
cdr_camate.c:389: error: dereferencing pointer to incomplete type
cdr_camate.c:390: error: dereferencing pointer to incomplete type
cdr_camate.c:391: warning: implicit declaration of function ‘ast_cdr_disp2str’
cdr_camate.c:391: error: dereferencing pointer to incomplete type
cdr_camate.c:392: warning: implicit declaration of function ‘ast_cdr_flags2str’
cdr_camate.c:392: error: dereferencing pointer to incomplete type
cdr_camate.c:393: error: dereferencing pointer to incomplete type
cdr_camate.c:394: error: dereferencing pointer to incomplete type
cdr_camate.c:396: warning: format ‘%s’ expects type ‘char *’, but argument 18 has type ‘int’
cdr_camate.c:396: warning: format ‘%s’ expects type ‘char *’, but argument 19 has type ‘int’
cdr_camate.c:396: warning: format ‘%s’ expects type ‘char *’, but argument 18 has type ‘int’
cdr_camate.c:396: warning: format ‘%s’ expects type ‘char *’, but argument 19 has type ‘int’
cdr_camate.c:398: error: ‘LOG_WARNING’ undeclared (first use in this function)
cdr_camate.c:409: error: ‘LOG_ERROR’ undeclared (first use in this function)
cdr_camate.c:421: error: ‘cache_lock’ undeclared (first use in this function)
cdr_camate.c: In function ‘load_module’:
cdr_camate.c:453: error: ‘LOG_DEBUG’ undeclared (first use in this function)
cdr_camate.c:459: warning: implicit declaration of function ‘ast_cdr_register’
cdr_camate.c:461: error: ‘LOG_ERROR’ undeclared (first use in this function)
cdr_camate.c:463: warning: implicit declaration of function ‘ast_cli_register’
cdr_camate.c:464: warning: implicit declaration of function ‘ast_mutex_init’
cdr_camate.c:464: error: ‘cache_lock’ undeclared (first use in this function)
cdr_camate.c: In function ‘unload_module’:
cdr_camate.c:471: warning: implicit declaration of function ‘ast_cli_unregister’
cdr_camate.c:472: warning: implicit declaration of function ‘ast_cdr_unregister’
cdr_camate.c:473: warning: implicit declaration of function ‘ast_mutex_destroy’
cdr_camate.c:473: error: ‘cache_lock’ undeclared (first use in this function)
cdr_camate.c: In function ‘key’:
cdr_camate.c:495: error: ‘ASTERISK_GPL_KEY’ undeclared (first use in this function)
gmake: *** [cdr_camate.o] Error 1
[root@dtw-pbxprod01 Asterisk]#

Tared the files in c:\bill\asterisk then moved to /usr/src/asterisk (this folder was created for this these files)

I have attempted this on two comparable asterisk servers with the same result for both.

Appreciate any help getting this compiled.  Thanks
26
Call Accounting Mate Q&A / Re: Answer Position Reporting
« Last post by jschneider on August 10, 2010, 10:16:57 AM »
Is there anyone here to answer questions???
27
Call Accounting Mate Q&A / Re: Answer Position Reporting
« Last post by Administrator on August 09, 2010, 01:39:59 PM »
Most of the drivers pre-packaged with the Call Accounting Mate software will report the duration of the call (either the talk time or total connect time of a call).  Please contact our support team at support@callaccounting.ws for additional options that may be available to you.  Please note, the ring time/hold time before the receptionist takes the call must be available in the CDR generated from your phone system.
28
Call Accounting Mate Q&A / Answer Position Reporting
« Last post by jschneider on August 06, 2010, 11:49:24 AM »
Is there a way to set up a report that monitors how long it takes the receptionist to answer calls?
29
Call Accounting Mate Q&A / Re: Com port problems
« Last post by Administrator on August 06, 2010, 10:53:29 AM »
Thank you for your inquiry.  If your phone system is delivering CDR data to a serial port on the PC hosting your Call Accounting Mate, you will be able to view the data with HyperTerminal without the CAM software running.  Raw data collection with Call Accounting Mate will still occur even if an incorrect CDR driver is selected.  The data driver will allow you to process your call records once they are collected with the Call Accounting Mate software.

Our support team will be contacting you shorty to provide additional assistance.
30
Call Accounting Mate Q&A / Re: Taskbar icon constantly red all of a sudden?
« Last post by Administrator on August 06, 2010, 09:05:24 AM »
A "Purge Calls" option is available under the Maintenance menu.  Here, you can select the date(s) to purge data from.  Please note, you may wish to make a backup of your call data beforehand.  Once data is purged from your database you may not be able to recover it without a backup.

Please note, in a correction to the post above, the c:\bill\calls.dat file is the database file that will grow with increased call volume.  The bill.exe is the executable; this should not vary in size.

If you require furhter assistance please contact our support team at support@callaccounting.ws
Pages: 1 2 [3] 4 5 ... 10