Source record · tier 2 current vendor documentation
Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - SIP Trunk Monitoring
- Publisher
- Cisco
- URL
- https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/ios-xe/config/ios-xe-book/m_oodo-ping-group.html
- Published
- 2026-04-25
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only
Source notes citing this source
- With OPTIONS keepalive, a SIP dial peer is busied out only when all of its destinations (for example every server-group member) fail to respond. in context
- A keepalive profile is applied with voice-class sip options-keepalive profile <id> on the dial peer, and show dial-peer voice summary reports keepalive state. in context
- Using the same OPTIONS keepalive profile on several dial peers with different bind interfaces is not supported. in context
- CUBE can monitor a SIP trunk with out-of-dialog OPTIONS pings and busies out the dial peer when the target stops responding. in context
- A CUBE voice class sip-options-keepalive profile defaults to an up-interval of 60 seconds, a down-interval of 30 seconds and 5 retries. in context
- CUBE marks a dial peer busyout only when every destination in the dial peer (for example every target in its server group) has a heartbeat failure. in context
- For DNS SRV destinations, if CUBE gets a 503 or no response to an INVITE it marks that destination busyout and tries the next destination; the call is rejected if all destinations are busied out. in context
- On CUBE (IOS XE 17.6 onwards), a voice class sip-options-keepalive profile defaults to up-interval 60 seconds, down-interval 30 seconds, retry 5 and transport system. in context
- When several CUBE dial peers share one OPTIONS keepalive profile and that ping fails, all of the associated dial peers are busied out. in context
- In the DNS SRV case, Cisco's CUBE guide says CUBE monitors all destinations irrespective of the response it receives, naming 503 and 200 OK as examples. in context
- When an OPTIONS keepalive fails, CUBE busies out (makes inactive) every dial-peer associated with that profile, so calls can be routed elsewhere. in context
- CUBE's default up-interval of 60 seconds appears to fall inside the 60-to-180-second OPTIONS window Microsoft describes for Direct Routing, so a CUBE left at its defaults should not break Microsoft's frequency rule while the destination is up. inferred in context
- In a CUBE keepalive profile, down-interval sets how many seconds apart OPTIONS pings are sent while the destination's heartbeat status is Down. The default is 30. in context
- If an outbound proxy is configured on the dial-peer, or on a tenant associated with it, CUBE runs the keepalive session against the outbound proxy address. in context
- Dial-peers that share a destination can be grouped under one keepalive profile, so CUBE sends a single set of OPTIONS pings for the whole group instead of one set per dial-peer. in context
- On CUBE, an OPTIONS keepalive profile is created globally with 'voice class sip-options-keepalive <tag>' and attached to a dial-peer with 'voice-class sip options-keepalive profile <tag>'. in context
- CUBE does not support putting one keepalive profile on two or more dial-peers that have different bind interfaces, and does not support it in a multi-VRF setup. in context
- In a CUBE keepalive profile, retry sets how many failed OPTIONS pings are allowed before the heartbeat status changes from Up to Down. The default is 5. in context
- For a dial-peer whose destination is a server group, CUBE sets the dial-peer to BUSY only when none of the group's targets answer the OPTIONS ping. in context
- Commands for checking CUBE keepalive state are 'show voice class sip-options-keepalive <tag>', 'show dial-peer voip keepalive status <dp-tag>' and 'show dial-peer voice summary'. in context
- From Cisco IOS XE Cupertino 17.9.1a, CUBE can use OPTIONS keepalive to monitor every SRV host behind a DNS destination and spreads calls across those hosts by SRV priority and keepalive status. in context
- A CUBE keepalive profile has a transport option accepting tcp, tcp tls, udp or system, with system as the default, and a sip-profiles option that picks the SIP profile applied to the OPTIONS message. in context
- In a CUBE keepalive profile, up-interval sets how many seconds apart OPTIONS pings are sent while the destination's heartbeat status is Up. The default is 60. in context
- When SIP out-of-dialog OPTIONS pings to a monitored destination fail after all retries, CUBE busies out every dial-peer associated with that options-keepalive profile. in context
- The CUBE options-keepalive profile defaults are a 60-second up-interval, a 30-second down-interval and 5 retries. in context
- CUBE tests the members of a server group one at a time, not in parallel, when monitoring them with OPTIONS. in context
Cite this source record
APA
WarmTransfer. (2026, April 25). Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - SIP Trunk Monitoring. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cube-xe-sip-trunk-monitoring
BibTeX
@misc{warmtransfer-cisco-cube-xe-sip-trunk-monitoring,
title = {Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - SIP Trunk Monitoring},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-cube-xe-sip-trunk-monitoring},
note = {Cisco, accessed 2026-09-24}
}