gsm_04_11: Remove direct RSL calls from the SMS code...
Do not use RSL to release the SAPI/Channel from within the code,
the normal channel release procedure will take care of releasing
the SAPIs and there should be no issue in keeping the SAPI=3
established until the end of the session.
diff --git a/openbsc/src/gsm_04_11.c b/openbsc/src/gsm_04_11.c
index 57d8089..f84463c 100644
--- a/openbsc/src/gsm_04_11.c
+++ b/openbsc/src/gsm_04_11.c
@@ -754,12 +754,6 @@
/* free the transaction here */
trans_free(trans);
-
- /* release channel if done */
-#warning "BROKEN. The SAPI will be released automatically by the BSC"
- if (!sms)
- rsl_release_request(msg->lchan, trans->sms.link_id);
-
return 0;
}
@@ -833,9 +827,6 @@
sms = db_sms_get_unsent_for_subscr(trans->subscr);
if (sms)
gsm411_send_sms_lchan(trans->conn, sms);
- else
- rsl_release_request(msg->lchan, trans->sms.link_id);
-#warning "BROKEN: The SAPI=3 will be released automatically by the BSC"
return rc;
}