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

SIP UniverseFree University

Home / Ecosystem, maps, and integration hooks / Sister technologies around the session

Sister technologies around the session

WFM, recording, emergency policy, analytics, CRM, AI agents, and programmable APIs hang off the session. They are not SIP proxies.

Learn in 5 minutes

  1. Name the neighbor and the document that mentions it
  2. Keep CRM and WFM out of the Via path
  3. Describe programmable APIs only as far as the Twilio docs page goes

Visual

The session completes. A neighbor hears an event. · study drawing · cyphermonkeylabs.com CallerSBCRecorder INVITE INVITE 200 200

SVG HTML PNG

The session is the seam. The neighbor consumes an event or a recording, or it places a call through a product API.

Worked example

Name the neighbor The symptom is a recording that never starts. SIP to the phone works.

  1. Separate the customer call from the recorder.
  2. Name the RFC.
  3. Do not blame WFM first.

Fault

The screen pop fails. RTP is one way. The ticket says to reboot the CRM.

Neighbors consume events. They do not replace c=.

Quiz

SIPREC is specified in


WFM is


The CRM is


SignalWire's hosted AI agents are described on


This lab's meaning for the word CPaaS is


A recording INVITE and the customer INVITE


Ecosystem

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

Quality management and recording QM scores interactions. The standardized way an SBC forks a session to a recorder is SIPREC.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper