From 2d6ca05225233510fcd6e241629c0953c276251c Mon Sep 17 00:00:00 2001 From: Lukasz Rymanowski Date: Mon, 7 Nov 2011 15:56:55 +0100 Subject: [PATCH] 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. --- sap/server.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/sap/server.c b/sap/server.c index 8bd8fe1b8..06a4361e0 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++; -- 2.47.3