Age | Commit message (Collapse) | Author | Files | Lines |
|
The problem has been here for a while, fix the parsing of the
generated config file
|
|
A virtual trunk is identified by a virtual domain name.
|
|
MGCP RFC 3435 does not specify that the Connection Id must be
generated with any kind of random. It must uniquely identify
the connection of an endpoint. So we can make it per trunk group
or could even have it per endpoint.
The code does not support multiple connections on the same endpoint
right now but the spec allows it.
|
|
It can be difficult to find the Timeslot/Multiplex for a higher
number virtual trunk. This would be used by default, but normally
the endpoint would be blocked on the switch already.
|
|
Instead of assuming which endpoints are blocked there is now a VTY
command to block those. Clean up the init of the trunks, the only difference
between Virtual and E1 is in the way to calculate the start port.
Reduce the number of endpoints to 32, 31 is the last one that can be
used on the E1 trunk, otherwise we move into TS 0 of the following trunk.
|
|
Create the endpoints as soon as possible, configure static ports
after we are through with the parsing of the VTY config.
|
|
The endpoint offset is needed for two reasons, first the API is 0
based here while we are normally 1 based, second because of the trunks
the first usable endpoint would be '2' (0 is CRC, 1 is signalling), but
this endpoint offset falls apart when we would block timeslots inside
this range.
Remove the endpoint offset, in each endpoint we will store the HW DSP
Port (1 based API) and then subtract one to get to the 0 based API for
the Simple API. Print a warning when someone is using the endpoint offset.
|
|
|
|
The MSC workaround was added in 5960ba387aa84574fc8b9df20ea98ca1594d1658
but it has never worked as in 8fd28dbbe64cb32e5f296bd2679cebf03b5d14c0 (earlier)
we were checking for link->conn != conn in the dispatch method. Move the
code over to the generic dispatch and check for NULL.
|
|
This will print details about each SCTP connection including the
FD and pointer of it.
|
|
When we get an ASP UP check if there is any other ASP that is
using the same identifier and then complain.
|
|
It appears that it is possible to have a stale SCTP connection
and this added LOGL_NOTICE and the VTY interface might help to
identify this situation in the future (the mean time of failure
is about five month).
|
|
The DSCCP/DM2UA code still needs to be updated to deal with the
new way to handle these regions in libraries.
|
|
|
|
This will hopefully make the MTN4200 always use the
5.9kbit change mode.
|
|
|
|
Instead of hardcoding which timeslot is blocked we will just
use the blocked flag in an endpoint. This should fix call
handling for CIC on the trunk config.
|
|
We don't let CGUAs pass when handling circuit blocking and
unblocking locally. But we did let a CGU go through and then
we never sent the response back to the sender. Respond to a
CGU with the same content.
|
|
|
|
|
|
|
|
We don't want the input change any state on the linkset and will
drop them if we think our application is not reachable.
|
|
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.
|
|
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.
|
|
|
|
After the expiry of T18 we should have collected the routing data
from the adjacent links and should be able to send SCCP packages
to remote endpoints.
|
|
|
|
|
|
Stop using the hardcoded link index and use the link index
of the link.
|
|
The MSC we test is not sending an ASP Active when the
link is unblocked. If the m2ua_link has no connection
associated we will forgive the MSC and active it.
|
|
|
|
Right now for the virtual trunk 0x0 and 0x1F is blocked, for the
E1 like interface we have 0x0 and 0x1 blocked. This should start
to be configurable in the future.
|
|
|
|
|
|
Configure the routing of audio ports if mgcp_mgw is configured
to do this. This allows to have multiple trunks, make virtual
ports go to a specific trunk as well.
|
|
|
|
With this commit we can have more than 30 endpoints that will work. We
ignore the blocked endpoints 0x1 and 0x1f for each trunk and calculate
everything from the right start point.
|
|
* Upstream has a separation of BTS and NET side for RTP ports and
can allocate them dynamically.
* Upstream has gained the concept of trunks. We will now have various
trunks to connect audio things.
* We will now be able to utilize multiple trunks and have the endpoints
used properly.
|
|
number_endpoints is always one bigger than it needs to be,
subtract the one in the show command, start counting at one.
|
|
|
|
|
|
|
|
Without events we don't have access to the SCTP sndrcvinfo and
the ppid in it and we will do bad things like sending M2UA on
PPID 0.
|
|
|
|
|
|
|
|
In a backtrace it is confusing to see variables called link and link
and one is a mtp_link and the other is a mtp_link_set.
|
|
|
|
Right now we assume that the source of an application with
SCCP state tracking is a linkset. Send the message to that
linkset.
|
|
For the SSP functionatilty we will need to have the timers T18
and T20. In the period of T18 we will collect TFP/TFR/TFA for the
reachable nodes of the system. Each of this node will send us a TRA
when it is finished. Right now we assume to only have one node and
stop the T18 after the TRA of this node. Then we would need to send
the TFP/TFR we have collected. On the expiry of the T20 timer we
will need to send our TRA and notify local users.
For more complex routing we will need to have a shared routing
cache and remember which SSNs and OPCs are reachable and have inter
linkset notifications.
|