Roman_Bessnow | 2021-01-06 01:59:34 UTC | #1
I was looking at this forum and was not able to find a good recommendation for the best practice regarding the incomplete inbound faxes. It looks like PureConnect has good configurations for handling of incomplete faxed, but I am at PureCloud faxing product. So, if suck out out of Genesys a fax event and the document is partial or “corrupted” and the conversation was terminated with bad code then how can I get that information from PureCloudPlatform.Client.V2.Mode.FaxDocument? How can I API from incoming fax Doc ID that I get in the FaxDocument to the status of the incoming conversation that had delivered this fax? Furthermore, If I get somehow the grip of the termination code and learn that fax is incomplete or corrupted then what would be a good practice for rejection of the fax? I would like to hear from somebody who have went over it already.
Sibi_Chakaravarthy | 2021-01-07 17:48:29 UTC | #2
Assuming fax is sent and received within Purecloud, conversationId will be available in the response as 'id' when fax is sent using ‘/api/v2/conversations/faxes’ API. Outbound and Inbound conversation information can be obtained using ‘/api/v2/conversations/{conversationId}’ API. (https://developer.mypurecloud.com/api/rest/v2/conversations/#get-api-v2-conversations). This can be used to determine conversation state and error information in a failure case.
/api/v2/fax/documents API don’t return conversation information in their response. But document information can be retrieved using the conversationId. Will check if there is a way to get list of conversation associated to a user and update.
system | 2021-02-07 17:48:08 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 9634