TCAP CNAM Database Queries

When making a call there are instances where the calling party's name is not in the incoming IAM message. For these instances, the TCAP CNAM Queries for ISUP to SIP Calls feature was developed. When this feature is configured/invoked the IMG 2020 will examine the incoming IAM and determine whether to do a CNAM Database lookup to determine the calling party's name. Once the calling party's name is found in the CNAM database it will be inter-worked into the From: header in the SIP INVITE message. The TCAP CNAM Database Queries feature gives the called party or application the ability to access the Calling Parties number if needed. This feature supports TCAP ANSI and is supported on calls going from SS7 to SIP. Refer to the TCAP/CNAM Configuration information below on how to configure using the Web GUI application. 

Diagram

1. The IMG 2020 processes the incoming IAM message and determines whether or not a CNAM query is required. (Calling Party must be 10 digits and Nature Of Address must be national number or unique national number).

2. If a CNAM query is required, the TCAP CNAM Service will be invoked to make a CNAM Query to the CNAM database.

3. Once the response from the CNAM database is received, the information is processed and eventually sent out in the outgoing SIP INVITE message with the calling party's name in the From: Header.

Call Flow Diagram

Call Trace

To view Call Trace click on the Call Trace - CNAM - SS7 to SIP topic. 

Additional Information

• CNAM Queries feature is supported in ANSI, the ITU protocol is not supported.* The CNAM Query feature is supported on SS7 to SIP calls only.

• If CNAM Service is not enabled and the Generic Name Parameter is present in the IAM, the call will proceed and the Generic Name will not be sent to the SIP side.

• If the Generic Name Parameter is present in the incoming IAM and the Type of Name subfield is set to something other than 001 (Calling Name) then the Generic Name information will be discarded and the IAM shall be processed as if no Generic Name Parameter is present.

• If the Generic Name Parameter is present in the incoming IAM and the Type of Name subfield is set to 001 (Calling Name) and the Availability subfield is coded “1” to indicate name not available, then unavailable will be sent in the display name section of the From: header in the outgoing SIP Invite message.

• If a Calling Party Number parameter is not included in the incoming IAM, then unavailable shall be sent in the display name section of the From: header in the outgoing SIP Invite message.

• If a Calling Party Number parameter is included in the incoming IAM and the Nature Of Address indicator is set to something other than unique national number (0x03) or non-unique national number (0x73), then unavailable shall be sent in the display name section of the From header in the outgoing SIP Invite message.

• If a 10-digit number is not included in the address contents of the Calling Party Number parameter, then unavailable will be sent in the display name section of the From: header in the outgoing SIP Invite message.

  • If a Generic Number Parameter is present in the incoming IAM, use shall be made of the presentation subfield along with the TCAP Generic Number presentation subfield to determine what shall be sent in the display name section of the From: header in the outgoing SIP Invite message. Below is table displaying what will be displayed.

• The IMG 2020 supports up to 32,768 simultaneous TCAP dialogs.

• If configuring a service such as CNAM or MWI on multiple IMG 2020 nodes, the SS7 Stack ID's cannot be configured with the same ID. For example, when configuring a IMG 2020 Node 0 with stack ID's 0 and 1 then any other nodes configured under any Logical Node can not have any of the stacks configured using the same ID's (0 or 1). By doing so, the TCAP services cannot be configured.

Configuration

Initial Configuration

The procedure below explains how to configure the IMG 2020 to initiate CNAM database queries. Before configuring, the IMG 2020 must have an initial configuration created on it. Follow the Basic Configurations procedure before proceeding onto configuring the MWI feature.

Configure SIP Profile

• 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. In this example the profile was named SIP_CNAM_Profile. Refer to the  SIP Profile - SGP topic for more information on configuring each of the individual fields.

Create SIP Channel Group

• 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 IMG 1010 - Configuring Routing 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_CNAM_ChGrp.

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

• Click back on the Channel Groups object. The channel groups object will display a yellow exclamation point in the icon. This indicates the configuration has not been sent to the IMG 2020 yet. Click on the Download Resource Tables button in the object pane and the channel group configuration will get sent.

Create an External Gateway

The SIP Channel group needs to communicate with an external SIP entity in the network. 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_CNAM_GW

For more information refer to the External Gateway topic.

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 Incoming SIP side of the configuration is complete. Follow instructions below to configure the outgoing SS7 side.

Configure SS7 Stack

An SS7 stack must be configured.

Configure SS7 Signaling and SS7 Network

When configuring SS7 signaling, an SS7 Network is created. The first two objects are the SS7 Signaling and SS7 Network objects. Follow the instructions below to create these objects.

• Right click on the Dialogic object and select New SS7. The SS7 object is a parent or container object and no configuration is needed within this object. Refer to the SS7 - Signaling topic for more information.

• Right click on theSS7object and select New SS7 Network. Select a Network ID from the drop down menu. Refer to the SS7 - Network topic for more information on this object.

• Right click on the SS7 Network object and select New SS7 Nodes. The Nodes object is a parent or container object and no configuration is needed in this object. Refer to the SS7 - Nodes topic for more information on this object.

• Right click on the SS7 Nodes object and select New Primary Node. Within the Primary Node object select from the drop down menu which node will be utilizing the SS7 network that is being created. Refer to the SS7 - Nodes - Primary Node topic for more information on this object.

Configure SS7 Stack

Configure the SS7 signaling stack and enter its Originating Point Code. Follow procedure below.

• Right Click on the SS7 Network object and select New SS7 Stack. An SS7 Stack Pane will get created. Enter the information needed for your specific network.

• Enable SCCP and TCAP signaling in the stack. Select ANSI from drop down menu of both the SCCP and TCAP fields. The CNAM feature is supported in ANSI only.  See screen capture below.

Refer to the topic for more information on configuring the individual fields of the SS7 Stack object pane. 

Configure SS7 Link Set

A signaling link set is an abstract path between the IMG 2020 and an APC (Adjacent Point Code). Within each link set, multiple physical signaling links can be added. A signaling stack must be assigned to all links in a link set. A typical configuration consists of two link sets. When configuring multiple SS7 stacks, the Link Set ID's assigned to each signaling stack must be different. For example, if Link Set ID is assigned to Stack 1, it cannot also be assigned to Stack 2.

• Right click on the SS7 Stack and select New SS7 Link Set. The Link Set ID is automatically populated with the next available ID.

• In the APC (Adjacent Point Code) enter the point code to which this link set will be connected. The format of the APC needs to follow the format given to the OPC. For example if the OPC is ANSI 97, which follows the format 7-7-7, the APC should also be running ANSI 97 and follow the 7-7-7 format. For more information on configuring the Link Set object refer to the SS7 - Link Set topic.

Configure SS7 Link

An SS7 Signaling Link is a point-to-point connection between two SS7 point codes (For example: A IMG 2020 and an STP). The Signaling Link is configured under the Signaling Link Set. The place holder assigns a physical location in the IMG 2020 (timeslot) and a previously configured Signaling Link Set to a Signaling Link. When configuring multiple stacks, the Link ID's assigned to each signaling stack must be different. For example, if Link ID:1 is assigned to Stack 1, it cannot also be assigned to Stack 2.

• Right click the desired SS7 Link Set and select New SS7 Link. The Link ID field is automatically populated with the next available ID.

• In the BDN Node field will display the node created within the SS7 Nodes object. Select from drop down menu which node the link being created is associated with.

• In the Span and Channel fields, select the DS-1/DS-0 that the link will be created on. The Span and Channel fields have a  drop-down menu which includes all the DS-1's/DS-0's available on the specific node selected. By default the first available DS-1/DS-0 is displayed. For more information on the individual fields in the SS7 Link pane refer to SS7 - Link Set - Link topic.

Configure the Destination

The SS7 Destination object communicates to the stack the Destination Point Code of the SS7 endpoint. The SS7 Destination is termed as the endpoint in an SS7 network and is not considered any of the signaling transfer points the SS7 signaling passes through to get to the endpoint. Follow procedure below.

• Right click on the SS7 Stack again and select New Destination. The Destination ID is automatically populated and cannot be modified.

• Enter the point code of the endpoint in the DPC field.

  • ITU - Point codes range from 0-0-0 to 7-255-7.

  • ANSI - Point codes range from 0-0-0 to 255-255-255.

Configure SS7 Routes

The path the SS7 signaling messages pass going from the OPC (Originating Point Code) to the DPC (Destination Point Code) is the SS7 Route. When configuring multiple SS7 stacks, the Route ID's assigned to each signaling stack must be different. For example, if Route ID:1 is assigned to Stack 1, it cannot also be assigned to Stack 2.

