...
...
...
...
Call:
The notifications for the call being joined come back via Redis LIST as, you will use BRPOP or RPOP to retreive these
...
URL
...
Tip | ||
---|---|---|
| ||
http_port settings are determined by your issued configuration - see the configuration document for more information |
Create Call:
RESTful API |
|
---|
...
|
...
- agent: <extension>
- callee: <number to dial>
- outbound_id: <number to use>
- call_ref: <the custom call ref you specified>
...
Key
...
enigma:notifications:c2d
...
Payload
...
DEPRECATED
- notifications: Array of Objects
- extension: <the agent this applies to>
- disposition: <how the call ended>
- recording_url: <Unique Recording reference used to fetch the recording>
- call_ref: <the call ref you specified>
- end_code: <The ISDN termination code>
Values:
...
| |||
WebRTC | From v3.0.0
From v4.0.0 The Sip Headers changed to X-Teleforge-* |
---|
Values:
<ext> | The agent extension number or the first number connected to the call
|
---|---|
<callee> | The number to dial: One of the following:
|
...
<outbound_id> | Number to use as caller ID: One of the following:
|
---|---|
<custom_call_ |
...
The enigma:notifications:c2d redis notification is deprecated.
...
ref> | Your custom call reference specified for this call Alphanumeric and .-_~: Max length 230 characters, thereafter they are truncated |
---|
...
Unique Recording reference for call
http://serverurl/click2dial/recordings/<recording_url>
...
title | DEPRECATED |
---|
Default: if none is provided, then one is generated, although it serves no real purpose |