Single-Function: MS810de, MS810, C950, CS510, CS410, CS310, MS610de, MS610dn, MS510, MS410, MS310, MS711, MS710, MS812de, MS812, MS811, MS415, MS315, MS312dn, C935, C920, C912, C910, C9235, CS927, CS923, CS921, CS417, CS317, MS417, MS317, MS622, MS621, MS521, MS421, MS321, M1140+, CS725, CS720, CS820, C6160, C4150, MS826, MS825, MS823, MS822, MS821, MS725, M5270, M5255, B2865, CS622, CS521, CS421, CS827, CS728, CS727, CS517, MS818, MS817, MS617, MS517
Multifunction: XM9165, XM9155, XM9145, MX912, MX911, MX910, MS911, XM1140, XC2132, XM7170, XM7163, XM7155, XM5170, XM5163, XM3150, XM1145, C925, C2132, M1140, M5170, M5163dn, M5163, M5155, M3150dn, M3150, M1145, CX510, CX410, CX431, CX310, MX511, MX611, XC2130, XM1135, MX610, MX510, MX410, MX310, MX812, MX811, MX810, MX711, MX710, MX6500, XC9265, XC9255, XC9245, XC9235, XC9225, CX927, CX924, CX923, CX922, CX921, CX920, CX417, CX317, MX417, MX317, XM3250, XM1246, XM1242, MB2236, MB2236i, MB2650, MB2546, MB2442, MB2338, MX622, MX522, MX521, MX421, MX321, MX331, M3250, M1246, M1242, B2650, B2546, B2442, B2338, B2236, XC4143, XC4150, XC4153, XC6152, XC6153, XC8155, XC8160, XC8163, CX860, CX825, CX820, CX725, XM7370, XM7355, XM5370, XM5365, MX826, MX822, MX725, MX722, MX721, MB2770, XC4240, XC2240, XC2235, MC2640, MC2535, MC2425, MC2325, CX625, CX622, CX522, CX421, C2535, C2425, C2325, C2240, XC4140, XM526
3, XM5270, XM7263, XM7270, CX827, CX727, CX517, MX718, MX717, MX617, MX517, MB3442i, MC3224i, MC3326i, MC3426i
What is etherFax?
By eliminating the need for costly components of a fax server, fax board, media gateways, and recurring telephony costs, the etherFAX company’s namesake solution leverages the Internet to manage all business-critical fax communications.
With etherFAX, expensive fax hardware, complex fault tolerance designs, and costly disaster recovery solutions are no longer needed. Additionally, etherFAX eliminates the complexities and costs of provisioning SIP, T.38, PRI, T1, and/or analog connections. By simply connecting on-premise fax server infrastructure to etherFAX, all fax communications are securely delivered via the cloud.
etherFAX is the fax board in the cloud, capable of processing billions of faxes each month.
Some Lexmark devices can send and receive faxes through the etherFAX service. This integration is such that an end user will not know the difference between using etherFAX or using the analog modem, except that their faxes may go through at a much faster speed (using HTTPS). The Fax Transport is set to etherFAX instead of Analog (or T.38 or G.711 for FoIP).
The Lexmark technical support agent (TSC) can also check the Fax setting from the SE setting page as shown in the image below.
My Lexmark device's Fax Transport is setup as etherFAX. The device has already been registered to the etherFAX portal and has been configured to connect to the etherFAX server. However, I sometimes see the "Lost connection to HTTPS Fax Server" message in the panel. The message usually clears on its own without me doing anything. What's going on with my device?
When a device's Fax Transport is setup as etherFAX, it needs to be connected to the etherFAX server all the time. It is highly recommended that the device be connected to a stable network connection. Any network connection problem will result into the device being unable to contact the server. When this happens, the device will post the Lost connection to HTTPS Fax Server" message in the panel. When the network problem is resolved and the device is able to contact the server again, the message in the panel will be cleared. Sometimes, it may take a while for the device to re-establish connection to the etherFAX server after the network becomes online again. To force the device to reconnect, you can reboot the device. It will try to reconnect at bootup.
My Lexmark device is setup to use the etherFAX transport. When I send a fax job, the call duration varies. Sometimes, the calls are short (a few seconds). Sometimes, the calls are longer (a few minutes). What's going on with my device?
When a device is setup to use the etherFAX transport, it connects to the etherFAX server to send and receive calls. The etherFAX server routes calls via the Secure Exchange Network (SEN) or the Public Switched Telephone Network (PSTN). There are 2 types of fax calls that may happen: 1) SEN to SEN calls 2) SEN to PSTN calls. When a phone number is dialed, the device routes the call to the etherFAX server. The server tries to determine where the destination is. If the server determines that the phone number is an endpoint within the SEN only, a SEN to SEN call is made and the fax document is transmitted using IP network speeds (fast). If the server determines that the phone number is a destination that is not within the SEN, it makes an outside call to the PSTN and the fax document is transmitted using fax speeds (slow) while the Lexmark device is made to wait for the status of the PSTN call. So if the call is routed w
ithin the SEN only, the call will be short. If the call was routed to the PSTN, it will be longer like any normal analog fax call.
My Lexmark device is setup to use the etherFAX transport. My network connection can sometimes become unstable. During this downtime, I'm concerned that I will miss some incoming fax calls. What do I need to do to address my concern?
It is highly recommended to connect the device to a stable network connection for etherFAX transport to work seamlessly. However in rare cases when the network is down, you will not miss any of your incoming fax calls. Unlike a regular phone number, the phone number provided by etherFAX will never be busy as the etherFAX server is the one who is answering all incoming calls. When a fax job is sent to a phone number within the SEN (Secure Exchange Network), the job is first received by the etherFAX server and stored in the receiver's inbox within the server. The etherFAX server would then inform the receiving device that a job is available in it's inbox. The receiver would then pull the job from the server; thus clearing the job from the inbox. In the event that the receiving device is down for whatever reason, the etherFAX server will just keep the fax job in the receiver's inbox until such time that the receiving de
vice becomes online again.
My Lexmark device is a non-harddisk model. It is setup to use the etherFAX transport. I tried to send a large fax job by scanning via ADF but I encountered a "Fax memory full" error. What do I need to do in order to send a large fax without error in my device.
Non-harddisk models have low fax storage memory. These models can't hold large fax jobs. However, it is sometimes still possible to send large fax jobs in these models using fax streaming mode. To use fax streaming mode, the original document is fed to the ADF when starting the fax workflow. When in fax streaming mode, the device will start the fax call and transmit fax pages while also still scanning the remaining pages via the ADF. For SEN to SEN calls, fax streaming mode is possible. For SEN to PSTN calls, the device is basically asking the etherFAX server to make the outside call to the PSTN. For this call to work, the etherFAX server needs to have the entire job at hand. Thus, fax streaming mode is not possible for SEN to PSTN calls. In order to send large documents via SEN to PSTN calls, we suggest you breakup the large document into smaller ones and send those smaller documents one at a time.
My Lexmark device is setup to use the etherFAX transport. Recently, it's system card has been replaced. Now, I get a "Lost connection to HTTPS Fax Server" message in the panel.
Whenever a Lexmark device registers to the etherFAX server, it creates an authentication token and stores it in non-volatile memory in the system card. This authentication token is used by the Lexmark device every time it connects to the etherFAX server. When the device's system card is replaced, this authentication token is effectively lost. The next time the device connects to the etherFAX server, it will attempt to register. However, the server will block the registration since the device is already marked as registered in the server's registry. A "Lost connection to HTTPS Fax Server" message is then posted in the MFP. In normal cases, the device's serial number remains the same after a system card replacement. Assuming that the device's serial number is retained with the new system card, you need to go to your etherFAX portal account and unregister the device from the etherFAX registry. Once this is don
e, the Lexmark device needs to be rebooted. When it boots up, it will try to register back to the etherFAX server. The server will no longer block the registration because the device is not yet marked as registered in its registry. In very rare instances that the device's serial number has been changed after the system card replacement, the device has to be added to the etherFAX portal as a new device using the new serial number.
When an end user calls in with a Fax issue, TSC agent must first check if the Fax Transport is set to etherFAX.
A. If Fax Transport is indeed set to etherFAX and the end user intends to use this option, then make sure to verify if there any hardware issues related to Fax.
• If it is a hardware issue, continue to troubleshoot and address the hardware issue of the Lexmark device.• If it is not related to hardware, redirect the customer to the etherFAX support
B. When the end user mentions that they do not want to use etherFAX, then set Fax Transport back to the traditional fax setting.
• If the issue persists after Fax Transport is back to its regular setting, follow the traditional troubleshooting for fax issues.
If the Fax Transport option is accidentally set to etherFAX, the error message "No analog phone line connected" will appear on the printer's control panel.
C. Lexmark technical support agent should direct end user to etherFAX support (
) once it is determined that the issue not related to Lexmark firmware (FW) or hardware (HW).
The etherFAX service is simply enabled on Lexmark devices. Resellers of the solution are etherFAX and the etherFAX dealers which means that they will already have a relationship with their end users, and, therefore would be the first point of contact should any issue related to fax occur.
If the end user does contact Lexmark first, then TSC agent will need to diagnose if the issue is related to FW,HW or etherFAX. In the event etherFAX needs Lexmark's help on an issue, they will contact Lexmark development directly.
If you have any questions or encounter problems when performing the steps above, please contact your next level of support (L2 or L3) for additional troubleshooting.
Please be prepared to describe the problem you are experiencing, the error message on the display, and the troubleshooting steps you performed.