Web UI Flashcards
FaxMaker users can log in to the web interface to access the web client to send faxes and SMS. They also have the option to print a document or file to the Web Printer, named FAXmaker. Once completed, the content is uploaded to the FaxMaker server and the web interface is automatically loaded in a new browser window.
What are the steps to fax form the web UI?
Log in to the GFI FaxMaker Web Interface.
In the “To” field, enter the fax number of the recipient or select To, to access the web client address book. More information on the web client printer can be found here: Web Client Printer Driver
In the “Subject” field, enter the subject of the fax.
In the “Message” field, enter your message.
Select “Add attachment”, bottom right, if there is an attachment to add.
Across the bottom, select the “Priority”, “Resolution”, and “Delivery” options if needed.
Select Send.
The web printer driver cannot be installed on a system where the FaxMaker Client (software) is installed.
What are the steps to use the printer driver?
Log in to the GFI FaxMaker Web Interface.
From the top menu bar, click the gear to open the settings screen and select Client from the left pane.
Under Web Printer Installer, read the terms and conditions, and if you agree choose I agree with the Web Printer Terms and Conditions. The Web Printer cannot be downloaded if you do not accept the terms and conditions.
Click Download to start the download.
On download, completion launch the installer.
Key in the GFI FaxMaker Server URL. This value is the same as the address used to access the web interface login page. For example, https://fax.mydomain.com/FaxMaker. Click Test to verify.
Click Install to start the installation.
Click Finish on install completion.
A new printer FAXmaker is now added to your list of printer devices.
What are the steps to use the web printer?
Print a document or file to the Web Printer, named FAXmaker.
On completion, the printed content is uploaded to GFI FaxMaker and the GFI FaxMaker web interface is automatically loaded in a new browser window.
Log in to the GFI FaxMaker web interface in the automatically loaded window.
The Client is automatically launched with the printed document pre-populated in the attachments area. The attachment name is the PreUploaded File.
Proceed to fill in the message form and hit Send to transmit the fax.
What are the files and folders used by the sub-parts of the FaxMaker Monitor?
The files fmremsst.dat and fmremsvr.dat contain the encoded information on the status of the devices configured in GFI FaxMaker. These two files are checked frequently.
The file mtastat.txt contains information about the status of the GFI FaxMaker Message Transfer Agent.
The \GFI\FaxMaker\Out\Pending folder is the location that holds the queued faxes for delivery.
List details of monitoring fax lines in the Fax monitor.
Starting with version 19, the monitor MMC (Microsoft Management Console) was removed from FaxMaker and is now located in the web interface.
The lines showing in the monitor are used to track the activity for the devices created in the Configuration > Lines and Devices.
The green phone shows a line that is ready.
The orange phone with an arrow shows a line that is in use.
The x to the right of the active line is there to terminate the fax transmission on that line.
The blue restart server button, top right, is there to restart the fax server service.
Describe the process of delivering information from the other FaxMaker services to the web monitor
When the fmserver receives a fax, then it creates an FMMonitorObject and adds it to the Publisher.
FMMonitorObject is a reflection of the real fax.
When fax moves over different processing steps (pending, sending, sent, and other), then the fmserver updates the FMMonitorObject to reflect actual fax status and attributes.
When the fax processing is finished, then the fax information is stored in a “.sfm” file for 3 days. After 3 days, the “.sfm” file is deleted, and the FMMonitorObject is marked as deleted. The fmmonitorlib will delete the marked as deleted FMMonitorObject after 5 minutes.
Portal.UI receives monitor data from fmmonitorlib.dll via JSON REST API.
Fmmonitorlib.dll processes the local HTTP requests and provides published data in JSON format.
Fmserver and fmgwinet implements the publishers from the fmmonitorlib for Lines, Queued Faxes, and SMS devices.
fmserver and fmgwinet add the publishers to the FMMonitor and pushes FMMonitorObject in the implemented publishers.
List the details of monitoring fax queues.
Selecting queued faxes allows you to see the faxes that are in the queue, ready to be transmitted.
Use a keyword to search by Sender, Recipient, or Priority.
Remove faxes from the queue if needed.
Use the blue button, Restart MTA (Message Transfer Agent), to restart the Message Transfer Agent service.
List the details of monitoring sms devices and queue
SMS Dashboard displays the list of SMS devices and their current transmission status and properties.
SMS in Queue: Total number of SMS in the queue to be sent to devices for transmission.
Last SMS number: The last phone number on which the SMS was sent.
The number of local and international SMS messages sent in the last 30 days.
Reports are based on data logged to the _____, ______, or Microsoft® ______ archiving database.
GFI FaxMaker
Firebird
SQL/MSDE
List the steps to access the reports
Log in to the GFI FaxMaker web console. Only GFI FaxMaker administrators have access to this screen and it is not shown to regular users that log in to the web console.
Click the Reports tab from the top menu bar.
Use the left pane of the Reports screen to filter between reports.
In the Default Reports section, choose All to show all the default reports or click Fax or SMS to show default reports related to fax or SMS usage respectively.
In the Corporate section, access your Custom or Scheduled reports.
List the 5 most common troubleshooting issues for the Web UI.
IIS issues
Issues logging in
Content population issues
Issues with updates
Issues with reporting
Starting with which version was the Fax monitor MMC deprecated?
version 19
How do you troubleshoot IIS issues with the web UI?
The FaxMaker web interface is located at https://servername/faxmaker. When navigating to this site and the login page does not load we can try the following things.
Opening the web interface itself, leave the /faxmaker off and use https://servername to check the operation and show the IIS website is a good first step to ensure IIS is operational.
If the issue does not appear to fall within IIS, usually an IIS update is required or a replacement of the web.config file (C:\Program Files(x86)\FaxMaker\WebUI) from a test environment as they can occasionally become corrupted. The replacement of the web.config file resolved the issue below.
There have also been instances of an HTTP error 500.19 internal server error. The article below links to the solution for this issue.
Error: “HTTP Error 500.19 - Internal Server Error” When Opening the FaxMaker Web Interface
How do you troubleshoot issues logging into the web UI?
ssues with users not being able to log into the web interface usually have to do with the FaxMaker Attendant service not being started or an issue with the user management system that is in place, whether it be Active Directory or GFIDirectory. Logging will give proper direction to troubleshoot as seen below.
The unable to log into the web interface article gives several possible solutions for login failure in the web interface.
Logging for this will be in the Portal.UI log and will appear as below in the screenshot.
Lines 8442 through 8447 are for a successful login
Lines 8448 through 8452 show a login failure
For the failure, the password was just typed in
improperly and the failure is authentication, which is correct.
If the error above had been “directory service not available” then we would troubleshoot the user management system rather than a specific user issue.
How do you troubleshoot issues with content population in the web UI
FaxMaker 19.1 had an issue where lines in the monitor would be duplicated when sending faxes.
This looks like the screenshot below and is resolved with an upgrade to version 20.
For other issues with the lines shown in the FaxMaker Monitor, the monitorlib.gfi_log.txt file would be reviewed for more clarity. Below is a typical file excerpt with requests being processed and in the end we also see the service starting.
