Hi,
After sending a fax through JobSumit, how do I get the number of pages easylink received?
thanks,
Nithi
It would actually be the number of pages EasyLink sent. You use the JobDeliveryStatusRequest to get the Delivery Details. This requires the XDN and MRN that are returned in your Submit Result.
Tom
I could see that DocumentPageCount of DeliveryDetail has the page count. however, this doesn't seem to reflect the actual pages delivered. when the transmission errored out in the middle of the delivery after resuming interrupted delivery, the receiver received only few pages...say 10 out of 20. But DeliveryDetail returns the PageCount as 21.(I guess the extra page is for the coverpage Easylink automatically generats when it resumes an interrupted delivery)
Could you clarify?
If a delivery is interupted in the middle of transmission the system retries the call. Upon connection it will continue sending with the page that the delivery was interupted on, hence the page count of 21. Ten the first time and eleven the second time.
1. I submitted 16 page fax to Easylink
2. Service interrupted (some problem with receiving fax machine) after Easylink delivered 5 pages.
3. Service resumed. Easylink delivered 5 more pages and the service got interrupted again forever.
4. So, a total of 10 out of 16 pages were delivered.
5. however, JobDeliveryStatus returned with Job State "Complete" and "Posted", Item state "Error". And, returned a page count of 17 instead of 10.
Would you please attach the XML of your JobDeliveryStatusResult? Then we should be able to explain it for you.
Thank you!
jobid is 1815430. or do you want only the xml?
<?xml version="1.0" encoding="UTF-8" ?>
Thanks. I've been looking at the same thing here.
Based on the job mentioned above, we looked at the internal behavior of the system.
The first item delivered successfully on its first attempt - it sent 16 pages as shown above.
The second item had 3 attempts, none of which succeeded; the error code for it (3935) indicates a timeout/no-answer condition. But in the process of making those three attempts, the system indicates that it actually sent a total of 17 pages, which is reflected in the XML.
So for future reference, the page counts provided by the API are the cumulative actual pages delivered across one or more attempts, as recorded by the system.
I am sorry, this is confusing. The receiving fax machine in this case received only 10 pages across all attempts. So, how would Easylink count as 17 pages?
I don't understand this either. The API just reports what is logged into the transaction database by the other parts of the system, and those other parts seem to have logged it as 17 pages.
I've sent a request to some other support folks to see if they can clarify.
Hi, do you have any update on this?
Sorry for the delay.
We've been able to explain what you saw on the fax machine, as follows:
The failed fax received 3 attempts.
The first attempt delivered 4 confirmed pages and one page was being transmitted (at the time of disconnect) which the fax machine would have likely printed out.
The second attempt delivered 5 confirmed pages and one was being transmitted when it disconnected. Apparently this last page wasn't far enough along to print.
The last (third) attempt resulted in no answer from the fax machine, so there were no pages exchanged.
As for the delivery detail, it turns out that for an unsuccessful fax, we do not actually log the partial count of pages transmitted. The page count in the JobDeliveryStatus result is the number of pages that we attempted to deliver, not the actual.
The reason the count is 16 for the first item and 17 for the second is that we added a special cover page when we made the additional attempts on the second item saying "this is a resumption of a previous partial fax".
I hope this explains what you're seeing.
thanks. you are right. as you said, receiving fax machine received a total of 11 pages including the special coverpage that Easylink added ( 5 in first attempt and 5+1 in second attempt).
so, since the DocumentPageCount is 17, it is apparent that Easylink does not capture the actual count of pages delivered to a fax destination.
we are trying to generate a delivery report and "pages delivered" is one of the information we would like to capture. do you see this as something you could fix in future or this is how it is going to be?
If the delivery is successful, then the page counts you get back will be correct.
If the delivery is unsuccessful, then it doesn't look like you can easily get the actual pages delivered as part of the failed delivery.
Can you just set up your report to indicate that there was a failure in these cases?
since we are charged by number of pages, we would like to provide accurate information to our business.
Unfortunately, I can't provide any additional information about exactly how you would be billed for the situation we've been discussing here; from what I know of the system, I don't think the page billing would include the pages for the failed faxes.
I suggest that you (or your business people) discuss this issue with your sales team to understand exactly how the billing will work for these types of jobs so you can report appropriately.
I'm sorry I can't solve the issue here, but we've gone beyond the area of the API at this point.
thanks. i will then leave this to the business for further discussion.
