| 4611e65ec532915b3a6968459d68e5a2dc3a08c8 |
|
28-Dec-2017 |
Pooja Jain <poojain@codeaurora.org> |
IMS: Add support for call deflection feature
Call deflection feature is useful to deflect MT call to another
number.
Test: Manual
Bug: 62170348
Change-Id: Ie31421b21dea6bf5514f1f137cf5a6c315fc1149
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsExternalConnection.java
|
| 1846615c7cb3d995efc8788b60aa1f5240de8b8f |
|
23-Jan-2018 |
Brad Ebinger <breadley@google.com> |
Change ImsService API namespaces
Changes the ImsService API namespaces
to allow them to be @SystemApi.
Bug: 63987074
Merged-In: I66b564e27d5e0995c4819bd2c6df304e7e04a7eb
Change-Id: I66b564e27d5e0995c4819bd2c6df304e7e04a7eb
Test: Telephony Unit Tests
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsExternalConnection.java
|
| f41783220aa8cc2e0e62c2ae2c3300b779c96101 |
|
29-Jun-2016 |
Tyler Gunn <tgunn@google.com> |
Label dialog event package entries for conferences.
Dialog event package entries (multiendpoint) for a conference call on
another device will have a uri something like this:
sip:conf=2001-4888-205-710f-e0-113-0-120-1466524732857069@[2001
This ends up looking nasty in the UI. To prevent this, adding code to
detect this type of URI and set the caller name to "Conference Call",
and blank out the caller number.
See bug for screenshot.
Bug: 29534470
Change-Id: I892897ca80347f57497928cb1b02fba83c3c664a
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsExternalConnection.java
|
| 1c23d391a314ffdb71874b06e9a0e54607208832 |
|
12-May-2016 |
Tyler Gunn <tgunn@google.com> |
Better handling of dialog event package numbers, and call pulling.
1. Remapping the ImsReasonInfo codes associated with pulling a call to
the DisconnectCause.CALL_PULLED cause. Note: This will need to be updated
in the future as there is a bug in the modem which remaps calls pulled to
the "answered elsewhere code".
2. Convert the dialog event package SIP URI to a tel URI and use that to
set the address on the connection.
Bug: 27458894
Change-Id: I197ce52f6a15df74dcc0c8609f74242b1af910bc
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsExternalConnection.java
|
| 93da8529345711fd1a5617f3c8b15c0921eececb |
|
15-Apr-2016 |
Tyler Gunn <tgunn@google.com> |
Wire up IMS framework APIs and call pull.
1. Wired up the IMS framework APIs so that the modem can inform us of new
dialog event package changes.
2. Wired up the call pull API so that calls to it make it down to an
ImsExternalConnection.
3. In ImsExternalCallTracker, listen to the call pull requests on the
external connections, and use this to trigger the actual pull of the call,
which is essentially a dial with an extra specified (per QCOM).
I abstracted away the idea of pulling the call using the ImsPullCall
interface, which ImsPhoneCallTracker implements.
Bug: 27458894
Change-Id: Idd20a95c2993b29dcd0a7e6c71fb6232cff88736
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsExternalConnection.java
|
| fec523bdc5d2b6dd90212c8076bf34bcc2ab08b2 |
|
01-Apr-2016 |
Tyler Gunn <tgunn@google.com> |
Add ImsExternalCallTracker and support for multiendpoint.
- Adding new ImsExternalCallTracker which is responsible for responding to
dialog event package information received via IMS framework.
- Added TelephonyTester intents so that I can inject fake dialog event
package data into the ImsExternalCallTracker.
Bug: 27458894
Change-Id: Icc7c4f9e25ad553107fc1cb9d5501ba45c5a1e45
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsExternalConnection.java
|