UCaaS
Open for Cisco Webex
Pair Open with Webex Calling via Local Gateway / SIP trunk and the AI picks up — Webex users, devices, and dial plans stay exactly as they are.
- Setup time
- Under 30 minutes
- Auth
- Digest credentials, IP allowlist, or LGW pairing
- Directions
- Inbound · Outbound · Call transfer
- Pricing
- Included with Open
01 — Overview
Can I add an AI phone agent to my Cisco Webex Calling setup?
Yes. Webex Calling supports external SIP routing via Local Gateway and direct trunk pairing; Webex Contact Center supports external routing destinations. Open plugs into either pattern.
Webex Calling remains the phone system. Users, devices (Cisco IP phones, headsets, Webex app), dial plans, hunt groups, and the Webex Control Hub all stay where they are. Open joins as a SIP destination on the side of your phone system that already speaks SIP — typically a Local Gateway (LGW) or a registered trunk to a third-party PSTN provider.
For Webex Calling with Local Gateway, the cleanest pattern is to add Open as a SIP destination reachable through the LGW. Inbound calls hit Webex, follow your hunt group / call queue / auto attendant routing, and at the point you'd hand off to an external endpoint you send the leg to Open over SIP. The AI picks up and the conversation runs over standard SIP/RTP.
For Webex Contact Center, the pattern is even more direct: Open is configured as an external routing destination on a queue or skill. Inbound calls matching the routing condition hand off to Open, the AI handles the conversation, and escalations transfer back into a Webex Contact Center queue via SIP REFER with the live transcript and detected intent attached.
What the AI does on the call: it listens, reasons over your knowledge base and connected tools (Salesforce, HubSpot, Zendesk, ServiceNow, calendar, payments), and acts. Every call is recorded and trace-logged on Open's side; on Webex's side the call leg appears in Control Hub analytics like any other SIP call.
Billing stays predictable. Cisco keeps invoicing your Webex seats and any Cisco-supplied calling plans. Open charges per resolved conversation, with no markup on Webex minutes and no extra Webex seats needed for an AI front-line.
What stays the same on Cisco Webex
Webex Calling users and devices
Seats, devices, hunt groups, and dial plans don't change.
Numbers and calling plans
Webex Calling numbers (or BYOC numbers via LGW) stay where they are.
Webex Control Hub
You manage the phone system the same way.
Webex devices and the app
Cisco phones, headsets, and the Webex app keep working untouched.
What's new with Open
A SIP destination via LGW or trunk
Open's SIP URI becomes a destination reachable from Webex via Local Gateway or a SIP trunk.
AI handles the conversation
On the queues / skills you opt-in, the AI greets, listens, calls your tools, and replies in natural speech.
Transfers carry context
Escalations to a Webex Contact Center queue or hunt group receive the live transcript via SIP REFER.
Pricing model
Open per resolved conversation. Webex seats and calling-plan minutes stay invoiced by Cisco.
02 — Why this works
The native Cisco Webex experience
Native SIP via Local Gateway
Open plays cleanly with Webex Calling's existing LGW pattern — no exotic licensing.
Webex Contact Center as a first-class target
Add Open as an external routing destination on a queue and route by skill, business hours, or overflow rules.
No new seats for AI
AI is a SIP destination, not a Webex user — your seat count doesn't change.
Warm transfer back to your Webex agents
When the AI escalates, the call returns to a Webex hunt group or Contact Center queue with the transcript attached.
03 — Setup guide
Wire up Cisco Webex in under 30 minutes
Two trunks — one inbound, one outbound. Both configurable from Settings → SIP in the Open dashboard.
- 1
Open Settings → SIP
Open the inbound trunk configuration in OpenCX.
- 2
Pick a SIP region
Choose Global, US, EU, or APAC.
- 3
Copy the SIP credentials
Grab the SIP endpoint, username, and password.
- 4
Pick the Webex target
Decide which hunt group, call queue, auto attendant branch, or Contact Center skill should route to AI.
- 5
Add Open as a SIP destination
Webex Calling: add Open as a route reachable through your Local Gateway. Webex Contact Center: add Open as an external routing destination on the queue/skill.
- 6
Add the matching numbers to Open
Under Phone Number (DID), add the Webex DIDs that fronted the queue.
- 7
Assign numbers to an AI agent
Channels → Phone → Agents → assign DIDs.
- 8
Place a test call
Dial a Webex number and confirm Open answers when the routing branches to AI.
04 — Configuration
Settings → SIP, at a glance
A real inbound trunk for Cisco Webex looks something like this. Yours are generated when you open Settings → SIP.
Inbound trunk · Webex
Sample
- SIP endpoint
- sip.us.opencx.comUS region
- Transport
- TLSrecommended
- Webex pairing
- Local Gateway / Trunk
- Username
- open_inbound_wbx…
- Password
- ••••••••••••••••
05 — Security
Encrypted, audited, refundable
SIP over TLS for signaling, SRTP for media. Every call is logged with full reasoning traces. SOC 2 Type II, GDPR-aligned, HIPAA- and PCI-ready. Backed by the Open $2M Refund Guarantee.
06 — FAQ
