Customizations for phone calls
Provides information about customizations you can configure for the phone or dialer app including branding, visual voicemail, caller ID matching, dialer codes, and more.
In this section
On CDMA devices, call durations in the call history may include the time spent before the call was connected. This behavior results in an incorrect calculation of the call duration. OEMs can address this potential issue by enabling this customization, which excludes the time spent before the call was connected. When enabled, the customization will also adjust the call duration to indicate that zero time was spent if the call ends before the connection was made.
OEMs can change the default behavior so that the number that's displayed in the call screen always matches the dialed phone number even if the number that the call connected to may be different.
Partners can add a custom image that displays the mobile operator name or logo on the Incoming Call screen.
Each country/region has a varying phone number length and style so with Windows 10 Mobile the OS maps a different minimum number of digits for matching caller ID that defaults to each country/region setting on the mobile device. This enables mobile users to get the proper settings for their preferred country/region.
In Windows 10 Mobile:
If OEMs do not customize this setting based on mobile operator requirements, the OS uses the current default of 6, which is the last 6 digits of the phone number.
On GSM networks, OEMs can enable mobile operator-defined codes, or cause codes, to show in the UI whenever a phone call is terminated unexpectedly.
Depending on the scenario that partners want to support, partners can configure the voicemail system so the device either ignores or responds to message waiting indicator (MWI) notifications.
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.
Partners can define a dialer code to use for services like changing the pin, changing the password, caller ID, call forwarding, call waiting, call blocking, and so on.
To use an OEM diagnostic app in environments such as a service center, OEMs can configure special dialer codes to start the application. OEMs can also configure dialer codes to start apps to interact with mobile operator networks or to diagnose phone malfunctions.
Disable the ability to access a contact's information while in the active call screen.
Disable automatic navigation to the Windows Store when the user attempts a video upgrade for which there is no installed app.
Disable voicemail phone number display on the call progress screen.
Dismiss the last USSD waiting dialog in the case where there is a sequence of USSD or SIM app dialogs.
Partners can configure the following DTMF tone settings when VoLTE calls are supported:
Partners can edit the list of valid emergency phone numbers for the market in which the phone will be sold.
Partners can configure devices to have the call recording feature enabled by default.
Partners can identify which IP Multimedia Subsystem (IMS) services, if any, are enabled on the device by default. The IMS services that can be identified are: IMS, SMs over IMS, Voice over IMS, and Video over IMS.
OEMs can enable long DTMF tones if the user presses a dialpad key for an extended period.
OEMs can configure the RCS settings using the multivariant support in the OS. Using these settings, you can:
OEMs can specify the maximum number of participants or callers that can be added to a voice over LTE (VoLTE) conference call based on the mobile operator's network requirements.
For markets or mobile operators that require support for network-controlled settings for outgoing caller ID, OEMs can configure the setting to indicate whether the network default setting is allowed and specify the default initial value for the caller ID setting.
Partners can define a dialer code to use for 3GP USSD services like changing the pin, changing the password, caller ID, call forwarding, call waiting, call barring, and so on. Partners can define new mappings or disable the default mappings. To define a new mapping or change the behavior of a provided supplementary service mappings, see Dialer codes for supplementary services
To meet certain market requirements or user expectations, OEMs can change the button label in USSD dialogs from Close (the default) to OK.
OEMs can customize call progress branding when a call is made using a specific audio codec.
To meet mobile operator requirements, OEMs can enable the voice domain to decide whether to use Emergency calls only or No service in the phone UI branding.
Visual voicemail supports both traditional voicemail (retrieved through a phone call) and visual voicemail. Users can select between traditional voicemail and visual voicemail when they first attempt to access voicemail. If the mobile operator does not support this visual voicemail implementation, the user will only see the traditional voicemail option. For mobile operators that have their own particular brand that they want to use instead of visual voicemail, partners can rebrand all instances of visual voicemail in the Windows 10 Mobile UI to use the operator's brand.
Partners can add a string to the phone's call progress screen to indicate if the active call is a voice over LTE (VoLTE) call depending on whether the phone call is in high quality voice status such as when using AMR-WB codec. The high quality voice status is determined by the modem and RIL implementation. This string is combined with the PLMN for the mobile operator and is only shown if the combination of the PLMN and the custom string is less than the maximum width available. For example, "Litware VoLTE" will be shown but "Litware Wireless VoLTE" may be too long and may be truncated.
Partners can define a filter that intercepts an incoming SMS message and triggers visual voicemail synchronization. The filtered message does not appear in the user’s conversation list.