Global Title Translation for +1 and 011 in North America
Global Title Translation (GTT) is the SS7 function that turns a signalling address into a routing decision. In North American networks, the digits may begin with +1, 011, or a national-format number, but those prefixes do not automatically mean the same thing to an SCCP translator.
The important distinction is between user dialling habits and signalling data. A subscriber may dial 011 61 from the United States to reach Australia, while an international carrier may present the destination as an E.164 number beginning +61. GTT must recognise the numbering context, apply the correct translation rule, and select the appropriate Global Title or signalling route.
What +1 Represents in SS7 Signalling
+1 is the international country-code form for the North American Numbering Plan (NANP). It covers the United States, Canada, and several Caribbean and Atlantic territories. The following ten digits contain the area code and subscriber number, although network logic may also consider numbering-plan indicators, service codes, and routing restrictions.
When a Global Title begins with 1, a translator often treats it as an NANP destination after normalising the incoming address. The + sign itself is not normally sent as an SS7 digit. Instead, the address is represented as a digit string, commonly with an E.164 numbering plan indicator or a national numbering plan setting.
A robust rule should therefore distinguish +1 212... from a local seven-digit number or a service identifier. It should validate the full structure before sending traffic towards an STP, HLR, SCP, or another signalling endpoint.
Why 011 Is a Dialling Prefix
011 is the international access code used by subscribers in the United States, Canada, and many other NANP locations. It tells a switch that the following digits are an international destination. It is not a country code and should usually be removed during number normalisation before a GTT lookup.
For example, 011 61 2 9374 4000 expresses an Australian destination when dialled from a NANP country. A translation engine may convert it into +61 2 9374 4000, then route it according to the destination country and carrier. If 011 is mistakenly retained as part of the Global Title, the lookup may fail or send the message to an invalid route.
Australian operators face the reverse situation. A caller in Sydney or Melbourne generally uses 0011 for an international call, not 011. Telstra, Optus, and other carriers can still receive traffic that has been normalised by a North American or international gateway, so their signalling platforms must handle the resulting E.164 format rather than assume the subscriber dial string is present.
How a Translation Rule Processes the Digits
The SCCP Called Party Address carries the information used by GTT. Important fields include the Global Title Indicator, translation type, numbering plan, nature of address, and the digit sequence. A translator can match a prefix, examine the address type, and replace or supplement the address with a destination point code and subsystem number.
A typical NANP rule may first strip a leading international access code, then identify country code 1, and finally use the ten-digit NANP number for routing. A separate rule may recognise 011 followed by a foreign country code. The ordering matters: a broad prefix match placed above a specific international rule can capture traffic too early.
Testing should include odd but legitimate cases, such as carrier selection codes, toll-free numbers, mobile ranges, and numbers received with a nature-of-address value that differs from the expected default. Engineers working through SS7 learning resources can use these cases to connect numbering theory with practical signalling design.
| Input received | Likely meaning | Normalisation action | Common risk |
|---|---|---|---|
+1 212 555 0182 |
E.164 NANP number | Keep country code and validate ten digits | Treating + as an SS7 digit |
1 212 555 0182 |
NANP address in national-style form | Interpret according to numbering plan | Confusing trunk prefix with country code |
011 61 2 9374 4000 |
International dial string from NANP | Remove 011, retain 61 |
Routing on the access code |
0011 1 212 555 0182 |
International dial string from Australia | Remove 0011, then process 1 |
Applying North American rules to the full string |
| Seven-digit local number | Local or area-dependent address | Add context only where authorised | Guessing the area code |
Routing Choices Beyond Prefix Matching
GTT rarely works as a simple digit replacement. The translation result may depend on whether the message is for an HLR lookup, SMS routing, number portability query, prepaid platform, or intelligent network service. A rule can send different traffic to separate point codes or subsystem numbers even when the visible prefix is identical.
Number portability makes this especially important. The original area code may no longer identify the serving carrier, so the translation process may need a portability database or an additional lookup. Traffic between North America and Australia can also pass through transit networks that alter point-code formats, screening indicators, or address presentation.
Operational and commercial controls matter as well. If signalling tests involve travel, hospitality, or meetings with external partners, teams should keep approval records aligned with travel and entertainment guidance. That governance sits outside GTT, but it helps protect carrier relationships and auditability.
Practical Checks for Engineers
A translation table should be reviewed with both valid and malformed inputs. Useful checks include:
- Confirm whether the incoming address uses E.164 or a dialled format.
- Verify the numbering plan and nature-of-address fields.
- Test
+1,1,011, and local forms independently. - Record the expected point code and subsystem result.
Packet captures and decoded SCCP fields often reveal problems that are invisible in a switch summary. A protocol analyser guide is useful when checking whether the translator received the expected digits or whether a gateway changed them first.
For production change control, retain evidence for:
- The rule version and effective date.
- Sample messages before and after translation.
- Fallback behaviour when no rule matches.
- Alarm and rollback procedures.
Common Failure Patterns
One frequent error is treating 011 as part of an E.164 address. The resulting Global Title may contain an impossible country-code sequence, causing a translation failure or an incorrect default route. Another is stripping every leading 1, which can damage a valid NANP address when the translator has not first established the numbering context.
A further issue appears when a network assumes all North American traffic is geographically local. NANP numbers span multiple countries and territories, and a destination point code may belong to a transit provider rather than the final operator. Screening, roaming, and portability data should be considered alongside the prefix.
For Australian operations, the practical rule is simple: 0011 is the common international access prefix used by callers, while 011 is primarily a North American dialling convention. Once either has been removed at the appropriate gateway, GTT should work with the normalised country code and a clearly declared numbering plan.
The essential memory is that +1 identifies NANP numbering, while 011 only signals international dialling from a NANP location. Global Title Translation succeeds when those user-facing prefixes are normalised before SCCP routing decisions are made.
