Configuring CCF to use TSANs for Reoriginating Calls

You can configure Call Control Framework (CCF) to use the TSAN reorigination service when processing mobile originating (MO) calls using the CAP1 protocol or CS1 INAP protocol.

When a roaming subscriber makes an MO call through a Visitor Mobile Switch Center (VMSC) that can process calls using only CAP1 or only CS1, the TSAN reorigination service returns a Temporary Service Access Number ( TSAN) to the VMSC. A TSAN is an operator-defined telephony number. Because the TSAN is a routable number, the VMSC can pass the TSAN to a GMSC that can handle calls using CAP2, CAP3, or CAP4. The GMSC then sends a new, reoriginated InitialDP for the call to CCF for processing using the TSAN reorigination service.

Note: The process for reoriginating CAP1 and CS1 calls using TSANs is the same. For information about the reorigination process, see the discussion about the CAP1 reorigination process.

Engine Configuration

During engine configuration, set CCF to use the TSAN reorigination service by defining:
  • The expected maximum rate of reoriginated calls for the TSAN reorigination service.
  • The expected average reorigination time in milliseconds.
  • The maximum time that the TSAN reorigination service waits for the reoriginated InitialDP before timing out.
  • MO voice services to search for TSANs in InitialDPs in TCAP messages.
  • For CAP1 calls only, whether the TSAN gateway is the default service. This option is not applicable to CS1 calls.
  • The TSAN reorigination service selectors that define criteria for selecting a service. You can configure up to a maximum of 20 selectors for the TSAN reorigination service.

For more information about configuring the TSAN reorigination service, see the discussion about how to configure the TSAN reorigination service.

TSAN Configuration

After configuring the TSAN reorigination service, you must add ranges of TSANs to the MATRIXX database. Each TSAN range consists of a list of operator-defined telephony numbers. The TSAN reorigination service uses the TSANs for reoriginating CAP1 or CS1 calls using CAP2, CAP3, or CAP4.
Note: If you are using sub-domains in your MATRIXX environment, you must populate unique TSAN ranges on the processing pods in each sub-domain.
You configure TSAN ranges by running the configure_tsan.py script. Use the configure_tsan.py script to:
  • Add or remove a range of TSANs from the MATRIXX database. In addition to populating TSANs in the database, the script updates the Route Cache with matching TSAN entries.
  • Generate a list of all the TSANs held in the database.

For more information about the configure_tsan.py script, see the discussion about configure_tsan.py in MATRIXX Administration. For information about configuring TSANs, see configure TSANs.