OpenBSC required additional care because of an unusal .git location.
This is not need anymore for osmo-mgw
Change-Id: I5aad67612026947ad52cdc9477b603732c146e7a
Add vty and logging previously used from libcommon
Rename libmgcp to libosmo-legacy-mgcp and install.
Use DLMGCP, not DMGCP.
Change-Id: I71a0a16ebaaef881c34235849601fc40aa12cfd7
Depends: libosmocore I09c587e2d59472cbde852d467d457254746d9e67
Remove libiu here, use the functions from libosmo-ranap instead, by applying
the ranap_ / RANAP_ prefix.
Corresponding change-id in osmo-iuh.git is I6a3f7ad15be03fb94689b4af6ccfa828c25f45c0
Change-Id: Ib8c4fcdb4766c5e575618b95ce16dce51063206b
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
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
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
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"
Change-Id: Ib56134193ba95538f63e09dc702dc3ff0e827a02
The warning message that is displayed when a non standard SSN is
set is confusing.
Make warning message more expressive.
Change-Id: I5283bcc5acf4739d468fe43937f0e59f44dee3d9