Calling Party Name (CNAM): We are used to seeing the incoming or originating telephone number (CallerID) display on our landline phone. Many people won’t answer a call if the CNAM data is ‘UNAVAILABLE’, ‘BLOCKED’, ‘UNKNOWN’ or ‘ANONYMOUS’. The databases containing CNAM data are maintained by the individual carriers (RBOC, ILEC, CLEC, WIRELESS) that offer voice services (>4000 in the US and Canada). These carriers in turn contract with a handful of service providers that then host the CNAM data on SCPs: AT&T, Verizon, CenturyLink, Cincinatti Bell, TNS, Telus, Syniverse, Accudata, Iowa Network and Cloud Stream Communications. Not all of the wireless carriers have chosen to allow their data to be loaded into SS7 accessible SCP databases.

• Transaction based solution
  This is a realtime transaction based solution where the carriers switch fabric sends SS7/TCAP or SIP INVITE messages to either the SS7 Controller Point Codes or the IPv4 public addresses managed by the Session Controllers (all in Converged SCPs operated by Cloud Stream Communications). The response message is either a properly formatted CLASS message containing the CNAM data element or is a SIP 3XX message using either a reformatted ‘From’ header or a ‘Contact’ header with the CNAM data properly embedded.

• Batch FTP solution
  There is an FTP site where the user can upload batch files.  Processing is continuous and each user account is configured with e-mail notification such that when a batch has been processed an e-mail is sent to the user with identifying batch information.  Batches are limited in size to one million records per file. The input argument is a ten digit telephone number per record query.

• C-SCP CapEx solution
  As carriers grow in traffic volume, t hey have the option of purchasing their own platform and software licenses allowing them  to bring this set of functions and services in house.