Issue with data written to call_log table
Posted: Wed Jul 22, 2009 3:38 pmOur organisation is testing ViciDialNOW 1.3 to see if it meets our needs. We oroginally had a group of agents using a standard Asterisk server and custom SIP softphones to manually call numbers from a spreadsheet.
We have now moved these agents onto a ViciDialNOW server but they are still doing "spreadsheet dialing", i.e. not using the ViciDial Agent frontend to make calls. (This approach is due to the custom softphone.) In other words, they have a phone registered on the ViciDial server, but no user accounts.
Because of the lack of user accounts, it's obviously not possible to use the standard ViciDial reporting, so I've turned to the base MySQL tables. One of the most interesting is the call_log table, which appears to hold information about all calls made on the server.
Unfortunately, the data in call_log isn't tying up with what the agents claim. Initially I thought the agents were at fault, but after examining the table more closely I've found instances where there is very obviously bogus data being written; for example, some of the rows have the "extension" field set to the IP address of the ViciDial server...
Posted below is the first line of the dialplan we're using to register our Carrier in ViciDial. As you can see, it does trigger the call_log script defined in FastAGI.pl:
exten => _0.,1,AGI(agi://127.0.0.1:4577/call_log)
So I'd just like to know: is this expected behaviour given the circumstances? In other words, will ViciDial's call logging be accurate as long as you have the correct line in our dialplan, or are there no guarantees if the software is being used in a "bastardised" manner such as this? Or am I just using the wrong script?
Using ViciDialNOW 1.3 (ViciDial 2.0.5/vicidial.php 90323-1554).
We have now moved these agents onto a ViciDialNOW server but they are still doing "spreadsheet dialing", i.e. not using the ViciDial Agent frontend to make calls. (This approach is due to the custom softphone.) In other words, they have a phone registered on the ViciDial server, but no user accounts.
Because of the lack of user accounts, it's obviously not possible to use the standard ViciDial reporting, so I've turned to the base MySQL tables. One of the most interesting is the call_log table, which appears to hold information about all calls made on the server.
Unfortunately, the data in call_log isn't tying up with what the agents claim. Initially I thought the agents were at fault, but after examining the table more closely I've found instances where there is very obviously bogus data being written; for example, some of the rows have the "extension" field set to the IP address of the ViciDial server...
Posted below is the first line of the dialplan we're using to register our Carrier in ViciDial. As you can see, it does trigger the call_log script defined in FastAGI.pl:
exten => _0.,1,AGI(agi://127.0.0.1:4577/call_log)
So I'd just like to know: is this expected behaviour given the circumstances? In other words, will ViciDial's call logging be accurate as long as you have the correct line in our dialplan, or are there no guarantees if the software is being used in a "bastardised" manner such as this? Or am I just using the wrong script?
Using ViciDialNOW 1.3 (ViciDial 2.0.5/vicidial.php 90323-1554).