Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
If we end up with a channel that has refcount of zero,
has no msc_data attached and the handler has not returned
1 we will just close it.
|
|
This can help to detect 'stale' channels in a network.
|
|
The nanoBTS will send us at least one measurement report
after we have decided to close the channel... degrade that
output to a debug message.
|
|
We have added two commands with the same name to the tree..
the second one should have been the BSC...
|
|
|
|
Inside the access-list we have a list of entries that have
either one allow or one deny rule... we do not allow to remove
a single rule but one has to remove the whole list, in that case
talloc will handle cleaning all entries.
Right now the matching is O(n*m) as we traverse the list
(multiple times) and run the regexp multiple times. One
way to make it faster would be to concat all regexps into
one.
|
|
|
|
The crash happened when we had released the primary channel
for one reason or another but still got the assignment complete
on the secondary. This null checking is some extra caution, with
the previous commit we should fail the msc_data test early in
this method.
|
|
When closing a SCCP connection and any of the two lchan's are open,
then close them down properly.
Move the lchan freeing into a new method and call that one from the
SCCP connection close handling. Move the bss scp data varaible to
the top of the context..
|
|
|
|
The bssap.c code is sending a multirate config with
only AMR 5.9kb marked as supported, the MSC does not
like if we assign a FR channel and send the GSM 0808
FR AMR mode back to the MSC. So change the code to
not look at the channel type for AMR...
|
|
I still believe NMO_III is what we want, but as indiciated some phones
absolutely refuse to even connect to the GPRS network in this mode :(
|
|
I added this to have the patch in the history, I don't think
that we need to include this but it is good to have it cherry
pickable in the history.
This reverts commit 290a11d0ad7f01564182834d53b2c1073d754c2a.
|
|
The value of this config is not known.... the paging load
needs to be tested again with these parameters...
|
|
Use the values but the paging configuration from a trace...
|
|
|
|
We need to start at argv[1] for the regexp of
this access-list, also subtract one from number
of items..
|
|
vty->index does not hold a BSC Config at this point as we are
on the nat level... use the global _nat pointer for now...
|
|
|
|
One can set one access-list to one BSC and one
access-list to one NAT. The matching of IMSIs
remains the same for now, also applying the
white/blacklist. Access lists can not be deleted
for now and no perf opt is done (e.g. one could
cache the result of the last lookup in the bsc
struct).
|
|
|
|
* Enable sending RLC3
* Use values from the trace..
This is not intended to be merged to master as this enables the
RLC3 that the comment claims to only work on EGPRS enabled models
and it is changing timers to hex indicating a change where none
happened... This is mostly for testing.
|
|
This is applied to all incoming BSC connections.
|
|
|
|
|
|
|
|
The previous code just hardcoded RSL_BCCH_CCCH_CONF_1_C, but
we need to inspect the timeslot config to know what to use.
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
|
|
Do not attempt to patch RTCP packets...
|
|
Allow to set the TOS field via the VTY interface. The
SO_PRIORITY was not used as it has no effect on the
packets being sent (in contrast to the documentation).
|
|
We will need to confirm the connection, then we can send the
GSM48 message, then we need to close the connection... the
embedding in the refusal method was way too easy..
|
|
|
|
|
|
|
|
Right now it was not possible to just find a connection, by returning
the connection that is created we will have direct access to it. It
will be used by the local connection handling.
|
|
The msgb needs to be around when we access the parsed structure
but that needs to be guranteed by the caller handing out the parsed
structure.
|
|
A local connection is only between the MUX and the real BSC. We will
not forward anything to the MSC. This will be needed for the IMSI
filtering as sending a CREF is not liked by every BSC...
|
|
In case of a RLC message we will destroy the SCCP connection. This means
that accessing the con and con->bsc will access old memory. Keep the status
local and move the con into an inner scope.
|
|
|
|
|
|
Split out the msg generation from the sending, this will
be used by the nat to send a refusal message.
|
|
We will need to generate messages with a proper reason
and it is easier to do that from a dedicated method.
|
|
Apparently I could not find the vty_interface_bsc.c when I was
searching for it. Move an extra BSC command into that file.
|
|
|
|
|
|
We are analyzing each CR message and it is nice to know the
reason these connections were created. Change the nat method.
|
|
|
|
|
|
This is a generic MI extraction for the MI if it is followed
after a classmark. For the Phase1 Phones the classmark2 is not
four bytes but it might be different. This code can be used
by the CM Service Request handling as well.
|
|
|