Configure the SCCP Address for Requests

Perform this task to configure the point code or global title value for the Signaling Connection Control Part (SCCP) calling party address sent in request messages, such as.

About this task

You configure the SCCP calling party address for requests, such as the following, per processing pod:
  • MAP call out requests.
  • USSD notifications.
  • MATRIXX-initiated call requests for USSD call back services.

The values specified for the first processing pod are used as the default values for each processing pod.

If required, you can configure a separate SCCP calling party address per called global title. For example, you can set the calling global title to 4512345678 if the called global title starts with 45.

Perform this task on any processing pod.
Note: The same SCCP calling party address configuration is used for MAP call out messages, USSD notifications service, and MATRIXX initiated calls for the USSD call back service. For more information about the USSD notifications and USSD call back services, see the discussion about support for USSD services in MATRIXX Call Control Framework Integration.
.

Procedure

  1. Go to the ${MTX_CUSTOM_DIR} directory:
    cd_custom_dir
  2. Open the create_config.info file with a text editor and delete the following questions:
    "Engine 1:Cluster 1:LogicalBlade 1:What SCCP address should be used for requests from this blade (pc/gt)?"
    Engine 1:Cluster 1:LogicalBlade 1:How many additional SCCP addresses does this blade require for requests?0
    Note: You must delete these questions for every logical processing pod, and then answer questions to configure the SCCP addresses on each processing pod when you run the configure_engine.py script.
  3. Save and close the file.
  4. Run the configure_engine.py script as user mtx.
  5. Configure the SCCP address type to use for requests by answering the following create_config.info question:
    "Engine 1:Cluster 1:LogicalBlade 1:What SCCP address should be used for requests from this blade (pc/gt)?"

    Answer "pc" to use the point code or "gt" to use the global title.

  6. Configure the global title to use in the SCCP address for requests by providing answers to the following create_config.info questions: 
    Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP global title type for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:What are the SCCP global title digits for requests from this blade?
Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP global title nature of address for requests from this blade?
Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP global title translation type for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP global title numbering plan for requests from this blade?
    Note: For MAP-SRI requests, the global title is a required field and must be configured even when the SCCP address type is set to "pc".
  7. If you specified to use the point code in the SCCP calling party address, configure the point code to use by answering the following create_config.info question:
    Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP point code for requests from this blade?
  8. Configure the SCCP sub-system number (SSN) to use for MAP callouts (and also USSD notifications) by answering the following create_config.info question:
    Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP sub-system number for MAP call outs from this blade?
  9. to configure additional calling party SCCP addresses that are based on the called SCCP global title, specify the number of additional SCCP addresses when you answer the following create_config.info question:
    Engine 1:Cluster 1:LogicalBlade 1:How many additional SCCP addresses does this blade require for requests?
  10. For each SCCP address, answer the following questions: 
    Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What destination SCCP GT prefix is this address for? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What destination SCCP global title type is this address for? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What destination SCCP global title nature of address is this address for? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What SCCP address should be used for requests from this blade (pc/gt)? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What is the SCCP global title type for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What are the SCCP global title digits for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What is the SCCP global title nature of address for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What is the SCCP global title translation type for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What is the SCCP global title numbering plan for requests from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What is the SCCP sub-system number for MAP call outs from this blade? 
Engine 1:Cluster 1:LogicalBlade 1:SccpAddress1:What is the SCCP sub-system number for MATRIXX initiated calls from this blade?
  11. To use the USSD call back service, configure the SCCP sub-system number (SSN) to use for MATRIXX initiated calls by answering the following create_config.info question:
    Engine 1:Cluster 1:LogicalBlade 1:What is the SCCP sub-system number for MATRIXX initiated calls from this blade?
  12. Repeat steps 6 to 12 for each processing pod.
    Note: The SCCP address values for each processing pod default to the values specified for the first processing pod.
  13. Restart the MATRIXX Engine:
    restart_engine.py