hmm i see what you are saying...
ok 3 questions..
1. on the a2billing callback feature... when they connect (is it just 1 second connect to the server and it will then autocallback.) i know on trixbox, it rings forever, there therefore it does not charge me the outgoing rate (when caling the callback server because it never actualyl connects to the other line it just rings contiunsouly but trixbox sees the CID and that is how it does the callback (so really no charging from carrier on that calll (only voip carrier). does a2billing callback work the same?
2. If i wanted to do callback based on CID, how can i do that in a2billing. Also how do i let customers type in their CID in like a registration thing, so that it automatically sets that up.
3.
jroper wrote:
With this configuration, the CLI of the customer should be delivered to A2Billing so you can authenticate on it.
Bear in mind with this system, you can only bill the B Leg of the call, so the rates will have to include the A Leg costs, so you may want to restrict where a customer can call from using inbound routes.
Joe
as you said in the above quote i dont quite understand "how that works" Plus the way i have the callback setup is based on CID. So that means that when they register for a2billing, the CID they put in, would become a new incoming DID/CID route in trixbox (to allow the callback to initiate) and minutes used would be billed through a2billing.
it seems the way to go is 100% a2billing but im not sure how to setup the CID callback situation where it does not charge me for that outgoing minute from the phone to the server before teh callback part (so the cell comapny does not charge me an outgoing minute), and also how to setup a system where the CID is used in registration.
Thanks so much for your time and comments