Attention is currently required from: laforge, pespin.

View Change

2 comments:

• File src/osmo-bsc/lchan_fsm.c:

  • Patch Set #1, Line 1207: /* if SAPI=0 is gone, it makes no sense if other SAPIs are still around,

    can do, but it's in the commitlog as Related.

    Ack

  • Patch Set #1, Line 1210: * seem to send a RLL_REL_IND for SAPI=3 if there was already one for SAPI=0 */

    it is _not_ applied for TCH, I guess the rationale is that there may still be speech frmames that we […]

    Some of my notes made while trying to understand what's happening here. handle_rll_rel_ind_or_conf() is called on LCHAN_EV_RLL_REL_IND and LCHAN_EV_RLL_REL_CONF. These events are sent from abis_rsl_rx_rll() on receipt of RSL_MT_REL_IND and RSL_MT_REL_CONF, respectively. So we're dealing with the RSL specific coding of the link ID (which is different from DLCI).

    RSL Link Identifier is defined in 3GPP TS 3GPP TS 48.058, section 9.3.2, and coded as follows:
        
          .... .SSS - SAPI value used on the radio link;
          ...P P... - priority for SAPI0 messages;
          CC.. .... - control channel identification:
            00.. .... - main signalling channel (FACCH or SDCCH),
            01.. .... - SACCH,
            other values are reserved

To view, visit change 27818. To unsubscribe, or for help writing mail filters, visit settings.