By going at large, I mean for instance, having many A2Billing AGI on different boxes connected to a main box containing a2billing and the database. When scheduling a callback from any of the remote host, the a2billing AGI does is in a way that consider the IP of the server as being 'localhost'. This will instruct the main box to trigger the callback locally instead of sending it to the proper server who has requested the callback in a first place.
The guilty code has been identified in A2Billing's AGI script at line 511
$server_ip = 'localhost';
I believe that the variable $server_ip should get his value from a configured parameter. This way, it would be set to a string (host name, IP, or domain name) that can be effectively used to contact the box from another server.