MAP Callout From CAP

Call Control Framework (CCF) can process Mobile Application Part (MAP) callout requests for subscriber data for voice calls that use the Camel Application Part (CAP) protocol.

MAP Call Out From CAP shows the message sequence used when the Charging Server determines that a MAP callout request for more information about a subscriber session is required. The Charging Server forwards the MAP request through CCF to an external database such as the Mobile Number Portability (MNP) database. The Charging Server then uses the results from the MAP request during rating to determine a rate for the call.
Figure 1. MAP Callout From CAP

MAP Callout From CAP Processing Example

The following example process describes a MAP callout for a CAP voice call where the voice charging service has been configured to use the MNP routing number. The routing number retrieved from the MNP database is prefixed to the destination routing address.
  1. When the caller dials a number, the Mobile Switching Center (MSC) sends a TCAP BEGIN(InitialDP) to Network Enabler.
  2. Network Enabler sends the TCAP BEGIN(InitialDP) message to CAMEL Gateway.
  3. CAMEL Gateway sends a MtxTcapMsg(TCAP BEGIN(InitialDP)) to the Charging Server.
  4. Rating determines that number portability information is required. The Charging Server sends a MtxTcapMsg(TCAP BEGIN(MAP-ATI or MAP-SRI)) to CAMEL Gateway in a new TCAP dialog. The MtxTcapMsg request message includes the following information:
    • The callout type to make; either MAP-ATI or MAP-SRI.
    • The MAP protocol version in use.
    • The call party of the query; for example, called party.
    • The MSISDN.
    • An indication to query the MNP database.
  5. CAMEL Gateway sends the TCAP BEGIN(MAP-ATI or MAP-SRI) request to Network Enabler.
  6. Network Enabler forwards the map request to the MNP database and waits for a response.
  7. The MNP sends a TCAP END response message to Network Enabler containing the MAP-ATI or MAP-SRI results.
  8. Network Enabler sends the TCAP END response message with the MAP results to CAMEL Gateway.
  9. CAMEL Gateway sends a MtxTcapMsg(TCAP END(MAP-ATI results or MAP-SRI results)) message to the Charging Server.
  10. The Charging Server stores the MAP results in the session data in the database, applies rating, and reserves funds for the call. The Charging Server sends a MtxTcapMsg(TCAP CONTINUE(ApplyCharging, Connect or Continue)) message to CAMEL Gateway using the original TCAP dialog.
  11. CAMEL Gateway sends the TCAP CONTINUE(ApplyCharging, Connect or Continue) message to Network Enabler.
  12. Network Enabler sends the TCAP CONTINUE message to the MSC and routine call processing continues.
    Note: The destination routing address in Connect operations is set to the called party number prefixed with the MNP routing number. This enables the call to be routed to the appropriate operator's network.

For more information about Network Enabler, see the information about configuring Network Enabler.