The PeerEdge Orchestrator determines whether a termination call is local as part of the broader jurisdiction determination process. Local (L) is one of several possible jurisdiction outcomes, alongside Interstate (E), Intrastate (A), and Indeterminate (U). The local determination applies only to United States calls where both ANI and DNIS resolve to the same state; it does not apply to Canadian or international calls.
Prerequisites
Before jurisdiction determination begins, the ANI and DNIS must each be resolved through LERG lookup. The LERG lookup requires the number to be exactly 11 digits (country code + 10 digits). If the number is not 11 digits, the LERG lookup is skipped entirely for that number.
- If the DNIS LERG lookup fails, the call is rejected with LERG_NOT_FOUND. The call does not proceed.
- If the ANI LERG lookup fails, the ANI is treated as unknown (state = X). The call continues, but jurisdiction will resolve to Indeterminate (U) because the originating state is unknown.
When an LRN (Location Routing Number) is available for the DNIS, the Orchestrator uses the LRN's LERG data (state, ratecenter, etc.) for the terminating side of the jurisdiction comparison rather than the dialed DNIS LERG data.
Important: this is a hybrid model for local jurisdiction. The LRN LERG data is used for the terminating-side geography comparison (country/state/ratecenter), while the exchange lookup used for local-pair validation still uses the dialed DNIS number.
Local Call Determination (USA Only)
Local determination is a three-step process that is only reached when the originating and terminating sides are both in the United States and share the same state. If the states differ, the jurisdiction is Interstate (E) and the LCAD is never consulted.
Step 1 — LERG Lookup
The LERG is queried using the NPANXXY (7-digit key) and NPANXX (6-digit key) derived from the ANI and the dialed DNIS. If an LRN exists, the LERG is also queried for the LRN. The 7-digit key is preferred; if it returns no result, the 6-digit key is used as a fallback. A successful lookup returns the state, OCN, LATA, ratecenter, and prefix type for each number.
Example: ANI = 19139545738 → keys 9139545 (NPANXXY) and 913954 (NPANXX)
Example: DNIS = 19133154925 → keys 9133154 (NPANXXY) and 913315 (NPANXX)
Step 2 — LCAD Exchange Lookup
The Local Calling Area Database (LCAD) cross-reference is queried using NPANXXY / NPANXX keys to identify which Exchange each number is assigned to. The 7-digit key is preferred; the 6-digit key is used as a fallback.
- The ANI exchange is the Originating Ratecenter Exchange (ORC).
- The dialed DNIS exchange is the Terminating Ratecenter Exchange (TRC).
If either exchange lookup returns no result, the jurisdiction defaults to Intrastate (A), not Local. The LCAD local pair check in Step 3 is skipped.
Step 3 — LCAD Local Pair Check
The LCAD is checked for the ORC/TRC exchange pair. If a match exists, the jurisdiction is Local (L). If no match exists, the jurisdiction is Intrastate (A).
Hybrid LRN + Dialed DNIS Behavior
When LRN exists, local jurisdiction determination combines two different terminating-side data sources:
- Geography comparison stage (country/state/ratecenter): uses LRN LERG data.
- Exchange pair stage (ORC/TRC local validation): uses dialed DNIS exchange lookup data.
This means local determination is not purely "all LRN" or "all dialed DNIS." It is intentionally mixed:
- LRN influences whether the call reaches the local/intrastate exchange decision path.
- Dialed DNIS influences whether that final exchange-pair validation returns Local (L) or Intrastate (A).
Example
Given ANI = 19139545738 and DNIS = 19133154925, both in Kansas:
- LERG resolves both numbers to state KS.
- LCAD exchange lookup: ANI → Exchange 20064370, DNIS → Exchange 20064370.
- LCAD local pair check: the pair 20064370 / 20064370 exists → jurisdiction = Local (L).
Jurisdiction Outcomes That Are Not Local
Jurisdiction | Code | Condition |
Interstate | E | ANI and DNIS (or LRN) are in different states |
Intrastate | A | Same state, but LCAD exchange pair not found (or exchange lookup failed) |
Indeterminate | U | ANI state is unknown, toll-free, or otherwise unresolvable |
International | I | DNIS is outside the USA/Canada NANPA region |
EEA | EEA | Both ANI and DNIS are in EEA countries |
For Canadian calls in the same province, the jurisdiction is always Intrastate (A). The LCAD local pair check is not performed for Canada.
Rate Deck Selection
Customer (Termination Customer Trunk Group)
For USA & Canada termination calls, the customer rate deck is selected using the following priority:
- Peering Rate Deck — used if assigned to the trunk group.
- Toll-Free Termination Rate Deck — used if the DNIS is toll-free and a toll-free termination deck is assigned.
- USCAN Rate Deck — the general USA/Canada deck.
- Local Rate Deck — used as a last-resort fallback if no other deck is assigned.
If none of these rate decks are assigned to the customer trunk group, the call fails with NO_CUSTOMER_DECK.
Vendor (Termination Vendor Trunk Group)
For USA & Canada termination calls, the vendor rate deck is selected per vendor trunk group using the following priority:
- Peering Rate Deck — used if assigned.
- Toll-Free Termination Rate Deck — used if the DNIS is toll-free and a deck is assigned.
- Local Rate Deck — used if the jurisdiction is Local (L) and a local deck is assigned.
- USCAN Rate Deck — the general USA/Canada deck.
If no applicable rate deck is assigned to a vendor trunk group, that vendor is not considered for routing. If no vendors have an applicable rate deck, the call fails with NO_VENDOR_DECK.
Key Difference Between Customer and Vendor Deck Selection
The Local Rate Deck is handled differently on each side:
- Customer side: The Local deck is the lowest-priority fallback (after Peering, Toll-Free, and USCAN).
- Vendor side: The Local deck takes priority over the USCAN deck when the jurisdiction is Local (L), allowing vendors to be rated with local-specific pricing when available.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article