openbsc - Legacy: OpenBSC, OsmoSGSN, OsmoBSC and other programs

Age	Commit message (Collapse)	Author	Files	Lines
2017-02-07	set transaction_id from transaction data	Sergey.Kostanbaev	1	-1/+3

2017-02-07	manual merge SS from sup-ussd-on-master-ss-wip	Sergey.Kostanbaev	1	-277/+240

2017-02-07	ussd: handle UCS-2 coding	Sergey Kostanbaev	1	-0/+2

2017-02-07	libmsc: fix no return and use after free	Sergey Kostanbaev	1	-2/+4

2017-02-07	ussd: send reject to sup	Sergey Kostanbaev	1	-59/+14

2017-02-07	libmsc: use message type as an entry point and handle release complete message	Sergey Kostanbaev	1	-22/+149

2017-02-07	USSD MAP external interface over SUP	Sergey Kostanbaev	1	-6/+243

2017-02-07	Revert "ussd: Add band-aid for interrogationSS"	Ivan Klyuchnikov	1	-16/+8
	This reverts commit 5085e0bf4c9674fb26754fd16b8e0c58113e1638.
2016-11-18	ussd: Add band-aid for interrogationSS	Holger Hans Peter Freyther	1	-8/+16
	This is a speculative change for interrogateSS and by not answering the request the radio connection would remain open long. The SS/USSD code is from a time where none of knew much about GSM. We do not support SS but should reject it. We have checked for an empty string in the text field to guess if it is a result/release to not send more information. The right way forward is to decode the ASN1 into the fields REQUEST/RESULT(last). Fix an issue and make the code worse. Assume ss_code > 0 to see if this is a interrogate invoke. The issue is that code 0 is a well defined value but unlikely to be used. MAP ASN1 definition: SS-Code ::= OCTET STRING (SIZE (1)) -- This type is used to represent the code identifying a single -- supplementary service, a group of supplementary services, or -- all supplementary services. The services and abbreviations -- used are defined in TS 3GPP TS 22.004 [5]. The internal structure is -- defined as follows: -- -- bits 87654321: group (bits 8765), and specific service -- (bits 4321) allSS SS-Code ::= '00000000'B Change-Id: Ib0dc4485388f030eb172fe21f5327b7ab94751f5
2013-12-28	ussd: Reject and release unhandled SS requests/interrogation	Tobias Engel	1	-1/+9
	In case the unpack of a USSD request is failing the channel would remain open and the phone would not receive a response. Simply reject the interrogation. Example interrogation: 0000 1b 7b 1c 0d a1 0b 02 01 01 02 01 0e 30 03 04 01 0010 11 7f 01 00
2013-10-15	ussd: Fix test for RELEASE COMPLETE	Alexander Huemer	1	-1/+1
	A correcsponding change in libosmocore sets text[0] to '\0'. The test for 0xFF could never have been true.
2012-02-24	Make sure USSD code only responds *#100# for retrieving own number	Tobias Engel	1	-1/+1
	strstr() was used with wrong argument order, causing it to always match, and causing an invalid response to a variety of different SS and USSD requests. This has apparently caused havoc among a number of HTC phones which issue SS requests without user interaction upon boot, and then trip over our inappropriate response.
2011-03-04	prefix sub-directories containing libraries with 'lib'	Harald Welte	1	-0/+79
	... and make sure tests work again after restructuring