Table of contents
TOC
Collapse the table of content
Expand the table of content

Dial string overrides when roaming

Last Updated: 12/12/2016

Partners can map certain dial strings to corresponding override numbers that are dialed when the user is roaming. To the user, it will appear as if the original number was dialed.

The mappings are customizable and stored in the registry. All roaming override dial strings are organized under a single registry key as name-data pairs. The OS uses the dialed string as the registry name to query and the associated data as the override number to be dialed.

Design requirements and considerations:

  • Partners must specify override numbers in full international format, including a leading +. The numbers are dialed as-is on 3GPP and the + is converted to the appropriate prefix on 3GPP2.

  • Dial string translation is only performed when the phone is roaming.

  • Partners may specify override numbers with <SUB> to represent the subscriber number. The first instance of <SUB> in an override number is replaced with the subscriber number. Partners cannot specify <SUB> as part of a dial string to search for.

Constraints: None
This customization supports: per-IMSI value

Instructions:

  1. Create a customization answer file using the contents shown in the following code sample.

    ``` syntax <?xml version="1.0" encoding="utf-8" ?>

  <!-- Define the Targets --> 
  <Targets>
     <Target Id="">
        <TargetState>
           <Condition Name="" Value="" />
           <Condition Name="" Value="" />
        </TargetState>
     </Target>
  </Targets>

  <Static>
    <Settings Path="Multivariant">
      <Setting Name="Enable" Value="1" />
    </Settings>
    <Settings Path="AutoDataConfig">
      <Setting Name="Enable" Value="0" />
    </Settings>
  </Static>

  <!-- Specify the Variant -->
  <Variant Name=""> 
    <TargetRefs>
      <TargetRef Id="" /> 
    </TargetRefs>

    <Settings Path="Phone/PerSimSettings/$(__IMSI)/RoamingNumberOverrides">  
      <Setting Name="DialString/$(DialString)" Value="" />      
      <Setting Name="DialString/$(DialString)" Value="" />      
      <Setting Name="DialString/$(DialString)" Value="" />      
      <Setting Name="DialString/$(DialString)" Value="" />      
    </Settings>  

  </Variant>

</ImageCustomizations>
```
  1. Specify an Owner.

  2. For the per-IMSI case:

    1. Define Targets or conditions for when a variant can be applied, such as keying off a SIM's MCC, MNC, and SPN.

    2. Define settings for a Variant, which are applied if the associated target's conditions are met.

  3. Determine the number of dial string overrides you need to configure. For each dial string:

    1. Replace $(DialString) in the settings name with the name of the dial string or number that the user will dial when roaming. For example, if the user will dial *611, set the setting name to:

            <Setting Name="DialString/*611" Value="" />
      
    2. Set the setting value to the override number or number that the dial string is translated into. This corresponds to the number that is actually called. For example, if the user dials *611 and the number that must be called whenever the user dials *611 is +18001234567, set the value as shown in the following example:

            <Setting Name="DialString/*611" Value="+18001234567" />
      

    The following example shows how to create a mapping for two dial strings, *611 and *86:

        <Settings Path="Phone/PerSimSettings/$(__IMSI)/RoamingNumberOverrides">  
          <Setting Name="DialString/*611" Value="+18001234567" />      
          <Setting Name="DialString/*86" Value="+1&lt;SUB&gt;" />      
        </Settings>
    

    In the preceding example:

    • *611 is the dial string and +18001234567 is the override number. The user dials *611 and the number that is actually called is +18001234567.

    • *86 is the dial string and +1<SUB> is the override number. The user dials *86 and the number that is actually called is +1 and the subscriber’s number.

Testing:
To verify this customization, the phone must be roaming internationally. Work with your mobile operator partner to test this customization on their network.

  1. Flash the build containing this customization to a phone.

  2. Dial the numbers that you specified and verify that numbers that are actually called are the override numbers that you specified for each dial string.

    Verify that the override numbers are not shown on the phone when the dial strings are called.

Send comments about this topic to Microsoft

© 2017 Microsoft