FaxBack NET SatisFAXtion 8.6 - Manual - Manual (Page 25)

2 – Server Administration NET SatisFAXtion 8.6 Manual 25
These fax cards are configured in Re-Detect Fax Devices.
2.2.5
Dialogic Brooktrout TR1034
Dialogic Brooktrout TR1034 cards are supported by NET SatisFAXtion using the
bos_man_setup utility. No additional driver software is required.
Please see the NET SatisFAXtion 8.6 Brooktrout Hardware Installation Guide
online at
http://www.faxback.com/docs for detailed instructions on installing
NET SatisFAXtion with TR1034 hardware.
2.2.6
Dialogic Eicon Diva Server
Dialogic Eicon Diva Server cards are supported by NET SatisFAXtion as a Class 1
device. See the NET SatisFAXtion 8.6 Server Installation Guide - New Install
online at
http://www.faxback.com/docs for instructions on installing NET
SatisFAXtion with Diva Server hardware.
After the install, in order to enable DID/DNIS collection, the initialization string
for each port must be updated.
[HKEY_LOCAL_MACHINE\Software\FaxBack\Class1\PORTNAME]
“init_string”
Append “ #CID=5 ” to the value of “ init_string ”.
2.3
Services and Monitoring
2.3.1
Internet Connectivity Requirements
Due to Microsoft signature verification requirements, services may fail to load if
the fax server is behind a proxy server, certain kinds of firewalls or has limited
Internet connectivity.
When the Microsoft .NET Framework prepares to load a signed service (or any
other signed application), it must first connect to
http :// crl .verisign.net to
determine if the signing certificate has been revoked. If the DNS lookup of
crl.verisign.net fails, it will assume the machine has no Internet connectivity
and will skip the certificate verification process. If the DNS lookup succeeds,
Windows will try to connect to it via HTTP and download the CRL. On machines
with limited Internet connectivity this is where the service loading process fails:
the HTTP timeout period is longer than the service loading timeout. This in
effect makes it impossible to load the service.
There are two resolutions to this problem.
Disable DNS resolution on the ser ver: If Windows cannot resolve
crl.verisign.net , it will not attempt to verify the signature. This can be done by
removing all DNS servers from the machine’s network settings.
Allow Windows to Connect to Verisign: If Windows is allowed to connect
to
http :// crl .verisign.net , the service will load properly.