ClearIP Documentation

Routing

The ClearIP routing features allow users to choose how to route a call either through static routing or least cost routing. ClearIP can return up to 12 selected routes in a Contact header of a SIP 302 response. Users can configure ClearIP to return route destinations as IP addresses, FQDNs, or trunk group IDs.

SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Contact: <sip:+18554742536@1.1.1.1>;q=0.99, <sip:+18554742536@2.2.2.2>;q=0.98, <sip:+18554742536@3.3.3.3>;q=0.97, <sip:+18554742536@4.4.4.4>;q=0.96
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0

To use any of the routing features, routing must first be enabled in the SBCs page under the Organization dropdown menu.

ClearIP checks for routes in the Routing menu in the following priority order:

  1. Disabled Routes
  2. Inbound Routes
  3. Outbound Routes
  4. Least Cost Routing

Routes defined in the Disabled Routes, Inbound Routes, and Outbound Routes pages are considered static routes. If ClearIP finds a matching route within the static route pages, then ClearIP does not perform a least cost routing lookup on the call. ClearIP searches for routes in the following order: Inbound Routes first, then Outbound Routes, followed by LCR routes. If ClearIP finds matching routes in Inbound Routes, it exits routing and does not proceed to search Outbound Routes or LCR routes. Similarly, if it searches Outbound Routes and finds matching routes, it exits routing and does not search LCR routes. LCR routes will only be searched if there are no matching routes in Inbound Routes and Outbound Routes.

Location Routing Number (LRN) lookup

By default, ClearIP performs an LRN lookup on each call for number portability to make routing decisions. However, the visibility into the LRN data is restricted in ClearIP for accounts by default.

Due to NPAC requirements, ClearIP can only provide the LRN NPANXX information instead of the full LRN for customers by default. ClearIP can only provide the full LRN to registered NPAC users who are registered in all 7 regions to receive LRN data. For registered NPAC users in all 7 regions who require visibility of the full LRN information, please contact TransNexus support to verify NPAC registration permissions.

The Called LRN NPANXX field can be viewed in the SIP Messages page. The Called LRN field contains the full LRN and can only be viewed by registered NPAC users.

Disabled Routes

The Disabled Routes feature allows service providers to disable routing on certain calls.

Inbound Routes

The Inbound Routes feature allows service providers to create routing rules based on the dialed (DID) number. Inbound Routes can be applied based on the prefix of the dialed number regardless of whether the number has been ported.

Outbound Routes

The Outbound Routes feature allows service providers to create routing rules based on the LRN of the called number. Outbound Routes can be applied based on the prefix of the dialed number if the number has not been ported. If the dialed number has been ported, then the Outbound Route prefix field must refer to the LRN of the dialed number. The outbound routing table is searched after the inbound routing table.

Least Cost Routing (LCR)

When routing a call, service providers can choose from multiple carriers to route the given call. Finding the cheapest paths to routing calls can save money for service providers. ClearIP’s LCR features enable the minimization of termination costs and increased profit margins. Users must upload provider rate decks for ClearIP to determine cheapest routes.

Routing