IMG 1010 - SIP Redirect IMG Initiated 302 - Example

The IMG already supports receiving 3xx Redirection messages. Feature 1442 will add the ability to initiate a SIP Redirect by sending a 302 message back to the originating gateway with information of other IMG's in the route list or route table that the originating gateway can send the invite message to. Procedure below will explain configuration of the SIP Redirect - IMG Initiated Redirect.

SIP Redirect Diagram

Procedure

The procedure below explains how to configure the 2020 IMG to function using the SIP Redirect 302 Initiated response message. First, please read the IMG 1010 - SIP Redirect IMG Initiated 302 topic for an understanding of how the feature functions. Once ready to configure, verify that an initial Basic Configuration is already configured on the IMG. If not, refer to the first section labeled Create IMG's along with the facilities. Once all initial steps have been executed the 2020 IMG can be configured for the SIP Redirect IMG Initiated 302 response feature. Follow steps below:

Create IMG's along with the facilities

Configure three Physical IMG's. Refer to the IMG 1010 - Logical IMG and IMG 1010 - Physical IMG topics.
Create TDM Profile for TDM spans. Refer to the IMG 1010 - Configuring T1 or E1 Bearer Profile - 10.5.x topic.
Create IP Bearer Profile for and IP Bearer Spans. Refer to the IMG 1010 - IP Bearer Profile topic.
Create facilities for each of the three IMG's. Refer to the IMG 1010 - Configuring T1 or E1 Bearer Spans - 10.5.x topic.
Configure VoIP modules for IP Channels. Refer to the IMG 1010 - IP Network (Interface) topic.

Create TDM Signaling

Referring to the diagram above, create the SS7 stack, SS7 Links, SS7 Routes, etc on IMG 0. The IMG 1 and IMG 2 nodes will be configured as remote SS7 nodes.

Create SS7 signaling on IMG 0. Right click on the Physical IMG0 object in the tree and select New Signaling. The signaling object will get created. The Signaling object is a container or parent object and no configuration is needed here. Refer to the IMG 1010 - Signaling Objecttopic for more information.
Right click on the signaling object and select New SS7. Leave the Redundancy Configuration field as StandAlone. Refer to the IMG 1010 - SS7 Signaling Object topic for more information on this object.
Right click on the SS7 Standalone object and select New SS7 Stack. Enter the Originating Point Code in the OPC field. Refer to the IMG 1010 - SS7 Stacktopic for more information on configuring the remaining fields in this object. For this example and demonstration purposes, the OPC will be given a value of 1-1-1.
Right click on the SS7 Stack and select New SS7 Link Set. Enter the Adjacent Point Code in the APC field. Refer to the IMG 1010 - SS7 Link Settopic for more information on configuring the remaining fields. For this example and demonstration purposes, the APC will be given a point code of 2-2-2. This is the point code of the PSTN from diagram above.
Right click on SS7 Link Set just created and select New SS7 Link. Select IMG 0 from the drop down menu in the IMG field. In this example, the link will be configured on IMG ID:0, Interface Offset ID:0, Channel 1. Refer to the IMG 1010 - SS7 Linktopic for more information on configuring the remaining fields.
Right Click on SS7 Link Set just created again and select New SS7 Route. In this example, the point code 2-2-2 was entered. This is the point code of the PSTN. Refer to the IMG 1010 - SS7 Route topic for more information on configuring the remaining fields in this object.
The SS7 stack, links, and routes have now been configured for the TDM side. If required, refer to the IMG 1010 - Configuring SS7 Signaling - 10.5.1 topic for more information on configuring SS7 signaling.

Create SIP Signaling Gateway Profile (SGP)

Right click on the Profiles object and select New SIP SGP. Change the SIP Profile ID to something other than ID:0 to allow the fields within the SIP SGP object to be modified.
In the SIP SGP object enter a name in the SIP Profile Name field to identify this object. In this example and for demonstration purposes, the SIP SGP Profile was labeled SIP_Redirect.
Verify the 3XX Redirect Support field is set to Enable (Default). For more information on the SIP SGP page refer to the IMG 1010 - SIP Profile - 10.5.3 topic.

Create SIP Signaling

