Service Route Table Element
The Service Route Table Entry page is used to configure a single entry for routing a call to a treatment or announcement. The Service Route Table Element object is created under the Service Route Tables object. To create the Service Route Table Element object, right click on the Service Route Tables object and select New Service Route Element. The Service Route Table Element will allow a user to configure rules and criteria on routing a call to a treatment. As displayed in the screen capture below, multiple route elements can be created under the Service Route Tables object. The IMG 2020 looks at the Service Route Elements within the Service Route Table and selects the element that meets its criteria. Refer to the Digit Matching topic for information on how the IMG 2020 selects the elements. See information below which explains the different features for each of the fields within the Service Route Table Element object.
Web GUI Page
Dialogic > Routing Configuration > Service Routing Tables > Service Route Table > New Service Route Table Element
Maximum Objects
The IMG 2020 will allow up to 66 combined Route Tables, Cause Code Tables, Time Of Day Tables and Service Routing/TOD Tables to be configured. The IMG 2020 has a max capacity of 100,000 combined entries of the tables mentioned above. For example, the IMG 2020 supports creating 20 Route Table objects and each Route Table supports up to 5000 entries.
Related Topics and Dependencies
Field Descriptions
ID
The Entry ID is automatically populated with the next available ID number. To modify, click in the Entry ID field and select from drop down menu. ID's range from 1 to 5000
Enable
The enable field enables or disables each individual Service Route Table Element. The element can be enabled and disabled without having to recreate it.
True - The Service Route Table Element is enabled and will be added to the Service Route Table database.
False - The Service Route Table Element is disabled and will be omitted from the Service Route Table database.
Route Criteria Type
Below are selections from drop down menu under Route Criteria Type. The Routing Criteria Type refers to a manner used to determine the appropriate path over which the call is transmitted or routed.
Route Criteria Type Value | Description |
Dialed Number | Router will match the dialed number entered in the Router String field. (i.e. - Called Party Number). |
Originating Number | Router will match the originating number. (i.e. - Calling Party Number). |
Channel Group | Router will match on the channel group configured in the In Channel Group field. |
Called NOA | Router will match on the Called Party Nature of Address value. When Called NOA is selected, the Criteria Values field below can now be modified. Select the Criteria Value from that drop down menu. |
Calling NOA | Router will match on the Calling Party Nature of Address value. When Calling NOA is selected, the Criteria Values field below can now be modified. Select the Criteria Value from that drop down menu. |
FCI | The router will match on the Forward Call Indictor value. Once FCI has been selected, the FCI M bit field can now be modified |
Router String
Click in the Router String field and enter the string of digits the IMG 2020 will match on. The Router String field becomes available when the Routing Criteria Type is either set to either Dialed Number or Originating Number. The valid characters are 0-f, X, and &. Refer to the Digit Matching and IMG 1010 - Digit Translation Examples topics for more information on the digits supported. The Router String field supports a maximum of 32 digits.
In Channel Group
The In Channel Group field has a drop down menu which lists of all the Channel Groups configured. The In Channel Group field becomes available when the Routing Criteria Type is set to Channel Group. The field is shaded green and cannot be modified when any Routing Criteria other than Channel Group is selected.
Criteria Values
Select from drop down menu the Criteria or NOA Values to be utilized. This field can be modified when the Routing Criteria Type field is set to either Called NOA or Calling NOA only. The field is shaded green and cannot be modified when any Routing Criteria other than Called NOA or Calling NOA is selected.
FCI - M bit
The FCI M bit field is initially set to Not Used. If the Routing Criteria Type field is set to FCI then this field can be modified. Below are the choices in the drop down menu of this field.
Don't Care - Doesn't matter what value of M-Bit in the ISUP IAM is. Route Call using Route Action Type below.
0 - Route call using Route Action Type field below when the value of the M bit in the ISUP IAM is 0.
1 - Route call using Route Action Type field below when the value of the M bit in the ISUP IAM is 1.
The FCI M bit routing feature was designed to be utilized following the Brazilian ITU specifications. Using this field for other protocols such as ANSI may result in unintended outcomes.
Route Action Type
What action to take once the incoming calls criteria has been matched is decided in the Route Action Type Table.
Treatment Table - Play the treatment selected in the Treatment Element field below before routing the call. The call is eventually routed using the routing criteria above. Treatment Table will be the only selection in the drop down menu.
Treatment Element
Select from drop down menu all the treatments/announcements configured. Refer to the Treatments and Announcements section in the Table of Contents for procedures on how to configure the IMG 2020 to configure/play a treatment.