Age | Commit message (Collapse) | Author | Files | Lines |
|
When writing the config file the options bsc-addr, and msc-addr,
a (null) string is written to the config file, which prevents
the config file from reading it back.
memorize the string names given to bsc-addr and msc-addr and
write them back, also check if the strings are NULL in case
the user did not set any names.
|
|
use osmo_sccp_addr_name() instead of osmo_sccp_addr_dump()
|
|
use osmo_sccp_addr_name() instead of osmo_sccp_addr_dump()
|
|
|
|
|
|
|
|
libosmo-sccp offers a function to set the SSN. Make use of this
function instead of manipulating the struct directlry
|
|
libosmo-sccp function osmo_ss7_vty_init_sg() now requires a talloc
context as parameter.
Note: It should not _asp() rather then _sg(). However, we can not
switch now, because then we will miss the vtx commands that
configure the default route. Since the default route is the only
valid route for application server processes, we need to fix this
in the simple client, so that this command is no longer needed,
when configuring the as. Also the VTX write functions of
libosmo-sccp need to be fixed first.
|
|
If invalid addresses, or a missing CS7 instance is detected
during startup, the BSC will assume safe defaults. The defaults
picked are complementary to osmo-msc, so in case the user just
wants to run the osmo-msc and osmo-bsc + the STP on one machine,
no CS7 configuration is needed at all.
|
|
Currently the force_realloc feature is turnd on and of in a
hardcoded way. This patch makes the option available via VTY.
|
|
|
|
If the user chooses to use a single sccp instance to connect to
the core network. That instance would be named OsmoMSC-Iu. This
is confusing because that same connection would also serve all
A interface traffic. This patch checks for the described condition
and picks a more suitable name then.
|
|
Use the check functionality of libosmo-sigtran to test if the
sccp addresses are smantically correct.
|
|
To prevent a situation where one ore more seized enpoints stay
seized after an MSC crash (information loss, endpoints can not
be released) we send a DLCX command before making new connections
on the MGCP-GW. This method is loud and hackish.
Remove all functionality that sends a DLCX before making a new
connection.
Enable force_realloc functionality in the MGCP code in order to
have seized enpoints automatically released on new connections,
in case they are seized
|
|
In SGSN, actually place the port in the SGSN config by default, so that the
gsup port may now be omitted in the VTY config (the IP address suffices).
Adjust the osmo-sgsn.cfg example.
Depends: I4222e21686c823985be8ff1f16b1182be8ad6175 (libosmocore)
Change-Id: I50f2040e2eb0baacb43849e93cfed10cbc2fc156
|
|
In case of an IMSI Detach, we don't have a conn_fsm, yet we still need to send
release messages. Hence directly release the conn in msc_subscr_conn_close()
when there is no conn_fsm present.
Move the conn release actions from the conn_fsm cleanup function to new
function msc_subscr_conn_release_all(). From the FSM cleanup, call
msc_subscr_conn_close(), and invoke msc_subscr_conn_release_all() from there.
Document msc_subscr_conn_close() behavior.
Change-Id: Ied6981099605ad803f8ffed38f23ed8203a97727
|
|
Adjust test expectations.
Note: this marks all the places where we are so far failing to send a
Clear/Release, where during an IMSI Detach the log now says "no conn fsm,
ignore".
In msc_vlr_test_reject_concurrency, the places are marked "already in release"
because these tests for simplicity have a rather peculiar sequence of sending
an IMSI Detach right after a CM Service Request, on an open connection.
Change-Id: I1c4dc4e5afce3bcb98237e3506300c78d7e4584f
|
|
Match the log message for known subscriber to the one for unknown subscriber.
Change-Id: I73871089036c9fd301e818eaaf48142aaf295d09
|
|
Change-Id: Ia64bc937d7f37ef6209efbdf884de61008f8816d
|
|
Change-Id: Ie60e00e07b2129ac4bb3cac94921bf3c8d9cd861
|
|
Change-Id: Ieba69e4014213b18c18282dd724e202cce85a047
|
|
0001-imsi-detach-improve-error-logging.patch
0002-imsi-detach-always-close-connection-explicitly.patch
|
|
The clear command is currently triggered from the wrong place.
This is a fixup that corrects that. However, it will introduce
another problem: The clear command is not sent on detach.
Adjust test expectations.
Change-Id: Ia27d7e94cb11adf351457b3b0e98a5c9d5070fbf
|
|
The sccp/ss7 configuration is now fixed. The cs7 instance id is
implicitly detected from the bsc_addr or the msc_addr. Depending
on what is listed last. (I am not sure if that is wise, maybe
we should only use the local/bsc address to do the lookup).
Remove cs7-instance vty command
Modify VTY commands, so that the fixed API is used
Set msc->a.cs7_instance from the VTY to when msc/bsc addr is parsed
Fix the initalization to use osmo_sccp_simple_client_on_ss7_id() and
pass the cs7-instance id we determined from the vty.
The whole thing is not waterproof yet. We are still not at the
point where we allow to leave the local address out. This would
be fine, but when it is left out, the only way to determine the
cs7 instance is to use the msc_addr then.
We also might want to make sure to reach a state where all cs7
related config may be left out (like with the MSC)
|
|
|
|
|
|
The clear command is sent via the A-Interface for both,
A and IuCS connections. This is wrong.
Only send the clear command for connections related to
the A-Interface, which means only for connections where
the RAN is set to GERAN
|
|
|
|
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"
|
|
|