aboutsummaryrefslogtreecommitdiffstats
path: root/sap
diff options
context:
space:
mode:
authorLukasz Rymanowski <lukasz.rymanowski@tieto.com>2011-11-07 15:56:55 +0100
committerJohan Hedberg <johan.hedberg@intel.com>2011-11-10 10:24:29 +0200
commit2d6ca05225233510fcd6e241629c0953c276251c (patch)
tree014d7d8a1adaee4fe7b0acf835c70e9513b943ad /sap
parenta5c10fdea5a4631ce4d9ac4c213b40dcc2ab01c0 (diff)
downloadbluez-2d6ca05225233510fcd6e241629c0953c276251c.tar.gz
bluez-2d6ca05225233510fcd6e241629c0953c276251c.tar.xz
bluez-2d6ca05225233510fcd6e241629c0953c276251c.zip
SAP: Fix for connect response
Max Message size shall be added to connect response when ConnectionStatus is SAP_STATUS_OK_ONGOING_CALL. Let's always attach maxmsgsize to the connect response if it is provided by the backend.
Diffstat (limited to 'sap')
-rw-r--r--sap/server.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/sap/server.c b/sap/server.c
index 8bd8fe1b..06a4361e 100644
--- a/sap/server.c
+++ b/sap/server.c
@@ -630,8 +630,7 @@ int sap_connect_rsp(void *sap_device, uint8_t status, uint16_t maxmsgsize)
size += PARAMETER_SIZE(SAP_PARAM_ID_CONN_STATUS_LEN);
/* Add MaxMsgSize */
- if (maxmsgsize && (status == SAP_STATUS_MAX_MSG_SIZE_NOT_SUPPORTED ||
- status == SAP_STATUS_MAX_MSG_SIZE_TOO_SMALL)) {
+ if (maxmsgsize) {
uint16_t *len;
msg->nparam++;