Send Fax Directlry

Based on the Documents, It seems that EasyLink can push all the incoming Faxes to the SFTP at Customer's Environment.

(1) So, do a Customer need to use any API in that case? Or the Fax, Other Required Information will be automatically stored in the SFTP of the Customer?

(2) Outbound FAX is the Reverse Process? So, If I put the Fax to the SFTP then the EasyLink will read it automatically from some PULL Service and send it to the User? Or Do we need to use some API for sending the Fax? If Yes then what should be the format for the Outbound Fax we do?

Find more posts tagged with

Comments

skamens

(1) So, do a Customer need to use any API in that case? Or the Fax, Other Required Information will be automatically stored in the SFTP of the Customer?

If the files are copied to the customer's location via FTP, only the fax file itself (either TIFF or PDF depending on the account setup) will be provided. It is possible to customize the file name to include some of the information about the fax (sender, recipient, number of pages, etc.), but otherwise no additional information is provided.

The system does not support the initiation of an outbound fax this way. You must submit the request via email, the API, one of our portals, or some other appropriate input agent.

CareMetxDevTeam

Thanks fro the Prompt Response. But I'm still having some doubts. Please go through my below text :

(1) So, in case of PUSH, Easy Link server will push all the faxes to the Customer's SFTP and each fax will have 3 Files i.e. Fax itself, Cover File, XML File. Please correct me if I"m wrong. And Is it possible that we can use our custom file naming convention for the incoming file/fax?

(2) Okay, So, If I have to send a Fax (Outbound Fax), So, I'll just need to call an API and can provide the attachment and other details and easy link will do the job. Correct? If yes then Please tell me which APIs I need to use?

Thanks.

skamens

In the case of FTP push, our server will only push a single document to the destination system. This is generally the inbound fax itself (converted to the desired format). The email body file that you would get with an email delivery is not available via FTP push, and neither is an XML meta file. If you already have a custom file naming convention for incoming faxes, the file that is FTP'd to you will have that name.

If you want to be able to receive the other information mentioned above, you might want to consider Web Services Push, in which we push a SOAP/XML request to a receiver on your system. That XML content will have all of the meta-data about the fax, the email body (if any), and the fax content itself.

If you want to initiate an outbound fax using web services, you would use the JobSubmit API (https://apiforums.easylink.com/emapidocs/25/JobSubmit/index.html). If you haven't done anything with the API to date, you can check out this post as a starting point: https://apiforums.easylink.com/content/how-do-i-get-started-api.