Isofax on Linux installation - bet 4

After removing them from Unix with the rm command you’ll also need to change the fax_status table and flip their status from P (pending) to S (sent).
Remove any ‘old’ pending faxes As seen from the Fax Status web page
Sign on to SQLPLUS to Live or Train as username of ccdba/ccnulls
Then run this SQL statement:
update ccdba.fax_status set complete_date = SYSDATE where status = 'P';
update ccdba.fax_status set status_detail = 'removed from isofax queue, terminated' where status = 'P';
update ccdba.fax_status set status ='S' where status = 'P';
This will change those stuck in the queue to think they’ve been sent, but they’ll have a terminated msg. If these faxes were sent while the web.xml file was missing the fax.war they will ALWAYS remain in Pending status. So run the above the SQL commands to remove these from showing.
WARNING Do NOT hit F5 refresh while on the Fax Status web page. Always close it down and re-enter from the main page.
It will send multiple copies of the same ‘failed’ fax if you hit F5 –refresh while on the fax status page.
If you click on the “failed faxes” tab and then back to the “all faxes” tab then the dupe problem goes away. Either that, or simply close down the webpage and re-launch it a few minutes later, so long as you don’t use F5-Refresh.
However, if faxing is working properly but the status is not changing and you have verified all your setup and went through all the KB’s, we have seen at one customer site that a change to the brick, was the issue. What was changed/corrected is shown below.
Status would not change, but faxing is up and everything looks up.
The problem was the hostname definition and host file configuration.
I fixed /etc/sysconfig/network.
[isofax@satx-hec-isof ~]$ more /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=satx-hec-isof <- removed the fully qualified definition
GATEWAY=10.20.13.1
[isofax@satx-hec-isof ~]$
I fixed /etc/resolv.conf
search baptisthealth.org <- added
search satx.vhs.net
domain satx.vhs.net <- added
nameserver 172.31.64.252
nameserver 172.31.64.41
fixed /etc/hosts. Localhost was commented out and CANNOT be. Also fixed the satx-hec-isof.satx.vhs.net line
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost <- uncommented
10.20.13.127 satx-hec-isof.satx.vhs.net satx-hec-isof <- fixed by removing baptisthealth.org and adding the satx.vhs.net entry
Knova 56615
Issue
SYMPTOM:
User tries to test fax from the fax admin page and gets the following error. Â“The test fax could not be generated or submitted to the HA faxing service; please check the logs for additional information."
PROBLEM:
The problem as it states is the 'INF.SENDFAX_TABLE_AIUDR1' trigger is invalid. This trigger actually needs disabled.
ERRORMSG:
In the HEC brick log you see something like below.
124327.127:0000:SE:ORA-04098: trigger 'INF.SENDFAX_TABLE_AIUDR1' is invalid and failed re-validation
124327.127:0000:SE:ORA-06512: at "SYS.DBMS_AQIN", line 345
124327.127:0000:SE:ORA-06512: at "SYS.DBMS_AQIN", line 1335
124327.127:0000:SE:ORA-06512: at line 1
FIX
Log into the database as ADF/ADFPAZZ and run
ALTER TRIGGER INF.SENDFAX_TABLE_AIUDR1 DISABLE;
Unsupported modem message As seen from the view_fax_service file
IsoFax server info, last update Wed Mar 12 12:41:21 2008
Line Model Usage Status
---- ----- ----- ------
/dev/tty0 Unknown SEND/REC DOWN: UNSUPPORTED MODEM
/dev/tty1 Unknown SEND/REC DOWN: UNSUPPORTED MODEM
You can update your MODEMS.info file to specify the modem and
$ more MODEMS.info
# MODEMS.info -- modem and serial port delclaration/configuration
[/dev/tty0] # Device declaration, can be full path
speaker_on = always # To hear dialtone, etc.
modem_type = multitech # force acceptance of modem
[/dev/tty1] # Device declaration, can be full path
speaker_on = always # To hear dialtone, etc.
modem_type = multitech # force acceptance of modem
To find out more information, we'll have to turn on faxd and faxinfod debug mesages to figure out what's going wrong.
Do this as the Isofax user from the ISOFAXHOME dir.
% cp TRACES.proto TRACES
% vi TRACES
Now un-comment the line which begins # faxd and make another line just like it, changing faxd to faxinfod .
Then restart faxd wait at least 2 minutes, then review both
$ISOFAXHOME/work/trace_faxd and $ISOFAXHOME/work/trace_faxinfod
Pete Harris at Bristol Group may be needed to review these files.
The Fax Report flow starts on the brick/application, is passed to the Unix SMP server to send the fax to the Isofax service located in the /u/isofax directory and finally back to the brick to update the status.
The fax log files can be found:
On the Unix SMP server, under hc account, fax service level:
/u//apps/fax/var/log/makePdf.log [process 2]
/u//apps/fax/var/log/sendFax.log [process 4 – fax process only] On the Unix SMP server, under isofax account:/u/isofax/work/fax_log
|