Route Table Element

 

 

The Route Table Element object is used to configure a single entry for routing. The Route Table Element object is created under the Route Table object. To create the Route Table Element, right click on the Route Table object and select New Route Element. The Route Table Element will allow a user to configure different rules and criteria for routing a call. As displayed in the screen capture below, multiple Route Table Element objects can be created under the Route Table object. These Route Table Elements  are displayed in the object table tab located below the Route Element object pane in the Web GUI Page. When a call is received, the IMG 2020 looks at the Route Table Elements configured under the 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 entries. Refer to the information below. 

Web GUI Page

Dialogic > Routing Configuration > Routing Tables > Route Table > New Route 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 Route Table Elements.

Related Topics and Dependencies

Routing Tables

Route Table

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 Route Table Element. The element can be enabled and disabled without having to recreate it.

True - The Route Table Element is enabled and will be added to the Route Table database.

False - The Route Table Element is disabled and will be omitted from the 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).

Prefix

This Prefix routing criteria will allow the user to associate a Prefix with an outgoing Channel Group. Note that the Prefix decoding needs to be enabled in SIP SGP.

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.

Multimedia Call

The IMG 2020 will route a call to a given endpoint when call is determined to be multimedia type. See Multimedia Call Routing. 

Router String

Click in the Router String field and enter the string of digits, or the prefix, the IMG 2020 will match on. The Router String field becomes available when the Routing Criteria Type is either set to either Dialed Number, Originating Number, or Prefix. The valid characters for digits are 0-f, X, and &. Refer to the Digit Matching and Digit Translations topics for more information on the digits supported. The Router String field supports a maximum of 32 digits.

The valid characters for prefix are a-z, A-Z, and -, for a maximum of 32 characters. 

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. Select Not Used if this field will not be utilized.

Criteria Values

Select from drop down menu the Criteria or NOA Values to be utilized. This field can be modified when the Routing Criteria Typefield is set to either Called NOA or Calling NOA only. Otherwise, it cannot be modified. 

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.

Route Action Type

Description

Channel Group/ Outgoing Channel Group

Route on a specific Channel Group. When Channel Group is selected, the field just below the Route Action Type field will be renamed to Outgoing Channel Group and will contain all available channel groups configured.

Route List/ Outgoing Route List

Route on a specific Route List. When Route List is selected, the field just below the Route Action Type field will be renamed to Outgoing Route List and will contain all available Route Lists configured.

Route Table/ Outgoing Route Table

Route on a specific Route Table. When Route Table is selected, the field just below the Route Action Type field will be renamed to Outgoing Route Table and will contain all available Route Table objects configured.

Treatment Table/ Treatment Element

Route on a specific Treatment Table. When Treatment Table is selected, the field just below the Route Action Type field will be renamed to Treatment Table ID and will contain the ID's of all the treatment tables created. Select the ID of the treatment table needed. Also, a Treatment Element field will be added just below the Treatment Table ID field. The Treatment element field contains a list of the audio files in the Treatment Table selected. Select the audio file from drop down menu.

Cause Code/ Route Action List

When the Route Action Type field is set to Cause Code the IMG 2020 will reject the incoming call with the cause code selected from the Route Action List field. The Route Action List field is created when Cause Code is selected. 

Outgoing Channel Group

The Outgoing Channel Group field has a drop down menu which lists of all the outgoing Channel Groups configured.

 

Return to Documentation Home I Return to Sangoma Support