[RFC BlueZ v2 16/27] doc: Make telephony docs more generic

["Frédéric Danis" <frederic.danis@collabora.com>]

Remove HFP specific parts or explicitly point it.
---
 doc/org.bluez.Call.rst        | 37 ++++-------------------------------
 doc/org.bluez.TelephonyAg.rst |  3 +--
 2 files changed, 5 insertions(+), 35 deletions(-)

diff --git a/doc/org.bluez.Call.rst b/doc/org.bluez.Call.rst
index 3fcd6f6ea..f4ff37c05 100644
--- a/doc/org.bluez.Call.rst
+++ b/doc/org.bluez.Call.rst
@@ -35,23 +35,9 @@ void Hangup()
 
 Hangs up the call.
 
-For an incoming call, the call is hung up using ATH or equivalent. For a
-waiting call, the remote party is notified by using the User Determined User
-Busy (UDUB) condition. This is generally implemented using CHLD=0.
-
-Please note that the GSM specification does not allow the release of a held
-call when a waiting call exists. This is because 27.007 allows CHLD=1X to
-operate only on active calls. Hence a held call cannot be hung up without
-affecting the state of the incoming call (e.g. using other CHLD alternatives).
-Most manufacturers provide vendor extensions that do allow the state of the
-held call to be modified using CHLD=1X or equivalent. It should be noted that
-Bluetooth HFP specifies the classic 27.007 behavior and does not allow CHLD=1X
-to modify the state of held calls.
-
-Based on the discussion above, it should also be noted that releasing a
-particular party of a held multiparty call might not be possible on some
-implementations. It is recommended for the applications to structure their UI
-accordingly.
+For an incoming call, the call is hung up.
+For a waiting call, the remote party is notified. For HFP by using the User
+Determined User Busy (UDUB) condition.
 
 NOTE: Releasing active calls does not produce side-effects. That is the state
 of held or waiting calls is not affected. As an exception, in the case where a
@@ -69,22 +55,7 @@ string LineIdentification [readonly]
 ````````````````````````````````````
 
 Contains the Line Identification information returned by the network, if
-present. For incoming calls this is effectively the CLIP. For outgoing calls
-this attribute will hold the dialed number, or the COLP if received by the
-audio gateway.
-
-Please note that COLP may be different from the dialed number. A special
-"withheld" value means the remote party refused to provide caller ID and the
-"override category" option was not provisioned for the current subscriber.
-
-string IncomingLine [readonly, optional]
-````````````````````````````````````````
-
-Contains the Called Line Identification information returned by the network.
-This is only available for incoming calls and indicates the local subscriber
-number which was dialed by the remote party. This is useful for subscribers
-which have a multiple line service with their network provider and would like
-to know what line the call is coming in on.
+present.
 
 string Name [readonly]
 ``````````````````````
diff --git a/doc/org.bluez.TelephonyAg.rst b/doc/org.bluez.TelephonyAg.rst
index ddb5eec0f..ad217a6dd 100644
--- a/doc/org.bluez.TelephonyAg.rst
+++ b/doc/org.bluez.TelephonyAg.rst
@@ -24,11 +24,10 @@ Methods
 object Dial(string number)
 ``````````````````````````
 
-Call number, if number is void try to call last dialed number.
 Initiates a new outgoing call. Returns the object path to the newly created
 call.
 
-The number must be a string containing the following characters:
+For HFP, the number must be a string containing the following characters:
 `[0-9+*#,ABCD]{1,80}` The character set can contain numbers, `+`, `*`, `#`,
 `,` and the letters `A` to `D`. Besides this sanity checking no further number
 validation is performed. It is assumed that the gateway and/or the network
-- 
2.43.0