SIP CIC and DAI Codes

The IMG 2020 supports the Interworking of the ISUP IAM Carrier Identification Code (CIC) RFC 4694 and Dial Around Indicator (DAI) parameter draft-yu-tel-dai-00 into the R-URI of the SIP INVITE. The CIC and DAI parameter is enabled through the SIP Profile object. See the R-URI Header Tags description in the SIP Profile object for more information.

Carrier Identification Code: CIC

The CIC parameter consists of a three or four digit code which identifies information sent in the forward direction to a transit network. This parameter indicates the specific transit network selected by the originating subscriber. The CIC parameter is carried in the SIP INVITE request R-URI and maps to the Carrier Identification Parameter (CIP) or Transit Network Selection (TNS) Parameter in the ISUP IAM and vice-versa.

Dial Around Indicator: DAI

The DAI is included in the SIP INVITE request R-URI which identifies how the carrier in the Carrier Identification Code is chosen. The DAI parameter is carried in the SIP R-URI and maps to the Carrier Selection Information (CSI) Parameter in the ISUP IAM and vice-versa. Below is a table of the ISUP CSI and its corresponding value in SIP DAI.

Call Flows

SS7 to SIP

This call flow demonstrates that when the IMG 2020 receives an ISUP IAM request from the PSTN/SS7 which has the Carrier Identification (CIP) and Carrier Selection Information (CSI) Parameters included in the IAM message. These will be interworked to the cic and dai parameters of the SIP URI of the INVITE request.

Open

SIP to SS7 ANSI

This call flow demonstrates that when the IMG 2020 receives a SIP INVITE R-URI containing the cic and dai parameters, it will be interworked to the CIP and CSI of the ISUP IAM.

Open

SIP to SS7 ITU

This call flow demonstrates that when the IMG 2020 receives a SIP INVITE R-URI containing the ‘cic’ tag, that the IMG 2020 will interwork an IAM ISUP request to the SS7 ITU side with the Transit Network Selection.

SIP to SIP

The call flow below demonstrates that when the IMG 2020 is doing something like transcoding that the 'cic' and 'dai' values are passed through the IMG 2020 transparently.

The IMG 2020 interworks the ISUP Carrier Selection Information into SIP dai parameter

Configuration

To interwork the CIC and/or DAI codes, the configuration is achieved through the SIP Profile object. Follow procedure below to configure. 

Initial Configuration

Before configuring, the IMG 2020 must have an initial configuration created on it. Follow the Basic Configurations procedure before proceeding onto configuring the CIC and DAI codes feature.

Create a SIP Profile and enable ISUB Encoding

Create a SIP Profile object. Under the SIP Profile object, the SIP Advanced Settings object can be created. The CIC and DAI Tag feature is configured there. Follow procedure below

• Create a SIP Profile. Right click on the Dialogic object and select New Profiles. The Profiles object is a parent or container object and no configuration is needed here.

• Right click on the Profiles object and select New SIP Profile. The first profile that gets created is a Default SIP Profile and cannot be modified. Disregard this profile.

• Right click on the Profiles object just created again and select New SIP Profile. Either enter a Name into the name field that identifies this profile or accept the default entry. Refer to the  SIP Profile - SGP topic for more information on configuring each of the individual fields.

• Right click on the SIP Profile object just created and select New SIP Advanced Settings. Highlight the entry CIC and DAI entry in the R-URI Header Tags field. See screen capture below.

Create SIP signaling stack

• Right click on the IMG 2020 physical node and select New Signaling.  The Signaling object is a parent or container object and no configuration is needed here. Refer to the Signaling topic for more information on this object.

• Right click on the Signaling object created and select New SIP. In the IP Address field, select from the drop down menu which IP address will be used for SIP signaling. Refer to IMG 1010 - SIP Signaling Object topic for more information.

Create SIP Channel Groups

• Right click on the Dialogic object and select New Routing Configuration. The Routing Configuration object is a parent or container object and no configuration is needed here. Refer to the Routing Configuration topic for more information.

• Right click on Routing Configuration and select New Channel Groups. The Channel Groups object is a container object also and no configuration is needed. Refer to the Channel Groups topic for more information.

• Right click on Channel Groups object and select New Channel Group. Either enter a name that identifies this channel group or accept the default entry. In this example the Channel Group was labeled SIP_PCharge_ChGrp.

• Select SIP from the drop down menu of the Signaling Type field. Refer to the Channel Group topic for more information on configuring this object.

Create an External Gateway

The SIP Channel group needs to communicate with an external SIP entity. Create an external network element and then an external gateway that the SIP channel group will transmit messages to. Follow procedure below to communicate with a remote gateway.

• Right click on the Dialogic object and select New External Network Elements. The External Network Elements object is a parent or container object and no configuration is needed here. Refer to External Network Elements topic for more information.

• Right click on External Network Elements and select New External Gateways. The External Gateways object is a parent or container object also and no configuration is needed here. Refer to External Gateways for more information.

• Right click on External Gateways and select New External Gateway. Enter a name that identifies the gateway being configured. In this example the gateway was labeled SIP_CIC_DAI_GW.

Insert SIP External Network Element into SIP Channel Group

• Right Click on the SIP Channel group created and select New IP Network Element. Within the IP Network Element field, select from drop down menu, the gateway created. See screen capture below.

• Click on the Channel Groups object again. The Channel Groups object will have a yellow exclamation point in place of the icon indicating the configuration has not been sent to the IMG 2020. Click on the Download Resource Tables button and the new configuration will be sent to the IMG 2020.

• At this point, the P-Charge header has been configured into a SIP Channel Group.

Additional Information

• The dai parameter can appear in the uri at most once.

• The dai parameter is not present if the cic parameter is not present.

• Below is an example INVITE with CIC and DAI

Troubleshooting

If experiencing problems with this feature, verify the following:

• Verify the CIC and DAI entry is selected in the R-URI Header Tags field of the SIP Profile object.

• Verify the correct SIP Profile is assigned to the External Gateway.

• Verify the incoming IAM contains a value in the CIP or TNS parameter.

• The IMG 2020 forwards the CIC parameter only if it appears in the incoming INVITE message in the format displayed below: