NO WARRANTY HOW THIS WILL WORK IN YOUR ENVIRONMENT. NOT TESTED ON A PRODUCTION SERVER. Mine is still in testing.
If you have a RightFax Server and did not purchase the Alerting & Monitoring portion, here is a script that will gather RightFax Queue information.
Place the .txt files and access DB in a folder
Places the script in another (I run all scripts out of a standard directory and place logs in another)
Update the PATHS in the script for the log files
If you are using SQL, you will have to change the osql statement, I am running SQLExpress on my RightFax Server
Create a system DSN pointing to the DB called RFAX
create a scheduled task to run every 30 minutes starting at 12:00am for 24HRs every day (use local admin account to run under).
Here is how the script works:
SQL is queried for a status (I dug into the SQL scripts within RighthFax to identify what should be queried). I group these by the creationtime and write to the TXT file.
I then perform a count of the failed and update the DB and TXT file with the Date,Time,Count,& Total Pending values. The Date and Time stamp is the earliest value that came from the osql command. The COUNT value is related to the Date/Time stamp.
When the alert runs the next time I compare the OLD results against the NEW results. If the Date,time,&Count (for the earliest # of pending) match I know that there is an error. So I write to the Eventlog.
If the scan does not match, but the TotalCount has increased and is greater than 10 I also error, this could mean that the earliest pending faxes went, but the over Total count has increased. (This is just incase phoneline(s) are broken resulting in longer than normal queue lengths.)
I have an APM the runs and looks for the eventlog error that I am posting to the system.