Overview:
F-1463 Route to a Cause Code allows the IMG to receive an incoming call and reject it with a cause code specified by the user. For example, a call comes into the IMG on Channel Group A. Channel Group A would route the call to a Route Table and then Route Table Entry. If Route Table entry is configured for this feature the IMG would reject the call and send the rejected call with the cause code out the same channel group the call came in on.
Configuration:
The configuration below covers the configuration of the feature above. It is assumed that the initial configurations such as Logical IMG, Physical IMG, Network Interfaces, Bearer Profiles, Facilities, Signaling and other initial configuration has already been accomplished. The procedure below will start from the Routing Configuration Pane within ClientView. The following configuration example will demonstrate a call coming into the IMG and it being rejected with Cause Code '003 - No Route To Destination'.
Call Flow Diagram:
Below is Call Flow diagram of the Route Call to a Cause Code feature. The procedure below will configure the IMG to follow this Call Flow diagram.
Create Incoming Channel Group:
The first step would be to create an incoming Channel Group. The incoming Channel group, configured for SS7, would receive the incoming call and route the call to a Route Table which would then send call to Route Table Entry.
Channel Group Initial Configuration:
Right Click on Dialogic IMG EMS and select New Routing Configuration. A Routing Configuration Pane will appear. See IMG 1010 - Routing Configuration Object for more information on this object.
Right Click on Routing Configuration and select New Channel Groups. A Channel groups container object is created. This object will allow multiple channel groups to be created beneath it. See IMG 1010 - Channel Groups for more information on this object.
Incoming Channel Group:
Right Click on Channel Groups Object and select New Channel Group. A Channel Group Object will appear. Enter a name for this channel group and set the 'Signaling Type' to 'SS7'. The Incoming Channel Group in this example will be an SS7 Channel Group and be named ChGrp_SS7. See IMG 1010 - Channel Group for more information on configuring the SIP channel group.
Create Route Tables and then Route Table Entries:
The routing for this feature will now be accomplished. The next few steps will configure the objects needed to reject the call.
Create Route Table and Route Table Entry:
Right Click on Routing Configuration and select New Routing Tables. The Routing Tables object created is a container object which will allow multiple individual Routing Tables to be created beneath it. See IMG 1010 - Routing Tables for more information.
Right Click on Routing Tables and select New Route Table. A Route Table object will get created. Enter a name for this Route Table. In this example the name will be RT1 for Route Table 1. See IMG 1010 - Route Table/Cause Code Table/Service Route Table for more information on configuring the Route Table Object.
Create a Route Entry under the Route Table by right clicking on Route Table and select Add Entry. A Route Entry screen will appear. Click in the 'Route Action Type' field and a drop down menu appears. Select Cause Code from the list as displayed below.
Once Cause Code is selected the last field in the New Entry pane will change to 'Reject Cause Code'. Select from drop down menu which cause code to send with the rejected call. In this example 'No Route to Destination' was chosen. See Below.
Select from drop down menu which cause code to send with the rejected call. In this example 'No Route to Destination' was chosen. See for a list of the Cause Codes.
Enter the Router String to match. In this example, the dialed number 5085551212 will be matched. See for more information on configuring this pane.
Configure Channel Group to access Route Table configured:
Once the Route Table and Route Entry are configured, go back to the Channel Group created. Select from drop down menu the Route Table just configured. See Below.
By selecting the Route Table, the rejected call with the Cause Code configured will be sent out this Channel Group.
Flow of above Configuration:
After configuring the Route Call to a Cause Code feature above the following bulleted list explains what happens once a call comes into the IMG and IMG rejects call with Cause Code configured.
Call comes into SS7 Channel Group labeled ChGrp_SS7. Within this Channel Group the Route Table field is set to RT1 - ID:5. This will send the call to Route Table RT1.
Route Table RT1 has one entry in it. The call then references this entry and sees that if the Router String 5088881212 is matched, reject this call with the cause code configured and send rejected message out Channel Group labeled ChGrp_SS7
ClientView Tree for above configuration:
Additional Information:
A compatibility issue arises when the GCEMS application being used supports the Route Call to a Cause Code Feature and the IMG system software being used does not. In this situation the GCEMS application tries to send information to the IMG which it does not understand. The IMG running the older software will ignore the messages and look for other routing tables etc. When IMG finds there is no routes it will reject incoming call with a 'No Route' message.
A compatibility issue arises when an older GCEMS application is utilized that DOES NOT support the Route to a Cause Code feature and the configuration file being utilized was created on a GCEMS application that supports the feature. In this scenario the GCEMS doesn't understand the new configuration and the new configuration file that applies to this feature will not get applied/configured.
The IMG will map the configured 'reject cause code' in the 'release' message so that the message corresponds to the protocol used for the incoming call. For Example: User configures a SIP cause code in the routing table but the incoming channel group is SS7, the IMG will map the SIP cause code to the SS7 cause code when rejecting the call.