This MAP Proxy feature proxies MAP messages between two network elements, typically a Serving MSC (SMSC) and an MSC.


The MAP proxy acts as an intermediary between two network elements, typically an SMSC and MSC. The MAP proxy manages two TCAP legs, one to each network element, and forwards messages received on each leg to the other linked leg.

map proxy
Figure 1. The MAP Proxy Feature

The SCCP address of the destination network element is found by searching the feature configuration using the Sentinel Selection Key and the TCAP Application Context of the initial Dialog Open Request.


The IPSMGW uses the Map Proxy feature in Sending Routing Info For SM call flows.

Feature cheat sheet

Feature Name Network Operator Data Used in PlanId(s) Stateful or Stateless POJO Feature or SBB Feature






Session Input variables

The feature reads the following fields in Session State

Session State variable name Variable type Comments


The MSISDN to use for addressing the HLR by GT


IPSMGWMapProxy statistics can be found under the following parameter set in REM:
SLEE-Usage → sentinel.ipsmgw service → sentinel.ipsmgw SBB → feature → IPSMGWMapProxy
or with rhino-stats:

Name Description

Incremented when a new proxy scenario is started


Incremented when the proxy feature is triggered but there is no leg associated with the triggering ActivityContextInterface. This may happen if the triggering leg is detached by some other feature before the IPSMGWMapProxy feature starts


Incremented when the proxy feature is triggered but there is no associated leg to proxy messages to. This may happen if the proxy leg is detached, or unlinked by some other feature before the IPSMGWMapProxy feature starts


Incremented when there is any error creating a new proxy leg


Incremented when a new proxy leg cannot be created because a leg with the requested name already exists


Incremented when there is an error linking the proxy leg to the triggering leg because the legs are already linked


The IPSMGWMapProxy can proxy to different destinations based on the triggering TCAP Application Context and the value of the Sentinel Selection key.

The first Profile Table used to hold feature configuration is Shared Configuration Profile. The following attributes are used:

Attributes Type Meaning


Address the outbound HLR leg using a GT address formed from the subscriber MSISDN, instead of using the configured DestinationAddress



When accepting an OpenRequest, the SCCP responder address in the OpenAccept will, by default, be set to the value of the SCCP called party in the OpenRequest. If UseGtAsCallingParty is set to true, and if the received sccp-called-party contains a global title, the responder address will be modified in the following way:
The Translation Type is set to 0
The Routing Indicator will be set to gt
The Point Code will be unset
The National indicator will be set to false.

This is useful when the inbound sccp-called-party has been modified by a network element to use PCSSN routing, but GT routing is required for establishing the TCAP dialog.

The second Profile Table used to hold feature configuration is IPSMGWMapProxyConfigProfileTable. Entries in the table are indexed by a Sentinel Selection key that is qualified by a TCAP Application Context. The following attributes are available

Attributes Type Meaning


The SCCP Address of the destination MSC, used when UseMsisdnAsHlrAddress is not configured

In the example below, the IPSMGWMapProxy feature is configured so 'shortMsgGatewayContext' triggers for MAP 1, 2 or 3 are proxied to 'type=C7,ri=pcssn,pc=5,ssn=6'.

Profile Name DestinationAddress







Using MSISDN as Destination Address

The MAP Proxy feature can optionally address the HLR leg using a GT address formed from the inbound subscriber MSISDN, as opposed to using the destination addresses configured in the IPSMGWMapProxyConfigProfileTable profile table described above.

This behaviour can be enabled or disabled by setting the UseMsisdnAsHlrAddress attribute in the Shared Configuration Profile.

Previous page Next page
Sentinel IP-SM-GW Version 4.1