provided by Star2Billing S.L.

one thing I have noticed is that the file :
/var/lib/pgsql/data/pg_hba.conf


does not take :

tcpip_socket = True


And that is to be added to the file. Whenver I try to add it then postgresql won't restart. If I remove it then it restarts. This is the only thing that I have been missing out of the manual.

The install guide asks you to ensure that directive is in postgres.conf, not pg_hba.conf.

Yes, my mistake. But still the file does not contain any tcpip socket variable. I do see the port variable and it can be uncommented. I tried adding tcpip_socket=True but then postgres fails to start.

Added after 8 minutes:

But, since we are on the topic of gp_hba file then this is what the end of file looks for me after the alteration:



# "local" is for Unix domain socket connections only
local all all ident sameuser
# IPv4 local connections:
host all all 127.0.0.1/32 ident sameuser
# IPv6 local connections:
host all all ::1/128 ident sameuser

local all all trust
host all all 127.0.0.1 255.255.255.255 trust
host all all 192.168.0.15 255.255.255.255 trust



Shouldn't I comment the "ident sameuser" lines? all three of them? As the file is read the last three lines will be considered to process if I am not wrong !!! ???

I wasn't previously aware of this, but it seems the tcpip_socket directive has been removed in the Postgres 8 series. v8.0.13 is listening on TCP just fine here without it:The Postgres man page indicates that listen_addresses now controls whether or not it listens on TCP.

That's entirely up to you. It's your database server, and you get to choose who/what connects to it. They're not necessary for A2B, assuming you have added a valid Postgres user correctly configured for A2B to pg_hba.conf.

I had the same problem in mysql. I guess its database permassion,
try this

GRANT ALL PRIVILEGES ON mya2billing.* TO 'username'@'localhost' IDENTIFIED BY 'password' WITH GRANT OPTION;
GRANT ALL PRIVILEGES ON asteriskcdrdb.* TO 'username'@'localhost' IDENTIFIED BY 'password' WITH GRANT OPTION;
GRANT ALL PRIVILEGES ON asterisk.* TO 'username'@'localhost' IDENTIFIED BY 'password' WITH GRANT OPTION;
flush privileges;
\q

it should work

You are quiet right the problem here is in deed mysql db permissions. I suggest this should be a guide to other users.
Wbr
Lu