Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify KEY_USE_TEL_URI_FOR_PIDF_XML_BOOL documentation

Browse Source 
Bug: b/229669620
Test: atest ImsCommonTests; manual validation of PUBLISH 200 OK
Change-Id: I18c6c6dc6683c13d354252b6df47f126cea3288c
This commit is contained in:
Brad Ebinger
2022-05-06 11:26:12 -07:00
parent d91518e463
commit 6c48620315
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
telephony/java/android/telephony/CarrierConfigManager.java
View File

@@ -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 =