diff options
| -rw-r--r-- | telephony/java/android/telephony/CarrierConfigManager.java | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/telephony/java/android/telephony/CarrierConfigManager.java b/telephony/java/android/telephony/CarrierConfigManager.java index dba18fda31d3..70fe6b10ef20 100644 --- a/telephony/java/android/telephony/CarrierConfigManager.java +++ b/telephony/java/android/telephony/CarrierConfigManager.java @@ -4982,12 +4982,17 @@ public class CarrierConfigManager { /** * Flag indicating whether or not to use TEL URI when setting the entity uri field and * contact element of each tuple. + * * When {@code true}, the device sets the entity uri field and contact element to be + * TEL URI. This is done by first searching for the first TEL URI provided in + * p-associated-uri header. If there are no TEL URIs in the p-associated-uri header, we will + * convert the first SIP URI provided in the header to a TEL URI. If there are no URIs in + * the p-associated-uri header, we will then fall back to using the SIM card to generate the * TEL URI. - * If the TEL URI does not exist, the first URI provided in p-associated-uri header is - * converted into a TEL URI. - * If {@code false}, if false, the first URI provided in the p-associated-uri header - * is used. + * If {@code false}, the first URI provided in the p-associated-uri header is used, + * independent of the URI scheme. If there are no URIs available from p-associated-uri + * header, we will try to generate a SIP URI or TEL URI from the information provided by the + * SIM card, depending on the information available. * @hide */ public static final String KEY_USE_TEL_URI_FOR_PIDF_XML_BOOL = |