Plum DEV Documentation
plumdevguide:outbounddevguide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
plumdevguide:outbounddevguide [2019/11/14 11:45]
admin
plumdevguide:outbounddevguide [2019/11/14 11:46] (current)
admin
Line 129: Line 129:
 |scheduled_timestamp| int|0 to start immediately or a UNIX-time integer indicating when to start attempting the call (scheduled_time can be used instead -- see below for details) <​sup>​6</​sup>​| |scheduled_timestamp| int|0 to start immediately or a UNIX-time integer indicating when to start attempting the call (scheduled_time can be used instead -- see below for details) <​sup>​6</​sup>​|
 |expiration_timestamp| int| 0 to never expire or a UNIX-time integer indicating when the system should give up attempting to complete an uncompleted call (expiration_time can be used instead -- see below for details) <​sup>​6</​sup>​| |expiration_timestamp| int| 0 to never expire or a UNIX-time integer indicating when the system should give up attempting to complete an uncompleted call (expiration_time can be used instead -- see below for details) <​sup>​6</​sup>​|
-|is_pci| int| 0 or 1. For customers who have been granted access to our HIPAA / PCI compliant secure environment setting this flag to 1 will cause connected outbound calls to execute within that secure environment.|+|is_pci| int| 0 or 1. For customers who have been granted access to our HIPAA / PCI compliant secure environmentsetting this flag to 1 will cause connected outbound calls to execute within that secure environment.|
  
 Notes: \\ Notes: \\
Line 192: Line 192:
 |scheduled_timestamp | int| 0 to start immediately or a UNIX-time integer indicating when to start attempting the call (scheduled_time can be used instead -- see below for details) <​sup>​7</​sup>​| |scheduled_timestamp | int| 0 to start immediately or a UNIX-time integer indicating when to start attempting the call (scheduled_time can be used instead -- see below for details) <​sup>​7</​sup>​|
 |expiration_timestamp| int | 0 to never expire or a UNIX-time integer indicating when the system should give up attempting to complete an uncompleted call (expiration_time can be used instead -- see below for details) <​sup>​7</​sup>​| |expiration_timestamp| int | 0 to never expire or a UNIX-time integer indicating when the system should give up attempting to complete an uncompleted call (expiration_time can be used instead -- see below for details) <​sup>​7</​sup>​|
-|is_pci| int| 0 or 1. For customers who have been granted access to our HIPAA / PCI compliant secure environment setting this flag to 1 will cause connected outbound calls to execute within that secure environment.|+|is_pci| int| 0 or 1. For customers who have been granted access to our HIPAA / PCI compliant secure environmentsetting this flag to 1 will cause connected outbound calls to execute within that secure environment.|
  
 Notes: ​ Notes: ​