Bad signalling message

[Pablo Neira Ayuso]

On Tue, Oct 16, 2012 at 10:44:00AM +0200, Lennart Müller wrote:
>    Hi,
> 
>    some problems with latest git clone and nanoBTS 165AU...
> 
>    <0002> gsm_04_08.c:412 -> LOCATION UPDATE ACCEPT
>    <0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 05) Sending 0x02 to MS.
>    <0002> gsm_04_08.c:754 -> MM INFO
>    <0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 05) Sending 0x32 to MS.
>    <0002> gsm_subscriber.c:337 Subscriber 262620001000026 ATTACHED LAC=10
>    <0003> gsm_04_08.c:1158 TX APPLICATION INFO id=0x00, len=4
>    <0001> gsm_04_08.c:116 (bts 0 trx 0 ts 0 pd 06) Sending 0x38 to MS.
>    <0000> abis_rsl.c:1542 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION
>    <0002> gsm_04_08.c:1045 TMSI Reallocation Completed. Subscriber:
>    262620001000026
>    <0000> chan_alloc.c:429 (bts=0,trx=0,ts=0,ss=0) starting release
>    sequence
>    <0003> gsm_04_08_utils.c:231 Sending Channel Release: Chan: Number: 0
>    Type: 1
>    <0004> abis_rsl.c:618 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD
>    <0004> abis_rsl.c:1017 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive
>    channel
>    <0004> abis_rsl.c:1017 (bts=0,trx=0,ts=0,ss=0): MEAS RES for inactive
>    channel
>    <0000> abis_rsl.c:1542 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION
>    <0004> bsc_api.c:638 Got data in non active state(RELEASE REQUESTED),
>    discarding.
>    <0019> input/ipaccess.c:454 Bad signalling message,sign_link returned
>    error
>    <0019> input/ipaccess.c:260 Forcing socket shutdown with no signal link
>    set
>    <001b> bsc_init.c:337 Lost some E1 TEI link: 1 0x81e4768
>    <001b> bsc_init.c:337 Lost some E1 TEI link: 2 0x81e4768
> 
>    I have no clue if that is a problem of configuration, nanoBTS or abis
>    library. With an old version (Feb 2012), the message...
> 
>    <0019> ipaccess.c:425 Bad signalling message,sign_link returned error.
> 
>    ...appears too, but socket is not being shut down.

This was recently changed to perform robust error handling.

But thinking it's too much to close the signalling link on recoverable
errors coming from the signalling layer.

Would you give a try to the following patch? Thanks.