path: root/openbsc/src/libmgcp/mgcp_osmux.c
AgeCommit message (Collapse)AuthorFilesLines
2015-11-02mgcp_osmux: available circuit IDs from 0 to 255, not from 0 to 128Pablo Neira Ayuso1-1/+1
Holger reports that the bitmap that accounts for available Osmux circuit IDs is limited to 128, when the maximum number of circuit IDs are determined by the uint8_t field in the header (ie. 256 circuits). [hfreyther: Update the testcase now that we have more ids to allocate]
2015-10-12osmux: Allow to listen to a specific addressHolger Hans Peter Freyther1-1/+1
For a setup with multiple network interfaces be able to pick the one that osmux should be used/visible.
2015-10-12osmux: Remember the allocated CID and make sure it is releasedHolger Hans Peter Freyther1-0/+13
There appears to be a leak of CIDs: <000b> mgcp_osmux.c:544 All Osmux circuits are in use! There are paths that a CID had been requested and never released of the NAT. Remember the allocated CID inside the endpoint so it can always be released. It is using a new variable as the behavior for the NAT and MGCP MGW is different. The allocated_cid must be signed so that we can assign outside of the 0-255 range of it. Fixes: OW#1493
2015-10-12osmux: Do not divide the number of bytes by eight.Holger Hans Peter Freyther1-2/+2
sizeof(uint8_t) == 1 and there is no need to create an array with 16 bytes and then only use the first two of them. This means the CID range is from 0 to 127 and we should be able to extend this to 256 by changing the array size to 32. Update the testcase now that we can have more than 16 calls with Osmux.
2015-10-12osmux: Test cid allocation and de-allocationHolger Hans Peter Freyther1-0/+14
* Test that one can get an id * That they are assigned predicatble right now * That returning them will make the number of used ones go down * That allocating more will fail
2015-08-19osmux: add option to pad the circuit with dummy messagesPablo Neira Ayuso1-0/+7
Iridium is a satellite network which operates a GPRS-like that allows you to get speeds up to 128kbit/s. However, it takes from 5 to 6 secs to get the bandwidth allocated, so the conversation is garbled during the time. This patch uses the new dummy padding support in libosmo-netif that is controlled through the osmux osmux_xfrm_input_open_circuit(). This includes a new VTY option for osmux.
2015-01-21mgcp: Honor the rtp IP_TOS settings for OsmuxHolger Hans Peter Freyther1-0/+1
Honor the IP_TOS settings for Osmux as well. Re-use the RTP setting as it makes sense to classify the audio packets the same way. Fixes: OW#1369
2014-09-17osmux: send osmux stats in MGCP DLCX responsesPablo Neira Ayuso1-0/+14
This allows us to know what number of messages and bytes has been received per active osmux endpoint. Note that an Osmux message is composed of several chunks. Each chunk contains an osmux header plus several voice data frames. P: PS=385, OS=11188, PR=195, OR=5655, PL=0, JI=49 X-Osmo-CP: EC TIS=0, TOS=0, TIR=0, TOR=0 X-Osmux-ST: CR=51, BR=3129 The new 'X-Osmux-ST:' notifies the received chunks and bytes.
2014-09-16osmux: account extracted traffic from the osmux batchPablo Neira Ayuso1-0/+6
Use struct mgcp_rtp_end statistics to account the RTP messages that has been extracted from the osmux batch and transmitted.
2014-08-29osmux: add 'osmux batch-size NUM' option to mgcp vtyPablo Neira Ayuso1-0/+2
This allows you to specify the osmux batch frame size. If zero, the library uses the default value.
2014-08-29osmux: set default port from mgcp_parse_config()Pablo Neira Ayuso1-5/+0
2014-08-28osmux: fix leak in osmux_deliver()Pablo Neira Ayuso1-0/+1
The callback is responsible for releasing the batch message that libosmo-netif builds.
2014-08-28osmux: fix access to uninitialized memory area in scheduled_tx_*_cbPablo Neira Ayuso1-2/+8
mgcp_send() needs some initialized address when printing a log message. Nothing really serious but let's calm down valgrind.
2014-08-28osmux: rename osmux.c to mgcp_osmux.cPablo Neira Ayuso1-0/+527
So we can easily identify in the log message what refers to libosmo-netif and what to libmgcp.