In this section:

 

Element Routing Priority profile entries are similar to routing criteria in that they also select elements that must be factored into a routing lookup. The Element Routing Profile indicates what originating Call Processing Elements types (including "none") must be used to determine matching routing table entries. In contrast to the Routing Criteria entities, routing table lookups are attempted in priority order for all matching Call Processing Element types until a match is found.

Different Element Routing Priority tables can be associated with different (ingress) trunk groups or countries. If no Element Routing Priority table is explicitly associated with a trunk group, the Element Routing Priority table associated with the trunk group's country (or the default assigned to the country) is used.

Command Syntax

% set profiles callRouting elementRoutingPriority 
	<unique_identifier> 
	entry <linear_call_type> 
	<priority#, 0-999> 
	entityType <callingNumber | carrier | none | trunkGroup>

Command Parameters

The Element Routing Priority Parameters are as shown below:

Parameter

Length/Range

Description

elementRoutingPriority

1-23

Element Routing Priority unique identifier.

entry

N/A

Select linear call type:

  • _private
  • carrierCutThrough
  • internationalOperator
  • internationalType
  • ipVpnService
  • localOperator
  • longDistanceOperator
  • mobile
  • nationalOperator
  • nationalType
  • otherCarrierChosen
  • test
  • transit
  • userName

<entityPriority>

0-999

Enter an entity priority.

entityType

N/A

The entity type. The possible values are:

  • callingNumber
  • carrier
  • none (default)
  • trunkGroup

Command Example

% set profiles callRouting elementRoutingPriority Custom_ERP entry longDistanceOperator 999
% show profiles callRouting elementRoutingPriority Custom_ERP 
	entry longDistanceOperator 999;
  • No labels