Lower end customers are looking to get away from having a dedicated phone line for their fax server. The TR1034 board also requires a physical server. These customers are looking to move to a service base deployment for the following benefits.
...
POST http://65.39.245.253/rest/1.0/api/send
Input Parameters
| Input | Description |
|---|---|
| dialnumber | Destination number in the format 1+areacode+number |
| callernumber | Specify the caller id |
| csid | Calling station id |
| faxfile | This field contains the document to send. Accepted format is tiff |
Output Parameter Description
| Output | Description |
|---|---|
| RefCode | Unique code for the sent fax |
| Status | Status of the sent fax |
| Created | Time Shows the time the fax was created |
Example: Sending a fax to 17274568620
...
This is used to check faxes that are in the process of being sent. The method used by this request is GET and has the URL http://65.39.245.253/rest/1.0/api/outbox
| Output | Description |
|---|---|
| RefCode | Unique code for the sent fax |
| Dialnumber | Shows the destination number |
| Callernumber | Specify the caller id |
| CSID | Calling station id |
| Status | Shows the status of a fax |
Fax sent to 7274568620 is in sending status. Here is the response from the outbox command:
...
| View file | ||||
|---|---|---|---|---|
|
Etherfax also has a REST API for faxing (and secure doc transport) that focuses on encryption: https://docs.etherfax.net/
Information from :
From: Eli Mann [mailto:emann@faxsipit.com]
Sent: Thursday, March 15, 2018 8:24 PM
I have dug some information that I think might be indicative for usage. There is no end to the data mining we can do (sector, volume, other profiles) but at the high level these are strong enough statistics based on few thousands of end users. So Inbound (IO) and Outbound (OB) split traffic SD and revenues for the higher volume accounts (lower minute rate).
|
| IB | OB |
|---|---|---|---|
Percent |
| 32% | 68% |
1 standard deviation minutes/month per 8 ports |
| 1000 | 2000 |
1 standard deviation minutes/month per 8 ports |
| 10000 | 7000 |
Port Count minimum |
| 2 | 2 |
Port Count maximum |
| 24 | 48 |
Monthly traffic charges @ high volume (under 100K minutes/month) |
| $ 200.00 | $ 140.00 |
I found that mid-size (8 ports) shows very consistent results while some of the larger users are specific application driven and shows skewed results.