I previously suggested you search for 'connection failed', yet you haven't described following any of the advice in any of the threads related to your question. Your Apache log files may well give you a clue as to where your problem really lies. I'm guessing the database credentials are wrong.
bruce wrote:
My console does not show a request from a2billing.conf for authentication on a reload
The section of the debug log you quoted shows that a reload had just taken place (Parsing xxx...) and that two different users had just been using the AMI (admin and phpconfig). Surely one of these users is used by your A2B install?
I notice you're defining the user 'myasterisk' in both manager.conf and manager_additional.conf which certainly won't be helping. You claim your manager_additional.conf includes the line "#include a2billing.conf" which would definately cause problems. You either need to spend some time educating yourself (primarily from voip-info.org) or be
much more careful with your configuration changes.
bruce wrote:
I still get : Connection failed
This is unrelated to being able to logon to the AMI.
bruce wrote:
Funny thing is that A2BCustomer_UI works fine even though it is using the same parametere that are set for both A2Billing_UI and A2BCustomer_UI in a2billing.conf.
The customer UI doesn't use the AMI at all. There are only two situations (that I'm aware of) in which A2B needs to use AMI: the admin UI uses it to issue a 'reload' command when you've updated SIP/IAX friends, and the AGI uses it for callback calls. In other words you've been looking in the wrong place.
If you're considering using A2B as more than a hobby or toy I strongly suggest you employ someone who knows what they're doing.