debug voip dialpeer shows dial-peer manager results such as 'Result=Success(0); Incoming Dial-peer=1 Is Matched', and Cisco advises buffered logging because it generates a large volume of messages.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco IOS voice gateway
- Subsystem
- debugging
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Cisco IOS Debug Command Reference - Commands S through Z - debug voip avlist through debug vpm signaling — Cisco Systems · tier 2 current vendor documentation · command entry 'debug voip dialpeer', Usage Guidelines and example output (DPM/MatchNextPeer)
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-dialpeer-matchnext. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-dialpeer-matchnext
BibTeX
@misc{warmtransfer-claim-cube-dial-peer-matching-troubleshooting-dialpeer-matchnext,
title = {Troubleshooting CUBE calls that match the wrong dial-peer: source note cube-dial-peer-matching-troubleshooting-dialpeer-matchnext},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-dial-peer-matching-troubleshooting-dialpeer-matchnext},
note = {Source note cube-dial-peer-matching-troubleshooting-dialpeer-matchnext, checked 2026-10-02}
}