Holger Hans Peter Freyther 4b85a32360 chan_alloc: Change Channel Release to release SAPIs, then the channel ... Currently every SAPI release indication will trigger the channel. It was possible that we had SAPI=3 and SAPI=0 allocated and we tried to release the channel by sending a RF Channel Release, the BTS answered with a RF Channel Release ACK but also sent the SAPI Release Indication which triggered a channel release here. So it was possible that we would have released a newly allocated channel because of the SAPI release of the old connection. This code now works by releasing all SAPIs from highest to lowest, then sending a SACH Deactivate and finally releasing the channel. This approach is in use on the on-waves/bsc-master.		2010-07-31 04:09:38 +08:00
..
openbsc	chan_alloc: Change Channel Release to release SAPIs, then the channel	2010-07-31 04:09:38 +08:00
Makefile.am	sccp: Use the external libosmo-sccp as sccp implementation	2010-07-31 04:09:38 +08:00
compat_af_isdn.h	move openbsc into its own subdirectory	2009-06-10 05:40:52 +08:00
mISDNif.h	move openbsc into its own subdirectory	2009-06-10 05:40:52 +08:00