Source note · Setting up a Bandwidth SIP trunk
Cisco advises against catch-all dial-peer patterns such as destination-pattern .T on CUBE and recommends routing only known phone number ranges or SIP URIs, because generic patterns raise the likelihood of routing a fraudulent call.
Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unified Border Element (CUBE)
- Subsystem
- toll-fraud prevention
- Deployment
- on-premises, virtual
- Region
- not restricted
- Release range
- IOS XE; source dated 2023-04-10
- Checked
- 2026-09-30
Sources
- Cisco Guide to Harden Cisco Unified Border Element (CUBE) Enterprise Devices — Cisco Systems · tier 2 current vendor documentation · Toll-fraud prevention, dial-peer patterns
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up a Bandwidth SIP trunk: source note bandwidth-sip-trunk-setup-cube-avoid-catch-all. WarmTransfer. https://warmtransfer.net/knowledge/claims/bandwidth-sip-trunk-setup-cube-avoid-catch-all
BibTeX
@misc{warmtransfer-claim-bandwidth-sip-trunk-setup-cube-avoid-catch-all,
title = {Setting up a Bandwidth SIP trunk: source note bandwidth-sip-trunk-setup-cube-avoid-catch-all},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/bandwidth-sip-trunk-setup-cube-avoid-catch-all},
note = {Source note bandwidth-sip-trunk-setup-cube-avoid-catch-all, checked 2026-09-30}
}