Customer case 03Call-routing issues within CUBE
Traffic landing on dial-peer 0 exposes a routing gap across the whole deployment.
- 1
Situation
FRINK consumes CUBE gateway CDRs and breaks call activity down by the dial-peer each leg matched. Meaningful volume showed up on dial-peer 0 – the gateway's built-in default, which a leg only matches when no configured dial-peer fits.
- 2
What the data showed
Dial-peer 0 carries none of the settings of the configured dial-peers – it accepts any codec, has VAD on and no DTMF relay – which explained the one-way audio and codec-mismatch drops users had reported.
Analytics · CUBE overview 
SIP debug · imported capture parsed into call flows and dial-peer decisions - 3
Resolution
The routing gap – a missing destination pattern and session target – was closed on every gateway with one template deployment, each gateway snapshotted before the change.