Home / Oracle, Ribbon, and AudioCodes / Certificate names and Contact
Certificate names and Contact
The certificate name and the SIP Contact need to be names the peer accepts. Teams and Webex Local Gateway do not share a wildcard rule.
Learn in 5 minutes
- Match a certificate name to the SIP name
- Use an FQDN in a Teams Contact
- Keep Webex Local Gateway off wildcard certificates
Visual
The same file can be acceptable to one peer and rejected by another.
Worked example
Read the Teams Contact Dissect the TLS INVITE. Is Contact an FQDN or an IP?
Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.
Fault
Direct Routing returns 403. The INVITE is TLS to port 5061, and Contact uses 203.0.113.20.
The plan and protocol articles require a name in Contact.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Workforce management WFM forecasts volume and builds schedules. It consumes contact-center events. It does not parse Via headers. When a forecast is wrong, the SIP symptom is usually queue delay and 480 or carrier congestion, not a broken dialog ID.
Programmable communications APIs Twilio’s docs home is API reference, tutorials, and integration for Twilio products. Elastic SIP Trunking is the SIP-shaped product already cited in this lab. This page does not define the word CPaaS from an RFC. Read the vendor page before you copy a diagram that uses that word.
Sources and go deeper
- RFC 5922 — last checked 2026-10
- Direct Routing SIP protocol — last checked 2026-10
- Plan Direct Routing — last checked 2026-10
- Get started with Local Gateway — last checked 2026-10