provided by Star2Billing S.L.

You mean, Your phone not hang up?

You have to hang up your phone by yourself.

Some carriers can cause this problem.

When you hangup, they have another go, and try one their failover routes, and as such, the caller can end up with 3 callbacks.

I find that creating a dialplan to allow asterisk to ring 2 or 3 times, then hang up, rather than hanging up immediately, circumvents this problem

Joe

Have a similar problem, same carrier (Vodafone Romania)
But I don't even see a hangup in the log, the last thing I see is:
== Spawn extension (a2billing-callback-cid, _X., 1) exited non-zero on 'SIP/40356123456-01fc4fc0'

But the callback works fine.

if this is a carrier issue, then I guess there isn't much we could do.
I will try to find some other carriers to do some tests and tomorrow I can test some austrian carriers. Last time I used callback was in Spain with Orange last year. Not sure which a2b Version I had installed, but that worked as expected.

Pls try,

answer_call = Yes

in associated AGI-CONF of callback trigger


Regards,
Nuiz (Asterisk, A2Billing Thailand)

Dear callingcard,

I'm getting same issue with you. For the short term, I tell customer to hang up his phone after hear busy signal.

I think if we change hangup cause code from "603 declined" to "486 busy here". We can solve this issue. But I don't khow how to.

I looked at file "A2Billing.php" as Joe told. I found this script call "$agi->hangup();" function. I don't know where it is? I'm not programmer.

Regards,
Nuiz

Hello,

we solved this problem on our a2billing 1.8.1 and asterisk 1.4.21
answer_call=No
and sending hangup code 38
exten => _X.,n,Hangup(38)

Hope this helps

Greetings
http:www.bestcallshop.com