Every call through CUBE uses two dial peers: one inbound and one outbound. Most CUBE problems come from the wrong inbound dial peer being matched, which silently applies the wrong codec, DTMF or SIP profile settings.
Inbound matching order (SIP)
- Explicit URI matching (incoming uri via / request-uri / to / from) is checked first.
- Then incoming called-number, then answer-address, then destination-pattern.
- If nothing matches, CUBE uses the default dial peer 0, which is almost never what you want.
voice class uri ITSP-IN sip
host ipv4:203.0.113.10
!
dial-peer voice 100 voip
description Inbound from ITSP
session protocol sipv2
incoming uri via ITSP-IN
voice-class codec 1
dtmf-relay rtp-nteDesigning for scale
Match inbound calls on the source (the via or from host) rather than on numbers, then use dial-peer groups or destination E.164 pattern maps to select outbound peers. You get fewer peers, deterministic behaviour and simpler troubleshooting.
Go deeper: our CUBE Professional training covers this topic with hands-on labs.