summaryrefslogtreecommitdiffstats
path: root/src/gsm/libosmogsm.map
Commit message (Collapse)AuthorAgeFilesLines
* Supplementary Services (de)activation, interrogation addedTobias Engel2015-01-011-0/+1
| | | | | | | | | | | | | These patches enhance the Supplementary Service (SS) processing from only being able to handle USSD to other SS, specifically activation, deactivation and interrogation of those SS. Registration is not yet implemented. include/osmocom/gsm/protocol/gsm_09_02.h has been added with needed values for SS. Modified by Harald Welte to keep the old ussd-only functiosn for API/ABI stability.
* add gsm0341_test to generate SMSCB hex stringsHarald Welte2014-12-291-0/+2
| | | | Those hex strings can then be copy+pasted into the OSmoNITB VTY
* ipa: rename functions for consistencyHarald Welte2014-08-201-0/+16
| | | | | | | | As we are breaking builds by moving functions from libosmo-abis to libosmocore anyway, we might as well give functions more appropriate names. ipaccess is a company, while IPA is the multiplex protocol, and CCM is the protocol used for establishing identities on the IPA multiplex.
* abis_nm: add abis_nm_msg_disc_names[] value_stringHarald Welte2014-08-171-0/+1
|
* abis_nm: introduce abis_nm_{osmo,ipa}_magic[]Harald Welte2014-08-171-0/+2
| | | | ... used to be oml_{osmo,ipa}_magic in osmo-bts
* Fix introducing osmocom speficic OML attributesHarald Welte2014-05-191-0/+1
| | | | | | | | | | | | | | | | | | | Rename NM_ATT_O_REDUCEPOWER to NM_ATT_OSMO_REDUCEPOWER, which makes it more clear that this is an osmcoom specific attribute. Also, we cannot simply overload 0x01 as an already defined OML attribute. The problem is quite simple: When we use abis_nm_att_tlvdef during the TLV parse, 0x01 will match to NM_ATT_ABIS_CHANNEL, which is defined as { TLV_TYPE_FIXED, 3 }. So instead, we need to introduce a new abis_nm_osmo_att_tlvdef[], which has to be patched into abis_nm_att_tlvdef[] by the means of tlv_def_patch(), exactly how we do it for bs-11 and nanobts specific attributes. I'm using 0xfe for the attribute, as 0xfe doesn't overlap with the IPA specific attribues (and we might want to combine/merge the 12.21 plus IPA plus osmocom spefici attributes)
* lapdm: Make lapdm_datalink_for_sapi publicDaniel Willmann2014-03-261-0/+1
| | | | | This API allows you to get the lapdm_datalink for a SAPI. It's needed in the lapdm_test, so make it public.
* sms: Added result buffer size parameter to 7bit conv funsJacob Erlbeck2013-08-121-1/+6
| | | | | | | | | | | | | The 7bit<->8bit encoding/decoding functions didn't check whether there is still enough space in the destination buffer. Therefore a buffer size parameter has been added to each of the functions which is used to truncate the output if the buffer is too small. In addition, the return value of the decoding functions has been changed to number of characters written (excluding \0), so this value is always equal to strlen(decoded). The old functions are still available as wrapper functions.
* Add special 7-bit encoding and decoding functions for USSD codingAndreas Eversberg2013-08-081-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Handling 7-bit coding is a little different for USSD, as TS 03.38 states: To avoid the situation where the receiving entity confuses 7 binary zero pad bits as the @ character, the carriage return or <CR> character shall be used for padding in this situation [...]. If <CR> is intended to be the last character and the message (including the wanted <CR>) ends on an octet boundary, then another <CR> must be added together with a padding bit 0. The receiving entity will perform the carriage return function twice, but this will not result in misoperation as the definition of <CR> [...] is identical to the definition of <CR><CR>. The receiving entity shall remove the final <CR> character where the message ends on an octet boundary with <CR> as the last character. Jacob has verified the fix with fakeBTS and the wireshark dissector. Fixes: OW#947 Reviewed-by: Jacob Erlbeck <jerlbeck@sysmocom.de>
* encoding: Provide an overload for the gsm_7bit_encode and a simple testHolger Hans Peter Freyther2013-08-081-0/+1
| | | | | | | This is required for encoding the SMS header using the alpha numeric rules. Reviewed-by: Jacob Erlbeck <jerlbeck@sysmocom.de>
* gsm: Add method to find ARFCN based on frequencySylvain Munaut2012-12-111-0/+1
| | | | Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
* TLV: add new "vTvLV" type for GANHarald Welte2012-07-141-0/+1
| | | | | | | | | | | | | This new TLV type is specific to TS 44.318. Contrary to the TvLV type of TS 08.16/08.18, it has an inverted meaning of the extension (0x80) bit: * if the extension bit is not set, 1-byte length * if the extension bit is set, 2-byte length Futhermore, it has support for variable-length tags, where the tag part can be optionally two bytes in length. As this esoteric option hasn't been seen in the wild yet, we only add encoding support but skip decoding for now.
* add gsm48_decode_lai() to map fileHarald Welte2012-07-131-0/+1
|
* ganc: add value_strings for GAN message type and protocol discriminatorHarald Welte2012-06-241-0/+3
|
* libosmogsm: Add tvlv_att_def to exported symbolsHarald Welte2012-04-051-0/+1
|
* libosmogsm: Introduce explicit list of exported symbolsHarald Welte2012-04-041-0/+230
There is now a "libosmogsm.map" file containing an explicit list of to-be-exported symbols. This should prevent us from leaking non-static symbols into the global namespace. A similar scheme should be adopted by all other osmocom libraries
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-18 19:57:54 +0000