Design inbound and outbound dial peers with clean destination patterns, COR (class of restriction) to block toll fraud, and translation profiles for NANP, international, and E.164.
Ad-hoc dial peers produce 40-entry messes with overlap, wrong priorities, and toll-fraud holes. This designer asks you five questions and outputs a clean, fully-commented dial peer block with COR, translation, and preference set correctly.
Set inputs, click Generate dial peers.
Carrier → CUCM + translation.
CUCM → Carrier with COR.
Always-allow 911/999.
Class of restriction lists.
E.164 ↔ extension mapping.
IOS-XE matches dial peers by longest match first, then preference (lower is better). Two dial peers with the same destination-pattern and different preference act as primary/backup. The easy trap: if you have destination-pattern .T (catchall) and destination-pattern +1.T (NANP), both match a 10-digit string, but +1 is longer so it wins. Good — that's usually what you want. But if you also have destination-pattern 9.T for access code, make sure the 9 gets stripped by your translation before CUCM hands it to CUBE.
COR (Class of Restriction) for toll fraud: create COR lists like toll-local, toll-ld, toll-intl. Apply corlist outgoing to each dial peer matching its toll level. Apply corlist incoming on the inbound side (from CUCM) based on the calling party's permission. Result: a lobby phone (class: local only) calling +44 gets rejected at CUBE, not 30 seconds into the carrier conversation when you're already being billed for the call setup.
Translation profiles: keep them direction-specific. from-carrier strips +1 and maps to internal extension. to-carrier prepends +1 and validates NANP format. Never apply the same profile in both directions — you'll double-translate and get weird A-numbers. Test each translation: test voice translation-rule 10 +14085551234 type international plan e164 — if the result isn't what you expect, fix the regex, not the dial peer.
.T everywhere?Creates toll-fraud surface. Specific patterns let COR restrict calls.
Voice class lets you reuse common settings across many dial peers (codec, srtp, translation).
Physically yes, but use dial-peer groups + voice class uri to reduce repetition.
Create a dedicated high-priority dial peer for 911 with preference 0 and no COR outgoing.
100 phones, 1 SIP trunk.
3 countries.
500 agents, outbound dialer.
Our UC Modernization Sprint re-designs dial plans for CUBE + CUCM + Webex Calling together, with test plan and rollback.