When we have the alarm when try to make external calls: "Bill pool is full" we thought that the CDR server is full but in some cases can happens that the connection between CDR server and the PBX is lost, the PBX save some files but when this is full we have this alarm.
Follow the next procedure to determinate this:
1. Get the CDR logs and analyse them.
2. The CDR records show that the application did not have access to the C: \ Windows \ NOT FOUND directory which caused the connection to abort.
To ensure that the CDR works correctly we must ensure the access of the application and the read / write permissions on disk C and that the space in it is sufficient, annex evidence as follows:
3. You can also see in the CDR.log that the path where the CDRs were written could not be opened, the client's computer path where we can find the .bill files is: C: \ Bill \ CurFile \ 172.17.107.23 \ date \ filename
4. We need to be sure about the connection between the U19 and the CDR server is not blocked by the firewall or any other tool and that the port is open and established, we validate the connection status with the following command:
netstat -an | findstr X -- > where X is the port number we are looking for 2020 is the port used for the connection.
The port should be on ESTABLISHED, otherwise it would be blocked by the firewall.
5. The next command can be use as Workaround to remove the restriction even though the billpool was full was: config billpoolfull callrestrict switch NO
6. After validating the connection with the show billserver state command and verifying that the connection is correct, the configuration was returned to default.
In this particular case, was needed verify the server in order to know why the server is disconnecting from the PBX.
