MAP Roaming Number Request for Mobile-Terminating SS7 Calls
When a mobile-terminating call reaches a subscriber registered on a visited network, the gateway needs a temporary number that the visited network can route. For an Australian subscriber travelling overseas, a foreign gateway queries the Australian HLR. For a visitor to Australia, the Australian gateway performs the lookup against the subscriber’s home HLR.
The central mechanism is the MAP roaming number request. In common SS7 documentation, it appears as Provide Roaming Number, although Send Routing Information or operator-specific equivalents may also be used. Each variant helps obtain the Mobile Station Roaming Number, a temporary number used for routing rather than the subscriber’s permanent mobile number.
Once the MSRN is returned, ISUP carries the call toward the serving MSC, while MAP assists with subscriber location and paging decisions. MTP3 and SCCP carry the underlying SS7 messages. The voice bearer remains separate, so a failed number lookup can prevent call setup even when the handset has strong mobile coverage.
| Component | Main responsibility | Typical handoff |
|---|---|---|
| Gateway MSC | Receives the incoming call | Sends a MAP lookup toward the HLR |
| Home HLR | Holds the subscriber profile and location | Confirms the serving VLR and obtains an MSRN |
| Visited VLR | Tracks the subscriber’s current location | Supports MSRN allocation and paging |
| Serving MSC and VLR | Reach the registered handset | Passes paging requests to the radio network |
| Base station | Delivers the page and access signalling | Establishes the radio and bearer resources |
Where the call enters the network
An incoming Initial Address Message from ISUP identifies the called party and the gateway that must route the call. The GMSC parses the destination number, determines that it belongs to a mobile subscriber and starts a TCAP transaction over SCCP and MTP3. Diameter or SIP-based interworking may sit beside this legacy signaling path.
Protocol primers covering MAP, MTP3 and TCAP are available through the SS7 training library. That background is valuable when distinguishing a failed lookup from a later failure to page the handset or negotiate speech and bearer resources.
Resolving the subscriber and visited network
The GMSC sends the roaming-number request to the subscriber’s home HLR using the international SS7 network. The HLR checks its profile, service restrictions and stored VLR location. If the subscriber is barred, unknown or not permitted to roam, the response carries the relevant rejection instead of an MSRN.
For an active roaming subscription, the HLR coordinates with the visited VLR, which owns the temporary-number resources needed for local routing. The returned MSRN is mapped to the subscriber’s IMSI and current serving network. Operator numbering plans determine its format, and its lifetime may be limited to the call or allocated from a short-lived pool. This temporary identity is what allows the call to continue without exposing the subscriber’s permanent MSISDN as the next routing address.
Delivering the call to the handset
After receiving the MSRN, the GMSC uses it in the next ISUP address message to direct the call toward the visited MSC. The associated VLR then initiates BSSAP paging through the serving base station. Once the handset responds, the network assigns the bearer, applies the agreed codec and exchanges answer supervision with the originating network.
A successful MSRN response does not prove that the handset is reachable. The VLR location may be stale, the handset may be outside coverage, or the paging transaction may time out. Operators in Australia often describe the last case as a “dropped call,” even when the signaling trace clearly shows that the number lookup succeeded.
Australian numbering and operating realities
Australian mobiles normally use 04xx numbers. International callers use the +61 4xx form and omit the domestic leading zero. Number conversion must therefore be checked carefully at the GMSC and HLR, because an incorrect prefix can cause a valid subscriber lookup to become an unknown-number rejection.
The market includes network operators such as Telstra, Optus and Vodafone, alongside mobile virtual network operators that use their own brands while relying on host infrastructure. A subscriber’s home HLR and serving VLR may consequently sit under different commercial arrangements. Emergency calls to 000, also reachable through 112, receive special handling and should not be judged against the ordinary MSRN-return path.
Coverage can differ sharply between Sydney, Perth, Cairns and regional routes, making location freshness and radio reach important operational details. SS7 expertise also transfers to adjacent connected systems. An intelligent parking guide illustrates how identifiers, location data and backhaul support a different service, revealing parallels in telemetry and service assurance.
Checks that isolate the failed stage
A structured trace separates subscriber resolution from call delivery:
- Normalize the called number into international format and confirm that the MSISDN belongs to the intended HLR.
- Compare the HLR’s stored VLR location with recent registration activity and check whether the MSRN allocation succeeded.
- Correlate the TCAP dialogue, SCCP routing and MTP3 indications, including returned errors and transaction timer expiry.
- Verify that the MSRN reached the GMSC and that BSSAP paging subsequently reached the serving base station.
These checks reveal whether the defect lies in number conversion, subscriber data, inter-network signaling or radio access. They also prevent engineers from attributing every unanswered call to the same cause when the failed stages require different remedies.
The end-to-end flow to remember
The sequence is a chain of responsibility: the GMSC asks for a roaming number, the home HLR identifies the subscriber, the visited network supplies the MSRN, and the serving infrastructure pages the handset. ISUP controls the call legs, MAP supports subscriber procedures, and MTP3 with SCCP provides their signaling foundation.
The essential point to remember is that mobile-terminating roaming succeeds only when number resolution, location data, routing and radio delivery all agree.