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

SIP UniverseFree University

Home / Ecosystem, certifications, and the UC bridge / Workforce tools and agents above the media

Workforce tools and agents above the media

Agents and workforce tools sit above the media path. The session is still SIP, and the voice is still RTP.

Learn in 5 minutes

  1. Keep SIP as the session protocol
  2. Place AI assistance above RTP
  3. Refuse invented agent features

Visual

Assistance is not a hop · study drawing · cyphermonkeylabs.com AliceSBCBob INVITE 100 INVITE 180 180 200 200 ACK

SVG HTML PNG

Assistance that cannot see SIP still does not become SIP.

Worked example

Point at the media hop Which response carries the answer that lets RTP start?

  1. Press Play.
  2. Step until the hop named in the question.
  3. Inspect that message and answer the check.

Fault

Silence after connect, and the ticket says the AI agent consumed the ACK. The ladder shows 200 OK and no ACK. The agent platform has no SIP socket.

A 2xx ACK is end to end between SIP roles. RFC 6026. The agent is not one of those roles.

Quiz

An assistive agent sits


Voice samples are


A disclosed SBC fork to a recorder is


A wrong 488 is fixed in


Named AI product features in this edition are


Call-ID still identifies


Ecosystem

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

E911 / emergency calling Location has to ride with the call. RFC 6881 is the BCP, RFC 6442 carries location in SIP, and the FCC MLTS page states Kari’s Law and RAY BAUM’s Act obligations for multi-line systems.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper