Source note · Setting up CUBE for a carrier SIP trunk

When the carrier leg is reached through a registrar, outbound proxy or sip-server rather than a dial-peer session target IP, the carrier's signalling addresses may not be trusted automatically, so they should be added explicitly to the trusted list.

inferred · Checked 2026-09-25

Vendor: Cisco
Product: Cisco Unified Border Element
Subsystem: toll-fraud prevention
Deployment: on-premises
Region: not restricted
Release range: current as of 2026-09-25
Status: inferred
Checked: 2026-09-25

Sources

Cisco Guide to Harden Cisco Unified Border Element (CUBE) Enterprise Devices — Cisco Systems · tier 2 current vendor documentation · Toll fraud section; list of automatically trusted sources (session target, server-group) read against the Local Gateway guide's instruction to add PSTN and data-centre ranges

Cite this note

APA

WarmTransfer. (2026, September 25). Setting up CUBE for a carrier SIP trunk: source note cube-carrier-trunk-setup-registrar-trust-gap. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-carrier-trunk-setup-registrar-trust-gap

BibTeX

@misc{warmtransfer-claim-cube-carrier-trunk-setup-registrar-trust-gap,
  title  = {Setting up CUBE for a carrier SIP trunk: source note cube-carrier-trunk-setup-registrar-trust-gap},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cube-carrier-trunk-setup-registrar-trust-gap},
  note   = {Source note cube-carrier-trunk-setup-registrar-trust-gap, checked 2026-09-25}
}

Read in context