A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Ecosystem, maps, and integration hooks / Integration hooks that are already named

Integration hooks that are already named

Future work should use hooks the documents already name: AMI, AGI, ARI, the Event Socket, SIPREC, and SIP over WebSocket. This lab does not ship a live connector.

Learn in 5 minutes

  1. Name the control interfaces on the Asterisk license page
  2. Name the FreeSWITCH Event Socket
  3. Leave unstated vendor webhooks unstated

Visual

A control event is not the SIP call · study drawing · cyphermonkeylabs.com SIPPBXController INVITE 180 event ack

SVG HTML PNG

If a product advertises another API, open that page before you build to it. Empty cells stay empty.

Worked example

Pick a real hook You want a program to hear that an Asterisk call is ringing. Choose an interface the license page names.

  1. Read the three Asterisk names.
  2. Do not invent a fourth.
  3. Remember it is not a SIP method.

Fault

A design review says the mind map has a box called CRM, so a webhook URL is assumed and coded.

The ecosystem drawing is a topic list.

Quiz

AMI, AGI, and ARI are named on


The FreeSWITCH programming interface named in the manual is


SWML belongs to


A recorder hooks in through


A browser that speaks SIP hooks in through


An integration this lab did not open a page for


Ecosystem

Glossary, sister systems, and the integration seam for this room.

CRM Screen pop uses data the contact center already has: ANI, DNIS, case id. Those values may arrive in SIP headers or in a CTI event after the call is up. The CRM is not a SIP element.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper