IMG 1010 - TCAP CNAM Database Queries
Overview:
When making a call there are instances where the calling party's name is not in the incoming IAM message. For these instances, feature F-1662 TCAP CNAM Queries for ISUP to SIP Calls' was developed. When this feature is configured/invoked the IMG 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. Feature F-1662 gives the called party or application the ability to access the Calling Parties number if needed. This feature is being added in software version 10.5.3 and supports TCAP ANSI. This feature is supported on calls going from SS7 to SIP. Since TCAP is not supported on the IMG 1004, this feature is restricted to the IMG 1010 and is not supported on the IMG 1004. For more information on this feature, see information below.
Diagram:
The IMG processes the incoming IAM message. The IMG will determine 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).
If a CNAM query is required, the TCAP CNAM Service will be invoked to make a CNAM Query to the CNAM database.
Once the response from the CNAM database is received, the information is processed within the IMG/GCEMS and eventually sent out in the outgoing SIP INVITE message with the calling party's name in the From: Header.
If the calling party's number is not present in the IAM, then the SIP INVITE will contain "unavailable" in the From Header.
If the calling party's information is not to be divulged, then the SIP INVITE will contain "Anonymous" in the From Header.
Call Flow Diagram:
Call Trace:
Call Trace - CNAM - SS7 to SIP
Additional Information:
CNAM Queries feature was added in software 10.5.3 and is supported in ANSI. In software version 10.5.3 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.
IAM Presentation | TCAP Presentation | SIP From: Header |
Allowed (0x00) | Allowed (0x00) | Calling Name |
Allowed (0x00) | Restricted (0x01) | Calling Name |
Allowed (0x00) | Blocking Toggle (0x02) | Calling Name |
Allowed (0x00) | No Indication (0x03) | Calling Name |
Restricted (0x01) | N/A No Query launched | "private" |
Blocking Toggle (0x02) | Allowed (0x00) | "private" |
Blocking Toggle (0x02) | Restricted (0x01) | Calling Name |
Blocking Toggle (0x02) | Blocking Toggle (0x02) | "unavailable" |
Blocking Toggle (0x02) | No Indication (0x03) | "unavailable" |
No Indication -or- No Generic Number in IAM | Allowed (0x00) | Calling Name |
No Indication -or- No Generic Number in IAM | Restricted (0x01) | "private" |
No Indication -or- No Generic Number in IAM | Blocking Toggle (0x02) | "unavailable" |
No Indication -or- No Generic Number in IAM | No Indication (0x03) | "unavailable" |
The IMG supports up to 32,768 simultaneous TCAP dialogs
If configuring a service such as CNAM or MWI on multiple IMG nodes, the SS7 Stack ID's cannot be configured with the same ID. For example, when configuring an IMG Node 0 with stack ID's 0 and 1 then any other IMG Nodes configured under any Logical Node can not have any of the stacks configured with the same ID's (0 or 1). By doing so, the TCAP services cannot be configured.
Related Topics:
IMG 1010 - TCAP-CNAM Configuration - SS7 to SIP