This notification type is very simple. All the tokens are encoded into the URL template, and the body template should be empty. The Http content type is also not relevant for this type of transaction.

HttpBodyContentType setting

Not applicable

HttpUrlTemplate setting

http://%{Destination}/ConcordFaxDeliveryNotification.Asp?AccountId=%{AccountId}&ReferenceId=%{ReferenceId}&FaxJobId=%{FullMessageId}&FaxJobStatusId=%{StatusId}&StatusDescription=%{Status}&PageCount=%{NumPages}&FaxDeliveryDateTime=%{TimeSent}&FaxDeliveryDuration=%{CallDuration}&RemoteFaxCSID=%{RemoteCSID}&ErrorCode=%{ErrorResult}&ErrorString=%{ErrorString}

OR

https://%{Destination}/abc.xyz?AccountId=%{AccountId}&ReferenceId=%{ReferenceId}&FaxJobId=%{FullMessageId}&FaxJobStatusId=%{StatusId}&StatusDescription=%{Status}&PageCount=%{NumPages}&FaxDeliveryDateTime=%{TimeSent}&FaxDeliveryDuration=%{CallDuration}&RemoteFaxCSID=%{RemoteCSID}&ErrorCode=%{ErrorResult}&ErrorString=%{ErrorString}

Note

  • %{Destination} token is replaced from the contents of the NotifyDestination field for the job, if the NotifyDestination does not start with ‘http’ or ‘https’.

  • If the %{Destination} field starts with ‘http’ or ‘https’ then it completely replaces this Template setting with a job specified notification.

  • For security reasons you may want to use the Https protocol.

HttpBodyTemplate setting

Not applicable

See Also