[PATCH] Fix: Use gsm_7bit_encode_ussd function to encode USSD response

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Andreas Eversberg jolly at eversberg.eu
Fri Aug 9 11:33:13 UTC 2013


The New function offers the actual octet that is needed to correctly
compose USSD response.
---
 openbsc/src/libmsc/gsm_04_80.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/openbsc/src/libmsc/gsm_04_80.c b/openbsc/src/libmsc/gsm_04_80.c
index 39738a5..1b1c449 100644
--- a/openbsc/src/libmsc/gsm_04_80.c
+++ b/openbsc/src/libmsc/gsm_04_80.c
@@ -72,7 +72,7 @@ int gsm0480_send_ussd_response(struct gsm_subscriber_connection *conn,
 
 	/* First put the payload text into the message */
 	ptr8 = msgb_put(msg, 0);
-	response_len = gsm_7bit_encode(ptr8, response_text);
+	gsm_7bit_encode_ussd(ptr8, response_text, &response_len);
 	msgb_put(msg, response_len);
 
 	/* Then wrap it as an Octet String */
-- 
1.7.3.4





More information about the OpenBSC mailing list