Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC
When OPTIONS keepalive fails for every destination of a dial-peer, CUBE marks that dial-peer inactive (busyout); status is shown by show voice class sip-options-keepalive <id>, show dial-peer voice summary and show dial-peer voip keepalive status <tag>.
Checked 2026-09-30
A dial-peer is marked as busyout, only if all the destinations in the dial-peer have a heartbeat failure and fail to respond.
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- OOD OPTIONS ping
- Deployment
- on-premises
- Region
- not restricted
- Release range
- IOS XE 17.6 onwards
- Checked
- 2026-09-30
Sources
- Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - SIP Trunk Monitoring — Cisco · tier 2 current vendor documentation · Feature description; verification 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-keepalive-busyout. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cube-keepalive-busyout
BibTeX
@misc{warmtransfer-claim-cube-teams-direct-routing-setup-cube-keepalive-busyout,
title = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-cube-keepalive-busyout},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cube-keepalive-busyout},
note = {Source note cube-teams-direct-routing-setup-cube-keepalive-busyout, checked 2026-09-30}
}