Sending Fax End User to FaxMaker Flashcards
List and describe the 4 fax sending methods available in FM.
Web client
Access the GFI FaxMaker web interface from a supported web browser and compose faxes from the web client.
Email
Users can send faxes and SMS messages directly from their favorite email client, such as Microsoft Outlook.
NetPrintQueue2Fax
To send faxes, users print content to the NetPrintQueue2Fax printer driver. The fax recipient number is keyed in within the document in a customizable format.
This enables fax sending in any format that allows printing of content (without installing the application on the FaxMaker machine).
APIs
Use third-party tools to automatically generate APIs containing the information about the faxes to send and automate the fax and SMS message sending process.
Store TextAPI or XMLAPI files to a central location and FaxMaker automatically processes files located in this folder.
Describe sending the fax via email.
Most companies use email and hence using it to send the fax is pretty simple to set up and use. Sending via the email client that is already used by the customer provides an already existing built-in fax sending method. This method also includes MS Office 365.
To send the fax using email, FaxMaker should be installed on the Microsoft Exchange server or have connectors installed to work with FaxMaker installed on a separate server. FaxMaker works with Microsoft Exchange Server, as well as some other non-MS Exchange mail servers. To understand how it is done, please see Faxmaker Mail Server Settings article.
Once the Faxmaker is installed, you can start sending faxes via email, for more details on it, please see Sending the Fax via Email article.
Faxmaker also works with POP3 mailboxes.
STEPS IN PROCESS
The email will be created to be sent to the fax number email, which is usually in the following format.
@ For example, 1234567890@faxmaker.com
This email will be sent from the email client to the mail server.
The email will leave the client and go to the mail server, and the mail server will route the email using the send connector to the IIS SMTP server on the fax server which will then drop the email in the following folder, which is the default location.
C:\Program Files (x86)\GFI\FaxMaker\SinkDrop
The FaxMaker Message Transfer Agent (MTA) service picks up the email and begins processing it.
The MTA separates the To and From information, the body, and the attachment(s).
The To and From information is used to create an SFM file.
The email body is copied to a BDY file (if applicable).
The SFM file, BDY file, and attachment files are saved to the FAXmaker\Out directory.
The FaxMaker fax server service retrieves the files from the FaxMaker\Out folder and generates the fax image and sends the fax via the fax device.
The FaxMaker fax server service generates a transmission report and saves it to the FAXmaker\In folder.
The MTA picks up the email report from FAXmaker\In folder and sends a fax report email to the sending user using the mail server defined in the Email2FaxGateway node of the FaxMaker configuration.
Describe sending a fax using textapi.
This API uses a text file to issue commands and create references for other files to be used to send the fax. The text file can point out attachments that are to be used in the fax as well as select specific cover pages and other details.
STEPS IN PROCESS
The control file and any associated files are dropped into the TextAPI pickup folder specified in the FaxMaker Configuration.
The FaxMaker Fax Server service picks up the files and processes them. This processing includes extracting the fax information from the control file and fax data.
Once the files are processed, the fax data is converted to an image and transmitted via the fax device.
The transmission report can work in one of the following two ways:
If a licensed user has sent the fax, the transmission report is generated and dropped in the FaxMaker\in folder for the message transfer agent to send it to the user.
If no user is specified in the control file, a transmission report will not be generated. Instead, a response file will be created and dropped into the pickup folder, by default. If a user that is not a licensed user is specified in the control file, the fax will fail due to a user error.
Describe sending a fax using XMLAPI
This API is the same as the previous TextAPI but uses an eXtensible Markup Language (XML) file as the control file instead of a text file. So the XML file will have the commands and references mentioned in the TextAPI section.
The control file and any associated files are dropped into the XMLAPI pickup folder specified in the FaxMaker Configuration. This would include the mandatory XML control file, the optional bdy file and an optional attachment of which the file type could vary between supported attachment file types.
The fax server service picks up the files, parses the XML information, and then processes them.
Once the files are processed, the fax data is converted to an image and transmitted via the fax device.
The transmission report is called a status file. This file is dropped back into the pickup folder, by default. Unlike TextAPI, you must be a licensed FaxMaker user to send faxes using this method, and there is no option to receive a transmission report via email.
Describe a fax via Web CLient/WSAPI
With FaxMaker Web Services API (WSAPI) a customer can create their application to send faxes to the FaxMaker server, or receive from, using web services and port 8555.
The FaxMaker Web Client is a built-in sending method that does not require installation of any other software and is accessible to all FaxMaker licensed users.
As long as the user can access the website, which is installed on the FaxMaker server when FaxMaker is installed, the web client is accessible and usable. It uses the same port, 8555, as the WSAPI.
With FaxMaker Web Services API (WSAPI) a customer can create their application to send faxes to the FaxMaker server, or receive from, using web services and port 8555.
The FaxMaker Web Client is a built-in sending method that does not require installation of any other software and is accessible to all FaxMaker licensed users.
As long as the user can access the website, which is installed on the FaxMaker server when FaxMaker is installed, the web client is accessible and usable. It uses the same port, 8555, as the WSAPI.
Describe sending a fax via NetPrintQueue2Fax printer drive.
The NetPrintQueue2Fax printer is installed on the FaxMaker server while installing FaxMaker and it is shared by default. From there each licensed user can install that printer driver on their computer and can send prints to this printer to send faxes.
Once the NPQ2F is configured, a document can then be set up and printed to be sent as a fax.
The print job is usually spooled to the printer.
Once the printer has the job, the npqf_drv.dll determines the account name of the user who sent that job, converts the document, and saves the job files to the FAXmaker\temp folder (*.NPQ and *.TXT file).
The npqf_proc.exe detects job files in FAXmaker\temp and then determines the licensed user status of sending account.
If the user is valid, the npqf_proc.exe generates an SFM and FAX file and saves them to the FaxMaker\out folder. Otherwise, it generates a Fax Admin notification and puts it into the FaxMaker\out\administration folder.
GFI Faxmaker fax server detects the job in FaxMaker\out folder and processes the job as it does for any other fax source.
A customer has the following request:
We are currently testing GFI FaxMaker and need to configure the integration with Aprima for sending faxes from patient documents.
Which KB article provides the requested information? Paste the link in the field below.
https://support.faxmaker.gfi.com/hc/en-us/articles/360018587260-Sending-Faxes-Using-Aprima-Medical-Software
A customer opens a ticker because a user sent a fax from Outlook via Office 365, and it didn’t get to the sinkdrop folder.
In the Office 365 message trace logs, it’s noticed the error “4.4.316 connection refused” and “sendasdenied” exception.
Paste in the field below the URL for the KB article that addresses the given scenario.
https://support.faxmaker.gfi.com/hc/en-us/articles/360018650799-Receiving-Sendasdenied-Error-Sending-Faxes-From-Office-365
A customer has the following request:
We have a lead that involves Canon MFD as the API and the reseller is evaluating, but we can’t find the download link of the eCopy Share Scan Connector.
In the field below, paste the link to the KB article that provides instructions for downloading and installing the required software.
https://support.faxmaker.gfi.com/hc/en-us/articles/360015130920-Installing-the-FaxMaker-Nuance-eCopy-ShareScan-Connector
A customer reports the following situation:
We now have a hybrid mode (on-prem Exchange 2016 & Office 365). The user (O365 mailbox) sends a fax via Outlook to fax#@faxmaker.com on behalf of a FaxMaker account (Houston-faxmaker; on-prem E2016 mailbox).
The message gets stuck on Office 365 queue because there are no MX records for faxmaker.com. Before the hybrid mode, we had a faxmaker.com Exchange connector that routed traffic to the Faxmaker Windows server.
Which KB article provides the instructions the check and configure FaxMaker according to the customer’s scenario?
Paste the article’s URL in the field below.
https://support.faxmaker.gfi.com/hc/en-us/articles/360018594940-Using-FaxMaker-with-Office-365-in-Hybrid-Mode
Customer:
Our customer states that one of our employee's faxes are not being received. I have confirmed she is using the correct way to send by applying @faxmaker.com to the end of the fax number. I have confirmed she is faxing to a fax line. GFI FaxMaker web interface indicates her fax is pending. I also saw her files stuck in the folder sinkdrop\ignored on Fax Server. Is there any way to get her fax from pending to sent? L1 Agent (public note):
Dear Customer, upon checking the log files you uploaded, I noticed the following message: “Fax sent from this email address cannot be transmitted because you are not a GFI FaxMaker user. Contact your administrator to start sending faxes using GFI FaxMaker.”
Can you confirm if the user is set as a FaxMaker licensed user? That would be required for her to send faxes.
Customer:
In response to the error message, it is referring to the HP Multi-function printer the employee is using.
Which of the following statements explains the issue?
The printer has to be added as a licensed user to send faxes
Faxes cannot be sent directly from a multifunction printer
The multifunction printer cannot have an email assigned to it
The printer has to be added as a licensed user to send faxes
A customer asks where they can find information about FaxMaker’s API to send faxes.
Paste in the field below the URL for the KB article that provides the requested information.
https://support.faxmaker.gfi.com/hc/en-us/articles/360018556179-Using-FaxMaker-s-APIs
If a customer opens a ticket asking for the FaxMaker’s Client download link, which of the following statements will give them a thorough answer?
The Web Client replaced the FaxMaker Client, which is not supported anymore, but customers can still download it for both 32 (http://cdndl.gfi.com/faxclient.exe) and 64 (http://cdndl.gfi.com/faxclient_x64.exe) bit platforms.
The FaxMaker Client is still developed and supported, and customers can download the latest versions for both 32 (http://cdndl.gfi.com/faxclient.exe) and 64 (http://cdndl.gfi.com/faxclient_x64.exe) bit platforms.
The Web Client replaced the FaxMaker Client, which is not supported anymore, but its latest version is still available in a single download for both 32 and 64-bit platforms (http://cdndl.gfi.com/faxclient.exe).
The FaxMaker Client is still developed and supported, and its latest version is available for download in a single installer for both 32 and 64-bit platforms (http://cdndl.gfi.com/faxclient.exe).
The Web Client replaced the FaxMaker Client, which is not supported anymore, but customers can still download it for both 32 (http://cdndl.gfi.com/faxclient.exe) and 64 (http://cdndl.gfi.com/faxclient_x64.exe) bit platforms.
A customer reports the following issue:
Faxmaker server is refusing mails sent to *@faxmaker.com I see this happening from the exchange email side:
Delivery has failed to these recipients or groups:
17067044751@faxmaker.com (17045044751@faxmaker.com)
Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
The following organization rejected your message: USCHFAX02.local.burkert.com.
Which of the next options helps to isolate the system that is causing the problem, so you can target your troubleshooting efforts?
From the email client, send an message to 17067044751@faxmaker.com while the MTA service is stopped. After that, if a .eml file is placed on the C:\Program Files(x86)\GFI\FaxMaker\Sinkdrop folder, the problem resides on FaxMaker’s end. Otherwise, it’s with the email system.
From the email client, send an message to 17067044751@faxmaker.com while the MTA service is stopped. After that, if a .eml file is placed on the C:\Program Files(x86)\GFI\FaxMaker\Sinkdrop folder, the issue is in the email system. Otherwise, the problem lies on FaxMaker’s side.
From the email client, send an message to 17067044751@faxmaker.com while the MTA service is running. After that, if a .eml file is placed on the C:\Program Files(x86)\GFI\FaxMaker\Sinkdrop folder, the problem resides on FaxMaker’s end. Otherwise, it’s with the email system.
From the email client, send an message to 17067044751@faxmaker.com while the MTA service is running. After that, if a .eml file is placed on the C:\Program Files(x86)\GFI\FaxMaker\Sinkdrop folder, the issue is in the email system. Otherwise, the problem lies on FaxMaker’s side.
From the email client, send an message to 17067044751@faxmaker.com while the MTA service is stopped. After that, if a .eml file is placed on the C:\Program Files(x86)\GFI\FaxMaker\Sinkdrop folder, the problem resides on FaxMaker’s end. Otherwise, it’s with the email system.
A customer opens a ticket regarding an issue that happens only to certain users. When a PDF file is printed to the FaxMaker web printer, the browser doesn’t open to ask for login credentials. Reinstalling the web printer did not fix the issue.
Which of the following options provides the correct instructions to set the permissions that solve the problem?
Set Full Control permissions to the group Authenticated Users in the registry location “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI Fax & Voice” of the FaxMaker server.
In the registry location
“HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI Fax & Voice” of the FaxMaker server, set Full Control permissions to the users who experience the issue.
Set Full Control permissions to the group Authenticated Users in the registry location “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI Fax & Voice” of the PC where the issue appears.
In the registry location “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI Fax & Voice” of the FaxMaker server, set Full Control permissions to the group FaxMaker Users.
Set Full Control permissions to the group Authenticated Users in the registry location “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI Fax & Voice” of the FaxMaker server.
