Home / Cisco CUBE, CUCM, and Unity Connection / Unity Connection SIP integration
Unity Connection SIP integration
SIP integration with CUCM is the documented Unity Connection path. Open the guide for your version. This lesson does not make SCCP the default.
Learn in 5 minutes
- State that SIP integration is the documented path
- Use Diversion as a redirecting-number example
- Open the version’s integration guide
Visual
In this synthetic, 192.0.2.40 stands for the Unity Connection SIP peer.
Worked example
Find the called number Dissect the forwarded INVITE. Which header carries +15551212 as the redirecting target?
Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.
Fault
Unity Connection answers, then cannot select a mailbox. The INVITE has no Diversion and no History-Info.
Neither Diversion nor History-Info is present.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
AI omni-channel agents A voice bot still needs a session. SIP creates, modifies, and ends sessions. Omni-channel, in the contact-center sense, means the same contact can also live on chat or another digital channel. Those channels do not replace the voice session. On Amazon Connect the platform owns the managed PSTN voice channel. Bridging an outside carrier into Connect with a Chime Voice Connector is not a supported pattern unless AWS reviews it. When an SBC forks the voice leg to a recorder, that fork is SIPREC, a different plane from the customer dialog.
AI agents A voice bot still needs a session. On Amazon Connect the platform owns the managed PSTN voice channel. Bridging an outside carrier into Connect with a Chime Voice Connector is not a supported pattern unless AWS reviews it. The FreeSWITCH manual page also describes SignalWire, founded by the FreeSWITCH team, as a hosted platform with AI agents behind REST APIs and SWML.
Sources and go deeper
- Cisco Unity Connection — last checked 2026-10
- Cisco Unified Communications Manager — last checked 2026-10
- RFC 5806 — last checked 2026-10
- RFC 7044 — last checked 2026-10