Age | Commit message (Collapse) | Author | Files | Lines |
|
It needs to be configured correctly on the NAT.
|
|
|
|
Encode a list of packets differently when we are dealing with a
marker bit. We now have 7 more bits to store information, we might
also want to add a mark to stop using marks.
|
|
|
|
No way to undo the compression yet, no integration with the
MGCP network code.
|
|
Summary of changes:
s/struct bsc_fd/struct osmo_fd/g
s/bsc_register_fd/osmo_fd_register/g
s/bsc_unregister_fd/osmo_fd_unregister/g
s/bsc_select_main/osmo_select_main/g
|
|
libosmogsm is a new library that is distributed in the libosmocore.
Now, openbsc depends on it. This patch gets openbsc with this
change.
This patch also rewrites all include path to the new
osmocom/[gsm|core]
Signed-off-by: Pablo Neira Ayuso <pablo@gnumonks.org>
|
|
A trunk will always have 32 endpoints to be used and we allow
a sparse allocation of endpoints.
|
|
We want to support real trunks in the MGCP code and we need to
have some better book keeping for those. Move the code around.
|
|
The reason for this is quite simple: We want to make sure anyone
running a customized version of OpenBSC to operate a network will
have to release all custom modifiations to the source code.
|
|
Introduce the trans_bts. Right now only a port is allocated
and the packets from the BTS are sent from this socket.
|
|
Packets arriving for trans_net will be send out to the
networking. We will introduce a trans_bts in a second.
|
|
This allows to switch off transcoding on the fly, or only enable
it for certain vessels with known problems.
|
|
Bind a new port for the transcoder, forward data from the BTS
to the transcoder, and from the transcoder to the network. Leave
BTS-IN where it is, BTS-OUT can now be after the transcoding took
place. We send the data from the BTS RTP port.
This whole route will be guarded by the transcoder_ip and if it is
NULL (current default) it will not go through the transcoder.
|
|
Do not use the CI_UNUSED to decide if an endpoint is allocated
but introduce a new flag. This way only the CRCX and free_endp
play with the allocated field.
|
|
|
|
For debugging it is useful to forward (tee) UDP packets to another
system and use gstreamer to inspect the rtp stream. This is untested
code and might contain bugs.... and of course only tap your own calls.
|
|
|
|
Allow to switch to a dynamic port allocator and not reuse
the ports for a long time... This should help with a crazy
network sending two streams at the same time.
|
|
Use the right source port when sending the message.
|
|
Stop using the memset in the mgcp_rtp_end_reset as we
will reset the list pointers and then have a mess..
|
|
|
|
We plan to have two different ports for the network and for the
BTS to avoid detecting the BTS and to dynamically allocate the
port to have old data not go to a new socket.
|
|
Group the data that each end (network/bts) have into a struct and use
this struct throughout the sourcecode.
|
|
|
|
Patch the sequence number, the SSRC and the timestamp to
allow to mix various voice streams, e.g. toggling the loop
during the call.
|
|
Use a struct to group the rtp state for the up and the down
link of the bts.
|
|
|
|
|
|
This code compares the UDP sequence numbers of two RTP messages
and guesses if packets are missing. It is guessing in two ways:
1.) by default the sequence number is 0, so on the first
value we ignore the jump... we might ignore a real issue
in case of a wrap around which is easily possible as the
sequence should be a random number.
2.) the UDP stream might have been reordered on the network
and we would see the jump...
In any case these two shortcomings are acceptable for the feature
that is meant to provide some basic analysis..
|
|
This can be used by higher level code to send one dummy
message from the audio port to the network. This can be
used to make the remote discover the nated port of this
endpoint.
|
|
|
|
This will be used by the NAT code to implement custom protocol
handling on top of that.
|
|
Conflicts:
openbsc/include/openbsc/Makefile.am
openbsc/src/Makefile.am
|
|
Keep track of which RTP payload type to use for which direction.
|
|
In separation of using the MGCP parsing in another context, refactor
the code to operate on a struct mgcp_config, split out the vty code
from the mgcp_protocol.c, and move the callbacks into the mgcp code.
There should be no functional changes.
|