• Right click on the Destination object and select New SS7 Route. The SS7 Route pane appears. The Route ID field is automatically populated with the next available ID.

• Select the Linkset that will be used from the drop down menu of the Linkset field.

• Use the Comments field to enter a meaningful name to identify the route. For more information on the SS7 Route pane refer to the SS7 - Destination - Route topic.

Configure SCCP/TCAP functionality

• Right click on the SS7 Stack object created above and select New SCCP/TCAP. The SCCP/TCAP pane is a parent or container object and no configuration is needed here. This pane will allow you to configure other objects that have to do with SCCP/TCAP. Refer to SCCP - TCAP topic for more information on this pane.

• Right click on the SCCP/TCAP object and select New Subsystem Number. Select a Subsystem Number from the drop down menu. The Subsystem Number Status is by default set to Prohibited. Using the buttons just below the Subsystem Pane, click on the Allow button and the status will change to Allowed. Refer to the Subsystem Number topic for more information on configuration of the Subsystem Number Pane.

• Right Click on Subsystem Number and select New Adjacent Translator. Select from drop down menu the Adjacent Point Code that will be used. The point codes in drop down menu are point codes from the DPC of the Route ID. Refer to the Adjacent Translator topic for more information.

Configure GCL Services for SIP to TCAP Interworking

• Right click on the SS7 Network object again and select New GCL Services. The GCL Services object is a parent or container object and no configuration is needed here. Refer to the GCL Services topic for more information on this object.

• Right click on GCL Services object and select New CNAM SIP-TCAP Interworking. In the Subsystem field, select from the drop down menu the stack that was created earlier. Refer to the screen capture below. For more information on the SIP-TCAP CNAM (Interworking) object, refer to the IMG 1010 - SIP - TCAP CNAM topic.

• Once the GCL Service has been created, the new service can be added to the SIP Channel Group created above. Right click on the SIP Channel Group created above and select New Channel Group Service. Refer to the Channel Group Service topic for more information on this object.

• Select from drop down menu the service that will be associated with this channel group. See screen capture below.

Configure the SS7 ISUP Group and Circuit Group (CICs)

Under the Destination object, multiple ISUP Groups can be created. The ISUP Groups created will be linked to the Channel Group object which will be completed in the next section. Follow procedure below which creates an ISUP Group.

• Right click the Destination object again and select New SS7 Group. Select from the drop down menu of the ISUP Profile field which ISUP Profile will be used in the ISUP Group being created. Refer to the ISUP Group topic for more information on configuring each of the separate fields within this object.

• OPTIONAL: Right click on the SS7 ISUP Group created and a list of advanced ISUP Group parameters will appear. Select one or more parameters to be added to the ISUP Group being created. Refer to the Configure ISUP Group Advanced Parameters topic for information on each of the individual parameters.

• Right click on the SS7 ISUP Group object again and select New SS7 Circuit Group. In the Node Name field, select the Node from which the DS-1's and DS-0's will be used to create the CICs. The nodes in the list will be from the list of nodes under the SS7 Nodes object created earlier.

• Select from the drop down menu of the next four fields, the Starting and Ending Spans/Channels (DS-1's/DS-0's). The DS-1/DS-0's in the drop down lists will be all the DS-1's/DS-0's available on the node selected above.

• Enter a Starting CIC number into the Start CIC field. Refer to the SS7 - Circuit Group under Signaling topic for more information on this object.Configure SS7 Channel Groups and a second SS7 Circuit Group

Configure an SS7 Channel Group to communicate with the local SS7 network.

• Right click on the Channel Groups object and select New Channel Group. In the Name field, either accept the default name entered or enter a name that will identify this specific Channel Group.

• Select SS7_ISUP from the drop down menu in the Signaling Type field. For more information on configuring the SS7 Channel Group refer to Channel Group topic.

• Right Click on the SS7 Channel Group created and select New Circuit Group. As described in the Configure the SS7 ISUP Group and Circuit Group (CICs) section above, select the node and DS-1'S/DS-0's that will be used for this circuit group. The selections made should mimic the selections made in the section above. Refer to the SS7 - Circuit Group under Signaling topic for more information on this object.

• Click on the Channel Groups object which will now have a yellow exclamation point displayed. Click on the Download Resource Tables button and the SS7 Channel Group configuration just created will be sent to the IMG 2020.

• Configuring the CNAM feature has been achieved. Below is screen capture of the Routing Configuration directory tree when finished configuring.