Web callback billing problem...

zuuldibo · **Posted:** Wed Feb 13, 2008 4:42 pm

The web callback is working perfect but when the first leg hangs up the second leg appears with 0 minutes 0 euros in the invoice. If I do it the other way, I mean If the second leg hangs up, then the invoice is correct (both legs are charged correctly).

Do you know if this is a bug or maybe I'm missing something...

thanks

stavros · **Posted:** Thu Feb 14, 2008 12:32 am

I think there was a bug fixed in Asterisk pertinent to your problem. Try upgrading to the latest release.
Also this thread might offer some other clues.

zuuldibo · **Posted:** Thu Feb 14, 2008 10:07 am

Thank you stavros but the solution in that post is to downgrade to version 1.3.0.

I think this could be a bug but I don't know. Could anyone try this and see if it is working for you?

stavros · **Posted:** Thu Feb 14, 2008 12:27 pm

zuuldibo wrote:

the solution in that post is to downgrade to version 1.3.0.

No, that's not right. That guy upgraded from v1.2.3 to v1.3.0, and found that fixed his problem.

Quote:

I think this could be a bug but I don't know. Could anyone try this and see if it is working for you?

I just checked a production server running v1.3.1 and both legs were billed correctly:

Code:

21.   2008-02-14 09:56  6xxxxxxxx4  0870xxxxxxx  uk special services  07:05  2xxxxxxxx7  UK_NATIONAL  ANSWER    STANDARD  x.xxx gbp  1.200 gbp  xx.xx%  xxx.xx%
22.   2008-02-14 09:55  6xxxxxxxx4  6xxxxxxxx4   brunei               07:33  2xxxxxxxx7  UK_NATIONAL  ANSWERED  CALLBACK  x.xxx gbp  0.000 gbp  n/a  -100.00%

Added after 1 hours 26 minutes:

Sorry, yeah you're right. He did go from v1.3.1 -> v1.3.0 which seemed to cure it for him. I disagreed it was a regression in v1.3.1 at the time, and for the two servers I've tested on here today I stand by that.
Perhaps there are special circumstances/configuration options that trigger this problem...

zuuldibo · **Posted:** Thu Feb 14, 2008 1:41 pm

Thanks for your help stavros I'm working on it I will try to change some things in my conf files. I will also leave them here so if you see anything strange please tell me. thank you anyway.

extensions.conf

Code:

[a2billing-callback]
exten => _X.,1,Set(AGISIGHUP=no)
exten => _X.,n,DeadAGI(a2billing.php|1|callback)
exten => _X.,n,Hangup

a2billing.conf

Code:

[callback]
; When web call-back is enabled this is the context to sent the call.
context_callback = a2billing-callback

; this is the Extension to redirect the call when the web callback is returned
extension = 1000

; this is the number of seconds to wait before initiating the call back.
sec_wait_before_callback = 10

;Number of seconds before the call-back can be re-initiated from the web page
; to prevent repeated and unwanted calls.
sec_avoid_repeate = 30

; if the callback doesnt succeed within the value below, then the call is deemed to have failed.
timeout = 20

; if we want to manage the answer on the call
; Disabling this for callback trigger numbers makes it ring not hang up.
answer_call = yes


; PREDICTIVE DIALER
; number of calls an agent will do when the call button is clicked
nb_predictive_call = 10

; Number of days to wait before the number becomes available to call again.
nb_day_wait_before_retry = 1

; The context to redirect the call for the predictive dialer
context_preditctivedialer = a2billing-predictivedialer


; When a call is made we need to limit the call duration : amount in seconds
predictivedialer_maxtime_tocall = 5400

; set the callerID for the predictive dialer and call-back
callerid = +3120XXXXXX

; ID Call Plan to use when you use the all-callback mode, check the ID in the "list Call Plan" - WebUI
all_callback_tariff = 1

; Define the group of servers that are going to be used by the callback
id_server_group = 1

; Audio intro message when the callback is initiate
callback_audio_intro = prepaid-callback_intro

krzykat · **Posted:** Thu Feb 14, 2008 4:46 pm

Zu - what version of asterisk are you using?

zuuldibo · **Posted:** Fri Feb 15, 2008 9:32 am

Asterisk 1.2.21.1, I now it isn't the last stable version but I thought this problem was related to the a2b. do you think this could be the reason for my problem?

stavros · **Posted:** Fri Feb 15, 2008 3:23 pm

Definitely. There were hundreds of reports of this problem on this forum for Asterisk v1.2.17-v1.2.24 (I think). I'm surprised you didn't chance upon one of them whilst searching.

nitzan · **Joined:** Fri Feb 15, 2008 2:43 pm **Posts:** 58

Actually, I'm seeing the exact same problem with Asterisk 1.4.17 and A2B 1.3.2...

Not sure if it's configuration on my end or what, but A2B bills the first leg alright, but for some reason decides the second leg didn't connect.

asiby · **Posted:** Fri Mar 07, 2008 1:37 am

I am running Asterisk 1.4.17 and A2Billing 1.3.2 and everything works perfectly. Well, at least, I am not having this problem. So it must be a configuration issue. I might have also compiled PHP in a way that makes things work for me.

nitzan · **Joined:** Fri Feb 15, 2008 2:43 pm **Posts:** 58

Yeah, it was a configuration issue. In the docs for 1.3.2 (INSTALL_AGI.txt) there is an error/typo:

Code:

[a2billing-callback]
exten => _X.,1,AGI(a2billing.php|1|callback)
exten => _X.,n,Hangup

It should be DeadAGI. Changing that fixed the problem apparently.

voipnoy · **Joined:** Sun Nov 25, 2007 2:53 pm **Posts:** 6

Hi to all.

Callback is working in my environment and both legs are being recorded except that the billing increment for the 1st leg is not computing properly.

For example, if I set the call rate and the corresponding call plan to charge the 1st leg with a 1 second billing increment and set the all_calback_tariff in the a2billing.conf to the ID of that callplan, the 1st leg will still be charge on a per minute increment.

provided by Star2Billing S.L.

Web callback billing problem...

Who is online