Avaya Listener

Currently we integrate with the Avaya IP office DevLink3 interface. PBX events are consumed from the onsite PBX then attached to cloud events to give CRM & 3rd party applications more detailed information including phone level events.

To enable PBX events, firstly ensure you have the correct integration with Avaya R9/R11 under webhooks.

Enter the public IP of the Avaya PBX, ensure you have the correct firewall rules in place to port forward either 50794 (R9) or 50797 (R11) UDP ports. This can be locked down to the monitor instance you select.

Avaya DevLink 3 username & password also needs to be set and needs to match the DevLink user set in the Avaya IP Office however the IP Office configuration is out of scope of this document.

Once the PBX integration is complete, Callable will consume these events and attach extension numbers to call recordings (if applicable). The next step is to send these events to your 3rd party integration (URL).

Once these steps are complete, you should start seeing PBX events being sent to your URL endpoint. Please note, events are sent using HTTP POST.

The following is an example pbx.event payload

 {  
   "accountId":"9539ee93-64c8-802b-360b-c6f2f7cf2507",
   "accountName":"Test Account",
   "organisationId":"5f748c16b0731b38efa4d25d",
   "organisationName":"Test Organisation",
   "parentCallId":"e5bc544c-2186-47e8-8784-6182cf8190cb",
   "callId":"e5bc544c-2186-47e8-8784-6182cf8190cb",
   "pbxId":"8821febc-430a-123a-1e93-0ae200042995",
   "caller":"07912345678",
   "called":"01234567890",
   "extension":"201",
   "event":"phone",
   "state":"connected",
   "timestamp":1623163324316
}

The callId field relates to the callId of the outdial leg to the pbx.
The parentCallId field relates to the original ingress leg of the call.