Age | Commit message (Collapse) | Author | Files | Lines |
|
The external mncc currently does not work properly since the
MNCC_RTP_CREATE commands are removed due to the MSC-Split. It
is possible to operate without these commands, but then it is
not possible to route the RTP streams to an outside leg. Only
internal bridging is currenlty possible. This method is used
when the internal MNCC is enabled.
Add the missing MNCC_RTP_CREATE implementation.
Add logic to keep the old bridging mode working.
|
|
The generated mgcp messages are not displayed properly (stray
newlines). Also, the messages we receive are not displayed
at all.
Display generated and received messages in logtext, reformat
the strings properly so that the logtext does not get messed
up
|
|
|
|
Change-Id: Iec3dbeb0ee1421129aaf9e313d616757955bee48
|
|
When a subscriber connection is freed on the MSC side (the
conversion is over) the MSC should send a clear command to
the BSC in order to inform the BSC that the connection is
over. Currently this step is missing. Instead we wait for
the BSC to issue a clear request. This is not as it should
be, connections should be actively cleared by the MSC.
Add the missing clear command
|
|
|
|
|
|
|
|
|
|
The allocation and usage of the iu struct was accidentally
re-introduced into a_iface_bssap.c.
Remove the allocation and the usage of iu struct.
Related to:
aoip: don't use iu struct: do not allocate unnecessary ue_conn_ctx
|
|
_dt1() is not applicable with the current setup, _dt() is
more accurate
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Using the MSC numbers in the logtext is not very expressive,
ise the SCCP-Addresses instead.
When creating the sccp instance and user, use more parseable
string than "MSC No.: n"
|
|
|
|
The warning message that is displayed when a non standard SSN is
set is confusing.
Make warning message more expressive.
|
|
Change-Id: I838cc9176b9d3e61e33f25d10bedd37c9c057fd3
|
|
The variable name "calling_addr" is not very expressive. Change
the variable name to "msc_addr".
|
|
The vty commands:
called-addr my_msc
calling-addr my_bsc
are not very expressive to the user. Change the command
names into something more expressive:
msc-addr my_msc
bsc-addr my_bsc
Also change the function and variable names accordingly
|
|
"calling_address" and "called_address" is not very expressive.
change the respective struct memeber names of bsc_msc_data to
bsc_addr and msc_addr to increase readability of the code.
|
|
do not start unless the user has configured sufficient SCCP
addresses via VTY. Do not accept address that lack point codes
or ssn
|
|
The VTY technically allows setting custom values for the
SSN. However, SSN values and their purposes are well
standardized.
If the user has configured an SSN, check that is compliant
to the standard. If not, warn and ignore the setting by
using the stanard SSN.
If the user left out the SSN, automatically use the standard
SSN.
|
|
|
|
The BSC clears all connections on reception of a
BSSAP RESET, however, the RESET command must not
affect the connections of other MSCs.
Ensure that only the connections of the MSC who
actually sent the BSSAP RESET are cleared.
|
|
Add VTY commands to configure the sccp-address of the BSC
and the one of the MSC.
|
|
The current VTY implementation has no knowledge about the
libosmo-sccp nodes and therefor can not resolve parent nodes,
nor decide if we deal with a config node.
|
|
finish the implementation for msc sided reset, automatically
register connecting BSCs.
Ensure that all sccp connections are cleared when the reset
procedure executes.
|
|
Swap libmsc.a and libcommon-cs.a to make symbols from
libcommon-cs.a available to libmsc.a
|
|
The call id field in the DLCX message is missing. Use the endpoint
id as call id in all CRCX and DLCX messages.
|
|
When the reset is started, state machines are allocated. The user
must provide a correctly filled structure where the reset start
function adds the state machine into.
This is prone to errors, besides of that, a proper deallocator
function which tears down the osmo fsm is missing.
make a more cofmortable allocator function and add deallocator
function.
|
|
Change-Id: I2ec2ecc2e3dcf0493168de6091d7fa4cfa028645
|
|
Change-Id: I6430d4704f5caf33275d403df93c222848b5b3ff
|
|
Change-Id: Ib065533273acfabec9d9d4380dcbd6cf16744343
|
|
Move osmo_sccp_simple_client() setup out of iu_init() and a_init().
In msc_main.c and sgsn_main.c, initialize the STP connection first and then
pass to iu_init() and a_init().
This allows serving 3G (IuCS) and 2G (A) from one and the same MSC instance.
Since both OsmoHNBGW and OsmoBSC are using PC 23 by default now, move BSC to PC
42 (because OsmoBSC typically has vty port 4242, bla).
Also:
a_iface.c: remove now unused defines
a_init(): remove osmo_ss7_init() call that duplicated msc_main.c
Change-Id: Ib1fb13ea756655f7e9d43636d497a54e6ae9c032
|
|
Change-Id: If12ca46c834466307bee6465b777d63d5c922405
|
|
Change-Id: I10e899777e21bf1dbfba1e7e692d7017593e5f38
|
|
|
|
Currently we do not check for errors during the generation of
channel type and speech codec list. This might blow an assertion
in gsm0808_create_ass if the generated data is invalid. So
we need to check beforehand.
|
|
The log output from the rsl layer injects line breaks at wrong
places in the log. This messes up the logtext. This commit fixes
the problem.
|
|
When the mgcp_client prints MGCP strings in the log text, it does
not remove the line break before printing. This will mess up
the log text. This patch removes the line break characters before
printing properly.
|
|
Change-Id: Ic659d6d79a6284732e1837f8b0947e8a128ddd87
|
|
The bsc side currently can not receive reset commands from an
MSC. This patch adds required functionality to receive a reset
command and acknowlege it properly. The effects are the same
as with when sending resets (all drop all ongoing calls and
sccp connections)
|
|
The AoIP standard also describes an MSC->BSC reset procedure. We
currently do not implement it. However, the fsm that is used to
issue the reset request from the bsc side is not generalized. This
patch generalizes the code in order to be able to use the same
code on the MSC side to perform a reset procedure from there.
|