Home / Cloud voice and CCaaS SIP
Cloud voice and CCaaS SIP
Documented SIP boundaries for Teams, Webex Calling, Amazon Connect, Five9, Twilio, Genesys, and NICE CXone.
7 rooms42 quiz items
Rooms
- Teams Direct Routing signaling
Direct Routing uses the pstnhub proxies on 5061, a certified SBC, and a verified domain. Contact must be an FQDN.
- OPTIONS health and SRTP media
OPTIONS followed by 200 marks the SBC healthy. Media processors use SRTP. The protocol article’s OPTIONS CSeq cell disagrees with RFC 3261.
- Webex Calling Local Gateway
An IOS XE Local Gateway uses SIP TLS and SRTP. Third-party SBCs use a certificate-based trunk. Wildcard certificates are not supported. ByoPSTN means bring your own PSTN.
- Three PSTN choices, one per location
Webex Calling offers Cisco Calling Plan, Cloud Connected PSTN, or premises-based PSTN through a Local Gateway. A location has one PSTN connection.
- Amazon Connect voice boundaries
Ordinary Connect calls use managed PSTN. SIPREC can feed a conversational analytics connector. A carrier bridged through Voice Connector is not the supported pattern.
- Five9 BYO SIP and Twilio trunks
Five9 BYO SIP connects your ITSP or gateway to Five9 SBCs. Twilio termination and origination are different directions, with a strict Request-URI rule.
- Genesys BYOC and NICE CXone SIP
BYOC Cloud and BYOC Premises can be combined. NICE CXone documents SIP trunks on 5060 and 5061 with dynamic RTP and SRTP. Confirm carrier details with NICE.
Ecosystem
SIP does not replace workforce management, quality monitoring, CRM, emergency policy, or a messaging registry. It is the session seam those systems hang from. Compliance notes on this page are educational and are not legal advice.
Sources and go deeper
- Plan Direct Routing — last checked 2026-10
- Direct Routing SIP protocol — last checked 2026-10
- Direct Routing definitions and RFCs — last checked 2026-10
- RFC 5923 — last checked 2026-10