Get new post automatically.

Enter your email address:


Number Processing in the CAMEL Event Reporting Flow

Number processing in the CAMEL event reporting flow is classified into number processing in the OCSI reporting flow and number processing in the TCSI reporting flow.
Number processing in the CAMEL event reporting flow refers to a process of normalizing numbers in the messages reporting the CAMEL events, which ensures that the subsequent CAMEL services can be normally triggered. Figure 1 shows the flowchart of the number processing in the OCSI and TCSI reporting flows.

Figure 1 Flowchart

Number processing in the CAMEL event reporting flow is applicable to all the CAMEL services triggered based on the information registered in the HLR and number segment configured on the MSC.
For details about IDP number normalization, see IDP Number Normalization.
Detail:

Table Description

Table Command Input Parameter Output Parameter Function Description
Special Service Number table ADD SPCLDN
  • Special service number
  • Minimum number length
  • Maximum number length
  • Trigger IN as toll
Based on the number dialed by the calling IN subscriber, the MSOFTX3000 queries the Special Service Number table to determine whether to trigger the OCSI service.
CSI Criteria Match Number Change Data table ADD CSIDNC
  • Called number address nature
  • Called prefix
  • DP number
  • Called number change name
Based on the called number address nature, called prefix, and DP number, the MSOFTX3000 queries the CSI Criteria Match Number Change Data table to determine whether to perform called number change.
IN Service Number table ADD SRVNUM
  • Service key
  • IN service number
  • DP number
  • Operator
  • Send ANM when PA flag
Based on the service key and IN service number, the MSOFTX3000 queries the IN Service Number table to adapt the DP number between the MSC and the SCP. In addition, the MSOFTX3000 determines whether to send the ANM message to the previous-hop office upon PA announcement playing based on the query result.