2c33e2a81e
ss7: Mark the link as down after the shutdown
2015-10-09 12:10:49 +02:00
b492e86e4f
ss7: Allow to force the link down when the IPA conn is going down
...
For the "bridging" to IPA mode we can force the SCTP/M3UA connection
down. This way the remote STP will do a proper link fail-over
procedure instead of the STP throwing data away.
This is not configurable yet.
2015-09-21 16:43:20 +02:00
78f5060c62
ss7: Inform the application layer that a connection is down
...
This can be used to force one connection down while the other
is down. E.g. to force SCTP down when the IPA connection is
down as well.
2015-09-21 15:47:10 +02:00
c4e5066d1d
app: Mark the transport as started for the relay mode
...
This code could be shared with the STP setup code.
2013-04-22 17:58:34 +02:00
e833478898
isup: Hook the reset scanner before we forward the ISUP message
...
Scan for two kind of reset messages in the ISUP messages. Forward
them to the mgcp_ss7.
2012-12-16 12:45:58 +01:00
b35c5c3227
stp: Allow to specify a trunk_name in the application
...
This trunk name will be used to send RSIP for the trunk on ISUP
resets. Right now each app can be associated only one trunk.
2012-12-16 12:10:32 +01:00
a59af64126
ss7: Make the forwarding methods static
2012-01-16 09:54:09 +01:00
fc98ce252e
vty: Add a config to enable MGCP command rewriting
2011-09-13 20:08:57 +02:00
Harald Welte
ff397edf38
Adopt to recent libosmocore namespace changes and libosmogsm
2011-05-08 10:29:23 +02:00
2068e8cfe3
vty: Remember if isup should be passed through or not.
2011-03-05 09:48:52 +01:00
56cba9ab45
ss7: Drop the input of packages as well
...
We don't want the input change any state on the linkset and will
drop them if we think our application is not reachable.
2011-03-03 01:20:03 +01:00
899198ed2e
ss7: Move the blocking of outgoing messages into the SS7 app
...
We are using knowledge of the SS7 application to drop outgoing
packages to force failures on the link and should move this into
the ss7 application.
2011-03-03 01:19:45 +01:00
d38b87a4c9
ss7: Do not send anything until both linksets in an app are up
...
We need some way to forward the failure of one link to another but
they are not normally routed so we can not send a TFP. Right now we
will simply stop responding until both links are up. This should make
the SLTM fail and trigger a re-alignment on both sides. The key here
is that the 2 * SLTM timeout needs to be higher than it takes to re-align
the link. I'm not sure this code will work.
2011-03-03 01:19:02 +01:00
7176030e02
vty: Add all mighty new vty interface for osmo-stp
...
This new interface allows to have multiple linksets, msc
connections and ways to connect those in one instance of
the osmo-stp. Forbid to reset linksets without an app.
2011-02-23 15:25:35 +01:00
169a1a918c
misc: Use llist_add_tail to add new links to the end
2011-02-22 21:05:59 +01:00
cfe9d718e2
vty: Remove more globals from the bsc data.
...
This is a interim solution until we have the new and all mighty
new config file format. This should work for now, makes the init
abit harder to understand though.
2011-02-22 21:05:59 +01:00
a33b23f293
mtp: Rename no to nr to align with the rest of the structs
2011-02-17 19:34:28 +01:00
64b7d56dc0
ss7: Move all mtp linksets callbacks into the app layer
2011-02-17 19:34:28 +01:00
c5200fcb35
ss7: Move the linkset up/down into the ss7_app, move some code around
2011-02-17 19:34:27 +01:00
ab7c601118
ss7: Provide a way to start the application
2011-02-17 19:34:27 +01:00
a7bc3aafdc
ss7: Create a SS7 application that is responsible for the routing
2011-02-17 19:34:27 +01:00
Holger Hans Peter Freyther
Harald Welte