A SIP signaling stack must be created for the incoming SIP protocol. Each of the IMG's that will be part of the SIP Redirected IMG Initiated 302 feature will need to have a SIP signaling stack configured on it. Refer to the IMG 1010 - Configuring SIP Signaling topic for information on how to configure a SIP Signaling stack on each of the IMG's being configured for this feature.

Create TDM Channel Groups

For the SIP Redirected IMG Initiated 302 feature to function properly there needs to be one TDM Channel Group with multiple ISUP Groups created under this one TDM channel group. For this feature we will have to configure one channel group with three separate ISUP groups. The steps below create the TDM channel group that is communicating with the PSTN. Refer to Diagram above as required.

Right click on the IMG EMS object and select New Routing Configuration. The Routing Configuration object is a parent or container object and no configuration is required here. Refer to the IMG 1010 - Routing Configuration Object topic for more information on this object.
Right click on Routing Configuration object and select New Channel Groups. Again, the Channel groups object is a container object and no configuration is required here. Refer to the IMG 1010 - Channel Groups topic for more information on this object.
Right click on Channel Groups and select New Channel Group. In the Name field, enter a name for this channel group. In this example and for demonstration purposes the channel group was labeled ChGrp1_SS7.
In the Signaling Type field, select SS7 from the drop down menu. Refer to the IMG 1010 - Channel Group topic for information on configuring the remaining fields.
Right click on the channel group ChGrp1_SS7 just created and select New ISUP Group. In the OPC-DPC field select the route that was configured when the TDM signaling channel group was created earlier in this procedure. In this example the OPC=1-1-1 and DPC=2-2-2 as displayed in the ISUP Group screen shot:
Right click on the ISUP Group created and select New Circuits. In the IMG Name field select IMG ID:0 which is the IMG with the stack configured on it. These CIC's will be communicating with IMG ID:0. Refer to the Circuits topic for more information on configuring the remaining fields in this object. Circuits object being configured for this example:
Repeat New ISUP Group and New Circuits steps above ISUP Group 2. ISUP Group 2 needs to be under the same Channel Group which was previously created.
Repeat New ISUP Group and New Circuits steps above ISUP Group 3. ISUP Group 3 needs to be under the same Channel Group which was previously created.
It is important that the ISUP Groups and CIC's all be part of the same channel group for the feature to function properly. Example Channel Group Tree:

Create SIP Channel Groups

Referring to the diagram above, three channel groups that are configured for the SIP protocol must be created. Follow procedure below to create the incoming SIP channel groups.

Right click on the Channel Groups object and select New Channel Group. In the Name field, enter a name to describe this channel group. In this example and for demonstration purposes, the channel group was labeled ChGrp1_SIP.
Select SIP from the drop down menu of the SignalingType field. For more information on configuring the remaining fields in this object, refer to the IMG 1010 - Channel Group topic.
Right click on the Channel Group just created and select New IP Network Element. Referring to the diagram above, select IMG ID:0 from the drop down list:

When selecting the IP network element under the SIP channel group, the network element selected should be configured as one of the Physical Nodes. The feature will not operate correctly if under the SIP channel group, the IMG selected was initially configured as an External Gateway. For Route list explained below it can be configured either way.

Create a second SIP Channel Group (ChGrp2_SIP) and IP Network Element:
Create a third SIP Channel Group (ChGrp3_SIP) and IP Network Element:

Create Route List

The next few steps configure the Route List section for this feature. Follow example below.

Right click on Routing Configuration object created earlier and select New Route Lists. The Route Lists object is a container or parent object and no configuration is needed here. Refer to the IMG 1010 - Route Lists topic for more information on this object.
Right click on Route Lists object and select New Route List. In the Route list object that appears, enter a name that identifies the route list being created. Refer to the IMG 1010 - Route List topic for information on configuring the remaining fields in this object.
Right click on the Route List object and select New Channel Group. An object pane as displayed below will appear. Within this pane will be a selection for Channel Group Type. The drop down menu will allow you to select either Normal or Redirect. If this will be one of the channel groups that will be part of the Redirect, select Redirect. Refer to screen capture below:
In the Group Name field, select one of the SIP channel groups created earlier for the feature. Only the configured SIP Channel Groups will be in this list:
Repeat the previous 2 steps to create up to three channel groups under the Route List object that are configured with the Redirect option.

The IMG supports creating up to three Channel Groups under the Route List object that have the Redirect option configured.

The SIP Redirect IMG Initiated 302 feature has now been configured