Outbound_call

Sent when an extension starts a call to the outside. It does not mean the call was answered by the other side, it only reports that dialing started.

Sample body

scenario: Outbound_call

{
  "pbx_num": "8501234567",
  "customer_num": "905551112233",
  "unique_id": "sip2-1767225700.10002",
  "internal_num": "101",
  "scenario": "Outbound_call",
  "timestamp": "1767225700000"
}

Send this body to your own address

The sample body above is sent to the address below as a POST request. The request goes from your browser, so the response cannot be read if the receiving endpoint sends no CORS header; the request itself still arrives. Use the cURL equivalent to try it from the server side.

cURL equivalent:

curl -X POST 'https://your-address.example/webhook' \
  -H 'Content-Type: application/json' \
  -d '{"pbx_num":"8501234567","customer_num":"905551112233","unique_id":"sip2-1767225700.10002","internal_num":"101","scenario":"Outbound_call","timestamp":"1767225700000"}'

Fields

Field	Type	Description
scenario	string	Always Outbound_call.
pbx_num	string	Your PBX number the call went out from.
unique_id	string	Unique identifier of the call.
internal_num	string	The extension that started the call.
customer_num	string	The called subscriber number.
timestamp	string	Event time (ms, Unix epoch).

On an outbound call customer_num is the called party

In inbound scenarios customer_num shows the caller, whereas here it is the called number. If you interpret this field as "the caller" without telling the direction apart, you will store outbound calls the wrong way round.

incoming_number is not sent

On an outbound call there is no such thing as "your dialed number", so this field is not present.

The number format may vary with the dialed destination; it can arrive with a country code as in the 905551112233 sample, or start with 0. Normalize numbers if you are going to compare them.