summaryrefslogtreecommitdiffstats
path: root/openbsc/doc/channel_release.txt
AgeCommit message (Collapse)AuthorFilesLines
2012-12-23lchan: Introduce T3109 handling for the release procedureHolger Hans Peter Freyther1-1/+2
T3109 is started when the SACCH is deactivated. It is stopped when the phones sends the DISC/UA/UM on LAPDm for the main signalling link. In case of timeout the abnormal release procedure will be initiated. Make sure to not issue the SACCH Deactivate twice to avoid confusing the equipment. This is still not fully spec compliant. In case of a timeout the abnormal release handling will be started which involves starting T3111+2. The error handling should be split out of the rf channel release method, e.g. lchan_release should be called and check if the channel release was already initiated.
2012-12-23lchan: Release the lchan more quickly, align with GSM 04.08Holger Hans Peter Freyther1-10/+9
* Release all channels with SAPI > 0 with the "local end release" (as of NOTE 1 of GSM 04.08). * No need to wait for all SAPIs to be torn down and the normal REL_IND/REL_CONF will call rsl_handle_release and the channel should be released. * Update the documentation
2012-04-18lchan: Fix the name of the SACCH in the variable namesHolger Hans Peter Freyther1-1/+1
Call the channel by the right name.
2010-09-03channel_release: First attempt to update the doc to new code.Holger Hans Peter Freyther1-23/+42
2010-06-28bsc_msc: Remove use_count from the subscriber connectionHolger Hans Peter Freyther1-0/+2
A channel will be released in case of * Errors via the clear_request callback... * no more transactions and operations are going on. This means that if we do something without a transaction the channel might be closed down right away. The bug fix will be to create a transaction/operation.
2009-08-10add some document about the channel release procedureHarald Welte1-0/+74
also note how we are not doing what the spec says :)