provided by Star2Billing S.L.

Dear fellow users,

I have came across a problem which is either a bug or something strange on my installation. I noticed that calls that are unanswered / canceled or wrongly dialed gets billed when I connect A2Billing to another Asterisk based switch.

All works as expected (unanswered / canceled) when connecting to expensive other hardware switches, but as soon as the call is passed to an Asterisk based switch they are wrongly billed.

I notice a setting in a2billing.conf called "answer_call", what is this for?

ANY suggestions will be much appreciated.

Thanks in advance

R

I'm guessing the remote Asterisk server is answering the call before dialling the B-leg for some reason. You may find you're being billed from before ringing starts. Time it and find out. Complain to your 'carrier' about false answer and overcharging.

I use the answer_call setting in A2B to avoid the above issue when A2B is providing wholesale billing. It won't help you in your current predicament.

Thanks allot for your quick response!

Please elaborate on "I use the answer_call setting in A2B to avoid the above issue when A2B is providing wholesale billing. It won't help you in your current predicament."

If the 'carrier' is also using A2Billing is there a solution? IE, if I hook one A2Billing Asterisk switch to another A2billing Asterisk switch, what is the best way to handle this?

PS: The carrier doesn't know how to change this!

Regards

R

Yes, that A2B needs to be correctly configured for wholesale if that's what it's doing. answer_call, play_audio, number_try are all settings that are related.

Find a better carrier so you can cease supporting a 'carrier' with no interest in providing a quality service and lacking even a basic understanding of telecoms.

Again thanks allot for your quick response!

Please provide me with the correct values for answer_call, play_audio, number_try etc. if I want to connect one A2B to another A2B

Regards

R