Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC

Because Cisco's command reference describes localhost dns as covering From, Call-ID and Remote-Party-ID but Microsoft requires the SBC FQDN specifically in Contact, an administrator should confirm the Contact header in a CUBE SIP trace and correct it with a SIP profile if it still carries an IP.

inferred · Checked 2026-09-30

Vendor: Cisco
Product: Cisco Unified Border Element
Subsystem: SIP headers
Deployment: on-premises
Region: not restricted
Release range: current as of 2026-09-30
Status: inferred
Checked: 2026-09-30

Sources

Cisco IOS Voice Command Reference - K through R - L — Cisco · tier 2 current vendor documentation · localhost command entry, read against ms-learn-dr-protocols-sip Contact header section

Cite this note

APA

WarmTransfer. (2026, September 30). Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-cube-contact-check. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cube-contact-check

BibTeX

@misc{warmtransfer-claim-cube-teams-direct-routing-setup-cube-contact-check,
  title  = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-cube-contact-check},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cube-contact-check},
  note   = {Source note cube-teams-direct-routing-setup-cube-contact-check, checked 2026-09-30}
}

Read in context