Home / Cisco CUBE, CUCM, and Unity Connection / CUCM trunks, SIP profiles, and Lua
CUCM trunks, SIP profiles, and Lua
A CUCM SIP trunk and a CUCM SIP profile are not the CUBE voice class. Lua normalization scripts exist. MTP required is version-specific.
Learn in 5 minutes
- Separate CUCM objects from CUBE sip-profiles
- Remember that Lua scripts exist
- Confirm MTP required in the guide for that version
Visual
Do not configure one product with the other product’s syntax.
Worked example
Dissect the trunk INVITE This INVITE leaves CUCM toward CUBE. Which host is in Contact?
Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.
Fault
The phone offered media from 203.0.113.10. The trunk INVITE offers c=198.51.100.30 and the call fails when that address is not a valid media path.
The connection address became the CUCM address.
Quiz
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.
Sources and go deeper
- Cisco Unified Communications Manager — last checked 2026-10
- Cisco CUBE SIP profiles (IOS XE 17.6+) — last checked 2026-10
- RFC 3264 — last checked 2026-10
- RFC 3261 — last checked 2026-10