This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".
The branch, master has been updated
via 3ffce19cb4929c907460753d302e4720558cc6d2 (commit)
from 35697b9a109f08791c00dbb1a8dfaaaff29a8a80 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=3ffce19cb4929c907460753d302e4720…
commit 3ffce19cb4929c907460753d302e4720558cc6d2
Author: Max <msuraev(a)sysmocom.de>
Date: Mon Apr 25 15:22:00 2016 +0200
Disconnect calls with incompatible channel types / modes
In case both TCH/H and TCH/F or different codecs are configured and
internal MNCC handler is used we might end up in a situation where call
legs with incompatible channel types or codecs would be connected
resulting in a broken audio. Disconnect such calls with appropriate
error message.
Fixes: OS#1663
-----------------------------------------------------------------------
Summary of changes:
openbsc/src/libmsc/gsm_04_08.c | 46 +++++++++++++++++++++++++++++++++++++++++-
1 file changed, 45 insertions(+), 1 deletion(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "OpenBTS' transceiver retro-fit".
The branch, fairwaves/ext-build-fix has been created
at c88385c69d6a8ed415b7bc2480d13683ac8f6ca0 (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-trx/commit/?id=c88385c69d6a8ed415b7bc2480d1368…
commit c88385c69d6a8ed415b7bc2480d13683ac8f6ca0
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Fri Apr 29 14:05:59 2016 +0300
makefile: Fix build from an external path.
When you build from an external path, compiler can't find convert.h
include, because it was specified relative to the current directory.
Change this to specify the include dit relative to the Makefile
location.
-----------------------------------------------------------------------
hooks/post-receive
--
OpenBTS' transceiver retro-fit
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "An utility library for Open Source Mobile Communications".
The branch, laforge/pending has been updated
discards 22c9f6b79869480d58ad9aa9d951ca88af70c60d (commit)
discards e8de4610400e299dedd4d143bb4fa9dc12d4e9b8 (commit)
discards 5d57360f7a3973dcc49c5d8f7e8f3086ee910441 (commit)
discards 01b4115a3dcc806297e6593ac0a01962209e32e2 (commit)
discards 85a1009e9f3c2bff8e3625129357e85a5c481cad (commit)
discards 197bc3364686881daecde62c3fc3b87bc4f20c4a (commit)
discards 0d7aaded15b683a3540ba85299ec8dd4b54ec475 (commit)
discards 090f9859b9bb6c0af5c17aca037951360217505a (commit)
discards 90d72bb18e6c0e236f22eaa12b52bab182e52bc9 (commit)
discards 6291ffafed10bfe31eef28f81ba7019aff4b557a (commit)
via 2cf120ff128e2ef10713b7b13149805df9f269fc (commit)
via fa128d3c4b7db9c1e6c84d8ffe2c2e843ba20d37 (commit)
via b1fc280438f6b8d23b3af7f9ea2cfacb6f51751b (commit)
via 4ba1323035d228fbd5146f603962f00854ad1cad (commit)
via 44409f9aa997e19e66cfdcefa0f51f66ea286971 (commit)
via f1088f7734b0b80ff39fbe09898d5a3cd778f26a (commit)
via 05ea145fd99872e1041aa733d2e4dc2a87d53598 (commit)
via dbe8e3e3901d67c5fd122cace146464d326e4efa (commit)
via 322a2f3874996bd32748b380178bf3e31aac9cf0 (commit)
via 1cd0d8af6f66010f2d59196bf227b87989a44282 (commit)
via aa16d63c273204dc69108f7361d38b751bfb69e4 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (22c9f6b79869480d58ad9aa9d951ca88af70c60d)
\
N -- N -- N (2cf120ff128e2ef10713b7b13149805df9f269fc)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmocore/commit/?id=2cf120ff128e2ef10713b7b13149…
commit 2cf120ff128e2ef10713b7b13149805df9f269fc
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Wed Apr 27 18:32:35 2016 +0200
import oap message parsing / encoding from openbsc.git
http://cgit.osmocom.org/libosmocore/commit/?id=fa128d3c4b7db9c1e6c84d8ffe2c…
commit fa128d3c4b7db9c1e6c84d8ffe2c2e843ba20d37
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Mon Apr 25 19:09:24 2016 +0200
add doc/*.tag to .gitignore
http://cgit.osmocom.org/libosmocore/commit/?id=b1fc280438f6b8d23b3af7f9ea2c…
commit b1fc280438f6b8d23b3af7f9ea2cfacb6f51751b
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Mon Apr 25 18:46:22 2016 +0200
import gprs_gsup_message.[ch] from openbsc as gsup.[ch]
Move those routines from OpenBSC to libosmogsm, so they can be
re-used from other programs. I think it was a mistake to add them only
inside the openbsc repository in the first place. We need to pay more
attention to this in the future.
http://cgit.osmocom.org/libosmocore/commit/?id=4ba1323035d228fbd5146f603962…
commit 4ba1323035d228fbd5146f603962f00854ad1cad
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Mon Apr 25 18:47:53 2016 +0200
Import osmo_{encode,decode}_big_endian() from openbsc
http://cgit.osmocom.org/libosmocore/commit/?id=44409f9aa997e19e66cfdcefa0f5…
commit 44409f9aa997e19e66cfdcefa0f51f66ea286971
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Mon Apr 25 15:19:35 2016 +0200
tlv: Import osmo_shift_* and osmo_match_shift_* from openbsc
These routines have nothing to do with specifically the BSC, so import
them to the TLV parser we keep in libosmogsm.
http://cgit.osmocom.org/libosmocore/commit/?id=f1088f7734b0b80ff39fbe09898d…
commit f1088f7734b0b80ff39fbe09898d5a3cd778f26a
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Mon Apr 25 12:11:20 2016 +0200
Update doxygen annotations in libosmocore
This adds and improves doxygen API descriptions all over libosmocore,
reducing the 'white spots' that don't have any documentation.
http://cgit.osmocom.org/libosmocore/commit/?id=05ea145fd99872e1041aa733d2e4…
commit 05ea145fd99872e1041aa733d2e4dc2a87d53598
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Wed Apr 20 17:28:03 2016 +0200
add new header file for TS 23.003
http://cgit.osmocom.org/libosmocore/commit/?id=dbe8e3e3901d67c5fd122cace146…
commit dbe8e3e3901d67c5fd122cace146464d326e4efa
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Wed Apr 20 17:12:24 2016 +0200
import gsm_04_08_gprs.[ch] from openbsc.git
The definitions in this header file (and associated strings in the
c file) are generic about the GPRS Layer3 signalling protocols, and
thus should be part of the library.
http://cgit.osmocom.org/libosmocore/commit/?id=322a2f3874996bd32748b380178b…
commit 322a2f3874996bd32748b380178bf3e31aac9cf0
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Wed Apr 20 10:41:27 2016 +0200
Add log_fini() function to release all memory allocated by logging framework
This is e.g. quite useful to call at the end of test code, in order to
show that all memory allocated actually is released before exit().
http://cgit.osmocom.org/libosmocore/commit/?id=1cd0d8af6f66010f2d59196bf227…
commit 1cd0d8af6f66010f2d59196bf227b87989a44282
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Wed Apr 20 10:39:00 2016 +0200
auth_core: Add osmo_auth_3g_from_2g() to compute CK+IK from Kc
This function performs the C5+C4 conversion to derive UMTS key
material from a 2G-only subscriber.
-----------------------------------------------------------------------
Summary of changes:
src/gsm/milenage/aes_i.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
An utility library for Open Source Mobile Communications
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom BTS-side code (Abis, scheduling, ...)".
The branch, master has been updated
via ed494443cc1e9732b43ef99cccf187d17ac931ef (commit)
from b61850248adbf717eb323d9ce7a17a817c302544 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-bts/commit/?id=ed494443cc1e9732b43ef99cccf187d…
commit ed494443cc1e9732b43ef99cccf187d17ac931ef
Author: Max <msuraev(a)sysmocom.de>
Date: Thu Apr 21 18:55:09 2016 +0200
Ensure TRX invariant
There is implicit invariant in trx_phy_instance() which is actively used
by various hw-specific implementations to get TRX's phy instance. Let's
make sure there's explicit assertion for this because there's been
segfaults in the past related to it.
-----------------------------------------------------------------------
Summary of changes:
include/osmo-bts/phy_link.h | 1 +
1 file changed, 1 insertion(+)
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenGGSN project".
The branch, master has been updated
via f89dc4e127eea6addea6a7b45eb96da8c1053ba4 (commit)
from b29ff1da554a2654cc593ea243e29cd7883c92da (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openggsn/commit/?id=f89dc4e127eea6addea6a7b45eb96da…
commit f89dc4e127eea6addea6a7b45eb96da8c1053ba4
Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Date: Mon Apr 25 13:00:10 2016 +0200
queue_new(): fix NULL dereference on allocation failure
Coverity complains about a 'Dereference before null check' on *queue.
So, push the NULL check further up.
Though I doubt that 'return EOF' is the proper way to handle allocation
failure, this patch is only about the NULL dereference.
Fixes: CID#57918
-----------------------------------------------------------------------
Summary of changes:
gtp/queue.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
hooks/post-receive
--
The OpenGGSN project
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom A-bis protcol interface library".
The branch, laforge/pending has been updated
discards 26c974681b0cd6fda0bd3255c02851d4143fbdfb (commit)
discards aee9302264b82d6361a922b9cce6bee0174a11f5 (commit)
discards 5c4e7d8d553c0e0fe6cb351c0a96adb01ede717d (commit)
via 9ed7ca5b86240313dc4df8dbf4ff67be112084c1 (commit)
via 12814b96367ca4ef7e94fb5fb18609d5fabd33a1 (commit)
via b2d727a10256ed133f0db7f6760bfef73f8b9f6e (commit)
via 8c119f7a0510b75e7fa1b96a37f2a6650e13824f (commit)
via 80f7c0465fd244c26b037aaee92458c8dce86c6e (commit)
via e54d7bcef534461f794f98fa186f8afd8f8c318d (commit)
via d8026ec1b7be7922fd1c3122d2407a783cdab163 (commit)
via 7c9337b7755bfa51bdcba5cc76682217202fd635 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (26c974681b0cd6fda0bd3255c02851d4143fbdfb)
\
N -- N -- N (9ed7ca5b86240313dc4df8dbf4ff67be112084c1)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmo-abis/commit/?id=9ed7ca5b86240313dc4df8dbf4f…
commit 9ed7ca5b86240313dc4df8dbf4ff67be112084c1
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Thu Apr 28 11:10:01 2016 +0200
ipa_bts_id_resp(): handle non-existing members of ipacces_unit
Just because the IPA server is requesting certain identities via the CCM
protocol, doesn't mean that the client actually has those fields
available and initialized in struct ipaccess_unit.
Instad of segfaulting the client, let's check if the respective
identities are known. If yes, send them. If not, send the empty string
for that particular identity.
http://cgit.osmocom.org/libosmo-abis/commit/?id=12814b96367ca4ef7e94fb5fb18…
commit 12814b96367ca4ef7e94fb5fb18609d5fabd33a1
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Thu Apr 28 07:54:31 2016 +0200
ipa_server_conn: Add server-side CCM handling
An ipa_server implementation may call ipa_server_conn_ccm for
the CCM processing on the server side of the connection. This
function in turn will call a conn->ccm_cb() function for messages to be
handled by the server implementation, such as the ID_RESP message,
which contains the Unit ID of the client that has just connected.
http://cgit.osmocom.org/libosmo-abis/commit/?id=b2d727a10256ed133f0db7f6760…
commit b2d727a10256ed133f0db7f6760bfef73f8b9f6e
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Thu Apr 28 07:53:49 2016 +0200
ipa_server_conn: Add remote (peer) address to struct
This is better than every implementation calling getpeername()
on its own.
-----------------------------------------------------------------------
Summary of changes:
Makefile.am | 2 ++
contrib/jenkins.sh | 19 +++++++++++++++++++
include/osmocom/trau/osmo_ortp.h | 1 +
src/trau/osmo_ortp.c | 24 ++++++++++++++++++------
4 files changed, 40 insertions(+), 6 deletions(-)
create mode 100755 contrib/jenkins.sh
hooks/post-receive
--
Osmocom A-bis protcol interface library
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".
The branch, master has been updated
via 35697b9a109f08791c00dbb1a8dfaaaff29a8a80 (commit)
via 299a9994656e97defea85689467e61ba34e8577e (commit)
from e01f5050efbc3828defa2df9b789624854297663 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=35697b9a109f08791c00dbb1a8dfaaaf…
commit 35697b9a109f08791c00dbb1a8dfaaaff29a8a80
Author: Max <msuraev(a)sysmocom.de>
Date: Fri Apr 29 12:51:31 2016 +0200
Adjust si2quater ranges
Change ranges of arguments for si2quater neighbor lists to proper values
according to 3GPP spec.
http://cgit.osmocom.org/openbsc/commit/?id=299a9994656e97defea85689467e61ba…
commit 299a9994656e97defea85689467e61ba34e8577e
Author: Max <msuraev(a)sysmocom.de>
Date: Thu Apr 28 17:51:15 2016 +0200
Fix comment typo
-----------------------------------------------------------------------
Summary of changes:
openbsc/src/libbsc/bsc_vty.c | 11 ++++++-----
openbsc/src/libbsc/system_information.c | 2 +-
2 files changed, 7 insertions(+), 6 deletions(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom A-bis protcol interface library".
The branch, master has been updated
via 8c119f7a0510b75e7fa1b96a37f2a6650e13824f (commit)
via 80f7c0465fd244c26b037aaee92458c8dce86c6e (commit)
via e54d7bcef534461f794f98fa186f8afd8f8c318d (commit)
from d8026ec1b7be7922fd1c3122d2407a783cdab163 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmo-abis/commit/?id=8c119f7a0510b75e7fa1b96a37f…
commit 8c119f7a0510b75e7fa1b96a37f2a6650e13824f
Author: Max <msuraev(a)sysmocom.de>
Date: Fri Apr 29 12:39:35 2016 +0200
Set connected mode after setting remote address
ortp: according to oRTP documentation rtp_session_set_connected_mode()
uses the address set by rtp_session_set_remote_addr() - move the
function call accordingly.
Fixes: OS#1661
http://cgit.osmocom.org/libosmo-abis/commit/?id=80f7c0465fd244c26b037aaee92…
commit 80f7c0465fd244c26b037aaee92458c8dce86c6e
Author: Max <msuraev(a)sysmocom.de>
Date: Fri Apr 29 12:39:34 2016 +0200
Fix RTCP port allocation
Force use of RTCP port adjacend to random RTP port, if random RTP port
is used.
Before this patch, port 0 could be selected for RTCP.
http://cgit.osmocom.org/libosmo-abis/commit/?id=e54d7bcef534461f794f98fa186…
commit e54d7bcef534461f794f98fa186f8afd8f8c318d
Author: Max <msuraev(a)sysmocom.de>
Date: Fri Apr 29 12:39:33 2016 +0200
Do not send RTP to port 0
Previously it was possible to send RTP data to port 0. This produce
multiple errors during the beginning of RTP transmission.
To address this OSMO_RTP_F_DISABLED flag was introduced. It's set by
default for all new RTP sessions. It can be manually unset after the
call to osmo_rtp_socket_create(). When the flag is set it prevents
transmission and reception of RTP frames for the session. The flag is
unset automatically in osmo_rtp_socket_connect() when session is bound
to non-zero remote port.
Fixes: OS#1662
-----------------------------------------------------------------------
Summary of changes:
include/osmocom/trau/osmo_ortp.h | 1 +
src/trau/osmo_ortp.c | 24 ++++++++++++++++++------
2 files changed, 19 insertions(+), 6 deletions(-)
hooks/post-receive
--
Osmocom A-bis protcol interface library
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom A-bis protcol interface library".
The branch, max/tmp has been updated
discards f8a6033124af552ea78bcd1a6bc38027dded8592 (commit)
discards 11c6ae4cd6dba71c69534ebc23061cc42238ba88 (commit)
discards 9acb2dc98a369c17151099e9e405e9c64e3e55a3 (commit)
via 620251cdc3160b647cb7433a7001d54f0ce7fece (commit)
via 80f3a0bc24ff22603012df791315b057c9e73c22 (commit)
via d2313ad4103a4850f4976a41433d46f4c0c4ade6 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (f8a6033124af552ea78bcd1a6bc38027dded8592)
\
N -- N -- N (620251cdc3160b647cb7433a7001d54f0ce7fece)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmo-abis/commit/?id=620251cdc3160b647cb7433a700…
commit 620251cdc3160b647cb7433a7001d54f0ce7fece
Author: Max <msuraev(a)sysmocom.de>
Date: Fri Apr 29 11:54:23 2016 +0200
Set connected mode after setting remote address
ortp: according to oRTP documentation rtp_session_set_connected_mode()
uses the address set by rtp_session_set_remote_addr() - move the
function call accordingly.
Fixes: OS#1661
http://cgit.osmocom.org/libosmo-abis/commit/?id=80f3a0bc24ff22603012df79131…
commit 80f3a0bc24ff22603012df791315b057c9e73c22
Author: Max <msuraev(a)sysmocom.de>
Date: Mon Apr 25 16:54:16 2016 +0200
Fix RTCP port allocation
Force use of random RTCP port if random RTP port is used. Before port 0
could be selected for RTCP.
http://cgit.osmocom.org/libosmo-abis/commit/?id=d2313ad4103a4850f4976a41433…
commit d2313ad4103a4850f4976a41433d46f4c0c4ade6
Author: Max <msuraev(a)sysmocom.de>
Date: Thu Apr 28 14:08:02 2016 +0200
Do not send RTP to port 0
Previously it was possible to send RTP data to port 0. This produce
multiple errors during the beginning of RTP transmission.
To address this OSMO_RTP_F_DISABLED flag was introduced. It's set by
default for all new RTP sessions. It can be manually unset after the
call to osmo_rtp_socket_create(). When the flag is set it prevents
transmission and reception of RTP frames for the session. The flag is
unset automatically in osmo_rtp_socket_connect() when session is bound
to non-zero remote port.
Fixes: OS#1662
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Osmocom A-bis protcol interface library
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Osmocom A-bis protcol interface library".
The branch, max/tmp has been updated
discards 1698a819d16167a84eff701edb8355865a1bc1e3 (commit)
via f8a6033124af552ea78bcd1a6bc38027dded8592 (commit)
via 11c6ae4cd6dba71c69534ebc23061cc42238ba88 (commit)
via 9acb2dc98a369c17151099e9e405e9c64e3e55a3 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (1698a819d16167a84eff701edb8355865a1bc1e3)
\
N -- N -- N (f8a6033124af552ea78bcd1a6bc38027dded8592)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmo-abis/commit/?id=f8a6033124af552ea78bcd1a6bc…
commit f8a6033124af552ea78bcd1a6bc38027dded8592
Author: Max <msuraev(a)sysmocom.de>
Date: Fri Apr 29 11:54:23 2016 +0200
Set connected mode after setting remote address
ortp: according to oRTP documentation rtp_session_set_connected_mode()
uses the address set by rtp_session_set_remote_addr() - move the
function call accordingly.
Fixes: OS#1661
http://cgit.osmocom.org/libosmo-abis/commit/?id=11c6ae4cd6dba71c69534ebc230…
commit 11c6ae4cd6dba71c69534ebc23061cc42238ba88
Author: Max <msuraev(a)sysmocom.de>
Date: Mon Apr 25 16:54:16 2016 +0200
Fix RTCP port allocation
Force use of random RTCP port if random RTP port is used. Before port 0
could be selected for RTCP.
http://cgit.osmocom.org/libosmo-abis/commit/?id=9acb2dc98a369c17151099e9e40…
commit 9acb2dc98a369c17151099e9e405e9c64e3e55a3
Author: Max <msuraev(a)sysmocom.de>
Date: Thu Apr 28 14:08:02 2016 +0200
Do not send RTP to port 0
Previously it was possible to send RTP data to port 0. This is not only
producing multiple errors but also breaks RTP transmission with
newer (>= 0.25) oRTP leading to calls with no audio.
To address this OSMO_RTP_F_DISABLED flag was introduced. It's set by
default for all new RTP sessions. It can be manually unset after the
call to osmo_rtp_socket_create(). When the flag is set it prevents
transmission and reception of RTP frames for the session. The flag is
unset automatically in osmo_rtp_socket_connect() when session is bound
to non-zero remote port.
Fixes: OS#1662
-----------------------------------------------------------------------
Summary of changes:
src/trau/osmo_ortp.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
hooks/post-receive
--
Osmocom A-bis protcol interface library