Support A2Billing :

provided by Star2Billing S.L.

Support A2Billing :
It is currently Sat Aug 24, 2019 11:16 pm
Hosted Voice Broadcast


All times are UTC




Post new topic Reply to topic  [ 23 posts ]  Go to page Previous  1, 2
Author Message
 Post subject: Balance Not Deducted. . . .
PostPosted: Mon Aug 06, 2007 6:19 am 
Offline

Joined: Sun Jul 29, 2007 5:46 pm
Posts: 21
wcjiang wrote:
OK, finally got it figured out. Ticket closed :-)



Hi Jiang

Can you please let us know that how you were able to resolve the minutes deduction issue ?

I have a similar problem.

The call gets completed successfully and the IVR also comes up with warning messages "31 seconds remaining". The call even drops when past the credit limit.

Most amazingly, the customer balance is not deducted from the database. It shows the same old balance.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Aug 06, 2007 2:36 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
The root of this issue was discovered by Xrg I think [url]http://forum.asterisk2billing.org/viewtopic.php?p=7962#7962[/url]

Starting from that post and following through to both applicable bugs on the asterisk bug tracker you can find that commit #71656 causes this problem.

This problem in my experience affects Asterisk 1.2.18-1.2.23, and perhaps future versions. I've not tested 1.4 at all yet.

I've tried attaching the patch I use to revert this change many ways and my post always gets dropped. Here it is inline:
--- branches/1.2/res/res_agi.c 2007/06/25 18:12:37 71656
+++ branches/1.2/res/res_agi.c 2007/06/22 14:52:18 71065
@@ -1103,7 +1103,7 @@
}
fdprintf(agi->fd, "200 result=%d\n", res);

- return res >= 0 ? RESULT_SUCCESS : RESULT_FAILURE;
+ return res;
}

static int handle_setcallerid(struct ast_channel *chan, AGI *agi, int argc, char **argv)


Top
 Profile  
 
 Post subject:
PostPosted: Tue Aug 07, 2007 10:52 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
Great news everybody!
Asterisk 1.2.24 was just released and according to the changelog it reverts the patch that was causing this issue.

Quote:
2007-07-30 18:40 +0000 [r77782] Tilghman Lesher <[email protected]>

* res/res_agi.c: Revert change in revision 71656, even though it
fixed a bug, because many people were depending upon the (broken)
behavior.


The bug he mentions isn't at all severe:
Quote:
* res/res_agi.c: Issue 10035 - handle_exec returns a result
inconsistent with all of the other AGI commands


Asterisk 1.2 is now in maintenance, so barring any more security issues v1.2.24 will be the last of the 1.2 series.
Sounds like a good time to upgrade :)


Top
 Profile  
 
 Post subject:
PostPosted: Wed Aug 08, 2007 11:55 am 
Offline

Joined: Fri Apr 28, 2006 5:11 am
Posts: 426
i think 1.4.10 should be too.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Mar 20, 2008 3:31 am 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
OK the cost was 0, but how about the duration? If the duration is non-zero then it your rates or offers causing this.

As for finding the other lost call have you tried reconciling the A2Billing CDRs against Asterisk's own CDRs in /var/log/asterisk/cdr-csv/ ?


Top
 Profile  
 
 Post subject:
PostPosted: Fri Mar 21, 2008 6:08 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
I don't like the look of:
Code:
chan_sip.c:12735 handle_response: Remote host can't match request BYE to
call '[email protected]'. Giving up
It may or may not be the root of your problem, but it's certainly not helping. Does the Asterisk CDR for this call show >0 duration? If not this looks like something that will need to be fixed in Asterisk, or at the remote end.

Perhaps enable 'agi debug' whilst you reproduce the fault might give some clues. Also turning up the debug to level 3 in a2billing.conf wouldn't hurt.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Mar 21, 2008 6:47 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
callingcard wrote:
I was unable to find the settings for debug level in a2billing.conf for version 1.3.2
Look harder. There's a setting 'debug = ' in each [agi-confX] section.

Ah, you edited. The answer is simple. You're using AGI() not DeadAGI().


Top
 Profile  
 
 Post subject:
PostPosted: Fri Mar 21, 2008 7:09 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
callingcard wrote:
I think the reason for which i used AGI instead of DeadAGI eas because I was getting a message that this command is deprecated.
For Asterisk v1.2 and v1.4 this message should be harmless. You need to use DeadAGI(), as the installation guide describes, or you will see the symptoms you described.

I'm sure A2Billing will need to be modified to be compatible with Asterisk v1.6 once they've reworked the AGI code fully. This promises to be a major pain to do if my understanding of the changes is correct. :x


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 23 posts ]  Go to page Previous  1, 2
VoIP Billing solution


All times are UTC


Who is online

Users browsing this forum: Google [Bot] and 0 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group