Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Call:

CDRs are sent after every call, whether or not it was answered/handled. These are used for call accounting both on the providers side as well as in the 3rd party application. As CDRs are critical we make use of a persistent Redis List to send them. A single worker must exist which handles/processes these notifications.

Type

List

Key

enigma:notifications:campaigns

Payload

  • type: cdr
  • payload: <notif>
    • extension: <ext> agent extension number
    • call_ref: <internal_call_ref> Internal dialler call reference
    • contact_ref: <custom_call_ref> your custom call reference
    • dialed_at: time the call was placed
    • end_reason: <disposition> how the call ended
    • end_code: <SIP_termination_code>
    • call_time: duration of call
    • call_dir: whether this was inbound or outbound
    • recording_url: location where you can fetch recording
    • ref: <campaign_ref> campaign reference

Values:

<ext>The agent extension number
<internal_call_ref>Internal dialler call reference, this is used to disposition the call
<custom_call_ref>Your custom call reference specified for this callee (use this for your lookups)
<disposition>Dispositions: how the call ended
<SIP_termination_code>The SIP termination code
<campaign_ref>Your Campaign reference

Example:

# get cdr's for all campaigns
brpop enigma:notifications:campaigns

When will you get a CDR?

You will receive a CDR for each call that the dialer makes, at the end of the call. 

If a callee has multiple numbers, it will try the numbers in order and send a CDR for each number it tried to call, if a call is connected then the callee has been contacted and the rest of the numbers won't be called. 

 

  • No labels