Versions Compared

Version Old Version 2 New Version 3
Changes made by

Lloyd Hughes (Deactivated)

Lloyd Hughes (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In order to be able to do lookups on inbound calls we make use of the Redis callback infrastructure which already exists. We will send a callback to your application which is of a similar type as the C2D notifications. Inbound call notifications consist of two parts, one notification when a call is answered and another when the call ends. The sub type of the inbound notification will be sent as part of the notificationThis incoming call notification is compatible with the notification used by the Teleforge Dialler for call connections, thus only one unpacking function is required to handle both.

 

URL

determined automatically

Key

enigma:notifications:inbound

Payload

  • extension: <the agent this applies to>
  • recording_url: <location where you can fetch recording>type: "call"
  • payload:
    • call_ref: <Unique internal ID for this call>
    • ref: <The handling agents extension number>
    • number: <the number which the call is coming from>
    call
    • contact_ref:
    <the call ref you specified>
    • <A unique matter/callee reference specified by the 3rd party application>
    • campaign_ref: "inbound"
Info
titlecall_ref

The callcontact_ref field may not always be populated, that depends if there is an IVR which allows inbound callees to type in a reference number or account number. If this is the case that will be filled in in the callcontact_ref field, otherwise the field will default to a null string ("").