Fix SACCH channel release indication not sent to BSC after location update.
Based on GSM 04.08 3.4.13 RR connection release procedure, after the network sends a deactivate SACCH it receives DISC from MS which cause BTS to send RLL release indication to BSC in order to stop T3109 timer. It has been found that after a location update BSC never receives RLL release indication which causes a T3109 timeout because no TCH is currently allocated. This fix ensures RLL release indication to be sent to BSC when no TCH is allocated in the particular case of a location update. Change-Id: Ibe2a365641eb8c9a7f0a462b7393ec3fd28cc366
This commit is contained in:
parent
1beb9bcbe0
commit
eb4a3392e1
|
@ -2284,7 +2284,8 @@ int lapdm_rll_tx_cb(struct msgb *msg, struct lapdm_entity *le, void *ctx)
|
|||
gsm_lchan_name(lchan), rsl_msg_name(rh->msg_type));
|
||||
|
||||
/* REL_IND handling */
|
||||
if (rh->msg_type == RSL_MT_REL_IND) {
|
||||
if (rh->msg_type == RSL_MT_REL_IND &&
|
||||
(lchan->type == GSM_LCHAN_TCH_F || lchan->type == GSM_LCHAN_TCH_H)) {
|
||||
LOGP(DRSL, LOGL_INFO, "%s Scheduling %s to L3 in next associated TCH-RTS.ind\n",
|
||||
gsm_lchan_name(lchan),
|
||||
rsl_msg_name(rh->msg_type));
|
||||
|
|
Loading…
Reference in New Issue