provided by Star2Billing S.L.

Hello everyone

I have installed the version 1.3.3 of A2billing.

This worked well, as long as the call is answered on the other side, if timbre and nobody answered, usually comes out a tape recorder asking to leave a voice message. But in my case when I called through a2billing not be heard answering, until he was fired because supposedly already left your message, and clear, that call costs and tariffs.

When using the same line calling directly with an annex, if we play the recorder from the beginning, so my provider is fine.

a2billing.conf he set in the values of "answer_call" "NO" and extensions.conf I removed the command "Answer"

Any idea?

Did you carrier bill you for this call? If so, the false answer is coming from them.
The only instance in which A2B will bill a call is when the carrier shows it was answered.

I agree that a2billing bill only when the carrier says so.

But what happens is that after stamp and nobody answered the other side, the recorder start talking and invite you leave a voice message. But the caller, not listening to the voice recorder, and so the second pass and to cut the call is billed.

When I called directly with the asterisk, if I hear the voice of the recorder from the beginning, so I think I set something in a2billing.

Here you send the reports to the CLI asterisk. In the last line you can see an "answer", incidentally, from beginning to answer is that a2billing bill. but the caller did not hear anything.



a2billing.php: file:Class.RateEngine.php - line:1037 - app_callingcard: CIDGROUPID='-1' OUTBOUND CID SELECTED IS '0'.
-- AGI Script Executing Application: (Dial) Options: (SIP/user/XXXXXXX|120|HLrCR(2147483647:61000:00000))
-- Called user/XXXXXXX
-- SIP/user-081ba110 is making progress passing it to SIP/2708-081b7e28
CENTRAL*CLI>
CENTRAL*CLI>
[Sep 18 16] NOTICE[2980]: chan_sip.c:15092 handle_request_subscribe: Received SIP subscribe for peer without mailbox: 2009
-- SIP/user-081ba110 answered SIP/2708-081b7e28

Added after 1 hours 30 minutes:

It found the solution, and if I leave here for someone else to what's happening
same.

The problem was that by having activated reversing polarity,
a2billing listened users a false ring. But removing the
option "r", the parameter of a2billing.conf has dialcommand_param
solved.

Are you saying that having the dial parameter "r" in the dial, that you got billed improperly, and when you removed it, that it was OK ?