Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
CUCM and Webex beside Connect — Learn it in 5 minutes
About five minutes of reading
There is no AWS-managed CUCM CTI adapter in the docs this campus cites. The seam is the phone number.
Leave extensions on CUCM or Webex Calling. Claim or port the public contact-center numbers to Connect. When a Connect agent must reach a desk, transfer to that number. When a desk must reach the center, dial the Connect number. Webex Contact Center, if you still have it, is a second CCaaS during dual-run, not a component.
E911 for people who still have a CUCM phone can stay on CUCM. Agents who only have the CCP need the Connect E911 design in the Ecosystem track. Do not assume the PBX location covers a home agent on the CCP.
- Test the transfer in both directions.
- Codec and DTMF on the CUCM side still matter after the transfer.
- Caller ID from Connect must be a number CUCM's route plan accepts.
- Document which system records the second leg.
Number on this page: Seam PSTN. Transfer to phone number
Sources and go deeper
- Flow block in Connect Customer: Transfer to phone number - Amazon Connect Customer AWS docs. last checked 2026-10
- The voice channel in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- RFC 3261: SIP: Session Initiation Protocol | RFC Editor RFC. last checked 2026-10
- Session Initiation Protocol - Wikipedia Wikipedia. last checked 2026-10
- confirm Cisco Unified Communications Manager. Wikipedia. last checked 2026-10. Opened 2026-10. HTTP 404.