DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
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.
% set profiles callRouting elementRoutingPriority <unique_identifier> entry <linear_call_type> <priority#, 0-999> entityType <callingNumber | carrier | none | trunkGroup>
The Element Routing Priority Parameters are as shown below:
Parameter | Length/Range | Description |
---|---|---|
| 1-23 | Element Routing Priority unique identifier. |
| N/A | Select linear call type:
|
< | 0-999 | Enter an entity priority. |
| N/A | The entity type. The possible values are:
|
% set profiles callRouting elementRoutingPriority Custom_ERP entry longDistanceOperator 999 % show profiles callRouting elementRoutingPriority Custom_ERP entry longDistanceOperator 999;