aboutsummaryrefslogtreecommitdiffstats
path: root/sap
diff options
context:
space:
mode:
authorLukasz Rymanowski <lukasz.rymanowski@tieto.com>2011-11-07 15:57:20 +0100
committerJohan Hedberg <johan.hedberg@intel.com>2011-11-10 10:27:18 +0200
commitcaf327643733bada77fab63181ab2fdbfef73748 (patch)
treef536fd77896329298669224b0608c920bf17c104 /sap
parent519ff20d9e0c5c9ba9305e33f77fd5db64c78dc4 (diff)
downloadbluez-caf327643733bada77fab63181ab2fdbfef73748.tar.gz
bluez-caf327643733bada77fab63181ab2fdbfef73748.tar.xz
bluez-caf327643733bada77fab63181ab2fdbfef73748.zip
SAP: Fix handling ongoing call in sap-dummy
There is no need to send sap_connect_rsp when "call" is ended. Status Indication is enough. Also we should provide max supported msg size in the connect response having status: OK_ONGOING_CALL.
Diffstat (limited to 'sap')
-rw-r--r--sap/sap-dummy.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/sap/sap-dummy.c b/sap/sap-dummy.c
index 37982bed..acdec777 100644
--- a/sap/sap-dummy.c
+++ b/sap/sap-dummy.c
@@ -71,7 +71,7 @@ void sap_connect_req(void *sap_device, uint16_t maxmsgsize)
return;
} else if (ongoing_call_status) {
sap_connect_rsp(sap_device, SAP_STATUS_OK_ONGOING_CALL,
- maxmsgsize);
+ max_msg_size_supported);
return;
} else {
sim_card_conn_status = SIM_CONNECTED;
@@ -226,8 +226,6 @@ static DBusMessage *ongoing_call(DBusConnection *conn, DBusMessage *msg,
if (ongoing_call_status && !ongoing) {
/* An ongoing call has finished. Continue connection.*/
- sap_connect_rsp(sap_data, SAP_STATUS_OK,
- max_msg_size_supported);
sap_status_ind(sap_data, SAP_STATUS_CHANGE_CARD_RESET);
ongoing_call_status = ongoing;
} else if (!ongoing_call_status && ongoing) {