summaryrefslogtreecommitdiffstats
path: root/doc/voicecall-api.txt
diff options
context:
space:
mode:
authorDenis Kenzior <denkenz@gmail.com>2009-11-12 17:54:26 -0600
committerDenis Kenzior <denkenz@gmail.com>2009-11-12 19:16:31 -0600
commite9341c520354375a3647ad4e0a7db114929cb1b9 (patch)
tree31402a8d1250e3ea76d4335b01b85322b187a3cb /doc/voicecall-api.txt
parent9b084e965662d82c14661ab721e270039217d8e5 (diff)
downloadofono-e9341c520354375a3647ad4e0a7db114929cb1b9.tar.bz2
Remove Voicecall.Busy method
According to 22.030, UDUB or CHLD=0 can only be invoked on waiting calls. Most AT command based modems do not support using CHLD=0 on an incoming call. So we remove the Busy method and invoke set_udub on a call that is in the waiting state.
Diffstat (limited to 'doc/voicecall-api.txt')
-rw-r--r--doc/voicecall-api.txt27
1 files changed, 14 insertions, 13 deletions
diff --git a/doc/voicecall-api.txt b/doc/voicecall-api.txt
index b360cca3..c8e34a47 100644
--- a/doc/voicecall-api.txt
+++ b/doc/voicecall-api.txt
@@ -7,21 +7,11 @@ Object path [variable prefix]/{modem0,modem1,...}/{voicecall01,voicecall02,...}
Methods dict GetProperties()
- Returns all global system properties. See the
+ Returns all properties for this object. See the
properties section for available properties.
Possible Errors: [service].Error.InvalidArguments
- void Busy()
-
- Notifies the incoming or waiting call that the user
- is busy. This is done by setting the User Determined
- User Busy (UDUB) condition. This method is only valid
- if there is an incoming or waiting call.
-
- This functionality is generally implemented by using
- the +CHLD=0 AT command.
-
void Deflect(string number)
Deflects the incoming or waiting call to number given
@@ -39,8 +29,19 @@ Methods dict GetProperties()
Hangs up the voice call.
- This functionality is generally implemented by
- +CHLD=1X, +CHUP or ATH AT commands.
+ 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,
+ or the release of a particular party in a held
+ multiparty call.
+
+ Note that releasing a held call or a particular party
+ of a held multiparty call might not be possible on some
+ implementations.
void Answer()