Cisco CUCM (SIP trunk)
Integration key: cisco-cucm-sip
For Cisco shops running CUCM where you want AI on the front end without changing your dial plan more than necessary. CallingEdge appears as a SIP trunk peer to CUCM. We answer the call, optionally bridge to CUCM extensions, and emit normalized webhooks back to your apps.
What you get
Section titled “What you get”- Outbound calls from your apps to phones / extensions reachable from CUCM
- Inbound calls from CUCM route patterns answered by AI
- Blind transfer via SIP REFER to any reachable destination
- Real-time call lifecycle webhooks
- Recording
What we need from you
Section titled “What we need from you”| Item | What it is |
|---|---|
| CUCM cluster reachable endpoint | FQDN or IP we point our SIP trunk at |
| Route pattern | The pattern on CUCM that routes inbound calls toward us |
| Trusted source IPs | Add our SIP termination IPs to your CUCM trunk security profile |
| Optional: AXL service account | Read-only is fine; used for health checks and pattern discovery |
| Inbound webhook URL | Where you want us to POST normalized events |
If you require an on-prem SBC (AudioCodes, Ribbon, AnyNode) in front of CUCM, that works too; we point at the SBC instead.
Setup at a glance
Section titled “Setup at a glance”- Send us the CUCM endpoint and (optionally) AXL credentials through the secure intake.
- We allowlist your CUCM and provision the SIP trunk.
- You add a route pattern on CUCM that targets our termination URI.
- Place a test call; we walk you through verifying the trace.
Limitations
Section titled “Limitations”- No wrap-up code surface (SIP trunks do not carry dispositions).
- Attended transfer not supported on this path; use blind transfer.